Difference between revisions of "TSC"

From fd.io
Jump to: navigation, search
(→‎Meeting Minutes)
(→‎Agenda)
Line 47: Line 47:
  
 
* Action Items from Last Week
 
* Action Items from Last Week
−
*** CJ to register CPE with NIST: https://nvd.nist.gov/cpe.cfm
+
** edwarnicke to put out the call for security response team volunteers [https://lists.fd.io/pipermail/vpp-dev/2016-May/001214.html Done]
−
*** David Jorm has volunteered to cut a first draft of the security response process in two weeks [https://wiki.fd.io/view/TSC:Vulnerability_Management Done]
+
** joelhalpern to take responsibility for getting the security response document to finalization and incorporate feedback from security response team members
−
*** David Jorm has volunteered to send email to https://lists.fd.io/mailman/listinfo/discuss https://lists.fd.io/mailman/listinfo/tsc https://lists.fd.io/mailman/listinfo/vpp-dev to start the conversation about forming a security response team [https://lists.fd.io/pipermail/tsc/2016-May/000121.html Done]
+
** jtollet To send out email to discuss, tsc, and the project mailers asking for talks from the other projects for the training and hackfest
  
 
* Good things that happened this week
 
* Good things that happened this week
−
** VPP project successfully cut its stable/1606 throttle branch.
 
−
 
−
* Security Process for fd.io (David Jorm)
 
−
** Announcement of Initial Draft of Security Response Process: https://lists.fd.io/pipermail/tsc/2016-May/000121.html
 
−
** Initial Draft of Security Response Process: https://wiki.fd.io/view/TSC:Vulnerability_Management
 
−
** Next Steps:
 
−
*** Call for volunteers for the security response team, sample text here: https://lists.fd.io/pipermail/tsc/2016-May/000121.html
 
−
*** Security response team forms and recommends approval of security response process to TSC
 
−
*** TSC approves security response process
 
−
*** Implementation
 
−
*** Question: Would it make sense to also consult PTLs directly as to their opinions of security response process?
 
−
** Reference processes:
 
−
*** [https://wiki.opendaylight.org/view/Security:Main OpenDaylight Security Process]
 
−
*** [https://www.kernel.org/doc/Documentation/SecurityBugs The Linux Kernel process for reporting security issues]
 
−
*** [https://wiki.openstack.org/wiki/Vulnerability_Management The OpenStack vulnerability management process]
 
−
*** [https://securityblog.redhat.com/2013/01/30/a-minimal-security-response-process/ Recommendations for a minimal security response process]
 
  
 
* Events
 
* Events
Line 76: Line 60:
 
** fd.io/dpdk OpNFV Track
 
** fd.io/dpdk OpNFV Track
 
** Call for any other fd.io events
 
** Call for any other fd.io events
 +
 +
* [https://lists.fd.io/pipermail/tsc/2016-May/000137.html Approve Jan Gelety as CSIT Committer]
 +
 +
* Project Proposals (not for creation review this week, but after 2 week public comment period):
 +
** [https://lists.fd.io/pipermail/tsc/2016-May/000129.html pkg-dpdk] - Packaging dpdk for Ubuntu/Debian
  
 
== Future Agenda Items ==
 
== Future Agenda Items ==

Revision as of 13:42, 26 May 2016

TSC Facts

TSC Members:

  • Dave Barach
  • Joel Halpern
  • Venky Venkatesan
  • Ed Warnicke

Welcome to the fd.io Technical Steering Committee (TSC) Wiki. This page hosts all information associated with the fd.io TSC, including meeting schedules,, Agendas, and Minutes. To contact the TSC, send an email to the TSC mail list.

Meeting Schedule and Logistics

TSC meetings are held weekly for one hour on Thursday mornings from 8-9am Pacific Daylight Time (-7:00 GMT). Meetings are held using Webex for screen sharing and audio and IRC for recording meeting minutes.

Weekly on Thursdays from 8-9am PST. Webex Link 

Meeting number:	201 476 977
Meeting password:	default
 
Join by phone
+1-408-525-6800 Call-in toll number (US/Canada)
+1-866-432-9903 Call-in toll-free number (US/Canada)
Access code: 201 476 977
Numeric meeting password: 46858148

Global Call in Numbers

Toll Free Calling Restrictions

Agenda

The next TSC meeting is scheduled for Thursday May 5, 2016 with the following agenda:

  • Start the recording
  • Roll Call, Agenda Bashing (all, 5 minutes)
    • Call for any new topics for the agenda
  • Action Items from Last Week
    • edwarnicke to put out the call for security response team volunteers Done
    • joelhalpern to take responsibility for getting the security response document to finalization and incorporate feedback from security response team members
    • jtollet To send out email to discuss, tsc, and the project mailers asking for talks from the other projects for the training and hackfest
  • Good things that happened this week
  • Project Proposals (not for creation review this week, but after 2 week public comment period):
    • pkg-dpdk - Packaging dpdk for Ubuntu/Debian

Future Agenda Items

The TSC often has forward visibility into agenda items (like creation reviews) prior to the date on which it will act on them. In order to provide visibility, a list of future agenda items (with dates) will be kept here.

Meeting Minutes

2016-05-19

2016-05-12

2016-05-05

2016-04-28

2016-04-24

2016-04-14

2016-03-31

2016-03-24

2016-03-17

2016-03-10

2016-03-03

2016-02-25

2016-02-18

Retrieved from "https://wiki.fd.io/index.php?title=TSC&oldid=1512"