Page Comparison

This proposal is being created as part of 

...

1. Update the README.rst file in the repository to state that it is deprecated and that the repository may depend on out-of-date libraries with security issues.
2. If the repository has a openedx.yaml file, add "obsolete:True" to that file.
3. Transfer ownership of the repository to edx-deprecated. See How To Transfer a Github Repo From a Personal Account to edX for an idea of what these steps may look like; a dedicated How-to will be created for the process once this proposal is approved.
4. Send an email to edx-code@googlegroups.com notifying the openedx community about the change.
5. If transferring a repository to edx-deprecated does not automatically cause Gemnasium to stop reporting on it, create a Devops ticket for this additional piece of work.

...

Leave all repositories within the edx organization, and utilize the "obsolete" flag in openedx.yaml to indicate deprecated repositories. For now, Devops manually removes obsolete repositories form Gemnasium, but in the future automation could be added.

...

1. Update the README.rst file in the repository to state that it is deprecated and that the repository may depend on out-of-date libraries with security issues.
2. Add "obsolete: True" to openedx.yaml (creating the file if necessary).
3. Send an email to edx-code@googlegroups.com notifying the openedx community about the change.
4. Create a DevOps ticket to change the status of the repo to "non-monitored" in Gemnasium.
   1. In the future, automation could be added that uses Gemansium APIs to update the monitored status based on the value of "obsolete" in openedx.yaml.

...