[Buildbot-devel] Buildbot needs project maintainers!

[Dustin J. Mitchell]

Buildbot is way too big for any one person to be able to understand
and fix everything -- much less me :)

So I've been working on dividing things up into what I'm calling
"projects" -- each of the various VC's, the web frontend, the database
backend, virtualization, windows, etc.

The full list is at

  http://buildbot.net/trac/wiki/TicketKeywords

I would like to put together a small group of maintainers for each of
these projects - folks who can triage bugs better than I can, and who
know better than I do what the best design decision is within a
particular area of Buildbot.  For example, there are a number of Darcs
bugs open which I'm helpless to address -- I just don't know Darcs
well enough.

Many of you on this list have been involved in various areas of
Buildbot at one time or another, and have some familiarity with it.
If you can take some time to look through the categorized bugs for
things you might be able to address, or at least comment on, I would
appreciate it.  There are links on the TicketKeywords page to search
for specific, categorized bugs:

  http://buildbot.net/trac/wiki/TicketKeywords

Finally, if you can put your name to a part of Buildbot, please add
yourself to the list of maintainers on the relevant page.  These are
folks I will be asking for help and advice when new, hairy bugs
arrive, and you will have a significant voice in the future direction
of Buildbot.

I'm hoping to get 0.8.2 out soon, mostly as a bugfix release.  We've
fixed a number of bugs, but there remain a lot of bugs that *look*
like low-hanging fruit, but which would take me quite a while to solve
because I don't have the necessary experience or external
dependencies.  I'd like to get some of those cleaned up before we
release.

TIA,
Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com