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

use Perl Log In

Log In

[ Create a new account ]

Bernhard (4508)

Bernhard
  Bernhard.Schmalhofer@gmx.de
https://www.xing ... hard_Schmalhofer

A freelance software engineer with experience in webapplications, databases and bioinformatics.

A contributor to Parrot and the person behind Pipp.

A physicist who worked with third sound in Helium-III and CCD X-ray detectors.

barney on irc.perl.org
github: http://github.com/bschmalhofer [github.com]
LinkedIn:http://www.linkedin.com/in/bernhardschmalhofer [linkedin.com]
XING: https://www.xing.com/profile/Bernhard_Schmalhofer [xing.com]

Journal of Bernhard (4508)

Monday April 09, 2007
03:19 PM

Choosing a license for Plumhead

[ #32949 ]

I have been thinking on how to proceed with Plumhead, that is PHP on Parrot. The problem is that I have neither the ability nor the inclining to write a PHP grammar from scratch. So a template is needed. This brings up the question of licensing.

Johnlim's blog http://phplens.com/phpeverywhere/?q=node/view/223 got me jumpstarted on which PHP implementations are out there. I have put my finding into the Parrot Wiki, http://rakudo.org/parrot/index.cgi?plumhead. The projects that look most interesting to me are phc, PHP4Mono and Roadsend. The PHP4Mono and the Roadsend grammars seem to be written from scratch. Both projects are GPL licensed. The phc grammar is derived from the PHP 5.2 grammar.

PHP 5.2 is licensed under the PHP license, while parts are under the Zend license. Both licenses are BSD-like, which is quite acceptable to me.

So the plan of the day is to derive the Plumhead grammars from the PHP 5.2 grammar. I'm not sure whether that means that I need to put the whole of Plumhead under BSD license, or whether I can stick with Artistic+GPL.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Generally speaking, BSD-style licenses allow you to redistribute the original or your own derived works under any licensing of your choice. This would give you the right to relicense your derivative work as Artistic+GPL, which would probably be preferable for anything associated with Perl6/Parrot. You should check with the authors of the PHP license and see if they truly intend for this to be allowed. If they don't, though, they should be explicit about it in their license, and/or switch to a copyleft li

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers