From owner-freebsd-questions@FreeBSD.ORG Wed Oct 24 00:03:01 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 29AD816A420 for ; Wed, 24 Oct 2007 00:03:01 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id 2088913C4AC for ; Wed, 24 Oct 2007 00:03:01 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from localhost (jn@ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id l9O02bPQ060128; Tue, 23 Oct 2007 20:02:38 -0400 (EDT) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-questions@freebsd.org Date: Tue, 23 Oct 2007 20:02:16 -0400 User-Agent: KMail/1.9.7 References: In-Reply-To: X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710232002.17866.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Aliya Harbouri 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:03:01 -0000 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). JN