[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170714182358.GA20536@openwall.com>
Date: Fri, 14 Jul 2017 20:23:58 +0200
From: Solar Designer <solar@...nwall.com>
To: oss-security@...ts.openwall.com
Subject: Re: accepting new members to (linux-)distros lists
On Fri, Jul 14, 2017 at 11:09:39AM -0700, Anthony Liguori wrote:
> We (Amazon Linux) are very happy to fill in whatever gaps are needed.
>
> Most of the places where that can be done most effectively already
> have a primary. I hate to just sign up to be backup but if we did
> that, we would track independently to ensure nothing got missed.
>
> So maybe backup for administrative tasks 9-13 and then we can be
> primary for technical task 3? We already test all of these fixes so
> responding with a report of the testing we've done is straight forward
> enough.
This works. I've just listed Amazon for those tasks as you suggested.
Thank you!
This leaves administrative task 10 with no primary yet, though:
10. Monitor relevant public channels (mailing lists, code repositories,
etc.) and inform the reporter and the list in case an issue is made
public prematurely (that is, leaks or is independently rediscovered) -
primary: vacant, backup: Amazon
Does this mean Amazon will be taking care of it until we find a primary?
Or only in cases when no other distro (visibly) does?
Ideally, a distro should volunteer to be primary for that task now, so
that Amazon wouldn't have to volunteer for more than they offered.
> > http://oss-security.openwall.org/wiki/mailing-lists/distros#contributing-back
Alexander
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
