-
Notifications
You must be signed in to change notification settings - Fork 23
Add Yourself as a Contributor
This page describes ...
- how get access rights to the repository
- how add yourself as contributor to the ontology
This is necessary for the numerical identifers used in the ontology.
Please note: The following steps are designed not only to add yourself as a contributor but in same time represent your very first material contribution to the ontology itself. Going through the process and finishing it successfully ensures you, that you can contribute to the OEO in a proper way.
This workflow is ... | |
---|---|
... predecessor of | numerical-identifer set-up |
Note: Before starting the workflow below, please take a close look at the OEA ontology course and introduce yourself in an oeo-dev meeting.
-
🐙 Become a member of the GitHub-Teams
- Use the OEP - Contact Form to request access. Please name your GitHub Handle and the corresponding team(s) you want to be part of.
- If you are already a member of the Open Energy Family Organisation, directly contact one of the members of the @oeo-community-manager.
By being added you gain the access permission needed to work on this repository.
You have to accept the invitation first! Otherwise the next steps will partially not work. -
🔶 Clone the ontology to your local machine
-
Check for next available user-id via ...
- 🐙: Look for open issues concerning adding new users
AND - 🐙: Look for open pull-requests concerning adding new users
AND- 📙: Open the
oeo.omn
-file and look in the "Active ontology tab" for the latestdc:contributor
-annotation
OR - 📝: Open the
oeo.omn
-file and search for the latestdc:contributor
-annotation
- 📙: Open the
- 🐙: Look for open issues concerning adding new users
-
🐙 Create an issue for your user-id
Name the issueAdd new contributor/user
and append the next available user-id (latest entry + 1) as a four-digit number -
🔶 Create branch named
feature-YourIssueNumber-add-new-contributor
from dev
Use either ...-
GitHub-Desktop
or - the command line via
git checkout -b feature-YourIssueNumber-add-new-contributor
Quick-Tip 🔎: The naming is consitent with our Git-convention 🏷TODO/ADD_LINK
-
GitHub-Desktop
-
📙 or 📝 Add yourself as a contributor in the ontology
- Create a
dc:contributor
-annotation in theoeo.omn
-file according to the following pattern:
0000 FirstName LastName (@GitHub-username)
(0000
is to be replaced by your new user-id!) - Add yourself in CITATION.cff using a text editor.
- Create a
-
🔶 Stage, commit and push the new changes (you don't need to add a term-tracker this time)
Use either ...-
GitHub-Desktop
or - the command line via
git push --set-upstream origin feature-YourIssueNumber-add-new-contributor
-
GitHub-Desktop
-
🐙 Create a pull-request and wait for acceptance
-
🐙 After being accepted, merge pull request
-
🐙 Delete branch
-
You obtained your contributor-id, adjust the numerical identifiers now
Follow the next guide to adjust your Protege settings to numerical identifiers.
This page is based on #1094
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