From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [RFC PATCH] glep-0039: Add a section describing who Gentoo developers are
Date: Tue, 24 Apr 2018 18:58:24 +0200 [thread overview]
Message-ID: <1524589104.1704.0.camel@gentoo.org> (raw)
In-Reply-To: <20180424165032.aqogcpcicli3ls5d@gentoo.org>
W dniu wto, 24.04.2018 o godzinie 11∶50 -0500, użytkownik Matthew Thode
napisał:
> On 18-04-24 16:51:58, 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.
>
> Appropriately needs to be defined.
Ah, I meant 'respectively' here. Will fix that.
>
> > +
> > +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
> > =========
> >
> > --
> > 2.17.0
> >
> >
>
> Nothting past that definition I think. Thanks for cleaning this up.
>
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2018-04-24 16:58 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 [this message]
2018-04-26 15:12 ` NP-Hardass
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=1524589104.1704.0.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-project@lists.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