[TYPO3-typo3org] TER crap!

georg kuehnberger georg at georg.org
Thu Nov 12 01:44:10 CET 2009


It might be nice (and even help to some extend) to write scripts and 
partly automate here or there.

However me feels you're missing an important point:
    The TER currently has NO meaningfil POLICY at all. (there are just 
some lived procedures).

Before any new & fancy typo3.org & EXT:TER or EXT:TER-FE changes could 
be planned, organized, coded, tested, ... there needs to be a TER-policy.

I'm aware that there some lived and partly organized concepts, 
procedures like:
- security removed extensions,
- handling of ownership (keys),
- review-process (sill alive? - where to find info upon?),
and even more. However the overall concept and policy seems to be 
missing (or is highly incomplete/not automated/followed up).

I'm not voting for too rigid restrictions, however I know that
- the ammount of extensions in TER is kinda useless, confusing, and 
meanwhile ruining reputation,
- the overall quality is bad,
- the overall view is terrible.
Searching for meaningful Extensions (that is: mantained, recent, 
following CGL, secure & documented) is quite impossible.

- The lack of a welldefined, executed or enforced TER-policy will soon 
render TER completely useless.
- Lets take action, by defining a policy, responsabilities & then lets 
"automate" its enforcement.

I strongly feel that the ASSOC (as owner of the TER) is in charge of 
setting up a meaningful & live-able TER-policy incl. its enforcement.

hth, georg

Steffen Kamper wrote:
> Hi,
> Peter Klein schrieb:
>> So I think a couple of changes needs to be done now!
>> How about writing a script, that checks all ext on TER to check if a 
>> docs/manual.sxw is present.
>> If not then send an automail to the autor of the ext, telling him/her 
>> that they have X days to provide a manual to their extension, 
>> otherwise it will be removed from TER. (Something similar could be 
>> done to weed out the ext. without descriptions.)
>> I think that will filter out a lot of (useless?) extensions.
>>> I agree that something has toi be done, like vote / negative vote 
>>> etc. to sort out crappy things.
>> The rating/vote system should be more prominent. Right now it says "No 
>> ratings" until the ext. have 3+ ratings, and no link to the rating 
>> form. (You 1st have to click the ext. name, and then the Ratings tab)
>> But when it has 3+ ratings, the text now links diretly to the rating 
>> form.
>> So how about changing the text "none" on ext with less than 3 ratings 
>> to "rate now" and make it a link just like on 3+ ratings?
>>> Also i think there should be some rules like we have in newslist, 
>>> minimum requirements like
>>> * use default english
>>> * include manual
>> It can't be that hard to add some text like that on the page where you 
>> register ext. keys. ;)
> it is - as the texts are from the extension.
> But we have ter_fe in forge, have a look and report issues there.
> I've planned a bugfix session on this ext next month, so any help is 
> welcome.
> vg Steffen

More information about the TYPO3-team-typo3org mailing list