Re: [PHP-DOC] LICENSE file
So I would suggest to put the same text into LICENSE as the one we have on the copyright page (just converted to plain text). We also need to have the Zend part there, as long as we include the Zend docs in the PHP manual. Plain text from the copyright page is now in RFC/LICENSE. The members of the PHP Documentation Group are listed on the front page of this manual. In case you would like to contact the group, please write to [EMAIL PROTECTED] sounds a bit strange in a plain text file. Maybe this should have an pointer to www.php.net/manual/en/ ? Yes, that would be better. Any comments from others? There were no comments from others and I just committed the reworded LICENSE to RFC. OK, so if there are not going to be any complaints or comments on this, this week, then we should replace the current LICENSE file. Given that this would be in line with the decisions the listed authors made. Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] LICENSE file
On Tuesday 27 May 2003 21:20, Gabor Hojtsy wrote: > >>So I would suggest to put the same text into LICENSE as the one we have > >>on the copyright page (just converted to plain text). We also need to > >>have the Zend part there, as long as we include the Zend docs in the PHP > >>manual. > > > > Plain text from the copyright page is now in RFC/LICENSE. > > > > > > The members of the PHP Documentation Group are listed on the front > > page of this manual. In case you would like to contact the group, > > please write to [EMAIL PROTECTED] > > > > > > sounds a bit strange in a plain text file. Maybe this should have an > > pointer to www.php.net/manual/en/ ? > > Yes, that would be better. Any comments from others? There were no comments from others and I just committed the reworded LICENSE to RFC. Friedhelm -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] LICENSE file
So I would suggest to put the same text into LICENSE as the one we have on the copyright page (just converted to plain text). We also need to have the Zend part there, as long as we include the Zend docs in the PHP manual. Plain text from the copyright page is now in RFC/LICENSE. The members of the PHP Documentation Group are listed on the front page of this manual. In case you would like to contact the group, please write to [EMAIL PROTECTED] sounds a bit strange in a plain text file. Maybe this should have an pointer to www.php.net/manual/en/ ? Yes, that would be better. Any comments from others? Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] LICENSE file
[...] > > So I would suggest to put the same text into LICENSE as the one we have > on the copyright page (just converted to plain text). We also need to > have the Zend part there, as long as we include the Zend docs in the PHP > manual. > Plain text from the copyright page is now in RFC/LICENSE. The members of the PHP Documentation Group are listed on the front page of this manual. In case you would like to contact the group, please write to [EMAIL PROTECTED] ... sounds a bit strange in a plain text file. Maybe this should have an pointer to www.php.net/manual/en/ ? Friedhelm -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage! -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DOC] LICENSE file
Does the LICENSE file in phpdoc need to be changed now to reflect the license change? Hehe, I have not checked we have a LICENSE file. Yes, it should be changed. RFC/LICENSE contains opl v1.0. After a review (by whom? (you) ;-)) this file can replace the LICENSE in the main directory. Uhm, seems like I forgot this thing, and just reviewed that file. I think a reference to the license would be enough. With the current license text you added to RFC/LICENSE the two options seem to be selectable while they are selected. I have sent an email message a few weeks ago to the contact provided at the opencontent site for questions regarding the usage of the license, but have not received any answer. I was interested in particularly the incorporation of the options if we elect both of them. So I came to the decision to have an incorporation by reference. That is still fully valid, and would lead us to no problems on modifying the license to express that we elect those options and they are not selectable... So I would suggest to put the same text into LICENSE as the one we have on the copyright page (just converted to plain text). We also need to have the Zend part there, as long as we include the Zend docs in the PHP manual. Goba -- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
