When I started the "Handling Large Installations" design proposal ,
it was intended to document a series of smaller steps towards the
specific goal of implementing more automated usage constraints and other
usability improvements in Beaker to reduce the level of training needed
to use a large installation appropriately.
Over time, it's usage morphed to become a running record of past Beaker
releases, and our current plans for future releases. I actually quite
like that usage style, so I'll be changing it to officially be that, and
dropping it as a "design proposal".
Red Hat Hosted & Shared Services
Software Engineering & Development, Brisbane
HSS Provisioning Architect