Opened 4 years ago

Last modified 2 days ago

#15948 new task

Can we do away with public SVN?

Reported by: nickm Owned by: tor-gitadm
Priority: Medium Milestone:
Component: Internal Services/Service - git Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #17202 Points:
Reviewer: Sponsor:

Description

According to https://svn.torproject.org/cgi-bin/viewvc.cgi/Tor/ , it's been at least six months since anything changed on the public SVN repository.

Most of the repositories there have been migrated to git.

We could migrate all the rest to git (if appropriate) or archive them (if appropriate), and turn off the lights on public svn.

Child Tickets

TicketStatusOwnerSummaryComponent
#4929closedtor-gitadmmigrate svn to gitInternal Services/Service - git

Change History (12)

comment:1 Changed 4 years ago by Sebastian

I wonder if we should turn it into a public directory of files for some parts of it. Some can just go because they have already been moved to git. Migrating dead repos to git is no fun, but deleting code also doesn't make me happy

comment:2 Changed 4 years ago by atagar

Migrating dead repos to git is no fun, but deleting code also doesn't make me happy

Agreed. Maybe just switch svn to be read-only? This would prompt us to migrate things we need to git if/when we need to touch them.

comment:3 Changed 4 years ago by nickm

I would happily volunteer to help migrating a bunch of not-yet-migrated stuff if that's what we decide to do; it is pretty easy to script.

One reason I'm suggesting migration or archiving here is that our list ofSVN repositories is largely invisible; I bet a lot of folks who look over gitweb from time to time have forgotten all the stuff that was in our SVN.

comment:4 Changed 4 years ago by atagar

One reason I'm suggesting migration or archiving here is that our list ofSVN repositories is largely invisible; I bet a lot of folks who look over gitweb from time to time have forgotten all the stuff that was in our SVN.

If it's unused and untouched I'd argue that's a good thing. Less is more - adding clutter to our gitweb listing will just make our ecosystem even tougher to navigate for newcomers.

comment:5 Changed 4 years ago by arma

I looked over https://svn.torproject.org/svn/ and so far as I can tell, everything outside https://svn.torproject.org/svn/projects/ is basically obsolete.

(blossom is interesting in an archaic archeology sort of way.)

Inside svn/projects/, I find https://svn.torproject.org/svn/projects/design-paper/ still useful,
and we still link people to https://svn.torproject.org/svn/projects/presentations/ and https://svn.torproject.org/svn/projects/articles/ and https://svn.torproject.org/svn/projects/roadmaps/

But it looks like those are all reasonably self-contained. Also, as people point out above, they are read-only at this point. (I think Andrew was committing to projects/presentations/ relatively recently, but he has of course stopped that since.)

comment:6 Changed 22 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:7 Changed 13 months ago by irl

Owner: changed from erinn, nickm, Sebastian, weasel to tor-gitadm
Status: newassigned

Setting owner to tor-gitadm as the owners that are set are not working on this currently. (Please correct me if I'm wrong).

comment:8 Changed 11 months ago by irl

Owner: changed from tor-gitadm to irl
Status: assignedaccepted

I believe we are closer to turning off public SVN, but need to have some redirects in place for articles, presentations and design paper.

svn.tpo will be served from the static mirrors but we'll have RewriteRules in place to send requests off to the new homes for these files. Some may go to media.torproject.org.

For everything that is not in the set of commonly linked resources, there is the full archive dump now uploaded to archive.org: https://archive.org/details/tor_public_svn

comment:9 Changed 5 months ago by irl

Owner: changed from irl to tor-gitadm
Status: acceptedassigned

I don't appear to be making progress with this currently, nor do I expect to this month at least.

comment:10 Changed 5 months ago by irl

Status: assignednew

comment:11 Changed 5 weeks ago by anarcat

so i'd love to shutdown the SVN server (#17202), can I help with this in some way?

it seems all that's left to be done here is move some stuff (projects/design-paper, projects/presentations and projects/articles/ and projects/roadmaps/) to media.tpo and "add redirects" (which probably would mean "turn svn.torproject.org in a static website").

then we fix the internal SVN stuff (#15949) and i can shutdown that darn machine already. :)

comment:12 Changed 2 days ago by anarcat

Parent ID: #17202
Note: See TracTickets for help on using tickets.