From: zimoun <zimon.toutoune@gmail.com>
To: "bdju" <bdju@tilde.team>
Cc: Jacob Hrbek <kreyren@rixotstudio.cz>, 51642@debbugs.gnu.org
Subject: bug#51642: Package wishlist location
Date: Mon, 08 Nov 2021 17:09:28 +0100 [thread overview]
Message-ID: <87ilx2sk7b.fsf_-_@gmail.com> (raw)
In-Reply-To: <CFJBET6MWJMX.14P8JUFH811TL@masaki> (bdju@tilde.team's message of "Sun, 07 Nov 2021 00:57:34 -0500")
Hi,
On Sun, 07 Nov 2021 at 00:57, "bdju" <bdju@tilde.team> wrote:
> which I think is where package
> requests are intended to go. At least, that's where I always add things
> I wish were packaged. I know Nixpkgs takes package requests on their
> issue tracker, but I don't typically see such things on the guix mailing
> lists.
>
> https://libreplanet.org/wiki/Group:Guix/Wishlist
Well, first Debbugs has the tag ’wishlist’ [1] and second I am not
convinced that people package software based on wishlist (wherever the
list is). Personally, I package what I use or need.
From my point of view, I would prefer this wishlist about packages
outside the Bug Tracker. I am fine with wishlist for missing features
because they are somehow kind of bug but not for packages – without
looking far, I can think to more than 50 Scientific packages missing,
and I do not see the need to list such packages or how it helps the
project to get them listed – for what my opinion is worth here – and if
such wishlist is useful, then it appears to me simpler to have the
complete list at one unique location (for instance [2]), instead of
filtering first the Bug Tracker to get such wishlist.
1: <https://debbugs.gnu.org/Developer.html#severities>
2: <https://libreplanet.org/wiki/Group:Guix/Wishlist>
Cheers,
simon
prev parent reply other threads:[~2021-11-08 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 23:07 bug#51642: Packaging request: FreeTube Jacob Hrbek
2021-11-07 5:57 ` bdju via Bug reports for GNU Guix
2021-11-08 16:09 ` zimoun [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
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=87ilx2sk7b.fsf_-_@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=51642@debbugs.gnu.org \
--cc=bdju@tilde.team \
--cc=kreyren@rixotstudio.cz \
/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).