[wp-docs] GNU General Public Licence

[Arlen Beiler]

That is what I am doing. Dougal described it exactly. If you still don't get
it, think of it this way. I am separately publishing whatever I contribute
as GPL and also as CC-By-SA. Meaning that if you want to use it on a GPL
licensed site, you can; as well as on a CC-By-SA licensed site.

On Thu, Jun 10, 2010 at 7:39 AM, Dougal Campbell <dougal at gunters.org> wrote:

> On Jun 10 2010 2:04 AM, Gooitzen van der Ent wrote:
>
>> If you want to license content about WordPress under a CC-By-SA license,
>>> then you should post it on your own site, not on the Codex, as the two
>>> licenses are not compatible, since they say inherently different things.
>>> Jane
>>>
>>
>> This is an interesting point. If you write content on WordPress which is
>> GPL licensed, why would you then use CC-By-SA. Surely there would be
>> limitations? Depends on the type of  content possibly?
>>
>
> Multiple licensing can be a sticky thing. But it's moderately common. As an
> example sometimes seen in software, a developer might dual-license a library
> as GPL and also under a commercial license. Users can use the software under
> the GPL, and accept the responsibilities of that license. But a corporate
> entity might choose to purchase the code under the commercial license,
> because then they won't be required to GPL any of their *own* code when they
> incorporate the library into their own projects.
>
> I can see dual licensing something as GPL and CC-By-SA for similar reasons.
> In the case of documentation, a publisher might not want to include GPL'd
> content, because it would require them to license the entire book under GPL
> (or a compatible license). But they could choose the CC-By-SA license, as
> long as they give attribution to the original author.
>
> --
> Dougal Campbell <dougal at gunters.org>
> http://dougal.gunters.org/
> http://twitter.com/dougal
> http://twitual.com/
>
> _______________________________________________
> wp-docs mailing list
> wp-docs at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-docs/attachments/20100610/61ed3d63/attachment.htm>