Users should have full control of their public email id

Bug #646026 reported by Aaron Bentley
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Both Bazaar and debian packaging tools use name+email address combinations as a means of identification. Experience has shown that Bazaar users want control over their email id-- they do not want it autogenerated for them. This is why bzr no longer autogenerates a user ID when none is supplied. Packagers probably want the same thing.

Now that lp:~jtv/launchpad/bug-643345 has landed, Launchpad uses the preferredemail if known, falling back to the noreply address. Both options are wrong: the preferredemail may be private, and even if not private, it may not be the user's desired identity. Silently using a bogus address is also wrong.

Instead, users should be able to select a public email id. Some users will want to use an invalid address in their email id to protect their privacy, so this should not be required to be a valid address (though we should require that it be a well-formed email id).

Aaron Bentley (abentley)
Changed in rosetta:
status: New → Confirmed
status: Confirmed → New
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Данило Шеган (danilo) wrote :

I am not in complete agreement that this is what we should do for translations. FWIW, the actual producers of the change are people who have done the translations for this particular revision. The actual committer is Launchpad Translations on their and behalf of the person who set up the export.

Considering it's common practice to use revision logs to extract contributor information, it might actually be a better idea to use the real people doing the contribution in appropriate places (i.e. --author), and mark the Launchpad Translations as the 'committer'.

Changed in rosetta:
status: New → Triaged
importance: Undecided → Low
tags: added: code-integration
Revision history for this message
Aaron Bentley (abentley) wrote : Re: [Bug 646026] Re: Users should have full control of their public email id

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/27/2010 09:58 AM, Данило Шеган wrote:
> I am not in complete agreement that this is what we should do for
> translations. FWIW, the actual producers of the change are people who
> have done the translations for this particular revision. The actual
> committer is Launchpad Translations on their and behalf of the person
> who set up the export.

Software is always committing on your behalf, though, even if it's
because you typed "bzr commit". So yes, I think that a public email id
should be used, and it should be the public email id of the person who
set up the export.

> Considering it's common practice to use revision logs to extract
> contributor information, it might actually be a better idea to use the
> real people doing the contribution in appropriate places (i.e.
> --author), and mark the Launchpad Translations as the 'committer'.

In order to provide accurate attribution of authors, we would need
public email ids for them, since the format is the same as that for
committers.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkygpmcACgkQ0F+nu1YWqI1COQCfZtOHJydGSvTO7FJaSIEei+Iv
UEUAmQFtJfAALyIdYWzbmOhOsmAraicb
=yrxv
-----END PGP SIGNATURE-----

Curtis Hovey (sinzui)
tags: added: translations-branch
removed: code-integration
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.