Create OSC standard operating procedure manual

[NeuroShepherd]

Potential topics to document:

• Criteria for members/fellows
• New research assistant onboarding
• New employee onboarding
• How to author tutorials from our tutorial template. Explain the underlying tech
• Explain the branding repo, and how to use it for e.g. presentations
• Important: documenting access procedures to our server, and what processes we have running there (A GitLab group runner, the Matomo analytics info, ...)
• ...

Private or public manual? Or mixed portions?

[MalikaIhle]

I think criteria for membership fellow should be explicit on the main OSC website https://www.osc.uni-muenchen.de/join/index.html and is an 'external facing' aspect. this manual should stay about our ways of working and an OSC staff or Hiwi I think. we don't expect anyone but us to read this manual so I'd remove the membership section.

We are currently gathering the content for

• New research assistant onboarding
• New employee onboarding
  e.g. admin, ways of communicating, where we work (google drive, LRZ sync and share, github, gitlab), and things for HiWi task 3 and 4 (how to organise an event from A to Z, how to use our social media, using all the tools we have, pretix, formR).

The current menu sections I'm seeing are:

• OSC STAFF ONBOARDING
• UPDATING FIONA OSC WEBSITE
• UPDATING QUARTO OSC WEBSITE (we don't ahve content for that yet)
• ORGANISE AN OSC EVENT
• OSC OUTREACH TASKS

ping @muchassgracia

[MalikaIhle]

I've now assigned Elizabeth to this part of the manual:

OSC STAFF ONBOARDING
ORGANISE AN OSC EVENT
OSC OUTREACH TASKS

@bethwater1

She will clone, create a branch, make merge request.