Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+-
 Reporter:  nickm|  Owner:  anarcat
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:  #17202   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 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.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+--
 Reporter:  nickm|  Owner:  anarcat
 Type:  task | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #17202   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by anarcat):

 > According to my original plan, we should add 4 RedirectRules

 Right, sorry I misunderstood, will do!

 I will also ship an `svnadmin dump`
 ([https://stackoverflow.com/questions/27131309/difference-between-
 svnrdump-dump-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.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+--
 Reporter:  nickm|  Owner:  anarcat
 Type:  task | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #17202   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by arma):

 Replying to [comment:19 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:
 >
 >  1. archive the rest of the repositories in `/svn`, which is `/tor`
 internally (if necessary?)
 >  2. 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. :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+--
 Reporter:  nickm|  Owner:  anarcat
 Type:  task | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #17202   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by anarcat):

 * owner:  arma => anarcat
 * status:  assigned => accepted


Comment:

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

  1. archive the rest of the repositories in `/svn`, which is `/tor`
 internally (if necessary?)
  2. 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?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+--
 Reporter:  nickm|  Owner:  arma
 Type:  task | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #17202   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by arma):

 Replying to [comment:17 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. :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+--
 Reporter:  nickm|  Owner:  arma
 Type:  task | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #17202   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by anarcat):

 * owner:  tor-gitadm => arma
 * status:  new => assigned


Comment:

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

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+
 Reporter:  nickm|  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #17202   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by anarcat):

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

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+
 Reporter:  nickm|  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #17202   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by arma):

 Ok, I've filed #32031 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.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+
 Reporter:  nickm|  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #17202   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by arma):

 Replying to [comment:13 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 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.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+
 Reporter:  nickm|  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #17202   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by arma):

 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 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?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+
 Reporter:  nickm|  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #17202   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by anarcat):

 * parent:   => #17202


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+
 Reporter:  nickm|  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (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. :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+
 Reporter:  nickm|  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by irl):

 * status:  assigned => new


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+
 Reporter:  nickm|  Owner:  tor-gitadm
 Type:  task | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by irl):

 * owner:  irl => tor-gitadm
 * status:  accepted => assigned


Comment:

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

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #15948 [Internal Services/Service - git]: Can we do away with public SVN?

[Tor Bug Tracker & Wiki]

#15948: Can we do away with public SVN?
-+--
 Reporter:  nickm|  Owner:  irl
 Type:  task | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by irl):

 * owner:  tor-gitadm => irl
 * status:  assigned => accepted


Comment:

 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

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs