Is switching from git to svn justified in 2015?

Question

git

We have a development team of 4 people. We are developing in python + js. We work in a government office. We maintain version control in git + local gitlab.
Our head of department implements CI, the choice fell on jenkins.
So, he suggests keeping new projects in svn (and not in git, in which we work).
He explains his choice by the fact that:
In svn, not a single commit is stored locally.
It will not pull to lead 2 systems at once: both on git and on svn.
Grannies work for us, which is hard to master git (but they don’t use svn at the moment)
. I didn’t catch the logic of the transition. The question is, are there any arguments in 2015 to start a new project in svn?
(Except: the boss said so)

Answer 1

As an active SVN user, I see no reason to start a new SVN project in 2015, unless there are ideological reasons. Moreover, since you have already mastered Git and suits everyone.

Answer 2

about a year ago, the whole department moved from svn to git. svn is an older and architecturally poor system :)

Answer 3

It seems to me that it doesn’t really matter if you don’t use GitFlow ( sitedev.ru/git-flow/) , you may not even notice the transition)
The boss should first of all focus on you, and not choose a tool that is more convenient for you. But this is in an ideal world.