fa0a930642
From discussions on the mailing list[1] it seems that there is support for the idea that projects that being with a code drop present a higher risk of failing to attract interest outside of the initial developers. This change aims to clearly communicate the TC's position to projects considering applying to join OpenStack, by explicitly stating both that code drops may be required to demonstrate traction in the community, and that no such requirement for community engagement exists in general. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-April/129703.html Change-Id: I8ee9bb08ee143402e2b8240e3cbe6ba5b0684596
This repository contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee.
Directory structure:
- reference/
Reference documents which need to be revised over time. Some motions will just directly result in reference doc changes.
- resolutions/
When the motion does not result in a change in a reference doc, it can be expressed as a resolution. Those must be named YYYYMMDD-short-name with YYYYMMDD being the proposal date in order to allow basic sorting.
- goals/
Documentation for OpenStack community-wide goals, organized by release cycle. These pages will be updated with project status info over time, and if goals are revised.
See https://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.