On Thu, May 11, 2023 at 11:34 AM Ruediger Pluem <rpl...@apache.org> wrote: > > > > On 5/11/23 12:27 PM, Ruediger Pluem wrote: > > > > > > On 5/4/23 10:34 AM, Ruediger Pluem wrote: > >> This is a formal vote on whether we should move our read/write repository > >> from Subversion to Git. > >> This means that our latest read/write repository will be no longer > >> available via svn.apache.org. It > >> will be available via Git at > >> https://gitbox.apache.org/repos/asf/httpd-site.git and > >> https://github.com/apache/httpd.git. > >> Github also offers the possibility to use a Subversion client: > >> https://docs.github.com/en/get-started/working-with-subversion-on-github/support-for-subversion-clients > >> > >> > >> [ ]: Move the read/write repository from Subversion to Git and leverage > >> the features of Github (for now Actions and PR). > >> [ ]: Move the read/write repository from Subversion to Git, but I don't > >> want to work with Github and I will only work with > >> what gitbox.apache.org offers. > >> [ ]: Leave everything as is. > >> > > > > > > After being open for one week I call this vote closed. Thank you for > > everyone who participated in this vote by > > either voting directly or voicing opinions on the subject. > > > > Result: > > > > Total number of votes: 16 > > > > [ ]: Move the read/write repository from Subversion to Git and leverage the > > features of Github (for now Actions and PR). > > > > 13 votes by jorton, ylavic, icing, gbechis, covener, humbedooh, rjung, > > jailletc36, jblond, gstein, rpluem, jim, fielding. > > > > [ ]: Move the read/write repository from Subversion to Git, but I don't > > want to work with Github and I will only work with > > what gitbox.apache.org offers. > > > > 0 votes. > > > > [ ]: Leave everything as is. > > > > 3 votes by manu, ivan, minfrin. > > > > Now that the vote is closed in favor of moving to Git what are the next steps? > Do we need to open an INFRA ticket to get this done? > Who will open it? > Is there any preferred point of time to do this?
FYI was thinking about this during the latest release -- I created a cwiki topic here to track any work that would be needed to move to read/write git: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311628229 I split it into a few sections based on timing. Currently I don't even think the release scripts are a blocker -- It would be much easier to run through it live on a low stakes release then trying to mock it up or make a bunch of blind changes. I think what's practical once we migrate might inform things like what we decide on how RTC works, including RTC exceptions. Maybe infra folks have some experience to share on the spectrum of options?
