14:58:48 #startmeeting OPNFV TSC 14:58:48 Meeting started Tue Nov 24 14:58:48 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:58:48 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:58:48 The meeting name has been set to 'opnfv_tsc' 14:58:56 too early GeraldK 14:58:58 #info Uli Kleber 14:59:01 #topic roll call 14:59:05 #info Uli Kleber 14:59:07 #info Gerald Kunzmann (DOCOMO) 14:59:13 #info Chris Price 14:59:15 #info Frank Brockners 14:59:42 #info mlynch 15:00:52 #info Edgar StPierre 15:01:15 #topic approval of previous minutes of meeting 15:01:49 #info the minutes of two past have been approved due to no feedback. 15:01:50 #info Bryan Sullivan 15:02:05 #info Brian Skerry 15:02:19 #info previous minutes are also approved. 15:02:22 #info Morgan Richomme 15:02:32 #info Dirk Kutscher 15:02:33 #topic Agenda Bashing 15:02:48 #link https://wiki.opnfv.org/wiki/tsc current agendsa 15:02:49 * bryan_att no vacation for me! 15:03:06 #info Vikram Dham 15:03:21 #info Tapio Tallgren 15:04:06 #info no further topics proposed 15:04:21 #topic Milestone D update 15:04:44 #info Debra outlines the plan for projects passing milestone D of Brahmaputra 15:04:52 #info Debra will prepare list of questions to every project 15:05:09 #chair GeraldK 15:05:09 Current chairs: ChrisPriceAB GeraldK 15:05:10 we now have quorum 15:05:12 #chair rpaik 15:05:12 Current chairs: ChrisPriceAB GeraldK rpaik 15:05:17 thanks ray 15:05:52 #info Debra will create a page per project on the Brahmaputra Wiki area 15:06:26 #info Frank requests to have this list of questions in advance, preferrably by today 15:06:51 #topic Project lifecycle discussions 15:07:30 #info The project proposal wiki is being updated to reflect the recent changes in bylaws 15:07:47 #info Ildiko asks rpaik when the www.opnfv.org pages will be updated 15:08:06 #info rpaik responds that the creative services team are working to update the web page 15:08:15 #info Parviz Yegani 15:08:43 #info Ildikov has asked for community input into the activity on the mailing lists. 15:09:08 #info Discussion on Word vs rst 15:09:11 #info dlenrow 15:09:24 happy vacation week dlenrow 15:09:52 #link https://wiki.opnfv.org/project_proposals/template 15:10:12 #link https://wiki.opnfv.org/project_proposals 15:10:53 #info frankbrockers promotes simplicity and thinks the wiki is suitable given our current best parctices 15:10:54 #info Chris prefers rst and using our repositories, Frank proposes Wiki (with link from project page to project proposal page) 15:11:20 #info a motion is put to remove the word document sitting on the wiki 15:11:24 we don't need the word template anymore 15:11:39 #info no 15:12:08 #info the TSC agrees to remove the word document and stick to the wiki proposal template 15:12:14 #undo 15:12:14 Removing item from minutes: 15:12:18 #agree the TSC agrees to remove the word document and stick to the wiki proposal template 15:12:58 #topic Project scope adjustments after the amended bylaws 15:14:21 #info question is on procedures around scope adjustment, e.g. reduce/increase project scope 15:15:21 #info Ray questions what is the project maturity gate when projects can change the scope frequently 15:16:06 uli-k your audio is having real trouble. I can hear your "white noise" only 15:16:32 #info dlenrow asks how active the TSC should be when project scope changes 15:17:14 #info problem might occur when a project scope might affect another project or even the overall OPNFV scope. 15:18:04 uli-k, We could hear you at the end - but it sounds like the static noise was also coming from you 15:19:46 #info Uli-K: there are several where the TSC would need to decide on updated project scope. we should encourage projects to seek guidance on the new scope. 15:20:36 #info Chris: if the project wants to change scope, they could just come to TSC to ask for approval. 15:20:44 #info Is there an example of a scope problem in OPNFV currently that we could use to test proposed solutions to this (possible non) problem? 15:21:27 #info Debra raises the question about the size of scope changes; would scope changes really affect the project that much? 15:22:34 #info Frank: what is the purpose of this discussion: does TSC simply wants to know about the change? 15:23:06 #info Ray: project scope should stay inside OPNFV scope and project should not overlap with other projects 15:25:01 #info frankbrockners proposes that we handle project scope change via a notification to the TSC, the TSC reserves the right to question or discuss the scope adjustment. 15:25:17 #info uli-k adds that the change should be well documented on the project page 15:26:05 can we provide some examples of scope change so PTLs have some idea as to what the TSC considers important to be notified of? 15:29:02 #agree the TSC agrees to implement the above procedures as a way of managing scope change. 15:29:16 #topic Process for archiving projects 15:29:56 #link https://www.opnfv.org/developers/technical-project-governance/project-lifecycle current lifecycle document 15:31:42 #info dneary asks how the community might terminate a project that has no active members 15:33:02 #info ttallgren outlines the confusion caused by having idle projects listed on the OPNFV wiki and creating misconceptions of our activity 15:34:36 #info if project steps out of SR,it should be clear it is inactive and carrying cost should be near zero 15:34:59 #info rpaik found a few projects that were dormant. He has discussed archiving with these projects. 15:35:27 #info we naturally split into participating in SR and not. This should be solved by rules for remaining active/eligible in SR 15:36:14 #info Ray basically used bitergia dashboard and Debra's project sheets to identify potentially stale projects 15:36:15 dlenrow participating in a SR is not the only way of being active. I would not be too strict on that. 15:37:30 #info Frank proposes after 1 year of no activity, TSC should try to contact the project and trigger a decision 15:39:09 if a project does not want to join a particular release, that should not mean they become dormant for that period 15:40:07 #info rprakash 15:40:47 #info can we look at Grading projects like OpenStack for people to know what are in good standing 15:40:57 #topic OPNFV Plugfest, needs and support 15:42:02 +1 to Uli 15:43:16 #info Uli-K proposed to discuss technical-related topic from Board meetings within TSC 15:43:27 #info Chris raised concern that Board discussions are closed 15:44:51 #info if BOD is considering major change in technical content of project, it would be nice for them to invite TSC to a (closed) meeting to discuss... 15:44:56 #info Uli-K proposes that Chris should request to have such technical topics be declared open by the board when possible 15:46:18 dlenrow: +1 15:46:57 #info +1 to TSC deciding technical scope of the OPNFV 15:47:15 https://www.sdxcentral.com/artiles/news/opnfv-opens-a-vote-on-nfv-mano/2015/11 ? 15:47:50 #info The board has a significant voice and the TSC should consider it's guidance carefully, but the life of the community is based upon the interest of the members at a technical level, and that includes new areas of scope. 15:48:24 Copied by hand.. https//www.sdxcentral.com/articles/news/opnfv-opens-a-vote-on-nfv-mano/2015/11/ 15:49:00 ttallgren: you're right. Somebody told SDXCentral LOL 15:49:13 #info for example, I will soon propose that the C release include projects addressing VNFM/NFVO functionality explicitly based upon upstream projects; I don't believe that we need the board to bless the scope of such projects in advance. 15:49:15 Just rumors, of course.. 15:49:28 Great link ttallgren! 15:50:12 #info that scope was clearly on the table for OPNFV at organizational creation; it's up to the TSC to determine when and how to address functionality in the overall scope of NFV/SDN. 15:51:02 #info this is just an example - others may be more problematic. but the TSC needs to drive the technical content, especially if it's the only "open" forum for scope discussion. 15:51:26 #info could we (Chris) ask for a joint BOD/TSC meeting to discuss technical aspects of changes w/ BOD? 15:53:07 #info info uli-k requests that TSC chair can request for more time to the board to collect TSC input 15:54:15 #Topic Wiki migration plans 15:54:37 #info rpaik outlines the plans for the confluence migration. 15:55:23 #info aricg is setting up the wiki hosting for confluence, it is expected that a 2 week lead time will be required before we start the migration process. 15:56:03 #info both sites wil be kept up for 2 weeks prior to final cut-over for review and formatting. 15:57:16 #info aricg asks if we can update Jira to Jira 7 15:57:49 #info no reason to reject 15:59:00 #info ChrisPriceAB requests Confluence migration to start after Dec. 1 (Brahmaputra Milestone-D) 16:00:40 #endmeeting