Differences between revisions 4 and 5
Revision 4 as of 2020-06-06 09:34:37
Size: 1169
Comment: Add requirement that images have to be built from Debian Infrastructure, copied from Mail from Cloud Delegate
Revision 5 as of 2020-06-07 03:47:13
Size: 1182
Editor: PaulWise
Comment: betterise machine names
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 * '''E. all cloud-related images have to be built on Debian infrastructure''' (for instance Salsa, Casulana, Patterson machines). This is to avoid risks that some cloud providers might injects their code.  * '''E. all cloud-related images have to be built on Debian infrastructure''' (for instance [[Salsa]] or casulana.d.o/petterson.d.o machines). This is to avoid risks that some cloud providers might injects their code.

This page is an attempt at document requirements for official Debian images (CD/DVD, Live CD/DVD, Cloud, etc.). It is work in progress, and not final. But the current listing outlines recommendations for people willing to provide such images with Debian's blessing.

  • A. the image includes only software available in Debian

  • B. the image generation process is controlled solely by Debian

  • C. the image generation tools are maintained inside Debian and/or by a Debian team, using usual Debian recommended practices

    • Ideally, this means that the generation tools are provided as Debian packages inside Debian, and maintained by a team following the usual Debian practices (e.g. using salsa).
  • D. the images most provide a user experience (in terms of default choice of packages, or of default configuration) identical to other means of installing Debian. Differences must be documented and justified.

  • E. all cloud-related images have to be built on Debian infrastructure (for instance Salsa or casulana.d.o/petterson.d.o machines). This is to avoid risks that some cloud providers might injects their code.