#opnfv-meeting: OPNFV release diagram

Meeting started by rpaik at 13:05:40 UTC (full logs).

Meeting summary

    1. purpose: architectural diagram + roadmap + Arno components? (rpaik, 13:10:08)
    2. weathermap for requirements project (vs. roadmap)? (rpaik, 13:11:51)
    3. press/analyst want higher-level information and they’re also interested in what’s comiing down the road (rpaik, 13:15:43)
    4. also questions on test & integration (rpaik, 13:16:20)
    5. Ray Nugent’s slide: a lot of info. on one slide. Trying to capture cadence/theme (rpaik, 13:18:55)
    6. Chris argues timeline is useful and could also be added at the bottom of a "weathermap" (Gerald_K, 13:19:52)
    7. hard to predict which themes are emerging (rpaik, 13:22:15)
    8. Chris’ slide: identify what infrastructure/HW is available (rpaik, 13:23:59)
    9. platform part a recognition of upstream projects OPNFV is working with (rpaik, 13:25:32)
    10. ...and acknowlegde the OPFNV projects (Gerald_K, 13:26:01)
    11. legal question: can we use the upstream logos? (Gerald_K, 13:26:26)
    12. need to figure out logo usage (rpaik, 13:27:18)
    13. logos can also confuse the message. you want to promote your own project, not the others (Gerald_K, 13:27:38)
    14. size of boxes/positioning are not indicative of anything (rpaik, 13:29:11)
    15. https://www.opnfv.org/developers/technical-project-governance/project-lifecycle (rpaik, 13:30:26)
    16. you may need to send logos to other upstream communities for approval (rpaik, 13:32:17)
    17. remove vRouter/vIMS (rpaik, 13:35:33)
    18. slide4 shows the "machinery", the process we are developing (Gerald_K, 13:37:31)
    19. OSCAR slide: good to have a process slide on our wiki (doesn’t need to be in the release diagram) (rpaik, 13:37:44)
    20. target would be tech. audience (rpaik, 13:38:30)
    21. Morgan’s slide: also includes definition of project types (rpaik, 13:41:14)
    22. timeline would be difficult + no reference to upstream projs (rpaik, 13:42:00)
    23. using the same format for multiple target audience (rpaik, 13:47:45)
    24. need to be careful with the use of code name (rpaik, 13:48:48)
    25. every project should come up with project descriptions (rpaik, 13:51:34)
    26. Bryan’s: rather than OpenStack/ODL use a more generic term? (rpaik, 13:56:48)
    27. Ray/Heather to get a strawman (rpaik, 14:01:34)


Meeting ended at 14:02:21 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. rpaik (28)
  2. Gerald_K (9)
  3. collabot (4)
  4. dneary (1)


Generated by MeetBot 0.1.4.