imported mails

1 files changed, 364 insertions, 0 deletions

diff --git a/tickets/84022c943cd848fd9ec630b8979dab3d/Maildir/new/1514076605.M558840P12443Q1.koom b/tickets/84022c943cd848fd9ec630b8979dab3d/Maildir/new/1514076605.M558840P12443Q1.koom
new file mode 100644
index 0000000..938b31c
--- /dev/null
+++ b/tickets/84022c943cd848fd9ec630b8979dab3d/Maildir/new/1514076605.M558840P12443Q1.koom
@@ -0,0 +1,364 @@
+Return-Path: <lare.lekman@gmail.com>
+X-Original-To: ick-devel@liw.fi
+Delivered-To: distix@pieni.net
+Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a])
+	by pieni.net (Postfix) with ESMTPS id E5137406FF;
+	Sat, 23 Dec 2017 19:20:51 +0000 (UTC)
+Received: by mail-lf0-x22a.google.com with SMTP id u84so14706179lff.7;
+        Sat, 23 Dec 2017 11:20:51 -0800 (PST)
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
+        d=gmail.com; s=20161025;
+        h=mime-version:subject:from:in-reply-to:date:cc
+         :content-transfer-encoding:message-id:references:to;
+        bh=Lbx/pMWTyy0XDCW59XWaSV4cAZ7oH6B7X4synXaSNE4=;
+        b=fE+75RiuUAJZx/Ay02jQQGP7sw3nFYi0i9rEJ6tv05h/pV+FdE2UqdwSaaDTpIYU4B
+         gUpKt0P9vbqDag3ZI2qaR6JD8BG6OUwXGhAM3Kk8w6p1MArof2Ybe/RZfC88+gEZjg68
+         8vwihTdD1k1a/RLpKXOY+Z8ZbwexDK29tpakSeziU7ydEhP1Lcay7vpmHw6dvNMJ17Ws
+         /VlrCnRDQaEO7rAuNSOORIiRpiJqq6D0nD8/esXrLiyAg1vm2kBOPMJDyVzx4TaBe6yQ
+         XBRxLliHj3dlkJcoU3EiKbc6AphInQln7jtqCTa5Z2Iv+jRHsxxihFHOqt9geqck2FWx
+         oOhg==
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
+        d=1e100.net; s=20161025;
+        h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc
+         :content-transfer-encoding:message-id:references:to;
+        bh=Lbx/pMWTyy0XDCW59XWaSV4cAZ7oH6B7X4synXaSNE4=;
+        b=X0jeIJYnTNxf/fW2pqyjG91EhStXxeJGbxmU2+R4+BUn3QkZ/Y2FpuL98q/fFS+1bM
+         2NVxpuzpIGRPgmOet9znaArHq0MII5EKUtvMqQMSyB5Gxj0MgtZ3qbRSTSyxNeC2A3mw
+         B0TdHXTx/u3CEdpdhQ/WPnLzAq9fPh/mKwl1/vW0/qPco780u73QVUjf2xZItGfjbYS6
+         wQFn03ocWVCISBZR8MQzvU0zrNyDoMix+runJ+K6he1OhLNC55i3li2myg07rSY0S0wX
+         JYPViv9ET5KH9IiZZ3L3DIyfvVCMTZSA/b37u3+9mQN69/kScws3ro/j53erFfA/Ld7m
+         IcUg==
+X-Gm-Message-State: AKGB3mLb737rfhuR3EjcffSifUG4YbSYgIWoCCYQ75+EKzNtrrvgB5tr
+	nT5hwtQRlY06u+xAWVEgzqRQhI+f
+X-Google-Smtp-Source: ACJfBovdz2VlBrcMRZAqqhlKyDklq8YGFfO5msTOUOEQF1WaoA1gqOUneCMqYwacX8WRE+1+rdtFyA==
+X-Received: by 10.25.113.4 with SMTP id m4mr9370678lfc.35.1514056850869;
+        Sat, 23 Dec 2017 11:20:50 -0800 (PST)
+Received: from [192.168.8.119] (mobile-access-5d6ab6-39.dhcp.inet.fi. [93.106.182.39])
+        by smtp.gmail.com with ESMTPSA id u10sm4916000lju.25.2017.12.23.11.20.49
+        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
+        Sat, 23 Dec 2017 11:20:49 -0800 (PST)
+Content-Type: multipart/alternative;
+	boundary=Apple-Mail-2C04E516-7B26-4FC0-96DC-281DCA63E2C8
+Mime-Version: 1.0 (1.0)
+Subject: Re: On project governance
+From: Lare Lekman <lare.lekman@gmail.com>
+X-Mailer: iPhone Mail (15C153)
+In-Reply-To: <20171220213303.drdmrnpscvoaz4l7@exolobe3>
+Date: Sat, 23 Dec 2017 21:20:48 +0200
+Cc: Ick develoment <ick-devel@liw.fi>
+Content-Transfer-Encoding: 7bit
+Message-Id: <105C7298-D800-44A6-82E6-1F7AA2088570@gmail.com>
+References: <20171220213303.drdmrnpscvoaz4l7@exolobe3>
+To: Lars Wirzenius <liw@liw.fi>
+
+
+--Apple-Mail-2C04E516-7B26-4FC0-96DC-281DCA63E2C8
+Content-Type: text/plain;
+	charset=utf-8
+Content-Transfer-Encoding: quoted-printable
+
+Without much prior Open Source governing experience, I would say that the te=
+xt is spot on: Easy to understand, fair, and intelligent.
+
+The levels of agreement (mundane decisions, group discussion, and voting) ar=
+e especially interesting and useful also to my own Agile coaching and traini=
+ng workshops.  :)
+
+I=E2=80=99m curious, did / does Linux development have similar decision-maki=
+ng philosophy and levels of agreement?
+
+Merry Christmas to All!
+Lare
+
+Agile Trainer & Coach | http://lekman.fi | +358 40 849 5117
+
+> Lars Wirzenius <liw@liw.fi> kirjoitti 20.12.2017 kello 23.33:
+>=20
+> I wrote this today. What do you all think?
+>=20
+> [[!meta title=3D"Ick&mdash;governance"]]
+>=20
+>=20
+>> **THIS IS A DRAFT. IT IS NOT OFFICIAL YET.**
+>=20
+>=20
+> Ick constitution
+> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+
+>=20
+> Introduction
+> --------------------------------------------------------------------------=
+---
+>=20
+> This constitution is the formal rules of the Ick project. The Ick
+> project develops the Ick software, for continuous integration. The
+> project governance structure is informally based on the principle of
+> **do-ocracy**: those who do, decide. This constitution formalises the
+> principle, to help the project grow, to make it easier for new
+> contributors to join the project, and to avoid misunderstandings.
+>=20
+> Levels of membership
+> --------------------------------------------------------------------------=
+---
+>=20
+> There are two levels of membership in the project: **contributors**
+> and **voting members**. Contributors are all those who work to the
+> project in order to make the Ick software, its website, documentation,
+> other deliverables, or the project itself better. Voting members have
+> the power to collectively make any decision of the project by voting
+> on it.
+>=20
+> **Voting members are chosen by voting.** Candidates are nominated by
+> themselves or by voting members, with approval of candidate. Voting
+> membership may not be inflicted upon anyone without their **explicit
+> approval**.
+>=20
+> Voting membership may be revoked by a vote.
+>=20
+> No contributors or voting member is required to do work for the
+> project, and the project cannot compel anyone to do anything. The
+> project may, via the constituion of a formal decision, forbid
+> something from being done in the context of a project, or require that
+> if a thing is done, it gets done in a particular way.
+>=20
+> Decision making
+> --------------------------------------------------------------------------=
+---
+>=20
+> Most decisions in the project are made by contributors as part of the
+> work they do to contribute. These are called **mundane decisions**,
+> and include things like how to structure a piece of code or
+> documentation, how to name some component, etc. Mundane decisions do
+> not normally need to be documented formally, but can be, if the
+> contributor thinks it useful.
+>=20
+> If a mundane decision is challenged, the project aims to find a
+> **rough consensus** on the matter via discussion. This is called a
+> **consensus decision**. Consensus decisions are documented on a
+> project website, and marked as such.
+>=20
+> 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
+> marked as such.
+>=20
+> Voting procedure
+> --------------------------------------------------------------------------=
+---
+>=20
+> 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.
+>=20
+> Voting members may suggest options for the ballot. The secretary
+> decides what the ballot should be, announces the vote on a suitable
+> project forum, and declares how a vote is to be cast. The **voting
+> period is 7 days**. The secretary receives votes, counts them, and
+> announces the result, and documents the decision on the project
+> website. **Votes are made public** at that time, if not earlier.
+>=20
+> Team delegations
+> --------------------------------------------------------------------------=
+---
+>=20
+> Responsibility of making decisions about an area or aspect of the
+> project may be **delegated to a team** by a vote among the voting
+> members. The decision shall name all members of the team and the scope
+> of the delegation. The team members may be any contributors, not just
+> formal members. Decisions within the team are made in the same manner
+> as by the project as a whole, with contributors voting as if they were
+> voting members. The team's consensus and formal decisions shall be
+> documented in the same way as project decisions.
+>=20
+> Time and term limitations
+> --------------------------------------------------------------------------=
+---
+>=20
+> 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.
+>=20
+> The **terms end on the following dates**, except terms do not end
+> automatically within their first three months:
+>=20
+> - voting membership ends September 1
+> - position of secretary ends March 1
+> - team delegations ends June 1.
+>=20
+> On each date, the term ends at 23:59:59 in the UTC time zone.
+>=20
+> 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.
+>=20
+> It is the duty of the secretary to arrange new votes to renew terms in
+> time before the terms end.
+>=20
+>=20
+> Other Ick governance
+> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+
+>=20
+> * Technical policy: how the software gets developed, programming
+>  languages, version control, issue tracking, website maintenance,
+>  etc. This will be decided by the project following procedures
+>  specified by the constitution.
+>=20
+> * Code of conduct: This will be a formal project decision. A delegated
+>  team may be given responsibility of enforcement. I'm personally in
+>  favour of something like what Gitano uses.
+>=20
+>=20
+> --=20
+> I want to build worthwhile things that might last. --joeyh
+
+--Apple-Mail-2C04E516-7B26-4FC0-96DC-281DCA63E2C8
+Content-Type: text/html;
+	charset=utf-8
+Content-Transfer-Encoding: quoted-printable
+
+<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
+utf-8"></head><body dir=3D"auto"><div><span></span></div><div>Without much p=
+rior Open Source governing experience, I would say that the text is spot on:=
+ Easy to understand, fair, and intelligent.</div><div><br></div><div>The lev=
+els of agreement (mundane decisions, group discussion, and voting) are espec=
+ially interesting and useful also to my own Agile coaching and training work=
+shops. &nbsp;:)</div><div><br></div><div>I=E2=80=99m curious, did / does Lin=
+ux development have similar decision-making philosophy and levels of agreeme=
+nt?</div><div><br></div><div>Merry Christmas to All!</div><div>Lare<br><br><=
+div id=3D"AppleMailSignature"><div class=3D"gmail_signature" data-smartmail=3D=
+"gmail_signature"><div dir=3D"ltr"><span style=3D"border-collapse: collapse;=
+"><div><div><span style=3D"background-color: rgba(255, 255, 255, 0);">Agile T=
+rainer &amp; Coach |&nbsp;<u><a href=3D"http://lekman.fi/" target=3D"_blank"=
+>http://lekman.fi</a></u>&nbsp;|&nbsp;<a href=3D"tel:+358%2040%20849%205117"=
+ dir=3D"ltr" x-apple-data-detectors=3D"true" x-apple-data-detectors-type=3D"=
+telephone" x-apple-data-detectors-result=3D"1">+358 40 849 5117</a></span></=
+div></div><div style=3D"font-family: arial, sans-serif; font-size: 13px; -we=
+bkit-text-size-adjust: auto;"><div></div></div></span></div></div></div><div=
+><br>Lars Wirzenius &lt;<a href=3D"mailto:liw@liw.fi">liw@liw.fi</a>&gt; kir=
+joitti 20.12.2017 kello 23.33:<br><br></div><blockquote type=3D"cite"><div><=
+span>I wrote this today. What do you all think?</span><br><span></span><br><=
+span>[[!meta title=3D"Ick&amp;mdash;governance"]]</span><br><span></span><br=
+><span></span><br><blockquote type=3D"cite"><span>**THIS IS A DRAFT. IT IS N=
+OT OFFICIAL YET.**</span><br></blockquote><span></span><br><span></span><br>=
+<span>Ick constitution</span><br><span>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</span><br><span></span><br><span>Introd=
+uction</span><br><span>-----------------------------------------------------=
+------------------------</span><br><span></span><br><span>This constitution i=
+s the formal rules of the Ick project. The Ick</span><br><span>project devel=
+ops the Ick software, for continuous integration. The</span><br><span>projec=
+t governance structure is informally based on the principle of</span><br><sp=
+an>**do-ocracy**: those who do, decide. This constitution formalises the</sp=
+an><br><span>principle, to help the project grow, to make it easier for new<=
+/span><br><span>contributors to join the project, and to avoid misunderstand=
+ings.</span><br><span></span><br><span>Levels of membership</span><br><span>=
+----------------------------------------------------------------------------=
+-</span><br><span></span><br><span>There are two levels of membership in the=
+ project: **contributors**</span><br><span>and **voting members**. Contribut=
+ors are all those who work to the</span><br><span>project in order to make t=
+he Ick software, its website, documentation,</span><br><span>other deliverab=
+les, or the project itself better. Voting members have</span><br><span>the p=
+ower to collectively make any decision of the project by voting</span><br><s=
+pan>on it.</span><br><span></span><br><span>**Voting members are chosen by v=
+oting.** Candidates are nominated by</span><br><span>themselves or by voting=
+ members, with approval of candidate. Voting</span><br><span>membership may n=
+ot be inflicted upon anyone without their **explicit</span><br><span>approva=
+l**.</span><br><span></span><br><span>Voting membership may be revoked by a v=
+ote.</span><br><span></span><br><span>No contributors or voting member is re=
+quired to do work for the</span><br><span>project, and the project cannot co=
+mpel anyone to do anything. The</span><br><span>project may, via the constit=
+uion of a formal decision, forbid</span><br><span>something from being done i=
+n the context of a project, or require that</span><br><span>if a thing is do=
+ne, it gets done in a particular way.</span><br><span></span><br><span>Decis=
+ion making</span><br><span>-------------------------------------------------=
+----------------------------</span><br><span></span><br><span>Most decisions=
+ in the project are made by contributors as part of the</span><br><span>work=
+ they do to contribute. These are called **mundane decisions**,</span><br><s=
+pan>and include things like how to structure a piece of code or</span><br><s=
+pan>documentation, how to name some component, etc. Mundane decisions do</sp=
+an><br><span>not normally need to be documented formally, but can be, if the=
+</span><br><span>contributor thinks it useful.</span><br><span></span><br><s=
+pan>If a mundane decision is challenged, the project aims to find a</span><b=
+r><span>**rough consensus** on the matter via discussion. This is called a</=
+span><br><span>**consensus decision**. Consensus decisions are documented on=
+ a</span><br><span>project website, and marked as such.</span><br><span></sp=
+an><br><span>If consensus is not reached, or is challenged by a voting membe=
+r, the</span><br><span>project will **vote** on the matter. This is called a=
+ **formal</span><br><span>decision**. Formal decisions are documented on a p=
+roject website, and</span><br><span>marked as such.</span><br><span></span><=
+br><span>Voting procedure</span><br><span>----------------------------------=
+-------------------------------------------</span><br><span></span><br><span=
+>The **project secretary** is chosen by voting by the voting members</span><=
+br><span>from among the voting members. The first secretary is Lars Wirzeniu=
+s,</span><br><span>the project founder. Candidates nominate themselves, or b=
+y other</span><br><span>voting members with the candidate's approval. The se=
+cretary has the</span><br><span>duty to conduct votes in a suitable manner. V=
+otes are decided by</span><br><span>**simple majority**, and voting members h=
+ave an **equal vote**. In</span><br><span>case of a tie, the project secreta=
+ry casts the decisive vote.</span><br><span></span><br><span>Voting members m=
+ay suggest options for the ballot. The secretary</span><br><span>decides wha=
+t the ballot should be, announces the vote on a suitable</span><br><span>pro=
+ject forum, and declares how a vote is to be cast. The **voting</span><br><s=
+pan>period is 7 days**. The secretary receives votes, counts them, and</span=
+><br><span>announces the result, and documents the decision on the project</=
+span><br><span>website. **Votes are made public** at that time, if not earli=
+er.</span><br><span></span><br><span>Team delegations</span><br><span>------=
+-----------------------------------------------------------------------</spa=
+n><br><span></span><br><span>Responsibility of making decisions about an are=
+a or aspect of the</span><br><span>project may be **delegated to a team** by=
+ a vote among the voting</span><br><span>members. The decision shall name al=
+l members of the team and the scope</span><br><span>of the delegation. The t=
+eam members may be any contributors, not just</span><br><span>formal members=
+. Decisions within the team are made in the same manner</span><br><span>as b=
+y the project as a whole, with contributors voting as if they were</span><br=
+><span>voting members. The team's consensus and formal decisions shall be</s=
+pan><br><span>documented in the same way as project decisions.</span><br><sp=
+an></span><br><span>Time and term limitations</span><br><span>--------------=
+---------------------------------------------------------------</span><br><s=
+pan></span><br><span>Voting membership and the position of secretary and tea=
+m delegations</span><br><span>are **time limited**, and **expire automatical=
+ly** with no further</span><br><span>action. Memberships expire one by one i=
+n order of earliest membership</span><br><span>first. The last membership do=
+es not expire, as that would leave the</span><br><span>project without voter=
+s.</span><br><span></span><br><span>The **terms end on the following dates**=
+, except terms do not end</span><br><span>automatically within their first t=
+hree months:</span><br><span></span><br><span>- voting membership ends Septe=
+mber 1</span><br><span>- position of secretary ends March 1</span><br><span>=
+- team delegations ends June 1.</span><br><span></span><br><span>On each dat=
+e, the term ends at 23:59:59 in the UTC time zone.</span><br><span></span><b=
+r><span>Voting membership, secretaryship, and team delegation may be renewed=
+</span><br><span>by a vote. There is no limit on how many times renewal happ=
+ens. The</span><br><span>point of the automatic expiration is to avoid havin=
+g inactive former</span><br><span>contributors as voting members indefinitel=
+y.</span><br><span></span><br><span>It is the duty of the secretary to arran=
+ge new votes to renew terms in</span><br><span>time before the terms end.</s=
+pan><br><span></span><br><span></span><br><span>Other Ick governance</span><=
+br><span>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+=3D=3D</span><br><span></span><br><span>* Technical policy: how the software=
+ gets developed, programming</span><br><span> &nbsp;languages, version contr=
+ol, issue tracking, website maintenance,</span><br><span> &nbsp;etc. This wi=
+ll be decided by the project following procedures</span><br><span> &nbsp;spe=
+cified by the constitution.</span><br><span></span><br><span>* Code of condu=
+ct: This will be a formal project decision. A delegated</span><br><span> &nb=
+sp;team may be given responsibility of enforcement. I'm personally in</span>=
+<br><span> &nbsp;favour of something like what Gitano uses.</span><br><span>=
+</span><br><span></span><br><span>-- </span><br><span>I want to build worthw=
+hile things that might last. --joeyh</span><br></div></blockquote></div></bo=
+dy></html>=
+
+--Apple-Mail-2C04E516-7B26-4FC0-96DC-281DCA63E2C8--