I came up with the idea of creating a global mailmap service earlier
this year and, given a recent discussion on maintaining .mailmap, I
decided to bring it up here. While only marginally related to Git
development, I hope that it is relevant enough to not be considered
spam.
The basic idea of the service I imagine is simple:
1. You register a primary email address and specify a password. You
receive a verification email to confirm that the address is yours.
2. At any time, you can add additional email addresses and link them to
your primary email address, using your previously specified password.
You can also update your primary email address. Any new addresses
obtain verification emails such that you cannot steal somebody else's
identity.
3. Anybody can use a public lookup interface to obtain the current
primary email address corresponding to any registered email address
they enter.
According to the principle of data economy, the full list of email
addresses is kept private. An email address is only returned if the user
performing a lookup already owns a (possibly outdated) email address of
the same user.
A batch query to the service can be used to automatically generate a
.mailmap file without having to maintain it on a per-project basis and
without having to be careful and confirm every entry manually.
I created a PoC here [1]. You can run
git log --pretty='%ae' | sort -u | curl -Ftopic=git -Femails='<-' https://mailmap.org/
from the Git source tree to auto-generate a .mailmap file. Of course,
this idea only works if people agree that it is useful and the majority
of developers register their email addresses to the service.
I am aware that some users use different email addresses for different
projects. The current approach is allowing the user to add primary
"topic email addresses". A request can optionally specify a topic (such
as "git" in the request above) and the lookup may potentially return an
email address different from the generic primary address. Of course,
these topics need to be standardized in some way. There might be better,
more sophisticated ways to tackle this and I'd be happy to discuss them
if there is interest in the general approach.
I am also aware that this may not cover all potential uses of .mailmap
files but, according to my understanding and experience, it should cover
a fairly large amount. The remaining adjustments can still be made on
top on a per-project basis.
Best regards,
Lukas
[1] https://mailmap.org/
