From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 3F386139082 for ; Mon, 27 Nov 2017 20:25:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ABA9DE0ECF; Mon, 27 Nov 2017 20:25:52 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7E4BFE0ECF for ; Mon, 27 Nov 2017 20:25:52 +0000 (UTC) Received: from oystercatcher.gentoo.org (oystercatcher.gentoo.org [148.251.78.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 882ED33BE2E for ; Mon, 27 Nov 2017 20:25:51 +0000 (UTC) Received: from localhost.localdomain (localhost [IPv6:::1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id 2BD98A9AE for ; Mon, 27 Nov 2017 20:25:50 +0000 (UTC) From: "Ulrich Müller" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Ulrich Müller" Message-ID: <1511814279.531ff2d2cab22d3f64ad95bce7bba5fc45332b3b.ulm@gentoo> Subject: [gentoo-commits] data/glep:master commit in: / X-VCS-Repository: data/glep X-VCS-Files: glep-0039.rst X-VCS-Directories: / X-VCS-Committer: ulm X-VCS-Committer-Name: Ulrich Müller X-VCS-Revision: 531ff2d2cab22d3f64ad95bce7bba5fc45332b3b X-VCS-Branch: master Date: Mon, 27 Nov 2017 20:25:50 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Archives-Salt: f72be9d8-dba0-4c26-a7d6-a8ee1c7ae2c4 X-Archives-Hash: 533a7be6321df1a7135af1637ff49a95 commit: 531ff2d2cab22d3f64ad95bce7bba5fc45332b3b Author: Ulrich Müller gentoo org> AuthorDate: Mon Nov 27 20:24:39 2017 +0000 Commit: Ulrich Müller gentoo org> CommitDate: Mon Nov 27 20:24:39 2017 +0000 URL: https://gitweb.gentoo.org/data/glep.git/commit/?id=531ff2d2 glep-0039: Fix whitespace in lists. glep-0039.rst | 147 +++++++++++++++++++++++++++++----------------------------- 1 file changed, 73 insertions(+), 74 deletions(-) diff --git a/glep-0039.rst b/glep-0039.rst index 396fb42..c458450 100644 --- a/glep-0039.rst +++ b/glep-0039.rst @@ -51,27 +51,27 @@ things aren't really so different now. Synopsis of the current system ------------------------------ - * There are 13-15 top-level projects (TLPs). Top-level projects are - comprised of sub-projects, and the goal was that every Gentoo - project would be a sub-project of one of the TLPs. Supposedly each - dev therefore belongs to one or more TLPs. - * Each TLP has at least a "strategic" manager, and potentially also an - "operational" manager. Only the strategic managers vote on global - Gentoo issues. - * The managers of each TLP were appointed by drobbins, the other - TLP managers, or elected by their project members. These managers - have no set term. - * Within each TLP the managers are responsible for making decisions - about the project, defining clear goals, roadmaps, and timelines - for the project, and solving problems that arise within the TLP - (see GLEP 4 for the specific list). - * The strategic TLP managers are also responsible for deciding issues that - affect Gentoo across project lines. The primary mechanism for - handling global-scope issues is the managers' meetings. - * Disciplinary action taken against erring devs is handled by the - "devrel" TLP, unless the dev is a strategic TLP manager. In that - case disciplinary action must be enacted by the other strategic TLP - managers. +* There are 13-15 top-level projects (TLPs). Top-level projects are + comprised of sub-projects, and the goal was that every Gentoo + project would be a sub-project of one of the TLPs. Supposedly each + dev therefore belongs to one or more TLPs. +* Each TLP has at least a "strategic" manager, and potentially also an + "operational" manager. Only the strategic managers vote on global + Gentoo issues. +* The managers of each TLP were appointed by drobbins, the other + TLP managers, or elected by their project members. These managers + have no set term. +* Within each TLP the managers are responsible for making decisions + about the project, defining clear goals, roadmaps, and timelines + for the project, and solving problems that arise within the TLP + (see GLEP 4 for the specific list). +* The strategic TLP managers are also responsible for deciding issues that + affect Gentoo across project lines. The primary mechanism for + handling global-scope issues is the managers' meetings. +* Disciplinary action taken against erring devs is handled by the + "devrel" TLP, unless the dev is a strategic TLP manager. In that + case disciplinary action must be enacted by the other strategic TLP + managers. Problems with the existing system --------------------------------- @@ -106,59 +106,58 @@ Additional problems identified by the current metastructure reform proposals Specification ============= - -A. A project is a group of developers working towards a goal (or a set - of goals). - - * A project exists if it has a maintained Wiki - project page as described below. ("Maintained" means - that the information on the page is factually correct and not - out-of-date.) If the Wiki page isn't maintained, it is presumed - dead. - * It may have one or many leads, and the leads are - selected by the members of the project. This selection must - occur at least once every 12 months, and may occur at any - time. - * It may have zero or more sub-projects. Sub-projects are - just projects that provide some additional structure, and their - Wiki pages are defined as sub-projects of the parent project. - * Not everything (or everyone) needs a project. - * Projects need not be long-term. - * Projects may well conflict with other projects. That's okay. - * Any dev may create a new project just by creating a new project - page on the wiki.gentoo.org (see [#Project_pages]_) and sending - a Request For Comments (RFC) e-mail to gentoo-dev. Note that - this GLEP does not provide for a way for the community at large - to block a new project, even if the comments are wholly negative. - -B. Global issues will be decided by an elected Gentoo council. - - * There will be a set number of council members. (For the - first election that number was set to 7 by acclamation.) - * Council members will be chosen by a general election of all - devs once per year. - * The council must hold an open meeting at least once per month. - * Council decisions are by majority vote of those who show up (or - their proxies). - * If a council member (or their appointed proxy) fails to show up for - two consecutive meetings, they are marked as a slacker. - * If a council member who has been marked a slacker misses any further - meeting (or their appointed proxy doesn't show up), they lose their - position and a new election is held to replace that person. The newly - elected council member gets a 'reduced' term so that the yearly - elections still elect a full group. - * Council members who have previously been booted for excessive slacking - may stand for future elections, including the election for their - replacement. They should, however, justify their slackerness, and - should expect to have it pointed out if they don't do so themselves. - * The 'slacker' marker is reset when a member is elected. - * If any meeting has less than 50% attendance by council members, a new - election for *all* places must be held within a month. The 'one year' - is then reset from that point. - * Disciplinary actions may be appealed to the council. - * A proxy must not be an existing council member, and any single person - may not be a proxy for more than one council member at any given - meeting. +A. A project is a group of developers working towards a goal (or a set + of goals). + + * A project exists if it has a maintained Wiki + project page as described below. ("Maintained" means + that the information on the page is factually correct and not + out-of-date.) If the Wiki page isn't maintained, it is presumed + dead. + * It may have one or many leads, and the leads are + selected by the members of the project. This selection must + occur at least once every 12 months, and may occur at any + time. + * It may have zero or more sub-projects. Sub-projects are + just projects that provide some additional structure, and their + Wiki pages are defined as sub-projects of the parent project. + * Not everything (or everyone) needs a project. + * Projects need not be long-term. + * Projects may well conflict with other projects. That's okay. + * Any dev may create a new project just by creating a new project + page on the wiki.gentoo.org (see [#Project_pages]_) and sending + a Request For Comments (RFC) e-mail to gentoo-dev. Note that + this GLEP does not provide for a way for the community at large + to block a new project, even if the comments are wholly negative. + +B. Global issues will be decided by an elected Gentoo council. + + * There will be a set number of council members. (For the + first election that number was set to 7 by acclamation.) + * Council members will be chosen by a general election of all + devs once per year. + * The council must hold an open meeting at least once per month. + * Council decisions are by majority vote of those who show up (or + their proxies). + * If a council member (or their appointed proxy) fails to show up for + two consecutive meetings, they are marked as a slacker. + * If a council member who has been marked a slacker misses any further + meeting (or their appointed proxy doesn't show up), they lose their + position and a new election is held to replace that person. The newly + elected council member gets a 'reduced' term so that the yearly + elections still elect a full group. + * Council members who have previously been booted for excessive slacking + may stand for future elections, including the election for their + replacement. They should, however, justify their slackerness, and + should expect to have it pointed out if they don't do so themselves. + * The 'slacker' marker is reset when a member is elected. + * If any meeting has less than 50% attendance by council members, a new + election for *all* places must be held within a month. The 'one year' + is then reset from that point. + * Disciplinary actions may be appealed to the council. + * A proxy must not be an existing council member, and any single person + may not be a proxy for more than one council member at any given + meeting. Rationale =========