Dear Andrew,
some work is currently ongoing in order to phase out CVS as version control tool [1] [2]. This is also a long term goal since a while [3]. The main dependency with CVS in our codebase regards rebuilding the *.apm package repository and only really affects openacs.org, as regular instances are not intended to act as repositories on their own.
Replacing the repository build is actually the easy part. More effort is to update the many documentation pages on the openacs.org website and in the acs-core-doc package so that they will refer to Git instead of CVS. This will include writing some new documentation detailing best practices, checking link references and so on. This is also ongoing. It would be nice if this was the chance to update other parts of the documentation as well and clean up obsolete pages (references to aolserver, ancient versions...) but I fear this would take us out of scope.
Concerning the GitHub mirror, this is actually "official", whatever this means and is actually what WU and other users get their code from. Commits are automatically translated from CVS to Git on a daily basis and is "safe for consumption". Because of its nature as a mirror, we currently cannot accept pull requests or move much of our workflows there, but we hope this will change in the near future.
Ciao
Antonio
[1] https://cvs.openacs.org/changelog/OpenACS?cs=oacs-5-10%3Aantoniop%3A20231018085957
[2] https://cvs.openacs.org/changelog/OpenACS?cs=oacs-5-10%3Aantoniop%3A20231018150037
[3] https://openacs.org/xowiki/openacs-todo
