open-telemetry
Document the project's roadmap change process
The Project appears to leverage the Discussions feature of GitHub to document Roadmap planning activities that occur in SIG meetings. The Project's Governance Committee charter details the GC as being responsible for ensuring the Roadmap is updated, but does not convey the process by which that occurs. While the project does maintain a project proposal process, this is not integrated into Roadmap development and maintenance efforts.
It is recommended the Governance Committee document the process by which they and the sub-components make changes or consider efforts to be prioritized and included within the Roadmap; connecting project proposal to roadmap inclusion.
xref: https://github.com/cncf/toc/issues/1739
Hi @TheFoxAtWork, this is something we've been focusing on over the last months, to formalise this process which is currently not consistently used across SIGs and projects. We're consolidating on approach based on the use of GitHub projects and GC/TC sponsorship and reviews, which we're documenting under https://github.com/open-telemetry/community/pull/2911
We will soon be able to provide a central, publicly available source of truth to view high-level, prioritised roadmap items, and a process to manage said items.
I will keep this issue updated with progress on this.
@TheFoxAtWork The roadmap doc has been merged, please review roadmap management doc in the root of this repo.
