From owner-freebsd-ports@FreeBSD.ORG Sun Jan 26 13:06:57 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C84C79; Sun, 26 Jan 2014 13:06:57 +0000 (UTC) Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 32EB11601; Sun, 26 Jan 2014 13:06:57 +0000 (UTC) Received: by mail-qc0-f176.google.com with SMTP id e16so6695916qcx.35 for ; Sun, 26 Jan 2014 05:06:56 -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=1qZLSiNL1D2NhUM3UVTeEPVdugTe+FEQd1rQXQhEx0Y=; b=dnwVBz9h58NIB58wwfPUtHEPV5hXkAdSdEGuIkMLhu5f+BMOBGG9qIR6rFOIa2hOJ4 7BUYpZfRMHDyiY6LBNCQMct9TRW+ewv0VyL7iYAHOQHPRV3Kfywj9VO+aeMmWOxTYv7z dj0ssfXgiXzDASAcQHtsy/IQkKqFE/6dvu9iemdjxXIO8EuHP2OY99//F4kmudoWFrsC x/IF3KdpTnnwQAR9CCuc9r/ZGy7ZB2NVq2MEJaG7upg4OPencGIhRm+w1m8TRC9dzbQL FGqawXlvXjHRsOMu5zW/6W0x22eYDvS0Z4WafCGRuq33yPIPD3T8pe7uv4aV48r4bXWC SgzA== MIME-Version: 1.0 X-Received: by 10.224.41.70 with SMTP id n6mr3034631qae.96.1390741616365; Sun, 26 Jan 2014 05:06:56 -0800 (PST) Received: by 10.229.208.202 with HTTP; Sun, 26 Jan 2014 05:06:56 -0800 (PST) In-Reply-To: <52E398FF.9000300@FreeBSD.org> References: <52E2FA36.5080106@marino.st> <52E303CB.6020304@marino.st> <52E30990.2060903@marino.st> <52E398FF.9000300@FreeBSD.org> Date: Sun, 26 Jan 2014 14:06:56 +0100 Message-ID: Subject: Re: What is the problem with ports PR reaction delays? From: Big Lebowski To: Matthew Seaman Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: marino@freebsd.org, 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: Sun, 26 Jan 2014 13:06:57 -0000 On Sat, Jan 25, 2014 at 11:59 AM, Matthew Seaman wrote: > On 25/01/2014 10:35, Big Lebowski wrote: > >> Thus, are you volunteering for this role? It's not my call, but if you > >> > really want to do clean out and triage the all PRs on an ongoing > basis, > >> > my guess is that would be very welcome and we'd figure out a way to > set > >> > that up. It would definitely help, especially for those maintainer > that > >> > "approve" patches but the PRs never get opened (or set to a better > state > >> > than "open"). > > > If I wouldnt care about FreeBSD and ports state and I wouldnt want to > help > > with that, I would have not wrote this message in first place. Yes, I > would > > love to help. > > There are a lot of people who would love to help with FreeBSD, and there > is a lot of help that FreeBSD needs. The problem is that anyone > volunteering probably only has a limited amount of time they can donate > to the project, and there exists at the moment no simple mechanism for > dividing up the workload into small, easily digestible chunks. > > Take the case of PR triage, often cited as a suitable track for people > to start getting involved. Say we get about 300 new PRs in a week. > What we need is 20--50 people looking at 6--15 PRs a week, rather than > 2--5 people trying to look at 60--150 PRs a week. Trouble is, the first > few people to volunteer will find themselves drinking from the PR > firehose, and will probably give up long before enough additional people > can be drummed up to share the load. > Does it have to be all-or-nothing situation, where we can do something only if we have 20-50 people looking at 6-15 PR's a week, and we cant do anything if we dont? Cant we start with 2-3 people (3 people so far volunteered to do so, and I belive a 'call to arms' via this list/announcements/bsdnow.tv/reddit would result in may others willing to help) doing as much as they can? Also, what about some kind of 'junior commiter' role, where solid port maintainers get rights to commit to their ports only? If that would be doable, we could offload a lot of work from current commiters to work on other things. B. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. > PGP: http://www.infracaninophile.co.uk/pgpkey > > >