Copyright?

Good day, tboley. I would like to apologize for calling the plugin the same as you. This is just a coincidence. I did not use your code, but simply named my plugin as you did. However, I want to note that I did not violate any community rules or licensing laws.At the request of the wordpress community, all plug-ins must be released under the GPL license . If you`ll read the text of this license, you will see that my actions do not violate the provisions of this license.
Also, there is “Take Over an Existing Plugin” order then it says:

“If a plugin is closed because it was unused, you can skip the rest of this and email [email protected] right away.”

Your plugin has been closed since it has not been updated since 2010. So I acted according to the instructions.
Accept my apologies. If after all that I have outlined here, you still insist that I have to change the name of the plugin, please let me know and we will discuss it.

• This reply was modified 5 years, 3 months ago by Evgeniy Zalevskiy.

Hello bikkel,

it would be great if you rename your plugin. Although my plugin ist not anymore in the WordPress repository, it is active in use by many of my clients. A few years ago I decided to offer newer versions of the plugin only as payed software. Reason for this was “NextGEN Gallery”.

The same plugin name is a problem for my clients, so a new name for your plugin would be great.

Ok, I’ll change the name of the plugin. What about the plugin URL and SVN? Do you want me to replace them too? This will be associated with certain chores.

Hi bikkel, many thanks. There is no need to change the plugin URL and SVN.

The same plugin name is a problem for my clients, so a new name for your plugin would be great.

Hi, as mentioned in your github issues, the problem that Thomas describes for users of the orginal plugin remains even after renaming your plugin. Two of my (old) installs got updated to your plugin. I suspect it is precisley because of the plugin URL/SVN address – so WordPress instances “think” this is the codebase of the old “myGallery” install.
I think the impact is bad for those affected, in my case it was just an annoyance because I already migrated away from “myGallery” and just had the plugin deactivated in the install. I don’t know how many active installs are left out there; supposedly they died out over the PHP upgrades 5 -> 7.
The whole thing makes wonder about WordPress’s way of handling outdated plugins. Theoretically all one needed to “hijack” WordPress installs is to find an since deleted plugin, and use it’s URL to inject your own code in installs still using that plugin. This just doesn’t feel right. ??

That’s why you need to update the plugins manually downloading them from the repository.
By installing a plugin written by another developer, you endanger your system in because inject someone else’s code in it.