Link development.rst to contributing.rst

A bit of a reorg combined with adding mention of the install guide
to the contributing doc.

Change-Id: I63678e0b3e2f60831ef28a8695a5c6cebcb087e2
changes/60/645960/10
Kendall Nelson 4 years ago
parent 68272b85d4
commit 62309ed2e8
  1. 9
      doc/source/contribute/contributing.rst
  2. 2
      doc/source/contribute/development.rst
  3. 4
      doc/source/contribute/webclient.rst
  4. 12
      doc/source/index.rst
  5. 2
      doc/source/migration.rst

@ -1,4 +1,4 @@
.. include:: ../../CONTRIBUTING.rst
.. include:: ../../../CONTRIBUTING.rst
.. NOTE(dhellmann): The title underline style just below relies on the
existing format of the file included just above.
@ -108,6 +108,13 @@ timeout to 3 minutes, run::
$ OS_TEST_TIMEOUT=180 tox -e py27
For More Extensive Testing...
-------------------------------
To set up your own local storyboard to see how your changes look in the webclient, see
the :ref:`development`.
.. _tox: https://tox.readthedocs.io/en/latest/

@ -1,3 +1,5 @@
.. _development:
=======================================
Installing and Running for Developers
=======================================

@ -5,7 +5,7 @@ Using tox:
----------
* Run the test suite::
tox -egrunt test
@ -28,7 +28,7 @@ Using grunt directly within virtual environment
-----------------------------------------------
* Activate virtual environment::
source .tox/grunt/bin/activate

@ -42,13 +42,6 @@ Using StoryBoard
Tasks, Stories, & Tags <gui/tasks_stories_tags>
Organizing Your Work: Best Practices <gui/best_practices>
Installation guides
-------------------
.. toctree::
:maxdepth: 1
install/development
Maintenance guides
------------------
.. toctree::
@ -70,8 +63,9 @@ Developer docs
.. toctree::
:maxdepth: 1
contributing
webclient
Running the Tests <contribute/contributing>
Webclient Commands <contribute/webclient>
Installation and Running for Developers <contribute/development>
Extending StoryBoard
--------------------

@ -33,7 +33,7 @@ Test Migration
you are infra-core or Zara or SotK, the best way to do this is to spin
up your own test instance in a VM or somewhere.
There are instructions on how to do that in :doc:`/install/development`.
There are instructions on how to do that in :doc:`/contribute/development`.
I won't go into detail
here on the ins and outs of getting set up. When you have an up-to-date
database you'll need to log in via the webclient. Upon successfully logging

Loading…
Cancel
Save