The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: developer criteria

On Sun, 19 Jan 1997 23:45:00 PST Bruce Perens (bruce@pixar.com) wrote:

> I am considering some criteria for developers. Response time is one we
> should formalize. This is something we can probably get away with now
> that we have enough developers to be able to afford some winnowing.
> Response time for security bugs should be no more than a week, for
> pre-known release issues no more than a month, for post-release gotchas
> that break a package badly, again no more than a week.

This is a good idea, this implies some kind of `sanction' when the 
delay has expired. I don't like this underlying sanction.

> One way to deal with respoonse time is to have a pre-established backup
> maintainer if you happen to be away or busy when something comes up.
> Maintainers should pair up to cover each others packages in this way.

This is a good idea, but it might be difficult to maintain. We already have difficulties tracking all out package developper (we should implement the developper-ping someone talked about in debian-devel, has anybody vonlunteered yet to write it ?), and maintaining and updating this list might be overkill...

Why not modifying the debian bug-tracking system in this way:
  1) When bug are opened, a message is sent to the maintainer as well as 
     debian-devel-bugs (same as now).
  2) The maintainer must answer to the bug saying he's working on it. 
     (new feature).
  3) If the developper doesn't answer in a delay (which could vary along with
     the bug severity), an other message is sent to debian-devel-bugs, saying
     the maintainer of the package isn't answering and asking for someone else
     to do the work.
  4) If someone doesn't take the bug in charge (by sending an email to the bug
     system), the message is re-sent every couple of days.
  5) Finally the bug is closed, and something is uploaded.

If several developpers reply at step 3-4, the first one gets the bug assigned to him, and the others receive a message saying that developper X gets the bug.

Comments ?

Phil.



--
Please respect the confidentiality of material on the debian-private list.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com