From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org, 53166@debbugs.gnu.org,
zimoun <zimon.toutoune@gmail.com>
Subject: [bug#53166] [PATCH] website: Announce Guix days!
Date: Tue, 11 Jan 2022 20:16:13 +0100 [thread overview]
Message-ID: <875yqqt75u.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")
Howdy!
Julien Lepiller <julien@lepiller.eu> skribis:
>>From b1ed3af5838b65293441f62e5d6447357be849b4 Mon Sep 17 00:00:00 2001
> From: Julien Lepiller <julien@lepiller.eu>
> Date: Mon, 10 Jan 2022 18:05:05 +0100
> Subject: [PATCH] website: Add conference announcement.
>
> * website/posts/online-guix-days-2022-announce-1.md: New file.
> * website/static/blog/img/Guix-Days-online-2022.png: New file.
> * website/apps/base/templates/theme.scm: Add announce banner.
Looks great to me, even more so with Luis’ artwork! :-)
Minor issues:
> +++ b/website/posts/online-guix-days-2022-announce-1.md
> @@ -0,0 +1,126 @@
> +title: Announcing the second online Guix Days Conference
Remove “Conference”?
> +date: 2022-01-10 00:00
> +author: Guix Hackers
> +slug: online-guix-days-2022-announce-1
s/announce/announcement/ ? (“announce” is a verb)
> +Talks will be released **before** the conference day, **watch them as soon
> +as possible**! And **no registration fee**.
s/And/And:/
> +##### Until February 8: talks proposal
“talk proposals”?
> +##### February 12-18: watch the talks
I know I’m a professional nitpicker, but I’d use en dash for date ranges
throughout, like this: 12–18. :-)
Thank you the organization!
Ludo’.
next prev parent reply other threads:[~2022-01-11 19:17 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 ` Ludovic Courtès [this message]
2022-01-12 11:58 ` bug#53166: " Ludovic Courtès
2022-01-12 12:07 ` 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=875yqqt75u.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=53166@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
--cc=zimon.toutoune@gmail.com \
/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).