* Branden Robinson <[EMAIL PROTECTED]> [2004-03-03 14:03]: > On Wed, Mar 03, 2004 at 10:35:18AM +0000, Martin Michlmayr wrote: > > Please keep what I said about core teams in mind and re-read > > "Internal - Core Teams, Delegates, Communication, Transparency". > > Many of the points I raise there equally apply to (big) packages > > and other technical matters. > > At the same time, you say: > > Coordinating a project the size of Debian requires a very > different set of skills than maintaining a large package, such as > glibc.[1]
I don't see the conflict. Yes, different tasks require different skills. Maintaining a package requires other skills than being the administrator of .debian.org hosts. The various delegates need different skills as well: the DAM might not do a good job as Release Manager, etc. However, what all of these have in common is that the _process_ has to work. The teams have to work. If the maintainer of a package is overworked, help has to be found, just like when a delegate is overworked. When a maintainer doesn't communicate, the problem has to be fixed, just like when a delegate cannot communicate. When it's not clear how to interact with a maintainer, this should be documented and the process be made more transparent, just like when the job of a delegate is not well documented. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
