From: zimoun <zimon.toutoune@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 43871@debbugs.gnu.org
Subject: [bug#43871] [PATCH website] Add community page
Date: Fri, 09 Oct 2020 01:16:19 +0200 [thread overview]
Message-ID: <86lfgg8g1o.fsf@gmail.com> (raw)
In-Reply-To: <20201009003823.0a15114b@tachikoma> (Julien Lepiller's message of "Fri, 9 Oct 2020 00:38:23 +0200")
Dear,
On Fri, 09 Oct 2020 at 00:38, Julien Lepiller <julien@lepiller.eu> wrote:
> This patch aims at adding a new page on the website that lists external
> resources that talk about guix (conference talks, blog posts and even
> academic papers).
Cool!
> diff --git a/website/apps/media/data.scm b/website/apps/media/data.scm
> index 76af25d..89f7a8c 100644
> --- a/website/apps/media/data.scm
> +++ b/website/apps/media/data.scm
[...]
> @@ -85,6 +87,53 @@ distribution."))
> #:last-updated (string->date "2020-03-28T16:00:00" "~Y-~m-~dT~H:~M:~S")))))
>
>
> +(define resources
Maybe chronological order? Last first:
> + (list
> + (resource
> + #:title (C_ "community resource title" "Reproducible System Administration with GNU Guix")
> + #:date (string->date "2019-12-04" "~Y-~m-~d"))
> + (resource
> + #:title (C_ "community resource title" "Bitcoin Build System Security")
> + #:date (string->date "2019-06-08" "~Y-~m-~d"))
> + (resource
> + #:title (C_ "community resource title" "Au-delà des conteneurs : environnements logiciels reproductibles avec GNU Guix")
> + #:date (string->date "2019-05-23" "~Y-~m-~d"))
> + (resource
> + #:title (C_ "community resource title" "Guix: A most advanced operating system")
> + #:date (string->date "2019-01-14" "~Y-~m-~d"))))
> + (resource
> + #:title (C_ "community resource title" "Everyday use of Guix")
> + #:date (string->date "2018-10-10" "~Y-~m-~d"))
> + (resource
> + #:title (C_ "community resource title" "Code Staging in GNU Guix")
> + #:date (string->date "2017-09-04" "~Y-~m-~d"))
Does it make sense to add all the FOSDEM ones? For example:
https://archive.fosdem.org/2014/schedule/event/gnuguix/
https://archive.fosdem.org/2015/schedule/event/the_emacs_of_distros/
etc. well what under talks/fosdem-*
All the best,
simon
next prev parent reply other threads:[~2020-10-08 23:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 22:38 [bug#43871] [PATCH website] Add community page Julien Lepiller
2020-10-08 23:16 ` zimoun [this message]
2020-10-12 16:41 ` Ludovic Courtès
2020-10-12 19:45 ` Brett Gilio
2020-10-13 12:47 ` Luis Felipe via Guix-patches via
2020-10-13 20:06 ` Ludovic Courtès
2020-10-13 20:46 ` Julien Lepiller
2020-11-04 10:38 ` zimoun
2020-11-04 16:12 ` Luis Felipe via Guix-patches via
2020-11-04 18:31 ` zimoun
2020-11-05 0:36 ` Luis Felipe via Guix-patches via
2021-05-25 14:55 ` Luis Felipe via Guix-patches via
2021-05-25 15:07 ` Julien Lepiller
2021-07-01 13:31 ` Luis Felipe via Guix-patches via
2021-11-19 14:36 ` bug#43871: " 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=86lfgg8g1o.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=43871@debbugs.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).