[TYPO3-ect] ECT - roles and responsibilities

[David Toshack]

Daniel Bruessler wrote:
> Helllo Fabien,
> 
> == moderator/team-leader/editor ==
>>> Daniel Bruessler wrote: in my view a moderator is needed, maybe 
>>> that's the best word for it.

I think we need a number of roles to fully complement the 
responsibilities of extension coordination. Organization of roles and 
responsibilities within the ECT will hopefully bring more pull in 
getting the quality up and the quantity down of TYPO3 extensions.

What I would like to propose is that we start with some brainstorming of 
possible ECT responsibilities based on the mission statement[1].

Remember, this is brainstorming so don't be shy. Feel free to throw 
something, even just to see if it sticks. If its not suitable enough for 
ECT it can always be suggested to the Association team for delegation.

Once we have a list of responsibilities we can group them into roles to 
manage them. Possibly with some sort of hierarchy so that we can have 
even the smallest (managed) roles leaving nothing to slip between the 
cracks of these voluntary limited roles.


>> 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.

This is a great start. I'll create a new thread for these responsibilities.


> 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?

I do. I definitely believe there should be an ECT team(s) and projects 
on the forge site. It would also be nice to encapsulate T3N's Extension 
Comparison team[2] into the ECT which could benefit both teams.

I think this would require the forge site to be better organized. Maybe 
with more project hierarchy. I like the idea of specific project 
categories like Drupal's module categories[3].

Although it may require a bit of recruiting; I believe there are enough 
TYPO3 _users_ out there to assign people to roles and responsibilities 
for each and every one of these extension categories.

Even if the assignment of these roles change often I think with the 
right role hierarchy we can manage to keep many of these type of minor 
roles filled by TYPO3 users of _any_ capacity.


> => 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.

+1 In fact I see great benefit in moving a lot of the content from the 
TYPO3 wiki in general into the forge site.


> == 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

Me too. Fabien, what do you think about incorporating gimmefive 
functionality into lib/div? So that lib/div functionality can be used 
for v. 4 and simply ignored to use FLOW3 functionality in v. 5?

This would be an even better intermediary than gimmefive alone, but I 
fear this may complicate more than it simplifies. What do you think 
about this?


>>
>>> I would love to have the ECT team work closer with the 4.x core team, 
>>> so we can maybe integrate
>>> some cool things.


+1! I would like to see the day when the "official typo3" extensions are 
treated with similar importance as core extensions.


>>
>> 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.

I would also like to see the day when projects like cal are handled 
completely through the ECT. Including delegating tasks to other TYPO3 
teams[4]. This is definitely within our grasp and I for one would like 
to help make this a reality.


Cheers,
David


[1] 
http://wiki.typo3.org/index.php/Mission_Statements#Extension_Coordination
[2] http://forge.typo3.org/projects/show/team-extcomp
[3] http://drupal.org/project/Modules
[4] http://wiki.typo3.org/index.php/Teams