or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing
xxxxxxxxxx
October workshop helper HackMD
Dear Helper,
you have made it here, awesome! 2 things we would like you to do here:
Helperlist
Please add yourself to the list below and add information on which call you are planning on attending: Friday, Oct 16, 09:00 - 10:00 CEST or Monday, Oct 19, 15:00 - 16:00 CEST (if you cannot attend any, please indicate with 'not available') and which of the workshop dates (20.,21,22,27,28,29.10 09:00 - 12:00 CEST) you cannot attend as helper. The first line serves as a guide of options
Helper questions
-> questions section moved to bottom of page for easier following :)
Helper introduction agenda
Helper introduction Friday, Oct 16, 09:00 - 10:00 CEST and Monday, Oct 19, 15:00 - 16:00 CEST (both same topics, afterwards installation help sessions)
Helper email draft
Hello helpers!
Dear {},
We're contacting you because you registered for the event Online CodeRefinery workshop Oct 20-22 and 27-29, 9:00 - 12:00 (Central European Time).
Thank you for being a CodeRefinery helper. In these times online courses are more popular than ever, and it is possible for more people to participate in our workshops. You all are what makes these huge courses possible. So thank you at this place already for being a helper! :)
As a helper, you are the first line of answering questions our learners have, and thus directly allow us to reach many more people than you normally could. You don't have to know everything, just have be able to provide advice and encouragement on basic issues, and know when to call someone else (which you can always do via hackmd, our collaborative document during the course).
There are some things we would like you to do in advance:
If you are on a team, try to make sure that the other teammates have software installed and configured in advance (and you, too). This is very important! In general, if you can, make sure that people can start off as smoothly as possible.
Visit our helper hackmd* ( https://hackmd.io/8bLEW1nySgqRglZvbwU_zw ) and
Come to one of the pre-workshop helper conference calls. They are:
Friday, Oct 16, 09:00 - 10:00 CEST
Monday, Oct 19, 15:00 - 16:00 CEST
If you can no longer be a helper, or there are other problems, reply to this message and let us know.
We've prepared some tips for helpers, which we'll go over in the helper call, but you can go ahead and read:
https://coderefinery.github.io/manuals/helper-intro/
If at any point you have questions, concerns, ideas or something else you would like us to know you can post in on our helper-hackmd : https://hackmd.io/8bLEW1nySgqRglZvbwU_zw
Best regards
Your CodeRefinery team
You registered as a "{}" (if on a team, the team is "{}").
You can view your registration details on this page:
{link}
Icebreaker
Why did you become a helper?
This is a very difficult question… I dunno, I like to help…? Gives meaning to life? :) (enrico, btw I have to leave at xx:30)
I am TA in a data science course that starts the 4th of November and this is code refinery workshop is part of the preparation for the students. Evelien
I am teaching a part and it is a good learning experience. Jens
I am in charge of a small team tasked with developing a new software library and as a team we could benefit from learning to use collaborative dev tools, so I reached out to CodeRefinery. Jakob
I want to learn how the Code Refinery worskhops are run. We are going to run Code Refinery Workshops at the Netherlands eScience Center. Mateusz
There will be a winter school for which I will be an assistant and we encouraged our participants to join this workshop as we will use a lot of tools that will be discussed here. Matthias
I enjoy supporting people in learning new (and important!) software skills. Barbara
Same reason as Richard :) I want to teach these things to my collegues, and it is more efficient to teach together. Jarno
Teaching at a personal level is the nicest thing ever. Johan
I have some knowledge in Git and python and I drew the shortest straw among my colleagues. Simoneta
I have experience with Git, and I enjoy sharing knowledge. Matthew
I'm interested in the Code Refinery material and how the workshops run Kees
Some of my colleagues are going to attend the workshop, and since I did it once I though it'd be nice to be a helper. It would also refresh my memory of things that I don't work with regularlyIngrid
teaching is the best way of learning Susan
I'm a Carpentries instructor and getting involved in coderefinery seems a good way to step up my game. Is a great way to acquire teaching skills Raúl
As an RSE I am involved in supporting researchers, being a helper is good training for this. Maurits
Interested in helping people to improve their software development skills and implement FAIR software through a collaborative workshop like this, while also learning myself. I enjoy teaching and believe it is the best way to learn. Niket
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
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.
git config --global core.editor "atom --wait"
according to https://stackoverflow.com/a/31389989-> Samantha done
Feedback collection
Please give us also helper related feedback.
We are interested in eg
did you feel well prepared for the workshop (if not let us know what we should cover more in the preparation meeting)?,
how did it go in your breakoutroom (was it very active/quiet/friendly/one person asking a lot/everyone discussing/etc)?,
most common questions,
anything you did not like?,
anything you did like a lot?,
tipps for future helpers?,
anecdotes from the breakoutrooms?
This section will be open the whole workshop duration. So feel free to add and edit whenever you have time :)
please write your question above this line