►
From YouTube: Atlassian and Git LFS - GitHub Universe 2015
Description
Steve Streeting discusses the history of Atlassian's interest in binary files and git, and their contributions to Git Large File Storage (LFS).
About GitHub Universe:
Great software is more than code. GitHub Universe serves as a showcase for how people work together to solve the hard problems of developing software.
For more information on GitHub Universe, check the website:
http://githubuniverse.com
A
The
next
presenter
I
want
to
go
ahead
and
bring
up
is
Steve
streeting
and
he
is
from
a
lassie
and
he
grew
up
actually
on
the
island
outside
of
France
on
a
tiny
island.
But
he
actually
does
not
speak
French
very
fascinating
things
about
him
and
he
also
plays
the
drums.
I
think
I'm,
going
to
start
a
little
band
with
my
speakers,
so
without
further
ado,
go
ahead
and
welcome
up
Steve.
B
B
Also,
if
you
were,
if
you're
keeping
tabs
on
getting
at
first,
the
the
latest
update
release
that
the
big
feature
update
was
done
recently,
which
is
now
at
1.0.
There's
a
lot
of
features
in
there,
which
you
can
blame
on
me.
So
you
know
you
know
who
to
to
ping.
If
there's
an
issue
I'm
going
to
talk
a
little
bit
about
a
couple
of
those
in
a
few
minutes,
but
some
of
you
might
be
wondering
why
why
lasting
is
is
contributing
to
a
get
of
projects
and
why
I'm
doing
it?
B
So,
in
order
to
explain
that
I'm
just
gonna
take
you
back
in
time
a
little
bit
because,
15
years
ago,
I
started
an
open
source
called
ogre,
which
was
a
3d
engine
still
is
a
3d
engine
is
still
going
right
now
and
it
was
used
to
power,
games,
simulations
training
projects
and
all
kinds
of
things.
Some
of
those,
the
one
was
promised
quite
pretty
one
and
torchlight.
If
anyone's
ever
played
that
and
serious
that
that
was
my
engine.
B
That
was
powering
that
so
I
work
with
a
bunch
of
teams
that
worked
on
on
games
and
simulations
and
worked
was
Ray
large
files.
Things
like
you
know,
textures
model
files,
animations,
video
and
sound,
so
I
gained
an
appreciation
of
the
kind
of
issues
they
had
was
working
with
version
control
with
those
sorts
of
files
and
at
the
time
it
was.
You
know,
subversion,
perforce
and
even
alien
brain.
If
you've
heard
of
that
one,
probably
nobody
but
yeah.
That
was
an
interesting
one.
B
So,
six
years
ago,
I
like
a
lot
of
developers
like
pretty
much
everybody
I
got
into
dbcs
and
I
loved
it.
You
know
I
love
dbcs,
I
loved
it.
So
much
that
I
actually
made
a
graphical
application
called
sorcery,
which
I'm
wearing
a
t-shirt
off
right
now.
That
was
really
just
a
tool
for
me
original
and
is
one
is
something
that
worked.
The
way
that
I
thought
things
should
work
but
actually
became
a
lot
more
popular
than
I
expected
and
that
eventually
brought
me
to
a
classroom.
B
So,
even
though
I
focused
on
on
source
control
in
the
last
few
years,
I've
always
had
this.
This
thing.
In
the
back
of
my
mind
that
you
know
I
like
large
files,
I
like
projects
to
use
large
files.
I've
done
that
a
lot,
but
it
doesn't
really
work
with
my
my
favorite
source
control
system.
So
what
are
we
gonna
do
about
that?
So
atlassian
was
also
hearing
from
customers
as
well.
B
So
what
we
didn't
know
was
github
was
having
the
exact
same
thoughts
as
we
were
having
at
exactly
the
same
time
and
we're
having
the
exact
same
conclusions
that
we
had.
We
do
nothing
of
this.
Obviously
neither
did
they,
so
you
know
we
would
be
bringing
away
on
on
our
own
on
our
own
issue
marine
projects
and
what
happened
was
Gail
Boston
came
up
was
Gail
FS.
We
came
up
with
something
called
git
log
and
they
had
very,
very
similar
ideas,
so
we
both
decided
that
we
needed
a
new
tool.
B
We
didn't
do
this
lightly.
I
mean
we
look
to
other
systems
that
are
out
there
already
wheeler
to
get
media,
which
we
thought
was
just
abandoned.
We
didn't
know
get
over
doing
anything
more
about
it,
but
we
felt
you
know
there
was
a
need
for
something
that
was
very
easy
to
configure
something
that
works
very
easily
out
of
the
box,
something
that
was
designed
for
teams.
It
wasn't
just
trying
to
do
things
to
all
people.
B
It
was
designed
for
specifically,
teams
were
working
with
large
files
and
we
wanted
to
make
it
open
source
because
you
know
as
we're
Exedra
we
want
to
interoperate
with
the
gay
community.
We
want
it
to
be
as
easy
to
access
and
easy
to
use
and
adapt
as
get
is,
and
we
just
want
to
you
know,
labreche
a
community
and
we
both
decided
to
write
it
in
go.
B
So
we
both
decided
that
go
is
a
very
good
system
for
writing
this
in
because
it
created
standalone
binary
is
a
very
easy
to
deploy
their
very
fast
and
it's
a
nice
language.
It's
a
modern
language
and
that's
that's
useful
for
getting
people
on
board.
If
you're
doing
an
open
source
project,
you
want
as
many
people
to
better,
join
it
and
be
productive
as
possible,
and
we
both
decided
that
we
would
announce
what
we
were
doing.
I
get
merged
earlier
this
year
and
we
both
came
up
with
these
sort
of
fairly
abstract
non-committal
titles.
B
For
our
talk,
so
we
could,
we
were
gonna
to
you,
know,
reveal
what
we
were
doing
and
it
was
only
in
the
bar
the
night
before
we
both
had
a
both
had
to
talk
them
the
same
day,
Ashley
I
think
they
were
straight
after
each
other
and
I
in
the
bow
is
I.
Are
we
doing
this
and
you
know
we're
doing
that
as
well?
B
Really,
okay
and
then
we,
when
we
discovered
that
actually
we
had
all
the
exact
same
thoughts
and
we're
doing
almost
exactly
the
same
thing
so
yeah
that
was
that
was
an
interesting
week.
We
decided
pretty
quickly
that
you
know
there's.
There
was
no
point
us
creating
yet
another
tool.
You
know
if
we
already
had
made
the
right
decision
to
create
a
little
there's,
no
point
not
creating
two.
At
the
same
time,
you
know
to
new
one,
especially
because
it
were
very
so
so
very
similar,
so
I,
don't
she
lost
a
ok,
you
can
actually
fight.
B
We
are
we
open
sourced
our
version
anyway,
you
can
find
it
on
github
under
atlassian
/
kitlope.
If
you
ever
want
to
see
it's
kind
of
archived
now,
because
I'm
posting
all
of
the
features
that
we
had
it
across
the
gala
fest.
So
what
we
had
it
as
well
as
having
a
lot
of
commonality,
we
found
that
there
were
certain
strengths
that
get
fs
hadn't
certain
strengths
that
what
we
vote
on
git
log
had
so
it
made
sense
just
from
bring
them
together
and
just
have
all
the
features
in
one.
B
So
a
lot
of
things
that
you'll
see
in
in
that
slide
that
I
I
mentioned
before,
about
the
features
that
we've
added.
Those
came
too
early
from
get
lawman.
I've
just
affect
a
report
on
Norcross
and
that's
been
great
because
if
I
look
at
it,
I
looked
at
the
features
again,
obviously
as
I
portal,
the
McGraw
and
having
the
second
bite
of
the
cherry
when
you're
writing
a
feature
means
it
ends
up
being
better.
B
So
I
actually
like
the
version
that
I
couldn't
get
Gail
FS
better
than
I
like
the
one
by
did
before
so
that's
good,
so
one
of
them
is
being
able
to
fetch
recent
objects
when
you're
doing
again,
lfs
fetch.
So
by
default.
When
you
do
a
fetch
in
NFS,
it's
downloading
files,
which
you
need
to
fulfill
your
current
head
and
that's
fine,
but
then,
if
you
then
want
to
switch,
goes
to
a
different
branch.
B
If
you
don't
have
the
files
that
are
required,
all
the
large
files
that
are
required
for
that
branch,
then
it
will
go
ahead
and
download
them
on
demand,
which
is
which
is
fine,
but
it
does
mean
you're
wasting.
Potentially,
when
you
check
out
that
branch
and
that
excuse
and
as
intuitive
as
you
would
think,
because
check
out
doesn't
know
what
you
mean
downloading
everything
so
I
early.
This
feature
called
fetch
recent
and
that's
configurable
in
me
and
I
get
complete
and
it
will
basically
go
and
find
recent
branches
that
have
been
updated.
B
Maybe
there
other
people's,
maybe
they're
yours
and
it
just
means
the
it
will
go
and
grab
those
and
download
them
so
that
when
you
switch
branches
you
can
also
matter.
You
quickly
get
that
that
content
and
you
don't
have
to
wait
for
the
download.
It
can
also
look
at
recent
commits
on
those
branches.
So
if
you
want
to
look
at
dis,
you
know
recent
changes
diff
between
things.
You
can
see
those
as
well.
This
is
all
configurable.
You
can
set
the
window
that
it
looks
for
and
that's
that's
used
when
you
can
do
this.
B
But
you
can
actually
configure
this
in
the
indicate
config
as
well.
So
if,
for
example,
this
was
my
repository,
I'd
have
the
listings
like
sounds
and
textures
and
things
may
we
just
skip
those
and
only
give
me
the
models
and,
in
this
case
also
excluded.
Another
sub
folder
of
models
of
us
only
get
the
the
sort
of
characters
and
enemies
model,
so
I
care
about.
Sorry.
For
a
modeler
working
on
those
sorts
of
models,
then
then
I
would,
I
would
only
download
what
I
need,
which
is
which
is
good,
there's
more
stuff
in
the
pipeline.
B
I'm
currently
working
on
a
prune
option,
which
mostly
what's
left
of
that,
is
to
do
immense
amounts
of
testing,
because
I'm
so
paranoid,
that's
about
deleting
things
which
you
don't
need
anymore.
So
you
can
keep
your
label
claim
as
slim
as
possible
over
time.
Also,
the
the
API,
the
new
API
you
put
in
1.0
I
I,
want
to
make
a
native
SSH
version
of
that
for
people
who
want
to
use
that
I'd
also
like
to
get
involved
in
the
resuming
of
transfers
and
maybe
deduplication
and
locking,
which
is
a
horrible
sort
of
subject
for
dbcs.
B
But
unfortunately,
when
it
comes
to
completely
unmoral
files.
You
really
don't
want
the
situation
where
accidentally
two
people
create
two
different
versions
of
the
same
file
and
absolutely
cannot
merge
at
the
end
of
it
and
someone
has
to
lose
their
changes
and
you
did
not
want
to
be
the
person
telling
that
person
to
lose
those
changes.
So
there
are
workflow
issues
to
make
it
easier
to
make
people
aware
that
you
know
they
won't
accidentally,
create
these
situations
and,
of
course,
because
Allah
seein
is
is
supporting
gala
fest.
Now
we're
we're
definitely
right
behind
it.