> does it need a vote?
I think it does.
The decision to provide a multiple backend API on top of the JCR API which
in turn does not limit the abilities of the JCR API and maintains
publication portability across repositories without loss of information or
manual migration will mean a lot of extra work and therefore definitely
another slip in schedules for any next feature rich release.
I recently read on some board notes of Apache:
The projects should not only concentrate on code but also on community. To
me this does not only apply to the inner community of the project but also
to the outreach of the project.
Lenya has managed to catch some attention out there, but a lot of
potential users are waiting on a stable 1.4 release that will probably
feature JCR support. If we keep them waiting too long, they might jump on
other projects, which is not going to help us in extending and sustaining
the Lenya community.
In other words: We might think of making smaller steps, i.e. provide JCR
only now (I understand it will not be too far away) and than think of the
next steps.
Regards,
Torsten
> Michael Wechner wrote:
>
>>>> Other repositories: what about svn ? Wouldn't moving to JCR-only mean
>>>> we can no longer support svn as a backend, and thus use Lenya for
>>>> Apache sites ? IMO that would be a real shame - please enlighten me
>>>> if I got something mixed up :)
>>>
>>>
>>>
>>> I'm afraid that would be the case until an SVN-based JCR storage
>>> manager
>>> (no idea if this is an appropriate term) is available. (or should I say
>>> JCR-frontend for SVN?)
>>>
>>> IMO that is a valid concern.
>>
>>
>>
>> I think it's definitely a concern and even if I am fan of JCR I don't
>> think we should do JCR only.
>
> OK, so the general opinion seems to be to support other repository
> solutions apart from JCR. IMO this decision is quite important for
> our next steps - does it need a vote?
>
> If we decide against a JCR-only approach, we have to face the question
> whether / how functionality should be handled which is provided only
> by JCR at the moment (transactions, queries, etc.)
>
> - don't use the functionality
>
> - mimic the functionality in other implementations
>
> - introduce compliance levels ("This functionality is not supported,
> please use the JCR-based repository")
>
>
> WDYT?
>
> -- Andreas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
