From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Getting ready for sup-0.13
Date: Sun, 28 Apr 2013 20:23:29 +0200 [thread overview]
Message-ID: <517D6921.3050006@gaute.vetsj.com> (raw)
Greetings list,
William has graciously given us access to the rest of the Sup
infrastructure and the plan is to move as much as possible to GitHub.
At the moment we are three maintainers: Hamish Downer, Matthieu
Rakotojaona and myself.
There are three categories for the sup repository team:
Owner, Commiter, Contributor. Pretty much any kind of contribution would
mean we would add you to the contributor team if you asked to be.
The plan for sup is:
Release sup-0.13 relatively soon:
- including the last bugfixes otherwise leave out the major changes
that have been discussed lately
And the proposed roadmap for sup-0.14:
- support ruby 2.0.0
- migrate to psych
- remove all deprecated and abandoned dependencies (e.g. switch from
RMail to Mail)
- implement IMAP syncback support
- get uft-8 encoding right
We have documented this setup and the roadmap in the wiki at:
-
https://github.com/sup-heliotrope/sup/wiki/Development%3A-Administration-and-Team
- https://github.com/sup-heliotrope/sup/wiki/Development
Please see https://github.com/sup-heliotrope/sup/wiki/Contributing on
how to submit changes or contribute.
There are a few tasks and roles that need some love, among them:
maintaining the web site and maintaining the maildir feature branch.
Regards, Fellow Suppers
next reply other threads:[~2013-04-28 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 18:23 Gaute Hope [this message]
2013-04-28 18:47 ` [sup-talk] " Jonathan Lassoff
2013-04-28 19:01 ` Gaute Hope
2013-04-28 19:59 ` Eric Weikl
2013-04-28 19:05 ` Steven Hum
2013-04-28 20:33 ` Ico Doornekamp
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=517D6921.3050006@gaute.vetsj.com \
--to=eg@gaute.vetsj.com \
--cc=sup-talk@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