...
Roles are listed below; the person listed next to the role is the person most highly responsible for the definition.
...
tCRIL Legal Requirements: Common for all Core Contributor Program Participants
We are asking that all Core Contributors, regardless of role, complete the following requirement:
...
We are additionally asking that, for those Core Contributors contributing on behalf of an employer, all employers of Core Contributors sign the Revised Declaration of Commitment to the Core Contributor Program when it is finalized in late November 2021, to demonstrate that they are willing to spend part of your time working on the Open edX project.
...
Responsibilities:
Translate Open edX strings into their spoken language(s)
Review/accept translations; serve as arbiters of correct translations
Attend Transifex Working Group meetings
Report Open edX-specific and uncontextualized strings to the edX teamTranslation Working Group
Identify stellar translators in their language and encourage/support them
Access:
Access they already can get for free: translator access on Transifex, reviewing capabilities for their language(s)
edX tCRIL requirements:
Required review of a Transifex training document
General accessibility overview course (TBD)
...
Responsibilities:
Test the following areas and produce actionable issue reports, following up with coders needing clarification, retesting, etc.
Test new features prior to or immediately after release, including accessibility and internationalization aspects
Test out/exercise named releases
Test and review documentation of features, both new and existing features (maintenance work)
Test and review release notes.
Access:
Potentially read only access to Miro
Potentially access to shared Google docs
Access they already can get for free: GitHub read access, devstack, edx.org student tCRIL training site account
tCRIL requirements:
Take the content authoring and/or developers versions of the a11y course to be able to better test a11y features (TBD)
...
Responsibilities:
Proficiency in professional English
Follows the documentation specifications laid out in OEP-19
Maintain existing documentation: reviewing/updating documentation as needed, including:
Onboarding materials
Courses
Documentation infrastructure
Produce new documentation, including:
Test out released features and document their use
Test out developer-facing tools (devstack, Tutor) and document their use
Test out installing/running named releases and document how to do it
(potentially) provide documentation for unreleased features (note: I currently believe we do not have the capacity to support documentation of unreleased features)
Access:
Access you already can get for free: devstack, learner account on tCRIL-hosted Open edX instance, edx.org, local instance, or other community-based instance
Write access to Open edX documentation repositories
(potentially) access to shared Google docs & read-only access to Miro, if documenting unreleased features
Requirements
Take the content author’s track of accessibility course (TBD)
...
Responsibilities:
Someone external coming in and managing OSPRs - does not need to be affiliated with an 2U/edX partner organization
Ideally someone technical enough to understand how complex a given changeset is
Can use CI tools
Able to communicate clearly and concisely to core committers & 2U/edX engineering about priority and relative effort
Follows newly incoming requests and triages them
Say Hi on the PR
Route to the proper team
Follows older PRs and bumps them
Ping the author if something’s been waiting on them for a long time
Ping the reviewers if something’s been waiting on them for a long time
We can train you on this job!
Access:
Already granted publicly: read access to GH, shared Slack channels
Ability to move ticket states on the open Jira OSPR board
tCRIL requirements:
No additional requirement
...