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

added component::internal services/tor sysadmin team owner::gaba priority::medium severity::normal status::assigned tpa-roadmap-june type::defect labels

Trac:
Owner: N/A to nickm
Status: new to assigned

Set all open tickets without a severity to "Normal"

Trac:
Severity: N/A to Normal

I am not actually working on these tickets, so they shouldn't be assigned to me.

Trac:
Owner: nickm to N/A

what's the next step with SVN? we discussed this briefly in Stockholm, and it's unclear to me what the consensus was. it seems it's still in use by some people, or at least some parts of it are still in use, according to timestamps:

root@gayi:/srv/svn.torproject.org# ls -alu repositories/*/db/current
-rw-rw-r-- 1 www-data www-data  5 aoû 16 13:02 repositories/corp/db/current
-rw-rw-r-- 1 www-data www-data  5 aoû  9 05:09 repositories/internal/db/current
-rw-rw-r-- 1 www-data www-data 14 aoû 16 16:29 repositories/tor/db/current
-rw-rw-r-- 1 www-data www-data  5 aoû 15 17:51 repositories/vidalia/db/current

that is, all of the repositories have been access in the last two weeks, and the tor one was accessed in the last two days. that said, the latest commit on some of those is much older:

root@gayi:/srv/svn.torproject.org# ls -al repositories/*/db/current
-rw-rw-r-- 1 www-data www-data  5 aoû 16 13:02 repositories/corp/db/current
-rw-rw-r-- 1 www-data www-data  5 aoû  4 03:58 repositories/internal/db/current
-rw-rw-r-- 1 www-data www-data 14 mai  8  2015 repositories/tor/db/current
-rw-rw-r-- 1 www-data www-data  5 mar 20  2011 repositories/vidalia/db/current

ie. the corp and internal ones have been written two in the last two weeks, but the tor and vidalia ones have been idle for years (4 and 8 years, respectively).

what we could do is archive (move aside) the last two (tor and vidalia) and see what breaks. then we need to figure out what to do with the corp and internal repos. in #17201 (moved), it seems the plan is to move to git, so I guess that would be the next step?

who uses that stuff anyways?

Trac:
Reviewer: N/A to N/A

update: it seems the proper tickets are #15948 (moved) (public) and #15949 (moved) (private), let's followup there and keep this ticket for the decommissioning of the host (gayi).

Trac:
Summary: Shut down SVN to Shut down SVN and decomission the host (gayi)

gayi is on textile, which we want to decomission, so mark that relation

Trac:
Parent: N/A to #31686 (moved)

Ok, I added #32025 (moved), for the third prong of this task: retiring corpsvn.

so svn internal was "shutdown" today (as in: made inaccessible). the public SVN still needs to be archived (#15948 (moved)) and a decision needs to be made about corp SVN before its shutdown (#32025 (moved)).

because SVN internal wasn't archived in any significant way, gayi should NOT be destroyed before that data is somewhat sorted through, same with corp SVN. i have opened #32273 (moved) to followup on that task.

i've disconnected this ticket from the textile decom (#31686 (moved)) because I don't want to wait for this project to complete before i turn off this machine. this and chiwui/check.tpo are the only two VMs left on the box...

Trac:
Parent: #31686 (moved) to N/A

Trac:
Keywords: N/A deleted, tpa-roadmap-march added

I will help bottomline it.

Trac:
Owner: N/A to gaba

Trac:
Description: It is now 2015. Let us not have an SVN server running in 2016.

to

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

Trac:
Description: 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

to

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

Trac:
Keywords: tpa-roadmap-march deleted, tpa-roadmap-april added

We are still waiting on #33537 (moved)

Trac:
Keywords: tpa-roadmap-april deleted, tpa-roadmap-june added

mentioned in issue #31686 (moved)

mentioned in issue #32025 (moved)

mentioned in issue #32273 (moved)

mentioned in issue #33537 (moved)