...
- Anything that is not specified in this section must be followed consistently with the rest of Governance, such as the approval process for new projects/repositories.
- Ecosystem projects may adopt a different model of Contributor vs. Committer, and may choose the code approval/merging process that is more appropriate to their team.
- Ecosystem projects do not have any expectation of aligning with EMCO's release cycle or reporting on progress.
- Ecosystem projects are expected to related to EMCO in some capacity (examples include documentation, proofs of concept, extensions, deployment scenarios, third-party integration, etc.).
- The TSC does not recognize official PTLs for any of the Ecosystem projects.
- Code licensing will comply with Project Charter.
Should code licensing be mentioned in Governance? emco-base and emco-gui are using Apache2.. we probably don't want to be surprised by an ecosystem project pushing proprietary code under the EMCO umbrella, right? or even GPL2
...