OEP-2: Repository Metadata
OEP-2: Repository Metadata#
Calen Pennington, Feanil Patel, Nimisha Asthagiri
Calen Pennington <email@example.com>
Proposes a standard format for repository metadata for Open edX projects.
One of the primary goals for Best Practice OEPs is to standardize techniques and tools across Open edX repositories. However, without tooling, it will be difficult to move all of the repositories in the same direction (and hard to validate which ones have been updated). This OEP exists to fill that gap. By providing a standard format for metadata about accordance to Best Practice OEPs, tools can be developed in the future to report on the current status of all of the Open edX repositories, and how well they follow the Best Practices listed in the OEPs.
Bear in mind that particular classes of Open edX repositories may have different Best Practices. The practices that apply to an XBlock may not be the same as those that apply to a standalone Django service or to a Django app.
Each repo will include a file
openedx.yaml, with the following keys:
tags: list of strings (optional)
This key is used to annotate repositories, for example to categorize them for automated reporting tools. See Tags.
oeps: dictionary (optional)
A list of keys corresponding to Best Practice OEPs (in the format
oep-n). Each value would be one of
False, or a reason dictionary.
Falseindicate compliance (or lack thereof) with the specified OEP.
A reason dictionary provides more detailed information. It can contain a boolean
state, a boolean
applicable, and a string
If the OEP is not currently applicable to this repository, the reason dictionary can simply contain a single value of
reasonvalue must be included that explains why.
reasoncan optionally provide more information. The
reasonvalue will be displayed in reporting tools. If an OEP isn’t listed in the
oepsdictionary, then it is assumed to be
False, unless the reporting tool can auto-detect accordance.
openedx-release: defined by OEP-10 (optional)
Define this key if your repo is an application or IDA that is part of Open edX releases. Omit this key if your repo is a library, or is not part of Open edX releases. See OEP-10 for details.
This key is obsolete, please remove if found.
supporting_teams: list of strings
This is an obsolete key that was used to specify Github handles for teams supporting the owner of the repository. This is now deprecated in favor of the updated
ownerdictionary. As a reasonable migration of this key, set
owner.valueto the first value in
supporting_teams, and then remove
This key used to contain information about the assigned owner of this repository.
type: string (optional)
The value of this key would be either
repo. It indicated which ownership model applied to this repository, and therefore which of these two keys would exist with a non-empty value.
team: string (optional)
The GitHub team responsible for this repository, prefixed with the Github organization (e.g.,
edx/arch-bom). If this value was set, this repository contained high-level, business-aligned functionality that was suitable for direct ownership designation to an individual responsible team.
repo: string (optional)
The GitHub repo responsible for this repository, prefixed with the Github organization (e.g.,
edx/XBlock). If this value was set, this repository contained lower-level technical functionality that was affiliated with another primary owning higher-level repository.
This key is obsolete, please remove if found. It was a short-name for this repository, used by reporting tools.
archived: boolean (optional)
True, this specifies that this repository is archived and no longer maintained by edX.
For example, in the edx-platform repo, the file might look like:
# openedx.yaml --- tags: - core - xblock - lms - studio oeps: oep-314: True # edx-platform uses django 3.14 oep-42: state: False reason: This OEP doesn't actually exist oep-2: state: True # no reason is required since this is True oep-100: applicable: False # state is not required since the OEP is not applicable reason: This OEP contains best practices for C++ which is not used in edx-platform oep-101: applicable: False # reason is not required since it's almost always just a redundant statement about it not being applicable
The keys in
openedx.yaml were derived from existing repository metadata collected by edx.org.
The design of the
oeps dictionary was guided by a couple of use cases:
Adding a new OEP that few repositories will support, initially. We shouldn’t need to update all repositories to detect if they are in accordance, we should be able to assume that they aren’t, or automatically detect whether they are.
Repositories may have specific requirements that force them to not implement a best practice. The tools should be able to present that reasoning to anyone looking across repositories, and the reasons should be documented in the repositories themselves.
As much as possible, Best Practices should be autodetected, but because they will often involve a judgement call, autodetection shouldn’t be mandatory.
archivedkey to the Obsolete Keys section.
nickkey to the Obsolete Keys section.
ownerkey to the Obsolete Keys section and removed no longer relevant ownership rationale and information.
ownerkey optional. Initially, the key served two purposes: assigning ownership of the repository and as a “who to contact” for repo related issues. Ownership info has now been moved to an edX internal location. As for contact info, this is still a work-in-progress. We plan on adding contact point to repos at some point in the future. The exact location is still to be determined, possibly in openedx.yaml or CODEOWNERS file.
New practices for ownership bookkeeping and designation in our repositories:
Ownership is assigned to squads (i.e., teams with 5-6 people each) as opposed to individuals.
Owners are assigned at the granularity of higher-level, business-aligned functionality (user-facing services, user-facing apps, and system-wide frameworks).
Lower-level repos are indirectly assigned owners through assignment to dependent higher-level repos.
Minor formatting and wording changes for clarity.
archivedand relax the requirement for an owner if
applicablekey in the reason dictionary.
Move the definition of
Add documentation of the
nickkeys in the