From: Adriano Peluso <randomlooser@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: issue tracking in git
Date: Sat, 14 Aug 2021 10:29:09 +0200 [thread overview]
Message-ID: <078de6ddead6a4599627348671a26c95560a0050.camel@riseup.net> (raw)
In-Reply-To: <87v949iitg.fsf@elephly.net>
Il giorno ven, 13/08/2021 alle 15.18 +0200, Ricardo Wurmus ha scritto:
>
> Hi Adriano,
> [...]
> Was it perhaps Carl Dong?
yes, it was Carl Dong
Thank you
> > I don't remember the name of such person and I am wondering if
> > amy
> > progress has been achieved on that front
>
> I don’t think there was a decision to do issue tracking in git.
Do you mean a decsion by the bitcoin community ?
Or by the Guix community ?
> 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.
>
I hadn't thought about this
This is a potential problem that deservses exploration
I think issue tracking in git could be explored starting with smaller
projects first
Probably Guix is too large and entrenched to be used as a test bed for
this kind of explorations
I'm asking about the state of the art in this regard because I feel
that server based solutions are problematic even for free software
oriented organizations
And should the bitcoin community explore this a bit, that would be a
very interesting development, in my view
next prev parent reply other threads:[~2021-08-14 8:29 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
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 [this message]
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=078de6ddead6a4599627348671a26c95560a0050.camel@riseup.net \
--to=randomlooser@riseup.net \
--cc=guix-devel@gnu.org \
--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).