Shut down SVN and decomission the host (gayi)
It is now 2015. Let us not have an SVN server running in 2016.
-- And is now 2020 and we are finally trying to shutdown this. Modifying this ticket to add the plan suggested by arma (with a few modifications by me).
(1) Freeze corpsvn (i.e. make it read-only), and make a full checkout of it somewhere, and have that accessible.
(2) Use Nextcloud for any other file people may need to save. Not move all the old files there, or at least not by default.
(3) Put together a strike team to look at the frozen corpsvn checkout, plus the frozen internalsvn checkout. Build a list of categories (HR, finance, grantwriting, grant manager, etc), and sort the files into these categories, discarding as many files as possible. Figure out where else people are storing these files currently (granthub? google docs? their hard drive?). Make a comprehensive plan for how files of each category should be stored, and who should have read or write access per category. For example, there's no reason that HR documents should go into the same database, or even the same storage service, as grant proposals. Process started in https://bugs.torproject.org/32273
Update, 2021: there's a "forest" of tickets surrounding this, as the "tree" was lost in the Trac migration, i'll try to reconstruct related tickets:
- SVN/host shutdown (this ticket)
-
#32273 - archive private information from SVN: determine what moves to where (presumably: "everything, to nextcloud") -
#15949 (closed) - shutdown SVN internal (done, but the repository is still on gayi, and not archived anywhere else) -
#32025 - stop using corpsvn and disable it (still open, blocked mostly on @sue iirc) -
#33537 (closed) - audit SVN accesses (led to the access control document and a private audit email with one minor remaining task, Message-ID: 871rq02rvt.fsf@curie.anarc.at, can probably be just closed) -
#15948 (closed) - public SVN retirement (done, moved to the static site mirror system (#32031 (closed)) and archive.org) -
#31686 (closed) - textile retirement (done) -
#40260 - actual proposal (next step, blocker)
-
It seems the next step here is to write a policy proposal to make sure we're all on the same page ("let's move to Nextcloud") and schedule a call with Sue to make sure it works in her workflow.