2H / 2025 - Priorities
The CNTi Community will focus on the following areas during 2H/2025:
|
|---|
Below are the notes and votes collected during July - Aug to establish community priorities for 2H/2025 (see above):
PRIORITY VOTING
Each member of the CNTi community has a total of 5 points to assign to the below priorities. All 5 points can be used to vote for one item or multiple.
Assign a total of 5 points on the row with your name (add your name if not listed and you want to contribute).
Under each main category (i.e. A, B, C, …) we also have sub bullets. If you want to prioritize on the sub bullet level (i.e. A1, B1, B2, etc.) please add your points in the respective column while also noting in the cell the sub bullet. See example at the top of the table below.
| A | B | C | D | E | F |
Martin | 1 | 1 |
|
| 1 | 2 |
Cedric | 1 | 1 | 1 | 1 |
| 1 |
Rich | 2 | 1 | 1 (C1) |
|
| 1 |
Olivier | 2 | 1 |
|
|
| 2 |
Viyoma | 2 | 1 | 1(C1) |
|
| 1 |
Christopher |
| 1 | 1 | 1 |
| 1 |
TOTAL | 8 | 6 | 4 with 2 for (C1) | 1 | 1 | 8 |
LIST OF POSSIBLE PRIORITIES FOR 2H/2025:
The list below was created through discussions held in CNTi Governance calls during July and August 2025. Use the above table to vote on what you think we should focus on during 2H/2025.
A - CNF test suite code cleanup/refactoring, hardening, and test cleanup
A1 Specifically, Github Actions - address unhealthy status of our Github Actions
B - Support fixes and enhancements for project Sylva as they occur
C - Identify key areas of tests or best practices that would be of interest to incorporate into CNTi test suite
C1 - Look at industry trends (for example new deployment beyond helm) and identify possible new enhancements/tests
C2 - Checking how CNFs are deployed and how we can scan the resources
C3 - Discuss platform tests - either maintain what we have or remove. CNTi focus is on workloads.
D - Identify and establish new collaboration with other communities, vendors, operators
D1 - Potential to communicate and showcase the collaboration between AWS and CNTi (could do blog post). Maybe also an opportunity to communicate on use of Open5GS (NRF) use in testing.
D2 - Potential to communicate “backlog” items (as a blog post) that are of priority to CNTi for 2H and in doing so try to attract additional contributors
D3 - Explore opportunities to collaborate with TMF (cloud native components). Same could apply to ETSI (NFV working group).
E - Restart/Rethink our work with best practices
E1 - Addressing a concern with STDOUT/STDERR and if this is a valid best practice for real-world telco network functions? Concerns over how we motivate best practices and/or exceptions. Need a way of working and ability to get input from a cross section of stakeholders.
E2 - Evolving best practices
E3 - Sylva Frameworks discussions started which may provide input to best practices that we can leverage
F - Establish a reference CNF (open source) for the CNTi test suite. The CNF would be used to exercise and validate all tests available in the test suite.
F1 - free5GC deployment for CNTi (early stages in progress)