I recently played with a plugin which I liked a lot, but felt it was missing something. So as first stage I went and wrote a tiny plugin (my first), that just added the needed feature - meaning, that the original plugin still had to be installed for something to work.

Now I gave credit to the authors for doing most of the job, but I have to think of the future, what happens if they decided to stop developing that plugin or don't resolve issues regarding it. My plugin will stop working or will potentially become incompatible with future Wordpress versions.

Would it be ethical for me to just avoid the issue alltogether by copying their code into mine and renaming the plugin functions? This of course causes other problems, but now they are my problem to resolve. What say you?


I'm assuming for now that the plugin is open source. If so ...

Send them an update

Most devs appreciate contributions from the community. Contact the original authors and offer your code as a patch to add your new feature.

Reference the plugin

Optionally, you can just hope that they keep developing the system and offer your smaller plugin as an extension. Just be sure to keep it up-to-date with a list of compatible WP versions and the 3rd party plugin versions.


Open source software is meant to be extended, adapted, and distributed. You have the right under most OS licenses to edit and redistribute the software so long as you follow a certain set of rules (i.e. maintaining original copyrights, releasing under a compatible license). I can't speak to specifics without knowing which plugin you're using, but in the majority of cases forking the plugin and releasing your own version is 100% acceptable.

  • These are all great suggestions, I think #2 would be the best option for this specific case. The plugin in question (mine) is wordpress.org/extend/plugins/floating-theme-list you can see the used plugins in the readme and plugin description. In fact, the second plugin in the list appears to be a fork of the first. – Moshe Eshel Apr 2 '12 at 23:43
  • 1
    @MosheEshel i know i helped you get this plugin going in your other question, but idk where to weigh in here. all are valid options. it has a different enough look to support a fork in my opinion, but it can be easier if the original author folds your code into the main plugin. #2 seems like a happy medium for as long as the main plugin works. – helgatheviking Apr 3 '12 at 2:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.