A mechanism for updating Debian Policy documents - Introduction, and Administrivia
[ previous ]
[ Contents ]
[ 1 ]
[ 2 ]
[ 3 ]
[ next ]
A mechanism for updating Debian Policy documents
Chapter 1 - Introduction, and Administrivia
This document documents the current practice followed in updating Debian Policy
documents. This mechanism has been designed for dealing with policy changes
that are light weight and can be decided upon within the policy group, by near
consensus. In most day-to-day cases, the Policy group should and must be able
to conduct Policy discussions and amendments without the intervention of the
Technical Committee or other Constitutional issues. Only in cases of extreme
dispute (formal objections) should the intervention of Constitutional bodies
come into play. In any other situation, the Policy group should be able to
conduct business unfettered. A consequence of this goal is that formal
objections should not be used lightly, else this mechanism shall be
ineffective.
It should be noted that the team responsible for the task of updating policy
does not act as author or editor of Policy itself, that is the task of the
Debian Policy mailing list.
In the following, the term developer refers to registered Debian
developers.