Account request procedure, random components

[Daniel Stone]

On Fri, Jul 01, 2005 at 09:44:05AM -0400, Owen Taylor wrote:
> If the procedure for requesting accounts is to stick them into
> bugzilla, there really needs to be a module for accounts unrelated
> to existing modules.

Yes, it is.  http://www.freedesktop.org/wiki/AccountRequests

> Is completely unrelated to the desktop entry specification, and
> it shouldn't be assigned to me.

Product fd.o, component New Accounts, means that the sitewranglers need
to take action and actually create an account.  Before that happens, as
we do not hand out accounts to random people, someone from the project
needs to approve (or reject) the account request.  This is why it is
assigned to the project.  The default owner for the product is a good
indication of who should deal with the request.

If this is insufficient, and your project hits this often enough that it
becomes a real drain on your productivity, you are welcome to request an
Account Requests component with a different default owner.  But the fact
remains that account approval must initially be done by a project
member, before sitewranglers can usefully deal with the request.

Bugzilla is used to represent this workflow by assigning it to the
project -- and person -- that needs to take action.  The project in
question at first, then later sitewranglers, after approval has been
granted.