Open rootwork opened 2 years ago
I've been meaning to have a lighter-weight template. I think having a blank one is a good start... I put so much effort into the one template we have I am biased/attached to it, but it's healthier that we have less barriers to contribution, rather than just the one template I'm sentimental about.
We get a lot of suggestions where maybe we as maintainers would feel differently to the person who opened the issue, and it's maybe not clear why we should do it. I wanted to make it the most likely we could recover a common ground by explaining more of where the issue poster was coming from. At least that's the idea -- that's what the template I put together was meant to solve.
Several times I considered adding a blank one... This is the first major project I became a maintainer on, and everything I change feels a bit sentimental... But it's really for the best to have a much lighter (if not totally blank) template to choose.
Your specific proposals seem thoughtful on first skim. Worth looking into. Thanks!
Edit/Update: There is now the blank issue template.
Hi! So I am new to this repo obviously, and just proposed #666. I found the issue template a little...surprising in the way it was set up. I thought I'd just relate what I experienced and let maintainers decide if anything is worth changing.
For one source of references, I've used the https://github.com/dec0dOS/amazing-github-template project in my own projects and found it helpful. In particular it has separate templates for bugs, feature requests, and code improvements, which I've found very useful. In this case, perhaps a template for code improvements would have space for technical implementation, while templates for bug reports and feature requests could be a little more open-ended.
I hope I'm able to convey that I'm aware I'm new to this project and might not appreciate the systems you've set up and how they work for you. If these feel like unhelpful suggestions then please feel free to dismiss them -- the last thing I want to do is tell you how to run your own project. (That said, if you are open to changes, I can definitely do a PR, because I feel 1000% more confident in GitHub issue templates than most of the languages [except JS] you're using :smile: )
Thanks for the tireless work you've done over the years to make this project shine!