unofficial mirror of 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <>
To: "Simon Tournier" <>
Subject: Re: [event] Next steps for 2021-2022?
Date: Thu, 09 Sep 2021 10:07:56 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Simon Tournier's message of "Wed,  08 Sep 2021 10:34:32 +0200")


"Simon Tournier" <> skribis:

> I propose a virtual meeting to discuss and list what we – as a
> community – would like to tackle this year.  For instance, my whishlist
> is:
>  - better coverage with long-term archive using Software Heritage

… and with Disarchive.

>  - online events as training / season school / workshop


Some items from my to-do list:

  - Good micro-architecture story with function multi-versioning along
    the lines of
    <> (help
    welcome especially on finding good applications to benchmark!).

  - Relocatable pack execution on clusters that lack user namespaces,
    thus with GUIX EXECUTION_ENGINE=fakechroot (I noticed glitches in
    the past due to glibc NSS and things like that.)

  - “Converting” papers to use a Guix workflow similar to what I did in
    <>, with the goal of extracting
    common helpers to make it more approachable.

> Let schedule a date between September, 27th and 30th.  Personally, I
> would prefer the morning (8-13:00 CET).  Drop an email (public or
> private) and let try to accommodate for all.

Works for me.

Thanks for starting this initiative!


  reply	other threads:[~2021-09-09  8:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08  8:34 [event] Next steps for 2021-2022? Simon Tournier
2021-09-09  8:07 ` Ludovic Courtès [this message]
2021-09-10  8:48   ` Konrad Hinsen
2021-09-14 13:05 ` Efraim Flashner
2021-09-24  9:04 ` User & Developer Meetup on Sept. 27th 9:00-10:30 (AM CEST) Simon Tournier
2021-09-24 16:00   ` Ludovic Courtès
2021-09-26 19:08   ` Yann Dupont

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).