The previous template had multiple sections at the top heading level which filled the rendered specs page with sub-sections. This change leaves only one main heading and reformats other sections with section and sub-section headings. This change includes fixes to the template and all merged user stories. Change-Id: Ib1fb08b1e67896a6f160b1b1649fadfc29b947e6
2.1 KiB
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.
Use Cases
User Stories
As an 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 usersAs an Operator, 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 an Operator, 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
Usage Scenarios Examples
- Common Question Usage - OpenStack Operator
-
- Go to common question repository
- Search for error code, topic, api call, etc
- Find most popular answer to common question
- Add support for popular answer if it resolves issue
- UnCommon Question Usage - OpenStack Operator
-
- Go to common question repository
- Search for error code, topic, api call, etc
- Discover no answers have been provided
- Create new request, or add support for existing request
- Receive notification that an answer has been submitted
- 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.