From: Nils Gillmann <niasterisk@grrlz.net>
To: guix-devel@gnu.org
Subject: Re: [REQ/DISCUSSION] patch managing system
Date: Mon, 21 Mar 2016 16:10:43 +0100 [thread overview]
Message-ID: <878u1bvpcc.fsf@grrlz.net> (raw)
In-Reply-To: 87egb3vr08.fsf@grrlz.net
Nils Gillmann <niasterisk@grrlz.net> writes:
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>
>> Nils Gillmann <niasterisk@grrlz.net> writes:
>>
>>> First follow up idea:
>>>
>>> Ideal case would be:
>>> - integration with Guix in the future (the emacs interface and
>>> other potential future interfaces)
>>> - integration into Guix website
>>> - patches can be marked:
>>> - state (done/open)
>>> - priority
>>> - patches can be assigned to more than 1 person
>>> - webinterface
>>>
>>> As we are not at the ideal case and need a software until we get
>>> there, most projects seem to either use mailman, bugzilla,
>>> something equal to prmon.freebsd.org (ports monitor), simple pull
>>> requests on a mirror on a bigger source control system.
>>
>> I have a very strong aversion to bugzilla and other complicated tracking
>> systems. All of the above points are covered by debbugs, which we
>> already use for bug tracking.
>
> That's right, rain1 pointed this out to me in irc some moments ago.
>
>> debbugs has an Emacs interface as well as a read-only web interface.
>>
>> I must admit that I’m not using debbugs regularly for our bug tracker
>> because I’m not working on bugs very often. If we really wanted to
>> track progress on patches we could be using debbugs, but I don’t
>> actually think it would improve the situation much.
>>
>> Right now I’m capturing guix-devel emails that I want to look at later
>> with Org capture, or I simply leave them in an unread state. The
>> problem, in my opinion, is not so much keeping track of patches, but
>> taking the time to review and engage in discussions. I cannot review as
>> much as I would like to and for follow up discussions I often miss time
>> (in front of the computer, and in a reasonably awake state).
>
> Would it make sense to have a patches-only list or at least a
> separation between [general not-patch-related disussions,
> questions, pre-bug report questions] and [patches and their
> discussions]?
> This would not fix the people and times situation
> but eventually prevent situations in the future where we only
> have -devel for discussions, questions, patches, pre-bug
> questions, and with a growing number of participants more
> reviewers might come, but also more questions and other non-patch
> related input on the list, making it /maybe/ difficult to
> follow.
> I think it's better to think ahead and solve problems
> before they become problems, but maybe this is too soon.
Appended: maybe not, just went through emacs-devel and it seems
to be working out with discussion and patches.
Only -help at our side, there are some threads in -devel which
would be more suited for -help.
> (sidenote:
> I envision something for much later which I will discuss in
> another project and see if it fits into what we (in that project)
> focus on, maybe in a couple of years it could be useful.)
>
>> I don’t think it’s a software problem, but a people problem. To deal
>> with more patches we need more people reviewing patches. We already
>> have “guix lint” to point out common problems. We probably should add a
>> little helper script for all non-Emacsers that runs Emacs over the
>> expression to check the indentation. But other than that I’d just say:
>>
>> resend a patch if you haven’t received any response within five days or
>> so.
>
> From my perspective, resending does not really help either. It
> fills up the mailinglist with duplicates and unless I mention
> which of these threads can be considered closed, any version
> could be seen as the patch and it only works around the problem
> you mentioned and I see - too little people to review and apply
> patches.
--
ng
personal contact: http://krosos.sdf.org
EDN: https://wiki.c3d2.de/EDN
next prev parent reply other threads:[~2016-03-21 15:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 22:35 [REQ/DISCUSSION] patch managing system Nils Gillmann
2016-03-21 13:58 ` Nils Gillmann
2016-03-21 14:15 ` Ricardo Wurmus
2016-03-21 14:34 ` Nils Gillmann
2016-03-21 15:10 ` Nils Gillmann [this message]
2016-03-21 16:43 ` Ludovic Courtès
2016-03-22 11:53 ` Nils Gillmann
2016-03-22 16:26 ` Ludovic Courtès
2016-03-23 4:44 ` Chris Marusich
2016-03-23 7:41 ` Ricardo Wurmus
2016-03-23 8:15 ` Chris Marusich
2016-03-23 8:57 ` Andy Wingo
2016-03-23 8:36 ` Alex Kost
2016-03-23 8:54 ` Chris Marusich
2016-03-23 22:24 ` Ludovic Courtès
2016-03-24 8:53 ` Alex Kost
2016-03-23 16:02 ` Leo Famulari
2016-04-16 11:13 ` Ludovic Courtès
2016-04-28 8:24 ` Patch tracking Ludovic Courtès
2016-04-28 11:30 ` Ben Woodcroft
2016-04-28 12:17 ` Ludovic Courtès
2016-05-02 8:25 ` Ricardo Wurmus
2016-03-21 15:48 ` [REQ/DISCUSSION] patch managing system Mathieu Lirzin
2016-03-21 16:08 ` Mathieu Lirzin
2016-03-30 20:52 ` Cyril Roelandt
2016-03-31 6:39 ` Efraim Flashner
2016-03-31 7:53 ` 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
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=878u1bvpcc.fsf@grrlz.net \
--to=niasterisk@grrlz.net \
--cc=guix-devel@gnu.org \
/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).