#opnfv-meeting: dovetail weekly meeting

Meeting started by hongbo5656 at 14:00:29 UTC (full logs).

Meeting summary

    1. Thaj (thaj, 14:00:38)
    2. Hongbo (hongbo5656, 14:00:58)
    3. Gabriel_YuYang (yuyang_gabriel_, 14:01:19)
    4. Chris Price (ChrisPriceAB, 14:01:19)

  2. dovetail development plan (hongbo5656, 14:02:39)
    1. https://global.gotomeeting.com/join/969604901 (ChrisPriceAB, 14:03:36)
    2. Uli Kleber (uli-k, 14:04:51)
    3. Bryan Sullivan (bryan_att, 14:05:41)

  3. CVP input from BOD (bryan_att, 14:05:57)
    1. Wenjing outlines the board discussion leading to a request for a plan and timeline for dovetail covering the test strategy, test working group activity and functions, any necessary gap items on the toolchain (ChrisPriceAB, 14:06:52)
    2. Wenjing reports on the BOD discussion: the BOD wants the TSC to move forward on the CVP, no specific guidance but a desire to move forward at least. (bryan_att, 14:06:55)
    3. BOD suggested to use more collaboration with DefCore etc. (uli-k, 14:08:53)
    4. to me the key question is one of timing, scope, and roadmap, and in practical terms our ability to define/agree/execute on a process for developing the program. (bryan_att, 14:09:04)
    5. with the 1st need to be to define the program and the process, esp the need to work upstream and leverage those assets directly rather than curating upstream tests in detail (bryan_att, 14:10:49)
    6. chris price get more people in from the test group (hongbo5656, 14:20:14)
    7. pother point: what compliance means (hongbo5656, 14:23:21)
    8. wenjing:1) test plan effort in jira should be done (hongbo5656, 14:32:47)
    9. 2) test tool: how to validate. (hongbo5656, 14:33:41)
    10. if we can use the tool in the test group, we do not need other tool. we need to discuss (hongbo5656, 14:34:34)
    11. (2) is a "how" and needs to follow the "what" definition (bryan_att, 14:34:42)
    12. we also need to be careful of thinking we can make progress simply by delegation to some other group (bryan_att, 14:35:27)
    13. 3) documentation: (hongbo5656, 14:35:43)
    14. re (3) the program management tools we are using are our documentation - if we plan to focus all this program definition effort on a collaboratively edited document managed thru gerrit we will not move any faster IMO (bryan_att, 14:36:50)
    15. https://docs.google.com/document/d/1M4jHLAAuLBHCWXDHmidrWfkjj0IaZqKnovj0WOkK344/edit#heading=h.fk7n1aaep7a3 (pjlynch, 14:37:42)
    16. (1) and (3) seem to be somewhat in conflict as the way we will manage the program definition phase (bryan_att, 14:37:50)
    17. (4) C&C should translate reqs to a scope, meaning, more specific so that Dovetail can have more specific guidance (bryan_att, 14:39:39)
    18. re (4) we should get C&C to collaborate with Dovetail thru JIRA, rather than waiting for a document will continue to slow us down, based upon the history of C&C progress (bryan_att, 14:40:42)
    19. (5) administering the CVP workflow, e.g. how does a candidate go thru the program (bryan_att, 14:41:36)
    20. re (5), I do not see that as Dovetail scope (bryan_att, 14:41:49)
    21. ChrisPriceAB each project in OPNFV should weight in as to how their scope would be covered under a CVP - Dovetail should not do that work, rather make sure it gets done (bryan_att, 14:45:44)
    22. http://techdiscuss.opnfv.org (bryan_att, 15:03:08)


Meeting ended at 15:03:27 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. hongbo5656 (15)
  2. bryan_att (15)
  3. ChrisPriceAB (6)
  4. collabot` (6)
  5. dneary (3)
  6. pjlynch (3)
  7. trevor_intel (2)
  8. uli-k (2)
  9. yuyang_gabriel_ (1)
  10. thaj (1)


Generated by MeetBot 0.1.4.