From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.229.71 with SMTP id jh7cs46517icb; Mon, 24 Jan 2011 10:42:11 -0800 (PST) Received: by 10.213.34.11 with SMTP id j11mr5410463ebd.54.1295894526606; Mon, 24 Jan 2011 10:42:06 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id c41si14663332vcs.160.2011.01.24.10.42.06; Mon, 24 Jan 2011 10:42:06 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 174771858317; Mon, 24 Jan 2011 13:42:06 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 3D0281858317 for ; Mon, 24 Jan 2011 13:40:50 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1PhRLN-0003tY-VR; Mon, 24 Jan 2011 13:40:50 -0500 From: William Morgan To: sup-devel , sup-talk@rubyforge.org Date: Mon, 24 Jan 2011 13:40:49 -0500 Message-Id: <1295894044-sup-7965@masanjin.net> User-Agent: Sup/git Subject: [sup-devel] call for new maintainers X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org I said this in another thread on sup-devel, but I thought I'd give it a broader audience. Rich is stepping down as maintainer due to lack of time (but will still be around as a contributor). I personally have a little more time nowadays than I did before. But I would rather spend it working on features, including possible a new index backend. So, anyone who would be interested in the maintainership busywork of collecting patches from sup-devel, making branches, and pushing releases, please let me know. You must be familiar with git, Ruby and, of course, Sup. I can provide a brief guide of how this all works. In exchange, you will have access to the secret Sup maintainer meetings that take place in the smoky backrooms of various San Francisco bars. If multiple people are interested, we can set up a rotation so that no one is stuck with it forever. If no one responds, I will continue to be your (not very responsive) maintainer. -- William _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel