> On 29 Oct 2019, at 09:16, Serge Stinckwich <[email protected]> wrote:
>
> 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
> <https://github.com/PolyMathOrg/PolyMath/labels>
> with different status, priorities and types like describe here:
> https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b63
> <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).
>
for that the Kanban boards are nice:
https://github.com/orgs/pharo-project/projects
> More people are needed to the triage of issues and polish them for sure.
The problem is that GitHub only allows people with *write* access to the repo
to add labels… or add issues to “projects”.
They suggest to put the issue tracker into it’s own repo and give everyone
write access there:
https://help.github.com/en/github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository
Marcus
