That sounds good to me, I went ahead and made a PR with a suggested structure for bug reports: https://github.com/apache/incubator-druid/pull/7105
Besides design proposals and bug reports, there are some other types of issues that I've seen, and I'm not sure if we should template them as well: - Feature requests: While these could be useful, my suspicion is that the vast majority of feature requests wouldn't get picked up by any dev and would be abandoned eventually. I don't think we should forbid them, but making a template feels like we would be encouraging people to submit feature requests that would most likely result in disappointment. - Questions on Druid behavior or operation: I feel like this type of issue is better handled on the mailing lists. On Mon, Feb 18, 2019 at 11:09 AM Gian Merlino <g...@apache.org> wrote: > Sounds good to me. IMO it also would make sense to remove the license > header from the templates, and add them as a rat exclusion if needed, and > also exclude them from release tarballs. The header is ugly and I don't > think there is a strong need to label these files if we don't plan to > include them in releases. > > On Sat, Feb 16, 2019 at 2:43 PM Roman Leventov <leven...@apache.org> > wrote: > > > The current interface of creating an issue in Druid draws a lot of > > attention to "Proposals": > > [image: image.png] > > I think we should at least create a "regular issue" template and make it > > go higher in this list of templates to restore the balance. > > >
