From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jack Hill Subject: Re: Mumi now uses raw emails and Mu Date: Sun, 21 Jul 2019 20:41:02 -0400 (EDT) Message-ID: References: <87ef2jdtuc.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="925712948-305291828-1563756063=:9756" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:53716) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hpMO1-0005ag-Sd for guix-devel@gnu.org; Sun, 21 Jul 2019 20:41:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hpMO0-0000Jf-Nm for guix-devel@gnu.org; Sun, 21 Jul 2019 20:41:05 -0400 Received: from minsky.hcoop.net ([104.248.1.95]:56688) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hpMO0-0000JL-Jt for guix-devel@gnu.org; Sun, 21 Jul 2019 20:41:04 -0400 In-Reply-To: <87ef2jdtuc.fsf@elephly.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel@gnu.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --925712948-305291828-1563756063=:9756 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT 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 --925712948-305291828-1563756063=:9756--