Re: svn: /php/php-benchmarks/trunk/ benchweb/config.php benchweb/deploy.php benchweb/functions.php
benchweb/installers/phpbb/bench/LoremIpsum.class.php benchweb/installers/phpbb/bench/Post.php benchweb/installers/phpbb/bench/Record.php bench
| From: | Nuno Lopes | Date: | Fri, 14 Aug 2009 13:03:21 +0000 |
| Subject: | Re: svn: /php/php-benchmarks/trunk/ benchweb/config.php benchweb/deploy.php benchweb/functions.php benchweb/installers/phpbb/bench/LoremIpsum.class.php benchweb/installers/phpbb/bench/Post.php benchweb/installers/phpbb/bench/Record.php bench |
||
| References: | 1 2 3 4 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-65291@lists.php.net to get a copy of this message | ||
A php/php-benchmarks/trunk/benchweb/installers/phpbb/phpBB3/The problem with GPL is that it taints all the other code. By using a file that is licensed under GPL, we have to release everything else as GPL. Executing a GPL program is not problem, but everything else is.Besides the licensing issues, its not really something we want to have in svn..I missed the licensing issue, sadly.That way we avoid the licensing issues.What exactly are the licensing issues? I understand that there is a PHP policy to not include GPL code in the repository. I would guess that this is because we can't allow GPL code to mingle with PHP- or Zend-licenced code. In the php-benchmarks section, this isn't important.
Anyhow, we already have GPL code in the php-benchmarks section of the repository, and the last discussion didn't go anywhere. Obviously, we want benchmarks in the repository, some of them will be GPL, and so we need to address this.I'm not very confortable with this, though. A technical workaround is to fork a separate process for each test, instead of including the code (and I believe we already do this). This way we are not including GPL code, we are just running it :P Anyway, whenever possible, we should try to contact the original authors to ask them to rerelease their code with a BSD-style license. I know that the few GPL tests that we have are tricky to sort out, so I would leave them as-is for now.
If there is someone who knows the rules for what goes in the repository (or can point to them), and could tell us why the rules are that way, we can make a decision as to whether this merits an exception?There are no formal rules. It's just that people in the PHP community appreciate the freedom of the BSD-style licenses. In summary, all the drivers and test runners and code produced by us should be licensed under the PHP license, but I think it's fine if a few tests are not. Nuno