From patchwork Mon Sep 12 16:20:11 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Lars Kurth X-Patchwork-Id: 9326989 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id A7F5460839 for ; Mon, 12 Sep 2016 16:23:36 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 9A4E928E35 for ; Mon, 12 Sep 2016 16:23:36 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 8F11328E42; Mon, 12 Sep 2016 16:23:36 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=2.0 tests=BAYES_00, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id BF17225250 for ; Mon, 12 Sep 2016 16:23:34 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bjTyJ-0006kt-JQ; Mon, 12 Sep 2016 16:20:39 +0000 Received: from mail6.bemta6.messagelabs.com ([193.109.254.103]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bjTyH-0006kM-Jc for xen-devel@lists.xenproject.org; Mon, 12 Sep 2016 16:20:37 +0000 Received: from [193.109.254.147] by server-9.bemta-6.messagelabs.com id 5F/4A-28857-5D5D6D75; Mon, 12 Sep 2016 16:20:37 +0000 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRWlGSWpSXmKPExsWS0XRdVffK1Wv hBruvilt83zKZyYHR4/CHKywBjFGsmXlJ+RUJrBmT+jYyFrxxqWhoncbcwPjOsouRi0NI4CSj xIN371ghnIuMEje+n2buYuTkYBPQkDj2sBnMFhFQkri3ajITiM0s4CQxbfU2NhBbWMBDYuWTX 6wgNouAqsS83W/A4rwCLhI7X/aC9UoI6ErcvXkBqIaDg1PAVWLF2iSQsBBQydKGFWwTGLkXMD KsYtQoTi0qSy3SNTbQSyrKTM8oyU3MzNE1NDDTy00tLk5MT81JTCrWS87P3cQI9C8DEOxg/Ls 28BCjJAeTkihvkuC1cCG+pPyUyozE4oz4otKc1OJDjDIcHEoSvLFXgHKCRanpqRVpmTnAQINJ S3DwKInwRoKkeYsLEnOLM9MhUqcYFaXEeZeBJARAEhmleXBtsOC+xCgrJczLCHSIEE9BalFuZ gmq/CtGcQ5GJWHemyBTeDLzSuCmvwJazAS0+OnWyyCLSxIRUlINjDXX987cIXb1Aefj5OS3M3 Zt+hKV7a8emvNqkq+UzuUqVqkfpSfkI6deWhgg8/Dn+5+aLId0QrdunrouK+ISw17/9Zkflx7 T6DLX0v2+pGyrib3q3jvVM1+aHOWS7Qu7faIz7ORV/lLFIwWLAz/OOuiZ+Pbpo1VSBs/+irLE 9IrVTP/7oHNK6FolluKMREMt5qLiRAAlKYZsaQIAAA== X-Env-Sender: lars.kurth@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1473697235!6436092!1 X-Originating-IP: [104.130.215.37] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 8.84; banners=-,-,- X-VirusChecked: Checked Received: (qmail 54845 invoked from network); 12 Sep 2016 16:20:36 -0000 Received: from mail.xenproject.org (HELO mail.xenproject.org) (104.130.215.37) by server-2.tower-27.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 12 Sep 2016 16:20:36 -0000 Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bjTy9-0003Pr-Qj; Mon, 12 Sep 2016 16:20:29 +0000 Received: from localhost ([127.0.0.1] helo=MacBook-Pro-6.Home) by xenbits.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bjTy8-0000lb-6O; Mon, 12 Sep 2016 16:20:29 +0000 From: Lars Kurth To: xen-devel@lists.xenproject.org Date: Mon, 12 Sep 2016 17:20:11 +0100 Message-Id: <1473697212-3245-3-git-send-email-lars.kurth@citrix.com> X-Mailer: git-send-email 2.5.4 (Apple Git-61) In-Reply-To: <1473697212-3245-1-git-send-email-lars.kurth@citrix.com> References: <1473697212-3245-1-git-send-email-lars.kurth@citrix.com> Cc: Lars Kurth , committers@xenproject.org Subject: [Xen-devel] [PATCH v2 2/3] Added comment sections to highight problem areas X-BeenThere: xen-devel@lists.xen.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" X-Virus-Scanned: ClamAV using ClamSMTP These are marked by ------------------------------------------------------------------------- ... ------------------------------------------------------------------------- blocks that will be removed in the published version Signed-off-by: Lars Kurth --- governance.pandoc | 91 +++++++++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 88 insertions(+), 3 deletions(-) diff --git a/governance.pandoc b/governance.pandoc index 2ce780c..86e4433 100644 --- a/governance.pandoc +++ b/governance.pandoc @@ -1,3 +1,4 @@ + This document has come in effect in June 2011 and will be reviewed periodically (see revision sections). The last modification has been made in July 2016. @@ -54,8 +55,23 @@ The Xen Project is a meritocracy. The more you contribute the more responsibility you will earn. Leadership roles in Xen are also merit-based and earned by peer acclaim. + + ------------------------------------------------------------------------------------- + I moved the "Roles" section up and split it into two sections with unmodified content + - Xen Project Wide Roles + - Project Team Roles + ------------------------------------------------------------------------------------- + Xen Project Wide Roles {#roles-global} ---------------------- + + ------------------------------------------------------------------------------------- + MINOR ISSUES TO BE ADDRESSED LATER: + - Sub-projects and Teams would benefit from some forward references to highlight the + difference between incubation mature projects. + - Also we should clarify what assets a sub-project owns. + - Add the role of Community Manager as it used throughout the document + ------------------------------------------------------------------------------------- ### Sub-projects and Teams @@ -103,6 +119,15 @@ behind the project. Project Team Roles {#roles-local} ------------------ + ------------------------------------------------------------------------------------- + ISSUES TO BE ADDRESSED LATER: + - Fix minor Inaccuracies and Improvements + - Allow for customization of roles by sub-projects (but this definition is the default) + - Allow for Security Response Team + - Allow for sub-projects to be lead by a Project Leadership Team (which may include a + Project Lead) + ------------------------------------------------------------------------------------- + ### Maintainers Maintainers own one or several components in the Xen tree. A maintainer reviews @@ -131,6 +156,10 @@ referees should disagreements amongst committers of the project arise. The project lead typically also has write access to resources, such as the web page of a specific project. + ------------------------------------------------------------------------------------- + Moved this section + ------------------------------------------------------------------------------------- + Making Contributions {#contributions} -------------------- @@ -147,18 +176,46 @@ documents: - [Contribution Guidelines](/help/contribution-guidelines.html) -Decision Making, Conflict Resolution, Role Nominations and Elections -{#decisions} + ------------------------------------------------------------------------------------- + Consolidated all Decision Making Related topics into one section + - I changed the order of the sections from ... + "Consensus Decision Making, Conflict Resolution, Elections and Formal Votes" to + "Consensus Decision Making, Formal Votes, Conflict Resolution, Elections" + - I changed header titles and fixed the headline + + Otherwise the relevant sections remain identical, with the exception of comment + sections that I added, which highlight issues that are to be addressed. + ------------------------------------------------------------------------------------- + +Decision Making, Conflict Resolution, Role Nominations and Elections {#decisions} -------------------------------------------------------------------- + ------------------------------------------------------------------------------------- + ISSUES TO BE ADDRESSED LATER: + - Add a pre-amble explaining the different decision making mechanisms and when they + apply + - Add a section about review and commit, which is the primary means of making + code related decisions + ------------------------------------------------------------------------------------- + ### Consensus Decision Making + ------------------------------------------------------------------------------------- + ISSUES TO BE ADDRESSED LATER: + - The "Consensus Decision Making" section is totally wrong. It does not describe + "Lazy Consensus" + ------------------------------------------------------------------------------------- + Sub-projects or teams hosted on Xenproject.org are normally auto-governing and driven by the people who volunteer for the job. This functions well for most cases. When more formal decision making and coordination is required, decisions are taken with a lazy consensus approach: a few positive votes with no negative vote are enough to get going. + ------------------------------------------------------------------------------------- + - Introduce -2 to +2 voting under a new section + ------------------------------------------------------------------------------------- + Voting is done with numbers: - +1 : a positive vote @@ -173,6 +230,13 @@ be addressed. ### Conflict Resolution + ------------------------------------------------------------------------------------- + ISSUES TO BE ADDRESSED LATER: + - Generalise refereeing in terms of Project Leadership instead of specific roles + - Also some examples for sPecific situations that have happened in the past may be + useful + ------------------------------------------------------------------------------------- + #### Refereeing Sub-projects and teams hosted on Xenproject.org are not democracies but @@ -196,6 +260,11 @@ mature projects will hold a private majority vote. If the vote is tied, the [Xen Project Advisory Board](/join.html) will break the tie through a casting vote. + ------------------------------------------------------------------------------------- + Changed headline structure: h2 to h3 + Removed Formal Votes from headline as it has been moved into a separate section + ------------------------------------------------------------------------------------- + ### Elections #### Maintainer Elections @@ -246,12 +315,23 @@ above. Formal Votes {#formal-votes} ------------ + ------------------------------------------------------------------------------------- + ISSUES TO BE ADDRESSED LATER: + - Local votes should be handled elsewhere: this section should only cover global + decision making + - Better specify scope : when are Formal Votes applicable + - In fact we do not have any clear rules for tallying votes (do votes have to be + unanimous or not) + - Note that the voting eligibility is maintainers? Do we want to retain this? + I assume NO, as in practive we never did this. + ------------------------------------------------------------------------------------- + Sometimes it is necessary to conduct formal voting within the community (outside of elections). Formal votes are necessary when processes and procedures are introduced or changed, or as part of the [Project Governance](#project-governance). Who is eligible to vote, depends on whether the scope of a process or procedure is **local** to a sub-project or team, or -whether it affects **all sub-projects** (or in other words, is **global**). +whether it affects **all sub-projects** (or in other words, is** global**). Examples of local scope is the [Security Policy](/security-policy.html) which applies to the [Hypervisor Project](/developers/teams/hypervisor.html) only. Examples of global scope are changes to this document or votes outlined in the @@ -280,6 +360,11 @@ private vote. Public review and voting should be open for a minimum of a week each. For voting a traceable poll mechanism (e.g. voting form that keeps auditable and tamper proof records) must be used. Voting follows the conventions as laid out in "Principle: Consensus Decision Making". + + ------------------------------------------------------------------------------------- + ISSUES TO BE ADDRESSED LATER: + - Verify terminology in light of changes above + ------------------------------------------------------------------------------------- Project Governance {#project-governance} ------------------