From: Per Andersson <avtobiff@gmail.com>
To: sup-devel@rubyforge.org
Subject: [sup-devel] Rubymail maintainership
Date: Tue, 28 Jan 2014 02:18:35 +0100 [thread overview]
Message-ID: <CABYrXSSE59VMtSg+Eze0m2P1Tx0XCN3zxVO+q3oJzgPOc4XFxw@mail.gmail.com> (raw)
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
next reply other threads:[~2014-01-28 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 1:18 Per Andersson [this message]
2014-01-28 7:55 ` Gaute Hope
2014-01-28 21:21 ` Per Andersson
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=CABYrXSSE59VMtSg+Eze0m2P1Tx0XCN3zxVO+q3oJzgPOc4XFxw@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