The purpose of this page is for projects to indicate their willingness to accept patches for new features, and under what conditions.
Project | Is Project willing to accept patches for new features? (Yes, Yes with conditions, No) | Conditions (if any) | Comments / Notes |
---|---|---|---|
AAI | Yes with conditions | Feature owner to help with GR, and resources must be provided by feature owner for use case updates. | |
OOF | Yes with conditions | Feature owner to help with GR and few items in the backlog | Currently, Only item in the backlog is removing GPL v3 from the docker image |
HOLMES | Yes with conditions | Features are fully clarified and resource permits. | |
CCSDK | Yes with conditions | Feature must be clearly defined and resources must be provided by feature owner. | |
SDNC | Yes with conditions | Feature must be clearly defined and resources must be provided by feature owner. | |
SDC | Yes with conditions | Feature must be clearly defined and resources must be provided by feature owner. | |
VVP | Yes | ||
UUI | Yes with conditions | Feature must be clearly defined and resources must be provided by feature owner. If not, UUI resource permits. | |
Modeling | Yes with conditions | Feature must be clearly defined and resource permits. | |
VFC | Yes with conditions | Feature must be clearly defined and resources must be provided by feature owner. | |
Policy | Yes with conditions | Feature must be clearly defined and resource permits. | |
EXTAPI | Yes with conditions | Feature must be clearly defined and resources must be provided by feature owner. | |
SO | No | No new functional features will be planned in H release. H release is intended to improve the key backlog items. | Any change that improves the SO platform usability are only accepted in H release |
DCAE | Yes with conditions | Feature must be clearly defined & approved by ARC team. Resources for dev/test must be provided by Feature owner. | |
CLI | Yes with conditions | Feature must be clearly defined & approved by ARC team. Resources for dev/test must be provided by Feature owner. | |
VNFSDK | Yes with conditions | Feature must be clearly defined & approved by ARC team. Resources for dev/test must be provided by Feature owner. | |
CPS | No | H release is the first release for this project. We are working with E2E network slicing and possible Son PCI Use-case (stretch goal) towards a Minimal Viable Product. Once that has been achieved CPS can be opened up for use by other components | |
MultiCloud | Yes with conditions | Feature must be clearly defined and resources must be provided by feature owner. | |
MSB | Yes with conditions | Feature must be clearly defined and resources must be provided by feature owner. |