From: MSavoritias <email@msavoritias.me>
To: Andreas Enge <andreas@enge.fr>
Cc: Simon Tournier <zimon.toutoune@gmail.com>,
Attila Lendvai <attila@lendvai.name>, Ian Eure <ian@retrospec.tv>,
guix-devel <guix-devel@gnu.org>
Subject: Re: rewriting history; Was: Concerns/questions around Software Heritage Archive
Date: Mon, 18 Mar 2024 17:34:11 +0200 [thread overview]
Message-ID: <02888c81-e835-2818-6616-60eab10bd7c6@fannys.me> (raw)
In-Reply-To: <ZfhaX6D21KOy7CG7@jurong>
On 3/18/24 17:14, Andreas Enge wrote:
> Am Mon, Mar 18, 2024 at 04:33:49PM +0200 schrieb MSavoritias:
>> Actually gitlab already is facing something like that and they are doing
>> what was proposed elsewhere: mapping of UUIDs to display names
>> https://gitlab.com/gitlab-org/gitlab/-/issues/20960
> Interesting, thanks! It is something that maybe could be implemented by
> Savannah, but it would probably require a bit of thought. And yet again,
> somehow the mapping uuid<->"real" names would have to be public (people
> would "git clone" commits with uuids, and would need to locally replace
> them by "real" names); so people can always keep copies of the mapping
> over time.
Sure. But we can only say about Guix not everything else.
> I am also not quite sure about the signing process for committers;
> in principle keys are enough, but in GPG they are tied to email addresses,
> and I do not know whether we use this in Guix.
I hope we don't because i use ssh to sign commits personally :D
>
> In the end, my impression is this will not achieve much more than what we
> already have with the .mailmap approach. In a sense, everyone would use
> a pseudonym (their uuid), and then we would keep a mapping between these
> pseudonyms and, well, "real" names or other pseudonyms chosen by the
> contributors...
>
> Hm, this could indeed be implemented exactly with .mailmap, no?
> We would need to enforce that authors use a uuid of a specific format,
> and potentially an empty or dummy email address, or another uuid.
> Then we could keep a .mailmap file. The history of "real" identities
> would still be visible in the git history, but as said above, anyway
> we could not prevent people from storing the association information
> over time.
Nicknames may change tho. UUIDs are not in any way meaningful to humans
so i doubt we would need to change them.
I have changed nicknames once for example.
>> Right fair. As I have said before SWH does break Guix CoC effectively right
>> now.
>> So what Guix does from this point on will effectively dictate if the CoC is
>> valid or not.
> Well, the CoC is valid on our communication channels; so what SWH does with
> our software is outside its scope (that is governed by the license).
>
> Andreas
My question was more like:
In the next Guix Days or any Guix conference, do we allow SWH to
participate if this matter is still unresolved?
Because we would be basically inviting people that don't respect the CoC.
MSavoritias
next prev parent reply other threads:[~2024-03-18 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 0:10 rewriting history; Was: Concerns/questions around Software Heritage Archive Attila Lendvai
2024-03-18 10:10 ` MSavoritias
2024-03-18 11:26 ` Simon Tournier
2024-03-18 12:08 ` Daniel Littlewood
2024-03-18 21:14 ` Tomas Volf
2024-03-19 10:04 ` Attila Lendvai
2024-03-18 13:35 ` Andreas Enge
2024-03-18 14:03 ` MSavoritias
2024-03-18 14:19 ` Andreas Enge
2024-03-18 14:33 ` MSavoritias
2024-03-18 15:14 ` Andreas Enge
2024-03-18 15:34 ` MSavoritias [this message]
2024-03-22 22:48 ` indieterminacy
2024-03-18 10:51 ` pelzflorian (Florian Pelz)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02888c81-e835-2818-6616-60eab10bd7c6@fannys.me \
--to=email@msavoritias.me \
--cc=andreas@enge.fr \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).