motivation: in order to fix bugs in the community libraries, we need "high quality issues" that allow maintainers to identify potential bugs quickly.
l propose to make the default bug report template more strict in the sense that we should make it clear that we require minimal runnable reproductions in the form of code snippets that can be copy-pasted and run, or links to repos with minimal repro (or snack - but how is it with native modules?). Reason is I'm seeing a lot of issues where people don't make enough effort to describe their problem and how to reproduce it. Such "low quality" issues then stall and I'd prefer to close them on the grounds of not following the template.
Many community repos have their own bug template which won't be affected
Summary
motivation: in order to fix bugs in the community libraries, we need "high quality issues" that allow maintainers to identify potential bugs quickly.
l propose to make the default bug report template more strict in the sense that we should make it clear that we require minimal runnable reproductions in the form of code snippets that can be copy-pasted and run, or links to repos with minimal repro (or snack - but how is it with native modules?). Reason is I'm seeing a lot of issues where people don't make enough effort to describe their problem and how to reproduce it. Such "low quality" issues then stall and I'd prefer to close them on the grounds of not following the template.
Many community repos have their own bug template which won't be affected
opinions?