15:00:52 #startmeeting OPNFV TSC 15:00:52 Meeting started Tue Mar 8 15:00:52 2016 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:52 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:52 The meeting name has been set to 'opnfv_tsc' 15:00:56 #topic Rioll Call 15:00:57 Uli-k, rprakash: I don't think we have a startmeeting yet 15:00:59 #undo 15:00:59 Removing item from minutes: 15:01:04 #topic Roll Call 15:01:05 #info Dave Neary 15:01:12 Uli-k, rprakash: Now we do 15:01:14 #info Uli 15:01:16 #info Chris Price 15:01:18 #info Jonas Arndt 15:01:21 #info Mark Beierl (proxy for Edgar StPierre) 15:01:22 #info rprakash 15:01:56 dneary, are you proxy for cdub? 15:02:03 #info Dirk Kutscher 15:02:08 rpaik, I believe so 15:02:16 rpaik, Let me double check 15:02:44 #topic Approval of the previous minutes of meeting 15:02:46 #info Morgan Richomme 15:02:54 #link https://wiki.opnfv.org/wiki/tsc#march_1_2016 previous minutes 15:02:56 #info Bryan Sullivan 15:03:08 #info Previous minutes are approved, no feedback or comments receieved 15:03:09 #info Brian Skerry 15:03:17 we now have quorum 15:03:28 #topic Agenda Bashing 15:03:44 #info Tapio Tallgren 15:04:15 #link https://wiki.opnfv.org/wiki/tsc#march_8_2016 current agenda 15:06:32 #info ebrjohn Brady Johnson, SFC PTL (IRC only today) 15:06:55 #info Frank Brockners 15:08:54 #info ashyoung would like to raise the topic of a name change for onosfw 15:09:54 Frank is on IRC only 15:10:08 Frank did start a new project - but the scope was different 15:10:20 IMHO we can change names 15:10:47 I can listen but cannot talk 15:10:53 #info Julien 15:11:22 How about we create a second repo etc. 15:11:30 and then you can move stuff to the new "name" 15:11:40 and abandon the old name once fully done 15:11:58 We are 12 mins into this call on a simple name change 15:12:10 No wonder our releases slip 15:12:27 #info To be added to the agenda the name change for onosfw 15:12:45 #topic TSC Meetings in Summer time transitions 15:13:38 #info the TSC meeting will be scheduled at 07:00 PST. This will result in some changes for other time zones as summer-time changes occur. 15:14:57 Is that an option to switch to UTC? 15:15:15 It's the same regardless summer/winter time 15:15:29 * bryan_att thinks that is more reason to can the whole timezone "standard" 15:15:49 ***JonasArndt agrees 15:15:53 #topic Board Agenda and TSC update 15:16:09 ildiko, intention was to keep fixed meeting times in most countries, not have different time in summer and winter 15:16:30 GeraldK: but it causes collisions this way 15:16:38 #ilnk http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-March/008633.html link to e-mail describing the board agenda for this week 15:17:10 GeraldK: UTC is easier to plan IMHO 15:17:13 ildikov: otherwise it will cause collisions in my agenda within the company 15:17:42 #agree with ildikov 15:19:01 GeraldK: I understand, but synchronizing an open source community around the globe is tough without corporate agenda already 15:19:43 GeraldK: we have this in OpenStack, so I know the internal collision part, but as the UTC time slot is fixed, that can be figured out in most cases 15:19:44 #info ChrisPriceAB notes that he will present the TSC policy update, Brahmaputra update, and C-release planning during the OPNFV Board meeting on March 10th 15:19:47 rpaik, Confirmed, I'm Red Hat proxy today 15:19:55 thanks dneary 15:20:15 #info Gerald Kunzmann (proxy for Ashiq Khan) 15:20:23 #topic Brahmaputra.2.0 planning and activities 15:20:47 #link https://etherpad.opnfv.org/p/steps_to_brahmaputra etherpad used for brahmaputra.2.0 planning 15:21:42 #info currently no plan for brahmaputra.3.0 15:22:58 #info Ashlee mentions that there might be some issue that may require brahamputra.3.0, but still investigating the issue 15:23:41 #info the daily release meeting are held at 06:30 PST on the opnfv-release channel 15:24:44 #info uli states that the meeting shave not been well published, improvements can be made in communication 15:25:04 #action chrispriceab to send an update mail to the community around the brahmaputra.2.0 meetings 15:25:21 #topic Release C Planning 15:27:04 #link https://wiki.opnfv.org/releases/releaseplanning proposals and sketch of C release milestones 15:30:09 #info ashyoung states that opening the project, having projects sign up and begin recording our state for the C release needs to be done quickly 15:30:19 #undo 15:30:19 Removing item from minutes: 15:30:25 #info ashyoung states that opening the release work, having projects sign up and begin recording our state for the C release needs to be done quickly 15:35:13 #info ashyoung raises project onboarding as a key item to address 15:35:25 #action ashyoung to send a mail to the lists to kick start the work 15:41:13 #info there is consensus that starting CRelease as soon as possible is important, and setting a one month planning phase is sufficient for the C-Release. 15:41:29 #info frankrockners also highlights that new project onboarding need to fit into that timeplan 15:46:37 #info today is the kick-off day 15:46:48 Can we call today MS0? 15:47:17 uli-k +1 it will avoid confusion and panic among projects... 15:47:18 #info projects have now 1 month to indicate their intent to join and establish their plans 15:51:01 +1 to both 15:51:05 +1 both 15:51:06 #info feature code freeze is very tight. 15:51:07 lets give it a shot 15:51:17 #info there is a holiday on May 1st. 15:51:30 May 1st is a sunday :) 15:51:44 #info in China, it's long holiday 15:51:56 how many days? 15:52:06 uli-k: In many countries it's the 1st Monday in May 15:52:23 #info maybe 7 days, I will double check it 15:53:47 #info uli-k, only 3 days. good news. 15:54:07 in August it will be hard/impossible to mobilize contributors for troubleshooting and test integration beginning of August to reach the release date... 15:54:19 #info Does the TSC approve the establishment of the C release active immediately with a release cadence of 6 months? (-1, 0, +1) 15:54:30 sounds reasonable to me 15:54:33 #startvote Does the TSC approve the establishment of the C release active immediately with a release cadence of 6 months? (-1, 0, +1) 15:54:33 Begin voting on: Does the TSC approve the establishment of the C release active immediately with a release cadence of 6 months? Valid vote options are , -1, 0, +1, . 15:54:33 Vote using '#vote OPTION'. Only your last vote counts. 15:54:39 #vote +1 15:54:41 #vote +1 15:54:44 #vote +1 15:54:45 #vote +1 15:54:46 #vote +1 15:54:46 #vote +1 15:54:47 #vote +1 15:54:49 #vote +1 15:54:50 #vote +1 15:54:53 #vote +1 15:54:54 #vote +1 15:54:58 #vote +! 15:54:58 dneary: +! is not a valid option. Valid options are , -1, 0, +1, . 15:55:01 #vote +1 15:55:01 #vote +1 15:55:02 #info proxy for Parviz 15:55:09 #endvote 15:55:09 Voted on "Does the TSC approve the establishment of the C release active immediately with a release cadence of 6 months?" Results are 15:55:09 +1 (13): Julien-zte, dku, dneary, TomNadeau, GeraldK, ChrisPriceAB, uli-k_, ttallgren, frankbrockners, JonasArndt, bjskerry, mbeierl, rpaik 15:55:25 #info bryan_att +1 vote too 15:56:16 #info "establish release plan wiki /projects//releaseplan" 15:56:54 #topic AoB 15:57:30 #info frankbrockners asks when the wiki switch will be in effect 15:57:34 To confirm: I'm not around for the hackfest, so cannot help with wiki at that time 15:57:54 #info rpaik describes that this is a topic for the hackfest next week. 15:59:01 #topic onosfw project renaming 15:59:47 #info ashyoung outlines that the naming of onosfw is confusing and that there is a trademark issue on the name 16:00:06 #info ashyoung states that changing the name is the best approach at this time 16:00:18 #info "ONOSFW" to avoid trademark issues would like to rename it to "networkfw" 16:01:06 #startvote Shall the TSC approve the name change of onosfw to networkfw? (-1, 0, +1) 16:01:06 Begin voting on: Shall the TSC approve the name change of onosfw to networkfw? Valid vote options are , -1, 0, +1, . 16:01:06 Vote using '#vote OPTION'. Only your last vote counts. 16:01:06 #info ashyoung confirms that this is just a name change and no change in scope 16:01:18 #vote +1 16:01:20 #vote +1 16:01:20 #vote 0 16:01:21 #vote +1 16:01:21 #vote +1 16:01:24 One small concern that the new project is a bit generic 16:01:27 #vote +1 16:01:39 #vote +1 16:02:08 #vote +1 16:02:09 #vote +1 16:02:15 #vote 0 16:02:28 #info proxy for bryan_att 16:02:51 #vote +1 16:03:19 #endvote 16:03:19 Voted on "Shall the TSC approve the name change of onosfw to networkfw?" Results are 16:03:19 0 (2): TomNadeau, Julien-zte 16:03:19 +1 (9): GeraldK, dku, dneary, ChrisPriceAB, ttallgren, frankbrockners, bjskerry, mbeierl, rpaik 16:04:09 #endmeeting