[TYPO3-ttnews] news2 vs tt_news -> TYPO3 CORE?

[Jordan van Bergen]

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. 

We all should get ride of all news extensions and start using the one
that's in the core. Doing it this way you will certainly know this is
a good news system used by every single TYPO3 user instead of us all
using different news extensions with less support outside the CORE. 

TYPO3 is a rock solid CMS but lacks quality extensions that other CMS
systems do have. And as news becomes more and more a default function
of a CMS system asked by customers it should melt into the CORE. I had
no single guy/girl that didn't ask TYPO3 without a new system. 

This thread is about my opinion and people can agree/disagree and I
don't mind what's going to happen (seperate or core) but I see a lot
of advantages as soon as a news system is integrated into the CORE. 

I see more advantages compared to disadvantages. 

Regards

Jordan van Bergen


On Sat, 09 Apr 2011 12:28:46 +0200, Georg Ringer <typo3 at ringerge.org>
wrote:

>Hi Jordan,
>
>first of all thanks for checking out news2 (which will maybe get a new 
>ext key in some days).
>
>Am 09.04.2011 12:14, schrieb Jordan van Bergen:
>> So a new news extension is being developed. Shouldn't NEWS in general
>> be part of the CORE of TYPO3? Every site (if you ask me) needs to
>> publish news.
>
>Many of my websites are not about news and therefore the extension 
>wouldn't be needed.
>
>> So if one news extension is going to be selected into
>> the CORE we users don't have to think about what extension to use.
>
>You have also not really to think which extension to use if the 
>extension is a normal one.
>
>> It's time one news extension is going to be transferred to the CORE of
>> TYPO3 as news is a CORE part of a CMS system if you ask me.
>
>There are many reasons against this:
>- Slow update process:
>	* New versions could only be shipped all 6 months
>	* Every change needs to go through the core review process
>- Harder to maintain:
>	* Bugs need to be fixed for all versions which are currently supported, 
>I wouldn't have time for that.
>
>- Bigger core
>- No benefit having it in the core
>
>So I really believe that there is no advantage for a single user or an 
>integrator if the extension would be shipped with the core.
>
>Georg