From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Seeking a "Patch Champion" Date: Mon, 25 Apr 2016 18:40:15 +0200 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1461602450 20346 80.91.229.3 (25 Apr 2016 16:40:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 25 Apr 2016 16:40:50 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 25 18:40:40 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aujYt-0003QJ-Gr for ged-emacs-devel@m.gmane.org; Mon, 25 Apr 2016 18:40:39 +0200 Original-Received: from localhost ([::1]:32924 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aujYs-0001JR-Ru for ged-emacs-devel@m.gmane.org; Mon, 25 Apr 2016 12:40:38 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35990) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aujYm-0001G1-I4 for emacs-devel@gnu.org; Mon, 25 Apr 2016 12:40:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aujYh-0003WA-HU for emacs-devel@gnu.org; Mon, 25 Apr 2016 12:40:32 -0400 Original-Received: from hermes.netfonds.no ([80.91.224.195]:59457) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aujYh-0003VM-Ay for emacs-devel@gnu.org; Mon, 25 Apr 2016 12:40:27 -0400 Original-Received: from cm-84.215.1.64.getinternet.no ([84.215.1.64] helo=stories) by hermes.netfonds.no with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.84_2) (envelope-from ) id 1aujYW-0004uU-91 for emacs-devel@gnu.org; Mon, 25 Apr 2016 18:40:18 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEWSmawXDhISBQkNAQQz MD0XCw8VCAwbFBvZIz+zAAACXklEQVQ4jW2UTWsbMRCGJ6CQa2Us710u8n0NPcswjc6CaM/NJpKv XrpBf7/vSF5oqSdgnHk073xoZDofx7M9/2V2diXWSuf/7GhtedcPwAiQFzo+jHgIRmedrv8CqcNa V/LAhKK6uQKXnW0pOQ0VwNoPHIO3iFMsJ11XRMBnRxGAxFRSSTnqoRK8pViHrqaUUp5ySlFrJO8q MHgNvMmYGAVIRgSIctImTcngfJMaXU8ICRONCG0Rdi5T04I3H5AqtogZxOnUUi5RH0o2EiARs33H ET2IuJmkiwY+nM1lAtDiGEwvt/aqzlZakmoWgwZTAzISXIFrveScpDx97/z4Y8ak4UdxqWQdN4B7 hjvLX0qT3hpExCin8yTDMlFqWBqYZ+egLU1DpE2k1nvnZYrwRr2ZgNm6XIoxUIh6aSWLv9LuxOX1 8/J22Ue9D/vLvoYaVtxgvHIOnz8BvmIDC9dwCytJnaUcemZI1UGEEGFdXRzmwSuHlS+i7ykAzCcO V+aBPCnvnwbmlYhDpXIi9QvMA+xJIY4FMCJwkl4/SamwJ7pxIFpJwHdSRF9vpJCcYAKYGyBSCYCD 9vhe8W+td/AU3wTrmzi9fDAlqPOThrxX+PQvdVXkkaMANCkBmn1Ac96rOyCDHHI/SLGi5g14egZY A6TUKADqNAF8I7Ulf9khipG9ARTWgaeLHjwARoLOg2uHBMgUpT25WjfLa8SClH59y9LmTuOX7c8M qO2m7I6AE8sDxkvDAkXZ1EX3O79yf9p4F1mkar3f4Meu/XiIyfoM0OlSv0f8Nsg6Iir1pWrgDznr BWkwEZ5tAAAAAElFTkSuQmCC In-Reply-To: (John Wiegley's message of "Sat, 23 Apr 2016 14:22:10 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 80.91.224.195 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:203295 Archived-At: John Wiegley writes: > Largely this is because we have so many of them: 435 this year, so far. And no > one (besides myself, who has been fully derelict in this duty) is currently > dedicated to ensuring that each of these patches receives due attention. > Unless someone with commit access has a particular interest in attending to a > patch right away, it generally fades into history. Well, that's what happens to patches on emacs-devel. The ones submitted to the bug tracker never fade away. > I would like to change this state of affairs by asking for a core of > volunteers who are willing to champion patches, and ensure that they go > through a process of review before being either rejected or applied. > > To assist this effort, I've connected our mailing lists with a service running > on my own VPS (for now) called "Patchwork"[1]: > > http://patchwork.newartisans.com/ I'm afraid I don't think this is likely to help much. Since it's not hooked up to the bug tracker, the list of patches on that site will just grow increasingly outdated. Having somebody herd a patch after it's already been applied is a waste of everybody's time. And I don't think adding yet another formality to the already pretty complicated "apply this patch already" "work flow" (for want of a better word) is the way to go. But the lost patch situation in Emacs is a genuine problem, and one that I think may be disencouraging new contributors. Here's what I think should happen: 1) Whenever somebody posts a patch to emacs-devel, and you don't feel like applying it at once, tell them "send this via `M-x report-emacs-bug', otherwise it'll never be applied". 2) People interested in herding patches should start using debbugs-gnu. I've now added another command to make this easier -- just say `M-x debbugs-gnu-patches', and you'll get a nice list of all the bug reports that contain patches. (Or at least the ones that have been marked as such, but that's pretty much all of them...) And I think that debbugs*.el should be included in Emacs core, so that we can get some traction here. Installing a package is apparently way too much work for most people... -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no