2777
Comment: defoma
|
3260
|
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
- Membership classes and/or processes.
- Discussion Starter: mjj29
Having a Code of Conduct (CoC) in Debian. References for inspiration can be found in: http://www.ubuntu.com/community/conduct , http://www.kde.org/code-of-conduct/ , http://live.gnome.org/CodeOfConduct , http://www.debian.org/MailingLists/, http://www.wesnoth.org/wiki/MP_CodeOfConduct, http://people.debian.org/~enrico/dcg/
- Restrict time people stay in positions of power, rotate people in these positions instead.
- Make the terms of DPL delegations written.
Release
- Ways to reduce the length of the freeze
Considering a Release Process change: http://wiki.debian.org/ReleaseProposals
- Additional/changed frequency of releases.
- Goals for Squeeze from various teams
Legal / Licences
- 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 [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)
- switch away from defoma towards fontconfig (since it is cross-distro)
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"]).