►
From YouTube: Sales Level Up: Moving from SVN to Git
Description
Quick video to educate SALs on SVN and moving from SVN to Git.
Presentation: https://docs.google.com/presentation/d/13bE9oKeqOdv05v6aqmY8K1KlN8VjKbSAkWaaQflDIsU/edit#slide=id.p
Docs: https://docs.gitlab.com/ee/user/project/import/svn.html
A
Hi,
my
name
is
Sami
Obadiah
and
I'm
part
of
the
product
marketing
team
at
github,
and
today
we're
gonna
talk
about
moving
from
SVN
to
get
so
first
things.
First,
what
is
SVM
so
as
VN
was
founded
in
about
in
2000
by
CollabNet
and
is
now
developed
as
a
part
of
the
Apache
foundation
similar
to
get
it
is
a
popular
version,
control
systems.
Albert
it's
been
passed
in
Haiti
today.
Only
about
16%
of
developers
use
it
as
per
a
research
by
Stack.
A
So
what
are
the
main
differences
between
SVN
and
git?
I?
Think
the
main
difference
lies
in
the
architecture
and
its
handling
of
large
binary
files.
In
fact,
most
of
the
users
or
organizations
that
still
do
use
SVM
continue
to
use
it
for
its
convenience
with
large
binary
files.
We
also
support
large
binary
files
in
a
since
2015
we'll
talk
about
that
later,
but
the
organization
still
consider
SVM
to
be
handling
a
large
binary
files,
a
lot
better
from
an
architecture
point
of
view.
A
Svn
is
a
centralized
architecture
where
every
change
is
maintained
on
a
central
server.
The
benefit
of
this
is
that
synchronization
is
much
better.
However,
if
it
is
not
set
up
adequately
for
high
availability
and
disaster
recovery,
such
a
centralized
server
can
tend
to
be
a
liability,
as
it
may
or
may
not
crash,
and
exactly
when
you
require
it
so
compared
to
it.
Git
is
a
distributed
repository.
It
ensures
that
code
can
be
pushed
and
committed
locally
and
independently
of
the
main
repository
this
makes
versioning
lighter
on
the
network
traffic.
A
A
Ask
a
developer
today
about
subversion
and
be
sure
to
be
faced
with
this
statement.
Possibly
many
of
the
young
developers
haven't
even
heard
of
SVN
today.
So
why
would
a
cast
want
to
move
away
from
a
sphere?
So
there
are
three
key
reasons
that
we
see.
The
first
is
a
majority
of
their
blockers
today,
use
get
as
per
the
Stack
Overflow
survey
that
I
mentioned
earlier,
close
to
90
percent
of
developers,
use
get
all
the
cool
kids
use
it.
All.
The
young
kids,
of
course
use
it.
A
So
it's
a
lot
easier
to
attract
and
retain
talent
for
kids
compared
to
subversion,
which
is
now
an
increasingly
rare
talent
to
finds
so
currently,
majority
of
the
workforce
is
distributed,
as
we
all
know,
with
more
than
one
location
or
office
for
the
workforce.
In
such
a
scenario,
the
development
experience
would
be
degraded
if
the
development
platform
is
network
intensive,
which
is
the
case
with
SVM
and
makes
pushes
and
commits,
take
too
long,
as
it
is
the
case
with
SVM
as
well.
A
A
Anecdotally
I've
heard
that
it
takes
about
three
minutes
per
push
which
does
not
really
serve
the
purpose
of
requiring
frequent
pushes
to
the
rep
repo,
which
is
good
development
practice
get,
on
the
other
hand,
makes
branching
and
merging
a
lot
easier
with
simultaneously
multiple
developers
being
able
to
work
on
the
same
piece
of
code
and
handling.
Merge
conflicts
is
a
lot
easier
in
git.
A
So,
let's
take
an
example
of
Waldheim,
which
is
a
reference
customer
for
gate
lab
so
way
back
in
2014.
They
actually
faced
many
many
challenges
with
their
development
platform
and
they
had
to
actually
set
up.
Many
integrations
with
different
tools
like
garrett
SVN
jenkins,
amongst
a
lot
of
other
tools
that
they
had
to
not
only
set
up,
but
also
maintain
each
time
they
required
a
new
repo
nest
VN.
A
In
their
words,
it
took
about
one
to
two
weeks
to
get
us
our
source
code,
repo,
using
a
separate
tool
for
code
review,
of
course,
did
not
encourage
developers
to
use
it.
With
short
in
the
usage
metrics,
only
10
to
20
of
the
3,000
plus
developers
use
the
quarter
of
your
tool
once
they
started
using
git
lab
SCM
for
ease
of
use
within
six
months
they
had
about
thousand
developers
on
the
platform.
A
Sem
and
code
review
have
become
so
easy
that
that
now
today
they
have
three
thousand
plus
users
active
users,
Orkut
lab,
and
they
are
not
only
using
get
lab
for
SEM,
but
they
also
use
a
lot
of
other
stages,
so
you
can
read
their
entire
story
on
this
link
below
so
do
we
support
a
customer
moving
from
SVN
to
get
laughs?
Yes,
we
do.
There
are
two
key
approaches.
The
first
is
that
a
customer
would
need
to
maintain
both
repositories
mirrored
with
each
other.
A
We
use
a
third-party
tool
called
sub,
get
which
is
paid
for
enterprises.
Both
repos
are
synced
frequently,
and
this
helps
to
smoothen
migration
issues.
The
second
approach
is
a
Catawba
migration,
where
a
customers
can
translate
all
of
their
data
history
and
also
details
to
get
lab.
They
move
to
the
endings
move
to
get
like
completely
post
migration.
This
is
a
recommended
approach,
especially
for
smaller
projects.
A
What
are
the
key
objections
you
may
face
when
trying
to
migrate,
SVN
customers?
The
biggest
objection
today
is
that
the
large
binary
file
handling
in
in
git
is
not
supported,
or
it's
not
good
enough.
While
this
was
traditionally
true,
it's
not
true
anymore
hit
lab
has
been
supporting
large
file
storage
since
2015.
This
requires
an
embedded
install
with
in
his
lab,
as
well
as
an
installation
of
an
LFS
client
on
the
local
system.
This
experience
is
now
being
improved
with
the
partial
clone
feature
which
does
not
require
separate
installs.
A
It's
just
a
command
line
configuration
at
the
moment.
So
to
summarize,
we
do
support
large
binary
files
and
we
continue
to
improve
it,
which
we
will
see
in
the
next
slide.
So
what
is
the
future
hold,
especially
in
the
context
of
Sdn
to
get
we
continue
to
want
to
make
get
friendly
for
designers,
data
scientists,
animators
and
so
on?
Who
are
the
people
who
actually
operate
a
lot
lab
lot
with
large
large
binary
files?
A
They
would
benefit
from
having
code
review
like
processes,
mergers
and
diffs,
and
from
having
pretty
much
everything
that
we
we
have
four
caught
in
the
repository
right.
They
would
like
to
have
the
same
experience
for
animations,
designs,
textures
and
so
on.
So
with
that
we're
making
a
lot
of
improvements
to
make
the
large
file
experience
excellent
to
make
sure
that
it
works
out
of
the
box
as
well
as
without
specialized
configuration
or
hardware.
A
So
to
summarize,
SVN
is
not
cool
anymore,
although
almost
all
new
projects
are
being
started
and
get
across
various
organizations.
Why
would
an
organization
want
to
maintain
two
different
version
control
systems
when
they
can
seamlessly
migrate
and
maintain
only
one
so
get
is
almost
a
de
facto
standard
today
everyone
needs
get
and
get
lab
is
one
of
the
leading
providers
for
version
control
and
collaboration
music.
Thank
you.