[FLOW3-general] Package handling / autoloading

[Jacob Floyd]

My $0.02:

On Tuesday, June 5, 2012 7:27:41 AM UTC-6, Robert Lemke wrote:
>
> So, if technically possible, we should provider Composer.json files for 
> all of the packages we maintain. The code which handles FLOW3 packages 
> separately should only be kept for BC reasons. We might even generate a 
> Composer.json file for those packages which don't have one yet. If viable, 
> we should also get rid of the Meta/Package.xml.

 
+1 on having just one metadata file (composer.json works great)
 

> Apart from that, our package management should not, in my opinion, 
> introduce non-trivial features (like special class loading rules) which are 
> not compatible with Composer. 


+1 if we do introduce any features, I'd love to see them contributed back 
to composer. That's just being a good open source community member (Just 
like how Sebastian has been working on Aloha and getting stuff included 
'upstream'. That's awesome!)
 

> I think that we should take the opportunity and make some buzz about 
> FLOW3's - and also TYPO3's - Composer support at the time we release it. 
> Jordi will certainly appreciate such a campaign and spread the word which 
> can give additional attention to TYPO3 / FLOW3. 
>

+5 The word needs spreading ;)