...
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended recommended to provide these agreements and dates in this section.
...
Date | Project | Deliverable |
---|---|---|
To fill out | To fill out | To fill out |
Documentation, Training
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Reach out to each project to help them to integrate with MSB, including tutorial, demonstration and code example.
- Provide introduction, guideline and API documentation in ONAP wiki.
- Populate release documentation content to http://onap.readthedocs.io includes Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
...
Other Information
Vendor Neutral
If this project is coming from an existing proprietary codebase, ensure that all proprietary All proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must removed to comply with this rule and be agnostic of any proprietary symbols. If there is any new findings, the team promises to remove them ASAP.
Free and Open Source Software
...