From: "Ludovic Courtès" <ludo@gnu.org>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Software Heritage & Guix
Date: Wed, 03 Apr 2019 23:27:40 +0200 [thread overview]
Message-ID: <87tvfeok37.fsf@gnu.org> (raw)
In-Reply-To: <87h8bfh58q.fsf@roquette.mug.biscuolo.net> (Giovanni Biscuolo's message of "Wed, 03 Apr 2019 10:17:57 +0200")
Hi!
Giovanni Biscuolo <g@xelera.eu> skribis:
> mikadoZero <mikadozero@yandex.com> writes:
>
>> Ludovic Courtès writes:
>>
>>> ...
>>> Long-term archival is something that cannot be left to peer-to-peer
>>> networks:
>
> I disagree here: P2P/decentralized archival is a _resilient_ archival
> method and is _not_ in contrast with long-term: a group of users
> (including institutions at various levels) can decide that some or all
> of a "decentralized Software Heritage" archive deserves availability
> guarantees :-)
My point is: the availability guarantee stems from the commitment of a
non-profit to provide the infrastructure and to sustain it. Whether
it’s IPFS or something else doesn’t matter much. It’s largely an
organizational matter more than a technical one.
Ludo’.
next prev parent reply other threads:[~2019-04-03 21:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 16:05 Software Heritage & Guix Ludovic Courtès
2019-03-29 16:42 ` John Soo
2019-03-29 18:19 ` sirgazil
2019-03-30 13:46 ` Pjotr Prins
2019-03-30 15:51 ` znavko
2019-03-30 17:30 ` Pjotr Prins
2019-03-30 18:03 ` znavko
2019-03-30 19:13 ` swedebugia
2019-03-31 16:24 ` Ludovic Courtès
2019-03-31 16:22 ` Ludovic Courtès
2019-03-31 1:57 ` mikadoZero
2019-03-31 16:30 ` Ludovic Courtès
2019-04-03 0:58 ` mikadoZero
2019-04-03 8:17 ` Giovanni Biscuolo
2019-04-03 21:27 ` Ludovic Courtès [this message]
2019-03-31 6:27 ` znavko
2019-04-01 8:33 ` znavko
2019-04-03 7:57 ` Chris Marusich
2019-04-18 16:39 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvfeok37.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=g@xelera.eu \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.