-
Notifications
You must be signed in to change notification settings - Fork 20
Usage of github labels
Simon Flügel edited this page Aug 4, 2021
·
3 revisions
The OEO uses different github labels to structure and annotate their issues.
If your issue is about the organisation of the project/ repository add label "organisation". If your issue is about the ontology itself add at least one of the following categories:
- issue type: "[A] new term", "[B] restructure", "[C] definition update"
- concerned module: "oeo-model", "oeo-physical", "oeo-social", "oeo-shared"
Other issues to add if appropriate:
- concerned topic: Energy carriers and fuels, external ontology, geographic
- bug
- ready for implementation
- specification_sheet: Projektorganisation
- SzenarienDB: not only the ontology, more general issues
- Time-L. Urgency-S
- enhancement
- good first issue
- question
- wontfix
You already know what to do? Perfect, make sure that you miss no step by using checklists
Symbols used in this wiki:
🐙➔ github | 🔶➔ git | 📙➔ protégé | 📝➔ text editor | 🤖➔ robot
-
Home
- Welcome!
- Use Cases
- Best Practice Principles
- Structure of the OEO
- Setup your work environment and get involved
-
Get to know the workflow
This sections will contain the full workflow in the future -
Tutorials: How to...
- use Protégé to change the ontology
- test the ontology
- write competency questions
- choose a class type
- deal with ambiguous terms
- use term tracker items
- use the GitHub labels
- set up OwlViz for visualisation
- Automation of recurring text entries
- Manually merging terms from other ontologies 🤖
- release a new ontology version
-
Tools and Utilities
- GitHub
- ROBOT
- Workflow & Checklist
- Community