[Typo3-typo3org] TER / EM - more categories

Rainer (Rene) Suthoelder t3 at boswel-remove-me.de
Tue Apr 19 18:18:28 CEST 2005

Michael Scharkow wrote:
> Minimum requirements should relate to TYPO3 version *only*. If 3.8
> runs with MySQL xyz and PHP xyz, then an extension for 3.8 should run
> on it. After all, we're extending Typo3 not PHP or Apache or Linux...

well, as the current situation with mysql 4.0.x vs. 4.1.x shows: this is not 
always true.
and consider typo3 running on php5 - most likely, there will be problems 
with older extensions...
and a future migration to DBAL may also lead to some incompatibilities (i 
don't hope so, but who knows).

>> as we all know, production status is _not_ maintained well enough by
>> the developers and kasper should decide to _drop the reviewing
>> process at all_: out of the 840 listed/available extensions only 8
>> have been reviewed and none have met the "cohiba status". if at all,
>> perhaps the review process should better be replaced by a voting
>> system by registered typo3.org users.
> As we all know as well, an extension reviewing team has been formed,
> so reviewing will be done in the near future.

yes, i do know. perhaps one needs to be more patient to see what happens. 
just to make it clear: i would love to see reviewed and therefore 
recommended/not-so-recommended extensions.

>> this makes more sense: in the EM you should be able to
>> select/de-select more options: perhaps based on you environment
>> (typo3 version, OS, PHP etc.) some fields should be
>> preselected/de-selected (like "runs on linux only", "needs typo3
>> v3.8" etc.).
> As said, I propose filtering by a) status, b) runs-on-my-installation
> (= Typo3 version) and later c) reviewed/non-reviewed...

this does not take into account future growth:
consider this: all extensions have been rated, developers start to rework 
their extensions to provide most compatibility and enhanced status, new 
extensions are developed constantly.
then we are in the same situation like today. personally, i believe that 
this http://www.xoops.org/modules/repository/ is a bit too much 
categorization - but a bit more categorization for typo3 would help to 
decrease TER load.

> This should give enough flexibility. And I am not sure about more
> categories because what would those be?

of course, that would definitely fall into the review team's domain.



More information about the TYPO3-team-typo3org mailing list