From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org, 53166@debbugs.gnu.org
Subject: Re: bug#53166: [PATCH] website: Announce Guix days!
Date: Wed, 12 Jan 2022 12:58:03 +0100 [thread overview]
Message-ID: <87ee5drws4.fsf_-_@gnu.org> (raw)
In-Reply-To: <20220110181521.71066758@tachikoma.lepiller.eu> (Julien Lepiller's message of "Mon, 10 Jan 2022 18:16:27 +0100")
Hi again!
Julien Lepiller <julien@lepiller.eu> skribis:
> +##### Until February 8: talks proposal
> +
> +Propose your talks by sending them to `guix-days@gnu.org`. Feel free to drop
> +in `#guix` on irc.freenode.net to discuss what you would like to talk about
Should be irc.libera.chat.
A couple of ideas occurred to me while biking this morning:
> +We welcome all kinds of topics from the community, especially your own experience
> +with Guix, your cool projects that involve Guix in some way, infrastructure around
> +guix (translations, continuous integration, ...), and any subject you feel
> +should be discussed during the conference.
What about adding something like:
We particularly encourage people who consider themselves part of a
group underrepresented in Guix and the broader free software movement
to submit a talk; do not hesitate to get in touch with the organizers
at `guix-days@gnu.org` if unsure or if you would like guidance on how
to prepare your talk.
Please make sure your talk is accessible to a non-expert audience, for
instance by explaining the general context before diving into
technical descriptions, and by avoiding acronyms and jargon.
?
After the first sentence above, I also thought about that one:
We accept talks in languages other than English provided English
subtitles are included.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2022-01-12 13:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 1:37 Organising Guix Days Julien Lepiller
2021-12-11 11:09 ` Gábor Boskovits
2021-12-13 9:07 ` zimoun
2021-12-18 17:56 ` Pjotr Prins
2021-12-20 17:51 ` Ludovic Courtès
2021-12-20 22:37 ` zimoun
2022-01-06 19:54 ` zimoun
2022-01-10 17:16 ` [PATCH] website: Announce Guix days! Julien Lepiller
2022-01-10 19:52 ` Luis Felipe
2022-01-10 21:04 ` Julien Lepiller
2022-01-10 22:44 ` [bug#53166] " Luis Felipe via Guix-patches via
2022-01-10 23:06 ` Julien Lepiller
2022-01-11 0:47 ` Luis Felipe
2022-01-11 9:41 ` Julien Lepiller
2022-01-11 13:15 ` Luis Felipe
2022-01-11 10:56 ` zimoun
2022-01-11 19:16 ` [bug#53166] " Ludovic Courtès
2022-01-12 11:58 ` Ludovic Courtès [this message]
2022-01-12 12:07 ` bug#53166: " Julien Lepiller
2022-01-12 12:20 ` Julien Lepiller
2022-01-12 22:07 ` [bug#53166] " Julien Lepiller
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=87ee5drws4.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=53166@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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).