[Typo3-dev] Less features, more future

[Alistair MacDonald]

Kasper Skårhøj wrote:

> ... this reminds of a problem there is for me. I believe I'm still the owner 
> of the "newloginbox" but effectively it is in CVS and others are invited to 
> develop it more and in fact that is what has happened (I didn't work on it 
> for quite a while...)

According to the system Ingmar Schlecht is, but it isn't really relevant.

> Now, I completely forget that a regular publication should happen once in a 
> while since I don't work on it, so should I transfer ownership to someone, 
> who should that be in case, what happens when HE/SHE becomes occupied with 
> something else etc. The best would be if we have some "typo3_release" user 
> who could own all extensions which are not really owned or maintained by a 
> single person all the time and this user could ensure regular releases in 
> TER?

It seems to me to make sense to have an "orphaned extensions" user in 
TER. If there is no clear successor then the extension can be 
transferred to this "orphaned extensions" user. Ideally that links to a 
list of all the orphaned extensions, along with a contact to talk to if 
you want to take one over. So long as an administrator somewhere can 
change the ownership of the extension again then it works quite nicely. 
Logically you would need to demonstrate some form of commitment to the 
extension by providing a feature, rather than just trying to collect up 
a list of extensions to put your name against. It goes without saying 
that if there are no changes then there aren't any releases to make.

In the case of orphaned CVS hosted extensions it should logically be the 
person who commits the changes who makes the decision about releasing or 
not. In the case of newloginbox I should stick my hand up and say that 
whilst I submitted the initial HTML template patch I have never said 
that the CVS version works. At least in part this was because it was so 
much easier for me to continue using my patched version than the CVS 
version because there is no way to get t3x files from CVS. What we need 
is a t3x export system at SourceForge 8-) At the moment you have to find 
the correct CVS project, pull the files locally, rename the folders and 
transfer them. (Some of the complication arises because the naming at SF 
is standardised, but different to TER: newloginbox => tx_newloginbox, etc.)

Alistair