slowly catching up

[William Morgan-4]

Hi all,

Just wanted to let you know that I am slowly catching up with the
backlog of patches and bug reports. We just had our first baby so it's
been a busy few weeks.

If you haven't heard back about something in the next week or so, please
ping me about it.

In the near future I would like to face reality and change the process
so that I am not the one and only bottleneck to development. (Which is
entirely a situation I have created myself.) E.g. use a bug tracker (not
ditz), delegate some responsibility to people who are interested, etc. I
would like to see the development of Sup continue, but not limited by
the small amount of time I have for it. Suggestions welcome. (Thanks,
Tero, for starting on this already.)
--
William <wmorgan-sup@...>
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

[Tero Tilus-2]

William Morgan, 2009-10-31 16:03:
> We just had our first baby so it's been a busy few weeks.

Congratulations!  Take your time.  Your family needs it now.

I've got two lovely kids, having the first one is a very special
thing.

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

[William Morgan-4]

Reformatted excerpts from Tero Tilus's message of 2009-11-01:
> Congratulations!  Take your time.  Your family needs it now.
>
> I've got two lovely kids, having the first one is a very special
> thing.

Thanks guys. It's been great so far.
--
William <wmorgan-sup@...>
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

[Andrei Thorp]

On Sat, Oct 31, 2009 at 9:03 AM, William Morgan
<wmorgan-sup@...> wrote:
> Suggestions welcome.

I propose promoting Rich Lane to commiter if he's up for it and
doesn't have access yet. From what I can tell, he's done a terrific
job thus far, and has a lot of experience with Sup.

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

[Rich Lane]

Excerpts from Andrei Thorp's message of Thu Nov 05 21:38:26 -0500 2009:
> On Sat, Oct 31, 2009 at 9:03 AM, William Morgan
> <wmorgan-sup@...> wrote:
> > Suggestions welcome.
>
> I propose promoting Rich Lane to commiter if he's up for it and
> doesn't have access yet. From what I can tell, he's done a terrific
> job thus far, and has a lot of experience with Sup.

Thanks! If William doesn't have the free time, I would be glad to help
out. Rather than committing directly to mainline, I'd rather keep a
public repo that I apply incoming patches to and that William can pull
from. This way I could do a lot of the first-line work and he could get
a more stable flow of patches to make releases from.

For my own process suggestion:

I can imagine that a lot of William's work caused by being the central
repository is reviewing the patches that get sent in. I'd like for
anyone who feels interested to read through incoming patches and comment
on them. I don't want any strict processes just yet, but I'd like to see
a couple of positive reviews (depending on the complexity of the patch,
etc) before things get merged.

Distributing the workload and ensuring code quality are only a couple of
my motives here. I know I feel more comfortable sending out a patch if
I'm sure someone will catch my mistakes before it's merged. Also, it's a
great way for people who aren't yet familiar with the codebase to start
contributing.

If anyone's interested and wants to get started right away, definitely
take a look at the immediate-updates patches I sent in yesterday.
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

[William Morgan-4]

Reformatted excerpts from Rich Lane's message of 2009-11-05:
> Rather than committing directly to mainline, I'd rather keep a public
> repo that I apply incoming patches to and that William can pull from.
> This way I could do a lot of the first-line work and he could get a
> more stable flow of patches to make releases from.

That sounds good to me. I'm happy to add you to the gitorious repo, of
course, but this is definitely more in line with the git lifestyle.

We have a couple options on how to organize this, but I think the best
would be for you to maintain one or more branches that I treat as
integration branches, and periodically merge into master whenever you
tell me they're ready. That's a very minimal amount of work for me. I
can just merge it and forget it.

The only things to be careful about in such a setup are not merging next
into your branch (merging master in is fine and good to keep up with
other stable changes), and not rebasing. And we will have to coordinate
on releases, if nothing else so that I can make reasonable changelogs
and release notes.

How does that sound?

> I can imagine that a lot of William's work caused by being the central
> repository is reviewing the patches that get sent in. I'd like for
> anyone who feels interested to read through incoming patches and comment
> on them. I don't want any strict processes just yet, but I'd like to see
> a couple of positive reviews (depending on the complexity of the patch,
> etc) before things get merged.

That would be great. Or heck, even an "I applied it and it works for
me" is useful.
--
William <wmorgan-sup@...>
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

[Rich Lane]

Excerpts from William Morgan's message of Fri Nov 06 08:47:51 -0500 2009:

> Reformatted excerpts from Rich Lane's message of 2009-11-05:
> > Rather than committing directly to mainline, I'd rather keep a public
> > repo that I apply incoming patches to and that William can pull from.
> > This way I could do a lot of the first-line work and he could get a
> > more stable flow of patches to make releases from.
>
> That sounds good to me. I'm happy to add you to the gitorious repo, of
> course, but this is definitely more in line with the git lifestyle.
>
> We have a couple options on how to organize this, but I think the best
> would be for you to maintain one or more branches that I treat as
> integration branches, and periodically merge into master whenever you
> tell me they're ready. That's a very minimal amount of work for me. I
> can just merge it and forget it.
>
> The only things to be careful about in such a setup are not merging next
> into your branch (merging master in is fine and good to keep up with
> other stable changes), and not rebasing. And we will have to coordinate
> on releases, if nothing else so that I can make reasonable changelogs
> and release notes.
>
> How does that sound?

Sounds good. I'll keep using my clone at http://github.com/rlane/sup/tree/master
unless people would prefer I move it to gitorious.

When I see a new patchset I'll create a branch for it, like William has
been doing. One difference is that I'll hold off on merging to my master
(where new patches cook before being sent upstream) until I see some
positive feedback on the list. Initially this might just come from me,
but like I said before I'm hoping others will join in too. My intention
in creating the branch quickly after the patch is mailed is to make it
trivial for people tracking my repo to try out the newest patches.

As for getting changes to William, I'll occasionally (weekly?) apply the
patches I deem stable on top of his master branch and send mail to
the list. This way it should be a fast-forward when he pulls and we
won't have to worry about resolving merges differently.

As a side note, I just created a Wishlist wiki page for feature requests:
http://sup.rubyforge.org/wiki/wiki.pl?Wishlist
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

[Tero Tilus-2]

Rich Lane, 2009-11-07 09:09:
> Sounds good. I'll keep using my clone at
> http://github.com/rlane/sup/tree/master unless people would prefer I
> move it to gitorious.

Does it really make that big difference?  I don't think.

> As a side note, I just created a Wishlist wiki page for feature
> requests: http://sup.rubyforge.org/wiki/wiki.pl?Wishlist

Why not use tracker for feature requests too?  If I don't hear any
reasons why, I'll go put the wishlist items there too.

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

[William Morgan-4]

Reformatted excerpts from Rich Lane's message of 2009-11-06:
> As for getting changes to William, I'll occasionally (weekly?) apply
> the patches I deem stable on top of his master branch and send mail to
> the list. This way it should be a fast-forward when he pulls and we
> won't have to worry about resolving merges differently.

Sounds good to me. I'm not even that concerned about fastforward vs
merge.

> As a side note, I just created a Wishlist wiki page for feature requests:
> http://sup.rubyforge.org/wiki/wiki.pl?Wishlist

I agree that these would be great to have on the issue tracker.
--
William <wmorgan-sup@...>
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk