From owner-freebsd-ports@FreeBSD.ORG Sat Jan 25 00:36:27 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 75024CBD; Sat, 25 Jan 2014 00:36:27 +0000 (UTC) Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1F342192C; Sat, 25 Jan 2014 00:36:27 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id m20so5291811qcx.23 for ; Fri, 24 Jan 2014 16:36:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zkCRmRKauH8xOAX382HPGdoQuIvdYvmQqaFDcNW2N0Y=; b=RY2vwABe9v3cm+HbQD+tO/GkN11mQWVXJggCohQST+54Dencm4X8GEttYpA9fgfkDA vt4FnjqBzD6oZuk0F+wrdTTxB04CwJZnnYmCxN5iyshwvialJ4u1o25qZ+910hStk6tz cgYBq5t9pvRavjqNKUqJ2PZb8NAtSTuc6nn2UCmE5gODXcCG8gu947lZlEULLEXqeF/S 27ZUsD6FB76dgC0K6MxKIp0b0J0ArFYUt8PWycfIFMytmFoxPsv05UBRtYq9Q0+g5LmD 293Zc6inX90nCxXcOLGVq6jLb51AELwhcjzzAhua4DO1SkSJw6o1ztSwrmakwF048T6s MRmA== MIME-Version: 1.0 X-Received: by 10.224.72.72 with SMTP id l8mr24954554qaj.51.1390610186354; Fri, 24 Jan 2014 16:36:26 -0800 (PST) Received: by 10.229.208.202 with HTTP; Fri, 24 Jan 2014 16:36:26 -0800 (PST) In-Reply-To: <52E303CB.6020304@marino.st> References: <52E2FA36.5080106@marino.st> <52E303CB.6020304@marino.st> Date: Sat, 25 Jan 2014 01:36:26 +0100 Message-ID: Subject: Re: What is the problem with ports PR reaction delays? From: Big Lebowski To: marino@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 00:36:27 -0000 On Sat, Jan 25, 2014 at 1:22 AM, John Marino wrote: > On 1/25/2014 01:03, Big Lebowski wrote: > > On Sat, Jan 25, 2014 at 12:41 AM, John Marino >wrote: > > > >> On 1/25/2014 00:30, Big Lebowski wrote: > >>> Hi everyone, > >>> > >>> I wanted to ask about the growing time of reaction to ports PR's - what > >> is > >>> the problem? It seems to me, as a ports contributor, that this time is > >> only > >>> growing, not shrinking, and there's no formal/automated procedures that > >>> would help in managing the issue. > >>> > >>> What is the problem? > >> > >> Seriously? You did all that research and didn't notice this? > >> query all open ports PRS: 1705 problems total. > >> > >> Short answer: Sheer number of PRs. > >> > > > > I did, in fact, and this is not the problem, this is the symptom of the > > problem. > > No, it's not. PRs are getting closed, all the time, every day. But PRs > are coming in faster than they are getting closed. A couple of days > ago, the number of open PRs was down to 1660. > > You can say the solution is to increase the rate of PR closing. I could > counter with not allowing any new PRs to be submitted. Both would solve > the problem, and my way is easier to implement. :) > > > >> I would have thought the situation is kind of obvious. There are lots > >> of PRs, nobody is paid to process them, there are no teams dedicated to > >> "new ports" > > > > Perhaps there could be? Or some commiters who would assess if the PR can > be > > handled easily or it needs a more experienced eye to look at it? > > > > Timeless question: How does one force a volunteer to do anything? > Answer: You can't. > > > >> , lots of PRs are stuck because their non-freebsd.org > >> maintainers are MIA or abandoned their emails and nobody is going to > >> > > > > Shouldnt those be invalidated and closed to reduce the workload illusion > > that tends to set off people from doing work? > > Yes. > Now, who is going to do it? > And after you select him or her, how do you force them to do it? > > > > >> touch a PR in "feedback", etc, etc. Finally, some committers are pretty > >> sloppy at closing complete/obsolete PRs. > >> > >> When people get paid to do it, I think the situation will improve. :) > >> > > > > Great, then perhaps FreeBSD deserves dedicated, paid commiter to handle > > that situation? After all, we're donating money to the project, and if > > there's general consensus this is a problem that needs to be fixed and > this > > is the only way to do it, then perhaps something can be done about it? > > > I don't control FreeBSD Foundation funds in any way. > Having a full time paid person doing PR triage would put a huge dent in > the backlog. But we're just wishing, right? There aren't many paid > positions and those don't do clerical work like trouble tickets. > I was hoping to get some discussion revealing how the work is organized around ports PR, perhaps some ideas on improving them and I hoped that people who can make decisions and changes would notice it and consider them, since as they say, the squeeky wheel gets the grease, that's all. At no point I insisted on forcing anyone to anything, and I dont think that's neither only nor a viable solution. It seems obvious that current process doesnt work very well, then I'd aim at reorganizing that process - it appears that there is no roles specified, so the responsibility is blurred, and when everyone is responsible for one thing, in practice no one is. Perhaps role assignment could be of any help? > > John > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >