Update Ask OpenStack
====================
Cross Project Spec - None

User Story Tracker - None

Problem description
-------------------

Problem description
+++++++++++++++++++
Operators of OpenStack environments lack a reliable source to find answers to
commonly encountered issues. The current ask.openstack.org site is not broadly
functional or well contributed to by the broader community.

Opportunity/Justification
+++++++++++++++++++++++++
A workable community knowledge base is a critical component of any successful
software. Even more so in free open-source projects. Having a simple place for
operators to go to acquire the collective community knowledge on a given topic
will significantly reduce the barrier to entry to utilizing OpenStack.

Requirements Specification
--------------------------

Use Cases
+++++++++
This section utilizes the `OpenStack UX Personas`_.

* As `Rey the Cloud Operator`_, I want to be able to quickly find reliable
  answers to common operational issues and questions so that I can continue to
  support my users
* As Rey, I want to ask an uncommon question in a community forum and receive
  an timely answer from the communities expertise so that I can continue to
  support my users
* As Rey, I want to see answers to previously asked uncommon questions and a
  notion to the popularity of previous answers so that I can continue to
  support my users

.. _OpenStack UX Personas: http://docs.openstack.org/contributor-guide/ux-ui-guidelines/ux-personas.html
.. _Rey the Cloud Operator: http://docs.openstack.org/contributor-guide/ux-ui-guidelines/ux-personas/cloud-ops.html#cloud-ops

Usage Scenarios Examples
++++++++++++++++++++++++
1. Common Question Usage - OpenStack Operator
	a. Go to common question repository
	b. Search for error code, topic, api call, etc
	c. Find most popular answer to common question
	d. Add support for popular answer if it resolves issue
2. UnCommon Question Usage - OpenStack Operator
	a. Go to common question repository
	b. Search for error code, topic, api call, etc
	c. Discover no answers have been provided
	d. Create new request, or add support for existing request
	e. Receive notification that an answer has been submitted
	f. Add support for answer if it resolves issue

Related User Stories
++++++++++++++++++++
None.

Requirements
++++++++++++
None.

External References
+++++++++++++++++++
None.

Rejected User Stories / Usage Scenarios
---------------------------------------
None.

Glossary
--------
None.