Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Tero Tilus <tero@tilus.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup for sale
Date: Thu, 25 Feb 2010 22:04:25 +0200	[thread overview]
Message-ID: <1267126809-sup-9599@tilus.net> (raw)
In-Reply-To: <1267109223-sup-351@masanjin.net>

William Morgan, 2010-02-25 16:51:
> But if someone wants to take the ball and be an official maintainer,
> I will give you my blessing and the power to gem push new releases.

One in particular comes into my mind.  Rich Lane has done an awesome
job with sup and shown exceptional vision with his work on sup-server.
IMHO, if Rich wants to catch the ball, he would make a great lead
maintainer.

> Otherwise, things will continue as they do now.

Which, I have to say, is not really bad at all.  People develop,
patches get merged and released.  Cycle could always be tighter, of
course.  But sup is alive and strong.

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  parent reply	other threads:[~2010-02-25 20:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 14:51 William Morgan
2010-02-25 15:32 ` Christian Dietrich
2010-09-23 11:50   ` Gaute Hope
2010-09-23 17:46     ` Alvaro Herrera
2010-10-06 22:47       ` Michael Stapelberg
2010-10-07  3:08         ` Rich Lane
2010-02-25 20:04 ` Tero Tilus [this message]
2010-02-25 21:55 ` Rich Lane
2010-02-25 23:26   ` William Morgan
2010-02-26 14:05     ` William Morgan
2010-02-26 16:07   ` Tero Tilus

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=1267126809-sup-9599@tilus.net \
    --to=tero@tilus.net \
    --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