From owner-freebsd-ports@FreeBSD.ORG Mon May 12 20:59:40 2014 Return-Path: Delivered-To: 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 4FC79D3A; Mon, 12 May 2014 20:59:40 +0000 (UTC) Received: from fire.magemana.nl (magemana.nl [IPv6:2a01:7c8:aaae:25e::1]) by mx1.freebsd.org (Postfix) with ESMTP id 119B32F92; Mon, 12 May 2014 20:59:40 +0000 (UTC) Received: by fire.magemana.nl (Postfix, from userid 1003) id 9FEF84AB4C5; Mon, 12 May 2014 22:59:32 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by fire.magemana.nl (Postfix) with ESMTP id 95D0B4AB4BF; Mon, 12 May 2014 22:59:32 +0200 (CEST) Date: Mon, 12 May 2014 22:59:32 +0200 (CEST) From: Melvyn Sopacua To: marino@freebsd.org Subject: Re: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st. In-Reply-To: <53711950.6040506@marino.st> Message-ID: References: <536E46E0.7030906@FreeBSD.org> <53707FF6.3010300@bsdforen.de> <5370843F.8070104@marino.st> <53711950.6040506@marino.st> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Ports , Dominic Fandrey , portmgr-feedback@FreeBSD.org, Melvyn Sopacua X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2014 20:59:40 -0000 Hi, On Mon, 12 May 2014, John Marino wrote: > On 5/12/2014 20:49, Melvyn Sopacua wrote: >> >> >> On Mon, 12 May 2014, John Marino wrote: >> >>> I commit PR patches that are 6 to 18 months old fairly frequently. >>> There is obviously a huge backlog but many PRs are processed daily. The >>> PRs that aren't getting processed quickly are "[NEW PORT]" PRs (and >>> apparently anything mentioning fuse-fs for some reason). A staging PR >>> is going to jump the line; it has a higher priority. >>> >>> Why would you even entertain the idea that a staging PR will fall >>> between the cracks? >> >> Perhaps the better question is: what are the factors that will make >> committers shy away from a PR, even if it's summary contains stage? [1] >> Maybe we (maintainers) can do better? >> >> [1] > > Heh, 54 out of 2000+ PRs isn't too bad. :) Ok..2000 ports PR's open at given time on how many committers? Starting to look like Kurt has the right idea here. > I doubt most cases are people intentionally passing over an ugly PR. I > am sure it happens but staging is generally straightforward so the PR > itself isn't going to scare someone off. Well, mine (ports/188901) I can see why someone walks around it, cause the patch is >1MB and needs to be downloaded. The bulk is of course the giant plist introduced by staging (and we can blame Zend for a file-intensive boilerplate heavy framework, but that's another topic). However, I don't see a way to make it more attractive, which is why I asked. -- Melvyn