Update author and GitHub link for Revived BlueBridge

[leobaehre]

Hello,

I don't know how you guys feel about this, but I want to revive this one addon that my server relies on. I have made a change, and because the original author is no longer maintaining it, I would like to continue maintaining it.

If I should mention the old author or anything else, let me know. I can add him because I give him most of the credit for the existing work. I would do some updating in the future and would like to actively maintain it from now on.

If you prefer not to have this, that is also okay.

[TBlueF]

Hi, i asked @Mark-225 and he said he'll think about and respond in a bit ..
lets give him a couple days to respond 👍

[Mark-225]

Hi, BlueBridge author here.

While I agree that I have been quite inactive in terms of improvements and feature requests, my plugin reportedly still works on the newest version. It is not "unmaintained" in the sense that if it actually became incompatible, I would update it to make it work again.
Of course I'm also happy to hear that apparently someone liked my work so much, they wanted to put in the effort into reviving and improving it.
And due to it being open-source you have every right to and are encouraged to create and distribute your own fork of my project.

But simply creating a pull request to replace my name as the author under the official BlueMap listing and keeping my original plugin's name without even trying to contact me about it first comes a bit surprising to me and is honestly not how I feel like you should have approached this.

I'm fine with it if you come up with a new name (or at least some "-reloaded" suffix) and add your fork as a separate plugin to the list (obviously Blue has the final say on whether that would be too much of a "duplicate").
I'm aware that the license only requires you to keep the original project's license text in addition to your fork's license, but I would also appreciate if you made it clear that your fork is derived from my BlueBridge project when you are advertising it on lists like these.

[leobaehre]

Hi Mark, thanks for the thoughtful reply, and you're right. I should have contacted you before opening this PR, and I'm sorry for the not thinking this trough. Replacing your name and link on the existing entry was the wrong approach. This is not something I have done before so I just gave it a try.

I'll rework this PR as you suggested:

• BlueBridge stays listed exactly as it is, under your name and your repo.
• My fork gets a separate entry with a different name ("BlueBridge Reloaded").
• The fork's README and the listing description will state clearly that it is derived from your BlueBridge, with a link to your repo, and your original license text stays in the repo.

I'll push the updated change shortly. @TBlueF, it's of course your call whether a separate entry is too much of a duplicate. If you'd rather not list it, I understand and will keep it on GitHub only.

Mark, thanks again for building BlueBridge and for being so generous about the fork. If you ever want to talk about sharing improvements back upstream, I'm happy to.