From owner-freebsd-ports@FreeBSD.ORG Mon Nov 10 13:32:22 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 074BB16A4CF for ; Mon, 10 Nov 2003 13:32:22 -0800 (PST) Received: from pi.codefab.com (pi.codefab.com [66.234.138.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1F3D43FAF for ; Mon, 10 Nov 2003 13:32:20 -0800 (PST) (envelope-from cswiger@mac.com) Received: from [10.1.1.193] (dpvc-68-161-244-25.ny325.east.verizon.net [68.161.244.25]) by pi.codefab.com (8.12.9p2/8.12.10) with ESMTP id hAALW5EC004543; Mon, 10 Nov 2003 16:32:09 -0500 (EST) In-Reply-To: <1068495958.690.72.camel@leguin> References: <1068458390.38101.19.camel@dirk.no.domain> <20031110152000.622db381.lehmann@ans-netz.de> <1068471598.38101.77.camel@dirk.no.domain> <20031110163623.GC93583@procyon.firepipe.net> <1068495958.690.72.camel@leguin> Mime-Version: 1.0 (Apple Message framework v606) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <53EC784E-13C5-11D8-AD24-003065ABFD92@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Mon, 10 Nov 2003 16:32:04 -0500 To: freebsd-ports@freebsd.org X-Mailer: Apple Mail (2.606) X-Spam-Status: No, hits=0.0 required=7.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on pi.codefab.com Subject: Re: Ability for maintainers to update own ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2003 21:32:22 -0000 On Nov 10, 2003, at 3:25 PM, Eric Anholt wrote: > One thing I've wondered about, though, is the process for people > getting > commit bits. Is it always on the initiative of an existing committer > (as it was in my case) or would it be considered acceptable for people > who would like to become committers and maintain their ports directly > to > propose themselves on a list for someone to pick them up as a new > committer? There may be some advantage to having an existing committer act as a guide and mentor for the person gaining commit privileges; certainly, that was the way Apple handled giving CVS commit access to the Darwin tree for non-Apple people. With regard to the origin of this thread, it might be useful to understand what the actual scope of the problem is: how long does it take, on average, for a new port submission to be committed? My limited experience suggests an interval between one week for a "highly interesting" port (dvd+rw-tools, in my case) to three or four months for other ports, but real data pulled out of the bug database would be more reliable than personal impressions. It might also be useful to set realistic targets for response times and mention them in the Porter's Handbook, so that people who submit ports know what to expect in terms of a timeframe. I'd really like to be able to suggest something like "you should have a committer review your submission within one month" and have that be doable, but I can't say whether that (or any particular fixed interval) would be practical. -- -Chuck