On Mon, Mar 04, 2002 at 07:24:36PM -0700, Bdale Garbee wrote: > email@example.com (David N. Welton) writes: > > > I want to know how the > > DPL candidates would handle a situation like this so as to 1) get > > services restored quickly and securely, or at the very minimum, keep > > the rank and file informed of what's going on, and 2) not piss off > > sponsors and volunteers. > > I think you have the priority of the two backwards. I don't think there's any reason to subordinate one to the other; the two goals aren't competing in a zero-sum game. I see no reason we can't treat sponsors well and keep them happy, *and* inform our Developers when there are service outages on our machines. Tomorrow, it will have been one week since the most recent outage, and there has still been no announcement, except an informal one on the OPN IRC network that is thanks entirely to Brainfood staff: "non-mail/http type services still blocked to bf network(including master)" (...and, of course, some casual discussion on Debian mailing lists, which does not an announcement make.) Perhaps the DSA team is overworked, and needs to add some members to even out the workload. If so, I'd be more than happy to delegate some as DPL. As I said before, Brainfood appears to be doing an exemplary job. We seem to have a failure of process on our end, and that is exactly the sort of thing the position of Project Leader is designed to handle.  At least, not one that I can find. There's nothing on debian-devel-announce, and no mention of this problem at <http://db.debian.org/machines.cgi>. -- G. Branden Robinson | Optimists believe we live in the Debian GNU/Linux | best of all possible worlds. firstname.lastname@example.org | Pessimists are afraid the optimists http://people.debian.org/~branden/ | are right.
Description: PGP signature