OpenStack Technical Committee Decisions
Go to file
Chris Dent f3ba38f791 Begin integrating vision feedback and editing for style
This patch, a followup to Ifde9f19cfa07c62320e2ce09f6d5e803357aa0b4,
attempts to do two main things:

* react to some of the feedback provided on the original document
  and in the related survey and summit sessions

* adjust the writing to be somewhat more structured (work in
  progress) and tighter

Notable changes include:

* adding section headers (current wording stubs for review)

* making room for a preamble which sets the stage for what the
  document is; many original readers did not understand the "this is
  a blog posting from the future" format

* making room for a bullet list of summary

* shrinking, slightly, the constellation section

* Being more consistent throughout about case and using the active
  voice. This is a bit difficult given the future-but-looking-back-
  format. It's not yet perfect but I hope at least improved. The
  change in voice probably has the most significant impact in terms
  of causing a large diff.

* Removing superflous "very" and "really" style words where they
  were superfluous. More of this could be done, but it might remove
  the somewhat folksy tone which appears to be there on purpose.

* Things like "drive-by" having been changed to use phrasing that
  hopefully has less risk of offending.

* Entries which felt too ambiguous or didn't add much value (such as
  the git-bot) have been removed or de-emphasized.

From my standpoint this continue to be a bit too long and too
story-like. It is not yet well suited for being read on the web.
Clearly, early drafts should be story like because that greatly
helps the authors to flesh out their ideas. But as an artifact to be
read in a useful fashion by others, that may be ideal. We probably
want to find a sweet spot in the middle.

This should be considered a work in progress both in terms of the
language and structure and the actual content. Not all feedback has
yet been incorporated.

Change-Id: I7374ccaf1c992cad0f1b1e7a0eacd17f3badd75b
2017-07-05 12:56:45 +01:00
doc/source Merge "Link to working groups list for discoverability" 2017-03-30 12:41:44 +00:00
goals [goals/pike] Update artifacts for Python 3.5 goal in I18n 2017-03-30 14:13:00 +00:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Begin integrating vision feedback and editing for style 2017-07-05 12:56:45 +01:00
resolutions add flake8 to the linter job 2017-03-15 17:47:28 -04:00
tools Merge "More gracefully handle intra-openstack moves" 2017-03-30 09:11:46 +00:00
.gitignore ignore files created by pbr during build 2015-05-23 08:09:26 -07:00
.gitreview Added .gitreview 2013-08-30 16:00:06 +00:00
.yamllint Reduce the scope of yamllints coverage 2016-10-18 14:09:41 +11:00
README.rst propose approval policy for goal responses 2016-08-30 14:56:20 -04:00
requirements.txt Keep py3.X compatibility for urllib 2015-12-23 20:48:17 +05:30
setup.cfg update sphinx and treat warnings as errors 2017-03-15 17:47:34 -04:00
setup.py provide infrastructure for publishing docs to html 2014-01-07 15:29:11 -05:00
test-requirements.txt update sphinx and treat warnings as errors 2017-03-15 17:47:34 -04:00
tox.ini add flake8 to the linter job 2017-03-15 17:47:28 -04:00

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.