Skip to content

Commit f45001c

Browse files
authored
Update CONTRIBUTING.md with Curriculum Working Group details
Added a section for the Curriculum Working Group outlining responsibilities and membership details.
1 parent 5eae408 commit f45001c

1 file changed

Lines changed: 12 additions & 7 deletions

File tree

CONTRIBUTING.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -28,11 +28,20 @@ Thanks also go to the following organizations that have supported this effort:
2828
- [Superbloom](https://superbloom.design/)
2929
- [STRUDEL project](https://strudel.science/), current maintainers for this lesson
3030

31-
This lesson is presently maintained by the STRUDEL Curriculum Working Group. Working group members include: Hannah Cohoon, Anh Le, and Georgia Bullen. To join the working group and become an official maintainer, [open an issue in this repo][issues] indicating your interest. You do not need to be a working group member to contribute; follow instructions below to contribute at any time.
32-
3331
STRUDEL is an effort of the Lawrence Berkeley National Lab Scientific Data (SciData) Division UX team.
3432
The project is generously funded by the Alfred P. Sloan Foundation, Liz Vu & Josh Greenberg Program Officers, grants #10074 and #10572
3533

34+
#### Curriculum Working Group
35+
This lesson is presently maintained by the STRUDEL Curriculum Working Group. Working group members include: Hannah Cohoon. To join the working group and become an official maintainer, [open an issue in this repo][issues] indicating your interest. You do not need to be a working group member to contribute; follow instructions below to contribute at any time.
36+
37+
Curriculum Working Group maintainers are responsible for developing and sustaining the Rapid Usability Testing lesson in the Carpentries Incubator. They must:
38+
- Keep the lesson usable by the community. This includes stewardship of lesson content, website, contributor guide, and related documentation.
39+
- Monitor issues, emails, and pull requests, even if they are not the primary contact point for a given issue, email, or pull request
40+
- Ensure a maintainer replies to new issues, emails, and pull requests promptly, ideally within one week
41+
- Ensure other contributors have adequate opportunity to engage
42+
- Define and maintain a roadmap for expanding this lesson as part of a larger curriculum
43+
44+
3645
### Contributor Agreement
3746
This lesson was developed in partnership with The Carpentries and is part of their [incubator program](https://carpentries-incubator.org/).
3847

@@ -42,17 +51,13 @@ Carpentries lessons are community-driven. By submitting your work, you agree to
4251
The Curriculum Working Group responsible for maintaining this lesson has defined the following roadmap, indicating current and future priorities:
4352

4453
*Current priorities:*
45-
46-
Resolving open issues
47-
54+
Resolving open issues
4855
Supporting community members in leading their own workshops that use the Rapid Usability Testing lesson
4956

5057
*Near future priorities:*
51-
5258
Continuing to refine lesson content so that it includes the minimum amount of content needed to empower learners
5359

5460
*Long term priorities:*
55-
5661
Supplement the Rapid Usability Testing lesson with additional lessons as part of a larger curriculum
5762

5863

0 commit comments

Comments
 (0)