[TYPO3-ttnews] news2 vs tt_news -> TYPO3 CORE?
Jigal van Hemert
jigal at xs4all.nl
Sun Apr 10 20:11:06 CEST 2011
Hi,
On 10-4-2011 19:08, Jordan van Bergen wrote:
> I didn't intend to start the discussion like it is in this thread now
> but it exactly shows why news should be in the core if you ask me.
(...)
> I see more advantages compared to disadvantages.
I haven't seen any advantages for an extension to be present in the core
in this thread. Maybe you can mention the advantages?
Disadvantages of being a system extension:
- slow speed of fixing bugs:
* you need to wait for a new bugfix release of the core. An extension
can easily be updated in TER and is instantly available
* installing a bugfix release of the core is more work than updating
an extension
- very slow speed of adding features
* you need to wait for a new major 4.x version (twice a year)
- lack of man power; the core team has no resources left to take care of
extensions
It's not easy to exactly describe what goes in the core and what not.
Generally speaking it's functionality which:
- is needed for (almost) every web site (e.g. templating mechanisms are
part of the core, mapping extensions (automaketemplate, templavoila,
...) are not absolutely needed
- is intertwined with core code (e.g. workspaces, dbal, ...)
- is already part of the core
There is a need for a group of high quality, essential extensions which
are (partly) maintained / supported by the core team, but which are
available in TER. It is however very hard to find a model which provides
enough certainty for future maintenance and can be supported by the v4
core team.
--
Kind regards / met vriendelijke groet,
Jigal van Hemert.
More information about the TYPO3-project-tt-news
mailing list