[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Scheduling a Board Discussion Telecon

No worries. Since there is not good overlap, I’ll issue a new poll for the meeting.





From: Kurt Seifried [mailto:kseifried@redhat.com]
Sent: Monday, March 21, 2016 9:03 PM
To: Waltermire, David A. (Fed) <david.waltermire@nist.gov>
Cc: cve-editorial-board-list@lists.mitre.org
Subject: Re: Scheduling a Board Discussion Telecon


I hate to do this my my schedule for next week just got flipped upside down (kid related issues, I can't wait till they're old enough to go away for spring break ;). My availability is now:


Monday: 15:30 EST until 20:00 EST

Tuesday: 10:00 EST until 14:30 EST

Wednesday: 10:00 EST until 14:30 EST

Thursday: 10:00 EST until 14:30 EST

Friday: 9:30 EST until 20:00 EST 


On Mon, Mar 21, 2016 at 3:40 PM, Waltermire, David A. (Fed) <david.waltermire@nist.gov> wrote:

We have been talking about having a discussion on the path forward around CVE for a while, but we haven't been able to get something scheduled. To get this conversation started, I would like to schedule an initial hour call. We would like to get as much board participation as possible. Please respond to the following Doodle poll to indicate your availability for next week and 4/4. It would be ideal to talk on 3/28 if you are available.


Please respond to this poll by CoB 3/24. I'll send out call details once we have a date/time selected.

As an initial agenda topic, I'd like to suggest that we give some time for Kurt Seifried to discuss his ideas around the Distributed Weakness Filing (DWF) System. I believe he has a number of good ideas that we may want to adopt for CVE. It would be good to discuss them as a group.

If you have other suggestions for the agenda, please respond with your ideas.


David Waltermire
Information Technology Laboratory | Computer Security Division
National Institute of Standards and Technology




Kurt Seifried -- Red Hat -- Product Security -- Cloud
PGP A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993
Red Hat Product Security contact: 

Page Last Updated or Reviewed: March 22, 2016