On 8 Feb 2004, at 08:15, Boris Kraft wrote:
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.
No, look, it was *our* fault (ASF + Day) to provide that source code at an early stage. You found it, saw that you could use it and you did. That's perfectly fine for me (as long as you don't market it as something else). We are not going to sue you or anything, and you took all the risks in building a product on top of this. If this is fine for you, that's fine for me as well.
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
From the Magnolia web site (http://www.obinary.com/en/magnolia.html):
<quote src="http://www.obinary.com/en/magnolia.html";> Magnolia in a nutshell
Magnolia is the first open-source content-management-system (CMS) which adheres to the upcoming standard of Java content repositories (JCR).
[...]
</quote>
This is a damn lie!
What you are first to adhere to is a pre-alpha 0.7 version of the API which is now at version 0.9.5 and strongly different from what you have (including radical non-compatible changes at the very core interfaces).
But, of course, that would scare all your potential users away so you choose to reshape reality a little, hoping that people are stupid enough to buy the fact that you can be adhering to a technology you don't even have access to!!!
Note to people: Obinary is *NOT* part of the JSR170 expert group, nor part of the JCP, therefore has no access to the JSR170 spec and doesn't know what has been changed.
You are stating the false and you are promoting yourself with the work of others, giving a false impression that might damange other open source projects that might choose to implement the *REAL* JCR API once is finished. (Slide, to cite one)
And this is pissing me off to no end.
, 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.
I don't give a damn about your marketing advantage. You will understand pretty soon how impossible it is to create a development community around a commercial product, even if the source is open.
What I'm concerned about is the impression that people will have taking a look at your code, thinking that *that* is JCR and making an architectural choice based on your false and misleading marketing advertising.
The reason why I was giving away the spec to almost everybody who asked was exactly to reduce the damange that you might have already done, especially since you somehow managed to get into the Apple Newsletter and got exposed to people who are not aware of the situation, nor read this mail list.
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.
This has been useful to you only and the cost of damanging other people's hard work.
The word "abuse" might not be precise, but it's the first that comes to mind.
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?
Sure, and you choose to use somebody else's work, without giving credits, misleading your users and potentially damaging the face of the upcoming API.
Thanks, very appreciated.
I think this needs to be resolved ASAP.
So do I, so do I.
So, stop tell the truth.
-- Stefano.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
