Front page | perl.perl6.internals |
Postings from May 2008
Will Coleda wrote: > On Tue, May 6, 2008 at 1:23 AM, Will Coleda <will@coleda.com> wrote: >> The goal for 1.0 is to ship languages separately from parrot; Can we >> get a brief summary of what sort of licensing/copyright issues apply >> when the languages are removed from perl.org repository? >> >> My simplistic understanding is at that point, language authors: >> >> - are free to change the license to any compatible one It doesn't even have to be a compatible license, as long as they're distributing separately. Language modules for Parrot are essentially like CPAN modules for Perl. The license of the virtual machine doesn't impose any restrictions on the license of code that runs on the virtual machine. >> - must maintain the original copyright notices of TPF (but can add >> their own copyright notices as they change files). Yes, at least to start. TPF will happily donate the code for languages developed inside the Parrot repository to any other appropriate group. (Like donating Pynie to the Python Software Foundation, etc.) Once that's done, the TPF copyright notices can be removed. >> Anything else? Languages that are moving out of the Parrot repository may want to think about their own policies for contributor agreements, handing out commit bits, etc. Moving out brings all the rights and responsibilities of a full independent project. The rest is just working out the technical aspects of installing external language modules. AllisonThread Previous | Thread Next