Differences between revisions 2 and 4 (spanning 2 versions)
Revision 2 as of 2013-07-05 00:27:27
Size: 961
Editor: GeoffSimmons
Comment: State page language, minor formatting fix.
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
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
   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 alioth).    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).
Line 12: Line 12:

 * '''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.

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, Casulana, Patterson machines). This is to avoid risks that some cloud providers might injects their code.