From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Lirzin Subject: Re: [REQ/DISCUSSION] patch managing system Date: Mon, 21 Mar 2016 16:48:50 +0100 Message-ID: <87wpoval25.fsf@gnu.org> References: <87h9g0eq1c.fsf@grrlz.net> <87d1qogcfw.fsf@grrlz.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43140) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ai24g-00038b-CH for guix-devel@gnu.org; Mon, 21 Mar 2016 11:48:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ai24f-0007f6-Fl for guix-devel@gnu.org; Mon, 21 Mar 2016 11:48:58 -0400 In-Reply-To: <87d1qogcfw.fsf@grrlz.net> (Nils Gillmann's message of "Mon, 21 Mar 2016 14:58:27 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Nils Gillmann Cc: guix-devel@gnu.org Hi, Nils Gillmann 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