How does a spin become the default offering?
Before the advent of Live distributions, the default Fedora product was a DVD with many software choices available. By default, a user who did not choose to customize the packages installed would end up with a GNOME Desktop environment along with some other best-of-breed applications. Because the Fedora DVD originally branched off from the Red Hat Linux product, it inherited these choices.
Live images were created not just to provide a simple way for users to "try before they buy," but also as an offshoot of "stateless" project work. The default Live image became a subset of the DVD product, because of size constraints (fitting the image onto CD sized media), and the desire to have a general purpose desktop productivity platform as the simplest expression of a Live image. Over time the number of Live images has expanded because the tools for creating them are easy to master, and because we have contributors interested in creating environments that are still constrained in size but show off other platforms available within the Fedora repositories.
The reason we have a default offering is because as a Project we need a single item we can hand out, offer, or promote for the general populace, which serves as the Project's "best foot forward" in terms of our mission of leading the advancement of FOSS. By definition we lead by showing off the most advanced software for a general populace.
The Board decided to make a default offering, and assign the Desktop Live spin as a default -- essentially codifying existing practice -- for several reasons:
- For best usability and stickiness, a general audience needs a call to action item. For the Fedora Project this is a download, which is the gateway to getting involved for the vast majority of people.
- A Live spin is more sensible than DVD because a run-before-install environment better meets users' needs and expectations
- The Desktop spin includes a large proportion of the new software innovations seen in feature listings
- The Desktop spin is maintained and driven by a large group of people originating new code directly in the upstream communities
- Refer to, for example, Godin's "The Big Red Fez."