[Buildbot-devel] Volunteering and some suggestions.

[Gavin]

Hi,

A couple of things I'd like to raise.

1. Do you have enough people looking after your VM instance? I'm in
Australia and the time difference might help provide a bit of round the
clock coverage. So, I'm volunteering to help maintain if you think it a good
idea.

2. I think it would benefit this project _greatly_ if Buildbot Trac Issues
were linked to the mailing list. All Issue activity I feel should be relayed
to the list so everyone knows what's happening there. Having this current
discontinuity between the list and the open issues is stifling progress.
People will go to the Issue Tracker and get more involved I feel if they can
see what is going on from their inbox. There are many patches there and
recent issues that some folks here probably have no clue about unless they
remember to check the tracker. The issue tracker is just a nice way to file
issues, but the mailing lists is where it all happens.

3. Going through the Issues, there are quite a few with what seem like
trivial patches already attached. Some many months old. Some of those people
have spent time working on the project to help improve it for their own and
everyone elses benefit, and provided some nice diffs etc. How much easier
does it need to be? The moral of some of these folks will wain if their
patches are left hanging on an issue tracker for weeks or months at a time.

I wonder if Trac can be configured or a custom feed configured to send an
email once a week to this list for all issues that contain a patch, is that
do-able?

I have just downloaded the latest trunk, would it help if I rounded up a few
of these patches and other ideas and applied them to my copy? Then a one off
merge to trunk (or a branch for testing by others if need be) would be
easier and time saving for you guys? Let me know if you want me to do that.

That's about it for now :)

Gav...