2017-01-26 Roadmap Meeting notes

Date

26 Jan 2017 at UTC 500: http://bit.ly/2jZ6Qbg

Meeting Link: https://join.att.com/meet/au3678/ZP7B80FR

Meeting number (access code): 598 054 473
+1-210-795-1110 US Toll
+1-866-662-9987 US Toll Free
Global call-in numbers: https://intel.webex.com/intel/globalcallin.php?serviceType=MC&ED=517226197&tollFree=1

Attendees

Goals

Discussion items

Time	Item	Who	Notes
10	Recap of the meeting with Carol Bennet	All	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
10	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?	Jamey	Deferred to the next meeting owing to low attendance in this meeting Working group session in Boston - need to submit by 2/6
10	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	Andy	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.
10	Discuss meetings for Intel to share OSIC Roadmap objectives in depth broken down by functional areas		link: https://osic.org/roadmap
10	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	Aditya	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.
10	Mention the JIRA focused side meeting later in the day: 2017-01-26 Roadmap Logistics Meeting notes
10	Discuss how/when to follow-up on the /wiki/spaces/LCOO/pages/6193156

Action items

Yih Leong Sun (Deactivated)Leong to contact Sundar and ask that we defer osic roadmap meetings until after we can discuss at next lcoo meeting
Andy Ukasickto create JIRA projects
Jamey McCabe Add an FST discussion to the next LCOO Agenda
Andy Ukasick to send out next meeting invitation
the Roadmap committee to nominate 2 more people to help out on JIRA administration