...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Task Forces:
<DRAFT> (Maybe this should be moved lower)
The architecture sub-committee can initiate tasks forces to progress specific topics. The output of the tasks forces are always reported back into the architecture sub-committee before further progressing towards the TSC or the ONAP projects. As per the nature of the architecture sub-committee the Task Forces are advisory by nature. The creation and termination of tasks forces are clearly announced in the architecture sub-committee meetings.
The current task forces are:
| Task Force | Scope | Contact |
|---|---|---|
| Maintains, defines the Platform Maturity Requirements per release | ||
| Microservices Sub-team | ||
| Architecture Tiger Team | Proposing the Architecture for the release beyond the current release | |
| ONAP API Common Versioning Strategy (CVS) Guidelines |
</DRAFT>
- Platform Maturity Requirements (S3P)
- Microservices Sub-team
- Architecture Tiger Team
- ONAP API Common Versioning Strategy (CVS) Guidelines
...