On Sat, Mar 19, 2005 at 03:17:33AM -0800, Steve Langasek wrote: > > - at least two buildd administrators > > > This allows the buildd administrator to take vacations, etc. > > This is at odds with what I've heard from some buildd maintainers that > having multiple buildd maintainers makes it hard to avoid stepping on one > another's feet,
That is the opinion of the !m68k buildd admins. However, as we have
proven by now, that isn't really a problem; all it requires is some
level of coordination, which is easily achieved by having a buildd
maintainers' mailinglist (or just eachother's email addresses, if the
team is sufficiently small).
Indeed, the m68k buildd team currently consists of seven people -- Adam
Conrad, Christian Steigies, Matthias Ulrichs, Michael Schmitz, Roman
Hodek, Stephen Marenka, and myself -- yet we don't usually "step on one
another's feet".
It is, however, true that both approaches to buildd maintenance have
their advantages and disadvantages; e.g., one of the disadvantages to
our approach is that rare but still recurring problems aren't easily
identified. I still think the advantages to our approach (there's
someone to take over temporarily if I go to $far_away for three weeks,
to name just one) by far outweighs the disadvantages, however.
I should note that I would be happy to help set up a team for one or
more of the currently singly-maintained architectures, if the people
that currently maintain it are willing to either join the team or give
up maintenance of that architecture; I'm quite sure it would prove to be
a workable alternative.
--
EARTH
smog | bricks
AIR -- mud -- FIRE
soda water | tequila
WATER
-- with thanks to fortune
signature.asc
Description: Digital signature
