Open Source Community

Overview

The Open Source Community feature area covers the governance, contribution, and coordination infrastructure of Open edX as an open source project — Open edX Proposals (OEPs), the working group system, the named release process, contributor tooling, and the community translation (i18n) pipeline.

This is the meta-layer of the platform: how decisions get made, how the codebase evolves, and how contributors across dozens of organizations coordinate without a single company dictating direction.

Current State (2026)

• OEPs (Open edX Proposals): Formal process for platform-wide changes; proposals in openedx-proposals repo as RST files; reviewed by core contributors
• Working groups: Domain-specific groups (Accessibility, Arch, Build-Test-Release, Data, Frontend, etc.) coordinate work across organizations
• Named releases: Biannual named releases (alphabetical; currently in "S" — Sumac); each release tested and supported by the community
• Translation: openedx-atlas manages pulling translated strings from Transifex; platform supports 50+ languages
• Axim Collaborative: The nonprofit steward of the Open edX project (formed after 2U retained the edx.org IP); governs community direction

Architecture

• OEP process: GitHub PRs on openedx-proposals; community review period; acceptance by core committers
• Release process: Working group manages picking a named release branch from each repo; integration testing via Tutor; release notes compiled
• Translation pipeline: Source strings extracted from repos → uploaded to Transifex → community translates → openedx-atlas pulls and distributes back
• Contribution: PRs to any openedx/ repo; CLA required; review by repo maintainers (often Axim or provider engineers)

Relevant Repositories

Repository	Role in This Feature	Activity Level	Notes
openedx/openedx-proposals	OEPs — Open edX enhancement proposals	Medium	Governance docs
openedx/openedx-atlas	Translation management and distribution	Medium	i18n pipeline
openedx/openedx-events	Events framework; community-contributed events	High	Open standard
openedx/openedx-filters	Filters; community extension points	High	Open standard
openedx/brand-openedx	Official Open edX brand assets	Low	Brand guidelines
openedx/docs.openedx.org	Official documentation (Sphinx/RST)	Medium	Docs source

Recent Changes

• Axim Collaborative maturing as the governance steward
• Named release process refined with biannual cadence

History

Origin

• Year introduced: 2013 (open sourced); community governance evolved significantly over time
• Initial implementation: Open sourced by edX as the "Open edX" project in June 2013; edX Inc. was the de facto owner
• Context: The original open source release was driven by edX's mission to democratize education; community governance came later as the ecosystem grew

Key Milestones

Year	Milestone	Teams / People Involved
2013	Open edX open sourced by edX	edX Engineering
~2016	OEP (Open edX Proposal) process established	Unknown
~2017	Named release process (alphabetical) established	Unknown
2021	edX acquired by 2U; community future uncertain	Unknown
2022	Axim Collaborative formed as nonprofit steward	Axim Collaborative
~2023	Axim takes on governance; working groups formalized	Axim Collaborative

People Who Shaped This Area

• Engineering: Unknown — key community architects to document
• Product: Unknown
• Community leadership: Axim Collaborative (post-2022); edX Engineering (pre-2022)

Open Questions

• [ ] Who designed the OEP process and what was the model (Python PEPs? Django DEPs?)?
• [ ] How did the transition from edX to Axim Collaborative affect the contributor community?
• [ ] Which OEPs have had the most impact on the platform architecture?
• [ ] How does the named release process work in detail — who decides what goes in?
• [ ] How does Schema Education participate in or observe the open source community?
• [ ] What is Marco's view of the health and direction of the Open edX open source community?