From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>, sup-talk@rubyforge.org
Subject: [sup-devel] call for new maintainers
Date: Mon, 24 Jan 2011 13:40:49 -0500 [thread overview]
Message-ID: <1295894044-sup-7965@masanjin.net> (raw)
I said this in another thread on sup-devel, but I thought I'd give it a
broader audience.
Rich is stepping down as maintainer due to lack of time (but will still
be around as a contributor). I personally have a little more time
nowadays than I did before. But I would rather spend it working on
features, including possible a new index backend.
So, anyone who would be interested in the maintainership busywork of
collecting patches from sup-devel, making branches, and pushing
releases, please let me know. You must be familiar with git, Ruby and,
of course, Sup. I can provide a brief guide of how this all works.
In exchange, you will have access to the secret Sup maintainer meetings
that take place in the smoky backrooms of various San Francisco bars.
If multiple people are interested, we can set up a rotation so that no
one is stuck with it forever.
If no one responds, I will continue to be your (not very responsive)
maintainer.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2011-01-24 18:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 18:40 William Morgan [this message]
2011-01-24 19:20 ` Michael Stapelberg
2011-01-26 15:18 ` William Morgan
2011-01-26 16:10 ` Ben Walton
2011-01-26 18:13 ` William Morgan
2011-01-26 23:44 ` Hamish D
2011-01-27 7:31 ` Tero Tilus
2011-01-28 6:20 ` William Morgan
2011-03-04 9:05 ` Damien Leone
2011-03-07 18:27 ` William Morgan
2011-03-04 12:16 ` Sascha Silbe
2011-03-04 12:19 ` Sascha Silbe
2011-03-07 18:27 ` William Morgan
2011-01-25 14:19 ` [sup-talk] " Wael M. Nasreddine
2011-01-25 17:04 ` [sup-devel] Fwd: " Wael Nasreddine
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=1295894044-sup-7965@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@rubyforge.org \
--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