From: Ryan Hill <dirtyepic.sk@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Monthly Gentoo Council Reminder for September
Date: Sun, 03 Sep 2006 00:11:23 -0600 [thread overview]
Message-ID: <eddrm5$kt3$1@sea.gmane.org> (raw)
In-Reply-To: <44FA1D6E.5040703@gentoo.org>
Alec Warner wrote:
> needs as far as QA. Last year Halcy0n petitioned for power for the QA
> team; it was quite like a ball crushing power (fix it or we will) and it
> seemed to have all kinds of frictional issues. This being a global
> issue I would like to hear thoughts on how this could be done better; or
> we can abandon the idea of a QA team.
I don't recall that it was that heavy handed at all. It said that the
QA team would work with maintainers to improve the quality of the tree,
and only in *emergency* situations would be empowered to take necessary
measures to address the issue. The major point of contention seemed to
concern the situation where QA and maintainers strongly disagreed on
whether or not a QA problem actually exists and were unable to come to a
resolution between themselves. In that case, the issue would be
appealed to the council for judgement. Now it also stated that the QA
team had veto power over the maintainer until the council can come to a
decision. I personally don't agree with this at all, except in the case
of security related issues. Even so, I think this falls more under the
umbrella of the security team rather than QA.
I do believe the QA team should have the ability to make trivial changes
to ebuilds (such as obvious typos and other minor issues), but all
effort should probably be made to first discuss these issues with the
maintainers themselves. Veto power *needs* to be the absolute last
resource, and should very rarely, if ever, be necessary.
--de.
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2006-09-03 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 5:51 [gentoo-dev] Monthly Gentoo Council Reminder for September Mike Frysinger
2006-09-01 13:53 ` Chris Gianelloni
2006-09-01 14:45 ` Paul de Vrieze
2006-09-01 14:57 ` Wernfried Haas
2006-09-02 0:08 ` Robin H. Johnson
2006-09-01 20:11 ` Daniel Ostrow
2006-09-03 0:10 ` Alec Warner
2006-09-03 6:11 ` Ryan Hill [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='eddrm5$kt3$1@sea.gmane.org' \
--to=dirtyepic.sk@gmail.com \
--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