all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mthl@gnu.org>
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: guix-devel@gnu.org
Subject: Re: [REQ/DISCUSSION] patch managing system
Date: Mon, 21 Mar 2016 16:48:50 +0100	[thread overview]
Message-ID: <87wpoval25.fsf@gnu.org> (raw)
In-Reply-To: <87d1qogcfw.fsf@grrlz.net> (Nils Gillmann's message of "Mon, 21 Mar 2016 14:58:27 +0100")

Hi,

Nils Gillmann <niasterisk@grrlz.net> writes:

> As you maybe already noticed, and I hope this is not just a
> temporary impression I have after ~4 months or so, guix-devel is
> getting an increasing amount of messages per day and per month.

Same feeling here.

> In my opinion this makes it hard to keep track of patches and
> maybe also makes the workflow of people with commit access
> harder and we need a patch managing solution.
[...]
> 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
[...]
> what are your thoughts?

I think keeping track of patches is a valid concern.  However I think
you are not focusing on the actual problem by speaking of adding other
interfaces.  IMO the crucial point to make life of reviewer easier,
would be to automate the repetitive tasks and to have a way to not
forget old unpushed patches.  I think providing interfaces that are not
email based is orthogonal to this.

To automate the repetitive tasks, Cyril Roelandt had started sometimes
ago to work on a bot that was continuously applying and building
incoming patches on top of master and report (by email) if things were
building correctly.  I think that is a good idea that could be extended
by providing a way to send commands to the bot like what is done for
Debbugs.

Cyril: Do you think the bot option is feasible?

-- 
Mathieu Lirzin

  parent reply	other threads:[~2016-03-21 15:48 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
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   ` Mathieu Lirzin [this message]
2016-03-21 16:08     ` [REQ/DISCUSSION] patch managing system 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wpoval25.fsf@gnu.org \
    --to=mthl@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=niasterisk@grrlz.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 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.