You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is to discuss some ways we can create a follow-up loop with Maintainers after survey results have been presented to the corresponding SIG, so that we can demonstrate that feedback is being/has been/will be acted on.
cc @open-telemetry/governance-committee
The text was updated successfully, but these errors were encountered:
Ideally part of the presentation to the corresponding SIG leads to the creation if issues. The End User SIG can take the list of these issues and create an issue in this repo to track their completion. 3,6,9 months later they can review them and report outcome. Best case for me would be the following
Survey -> Survey results are presented to maintainers -> maintainers take note and create issues -> issues get listed by the end user SIG -> survey results + the list of issues are published (in a blog post) -> time passes (3-6 months) -> End User SIG reviews the issues and follows up with the SIG if needed -> time passes (3-6 months) -> End User SIG writes another blog post where accomplishments are highlighted
This is to discuss some ways we can create a follow-up loop with Maintainers after survey results have been presented to the corresponding SIG, so that we can demonstrate that feedback is being/has been/will be acted on.
cc @open-telemetry/governance-committee
The text was updated successfully, but these errors were encountered: