From owner-freebsd-ports@FreeBSD.ORG Sat Jan 25 00:03:10 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 708E9C07; Sat, 25 Jan 2014 00:03:10 +0000 (UTC) Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1C74E16E0; Sat, 25 Jan 2014 00:03:10 +0000 (UTC) Received: by mail-qa0-f41.google.com with SMTP id w8so4773249qac.28 for ; Fri, 24 Jan 2014 16:03:09 -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=LV3FNK+eABXVfNnn7UndV9Wd/iaeisu7g9ixwBFIrPI=; b=YKsW/Cpedh6dcu/1yVk2v7hT+BM3awWvQm0sb3vKjM6/CdMN+Duz2FOX41Kj8sGrKK EJY+KlOM4UVdQU/9I5yfpt4X0mB3BOk1ynIESOgZ/YZElj08sIeDu2a1Ibc8tqW+suSE iKpelShJaM2ni+6c5lXnAb1AahqpCNEb1DMh1Td+juozUZL58spW2qQ40biUhVXKFJ7A e+pml7nUYEUXHbyGAxpA5c0IhqytZXLgUv9fO/Q2jtBBPdttvavCiRL0o3v532ttPDL7 Tf4DVHN8Y2WEkKHq+3QSZf9cfK8AyZZGHAiaqhxmqomOcf/S2EVJC1+zgTyQ9kE/uGOj izSA== MIME-Version: 1.0 X-Received: by 10.140.44.119 with SMTP id f110mr23761781qga.31.1390608189285; Fri, 24 Jan 2014 16:03:09 -0800 (PST) Received: by 10.229.208.202 with HTTP; Fri, 24 Jan 2014 16:03:09 -0800 (PST) In-Reply-To: <52E2FA36.5080106@marino.st> References: <52E2FA36.5080106@marino.st> Date: Sat, 25 Jan 2014 01:03:09 +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:03:10 -0000 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. > > > Isnt there enought commiters? > > Well, at least there are more PRs than people closing PRs. Not all > committers deal with PRs. Getting a commit bit does not obligate you to > process PRs. If there's a PR already on a port a committer has interest > in fixing, then he/she will probably process the PR while they are there. > > > Isnt there a automated > > PR handling procedure reminding commiters with relevant access about such > > submissions? Can we help? I hope to spark some discussion. > > Of course there is. People get reminded about assigned PRs constantly. > You think a computer message will make somebody work faster if they > didn't forget about it (iow they are aware and actively decided not to > deal with it yet). > > 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? > , 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? > 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? > > 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" >