[TYPO3-ect] ECT - roles and responsibilities

philip.almeida at ippimail.com philip.almeida at ippimail.com
Wed Jul 2 12:39:13 CEST 2008


Hello,
> Hello Franz,
> 
>>> I think we
need several coordinators. You're the best for the lib/div
>>> framework. Seems so that nobody can coordinate all
TYPO3-projects what
>>> needs any kind of common API. ;-)
>>>
>>> Do we reach a consensus on it now?
>>
>> So what is the common opinion of the extension
developers?
>>
>> 1) The div/lib should still be
developed in the ECT. It will be
>> refactored as much as
needed and considered usefull.
>> 2) The div/lib should be
moved now into TYPO3 Core and only Core
>> developers will make
decisions on it.
>> 3) A completely new MVC framework shall be
developed instead of lib/div.
>> 4) Another MVC framework
extension shall be taken und developed instead
>> of lib/div.
All current code of lib/div will be put there.
My Opinion: 
I
go with number 2 but with the following notes:
Development should
continue to be done in current  lib/div ALPHA, the core version may be
versioned from the Alpha and only core team may commit it to
core.
The Alpha version will be the "forge" for upcoming
core version and may be developed  together by core and ETC.
LIB/DIV
would be a optional* install in core and a new standard for MVC
programming in TYPO3 version 4 . The main tutorials should be updated so
new developers start to now the existence of this new paradigm. This shoud
give a new breath to young typo3 developers and we should see the upcoming
of new extensions based on MVC.
*IMPORTANT: Do not forget the mvc
kickstarter extension, the core team should check a way for a transparent
include of this feature as well (optional or not this is a question for
debate by the big Typo3 Gurus ).
The lib/div/kickstarter  trio can
become a MVC standard in typo3 (althougth there are others ex Ameos.
 
Best regards,
Philip Almeida 
>>
>> I vote for 1) if no good proposal for another already working
MVC
>> extension is made. I would leave it in alpha state. The
API is open to
>> changes with losing compatibility amongst
different versions if the
>> second version number is
different.
> 
> please ask this in a NEW thread, because
it's an important question.
> 
> my opinion:
>
NOW for the current extensions: 1)
> for FUTURE extensions (in 1
year?) as alternative: 4) FORGE-MVC
> 
>>> by the
way: A nice trip-hop radio-station is this:
>>> TripHop
MonkeyRadio SanFranzisco http://groove.monkeyradio.org/
>> This
sounds good,
> 
> yeah :-)
> 
>> -
Franz
> 
> HaveANiceDay!
> Daniel
>
_______________________________________________
>
TYPO3-team-extension-coordination mailing list
>
TYPO3-team-extension-coordination at lists.netfielders.de
>
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-extension-coordination
> 
Email and shopping with the feelgood factor!
55% of income to good causes. http://www.ippimail.com/


More information about the TYPO3-team-extension-coordination mailing list