From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost ([128.39.46.106]) by mx.google.com with ESMTPSA id 8sm584485eef.1.2014.01.29.01.00.05 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Jan 2014 01:00:05 -0800 (PST) From: Gaute Hope To: sup-devel Subject: Re: [sup-devel] Rubymail maintainership In-reply-to: References: <1390895256-sup-521@qwerzila> Date: Wed, 29 Jan 2014 09:59:20 +0100 Message-Id: <1390985761-sup-8931@qwerzila> User-Agent: Sup/git Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=-1390985960-482087-31734-2736-1-=" --=-1390985960-482087-31734-2736-1-= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Excerpts from Per Andersson's message of 2014-01-28 22:21:48 +0100: > 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 sam= e > >> functionality. Is there any reason for carrying a fork of this any l= onger? > > > > Where is upstream for this, I'm not sure if I am following you? The o= nly > > 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 i= n > 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 p= lanned. > >> 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 direc= tly > > to RMail (and drop rmail-sup). I suggest you contact Matt and we migr= ate > > the rmail-sup repoistory in sup-heliotrope (at github) to use the rma= il > > 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! Sounds good! If Matt agrees to make us maintainers, but wants to retain the original repo, we can just rename the rmail-sup repo to rubymail and revert the gemspec changes. - gaute --=-1390985960-482087-31734-2736-1-= Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJS6MLoAAoJEJgnp+igdJAjxuoQAISS3zCx/LHwWCYbvJjwWvBV b8OcUYregXIlN9AnKVq9lYtQlpOTuqwTw44HRd+h/HP3mTsx+6lL3/oc75GqSB+K VHGLIvbkwYYGYnYeFWXyAZxd+kgze5Kw2Q0LOWSqVG+ZHBUzj1IJua7s63zvOJfV SjfVh7kcSRdVxO6EWWPe/4WlIJGRdekr6s5vgqMnv8tlRnklxnMsPBJs5RBxSV+b gK7nJiElNOuaqjdQMp4KDgdy9u2RoLyOKHnMcv+QZ3NQ6hHTUyywDRJZ1NN0HLcX Rtjw5bd91TvLK5HIzTc7M1bj/KnMEWTOsXfS8zlNpIKsF7ZLX4PnREpiNEHXVMO1 HMk8Auhw6e6x+eLVQb7Hstn/Pge0Mt0igmJGD6tl0cVZ5ymeldm5N9SEG0hxTSLX t/mA4Lr8Iu7WVvemmd870VurGIvEie6Ymp7CWKTADk6Kq3v5pY2qWM1Yzr7mxS+v Bpq1Gbaxw+Trmke5wv7qulwiJTZkvyd3qO5wWZehegP42F9gF/cgWONDhBIDGIEv K8Q1WCt7uiwgede3tYKToUBrqM7dCf6KiHfrCtN065KKtkMieCFEycuRuFQdx2fT H2dqOoJVxV2f/BJwwcKpTcb6AIZckFETBo6op4aNN7hduEbJtq7sPueVrySyUx5E d10WCOlPIqFI0rwzLTQH =oHcm -----END PGP SIGNATURE----- --=-1390985960-482087-31734-2736-1-=--