[TYPO3-ect] Groupware bridge or API Layer

[Elmar Hinz]

Jean-Baptiste Rio schrieb:
> More seriously, what extensions are missing to Typo3 to be a groupware ?
> - Users, groups and security access (ACL) : it has
> - Calendar : it has
> - Workflows : it has... but it should have more
> - Planification : it could have
> - Emailing : it has
> - Shared resources (meeting rooms, technical hardwares) : not difficult
> to have
> - Project management : not far if we create two new kinds of pages =>
> Projet and Module, and one new kind of content => Task.

Hi Jean-Baptiste,

we still need to call your collection a patchwork rather than a
groupware. The whole is more than the sum of it's parts. A tight
integration of all components is the chariacteristic of a real
groupware. An integration of functionality and a uniform user interface.

To reach the tight integration is one mayor task of ECT. But we still
don't observe much efforts to work on this integration in this list
from side of the responsible extension developers. I don't need to be
a prophet to say that this way will be a long one. A way to measure in
years rather than in monthes.

We need to compare the distance of this way with the alternative of
adapting a fully integrated groupware into TYPO3. I can't judge wich
will be more promising, but I think it is at least worth to compare
them both or find a mixture.

Regards

Elmar