What's the proper way to show attribution when using code taken from another open source WordPress plugin?

I'd like to know both in the case of just a particular function, and even for a whole file containing many functions.


The plugin should have information in it regarding the license in use. Look in the readme file (could be called README, readme.txt, README.TXT, readme.md, or some other permutation), the plugin's PHP files (there will be one with a block that begins with:

 Plugin Name: xyz

and that block will often contain the type of license in use. You may also find a License file -- possibly LICENSE, license.txt, license.md, or some permutation.

The License section of the Codex page on Writing a Plugin states that

Most Plugins use the GPL2 license used by WordPress or a license compatible with the GPL2.

Read up on the GPL (GNU Public License) here. (Note that the current GNU page references GPL v3, not v2. I don't know what differences might exist between v2 and v3.)

Markdown on Save Improved was forked from Markdown on Save, and includes this text in its code:

This software is forked from the original Markdown on Save plugin (c) Mark Jaquith

...as well as a link to the parent plugin on its Wordpress.org Plugin home page.

If in doubt, you can always try to contact the plugin's developer(s).

  • Thanks, I would like to know what commenting to use specifically for particular functions that are being taken from other plugins, and for a file of functions. Your example is one I'm familiar with (forking of a whole plugin). – urok93 May 27 '13 at 16:02
  • I would suggest that Section 5 (Conveying Modified Source Versions) of the GPL covers what you're asking about: "The work must carry prominent notices stating that you modified it, and giving a relevant date." That said, I am not a lawyer. – Pat J May 27 '13 at 16:15

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.