...
Roles are listed below; the person listed next to the role is the person most highly responsible for the definition.
...
Axim Legal Requirements: Common for all Core Contributor Program Participants
We are asking that all Core Contributors, regardless of role, complete the following requirement:
...
Responsibilities:
Effectively and efficiently enable collaboration on Open edX projects and working groups.
Perform quality control on the project throughout development to maintain the standards expected.
Keeping up with the development team on a regular cadence to ensure work is progressing
Planning
Create long- and short-term plans, including setting targets for milestones and adhering to deadlines.
Adjust schedules and targets on the project as needed.
Communications
Communicate updates and keep the project aligned with their goals to relevant stakeholders & the broader community
Serve as a point of contact for the project.
Collaboration
Facilitate group discussions that result in effective decision-making when multiple options are present.
Delegate tasks on the project to community members best positioned and interested to complete them.
Prefer asynchronous discussions to accommodate global timezones.
Keeping track of project or program specifics
For example, for funded projects, keep track of how much of the budget is being spent on a sprint (2-week) basis
Access:
GitHub - Write Triage Access to GitHub Projects
? Miro access for facilitating group conversationsCalendly account
Any additional access, as needed, to support particular projects and working groups that the PM is associated with.
Requirements for nomination:
Demonstrated consistent participation in the Open edX project in areas of project management that are detailed above
Per the definition of the Core Contributor program, a demonstration of the “3 C’s”:
Commitment: Has shown ongoing organizational and “glue” work - plus anything else - for the Open edX community
Conduct: In written and verbal communication, is welcoming to all, provides helpful feedback, and overall maintains a positive attitude
Caliber: The work produced is of a consistent high quality
...
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, tCRIL Axim training site account
Requirements for nomination:
At least 6 months of QA work for any area of the Open edX project, including QA work for BTR and reporting well-documented bugs with reproduction steps
Per the definition of the Core Contributor program, a demonstration of the “3 C’s”:
Commitment: Has shown ongoing work in the Product space for the Open edX community
Conduct: In written and verbal communication, is welcoming to all, provides helpful feedback, and overall maintains a positive attitude
Caliber: The work produced is of a consistent high quality
...
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 tCRILAxim-hosted Open edX instance, 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 for nomination:
Portfolio of documentation work done for the Open edX project (not a fork)
Per the definition of the Core Contributor program, a demonstration of the “3 C’s”:
Commitment: Has shown ongoing work in the Product space for the Open edX community
Conduct: In written and verbal communication, is welcoming to all, provides helpful feedback, and overall maintains a positive attitude
Caliber: The work produced is of a consistent high quality
...
Responsibilities:
Regular, active participation in the Product Working Group, which may include:
Contributing to the discussions
Participating in review and prioritization exercises
Providing input on product direction
Leading collaborative efforts with stakeholders in other working groups, focus groups, other core contributors
Help define opportunity areas, which may include:
Performing market/user research
Gathering community input
Conducting competitive/landscape research
Gap analysis
Product Briefs, Concept Documentation
Lead, or assist leading, the development of an initiative, feature or effort, which may include:
Scoping exercises such as user stories, specs, requirements
Working with UX designers on wireframes
Managing user feedback loops
Performing acceptance testing
Project Management skills may sometimes be required
Tools/Access:
Project Trackers, such as GitHub Issues
Triage access to all Github issues
Documenting systems such as wiki, google docs, Open edX documentation
Skills
Common product documentation types, such as product briefs, gap analysis, concept notes, user stories, feature specs
Common product tools, such as survey work, market feedback methods, user interviews, project boards
Able to work synchronously via Zoom, Meet, and asynchronously via Slack
Requirements:
Able to present a portfolio of product-related work
Per the definition of the Core Contributor program, a demonstration of the “3 C’s”:
Commitment: Has shown ongoing work in the Product space for the Open edX community
Conduct: In written and verbal communication, is welcoming to all, provides helpful feedback, and overall maintains a positive attitude
Caliber: The work produced is of a consistent high quality
...
Responsibilities:
Create design work in standard tools for upcoming/in flight projects
Participates in Design Review meetings with 2U/edX UX team, as needed
Has a “champion” relationship with a UX manager, as needed
Unfortunately 2U/edX does not currently have opportunities for UX work that is not a part of established projects. This means you should bring your own community projects, or ask the 2U/edX team if there’s work available that you can pick up.
email cc-program-admins@tcriladmins@Axim.org if you have a project/proposal of what to work on, and we’ll start a conversation
Access:
Miro
Figma
In some cases, JIRA/Confluence
2U/edX requirements:
Participate in an interview with UX team
Requirements for nomination:
Portfolio of UX work done for Open edX (the main project, not a fork)
Per the definition of the Core Contributor program, a demonstration of the “3 C’s”:
Commitment: Has shown ongoing work in the Product space for the Open edX community
Conduct: In written and verbal communication, is welcoming to all, provides helpful feedback, and overall maintains a positive attitude
Caliber: The work produced is of a consistent high quality
...
Forum moderators have the “moderator” capability in the Open edX forums. Additionally they may serve as Community TAs for one or more courses hosted on a tCRILAxim-hosted Open edX instance.
Responsibilities:
Re-Categorize new topics
Remove spam posts/ban spam users
Organize older topics as needed/maintain the platform
Respond to topics with high quality answers - pointers to documentation, referral to other users, etc
Access:
(for regular forum) Moderator role on discuss.openedx.org
(for regular forum) Access to #discourse-moderators in Open edX Slack
(for Community TAs) Community TA permissions on one or more tCRILAxim-produced Open edX courses
Requirements for nomination
At least 6 months of consistent forums presence and high quality answers
Per the definition of the Core Contributor program, a demonstration of the “3 C’s”:
Commitment: Has shown ongoing work in the Product space for the Open edX community
Conduct: In written and verbal communication, is welcoming to all, provides helpful feedback, and overall maintains a positive attitude
Caliber: The work produced is of a consistent high quality
...
This role refers specifically to those community members with authoring permissions on a tCRILAxim-hosted Open edX instance.
...
Responsibilities
Author content for one or more tCRILAxim-produced courses
Access
Studio (authoring) access to one or more tCRILAxim-produced courses in the tCRIL Axim Open edX instance
Requirements for nomination
Per the definition of the Core Contributor program, a demonstration of the “3 C’s”:
Commitment: Has shown ongoing work in the Product space for the Open edX community
Conduct: In written and verbal communication, is welcoming to all, provides helpful feedback, and overall maintains a positive attitude
Caliber: The work produced is of a consistent high quality
...
This role refers specifically to those community members with admin permissions for one or more courses on a tCRILAxim-hosted Open edX instance. Admin permissions are defined as permissions which allow you to view sensitive learner information such as learner email addresses, learner course grades, and problem submissions. A person with an in-course designation of “Community TA” does not fall under this umbrella but rather would fall under the “Forum moderators” CC distinction.
...
The right to commit code directly to the Open edX project is not granted lightly. Please see the following set of pages which dives deeper into the rights and responsibilities of an Open edX code contributor: Coding Contributors Materials
What are a Core Contributor’s access & responsibilities?
...
Release Manager - Sarina
See discussion thread about new role
A release manager is elected by the BTR group for a six-month period; this person should already be a coding CC.
Responsibilities:
Perform release management for BTR (for both the new release as well as maintenance of the previous release) in any and all repos that are defined as part of the Open edX named release for that iteration.
Reviewing and merging patches
Cutting new release branches - and amending them as needed
Access
Write access to all repos currently part of the named release; see https://github.com/orgs/openedx/teams/community-release-managers
Requirements for nomination
A coding CC
This role would be elected by the BTR group, as is currently done - and as part of the election, a nomination thread is put in this forum with the clear indication that BTR approves the choice. This thread has a shortened 1-week review period
What are a Core Contributor’s access & responsibilities?
CCs may need access to…
Internal 2U/edX tools
Various Google docs/sheets (WG members/Project mgrs/PMs/UX)
Design Tools
Figma (PM/UX)
Miro (PM/UX/QA/Project mgr)
Committer access to documentation repos (docs)
Admin access to marketing sites/materials (marketing WG)
Tools that already have access but we should be sure are set up
Appropriate Jira/Confluence access - may involve some access to currently-private spaces
Shared Slack channels
...
Could have a Champion (essentially point of contact & advocate) per role type - thinking
The Transifex Working Group with assistance from Eden will serve as champion for and oversight of Translators.
We could build out a QA function organically and have a QA Working Group oversee team efforts
Marketing WG with assistance from Eden serves as champion/oversight of Marketing CCs
UX Core Contributors will work alongside a 2U/edX “champion”
Project managers will likely not need champions, but rather points of contact at tCRIL Axim and possibly within other community member orgs necessary to carry out their work
Product managers will work alongside a 2U/edX or tCRIL Axim “champion”, likely the person they work most closely with for a given project or someone acting in a bit of a mentorship-like capacity
...