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 16:33:49 +0200 [thread overview]
Message-ID: <4df2f043-cde1-8128-8911-e3d6bfc2958e@fannys.me> (raw)
In-Reply-To: <ZfhNb4M1JEnrAF9V@jurong>
On 3/18/24 16:19, Andreas Enge wrote:
> Am Mon, Mar 18, 2024 at 04:03:20PM +0200 schrieb MSavoritias:
>> Rewriting history is the wrong question imo. I dont think a request to
>> change all of the history of Guix will be accepted anyway.
>> A much easier thing to do is to change the approach in the future. And let
>> all the past history untouched.
> I was well thinking about the future history as well as the past one...
> Everything we do now becomes unmutable history in the future; so the
> question how we can rewrite an a priori unmutable history remains the same,
> regardless of the date when person X wants to be known as person Y: Also in
> the future, someone may wish to travel to a time before the change.
> And the fundamental problem of history rewriting remains; I do not see
> how we could simplify it. So I do not think that it is "a much easier
> thing to do". Please feel free to prove me wrong by making a concrete
> suggestion!
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
So no reason we couldn't do something like this.
>
> Am Mon, Mar 18, 2024 at 04:00:38PM +0200 schrieb MSavoritias:
>> On 3/18/24 15:12, Simon Tournier wrote:
>>> Again, this is an incorrect frame, IMHO. Software Heritage (SWH) do the
>>> things you granted them to do. SWH respects the “ethical” definition of
>>> “free software”.
>> You are bringing the legal argument again. The argument that you can do what
>> you want with Free Software is based around a licence which is a legal
>> construct of states.
> I think there is a misunderstanding here, rooted in the use of "you" in
> "you can do what you want". We need to be clear about whom we are speaking.
> There is SWH, and what they can do is a result of the free license. The
> other question is what we as the Guix community want to do (and can do);
> I would suggest to concentrate in our discussion on the latter, which is
> where we have agency.
>
> Andreas
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.
MSavoritias
>
next prev parent reply other threads:[~2024-03-18 14:34 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 [this message]
2024-03-18 15:14 ` Andreas Enge
2024-03-18 15:34 ` MSavoritias
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=4df2f043-cde1-8128-8911-e3d6bfc2958e@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).