Hi! I think one of the problems is that not everybody can set labels. I've created a lot of issues but the only thing I can do is to set the description and title, even if I already know if it's a bug or feature, or the Pharo version it affects. For ba-st projects we have a set of standardized labels (see for example https://github.com/ba-st/Stargate/labels) and using it in every project makes it easy to filter them.
AFAIR the permissions on GitHub are pretty crappy, so I think it's not possible to give permissions to external collaborators to change labels on issues without giving it write permissions over the repository. In any case having templates for bugs and feature issues sounds like a good idea. And I love the option to not have to open an issue if I will immediately provide a PR with code, because this avoids duplicating the discussion in two places. Best, Gabriel On Mon, Oct 28, 2019 at 7:13 PM Myroslava Romaniuk via Pharo-dev < pharo-dev@lists.pharo.org> wrote: > 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 >
