public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Doug Freed <dwfreed@mtu.edu>
To: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] Clarify language of GLEP 39
Date: Sat, 14 Jan 2017 21:17:57 -0500	[thread overview]
Message-ID: <CAFyXEp+hudCHRYZUYtmd29thm2XRQ-X0yi92dsyqW7n6rPyujA@mail.gmail.com> (raw)

GLEP 39 currently states that "[A project] may have one or many leads"
(Specification section, first list, last item).  I believe (and a few
others agree) that this language is ambiguous,  Some projects have
interpreted this language to mean that a project may have no lead,
while others believe the language is to be interpreted as meaning that
projects must have at least one lead.  Therefore, I request that the
Council clarify the language of GLEP 39 to remove this ambiguity.  I
offer up the following choices as possible replacements (though feel
free to come up with your own):

"It must have at least one lead, and may have many leads.  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."

OR (if the Council wishes to allow no lead as an option)

"It may have no lead, one lead, 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."

(The slight change in wording in otherwise unaffected parts is to
avoid repetitive use of "and" in one sentence.)  The reason for the
ambiguity in the first place is that the English language allows you
to apply the "may" to the collective "one or many leads," which would
make any lead optional.  Others consider it to just be a choice
between "one lead" and "many leads," which is also a valid
interpretation.

I believe that the original intention was that every project would
have a lead (indeed, in GLEP 4, which GLEP 39 replaced, every project
had a manager, which is the equivalent), but I don't speak for the
authors of GLEP 39.  It is my personal opinion that every project
should have a lead.  The lead serves to resolve disputes among project
members, coordinate project effort, and be the point of contact
between the project and the rest of Gentoo, all on an as-needed basis.

-Doug
dwfreed


             reply	other threads:[~2017-01-15  2:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15  2:17 Doug Freed [this message]
2017-01-15  3:28 ` [gentoo-project] Clarify language of GLEP 39 Rich Freeman
2017-01-15  3:40 ` Gokturk Yuksek
2017-01-15  3:53   ` Doug Freed
2017-01-15  9:10     ` Ulrich Mueller
2017-01-15 12:28       ` Rich Freeman
2017-01-15 12:58         ` Aaron Bauman
2017-01-15 13:00           ` Ciaran McCreesh
2017-01-15 13:13             ` Aaron Bauman
2017-01-15 13:19               ` Ciaran McCreesh
2017-01-15 13:21                 ` Aaron Bauman
2017-01-15 14:18                 ` Ulrich Mueller
2017-01-15 13:15           ` Rich Freeman
2017-01-15 13:18             ` Aaron Bauman
2017-01-15 14:27               ` Rich Freeman
2017-01-15 14:32                 ` Ulrich Mueller
2017-01-15  4:58 ` Seemant Kulleen
2017-01-15  9:29   ` Michał Górny

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=CAFyXEp+hudCHRYZUYtmd29thm2XRQ-X0yi92dsyqW7n6rPyujA@mail.gmail.com \
    --to=dwfreed@mtu.edu \
    --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