Materials

• Priorities & Topics Covered
• Prague 2020 - CNTT Hack Challenges Under Consideration
• CNTT_Status_2019-11-13.pptx
• CNTT_Weekly_Governance - RI RC.pptx

Attendees

@name (Company)

1. Mark Cottrell (AT&T)
2. Rick Tennant (AT&T)
3. Jim Baker

4. Beth Cohen (Verizon)

5. Vincent Danno (Orange)

6. Joerg Aelken (Ericsson)
7. Mark Shostak (AT&T)
8. Peter Woerndle (Ericsson)
9. Rabi Abdel (Vodafone)
10. @Pankaj Goyal (AT&T)
11. Heather Kirksey  (LF)
12. Dongwook Kim (GSMA); on behalf of Jisu Park
13. Jonathan Beltran
14. Michael Fix (AT&T)
15. Ulrich Kleber (Huawei)
16. Pierre Lynch (Keysight)
17. Herbert Damker (DT)
18. Walter Kozlowski (Telstra)
19. Nick Chase (Mirantis)
20. Karine Sevilla (Orange)
21. Trevor Cooper (Intel)

Topics

• Walk-on Items & Agenda Bashing
• Housekeeping

• GSMA & LFN Updates

  • (Jisu & Heather)
  • Applicability of CLA to CNTT 
• Governance Workstreams

  • Prague F2F Planning (Rick & Jonathan)

    • Developing the Agenda
      • Wiki Link: Priorities & Topics Covered
    • Developing the CNTT Hack Challenges
      • Wiki Link: Prague 2020 - CNTT Hack Challenges Under Consideration
  • KubeCon F2F Planning
    • Agenda and Info  CNTT - CNCF TUG F2F workshop in KubeCon NA 2019 

    • Please indicate your participation on the CNTT – CNCF TUG F2F meetings during KubeCon using this link: https://forms.gle/VahVc9WVPNGMdk9p9

• Technology Status
  
  • Overall Status (Rabi)
  • CIRV - OPNFV (Fu Qiao, Mike F.)
• Marketing question: Business Decision Makers

Notes

• Anti-Trust Policies for GSMA and LFN are in effect for CNTT discussions
• Walk-on Items & Agenda Bashing
• Housekeeping

• GSMA & LFN Updates

  • GSMA considering hosting a CNTT event in London. Early 2020. (Kim Dongwook)
    • AI - F2F planning need to consider the offer and do some planning around this, consider facility sizing needed, topics, etc.
      • Workstreams could consider doing a more deep dive type of sessions.
        • Ideas/options:
          • Containerization discussion.
          • RI - RC planning
  • Contributor Licensing Agreement (CLA) - Jim Baker
    • All projects in LF subject to some sort of CLA
    • Activities per the ToR includes writing specs – which may require CLA for CNTT orgs - Jim has inquiry to legal
    • Work product that goes into OPNFV repos comes under CLA (on OPNFV side)
      • Includes code development and related artifacts
    • Question is whether CLA needs to be applied to work product in GitHub
    • Creative Commons work product doesn't need CLA - caveat - legal is checking
    • Action Item - main question - do we need to apply CLA to the specification documentation. LFN will return answer back. 
      
      • Assume we are ok unless/until we hear back.
• Governance Workstreams
• Technology Status