...
How many changes are in our fork that don’t have equivalents upstream?
No obvious equivalent upstream, many of these are probably worth submitting upstream PRs for:
https://github.com/edx/django-wiki/pull/48 (there may be an equivalent upstream mitigation, but it isn’t immediately obvious and should be verified)
https://github.com/edx/django-wiki/pull/34 (another user retirement change for GDPR compliance)
https://github.com/edx/django-wiki/pull/19 (but do we still need this?)
Probably upstream, but need verification:
https://github.com/edx/django-wiki/pull/28 (the changed code is no longer use, but make sure these characters are still allowed in URLs with the new code)
Other points that need care:
Our migration history is different from upstream; if moving back to an upstream release, we’d need to do something like add one last custom migration that would get us to a point in upstream’s migration history and then edit the history table
See https://github.com/edx/edx-platform/pull/6019 for a much earlier attempt at a similar update that was ultimately abandoned, but raised some good points to consider
Note that we made our fork over 8 years ago, so upstream has made many changes in the meantime that we’d need to review, probably meriting somewhat careful a11y and security reviews at the very least.