From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Help wanted for mumi (issues.guix.gnu.org)
Date: Thu, 28 Nov 2019 19:05:46 +0100 [thread overview]
Message-ID: <CAJ3okZ0Ge0EpGWaQ3ZJQ1yAB1Eh21czAKkfTHO1p6XV+aB8fSA@mail.gmail.com> (raw)
In-Reply-To: <87o8ycjv7l.fsf@elephly.net>
Hi Ricardo,
Thank you for initiating this project.
On Sat, 19 Oct 2019 at 23:13, Ricardo Wurmus <rekado@elephly.net> wrote:
> our bug tracker web interface at issues.guix.gnu.org could really
> benefit from a more reliable, faster search.
Yes, it already improves the situation.
I feel grumpy when I use debbugs.gnu.org or even emacs-debbugs. It is
so slow and you need Internet connection: query, wait, query again,
... argh! :-)
Operate on a *local* copy is not easy, IMO. Even if the Gnus guru is
doing [1], it needs some tricks [2] or [3].
[1] https://lists.gnu.org/archive/html/emacs-devel/2019-11/msg00663.html
[2] https://lists.gnu.org/archive/html/emacs-devel/2019-11/msg00666.html
[3] https://lists.gnu.org/archive/html/emacs-devel/2019-11/msg00671.html
> So I decided to switch away from using the Debbugs API and instead
> operate on a *local* copy of all messages that reach Debbugs. Debbugs
> operates on email messages, and luckily it allows us to download these
> original messages. Whenever someone visits an issue page, all related
> messages are downloaded by mumi, so it amasses a sizeable stash of
> emails over time.
>
> Mumi is using a modified version of “mu”, the mail indexer and search
> tool, to continuously index the contents of all messages. (“mu” is
> modified only so that the issue number is indexed alongside the message
> contents.)
This should be nice to be able to work search/query offline.
(Even if I am more from the notmuch side. ;-))
> Unfortunately, that’s as far as I got before life intervened. The next
> step is really close, but getting there requires more contiguous
> segments of time than I can free at the moment. We really only need to
> do the following things next:
>
> 1) keep updating the mu database as new messages are stored
Cron task every hour is not enough?
> 2) using the mu Guile bindings to search messages via mu instead of
> using the slow Debbugs API.
This should be really nice!
One direction I am more interested is a CLI to work offline, say
mumi pull
mumi search
and I am sure that our Emacs magicians could write a nice frontend. ;-)
> Does anyone here have an interest in playing with and improving mumi?
> It’s a very simple code base and it’s very easy to get started.
I am not enough skilled but I am currently using enough the Debbugs to
be bitten. :-)
Cheers,
simon
prev parent reply other threads:[~2019-11-28 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 21:12 Help wanted for mumi (issues.guix.gnu.org) Ricardo Wurmus
2019-10-22 14:04 ` Ludovic Courtès
2019-11-28 18:05 ` zimoun [this message]
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=CAJ3okZ0Ge0EpGWaQ3ZJQ1yAB1Eh21czAKkfTHO1p6XV+aB8fSA@mail.gmail.com \
--to=zimon.toutoune@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).