review issue labels (tags)

VladimirAlexiev commented 2 months ago

I labeled (tagged) all issues and discussions so now you can search eg like this:

There's also https://github.com/Sveino/Inst4CIM-KG/labels, a nice dashboard.
Please review tags.
- Add some more?
- Maybe we don't need the standard ones (have 0 in the dashboard above)
- Change some colors
Let's keep new issues tagged! We should periodically check is:open is:issue no:label and add tags where missing.
NEW When you read an issue, you often think of related but different things.
- Rather than adding a comment that increases the scope of the original issue, it's best to open a new issue and link it to the original one (eg #49 -> #55).
- It's better to have 100 "atomic" interlinked issues, rather than 50 tangled complicated issues. This allows us to reach conclusion and closure on individual issues faster.
- But if you don't have time to open a new issue, or the new thing is really close, then at least add a label to the original issue to indicate it's related to the new topic.
Since there are many issues, we need to worry about prioritization. After the discussion: when you want me to start working on something: assign it to me and tag it approved
If you like, add a section Working With Labels in the root README

griddigit-ci commented 2 months ago

Some ideas

AP (ApplicationProfile) - issues related to the profile description
serialisation - issues on serialisation - we may want to have json-ld as well
vocabulary - to cover RDFS stuff
constraints - to cover shacl stuff, but we can also have shacl instead
specification- when we need to also change some standard or specification rather than the e.g. serialisation bug in a RDFS export

VladimirAlexiev commented 2 months ago

@griddigit-ci answering your bullets in order, :

I added on top (end of description) some more guidance about labels, do you agree?

Sveino / Inst4CIM-KG