unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: Luis Felipe <luis.felipe.la@protonmail.com>, 43871@debbugs.gnu.org
Subject: [bug#43871] [PATCH website] Add community page
Date: Mon, 12 Oct 2020 18:41:01 +0200	[thread overview]
Message-ID: <87pn5no0rm.fsf@gnu.org> (raw)
In-Reply-To: <20201009003823.0a15114b@tachikoma> (Julien Lepiller's message of "Fri, 9 Oct 2020 00:38:23 +0200")

Hello!

(+Cc: Luís Felipe, the web site designer.)

Julien Lepiller <julien@lepiller.eu> skribis:

> From fe6910a5877ad039e2d6cf95efc10a62c0762871 Mon Sep 17 00:00:00 2001
> From: Julien Lepiller <julien@lepiller.eu>
> Date: Fri, 9 Oct 2020 00:32:56 +0200
> Subject: [PATCH] website: Add community page.
>
> * website/apps/media/templates/community.scm: New file.
> * website/apps/media/builder.scm: Add community builder.
> * website/apps/base/templates/components.scm: Add it to the menu.
> * website/apps/media/templates/components.scm: Add resource->shtml.
> * website/apps/media/types.scm: New resource data type.
> * website/apps/media/data.scm: Add community resources.
> * website/static/base/css/index.css: Add css for new classes.
> * website/static/media/css/community.css: New file.
> * website/static/media/img/community/carl-dong-bitcoin-security.webp: New file.

Nice!  It was a bit sad that all this material wasn’t linked.

I wonder if “Community” is the right heading and/or if we should group
additional things in there?

> +(define resources
> +  (list
> +    (resource
> +      #:title (C_ "community resource title" "Everyday use of Guix")
> +      #:link "https://media.marusich.info/everyday-use-of-gnu-guix-chris-marusich-seagl-2018.webm"
> +      #:type 'video
> +      #:language (G_ "English")
> +      #:author "Chris Marushich"
> +      #:date (string->date "2018-10-10" "~Y-~m-~d"))
> +    (resource
> +      #:title (C_ "community resource title" "Bitcoin Build System Security")
> +      #:link "https://www.youtube.com/watch?v=I2iShmUTEl8"
> +      #:type 'video
> +      #:language (G_ "English")
> +      #:preview (guix-url "static/media/img/community/carl-dong-bitcoin-security.webp")
> +      #:author "Carl Dong"
> +      #:date (string->date "2019-06-08" "~Y-~m-~d"))
> +    (resource
> +      #:title (C_ "community resource title" "Reproducible System Administration with GNU Guix")
> +      #:link "https://replay.jres.org/videos/watch/c77b3a44-b75f-4c10-9f39-8fb55ae096d7"
> +      #:type 'video
> +      #:language (G_ "French")
> +      #:author "Julien Lepiller"
> +      #:date (string->date "2019-12-04" "~Y-~m-~d"))
> +    (resource
> +      #:title (C_ "community resource title" "Au-delà des conteneurs : environnements logiciels reproductibles avec GNU Guix")
> +      #:link "https://webcast.in2p3.fr/video/au-dela-des-conteneurs-environnements-logiciels-reproductibles-avec-gnu-guix-1"
> +      #:type 'video
> +      #:language (G_ "French")
> +      #:author "Ludovic Courtès"
> +      #:date (string->date "2019-05-23" "~Y-~m-~d"))
> +    (resource
> +      #:title (C_ "community resource title" "Code Staging in GNU Guix")
> +      #:link "https://arxiv.org/abs/1709.00833"
> +      #:type 'article
> +      #:language (G_ "English")
> +      #:author "Ludovic Courtès"
> +      #:date (string->date "2017-09-04" "~Y-~m-~d"))
> +    (resource
> +      #:title (C_ "community resource title" "Guix: A most advanced operating system")
> +      #:link "https://ambrevar.xyz/guix-advance/index.html"
> +      #:type 'blog
> +      #:language (G_ "English")
> +      #:author "Pierre Neidhardt"
> +      #:date (string->date "2019-01-14" "~Y-~m-~d"))))

At least for the one that’s on YouTube, but perhaps also for the other
videos, we should host a copy at audio-video.gnu.org (I’ll check what it
takes to do that.)

We should also have a policy to not link to material that steers towards
non-free software (I believe the links above are fine).

Last but not least: we should encourage people to submit their things,
because I’m sure there’s much more we could add here!  :-)

That’s all I have to say.  Luís, everyone: thoughts?

Ludo’.




  parent reply	other threads:[~2020-10-12 16:42 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
2020-10-12 16:41 ` Ludovic Courtès [this message]
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=87pn5no0rm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=43871@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=luis.felipe.la@protonmail.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).