[TYPO3-50-general] Adding PHPCR to NEOS

[Chris Zepernick]

Hi Robert,

will check on the weekend and get back to you during the next week.

As Far as I can see it at the moment only the TYPOP3CR would need to be 
replaced with DOCTRINE.ODM, right?

cheers

Chris

On 2012-10-09 13:01:11 +0000, Robert Lemke said:

> Hi Chris,
> 
> On 09.10.2012, at 14:39, Chris Zepernick (SwiftLizard) 
> <chris at swift-lizard.com> wrote:
> 
>> just started the discussion on Twitter about this topic.
>> Basicly it might make sense to drop TYPO3CR for PHPCR and parts of 
>> symfony2-CMF, especially now that TYPO3 Flow is composer compatible.
>> 
>> What do you think?
>> Pros and Cons please,..
> 
> 
> my position (in short and in general):
> 
> - great if we can use phpcr
> - doesn't have top priority for the core team because first we should 
> concentrate on getting 1.0 out of the door
> - we support anyone taking initiative on this matter (well, you … ;-)
> - implementation must have roughly the same feature set we have now, 
> most importantly: personal workspaces with copy-on-write
> - we must always be able to provide a PHP-only implementation with at 
> least the current feature set
> - Jackrabbit (or Oak) must, if used, be drop in replacements for the 
> key feature set we declare for Neos
> 
> So, what we'd need is a plan for what needs to be done and what 
> implications it has for our current codebase.
> 
> Cheers,
> Robert