From owner-freebsd-ports@FreeBSD.ORG Mon Nov 10 17:13:05 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 B658216A4CE for ; Mon, 10 Nov 2003 17:13:05 -0800 (PST) Received: from cultdeadsheep.org (charon.cultdeadsheep.org [80.65.226.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CE2243FDF for ; Mon, 10 Nov 2003 17:13:03 -0800 (PST) (envelope-from sheepkiller@cultdeadsheep.org) Received: (qmail 43704 invoked by uid 85); 11 Nov 2003 02:13:01 +0100 Received: from sheepkiller@cultdeadsheep.org by goofy.cultdeadsheep.org by uid 82 with qmail-scanner-1.20rc2 ( Clear:RC:1:. Processed in 0.206756 secs); 11 Nov 2003 01:13:01 -0000 Received: from persephone.cultdeadsheep.org (192.168.0.8) by goofy.cultdeadsheep.org with SMTP; 11 Nov 2003 02:12:59 +0100 Received: (qmail 95101 invoked from network); 11 Nov 2003 02:13:34 +0100 Received: from unknown (HELO lucifer.cultdeadsheep.org) (192.168.0.2) by persephone.cultdeadsheep.org with DES-CBC3-SHA encrypted SMTP; 11 Nov 2003 02:13:34 +0100 Date: Tue, 11 Nov 2003 02:12:59 +0100 From: Clement Laforet To: Sergey Matveychuk Message-Id: <20031111021259.03adac22.sheepkiller@cultdeadsheep.org> In-Reply-To: <3FB02AA6.6000803@ciam.ru> 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> <53EC784E-13C5-11D8-AD24-003065ABFD92@mac.com> <3FB00E53.8060603@fillmore-labs.com> <3FB02AA6.6000803@ciam.ru> Organization: tH3 cUlt 0f tH3 d3@d sH33p X-Mailer: Sylpheed version 0.9.7 (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: cswiger@mac.com cc: freebsd-ports@freebsd.org cc: eikemeier@fillmore-labs.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: Tue, 11 Nov 2003 01:13:05 -0000 On Tue, 11 Nov 2003 03:17:42 +0300 Sergey Matveychuk wrote: > > Yes. It's a good point to have two branches for ports. So many times I > > cvs'ed an old port version because found a new one unstable... Hey guys, it looks like debian packages management system :-) CVS branches, by-port-mentoring, etc. are pretty good ideas but are we able to deal with this ? Two branches implies two commits. If maintainer can commit on the "testing" branche, you have just push the dirt under the carpet, who will consider your port(s) stable enough ? Who will be responsible for massive changes (like gettext update) ? By-port-mentoring (I mean "when a committer add a ports, he's reponsible of it") is seducing, but committers have a real life too, so they can be AFK for a while, so PR will rot in GNATS too. Everyone who submits a port hopes his port will be committed quickly, to contribute with the project. It's quite hard to get a "minor port" committed if committers don't know you. Another approach of the problems: 1. insert more revelant informations in PR. We can add fields in PR bodies to simplify Mark Linimon works. i.e. PORTNAME: my-ports CATEGORY: what-I-want CLASS: [update|patch|fix] maintainer-update is no more efficiant nowadays and synopsises are overloaded with redundant informations to catch committers attention. 2. Encouraging committers to get involved in maintaining categories, like Joe Marcus Clarke for gnome related ports. I know it's not as easy at it seems: you can't ask a committer to deal with very specific port he don't know. If we "segment" (a little more) ports-bugs, new ports (and only new ports) can be routed to sublists which committers choose to subscribe or unsubscribe when they want, avoiding new ports to be lost in the mass. clem