From: Per Andersson <avtobiff@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Rubymail maintainership
Date: Tue, 28 Jan 2014 22:21:48 +0100 [thread overview]
Message-ID: <CABYrXSRPLdBt4ba2H1qCV83-AaP4_fj0Md4QWgS_Fe58B-02UA@mail.gmail.com> (raw)
In-Reply-To: <1390895256-sup-521@qwerzila>
On Tue, Jan 28, 2014 at 8:55 AM, Gaute Hope <eg@gaute.vetsj.com> 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
next prev parent reply other threads:[~2014-01-28 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 1:18 Per Andersson
2014-01-28 7:55 ` Gaute Hope
2014-01-28 21:21 ` Per Andersson [this message]
2014-01-29 8:59 ` Gaute Hope
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABYrXSRPLdBt4ba2H1qCV83-AaP4_fj0Md4QWgS_Fe58B-02UA@mail.gmail.com \
--to=avtobiff@gmail.com \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox