• Let's have an aspirational roadmap to support prioritization and how to get it funded.
• What is in the roadmap?
• Process of how we get to agreement

• Reviewing OpenNebula roadmap process - ticket based system based on demand.  Priorities based on who the submitter is/what their role
• Does not have a "high-level / conceptual road map" that would be useful for donors/investors 
• Reviewing OpenStack - meeting twice a year in person to develop PDF which scopes out release.   Much more of an open-person / dialog based development.
• On the call, was interest in a hybrid approach.
• What would work for our community:
  • in-person is challenging because of funding for travel
  • OpenNebula process may be challening because there isn't a lot of current engagement wth the ticketing system
  • So far, only verbal input for feature request
• Carl: What could the hybrid approach look like?
  • Perhaps a virtual community process of pooling in the features.
  • Smaller meeting to do the synthesis work and prioritization. Perhaps leverage travel to a conference or another venue.
  • Need to document the expectations of the stakeholders

potential TOR/expectations for product committee to support development of aspirational roadmap (may need to clarify with examples)

Product Committee

• Review and consolidate user stories from user and implementor communities
  • user stories / features coming from issue tracker submissions as well as synthesized by implementing organizations as they work with users 
  • how can we ensure user community members can directly submit feature requests to the product committee?
  • how do we ensure accountability of implementing organizations to provide feedback ?via tickets? and actively engage in the development of the roadmap?
  • who defines/approves the high level roadmap? who is the product owner?   
  • should we use issues/tickets to track feature reqeusts?  who curates/synthesize?
• Resource estimation (LOE for features)
• Prioritization of user requirements (decide and confirm what goes into the release)
• Prepare the feature roadmap for approval by governance committee

Release Sub-committee 

• manage the release cycle
• can be aligned with an in-person meeting