From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2014-02-25
Date: Thu, 20 Feb 2014 21:47:46 -0600 [thread overview]
Message-ID: <20140221034746.GF8819@comet.hsd1.mn.comcast.net> (raw)
In-Reply-To: <53069A66.2090907@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
On 01:14 Fri 21 Feb , Chí-Thanh Christopher Nguyễn wrote:
> Andreas K. Huettel schrieb:
>
> > Please respond to this message with agenda items. Do not hesitate to
> > repeat your agenda item here with a pointer if you previously suggested
> > one (since the last meeting).
> >
> > We will send out the agenda one week before the meeting date, i.e.
> > 2014-02-18.
>
> If that is still possible, I would like to add one more item related to the
> gtk/gtk2/gtk3 USE flags to the agenda. Namely, whether Council gives QA the
> powers to enact such a rule.
>
> In my opinion, it is not necessary for QA to have such powers (and
> therefore better if they don't have it). QA can already act per GLEP 48 if
> there is an immediate serious problem for users. And when there is not an
> immediate serious problem, any such rule can be proposed by QA to council
> for decision, especially if the topic is as controversial as the gtk USE
> flag issue.
Funny how every time a controversial decision gets made, somebody
inevitably tries to undermine the authority of the group making the
decision.
In my understanding, the issue you want to address is whether the QA
team has authority over tree policy.
Will add to the agenda.
I happen to disagree. GLEP 48's point about maintaining "QA Standards"
applies to this.
--
Thanks,
Donnie
Donnie Berkholz
Council Member / Sr. Developer, Gentoo Linux <http://dberkholz.com>
Analyst, RedMonk <http://redmonk.com/dberkholz/>
[-- Attachment #2: Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2014-02-21 3:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 14:45 [gentoo-project] Call for agenda items - Council meeting 2014-02-25 Andreas K. Huettel
2014-02-10 15:39 ` Ulrich Mueller
2014-02-10 16:00 ` Andreas K. Huettel
2014-02-10 16:22 ` Ruud Koolen
2014-02-10 18:03 ` Tom Wijsman
2014-02-10 18:49 ` Ciaran McCreesh
2014-02-10 18:51 ` Ulrich Mueller
2014-02-10 19:07 ` hasufell
2014-02-11 2:39 ` Rick "Zero_Chaos" Farina
2014-02-11 23:20 ` hasufell
2014-02-20 9:33 ` Ulrich Mueller
2014-02-20 15:46 ` hasufell
2014-02-11 19:46 ` Andreas K. Huettel
2014-02-13 4:35 ` William Hubbs
2014-02-13 11:41 ` Andreas K. Huettel
2014-02-21 3:28 ` Donnie Berkholz
2014-02-21 0:14 ` Chí-Thanh Christopher Nguyễn
2014-02-21 3:47 ` Donnie Berkholz [this message]
2014-02-21 4:03 ` Rich Freeman
2014-02-21 4:04 ` Donnie Berkholz
2014-02-21 13:32 ` Anthony G. Basile
2014-02-21 8:38 ` Michał Górny
2014-02-21 10:34 ` Tom Wijsman
2014-02-24 16:46 ` Chí-Thanh Christopher Nguyễn
2014-02-24 18:59 ` Tom Wijsman
2014-02-24 21:43 ` Chí-Thanh Christopher Nguyễn
2014-02-24 23:55 ` Tom Wijsman
2014-02-25 0:12 ` Rich Freeman
2014-02-24 23:13 ` Patrick Lauer
2014-02-24 23:54 ` Patrick Lauer
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=20140221034746.GF8819@comet.hsd1.mn.comcast.net \
--to=dberkholz@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