From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.236.136 with SMTP id uu8csp22454vdc; Sat, 20 Apr 2013 20:58:50 -0700 (PDT) X-Received: by 10.236.191.33 with SMTP id f21mr14428403yhn.119.1366516729773; Sat, 20 Apr 2013 20:58:49 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id 67si6515441yhn.133.2013.04.20.20.58.48; Sat, 20 Apr 2013 20:58:49 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 758C42E0FC; Sun, 21 Apr 2013 03:58:48 +0000 (UTC) X-Greylist: delayed 1587 seconds by postgrey-1.31 at rubyforge; Sun, 21 Apr 2013 03:58:31 UTC Received: from masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id E924B2E0C0 for ; Sun, 21 Apr 2013 03:58:31 +0000 (UTC) Received: from w by masanjin.net with local (Exim 4.71) (envelope-from ) id 1UTlCq-0006mV-O3 for sup-talk@rubyforge.org; Sun, 21 Apr 2013 03:44:48 +0000 From: William Morgan To: sup-talk Date: Sat, 20 Apr 2013 20:31:35 -0700 Message-Id: <1366514503-turnsole-37382@cugel> User-Agent: turnsole, a heliotrope client v.git Subject: [sup-talk] what can i help with? X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup 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-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hi folks, My sincere apologies for the complete and utter abandonment of Sup and Heliotrope. It's a constant source of emotional distress to me, but I do not have time to do anything with these projects any more. (Including monitoring this mailing list, which long ago fell victim to an overly-aggressive filtering rule.) I apologize. But I'm thrilled to see that there is enough community momentum to keep things going. I'd love to enable this as best I can. What is the list of things you need from me to take over maintenance of Sup? 1. Add some new owners to the sup gem. (Who?) 2. Add some administrators to the Rubyforge page. (Who?) 3. What else? -w _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk