#opnfv-meeting: OPNFV TSC

Meeting started by ChrisPriceAB at 14:00:17 UTC (full logs).

Meeting summary

  1. roll call (ChrisPriceAB, 14:00:23)
    1. Chris Price (ChrisPriceAB, 14:00:27)
    2. Ashlee Young (ashyoung, 14:00:51)
    3. Frank Brockners (frankbrockners, 14:01:05)
    4. Tapio Tallgren (tapio__, 14:02:06)
    5. Ildiko Vancsa (ildikov, 14:02:21)
    6. Wenjing (Wenjing, 14:03:00)
    7. Bryan Sullivan (bryan_att, 14:03:15)
    8. Dave Neary, proxy for Chris Wright (dneary, 14:03:45)

  2. Approval of previous minutes of meeting (ChrisPriceAB, 14:03:53)
    1. AGREED: the TSC approves the previous minutes of meeting. (ChrisPriceAB, 14:04:27)

  3. Agenda Bashing (ChrisPriceAB, 14:04:52)
    1. https://wiki.opnfv.org/wiki/tsc TSC Agenda (ChrisPriceAB, 14:04:58)

  4. OPNFV Project classification discussion (ChrisPriceAB, 14:06:42)
    1. https://wiki.opnfv.org/requirements_projects?&#project_lifecycle (ildikov, 14:07:04)
    2. https://wiki.opnfv.org/requirements_projects Link to the proposal (ChrisPriceAB, 14:07:07)
    3. Ildiko outlines a proposal to combine the project types in the project lifecycle document into a single project type. (ChrisPriceAB, 14:10:49)
    4. the projects would include needed combinations of documentation, upstream development, needed integration and documentation. (ChrisPriceAB, 14:11:23)
    5. this is reflective of the way the projects are working, adopting an agile fashion of development that is inclusive of all aspects of working on technology development. (ChrisPriceAB, 14:12:18)
    6. ildikov describes the next step includes the need to update the project lifecycle document to reflect the listed proposal. (ChrisPriceAB, 14:14:49)
    7. The question is raised that if a project does not result in the development of code should it exist in OPNFV at all? (ChrisPriceAB, 14:15:45)
    8. ildikov describes that projects intending to provide requirements are already doing that. (ChrisPriceAB, 14:17:04)
    9. : I need to leave early today. Vikram Dham would be alternate for me. (Wenjing, 14:18:11)
    10. trevor_intel (trevor_intel, 14:20:20)
    11. http://projects.bitergia.com/opnfv/browser/scm-companies.html (aricg, 14:26:19)
    12. the proposal includes the re-classification of project types to; Continuous Build and Integration, Continuous Deployment and Testing & New Requirements and Features (ChrisPriceAB, 14:31:50)
    13. the proposal also removes the need for the "top level project" and aligns the project lifecycle reviews across the category types. (ChrisPriceAB, 14:32:28)
    14. AGREED: the TSC agrees to pursue further development of the above described changes. A community activity will be established to create a firm proposal. (ChrisPriceAB, 14:41:59)
    15. ACTION: Ildikov: to lead a community activity to revise the Project Lifecycle document and any needed changes to the bylaws for TSC review at a future date. (ChrisPriceAB, 14:43:04)
    16. question was raised what happens when you remove the “Top-Level” project? (rpaik, 14:43:36)
    17. Pls include me in team to propose changes (dlenrow, 14:45:14)

  5. OPNFV Support review and next steps (ChrisPriceAB, 14:45:49)
    1. please dont forget to include RayNugent as co-lead (RayNugent, 14:45:54)
    2. postponed this topic to next week. (ChrisPriceAB, 14:46:01)

  6. OPNFV Brahmaputra Release discussion (ChrisPriceAB, 14:46:12)
    1. please also include me in the team (ashyoung, 14:46:19)
    2. Debra reflects that there is limited dependency on OpenStack Liberty which makes a December releaese a viable release date. (ChrisPriceAB, 14:46:58)
    3. This raises the question of providing a Brahmaputra release in December based on Kilo, which would be after the Liberty release of OpenStack. (ChrisPriceAB, 14:47:45)
    4. there may be dependencies on a future Linux Kernel release planned to be available in December. (ChrisPriceAB, 14:48:03)
    5. There is a lot of information emerging on cross project dependencies, this requires further analysis from dependant projects. (ChrisPriceAB, 14:49:33)
    6. Discussion if the community is comfortable with being “behind” on OpenStack release if we stay with June/December cadence. (rpaik, 15:04:21)
    7. feedback that installer support & testing will likely require ~2 months post OpenStack release (rpaik, 15:06:27)
    8. https://wiki.opnfv.org/releases/brahmaputra/release_plan?&#brahmaputra_release_participating_projects (debrascott, 15:08:24)
    9. https://wiki.opnfv.org/releases/brahmaputra/release_plan?&#brahmaputra_release_participating_projects Brahmaputra release planning, including definition of "lab ready" (ChrisPriceAB, 15:08:52)
    10. suggestion made to agree on dates for Miestones A/B/C next week (rpaik, 15:27:51)
    11. https://wiki.opnfv.org/releases/brahmaputra/upstream_projects_schedules (frankbrockners, 15:28:01)

  7. Creation review for the Genesis project. (ChrisPriceAB, 15:30:15)
    1. https://wiki.opnfv.org/genesis/genesis_project_proposal genesis project proposal (ChrisPriceAB, 15:30:23)
    2. the genesis project intends to work across the installer projects to create a common set of requirements for the installers to comply to during the release project. (ChrisPriceAB, 15:32:19)
    3. the genesis project will additionally work with component teams to facilitate the integration of new components into the installers. (ChrisPriceAB, 15:32:53)
    4. https://wiki.opnfv.org/genesis (frankbrockners, 15:34:00)
    5. governance details are still in draft and will evolve (rpaik, 15:46:05)
    6. there are quetsions around some the text in the governance described on the genesis page. To be clarified further within the project. (ChrisPriceAB, 15:56:38)
    7. ashyoung will help clean up genesis governance (ashyoung, 15:57:16)
    8. VOTE: Voted on "TSC to vote to create the Genesis project?" Results are, +1: 8 (ChrisPriceAB, 15:57:52)
    9. AGREED: The TSC agrees to create the Genesis project in OPNFV. (ChrisPriceAB, 15:58:44)


Meeting ended at 15:58:53 UTC (full logs).

Action items

  1. Ildikov: to lead a community activity to revise the Project Lifecycle document and any needed changes to the bylaws for TSC review at a future date.


Action items, by person

  1. ildikov
    1. Ildikov: to lead a community activity to revise the Project Lifecycle document and any needed changes to the bylaws for TSC review at a future date.


People present (lines said)

  1. ChrisPriceAB (42)
  2. dneary (20)
  3. ashyoung (19)
  4. frankbrockners (12)
  5. collabot (10)
  6. bryan_att (6)
  7. rpaik (5)
  8. ildikov (4)
  9. TomNadeau (3)
  10. bjskerry (3)
  11. debrascott (3)
  12. dlenrow (2)
  13. VikramDham (2)
  14. Wenjing (2)
  15. tapio__ (2)
  16. aricg (1)
  17. RayNugent (1)
  18. HKirksey (1)
  19. Parviz (1)
  20. trevor_intel (1)
  21. fdegir (1)
  22. mlynch (1)


Generated by MeetBot 0.1.4.