What is the meaning of a +1 review for submitted User Stories?
This depends on the ProductTeam/User_Stories stage of the user story. If the User Story is in Draft status then a +1 review denotes agreement that the User Story conforms to the template requirements. If the story is in Proposed or Tracked status then the +1 review denotes agreement to the usefulness and priority of the use case as well as meeting the template requirements.
How to get involved with OpenStack Product Working Group?
All are welcome so please join, even if to just make a connection to other Product Managers working with OpenStack. The easiest way to get involved is to join [our mailing list], one of our [IRC meetings], or an upcoming Sprints/ProductMitakaSprint meeting. Feel free to reach out to one of the [core reviewers] for individual advice on how to plug in.
How to contribute a user story?
Great question! One of the primary ways you can contribute to the OpenStack and the Product Work group is to provide use cases (existing or aspirational) for OpenStack. These use cases are stored in the [OpenStack User Story Repository] and can be viewed in HTML format on the [OpenStack Specs] page.
Because stories are treated in the same way as code, they are managed by the standard OpenStack code management services, Github and Gerrit. I'd recommend using the exceptional [first times documentation] provided by the OpenStack Documentation. Just remember to use the openstack-user-stories Github repository. It is admittedly tricky so feel free to reach out to any of the Product Working Group [Core Reviewers] for assistance.
Is there a template for writing a user story?
Please add additional questions to this wiki page and the members of the Product Work Group will provide answers.