Use labels to identify context about standards-positions HOT 6 CLOSED

Just a thought: We could also apply the labels for all the positions ... then we might not need the python script. We can get the position for things using the Github API, instead.

from standards-positions.

There was a long discussion about the use of labels for tracking positions. We ended up here. Having a solid artefact that records conclusions has the benefit of having a nice blame. (The script is really just enforcing consistent formatting and making contributions easier.)

from standards-positions.

Why can't @marcoscaceres and I create labels and apply them? That seems rather restrictive and unnecessary.

It might also be good to distinguish "new work" from "new feature" as the latter need a somewhat more expedient resolution.

from standards-positions.

I was only saying that you can't currently create labels. Giving write access for a small group of people so that they can manage labels is a solution.

I don't know about labeling schemes for scope of work. It might pay to spend a little time learning what granularity works best before committing to labels (every layer adds overhead).

from standards-positions.

I made labels for the various standards orgs, as well as a policy label for issues about how we run/operate this repository, and started using the bug label for bugs in the python code. Probably more to do here, though.

from standards-positions.

If folks need more labels, I'd be happy to add them, just let me know.

from standards-positions.