From: Jack Hill <jackhill@jackhill.us>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Mumi now uses raw emails and Mu
Date: Sun, 21 Jul 2019 20:41:02 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1907212035220.9756@marsh.hcoop.net> (raw)
In-Reply-To: <87ef2jdtuc.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 2130 bytes --]
Ricardo,
On Sun, 21 Jul 2019, Ricardo Wurmus wrote:
> Hey there,
>
> I just wanted to let y’all know that Mumi at issues.guix.gnu.org now
> stores raw emails from Debbugs instead of fetching them through the
> Debbugs SOAP service. This means that messages are no longer truncated,
> which is what happened to some multipart messages in the past.
>
> While I don’t think Mu is directly suitable for Mumi, I added Mu as a
> dependency for now, and I’m indexing all emails in regular intervals.
> This can be used to speed up the message search. If you want to
> implement this, I’d be happy to receive patches!
>
> The code for Mumi can be found here:
>
> https://git.elephly.net/software/mumi.git
>
> Going forward I think it would be better to use Xapian directly. Then
> we could store more relevant information in the database, such as the
> Debbugs bug number to which a certain message relates. I would like to
> be able to almost instantaneously answer these questions:
>
> * which of our issues have seemingly been forgotten?
> * which have been ignored?
> * which issues involve a certain person?
> * what issues match this text query?
>
> Since we’re interested in issues (not individual messages) these
> questions cannot quickly be answered with Mu. To compute the issue
> number from a message requires parsing it and I’d much rather do this at
> index time.
>
> I guess we could even just fork Mu and make it store additional
> information in its database.
Very cool!
> If you’d like to take part in this effort to make Mumi more useful to
> all of us, please reply to this message.
I'd like to try to take part. I'm still very much a novice
programmer/Guiler, so I might require a fair amount of hand-holding, but if
others are working on it too, that should be fine.
With the currently deployed mumi, it looks like my mails in
https://issues.guix.gnu.org/issue/36207 are still mangling the '’' after
Ludo, but in a different way than before. Perhaps this will be a good
place for me to start trying to debug and learning the mail processing
code paths in mumi.
All the best,
Jack
next prev parent reply other threads:[~2019-07-22 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 20:18 Mumi now uses raw emails and Mu Ricardo Wurmus
2019-07-22 0:41 ` Jack Hill [this message]
2019-07-22 9:53 ` Ricardo Wurmus
2019-07-23 11:01 ` Ricardo Wurmus
2019-07-23 13:49 ` Ricardo Wurmus
2019-07-24 17:07 ` Arun Isaac
2019-07-24 17:45 ` Ricardo Wurmus
2019-07-24 18:46 ` Arun Isaac
2019-07-22 17:54 ` Arun Isaac
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=alpine.DEB.2.20.1907212035220.9756@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--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).