Difference between revisions of "TSC"

From fd.io
Jump to: navigation, search
(Meeting Minutes)
(Agenda)
Line 53: Line 53:
 
** Yet-to-be-done action items are restarted here
 
** Yet-to-be-done action items are restarted here
 
* Events
 
* Events
* Making infrastructure tickets visible to the community
+
* Making infrastructure tickets visible to the community (C.J. Collier)
* TSC Proxies
+
 
* Security Process for fd.io
 
* Security Process for fd.io
 +
** Report back from Ash Young on proposed Security Process.
 
** We have [mailto:security@lists.fd.io security@lists.fd.io ].
 
** We have [mailto:security@lists.fd.io security@lists.fd.io ].
 
** We probably need to form a security response team.
 
** We probably need to form a security response team.
Line 63: Line 63:
 
*** [https://wiki.openstack.org/wiki/Vulnerability_Management The OpenStack vulnerability management process]
 
*** [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]
 
*** [https://securityblog.redhat.com/2013/01/30/a-minimal-security-response-process/ Recommendations for a minimal security response process]
 +
* Draw attention to Project Proposals out for public comment
 +
** [https://lists.fd.io/pipermail/tsc/2016-March/000022.html CSIT]
 +
** [https://lists.fd.io/pipermail/tsc/2016-March/000029.html Honeycomb]
 +
** [https://lists.fd.io/pipermail/tsc/2016-March/000028.html NSH SFC]
 +
 +
== 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-03-17 ===
 +
 +
* CSIT Project Creation Review
 +
** [[Project_Proposals/CSIT|CSIT Project Proposal]]
 +
** [https://lists.fd.io/pipermail/tsc/2016-February/000020.html Notification of CSIT Project Proposal], sent 2016-02-26
 +
** [https://lists.fd.io/pipermail/tsc/2016-March/000022.html Request for CSIT Creation Review] to occur on 2016-03-17
 +
 +
=== 2016-03-24 ===
 +
 +
* Honeycomb Project Creation Review
 +
** [[Project_Proposals/Honeycomb|Honeycomb Project Proposal]]
 +
** [https://lists.fd.io/pipermail/tsc/2016-March/000026.html Notification of CSIT Project Proposal], sent 2016-03-04
 +
** [https://lists.fd.io/pipermail/tsc/2016-March/000029.html Request for CSIT Creation Review] to occur 2016-03-24
 +
* NSF SFC Project Creation Review
 +
** [[Project_Proposals/NSH_SFC|NSH SFC Project Proposal]]
 +
** [https://lists.fd.io/pipermail/tsc/2016-March/000028.html Notification of CSIT Project Proposal and Request for CSIT Project Creation Review on 2016-03-24] , sent 2016-03-04
  
 
== Meeting Minutes ==
 
== Meeting Minutes ==

Revision as of 14:08, 7 March 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: 203 059 649


Meeting password: default

Host key: 202817

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: 203 537 710

Numeric meeting password: 98137286

Global Call in Numbers

Toll Free Calling Restrictions

Agenda

The next TSC meeting is scheduled for Thursday February 25, 2016 with the following 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-03-17

2016-03-24

Meeting Minutes

2016-03-03

2016-02-25

2016-02-18