From: "Simon Tournier" <simon.tournier@univ-paris-diderot.fr>
To: "Konrad Hinsen" <konrad.hinsen@cnrs.fr>,
"Ludovic Courtès" <ludovic.courtes@inria.fr>,
"Simon Tournier" <simon.tournier@univ-paris-diderot.fr>
Cc: guix-science@gnu.org, efraim@flashner.co.il
Subject: Re: Online meeting on Mon., Sept. 27th
Date: Fri, 17 Sep 2021 15:12:05 +0200 [thread overview]
Message-ID: <web-253264142@univ-paris7.fr> (raw)
In-Reply-To: <m1tuijvava.fsf@fastmail.net>
Hi,
On Fri, 17 Sep 2021 10:56:25 +0200
Konrad Hinsen <konrad.hinsen@cnrs.fr> wrote:
>Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>
>>> Let meet online the Monday, September 27th at 9:00 CET.
>>
>> Woohoo! I think you meant CEST (UTC+2) though.
Yes, it is 09:00 CEST (Paris time). Sorry for the confusion, jet lag
effect.
>And it would be nice to say where exactly in cyberspace the meeting
>will happen.
It is not decided yet. I will provide the link as soon as possible.
>> 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.
Ah I would like to add another item: optimizing Docker layers for
better caching.
All the best,
simon
next prev parent reply other threads:[~2021-09-17 13:12 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 [this message]
2021-09-17 17:04 ` Ludovic Courtès
-- 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=web-253264142@univ-paris7.fr \
--to=simon.tournier@univ-paris-diderot.fr \
--cc=efraim@flashner.co.il \
--cc=guix-science@gnu.org \
--cc=konrad.hinsen@cnrs.fr \
--cc=ludovic.courtes@inria.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).