unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "jgart" <jgart@dismail.de>
To: guix-devel@gnu.org
Subject: Should a Guix Channel Have a Description?
Date: Sat, 07 Jan 2023 17:08:00 +0000	[thread overview]
Message-ID: <d1ef9d3e5019f3c6a4b68e984f1e772d@dismail.de> (raw)

Hi Guixers,

What do you think of this proposal:

https://issues.guix.gnu.org/60630

Should a <channel> record have a description?

Here's a user story:

WhereIsEveryone is developing a webring as an API for discovering Guix channels and their contents.

With a growing* channels.scm file, IWBN to have a description about each channel as part of the data about that channel in the same way that users get a description about a package.

WDYT

See the toys README** for instructions on how to try this API and for more information on contributing. We could use all the hacking help we can get.

* https://git.sr.ht/~whereiseveryone/toys/tree/master/item/channels.scm
** https://git.sr.ht/~whereiseveryone/toys/#usage


             reply	other threads:[~2023-01-07 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07 17:08 jgart [this message]
2023-01-09 17:38 ` Should a Guix Channel Have a Description? Ludovic Courtès

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=d1ef9d3e5019f3c6a4b68e984f1e772d@dismail.de \
    --to=jgart@dismail.de \
    --cc=guix-devel@gnu.org \
    /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).