GPL attribution is one of those tangential topics to a lot of the GPL discussion around WordPress (which I’m not interested in discussing here).

The GPL homepage for GPL attribution information.

Instead, what I’m trying to answer is this:

How do you give proper GPL attribution when using someone else’s work in your work?

Case in point: Let’s say someone is building a theme and wants to bundle some code you’ve written (and it’s available on GitHub) and is trying to attribute it properly to you?

First, this is something that someone was kind enough to ask me when working on a project of his own. Second, I think it’s a great question as it’s something we should all know how to answer since much of our work is likely using other third-party, open source libraries.

Proper GPL Attribution

Remember that the GPL allows for the re-use of code and the four freedoms and all of that, one of the contingencies of using said license and said code is this:

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or

Obviously, irrelevant sections were removed to keep this concise.

First, the remarks above are for GPL-3.0. This is important as WordPress is licensed under GPLv2 or later. Secondly, it’s also my understanding from reading the documentation that you can’t really require a person to provide attribution.

After all, the license itself states the following (emphasis mine):

the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program

This is where it starts to get into a legal territory, and I am not a lawyer. Not even close. So though a debate may ensue as to whether or not you must include a license is different than if you ought or ought not to include a license.

If it’s that much of a dilemma for you, then I recommend consulting a lawyer. However, I’m of the mind that if you use code from a third-party library that’s also licensed under the GPL, it’s respectful and shows integrity to give attribution where it’s due.

In those cases, this is how I normally do it:

And while we’re speaking of attribution, this is also from a longstanding answer on Stack Exchange.

Ultimately, any discussion about this should be why you ought or ought no to give attribution and proper ways to do it. I’m not necessarily interested in having a debate over the license itself, and I’ll likely be moderating comments that stray far off topic.

Nonetheless, for those who are curious as to how to give proper attribution, I hope this helps (and I hope any additional comments help, as well).


Join the conversation! 2 Comments

  1. Is there a way to keep the attribution in a minified file?

    • There are a couple of ways to do it, but it largely depends on what type of minificiation you’re using.

      Another alternative to mention it in a README or similar file and then list the files that you’re using.

Leave a Reply