Bugzilla user/group permissions

[Daniel Berlin <dberlin at dberlin dot org>]

Currently, I have it set so anyone who has a * at gcc dot gnu dot org bugzilla 
account can edit/confirm bugs, and anyone else can view/submit them.

This is much like what we have with gnats now.

However, with GNATS right now (correct me if i'm wrong), it takes 
someone on overseers to add/remove a component, etc.

With bugzilla, I can give access to this without needing an overseer 
(same with adding new milestones, versions, etc) .

Currently, nobody but me (since i happen to have the only account with 
admin access, mainly because i haven't finished adding people to the 
admin group) can do this.

Do we want to have anyone with a gcc.gnu.org account able to add 
components/versions/milestones, on the assumption that people with 
write access are careful enough, or should I just specifically add 
release managers or global write people to the list of people who can 
edit components/milestones/versions, or should it just be people who 
used to be able to do this for gnats (through virtue of having the 
right access on sources).

I have no opinion on any of these, and it's just as trivial to do it 
any of these ways (though it's slightly easier to just give it to 
anyone with a gcc.gnu.org account, since i just have to set a regex 
based group, and it will always be correct, rather than having to 
manually update it), but i wasn't sure what we wanted to do.

--Dan