The Carpentries is preparing to retire this handbook at the end of 2023. Existing content that has not already been replicated elsewhere will be relocated. See the relevant issue on the source repository for more details.
The Carpentries Incubator is where The Carpentries community develops curricula together. It is intended to serve as a place to find and contribute to lessons that members of our community are developing with the approaches and infrastructure introduced in this handbook.
Proposals to begin development of a new lesson in the Incubator, and to transfer existing material (regardless of its current state/stage of development) into the Incubator, can be made by opening an issue on the Proposals GitHub repository. The requirements are minimal for a proposal to be accepted, predominantly designed to maintain consistency across the community’s lessons. The README of that repository contains more detailed guidance for those who wish to submit a proposal.
GitHub allows the maintainers of a repository to add contextual information to Issues and Pull Requests in the form of labels. Visit the How to Label Issues page of The Carpentries handbook for a list of the labels used on official Carpentries lesson repositories and to read recommendations on how to use them for your own lesson.
Two labels, used by The Carpentries and in many repositories across GitHub, can be deployed to increase the visibility of your lesson and encourage community members to contribute to its development.
The “help wanted” label should be used to highlight issues with which you would welcome additional help. The Carpentries website includes a Help Wanted page, which can automatically list every issue labelled “help wanted” on repositories from The Carpentries, Software Carpentry, Data Carpentry, Library Carpentry, CarpentriesLab, and The Carpentries Incubator. Find out how to include issues from your lesson repository on the Help Wanted page by reading the Information for Maintainers on the page itself.
The “good first issue” label should be used to identify issues that would make a good entry point for newcomers looking for a way to contribute to your lesson. The work needed to close an issue with this label would typically not require an extensive knowledge of the structure or intricacies of your lesson repository, or an expert understanding of the content. The “good first issue” label is used so extensively that GitHub provides a page at
[repository URL]/contribute for every repository, listing issues with this label.