Maybe this is possible with people with enough privilege to edit the issues in order to provide more details ?
I try for the PolyMath project to have more elaborate labels: https://github.com/PolyMathOrg/PolyMath/labels with different status, priorities and types like describe here: https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b63 but you need people to tag correctly issues and labelling is more complex. And I guess for Pharo, you will have to use a label to know what is the area of the system impact (like Compiler or UI). More people are needed to the triage of issues and polish them for sure. Regards, On Mon, Oct 28, 2019 at 11:23 PM 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à... > > 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 ;) > > > Le lun. 28 oct. 2019 à 23:12, Myroslava Romaniuk via Pharo-dev < > [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 >> > -- Serge Stinckwic h Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) Sorbonne University (SU) French National Research Institute for Sustainable Development (IRD) U niversity of Yaoundé I, Cameroon "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich
