From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.96.42.35 with SMTP id k3csp52293qdl; Tue, 28 Jan 2014 13:22:52 -0800 (PST) X-Received: by 10.182.102.134 with SMTP id fo6mr2847812obb.10.1390944171852; Tue, 28 Jan 2014 13:22:51 -0800 (PST) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id iz10si7730001obb.104.2014.01.28.13.22.51 for ; Tue, 28 Jan 2014 13:22:51 -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 94064263085; Tue, 28 Jan 2014 21:22:52 +0000 (UTC) Received: from mail-ve0-f176.google.com (mail-ve0-f176.google.com [209.85.128.176]) by rubyforge.org (Postfix) with ESMTP id 4C0D4263063 for ; Tue, 28 Jan 2014 21:21:50 +0000 (UTC) Received: by mail-ve0-f176.google.com with SMTP id oz11so640578veb.35 for ; Tue, 28 Jan 2014 13:21:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=bGm1j7kLtQlJdnUf3mGjiqMsG1cvktmdNcUUB4UETIU=; b=DpkZILpMzwQRVOkFw2uyNWT70Dm5HEwVyhE/F00nfhlu4ucSjnIYlBQMB1kJBzoMRu UnJqq7MdEF9Xty2qiDTuA9394g5d5TSHhYwbqXn/blBwpwoAkpHI66+Q5DFe4Yu9JwG7 paXoJY2BAf7pALKrQ8s/VwjZLZ9rXh3E4qQaBlu9Z5bNOcg6pLFSLPdLo+hjh9V8VgyS V5F54qyn2dcGnNGVMdaqGIs4OsABHyM0Fo09835TYorryHrIl/1FRDE/88mlvRtJH/SV 9/jm4Ucnfr8Nn64NhPCE+WovA/fOBQqyXUe77hmkvkcEjDQowUCBHo8HgN9Z06Xn4Xag DOew== MIME-Version: 1.0 X-Received: by 10.52.89.230 with SMTP id br6mr2485540vdb.20.1390944108585; Tue, 28 Jan 2014 13:21:48 -0800 (PST) Received: by 10.220.187.8 with HTTP; Tue, 28 Jan 2014 13:21:48 -0800 (PST) In-Reply-To: <1390895256-sup-521@qwerzila> References: <1390895256-sup-521@qwerzila> Date: Tue, 28 Jan 2014 22:21:48 +0100 Message-ID: From: Per Andersson To: Sup developer discussion Subject: Re: [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 On Tue, Jan 28, 2014 at 8:55 AM, Gaute Hope wrote: > Excerpts from Per Andersson's message of 2014-01-28 02:18:35 +0100: >> 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? > > Where is upstream for this, I'm not sure if I am following you? The only > active fork of ncurses-ruby (ncursesw-ruby) that I can find is ours - > which is now known as 'ncursesw' in gem world (ncursesw-sup has been > removed). It was late when I wrote this. What I mean, but did not manage to put in writing, is that the rmail-sup gem carries the same functionality. And my suggestion was that we adopt active maintainership of rmail. Sorry for the total confusion, I was tired... >> 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 >> > > If you are up for it, that would be good, we might as well push directly > to RMail (and drop rmail-sup). I suggest you contact Matt and we migrate > the rmail-sup repoistory in sup-heliotrope (at github) to use the rmail > namespace. If he wants, we could also just move his repository to the > sup-heliotrope organization. I'll contact Matt and ask! > Please also make sure that the other maintainers of sup are > owners of the rmail gem so that it is not all dependant on one person. Absolutely! Best, Per _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel