From owner-freebsd-ports@FreeBSD.ORG Wed Apr 27 13:33:02 2011 Return-Path: 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 C8D2C106566C for ; Wed, 27 Apr 2011 13:33:02 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-yi0-f68.google.com (mail-yi0-f68.google.com [209.85.218.68]) by mx1.freebsd.org (Postfix) with ESMTP id 763038FC08 for ; Wed, 27 Apr 2011 13:33:02 +0000 (UTC) Received: by yih10 with SMTP id 10so281050yih.7 for ; Wed, 27 Apr 2011 06:33:01 -0700 (PDT) Received: by 10.150.210.15 with SMTP id i15mr449023ybg.377.1303911181684; Wed, 27 Apr 2011 06:33:01 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id p41sm801326ybk.14.2011.04.27.06.33.00 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Apr 2011 06:33:00 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QKMfz18xWz2CG6F for ; Wed, 27 Apr 2011 09:32:59 -0400 (EDT) Date: Wed, 27 Apr 2011 09:32:58 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110427093258.3966cfd2@seibercom.net> In-Reply-To: <19896.4396.161941.282904@jerusalem.litteratus.org> References: <4DB7B237.7000603@marino.st> <20110427075436.70ae18ac@seibercom.net> <19896.4396.161941.282904@jerusalem.litteratus.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: How are [MAINTAINER] patches handled and why aren't PRs FIFO? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 13:33:02 -0000 On Wed, 27 Apr 2011 08:50:52 -0400 Robert Huff articulated: > > Jerry writes: > > > > Ha, i've submitted mine about two months ago and still no luck. > > > > Personally, I believe that the current system, if not partially > > broken, is far from ideal. I would prefer to see a system where > > each submitted PR is assigned a specific number (I believe it is > > actually) and then assigned in numeric order to the next > > available committer. > > Not all committers are created equal. Asking Joe-the-fonts- > guru to work on Mary's network monitoring application is probably > not productive. > Keeping a centralized list of who/what pairs - more > importantly, keeping it useful - is another job on someone's desk. > Are you that someone? > > > I am sure that the old, "But they are all volunteers", or some > > such tirade will erupt. > > Not a tirade, but ... guilty. > > > It must be remembered that those who submit items for approval > > are also volunteers. They deserve at least as much respect as > > those who are actively working on those submitted items. > > Am I correct you are asking for a (far) higher level of > dedication from the committers than from those who submit changes? > Consider the port that goes untouched (in spite of substantial > upstream changes) for months or even years; someone picks up the > torch, and the poor committer gets N-thousend lines of new features, > security patches, and dependency changes dumped on them to be > checked in ... how long was that? > > Do I think there are flaws in the current system? Sure. > But as long as we're faced with this particular choice of > evils > - slow updating versus lowered quality - I vote "first, do no harm". I am not sure how the Hippocratic Oath got involved here. In any case, I see no reason why the "slow" and "lowered" qualities cannot find happiness together. Please reread what I posted. I stated that if a submitter's item was to be delayed for an extended period or bypassed in favor of a later submission by another submitter then the submitter of the older item should be notified as to why and if possible given an approximate commit date. I fail to see why that would cause undo stress or an unbearable burden on the committer(s). The committer(s) could create a boiler plate document to handle just such cases. However, I do find troubling you statement regarding a large update to an older port or even a new port submission for that matter. I see no logical reason for a committer to bypass an item simple based on its size or the amount of work involved in getting it committed. After all, consider that the original submitter invested a large amount of his/her time in that same item. The only honest and fair way to handle ports request is on a FIFO basis unless a bona fied excuse can be shown to deviate from that procedure. To simplify the system, a two week limit, or whatever reasonable time frame can be agreed upon, should be put into effect. Any submitted item that cannot be committed within that time frame would require the committer to notify the submitter of such and if possible a reasonable date to complete the commit. I do not believe that, that is by any stretch of the imagination excessive. Many government and private organizations work under those same basic constraints without undo harm. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ The great nations have always acted like gangsters and the small nations like prostitutes. Stanley Kubrick