September 26-28 Topics

Owned by Kenny Paul
Last updated: Nov 13, 2017 by Shuki Yulzari
23 min read

Service Orchestration Workflow Development and Testing~The September Developers Event is for ONAP developers, by ONAP developers. Your contributions and needs are what will drive the agenda for all of these sessions.  To build the agenda for the we are soliciting Topics for discussion from the community.  Ideally these are questions that you need a deeper understanding of in order to make progress or deep-dive information sharing in a particular area.

Topic Template - Cut&Paste as needed

Topic/Question Name

  • Description: Description of the topic and the objective/outcome desired at the end of the discussion.
  • Topic Leader: The person that is knowledgeable enough to lead and moderate this discussion.
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:
  • Link to data Source (if applicable)


INSTRUCTIONS:  

Please edit the section below and add any topics (using the template) that you would like to lead and/or attend. List the topic, and your name. If there is a topic that you would like discuss, but you do not feel that you can lead it, please list the topic below and indicate that you are "Interested in Attending", then indicate TBD as the "Topic Leader"

IMPORTANT DATES

Community Members provide Topic recommendations Aug. 3 - Sept. 10

Attendees self-select Topics of interest Sept. 11 - 15

Agenda set Sept. 18

TOPIC RECOMMENDATIONS



Amsterdam M4 Code Freeze Milestone Review  

  • Description: M4 Code Freeze Review of all Amsterdam Projects. TSC will vote on the projects and depending on the findings, TSC will need to decide on:
        1. projects who pass M4
        2. projects that will need to be removed from Amsterdam
        3. projects that will need some adjustements


Training: On the Importance of adopting Scrum and Estimating 

  • Description: Discussion on the benefits of applying Scrum techniques and Poker Planning for Estimating.
    1. Why is Scrum important for the Team. How to apply Scrum for distributed Team
    2. You can't swallow more that you can shew: Estimating with Poker Planning will make the team more realistic.

Beijing Release Calendar Proposal

Enforcing an "Upstream first" approach to ONAP

  • Description: Description of the topic and the objective/outcome desired at the end of the discussion.
  • Topic Leader: The person that is knowledgeable enough to lead and moderate this discussion.
  • Volunteer Note Taker: First Last  email
  • Estimated Duration:
  • Link to data Source (if applicable)
  • Interested to attend:


External Open Source collaboration (OPNFV, ODL, etc.) and required actions  


External Standards Coordination and required actions with a different SDO   


Joint Architecture/Usecase subcommittees' meeting 


Joint Architecture/Usecase/Modeling subcommittees' meeting 


ONAP security subcommittees' meeting   

  • Description: A discussion and feedback on ONAP security topics:  Static Code Scanning; CII Badiging program certification feedback (CLAMP team); Credential Management
  • Topic Leader: Alla.Goldnerephen Terrill; (together with a CLAMP team memember)
  • Volunteer Note Taker: Pawel Pawlak pawel.pawlak3@orange.com 
  • Estimated Duration: 1 hour
  • Link to data Source (if applicable)
  • Interested to attend:


Operator Perspectives on R2 (Beijing) Architecture 


R2 (Beijing) use cases/platform capabilities first presentation to the TSC