[TYPO3-ttnews] Switch to news

[ben van 't ende]

Hey Georg,

Funny to see you mention me as a silent listener ;-) It is hard to react to this
whole thread as so many things have been said so many times before. At the
moment we do not have the possibility to deal with A-class extensions. Kay wants
to build this into the Extension Repository. That is the easy part, but after
that the extensions need to be maintained and checked by a group and at the
moment we simply do not have the manpower for that. I do agree that the most
downloaded extension of TYPO3 needs some more love then currently and I have
brought that topic up again in the RnD committee. Our main concern however still
is the core development of TYPO3. Everyone involved in this whole thread is able
to contribute to the community. I realise we are not doing a good job at the
moment to allow easy contribution to TYPO3. I am currently working at the
typo3.org relaunch sprint in Wiesbaden. The new website will be a lot clearer in
indicating where and how one can contribute. As community manager I try to
improve communication in the community and especially in the teams or rather
between the teams. There is a lot that can be improved, but this can't be done
from one day to the other, but still there is a lot of progress as you might
have seen in the steady release cycle, the LTS release of 4.5 and the many
accessible meetings we have nowadays.

In this thread I see a lot of demands, but those demands cannot be achieved
without your participation.

Please feel free to mail me personally if you have any ideas or questions.

Have a great sunday!

ben



On 17/09/11 18:40, Georg Ringer wrote:
> Hi,
> 
> Am 17.09.2011 16:18, schrieb Robert Wildling:
>> Thanks for your response, Georg! It must be hard for you: you did
>> actually the work that most of us needed - rewrite the all important
>> news ext - and still: critique all over the place...
> 
> this is something which comes all the time but yes it isn't that easy
> sometimes.
> 
>> Well - as for me: I love your news ext! So much that it should actually
>> be a core ... ;-)
> 
> thanks but love is not a criteria for it. Furthermore having it *not* in
> the core means that features can come faster than all 6months (as a
> release of TYPO3).
> 
>> And actually - no offense, Georg: but you are one of those developers,
>> who first says "no" to almost everything that comes from users. 
> 
> yes I know that. SOme words about that. It is a no for features which
> are not that important (for me) in the first place. There are not so
> many people working for the extension currently, therefore it is for 98%
> of everything me who will implement it. Therefore I got the freedome to
> decide because I need to do it (in my free time, instead of having time
> for my girlfriend, blablablabla).
> 
> If there is a regular team and another member wants to do a feature from
> the roadmap, I won't have a problem with it.
> 
>> That
>> makes it a bit hard to keep up fighting for an idea, because: how can
>> things be changed, if a non-programmer has a need for sth? (Lets not
>> discuss the ext system a "pay a developer"-line now, that's just not the
>> only way.) I would like to read one discussion here where you go along
>> with the idea of another... sorry, but true for me. Please proof me wrong!
> 
> As said: I am happy to integrate more features like the calendar thing
> and so on but I guess some things like a category view or a search could
> be more important.
> 
> Furthermore it was *very* important for me to have the 1st version out
> there which was maybe a small step code wise but not so small at other
> things.
> 
>> I would very much like to talk to a core developer here who actually
>> really thinks along with what users need. But where are they?
> 
> Maybe a silent reader like Ben could enlighten us. First of all
> something like that should be done in person because it makes so many
> things easier when you meet. Are you at t3con, t3board? Let us dring a
> beer and meet.
> 
>>
>> The simple answer to your "whys" and "buts" is: because other systems
>> ship it natively. It is a standard. It is one of those things that makes
>> live easier. It is an "overall usability feature". 
> 
> I agree there but still I think that it should not be shipped nativly
> with the core because there are also drawbacks like the release cycle.
> 
> I just had an interesting idea which would be awesome for me and I guess
> it would solve your problem too: 1st: If you know the idea of "a class
> extensions", read one, if not read
> http://buzz.typo3.org/people/olivier-dobberkau/article/a-class-extensions-name-your-tune/
> 
> What about an extension manager which would show those a-class extension
> at the same (or nearly the same) place as system extensions. Therefore
> it would be for every user like installing an sys ext but code would
> still come from EM.
> 
>> But: google for TYPO3 tt_news and TYPO3 Workspace - and I think the
>> answer is there.
> 
> forums are always full of troubles and problems, so maybe because people
> got som many troubles with tt_news? just kidding.
> 
> But maybe the core team should just make a voting which extensions
> should be shipped with the core. Before the news extension should be
> shipped, IMO it still needs some polish and some further features
> 
>> And I again would like to emphazie that I DO VERY MUCH APPRECIATE your,
>> Georg Ringer, work!!! Since years!
> 
> Thanks a lot!
> it could be you buying the beer at the next event ;)
> 
> Georg

-- 
TYPO3 Community Manager