=================================
#opnfv-meeting: scenario planning
=================================


Meeting started by dmcbride at 13:02:35 UTC.  The full logs are
available at
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-04-06-13.02.log.html
.



Meeting summary
---------------

* roll call  (dmcbride, 13:02:45)
  * David McBride  (dmcbride, 13:02:57)
  * Frank Brockners  (frankbrockners, 13:03:48)
  * Ana Cunha  (anac1, 13:03:55)
  * Ray Paik  (rpaik, 13:03:59)
  * Bin Hu  (bin_, 13:04:03)
  * Brian Skerry  (bjskerry, 13:04:15)

* scenario ownership  (dmcbride, 13:04:43)
  * please document what a scenario on the wiki so we can distinguish it
    from a project and a feature  (RayNugent_, 13:08:08)
  * frankbrockners notes that scenario is a release vehicle that we had
    since Arno (there were 2 for Arno)  (rpaik, 13:08:38)
  * ACTION: David McBride - create glossary of terms (i.e., scenario,
    component, etc.)  (dmcbride, 13:11:09)
  * scenario is a collection of projects/components and their
    configuration  (rpaik, 13:13:26)
  * LINK:
    https://wiki.opnfv.org/display/SWREL/2.0.release.plan#id-2.0.release.plan-Scenariostatus
    (frankbrockners, 13:19:14)
  * so far most of the burden on scenarios has been falling on installer
    or test teams  (rpaik, 13:23:31)
  * integration needs to be task on its own and requires owners  (rpaik,
    13:24:29)
  * frankbrockners proposes using the current project structure to take
    ownership of scenarios  (rpaik, 13:40:56)
  * project teams can then prioritize which scenarios they will work on
    (rpaik, 13:45:34)
  * some of the components (e.g. ODL) have no associated projects
    (rpaik, 13:50:37)
  * dmcbride will schedule another meeting next week  (rpaik, 14:00:49)



Meeting ended at 14:01:00 UTC.



People present (lines said)
---------------------------

* rpaik (12)
* dmcbride (7)
* collabot` (6)
* RayNugent_ (4)
* frankbrockners (2)
* anac1 (1)
* bjskerry (1)
* bin_ (1)



Generated by `MeetBot`_ 0.1.4