Le jeudi 5 avril 2018, 00:42:57 CEST sebb a écrit : > On 4 April 2018 at 23:34, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > there is a little misunderstanding: I'm not talking about fully switching > > from svn to git > > I'm talking about keeping svn as canonical repository but adding a > > read-only git mirror like done on many svn repositories [1] > > The JIRA said otherwise... yes, external people nowadays just think "switch to Git" et voilà. But I have a long experience on Maven (more than 5 years to to the near full migration [2]), and I know that it does not happen like this: there are steps to have the team find advantages along the journey, letting time to learn and do progressive adoption This is how I naturally transformed the initial typical request: into the typical first step
[2] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration > > > This does not change anything to the host configuration, but adds a GitHub > > mirror for external people to contribute through GitHub Pull Requests, > > which are so much easier to submit than svn patch attached to a Jira > > issue: this will give a chance to get more contributions. > > OK, fine. > > > Later on, we can decide to switch to Git (with gitwcsub acting like > > currently svnwcsub), but that will be another choice to do in another > > time. > > That will be a lot of work. We'll see it later: for sure, it's more impact, then requires to be prepared. svn 2 git mirror is a good first step, that is required if we do the next steps or not > > > Regards, > > > > Hervé > > > > [1] http://git.apache.org/ > > > > Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit : > >> On 4 April 2018 at 07:09, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > >> > What about creating a Git/GitHub svn2git mirror for > >> > projects.apache.org? > >> > This would be our first Git repo for community/comdev: I don't know > >> > which > >> > prefix we should use... > >> > > >> > Any objection? > >> > >> What are the benefits to using Git over SVN? > >> Do they outweigh the costs? > >> Who gets the benefit, and who pays the costs? > >> > >> == > >> > >> Note that projects.a.o actually updates its own code repo using a role > >> account. I don't know if that can be done in Git. > >> It took quite a bit of work to ensure that the updates did not result > >> in a locked workspace. > >> (This used to happen regularly at the beginning) > >> > >> Also, the projects.a.o and reporter.a.o hosts share the same VM. > >> They would need to move together. > >> > >> And of course the VM puppet definition will need to be updated. > >> It's more complicated than a simple pubsub operation. > >> > >> > Perhaps we can do the same for the 3 other locations in svn > >> > https://projects.apache.org/project.html?comdev-community_development > >> > > >> > Regards, > >> > > >> > Hervé > >> > > >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit : > >> >> Vincent Tuybens created COMDEV-288: > >> >> -------------------------------------- > >> >> > >> >> Summary: Request "Projects Directory" migration to GIT > >> >> > >> >> Key: COMDEV-288 > >> >> URL: https://issues.apache.org/jira/browse/COMDEV-288 > >> >> > >> >> Project: Community Development > >> >> > >> >> Issue Type: SVN->GIT Migration > >> >> Components: Projects Tool > >> >> > >> >> Reporter: Vincent Tuybens > >> >> > >> >> Dear all, > >> >> > >> >> is it possible for you to plan SVN to GIT migration for "Projects > >> >> Directory" project ? > >> >> > >> >> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apach > >> >> e.o > >> >> rg/ {color}] > >> >> > >> >> Thank you, > >> >> > >> >> Regards. > >> >> > >> >> > >> >> > >> >> -- > >> >> This message was sent by Atlassian JIRA > >> >> (v7.6.3#76005) > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> >> For additional commands, e-mail: dev-h...@community.apache.org > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> > For additional commands, e-mail: dev-h...@community.apache.org > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> For additional commands, e-mail: dev-h...@community.apache.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
