Re: PHP development principles
| From: | zoe | Date: | Thu, 30 Oct 2008 09:54:42 +0000 |
| Subject: | Re: PHP development principles | ||
| References: | 1 2 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-2947@lists.php.net to get a copy of this message | ||
Hannes Magnusson wrote:
On Wed, Oct 29, 2008 at 17:02, zoe <zoe.slattery@googlemail.com> wrote:Hi I sent a suggested patch to the svn-migration list a couple of weeks ago, see here: http://news.php.net/svn.migration/109. Hannes suggested that this would be better discussed on the webmaster mailing list, so I'm posting it here too. It's an attempt to summarise PHP licensing in terms that can be simply understood by potential committers to PHP. With the usual IANAL caveat of course :-) The patch is here: http://pastebin.ca/1239610"PHP will be redistributed under the PHP 3.01 license [link]" wouldn't something like "PHP is distributed under the PHP license (currently r3.01) [link-to php.net/license, not any version]" be more suitable? Yes, it would :-)
You also probably want to add more <br /> or more <p> there rather then all the \n :) ooops - yes
It seems very php-src and pecl specific.. People signing up for pear/doc/gtk/gd accounts will also have to go via that form. That's a good point. I know the docs have a separate license and what I have written does not apply to some of the things you have listed.I looked at what Perl and Python do, they both have "about" pages where the licenses are described in simple non-legal terms. We could write pages like that for PHP and link to them from the CVS account request form, I think adding all of the possibilities into the CVS request form would make the form too long. Is that a better solution?
-Hannes