[Typo3-dev] Sharing the load of development?

[Kasper Skårhøj]

Hi folks.

It's a favourite worry for some people that TYPO3 is developed by
me/handful of people. 
First of all this is only true if you think TYPO3 is the core only and
extensions doesn't count. But since extensions - or at least "Official
extensions" - are to be counted as a part of TYPO3 as a system, the
"core team" is in reality a much larger group of people; namely all the
extension authors as well!

However; Many "Official extensions" are still in my ownership which is
"bad". So what about outsourcing these as a step towards less
Kasper-dependency?
(Notice: Recent examples has shown that we are working in a direction
away from this eg. Robert Lemke running "TemplaVoila" and "Office
displayer" autonomously, Karsten D. running "dbal" extension). 

INVITATION:
This mail is an invitation to the developer community to get more
involved in maintaining / developing my "old" extensions. For this we
have long time ago created the source forge project "typo3xdev" where
extensions can have a module in CVS. This is already the case with a
number of my extensions and I want to know if some of you want to help
out on some of them:


tx_directmail
- I'm not currently using this myself so my motivation for fixing is
very low. This could be developed by someone who is USING this a lot and
has the expertice to develop it further (and make sure it works for
current installations still!)

tx_indexedsearch
- I would like to keep control with this extensions since it contains
some complex code which could easily be spoiled. However it might be
nice having a development team aroudn this extension.

tx_rte
- Open for development. In particular I think the table wizard needs
work. However, I would far more like that efforts are put into the new
"rtehtmlarea" extensions (possibly by some of those who has already made
RTEs based on htmlarea).

tx_ttproducts
tx_ttnews
- Anyone?

tx_tipafriend
- There is a serious bug in this which makes it easy for spammers to use
the mail-sender by simple GET requests. Someone wants to fix this
security hole?

tx_mininews
- Anyone?


It is also possible to be in charge of maintaining certain scripts in
the core code. For instance for maintaining "directmail" you might
quickly need to maintain "t3lib_htmlmail" and "t3lib_dmailer" as well
since they are intertweened. Or like Martin Kutschker maintains the
t3lib_cs script.


Requirements for getting CVS access:
- You MUST be committed to finish what you start! Make small promises,
but keep them!
- You accept that adhere to the coding guidelines and bring the code up
to that standard.
- You must persue backwards compatibility.
- You must document your code and functionality.
- Bugs you might introduce must be fixed promptly - people might depend
on that.
- General maintaining; Fixing bugs reported and adding features
requested by the community.



If you are interested in maintaining any of the extensions listed above,
please send me your SourceForge username so I can give you CVS write
access.
If there are any extension which is not listed above, but which you want
to maintain, please let me know.

This discussion has *nothing* to do with the scheduled release on
friday. We are thinking ahead of that now.



-- 
Best regards

- kasper

--------------------
It's not a bug, it's a missing feature.