Whenever you create or update a bug or patch you get the e-mail adresses of all users involved in that.
I do not think this has to be available on appdb, bug tracker or the mailing list archive to work.
If you are on the mailinglist, you get it. If you are not and you are an outside just checking the archive there is no need to have more than a name.
If the bug is something interesting you will be notified about comments and updates already and since you can write private messages over winehq already.
revealing other users e-mail adress is not necessary
Re: revealing other users e-mail adress is not necessary
The AppDB doesn't reveal anyone's email address to anyone in its notices, not even to admins.
As for bugzilla, that's third party software that was originally developed by Mozilla and is now used by many projects. The policy here is not to apply custom patches to outside software because of the problems it causes when upgrading. If you want changes to the way bugzilla works, you need to submit patches upstream. https://wiki.mozilla.org/Bugzilla:Developers
As for bugzilla, that's third party software that was originally developed by Mozilla and is now used by many projects. The policy here is not to apply custom patches to outside software because of the problems it causes when upgrading. If you want changes to the way bugzilla works, you need to submit patches upstream. https://wiki.mozilla.org/Bugzilla:Developers
Re: revealing other users e-mail adress is not necessary
Ok maybe i was wrong about appdb, but how about the mailinglist archive? Does it support a more conservative approach yet?
Re: revealing other users e-mail adress is not necessary
The mailing list archive replaces "@" with "at" in email addresses to foil bots, but otherwise does not alter what bugzilla sends to it.
You can always create a separate email address for use in bugzilla if that bothers you.
You can always create a separate email address for use in bugzilla if that bothers you.