Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.
Change-Id: Idf519ff362731c106bbd9b63135f8dab4c7b7b92
... | ... |
@@ -20,7 +20,7 @@ in `How To Contribute`__ in the OpenStack wiki. `DevStack's LaunchPad project`_ |
20 | 20 |
contains the usual links for blueprints, bugs, etc. |
21 | 21 |
|
22 | 22 |
__ contribute_ |
23 |
-.. _contribute: http://wiki.openstack.org/HowToContribute |
|
23 |
+.. _contribute: http://docs.openstack.org/infra/manual/developers.html |
|
24 | 24 |
|
25 | 25 |
__ lp_ |
26 | 26 |
.. _lp: https://launchpad.net/~devstack |
... | ... |
@@ -3,9 +3,9 @@ Contributing |
3 | 3 |
============ |
4 | 4 |
|
5 | 5 |
DevStack uses the standard OpenStack contribution process as outlined in |
6 |
-`the OpenStack wiki 'How To |
|
7 |
-Contribute' <https://wiki.openstack.org/wiki/How_To_Contribute>`__. This |
|
8 |
-means that you will need to meet the requirements of the Contributors |
|
6 |
+`the OpenStack developer |
|
7 |
+guide <http://docs.openstack.org/infra/manual/developers.html>`__. This |
|
8 |
+means that you will need to meet the requirements of the Contribututors |
|
9 | 9 |
License Agreement (CLA). If you have already done that for another |
10 | 10 |
OpenStack project you are good to go. |
11 | 11 |
|
... | ... |
@@ -46,8 +46,8 @@ Q: I'd like to help! |
46 | 46 |
`git.openstack.org <https://git.openstack.org/cgit/openstack-dev/devstack>`__ |
47 | 47 |
and bug reports go to |
48 | 48 |
`LaunchPad <http://bugs.launchpad.net/devstack/>`__. Contributions |
49 |
- follow the usual process as described in the `OpenStack |
|
50 |
- wiki <http://wiki.openstack.org/HowToContribute>`__. This Sphinx |
|
49 |
+ follow the usual process as described in the `developer |
|
50 |
+ guide <http://docs.openstack.org/infra/manual/developers.html>`__. This Sphinx |
|
51 | 51 |
documentation is housed in the doc directory. |
52 | 52 |
Q: Why not use packages? |
53 | 53 |
A: Unlike packages, DevStack leaves your cloud ready to develop - |