jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Marth <mma...@adobe.com>
Subject Re: The destiny of Oak (Was: [RESULT] [VOTE] Codename for the jr3 implementation effort)
Date Fri, 05 Oct 2012 17:19:24 GMT
+1 to the Bertrand's suggestion "same project name, different software name"

This would keep the community together, but also allows us to have different aims for Jackrabbit
(reference impl) and Oak (some level of compliance, not reference impl).

On Oct 3, 2012, at 7:23 PM, Bertrand Delacretaz wrote:

> On Wed, Oct 3, 2012 at 1:53 PM, Tommaso Teofili <teofili@adobe.com> wrote:
>> ...there is a goal in Oak to be less strict with regard to JCR spec compatibility
which, in my opinion, makes a
>> possibly important point of distinction.
>> If this understanding is correct then I think it'd make sense to have separate projects....
> You can have separate software projects/modules in a single Apache
> project - I agree with others that keeping Oak (the software
> project/module) within Jackrabbit the Apache project is less risky in
> terms of community.
> Saying that Jackrabbit 2 is the JCR reference implementation, and
> Jackrabbit Oak (or whatever it's called) is a mostly compliant JCR
> repository is perfectly fine as long as that's clear.
> -Bertrand

View raw message