Core Contributor Role Definitions

Owned by Sarina Canelake (Do Not Use) (Deactivated)
Last updated: Oct 17, 2024 by Sarina Canelake
11 min read

 

Problem Statement

There are many contributors to the Open edX platform that participate in a variety of ways - writing code for the Open edX software, translating the project, people performing Quality Assurance tasks, members of the Marketing working group, documentation writers, and more. While previously the Core Contributor Program has focused on code contributors, we want to send the message that all contributors to the platform play a meaningful role and deserve the designation Core Contributor.

Core Contributors have a set of Rights and Responsibilities to the Open edX platform. In exchange for those Rights to contribute, we ask for some Responsibilities: this will include signing a Program Agreement and following the responsibilities of the roles that are laid out below.

Who can become a Core Contributor?

What specific roles required is detailed in the below Role Descriptions section. In general, however, people wishing to be Core Contributors need to show sustained, active performance in the role prior to being nominated as a NTC. We call this the “3 Cs”: Commitment, Conduct, Caliber. These people follow the Code of Conduct, are respectful of other community members, and are generally polite and welcoming. That means if you wish to be a Core Contributor, you should begin by joining the Open edX project and participate in a way that’s meaningful to you. Reach out to us if you don’t know how to begin!

How to become a Core Contributor?

Please familiarize yourself with the contents of OEP-54: Core Contributors, which discusses the program and how nominations occur. To become a core contributor, you will need to be nominated and provide evidence of how you’ve demonstrated the “3C’s” as defined above. That is, what have you already contributed to the Open edX community, and at what quality (Caliber), how have you interacted on pull requests, in writing (Discourse, wikis, Slack, etc), and/or in working groups (Conduct), and how long have you been an active member of the community/how do you intend to actively continue to contribute as a CC (Commitment)?

Core Contributor Role Descriptions

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:

Sign a Core Contributor Program Agreement, sent to you by Program administrators when you are invited to the program. This Agreement covers all NTC role types, so if you switch to a new role or add on responsibilities of a second, you will not need more paperwork (exception: the Committer role requires a bit more paperwork)

We are additionally asking that, for those Core Contributors contributing on behalf of an employer, all employers of Core Contributors sign the Declaration of Commitment to the Core Contributor Program to demonstrate that they are willing to spend part of your time working on the Open edX project.

Project manager (leading Open edX projects and/or working groups)

  • 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 - Triage Access to GitHub Projects

    • ? Miro access for facilitating group conversations

    • 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

Community Contribution Project Manager

  • Responsibilities:

  • Access

    • Triage access on some to all of the openedx code repos

  • Requirements for nomination

    • Demonstrated consistent participation in the Open edX project in areas of project management (see the “Project Management” description) and/or project participation in any form (working group participation, writing code, etc)

    • 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

Translation Reviewers

  • Responsibilities:

    • Translate Open edX strings into their spoken language(s)

    • Review/accept translations; serve as arbiters of correct translations

    • Attend bi-weekly Translation Working Group meetings

    • Report Open edX-specific and uncontextualized strings to the Translation 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)

  • Requirements for nomination:

    • Consistent contributions to string translation and review of translations within the edX platform project in TX (can be tracked through TX reporting mechanism, which displays contributions by individual), to help us achieve 100% completion rates in the translation & review of translations per release.

    • Contributions to projects that enhance the overall Open edX i18n strategy (e.g. updating current documentation, assisting in reviewing the machine translations on openedx.org, technical discovery on enhancing content translation availability within the LMS, assisting with string decoupling efforts between edX and Open edX strings, etc.)

QA

  • 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, 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

Marketing WG members

  • Responsibilities:

    • Website enhancements to increase consumer site traffic (addition of pages, features, marketing material for external consumption)

    • Marketing and media outreach to increase the global awareness of the Open edX platform

    • Representing the Open edX project in public events, event planning and organizing (for both online and in person events)

    • Video Production assistance for marketing and other user materials

    • Content Creation: identifying blog content & authors, social media content mgmt., website content in form of videos, images, demos + documentation

  • Access:

    • Website (authoring roles)

    • Shared space to discuss ideas, posts, and key launch dates

  • Requirements for nomination:

    • TBD

Documentation

  • 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 Axim-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

Product managers

  • 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, 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

*Note: As we are in the early stages of building a product organization for Open edX, it is expected that no one currently has very much community Product work to showcase in their portfolio or as part of their Commitment. Thus, we expect it may take some time before any member of the community is a candidate for the Product Core Contributor position.

UX/UI

  • 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.

  • 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

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 Axim-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 Axim-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

Content Authors

This role refers specifically to those community members with authoring permissions on a Axim-hosted Open edX instance.

Please note: The Course Author role is separate and distinct from the Course Administrator and Course Data Manager roles, and there is explicitly no guarantee that a Course Author will be approved to serve as an administrator or data manager on any given course, including a course that they authored.

  • Responsibilities

    • Author content for one or more Axim-produced courses

  • Access

    • Studio (authoring) access to one or more Axim-produced courses in the 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

Course Administrators

This role refers specifically to those community members with admin permissions for one or more courses on a Axim-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.

  • Responsibilities

    • Perform administrative tasks for such courses, including but not limited to responding to learner requests and managing course bulk email

  • Access

    • Course team member or course admin level permissions in the LMS

    • If needed/desired, Discussion moderator access (grants “Staff” badge in course forums)

  • 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

Code contributors

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

Release Manager

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

  • 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

Maintainer At-Large

See discussion thread about new role

A Maintainer At-Large CC performs necessary updates (such as major and minor version updates as well as updates to CI infrastructure) for a group of related repositories in the openedx GitHub organization.

Responsibilities

  • Perform upgrades from edx-requirements-bot / dependabot / renovate in a timely manner

  • Participate in coordination and execution of major upgrades (such as Python, Node, etc) driven by the Maintenance Working Group

  • Defer to the repo’s maintainer for any other type of work (that is, do not merge in features or bugfixes unless a named repository Core Contributor or Maintainer has asked)

Access

  • Write access to a group of related repositories

Requirements for nomination

Same as for Coding Core Contributors, see ​​Coding Contributors Materials

What are a Core Contributor’s access & responsibilities?

CCs may need access to…

  • Internal Axim or other partner tools/resources

    • 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

Should we adopt a “Champion” model?

  • 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 Axim and possibly within other community member orgs necessary to carry out their work

    • Product managers will work alongside a 2U/edX or 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

For certain, the 2U/edX UX & Product Management teams would like their CCs to have a designated point of contact/mentor within the building, in order to advance a consistent platform product vision (for example, adhering to style conventions like Paragon)