From b40cb8e0e07b85b83cedd8a87753dd7206158e19 Mon Sep 17 00:00:00 2001 From: Witold Bedyk Date: Thu, 18 Oct 2018 14:52:55 +0200 Subject: [PATCH] Highlight Monasca Board in Contributor Document * remove generic blabla introduction Change-Id: Ie347274562608b5b1a7d317749f7e949d9baa1af --- doc/source/contributor/index.rst | 24 +++++++----------------- 1 file changed, 7 insertions(+), 17 deletions(-) diff --git a/doc/source/contributor/index.rst b/doc/source/contributor/index.rst index d203bbaaa..6d33cf631 100644 --- a/doc/source/contributor/index.rst +++ b/doc/source/contributor/index.rst @@ -1,19 +1,12 @@ -======================= -Contribution Guidelines -======================= +========================== +Contribution documentation +========================== -In the Contribution Guide, you will find documented policies for -developing with Monasca. This includes the processes we use for -blueprints and specs, bugs and other procedural items. +Kanban Board +~~~~~~~~~~~~ -Monasca, as with all OpenStack projects, is written with the following -design guidelines in mind: - -* **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 +Progress on implementation of important stories in Stein release is tracked in +`Monasca Board on StoryBoard `_. 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 merged. -Progress on implementation of important stories in Stein release is tracked in -`Monasca Board on StoryBoard `_. - .. _bug report: Bug Reports