Skip to content
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

Closed
3 tasks done
svenvanderburg opened this issue Nov 23, 2022 · 5 comments
Closed
3 tasks done

Progressing from 'beta' to 'stable' stage #262

svenvanderburg opened this issue Nov 23, 2022 · 5 comments
Assignees
Labels
high priority Need to be addressed ASAP lesson-dev-sprint

Comments

@svenvanderburg
Copy link
Collaborator

svenvanderburg commented Nov 23, 2022

The lesson should progress from 'beta' stage to 'stable' stage. See https://carpentries.github.io/curriculum-development/the-lesson-life-cycle.html.

@svenvanderburg
Copy link
Collaborator Author

@tobyhodges can you specify:

  • How many beta pilot testers we need
  • Is this everything we still need to do?
  • What is the final action for progressing this to the next stage?

@tobyhodges
Copy link
Member

  • How many beta pilot testers we need

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.

  • Is this everything we still need to do?

Pretty much. But there is more you can do if you want to make the lesson even better - see below.

  • What is the final action for progressing this to the next stage?

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 paper.md file to accompany the lesson.

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 life_cycle field in _config.yml and the repository tags in the "About" box of the repository homepage.

@dsmits dsmits added high priority Need to be addressed ASAP lesson-dev-sprint labels Nov 29, 2022
@dsmits
Copy link
Collaborator

dsmits commented Nov 29, 2022

Related: #178

@svenvanderburg
Copy link
Collaborator Author

@colinsauze and @psteinb we thought it would be best to submit the lesson to Carpentries Lab. How do you feel about that?

@svenvanderburg
Copy link
Collaborator Author

Lesson marked as stable with #371, submission to carpentries lab will done with #333

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high priority Need to be addressed ASAP lesson-dev-sprint
Projects
None yet
Development

No branches or pull requests

3 participants