From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.96.86.234 with SMTP id s10csp152225qdz; Mon, 27 Jan 2014 17:41:46 -0800 (PST) X-Received: by 10.60.246.104 with SMTP id xv8mr23788166oec.18.1390873305815; Mon, 27 Jan 2014 17:41:45 -0800 (PST) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id w10si6208910obo.69.2014.01.27.17.41.45 for ; Mon, 27 Jan 2014 17:41:45 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-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-devel-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (bad format) header.i=@gmail.com; dmarc=fail (p=NONE dis=NONE) header.from=gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 5F3B42E1CC; Tue, 28 Jan 2014 01:41:45 +0000 (UTC) X-Greylist: delayed 1072 seconds by postgrey-1.31 at rubyforge; Tue, 28 Jan 2014 01:41:32 UTC Received: from mail-ve0-f175.google.com (mail-ve0-f175.google.com [209.85.128.175]) by rubyforge.org (Postfix) with ESMTP id E77C42E190 for ; Tue, 28 Jan 2014 01:41:32 +0000 (UTC) Received: by mail-ve0-f175.google.com with SMTP id c14so3956255vea.20 for ; Mon, 27 Jan 2014 17:41:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=zVJ8K1jpasR93YTFChhSc8Ohrf8V24zOnzNNOoW9468=; b=HkvZtTpB8ZHG0gR6I0OazJScJwJYjW0wU9B3QFqEPLYCXK7+GIOAh3n7O8QYhNHcZa 39JCbP2yrf6ICcfvn/c0gDHmeOHQtopgArFKX/Jnr0nOejzK/GJQ13Kk51sd8gcYWeMg /PPjntLK/Wx8GqTGe3km+bUoBcRUwkbKR1/2oE2OmMKUyj1VzFAIlDKi7NBo6jBrqf0g AxQVkcCJSRjErSxJXrWhLKn+dbrqhKwKO939AO09X1nfn+cC+vz8OrVF13K1IHqW+Gka sRYp8axTdr52PUI+LWG1wLQxMykIXI0/2QJZIsAiBjBOEl3p94gMFTB6y3oW87EkhuRy tTqQ== MIME-Version: 1.0 X-Received: by 10.52.110.201 with SMTP id ic9mr167207vdb.22.1390871915471; Mon, 27 Jan 2014 17:18:35 -0800 (PST) Received: by 10.220.187.8 with HTTP; Mon, 27 Jan 2014 17:18:35 -0800 (PST) Date: Tue, 28 Jan 2014 02:18:35 +0100 Message-ID: From: Per Andersson To: sup-devel@rubyforge.org Subject: [sup-devel] Rubymail maintainership 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: , 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! I am the Debian maintainer for sup. Recently Sup developers adopted ncursesw-ruby (the ncursesw gem) and became the new upstream for that. (Instead of having a fork.) Since a few days ago the original upstream now carries the exact same functionality. Is there any reason for carrying a fork of this any longer? I understand that the in the future a migration away from rmail is planned. In the meantime, using rmail gem, could reduce complexity. Perhaps a similar move as with ncursesw-ruby can be made, adopting active maintainership? (I can volunteer for this!) As Matt states, rubymail is looking for active maintainership https://github.com/matta/rubymail/pull/2#issuecomment-33173575 -- Per _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel