Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: "Wael M. Nasreddine" <wael.nasreddine@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>
Cc: sup-talk@rubyforge.org, sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-talk] call for new maintainers
Date: Tue, 25 Jan 2011 15:19:10 +0100	[thread overview]
Message-ID: <AANLkTiktGxmVWJCrc=BJdVvA6g3521VCvsF22scY_BhH@mail.gmail.com> (raw)
In-Reply-To: <1295894044-sup-7965@masanjin.net>


[-- Attachment #1.1: Type: text/plain, Size: 1756 bytes --]

Hello,

How much work you estimate per week?

I'm familiar with Ruby and Git, but I'm not very familiar with the code of
SUP itself as I haven't read it entirely yet.. I would gladly help sup but I
need to know first how much work to expect..

Regards,
Wael Nasreddine

On Mon, Jan 24, 2011 at 19:40, William Morgan <wmorgan-sup@masanjin.net>wrote:

> 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-talk mailing list
> sup-talk@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
>



-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Waêl Nasreddine
TechnoGate www.technogate.fr
mobile :  06.32.94.70.13
agence : 09.70.444.236
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[-- Attachment #1.2: Type: text/html, Size: 2455 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  parent reply	other threads:[~2011-01-25 14:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 18:40 [sup-devel] " William Morgan
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 ` Wael M. Nasreddine [this message]
2011-01-25 17:04   ` [sup-devel] Fwd: [sup-talk] " 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='AANLkTiktGxmVWJCrc=BJdVvA6g3521VCvsF22scY_BhH@mail.gmail.com' \
    --to=wael.nasreddine@gmail.com \
    --cc=sup-devel@rubyforge.org \
    --cc=sup-talk@rubyforge.org \
    --cc=wmorgan-sup@masanjin.net \
    /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