unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Luis Felipe via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Julien Lepiller <julien@lepiller.eu>,
	"43871@debbugs.gnu.org" <43871@debbugs.gnu.org>
Subject: [bug#43871] [PATCH website] Add community page
Date: Tue, 13 Oct 2020 12:47:11 +0000	[thread overview]
Message-ID: <q1zs49KModf58A5fGfRcemgcOdE87-D20jZt3lBRQmJ52htHXfk3gz3AhjzGQDsmzamOoQxIU6_5pf8MtFTePDPH-rxlynmd071bupoTc3E=@protonmail.com> (raw)
In-Reply-To: <87pn5no0rm.fsf@gnu.org>

Hi,

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, October 12, 2020 4:41 PM, Ludovic Courtès ludo@gnu.org wrote:

[...]

> 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?

Well, my idea was to have these kinds of resources grouped according to their types (https://lists.gnu.org/archive/html/guix-devel/2017-12/msg00356.html). So, instead of a Community resources entry in the Media menu, there would be separate entries like Talks, Papers, etc.

So the Media part of the website could work like the Blog in that you could explore all kinds of media (/lang/media/) or media of some type (e.g. /lang/media/talks/).

Also, at this point you can see that blog posts and media items are resources that usually have a preview with similar information: title, date, summary, etc. Using record types you end up defining one preview procedure for every record type (type->shtml) with pretty much the same body. At that time I was looking for records that allow some kind of inheritance, or GOOPS, to have one preview procedure (or method) that would accept different records/objects with a common ancestor specifying the common fields (title, date, summary, etc.). I tried GOOPS at that time and it worked.

I don't know, I'm still inclined to do it this way...




  parent reply	other threads:[~2020-10-13 12:48 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
2020-10-12 19:45   ` Brett Gilio
2020-10-13 12:47   ` Luis Felipe via Guix-patches via [this message]
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='q1zs49KModf58A5fGfRcemgcOdE87-D20jZt3lBRQmJ52htHXfk3gz3AhjzGQDsmzamOoQxIU6_5pf8MtFTePDPH-rxlynmd071bupoTc3E=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=43871@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=ludo@gnu.org \
    --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).