From owner-freebsd-ports@FreeBSD.ORG  Fri Apr 17 15:51:32 2009
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2F6381065687
	for <ports@freebsd.org>; Fri, 17 Apr 2009 15:51:32 +0000 (UTC)
	(envelope-from mark@foster.cc)
Received: from QMTA12.emeryville.ca.mail.comcast.net
	(qmta12.emeryville.ca.mail.comcast.net [76.96.27.227])
	by mx1.freebsd.org (Postfix) with ESMTP id 1B0928FC12
	for <ports@freebsd.org>; Fri, 17 Apr 2009 15:51:32 +0000 (UTC)
	(envelope-from mark@foster.cc)
Received: from OMTA11.emeryville.ca.mail.comcast.net ([76.96.30.36])
	by QMTA12.emeryville.ca.mail.comcast.net with comcast
	id gcBZ1b0090mlR8UACfeNSa; Fri, 17 Apr 2009 15:38:22 +0000
Received: from [10.2.1.101] ([216.254.13.253])
	by OMTA11.emeryville.ca.mail.comcast.net with comcast
	id gfeD1b0055TbLEG8XfeFcX; Fri, 17 Apr 2009 15:38:20 +0000
Message-ID: <49E8A264.7000001@foster.cc>
Date: Fri, 17 Apr 2009 08:38:12 -0700
From: Mark Foster <mark@foster.cc>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: ports@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Re: ports/132800: vuxml submission for net-im/ejabberd
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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, 17 Apr 2009 15:51:32 -0000

I'm following up regarding this apparent maintainer timeout. It's not my 
intention to place blame, but to me it is unacceptable that important 
security (vuxml) updates are sometimes blocked by unresponsive 
maintainers. It is not in the best interest of the users or FreeBSD to 
let these things slip.

The vuxml updates should be reviewed & committed without waiting on the 
maintainer of the port. Perhaps a simple non-blocking heads-up (Cc:) to 
the maintainer is more appropriate. Once publicized, the security 
notifications (via portaudit) become known to a wider, targetted 
audience. This establishes an important feedback loop as opposed to 
keeping the problem a "secret", since the users are more likely to 
either nudge the maintainer for an update to the port or submit one (via 
send-pr) themselves.

-- 
I hate rascists.
Mark D. Foster <mark@foster.cc>  
http://mark.foster.cc/ | http://conshell.net/