all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "jgart" <jgart@dismail.de>
Cc: Liliana Marie Prikler <liliana.prikler@gmail.com>, 60630@debbugs.gnu.org
Subject: [bug#60630] [PATCH] guix: channels: Add description field.
Date: Tue, 10 Jan 2023 10:50:39 +0100	[thread overview]
Message-ID: <875ydepvkg.fsf_-_@gnu.org> (raw)
In-Reply-To: <b689d55184cee4046ecb248e1502f395@dismail.de> (jgart@dismail.de's message of "Tue, 10 Jan 2023 02:38:14 +0000")

Hi,

"jgart" <jgart@dismail.de> skribis:

>> Right, I agree. What use case did you have in mind, jgart?
>
> See the search that we are building here:
>
> https://toys.whereis.みんな/

Woow, very nice!  We definitely need that kind of tool.

There might be interesting stuff to borrow/share with hpcguix-web, in
particular the bit the periodically updates channels from which packages
are displayed.

> toys is a channel webring in the form of a web API. It currently allows searching for public symbols (parses docstring info if available), services, and packages across the Guix channels that are part of the webring channels.scm file: https://git.sr.ht/~whereiseveryone/toys/tree/master/item/channels.scm
>
> We'd like to be able to have a standardized way to get a channel description in the same way that we have a standardized way to get a description or synopsis of a package.
>
> In other words, we want to make it easy to describe each channel for the users that subscribe to that channel or are browsing channels for stuff that they might want to use.

Right, so I think this could go in <channel-metadata> and
‘read-channel-metadata’, which is what reads ‘.guix-channel’.  To
support i18n, we might want to have a format similar to that of channel
news files.

As additional metadata, we might want to add a link to a logo, to a
substitute server, substitute key, and things like that, as in:

  https://gitlab.inria.fr/guix-hpc/website/-/blob/master/channels.scm

So I’m closing this one and looking forward to addressing this!

Thanks,
Ludo’.




      reply	other threads:[~2023-01-10 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07 16:24 [bug#60630] [PATCH] guix: channels: Add description field jgart via Guix-patches via
2023-01-08 15:42 ` Liliana Marie Prikler
2023-01-08 15:43 ` [bug#60630] " Liliana Marie Prikler
2023-01-09 16:25   ` Ludovic Courtès
2023-01-10  2:38   ` jgart via Guix-patches via
2023-01-10  9:50     ` Ludovic Courtès [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875ydepvkg.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=60630@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=liliana.prikler@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.