Differences between revisions 25 and 26
Revision 25 as of 2009-02-15 11:25:57
Size: 2777
Editor: PaulWise
Comment: defoma
Revision 26 as of 2009-02-17 01:49:49
Size: 3260
Editor: ?MichaelGilbert
Comment:
Deletions are marked like this. Additions are marked like this.
Line 29: Line 29:
 * Discussion on potential Debian Policy changes for packages with scripts that download files external to the Debian archives (see http://bugs.debian.org/449497 and http://bugs.debian.org/511644 for examples). The primary concerns are breakages in stable packages, exposing potential vectors for malicious software (e.g. the practice of signing all files/packages by a maintainer is circumvented), and allowing software in main to rely upon (or depend) on non-free software/data.

This page tries to contain the list of things that should be discussed regarding the Debian's project, but should be delayed until after Lenny is out to avoid creating new problems for the release, and also to be able to discuss them in a calmer environment than that before a release.

Constitutional

Discussion Starter: mjj29 (should probably be discussed first)

  • Clarify requirements for GRs
    • Number of seconds
    • Supermajority requirements
    • Override vs amend foundation documents

Organisational / Human

Release

  • Ways to reduce the length of the freeze
  • Additional/changed frequency of releases.
  • Goals for Squeeze from various teams

  • Removing non-free (again)
  • DFSG - drop it, ignore it for every release individually or pay attention to it.
  • Allow redistributable but non-DFSG-free files in the Upstream sources of the main archive (but no in the binary packages of course).
  • Discussion on potential Debian Policy changes for packages with scripts that download files external to the Debian archives (see http://bugs.debian.org/449497 and http://bugs.debian.org/511644 for examples). The primary concerns are breakages in stable packages, exposing potential vectors for malicious software (e.g. the practice of signing all files/packages by a maintainer is circumvented), and allowing software in main to rely upon (or depend) on non-free software/data.

Technical

Undefined

  • Sections; their history, what they are for, what to do about them - drop them, keep them in current state, introduce more sections and or more clearly specify in policy what each section is for. Also audit the current ftp-master overrides for them (see ["/Sections"]).