GitHub Org - Unified Labels

[mmcky]

I would like to setup unified labels for ALL repositories.

This means setting up organization level labels and removing all "repo" level labels.

I will propose a QuantEcon set in the table below

Status Labels

Label	Colour	Description
in work		a PR can be open but in-work (alternatively you can use DRAFT)
ready		shows you are ready for a reviewer to be assigned to a PR
blocked		waiting on another PR
testing		shows it is for testing only and likely will not be merged
help wanted		for requesting help

Priority Labels

Label	Colour	Description
priority: high		an important PR that needs review within days
priority: low		an issue/PR that needs would be good to fix

Issue Types

Label	Colour	Description
good first issue		an indicator of an entry level issue
bug		something isn't working right
question		raising something for discussion relating to a lecture
wontfix		this issue will not be worked on and will be closed soon
dependency		indicating an issue needs to be fixed in a dependency (themes etc.)
maintenance		for changes to repo infrastructure

Skills needed for reviewer

Label	Colour	Description
skill: editor		for final stages where the editor is required for final review
skill: econ		for changes require domain specific economics expertise

Automation

Automation scripts may add their own labels but we don't have to maintain or select those (i.e. linkchecker)

The current organization level labels are

This will help with consistency across repos and unified colours and label titles for tagging PRs and Issues.

[jstac]

Thanks @mmcky , good call!

do we want an 'in-work' label that tells people not to merge?

[mmcky]

thanks @jstac

I am going to loop through our current repos to survey which ones we tend to use. I was then going to make a quick table above and then ping @jstac and @HumphreyYang for review and/or further suggestions.

I think in-work labels can be useful as then I know (as a maintainer) not to click into it for now, but I know work is happening on a specific issue.

[mmcky]

@jstac I have distilled a list of labels (updated the first cell block) by topic that I think could be useful.

I might drop a few more -- trying to focus on a set <= 12 so they remain relevant, clear and useful.

If you have any cycles - any comments most welcome. Otherwise I will run with it tomorrow and reset the labels across our lecture repositories (based on Organization level settings). Once that transfer is done -- it will be easy to maintain, add and remove.

[jstac]

Thanks @mmcky , looks good. I agree about keeping the list minimal.

[mmcky]

OK so I updated the GitHub Organization level labels but this doesn't sync to existing repositories unfortunantely.

I will need to make use of the script that has been written in #183 and programmatically update the labels on all lecture- repositories.