TSC subcommittee name:
...
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
...
Architecture subcommittee is contribution-driven
People can sign up for slots on the agenda
We will request people to develop proposals/presentations to discuss during meetings and via email
- Looking for input from the community, including EUAG
- Mid-release, we will work with PTLs to schedule a walk-through
...
The architecture subcommittee is responsible for developing and maintaining a functional ONAP architecture, guided by principles. This functional architecture helps inform maintain relationships and interaction between functional modules, which may include high level information flows between the modules supporting the use case(s) driving each release. It also helps the community with project proposals by clarifying the new project relationship with existing components.
...
The architecture subcommittee will not make decisions regarding internal functioning of projects, but may identify synergies across projects.
The architecture subcommittee is advisory by nature, and not authoritative. It may provide advice to projects and to the TSC, such as by providing a forum to help resolve architectural questions that may arise.
...