unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Julien Lepiller" <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Thank you for participating in the Guix Day!
Date: Fri, 27 Nov 2020 15:01:32 +0100	[thread overview]
Message-ID: <86zh32rj9f.fsf@gmail.com> (raw)
In-Reply-To: <87zh33t6d2.fsf@gnu.org>

Hi Ludo,

On Fri, 27 Nov 2020 at 11:57, Ludovic Courtès <ludo@gnu.org> wrote:

> Despite being a first experience, the live event went very smoothly (for
> me at least, with ungoogled-chromium), it was great to see faces during
> the break :-), and the discussions were all exciting for me.  I agree
> it’d be great to have a blog post summarizing the event while it’s
> fresh, even if it’s concise because we were all busy listening and
> chatting instead of taking notes.

The blog post is coming…  Writing depends on the materials at hand; for
now nothing.

Could you send your Org file to guix-days? Because I only noted the
items that interested me.  Well, I volunteer to add words because it is
worth, IMHO.  Nothing is written on stone but from my point of view, it
is good to specify where Guix is eager to go more or less and especially
helpful for the future when looking back. :-)

BTW, initially the idea was to publish in this very blog post the links
of the talks on audio-video.gnu.org.  But, I am confused how to upload
them and the GNU folks behind have not answered to my email.  Anyway, it
is not a blocking and will be added later.


> I like the idea of having per-topic sub-rooms next time, presumably for
> a few select “hot topics”.  Some people asked whether a recording of the
> live event was available, and I think it might be a good idea to do that
> too.

When preparing, we discussed per-topic sub-room but the implementation
was vague.  Now, it is clearer, so definitively for the next one. :-)

About not recording, it was a conscientious choice.  We discussed it and
we agreed that not-recording seems more in the usual “unconference” Guix
style; especially discussions are freer when the words are not saved for
eternity and so take the floor should be less impressive.

Let revisit this topic for the next events.


All the best,
simon


  reply	other threads:[~2020-11-27 14:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24  2:00 Thank you for participating in the Guix Day! Julien Lepiller
2020-11-24 15:43 ` Arun Isaac
2020-11-24 17:58   ` Leo Famulari
2020-11-25 12:37     ` Arun Isaac
2020-11-27 10:44     ` Ludovic Courtès
2020-11-25 13:19   ` zimoun
2020-11-25 17:52     ` Leo Famulari
2020-11-26 19:18   ` Andreas Enge
2020-11-24 20:26 ` raingloom
2020-11-25  3:53   ` Leo Famulari
2020-11-25 22:28     ` raingloom
2020-11-25 23:00       ` zimoun
2020-11-26  4:23         ` raingloom
2020-11-25 10:47   ` Michael Rohleder
2020-11-25 13:21     ` zimoun
2020-11-25 17:50       ` Michael Rohleder
2020-11-25 18:24         ` Leo Famulari
2020-11-25 22:57           ` zimoun
2020-11-26 11:32           ` Why is BigBlueButton slow on GuixSystem (was: Re: Thank you for participating in the Guix Day!) Jonathan Brielmaier
2020-11-26 18:55             ` Leo Famulari
2020-11-25 22:31     ` Thank you for participating in the Guix Day! raingloom
2020-11-26  4:17       ` Leo Famulari
2020-11-26 14:42         ` raingloom
2020-11-26 18:57           ` Leo Famulari
2020-11-27 10:57 ` Ludovic Courtès
2020-11-27 14:01   ` zimoun [this message]
2020-12-05 14:13     ` 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=86zh32rj9f.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=ludo@gnu.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.
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).