unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Ricardo Wurmus <rekado@elephly.net>,
	Adriano Peluso <randomlooser@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: issue tracking in git
Date: Fri, 13 Aug 2021 18:19:23 +0200	[thread overview]
Message-ID: <874kbtfhbo.fsf@xelera.eu> (raw)
In-Reply-To: <87v949iitg.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 2199 bytes --]

Hi Adriano and Ricardo,

I'm also _very_ interested in keeping issues in the same repo as code
and I'm really envious of Fossil users [1] :-D

Ricardo Wurmus <rekado@elephly.net> writes:

[...]

> Many years ago I used Bugs Everywhere 
> (https://bugs-everywhere.readthedocs.io/en/latest/) for my 
> personal projects.  I really quite liked it, not least because you 
> can close a bug right as you fix the issue — it’s part of the same 
> commit.

I've still not tested it but there is also git-issue
(https://github.com/dspinellis/git-issue), there's also a Guix patch
[bug#49581]

> I have no idea how well it works when there’s a lot of “traffic” 
> in a distributed project, e.g. when there are several comments to 
> the same issue by different people.  Having merge conflicts in the 
> issue tracker is a headache I’d like to avoid.

Each issue and issue comment is a file named with a SHA, see
https://github.com/dspinellis/git-issue#internals for details; issues
and comments can be edited, so coordination and contribution guidelines
(also) for issues and comments are still needed.

There's no other interface than the CLI, so no email based workflows.

An interesting workflow could be to use emails as a "side-channel" for
discussions /about/ issues (and issue comments), and maintainers could
provide a public-inbox [2] of the "issues-discussion" messages; email
discussions can be linked with the git-issue managed issues (and
comments) by the maintainers of the project, in order to keep track of
the discussions while maintaining them separated from issues (and issue
comments).  This way, issues should be considered more like (meta-)code
than out-of-channel-text, from a maintainers POV. :-D

Last, AFAIK Diomidis Spinellis have compiled the most updated list of
tools for issue tracking "embedded" in git:
https://github.com/dspinellis/git-issue#related-work


Best regards, Gio'


[1] https://fossil-scm.org/home/doc/trunk/www/bugtheory.wiki

[2] that in turn creates a git repo of the messages, and provides a
read-only web view of all the archived messages

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  reply	other threads:[~2021-08-13 16:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13  6:29 issue tracking in git Adriano Peluso
2021-08-13 13:18 ` Ricardo Wurmus
2021-08-13 16:19   ` Giovanni Biscuolo [this message]
2021-08-14  8:30     ` Adriano Peluso
2021-08-15 10:39     ` Pjotr Prins
2021-08-15 15:28       ` Giovanni Biscuolo
2022-11-22 17:57         ` Giovanni Biscuolo
2022-11-23  4:35           ` Pjotr Prins
2022-11-23 10:29             ` Giovanni Biscuolo
2022-11-23 10:59               ` indieterminacy
2022-11-23 14:19                 ` Giovanni Biscuolo
2022-11-23 16:53                   ` indieterminacy
2022-11-23 13:18               ` Pjotr Prins
2022-11-23 14:58                 ` Giovanni Biscuolo
2022-11-25 13:45                 ` zimoun
2022-11-25 22:03                   ` Arun Isaac
2022-11-26  9:51                     ` zimoun
2022-11-24 22:01               ` Arun Isaac
2021-08-14  8:29   ` Adriano Peluso
2021-08-13 14:39 ` raingloom
2021-08-16  4:39   ` Adriano Peluso

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=874kbtfhbo.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=guix-devel@gnu.org \
    --cc=randomlooser@riseup.net \
    --cc=rekado@elephly.net \
    /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).