[TYPO3-ect] ECT - teamleaders

[Franz Holzinger]

Hello Benjamin,

> I'm not 100% in the ECT and what's going on there, but for me it seems
> like the ECT, mainly div/lib, missed its goal. I thought it should also
> be a starting point for migrating to 5.x, but there seems no
> communication between the teams. Also, I would love to have the ECT team
> work closer with the 4.x core team, so we can maybe integrate some cool
> things.

Only a ECT teamleader could do so. div/lib is for providing a class
collection to replace the _pibase_ class which is not developed any
further by the TYPO3 Core team. And of course it goes to PHP5 and
provides a MVC. However it has stuck in alpha phase.

> Then, there are IMHO some crazy ideas like "div2007" that I think are
> just plainly wrong, as it is another dependency and some more extra you
> have to juggle around with versions, incompatibilities and the
> extensions (hard enough with TYPO3 4.1 and 4.2 already after updating).
> Developing extensions make it even harder then. "This extension only
> runs with TYPO3 4.0 and div2007 and lib2008" ;-)

No this is wrong. The div2007 has become necessary because the API of
div might still change a lot. And TYPO3 is not able to have more than
one version of an extension installed at the same time.
Otherwise it would not be possible to use 2 different extensions which
relied on different div APIs. So you could not download the latest
version of an extension if you need other extensions depending on div
which have not been updated any more.

> Why not finish div/lib and that's it then? It's been long enough in
> alpha/beta state now.

There seems to be no developer group any more for div/lib. And I think
that div/lib should still be changed a lot. More functionality should
come into it.

> Again, no offense guys, but the ECT should not just coordinate
> extensions but also the development of the core teams with the
> extensions, instead of defining its own core (div/lib). Maybe one guy
> could be in 4.x, 5.x and the ECT to coordinate?
What do you mean exactly? Should the FLOW3 be used instead of lib/div in
the future? But where should the functions of lib/div come then? Will
new requirements of extensions and patches come into TYPO3 Core, but
where? The response time in the Core list is very long in some cases.
And the time between new TYPO3 versions with an enhanced API is very
long. It takes many months until a new class would be put into the next
TYPO3 version. But if you develop an extension than you require that a
new function is available after a very short time. So I fear that no
coordinated development of extensions would be possible, because
everyone would still continue to write his own function API and classes.


Franz