From owner-freebsd-ports@FreeBSD.ORG  Fri Mar 14 11:18:29 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A28F8EC8;
 Fri, 14 Mar 2014 11:18:29 +0000 (UTC)
Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 78DC9A6E;
 Fri, 14 Mar 2014 11:18:29 +0000 (UTC)
Received: from [192.168.0.20] (unknown [130.255.19.191])
 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by shepard.synsport.net (Postfix) with ESMTP id 8DBFD438BC;
 Fri, 14 Mar 2014 06:18:11 -0500 (CDT)
Message-ID: <5322E563.5030009@marino.st>
Date: Fri, 14 Mar 2014 12:17:55 +0100
From: John Marino <freebsd.contact@marino.st>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "A.J. 'Fonz' van Werven" <freebsd@skysmurf.nl>, marino@freebsd.org
Subject: Re: FreeBSD ports you maintain which are out of date
References: <201403140915.s2E9Fa8I009565@portscout.freebsd.org>
 <5322CB0E.7000908@marino.st> <20140314093036.GB17905@tuxaco.net>
 <5322DE4E.7090200@marino.st> <5322DEE3.6030604@marino.st>
 <20140314110830.GA88914@spectrum.skysmurf.nl>
In-Reply-To: <20140314110830.GA88914@spectrum.skysmurf.nl>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ports@freebsd.org,
 =?ISO-8859-1?Q?Philippe_Aud=E9oud?= <jadawin@FreeBSD.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: marino@freebsd.org
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Mar 2014 11:18:29 -0000

On 3/14/2014 12:08, A.J. 'Fonz' van Werven wrote:
> John Marino wrote:
> 
>> I wanted to suggest that maybe portscout can not send any notice to
>> ports@ by rule if the port is unmaintained.
> 
> On the other hand, seeing that a certain port is unmaintained might be an
> incentive for someone to pick it up. Apparently it's just this doomsday
> game that nobody seems to care for ;-)

we get periodic summaries of all broken and deprecated reports.  I don't
see why that approach can be extended to this, e.g. "unmaintained
reports with available updates".

Once a month to cover every port like this is okay.  The current
approach of spamming per port on every change is not really okay.

John