all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: Ricardo Wurmus <rekado@elephly.net>,
	Mathieu Othacehe <othacehe@gnu.org>,
	guix-devel@gnu.org
Subject: Closing submission incomplete since years?
Date: Mon, 11 Sep 2023 13:23:03 +0200	[thread overview]
Message-ID: <877coxj6nc.fsf@gmail.com> (raw)
In-Reply-To: <871qf7xadm.fsf@gmail.com>

Hi Maxim,

For reference [1].

On Sat, 09 Sep 2023 at 18:14, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

> On a related note sometimes we have WIP kind of work that stays on our
> tracker with deeper questions / problems to solve, and I don't think
> it's fair for our reviewers to have these linger on for years on the
> tracker (they take a lot of time to get familiar with, and would then
> require quit more investment to be completed, sometimes with the
> original submitter no longer active in the discussion) -- I think for
> these situations it's fair to close it.  An interested person can
> hopefully find these in the archives and resume work on it if they are
> so inclined.

I am more or less agree.  Especially for keeping the tracker
healthy. However, I am missing how “an interested person can hopefully
find these in the archives and resume work on it if they are so
inclined.“

Maybe we could have another usertags for tagging this case or another
tag.  Else, it appears to me unpractical to find these in the archives.
Well, I personally do not even know how or where to start for finding
these.

Exercise: find the patches that someone pinged their status from the 10
Years of Guix event and another person then closed. :-)

    Found it?  If no,

    Hint 1: someone was me. ;-)

    Found it?  If no,

    Hint 2: another person was you. ;-)

    Found it?  If no,

    Hint 3: it was about elasticsearch.

    https://issues.guix.gnu.org/search?query=elasticsearch

    Found it?  If no,

    Hint 4: tag ’moreinfo’.

Well, if just marked as done, then it appears to me unpractical to find
these in the archives.

Cheers,
simon


1: [bug#31444] 'guix health': a tool to report vulnerable packages
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Sat, 09 Sep 2023 18:14:13 -0400
id:871qf7xadm.fsf@gmail.com
https://yhetil.org/guix/871qf7xadm.fsf@gmail.com
https://issues.guix.gnu.org/msgid/871qf7xadm.fsf@gmail.com


  reply	other threads:[~2023-09-11 11:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 22:15 [bug#31444] 'guix health': a tool to report vulnerable packages Ludovic Courtès
2018-05-14  8:06 ` Martin Castillo
2018-05-14  9:07   ` Ludovic Courtès
2018-05-14 16:49 ` Nils Gillmann
2018-05-15  7:24   ` Ludovic Courtès
2020-09-18 22:43 ` zimoun
2020-09-25 16:34   ` Ludovic Courtès
2023-07-21 16:44   ` Maxim Cournoyer
2023-09-08 16:25     ` Ludovic Courtès
2023-09-09 22:14       ` Maxim Cournoyer
2023-09-11 11:23         ` Simon Tournier [this message]
2023-09-11 17:54           ` Closing submission incomplete since years? Maxim Cournoyer
2023-09-11 18:17             ` Simon Tournier
2023-09-11 20:43               ` Maxim Cournoyer
2023-09-13 19:58         ` [bug#31444] 'guix health': a tool to report vulnerable packages 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

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

  git send-email \
    --in-reply-to=877coxj6nc.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=othacehe@gnu.org \
    --cc=rekado@elephly.net \
    /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.