You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Please add your suggestions for the ONAP DDF below. Timeline for topic selection is:

  • Initial proposals due for review by the ONAP Program Committee 
  • Final review and selections   

There is a strong need to align the selection early.  This is response to feedback from previous events and due to the evolution of LFN events in general

  • Expectations for stronger developer engagement
    • Less slide-ware and more doing work. Topics that are development oriented are more likely to be selected for the Prague event.
  • Expectations for a better managed agenda 
    • Lots of frustration in the past over sessions getting created, changed and cancelled in an adhoc fashion.
    • There are going to be concurrent tracks from OPNFV and CNTT in addition to ONAP.
    • The number and size of meeting rooms available to ONAP is likely to be less than we have previously enjoyed. 

Program Committee

Eric Debeau

Davide Cherubini

Alla Goldner

Topics

<Sample Topic>

  • Short Description:  One line description of topic

  • Detailed Description: Detailed description of topic
  • Topic Leader: name 1, name 2, ...
  • Estimated Audience Size (1-15 / 15-30 / 30-50 / >50):
  • Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.

ONAP TSC Meeting

  • Short Description:  Standard TSC Meeting

  • Detailed Description: Meeting agenda here https://wiki.onap.org/display/DW/TSC+2020-01-16+Prague+F2F
  • Topic Leader: Kenny Paul
  • Estimated Audience Size (>50):
  • Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.

Platform Maturity Requirements (S3P) for Guilin

  • Short Description:  Review & discuss changes to platform maturity (S3P) requirements for Guilin release

  • Detailed Description: The ONAP Platform Maturity level definitions and required levels have remained static for the past few releases.  In this session we will review feedback from the project teams (to be gathered prior to the session) & discuss what changes can be made to the requirements so that ONAP can improve its maturity posture in a way that projects can easily achieve.  Please join to have your voice heard.
  • Topic Leader: Jason Hunt
  • Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 30-50
  • Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.
  • No labels