# November workshop helper HackMD
###### tags: `workshop`
Dear Helper,

You have made it here, awesome!
Thank you for attending the helper onboarding session. Hope you will enjoy the workshop :)

This document: https://hackmd.io/@coderefinery/2020-nov-helper

## Helper onboarding agenda

Helper onboarding are held on 2 different dates. Both same topics, afterwards installation help sessions.

1. Short introduction round with HackMD icebreaker
2. Reviewing learners survey
3. Short overview on what will happen in workshop
- teams
- main session vs breakoutrooms
- HackMD and expert helpers
4. How to helper: https://coderefinery.github.io/manuals/helping-and-teaching/
- Code of conduct
- positive learning environment
- things to avoid
5. Helpers in breakoutrooms: https://coderefinery.github.io/manuals/breakout-rooms-helping/#helpers-in-breakout-rooms
- Helper as moderator and time keeper
- breakoutroom strategies
- common problems
6. Plan on exercises in breakout rooms
7. Open questions
8. Transition to installation help

__________

## Icebreaker
to add to the HackMD: write which other programming languages are you using (except the ones that were explicitly listed in the survey)

Why did you become a helper and what are you looking forward to?

- Example: Being a helper to motivate myself to learn more, looking forward to sharing my knowledge [name=Xyz]
- Helping/teaching other helps to understand things better. I learn something new myself and learn about new tools every time I attend a CR workshop. It is also a nice to be part of the CR community. [name=Diana]
- I like helping others understand tricky concepts, and I had a good experience helping in previous CodeRefinery workshops :) [name=Matthew]
- I love to learn and teach. I am looking forward to learning more as well as to improve my teaching through taking a closer look. [name=Annajiat]
- Radovan: learning something new at every workshop
- I am part of a Team for which I recommended this workshop. [name=Anthony]
- I enjoy going over the material covered by CodeRefinery (feels like a natural outgrowth of the Carpentries content I'm used to teaching), and it's a fun use of my time. I'm looking forward to interacting with the rest of the helpers, learners and instructors, it's a great community! [name=Rohit]
- It is fun and way to learn more [name=Pavlin]
- I like to help and contribute to the community + gaining helping&teaching experience [name=Raphaela]
- I think the material taught by CodeRefinery is very useful, and is taught in a very pedagogical way. I want to get more involved, both to keep learning, but also to share what I have learned so far. [name=Patric]
- Acting as helper for one team as asked by the colleagues. Practice and develop pedagogical skills. [name=Octavian]
- I like to contribute, and it's also good for your own development. [name=Ingrid]

## Links

https://coderefinery.github.io/manuals/helper-intro/
https://coderefinery.github.io/manuals/helping-and-teaching/
https://coderefinery.github.io/manuals/breakout-rooms-helping/#breakout-helpers

## Exercise plan
### Git intro (Day 1)
- [Record changes](https://coderefinery.github.io/git-intro/02-basics/#exercise-record-changes)
### Git intro (Day 2)
- [create and commit to branches](https://coderefinery.github.io/git-intro/06-branches/#exercise-create-and-commit-to-branches)
- [Type along. Create a conflict and try to resolve it. Try to repeat the same thing the instructor did](https://coderefinery.github.io/git-intro/08-conflicts/#type-along-create-a-conflict)
- [Basic archaeology commands](https://coderefinery.github.io/git-intro/10-
### Git collaborative (Day 3)
- [Centralized workflow (Try to accomplish steps 1-8, we will do 9 once we meet back together. If things don’t go perfectly for everyone, it is OK since we start anew in the next part.)](https://coderefinery.github.io/git-collaborative/02-centralized/#centralized-workflow-exercise)
- [Practice collaborative forking workflow, steps A-E](https://coderefinery.github.io/git-collaborative/03-distributed/#exercise-practice-collaborative-forking-workflow)
### Reproducible research (Day 4)
- In episode 4 we will to type-along using Binder: https://coderefinery.github.io/reproducible-research/04-workflow-management/#one-problem-solved-in-4-different-ways
- helpers need to be aware and ready to use binder for the exercise - try the first steps in the type-along section
- good to know that if a binder session is idle for a very long time it will stop working and users will have to re-create a new one.

### Social coding and open software (Day 4)
- None

### Jupyter (Day 5)

- Exercise 1: https://coderefinery.github.io/jupyter/03-basic-workflow/#calculating-pi-using-monte-carlo-methods
- Exercise 2: https://coderefinery.github.io/jupyter/06-sharing/#exercise-20-min-making-your-notebooks-reproducible-by-anyone-via-binder
- Optional exercises are bonus but most participants will probably not have time

### Documentation (Day 5)

- [Generate the basic documentation template](https://coderefinery.github.io/documentation/04-sphinx/#exercise-1-generate-the-basic-documentation-template)
- [Deploy Sphinx documentation to Read the Docs](https://coderefinery.github.io/documentation/05-rtd/#exercise-deploy-sphinx-documentation-to-read-the-docs)

### Automated testing (Day 6)
- [Pytest (run the test using pytest, then break it and test again)](https://coderefinery.github.io/testing/pytest/)
- [Exercise a full-cycle collaborative workflow (up to step 4, or as far as you get)](https://coderefinery.github.io/testing/gh-actions/)

### Modular coding (Day 6)
- No group exercise.

## Helper questions

You can ask helping related questions and concerns here or in the workshops hackMD. You can also share some questions you got, that would be good to be covered during the lesson in the future. Or if some more information/background is needed on some topics.

* Ex. Should I read all the lesson materials beforehand? [name=Xyz]
- No, you don't have to, but we will send the plan on exercises to do as well as advices from instructors when they are ready. It will be great if you could then take a look at them.

During the workshop we will be using the [CodeRefinery Zulipchat](https://coderefinery.zulipchat.com/) for backend communication. See the "november 2020 workshop chat" topic under workshop-chat stream - [direct link](https://coderefinery.zulipchat.com/#narrow/stream/259940-workshop-chat/topic/november.202020.20workshop.20chat)

## Feedback collection

Please give us also helper related feedback.

- Ex. Is it to be the place that I can write my feedback that I would like to share with only instructors and other helpers? [name=anonymous]
- Yes, we keep this open during the workshop and a few days after the workshop is over, so please let us hear your feedback!
- **Suggestion**: Lets try to find out the *Other* category people have opted for in programming languages! [name=Rohit]
- More concretely, maybe we could use favorite language as an icebreaker
- **Idea**
- have a virtual machine for the workshop?
- disadvantage: users will not learn to install the tools and be able to use them after the workshop
- question 1 +1+1+1+1
- answer 1
- followup question
- answer
- answer 2
- answer 3

- Regarding the Collaborative distributed version control lesson, I think it is helpful to have 2 GitHub accounts in order to test the exercise - just my impression. Do you use have more than one GitHub account? [name=Diana]

- In the [Jupyter installation instructions](https://coderefinery.github.io/installation/jupyter/), it may be helpful to have a link to Anaconda or Miniconda or some notes on how to install any of them.

- If there is a *long* exercise that needs to be done in a breakout room, it may be hard for the participant to follow or remember all the steps. It may be better if the teacher does not spend more than a couple of minutes to explain (or have a summary list of the steps that one will go through in the exercise) and one is redirected to the breakout room rather quickly, especially if one is running late. This way the helpers can explain which steps to do at the appropriate time.

___________
please write your question above this line