Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

What's licensing got to do with it? 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Is a fundamental problem wiht Public Domain code a Problem and ALv2 that I don't understand ? I understand there might be legal issues with PD code that don't arise with MIT licensed code, but is there is implication that Public Domain code is unacceptable? This may sound like an odd question, but ... If so, will that limit the ability to incorperate code say writen by employees or contractors of U.S. Government since the U.S. Government can not by law assert a copyright? (and the writer is not be able

    • 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.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.