#opnfv-meeting: Weekly Technical Discussion

Meeting started by bh526r at 14:00:02 UTC (full logs).

Meeting summary

  1. Roll Call (bh526r, 14:00:30)
    1. Bin Hu (bh526r, 14:00:49)
    2. Trevor Cooper (bh526r, 14:00:57)
    3. Mark Beierl (bh526r, 14:01:52)
    4. Cristina Pauna (bh526r, 14:02:49)
    5. Pierre Lynch (bh526r, 14:04:58)
    6. Al Morton (bh526r, 14:05:04)

  2. Discussion of Code and Release Quality (bh526r, 14:05:30)
    1. Cristina introduced the process of implementation (bh526r, 14:06:52)
    2. There are 6 steps in the process (bh526r, 14:07:09)
    3. Step 1 is to create standard format for input (bh526r, 14:07:43)
    4. Step 2 is to gather proposals (bh526r, 14:08:10)
    5. Step 3 is to debate proposals, polish them and get them in a better shape. This can be done in weekly technical discussion (bh526r, 14:08:53)
    6. Step 4 is to get approval from TSC (bh526r, 14:09:09)
    7. Step 5 is to create a JIRA for each proposal (bh526r, 14:09:30)
    8. Step 6 is to monitor progress, e.g. get them implemented, etc. (bh526r, 14:10:04)
    9. Mark asked if we want to achieve a consistent format of all projects, or we allow each project flexibility (bh526r, 14:11:08)
    10. Cristina explained we intend to help project, if one proposal gets buy-in of all projects, they will adopt it. If one proposal only gets support of very few projects, or no resources, then it won't be adopted. (bh526r, 14:14:41)
    11. Mark likes the approach of project helps each other (bh526r, 14:15:13)
    12. Cristina further introduces the template (bh526r, 14:15:26)
    13. as the Step 1 (bh526r, 14:16:10)
    14. The template includes (1) Problem description (2) Possible solution and Pros and Cons analysis (3) Resources needed such as HWs and human resources (4) Proposed Changes and (5) Owner of Implementation (bh526r, 14:18:57)
    15. Cristina gives an example of using template to describe (1) Use FuncTest to Verify Installer Patches (2) Reduce the time it takes for running tests (bh526r, 14:20:39)
    16. Georg Kunz (bh526r, 14:23:49)
    17. Al says it is worth trying (bh526r, 14:26:55)
    18. Trevor asks if there is specific area for each project (bh526r, 14:27:13)
    19. Cristina doesn't think there is a reason to have a limit (bh526r, 14:27:43)
    20. Trevor thinks TSC may make some suggestions (bh526r, 14:28:33)
    21. Mark thinks the idea is that anyone can make a proposal, and if enough interest, TSC may make guidance of where resources should go (bh526r, 14:29:40)
    22. Trevors thinks eventually we need to apply the process to direct the direction (bh526r, 14:30:40)
    23. Cristina thinks the area is the code and release (bh526r, 14:31:03)
    24. Mark thinks there is a TSC checkpoint in the process. When TSC takes the checkpoint, TSC will consider the strategic direction. (bh526r, 14:33:15)
    25. Mark suggests that we add a bullet point of TSC checkpoint to check alignment with strategic direction (bh526r, 14:33:52)
    26. Trevor likes this suggestion (bh526r, 14:34:07)
    27. Mark thinks TSC's role is to help proposal get more alignment with strategic direction (bh526r, 14:35:04)
    28. TSC needs to take into account the strategic direction to make go/no go decision (bh526r, 14:35:56)
    29. Cristina will add a note in the template for TSC to consider aligning with strategic direction (bh526r, 14:36:24)
    30. Mark is happy with it (bh526r, 14:38:23)
    31. Cristina will share the proposal and etherpad in the mailing list after new year. Input and comments are expected from community discussion in mailing list, and make proposal more polished and mature. (bh526r, 14:41:48)
    32. The target is to discuss it again on Jan 24. (bh526r, 14:42:28)

  3. AOB (bh526r, 14:42:37)
    1. Meeting adjourned (bh526r, 14:42:44)


Meeting ended at 14:43:05 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. bh526r (44)
  2. collabot` (3)


Generated by MeetBot 0.1.4.