From owner-freebsd-ports@FreeBSD.ORG Wed Jan 29 09:27:05 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 DC24E9B0 for ; Wed, 29 Jan 2014 09:27:05 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 919711350 for ; Wed, 29 Jan 2014 09:27:05 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1W8RQF-000JNQ-Pr for freebsd-ports@freebsd.org; Wed, 29 Jan 2014 10:27:03 +0100 Date: Wed, 29 Jan 2014 10:27:03 +0100 From: Kurt Jaeger To: FreeBSD Mailing List Subject: Re: What is the problem with ports PR reaction delays? Message-ID: <20140129092703.GU2951@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: Wed, 29 Jan 2014 09:27:05 -0000 Hi! > Unfortunately, nothing is happening. I expected to hear some voices about > certain ideas that have popped up, like: > > * can we cut off old and 'unloved' PR's in order to reduce the amount of > work and make reassessment of that amount There is the other view of this which says "PRs do not eat hay, closing them does not really fix anything". I think this one is still open for debate. > * can we use people who volunteered to work on the PR's There are people submitting PRs, and those committing changes, and in between them those people that check/confirm PRs. They could do that before and they can still do it now, if they want to. So besides *doing* this there is not much "push" that can help here. > * can we incorporate automation in the PR workflow, for example, the one > provided by redports I've read through the thread and would like to hear more about this. Can anybody with knowledge about it please remind us of the details to this idea ? > * can we introduce new levels of access, the commiters that are commiting > on the ports they're maintaining I would welcome this, and by doing this, I would learn more about the committing process and would probably apply this to other ports in the future. There is another option, which needs to be debated: Start regular money collection which pays for some full-time staff that does commits etc. The downside might be that the volunteers see themselves less valued and become less involved in committing/reviewing etc, because "someone else ist paid for it and I'm not". This might be a serious issue, so how could we solve this motivational effect ? -- pi@opsec.eu +49 171 3101372 6 years to go !