...
| near-RT RIC (end of Cherry) | |||
| Criteria | Result / Proof point / Notes | ||
|---|---|---|---|
| Identification | |||
What is the human-readable name of the project? | yes | O-RAN SC's Near-RT RIC RT = realtime RIC = RAN intelligent controller RAN = Radio Access Network O-RAN = Open RAN SC = software community | |
What is a brief description of the project? | yes | The near-RT RIC Platform is a software based near‐real‐time micro‐service‐based platform for hosting micro-service-based applications - the xApps - that run on the near-RT RIC platform. xApps are not part of the RIC platform and developed in projects that are separate from the near-RT RIC platform project. The near-RT RIC platform is providing xApps the infrastructure for controlling a distributed collection of RAN base stations (eNB, gNB, CU, DU) in a region via the O-RAN alliance's E2 protocol ("southbound"). (quote from Scope of the near-RT RIC platform and its components (summary)) | |
What is the URL for the project (as a whole)? | yes | Near Realtime RAN Intelligent Controller (RIC) | |
What is the URL for the version control repository (it may be the same as the project URL)? | yes | Multiple repositories in Linux Foundation Gerrit: https://gerrit.o-ran-sc.org/r/admin/repos/ List of repos: Scope of the near-RT RIC platform and its components (summary) | |
What programming language(s) are used to implement the project? | yes | C++, Golang, Python | |
What is the Common Platform Enumeration (CPE) name for the project (if it has one)? | no ID | ||
Basic project website content | |||
| The project website MUST succinctly describe what the software does (what problem does it solve? | yes | Scope of the near-RT RIC platform and its components (summary)) | |
| The project website MUST provide information on how to: obtain, provide feedback (as bug reports or enhancements), and contribute to the software. | yes | obtain: from gerrit repos or from the OSC releases: Releases bugs: Tools (mailing list, JIRA, Gerrit) enhancements: Same JIRAS tool as for feature planning. contribute: See OSC guidelines: Project Developer Wiki | |
| The information on how to contribute MUST explain the contribution process (e.g., are pull requests used?) (URL required) | yes | contribute: See OSC guidelines: Project Developer Wiki | |
| The information on how to contribute SHOULD include the requirements for acceptable contributions (e.g., a reference to any required coding standard). (URL required) | no (fix-priority very-low) | not available. | |
FLOSS license | |||
| What license(s) is the project released under? | yes | Apache 2.0 | |
| The software produced by the project MUST be released as FLOSS. | yes | Apache 2.0 | |
| It is SUGGESTED that any required license(s) for the software produced by the project be approved by the Open Source Initiative (OSI). | yes | ||
| The project MUST post the license(s) of its results in a standard location in their source repository. | yes | root dir of all repos included in the project | |
| Documentation | |||
| The project MUST provide basic documentation for the software produced by the project. | yes | https://docs.o-ran-sc.org/projects/o-ran-sc-ric-plt-ric-dep/en/latest/ and other documentation under: https://docs.o-ran-sc.org/en/latest/projects.html | |
| The project MUST provide reference documentation that describes the external interface (both input and output) of the software produced by the project. | partial (fix-priority medium) | Could be better organized. | Governance[2/17/2021] 2021-02-17 A page is to be created Introduction and guides & the page will be regularly updated for below:
|
| Other | |||
| The project sites (website, repository, and download URLs) MUST support HTTPS using TLS. | yes | ||
| The project MUST have one or more mechanisms for discussion (including proposed changes and issues) that are searchable, allow messages and topics to be addressed by URL, enable new people to participate in some of the discussions, and do not require client-side installation of proprietary software. | yes | Tools (mailing list, JIRA, Gerrit) | |
| The project SHOULD provide documentation in English and be able to accept bug reports and comments about code in English. | yes | ||
...