Jay S. Bryant f5797bdc85 [upstream] Add slides on 'WIP' patches to Workflow
It was discussed after the class in Boston that we might want
to add something about 'Work In Progress' patches in the
workflow section somewhere.  After looking through the content the
best place to put it seemed to be in the 'Reviewing' section as
that allowed to tell how a 'WIP' could be indicated and then how
that should be handled from a review standpoint.

This patch adds a couple of slides to cover the topic.

Change-Id: Icf77b248e4cfddf1d6efd5fa1d8b0a94fefdc76d
2017-10-25 13:57:48 -05:00
2015-11-27 15:36:47 +01:00
2017-02-07 14:06:43 +07:00
2016-10-14 14:52:30 +09:00
2016-10-19 18:29:57 +09:00
2014-06-11 18:04:08 -07:00
2017-10-14 11:32:54 +02:00
2014-05-29 10:32:06 +08:00
2017-08-22 11:20:14 +08:00
2016-10-09 03:35:30 +00:00

Team and repository tags

image

OpenStack Training Guides

This repository contains open source training material that can be used to learn about using and different ways of contributing to OpenStack (Upstream training).

For more details, see the OpenStack Training Guides wiki page.

It includes:

  • Upstream training
  • Training guides (draft)

Both guides include a set of slides used in the training events.

Building

Various manuals are in subdirectories of the doc/ directory.

Guides

All guides are in the RST format. You can use tox to prepare virtual environment and build all guides:

$ tox

You can find the root of the generated HTML documentation at:

doc/upstream-training/build/slides/index.html
doc/training-guides/build/slides/index.html

Testing of changes and building of the manual

Install the Python tox package and run tox from the top-level directory to use the same tests that are done as part of our Jenkins gating jobs.

If you like to run individual tests, run:

  • tox -e checkbuild - to actually build all guides
  • tox -e upstream-slides - build the Upstream training
  • tox -e training-slides - build the Training guides

Contributing

Our community welcomes all people interested in open source cloud computing, and encourages you to join the OpenStack Foundation.

The best way to get involved with the community is to talk with others online or at a meet up and offer contributions through our processes, the OpenStack wiki, blogs, or on IRC at #openstack on irc.freenode.net.

We welcome all types of contributions, from blueprint designs to documentation to testing to deployment scripts.

If you would like to contribute to the documents, please see the OpenStack Documentation Contributor Guide.

Bugs

Bugs should be filed on Launchpad, not GitHub:

https://bugs.launchpad.net/openstack-training-guides

Published guides

Guides are published at:

Description
Community created, open source training guides for OpenStack.
Readme 48 MiB
Languages
Shell 84%
Python 16%