unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Brainstorming features for issues.guix.gnu.org
Date: Thu, 26 Mar 2020 10:46:14 +0100	[thread overview]
Message-ID: <CAEwRq=qHJ0GGrBf+pFx4U=Om-GdzZcxGFv_48y+AqyaQwfszTg@mail.gmail.com> (raw)
In-Reply-To: <87mu83xzzr.fsf@elephly.net>

Hello,

On Thu, Mar 26, 2020 at 9:49 AM Ricardo Wurmus <rekado@elephly.net> wrote:
>
> Hello Guix!
>
> I want issues.guix.gnu.org to become more useful for all of us.

Yes, that is a nice goal, I have a few ideas.

> If you do use it: what features do you think are missing?

* I'd like to have a way to reverse the ordering of the results, especially
to get newer issues at the top (I think this should even be the default).

But as you say later, the "oldest first" view is also of interest, so
a classical
ordering combobox could be added

order-by:
- oldest to newest
- newest to oldest
- etc.

* The filtering hints are great (are they an exhaustive list, is there a full
list somewhere). But to ease their use, maybe they could be made
clickable, and a click on one could append it to the search entry, making
their usage from a "select, copy, change focus, paste, click search" into
"click item(s) from the hint list, click search"... This is not high
priority, but
maybe nice to have UI enhancement.

* the "is:Done" filtering shows some Open issues, is that a bug, or a
misunderstanding on my part about what is "Done"

> Personally, I’d wish for a more streamlined workflow to download and
> apply patch sets.  I don’t want to click on each “download” link in the
> web interface.  Instead I would like to run something like
>
>     ./etc/review 12345
>
> which would fetch the patches in issue 12345 and apply them to my
> git worktree.

or to a new branch (maybe you can take ideas from gerrit, not all of
it hopefully ;-))

> I would also like to see neglected issues in the web interface, i.e. a
> list of open issues that haven’t seen any response in a while and that
> haven’t been tagged as awaiting more information from the submitter.
> This should make it easier for us to prevent patches from slipping into
> obscurity, which is a terrible thing to happen especially for new
> contributors.

An indicator (à la Done, Open) could be added to make issues with
patches stand out.

Thanks for the great work BTW
Tchuss

-- 
Vincent Legoll

  parent reply	other threads:[~2020-03-26  9:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  8:49 Brainstorming features for issues.guix.gnu.org Ricardo Wurmus
2020-03-26  9:40 ` Arun Isaac
2020-03-26  9:49   ` Vincent Legoll
2020-03-26  9:46 ` Vincent Legoll [this message]
2020-03-26  9:47 ` Pierre Neidhardt
2020-03-26  9:51   ` Vincent Legoll
2020-03-26 10:29     ` Vincent Legoll
2020-03-26 11:06       ` Ricardo Wurmus
2020-03-26 11:39         ` Pierre Neidhardt
2020-03-27  0:03           ` John Soo
2020-03-26 20:56 ` Christopher Baines
2020-03-27  7:30   ` Pierre Neidhardt
2020-03-27  9:16     ` Christopher Baines
2020-03-27 10:17       ` Pierre Neidhardt
2020-03-27  8:34 ` pinoaffe
2020-03-27  9:42   ` Ricardo Wurmus
2020-03-27  9:59     ` Vincent Legoll
2020-03-27 14:19       ` Ricardo Wurmus
2020-03-27 14:31         ` Vincent Legoll
2020-03-27 18:36     ` pinoaffe
2020-03-28 11:40       ` Vincent Legoll
2020-03-28 22:20         ` Vincent Legoll
2020-03-28 22:20         ` Ricardo Wurmus
2020-03-30 11:07         ` Ricardo Wurmus
2020-03-30 11:33           ` Vincent Legoll
2020-03-29 23:07 ` Björn Höfling
2020-04-01  2:05   ` Ricardo Wurmus
2020-04-06 21:29     ` Björn Höfling
     [not found] ` <87blofpii8.fsf@asu.edu>
2020-03-30  8:07   ` Ricardo Wurmus
2020-03-30 21:48     ` John Soo

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='CAEwRq=qHJ0GGrBf+pFx4U=Om-GdzZcxGFv_48y+AqyaQwfszTg@mail.gmail.com' \
    --to=vincent.legoll@gmail.com \
    --cc=guix-devel@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 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).