[TYPO3-dev] not amused...

[Reinhard Führicht]

bernd wilke schrieb:
> Reinhard Führicht schrieb:
>>
>> Just a thought about extensions in general:
>>
>> We all know that the TER is a mess. There is no easy way to find out 
>> if an extension is well written, secure and most important even working!
>>
>> The design of the repository listing on typo3.org is outdated and is 
>> giving no useful information.
>>
>> A simple possible solution:
>>
>> Only allow extensions marked 'stable' to be released in TER.
>> For development we have Forge.
>> For publishing the extensions we have the TER.
> 
> every update/ upgrade/ bugfix will lead to an (temporary) unstable 
> extension. having this new version only in SVN you reduce the amount of 
> people testing and giving feedback and leading to a new stable version.

Basically there is no extension which is 100% stable. Some features will 
not work under special circumstances or sometimes you simply did not 
test them good enough. That's where the community comes to play and 
gives feedback. I agree with you that releasing an extension in TER will 
increase the amount of testers.

But I think that an extension in TER should at least have a certain 
amount of functionality (no more 'nothing' extensions).
Furthermore I do not see any need to release an extension in TER with 
state 'alpha' and no manual at all. This doesn't lead to a higher amount 
of testers, this is just flooding the TER with development stuff that 
should be in Forge. An extension should be released when it reached a 
state in which everything works on the developer's system. It can have 
experimental features and bugs, but the core should be at least nearly 
stable.

A developer of a TYPO3 extension should know how to use SVN. Nothing 
more to say about that. With integration of extbase and fluid and lastly 
with v5 development will get more complex and extension developers have 
to learn what the buzz words mean (OOP, DDD, MVC, AOP, ...) to be able 
to extend TYPO3. Having that in mind SVN isn't really a problem, is it?


> 
> As long as SVN-Access is much more complicated than TER you will more 
> and more reduce the number extensions.
> Or you will get extensions declared stable which are miles away from 
> being realy stable. (as said before)
> 
>> Allowing only stable extensions there, will
>>
>> 1. Decrease the number of crappy extensions
>> 2. Decrease the overall number of extension which will make it easier 
>> to find what you are searching for
>> 3. Will make it easier to review an extension.
>>
>> Further aspects:
>>
>> - Allow to enter keywords for an extension, so that the search will 
>> not only use title, key and description, ...
> 
> every ext-dev is free, to insert keywords in description

Sure he can. Why don't we just get rid of all the other fields and just 
use the description field only. The author can enter his name, 
dependencies, even the manual there... No offense, but I think you get 
my point.

> 
>> - Fix the download counter! (I know, I know :-))
>> - Provide a better rating, commenting system (I know, I know :-))
>> - Only show extensions which will work in a specific TYPO3 version. On 
>> typo3.org, let the user filter by TYPO3 version. In extension manager 
>> use the installed version.
> 
> +1 on getting a better FE-interface for TER.
> 
> But don't forget the TER-interface inside of each TYPO3-installation.
> while all extension-informations are stored in database you are free to 
> create an BE-Module, which will provide all the restricted views you 
> request

Yes, I know. The backend interface needs a facelift too, but that's not 
the most important stuff. I think the extension list on typo3.org is 
more important, since any user, customer, interested person can see and 
browse it. Anyone can browse it, but no one will find anything unless he 
knows what he looks for.

Reinhard