Currently there is some duplication between configuration files in buildbot-configs/mozilla directory (e.g. see https://hg.mozilla.org/build/buildbot-configs/file/3cff563f36cf/mozilla). The task is to investigate this data, to see if the data can be modeled in such a way that there is reduced redundancy, without increasing complexity in such a way that the benefits of the reduced data duplication is outweighed by the higher level of complexity. The goal should be to find a clean/elegant solution for configuring the settings, such that configuration data is inherited in such a way that it is easy to see what all settings should be for a given job, but configuration settings that are constant in a given context are only defined once. This task is not (yet) to re-implement, only to investigate and propose a design, for review by relevant stakeholders.
Also it is my understanding that many of the mozconfigs are redundant now that we use the in-tree ones: https://hg.mozilla.org/mozilla-central/file/tip/browser/config/mozconfigs https://hg.mozilla.org/mozilla-central/file/tip/mobile/android/config/mozconfigs https://hg.mozilla.org/mozilla-central/file/tip/b2g/config/mozconfigs https://hg.mozilla.org/mozilla-central/file/tip/xulrunner/config/mozconfigs That said, I think the l10n builds still may have some use for a subset of the buildbot-configs versions.
Will also try to look at this again in July 2014.
Buildbot is going to silicon heaven, behold Task Cluster.