From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.236.136 with SMTP id uu8csp98908vdc; Sat, 13 Apr 2013 08:48:59 -0700 (PDT) X-Received: by 10.229.93.71 with SMTP id u7mr6103434qcm.44.1365868138926; Sat, 13 Apr 2013 08:48:58 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id m6si4846058qct.29.2013.04.13.08.48.58; Sat, 13 Apr 2013 08:48:58 -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; dkim=neutral (bad format) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 6306F2E0FB; Sat, 13 Apr 2013 15:48:59 +0000 (UTC) X-Greylist: delayed 74993 seconds by postgrey-1.31 at rubyforge; Sat, 13 Apr 2013 15:43:09 UTC Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) by rubyforge.org (Postfix) with ESMTP id 678862E0F0 for ; Sat, 13 Apr 2013 15:43:09 +0000 (UTC) Received: by mail-ie0-f169.google.com with SMTP id ar20so4057102iec.0 for ; Sat, 13 Apr 2013 08:43:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:from:to:subject:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; bh=pGc/2cRpQpxK8qLz+2CwiY/22hs7sXzvHU8p330I4UI=; b=mMajVJw7BPKqK+HN5Q9GzqnkrPAvJXhkyRmjUK21Htm5v+D74Ng0fBPGafK2yre9Pe R+yATGQqr4gMDKgfjkaZAXjO4iw0lXI0uKDwgAb/77B0LakJ3yD/aDDJqzzk6mtLp7n4 hOPfsIBY03Dj1F6zx/EVj4uZmwrDAAScCAazrDZkoPK7xE+cCAgYU3adcFfbUQTLVGPK o+Psjrm2dTb1AnPHWGaILUlgLVYpf0ToOQJaE6AAeQt34O0bScvl/uZhxjWkciqNK9FN g6aM9G5NNZFstg9L3ShNiVpQ6mSeN0VvhLQpxjyPdQqvPMnEhg6mzgm4bP4X+WREuSGC eJ3Q== X-Received: by 10.50.173.6 with SMTP id bg6mr1645279igc.102.1365867788087; Sat, 13 Apr 2013 08:43:08 -0700 (PDT) Received: from localhost (dsl-173-206-13-123.tor.primus.ca. [173.206.13.123]) by mx.google.com with ESMTPS id hi4sm3501758igc.6.2013.04.13.08.43.04 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sat, 13 Apr 2013 08:43:06 -0700 (PDT) From: Steven Hum To: sup-talk In-reply-to: <51695DA4.4030906@gaute.vetsj.com> References: <51692285.8000709@gaute.vetsj.com> <20130413124946.GA22905@kpad.otokar.looc2011.eu> <51695DA4.4030906@gaute.vetsj.com> Date: Sat, 13 Apr 2013 11:42:45 -0400 Message-Id: <1365867255-sup-1309@luna> User-Agent: Sup/git Subject: Re: [sup-talk] sup: Fix for an UndefinedMethodError 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 I was thinking the same, that it may be time for a sup2 repository. This is very premature, but are there any thoughts to integrate some of the work done in the sup forks. I am thinking in particular of the imap work ezyang did -- I adopted his fork as he seemed to be the most active with regards to imap folder handling, notably propagating updates. It would be nice to consolidate the features many of these forks addressed.. though, I have no idea how this can be easily facilitated. Regards, Steven Excerpts from Gaute Hope's message of 2013-04-13 09:29:08 -0400: > On 13. april 2013 14:49, Matthieu Rakotojaona wrote: > > I guess it's also the occasion to think about the mailing list. I guess > > no one has the rights on this one ? I don't see anything in github for > > this functionality. > > > Yup - maybe its time for 'sup2' - from rubyforge: > > http://rubyforge.org/docman/view.php/5/460/faq.html#abandoned > > Project xyz seems to be abandoned. Can you pass it to me? > > This comes up occasionally - a well-named or positioned project gets > started, then the project admin falls out of sight and can't be reached. > Patches pile up, people start wondering what's going on, and it seems a > shame to lose the project name by forking it. So someone will ask if we > as RubyForge admins will pass over control of the project to them. > > We really, really, hesitate to transfer admin privileges from one person > to another, even if the original admin has completely disappeared. I > suspect there are legal complications, and we don't have the budget to > deal with those. Furthermore, suppose the original admin has been off on > furlough for a year and comes back to find that his project has been > moved away from him. Not a pleasant situation. > > In situations where the project admin can't be reached for a long time > and folks want to move forward, I suggest forking the project. You're > welcome to host a xyz2 version of project xyz on RubyForge, and if the > original admin ever shows up again and wants to hand over the project to > you, we can help facilitate that. -- "Truth or die." Steven Hum 5 - 28 Gilmour St Ottawa, ON K2P 0N3 email sdothum@gmail.com tel 613.237.9058 _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk