---
# System prepended metadata

title: Open WIN Ambassadors

---

# Open WIN Ambassadors
## Agenda and collaborative notes (wk2): GitLab

-----

**Important information**

- Date/time: Wednesday 10th November 2021, 09:30-11:00 (UTC)
- Join the call: Start on MS Teams then move to [Wonder](https://www.wonder.me/r?id=0caf9983-991a-4d20-9900-e3a359953a49) (use Chrome or Firefox)
- These notes: [https://hackmd.io/@FE_yEojCQPW4PD8RcTWR0A/Sy_dAU_vF](https://hackmd.io/@FE_yEojCQPW4PD8RcTWR0A/Sy_dAU_vF)
- Discussion: Please join the [Open WIN Slack](https://join.slack.com/t/openwin/signup) Channel #ambassadors-2021 or email cassandra.gouldvanpraag@psych.ox.ac.uk 


<mark>Yellow = action</mark>


-----

## Agenda
0. Participation guidelines and check-in
1. Wonder orientation
2. GitLab - Understanding our current skill base
3. Exercises
4. Feedback

## Participants
(name / Pronouns / Department / git handles (GitLab;GitHub) / ORCID ID)
<mark>(delete anyone absent)</mark>
1. Cassandra Gould van Praag / she/her / Psychiatry / @cassag;@cassgvp / 0000-0002-8584-4637
2. Dejan Draschkow / he/him / [Experimental Psychology](https://www.psy.ox.ac.uk/team/dejan-draschkow) / [@DejanDraschkow](https://github.com/DejanDraschkow) / [0000-0003-1354-4835](https://orcid.org/0000-0003-1354-4835)
3. Yingshi Feng / she/her / NDCN / [@yingshif](https://github.com/yingshif) / [0000-0001-9065-4945](https://orcid.org/0000-0001-9065-4945)
4. Bernd Taschler / he/him / NDCN-FMRIB / [@btaschler](https://github.com/btaschler) / 0000-0001-6574-4789
5. Verena Sarrazin/ she/her / Psychiatry / [@verenasarrazin](https://github.com/verenasarrazin) / 0000-0002-5796-5378
 
## Participation guidelines
- We value the participation of every member of our community and want to ensure that each of us has an enjoyable and fulfilling experience. Please show respect and courtesy to other community members at all times.
- We are dedicated to a harassment-free experience for everyone, regardless of gender, gender identity and expression, sexual orientation, disability, neurodiversity, physical appearance, body size, race, age, religion, politics or technology choices. We do not tolerate harassment by and/or of members of our community in any form.
- We welcome, support and respect eachother as whole people.
- We fall under the formal policy and reporting guidelines of the University of Oxford Bullying and Harassment Policy and we expect everyone to be a responsible bystander.

## Check in
How are you, right now, in this moment?

Cass to remember: Feedback from last week was a request for backgroupnd of Open WIN - great idea, thank you for requesting! Clare Mackay will give a presentatiopn on this on 17th November after tools demos (10:30)

-----

## 1. Wonder orientation
We'll use Wonder this week so we can flexibly make breakouts to work together. 

Come over to Wonder and lets check everyone can:
- Move around (click and hold) and create circles
- Zoom
- Chat (private, circle, everyone)
- Broadcast
- Rooms
- Agree a protocol for when things break! Message on slack or Teams?

## 2. GitLab - Understanding our current skill base
We'll start by establishing who has what level of experience, so we can taylor the training to our individual needs.

<mark>Please fill in the table below to indicate your current comfort level with the tools we'll use for working with GitLab.</mark>

0 = never heard of

1 = heard of but never used

2 = used a little (still uncomfortable)

3 = used a fair amount (mostly comfortable)

4 = used a lot (very comfortable)

| tool                    | bernd | cass | dejan | georgina | verena | yingshi |
|-------------------------|-------|------|-------|----------|--------|---------|
| command line            |   3   |   3  |   3   |          |    2   |    2    |
| mark down               |   4   |   4  |   3   |          |    2   |    0    |
| text editor (e.g. atom) |   3   |   3  |   4   |          |    2   |    3    |
| github                  |   3   |   3  |   3   |          |    3   |    1    |
| gitlab                  |   2   |   3  |   2   |          |    1   |    1    |
| issues                  |   3   |   3  |   2   |          |    0   |    0    |
| pull/merge request      |   2   |   2  |   2   |          |    2   |    0    |
| branches                |   3   |   2  |   2   |          |    2   |    0    |

Text editors we use:
- Atom +2
- Emacs
- Pycharm
- Qt Creator
- RStudio +2
- Jupyter Notebook

Other comments/notes:


## 3. Exercises

We can go through a few different exercises based on our current skill sets.

- Mostly 0-1s => Cass will give a full "OMG what is all this" tutorial
- Mostly 3-4s => Jump into the [issues on Open WIN Community pages](https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues) and have a go at those tagged "Ambassadors". 
- Mostly 2s => Chose which of the above groups to join.

What happened: Everyone wants to do the training!
- No-one had all 4
- Insecurity of not knowing what is ahead of us (as amabassadors), so trying to avoid missing smth important
- Wanting to see how other people teach

### Full tutorial
Learning outcomes:
1. Understand why we are using GitLab for the Open WIN community and our documentation. 
2. Learn the main terminology used when working with git
3. Learn how to use the gitlab web interface to fork someone elses repository and make changes to it. 

Slides: [https://git.fmrib.ox.ac.uk/open-science/community/open-win-ambassadors/-/blob/master/slides/wk2-gitlab.pptx](https://git.fmrib.ox.ac.uk/open-science/community/open-win-ambassadors/-/blob/master/slides/wk2-gitlab.pptx)


#### Homework
For this session we have worked with gitlab in the online editor. You will later find it is more effective and efficient to work with local versions of a project using a text editor and command line. 

<mark>Complete the below activties to practice working on a local git repo using command line</mark>

1. [Practice using the command line](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/1-1-tools-command-line/)
2. Set up your computer to use git ([check that this is already installed](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git))
3. [Set up a text editor (I like atom)](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/1-3-tools-atom/)
4. [Configure your gitlab access](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/2-1-starting-gitlab-account/)
5. Pull a local version of your repo
6. [Edit your repo and push changes](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/2-4-starting-git-basics/)

<mark>We need to think of some homework for mostly3/4 folk! Maybe supporting the others?</mark>


## 4. Feedback on this session

#### A few git/github/gitlab resources
- very nice interactive tutorial using a command line interface and visual representation of changes (basic and advanced topics): https://learngitbranching.js.org/ 
- short overview of main git commands: http://rogerdudler.github.io/git-guide/
- gitlab cheatsheet: https://about.gitlab.com/images/press/git-cheat-sheet.pdf
- extensive documentation of gitlab: https://docs.gitlab.com/ee/gitlab-basics/start-using-git.html
- extensive tutorial and documentation of how to integrate git and R: https://happygitwithr.com/ 

<br>

<mark>Please add a few words to each of the sections below so we can improve the experience of others.</mark>
### What worked well?
- Going through the terminology of GitLab.
- getting everyone on the same page (I think that's especially useful for collaborative software tools)
- Wonder is fun
### What surprised you?
- I could publish my own page under open.win.ox.ac.uk domain.
### What would you change?
- 
### What would you like to know more about?
- Page building; build my own site as pretty as the open win community site.
- best way of solving merge conflicts

