•  Collaboration with ITU on AI/ML for NFV (LFN/EUAG/Anuket/.. as Host)
  
  •  Collaboration - ITU

•  Release Updates
  •  Moselle leftover: https://github.com/cntt-n/CNTT/pull/3077
  •  Nile Release
    • Schedule

Moselle retrospective 

Let's discuss what went well, what was problematic in Moselle and what should we change.

What went well

• New content in RA2
• New content in RM, however scope was not always clear
• Working together with CNCF CNF Testsuite
• Lots of support from the team across the board

What was not going very well

• Chaotic doc conversion with lots of late changes and non review-ed merges
  • rst limitations and quirks
  • limited PoC / trial conversion
• Long time pending pr-s without any reviews
• Lots of cat herding
• Still have some disconnect between the RA and RC communities.  Always going to be an issue between converting requirements into deliverables.  Basically converting requirements into user stories and tests.  Some of the requirements cannot be tested. 
• Need to better articulate the must haves, should haves, and nice to haves 
• Recruiting new members into the community
• Anuket has not developer potential in upstream projects, like CNF Testsuite, Kubernetes of OpenStack
• Limited resources on RI2, RC2 and Functest potential for single point of failure.
• Functest's bus factor is 1, what happens if Cedric Ollivier wins the lottery?

What should we change

• Add documentation guidelines
  • heavily commented template, for example, with comments indicating heading level, simple and complex table formats (use of csv?), etc.
• Clarify contribution guidelines
• Do a better job of converting RAx requirements into user stories and test cases that can be used in RCx.
• More community outreach to recruit new member companies – propose session at ONS Summit
• Need to add field trials against the Anuket Assured badge to gain traction in the community
• Can we work with CNCF to develop field trials of not only the Anuket infrastructure piece, but also toe CNF/VNF piece.
• Need to relook at Functest as it is currently a single point of failure 
• Maybe we should create a doc team with a sub-stream leader who should review and merge the pr-s outside of the scope of doc sub-streams

Gergely Csatari 

•  CLA clarification
  
  • https://lists.anuket.io/g/anuket-tsc/message/1101?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Arecentpostdate%2Fsticky%2C%2Cgeorg%2C20%2C2%2C0%2C91310407

•  Scope of Anuket
  
•  

•  Software composition analysis

•  Leftovers from the merger

• • Leftovers of the OPNFV CNTT merger

•  Doc Conversion
  •  Progress tracking: Convert Anuket specifications to rst

•  PTL and WSL Stand-up
  
  • All meetings: Anuket Meetings

• \also be a good add