[TYPO3-ect] Lauching the "Partner Framework" project

[Ernesto Baschny [cron IT]]

Elmar Hinz schrieb am 25.01.2006 15:31:

> My vision can't bloat the core, because I would remove the core at all. There
> would only remain the TER, an installer and different lists of extensions to
> import.
> 
> You click the list that matches your purpose i.e. "quickstart tutorial" or
> "TYPO3 blog". The rest is done by the installer. If cms isn't insalled yet, it
> would be installed now.

I like that idea. But there are still things that need to be "core",
which is what glues all "extensions" together (e.g. t3lib, which can get
a whole lot slimer if we move most of the classes to extensions).

Reviewed and "approved" extensions is a nice thing that has been
discussed many times as it not only serves the marketing folks, but also
all TYPO3 users who cannot find the "right" extensions. The extension
coordination team should do that, under the wings of the Association.

Major issue seems to be nomenclature. Maybe we should call extensions
"components", which would fit more the "block-building" approach. The
"core" can be renamed to "typo3-glue" or something more unattractive, so
that noone will dare to state that his company is sponsoring the
development of the "typo3-glue". :) It will be more interesting to be
sponsor "components", which can be "core components" or "extension
components" or whatever other category one creates.

Cheers,
Ernesto