From: "Jonathan McHugh" <indieterminacy@libre.brussels>
To: "zimoun" <zimon.toutoune@gmail.com>,
"Arun Isaac" <arunisaac@systemreboot.net>,
"Ricardo Wurmus" <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Incentives for review
Date: Fri, 22 Oct 2021 08:37:03 +0000 [thread overview]
Message-ID: <2bfcad97b143c02bae05f04d26c0512d@libre.brussels> (raw)
In-Reply-To: <86mtn1zevq.fsf@gmail.com>
Hi Simon,
I had noticed Woof and it does seem interesting and worthy of analysis.
I should point out that the Ogmode community have the same problems and complaints regarding the governance and efficacy of issue/bug tracking. This is a socio-technological problem, which hopefully has solutions which can cut across communities.
Its also worth citing some of the suggestions in this devel-guix thread concerning tooling or options:
https://lists.nongnu.org/archive/html/guix-devel/2021-08/msg00042.html
Suggestions included:
Bugs Everywhere https://bugs-everywhere.readthedocs.io/en/latest/
Git-Issue https://github.com/dspinellis/git-issue
Fossil https://fossil-scm.org/home/doc/trunk/www/bugtheory.wiki
IMHO, I though Bugs Everywhere was the most interesting, though it may have experienced some bitrot.
More recently I have been deliberating on the idea of using a MUD type tool as an interface for issue and bugtracking.
It seems that Powwow would be capable of using scripts in an interesting way.
https://www.hoopajoo.net/static/powwow-mirror/powwow/index.html
This interests me:
```
Powwow also implements the MUME remote editing protocol, which enables you to edit texts on the MUD using your own favourite editor, several texts at once if you have a windowing terminal.
```
Im also investigating Tintin++
https://tintin.mudhalla.net/
I personally would find it interesting to create 'conversational models' for issue/bug tracking in such an environment, backed by:
* interoperability with computing environments
* interpreting infrastructure
* projectile style configurations
* supplementary protocols
* light writing formats
* configs and bindings to provide workflow
A MUD type inferface is perhaps only a speculative concern but Id be interested in hearing -/+ opinions and interest levels, if not practical suggestions.
As some may be aware, I have been considering the issue/bug tracking topic from the perspective of the Gemini protocol (though now with a wider scale than just comsidering Debbugs).
That is proceeding, though I was impeeded by some physical setbacks (status:resolved) and completing wider responsibilities. Now back in the flow, I will provide updates once my projects start perculating.
@Arun please mail me privately regarding your plans, Id like to hear about where they may be intersections.
@Christine I look forward to replying to your (private) mail in due course - apoligies for radio silence. If you have suggestions regarding how Guix can go MUD Im sure we'd all be interested!
Kind regards,
====================
Jonathan McHugh
indieterminacy@libre.brussels
October 22, 2021 9:44 AM, "zimoun" <zimon.toutoune@gmail.com> wrote:
> Hi Arun,
>
> On Thu, 21 Oct 2021 at 23:51, Arun Isaac <arunisaac@systemreboot.net> wrote:
>
>> The way I see it, we are outgrowing general purpose bug trackers like
>> debbugs. We need a special purpose bug tracker specifically for Guix
>> with its special requirements. We are a big enough community for this to
>> be important.
>
> For an example of such «special purpose bug tracker», give a look at
> what Org-mode people do:
>
> <https://updates.orgmode.org>
>
> Well, it is currently down. It looks like that:
>
> <https://web.archive.org/web/20210228064154/https://updates.orgmode.org>
>
> The code running it is Woof (lisp based):
>
> <https://github.com/bzg/woof>
>
> Maybe there are some ideas to borrow. :-)
>
> Cheers,
> simon
next prev parent reply other threads:[~2021-10-22 8:37 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 18:54 Tricking peer review Ludovic Courtès
2021-10-15 22:03 ` Liliana Marie Prikler
2021-10-15 22:28 ` Ryan Prior
2021-10-15 22:45 ` Liliana Marie Prikler
2021-10-15 22:59 ` Ryan Prior
2021-10-18 7:40 ` Ludovic Courtès
2021-10-18 19:56 ` Ryan Prior
2021-10-19 8:39 ` zimoun
2021-10-20 23:03 ` Leo Famulari
2021-10-21 8:14 ` zimoun
2021-10-15 23:13 ` Thiago Jung Bauermann
2021-10-18 7:47 ` Ludovic Courtès
2021-10-18 7:34 ` Ludovic Courtès
2021-10-19 8:36 ` zimoun
2021-10-19 12:56 ` Ludovic Courtès
2021-10-19 14:22 ` zimoun
2021-10-19 15:41 ` Incentives for review Ludovic Courtès
2021-10-19 16:56 ` zimoun
2021-10-19 19:14 ` Ricardo Wurmus
2021-10-19 19:34 ` Christine Lemmer-Webber
2021-10-19 19:50 ` Joshua Branson
2021-10-21 20:03 ` Ludovic Courtès
2021-10-20 21:37 ` Thiago Jung Bauermann
2021-10-21 13:38 ` Artem Chernyak
2021-10-22 20:03 ` Thiago Jung Bauermann
2021-10-23 1:43 ` Kyle Meyer
2021-10-23 3:42 ` Thiago Jung Bauermann
2021-10-23 7:37 ` zimoun
2021-10-23 16:18 ` public-inbox/elfeed -> Maildir bridge (was: Incentives for review) Kyle Meyer
2021-10-24 12:18 ` Jonathan McHugh
2021-10-21 16:06 ` Incentives for review Ricardo Wurmus
2021-10-21 16:32 ` zimoun
2021-10-22 20:06 ` Thiago Jung Bauermann
2021-10-21 15:07 ` Katherine Cox-Buday
2021-10-21 16:10 ` Ricardo Wurmus
2021-10-21 17:52 ` Katherine Cox-Buday
2021-10-21 18:21 ` Arun Isaac
2021-10-21 19:58 ` Ludovic Courtès
2021-10-21 21:42 ` Ricardo Wurmus
2021-10-22 10:48 ` Arun Isaac
2021-10-22 11:21 ` zimoun
2021-10-23 6:09 ` Arun Isaac
2021-10-22 10:56 ` Jonathan McHugh
2021-10-22 7:40 ` zimoun
2021-10-22 11:09 ` Arun Isaac
2021-10-22 8:37 ` Jonathan McHugh [this message]
2021-10-22 9:15 ` zimoun
2021-10-22 10:40 ` Jonathan McHugh
2021-10-22 11:32 ` zimoun
2021-10-21 21:18 ` Jonathan McHugh
2021-10-22 10:44 ` Arun Isaac
2021-10-22 11:06 ` Jonathan McHugh
2021-10-21 21:22 ` zimoun
2021-10-28 14:57 ` Katherine Cox-Buday
2021-10-21 17:51 ` Vagrant Cascadian
2021-10-24 11:47 ` Efraim Flashner
2021-10-20 8:22 ` Tricking peer review Giovanni Biscuolo
2021-10-20 9:10 ` zimoun
2021-10-20 8:29 ` patches for new packages proper workflow (Re: Tricking peer review) Giovanni Biscuolo
2021-10-20 23:09 ` Tricking peer review Leo Famulari
2021-10-21 7:12 ` Ludovic Courtès
2021-10-25 13:09 ` Christine Lemmer-Webber
2021-10-28 8:38 ` Ludovic Courtès
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=2bfcad97b143c02bae05f04d26c0512d@libre.brussels \
--to=indieterminacy@libre.brussels \
--cc=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
--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.