a1c444beed
During numerous discussions at the Vancouver 2018 Forum, the topic of discouraging review cultural behaviors came up repeatedly. This has come up before, but never to the point where prior community participants and leaders who took the opportunity to reconnect with the community came into the room and explicitly stated that it was the review culture as to why they left. The common frustration that was repeatedly raised was having to revise patches over and over due to varying nitpicks where negative feedback was left forcing the patch to be updated in order to gain any additional review feedback. We recognize that this is counter productive, and that we need to change our review culture, so we are updating the principles to express the aspects of peer review that we value. Co-Authored-By: Doug Hellmann <doug@doughellmann.com> Change-Id: I3b615784824de2a15a911780fe8c37928f2c453e |
||
|---|---|---|
| doc | ||
| goals | ||
| pre-history | ||
| reference | ||
| resolutions | ||
| tools | ||
| .gitignore | ||
| .gitreview | ||
| .yamllint | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
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.