https://issues.guix.info

https://issues.guix.info

[Ricardo Wurmus]

Hello Guix!

Some of you know this already, but I think it’s time for a proper
announcement here.  I made a little something:

    https://issues.guix.info

It tries to provide a friendlier web interface to Debbugs, the software
we use for tracking bugs that are sent to bug-guix@gnu.org and for
tracking patch submissions at guix-patches@gnu.org.  The software that
provides this web interface is called “mumi” (for reasons that are not
important).

Behind the scenes it uses guile-debbugs, a simple Guile client for the
SOAP service that Debbugs instances provide.

It isn’t very snappy, because it has to make requests to Debbugs, wait
for an answer, parse the XML, and then make some more requests.  It
tries to cache these SOAP requests for a while, but it’s rather
primitive.

The search box accepts issue numbers (for *any* bug on the GNU instance
of Debbugs), but it also supports a few special queries, such as

    is:open / is:pending –> only open issues
    is:done / is:closed  –> only completed issues
    title:foo -> issues containing “foo” in the title
    author:rekado –> issues that “rekado” contributed to

Other supported terms are “severity”, “tag”, and “submitter”, but not
all of them really work as they should, partly because of bugs in mumi,
partly because of limitations in Debbugs.

I haven’t yet thought about how to serve this reliably, so for the time
being it’s just a single Guile web server behind a proxy.

I hope that eventually we could offer extra features for people who are
members of the Guix project on Savannah, such as sending control
messages from within the web interface.  I’d also like to eventually
allow people to comment on issues and create new ones right from the web
interface, but that’s a little tricky to get right.

The code is available here:

    https://git.elephly.net/software/mumi.git

I would be delighted if any of you would like to help make mumi better.
Here are a couple of things that come to mind that could need some work:

- proper handling of attachments in multipart messages.  If a multipart
  message contains an attachment, mumi tries to display it like any
  other multipart type.

- processing of mail body.  Mumi goes through the mail body line by line
  and wraps matching lines in extra styles.  It would be nice if we
  could put all quotes in a single div and allow the visitor to toggle
  display of quoted lines, for example.  (On the other hand, maybe
  people will learn to avoid quoting irrelevant parts of other messages
  when they see how bad it looks on the web interface… :))

- make the search bar look good

- turn URLs into clickable links

- turn commit hashes into links to the commit on Savannah

Anyway, hope you’ll find this useful!

--
Ricardo

Re: https://issues.guix.info

[Amin Bandali]

Hi Ricardo,

> Some of you know this already, but I think it’s time for a proper
> announcement here.  I made a little something:
>
>     https://issues.guix.info

Awesome, it looks pretty neat!

> The search box accepts issue numbers (for *any* bug on the GNU instance
> of Debbugs), but it also supports a few special queries, such as
>
>     is:open / is:pending –> only open issues
>     is:done / is:closed  –> only completed issues
>     title:foo -> issues containing “foo” in the title
>     author:rekado –> issues that “rekado” contributed to
>
> Other supported terms are “severity”, “tag”, and “submitter”, but not
> all of them really work as they should, partly because of bugs in mumi,
> partly because of limitations in Debbugs.

I think It would be neat to present these to the user, right on
the website itself.

> - make the search bar look good

Adding class="form-control" would be a nice first step.  Also,
it'd probably be a good idea to wrap the <form> in a div with
class="row", and use bootstrap grids to make the search bar and
the button smaller (by putting them in a column), and display the
above information about the search syntax in another column to
the right of the form.

  -amin

Re: https://issues.guix.info

[Ricardo Wurmus]

Hi Amin,

>> The search box accepts issue numbers (for *any* bug on the GNU instance
>> of Debbugs), but it also supports a few special queries, such as
>>
>>     is:open / is:pending –> only open issues
>>     is:done / is:closed  –> only completed issues
>>     title:foo -> issues containing “foo” in the title
>>     author:rekado –> issues that “rekado” contributed to
>>
>> Other supported terms are “severity”, “tag”, and “submitter”, but not
>> all of them really work as they should, partly because of bugs in mumi,
>> partly because of limitations in Debbugs.
>
> I think It would be neat to present these to the user, right on
> the website itself.

I agree.  I don’t know how to present these things nicely, but I’ll play
around with this.

BTW: “submitter:who” should also work now.  Like “is:…” it’s a rather
expensive query because the result set from Debbugs has to be filtered
locally.

>> - make the search bar look good
>
> Adding class="form-control" would be a nice first step.  Also,
> it'd probably be a good idea to wrap the <form> in a div with
> class="row", and use bootstrap grids to make the search bar and
> the button smaller (by putting them in a column), and display the
> above information about the search syntax in another column to
> the right of the form.

Thanks for the suggestions.  I read the bootstrap CSS docs and came up
with something that I hope is an improvement.

--
Ricardo

Re: https://issues.guix.info

[Clément Lassieur]

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi Amin,
>
>>> The search box accepts issue numbers (for *any* bug on the GNU instance
>>> of Debbugs), but it also supports a few special queries, such as
>>>
>>>     is:open / is:pending –> only open issues
>>>     is:done / is:closed  –> only completed issues
>>>     title:foo -> issues containing “foo” in the title
>>>     author:rekado –> issues that “rekado” contributed to
>>>
>>> Other supported terms are “severity”, “tag”, and “submitter”, but not
>>> all of them really work as they should, partly because of bugs in mumi,
>>> partly because of limitations in Debbugs.
>>
>> I think It would be neat to present these to the user, right on
>> the website itself.
>
> I agree.  I don’t know how to present these things nicely, but I’ll play
> around with this.
>
> BTW: “submitter:who” should also work now.  Like “is:…” it’s a rather
> expensive query because the result set from Debbugs has to be filtered
> locally.

Nice :-)  Thank you.

>>> - make the search bar look good
>>
>> Adding class="form-control" would be a nice first step.  Also,
>> it'd probably be a good idea to wrap the <form> in a div with
>> class="row", and use bootstrap grids to make the search bar and
>> the button smaller (by putting them in a column), and display the
>> above information about the search syntax in another column to
>> the right of the form.
>
> Thanks for the suggestions.  I read the bootstrap CSS docs and came up
> with something that I hope is an improvement.

Re: https://issues.guix.info

[Amin Bandali]

Hi Ricardo,

> I agree.  I don’t know how to present these things nicely, but I’ll play
> around with this.
>
> BTW: “submitter:who” should also work now.  Like “is:…” it’s a rather
> expensive query because the result set from Debbugs has to be filtered
> locally.

Cool, thanks!

>>> - make the search bar look good
>>
>> Adding class="form-control" would be a nice first step.  Also,
>> it'd probably be a good idea to wrap the <form> in a div with
>> class="row", and use bootstrap grids to make the search bar and
>> the button smaller (by putting them in a column), and display the
>> above information about the search syntax in another column to
>> the right of the form.
>
> Thanks for the suggestions.  I read the bootstrap CSS docs and came up
> with something that I hope is an improvement.

Thanks, that does looks better!  I'm not much of a UI person
either, but I'll see if I can manage to make a nice presentation
of the search syntax on the front page and will send a patch if
it turns out looking ok.

  -amin

Re: https://issues.guix.info

[Pierre Neidhardt]

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

Looks great, thanks for the hard work!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: https://issues.guix.info

[Hartmut Goebel]

Am 01.09.2018 um 22:26 schrieb Ricardo Wurmus:
> I hope that eventually we could offer extra features for people who are
> members of the Guix project on Savannah, such as sending control
> messages from within the web interface.  I’d also like to eventually
> allow people to comment on issues and create new ones right from the web
> interface, but that’s a little tricky to get right.

This would be really, really great! Interacting with debbugs is a pain
for occasional users.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

Re: https://issues.guix.info

[Ricardo Wurmus]

Hi Amin,

> […] I'll see if I can manage to make a nice presentation
> of the search syntax on the front page and will send a patch if
> it turns out looking ok.

I went ahead and documented the supported query terms on
https://issues.guix.info/help and linked to it from the start page.

I also added support for “date:” (submission date) and “mdate:” (message
date) filters, which should look familiar to users of mu/mu4e.

--
Ricardo

Re: https://issues.guix.info

[Amin Bandali]

Hi Ricardo,

> I went ahead and documented the supported query terms on
> https://issues.guix.info/help and linked to it from the start page.
>
> I also added support for “date:” (submission date) and “mdate:” (message
> date) filters, which should look familiar to users of mu/mu4e.

Wonderful, looks great!  Thanks again for all your work.

  -amin

Re: https://issues.guix.info

[Arun Isaac]

> Some of you know this already, but I think it’s time for a proper
> announcement here.  I made a little something:
>
>     https://issues.guix.info
>
> It tries to provide a friendlier web interface to Debbugs, the software
> we use for tracking bugs that are sent to bug-guix@gnu.org and for
> tracking patch submissions at guix-patches@gnu.org.

Thanks for sharing! This is so much better than the old debbugs
interface! :-)

> - proper handling of attachments in multipart messages.  If a multipart
>   message contains an attachment, mumi tries to display it like any
>   other multipart type.

Is this about allowing attached patches to be downloaded? Is it
currently possible to download patches using mumi? It would be nice to
use mumi for my entire workflow, and not have to fallback to the old
debbugs web interface.

Also, is there any value in having a pure guile email parser instead of
using bindings to mailutils? I attempted a similar project, and for some
reason, I ended up writing an email parser from scratch using (ice-9
peg). But, now that I see how you have used mailutils bindings, I am
unsure if writing an email parser from scratch was wise. However, if you
think it is worthwhile, I can contribute that code to mumi.

Re: https://issues.guix.info

[Ricardo Wurmus]

Hi Arun,

>> - proper handling of attachments in multipart messages.  If a multipart
>>   message contains an attachment, mumi tries to display it like any
>>   other multipart type.
>
> Is this about allowing attached patches to be downloaded? Is it
> currently possible to download patches using mumi? It would be nice to
> use mumi for my entire workflow, and not have to fallback to the old
> debbugs web interface.

This is now possible.  I currently only decode attachments that are in
base64 and quoted printable formats; all others are sent as is.

> Also, is there any value in having a pure guile email parser instead of
> using bindings to mailutils? I attempted a similar project, and for some
> reason, I ended up writing an email parser from scratch using (ice-9
> peg). But, now that I see how you have used mailutils bindings, I am
> unsure if writing an email parser from scratch was wise. However, if you
> think it is worthwhile, I can contribute that code to mumi.

I’m not using a lot of mailutils.  I use the following procedures:

- mu-address-get-email
- mu-address-get-personal (problem: swallows non-ASCII characters)
- mu-header-decode
- mu-decoder-port

Of all these only “mu-decoder-port” would be non-trivial to implement.
It’s used to decode strings that are encoded as “quoted-printable”.  It
wouldn’t be too difficult to implement in pure Guile – I just wanted to
save time.

I’d be happy if your work on email parsers could end up in mumi and
replace some of my own poor quality code :)

--
Ricardo

Re: https://issues.guix.info

[Ludovic Courtès]

Hello!

Ricardo Wurmus <rekado@elephly.net> skribis:

> Some of you know this already, but I think it’s time for a proper
> announcement here.  I made a little something:
>
>     https://issues.guix.info

One word: awesome!

Hopefully contributors-to-be will be less scared than with the old
interface, and… hopefully more of the current contributors will feel
like reviewing patches too!  :-)

Ludo’.

Re: https://issues.guix.info

[Arun Isaac]

>> Is this about allowing attached patches to be downloaded? Is it
>> currently possible to download patches using mumi? It would be nice to
>> use mumi for my entire workflow, and not have to fallback to the old
>> debbugs web interface.
>
> This is now possible.  I currently only decode attachments that are in
> base64 and quoted printable formats; all others are sent as is.

How is it possible to download patches (or their mboxes) from the mumi
interface? I didn't see it anywhere in the web interface. Did I miss
something?

> I’d be happy if your work on email parsers could end up in mumi and
> replace some of my own poor quality code :)

Sure, I'll contribute to mumi. :-) Where do I send patches? It would be
nice to use debbugs (say, mumi@debbugs.gnu.org) to track the patches, so
that we can dogfood with mumi.

Re: https://issues.guix.info

[Ricardo Wurmus]

Hi Arun,

>>> Is this about allowing attached patches to be downloaded? Is it
>>> currently possible to download patches using mumi? It would be nice to
>>> use mumi for my entire workflow, and not have to fallback to the old
>>> debbugs web interface.
>>
>> This is now possible.  I currently only decode attachments that are in
>> base64 and quoted printable formats; all others are sent as is.
>
> How is it possible to download patches (or their mboxes) from the mumi
> interface? I didn't see it anywhere in the web interface. Did I miss
> something?

I haven’t yet added a way to download attached patches (they are only
displayed inline).  At the moment you can only download attachments that
cannot be displayed.  I’ll try to find time to change this today.

>> I’d be happy if your work on email parsers could end up in mumi and
>> replace some of my own poor quality code :)
>
> Sure, I'll contribute to mumi. :-) Where do I send patches? It would be
> nice to use debbugs (say, mumi@debbugs.gnu.org) to track the patches, so
> that we can dogfood with mumi.

I think that only GNU packages may use debbugs.gnu.org.  Mumi is not a
GNU package (yet?).

--
Ricardo

Re: https://issues.guix.info

[Arun Isaac]

> I haven’t yet added a way to download attached patches (they are only
> displayed inline).  At the moment you can only download attachments that
> cannot be displayed.  I’ll try to find time to change this today.

Sure, thanks!

> I think that only GNU packages may use debbugs.gnu.org.  Mumi is not a
> GNU package (yet?).

According to https://debbugs.gnu.org/Using.html , even "Savannah hosted
non-GNU free software" can use debbugs.

Re: https://issues.guix.info

[Ricardo Wurmus]

Arun Isaac <arunisaac@systemreboot.net> writes:

>> I haven’t yet added a way to download attached patches (they are only
>> displayed inline).  At the moment you can only download attachments that
>> cannot be displayed.  I’ll try to find time to change this today.
>
> Sure, thanks!
>
>> I think that only GNU packages may use debbugs.gnu.org.  Mumi is not a
>> GNU package (yet?).
>
> According to https://debbugs.gnu.org/Using.html , even "Savannah hosted
> non-GNU free software" can use debbugs.

Oh, I suppose I should apply for having Mumi hosted on Savannah then.
Thanks for checking!

-- 
Ricardo

Re: https://issues.guix.info

[Gábor Boskovits]

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

Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2018. szept. 5.,
Sze, 10:56):

>
> Arun Isaac <arunisaac@systemreboot.net> writes:
>
> >> I haven’t yet added a way to download attached patches (they are only
> >> displayed inline).  At the moment you can only download attachments that
> >> cannot be displayed.  I’ll try to find time to change this today.
> >
> > Sure, thanks!
> >
> >> I think that only GNU packages may use debbugs.gnu.org.  Mumi is not a
> >> GNU package (yet?).
> >
> > According to https://debbugs.gnu.org/Using.html , even "Savannah hosted
> > non-GNU free software" can use debbugs.
>
> Oh, I suppose I should apply for having Mumi hosted on Savannah then.
> Thanks for checking!
>
> --
> Ricardo
>
>  Hello Ricardo,
I'm now playing with this. It's really nice.

[-- Attachment #2: Type: text/html, Size: 1415 bytes --]

Re: https://issues.guix.info

[Pierre Neidhardt]

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

Just noticed something: on http://issues.guix.info/help, the "submitter" example
suggests "author:ludo" instead of "submitter:ludo" :)

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]