open policy topics
(Just in case someone is intrested: I was extremely busy at work for the
last 6 weeks so I didn't had much time to work on Debian. However, I have
3 weeks holidays now and I'm planning to catch up with the open policy
discussions soon.)
The list of open topics is so long that I decided to post it here for your
information. I'll start working on these issues by priority. Of course,
everyone should feel free to discuss either topic in any order, but please
don't expect that I can "manage" all these discussions at the same time :)
If you know of an important open policy topic which is missing on my list,
feel free to contact me. (Either I forgot about the topic or I didn't
consider it important enough.)
Thanks,
Chris
(Note, that the topic titles are shortened very much! Of course, the
actual policy text will be much more detailed.)
Topics which affect hamm and thus have to be resolved ASAP
==========================================================
1. Shared library packages must call ldconfig in the postinst script.
(see bug#20515)
-> I haven't seen objections to my previous posting. Thus, I'll
prepare a policy change and include it in the next policy weekly for
approval.
2. Pre-Depends and Essentials
-> People seem to agree that Essential packages always have to use
Pre-Depends instead of Depends. There may be single exceptions--but these
have to be approved by debian-devel.
3. Manual pages for X11 games have to be in /usr/man/man6, not
/usr/X11R6/man/man6
4. Symbolic links between top-level directories
5. Several small fixes/updates (e.g., /etc/init.d policy, emacs
policy)
Topics which are less URGENT and can wait until hamm is out
===========================================================
1. Migration process from FSSTND to FHS
2. Fix/clarify the terms "conffiles" and "configuration files"
3. Specify policy for "experimental" distribution
(`What goes into experimental' is a FAQ)
4. Discuss `One Maintainer per Package' policy again
5. Each developer must have a working @debian.org address
6. New control fields (Keywords:, Origin:, etc.)
7. Policy for file names (name space pollution, etc.)
8. Syslog facilities/priorities
9. Cron jobs may not emit messages to stdout/stderr unless in error
situations
10. doc-base menu structure
11. several new VP's have been requested
12. Should package contain settings for "Section:" and "Priority:" ?
13. Document what the VP `mail-transport-agent' provides in detail
14. FHS: request removal of /usr/games ??
15. Do we allow/encourage the use of "env" ??
16. policy for -rpath?
17. dynamically linking vs. statically linking
18. UUCP-lock policy
19. document how `essential virtual packages' can be registered (via
dependency from base-files)
20. how to parse another program's output (set LOCALE=C)
21. dependency policy:
- do we allow/disallow indirect dependencies?
- conflict loops depreciated?
22. general policy on bug report handling
23. documentation about why a package is in non-free/contrib
24. how to handle "extra" files
-- Christian Schwarz
schwarz@monet.m.isar.de, schwarz@schwarz-online.com,
Don't know Perl? schwarz@debian.org, schwarz@mathematik.tu-muenchen.de
Visit PGP-fp: 8F 61 EB 6D CF 23 CA D7 34 05 14 5C C8 DC 22 BA
http://www.perl.com http://fatman.mathematik.tu-muenchen.de/~schwarz/
--
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: