-
-
Notifications
You must be signed in to change notification settings - Fork 36
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.
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
Progressing from 'beta' to 'stable' stage #262
Comments
@tobyhodges can you specify:
|
For official lessons, we run at least two beta pilot workshops before proposing that a curriculum/lesson be granted stable status. That is also the requirement before a community-developed lesson can be submitted to The Carpentries Lab.
Pretty much. But there is more you can do if you want to make the lesson even better - see below.
It depends on what you determine the next stage to be. My recommendation is to submit the lesson for open peer review in The Carpentries Lab, which you can do as soon as you have feedback from at least two beta pilots. If you choose to do that, you have the option to also submit the lesson to the Journal of Open Source Education at the same time. If you want to do that, you will need to write a However, if you do not want to submit the lesson to the Lab, you are free to mark it stable any time you like. To do that, you can adjust the |
Related: #178 |
@colinsauze and @psteinb we thought it would be best to submit the lesson to Carpentries Lab. How do you feel about that? |
The lesson should progress from 'beta' stage to 'stable' stage. See https://carpentries.github.io/curriculum-development/the-lesson-life-cycle.html.
The text was updated successfully, but these errors were encountered: