all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Brainstorming features for issues.guix.gnu.org
Date: Mon, 30 Mar 2020 01:07:51 +0200	[thread overview]
Message-ID: <20200330010751.529006e2@alma-ubu> (raw)
In-Reply-To: <87mu83xzzr.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 3702 bytes --]

Hi Ricardo,

On Thu, 26 Mar 2020 09:49:12 +0100
Ricardo Wurmus <rekado@elephly.net> wrote:

> Hello Guix!
> 
> I want issues.guix.gnu.org to become more useful for all of us.  It’s
> easy to get lost in a deluge of bug reports and patch submissions, so
> our tools should allow us to stay afloat.
> 
> Do you use issues.guix.gnu.org?  If you aren’t: what workflow do you
> have to review patch submissions?

I prefer my mailbox, with sometimes looking through the Debbugs web
page. I have to admit, I'm not using it and I think it is not
intuitive. It is as colorful as the bug trackers at github.com, but not
as useable as them.

Here are my suggestions for mumi, some of them already said by others:

* First of all, I find this mixture very confusing: Is this about bugs
or is this about patches? I really don't know, and the start page is
ambigious about it too: 

"Guix /patch/ tracker
This is a web frontend to the Guix /issue/ trackers.
/Issues/ of interest
Priority /bugs/"

I would prefer two trackers: 
https://issues.guix.gnu.org/ for bugs and
httsp://patches.guix.gnu.org/ for patches.

* Is it intentionally that there still is a http site? I would have
expected a redirect onto https.

* http[s]://issues.guix.info/ is also still alive. Shouldn't it redirect
to http[s]://issues.guix.gnu.org/?

* If you search for something, you get away from the homepage and
tips are missing. There should be a "help/tooltip" button near the
search input that explains the query language.

* If you enter a query, that query should be kept in the input field.
Currently, it is discarded. That would make it more easy to update your
query.

* I would expect the home page to present the newest issues first, and
only open ones.

* It is not clear to me how long a closed issue is still visible on the
home-page. Is it still an "Issue of interest" if it is closed? 

* Sorting issues by columns would be cool.

* Mumi has no paging: It only presents one page of issues, but it
doesn't say how many are there in total nor does it page through all
other pages of issues.

* That means: If I search only for open issues, I get one page ranging
from 2013 until 2017, nothing newer:
https://issues.guix.gnu.org/search?query=is%3Aopen
This is unsatisfying.

* In that list, it is not clear what a red/orange colored bug-number
means: A tool-tip would be nice.

* As others mentioned, linking and explaining the tags (like easy)
is missing.

* A long desired feature is having general tags. It took me a very long
time until I realized that Debbugs allows user-tags. What about using a
common email address like "issues AT guix.gnu.org" and add user-tags
for that address, like "python", "core-updates", "release-1.1.x", etc.

* I still don't see that all bugs and patches from the mailing list are
part of the mumi issues list?

* The HTML could be responsive.

* The query syntax examples are only on the home page. Please repeat
them also on the help page.

* Either I don't understand the "date:<start>..<end>" semantics or it
is broken. The range yesterday..today lists no issues after 2015. Not
the "yesterday" I expected...:

https://issues.guix.gnu.org/search?query=date%3Ayesterday..today

With numbers, it gets even more strange:
https://issues.guix.gnu.org/search?query=date%3A2020-03-29..2020-03-30
--> Nothing found.

Some more, but why are these selected?:
https://issues.guix.gnu.org/search?query=date%3A2020-03-29..2020-03-30

* Mdate does not find anything?
https://issues.guix.gnu.org/search?query=mdate%3A2w..12h

Despite all the critics, thanks for caring and improving mumi.

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2020-03-29 23:08 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=20200330010751.529006e2@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --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 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.