A long term endeavor to deliver features across multiple releases
Rationalized based upon clear technical and industry benefits
Has a clearly defined scope
Requires a dedicated content repository
A community which acts collectively as a single development entity
Has Committers with expertise in the relevant areas
Intended for a single ONAP release
Rationalized based upon convenience for an individual entity
Scoped broadly or a collection of unrelated items to satisfy a use case
Something that can exist without having a dedicated repo
A fully self-contained internal development team
Require Committers with different expertise
Info
title
Pro Tip
The TSC will always give preference to project proposals that address gaps in existing ONAP functionality vs. replacing existing functionality with a new proposal.
