search

wert007 / commit-analyzer

Gets the time somebody worked on something from `git log`
MIT License
1 stars 1 forks source link

[Enhancement] Create Issue Templates (#1) #32

Closed kevinmatthes closed 2 years ago

kevinmatthes commented 2 years ago

I think issue templates would help to keep a better overview about the things an issue is about.

wert007 commented 2 years ago

I feel like this would hinder people more from actually opening an issue. It makes it a lot more work involved, then it currently is. So I think I oppose this in general for this repo. 😅

kevinmatthes commented 2 years ago

In my opinion, it is easier to inform the maintainers about a bug if you know how they would like to be notified. This is why I created this initial form-like structure for the Bug Report. But this is just a draft for further discussion, so there is no problem to remove the obsolete sections from it -- or the complete form structure, if you disagree with it.

This was an idea on how to agree on contribution guidelines for bug reports, see #11 for further discussions. When categorising the types of an issue, one will be able to articulate the issue's subject more clearly since the main requirements are already set. And after all, you can still choose to use the default issue which has nothing predefined.

wert007 commented 2 years ago

Hmm, idk, I think it is easier, and also less formal, to just talk about bugs without any forms at all. There is nothing wrong with talking to people basically 😄

kevinmatthes commented 2 years ago

How about headlines in the Bug Report template to give an idea about which information are required to work on the issues effectively?

kevinmatthes commented 2 years ago

Indeed, the overhead of both issue templates and forms would be too much for the current size of the project.