Ahah. Yes. Agreed:
In an issue or issue comment, any link with a BZ User Name has a mailto: behind it. It will be the *current* e-mail that the account is set to forward to. For example, I just changed my forwarding for orcmid@ openoffice.org in the AOO BZ to orcmid@ apache.org, and that is now what the "orcmid" link will open a new e-mail to if the link is followed. If you mouse over the link, you should see that address as well, depending on how your browser does it. And a clip-board copy of the link will bring the e-mail address. I need to check that the log-in has not actually changed. I think it is the forwarding address that is shown, not the login id. I also think the name on the link might be derived from the full-name field in the account entry. To change this requires some careful analysis of how BZ handles this and how it might have been warped in having the migration work. The alternative would be to have a profile-based system that provided a mailing form that did not disclose the recipient's e-mail address. I don't know if it is in the Apache DNA (and I hesitantly mention that the Forums do exactly that). For ASF, it is important to have everything grounded to some concrete identifier. The current approach involves e-mail addresses, where committers are more grounded: there is a definite connection between the Apache User Name/ID and an iCLA. There is also a MailAlias registry where other e-mails used by a committer can be listed (and known to all committers) so that there use can still be recognized as theirs (by manually checking that list, usually). It is not a perfect system, but apparently good enough. I suspect that, as a policy matter, the forwarding mail associated with a BZ account is as important an identifier as the visible e-mail addresses shown on mailing lists and elsewhere. I wonder what conversation is needed to modify this. Certainly, the registration process for Bugzilla and other services established at AOO need to inform folks when the e-mail provided as part of a registration or subscription will be made visible. It is important for those who fear scraping of their e-mail addresses for use by spammers, phishers, stalkers, and other undesirables. Each will determine how that risk is to be tolerated or mitigated. (Any ASF Privacy Policy statements should also indicate that there are conditions where an e-mail address is always public.) For Apache committers, those @apache.org e-mail addresses are public and easily obtained. Having them in convenient mailto: elements on a web page simplifies the work. Still, I think there is no escape. -----Original Message----- From: Marcus (OOo) [mailto:[email protected]] Sent: Sunday, November 13, 2011 12:38 To: [email protected] Subject: Re: How to change the login of AOO BZ instance? [ ... ] Sorry, but you still don't get it. ;-) When I login in BZ and write comments to issues my full mail address is shown. When I change my address from "[email protected]" to a new one, this new mail address in shown in the comment header in issues and update mails from BZ. <example quote> https://issues.apache.org/ooo/show_bug.cgi?id=118518 orcmid <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Issue Type|DEFECT |TASK --- Comment #1 from orcmid <[email protected]> 2011-10-17 04:36:20 UTC --- The issue on legal-discuss is LEGAL-104, at <https://issues.apache.org/jira/browse/LEGAL-104>. </example quote> This is what I want to prevent. OK, I can change to "[email protected]". But I want to have just an ID or name or similar but no mail address. I hope it's now clear. :-) Marcus
