OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|6 days ago|
|.gitignore||5 years ago|
|.gitreview||6 days ago|
|README.rst||4 years ago|
|index.html||1 year ago|
|make-index||1 year ago|
Each publication should get its own branch and is a living document.
In order to create a new slide deck, create your branch from the presentation template. See the template README for step by step instructions on this process.
Note that each branch should have a README.rst file where the first line is the title of the presentation.
Each time a publication is presented or published, the branch should be tagged (with a signed, annotated tag). The first line of the tag message should be the title of the event or publication, and the tag itself should be in the format "year-venue-publication". For example, if the presentation "overview" was given at LinuxCon North America 2013, you might tag it with:
git tag -s -m "LinuxCon North America, 2013" 2013-linuxcon_na-overview
The 'make-index' script will create an index page based on index.html, and all current branches and tags in the repo and their README.rst files.
Viewable publications are published to: http://docs.openstack.org/infra/publications