openstack
/
monasca-api
Code Issues Proposed changes

Highlight Monasca Board in Contributor Document 

* remove generic blabla introduction

Change-Id: Ie347274562608b5b1a7d317749f7e949d9baa1af
This commit is contained in:
Witold Bedyk 2018-10-18 14:52:55 +02:00
parent 1c0543f21d
commit b40cb8e0e0
1 changed files with 7 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/source/contributor/index.rst
View File

@ -1,19 +1,12 @@
======================= ==========================
Contribution Guidelines Contribution documentation
======================= ==========================
In the Contribution Guide, you will find documented policies for Kanban Board
developing with Monasca. This includes the processes we use for ~~~~~~~~~~~~
blueprints and specs, bugs and other procedural items.
Monasca, as with all OpenStack projects, is written with the following Progress on implementation of important stories in Stein release is tracked in
design guidelines in mind: `Monasca Board on StoryBoard <https://storyboard.openstack.org/#!/board/111>`_.
* **Component based architecture**: Quickly add new behaviors
* **Highly available**: Scale to very serious workloads
* **Fault tolerant**: Isolated processes avoid cascading failures
* **Recoverable**: Failures should be easy to diagnose, debug, and rectify
* **Open standards**: Be a reference implementation for a community-driven api
Workflow Workflow
~~~~~~~~ ~~~~~~~~
@ -28,9 +21,6 @@ desires for new features using Storyboard stories. The workflow is very simple:
* Significant features require `release notes`_ to be included when the code is * Significant features require `release notes`_ to be included when the code is
merged. merged.
Progress on implementation of important stories in Stein release is tracked in
`Monasca Board on StoryBoard <https://storyboard.openstack.org/#!/board/111>`_.
.. _bug report: .. _bug report:
Bug Reports Bug Reports