Attendees:

Please add your name in here:

• @Tom Kivlin

• @Pankaj.Goyal (AT&T)

• @Trevor Cooper (Intel)

• @Peter Woerndle (Ericsson)

• @Ulrich Kleber (Huawei)

• @Trevor Lovett (AT&T)

• @Toshi Wakayama (KDDI)

• @Rabi Abdel (Vodafone)

• @Al Morton (AT&T)

• @Gergely Csatari (Nokia)  (Nokia)

Agenda and Minutes:

• Antitrust notices

  • Linux Foundation Anti-Trust Policy Notice

  • GSMA Anti-Trust Policy Notice

• Walk-in items

  • CNTT webinar ideas

    • CNTT Technical Webinar Topics

  • June vConf ideas

  • Baraque release planning: CNTT Baraque#ReferenceArchitecture2

• Agenda:

  • Project Review: https://github.com/cntt-n/CNTT/projects/10

• AOB

  • Branch/release process: if we are creating PRs for new/improved content, we will label as On Hold until after the Baldy release takes place (new "Baldy" branch will get created). Bug fixes/typos/etc. PRs can be created but use the label "Bug" to identify it can be merged pre-release.

  • Taylor: lots of updates to the spreadsheet that is tracking the CNTT requirements following the big updates in the last week(s)

    • https://docs.google.com/spreadsheets/d/12EWZVvlumktXoywvmlYPR_DrU34e7Gk_rSED3VyCG4o/edit#gid=0

    • Q (Peter W): how is this work coming back into the regular review flow in GitHub.  A: isn't yet, mainly covered in the various calls (RA2, RI2, etc.). Source of truth for CNTT requirements would be markdown files in CNTT repo.  e2e integration would be hard.

Meeting recording:

Open