From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Mumi now uses raw emails and Mu Date: Sun, 21 Jul 2019 22:18:51 +0200 Message-ID: <87ef2jdtuc.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:40531) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hpIIQ-00051x-9d for guix-devel@gnu.org; Sun, 21 Jul 2019 16:19:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hpIIP-0007yV-5Y for guix-devel@gnu.org; Sun, 21 Jul 2019 16:19:02 -0400 Received: from sender4-of-o53.zoho.com ([136.143.188.53]:21395) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hpIIO-0007xV-Nl for guix-devel@gnu.org; Sun, 21 Jul 2019 16:19:01 -0400 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: guix-devel@gnu.org Hey there, I just wanted to let y=E2=80=99all 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=E2=80=99t think Mu is directly suitable for Mumi, I added Mu as= a dependency for now, and I=E2=80=99m indexing all emails in regular interval= s. This can be used to speed up the message search. If you want to implement this, I=E2=80=99d 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=E2=80=99re 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=E2=80=99d much rather do th= is at index time. I guess we could even just fork Mu and make it store additional information in its database. If you=E2=80=99d like to take part in this effort to make Mumi more useful = to all of us, please reply to this message. -- Ricardo