Publish the buildbot configuration in a public repository & define where to track its issues

[nejucomo]

Problem:

The buildbot config, the process used to update it, policies about what go into it, and issues related to it are all somewhat opaque.

Solution:

Publish the buildbot config in a public repository and clearly declare where issue tracking for it should live.

If it is on github, but issue tracking should be this track, I recommend disabling the github issue tracker and linking to this trac in an obvious place.

NOTE: Be careful to separate out secrets from the public config prior to publishing it (in both the current state and the entire history).

[daira]

This will live at ​https://github.com/tahoe-lafs/buildbot-config-tahoe , but that repo is currently empty.

[zooko]

Here is some code! Mark Berger and I worked on this.

​https://github.com/zooko/buildbot-config-tahoe

[daira]

This is now committed to ​https://github.com/tahoe-lafs/buildbot-config-tahoe. The buildmaster is currently using this config, but the history of past builds has not been copied over to the new config yet.

[zooko]

I decided to let the history of past builds die. :-( That probably means there are a few broken links out there pointing to historical build results.