On 18 Oct 2004, at 10:24, Steven Noels wrote:
On 18 Oct 2004, at 10:18, Jeremy Quinn wrote:
So, to summarise ....
What package names should I use?
org.cocoondev should be OK.
eg.
org.cocoondev.cocoon.hibernate ???
or
org.cocoondev.hibernate ??
etc.
What license should I add?
You _can_ do AL2 if you make it clear that the redistribution clause is tainted by the LGPL dependency, so people should do their own due diligence. That's quite different from ASF-proper code, since the ASF policy is that the ASF doesn't ship tainted code.
Could we come up with a common caveat to add (under) AL2 ?
Are we going to have a multi-project repository at cocoondev.org?
I could do that.
Excellent!!
Are we going to have an external-blocks build?
That would be cool.
Indeed.
What about JavaDocs? Will we add 'org.cocoondev/*' to the 'packagenames' attribute in the Cocoon's build.xml, so these projects are integrated into the main javadocs for Cocoon?
Thanks
regards Jeremy
--------------------------------------------------------
If email from this address is not signed
IT IS NOT FROM MEAlways check the label, folks !!!!! --------------------------------------------------------
smime.p7s
Description: S/MIME cryptographic signature
