Regards
(DISCLAIMER: The below might be codswallop - but this is what I think is
going on)
I think that is probably hard to fix, because bugzilla IDs are not
necessarily the same as the email used for a CVS account. The
owners.html page is generated from the despot tool (I think), which has
all these CVS account email addresses. Some are completely different
from the bugmail address, some are only vaguely related (mine is
gijskruitbosch+bugs [at] gmail for bugzilla, but the +bugs suffix is not
there for my CVS account, for example). Most people would be unwilling
to move the bugzilla email addresses (moving lots of mail, updating
filters, etc.) and the cvs accounts being messed with is even worse
(having to make new private keys, submitting everything, IT updating all
the accounts and removing old ones). I don't think it will be
straightforward to link the owners.html generation to a separate bugmail
field in despot, either. But I guess you could possibly file a bug on that.
As a short-term solution: what I find usually works is to use the
surname of the reviewer in the review field. Bugzilla will look for
matching email addresses, and this will usually be a short list, from
which you can pick the bugzilla account you want.
Hope that helped,
Gijs
This is primarily a problem because Bugzilla doesn't handle mismatch/
not found cases well for flag requests. If this gets fixed, this
matters a whole lot less.
The syncing is currently not possible, because we use despot to
generate that page (which gives it all of the right access controls,
IMO). My current bugzilla account is my work e-mail. My CVS account
is not linked to my employment, nor do I wish it to be (this is a
problem with the current Hg LDAP setup, but there's a bug on fixing
that).
I will add that owners.html is not exhaustive, especially for browser/
toolkit, and the appropriate module docs should be consulted before
requesting review.
-- Mike
> _______________________________________________
> governance mailing list
> gover...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/governance
There is a threads in this newsgroup from January and February of this
year that you might want to look at. Look for: "Module Ownership",
"mozilla directories not owned by modules" and "governance topics".
What you might be wanting is a clear chain of responsibility that one
can use to link bugs to people to code to checkins and so on. I asked
for that and still think it would be a good idea. But it is not really
the way Mozilla works.
The various Mozilla systems basically do things in a 'who can do
something' fashion and not a 'who should do something' manner. It is not
clear who is responsible for code, but anyone can propose a change. It
is not clear who should be responsible for a bug, but anyone can take
responsibility if they want to.
This is not an efficient process, but efficiency is not necessarily the
goal of a socially-defined organization.
Good luck - ray