I'd like to raise the (biannual) proposition that we consider launching Byobu by default on Ubuntu Server installs for at least part of the Oneiric cycle. As an LTS-1 release, this provides an ideal opportunity (Alpha1-3?) to innovate and differentiate, while still allowing for recalibration and reconsideration ahead of the subsequent stability-focused LTS cycle.
Byobu has come a long way in the last 2.5 years, having addressed many of the early concerns about functionality, stability, and usability. New features, such as horizontal and vertical splitting, and traditional ones such as convenient keybindings and dozens of real-time monitors provide a rich, unique command line experience for many Ubuntu users. Byobu has won the praise of numerous users, bloggers, and magazines, with many people swearing by its utility. That praise is not unanimous, of course (though what is unanimous in Ubuntu these days?). So such a change would be easily overridden by the following preseed parameter (and could even be a single question in the installer): byobu byobu/launch-by-default boolean false At login, the user would be clearly informed that this is brand new behavior which can be trivially and permanently reverted with the command: $ byobu-disable Furthermore, derivative distributions should be able to cleanly and easily opt in or out of this change. At the very least, I suggest that we consider enabling Byobu by default for our cloud images that necessarily run detached and "elsewhere" -- which is really where Byobu shines! Byobu provides some distinct advantages over numerous indistinguishable cloud images on the market. Shall we take a risk and innovate a bit here? At least for a couple of non-LTS Alpha releases? Or perhaps localized to our cloud images? -- D'nalkrik Nit-sud Registered Byobu user #00000001 Okay, okay ... it's really Dustin Kirkland, of course. -- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
