unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: "Simon Tournier" <simon.tournier@univ-paris-diderot.fr>
Cc: Konrad Hinsen <konrad.hinsen@cnrs.fr>,
	 guix-science@gnu.org, efraim@flashner.co.il
Subject: Re: Online meeting on Mon., Sept. 27th
Date: Fri, 17 Sep 2021 19:04:12 +0200	[thread overview]
Message-ID: <87y27vw2ur.fsf@inria.fr> (raw)
In-Reply-To: <web-253264142@univ-paris7.fr> (Simon Tournier's message of "Fri,  17 Sep 2021 15:12:05 +0200")

Hello!

"Simon Tournier" <simon.tournier@univ-paris-diderot.fr> skribis:

> On Fri, 17 Sep 2021 10:56:25 +0200
>  Konrad Hinsen <konrad.hinsen@cnrs.fr> wrote:
>>Ludovic Courtès <ludovic.courtes@inria.fr> writes:

[...]

>>> What duration did you have in mind?  Maybe 1h30–2h?  The challenge
>>will
>>> be to leave room for each topic.
>>
>>Given that the point is not to work on a topic, but just to check who
>>is
>>interested in what, we could set a limit of 15 minutes per topic, with
>>a
>>general discussion in the end.
>
> Yes, that's the idea. :-)  We could then organize hackathons or similar
> events to address a specific item.

+1!

Since Simon tends to be talkative, I feel like Konrad would be a perfect
timekeeper.  :-)

> Ah I would like to add another item: optimizing Docker layers for
> better caching. 

Sounds good.  I guess we can prepare an editable notepad with the list
of topics beforehand?

Thanks,
Ludo’.


  reply	other threads:[~2021-09-17 17:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  6:23 Online meeting on Mon., Sept. 27th Simon Tournier
2021-09-17  7:25 ` Ludovic Courtès
2021-09-17  8:56   ` Konrad Hinsen
2021-09-17 13:12     ` Simon Tournier
2021-09-17 17:04       ` Ludovic Courtès [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-23 15:11 Paul Garlick

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=87y27vw2ur.fsf@inria.fr \
    --to=ludovic.courtes@inria.fr \
    --cc=efraim@flashner.co.il \
    --cc=guix-science@gnu.org \
    --cc=konrad.hinsen@cnrs.fr \
    --cc=simon.tournier@univ-paris-diderot.fr \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).