From: Tom Wijsman <TomWij@gentoo.org>
To: calchan@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: formally allow qa to suspend commit rights
Date: Mon, 20 Jan 2014 03:47:35 +0100 [thread overview]
Message-ID: <20140120034735.52e87b9e@TOMWIJ-GENTOO> (raw)
In-Reply-To: <CA+CSuALpkmxifRWN8cRxPwbU5w_1SjmFJBgJg3egyDzwNX-gPw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3405 bytes --]
On Sun, 19 Jan 2014 18:22:39 -0700
Denis Dupeyron <calchan@gentoo.org> wrote:
> On Sun, Jan 19, 2014 at 6:01 PM, Tom Wijsman <TomWij@gentoo.org>
> wrote:
> > It is more of a "Do we want QA to delegate this through ComRel or
> > not?".
>
> Actually, no. What it is is a "Subject was thoroughly discussed in the
> past, and a decision was made." More than once, in fact. What basis do
> you have that would warrant more bilkeshedding on this subject?
The basis that it has once been accepted as well as another time invited
more discussion, clearly indicates that it needs further bikeshedding:
http://www.gentoo.org/proj/en/council/meeting-logs/20110308-summary.txt
* GLEP 48 (QA)
After a long discussion and a review of the final proposal text, the
result is the following:
- vote:
in favor: scarabeus, ferringb, wired, jmbsvicetto
didn't state (abstain): betelgeuse, patrick, a3li
-> Given the result, the GLEP update is accepted and can proceed,
albeit Peteri raised a question how Devrel is going to work out the
resolution after the process is handled over from QA. It was agreed
that the part of the text (last sentence of the diff) will be
updated with string based on what those two teams agree with
without more council involvment (unless required otherwise)..
http://www.gentoo.org/proj/en/council/meeting-logs/20110608-summary.txt
* GLEP48 review
Jorge submitted a proposal to the ml to update GLEP48[4].
After some initial debate over the power granted to the QA team,
the timeline in case of an escalation to DevRel, the relation with
DevRel and whether QA should only enforce policies or also take
part in creating policies, after the request by Patrick, Jorge
-> suggested pushing this back to the mls. Petteri then asked the
council to at least vote to commit the non suspension related parts
of the proposal. The diff[5] was approved with 6 yes votes. Alec
during this discussion presented some thoughts about the QA team[6].
[4] -
http://archives.gentoo.org/gentoo-project/msg_ac161677a6e06a8647e16420eeae8d47.xml
[5] -
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/proj/en/glep/glep-0048.txt?r1=1.3&r2=1.4
[6] - http://pastebin.com/C1jGF1DJ
> It may sound crazy, but it isn't entirely impossible that decisions
> made in the past were not made lightly.
This assumes that the decisions have voted against the matter; however,
they voted for this matter on the basis of a small change to be made to
it (20110308-summary.txt) but that never happened and seems forgotten.
Some developers even refer to Diego having used this power in the past.
> It's also not entirely impossible that one of the reasons such
> decisions are made is so that people can stop rehashing the same
> topics over and over again and focus on more useful and fun topics.
This assumes the topic to be useless or boring; however, that's personal
opinion and there is an useful need for this from the QA, Council and
ComRel perspective. Sometimes we need to deal with a more serious topic.
This is one of those days.
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-01-20 2:48 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 5:02 [gentoo-dev] rfc: formally allow qa to suspend commit rights William Hubbs
2014-01-19 5:07 ` William Hubbs
2014-01-19 5:17 ` [gentoo-dev] " W. Trevor King
2014-01-19 12:46 ` [gentoo-dev] " hasufell
2014-01-20 1:05 ` Tom Wijsman
2014-01-19 20:22 ` Denis Dupeyron
2014-01-20 1:01 ` Tom Wijsman
2014-01-20 1:22 ` Denis Dupeyron
2014-01-20 2:47 ` Tom Wijsman [this message]
2014-01-22 16:30 ` Jeroen Roovers
2014-01-20 1:24 ` Alec Warner
2014-01-20 2:54 ` Tom Wijsman
2014-01-20 13:59 ` Rich Freeman
2014-01-20 14:09 ` Alan McKinnon
2014-01-21 0:22 ` Patrick Lauer
2014-01-21 0:46 ` Rich Freeman
2014-01-21 5:29 ` Alec Warner
2014-01-21 5:27 ` Alec Warner
2014-01-22 17:54 ` Ciaran McCreesh
2014-01-22 22:37 ` Andreas K. Huettel
2014-01-22 22:59 ` Tom Wijsman
2014-01-21 14:56 ` Tom Wijsman
2014-01-21 15:47 ` Rich Freeman
2014-01-21 17:26 ` William Hubbs
2014-01-21 17:50 ` Rich Freeman
2014-01-21 17:56 ` Peter Stuge
2014-01-21 18:11 ` Tom Wijsman
2014-01-21 18:16 ` Peter Stuge
2014-01-21 19:18 ` Tom Wijsman
2014-01-21 21:03 ` Thomas Sachau
2014-01-21 22:56 ` Tom Wijsman
2014-01-21 23:14 ` William Hubbs
2014-01-22 7:00 ` Alan McKinnon
2014-01-22 10:36 ` hasufell
2014-01-22 10:39 ` hasufell
2014-01-22 10:58 ` Alec Warner
2014-01-22 23:29 ` Tom Wijsman
2014-01-22 12:34 ` Patrick Lauer
2014-01-22 19:42 ` Rich Freeman
2014-01-22 23:40 ` Tom Wijsman
2014-01-22 22:06 ` Alan McKinnon
2014-01-22 23:15 ` Tom Wijsman
2014-01-21 23:20 ` hasufell
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=20140120034735.52e87b9e@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=calchan@gentoo.org \
--cc=gentoo-dev@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