[TYPO3-ect] Ideas to clean up TER

[Jigal van Hemert]

Hi,

On 29-1-2012 12:31, Rens Admiraal wrote:
> - If we want SVN / git as archive: do we also require extensions to be
> in forge? And if so, doesn't it make sense to publish tags as extension
> version in TER automatically? And by this requiring a solid tagging
> workflow?

No, extensions should not be required to be in forge. A tag doesn't mean 
a new TER version automatically. Before an extension is ready for TER 
there could already be tags during development.

> - What to do with extensions which are not in forge? It is now possible
> to create a new forge project for an already published extensionkey...

Automatically created forge projects? Can forge handle this load? A 
substantial number of extensions is put in TER (sometimes because of 
project requirements) while nobody is interested in maintaining them. 
This would add a load to forge, which in the end should be cleaned up too.

> - How can we help developers find the minimal / maximal required
> version? Does it make sense to set the max version automatically to the
> maximum version of the current release the developer uses to publish the
> extension? For example: I upload an extension in 4.4, and the maximum
> version is 4.3.99, It would make sense to set this to 4.4.99 during
> publishing... (With some kind of user interaction of course)

Nice to have. Make a patch for the EM if you want!

> - Does it make sense to create some automatic checks? You know for sure
> an extension is not compatible with 4.7 if eregi() is used for example,
> and the same can apply to certain core methods...

Also nice features, but rather independent from the cleaning of TER I guess.

> Regarding the other stuff in this discussion: I'd prefer not to delete
> the extensions from TER, but hide them in some setting in the extension
> manager. Like we had "only search reviewed extensions" before.

And the point would be? Most integrators would be annoyed that they 
"had" to set this setting first before getting access to all the 
extensions. Same as we had with the reviewed extension setting.
That's not cleaning up, but making old stuff a little less obvious.

> But I would like the notifications to developers when a new stable TYPO3
> version is out, or the current maximum version is EOL. I can imagine
> this is a trigger for developers to keep the extension maintained...

Really a trigger? We have an announcement list, buzz, news, 
announcements on other mailing lists/newsgroups, release parties, 
messages on forums, websites, etc.
We could try to get it on the evening news and maybe visit extension 
authors in person (just kidding).

-- 
Kind regards / met vriendelijke groet,

Jigal van Hemert.