all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Jacob Hrbek <kreyren@rixotstudio.cz>
Cc: 54064@debbugs.gnu.org
Subject: bug#54064: Packaging request: Ultimaker Cura
Date: Mon, 07 Mar 2022 17:08:58 +0100	[thread overview]
Message-ID: <874k49bv8l.fsf@gmail.com> (raw)
In-Reply-To: <0c1d5591-ec12-6c34-0c11-5273f6369e08@rixotstudio.cz> (Jacob Hrbek's message of "Sat, 05 Mar 2022 07:11:16 +0000")

Hi,

On sam., 05 mars 2022 at 07:11, Jacob Hrbek <kreyren@rixotstudio.cz> wrote:

> Please mark as wishlist same as https://issues.guix.gnu.org/51643#3 so
> that the reasoning is available to the users and can be worked on in a
> controlled manner.

I tagged it as wishlist but I am not convinced that package request
should be in the bug tracker.  Especially complex packages.  The backlog
is already long enough and many packages could be requested.

I think wishlist tag should be reserved for, both in the same time:
missing core features *and* entry point for newcomers.  Therefore,
tag wishlist on https://issues.guix.gnu.org/51643 appears to me a
mistake.  I am closing for the same reason Maxim explained.

Package requests must be outside the bug tracker to ease the work on it.
From my point of view, for instance, something like [1] seems a better
fit for package request that can be worked on in a controlled maner.

1: <https://todo.sr.ht/~whereiseveryone>


Cheers,
simon




  reply	other threads:[~2022-03-07 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19 14:27 bug#54064: Packaging request: Ultimaker Cura Jacob Hrbek
2022-02-22 18:23 ` Bengt Richter
2022-02-22 18:32   ` Jacob Hrbek
2022-02-22 21:44     ` Bengt Richter
2022-03-02 13:35 ` Maxim Cournoyer
2022-03-02 19:02   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-03-05  7:11 ` Jacob Hrbek
2022-03-07 16:08   ` zimoun [this message]
2022-03-05  7:11 ` Jacob Hrbek

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=874k49bv8l.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=54064@debbugs.gnu.org \
    --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 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.