From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Arun Isaac <arunisaac@systemreboot.net>,
zimoun <zimon.toutoune@gmail.com>,
Guix Devel <guix-devel@gnu.org>, Kyle Meyer <kyle@kyleam.com>
Subject: Re: Mumi, public-inbox and tools
Date: Sun, 15 May 2022 23:08:15 +0200 [thread overview]
Message-ID: <874k1qcxmo.fsf@gnu.org> (raw)
In-Reply-To: <877d6vspez.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 08 May 2022 23:07:49 +0200")
Hi!
Ricardo Wurmus <rekado@elephly.net> skribis:
> Arun Isaac <arunisaac@systemreboot.net> writes:
>
>> Hi Ludo,
>>
>>> The attached super-early-draft ‘guix review’ script fetches mboxes from
>>> mumi—that part is OK.
>>
>> I like the idea! But, could we put this in mumi instead of guix? That
>> way, other packages that use debbugs/mumi (skribilo comes to mind), can
>> benefit from it as well. Something like
>>
>> $ guix shell mumi -- mumi review 54874
>
> I also think it would be a good fit for mumi.
Yes, there are good arguments for having it in mumi. One of them is
that we can make the server and client-side work hand-in-hand.
An argument in favor of having such a tool in Guix is that we could have
Guix-specific tooling layered on top, such as listing the set of
new/upgraded packages, automatically building them, things like that.
But look: we could have a generic ‘mumi review’ that a hypothetical
‘guix review’ could use as a library and extend.
At any rate, anything will be better than the status quo, so I’m all for
starting with a simple ‘mumi review’!
Perhaps we should organize a hacking session or something eventually?
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-05-15 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 18:10 Mumi, public-inbox and tools zimoun
2022-05-03 17:50 ` Arun Isaac
2022-05-04 8:53 ` zimoun
2022-05-07 22:52 ` Ludovic Courtès
2022-05-08 6:13 ` Arun Isaac
2022-05-08 20:59 ` zimoun
2022-05-08 21:07 ` Ricardo Wurmus
2022-05-15 21:08 ` Ludovic Courtès [this message]
2022-05-08 20:29 ` zimoun
2022-05-09 16:56 ` Maxime Devos
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874k1qcxmo.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.