From owner-freebsd-questions@FreeBSD.ORG Wed Oct 24 00:20:09 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABB8616A41B for ; Wed, 24 Oct 2007 00:20:09 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id 6348913C4B0 for ; Wed, 24 Oct 2007 00:20:09 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from working (c-71-60-127-199.hsd1.pa.comcast.net [71.60.127.199]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTP id 12E8CEBC3C; Tue, 23 Oct 2007 20:11:54 -0400 (EDT) Date: Tue, 23 Oct 2007 20:11:53 -0400 From: Bill Moran To: John Nielsen Message-Id: <20071023201153.e8354485.wmoran@potentialtech.com> In-Reply-To: <200710232002.17866.lists@jnielsen.net> References: <200710232002.17866.lists@jnielsen.net> X-Mailer: Sylpheed 2.4.7 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Aliya Harbouri , freebsd-questions@freebsd.org Subject: Re: the right next step? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2007 00:20:09 -0000 John Nielsen wrote: > > On Tuesday 23 October 2007, Aliya Harbouri wrote: > > Hi everybody! > > > > If we've > > > > i) raised a question about a port on this list > > ii) sent an email to the port maintainer > > iii) filed a pr > > iv) waited ~ a month, then followed-up the pr > > > > and there's still no communication / action, what's the right next > > step? Is there a different list to communicate to/on for follow-up? > > Does your PR include a fix? > > If it does, make some noise about it on the freebsd-ports mailing list and > include the PR number and the fact that you've not heard back from the > maintainer. > > If it doesn't, you might still want to bring it up on -ports, but getting it > fixed depends on someone volunteering to take ownership of the problem (if > not outright maintainership of the port). Note also that a ports freeze is starting soon for 7.0 and 6.3 release. During the freeze, you'll have difficulty getting any ports changes through. -- Bill Moran http://www.potentialtech.com