...
| RICAPP - Q1 2021 | |||
| Criteria | Result / Proof point | ||
|---|---|---|---|
| Identification | |||
What is the human-readable name of the project? | Met | OSC RICAPP | ORAN-SC RICAPP O-RAN = Open RAN RAN = Radio Access Network SC = software community RIC = RAN Intelligent Controller (Near real time RIC) APP = application, specifically an xApp that runs on the nearRT RIC |
What is a brief description of the project? | Met | This project develops xApps to support the OSC e2e use cases as well as demo xApps to demonstrate the use of the nearRT RIC platform and xApp SDK. | |
What is the URL for the project (as a whole)? | Met | ||
What is the URL for the version control repository (it may be the same as the project URL)? | Met | Gerrit (Multiple):
Find detailed list and short explanation here: RICAPP Wiki | |
What programming language(s) are used to implement the project? | Met | C++, Go, Python | |
What is the Common Platform Enumeration (CPE) name for the project (if it has one)? | no CPE | ||
Basic project website content | |||
| The project website MUST succinctly describe what the software does (what problem does it solve? | Met | ||
| The project website MUST provide information on how to: obtain, provide feedback (as bug reports or enhancements), and contribute to the software. | Met | OSC guidelines for reporting bugs Mailing list: Wiki: https://wikilists.o-ran-sc.org/pages/viewpage.action?pageId=20877888g/discuss: discuss@lists.o-ran-sc.org
| |
| The information on how to contribute MUST explain the contribution process (e.g., are pull requests used?) (URL required) | Met | See OSC : https://wiki.o-ran-sc.org/display/ORAN/Tutorial%3A+Making+code+contributions+to+O-RAN+open+source+projectguidelines: 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) | Unmet | Note: OSC should provide common requirements. | |
FLOSS license | |||
| What license(s) is the project released under? | Met | Apache 2, CSL.0, O-RAN Software license | |
| The software produced by the project MUST be released as FLOSS. | ? | Yes, for Apache 1.0. ? for O-RAN Software license | |
| It is SUGGESTED that any required license(s) for the software produced by the project be approved by the Open Source Initiative (OSI). | ? | Is O-RAN Software license OSI approved? | |
| The project MUST post the license(s) of its results in a standard location in their source repository. | Met | Referenced in all code & repos | |
| Documentation | |||
| The project MUST provide basic documentation for the software produced by the project. | Met | Docs: https://docs.o-ran-sc.org/projects/o-ran-sc RICAPP documentation | |
| The project MUST provide reference documentation that describes the external interface (both input and output) of the software produced by the project. | |||
| Other | |||
| The project sites (website, repository, and download URLs) MUST support HTTPS using TLS. | Met |
| |
| 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. | Met |
| |
| The project SHOULD provide documentation in English and be able to accept bug reports and comments about code in English. | Met |
| |
...