From owner-freebsd-ports@FreeBSD.ORG Thu Jul 16 20:45:02 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B4B7106564A for ; Thu, 16 Jul 2009 20:45:02 +0000 (UTC) (envelope-from carpetsmoker@rwxrwxrwx.net) Received: from smtp-vbr6.xs4all.nl (smtp-vbr6.xs4all.nl [194.109.24.26]) by mx1.freebsd.org (Postfix) with ESMTP id 9814E8FC14 for ; Thu, 16 Jul 2009 20:45:01 +0000 (UTC) (envelope-from carpetsmoker@rwxrwxrwx.net) Received: from roundcube.xs4all.nl (roundcube3.xs4all.nl [194.109.20.199]) by smtp-vbr6.xs4all.nl (8.13.8/8.13.8) with ESMTP id n6GKPmTZ097587; Thu, 16 Jul 2009 22:25:57 +0200 (CEST) (envelope-from carpetsmoker@rwxrwxrwx.net) MIME-Version: 1.0 Received: from tournoij.xs4all.nl [83.161.253.7] with HTTP/1.1 (POST); Thu, 16 Jul 2009 22:25:48 +0200 Date: Thu, 16 Jul 2009 22:25:48 +0200 From: Martin Tournoij To: Charlie Kester In-Reply-To: <20090716181711.GC90253@comcast.net> References: <20090706014719.GG11993@lonesome.com> <070151759cb2aacd36a14eb4b318a435@xs4all.nl> <20090716181711.GC90253@comcast.net> Message-ID: <24f340e05fad661d8fac226ce6e9d801@xs4all.nl> X-Sender: carpetsmoker@rwxrwxrwx.net (uyktHlVU1YmNxSP/KKwQnOAPqXXD6BBu) User-Agent: XS4ALL Webmail Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-ports@freebsd.org Subject: Re: status of FreeBSD ports you maintain as of 20090705 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: carpetsmoker@rwxrwxrwx.net List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2009 20:45:02 -0000 On Thu, 16 Jul 2009 11:17:11 -0700, Charlie Kester wrote: > On Wed 15 Jul 2009 at 14:08:18 PDT Martin Tournoij wrote: >>On Sun, 5 Jul 2009 20:47:19 -0500, linimon@FreeBSD.org wrote: >>> I have noticed some maintainer-timeouts on ports that you maintain. >>> Please let me know if you are still interested in these ports; >>otherwise, >>> I would like to reassign them. Thanks. >>> >>> mcl >>> >>> audio/mpdscribble carpetsmoker@rwxrwxrwx.net 1 >>> x11-wm/pekwm carpetsmoker@rwxrwxrwx.net 2 >> >>Hi there, >> >>I would like to maintain these ports, but unfortunately I haven't had the >>time >>in the last few months. And not having a X11-enabled FreeBSD machine >>installed >>doesn't help either... >> >>I thought about it during the last week, and will resign the >>maintainership of >>all my ports in the coming weeks, (For a few ports I have a few changes/ >>updates in the pipeline I would like to finish). >> >>So it's Ok to reassign these ports. > > Judging by your followups, Martin, there seems to be some confusion > about which ports you're relinquishing at this time. > > Was your OK meant to apply only to the mpdscribble and pekwm ports? And > your mention of your other ports was only a heads-up that you intend to > be resigning maintainership in the near future, after submitting some > final changes? Yep, that was it (See below). > Just trying to clarify the situation. It's good to see that there are > volunteers ready to take over once you're done Indeed, thanks to everyone. I would like to pass on maintainership of all my ports, most ports I maintain are X11 based and I don't really use FreeBSD with X11 anymore nowadays (Due to crappy Xorg ``releases'' if you can call 'em that, OpenBSD works much better for me ATM). However, I don't want to pass maintainership *right now*, for example, I have spent quite some time a few months ago improving the audio/csound port, and this afternoon I spent some time making final adjustments and some (hopefully useful) instructions for the new maintainer. I guess all of this can also be done after maintainership is passed, but my idea was that people would call out that they were willing to maintain a port, that I would make final adjustments (if any), and then submit a PR with the adjustments and maintainer change. Sorry if I wasn't too clear, I just assumed this must be standard procedure ... Regards, Martin