On Fri, Jan 19, 2001 at 12:50:26AM +0100, [EMAIL PROTECTED] wrote:
> On Thu, Jan 18, 2001 at 03:29:31PM +0800, Jim Winstead wrote:
> > In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> > wrote:
> > > On Thu, Jan 18, 2001 at 11:55:30PM +0100, Hojtsy Gabor wrote:
> > >> Do we use chapters/copyright.xml for anything? I don't see where...
> > >> Maybe we can remove it... This is far not actual and the copyright of
> > >> PHP not the doc, so it musnt be there I think... 
> > > 
> > > Don't remove them. Otherwise I will send you may lawyer. Only
> > > discussions on a switch to the Open Public Documentatian are allowed
> > > here.
> > 
> > woah, take a pill.
> > 
> > chapters/copyright.xml is an out-of-date copyright notice for php itself.
> > the documentation's copyright notice is in bookinfo.xml.
> > 
> > i don't see where chapters/copyright.xml gets included in the generated
> > documentation, actually, but i could easily be overlooking it.
> 
> I haven't checked Hojtsy' removal. What I ment to say was, we need a legal
> notice. A Open Public Documentation license would be better. 

i'm saying we have a legal notice. it is in bookinfo.xml. there is
another "copyright notice" in copyright.xml that implies that php
is copyright 1997 and under the gpl. that text doesn't get output
in html format of the manual. that file can go away. without you
needing to send your lawyer after anyone.

now, on the topic you've brought up, if someone wants to convince
all of the authors that changing the license is a good idea, they
can feel free. i've tried before, and nobody really seems to care.

> With the GPL people all over the world can make money with old PDFs. If
> you understand the GPL this would result in, stop the documentation team,
> we have the rights to distribute it. 

i can't parse that second sentence.

> I have recently put Jouni Ahto on the list of authors, he thinks the same.

does that mean he understands that second sentence? :)

> Have you had a look at amazon or barns and nobles?  You can buy there the
> PHP manual in two parts. 

cool!

(but maybe you're trying to imply this is a bad thing?)

jim

Reply via email to