From owner-freebsd-ports@FreeBSD.ORG Wed Nov 28 19:07:01 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 DBC096E2 for ; Wed, 28 Nov 2012 19:07:01 +0000 (UTC) (envelope-from yerenkow@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 601CB8FC0C for ; Wed, 28 Nov 2012 19:07:01 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id 12so1742858wgh.31 for ; Wed, 28 Nov 2012 11:06:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PeTbRoJKVBs7bo8e9gbQRYa/0wz3Y99MWUMzq/sQSwQ=; b=y0NKmv9KiB+ygnsPtZftC2Idx80NOI4D1IBavwdFVmW9flVseYLYzPPOT7hyIhzSGZ GoOiOTUnMbLLtYcrj5HN2CODX4Phqf2cN3dGwDTZbMp9ZrFijJj0RWJYO85NcZZEPoUZ t9JnWHqq01n3EQKUUYzzQrlmgodb3WVa2Fnx8PVFiZQiqnfO9BExitl0yyhy2SDQ4zjY MBMT7tCS+dfGU9QjFBoXiN6RrZW94+9bDU3kQps5mU2rExmmZ/OflRqc22Kc+kBj/k8w yuWW2ARihlzR9wMO9OITRMF1VJdCZ85polgfgdFxcUtGcTX396ZwjVS4TfaBSn+88Fsd UYzQ== MIME-Version: 1.0 Received: by 10.180.78.161 with SMTP id c1mr31334900wix.4.1354129619587; Wed, 28 Nov 2012 11:06:59 -0800 (PST) Received: by 10.194.40.131 with HTTP; Wed, 28 Nov 2012 11:06:59 -0800 (PST) In-Reply-To: References: <201211271554.qARFs9un067018@null.zi0r.com> <50B4E664.6030606@filez.com> <50B56392.9060506@ShaneWare.Biz> <31BBFCB108C82225ADF20511@utd71538.campus.ad.utdallas.edu> Date: Wed, 28 Nov 2012 21:06:59 +0200 Message-ID: Subject: Re: FreeBSD ports you maintain which are out of date From: Alexander Yerenkow To: Kevin Oberman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: ports@freebsd.org, Paul Schmehl , portscout@portscout.zi0r.com, Shane Ambler , Radim Kolar 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: Wed, 28 Nov 2012 19:07:02 -0000 2012/11/28 Kevin Oberman > On Wed, Nov 28, 2012 at 7:45 AM, Alexander Yerenkow > wrote: > > In that case, near each port should be.mntr contact mentioned, to.make it > > easier for anyone to contact mntr immediately, instead making additional > > 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. > Not exactly :) My suggestion about including current maintainer contact info was about this part of discussion: >>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 else 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. 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. > -- > R. Kevin Oberman, Network Engineer > E-mail: kob6558@gmail.com > -- Regards, Alexander Yerenkow