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: Quality: some thoughts on achieving it (long)

On releasing according to schedule:
> I think so too, but not the way we've been doing it so far.
> However, I'd rather stress reaching goals than reaching time
> tables, and then work on setting such goals that can be done
> in three months.

That's true, but goals have not been why the release has been slipping.
It's been slipping because we haven't gotten our act together for a
complete cycle yet.  The last one, I tried to do it starting half
way into the cycle instead of at the beginning.  In retrospect, that
was my first mistake.

If we plan to start the cycle on Feb 1st, at least we'll be
pretty close to organized at the start of it all.


> I suspect most people won't subscribe to both lists, especially the
> policy one. I'd suggest the following procedure:
> 
>         debian-devel-policy would discuss things freely
> 
>         when some kind of consensus is reached, the BoD makes sure
>         someone writes down a concrete proposal for the new policy
> 
>         this proposal is announced on debian-devel-announce, and
>         comments are made to the editor of the proposal, or on
>         debian-devel-policy
> 
>         proposal is modified based on comments
> 

On policy cycle "discuss, go to BoD, (announce, modify){1,3}":
> Repeat up to three times, and have the BoD make and announce a
> formal decision if they accept the final draft. This procedure
> would mean that most people wouldn't need to follow the
> discussions on debian-devel-policy, but would still be able to
> comment on proposals before they're decided on.

That sounds good to me!


> On dividing:
> >   project leader
> >   testing manager
> >   policy manager
> >   security manager
      distribution manager
> 
> I assume the last three won't need to be on the BoD. It's probably
> not a good idea to collect volunteers yet, until the BoD starts
> working and there is a more complete proposal on how to divide
> work from now on.

None of them should have to be filled by people on the BoD.  Neither
should being on the board mean someone cannot be in one of the above
positions.

                                          Brian
                                 ( bcwhite@verisim.com )
                                             
-------------------------------------------------------------------------------
  Want to get it together?  We can help!  http://www.verisim.com/coordinator/



--
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