From: "Ludovic Courtès" <ludo@gnu.org>
To: mikadoZero <mikadozero@yandex.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Software Heritage & Guix
Date: Sun, 31 Mar 2019 18:30:12 +0200 [thread overview]
Message-ID: <871s2n0zxn.fsf@gnu.org> (raw)
In-Reply-To: <cuczhpb4xgm.fsf@yandex.com> (mikadoZero's message of "Sat, 30 Mar 2019 21:57:45 -0400")
Hi,
mikadoZero <mikadozero@yandex.com> skribis:
> From reading the post I found it unclear what this Software Heritage
> group is and what it's relation to Guix is.
Software Heritage is a non-profit currently hosted by Inria (I work for
Inria, but I’m not affiliated with Software Heritage.) I know the
people who work on Software Heritage and I’m sympathetic to their goals,
but other than that there’s no connection between them and Guix. Their
web site explains their mission and goals better than I do.
The archive they maintain is centralized (although it has mirrors).
Long-term archival is something that cannot be left to peer-to-peer
networks: it’s something where you want availability guarantee, whereas
peer-to-peer storage networks usually replicate content that’s popular,
while unpopular content disappears.
Ludo’.
next prev parent reply other threads:[~2019-03-31 16:30 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 [this message]
2019-04-03 0:58 ` mikadoZero
2019-04-03 8:17 ` Giovanni Biscuolo
2019-04-03 21:27 ` Ludovic Courtès
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
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=871s2n0zxn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mikadozero@yandex.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).