[Pkg-privacy-maintainers] Proposal: membership and decision-making process

[Daniel Kahn Gillmor]

thanks for all the clarifications, Ulrike!

I've pushed a dkg/policy-amendment branch to the git repo
(https://salsa.debian.org/pkg-privacy-team/team-processes) that i think
reflects those changes.

I'm attaching a collapsed changeset that shows the differences between
the two versions.  the git history itself breaks the changes down into
sensible bite-size pieces.

i hope this is useful!

  --dkg

ps another detail concern pops up: if you decide to adopt these changes,
   does that reset the clock on the decision-making process?  that's not
   clear here.


diff --git a/pkg-privacy-process.mdwn b/pkg-privacy-process.mdwn
index 13bc878..d9b644a 100644
--- a/pkg-privacy-process.mdwn
+++ b/pkg-privacy-process.mdwn
@@ -7,6 +7,12 @@
   (b) team member: individual member of the team
   (c) team administrator: team member with additional administrative
       rights on the team's infrastructure
+  (d) mailing list: the mailing list used by the Debian Privacy Tools
+      Maintainers, currently
+      pkg-privacy-maintainers at lists.alioth.debian.org
+  (e) GitLab group: the public collection of git repositories and other
+      metadata jointly controlled by the group, currently
+      https://salsa.debian.org/groups/pkg-privacy-team
 
 1. Membership process
 ---------------------
@@ -51,37 +57,71 @@
 2. Decision making process
 --------------------------
 
-Our goal is to make decisions by consensus; we will do this by this process.
-
-  (a) The proposal is passed if there are 1/3 (rounding up) of the
-      team members, or 3 team members, whichever is the smallest,
-      voting positively at the time of the proposal; and no
-      negative votes.
-  (b) We have a time limit of two weeks for proposals, after this
-      point the proposal is dropped if there are not enough
-      positive votes.
-  (c) The decision-making time is automatically increased at the
-      request of a team member, if they give a reason for the
+2.1 Consensus:
+
+  Our goal is to make decisions by consensus; we will do this by this process.
+
+  (a) When a proposal is made, it has an initial time limit.  At the
+      conclusion of the time limit, the proposal is either accepted or
+      dropped.
+  (b) The earliest time limit for any proposal is two weeks from when
+      the proposal is made.
+  (c) The time limit can be automatically increased at the
+      request of any team member, if they give a reason for the
       extension and a specific date for the new deadline.
+  (d) At the end of its time limit, the proposal is accepted if there
+      are positive votes from 1/3 (rounding up) of the team members at
+      the time the proposal is made, or 3 team members, whichever is
+      the smallest; and no negative votes.
+
+2.2 Examples:
+
+  The decision-making process can be used to make any sort of decision
+  for the group.  This includes, for example:
+
+  (a) adding team members
+  (b) orphaning or removing packages
+  (c) amending this process document
+
+2.3 Exceptions:
+
+  This document describes two specific actions that do not follow the
+  standard decision-making process:
+
+  (a) member expulsion (§1.2)
+  (b) package adoption (§3.3)
 
 3. Tools
 --------
 
 3.1 Repositories:
 
-  a) Team members are given commit rights on all team-maintained
-     packages repositories (e.g. GitLab "developer" or "maintainer").
-     They may choose to opt-out entirely or partially, e.g.
-     following the principle of least privilege.
-  b) Team administrators can give or revoke rights on the
-     infrastructure used by the team (e.g. GitLab "owner").
+  (a) Team members are given commit rights on all team-maintained
+      packages repositories (e.g. GitLab "developer" or "maintainer").
+      They may choose to opt-out entirely or partially, e.g.
+      following the principle of least privilege.
+  (b) Team administrators can give or revoke rights on the
+      infrastructure used by the team (e.g. GitLab "owner").
 
 3.2 Mailing list:
 
-    The mailing list is public. Votes related to the decision making
-    process happen on the mailing list.
-
-3.3 Packages:
-
-  Team members, and only them, may add to the set of team
-  maintained packages.
+  (a) The mailing list is public. Votes related to the decision making
+      process happen on the mailing list.
+  (b) An e-mail message that is intended to be a vote on a proposal
+      should clearly indicate the proposal being voted on, and should
+      include explicit language in favor or opposition.  For example,
+      "I support this proposal." or "I oppose this proposal." are
+      considered votes.  A message that does not explicitly indicate
+      support or opposition will not be considered a vote.
+
+3.3 Adopting Packages:
+
+  (a) As a special exception to the decision-making process, any team
+      member can unilaterally add to the set of team-maintained
+      packages by announcing it on the mailing list.  The announcement
+      should include the name of the source package, and a brief
+      description of how the package relates to the goals of the team.
+  (b) When a package is added the set of team-maintained packages, a
+      new git repository named after the name of the source package
+      should be added to the team GitLab group.
+  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20180726/03c15051/attachment.sig>