Attendees:
Agenda
- Brainstorm discussion
- Identified actionable items Anuket can implement now
- More cross community collaboration - Identify communities to collaborate with:
- Nephio – Get the cloud vendors on board at the same time. Mostly an orchestrator and automation tool. Need to confirm that the two communities are in alignment. This is potentially the most fruitful approach. As the cloud providers are working hard on attracting the Telcos to use their cloud infrastructure, this might be a win -win strategy.
- Sylva – Already in alignment, but if Anuket goes into maintenance mode, there is a danger that Sylva might have trouble continuing as well.
- O-RAN? – Needs a definition of the underlying infrastructure and need to make sure that the projects are in alignment
- selective and focused collaboration
- Ask the vendors to participate on the implementation piece
- Find a project (developing markets)to assist
- Approach cloud vendors to contribute to projects by aligning with specs
- More cross community collaboration - Identify communities to collaborate with:
Overall, what do the different communities need from Anuket? Does Anuket need to change to be more attractive to these other communities? It does, but we don't have a good idea of what it is. Discussion of conformance, is it useful? We have launched several conformance projects that have not been adopted by the larger community. Quality specs and quality code is needed, but the backing of the Telcos is needed to drive adoption by the vendors. We lost the backing of one of the major Telcos due to changes in strategy.
Attendees:
...