#15949: Can we migrate internal SVN to a document store, wiki, or set of git repositories? ---------------------------------------------+----------------------------- Reporter: nickm | Owner: tor-gitadm Type: defect | Status: | needs_information Priority: Medium | Milestone: Component: Internal Services/Service - git | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: #17202 | Points: Reviewer: | Sponsor: ---------------------------------------------+-----------------------------
Comment (by arma): Note that I'm going to treat this ticket as being what it says it's about in the ticket description -- svninternal, not corpsvn. I believe I am the only user of svninternal at this point, either reading or writing. And I'm fine stopping my use of it if it simplifies things for others. So I believe that we can turn it off as a service, so long as we keep the files around for the future "sorting and filing and discarding" exercise that we're going to need to do. When we get to that sorting step, we might decide to dump the files into nextcloud en masse to start, or we might decide to do some triaging on them first and only import the ones we want to import. We should stick the files somewhere and open a new ticket for that triaging, once we turn off the svninternal service. Also, when we do turn off svninternal, we can disable the tor- svninter...@lists.tpo list which is where commits get sent currently. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15949#comment:14> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs