During the Board+TC+UC strategy workshop we decided to work on how we can have the greatest impact on addressing unanswered requirements. Our goal was to have a session at the Boston Forum at a minimum around this. We had a number of notes up on the board divided up primarily into four categories:
1. How to Prioritize
2. Solution Focus
3. Scale
4. Feature List
How to Prioritize
Here there were a number of suggestions for capturing requirements and how such requirements would become prioritized. We had ideas from a open voting system to encouraging the users to become contributors and work on their needs.
Solution Focus
Here we had notes that addressed the core of OpenStack with a stable and reliable API that keeps compatibility between versions, to adjacent technologies and solutions with multi-cloud interoperability, the vertical industries and IOT/AI/Machine Learning, and building up our App Ecosystem.
Scale
Scale speaks for itself and really needs no direct discussion around its importance but maybe more about how do we actually concern ourselves with the needs of large scale environments; 500, 1000, 10,000 nodes.
Feature List
Essentially this appears to have come down to either focus on core refactor or along the lines of diving into the world of lambda/serverless support and OpenStack control of edge-based nodes/services, etc. Effort to refactor code so that it better supports adjacent technologies makes a lot of sense and I think it warrants discussion potentially about how a focus on this affects unanswered requirements and how we communicate this consistently at a minimum.
This session aims to bring all stakeholders together to determine our strategy and plan to implement our strategy.
