14:03:58 <bh526r> #startmeeting Weekly Technical Community Meeting 14:03:58 <collabot> Meeting started Thu Feb 9 14:03:58 2017 UTC. The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:58 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 14:03:58 <collabot> The meeting name has been set to 'weekly_technical_community_meeting' 14:06:42 <bh526r> #topic Strategic Items in Technical Community Discussion 14:07:02 <bh526r> #info Bryan proposed it on the mailing list 14:07:40 <bh526r> #info The background is that the Polestar WG is addressing strategic aspects from EUAG, which is good 14:08:20 <bh526r> #info If the strategy is related to implementation etc. technical nature, it is more appropriate to discuss it in technical community 14:10:06 <bh526r> #info Suggestion is to start to discuss on it 14:10:51 <bh526r> #info Bin Hu 14:10:57 <bh526r> #info Bryan Sullivan 14:11:12 <bh526r> #info Aimee Ukasick 14:11:36 <bh526r> #info Amar Kapadia 14:11:51 <bh526r> #info Dan Druta 14:12:18 <bh526r> #info Dave Neary 14:12:34 <bh526r> #info David McBride 14:12:53 <bh526r> #info Giuseppe Carella 14:13:05 <uli-k> #info Uli 14:13:23 <bh526r> #info Pasi Vaananen 14:13:46 <bh526r> #info Prakash Ramchandran 14:13:58 <bh526r> #info Dan Radez 14:14:12 <bh526r> #info Tapio Tallgren 14:14:45 <bh526r> #info Timo Perala 14:15:32 <bh526r> #info Hongbo Tian 14:18:28 <bh526r> #info Stuart Mackie 14:20:58 <bh526r> #info The discussion focused on specific examples 14:29:28 <bh526r> #info Narinder Gupta 14:30:09 <bh526r> #info Al Morton 14:32:01 <bh526r> #info Bryan will bring specific proposal on the table, e.g. focusing on devops model, using devstack or packstack, etc. 14:32:26 <bh526r> #info Uli added to coordinate with Fatih 14:32:56 <bh526r> #topic Update of Scenario Consolidation 14:33:00 <uli-k> #link https://wiki.opnfv.org/display/INF/Scenario+Consolidation 14:33:58 <bh526r> #info Uli had discussions with Joid, Fuel, Apex etc. teams 14:35:24 <bh526r> #info Uli collected information from those installers, e.g. from repos, started to compare yaml files 14:36:32 <bh526r> #info With comparison of those yamls, we may start to propose the common characteristics of scenarios 14:36:50 <bh526r> #info The proposal is the future step once the comparison is done 14:37:30 <bh526r> #info Uli can do a lot of proposals, but he needs review and comment 14:38:04 <bh526r> #info He can use ppt, easy to illustrate and present, but difficult to maintain as a record 14:38:16 <bh526r> #info what if we move it to gerrit? 14:39:32 <bh526r> #info Uli will move it to rst file, and appreciate review and comments 14:39:56 <bh526r> #info Dan Radez thinks it is a right approach, and community is moving to this direction anyway 14:40:08 <bh526r> #info Bryan asked which project's repo? 14:40:16 <bh526r> #info Uli said Octopus repo 14:41:33 <bh526r> #info All agreed above suggestion, and Uli will start to work on it 14:42:33 <bh526r> #topic Milestone Exception Process 14:42:57 <bh526r> #link https://wiki.opnfv.org/pages/viewpage.action?pageId=8690432 14:44:48 <bh526r> #info Background: during TSC call on Tuesday, this was discussed, and suggested to discuss it in technical community call on Thursday 14:46:21 <bh526r> #info David presented 3 options, and asked how to triage the exception requests 14:54:35 <bh526r> #info Tapio said the important is the visibility 14:54:51 <bh526r> #info transparency 14:55:14 <bh526r> #info meaning open communication with project team, and within project team 14:55:56 <bh526r> #info Uli said that we should consider whether or not the project is going to make the release 14:56:13 <bh526r> #info i.e. if recovery plan is credible 15:00:49 <bh526r> #info Option 2 is not a popular option, David will clean it up and continue discussion next week 15:02:25 <bh526r> #endmeeting