https://blueprints.launchpad.net/openstack-manuals/+spec/common-glossary-setup
The repositories security-doc, operations-guide, and openstack-manuals share the glossary. In the future the training-guides repository might use it as well. We should only maintain it in one place.
Also, translation should be only done in one place. Right now, translations happen in any of these repositories: In openstack-manuals using a separate POT file, in security-doc and operations-guide as part of the books.
Currently, the glossary is manually imported in the operations-guide and security-doc repositories when necessary. The operations-guide even contains a slightly different header than the version in the openstack-manuals repository.
The glossary terms must be available to maven at build time to ensure the links all work correctly.
We should continue to have a master source glossary.
The openstack-manuals repository should continue to be the master source.
Once a change to the glossary in the master source happens, it will be proposed to the other repositories via a Jenkins job.
Andreas Jaeger (jaegerandi)
Current build of complete glossary: http://docs.openstack.org/glossary/content/glossary.html
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.