Difference between revisions of "TSC"

From fd.io
Jump to: navigation, search
(→‎Meeting Minutes)
(→‎Agenda)
Line 43: Line 43:
  
 
* ''Start the recording''
 
* ''Start the recording''
−
* ''Roll Call, Agenda Bashing, Action items (all, 5 minutes)
+
* ''Roll Call, Agenda Bashing (all, 5 minutes)
 
** Call for any new topics for the agenda
 
** Call for any new topics for the agenda
−
** Action Items from Last Week
+
 
 +
* 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]
 +
 
 +
* Action Items from Last Week
 
*** CJ to register CPE with NIST: https://nvd.nist.gov/cpe.cfm
 
*** CJ to register CPE with NIST: https://nvd.nist.gov/cpe.cfm
−
*** cj to ask whoever has been saying no to general ticket access to provide a coherent explanation of why not and report back
 
−
*** ppfister put info on how to prepare for training on the wiki [[Events/Training_Hackfest-2016-05_Details|Done]]
 
 
*** David Jorm has volunteered to cut a first draft of the security response process in two weeks
 
*** David Jorm has volunteered to cut a first draft of the security response process in two weeks
 
*** 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
 
*** 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
−
*** Keith Burns to document convention on wiki and email the mailing list
+
 
 
* Events
 
* Events
 
** Planning for Training/Hackfest in EU
 
** Planning for Training/Hackfest in EU
Line 57: Line 71:
 
**** [[Events/Training_Hackfest-2016-05_Agenda| Tentative Agenda]]
 
**** [[Events/Training_Hackfest-2016-05_Agenda| Tentative Agenda]]
 
**** '''[https://app.smartsheet.com/b/form?EQBCT=503f45e9004043d2ada3334568ad04cf Register here]''' - Please register
 
**** '''[https://app.smartsheet.com/b/form?EQBCT=503f45e9004043d2ada3334568ad04cf Register here]''' - Please register
−
** fd.io/dpdk OpNFV Track (John DiGiglio)
+
** fd.io/dpdk OpNFV Track
 
** Call for any other fd.io events
 
** Call for any other fd.io events
−
* Approval of new VPP Committers:
 
−
** [https://fd.io/governance/technical-community-charter#3_2_2_1 Process for adding Committers]
 
−
** [https://lists.fd.io/pipermail/tsc/2016-May/000119.html vpp PTL request for TSC to approve 3 new vpp committers]
 
−
*** Chris Luke: https://lists.fd.io/pipermail/vpp-dev/2016-May/000882.html
 
−
*** Florin Coras: https://lists.fd.io/pipermail/vpp-dev/2016-May/000885.html
 
−
*** Keith Burns: https://lists.fd.io/pipermail/vpp-dev/2016-May/000888.html
 
−
* Creation Review: Transport Layer Development Kit creation review
 
−
** Project Proposal: https://wiki.fd.io/view/Project_Proposals/TLDK
 
−
** Announcement of Project Proposal: https://lists.fd.io/pipermail/tsc/2016-April/000107.html - 2016-04-28
 
−
** Request for creation review on May 12: https://lists.fd.io/pipermail/tsc/2016-April/000109.html
 
 
* Ubuntu packaging subproject
 
* Ubuntu packaging subproject
−
* Making infrastructure tickets visible to the community (C.J. Collier)
 
  
 
== Future Agenda Items ==
 
== Future Agenda Items ==

Revision as of 12:04, 19 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

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.

2016-05-19

Meeting Minutes

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=1421"