New end-of-workshop message #125
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Cross-linking previous discussion in #123.
|
|
|
||
| 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. |
There was a problem hiding this comment.
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).
|
Could you please add a sentence about reading the CONTRIBUTING file that is in the repository where they do their PR? |
| 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. | ||
|
|
There was a problem hiding this comment.
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.
|
Another possible suggestion for end-of-workshop training contributions: translation of existing material into another language. Objections:
Pros:
|
|
I'd really like translations, but they're an enormous amount of work to
maintain (and we need to figure out how to structure it - multiple
repos? branches? directories in a repo?).
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.