Difference between revisions of "TSC"

From fd.io
Jump to: navigation, search
(Meeting Minutes)
(Agenda)
Line 49: Line 49:
 
** edwarnicke to put out the call for security response team volunteers [https://lists.fd.io/pipermail/vpp-dev/2016-May/001214.html Done]
 
** edwarnicke to put out the call for security response team volunteers [https://lists.fd.io/pipermail/vpp-dev/2016-May/001214.html Done]
 
** joelhalpern to take responsibility for getting the security response document to finalization and incorporate feedback from security response team members
 
** 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
 
* Good things that happened this week
  
* Events
+
* Events - Introducing the fd.io marketing committee
 
** Planning for Training/Hackfest in EU
 
** Planning for Training/Hackfest in EU
 
*** [[Events#May_FD.io_.2Fdev.2Fboot_Training_.26_Hackfest_.7C_Paris.2C_Francefd.io|Training/Hackfest in Paris May 31-Jun 3]]
 
*** [[Events#May_FD.io_.2Fdev.2Fboot_Training_.26_Hackfest_.7C_Paris.2C_Francefd.io|Training/Hackfest in Paris May 31-Jun 3]]
Line 61: Line 60:
 
** 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]
+
* [https://wiki.fd.io/view/TSC:Vulnerability_Management Security Response Process]
 
+
** [https://lists.fd.io/pipermail/tsc/2016-May/thread.html Call for volunteers for security response team]
* Project Proposals (not for creation review this week, but after 2 week public comment period):
+
*** [https://lists.fd.io/pipermail/tsc/2016-May/000127.html Jim Thompson]
** [https://lists.fd.io/pipermail/tsc/2016-May/000129.html pkg-dpdk] - Packaging dpdk for Ubuntu/Debian
+
*** [https://lists.fd.io/pipermail/tsc/2016-May/000140.html Dave Wallace]
 +
*** [https://lists.fd.io/pipermail/tsc/2016-May/000141.html Mathieu Lemay]
 +
* Proposal to proceed:
 +
** Last call for security response process, TSC vote next week (can be evolve thereafter, but needs to get going)
 +
** Last call for security response volunteers, TSC vote next week (membership can evolve over time there after)
  
 
== Future Agenda Items ==
 
== Future Agenda Items ==

Revision as of 13:00, 2 June 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
  • Good things that happened this week

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-26

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