[tor-bugs] #17202 [Internal Services/Tor Sysadmin Team]: Shut down SVN and decomission the host (gayi)

Tor Bug Tracker & Wiki blackhole at torproject.org
Wed Feb 12 14:17:12 UTC 2020


#17202: Shut down SVN and decomission the host (gayi)
-------------------------------------------------+-------------------------
 Reporter:  nickm                                |          Owner:  gaba
     Type:  defect                               |         Status:
                                                 |  assigned
 Priority:  Medium                               |      Milestone:
Component:  Internal Services/Tor Sysadmin Team  |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tpa-roadmap-march                    |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Description changed by gaba:

Old 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

New 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

--

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17202#comment:14>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list