From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.86.59.13 with SMTP id h13cs203015fga; Thu, 25 Feb 2010 06:53:11 -0800 (PST) Received: by 10.224.118.146 with SMTP id v18mr956355qaq.200.1267109590982; Thu, 25 Feb 2010 06:53:10 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 13si4127425qyk.76.2010.02.25.06.53.10; Thu, 25 Feb 2010 06:53:10 -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 7153018582C2; Thu, 25 Feb 2010 09:53:10 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 32F1318582DC for ; Thu, 25 Feb 2010 09:51:55 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1Nkf4F-0000jz-Mm for sup-devel@rubyforge.org; Thu, 25 Feb 2010 09:51:55 -0500 From: William Morgan To: sup-devel mailing list Date: Thu, 25 Feb 2010 09:51:55 -0500 Message-Id: <1267109223-sup-351@masanjin.net> User-Agent: Sup/git Subject: [sup-devel] sup for sale 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 Hi all, As has probably become painfully obvious to you all, my motivation for developing and maintaing Sup has been waning over the past year. I use Sup every day as my primary email client, so its bugs, problems and misfeatures irritate me every day. This provides just enough motivation for the current glacial pace of maintainership, which I'm happy to continue doing. Sup will not die so long as I am around to use it. But if someone wants to take the ball and be an official maintainer, I will give you my blessing and the power to gem push new releases. You don't even have to maintain my current crazy branching scheme! Otherwise, things will continue as they do now. -- William _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel