Dear TSC, I'd like to propose the formation of an architecture subcommittee to develop and maintain a functional architecture for ONAP.
Please see the details below. Chris * TSC subcommittee name: Architecture Subcommittee (ARC) * TSC subcommittee purpose: The architecture subcommittee is responsible for developing and maintaining a functional ONAP architecture. This functional architecture helps inform 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. 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. The architecture subcommittee operates on a rough consensus basis. If the subcommittee is unable to reach consensus on what advice to offer, the subcommittee will refer the matter to the TSC or inform the project that advice cannot be rendered. The architecture subcommittee will consult with Projects to help drive alignment between components and with the functional architecture. * TSC subcommittee expected deliverables: The architecture subcommittee will develop and maintain a functional architecture diagram and any explanatory material. Periodically, or midway through a release, the architecture subcommittee will schedule a walk-through with each project to understand API interactions between components. * TSC subcommittee starting participants: The architecture subcommittee is open to all interested participants, and meetings are open.
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
