How about put all licenses in one big single file?  httpd-2.0 does that this
way.

http://cvs.apache.org/viewcvs.cgi/httpd-2.0/LICENSE?rev=1.5&content-type=tex
t/vnd.viewcvs-markup

If I make the software that depends on cocoon, I can just include this big
license file instead of a bunch of these.

Of course, big license file has _scalability_ problem.  i.e. You have to
edit the file if you add new software in cocoon.

Regards,
Punky

----- Original Message -----
From: "Stefano Mazzocchi" <[EMAIL PROTECTED]>
To: "Apache Cocoon" <[EMAIL PROTECTED]>
Sent: Thursday, January 17, 2002 7:17 AM
Subject: [legal] getting legal things straight


> as we start getting bigger and more recognized, we must take into
> serious consideration our 'legal shield' which is done by software
> licenses.
>
> Cocoon ships with an incredible amount of libraries and only a few of
> them have a license explicitly indicated.
>
> [note: all ASF projects have equivalent but still different licenses]
>
> So, here is my proposal:
>
>  1) create a /legal directory in the CVS
>
>  2) move our license there
>
>  3) place all licenses from the shipped libraries there.
>
> ASF software includes:
>
>  - Avalon
>  - Commons (both jakarta and XML)
>  - Regexp
>  - xalan
>  - xerces
>  - axis
>  - batik
>  - fop
>  - lucene
>  - velocity
>
> non ASF software is:
>
>  - BSF
>  - Deli
>  - Hypersonic
>  - jimi
>  - jstyle
>  - jtidy
>  - maybeupload
>  - rdffilter (what is this for?)
>  - resolver (will move to xml-commons, but for now is sun's stuff)
>  - rhino
>  - XML:DB
>  - XT (why are we still shipping this that even James Clark doesn't use
> it anymore?)
>
> Can we please fix this legal stuff before release?
>
> Thanks.
>
> --
> Stefano Mazzocchi      One must still have chaos in oneself to be
>                           able to give birth to a dancing star.
> <[EMAIL PROTECTED]>                             Friedrich Nietzsche
> --------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to