Can we do away with public SVN?

added component::internal services/service - git owner::anarcat parent::17202 priority::medium resolution::fixed severity::normal status::closed type::task labels

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

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.

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.

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.

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.)

Set all open tickets without a severity to "Normal"

Trac:
Severity: N/A to Normal

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

Trac:
Owner: erinn, nickm, Sebastian, weasel to tor-gitadm
Status: new to assigned

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

Trac:
Owner: tor-gitadm to irl
Reviewer: N/A to N/A
Sponsor: N/A to N/A
Status: assigned to accepted

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

Trac:
Owner: irl to tor-gitadm
Status: accepted to assigned

Trac:
Status: assigned to new

so i'd love to shutdown the SVN server (#17202 (moved)), 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 (moved)) and i can shutdown that darn machine already. :)

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

I'm ok with a variety of solutions here, so long as a few of the existing urls continue to work somehow. To make concrete progress, here is one proposed way forward:

/svn/projects/design-paper/
/svn/projects/articles/
/svn/projects/roadmaps/

For these, I propose we create a new website, as a static component, called svn.torproject.org, and we put these files on it. Then it can keep serving them just like before, and they're small and straightforward.

/svn/projects/presentations/

Moving these to media.tpo and adding a redirect rule would make sense. And if we don't want to wait for #23377 (moved) or other "revamp media.tpo" tickets, we could put them on the static svn.tpo component for now, and then a new media.tpo could intake them at its own pace.

All the other files, we can either rely on the archive.org snapshot that irl made (and delete them ourselves), or we can grab that snapshot and keep it squirreled away somewhere, maybe eventually destined for archive.tpo or museum.tpo or whatever.

Anarcat, shall I put together that proposed future svn.tpo set of static files, and we can proceed?

Replying to arma:

/svn/projects/presentations/

Moving these to media.tpo and adding a redirect rule would make sense. And if we don't want to wait for #23377 (moved) or other "revamp media.tpo" tickets, we could put them on the static svn.tpo component for now, and then a new media.tpo could intake them at its own pace.

Slightly better plan for this one, on the theory that I bet the static webserver rotations won't enjoy a bonus 500 megabytes of stuff that they didn't otherwise expect: mkdir an "outreach-material/svn-presentations" directory on media.tpo and dump them in. Then plan to do the rewriterule thing for that directory.

Ok, I've filed #32031 (moved) for getting this new static website component called svn.

Once we have it, we can populate it with the 500MB of files we want to rescue, and then point svn.tpo dns to it, and then we'll be nearly done here.

static component created, ready to populate. i don't think we can point svn.tpo there before internal and corp are migrated, however, as they live on the same FQDN (even if invisible).

@arma - do you need help with populating that static component or the redirections? should i take this on instead?

explicitely reassigning to you, in any case, to show the current known state, AFAIK.

Trac:
Owner: tor-gitadm to arma
Status: new to assigned

Replying to anarcat:

@arma - do you need help with populating that static component or the redirections? should i take this on instead?

explicitely reassigning to you, in any case, to show the current known state, AFAIK.

Yes please! Help would be great.

I made a README.html file in /srv/svn-archive.torproject.org/htdocs/ on staticiforme, but then I got distracted before writing the body of that file. So, yes please, tag you're it. :)

I made a README.html file in /srv/svn-archive.torproject.org/htdocs/ on staticiforme, but then I got distracted before writing the body of that file. So, yes please, tag you're it. :)

I've completed the README and pushed the result to the mirrors. I'm not sure what's left to be done here, but it sure looks like there's stuff missing from svn-archive.tpo when looking at svn.tpo... is that by design?

the next steps are therefore:

archive the rest of the repositories in /svn, which is /tor internally (if necessary?)
redirect https://svn.torproject.org/svn/ to https://svn-archive.torproject.org/svn/

The latter will not break internal or corp as they are in a different namespace (svn.tpo/internal/ and /corp, respectively).

Makes sense?

Trac:
Status: assigned to accepted
Owner: arma to anarcat

Replying to anarcat:

but it sure looks like there's stuff missing from svn-archive.tpo when looking at svn.tpo... is that by design?

Yes

the next steps are therefore:

archive the rest of the repositories in /svn, which is /tor internally (if necessary?)

redirect https://svn.torproject.org/svn/ to https://svn-archive.torproject.org/svn/

According to my original plan, we should add 4 RedirectRules, one for each of the directories in https://svn-archive.torproject.org/svn/projects/ and the rest can stay where it is as a 404.

I'm fine with somebody else wanting to make a competing plan, but this was the one I had in mind. :)

According to my original plan, we should add 4 RedirectRules

Right, sorry I misunderstood, will do!

I will also ship an svnadmin dump (equivalent of the svnrdump available on IA) with the archive, because I'm worried some source code might actually be lost forever if IA forgets about us. It seems that some repositories have not been migrated in there, so I think it's worth the extra space.

okay, i think we're done here. i've done a svnadmin dump of the entire repo, slapped that in the static component, tweaked up the README file and added a redirect from svn.tpo/svn to the new repo. eventually, that redirect will go away of course when we totally shutdown gayi, but this is good for now.

Trac:
Status: accepted to closed
Resolution: N/A to fixed

closed

mentioned in issue #15949 (moved)

mentioned in issue #17202 (moved)

mentioned in issue #32025 (moved)

mentioned in issue #32031 (moved)

Can we do away with public SVN?

Child items 0

Activity