On Wed, 19 Mar 2008, Peter Palfrader wrote: > I think the "problem" would be trivial to fix. The DAM should be the > party that makes the *policy decision*, and then DSA should be > tasked with actually creating the account, and keyring-maint with > adding the key to the debian keyring.
What is needed for this to become so? From where I sit, the solution seems clear: 1) Upon direction from DAM(s) DSA creates/deletes/deactivates accounts; all acccount activities are announced to -newmaint (or -private for non-public issues) 2) keyring-maint adds/removes identities to the keyring upon the direction of DAM; syncing with LDAP. Updates keys on own volition, with announcements to some appropriate location. (-newmaint?) I don't see any reason why both DSA and the keyring-maint should fail to deal with requests within a week or so unless they're on VAC.[1] As near as I can gather, it appears that so far no one feels to have the power necessary to change how account creation and key modification actually works. What do the DPL candidates feel about this? Do we require a GR to direct how account creation and keyring management is to be handled? Don Armstrong 1: There's nothing bad about not having enough time to do a volunteer job, but failing to ask for help (or turning a task over to someone else) hurts us all. -- Democracy means simply the bludgeoning of the people by the people for the people. -- Oscar Wilde http://www.donarmstrong.com http://rzlab.ucr.edu
