Chapter 8 The lesson life-cycle
- Definitions of alpha, beta, 1.0
- Alpha: The stage that it is in the first time it is taught. (in house)
- Beta: The stage that it is in after the pilots and clean-up. (wider community)
- pre-release: The stage that it is in after initial publication. (anyone)
- letting the community know that the lesson is being prepared for release and what that means
- Advertising for Bug BBQ
- Bug BBQ
- How to organize for, how to schedule
- Communications (when and how to announce)
- Prep (communicating with maintainers about the process)
- Facilitating communications during the actual event (real time communications, issue assignments, avoiding duplication of work)
- Clean-up (maintainers, staff, authors)
- Lesson release checklist
- Pre-Release Release
- How to communicate about a release
- How to do the release in Zenodo
- Move on website to different category
- Community-developed lessons
- Lessons with grant support
8.2 Pathway for community-developed lessons
If you have an idea for a lesson that would be a good fit for The Carpentries, you first need to check if there are not already existing efforts to develop lessons on the same topic that you could join. The first draft (Pre-Alpha) of a lesson is usally written by an individual or a small group of people. From this first draft, the original authors organize a pilot workshop, and improve the content of the lessons based on the feedback from learners and co-instructors. They go through this iterative process a few times to bring the lesson where it is ready to be peer-reviewed by members of The Carpentries. After that, the lesson should be developed enough that people not involved in initial development efforts can teach it and contribute to it (Beta). After about six months in this stage, the lesson is mature enough and documented enough so that anyone interested can teach it and is officially released.
The Pre-Alpha and Alpha development stages should focus on the content of the lesson: What to teach? How to teach it (which exercises, in which order should the concepts be introduced)? In the Beta stage, development efforts should focus on documenting the lesson, so that any Instructor familiar with the concepts covered in the lesson can understand the design of the lesson.
8.2.1 The blueprint (lesson proposal)
If you have an idea for a lesson you think would be appropriate for The Carpentries, submit a proposal to the
proposals repository in the Carpentries Lab organization following our template. The Curriculum Development Team will assess the fit of the proposed lesson, check for possible overlap with other efforts, and assign an Editor. If you have questions before submitting your proposal you may contact the Curriculum Development Team.
The Curriculum Development Team and the Editor will work with you on your proposal. Once your proposal is accepted, we will publish the revised version of your proposal on The Carpentries websites. Community members who wish to join the proposal or support it in other ways will be able do so.
The Editor for your lesson will provide guidance during the lesson development process, answer questions that may arise during the development, and coordinate the review process for your lesson.
8.2.2 The assembly (Early development, “Pre-Alpha”)
We will create or transfer your repository to the GitHub Carpentries Lab organization where you will develop your lesson. We will provide you with our lesson template, and you will follow The Carpentries lesson development guidelines. During this initial development stage, your lesson will be in the “Pre-Alpha” stage.
As lesson development progresses, you will report monthly to the Editor for your lesson. You will work with your handling Editor to set a date to teach the lesson for the first time. The Editor will provide general feedback on the content and structure of the lesson, and ensure that it is ready to be taught.
8.2.3 The sanding (field test, “Alpha”)
Once the lesson is ready to be taught for the first time, it will enter the “Alpha” stage. Field-testing a lesson is a good opportunity to receive and incorporate feedback from learners, Instructors, and Developers who can compare their expectations to the reality. The initial feedback gathered during the first time a lesson is taught is really important. The Carpentries Assessment Team will work with you to develop surveys to gather feedback from your learners, helpers, and instructors. The Curriculum Development Team and the Editor for the lesson will review the feedback with you, and help you decide how to incorporate this feedback in your lesson.
The Carpentries Community Manager will make an announcement that a new “Alpha” lesson is available to contribute to and can be taught by instructors interested in early-adoption of the lesson.
These early workshops are also a good time for Instructors not involved in the development process to teach these lessons. They can provide a fresh perspective and useful feedback on the content of the lessons.
After a few iterations of teaching and integrating feedback (and at least 2 early workshop pilots), you will let the Carpentries Editor know that your lesson is ready to be reviewed. The Editor will select 2-3 reviewers within The Carpentries community with teaching experience and/or appropriate domain expertise, who will provide an open and friendly review of the lesson. After incorporating feedback and comments from the reviewers, your lesson will be badged “Reviewed by the Carpentries Community” and will be listed on our websites as such.
During this process, you will have the possibility to include a short paper describing your lesson in the GitHub repository and have your lesson considered for publication in JOSE, the Journal of Open Science Education. Once your lesson has gone through the peer-review process and has been approved by the Editor, we will create an official Zenodo release for it, and the lesson will enter the “Beta” stage.
8.2.4 The polishing (“Beta”)
The “Beta” stage lasts approximately 6 months. During this time, members of The Carpentries community can teach it and contribute to the content of the lesson. Around the 4th month in this stage, you will organize a “Lesson Polishing” event (aka Bug BBQ). The main goal of this phase of the lesson development is to develop the documentation needed to ensure that people who have not contributed to the initial development efforts of the lesson have enough information to teach it effectively.
After a final check from one of The Carpentries’ Editors, we will create a stable release for the lesson that will be listed on our website. Anyone in our community, including local Carpentries communities, will be able to use the lesson in their workshops or meetups.
8.2.5 The stable lesson
T We will generate new releases every 6 months.