From: Iain Parris <ipv2.lst@parris.org>
To: supmua@googlegroups.com
Cc: Dan Callaghan <djc@djc.id.au>, Gaute Hope <eg@gaute.vetsj.com>
Subject: sup is up
Date: Sun, 14 Jun 2020 23:08:31 +0100 [thread overview]
Message-ID: <1592168780-sup-6450@ceres> (raw)
Greetings fellow Suppers,
tl;dr - sup had become inactive and unmaintained. But it still has kept
a cult following of delighted users over the years (source: I am one!),
and it is now going to be maintained again.
This mailing list has been inactive for a long time.
<supmua@googlegroups.com> for the "sup" mail client,
<https://sup-heliotrope.github.io/>.
I would first like to say a huge thank you to all of the sup
contributors over the years, and in particular special thanks to William
Morgan (original creator) and Gaute Hope (took over most maintenance in
2013, though now has a focus on notmuch/astroid - different email client
ecosystem, and all originally inspired by sup).
I am a long-time very happy sup user. It has been my primary mail client
for over 11 years.
I found out a few days ago that sup was no longer being maintained,
after spotting that the "sup-mail" package had disappeared in the latest
Ubuntu release (focal, 20.04 LTS).
I contacted Gaute Hope (@gauteh on GitHub, previous maintainer) and Dan
Callaghan (@danc86 on GitHub, owner of the most recently active sup fork
on GitHub).
After discovering each other and realising we aren't the only people
interested in keeping sup going, Dan and I have volunteered to maintain
sup once more, and Gaute has very kindly facilitated passing on the
baton. A huge *thank you* again to both of you, Dan and Gaute.
To be upfront about goals, however: Dan & I are looking to be extremely
conservative with respect to new features. We are interested in fixing
what's broken, and keeping it fixed, rather than adding new features.
This is because we are both long-time very happy users with the existing
feature set. We aren't presently seeking new feature development, or to
accept PRs for new features.
The current tentative plan is:
(0) Fix failing Travis CI build. Done. The build is now green again
for the first time in five years, and sup has its first recent commits:
<https://github.com/sup-heliotrope/sup/commits/develop>.
(1) Incrementally modernise the build. Likely to require applying
incremental code fixes. For example, we would like to officially
support all current Ruby versions (2.5, 2.6, 2.7). See:
<https://github.com/sup-heliotrope/sup/issues/552>.
(2) Update documentation, e.g., to remove the "no longer maintained"
notice, fix broken links, and provide up-to-date installation
information for the most common distributions.
(3) Create a new 0.23 release of sup - the first release since
0.22.1 five years ago (2015-06-18). To be released on GitHub and
published as a new version of the "sup" Ruby gem,
<https://rubygems.org/gems/sup>.
(4) Collaborate with major downstream packagers, for example perhaps
(not a definitive list):
- Debian & Ubuntu (apt)
- Fedora (yum)
- MacPorts?
Interested? Comments? Thoughts? Ideas? Suggestions? It would be
*wonderful* to hear from you all. I'm sure there are many other happy
users out there, and this list is for the community as well as for
development. :-)
Do feel free to reply here on this mailing list, and/or to contribute in
any other way (pull requests, GitHub issues, or any other way!).
Dan, Gaute - I hope I have accurately summarised our conversations.
Would you like to add anything? :-)
Brief pointers:
- sup on GitHub: <https://github.com/sup-heliotrope/sup>
- This mailing list: <supmua@googlegroups.com>
- Mailing list archives: <https://groups.google.com/d/forum/supmua>
- Dan Callaghan <djc@djc.id.au>, @danc86 <https://github.com/danc86>
- Iain Parris <ipv2.lst@parris.org>, @IPv2 <https://github.com/IPv2>
(Admin info: Gaute has now setup Dan with access to sup on GitHub, the
sup gem on RubyGems, and this mailing list.)
Kind regards,
Iain
next reply other threads:[~2020-06-14 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 22:08 Iain Parris [this message]
2020-06-15 6:57 ` Gaute Hope
2020-06-16 7:31 ` Dan Callaghan
2020-06-21 8:51 ` [sup] " Matthieu Rakotojaona
2020-06-21 12:48 ` Iain Parris
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=1592168780-sup-6450@ceres \
--to=ipv2.lst@parris.org \
--cc=djc@djc.id.au \
--cc=eg@gaute.vetsj.com \
--cc=supmua@googlegroups.com \
/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