2017-01-26 Roadmap Team Meeting

It was suggested for better attendance to meet in US morning times? Ask the group for the best meeting time suggestions.

• The rolling  upgrade  feature may be a good example to run through the PWG process
• Cross project sessions occur at the Forum
• There is a Logging user story (error codes) already under development that would be a good example for the LCOO  to  review and refine further

Difference between Summit and Forum: https://wiki.openstack.org/wiki/Forum

Discuss presentation ideas for Boston Summit: https://www.openstack.org/summit/boston-2017/call-for-presentations/

• What is value we bring the community?
• What messages do we want to convey?
• How are we positioning ourselves in relation to the OpenStack product working group? 

Deferred to the next meeting owing to low attendance in this meeting

• Working group session in Boston - need  to submit by 2/6

High level LCOO JIRA Demo

Discuss/Review LCOO JIRA usage options

Schedule side meeting to take a deeper dive into jira,training, administration, etc.

Discuss whether we should have individual boards for each company or a consolidated board for the LCOO

the Roadmap committee to nominate 2 more people to help out on JIRA administration

• JIRA is beneficial to manage cross projects
• JIRA has the ability to create themes, EPICs, stories, tasks etc.
• Roadblocks can be ascertained through comments input by Developers, e.g. waiting for +2
• JIRA may not be the right option in all instances, but is  beneficial for driving work together and exposing where members need assistance, e.g. need help with a review etc.

Discuss FST's (roadmap sub-teams)

Should we first try to outline a basic roadmap? or Should we jump into smaller FSTs and get multiple threads started in parallel?

Perhaps pick one "Story" and run it through the PWG Process

Development community needs highly detailed specs and blueprints which is an outcome of a user story discussion and a subsequent extensive Gaps analysis discussion.

This can be driven by collaboration with PWG as well. 

• A key question to be answered on user stories is who is the user story supporting and why should it  be implemented.