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).

> 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.

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.

Cheers, Gaute