> On 28 Oct 2019, at 23:22, Nicolas Cellier > <[email protected]> wrote: > > +1 for improving the issues. > I call that the "checkbox attitude": > Opening an issue is mandatory for a change to be merged? > No problem, i open an issue (just a title), check the box, et voilà... >
It actually is not mandatory anymore… and we should encourage people to just do PRs without opening an issue. (as the issue is really not useful in this case and tends to be empty). > That's applying the letter of the law rather than the spirit of the law. > Either the law is bad (too cumbersome for trivial changes?), or we are at > degree zero of quality... > I also call that quality-dry: > It has the color of quality, the smell of quality, but it's not quality ;) > I have added the robot that complaints when people do not add a description. This seems to help a little, as it forces people to add some explanation. > > Le lun. 28 oct. 2019 à 23:12, Myroslava Romaniuk via Pharo-dev > <[email protected] <mailto:[email protected]>> a écrit : > Hi everyone > > Maybe it makes sense to generate some github issue templates and encourage > people to fill in the related information from a prompt? I think with bug > reports the situation is better, but for feature requests the state of things > could be very much improved by adding a template that goes: "describe > problem", "describe solution you'd like", "other alternatives", "additional > context". > > Because right now github issues are a mess. I get it that some projects have > particular maintainers and they know what the issues are and the phrasing > doesn't matter, ok, but a lot of the issues that don't have a tie to any > particular project and are labeled "easy" or "beginner" take a while to > understand because you have no idea what the person who created the issue > actually means. > > Just a suggestion, but i think there's really a lot of room to improve with > labels and templates for issues, and make them more accessible to outsiders. > > Best, > Myroslava
