4 Comments


  1. I have just recently been adding an explicit reference that my plugins are released under a GPL license due mostly to the discussions here. Every one of my plugins will include this reference, included under “Other Notes” in the readme.txt file as well as in the main plugin PHP file with their next releases.


  2. Ideally, you should put a message in the header of the PHP file itself that explains the license. This way, the license declaration travels with the file.

    I add this to the beginning of all my plugin’s PHP files:

    Copyright 2010 Samuel Wood (email : otto@ottodestruct.com)

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License version 2,
    as published by the Free Software Foundation.

    You may NOT assume that you can use any other version of the GPL.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
    GNU General Public License for more details.

    The license for this software can likely be found here:
    http://www.gnu.org/licenses/gpl-2.0.html

    Simple, easy.

    You don’t really have to include the entire license. Specifying which license is valid and giving probable location is enough. It’s up to the user to find the terms and agree to them to gain the rights specified in the license.


  3. @Otto -

    Ideally, you should put a message in the header of the PHP file itself that explains the license. This way, the license declaration travels with the file.

    That’s what I do, too, Otto. I also explicitly state the license (and version), and the URL to find the full text of the license, using “License” and “LicenseURI” slugs.

    Simple? Easy? Very much so.

    The problem, though, is that there is currently nowhere on wordpress.org/extend/plugins Developer Center that either a) explicitly states that such a declaration MUST be made, or b) gives suggestions/examples for how to make such a declaration.

    There is good information in the Codex, but that information isn’t even linked from the Extend/Plugins Developer Center, where the repository guidelines exist.


  4. @Otto – I like your “license” better than the verbiage that I am using. Time for more plugin updates …

Comments are closed.