What is the meaning of a +1 review for submitted User Stories?
This depends on the 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 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 Team. 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?
How Product Working Group collaborate with OpenStack Project team?
Product Working Group has a list of Cross Project Liaisons (PWG CPL). When a user story is created it is assigned a User Story Owner (USO). A cross-project spec is proposed to the cross project repository by USO. This spec need to be approved by Technical Committee (TC). USO will work with PWG CPL and Cross Project Spec Liaisons (CPSL) to assign ownership to implementors in each project and track the implementation status.
For example, a user story is created and assigned an USO. This user story requires changes in Nova, Neutron and Glance. The PWG CPL of Nova, Neutron and Glance will work together with CPSL in their designated project to review a drafted Cross Project Spec. Once Cross Project Spec is approved and endorsed by TC, the PWG CPL collaborate with the owners of various work items and provide status update to USO via the Tracker as blueprint, project spec and bugs are identified.
Community-Generated OpenStack Roadmap
How is the community generated roadmap developed?
Generating the roadmap is indeed a community effort! The team usually consists of 8+ Product WG members who have volunteered to document the roadmap for 20+ OpenStack projects. The team has a list of questions (which is reviewed before each roadmap release) which is sent to the OpenStack Project Team Leads (PTLs) for the projects that will be covered by the roadmap. We ask the PTLs to provide us with an updated view of the upcoming release and to also give us some information on the potential direction for future releases. The list is sent via email but the PTLs can chose to answer the questions by email or we can also setup a quick conference call. The roadmap generally contains information for three releases: the upcoming release, the release that will be discussed at the next design summit, and the one after that. The timing for gathering this information usually coincides with Milestone-3 of the current release being developed. The team also does a refresh of the roadmap data for the next release after the design summit has concluded and this usually happens during Milestone-2 of the upcoming release.
There is also a roadmap sub-team page on the Product working group wiki with additional information.
Where can I find the community generated roadmap?
The roadmap can be found on the OpenStack roadmap page in the "Community Generated View" section.
Please add additional questions to this wiki page and the members of the Product Work Group will provide answers.