Project Maturity Review for AAA - EXAMPLE-PURPOSES-ONLY
DO NOT COPY THIS AND EDIT IT - USE THE TEMPLATE BUTTON HERE TO CREATE YOUR PAGE
- 1 Information for PTL
- 2 Review Submission Date:
- 3 Project Description:
- 4 Project Landing Page: link to your project's wiki page
- 5 Project Meeting Minutes: link to your projects meeting minute page
- 6 Leadership Resources :
- 7 Project & Release History
- 8 Architecture Alignment:
- 9 Artifact Information:
- 10 Other Information:
Information for PTL
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 Landing Page:
Project Meeting Minutes:
Leadership Resources :
add lines if necessarry
Role | Name | Linux Foundation Login (LFID) | Email Address |
---|---|---|---|
PTL | |||
Committers | |||
Project & Release History
How long the project has been an active:
Release Participation:
Engagement levels for past releases (up to 3):
Commits per Release:
Contributors per Release:
Companies per release:
Use Cases: