Hi Matthias, On Thursday 09 December 2004 01:41, Matthias Niess wrote:
> Please let me know, what you think. I think there should be a strict code review before committing changes, anyway. Therefore, if we could manage to distribute reviewing responsibilities among a few core developers, this could reduce Elpidio's work load indeed. But as far as I can judge, there are several people who work on very small issues and Elpidio is the only one who works on the whole system. So just letting the whole world commit changes will end up in a mess ;-) Nevertheless, as of updates of special modules - or say of the help files - or maybe even of the translations, for them it *might* be of advance to bypass Elpidio. If there are the right people who will take responsibility for their areas. It might even be a challenge to increase engagement?! So the first question I suggest is, who is willing to take responsibility for a certain sub-task? Or, beginning with Elpidio, what task would you delegate first if you had the right person to take it? Regards, Nino ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers
