[TYPO3-dev] Ideas solving the bloated TER problem?

[Stefano Cecere]

as first step, something that could be done in 1 hour of wotrk, i would  
add a "staff pick" checkbox to some exts..
let's call it "core devs preferred", taht would be all those ext that  
could really be in the core but aren't (for sweveral reasons)
see the latest "feeditadvanced"

in a few days nobody will find it, unless they NOW know about it.

a simple menu showing all staff picks ext could help anybody to find the  
ext gems.

for me it would be easy to develop such thing.. but from where to start?  
who to talk with?

all other things you are saying have been talked in latest years.  
expecially categorization.
i guess the Association should ask a core and UX dev or a trusted dev to  
take a few days and improve ter_fe



stefano



On Thu, 12 Nov 2009 10:42:44 +0100, Stig Nørgaard Færch <snf at dkm.dk> wrote:

> TER becomes more and more bloated with more or less redundant  
> extensions. Has there been any concensus on how to solve this problem?
>
> My thoughts:
>
> No good extension overview
> TER doesn't provide a good oveview of what already exists.
> If I don't find what I need, I create it. But maybe it already existed  
> in the TER - but I couldn't find it.
> We really need categorization of extensions back.
>
> Mangement of key extensions
> When key extensions are managed by individuals, we have a greater risc  
> that development at some point stops.
> TYPO3 companies should manage key extensions of TYPO3.
>
> Key extensions supported by the Association
> The Association should support a specific key extension of each category  
> (not necessarily with money) which supports the most common features of  
> that category. Then decisionmaker with the money knows which ones are  
> worth supporting.
>
> Channelize money
> It should be easier to donate money.
>
>
>
> My two cents.
>
> /Stig


-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/