In my opinion a body is needed that would be in charge of development tools and
best practices across ONAP.
* Unified coding conventions
* Selection of tools and libraries
* Structure of the code base
* Exceptions from the rules, if a project requires one
The goal is to streamline the development and making contribution to different
projects easier, while at the same time giving each project enough freedom in
terms of technologies and timelines. The number and heterogeneity of ONAP
projects must be taken into account.
Currently the integration committee is doing a great job there, but they also
handle a wide range of other topics such as the use cases.
Do you think a task force or subcommittee is due here? Please share your
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
ONAP-TSC mailing list