[TYPO3-ect] Proposal: Tagging Extensions before publishing / Soft validation against other tags [Re: FYI 3 x nusoap-extension ?!]

[Christian Trabold]

Hello Ries,

> this is indeed a huge problem.
> I have even see core developers doing the same thing,
> what can we do about it?

what do you think about this approach:

Before an extension gets published to the official TER the developer has 
to tag it with at least three different tags, that describe the 
core-features of the extension best.

Eg. the nusoap-extension could have

   NuSoap, Web Service, Library



After submitting this data, it will be "validated" against other Tags in 
the TER and the developer will get an instant feedback (CloudTag?), if 
there are other extensions with similar tags (it could be considered to 
take the extension key into account too).

If his extension seems to be unique in TER, everything is fine and the 
extension gets published.

But if there are similar extensions, he gets a friendly recommendation, 
to investigate each extension and to get in contact with the other 
extension developer to share coding power.

In this case there could also be a checkbox, which allows the developer 
to explicit ignore these recommendations, which could come handy if the 
recommendations do not make no sense or if the developer wants to force 
the publishing of his extension.




*Misc notes*
- The tags of each extension are stored internally and not in 
ext_emconf.php.

- The tags could be used for other features on typo3.org, like improving 
the extension-search. Maybe a visitor searches for "Web Service 
Integration" and finds all extensions with these tags assigned (this 
could also accomplished with a search on the extension description).

- Tagging existing extensions could be done by calling all extension 
developers to do so or to make tagging obligate when an extension gets 
updated.



These are my ideas.

Greetings

Christian