[TYPO3-ect] ECT - roles and responsibilities

[Franz Holzinger]

David Toshack a écrit :
> 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.

Yes, that is the point.
We need a library extension like lib/div to where all code can be put
which is needed in most extensions and which will be used instead of the
pibase TYPO3 class.
We can add more specific extension libraries which are needed by a
smaller number of exensions.

> What I would like to propose is that we start with some brainstorming of
> possible ECT responsibilities based on the mission statement[1].
- contact all extension developers to contribute to the ECT extensions.
They shall give up their own extension libraries and move their written
code into these ECT library extensions. The ECT coordinator should do
this move or give the guidelines how to do so.

- Also copy and improve code from the TYPO3 core on which the further
development has been frozen.

- Change the code and API and release new versions of the library
extensions. (refactoring) Make many releases, because the developers
want to see their methods very soon in the TYPO3 TER.

>> 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?
But you would also need a group of persons who take care of the code.
So a separate ECT code decisions and code review team will be needed.

> 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.
A ECT coordinator must survey on these teams. If no work is done and a
leader disappears then another one must be found after a short time.

>> 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.
Some decision must be made which MVC extension sto use. So maybe a
redesign of lib/div should be started to fit all needs. Then this should
be used as the base MVC sytem for most TYPO3 extensions. cal should be
one of the exensions which use this.

Franz