OEP-14: Archiving edX GitHub Repositories




Archiving edX GitHub Repositories

Last Modified



Christina Roberts <christina@edx.org> Feanil Patel <feanil@edx.org>


Nimisha Asthagiri <nasthagiri@edx.org>








ORA PR Discussion, Initial Archiving Discussions, Moving More Repos to edx-unsupported


The edx organization contains a large number of repositories, most of which are active and maintained, but some of which are now obsolete. To clarify the status of repositories, a process for archiving a repository is defined below.


Recently openedx.yaml files were added to edX repositories per OEP-2. In the course of deciding owners for those repositories, there was an ORA PR Discussion about how best to handle deprecated or obsolete repositories. In particular, do obsolete repositories need owners, and how can repositories be clearly marked as present for archive purposes only?

This discussion resurfaced related to edX’s usage of Gemnasium to report the usage of third-party libraries that have known security issues. All repositories under the edX organization were being monitored, but this added noise when trying to understand the number of third-party library updates required for actively maintained repositories.


When a repository under the edx organization will no longer be maintained by edx Inc. because it is no longer in use by the latest version of the Open edX platform, the following steps should be followed.

This process is not for repositories that are currently still in use by either the latest version of the Open edX platform or by edX Inc. the company. If a repository is in use, but planned to be removed, it should go through the deprecation process and when that is completed it can be archived as described by the process below.

Transfer to New Owner if Interest

First, if the repository is public, and a part of Open edX releases, follow these steps to see if anyone would like to take ownership of it:

  1. Post a notice to Open edX Deprecation Announcements announcing that the repository will be archived, and inquiring if anyone would like to take ownership of the repo. If there are no responses after 2 work days, skip to Archive Steps.

  2. If someone does wish to take ownership of the repository, email the internal edX developers mailing list to see if there are any objections. If there are no objections after 2 work days, post to Open edX Deprecation Announcements that the transfer will take place.

  3. Create an IT help ticket for the repository to be transferred to the new organization.

  4. Once the transfer has occurred, create a fork of the transferred repository into the edx organization and follow the Archive Steps below for the forked repo.

Archive Steps

These steps should be followed for all repos within the edX organization(forks included). After some experiments with keeping archived repos in the edx organization, we’ve learned that having abandoned code show up in searches hinders work to understand the current state of the system and the risk around new work, particularly deprecations and API changes. Thus we decided to move all archived repositories to a separate org.

  1. Update the README.rst file in the repository to add a brief note about why the repo is being archived, and what is serving as its replacement (where applicable). This may be as simple as a linking to the appropriate DEPR ticket.

  2. Unless you have the relevant permissions to perform this step, create an IT help ticket and ask them to do the following:

    • Archive the repository per GitHub’s archive process

    • Move the repository to the edx-unsupported organization

      • If the repo is not coming from the edx github org then before moving it, rename it with a prefix of the source org’s name. For example the notifier repo in the edx-solutions org wolud be renamed to edx-solutions-notifier before moving.


Over the lifetime of Open edX, we may fork the same external open source repository multiple times. In this case, we may need to archive the fork multiple times as we move between our fork and following upstream. When this is necessary, if possible un-archive the old fork and update it. If you’ve already made a new fork, delete the old copy of the fork before you move the new repo to edx-unsupported.

This may break some older version of Open edX. Some combination of copying branches between forks, renaming branches, and changing unsupported versions of Open edX would have to be done to keep things working. We opt not to take on this extra work by default though may do so under extenuating circumstances.

One such circumstance is if the previous fork is being used by a supported Open edX named release. In this case, one option would be to port any referenced branches in the old fork to the new fork before deleting the old fork.


We previously archived in place and move to this previously rejected alternative based on lessons learned in going through the deprecation process and major upgrades(Python 3, Django 2.x)


  • edx organization is no longer littered with unsupported/obsolete repositories.

  • GitHub search results within the edx organization do not include matches in archived repositories. This could decrease confusion, especially since repo descriptions are not included in search results.

  • Gemnasium monitoring may cease automatically (although this would need to be confirmed).

  • Pattern followed by Facebook, and thus might be familiar to others.

(see Rejected Alternatives for other options we considered).

Backward Compatibility

This proposal does not introduce any backward compatibility issues.

Reference Implementation

The Discussions Hackathon repository has been updated to conform to the Archive Steps.

Rejected Alternatives

There are a couple variations of this proposal that were originally discussed in Initial Archiving Discussions. Many of the steps of updating documentation and notifying the open source community are essentially the same; the major differences from the proposed process are outlined below.

Alternative 1: Archive In Place

Use Github’s archive feature and updated documentation to archive the repository in place.


  • Old code hasn’t moved so it can be easily found.

  • Old code can show up in searches to find historical context.

Reasons rejected:

  • Through some experience with this method, we’ve learned that it’s less valuable than we expected.

  • Being able to know whether code is alive or dead is really helpful when making major changes and if dead code can’t easily be filtered from searches it slows us down.

Alternative 2: Create Archive Branch

Move the code from the master branch to an archived branch, while leaving the repository itself within edx organization.


  • No need to create and maintain a new organization.

  • Gemnasium monitoring will cease automatically.

  • No help tickets to IT or DevOps are required.

  • This pattern was recommended on Anselm Hannemann’s blog, though it is not known how many organizations (if any) have adopted this process.

Reasons rejected:

  • Non-intuitive, and could be confusing for developers to understand the state of the code, as cloning the repo or viewing it on GitHub would show an empty repository (Note: this could possibly be improved by changing the default branch for the repository, but that might reintroduce the Gemansium monitoring issue).

  • It is unclear what the implications would be for any existing forks.

Change History


  • Original publication


  • Added steps for repositories that live in the edX org, but are forks of other, independent repositories


  • Updated to use GitHub’s archive capability.

  • Don’t ask the community about public repos in the edx org that are not a part of Open edX.


  • Decide to use the new edx-unsupported org for all archived repos. Old way we were doing things is now recorded as Alternative 1: Archive In Place.


  • Updated to provide more details around archiving the same fork multiple times.


  • Removed step of adding [ARCHIVED] to the repo name. Github’s “archive this repo” setting is now available and is a sufficient indicator.

  • Removed step of adding paragraph to README about what archiving means now that we use Github’s “archived” marker; the concept of an unmaintained repository and its dangers should be familiar to developers. Keep recommendation to add an explanation of why it was archived.

  • Removed openedx.yaml update steps, since the rest of the archive process is sufficient.