[TYPO3-dev] Experience from usergroup meeting about core development

[Frank Gerards]

Hi,

I share your impression mostly and I add, that communication of core-team development lacks a bit of transparency.

For myself I would like less features, but stable maintenance by the core-team dedicated to a feature.

I also think, that due to the FLOW3 and Phoenix development, the vision of TYPO3 v4 has gradually blurred and 
that tends to affect team-spirit here and there.

I think the Developer Days are a very good event to get momentum on important subjects of core-development again
and I hope there can be like a voteable wishlist or sth for TYPO3 users, that don't have the know-how or time
to code features TYPO3 is missing for practical enterprise use. Each voted feature could then be added as a task
to a core-team or a new team could be built up, if enough devs are interested.

Finally, I tend to see the future of TYPO3 like this: 

TYPO3 v4 will continue to be developed after Phoenix comes up, but will be more focused on the "KMU" segment
than on really big enterprise sites. These sites will be developed with the OO-toolset of Phoenix (and FLOW3).
The success of Phoenix for the average TYPO3 Integrator/developer will depend mainly on Typoscript and good
tutorials on the plugin development. Only few devs will take full advantage of DI or AOP as the majority of
integrators or devs esp. for small and mid-sized TYPO3 projects will continue thinking procedural or Typoscript-driven.

Regards,
Frank

-----Ursprüngliche Nachricht-----
Von: typo3-dev-bounces at lists.typo3.org [mailto:typo3-dev-bounces at lists.typo3.org] Im Auftrag von Georg Ringer
Gesendet: Montag, 13. Februar 2012 08:03
An: typo3-dev at lists.typo3.org
Betreff: [TYPO3-dev] Experience from usergroup meeting about core development

Hi guys & girls,

I just wanna share a part of the experience / result from the last austrian usergroup meeting.

The common opinion was that there is no direction of development which is then followed by the whole core team. Everybody does the features which are nice for himself but nobody checks the requirements of an enterprise cms or from the competitors.

There was a nice comparison to the red cross and the voluntary fire brigade ("freiwillige feuerwehr"): In both and TYPO3, it is an own decision to work for those and you do it in your spare time *but* what you do there then exactly is told by the captain and everybody follows.
It would be impossible to extinguish a fire if everbody wants to drive the truck or at the same time nobody wants to This leadership is kind of missing and hindering for development.

I would be happy to get your impression, feedback, whatsoever

Georg

_______________________________________________
TYPO3-dev mailing list
TYPO3-dev at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev