On Fri, 23 Jan 2004 [EMAIL PROTECTED] wrote:
> > As far as I understand, you can pick whatever license you want as long as
> > you don't redistribute Cocoon classes under a non-Apache license.
> is it possible to be commercial a product based on cocoon?
Absolutely - a lot of people do this; from tiny 1 person outfits to the
size of IBM, Sun or Oracle.
See the first paragraph of the license:
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met
You -do- have to stick to the other clauses of course; in particular for
you clause 2 (as you are propably going to ship it binary):
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
So what that means is that when you ship the product you should have a
directory '3rd party licenses' and/or, say, an appendix in the manual
which lists the one page license.
Do note that although -we-, the asf, insist in the above that you include
the disclaimer (where we say, if it breaks, you get to keep the pieces but
do not come sue us) - but it a) only applies to the apache/cocoon code and
b) you are free to of course sell/offer/give to your customer some more
service, support or warranty. On your own code; but also on cocoon if you
want. It is just that one should not sue us if it breaks.
> or every cocoon based product MUST be opensource
No absolutely not. You can do with it as you please; as long as you abide
by the license. Do note clause '4' and '5' - i.e. you cannot call your
commercial product Cocoon; or use Apache as an endorsement.
Only the ASF can release Cocoon under the Cocoon label. Most organisation
get around that by adding something like 'powered by Cocoon' to their
product title.
I.e. 'LogisticsUnited, powered by Cocoon'(and note hte various 'powered by
icons you can use) is fine; but 'Cocoon LogisticsUnited' is not. And
finally there is clause 3 you want to read:
3. The end-user documentation included with the redistribution,
if any, must include the following acknowledgment: ...
Good to see the commercial ecosystem getting larger with time.
Dw
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
