The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Edouard Klein <edouardklein@gmail.com>
To: Robert Brockway <robert@timetraveller.org>
Cc: TUHS List <tuhs@tuhs.org>
Subject: Re: [TUHS] UNESCO call for a study on the future institutional structure for Software Heritage (fwd)
Date: Thu, 10 Sep 2020 11:33:38 +0200	[thread overview]
Message-ID: <87k0x2ugb2.fsf@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2009101414510.31988@mira.opentrend.net>

Adding a bit of context, Software Heritage is used for example by GNU
Guix, which aims at making builds reproducible down to the exact bit.

Every piece of public source code used by Guix in a build will get
automatically archived by software heritage.

https://www.softwareheritage.org/2019/04/18/software-heritage-and-gnu-guix-join-forces-to-enable-long-term-reproducibility/

Given the time spent by people here trying to get things to build again,
I expect the ability of Guix to freeze and archive all dependencies and
build instructions to be of interest here:
https://guix.gnu.org/manual/en/html_node/Channels.html#Replicating-Guix

Cheers,

Edouard.

Robert Brockway writes:

> FYI.  UNESCO call for a study on the future institutional structure for Software
> Heritage.
>
> ---------- Forwarded message ----------
> Dear all,
>     I do hope you are all safe, and could take some time off to recharge the
>     batteries that these hectic times have drained quite a bit.
>
> Some of you know already Software Heritage (https://www.softwareheritage.org):
> it is a nonprofit initiative, started by Inria and supported by UNESCO, whose 
> mission is to ensure that software source code, as part of the common heritage
> of humankind, is preserved over time and made available to all, building, 
> maintaining and developing a universal source code archive, providing persistent
> identifiers for all software artifacts, and creating the largest shared
> knowledge base about software artifacts ever built.
>
> This is a long term undertaking, and UNESCO has just published a call for
> advice, via a small feasibility study providing options for establishing the 
> future independent, non profit, multi-stakeholder organization that will host
> Software Heritage for the long run.
>
> As Software Heritage is a shared infrastructure that will support use cases of
> interest to the members of this list, I take the liberty to bring this call to 
> your attention, and I'd be very grateful if you could also forward it to
> whomever you believe could be interested in answering.
>
> Detailed information on the expected advice and procedures to answer the call is
> online at:
> https://careers.unesco.org/job/Paris-Consultant-on-Software-Heritage-CIMID/519826502/
>
> The deadline for the answer is September 26th.
>
> Thank you for your help
>
> Roberto Di Cosmo (roberto@dicosmo.org)
> _______________________________________________
> foundations mailing list
> foundations@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/foundations


  reply	other threads:[~2020-09-10  9:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10  4:16 Robert Brockway
2020-09-10  9:33 ` Edouard Klein [this message]
2020-09-13 17:42   ` Paul Winalski
2020-09-14  0:33     ` John Gilmore

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=87k0x2ugb2.fsf@gmail.com \
    --to=edouardklein@gmail.com \
    --cc=robert@timetraveller.org \
    --cc=tuhs@tuhs.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. 
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 NNTP newsgroup(s).