We currently seem to be using
OSTC/OHOS/components/staging/ as a dumping ground for all new components, including those known of questionable IP provenance. It was meant to be a ground for components with design and software quality issues and not for components with known IP problems. Currently, we resort to making the repo under staging private if IP issues are found - after the fact.
OSTC/OHOS namespace should only contain software that has passed IP compliance checks so that as a project nobody can point to a subtree under this namespace to question our IP policies. Furthermore, with the transition to an NewCo project, anything that doesn’t pass IP compliance should never be integrated into the OHOS namespace.
I propose the creation of a separate
OSTC/pre-integration namespace where every new component and new versions of existing components (e.g. ACTS) are merged for IP compliance checks before they can be merged into the
OSTC/OHOS namespace in the appropriate location.
Obviously, this creates some additional burden since after the IP check the components needs to be moved to its appropriate location in the main code repos. Any solution to do this promotion automatically (at least in case of version upgrades for existing components) are appreciated. Perhaps we can being with only making this mandatory for NEW components.
After the migration to NewCo, new components can continue to be checked under
OSTC/pre-integration before being pulled into the NewCo project.
Any thoughts on this proposal?