Add wiki entry "how to add a new contributer (first steps)"

[stap-m]

Description of the issue

Adding oneself as contributor to the OEO is often one of the first GitHub steps new oeo developers take and should be documented in the wiki.

Ideas of solution

Include description as subsection in the wiki article on how to participate.

Workflow checklist

• I am aware of the workflow for this repository

[markus-rothkoetter]

I'm currently in the process of trying to add myself.
So, I'll note down the exact steps and can provide a proposal for a wiki entry afterwards.

I think the cloning step discussed in #1096 has to be part of the guide.
(#1096 (comment))

Shall each new contributor create an issue in order to obtain a "feature number" for the branch they're creating to add themselves? (Otherwise the branch won't adhere the naming convention)
How shall contributors name their branch otherwise?

[l-emele]

Often, the addition of a new user is together with implementing something. Only if a user is added without implementing at the same time, the problem you described arises. I see two possible solutions:

• Either create an issue and branch containing the issue number
• Or create a branch without issue number. Something like feature-new-user-[username]

[stap-m]

See also #1096 (comment)

[markus-rothkoetter]

* Either create an issue and branch containing the issue number

* Or create a branch without issue number. Something like `feature-new-user-[username]`

I'd opt for the later, as ...

• it's adhering to the standard convention (less things to think about for newbies like me)
• allows to "allocate" a user-id in case of simultaneous joins. (like it was happening with now)
• one can set-up the working environment fully prior starting to work

[markus-rothkoetter]

This is my rough outline of the steps needed to add oneself as a contributor:

1. Get added to the organisation by one of the maintainers
   (like noted in Add new user #1096)
2. Clone the ontology
3. Check for the next available user-id, check:

• open issues
• pending pull-requests
• oeo.omn file at dc:contributor

4. create issue Add new contributor/user 0000
5. create new branch from dev named according to Git-convention
6. Open either ...

• ... Protégé or

• ... texteditor editing the oeo.omn

7. Add yourself as a contributor with the annotation pattern:
   0000 FirstName LastName (@GitHub-username)
8. Commit change
9. Push your change
10. Create a pull-request

You obtained a contributor/user-id now, but still have to adjust your Protege settings to numerical identifers (linking to other guide)

Concerning step 1 shall there be a default team-member to adress?

Did I miss anything important?
If not, I'm going to compose a wiki-entry.

[markus-rothkoetter]

After having added this to the wiki, I'll close this.
For further comments refer to #1106