Forget classes, think privileges (was: Developer Status)
also sprach Joerg Jaspert [EMAIL PROTECTED] [2008.10.22.2333 +0200]: Now let us describe the way the account status is meant to be handled in future. Finally! http://lists.debian.org/debian-project/2005/02/msg00079.html It's the latest message I could find. I am sure I have been harping on about this before. One thing that occurs to me reading about what Clint has to say[0] is that we have a set of privileges, such as voting and uploading and the access to the various different machines, one punishment (debian-private access), and Jörg wants to map different combinations of those to classes. 0. http://xana.scru.org/xana2/ranticore/debknights/ Why don't we just take each and every of those privileges and define criteria for how to obtain the privilege, and then simply give people privileges according to what they need, rather than having a defined set of rigid classes? Obviously, one could still group privileges (e.g. to be able to vote, you have to endure debian-private). And yes, I agree that this ought to be a GR or at least that Jörg's email should not have been of the this is what we'll most likely do nature, but rather in the this is what I've been thinking about and would like to propose for discussion department. Cheers, -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems once ... in the wilds of afghanistan, i lost my corkscrew, and we were forced to live on nothing but food and water for days. -- w. c. fields, my little chickadee digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: Forget classes, think privileges (was: Developer Status)
On Thu Oct 23 10:25, martin f krafft wrote: Why don't we just take each and every of those privileges and define criteria for how to obtain the privilege, and then simply give people privileges according to what they need, rather than having a defined set of rigid classes? Obviously, one could still group privileges (e.g. to be able to vote, you have to endure debian-private). This is what I was trying to propose last year[0,1] Matt 0. http://wiki.debian.org/Projects/AltReformedMembershipProcess 1. http://lists.debian.org/debian-newmaint/2007/12/msg00013.html -- Matthew Johnson signature.asc Description: Digital signature
Re: Forget classes, think privileges (was: Developer Status)
martin f krafft [EMAIL PROTECTED] wrote: http://lists.debian.org/debian-project/2005/02/msg00079.html [...] Why don't we just take each and every of those privileges and define criteria for how to obtain the privilege, and then simply give people privileges according to what they need, rather than having a defined set of rigid classes? Obviously, one could still group privileges (e.g. to be able to vote, you have to endure debian-private). I think that's an excellent idea. I would also like any privilege request queue handled in an approximately First In First Out manner and I would try to vote accordingly in a GR. I've been suggesting NM reform since 2003ish. One recent post is:- http://lists.debian.org/debian-project/2007/11/msg00085.html Thanks for saving me time by putting the suggestion in better words than I could! -- MJR/slef My Opinion Only: see http://people.debian.org/~mjr/ Please follow http://www.uk.debian.org/MailingLists/#codeofconduct -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
