On 06.02.2004, at 18:03, Stefano Mazzocchi wrote:
No, but others might sue you on that code, since no license means "public domain", therefore *you* are responsible for that code, not the ASF.
I hope we (with Magnolia) do not give the impression that the ASF is responsible if things don't work as they should.
Making JCR-RI code available at this stage and with no license was a very big mistake, IMHO. This made people going around saying that they are JCR compliant (Obinary is not the only one)
AFAIK we do not claim to be JCR compliant, but even if so, it would not mean anything as there is no public definition of what exactly that means. There has been no marketing of JCR, so there is no immediate advantage for the time being of claiming to be JCR compliant.
The people that use Magnolia today do so because it is an easy to use product, and it adheres to industry standards, and it is free. Having the JCR-RI at hand, even if premature, made us go into a direction that I consider to be a good choice. The result is, that we have released a CMS that has shown that the JCR-API (even at .8) is useful. I hope that this has been helpful to somebody.
when not even the expert group knows what JCR really is going to be [and that RI is certainly so oudated that it's laughable to include it in any product]
We all have to start somewhere, don't we?
I think this needs to be resolved ASAP.
So do I, so do I.
Best regards Boris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
