public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: NP-Hardass <NP-Hardass@gentoo.org>
To: gentoo-project@lists.gentoo.org, "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-project] [RFC PATCH] glep-0039: Add a section describing who Gentoo developers are
Date: Thu, 26 Apr 2018 11:12:46 -0400	[thread overview]
Message-ID: <db991774-1e63-90f5-e673-ff25d541db06@gentoo.org> (raw)
In-Reply-To: <20180424145158.7695-1-mgorny@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 4841 bytes --]

On 04/24/2018 10:51 AM, Michał Górny wrote:
> Hi,
> 
> Here's a followup of my pre-GLEP.  After the content being reduced even
> more by the bikeshed, and suggestions that this would fit better inside
> GLEP 39, here's a minimal patch to GLEP 39 that prepends the two main
> points of the specification with short definition of developers.
> 
> ---
> 
> Amend GLEP 39 by adding missing definition of Gentoo developer, along
> with a short explanation on how new developers are being admitted
> and how existing developers are removed.  This GLEP has been writting
> with strong focus on what developers can do; however, no GLEP has really
> defined whom developers really are.
> 
> The aim of this change is merely to describe the status quo, without
> introducing any changes to the structure or procedures.  The wording has
> been reduced to absolute minimum necessary to outline the processes
> without getting into any details that could be considered controversial.
> ---
>  glep-0039.rst | 40 ++++++++++++++++++++++++++++++++++------
>  1 file changed, 34 insertions(+), 6 deletions(-)
> 
> diff --git a/glep-0039.rst b/glep-0039.rst
> index c458450..f68247e 100644
> --- a/glep-0039.rst
> +++ b/glep-0039.rst
> @@ -5,10 +5,10 @@ Author: Grant Goodyear <g2boojum@gentoo.org>,
>          Ciaran McCreesh <ciaranm@gentoo.org>
>  Type: Informational
>  Status: Final
> -Version: 2
> +Version: 2.1
>  Created: 2005-09-01
> -Last-Modified: 2016-07-30
> -Post-History: 2005-09-01, 2006-02-09, 2007-10-12, 2008-01-19
> +Last-Modified: 2018-04-24
> +Post-History: 2005-09-01, 2006-02-09, 2007-10-12, 2008-01-19, 2018-04-24
>  Content-Type: text/x-rst
>  Replaces: 4
>  ---
> @@ -17,7 +17,10 @@ Status
>  ======
>  
>  Implemented. GLEP amended on 2006-02-09 to add the final bullet point to
> -list B in `Specification`_.
> +list C in `Specification`_.
> +
> +GLEP amended on 2018-04-24 to prepend new point A to the specification
> +describing who developers are.
>  
>  Abstract
>  ========
> @@ -106,7 +109,28 @@ 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
> +A. A developer is a person who has successfully passed recruitment
> +   procedure as defined of the time of the recruit's joining and is
> +   actively contributing to Gentoo Linux.
> +
> +   *  New developers are admitted by the Recruiters project
> +      [#RECRUITERS]_ upon asserting that the candidate(s) have
> +      the necessary skills, motivation and have recent contributions
> +      in the areas of their interest.
> +   *  Developers are removed by the Undertakers project [#UNDERTAKERS]_.
> +      The developer status can be revoked in one of the following cases:
> +
> +      - The developer's own explicit request.
> +      - Determining that the developer is no longer actively
> +        contributing to Gentoo.
> +      - A result of disciplinary action taken by an appropriately
> +        authorized project.
> +
> +   *  The policies for admittance and removal of developers shall
> +      be defined and published by the Recruiters and Undertakers
> +      projects appropriately.
> +
> +B. 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
> @@ -130,7 +154,7 @@ A. A project is a group of developers working towards a goal (or a set
>        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.
> +C. 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.)
> @@ -209,6 +233,10 @@ References
>  
>  .. [#Project_pages] https://wiki.gentoo.org/wiki/Gentoo_Wiki:Developer_Central/Project_pages
>  
> +.. [#RECRUITERS] https://wiki.gentoo.org/wiki/Project:Recruiters
> +
> +.. [#UNDERTAKERS] https://wiki.gentoo.org/wiki/Project:Undertakers
> +
>  Copyright
>  =========
>  
> 

I understand your intent to be a trivial clarification update to GLEP
39, but by enshrining two projects in GLEP 39 (effectively as permanent
institutions in Gentoo Metastructure) without anything but an RFC, I
think you are making an extremely nontrivial update to the GLEP.  I
strongly oppose this change from both the non-triviality of the change
and the substance of the change (which I can go into if we really need
to get into it, but I think the non-triviality argument is strong enough
on its own).

-- 
NP-Hardass


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2018-04-26 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 14:51 [gentoo-project] [RFC PATCH] glep-0039: Add a section describing who Gentoo developers are Michał Górny
2018-04-24 16:50 ` Matthew Thode
2018-04-24 16:58   ` Michał Górny
2018-04-26 15:12 ` NP-Hardass [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=db991774-1e63-90f5-e673-ff25d541db06@gentoo.org \
    --to=np-hardass@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=mgorny@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox