public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: About changing security policy to unCC maintainers when their are not needed
Date: Wed, 12 Sep 2012 20:54:07 +0200	[thread overview]
Message-ID: <1347476047.2365.15.camel@belkin4> (raw)
In-Reply-To: <5050D4AF.1010205@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]

El jue, 13-09-2012 a las 04:30 +1000, Michael Palimaka escribió:
> On 2012-09-13 03:59, Pacho Ramos wrote:
> > Hello
> >
> > Currently, package maintainers are CCed to security bugs when their are
> > needed. The problem is that, once maintainers add a fixed version and
> > tell security team they are ok to get it stabilized, maintainers are
> > kept CCed until bug is closed by security team. This usually means
> > getting a lot of mail after some time when security team discuss if a
> > GLSA should be filled or not, if security bot adds some comment... some
> > of that comments are applied to really old bugs that need no action from
> > maintainers.
> >
> > Maybe would be interesting to change the policy to unCC maintainers
> > again when their action is no longer required.
> >
> > What do you think?
> >
> > Thanks for your thoughts
> >
> 
> Hello,
> 
> Is the policy you describe officially documented, or just current behaviour?
> 

I don't know, at least it's the current behavior, but I don't know if
it's a policy :/

> In KDE and Qt herds for example, we usually just unCC ourselves when 
> we've taken the required action.
> 
> Best regards,
> Michael
> 
> 
> 



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-09-12 18:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 17:59 [gentoo-dev] About changing security policy to unCC maintainers when their are not needed Pacho Ramos
2012-09-12 18:29 ` Jeroen Roovers
2012-09-12 18:42   ` Rich Freeman
2012-09-12 18:55     ` Pacho Ramos
2012-09-12 18:53   ` Pacho Ramos
2012-09-13  1:43     ` Jeroen Roovers
2012-09-13  3:29       ` Ben de Groot
2012-09-13  7:32       ` Pacho Ramos
2012-09-12 18:30 ` [gentoo-dev] " Michael Palimaka
2012-09-12 18:54   ` Pacho Ramos [this message]
2012-09-12 22:30     ` Sean Amoss
2012-09-13  7:29       ` Pacho Ramos
2012-09-14 11:15         ` Alex Legler
2012-09-14 11:33           ` Rich Freeman
2012-09-13  7:30       ` Pacho Ramos
2012-09-13 13:48 ` [gentoo-dev] " Alex Legler
2012-09-13 19:57   ` Pacho Ramos
2012-09-13 20:11     ` Rich Freeman
2012-09-14  9:34       ` Alex Legler

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=1347476047.2365.15.camel@belkin4 \
    --to=pacho@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