{The \TeX\ Live M sub-project} {Arthur Reutenauer\regularorprogramstring{, Mojca Miklavec}{}} {\TeX\ Live is the most versatile of \TeX\ distributions, available on a variety of platforms, and very actively developed. It is the basis for Mac\TeX\ on \MacOSX, and is bundled by many package managers in Unix distributions. It has, however, a major drawback: its titanic size. This talk will discuss a sub-project to address that, with time for general discussion on wishes and ideas for \TeX\ Live's future. At its inception in 1996, it was contained in a \CD\ and started growing immediately. Packages are rarely removed, due to compatibility considerations, and only technical considerations are taken into account when considering new packages: if a package fits the requirements, it is added. Today, the \code{texlive-full} installation scheme includes over 140,000 files and has an installed size of over 4.5\,\acro{GB}. %Together with an extract of the contents of \CTAN\ it forms the \TeX\ %Collection that fits on a double-layered \DVD, but for how much longer? This situation is a problem for many downstream package developers and also affects the \TeX\ community as a whole. We have started a conversation to see how we could help users find packages. We would like to offer an option to have a more controlled set of packages, probably by creating a new \TeX\ Live ``scheme'' in the existing distribution by selecting among the 3200+ (to date) packages. We could define strict dependencies between packages, and also strive to do some measure of quality control, in order to create a distribution that's truly useful for newcomers and long-time users alike. The selection has to be community-driven, but there has to be a selection. In another area, we also want to improve how the binaries are built: at the moment, they're compiled once per year by a number of volunteers who work on one or more of the twenty or so different platforms, and never get updated during the year. While this strikes a good balance between stability, the demand for reasonably recent binaries, and the workload of volunteer builders and packagers, we thought we could do better. We have recently set up a build infrastructure that can automatically build \TeX\ binaries after every source change for a number of platforms, send emails when builds break, show reports, and make the binaries available to users. This approach takes a lot of burden off the shoulders of people previously responsible for building \TeX\ binaries, while at the same time giving us freedom to run the builds a lot more frequently, getting binaries to users much faster and providing earlier feedback about problems to developers. This part is almost ready and we will give some technical details of how it works. }