From: sirgazil <sirgazil@zoho.com>
To: Catonano <catonano@gmail.com>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, guix-devel <guix-devel@gnu.org>
Subject: Re: package requests
Date: Mon, 27 Apr 2020 16:07:07 +0000 [thread overview]
Message-ID: <171bc646374.b32988984370.2063073606534099294@zoho.com> (raw)
In-Reply-To: <CAJ98PDwq4W3EhKM9SuxF5-c=4PLHcJUjitaA-O=awind8SDUsw@mail.gmail.com>
---- On Mon, 27 Apr 2020 04:14:52 +0000 Catonano <catonano@gmail.com> wrote ----
>
>
> Il giorno sab 25 apr 2020 alle ore 15:06 Tobias Geerinckx-Rice <me@tobias.gr> ha scritto:
> Hi Catonano,
>
> Catonano 写道：
> > Say that some people file bugs in the Guix issue tracker
> > requesting the
> > packaging of some software projects
> >
> > Can a list of such requests be seen in any way ?
>
> […]
>
> > Is there any specific tagging scheme to be used for package
> > requests filing ?
>
> Not that I know of. It's all very ad-hoc and things get lost &
> forgotten.
>
> <https://libreplanet.org/wiki/Group:Guix/Wishlist> is the closest
> thing we have to an ‘official’ list.
>
> While a structured approach would be much better than our wiki
> page, I prefer that wiki page over *our* bug tracker.
>
> don't you like Debbugs ?
> I can see why
> Have you seen this, anyway ?
> https://lists.gnu.org/archive/html/guix-devel/2020-03/msg00238.html
> Sirgazil proposed to send a patch to allow Debbugs to tag package requests so that they could be easily searched
Not really patch Debbugs, but patch the website with proposed changes to make any list of requested packages visible (and add instructions to request new packages).
I still think Debbugs could be used for package requests, even if it doesn't support custom tags like "package request". One could instruct people to send requests to bug-guix@gnu.org using a provided template. For example:
Subject: [PACKAGE REQUEST] Add Some Software
Body: Some other necessary information (website, license?)
Then, maybe link to issues.gnu.org with a query like this:
https://issues.guix.gnu.org/search?query=%5BPACKAGE+REQUEST%5D+in%3Asubject+is%3Aopen
(The in:subject filter doesn't exist, though).
next prev parent reply other threads:[~2020-04-27 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 11:38 package requests Catonano
2020-04-25 12:55 ` Nicolò Balzarotti
2020-04-25 13:06 ` Tobias Geerinckx-Rice
2020-04-26 21:14 ` Catonano
2020-04-27 16:07 ` sirgazil [this message]
2020-04-27 16:42 ` Catonano
2020-04-25 13:52 ` sirgazil
2020-04-26 21:03 ` Catonano
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=171bc646374.b32988984370.2063073606534099294@zoho.com \
--to=sirgazil@zoho.com \
--cc=catonano@gmail.com \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).