-+ Commit access to the Git repository and uploads of the debian-policy
- package itself, which makes them responsible for debian-policy as a
- package in Debian and for making final decisions about when a new
- version is released and what bits go into it.
-+ Rejecting proposals. Anyone can argue against a proposal, but only
- Policy delegates can formally reject it.
-+ Counting seconds and weighing objections to proposals to determine
- whether the proposal has sufficient support to be included.
++ Guide the work on the Debian Policy Manual and related documents as a
+ collaborative process where developers review and second or object to
+ proposals, usually on the debian-policy mailing list.
+
++ Count seconds and weight objections to proposals, to determine whether
+ they have reached sufficient consensus to be included, and accept
+ consensual proposals.
+
++ Reject or refer to the Technical Committee proposals that fail to
+ reach consensus.
+
++ Commit changes to the version control system repository used to
+ maintain the Debian Policy Manual and related documents.
+
++ Maintain the "debian-policy" package. As package maintainers, they
+ have the last word on package content, releases, bug reports, etc.