For current projects, continually update the documentation. Preferably there are doc patches for every blueprint or feature added.
For new projects, docs can go onto docs.openstack.org after a project gets approved by the TC and moved to the OpenStack git namespace.
The centralized doc team has to give approval to publish certain centralized guides that are related to multiple projects. Install Guides, configuration guides (high availability, security), API reference, admin guides, ops guides. All these types of guides are in that category.
Docs core does not always review content published to
But they do review the index pages listing them:
Docs core members review:
Specialty teams for docs are set up to review:
Projects should seek writers and developers who are willing to follow a set of conventions maintained by the docs team. Those conventions are available on the OpenStack wiki at Documentation/Conventions.
Currently Andreas manages to keep up most all our automation for builds, with help from Christian Berendt, Anne Gentle and Gauvain Pocentek.
If you ever question what to write, the docs team is happy to help. Typically we consider the audience (such as, cloud admins, operators, or application developers using an OpenStack cloud) and what tasks they want to complete (such as, configuring external networks or launching an instance).
Consult the Documentation/ContentSpecs page to determine where a document gets published. All of our docs are licensed with the intention of sharing with attribution, so you can take the doc content and repurpose it as long as you only use the OpenStack logo with brand guidelines in place. Refer to openstack.org/brand if you have questions.