#opnfv-meeting: OPNFV TSC

Meeting started by ChrisPriceAB at 14:01:13 UTC (full logs).

Meeting summary

    1. Uli Kleber (uli-k, 14:01:17)
    2. Dirk Kutscher (dku, 14:01:22)

  2. roll call (ChrisPriceAB, 14:01:26)
    1. Chris Price (ChrisPriceAB, 14:01:32)
    2. Morgan Richomme (morgan_orange, 14:01:45)
    3. Bryan Sullivan (bryan_att, 14:02:05)
    4. Wenjing Chu (Wenjing, 14:02:15)
    5. Larry Lamers (ljlamers, 14:03:42)
    6. Chris Wright (cdub, 14:03:45)
    7. Gerald Kunzmann (Gerald_K, 14:04:04)
    8. Debra Scott (Debra, 14:04:29)

  3. Approval of previous MoM (ChrisPriceAB, 14:04:39)
    1. AGREED: TSC approved previous minutes (ChrisPriceAB, 14:05:04)
    2. hui (hui, 14:05:05)
    3. Tapio Tallgren (Tapio_ta, 14:05:07)

  4. Agenda Bashing (ChrisPriceAB, 14:05:11)
    1. https://wiki.opnfv.org/wiki/tsc TSC agenda (ChrisPriceAB, 14:05:21)
    2. Parviz Yegani (Parviz, 14:05:53)
    3. Rajeev Koodli (rajeev, 14:06:41)
    4. 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. (ChrisPriceAB, 14:07:57)

  5. AP Follow up (ChrisPriceAB, 14:08:46)
    1. opnfv-users list has been created, the TSC mailing list will be populated on that list (ChrisPriceAB, 14:09:23)
    2. ljlamers2 (ljlamers_, 14:09:28)
    3. requirements project action underway. Preparation for discussions ongoing, meeting to be organised. (ChrisPriceAB, 14:10:10)
    4. dneary has created a list of project deliveries as input for B-Release planning. (ChrisPriceAB, 14:11:45)
    5. https://wiki.opnfv.org/community/release_dates (ChrisPriceAB, 14:11:48)
    6. Trevor will present the pharos plan to the TSC when ready (ChrisPriceAB, 14:13:30)

  6. Project activities (per project): (ChrisPriceAB, 14:13:39)
    1. Rajeev Koodli (rajeev, 14:14:43)
    2. aricg mentions he has the list of all contributors. aricg will inform the project leads of those who have been granted access. (ChrisPriceAB, 14:16:26)
    3. Project leads should take action within their projects based upon need to optimize the lists (bryan_att, 14:17:03)
    4. General discussion on identifying active participants in projects re refreshing committers list for projects (dneary, 14:17:26)
    5. Can we just look at who has contributed, and propose additions/removals based on that? (dneary, 14:17:33)
    6. Lessons learnt regarding to the deliverable document way of working from Doctor: https://wiki.opnfv.org/requirements_projects?&#requirement_and_document_handling_procedures (ildikov_, 14:20:11)
    7. uli-k mentions we should not call the "retrospective" a "post-mortem" (ChrisPriceAB, 14:20:15)
    8. ljlamers2 (ljlamers__, 14:20:29)
    9. request to capture lessons learned on the wiki (RayNugent, 14:21:00)
    10. 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 (bryan_att, 14:21:32)
    11. Request to do improvement in documentation management in gerrit DOCS-33 (ChrisPriceAB, 14:21:54)
    12. anyone can comment on Jira tickets (rpaik, 14:22:11)
    13. Branching and patching arno/stable OCTO-xx (ChrisPriceAB, 14:22:14)
    14. https://jira.opnfv.org/browse/OCTO-76 (fdegir, 14:24:26)
    15. 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 (ChrisPriceAB, 14:26:17)
    16. OpenStack Stable branch guide as an example: https://wiki.openstack.org/wiki/StableBranch (ildikov_, 14:26:48)
    17. ACTION: uli-k and the octopus team to define the intention for our maintenance branch stable/arno and our methods for working with it. (ChrisPriceAB, 14:29:02)

  7. Scheduling the Arno retrospective session (ChrisPriceAB, 14:30:16)
    1. rpaik outlines the plan to run an Arno retrospective (ChrisPriceAB, 14:31:47)
    2. Go for Thursday (ljlamers, 14:33:41)
    3. question on what time we should run the retrospective (ChrisPriceAB, 14:33:55)
    4. the proposal is to run the meeting from 06:00 to 07:30 PST on this Thursday (ChrisPriceAB, 14:34:42)
    5. Tapio Tallgren (tapio_t, 14:35:15)
    6. AGREED: to run the call this Thursday at 06:00 (ChrisPriceAB, 14:36:11)
    7. ACTION: ray to set up the meeting (ChrisPriceAB, 14:36:18)
    8. 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 (ChrisPriceAB, 14:38:03)

  8. Release 2 planning discussion (ChrisPriceAB, 14:38:28)
    1. Debra describes that she has seen questions around scope creep, roles and responsibilities, communication planning, and project dependancies. (ChrisPriceAB, 14:39:29)
    2. this creates a need for a detailed schedule including dependancies across projects (ChrisPriceAB, 14:39:54)
    3. there may be a need for a change management process that is well defined. (ChrisPriceAB, 14:40:38)
    4. the retrospective will provide Debra with useful feedback, and she is interested to hear from community members (ChrisPriceAB, 14:42:09)
    5. https://etherpad.opnfv.org/p/Arno_retrospective Etherpad for “Arno Retrospective” (rpaik, 14:42:16)
    6. 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. (ChrisPriceAB, 14:43:03)
    7. We need a high level plan for project guidance in their r2 planning (ChrisPriceAB, 14:45:04)
    8. time estimations for release processes are required to add to the release planning in order to establish timelines. (ChrisPriceAB, 14:46:13)
    9. ray asks if planning will consider a probable release date. (ChrisPriceAB, 14:47:11)
    10. 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 (ChrisPriceAB, 14:47:55)
    11. tnadue agree, we should align with upstream (RayNugent, 14:54:46)
    12. Debra is looking for support from project leads for her work (rpaik, 14:54:55)
    13. will look at analysis from Debra (+ team) and visit the feaibility of B-release in December (rpaik, 14:56:07)


Meeting ended at 14:56:11 UTC (full logs).

Action items

  1. uli-k and the octopus team to define the intention for our maintenance branch stable/arno and our methods for working with it.
  2. ray to set up the meeting


Action items, by person

  1. uli-k
    1. uli-k and the octopus team to define the intention for our maintenance branch stable/arno and our methods for working with it.


People present (lines said)

  1. ChrisPriceAB (44)
  2. bryan_att (13)
  3. dneary (9)
  4. tnadeau (8)
  5. ildikov_ (5)
  6. rpaik (5)
  7. collabot (4)
  8. ljlamers (3)
  9. fdegir (3)
  10. rajeev (2)
  11. RayNugent (2)
  12. hui (2)
  13. uli-k (2)
  14. tapio__ (2)
  15. Debra (1)
  16. ljlamers__ (1)
  17. Tapio_ta (1)
  18. [1]JonasB (1)
  19. tapio_t (1)
  20. aricg (1)
  21. morgan_orange (1)
  22. ljlamers_ (1)
  23. Wenjing (1)
  24. cdub (1)
  25. Gerald_K (1)
  26. Parviz (1)
  27. dku (1)


Generated by MeetBot 0.1.4.