I've spent a good part of the past week answering Pugs legal questions. Still haven't cleared up all the confusion there, but we're close.
So why is this licensing stuff important? Well, part of Larry's original intent with the Artistic License was to allow proprietary and free versions of Perl to peacefully coexist. It would be great if everyone would peacefully coexist without encouragement, but since this world isn't always nice, we need other tools. The Artistic License helps by limiting the ways people can release a proprietary version, and also by saying what it takes to be considered a "free" version.
To do this it relies on copyright law, the same as the GPL and most other software licenses. The word "copyright" can be loosely translated into plain English as "an artist's right to copy or change their work, or to give it to someone else". In the commercial world, copyright law, is sometimes used to take away freedoms (which is unfortunate). But in the open source/free software world we use copyright law to promote greater freedom. (Hence the term "copyleft" which is a pun on the fact that the word "right" is sometimes used to refer to conservative political views, and "left" to more liberal ones.)
So, if you're wondering why someone would object to having their code released as public domain, or why it's worth spending a week or so to get the terms right, it's this: we want to protect and promote the freedoms of our users.
Is there an appropriate public forum to ask questions about Artistic 2? Is there a FAQ?
You mention answering questions. Is there any record of the question and answer session?
I ask, because the mailing list you mentioned in your announcement has been inactive for 4 years. And the questions asked in the comments section of your announcement have gone unanswered. As have the questions I asked on perl6-internals mailing list back in October.
I don't understand the need for the compilation copyright. But I fear it could be used to legally prevent forks. I fear what I don't understand. Please help me to understand why it is needed.
Re: questions
Allison on 2006-04-25T16:26:51
The perl6-licenses list is dead, please subscribe to artistic2 {at} perl {dot} org. Or, just follow the mailing list archives. I'll try to move all the answers to these kinds of questions there. (And if you see questions of this sort in other blogs or forums, I'd appreciate it if you'd post a link to that list so I don't miss them.)
Re: I don't understand.
Allison on 2006-04-27T18:19:34
No, there isn't a fundamental problem with public domain code and AL2. Public domain code can always be included in anything. (That's the whole point of the public domain.)
I think you're referring to the problem with having Pugs be public domain and then become the production implementation of Perl 6? The problem there is not that we can't include public domain code in AL2 code, the problem is that if all of Perl 6 (or even 90% of it) is available as public domain, then there's nothing to stop an unscrupulous company from creating a proprietary version of Perl 6 and refusing to release the source code or send patches of their improvements back to the free version. (AL2 allows proprietary versions, but only under certain conditions.)
Public domain contributions to the whole aren't a problem.
