[TYPO3-ect] ECT - teamleaders

[Daniel Bruessler]

Helllo Fabien,

== moderator/team-leader/editor ==
>> Daniel Bruessler wrote: in my view a moderator is needed, maybe that's 
>> the best word for it.
> 
> What is the scope of such a role?
> 
> Some suggestions about tasks assigned to the moderator / ECT leader :
> 
> - have a global overview of the different team and projects,
> - encourage developers to coordinate their effort,
> - maintain the different wiki / typo3.org pages up to date.

in forge we can use several categories for the coordination-efforts:
* coord. MVC-frameworks and standards
* coord. Ajax-frameworks and standards
* coord. templating-renderers
* coord. general libraries (e.g. div2007)
* coord. Calendars
* coord. Form-libraries
* coord. export/import (PDF, ODF, DocBook)
* coord. payment-libraries
* coord. auth-libraries

These categories would NOT be coding-efforts, this would be 
coordination-efforts.

##Who does see the point that I mean?


== content ==
> http://wiki.typo3.org/index.php/ECT/Homepage
> http://typo3.org/teams/extension-coordination-team/
> http://...
> 
> It looks like the moderator needs some good communication skills more 
> than technical!


it's easy: the ECT was born in the wiki because the wiki was the only 
usable platform at that time. And I really know what is in the wiki. The 
team-page on typo3.org was made by Steffen and me and is a excerpt from 
the wiki-pages.

=> in my view as wiki-maintainer it IS important to move from wiki to 
forge. and again: lib/div is just ONE project of ECT.


== lib/div, FLOW3-MVC aka gimmefive ==
>> Steffen Kamper wrote : the goal of ECT was to have a platform, where 
>> teams are build to develop extensions instead of 10 extensions doing 
>> all the same.
> 
> That's my opinion too... and the benefit goes to everyone.
> 
>> Benjamin Mack wrote:  Why not finish div/lib and that's it then? It's 
>> been long enough in alpha/beta state now.
> 
> Well... for many, it's often a question of time. Unfortunately, at the 
> moment, I don't have enough
> realistic time to invest.
> 
> Furthermore, I see a lot of potential in gimmefive
> http://forge.typo3.org/projects/show/extension-gimmefive
> 
>> I would love to have the ECT team work closer with the 4.x core team, 
>> so we can maybe integrate
>> some cool things.
> 
> Yes, but this kind of work is certainly harder. As I far as I have 
> understood, lib/div is supposed to be a light framework without 
> dependency with the past.
>> However, "cal" from the ECT is great, but as you see, it also defined 
>> its own MVC framework again
>>  --- why reinvent the wheel again and again and not collaborate? (no 
>> offense to the cal guys, I just think communication is important).
> 
> That's maybe for some historical reasons. At the time, I am not sure 
> lib/div existed.

Yes, cal was earlier, and lib/div had the view to be extremely flexible.

> kind regards,
> 
> Fabien

Cheers!
Daniel