| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
...
This template is to be filled out for any project wishing to move to the "Mature" phase of the ONAP project lifecycle.
Once completed, remove this info box and the send the link for this page to onap-tsc@lists.onap.org to initiate the maturity review.
Per the ONAP Technical Community Document, the metrics for maturity review are:
›Successful participation in releases: The project demonstrates stable output (code base, documents) within its history of releases in accordance with the release policy.
›Architecture has been reviewed by the Architecture Committee
›Project is active and contributes to ONAP: The project demonstrates a stable or increasing number of contributions across recent releases. Contributions are commits which got merged to a repository of an ONAP project or a related upstream project. Commits can for example be patches to update the requirements document of a project, code addition to an ONAP or upstream project repository, new test cases and so forth.
›Mature artifacts produced: The project demonstrates that the artifacts produced by the project are deployable (where applicable) and have been successfully deployed, configured and used by end users (typically, service providers).
Review Submission Date:
Project Description:
...
Project Meeting Minutes:
Most of the contributors are from ZTE, so we choose to communicate with each other in person or via IM tools that are widely used in China. Unless we need to discuss something with people from abroad (areas out of China), we don't usually use the Zoom bridge for meetings.
Leadership Resources :
add lines if necessarry
Role | Name | Linux Foundation Login (LFID) | Email Address |
|---|---|---|---|
| PTL | Guangrong Fu | GuangrongFu | fu.guangrong@zte.com.cn |
| Committers | Guangrong Fu | GuangrongFu | fu.guangrong@zte.com.cn |
| tangpeng | tang.peng5@zte.com.cn |
Project & Release History
...
Statistics data from Bitergia from the very beginning
Release Name and Timeframe | Commits | Contributors | Companies |
|---|
Notes
| Amsterdam | 360 | 10 | 5 |
| Beijing | 136 | 13 | 6 |
| Casablanca | 134 | 10 | 4 |
| Dublin | 85 | 7 | 4 |
| El Alto | 21 | 1 | 1 |
- Use Cases:
- VoLTE
- CCVPN
Architecture Alignment:
We didn't create any doc under Elalto Architecture or somewhere else alike because we are not demanded to. If it is a MUST, we will add a page to Guilin-R7 Architecture.
Artifact Information:
Codes:
- https://gerrit.onap.org/r/admin/repos/holmes/common
- https://gerrit.onap.org/r/admin/repos/holmes/dsa - Deprecated
- https://gerrit.onap.org/r/admin/repos/holmes/engine-management
- https://gerrit.onap.org/r/admin/repos/holmes/rule-management
Documents:
Integration:
- In the past several releases, the Holmes team collaborated with the MSB team, A&AI team, and most importantly, the DCAE team in integration tests in the WindRiver lab to ensure the success of releases.
Tests:
End Users:
- China Mobile
- Fujitsu
Other Information:
Code Coverage:
The Holmes team has been constantly working on the code coverage improvement on our codes. Currently, the coverage of all repos of Holmes is above 60%.
Presentations: