Re: Bugzilla update and schedule for changeover

[Daniel Berlin <dberlin at dberlin dot org>]

On Friday, March 21, 2003, at 11:27  AM, Gerald Pfeifer wrote:

> On Fri, 21 Mar 2003, Daniel Berlin wrote:
> > You need an account to be on a CC list of a bug or to get mail about 
> > bug
> > changes, etc
>
> This would have been my questions: the submitter of a PR _must_ be
> kept informed about all changes related to that PR.
>
> If that's not feasible with some approach (like having no account for
> submitters) we cannot use that approach, AFAICS.

I'm in agreement.

Note that I can *eventually* get Bugzilla to do what we want (no 
account cc'ing and whatnot). It's just that because it's non-trivial 
(though not all *that* difficult) coding, i'd rather it be worked on 
and added to bugzilla's code (which means going through their review 
process and whatnot), then merged back into ours, rather than us 
maintaining it.  Especially since Bugzilla is currently rapidly 
modularizing things, and thus, code tends to move around or disappear 
between releases of the HEAD branch, and i'd like to be able to track 
releases without a ton of merge work and rewriting.

There *is* a bug already on bugzilla.mozilla.org for allowing 
non-member submissions and cc'ing, which one can use to follow the 
progress of my work on this issue, if auto-creating accounts is an 
acceptable solution for email for now.

Of course, we could always do the following:
1. Create them an account automatically and not mail them the password 
(these are two different functions in bugzilla, i just call one after 
the other in the email scripts)
2. If they decide they have the urge to log in to bugzilla, they can 
use the "forgot password" link.

I fear that if we do that, however, people will complain they never got 
sent a password.

We could always start with this, and if people complain, mail them 
passwords. Or the reverse (start with mailing passwords, and if they 
complain, don't).

--Dan

> Gerald