Update: tweak constitution based on feedback so far

1 files changed, 42 insertions, 10 deletions

diff --git a/governance.mdwn b/governance.mdwn
index c523747..79553a5 100644
--- a/governance.mdwn
+++ b/governance.mdwn
@@ -3,6 +3,15 @@
 
 > **THIS IS A DRAFT. IT IS NOT OFFICIAL YET.**
 
+Changes from first published version:
+
+* Added a reference to [lazy consensus][], suggested by Russ.
+* Voting membership gets automatically renewed by voting, suggested by
+  Russ.
+* Added a note that the constitution is likely to change as the
+  project grows.
+* If there's only one voting member, they are also the secretary.
+
 
 Ick constitution
 =============================================================================
@@ -17,6 +26,14 @@ project governance structure is informally based on the principle of
 principle, to help the project grow, to make it easier for new
 contributors to join the project, and to avoid misunderstandings.
 
+This is the first version of the constitution. It is expected to grow
+as the project gets more contributors. A probable change is to start
+using a [Debian-style condorcet][] voting method. It is overkill with
+only a handful of contributors, but will become more imporant later
+on.
+
+[Debian-style condorcet]: https://www.debian.org/vote/
+
 Levels of membership
 -----------------------------------------------------------------------------
 
@@ -55,6 +72,15 @@ If a mundane decision is challenged, the project aims to find a
 **consensus decision**. Consensus decisions are documented on a
 project website, and marked as such.
 
+To make rough consensus easier to achieve, the project follows the
+[lazy consensus][] approach. If you don't think a change is
+controversial, just do it. We use version control, changes are easy to
+revert. If you're not entirely sure, announce that you're going to
+make the change in three days, which gives everyone time to object.
+Details of this may be specified as a project decision.
+
+[lazy consensus]: https://rave.apache.org/docs/governance/lazyConsensus.html
+
 If consensus is not reached, or is challenged by a voting member, the
 project will **vote** on the matter. This is called a **formal
 decision**. Formal decisions are documented on a project website, and
@@ -64,12 +90,13 @@ Voting procedure
 -----------------------------------------------------------------------------
 
 The **project secretary** is chosen by voting by the voting members
-from among the voting members. The first secretary is Lars Wirzenius,
-the project founder. Candidates nominate themselves, or by other
-voting members with the candidate's approval. The secretary has the
-duty to conduct votes in a suitable manner. Votes are decided by
-**simple majority**, and voting members have an **equal vote**. In
-case of a tie, the project secretary casts the decisive vote.
+from among the voting members. The secretary must themselves be a
+voting member for the duration of their term. Candidates nominate
+themselves, or by other voting members with the candidate's approval.
+The secretary has the duty to conduct votes in a suitable manner.
+Votes are decided by **simple majority**, and voting members have an
+**equal vote**. In case of a tie, the project secretary casts the
+decisive vote.
 
 Voting members may suggest options for the ballot. The secretary
 decides what the ballot should be, announces the vote on a suitable
@@ -97,7 +124,11 @@ Voting membership and the position of secretary and team delegations
 are **time limited**, and **expire automatically** with no further
 action. Memberships expire one by one in order of earliest membership
 first. The last membership does not expire, as that would leave the
-project without voters.
+project without voters. If the project only has one voting member,
+that member is automatically also the secretary.
+
+The point of the automatic expiration is to avoid having inactive
+former contributors as voting members indefinitely.
 
 The **terms end on the following dates**, except terms do not end
 automatically within their first three months:
@@ -109,9 +140,10 @@ automatically within their first three months:
 On each date, the term ends at 23:59:59 in the UTC time zone.
 
 Voting membership, secretaryship, and team delegation may be renewed
-by a vote. There is no limit on how many times renewal happens. The
-point of the automatic expiration is to avoid having inactive former
-contributors as voting members indefinitely.
+by a vote. There is no limit on how many times renewal may happen.
+
+Voting membership gets automatically renewed if the member has voted
+at least once in the preceding 12 months.
 
 It is the duty of the secretary to arrange new votes to renew terms in
 time before the terms end.