14:01:13 <ChrisPriceAB> #startmeeting OPNFV TSC 14:01:13 <collabot> Meeting started Tue Jun 9 14:01:13 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:13 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 14:01:13 <collabot> The meeting name has been set to 'opnfv_tsc' 14:01:17 <uli-k> #info Uli Kleber 14:01:22 <dku> #info Dirk Kutscher 14:01:26 <ChrisPriceAB> #topic roll call 14:01:32 <ChrisPriceAB> #info Chris Price 14:01:39 <ChrisPriceAB> #chair rpaik 14:01:39 <collabot> Current chairs: ChrisPriceAB rpaik 14:01:45 <morgan_orange> #info Morgan Richomme 14:02:05 <bryan_att> #info Bryan Sullivan 14:02:15 <Wenjing> #info Wenjing Chu 14:02:23 * bryan_att will be IRC-only today 14:02:53 <ChrisPriceAB> ok brian we'll try and keep you informed 14:03:12 * bryan_att unless I can connect and just listen - in an OMA meeting 14:03:42 <ljlamers> #info Larry Lamers 14:03:45 <cdub> #info Chris Wright 14:04:01 <dneary> Hi all 14:04:04 <Gerald_K> #info Gerald Kunzmann 14:04:19 <ChrisPriceAB> morning Mr neary 14:04:29 <dneary> Whose video was that we were seeing? 14:04:29 <Debra> #info Debra Scott 14:04:39 <ChrisPriceAB> #topic Approval of previous MoM 14:04:40 <hui> # info hui 14:05:04 <ChrisPriceAB> #agree TSC approved previous minutes 14:05:05 <hui> #info hui 14:05:07 <Tapio_ta> #info Tapio Tallgren 14:05:11 <ChrisPriceAB> #topic Agenda Bashing 14:05:21 <ChrisPriceAB> #link https://wiki.opnfv.org/wiki/tsc TSC agenda 14:05:53 <Parviz> #info Parviz Yegani 14:06:41 <rajeev> #info Rajeev Koodli 14:07:57 <ChrisPriceAB> #info Uli raises the required 2 week window prior to creation review for the Quickstart project. We will defer that until next week to allow for community feedback. 14:08:46 <ChrisPriceAB> #topic AP Follow up 14:09:23 <ChrisPriceAB> #info opnfv-users list has been created, the TSC mailing list will be populated on that list 14:09:28 <ljlamers_> #info ljlamers2 14:10:10 <ChrisPriceAB> #info requirements project action underway. Preparation for discussions ongoing, meeting to be organised. 14:11:45 <ChrisPriceAB> #info dneary has created a list of project deliveries as input for B-Release planning. 14:11:48 <ChrisPriceAB> #link https://wiki.opnfv.org/community/release_dates 14:13:30 <ChrisPriceAB> #info Trevor will present the pharos plan to the TSC when ready 14:13:39 <ChrisPriceAB> #topic Project activities (per project): 14:14:43 <rajeev> #info Rajeev Koodli 14:15:41 <bryan_att> sorry having difficulty following - can someone take notes in IRC? 14:16:07 <bryan_att> what is the current topic "list of interested parties"? 14:16:26 <ChrisPriceAB> #info aricg mentions he has the list of all contributors. aricg will inform the project leads of those who have been granted access. 14:16:26 <dneary> bryan_att: General discussion on identifying active participants in projects re refreshing committers list for projects 14:17:03 <bryan_att> #info Project leads should take action within their projects based upon need to optimize the lists 14:17:04 <dneary> bryan_att: Can we just look at who has contributed, and propose additions/removals based on that? 14:17:26 <dneary> #info General discussion on identifying active participants in projects re refreshing committers list for projects 14:17:33 <dneary> #info Can we just look at who has contributed, and propose additions/removals based on that? 14:17:45 <bryan_att> dneary: that's my intent, with confirmation from the committers (it may prompt them to get more active9 14:18:26 <bryan_att> i.e. a "grace period" for demotion 14:18:57 <dneary> ChrisPriceAB, "retrospective" 14:19:25 <dneary> bryan_att: Just taking notes, not asking you the question... 14:19:42 <aricg> We can also see all the people who contributed so far here: https://build.opnfv.org/releases/ 14:20:03 <bryan_att> never shy to offer my opinion anyway 14:20:11 <ildikov_> #info Lessons learnt regarding to the deliverable document way of working from Doctor: https://wiki.opnfv.org/requirements_projects?&#requirement_and_document_handling_procedures 14:20:15 <ChrisPriceAB> #info uli-k mentions we should not call the "retrospective" a "post-mortem" 14:20:29 <ljlamers__> #info ljlamers2 14:21:00 <RayNugent> #info request to capture lessons learned on the wiki 14:21:01 <ChrisPriceAB> #topics Toolchain/workflow 14:21:32 <bryan_att> #info the stats at https://build.opnfv.org/releases/ need to include other things I sent in email, e.g. wiki edits, email, jira, gerrit, etc 14:21:54 <ChrisPriceAB> #info Request to do improvement in documentation management in gerrit DOCS-33 14:22:11 <rpaik> #info anyone can comment on Jira tickets 14:22:14 <ChrisPriceAB> #info Branching and patching arno/stable OCTO-xx 14:22:33 <fdegir> octopus has a jira ticket regarding documenting way to work with stable/arno: https://jira.opnfv.org/browse/OCTO-76 14:22:50 <fdegir> and more will be added 14:24:26 <fdegir> #link https://jira.opnfv.org/browse/OCTO-76 14:26:17 <ChrisPriceAB> #info a discussion on where bugs should be solved for arno/stable (in main or in the maintenance branch) and if any features should be added to arno/stable 14:26:48 <ildikov_> #info OpenStack Stable branch guide as an example: https://wiki.openstack.org/wiki/StableBranch 14:28:38 <tnadeau> one suggestion: any patches/changes to the code base must have an associated Jira ID/bug ID 14:28:48 <tnadeau> this is how patches should be tracked 14:29:02 <ChrisPriceAB> #action uli-k and the octopus team to define the intention for our maintenance branch stable/arno and our methods for working with it. 14:29:07 <tnadeau> i didn't hear anyone explicitly agree to do that 14:29:12 <bryan_att> we need to start CI using Kilo as a base asap, and add additional non-default features to it 14:29:24 <ildikov_> tnadeau: huge +1, very important from tracking perspective 14:29:49 <tnadeau> ok 14:29:52 <bryan_att> this is essential for liberty development activities 14:30:16 <ChrisPriceAB> #topic Scheduling the Arno retrospective session 14:30:26 <tnadeau> this process should also be clearly outlined on the dev's wiki so that everyone is on the same page as to how patches are pushed/etc... 14:31:47 <ChrisPriceAB> #info rpaik outlines the plan to run an Arno retrospective 14:33:35 <tnadeau> didn't we want to discourage audio calls for meetings going forward? 14:33:41 <ljlamers> #info Go for Thursday 14:33:55 <ChrisPriceAB> #info question on what time we should run the retrospective 14:34:42 <ChrisPriceAB> #info the proposal is to run the meeting from 06:00 to 07:30 PST on this Thursday 14:35:03 <ljlamers> I like 06:00 PDT 14:35:15 <tapio_t> #info Tapio Tallgren 14:35:42 <bryan_att> most of the points I would make have already been made in email - but little response so far... 14:36:11 <ChrisPriceAB> #agree to run the call this Thursday at 06:00 14:36:18 <ChrisPriceAB> #action ray to set up the meeting 14:38:03 <ChrisPriceAB> #info bryan_att mentions it is worth sending comments via e-mail as well. Ildiko adds that an etherpad provides a good fast way of tracking issue on the next 2 days 14:38:28 <ChrisPriceAB> #topic Release 2 planning discussion 14:39:29 <ChrisPriceAB> #info Debra describes that she has seen questions around scope creep, roles and responsibilities, communication planning, and project dependancies. 14:39:54 <ChrisPriceAB> #info this creates a need for a detailed schedule including dependancies across projects 14:40:38 <ChrisPriceAB> #info there may be a need for a change management process that is well defined. 14:42:09 <ChrisPriceAB> #info the retrospective will provide Debra with useful feedback, and she is interested to hear from community members 14:42:16 <rpaik> #link https://etherpad.opnfv.org/p/Arno_retrospective Etherpad for “Arno Retrospective” 14:43:03 <ChrisPriceAB> #info our project plan should provide a method for prioritization of the features and activities in order that we are able to time schedule our activities. 14:43:04 <ildikov_> rpaik: cool, thanks! 14:45:04 <ChrisPriceAB> #info We need a high level plan for project guidance in their r2 planning 14:46:13 <ChrisPriceAB> #info time estimations for release processes are required to add to the release planning in order to establish timelines. 14:47:11 <ChrisPriceAB> #info ray asks if planning will consider a probable release date. 14:47:55 <ChrisPriceAB> #info Debra answers that once we have the plan backwards from the release date we will be able to identify how the high level plan matches the release schedule 14:48:31 <dneary> Why not base release 2 on Liberty? 14:48:55 <uli-k> +10 14:48:57 <tnadeau> shouldn't our major releases here coincide with major upstream releases somehow? 14:48:58 <ChrisPriceAB> that has not been ruled out, but having our dependencies matched to a planned timeline will help us decide 14:49:50 <tnadeau> dep planning has to be part of our release planning 14:50:12 <ildikov_> As for the requirements projects' artifacts, if we go for Kilo, we will not have their new functionalities added during this cycle in the second release of OPNFV 14:51:41 * ChrisPriceAB has to drop off IRC, rpaik can you take over here please. 14:54:46 <RayNugent> #info tnadue agree, we should align with upstream 14:54:55 <rpaik> #info Debra is looking for support from project leads for her work 14:55:08 <[1]JonasB> Basing B on Liberty will mean we will slip over new year 14:55:12 <tapio__> /exit 14:55:22 <tapio__> sudo pacman -Syu 14:56:07 <rpaik> #info will look at analysis from Debra (+ team) and visit the feaibility of B-release in December 14:56:11 <rpaik> #endmeeting