Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New end-of-workshop message #125

Merged
merged 1 commit into from
Mar 14, 2016
Merged

New end-of-workshop message #125

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 20 additions & 14 deletions messages/training-checkout.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,17 +6,31 @@ Thanks again for taking part in Software Carpentry (SWC) and Data Carpentry (DC)

- If you want to teach SWC, you need to demonstrate that you've mastered one of its core lessons. Similarly, if you want to teach DC, you need to show you've mastered one of its. (This is Steps 2 and 3 below, which you do separately for each Carpentry.)

The steps are therefore:
The steps are:

1. Submit a small improvement to one of our lessons. If you want to become a SWC instructor, or to teach both SWC and DC, you must do this as a GitHub pull request; if you want to become a DC instructor only, go to http://www.datacarpentry.org/instructor-checkout-exercises/, which will redirect you to a Google Doc - please append your addition to the bottom of the doc to make it easier to find. Either way, please mail me once your submission is in so I can get it reviewed. You only have to submit *one* change to move on to the next step, not one per Carpentry, and we strongly prefer contributions to Data Carpentry right now (since their lessons are much younger).
1. Submit an exercise or diagram for one of our lessons. If you want to become a SWC instructor, or to teach both SWC and DC, you must do this as a GitHub pull request; if you want to become a DC instructor only, go to http://www.datacarpentry.org/instructor-checkout-exercises/, which will redirect you to a Google Doc - please append your addition to the bottom of the doc to make it easier to find. Either way, please mail me once your submission is in so I can get it reviewed. You only have to submit *one* change to move on to the next step, not one per Carpentry.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At some point there should be a dedicated instructor training email so that we can retrieve these emails when a given trainer is for any reason unavailable.


2. If you want to teach DC, pick one of its lessons (possibly the one you chose for step 1, but not necessarily) and sign up on http://pad.software-carpentry.org/lesson-discussion-2016 to take part in an hour-long discussion session about it. Similarly, if you want to teach SWC, pick one of its lessons and sign up for a discussion session about it (same Etherpad). If there aren't upcoming slots on the Etherpad that work for you, please add yourself to the top and we'll set something up. You must do this step separately for each Carpentry, and you're expected to read through the lesson(s) carefully *before* your session and show up with questions. If the session moderator (an experienced instructor) feels you haven't done this, you'll be invited to come back to a future session.
We strongly prefer contributions to the Data Carpentry lessons right now (since their material is much younger), or to our fledgling "Python for complete novices" lesson. You can find links to the Data Carpentry lessons on http://www.datacarpentry.org/lessons/, and the Python lesson on https://github.com/swcarpentry/python-novice-gapminder. Whatever you contribute to, and however you do it (by pull request or by adding to the Google Doc), please:

3. Once you're through the discussion session(s), sign up for a 5-minute online demonstration lesson slot on http://pad.software-carpentry.org/teaching-demos (or add yourself to the top of the pad if none of the available slots works for you). In that, we will ask you to teach a short segment from your chosen lesson - we'll pick the starting point on the day, so you will need to be familiar with the whole lesson. If that goes well, we will send you your certificate, add you to our roster, and get you on the dance floor.
a) Look at how the existing exercises in that lesson are formatted, and format yours in the same way.

Your change can be a fix to the existing material, a new exercise, or a diagram of some kind (preferably in a vector format like SVG, but we'll take anything). We are *not* presently accepting material with new concepts: the lessons are full to bursting as it is, and our rule is that new stuff can only be added if we can identify something to take out. (Note: refactorings that rearrange the order of material are also welcome.)
b) If you're submitting by PR, please include discussion in the comments on the PR (*not* in the submitted content) about the purpose of the exercise.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather have some of that motivational discussion in the commit messages (which are easier to find via git blame … than the PR that landed the commit and then the appropriate comment in the PR discussion).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like you dropped the SVG suggestion. I'd recommend keeping it, since raster diagrams are harder to maintain.


Your change doesn't have to be accepted in order for you to become an instructor - the point is to make sure that you understand the process and have met the people who review material. If you want to do your final demonstration(s) in a language other than English, please let us know in advance so that we can find someone to sit in.
Please note:

- We do *not* want exercises or other material that introduce new concepts - our lessons are already full to bursting.

- We accept submissions to DC for the purpose of becoming a SWC instructor.

- Your change doesn't have to be accepted in order for you to become an instructor - the point is to make sure that you understand the process and have met the people who review material.

2. Once you have submitted, pick a SWC lesson (if you want to become a SWC instructor) and/or a DC lesson (if you want to teach DC - if you want to teach both, pick one of each) and read through it carefully. Once you've done that, sign up on http://pad.software-carpentry.org/lesson-discussion-2016 to take part in a discussion session. Some of these sessions focus on specific lessons, while others are combined with our workshop debriefing sessions. We're trying both formats for the next month or so to figure out which works best.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest different wording and order of saying that. I.e. tell them to pick lesson(s) so that they read through them, submit a PR and join a discussion session. Spell out that they need to be active at the discussion session and not just listen!


If there aren't upcoming slots on the Etherpad that work for you, please add yourself to the top and we'll set something up. You must do this step separately for each Carpentry, and you're expected to read through the lesson(s) carefully *before* your session and show up with questions. If the session moderator (an experienced instructor) feels you haven't done this, you'll be invited to come back to a future session.

3. Once you're through the discussion session(s), sign up for a 5-minute online demonstration lesson slot on http://pad.software-carpentry.org/teaching-demos (or add yourself to the top of the pad if none of the available slots works for you). In that, we will ask you to teach a short segment from your chosen lesson - we'll pick the starting point on the day, so you will need to be familiar with the whole lesson. If you want to do your final demonstration(s) in a language other than English, please let us know in advance so that we can find someone to sit in.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

change:
so you will need to be familiar with the whole lesson
to:
so you have to be prepared enough to be able to teach any given part of the lesson.

If all goes well, we will send you your certificate, add you to our roster, and get you on the dance floor.

We'd like to get everyone through this by the end of May, so please get started as soon as you can. If you have any questions, or if family or work commitments mean that you need an extension, please mail me and we'll work something out.

Expand All @@ -31,11 +45,3 @@ DC Lessons (from http://www.datacarpentry.org/lessons/): we would prefer contrib
- OpenRefine-ecology: https://github.com/datacarpentry/OpenRefine-ecology/

New Python lesson: https://github.com/swcarpentry/python-novice-gapminder. This lesson is an experiment to see if we can start collaboration much earlier than we have in the past. If you want to add to this, please submit an exercise that uses the Gapminder data set (in the "data" directory). Please don't worry too much about formatting, and please only submit the Markdown files (not generated HTML) in pull requests.

SWC Lessons (from http://software-carpentry.org/lessons/): these are pretty mature, and have had their tires kicked a lot by other trainees, so they need the least attention. However, if you want to go through http://software-carpentry.org/blog/categories/#debriefing and pull out a few pieces of advice to add to the instructor's guide for any of these lessons, you would be my new best friend...

- Unix shell: https://github.com/swcarpentry/shell-novice
- Git: https://github.com/swcarpentry/git-novice
- Python: https://github.com/swcarpentry/python-novice-inflammation
- R: https://github.com/swcarpentry/r-novice-inflammation or https://github.com/swcarpentry/r-novice-gapminder
- SQL: https://github.com/swcarpentry/sql-novice-survey