...
- The list of repos that are to be included in Amber release under your project.
- For each repo, provide the following information:
- License Status:
- What license for each repo, Apache 2 or O-RAN?
- Whether the LICENSES.txt is included at the root of the repo and whether each code file has a license and copyright claim header?
- NOT including any contributing company proprietary information?
- Code status:
- Is the code available (code MUST be in by code freeze date of 11/04)?
- Is the code build-able?
- Is the building and artifact generation integrated with LF Jenkins? We can mark this item as "yes" if a particular repo implements a (a) verify, (b) merge and (c) daily release job. The group maintaining a repo needs to implement this.
- Documentation status:
- Following the documentation format, structure, and template provided by DOC project?
It is sufficient to have these files in your repo as per https://wiki.o-ran-sc.org/display/DOC#DocumentationHome-RequiredFiles as per these templates https://wiki.o-ran-sc.org/display/DOC#DocumentationHome-Templates : docs/installation-guides.rst, docs/release-notes.rst , docs/developer-guide.rst , docs/api-docs.rst. (docs/index.rst is also needed, but coming from the next step below).
- Documentation buildable by the DOC project?
- Also implement a Jenkins job for pushing these to https://o-ran-sc.readthedocs.io/en/latest/ . Instructions on how to publish them to via an automatic Jenkins job are here: Configure Repo for Documentation.
- Prepared a video demo for how to build and run your project.
- Following the documentation format, structure, and template provided by DOC project?
...