I also believe it is vital for operators/consumers of our software to provide such feedback. Team may not be aware of issues because of a different scale or pattern than what was originally expected. The only way we discover these sorts of things is to spread the word and try and collect as much information as possible. On Thu, Jul 15, 2021 at 8:09 AM Rico Lin <ricolin@ricolky.com> wrote:
Dear all As a proposal for pre-select goals for Yoga [1]. We need to figure out the possibility.
I would like to ask each project team, SIG, and pop-up if you can kindly provide the major pain point you have (and better to be fixable by bugs/features).
What you can help with is added in pain point information in [2]. Information like pain point topic, description, and ideas on how to targeting them.
Why this is important? I think this data allows us to see clearly if we can have goals like `eliminate pain points`.
What's after this? If we can make sure this can be a goal material, we might be able to have this as a goal and allow project teams to focus on one of their most important issues.
As an alternative, we might be able to collect from user side with a user survey, but that's more like a really long-term plan for this.
[1] https://etherpad.opendev.org/p/y-series-goals [2] https://etherpad.opendev.org/p/pain-point-elimination
Rico Lin OIF Board director, OpenStack TC, Multi-arch SIG chair, Heat PTL, Senior Software Engineer@EasyStack