From owner-freebsd-ports@FreeBSD.ORG Tue Nov 11 13:22:07 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 9F81016A4D0 for ; Tue, 11 Nov 2003 13:22:07 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83FDC43FB1 for ; Tue, 11 Nov 2003 13:22:01 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D47E966B28; Tue, 11 Nov 2003 13:22:00 -0800 (PST) Date: Tue, 11 Nov 2003 13:22:00 -0800 From: Kris Kennaway To: Sergey Matveychuk Message-ID: <20031111212200.GA28576@xor.obsecurity.org> 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> <3FB02895.5050108@ciam.ru> <20031111001932.GA95315@toxic.magnesium.net> <20031111144221.GA527@iib.unsam.edu.ar> <3FB05FE0.2090005@lonesome.com> <3FB13ABD.1000800@ciam.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline In-Reply-To: <3FB13ABD.1000800@ciam.ru> User-Agent: Mutt/1.4.1i cc: Fernan Aguero cc: Mark Linimon cc: freebsd-ports@freebsd.org 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 21:22:07 -0000 --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 11, 2003 at 10:38:37PM +0300, Sergey Matveychuk wrote: > Mark Linimon wrote: >=20 > >In the meantime, it really comes down to just getting more > >volunteers involved within the existing framework, IMHO. >=20 > OK, where can we get they? :) >=20 > I think a new committer should get some obligations (say, to care about= =20 > an other's/orphaned ports). >=20 > May be there is a reason to designate a resposible person for each ports= =20 > category to move things faster? Designating someone as responsible for a certain thing doesn't work in a volunteer project, unless they agree to do it. But if they want to do it, there's nothing stopping *any* existing committer or non-committer from deciding they care about e.g. the audio/ category and working on fixing everything within it. Indeed, there are a number of people who decided they care about fixing the entire ports collection and started working on monitoring or fixing the numerous problems with it. Mark and Oliver are two such examples, who were non-committers when they started doing this (and eventually became committers as a result of doing a job that needed doing). Kris --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/sVL4Wry0BWjoQKURApNcAJ9GigSpHckMT0J407CIQRdgXJGlvACgq71V 20tXAu0Zn0mls/Txth5SMGY= =qMaW -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH--