TSC subcommittee name:
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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
...
Recurring meetings: Tuesdays, 1400-1600 UTC (starting June 13)
- January 2 Call
- January 9 Call
- January 16 Call
- January 23 Call
- January 30 Call
- February 13 Call
- February 20 Call
- February 27 Call
- March 6-7 Calls
- March 13 Call
- March 20 Call
- April 3 Call
- April 10 Call
- April 17 Call
- April 24 Call
- May 1 Call
- May 8 Call
- May 15 Call
- Casablanca Architecture Planning Meeting
- May 29 Call
- June 5 Call
- June 12 Call
- June 26 Call
- July 3 Call
- July 10 Call
- July 17 Call
- July 24 Call
...