From owner-cvs-ports@FreeBSD.ORG Sun Aug 14 15:52:01 2011 Return-Path: Delivered-To: cvs-ports@FreeBSD.ORG Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 7F6D91065673; Sun, 14 Aug 2011 15:52:01 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 93EE523CF2B; Sun, 14 Aug 2011 17:52:00 +0200 (CEST) Message-ID: <4E47EF20.8000409@FreeBSD.org> Date: Sun, 14 Aug 2011 17:52:00 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Mnenhy/0.8.3 Thunderbird/3.1.11 MIME-Version: 1.0 To: Alexey Dokuchaev References: <201108020942.p729g1Ti068765@repoman.freebsd.org> <20110811180338.GB88978@hades.panopticon> <20110812093328.GE85247@hades.panopticon> <20110812101133.GF85247@hades.panopticon> <4E4584EA.7090306@FreeBSD.org> <20110813133717.GA38385@hades.panopticon> <4E469837.1030903@FreeBSD.org> <20110813172040.GC38385@hades.panopticon> <20110814030033.GA80255@FreeBSD.org> In-Reply-To: <20110814030033.GA80255@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: Baptiste Daroussin , Doug Barton , cvs-all@FreeBSD.ORG, ports-committers@FreeBSD.ORG, Chris Rees , Dmitry Marakasov , cvs-ports@FreeBSD.ORG Subject: Re: cvs commit: ports/cad/admesh Makefile X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2011 15:52:01 -0000 Am 14.08.2011 05:00, schrieb Alexey Dokuchaev: > On Sat, Aug 13, 2011 at 09:20:40PM +0400, Dmitry Marakasov wrote: >> * Matthias Andree (mandree@FreeBSD.org) wrote: >>> Possibly we should always mark ports for removal for three months after >>> the point in time when the maintainer gets reset to ports@. >> >> Nice. Well that'll only result in two processes: more and more ports >> will have maintainers reset and then removed, and remaining maintainers >> will take more and more ports beyond their ability to maintain them, >> both will lead to collapse. Is this also not undesirable? > > Big +1 for Dmitry here; ports@ is perfectly fine maintainer entity, much > easier to work with, and often receives more and better care than many of > seemingly "properly" maintained ports. Assuming that were true, how else do we make sure not to let rotten code linger in the ports tree?