## California Libraries Carpentries Meetup These slides: <https://hackmd.io/@timdennis/cali-carps> View mode: <https://hackmd.io/xA426D4XQuasjNRqKq7X2A?view> --- ## Today: 1. Contributing to existing lessons 2. Lesson Development 3. Carpentries Incubator --- ## Contributing to existing lessons --- ### Find a lesson you want contribute to: <img src="http://swcarpentry.github.io/shell-novice/assets/img/swc-icon-blue.svg" alt="drawing" width="50"/> - <https://software-carpentry.org/lessons/> <img src="https://datacarpentry.org/genomics-workshop/assets/img/dc-icon-black.svg" alt="drawing" width="50"/> - <https://datacarpentry.org/lessons/> <img src="https://librarycarpentry.org/lc-data-intro/assets/img/lc-icon-black.svg" alt="library carp" width="75"> - <https://librarycarpentry.org/lessons/> --- **Also check out the evolving incubator lessons:** <https://carpentries.org/community-lessons/#the-carpentries-incubator>  --- **See something you want changed/improved** Create an issue:  --- **Another method is to look at existing issues on a lesson**  Pick one you'd feel like you can resolve. --- **To fix:** 1. Fork the repo to your own account 2. Make the change 3. Make a pull request back to the lesson 4. Maintainers will communicate back about the suggested request 5. Changes merged & lesson is better --- **You can also review the help wanted page for issues across lessons:**  This lists issues with 'help wanted' or 'good first issue' <https://carpentries.org/help-wanted-issues/> --- There is a good step-by-step guide on how to contribute via a pull request:  <https://github.com/dmgt/swc_github_flow/blob/master/for_novice_contributors.md#> --- As you contribute, you'll get to know the maintainers of a lesson. If you really like the lesson, volunteer to help maintain it. Maintainers welcome this. --- **Remember, once you contribute to a lesson, you become a co-author on the lesson when published.** --- ## New Lesson Development --- **Carpentries have a defined lifecycle to lesson development** [][cdh-lifecycle] --- We also recommend a **backwards design** approach when you develop lessons. --- **Backwards design approach:** 1. Write learner personas to figure out who you are trying to help 2. Brainstorm to get a rough idea of what you want to cover, how you’re going to do it, what problems or misconceptions you expect to encounter, what’s not going to be included, and so on. 3. Create a summative assessment to define your overall goal (final exam or capstone) 4. Create formative assessments that will give people a chance to practice the things they’re learning --- **Backwards design approach:** 6. Order the formative assessments to create a course outline based on their complexity, their dependencies, and how well topics will motivate your learners 7. Write material to get learners from one formative assessment to the next. Each hour of instruction should consist of three to five such episodes 8. Write a summary description of the course to help its intended audience find it and figure out whether it’s right for them *From: Teaching Tech Together: <https://teachtogether.tech/en/index.html#s:process>* Note: * These will also tell you (and them) whether they’re making progress and where they need to focus their attention. * The best way to do this is to itemize the knowledge and skills used in the summative assessment you developed in the previous step and then create at least one formative assessment for each. --- **Resources to help with lesson development** [](https://cdh.carpentries.org/) <https://cdh.carpentries.org/> --- **Resources to help with lesson development** [Lesson Development Study Group](https://carpentries-incubator.github.io/study-groups/) ---  Teaching Tech Together: <https://teachtogether.tech/en/index.html#s:process> --- # :fork_and_knife: --- ## The Carpentries Incubator --- **Why The Carpentries Incubator?** * Interest in the way The Carpentries teach and deliver workshops * Tools and templates for lessons formatted for both in-workshop settings and in self-guided settings * Need from learners who have participated in our workshops to explore further topics that can only just be covered briefly in our 2-day trainings --- **Goals of Carpentries Incubator** * Be a place for Carpentries community members to share resources in early stages of development. * Can be taught in meetups, in class, or in complement of a "standard" Carpentries 2-day workshop. --- **Why should you submit your lesson to The Carpentries Incubator?** * You want to make your lesson materials available to others in The Carpentries community. * You are interested in getting contributions from other community members. --- ## Requirements for being included in The Carpentries Incubator? --- **For all proposals:** * Lesson/proposed topic are distinct from existing [official][curricula-official] and [community developed lessons][curricula-community] * If this is not the case, we recommend you collaborate with the authors/maintainers of those existing materials. * Please also refer to the [list of open Issues on this repository][issues]: you might find someone else has already proposed a new lesson on the same topic - they could be your first collaborator! --- **For pre-existing lesson material:** 1. Must use the [lesson template][lesson-template] and conform to our [Code of Conduct][coc]. 1. Use the [lesson example][lesson-example] ([GitHub Repo][lesson-example-repo]) to learn more about how to use the lesson template. 1. Your lesson is licensed [CC-BY][cc-by] or [CC-0][cc-0] 1. The displayed life-cycle stage of your lesson fits with the recommendations in [Chapter 7 of the Curriculum Development Handbook][cdh-lifecycle]. 1. (Recommended) Your lesson follows The Carpentries approach to curriculum development detailed in our [Curriculum Development Handbook][cdh]. --- **How to submit a lesson or a lesson idea to the Incubator?** * Open an [Issue][issues] in the repository: <https://github.com/carpentries-incubator>. * The Issue template has a [short set of questions][issue-template] for you to answer. * Your answers to these questions will help us to determine an appropriate next step for your lesson materials or lesson idea. * Feel free to get in touch with <team@carpentries.org> with any questions, either before or after submitting your Issue. --- ### Thank you! :sheep: --- [cc-0]: https://creativecommons.org/share-your-work/public-domain/cc0/ [cc-by]: https://creativecommons.org/licenses/by/4.0/ [cdh]: https://cdh.carpentries.org/ [cdh-lifecycle]: https://cdh.carpentires.org/the-lesson-life-cycle.html#overview-and-definitions [carpentries-lab]: https://github.com/carpentrieslab/proposals [coc]: https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html#code-of-conduct-summary-view [curricula-community]: https://carpentries.org/community-lessons/ [curricula-official]: https://carpentries.org/workshops-curricula/ [issues]: https://github.com/carpentries-incubator/proposals/issues [issue-template]: https://github.com/carpentries-incubator/proposals/blob/master/.github/ISSUE_TEMPLATE/issue_proposal.md [lesson-example]: https://carpentries.github.io/lesson-example/ [lesson-example-repo]: https://github.com/carpentries/lesson-example/ [lesson-template]: https://github.com/carpentries/styles