Replies: 3 comments 4 replies
-
I think it is a good idea to have such templates. It does not only (and not even necessarily) unify the way issues look like, but also gives important hints on which kind of information may be important. I would also propose to automatically assign labels to issues created with different templates, such as a destinction between "bug", "feature request" or "feature proposal". |
Beta Was this translation helpful? Give feedback.
-
I am more annoyed by templates. They often ask things that are either obvious, unrelated or unknown. |
Beta Was this translation helpful? Give feedback.
-
I also support the idea of such templates. They really help the contributor in telling the right things when they're not really aware of what matters to investigate the cause and it doesn't prevent people who feel comfortable enough to from ditching the template if they know a better way to describe their issue.
""" I suggest at this stage, someone can submit a PR to this repo in order to add some concrete issue templates and then we can refine them so they match the expectation of maintainers. |
Beta Was this translation helpful? Give feedback.
-
Many projects on github use github's feature to define issue templates
This may bring a few advantages like having Standardized issues and on average, a Higher quality of issues.
I therefore propose that we implement issue-templates accross our repositories, like SWT already does.
We could have the following issue-templates (subject for debate!)
Bug Report
Feature Proposal
Feature Request
...
Beta Was this translation helpful? Give feedback.
All reactions