cabe68f95c
This will be standart way for end users to ask Rally team to get some new feature. The idea is to make it realy simple for end users to ask about covering their use cases. E.g. to add request users don't need to deep dive in rally community, road map and how it works. They need just to share their use cases that is not covered by current rally functionality. As a bonus adding some Readme.rst files related to doc/* dirs Change-Id: I4c615101012ac9d1668ed766ac831f7e5c8129a8
38 lines
888 B
ReStructuredText
38 lines
888 B
ReStructuredText
========================
|
|
Content of doc directory
|
|
========================
|
|
|
|
This directory contains everything that is related to documentation and
|
|
bureaucracy. You can find here 4 subdirectories:
|
|
|
|
|
|
feature_request
|
|
~~~~~~~~~~~~~~~
|
|
|
|
If some use case is not covered by Rally, it is the right place to request it.
|
|
To request new feature you should just explain use case on high level.
|
|
Technical details and writing code are not required at all.
|
|
|
|
|
|
samples
|
|
~~~~~~~
|
|
|
|
If you are looking for samples of deployments and benchmarks configuration
|
|
you are on the right way
|
|
|
|
|
|
source
|
|
~~~~~~
|
|
|
|
Source of documentation. Latest version of documentation_.
|
|
|
|
.. _documentation: http://rally.readthedocs.org/
|
|
|
|
|
|
user_stories
|
|
~~~~~~~~~~~~
|
|
|
|
Place where you can share any of Rally user experience. E.g. fixing some bugs,
|
|
measuring performance of different architectures or comparing different
|
|
hardware and so on..
|