#7805 bug: Guidelines on filing issues is sparse and hard to find Issue created by BraedonLeonard While the handbook goes over things like

kind

and

valuestream

labels, it does not really lay out the process of filing an issue. There are 2 templates on Github, but they do not encompass all of the different kinds of issues that can be created. I've also noticed that most issues use the

<kind>: <desc>

syntax, but I haven't been able to find any documentation stating that issues should use this syntax, I've only seen it for PRs. The contributing guidelines are linked when creating an issue, but they do not contain any link to documentation related to filing issues. They just link to resources around the PR process, creating plugins, etc. Given that they are linked from the issue creating page on github, they should probably contain documentation around creating a new issue. It is also unclear how certain documentation-related issues should be filed. The Kind Labels section mentions in its FAQ that documentation issues "will most likely be considered a Bug", but this leaves a grey area for documentation issues that are not strictly about incorrect or blatantly missing documentation. For example, a request to expand upon a section in a walkthrough to give more context, or a request for a UX change. The docs should have a little more clarity around this. meltano/meltano