13:56:08 #startmeeting OPNFV TSC Meeting 13:56:08 Meeting started Tue Mar 31 13:56:08 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:56:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:56:08 The meeting name has been set to 'opnfv_tsc_meeting' 13:56:14 #topic roll call 13:56:18 # Chris Price 13:57:14 ChrisPriceAB: #info ;) 13:57:31 * ChrisPriceAB oops yep.... long day 13:57:32 #info Carlos Goncalves (proxying Dirk Kutscher) 13:57:37 #info Chris Price 13:59:06 #info Frank Brockners 13:59:08 #info Uli Kleber 14:00:07 #info Bryan Sullivan 14:00:37 I can 14:00:42 #chair rpaik 14:00:42 Current chairs: ChrisPriceAB rpaik 14:00:51 #chair rprakash 14:00:51 Current chairs: ChrisPriceAB rpaik rprakash 14:00:58 #info Tapio Tallgren (Nokia) 14:01:08 #info dlenrow 14:01:56 #topic Approval of previous minutes 14:02:17 #agree TSC approves the previous meetings minutes 14:02:26 #info Chris Wright 14:02:32 #topic Agenda Bashing 14:02:53 #Info unanimously approved agenda of last tsc meeting 14:04:33 #info frankbrockners raises the pending actions on populating the wiki with event details 14:04:50 #info Pierre Lynch 14:05:16 #info frankbrockers asks for a discussion on communication tools and quality 14:05:52 #info iben asks is it is the same topic as meeting methods and tooling 14:05:56 #info Parviz Yegani 14:06:28 #info video & recording for external marketing and internal to be decoupled 14:06:36 #info added to the agenda OPNFV communications tools and meeting methods 14:07:07 #link https://wiki.opnfv.org/wiki/tsc TSC meeting Agenda 14:08:18 #topic OPNFV videos & recordings - sharing and storing 14:08:56 #link https://www.youtube.com/channel/UC3EjXLJbub0tPFpnI3vEmYg/featured OPNFV YouTube channel 14:09:12 did the marketing update make it to the agenda on the wiki? 14:10:27 #info video recordings include training and tutorial and need storage and youtube channel and /or using different methods 14:11:01 #info YouTube is blocked in China so an alternative video website would be needed for our members in China 14:12:44 #info China has limitation so we can use our own opnfv channels in different websites in china to be decides through email communications 14:13:32 #info look for ways to organize marketing vs. tutorials on YouTube 14:14:09 #info having one channel with different playslists and content currently managed by Prothima 14:14:14 #info Ray to investigate options with Howard in China 14:15:17 #info Iben and Chris have volunteered besides Prothoma, Ray and Brandon 14:15:46 #action Iben, ChrisPriceAB, rpaik, Prathim and Brandon to resolve video storage and sharing. 14:16:08 it’s Prathima :-) 14:17:42 #topic OPNFV communications tools and meeting methods 14:18:06 #link https://www.youtube.com/channel/UC3EjXLJbub0tPFpnI3vEmYg <— this is the OPNFV youtube channel 14:18:21 #info frankbrockners outlines some concerns with conflicts between meetings using the gotomeeting account. 14:18:38 #info may be resolved with additional accounts. 14:18:57 #info multiple meetings using one gotomeeting account is difficult to handle due to overruns, echos, etc. 14:19:03 #info at time it is difficult to hear and communicate using online meeting tools. 14:20:06 * dneary heartily approves frankbrockners's proposal to do fewer calls 14:20:15 * ChrisPriceAB aye aye 14:20:30 #info whether we should have alternate tools and solutions for recording or using irc more often, create another sub-team to decide this 14:20:45 as we grow using IRC is needed 14:20:54 * ChrisPriceAB yes agree 14:21:02 we are bridging the enterprise world to the open soruce world 14:21:27 I have no strong feelings about the meeting tools, I have been able to use WebEx, Bluejeans, GoToMeeting on Android/Linux/Windows... 14:23:07 #info frankbrockners asks for a group to investigate and make proposals for how we meet in OPNFV 14:23:37 I agree we should take this offline. It's a large part of what drives the community and its effectiveness. 14:23:43 #info may be irc could be better solution - lets take it offline - look outside of opnfv - va;ue based on existing teams value based on communications 14:24:35 #info some OpenDaylight group uses Google hangout 14:25:04 #info There is certain Hangout recording tool 14:25:44 Add bryan too. 14:26:06 #action frankbrockners, ray nugent, Iben, dlenrow, bryan_att to look into this issue and propose solutions 14:26:54 #topic Summit travel planning and registration etc… 14:28:05 #info no opnfv meetup at openstack 14:29:15 #undo 14:29:15 Removing item from minutes: 14:29:27 #info no opnfv meetup registration at openstack 14:29:42 #info - It will be event by event basis using special code for co-location basis with registration code 14:30:59 frankbrockners: let me know when your meeting about meetings and i'll see if i can fit it in between all my meetings 14:31:19 s/your/you're/ 14:31:24 cdub: do you have a preference? 14:31:29 #link https://wiki.opnfv.org/#community_events 14:31:57 #action rpaik to add a link to the registration page for each event in the event table on wiki.opnfv.org 14:32:10 #link https://etherpad.opnfv.org/p/Vancouver_OpenStack 14:33:00 * cdub looks... today at end of this, later in the afternoon (not .eu friendly), 7:30am PDT tomorrow...not many good times (part of the problem ;) 14:33:22 * frankbrockners how about 9am PDT on Thur? 14:33:57 * cdub double booked 14:33:59 #info Notes column on the page contains Event content link 14:34:03 iben, Kind of like a community manager? 14:34:20 * frankbrockners 8am PDT tomorrow? 14:34:40 * frankbrockners we'd do IRC rather than audio - so you can be double booked 14:34:49 #info community events are different from TSC meeting 14:36:35 frankbrockners: true, although tomorrow 8am PDT is also booked (and i'm leading it, so won't have spare eyes for irc...this is why i didn't readily volunteer) 14:36:44 #info please update the wiki if something is needed 14:37:57 #info send email to Heather for any info on passes etc. 14:38:07 cdub: next try: 11am PDT on Thur? 14:39:02 frankbrockners: ding ding ding! we have a winner ;) 14:39:15 * frankbrockners w00t 14:39:37 #info Hetaher wants contributors to add to etherpad for Vacouver summit Monday 14:39:41 #topic OPNFV functest project issues 14:40:00 #link http://lists.opnfv.org/pipermail/opnfv-tsc/2015-March/000706.html email thread on the topic 14:41:55 #info Iben ready to lead the func test team 14:43:26 #info whether TSC should take action to 6-new name as commiters and change the list to get work done 14:43:34 In this startup phase we need to have latitude to add committers without meritocratic assessment 14:45:06 #info can existing team nominate some one from the list on func test site 14:45:26 here they are: https://gerrit.opnfv.org/gerrit/#/c/133/1/INFO 14:46:36 Is the project lead unavailable? 14:46:39 I vote for Iben 14:46:44 +1 14:46:45 ;) 14:46:48 #+1 14:46:49 Seems obvious that he could name a successor 14:46:55 #info please add me to the Functest project, I have done a lot of work in this area 14:47:40 #info why not get an email from Palani to Iben to be brought in as new memeber and then let him lead? 14:47:41 #link https://wiki.opnfv.org/developer/committer_promotions committer promotion process 14:50:14 #info current committers can also +2 whatever comes into the repo 14:52:03 ChrisPriceAB, How about dissolving functest, and creating fuctest-new with the same materials, and a different list of committers? 14:52:54 #info trevot to chase commiters and get 5 for getting majority for approval 14:53:49 #action trevor to wrangle the existing committers to vote in and approve the new committers to the project 14:54:12 #topic Development process and guidelines discussions 14:56:01 #info TSC will approve the project based on the scope defined at the time of approval and if it chnages need to bring back to TSC for approval 14:58:47 Scope is operating envelope project stays in for life unless TSC amended 15:00:22 #info project leads need to communite commiter changes (showing votes in IRC, email, etc.) 15:00:49 #info commiterlist addition/changes should be conveyed to opnfv help desk (Aric Garner) by sending email with proof of votes 15:02:49 #info require tools for handling managing blue prints etc 15:02:59 #link https://wiki.opnfv.org/requirements_projects proposed ways of working with requirements projects 15:03:47 change #topic? 15:04:17 ulik, This seems to fit in the current #topic 15:05:47 ulik: no still in dev process 15:08:24 In terms of fitting this into the OpenStack review, this is an improvement - we'll be submitting RST files to OpenStack Gerrit for review, and managing early drafts as RST in Git, so the workflow fits better 15:09:23 I do think there's a risk that the project->requirement specs and requirement spec->blueprint mapping needs to be managed so that it doesn't add a lot of work 15:09:29 #info binary artifacts as opposed to ascii so one can use different tools and sio can be discussed in community 15:09:34 #topic Arno and OPNFV release graphic 15:11:10 #info Chris Morgan Parveez Frnak proposed different release grapahics and under considerations for selection and options 15:12:19 #info Ray & Heather to go over and continue brainstorming for slection 15:13:00 #link http://lists.opnfv.org/pipermail/opnfv-tsc/2015-March/000691.html reference to the proposed diagram from frank 15:13:06 +1 informative project labels 15:13:52 #info need consensus for name change for required for projects based on marketing needs 15:15:04 #info Types of Graphics needed and release representative , process representative and finally time line representative - Friday guidelines 15:15:21 Graphics by committee, from the TSC no less :) 15:15:53 #info work with creative services to finalize and we will have another look 15:16:12 dlenrow, That's the best way to do it, haven't you heard? :-) 15:17:45 dneary: I'm as weak graphically as I am strong technically 15:18:19 #info Parviz had some questions on process what creative service will do and that can wait for return graphics for creative services 15:18:44 Y'all is folksy and gender neutral :) 15:19:04 * ChrisPriceAB oh don't start dave 15:19:52 #info descriptive names describing function and legends 15:19:59 dlenrow, I'm sure there's a veiled insult in there somewhere (around how good an artist you are?) 15:20:21 ChrisPriceAB: Ozzie's for "Y'all" 15:20:29 #info two versions: codename vs. descriptors 15:20:47 .Trademark disputes are also a great way to gain attention 15:20:53 #undo 15:20:53 Removing item from minutes: 15:21:14 #info come back to the community with two versions: codename vs. descriptors 15:21:38 #topic Arno release candidacy planning 15:21:40 #info openstack compute , openstack network like opnfv function test etc in future 15:21:59 #link https://wiki.opnfv.org/releases/arno/releasecandidates release candidate plan 15:26:05 #info irc meetings for rc release 7 AP PDT Thursdays 15:26:30 #agree to run the RC meeting via IRC on the Thursday at 07:00 AM Pacific time, directly following the weekly tech call 15:27:29 #link https://www.irccloud.com is a great option 15:28:39 #topic Arno Project plans & tracking 15:30:58 #info common understanding BGS to reach before Thursday for rc0 reporting 15:31:08 Correction: which boots the jump host (in the case of Foreman) 15:31:31 Current plan will not install a Jump host from the CD, it will run it as a live CD image 15:32:55 #info Octopus should be ready for rc0 since LF hardware will be ready by wednesday 15:33:10 https://dl.dropboxusercontent.com/u/12773330/opnfv_hw_pics/lfwirefront.png 15:33:17 https://dl.dropboxusercontent.com/u/12773330/opnfv_hw_pics/lfwirerear.png 15:34:07 #info image readiness is what is required for rc0 15:35:15 #info function test - running Jenkins on different labs - end of week part of function test running 15:35:55 #info documentation may need some 100 person hours 15:36:53 #info OSCAR is post release 1 - BGS will be dessolved and multiple option for Release 2 OSCR, Fuel, Juju projects tec 15:39:22 #info Installer scripts will be maintained in storage and maintained for future with new name for BGSc. 15:39:35 #topic TSC approval of OPNFV Documentation project 15:39:45 #info vimnbi can wait for documentaion project 15:40:03 #link https://wiki.opnfv.org/documentation_projects/opnfv_documentation 15:43:03 #info Documentation link contains all the required elements for release as described 15:45:23 #link https://wiki.opnfv.org/documentation_projects 15:45:34 #info some standardization for documents ans some more details 15:48:11 #info Document to wiki and pdf using tool as listed by iben 15:48:28 #startvote Vote to create the OPNFV Documentation project? (-1, 0, +1) 15:48:28 Begin voting on: Vote to create the OPNFV Documentation project? Valid vote options are , -1, 0, +1, . 15:48:28 Vote using '#vote OPTION'. Only your last vote counts. 15:48:33 #vote +1 15:48:39 #vote +1 15:48:40 #vote +1 15:48:42 #vote +1 15:48:43 #vote +1 15:48:45 #vote +1 15:48:45 #vote +1 15:48:50 #vote +1 15:48:59 #vote +1 15:49:02 #vote +1 15:49:17 #endvote 15:49:17 Voted on "Vote to create the OPNFV Documentation project?" Results are 15:49:17 +1 (10): frankbrockners, dlenrow, cgoncalves, tapio_, bryan_att, ChrisPriceAB, cdub, rprakash, julien_ZTE, ulik 15:49:27 #info rprakash proxy votes for Wenjing, on the phone, voted orally. 15:49:52 #topic Re-visit VIM Northbound Model and Interface review 15:50:09 #link https://wiki.opnfv.org/requirements_projects/vimnbi project proposal 15:50:10 #link https://wiki.opnfv.org/requirements_projects/vimnbi 15:50:21 * ChrisPriceAB beat you 15:50:31 :-) 15:52:19 #info “service orientated abstraction” will be the focus of the project 15:52:56 #info renaming vimnbi o serv ice oriented nbi might hlep show the limited scope 15:53:49 #info Parveez where shimlayer sits 15:54:48 #info major work is to describe the work and shimlayer is implementation issues 15:55:13 #inof on what rather than how 15:55:23 #undo 15:55:23 Removing item from minutes: 15:55:37 #info on what rather than how 15:57:54 Question: Would a title like "Service Oriented VIM Northbound Model and Interface" be OK? 15:58:02 #info VNFM or orchestrator can be edited for correctness after the approval if needed 15:58:24 And: a repository name like servicenbi or sonbi be OK? 15:59:25 #info previous discussions surrounding parser is not have any relationship with this 16:00:40 #info questions asked to be send to email and vote next week 16:00:55 #info send questions to the mailing list. will vote only next week (no discussions) 16:01:18 #info no presentation for vimnbi next week 16:01:41 #endmeeting