From owner-freebsd-ports@FreeBSD.ORG  Wed Jul 18 10:33:02 2012
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 745901065670;
	Wed, 18 Jul 2012 10:33:02 +0000 (UTC)
	(envelope-from freebsdml@marino.st)
Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148])
	by mx1.freebsd.org (Postfix) with ESMTP id 408658FC0C;
	Wed, 18 Jul 2012 10:33:02 +0000 (UTC)
Received: from [192.168.0.225] (atoulouse-256-1-130-170.w90-45.abo.wanadoo.fr
	[90.45.57.170])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by shepard.synsport.net (Postfix) with ESMTP id DF69543BA8;
	Wed, 18 Jul 2012 05:32:59 -0500 (CDT)
Message-ID: <500690C9.5080700@marino.st>
Date: Wed, 18 Jul 2012 12:32:41 +0200
From: John Marino <freebsdml@marino.st>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: freebsd-ports@freebsd.org, Chris Rees <crees@freebsd.org>
References: <50017C97.3050200@filez.com>
	<CADLo83_a=qOqTgGQF+LSYyGDaJoT6B2vF9JGV=a2ZHRXRyR6Pw@mail.gmail.com>
	<20120714192119.GA61563@vniz.net> <5001CB97.6070205@filez.com>
	<CAF6rxgkYjKAcLqX6ehX04ho-g7mCvcDOOb1KJC1Oxc4zvfjtHA@mail.gmail.com>
	<50054F6E.9040002@filez.com> <50055293.3010002@FreeBSD.org>
	<20120717213902.GB21825@lonesome.com> <5005E2AE.3040806@marino.st>
	<20120717224302.GA26742@lonesome.com> <50065B3B.8040404@marino.st>
	<CADLo83_9FexxjUA8Ws02iFUhB5VLqCQzf7G4ELcm2S2uJFhkxQ@mail.gmail.com>
In-Reply-To: <CADLo83_9FexxjUA8Ws02iFUhB5VLqCQzf7G4ELcm2S2uJFhkxQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Re: maintainer timeout for FreeBSD commiters
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 10:33:02 -0000

On 7/18/2012 12:19, Chris Rees wrote:
> On 18 Jul 2012 07:44, "John Marino"<freebsdml@marino.st>  wrote:
>> Yes, somebody would have to set that up but it would pay big dividend I
> think.
>
> It also does away with the QA aspect that committers currently provide.
> I'd like to repeat that people sufficiently familiar with the ports system
> to QA patches generally ends up with a commit bit fairly quickly.
>
> Chris


I wouldn't assume people that become this proficient necessarily want a 
commit bit.

The whole point of my proposal is give and take.
Yes, you take away "QA" responsibility from an entire pool of committers 
and make it the primary responsibility of this new class of maintainer 
on a per port basis (and not nearly all ports either).  I was proposing 
that your gains (much less PRs, more often maintained ports) far 
outweigh the liabilities.  I would be selective who gets assigned to 
this new class.  They should have a body of work that instills 
confidence that they can handle QA.

You don't get something for nothing and it's not hard to revoke the 
privilege if a person can't handle it.
John