TBH: I tried to initiate the discussion two years ago and there was no reaction: https://lists.apache.org/thread.html/4ada22cf37faf7e865e4d33451fe14d34d67846824a86dfdbb150d9e%40%3Coak-dev.jackrabbit.apache.org%3E <https://lists.apache.org/thread.html/4ada22cf37faf7e865e4d33451fe14d34d67846824a86dfdbb150d9e@%3Coak-dev.jackrabbit.apache.org%3E>, but feel free to raise any concerns in this thread.
> On 19. May 2021, at 09:32, Julian Reschke <[email protected]> wrote: > > Am 19.05.2021 um 09:24 schrieb Konrad Windszus: >> Hi, >> in >> https://lists.apache.org/thread.html/8ea0d827d9e8488183648f2364ecd4e178b6d82e03193735aae6b5cd%40%3Coak-dev.jackrabbit.apache.org%3E >> we discussed moving to Git. After the successful migration of FileVault to >> Git we should tackle Oak as well. >> I am volunteering to trigger the actual work (mostly on ASF INFRA side). I >> hereby propose to >> >> 1. migrate the SVN repository at >> https://svn.apache.org/repos/asf/jackrabbit/oak/ to a Git repository named >> "jackrabbit-oak" >> 2. migrate GitHub SVN mirror at https://github.com/apache/jackrabbit-oak to >> mirror the new native Git repo (at Gitbox) >> 3. change the main branch name from "trunk" to "main" >> 4. make the SVN repository read only >> >> Vote is open for 72 hours. >> [ ] +1, migrate Oak to Git >> [ ] 0 >> [ ] -1, because... >> >> >> The actual work is tracked in https://issues.apache.org/jira/browse/OAK-9440. > > FWIW, this *really* needs suport from those who currently do the Release > Management, because it affects them more than others. > > As such I would not recommend to have a vote until this has been > discussed among the current RMs. > > Best regards, Julian
