[TYPO3-ttnews] Switch to news2

[Robert Wildling]

A topic that obviousely is of more people's interest! I'd like to add my 
2 cents here since I already had some discussion in the past without 
having any impact.

Am 17.09.11 12:25, schrieb Jigal van Hemert:

>> The people behind TYPO3 are making some big mistakes if you ask me:
>
> Since TYPO3 is a community product, "the people behind TYPO3" is also you!


This discussion is characterized by the very standard arguments coming 
from the core developers. And "The People behing TYPO3 is also you" is 
exactely one of them.

Not all people behing TYPO3 are programmers - actually I assume only a 
small percentage is. But it is those people - the users - who make TYPO3 
a wide spread and therefore famous CMS. Which is also a curse, because - 
and this is really to be realized! - TYPO3 is a standard CMS that many 
firms, agency etc demand when it comes to gathering offers for their web 
presence. "It has to be TYPO3". (Why not Drupal?)

So meanwhile as a web developer (in Europe at least) there is _no way_ 
around TYPO3, if one wants to stay in business - whether you like TYPO3 
or not, you _need to know it_!

The power of decision influence that TYPO3 has on the marked has to be 
reflected when it comes to the discussion that it is a free CMS. Shall 
everybody donate to TYPO3 so that the features that are really necessary 
will one day get implemented? I personally won't, because developers do 
their thing and seem to absolutely no be willing to implement the 
features that so many people need who made it famous - and who are now 
depended on TYPO3.

It is about time that the core developers start to rethink some facts:

>> 1. No core news extension but an addon extension. Every big open
>> source CMS has a news module in the core of the basic installed CMS
>> system
>
> The Core Team simply doesn't have the man power available to maintain a
> lot of extensions. Every user of TYPO3 has a different set of "must
> have" extensions. It's simply impossible to maintain them all inside the
> core.


Is is nothing else but the truth that every other major CMS has a news 
module. The - again - often read "excuse" that "the core team does not 
have the man power" ... is lame and boring. Why do you have the man 
power for a workspace module? Or a link validator? Or the new Extension 
manager? Or all those Content Elements, where one has a subheader, the 
other one not - and excluding it just leads to bugs and more work for 
you developers? (That was a recent discussion here, maybe you remember...)

No doubt - those are fancy and shiny extensions and all those 
configuration possibilities - it is soooo feature rich that TYPO3 can't 
be anything else but an _Enterprise_ CMS. And the programming skills are 
admirable! Actually so admirable that I wonder what is so difficult with 
a basic news system? Extend the date functionalies, integrate a category 
system, maybe a new menu type for archive menues - and voila!

This is what I dare to say - please proof me wrong:

- A news system is needed by way more people than a workspace / link 
validator and other stuff

- A news system actually WAS ORIGINALLY SHIPPED with TYPO3 when Kaspar 
brought it to the market. It was maybe not very rich of features as was 
tt_news, but actually I do not understand why that respective news 
module wasn't developed any further. Please explain, core team.


>> 2. The battle for the best extension per solution. Someone should say:
>> this is the news extension we support and the rest can do what ever
>> they want but you are on your own. We only support 1 news extension.
>
> TYPO3 / the Core Team doesn't support any of these extensions. Of course
> extension developers get as much help as possible with maintaining their
> extensions, but anything that is in the TER is simply not part of the
> TYPO3 core.

Well - make news a core EXT again! It is just about time I'd say!

The problem with all that discussion here is that we as users won't have 
any chance either way, because the core team cooks its own soup - a vey 
good soup, but not one for every day hunger. The users can bring in one 
argument after the other, the other CMSs can evolve further and further 
- TYPO3 just won't jump on the train.

And all I hear as a user is either the excuses from above (no man power, 
no time, no use, it is an ext.. etc...) or - and this didn't comeup yet 
-: don't forget: Typo3 is actually a _framework_, not a CMS...

Meanwhile, actually, I think it is too late to incorporate a news 
feature into the core. TYPO3 became too complex and - talking about 
tt_news spaghetti code - how well is TYPO3 core code, if it is sooo 
difficult and / or time consuming to implement a news feature? Putting 
all the weight on Rupi who did a great job with tt_news does not seem 
fair to me at all!!! There must be reason why he left off from TYPO3...

Again - core team, beloved core team: it is really time to rethink!!! 
You do get lost in all your fancy configuration stuff and additional 
features that you completely lost the view for the things that are needed!

Regards,
Robert