Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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.

...