* [sup-devel] call for new maintainers
@ 2011-01-24 18:40 William Morgan
2011-01-24 19:20 ` Michael Stapelberg
2011-01-25 14:19 ` [sup-talk] " Wael M. Nasreddine
0 siblings, 2 replies; 15+ messages in thread
From: William Morgan @ 2011-01-24 18:40 UTC (permalink / raw)
To: sup-devel, sup-talk
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-01-24 18:40 [sup-devel] call for new maintainers William Morgan
@ 2011-01-24 19:20 ` Michael Stapelberg
2011-01-26 15:18 ` William Morgan
2011-01-25 14:19 ` [sup-talk] " Wael M. Nasreddine
1 sibling, 1 reply; 15+ messages in thread
From: Michael Stapelberg @ 2011-01-24 19:20 UTC (permalink / raw)
To: sup-devel
Hi William,
Excerpts from William Morgan's message of 2011-01-24 19:40:49 +0100:
> 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.
I don’t have enough time to be the only person doing this, but I do offer my
help on reviewing/merging patches. Maybe having more than one guy with commit
access turns out to be a good thing?
Best regards,
Michael
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-talk] call for new maintainers
2011-01-24 18:40 [sup-devel] call for new maintainers William Morgan
2011-01-24 19:20 ` Michael Stapelberg
@ 2011-01-25 14:19 ` Wael M. Nasreddine
2011-01-25 17:04 ` [sup-devel] Fwd: " Wael Nasreddine
1 sibling, 1 reply; 15+ messages in thread
From: Wael M. Nasreddine @ 2011-01-25 14:19 UTC (permalink / raw)
To: William Morgan; +Cc: sup-talk, sup-devel
[-- 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
^ permalink raw reply [flat|nested] 15+ messages in thread
* [sup-devel] Fwd: [sup-talk] call for new maintainers
2011-01-25 14:19 ` [sup-talk] " Wael M. Nasreddine
@ 2011-01-25 17:04 ` Wael Nasreddine
0 siblings, 0 replies; 15+ messages in thread
From: Wael Nasreddine @ 2011-01-25 17:04 UTC (permalink / raw)
To: sup-devel
[-- Attachment #1.1: Type: text/plain, Size: 2219 bytes --]
Hello,
I'm just forwarding the message because it bounced coz I wasn't a member
Regards,
Wael Nasreddine
--
Wael Nasreddine
Sent from my iPhone
Begin forwarded message:
*From:* "Wael M. Nasreddine" <wael.nasreddine@gmail.com>
*Date:* January 25, 2011 15:19:10 GMT+01:00
*To:* William Morgan <wmorgan-sup@masanjin.net>
*Cc:* sup-devel <sup-devel@rubyforge.org>, 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 <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: 3721 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-01-24 19:20 ` Michael Stapelberg
@ 2011-01-26 15:18 ` William Morgan
2011-01-26 16:10 ` Ben Walton
` (3 more replies)
0 siblings, 4 replies; 15+ messages in thread
From: William Morgan @ 2011-01-26 15:18 UTC (permalink / raw)
To: sup-devel
Reformatted excerpts from Michael Stapelberg's message of 2011-01-24:
> I don’t have enough time to be the only person doing this, but I do
> offer my help on reviewing/merging patches. Maybe having more than one
> guy with commit access turns out to be a good thing?
Yeah, maybe that's the right idea.
So let's try this. Michael, Tero, Sascha, Edward, and everyone else
who's had code make it into Sup successfully... if you send me your
Gitorious usernames, I will add you to the Sup group and you will have
push access. Then you can bypass the list mailing list for patches
entirely, which will save me a lot of work.
All I ask is that you divide things into nice topic branches and merge
them into next but not master. I'll merge individual branches into
master when prepping for a release.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-01-26 15:18 ` William Morgan
@ 2011-01-26 16:10 ` Ben Walton
2011-01-26 18:13 ` William Morgan
2011-01-27 7:31 ` Tero Tilus
` (2 subsequent siblings)
3 siblings, 1 reply; 15+ messages in thread
From: Ben Walton @ 2011-01-26 16:10 UTC (permalink / raw)
To: sup-devel
Excerpts from William Morgan's message of Wed Jan 26 10:18:59 -0500 2011:
Hi William,
> Gitorious usernames, I will add you to the Sup group and you will
> have push access. Then you can bypass the list mailing list for
> patches entirely, which will save me a lot of work.
I think it would be nicer to still see all patches posted to the list
first, regardless of committer rights. It's nice to see what people
are doing and be able to comment on proposed changes.
This doesn't preclude pushing to a topic branch as well, but it's
easier to comment on something if you don't need to track all of those
branches too...
Just a thought.
I'm bwalton on gitorious, btw.
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-01-26 16:10 ` Ben Walton
@ 2011-01-26 18:13 ` William Morgan
2011-01-26 23:44 ` Hamish D
0 siblings, 1 reply; 15+ messages in thread
From: William Morgan @ 2011-01-26 18:13 UTC (permalink / raw)
To: sup-devel
Reformatted excerpts from Ben Walton's message of 2011-01-26:
> I think it would be nicer to still see all patches posted to the list
> first, regardless of committer rights. It's nice to see what people
> are doing and be able to comment on proposed changes.
Yeah, that would be good, and I hereby encourage that kind of behavior.
I just don't want the "waiting for William to get around to it" to be
the blocking factor like it's always been.
> I'm bwalton on gitorious, btw.
Added.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-01-26 18:13 ` William Morgan
@ 2011-01-26 23:44 ` Hamish D
0 siblings, 0 replies; 15+ messages in thread
From: Hamish D @ 2011-01-26 23:44 UTC (permalink / raw)
To: Sup developer discussion
> Reformatted excerpts from Ben Walton's message of 2011-01-26:
>> I think it would be nicer to still see all patches posted to the list
>> first, regardless of committer rights. It's nice to see what people
>> are doing and be able to comment on proposed changes.
>
> Yeah, that would be good, and I hereby encourage that kind of behavior.
> I just don't want the "waiting for William to get around to it" to be
> the blocking factor like it's always been.
Sounds good to me. I've just signed up to gitorious with user name foobacca.
Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-01-26 15:18 ` William Morgan
2011-01-26 16:10 ` Ben Walton
@ 2011-01-27 7:31 ` Tero Tilus
2011-01-28 6:20 ` William Morgan
2011-03-04 9:05 ` Damien Leone
2011-03-04 12:16 ` Sascha Silbe
3 siblings, 1 reply; 15+ messages in thread
From: Tero Tilus @ 2011-01-27 7:31 UTC (permalink / raw)
To: Sup developers
William Morgan, 2011-01-26 17:18:
> So let's try this. Michael, Tero, Sascha, Edward, and everyone else
> who's had code make it into Sup successfully... if you send me your
> Gitorious usernames
I'm http://gitorious.org/~terotil
> All I ask is that you divide things into nice topic branches and
> merge them into next but not master.
Do you prefer basing feature branches to master or next?
Should we prefix feature branch names to keep `git branch` more
readable? They could be topic-* or feature-* or alike.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-01-27 7:31 ` Tero Tilus
@ 2011-01-28 6:20 ` William Morgan
0 siblings, 0 replies; 15+ messages in thread
From: William Morgan @ 2011-01-28 6:20 UTC (permalink / raw)
To: sup-devel
Reformatted excerpts from Tero Tilus's message of 2011-01-27:
> I'm http://gitorious.org/~terotil
Added! And now I can ignore all your outstanding patch requests. :)
> > All I ask is that you divide things into nice topic branches and
> > merge them into next but not master.
>
> Do you prefer basing feature branches to master or next?
Base them off of master, please. If they're based off of next, I can't
merge them into master without also merging all of next.
> Should we prefix feature branch names to keep `git branch` more
> readable? They could be topic-* or feature-* or alike.
I don't think that's necessary. The only two integration branches are
master and next (and the release-* branches, I suppose). When I merge
things into master I will delete the remote branches as well, so we
shouldn't end up with a big mess.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-01-26 15:18 ` William Morgan
2011-01-26 16:10 ` Ben Walton
2011-01-27 7:31 ` Tero Tilus
@ 2011-03-04 9:05 ` Damien Leone
2011-03-07 18:27 ` William Morgan
2011-03-04 12:16 ` Sascha Silbe
3 siblings, 1 reply; 15+ messages in thread
From: Damien Leone @ 2011-03-04 9:05 UTC (permalink / raw)
To: sup-devel
Hello,
Could I have an access so I can push the finished maildir-sync branch
as well as some other patches?
My gitorious login is dleone.
Thanks,
Excerpts from William Morgan's message of mer. janv. 26 16:18:59 +0100 2011:
> Reformatted excerpts from Michael Stapelberg's message of 2011-01-24:
> > I don’t have enough time to be the only person doing this, but I do
> > offer my help on reviewing/merging patches. Maybe having more than one
> > guy with commit access turns out to be a good thing?
>
> Yeah, maybe that's the right idea.
>
> So let's try this. Michael, Tero, Sascha, Edward, and everyone else
> who's had code make it into Sup successfully... if you send me your
> Gitorious usernames, I will add you to the Sup group and you will have
> push access. Then you can bypass the list mailing list for patches
> entirely, which will save me a lot of work.
>
> All I ask is that you divide things into nice topic branches and merge
> them into next but not master. I'll merge individual branches into
> master when prepping for a release.
--
Damien Leone <damien.leone@fensalir.fr>
Web: http://dleone.fensalir.fr/
GPG: 0x82EB4DDF
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-01-26 15:18 ` William Morgan
` (2 preceding siblings ...)
2011-03-04 9:05 ` Damien Leone
@ 2011-03-04 12:16 ` Sascha Silbe
2011-03-04 12:19 ` Sascha Silbe
3 siblings, 1 reply; 15+ messages in thread
From: Sascha Silbe @ 2011-03-04 12:16 UTC (permalink / raw)
To: sup-devel
[-- Attachment #1.1: Type: text/plain, Size: 1137 bytes --]
Excerpts from William Morgan's message of Wed Jan 26 16:18:59 +0100 2011:
> So let's try this. Michael, Tero, Sascha, Edward, and everyone else
> who's had code make it into Sup successfully... if you send me your
> Gitorious usernames, I will add you to the Sup group and you will have
> push access.
I've finally created a gitorious account. I don't quite like the wording
of the ToS [1] concerning licenses (the way I read it Gitorious AS is
allowed to redistribute my code using a proprietary license), but
then the sup repository with all my submitted patches already is hosted
by them...
> Then you can bypass the list mailing list for patches
> entirely, which will save me a lot of work.
I'm happy to push my patches, but I'd still prefer to get at least one
Reviewed-By to make sure my changes are kosher.
> All I ask is that you divide things into nice topic branches and merge
> them into next but not master. I'll merge individual branches into
> master when prepping for a release.
Noted.
Sascha
[1] http://en.gitorious.org/tos/
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-03-04 12:16 ` Sascha Silbe
@ 2011-03-04 12:19 ` Sascha Silbe
2011-03-07 18:27 ` William Morgan
0 siblings, 1 reply; 15+ messages in thread
From: Sascha Silbe @ 2011-03-04 12:19 UTC (permalink / raw)
To: sup-devel
[-- Attachment #1.1: Type: text/plain, Size: 251 bytes --]
Excerpts from Sascha Silbe's message of Fri Mar 04 13:16:41 +0100 2011:
> I've finally created a gitorious account.
And of course forgot to mention the account name: silbe.
Sascha
--
http://sascha.silbe.org/
http://www.infra-silbe.de/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-03-04 9:05 ` Damien Leone
@ 2011-03-07 18:27 ` William Morgan
0 siblings, 0 replies; 15+ messages in thread
From: William Morgan @ 2011-03-07 18:27 UTC (permalink / raw)
To: sup-devel
Reformatted excerpts from Damien Leone's message of 2011-03-04:
> My gitorious login is dleone.
Added.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [sup-devel] call for new maintainers
2011-03-04 12:19 ` Sascha Silbe
@ 2011-03-07 18:27 ` William Morgan
0 siblings, 0 replies; 15+ messages in thread
From: William Morgan @ 2011-03-07 18:27 UTC (permalink / raw)
To: sup-devel
Reformatted excerpts from Sascha Silbe's message of 2011-03-04:
> And of course forgot to mention the account name: silbe.
Added.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2011-03-07 18:51 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-24 18:40 [sup-devel] call for new maintainers 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 ` [sup-talk] " Wael M. Nasreddine
2011-01-25 17:04 ` [sup-devel] Fwd: " Wael Nasreddine
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox