From: swedebugia <swedebugia@riseup.net>
To: Alex Vong <alexvong1995@gmail.com>,
Laura Lazzati <laura.lazzati.15@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: New topic: asking for help
Date: Sun, 17 Feb 2019 09:26:09 +0100 [thread overview]
Message-ID: <27E9A479-55F4-4D52-819B-03BAD937A969@riseup.net> (raw)
In-Reply-To: <877edzlfvk.fsf@gmail.com>
Alex Vong <alexvong1995@gmail.com> skrev: (16 februari 2019 19:58:39 CET)
>Laura Lazzati <laura.lazzati.15@gmail.com> writes:
>
>
>>> We might also propose the mumi as the primary issue tracking
>>> interface, and mention debbugs in
>>> case more advanced stuff is needed. No strong opinion here.
I agree.
Although an important missing piece in both debbugs and mumi is the ability to report a bug directly on the webpage.
They are both essentially just listings of bugs.
>> Already mentioned my idea about debbugs. Don't know what mumi is :/
>>
>I don't know what's mumi either. But I think there's a (relatively new)
>web frontend for debbugs: https://issues.guix.info/
Mumi is the debbugs frontend code serving that adress. It is written by Ricardo but very little advertised it seems.
The code is linked in the bottom of the page.
Ricardo maybe you could submit mumi to the list if guile programs on gnu.org to help people find it? And perhaps add the name mumi to issues.guix.info
--
Sent from my k-9 mail for Android.
prev parent reply other threads:[~2019-02-17 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 14:29 New topic: asking for help Laura Lazzati
2019-02-11 15:38 ` znavko
2019-02-11 15:49 ` Laura Lazzati
2019-02-13 3:02 ` Laura Lazzati
2019-02-13 9:06 ` Björn Höfling
2019-02-14 14:55 ` Gábor Boskovits
2019-02-14 19:37 ` Laura Lazzati
2019-02-16 18:58 ` Alex Vong
2019-02-17 8:26 ` swedebugia [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=27E9A479-55F4-4D52-819B-03BAD937A969@riseup.net \
--to=swedebugia@riseup.net \
--cc=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=laura.lazzati.15@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 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).