9550674275
Previously we indicated that retired projects should use the openstack/retired.config file when retiring projects. This would have worked in the past because this file didn't confer any special permissions to openstack. That has since changed and we now want to use the more generic opendev/retired.config file which only marks the project as read only. OpenStack should continue to use their special acl for retirment and that can be covered in OpenStack docs. Change-Id: Iafdd6c058c90d3e14c2bebcefc0d8351288ac55c |
||
|---|---|---|
| doc/source | ||
| .gitignore | ||
| .gitreview | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
OpenDev Manual
To build the manual, execute the following command:
$ toxAfter running tox, the documentation will be available
for viewing in HTML format in the doc/build/ directory.
Terminology
A note on terminology use in the manual:
This manual is in service of OpenDev, but does so primarily by documenting how developers and project drivers can use the infrastructure to accomplish their work.
We strive for consistent terminology that matches what developers and our tooling use, even if some hosted projects use different terminology.
Generally speaking these terms should be used as follows:
Project: The overall idea that there is a bunch of people working on a bunch of code/text/etc. It can also refer to that actual collection of code/text/etc (for instance, a project can be bundled up into a tarball, and extracted into a directory). When a tool interacts with that collection of code/text/etc, it interacts with the project (even if it does so via the mechanism of git).
Repository: There are times when one needs to refer to the actual source code management system of a project, that is, "git", and the actual technical implementations of that SCM. In those cases where it is important to distinguish the actual attributes of the SCM from the project, it is useful to use the word "repository".