From owner-freebsd-ports@FreeBSD.ORG Thu Nov 29 09:33:45 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3ED62FE2 for ; Thu, 29 Nov 2012 09:33:45 +0000 (UTC) (envelope-from roam@ringlet.net) Received: from nimbus.fccf.net (nimbus.fccf.net [77.77.144.35]) by mx1.freebsd.org (Postfix) with ESMTP id CD7538FC17 for ; Thu, 29 Nov 2012 09:33:44 +0000 (UTC) Received: from straylight.m.ringlet.net (unknown [78.90.13.150]) by nimbus.fccf.net (Postfix) with ESMTPSA id 00856ACF for ; Thu, 29 Nov 2012 11:24:33 +0200 (EET) Received: from roam (uid 1000) (envelope-from roam@ringlet.net) id 50e0b1 by straylight.m.ringlet.net (DragonFly Mail Agent); Thu, 29 Nov 2012 11:24:33 +0200 Date: Thu, 29 Nov 2012 11:24:33 +0200 From: Peter Pentchev To: Alexander Yerenkow Subject: Re: FreeBSD ports you maintain which are out of date Message-ID: <20121129092433.GA5519@straylight.m.ringlet.net> Mail-Followup-To: Alexander Yerenkow , Kevin Oberman , ports@freebsd.org, Paul Schmehl , portscout@portscout.zi0r.com, Shane Ambler , Radim Kolar References: <201211271554.qARFs9un067018@null.zi0r.com> <50B4E664.6030606@filez.com> <50B56392.9060506@ShaneWare.Biz> <31BBFCB108C82225ADF20511@utd71538.campus.ad.utdallas.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: portscout@portscout.zi0r.com, Radim Kolar , Paul Schmehl , Kevin Oberman , ports@freebsd.org, Shane Ambler X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 09:33:45 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 28, 2012 at 09:06:59PM +0200, Alexander Yerenkow wrote: > 2012/11/28 Kevin Oberman >=20 > > On Wed, Nov 28, 2012 at 7:45 AM, Alexander Yerenkow > > wrote: > > > In that case, near each port should be.mntr contact mentioned, to.mak= e it > > > easier for anyone to contact mntr immediately, instead making additio= nal > > > unnecessary steps. > > > > I suspect that you are missing the fact that all ports which lack a > > specific maintainer (most of them) are maintained by ports@. So the > > messages to ports are only for the vast array of ports that are > > unmaintained. There is no one else to contact. > > > > Ideally, if someone has a little free time, they can look at the list > > and pick a couple to update and submit the update in a PR to ports > > with a category of "update". Or even better, become the maintainer, > > yourself. I have been maintainer for a couple of ports that were > > critical to my work, so I could be sure that they would be updated > > promptly. > > >=20 > Not exactly :) My suggestion about including current maintainer contact > info was about this part of discussion: >=20 > >>Probably more to the point is that it shouldn't get sent to the ports > >>mailing list - just to port maintainers. > >Did you ever think that sending it to the list might motivate someone el= se > to take over the port? > >There's a reason ports get out of date. One of the reasons is because the > port maintainer has lost interest or no longer has the time. If people on > the list see it, someone who is motivated might update the >port and end = up > being its new maintainer. >=20 > So, my thought was, if you ever came to sending portscout messages with > alive maintainer to all ports@ list, would be nice to see contacts > immediately. > You could learn that some maintainer is inactive last time, and next time > you see update for his port, you could get it to work. > Something like that. But this is exactly the point - portscout *only* sends messages to the e-mail address listed in the port's MAINTAINER line. If portscout's message goes to the ports@FreeBSD.org list, then there *is* no active maintainer - what Paul means is that the maintainer has lost interest (or the ability / resources / time to work on the port) and somebody has reset the port's maintainership to ports@FreeBSD.org. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org peter@packetscale.com PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 If I had finished this sentence, --FCuugMFkClbJLl1L Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQtynMAAoJEGUe77AlJ98T4mYP/1jZbE4vZJebY/Jc/n/rlxPi /zH7JbfUzfulpi3aw6jBsx/qDTxLO4AqrvAOmZLy0EVrJl9xxcPcLMeprFLltB3o FNuWpR68H5z2J3peue7V0UBJTOB0lISUrUbpWi0+gFWvqk8Q6hPIyqaJeB2w+kZR FMYLkZQD4OpVOkxCLOBBkcJ8R6Vxd522kGeg+QZHm0K8L+mmtPQFhg1Q06VKGU+c WpE3mgPQeK0aIexOmPxUNg4R3Yfs9Xlabuq3T7TIy/NzUEYRpxV1RiyTnziUKKwW gcKDi2AHlQlKFogZ7OtlcP2y03Kgfn71p6R7qrzYRwPfoE8uBEtOc7oSQRGzy+8W Z2vunBYwE/mcmC31yTZUNNmuSGfUyqK+383TfaRD734HT2/d7BuBMUdOr8iS2LBc 5IKTJnDUrsRl0OXnfeSQoyRgMhDtjkKzfHMYKWUbh4YxV+39bXVJ189wTjALW73R TFDYDWZD6KyklUIZvz/Hgrh4H6LqsqxDgmEeib4ZTWM3pjazSwQOs6bQcHyMWYZk VD1x9ZEjeSZqJ0Rg3qR/oW+mnHwt8G0hV6wiCYPO34nXgS6Q8YoU2P+wqwlmMRvK avHLcCYy5ekIw5eYEQxFeK7WTNrNt1P09ay6VDOOgIRM1m4dQKFmeJ6B2ks/1ei0 qcQicp8Et4rlG/4peYMH =Ksoa -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L--