-
Notifications
You must be signed in to change notification settings - Fork 23
Usage of Github Labels
madbkr edited this page Sep 11, 2024
·
1 revision
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! How to participate
- Use Cases
- Best Practice Principles
- Structure of the OEO
-
Tutorials: How to...
- ...Get Involved (First Steps)
- ...Contribute
- ...Use Protégé to Change the Ontology
- ...Test the Ontology
- ...Write Competency Questions
- ...Choose a Class Type
- ...Deal with Ambiguous Terms
- ...Use Term Tracker Annotations
- ...Use the GitHub Labels
- ...Set up OwlViz for Visualisation
- ...Use Automation of Recurring Text Entries
- ...Manually Merge Terms from Other Ontologies 🤖
- ...Release a New Ontology Version
- ...Translate Into Turtle RDF
- Setup your Work Environment and Get Involved
- ...Maintain automated Workflows for GitHub Issues and PRs
- Get to Know the Workflow This sections will contain the full workflow in the future
- Tools and Utilities
- Community