From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.229.71 with SMTP id jh7cs86035icb; Tue, 25 Jan 2011 09:36:06 -0800 (PST) Received: by 10.229.181.9 with SMTP id bw9mr4951477qcb.143.1295976966126; Tue, 25 Jan 2011 09:36:06 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id u4si30607502qcq.14.2011.01.25.09.36.05; Tue, 25 Jan 2011 09:36:06 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 88F3C19783BC; Tue, 25 Jan 2011 12:36:05 -0500 (EST) Received: from mail-ew0-f50.google.com (mail-ew0-f50.google.com [209.85.215.50]) by rubyforge.org (Postfix) with ESMTP id B59CB185836C for ; Tue, 25 Jan 2011 12:07:16 -0500 (EST) Received: by ewy27 with SMTP id 27so2745915ewy.23 for ; Tue, 25 Jan 2011 09:07:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:references:from:mime-version:date:message-id :subject:to:content-type; bh=3r9CAzwlYe4ZC4fM1Ux8bu7FmXIOpt9yZBcMBBoSlNI=; b=hRd6J7FAA2ceWW10jxKXCF8rSbpM+hoiMYmlNd/Nr1bIqKMpTftFqD5wulk59YBJk4 9IdpneeKjoXAmskOx+94Rz/4FJYjJWmZjrvJCttCMRYVu7Cxpr4eyqIFcJWR1o5COdsQ TmW3vQmMF4E4s6NSoppZGK+TOzQZMNBq8DZlo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:from:mime-version:date:message-id:subject:to :content-type; b=p8ZtygXu42aYcvXffTqtrkYFhfCT9NKYy7H7xRvy0YFSrfrJ9UhPu7mSLjxZf6H1aO i2E3XZgR2FmsyXcJBusLtusybmLxz27OD559F61b3DTbbw39WaIqYehweLZJsqkOSuC6 bgohNfkQjHD25bY6hB3gAnDYr1y8LOUVLX+Vc= Received: by 10.204.140.208 with SMTP id j16mr5373184bku.151.1295975130725; Tue, 25 Jan 2011 09:05:30 -0800 (PST) References: From: Wael Nasreddine Mime-Version: 1.0 (iPhone Mail 8B117) Date: Tue, 25 Jan 2011 18:04:55 +0100 Message-ID: <-4037281717927276068@unknownmsgid> To: "sup-devel@rubyforge.org" Subject: [sup-devel] Fwd: [sup-talk] call for new maintainers X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1604069612==" Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org --===============1604069612== Content-Type: multipart/alternative; boundary=0015174c1c3c4dfc7a049aaeb948 --0015174c1c3c4dfc7a049aaeb948 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, I'm just forwarding the message because it bounced coz I wasn't a member Regards, Wael Nasreddine --=20 Wael Nasreddine Sent from my iPhone Begin forwarded message: *From:* "Wael M. Nasreddine" *Date:* January 25, 2011 15:19:10 GMT+01:00 *To:* William Morgan *Cc:* sup-devel , sup-talk@rubyforge.org *Subject:* *Re: [sup-talk] call for new maintainers* 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 wro= te: > 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 > _______________________________________________ > sup-talk mailing list > sup-talk@rubyforge.org > http://rubyforge.org/mailman/listinfo/sup-talk > --=20 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Wa=C3=AAl Nasreddine TechnoGate www.technogate.fr mobile : 06.32.94.70.13 agence : 09.70.444.236 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --0015174c1c3c4dfc7a049aaeb948 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I'= m just forwarding the message because it bounced coz I wasn't a member<= /div>

Regards,
Wael Nasreddine

--= =C2=A0
Wael Nasreddine
Sent from my iPhone

Begin forwarded= message:

From: "Wa= el M. Nasreddine" <wae= l.nasreddine@gmail.com>
Date: January 25, 2011 15:19:10 GMT+01:00
To: William Morg= an <wmorgan-sup@masanjin.net= >
Cc: sup-devel <sup-devel@rubyforge.org>, sup-talk@rubyforge.org
Subject: Re: [sup-talk] call for new maintainers

He= llo,

How much work you estimate per week?

I'm familiar with Ruby and Git, but I'm not very familia= r with the code of SUP itself as I haven't read it entirely yet.. I wou= ld 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://rubyfor= ge.org/mailman/listinfo/sup-talk



--
~~~~~~~~~~~~~~~~= ~~~~~~~~~~~~~~~~~~~~~~~
Wa=C3=AAl Nasreddine
TechnoGate www.technogate.fr
mobile : =C2=A006.32.94.70.13
agence : 09.70.444.236
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--0015174c1c3c4dfc7a049aaeb948-- --===============1604069612== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel --===============1604069612==--