<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">If I understand correctly, I think he's saying that he would release it to the codex under GPL, and release it on his own site under CCbySA.<div><br></div><div>Arlen - you should try working <i>with</i> the system rather than against it some time, I promise it's much more enjoyable and productive all round. You need to pick the battles that are worth fighting.</div><div><br></div><div>John</div><div><br></div><div><br></div><div><br></div><div><br><div><div>On 10 Jun 2010, at 00:21, Jane Wells wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 6/9/10 7:08 PM, Arlen Beiler wrote:<br><blockquote type="cite">I am releasing it under both licences, to facilitate changing it, and what not. GPL is a software licence, and CC-By-SA is a generic license (sort of), more documentation oriented. I would require everyone to release it under CC-By-SA if I had my way. And no, there are no limitations to releasing something under two licences. It is GPL *OR* CC-By-SA, not AND. You can use either.<br></blockquote>However, you do not have your way in this case, and just because you want the WordPress Codex to be licensed according to your desires doesn't make it so. I'm not disputing that GPL is a strange choice for the Codex, I'm disputing that CCbySA is in any way compatible. If you post anything to the Codex under a CCbySA license, it will be removed, as it is incompatible with the overall Codex license.<br>_______________________________________________<br>wp-docs mailing list<br><a href="mailto:wp-docs@lists.automattic.com">wp-docs@lists.automattic.com</a><br>http://lists.automattic.com/mailman/listinfo/wp-docs<br></div></blockquote></div><br></div></body></html>