Danube Release Docs Fixup patch 1

Done in this patch
1. Fixes in overview.rst
2. Moves governance folder under docs
3. Adds arno release use case doc from
https://wiki.opnfv.org/display/parser/Parser+Use+Cases to the
requirement folder
4. Moves two old tosca2heat documents into developer/design/examples
5. Adds new empty tosca2heat and verigraph design document under
developer/design.
6. Remove old contents in yang2tosca and policy2tosca design docs since
they are all related to installation/execution, not design.
7. Fixes in installation.instruction.rst and usage,guide.rst

To do in the following patches
1. Design doc writeup: Xiaodong(tosca2heat),
Shiva(yang2tosca/policy2tosca), Serena(verigraph)
2. Release doc writeup: Xiaodong and Howard
(postinstall.rst,scenario.description.rst), Serena(verigraph part of
release-notes.rst), release-notes.rst

Change-Id: If4f51067dd33acd2332e503ee31d6941b4df4c89
Signed-off-by: zhipengh <huangzhipeng@huawei.com>

2 files changed, 161 insertions, 0 deletions

diff --git a/docs/governance/committer/colorado release committer email motion vote record b/docs/governance/committer/colorado release committer email motion vote record
new file mode 100644
index 0000000..84cfc75
--- /dev/null
+++ b/docs/governance/committer/colorado release committer email motion vote record
@@ -0,0 +1,93 @@
+From: "Ram, Vinayak (NFV BU)" <vinayak.ram@hpe.com>
+To: "zhang.jun3g@zte.com.cn" <zhang.jun3g@zte.com.cn>, huangzhipeng <huangzhipeng@huawei.com>
+Cc: "Huruifeng (Victor)" <huruifeng@huawei.com>
+Date: Mon, 18 Apr 2016 12:06:52 +0000
+Subject: RE: Parser Committer Promotion Guidline call for approval from comitters
++1
+ 
+From: zhang.jun3g@zte.com.cn [mailto:zhang.jun3g@zte.com.cn]
+Sent: Monday, April 18, 2016 12:07 PM
+To: huangzhipeng <huangzhipeng@huawei.com>
+Cc: Huruifeng (Victor) <huruifeng@huawei.com>; Ram, Vinayak (NFV BU) <vinayak.ram@hpe.com>
+Subject: 答复: Parser Committer Promotion Guidline call for approval from comitters
+ 
+Hi,team, 
+
++1 
+
+it's ok for me! 
+
+Regards, 
+Julien
+
+ 
+
+ 
+
+
+  Julien(Jun) Zhang
+ NFV Architect
+D206(D2028), R&D Building, ZTE Plaza, #889, Bibo RD, 
+Pudong District, Shang Hai, P.R.China, 201203 
+T:+86 21 68897791 M:+86 15317680806 F:+86 21 50801070 
+E: zhang.jun3g@zte.com.cn G: julienjut@gmail.com
+www.zte.com.cn, www.opnfv.org
+
+
+
+
+
+发件人:         huangzhipeng <huangzhipeng@huawei.com> 
+收件人:         "Huruifeng (Victor)" <huruifeng@huawei.com>, "zhang.jun3g@zte.com.cn" <zhang.jun3g@zte.com.cn>, "vinayak.ram@hpe.com" <vinayak.ram@hpe.com>, 
+日期:         2016/04/18 08:33 
+主题:        答复: Parser Committer Promotion Guidline call for approval from comitters
+ 
+
+Hi Guys, 
+  
+Please perform the actions as described below by the end of this week. 
+  
+发件人: huangzhipeng 
+发送时间: 2016年4月11日 16:30
+收件人: Huruifeng (Victor); 'zhang.jun3g@zte.com.cn'; 'vinayak.ram@hpe.com'
+主题: Parser Committer Promotion Guidline call for approval from comitters 
+ 
+Hi everyone, 
+  
+Since I received only one comment from Julien so far on the cap of committer number, I updated the slide to address Juline’s comment and call for your approval. Please reply +1 if you are ok with our non-mandatory additional guideline, or specify your concerns if you have doubts about the current version. 
+  
+As I discussed in the previous meetings, after the slide (i.e the “Motion”) got unanimous +1 approval, I will submit it to our Parser repo so that it becomes a public document. Any further changes to the document should be done in a similar way: PTL or committer initiate a motion via email, and after committer approval submit it to parser repo, and merge after all the concerns addressed (all the -1 comments) 
+  
+This first document will be merged after the consent from you guys tho, since this is the starting piece. 
+  
+I will also show the record of the committer voting for openness and publicity. 
+  
+ 
+Best Regards 
+  
+Zhipeng Huang (Howard) 
+IT Standard & Patent
+华为技术有限公司 Huawei Technologies Co., Ltd. 
+  
+Mobile: +86-18576658966
+Email: huangzhipeng@huawei.com
+地址：深圳市龙岗区坂田华为基地 邮编：518129
+Huawei Technologies Co., Ltd.
+Bantian, Longgang District,Shenzhen 518129, P.R.China
+http://www.huawei.com
+本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
+止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
+的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
+This e-mail and its attachments contain confidential information from HUAWEI, which 
+is intended only for the person or entity whose address is listed above. Any use of the 
+information contained herein in any way (including, but not limited to, total or partial 
+disclosure, reproduction, or dissemination) by persons other than the intended 
+recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by 
+phone or email immediately and delete it! 
+ 
+ 
+ 
+--------------------------------------------------------
+ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.
+ 
+ 
diff --git a/docs/governance/committer/parser project committer promotion guidline.rst b/docs/governance/committer/parser project committer promotion guidline.rst
new file mode 100644
index 0000000..cc65a2d
--- /dev/null
+++ b/docs/governance/committer/parser project committer promotion guidline.rst
@@ -0,0 +1,68 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+============================================
+Parser Project Committer Promotion Guideline
+============================================
+
+Note
+====
+
+This rst document serves only as a guideline for current committers and PTL to
+refer when they are electing new committers. We would strongly recommend the
+qualities listed in this document (in the Guidelines section) to be taken into
+consideration, however there is no legal or mandatory authority whatsoever.
+Any terms that might be in conflict with TSC charter is void by nature.
+
+Goal
+====
+
+* Make Parser grow stronger and healthier, with more new ideas and new
+  contributors.
+* Few committers who work with more contributors on a large size of work.
+* Committers number expands when Parser project itself grows.
+* Committer swap to ensure participating company’s interest.
+* Do not mandatory set limit to ban contributors to run, the ultimate result of
+  a promotion is still a consensus driven by community discussion.
+
+Rationale
+=========
+
+* Committers should be a small group of core contributors that could provide
+  a leading force for a balk of work in the project.
+* As a small new project, the growth of Parser is very important.
+* For any newly proposed committers, besides KPIs like commits, they should be
+  able to bring and work on an appropriate size of workload, with or without new
+  work force, so that the ratio between committer numbers and the workload is
+  appropriate.
+* Key mission of the committer is to expand and strengthen the project,
+  with new ideas or new participants.
+
+Guidelines
+==========
+
+* For those who are proposed as committers, if other KPI holds, for approval
+  they should have new work plan proposed that are beyond the work from past
+  release. For those who have brought forward both new work plan as well as
+  new contributors, their promotion should be considered approved in a fast
+  track.
+* For those who are proposed as committers, if other KPI holds, but they only
+  cover a similar size of work to the past release, for approval they should
+  replace the original committer of the same company. If there is no previous
+  committer member from the same company, then the promotion should be put
+  through with enough discussions.
+* There will be a cap on committer number per company. It is recommended that
+  each participating should not have more than 2 committers at the moment.
+  However this cap subjects to modification in the future should the team
+  decide to change. There is no cap for individual contributors.
+
+Guideline Creation and Modification Procedure
+=============================================
+
+* Current committers vote on this motion via email, approval require a unanimous
+  consent.
+* Submit this motion as a rst file into the parser governance repo, to setup a
+  precedent. PTL should kick off a review for the document each cycle.
+* Any future change to the guideline should be done via new patches and code
+  reviews, with record of showing a previous committer unanimous vote result on
+  the motion of such modification.