- Created by Mahesh Jethanandani, last modified on Feb 23, 2021
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 2 Next »
Basics (12 Points)
(Result/Proof point (column A: enter Met/Unmet; Column B: enter relevant URLs/comments)
| SMO | ||
| Criteria | Result / Proof point | |
|---|---|---|
| Identification | ||
What is the human-readable name of the project? | Met | OSC Service Management and Orchestration (SMO) |
What is a brief description of the project? | Met | The primary goal of the SMO project is to creating a fully functional open-source Service Management and Orchestration (SMO) that is able to orchestrate and manage Network Functions defined by O-RAN based on the use cases defined by O-RAN Alliance WGs. |
What is the URL for the project (as a whole)? | Met | Service Management and Orchestration (SMO) |
What is the URL for the version control repository (it may be the same as the project URL)? | Met | Gerrit |
What programming language(s) are used to implement the project? | Met | Mostly Python |
What is the Common Platform Enumeration (CPE) name for the project (if it has one)? | Unmet | N/A |
Basic project website content | ||
| The project website MUST succinctly describe what the software does (what problem does it solve? | Met | Service Management and Orchestration (SMO) |
| The project website MUST provide information on how to: obtain, provide feedback (as bug reports or enhancements), and contribute to the software. | Unmet | |
| The information on how to contribute MUST explain the contribution process (e.g., are pull requests used?) (URL required) | Met | Tutorial: Making code contributions to O-RAN open source project |
| 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 | |
FLOSS license | ||
| What license(s) is the project released under? | Met | Apache 2.0 |
| The software produced by the project MUST be released as FLOSS. | Met | 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). | Met | Apache 2.0 |
| The project MUST post the license(s) of its results in a standard location in their source repository. | Met | Apache 2.0 |
| Documentation | ||
| The project MUST provide basic documentation for the software produced by the project. | Unmet | |
| The project MUST provide reference documentation that describes the external interface (both input and output) of the software produced by the project. | Unmet | |
| Other | ||
| The project sites (website, repository, and download URLs) MUST support HTTPS using TLS. | Met | All support HTTPS |
| 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 |
|
- No labels