With forms, we can also maintain consistency across issues, enforce mandatory fields, and allow users to provide logs as a simple copy-paste operation with formatting automatically applied by the respective form. I believe this will simplify the process for new contributors and ensure they provide all the necessary information.
It's just a simple proposal, so I'm also open to any suggestions you have, especially on defining the required fields. In general, I think this will enhance the overall contributor experience and streamline issue management for maintainers. Templates proposed here are based on the ones from otel-rust and otel-js.
This PR proposes to transition otel-python issue templates to GitHub's issue forms feature.
I noticed other otel projects are adopting this model, including opentelemetry-js, opentelemetry-rust, opentelemetry-dotnet, otel-operator, otel-collector-contrib.
With forms, we can also maintain consistency across issues, enforce mandatory fields, and allow users to provide logs as a simple copy-paste operation with formatting automatically applied by the respective form. I believe this will simplify the process for new contributors and ensure they provide all the necessary information.
It's just a simple proposal, so I'm also open to any suggestions you have, especially on defining the required fields. In general, I think this will enhance the overall contributor experience and streamline issue management for maintainers. Templates proposed here are based on the ones from otel-rust and otel-js.
This is what it looks like if anyone wants to try