From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: rich0@gentoo.org, pinkbyte@gentoo.org
Subject: Re: [gentoo-project] Council meeting 2015-01-13: call for agenda items
Date: Wed, 7 Jan 2015 10:30:52 -0600 [thread overview]
Message-ID: <20150107163052.GA7151@linux1> (raw)
In-Reply-To: <CAGfcS_=_yAs72Q1sKGfNs+BADE3UUQFHcteY_kG0c7_XaguOaw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]
On Wed, Jan 07, 2015 at 08:03:04AM -0500, Rich Freeman wrote:
> On Sat, Dec 27, 2014 at 7:34 AM, Andreas K. Huettel
> <dilfridge@gentoo.org> wrote:
> >
> > For proposing agenda items and discussion of these, please reply to this mail
> > on the gentoo-project mailing list.
> >
>
> I think that it is probably worth discussing what the right policy
> should be around allowing masked packages to remain in the tree (if
> they have a maintainer). This would include packages with documented
> security flaws in the mask message, but it could also include other
> kinds of flaws. If the maintainer wants to keep them around, should
> they be permitted to? Are there any conditions on this, or is it
> maintainer-preference as long as it stays masked?
>
> See:
> http://article.gmane.org/gmane.linux.gentoo.devel/94200
> http://article.gmane.org/gmane.linux.gentoo.devel/94199
(qa hat firmly in place)
I gave people several weeks to respond to the last rites and discuss
which packages should be kept. I will adjust my list based on their
responses.
That's the whole point of a last rites, to get people to step up and
take responsibility for packages. Also, this was cleared with the qa
lead before it was ever sent out.
So I am operating clearly within the scope of qa, since the job of QA is
to keep the tree in a consistent state for our users.
So with all respect, I don't understand why this even needs to be
escalated to the council.
Thanks,
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-01-07 16:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 12:34 [gentoo-project] Council meeting 2015-01-13: call for agenda items Andreas K. Huettel
2014-12-28 11:43 ` Anthony G. Basile
2014-12-28 11:57 ` Michał Górny
2014-12-28 16:45 ` Andreas K. Huettel
2014-12-28 16:54 ` Michał Górny
2014-12-29 0:02 ` Patrick Lauer
2014-12-29 20:57 ` Matthew Thode
2014-12-29 21:44 ` Andreas K. Huettel
2014-12-30 0:18 ` Alex Legler
2014-12-30 14:20 ` Anthony G. Basile
2014-12-30 15:05 ` Rich Freeman
2014-12-30 16:18 ` Anthony G. Basile
2014-12-30 4:59 ` Dean Stephens
2014-12-29 19:34 ` hasufell
2014-12-29 20:06 ` Rich Freeman
2014-12-29 21:02 ` Matthew Thode
2014-12-30 2:22 ` hasufell
2014-12-30 2:47 ` Rich Freeman
2014-12-30 5:00 ` Dean Stephens
2014-12-30 8:28 ` Ciaran McCreesh
2014-12-30 11:31 ` Rich Freeman
2014-12-30 14:25 ` hasufell
2014-12-30 15:12 ` Rich Freeman
2014-12-30 20:51 ` hasufell
2014-12-31 4:19 ` Dean Stephens
2015-01-04 23:27 ` hasufell
2015-01-05 4:38 ` Dean Stephens
2015-01-05 14:06 ` hasufell
2015-01-06 4:25 ` Dean Stephens
2015-01-07 13:03 ` Rich Freeman
2015-01-07 16:30 ` William Hubbs [this message]
2015-01-07 17:45 ` Rich Freeman
2015-01-07 19:35 ` William Hubbs
2015-01-07 21:21 ` Andrew Savchenko
2015-01-08 15:05 ` William Hubbs
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=20150107163052.GA7151@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=pinkbyte@gentoo.org \
--cc=rich0@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