Differences between revisions 29 and 30
Revision 29 as of 2009-03-10 14:54:53
Size: 3411
Comment: multi-arch
Revision 30 as of 2009-03-16 03:31:08
Size: 3419
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 36: Line 36:
  * Use pseudo structured format, like [http://www.methods.co.nz/asciidoc/asciidoc.css-embedded.html asciidoc] or [http://docutils.sourceforge.net/rst.html rst]. (An later, publish them on the web in p.d.o)
 * [http://wiki.debian.org/Proposals/CopyrightFormat Proposals/CopyrightFormat]
 * [http://wiki.debian.org/Proposals/DebianMenuUsingDesktopEntries Proposals/DebianMenuUsingDesktopEntries] (volunteer to drive the discussion and the transition: CharlesPlessy)
  * Use pseudo structured format, like [[http://www.methods.co.nz/asciidoc/asciidoc.css-embedded.html|asciidoc]] or [[http://docutils.sourceforge.net/rst.html|rst]]. (An later, publish them on the web in p.d.o)
 * [[http://wiki.debian.org/Proposals/CopyrightFormat|Proposals/CopyrightFormat]]
 * [[http://wiki.debian.org/Proposals/DebianMenuUsingDesktopEntries|Proposals/DebianMenuUsingDesktopEntries]] (volunteer to drive the discussion and the transition: CharlesPlessy)
Line 43: Line 43:
 * 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"]).  * 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]]).

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
  • Packages interfacing with external resources and where they belong

  • 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

  • Automated modification of debian/control files in cross-building and multi-arch packages (gcc and glibc).
  • README.Debian
    • Describe or formalise some typical entries, like in manpages (Introduction, Quick-start, where-is-the-doc Howto, Enabling features (aka why install recommends/suggest).
    • Use pseudo structured format, like asciidoc or rst. (An later, publish them on the web in p.d.o)

  • Proposals/CopyrightFormat

  • Proposals/DebianMenuUsingDesktopEntries (volunteer to drive the discussion and the transition: CharlesPlessy)

  • switch away from defoma towards fontconfig (since it is cross-distro)
  • multi-arch - i386 and amd64 packages coexisting (and ppc/64, i386/ia64 etc)

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).