►
From YouTube: Creating a Community at Docker - GitHub Universe 2015
Description
Marianna Tessel is the SVP of Engineering at Docker, which actively contributes to the open source project and is also responsible for Docker’s commercial product offerings. Prior to Docker, she was a VP of engineering at VMware, where she led an engineering team developing various VMware vSphere subsystems as well as working with VMware’s tech ecosystem. Prior to VMware, Marianna was the VP of engineering for Ariba (now part of SAP). Before Ariba, Tessel was part of General Magic, starting there as an engineer and rising to vice president. Marianna holds a few technology patents.
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
Hi
everybody,
what
a
great
set
of
talks
aren't
totally
inspired,
so
many
people
doing
so
many
great
things
in
the
world.
Quite
amazing
I
want
to
start
with
this.
This
is
the
graph
of
number
of
image
downloads
for
darker.
It
is
now
stands
on.
800
million
downloads.
That's
a
really
impressive
number.
It
grew
more
than
18,000
percent,
just
in
the
last
year.
My
talk
is
about
a
community
and
how
you
create
a
community.
So
why
am
I
starting
with
this
I'm?
A
A
First
of
all,
obviously
it
starts
with
a
great
idea.
I'm
sure
you're
all
working
on
amazing
ideas,
otherwise
you
won't
be
working
on
them
right.
I
want
to
talk
a
little
bit
about
what
is
a
community?
Sometimes
we
say
community.
Does
this
community?
Does
that
you
know
a
docker?
Something
to
say:
is
the
community
going
to
be
happy
with
this
or
they're
not
going
to
be
happy?
We
treat
it
as
if
it's
a
person
or
a
thing,
but
you
know
it
is
not
community-
is
really
a
lot
of
people
working
together.
A
They
all
have
different
backgrounds
all
from
different
countries.
They
do
all
different
things.
They
have
different
skill
sets.
Some
of
them
want
to
contribute
code,
others
their
users,
others
they
want
to
just
add
test
to
write
a
dock
or
a
training
to
all
bring
something
else
to
the
table.
Some
just
individuals
that
work
from
home-
or
you
know
very
passionate
about
your
project
and
other-
are
part
of
corporations
that
do
things
in
the
projects
to
have
more
of
a
plan
and
more
of
a
roadmap
for
the
work
with
your
project.
A
A
You
can
also
think
of
the
community
as
this
like
galaxy,
you
know,
the
community
is
usually
interacts
with
other
communities,
so
it's
kind
of
the
community
of
communities
and,
as
you
work
on
your
project,
you
often
use
other
projects
and
you
interact
in
this
galaxy
of
communities
and
you
give
and
you
get
and
you're
part
of
that
system.
I
want
to
get
share
with
you
a
couple
of
stories.
It
is
really
well
known
that
the
beginning
of
darker
they
keep
the
Google
people
that
work
in
a
project
called.
A
Let
me
contain
it,
for
you
have
joined
the
live
container
work
and
now
they
are
still
part
of
the
product
and
the
still
part
of
run
see.
On
the
other
end,
a
darker
we're
really
used
go
quite
extensively,
we're
probably
one
of
the
most
extensive
users
of
the
go
tower
package
and
as
part
of
that,
we
contribute
a
lot
to
that
effort.
There's
many
other
things
like
that.
A
So
what
are
the
different
roles
in
the
community?
Well,
let's
take
a
look
in
a
really
really
broad
brush.
You
can
think
of
three
different
roles
in
the
community.
First
of
all,
there
is
a
user's
the
users
really
want
to
use
the
software.
They
want
to
be
successful
with
it.
They
want
to
have
really
great
software
that
they
can
rely
on
really
good
quality
predictability.
A
You
have
the
contributors,
the
contributors
want
to
add
your
product,
the
one
are
sometimes
change.
They
want
to
create
impact
to
the
to
the
project,
and
then
last
you
have
the
project,
the
people
that
run
the
project
itself
together.
These
kind
of
forms,
your
community
and
people
can
have
multiple
hats.
You
don't
have
to
belong
just
one
category.
A
Let
me
actually
mention
a
special
category.
The
category
of
maintainer
'he's,
maintainers
kind
of
sit
a
little
bit
in
the
middle.
Often
their
users,
in
fact,
maintain
is
often
starts
as
users
because
they
use
the
softer
the
like
it.
They
become
contributors,
then
they,
you
know
so
such
a
good
contributors
to
becoming
teeners.
So
often
they
sit
in
the
middle
there.
A
Helping
running
the
project
they're
also
contributing
and
are
using
again
there's
people
that
are
in
different
parts,
and
you
know
you
don't
have
to
belong
to
only
one
circle,
you
know,
contrary
to
your
probably
common
belief,
maintain
errs,
is
not
a
very
prestigious
job.
It's
a
really
really
hard
job.
You
know
you,
the
constant
stream
of
PRS
and
requests
and
constantly
need
to
review
and
constantly
you
have
to
work
on
that
and
it's
a
really
hard
job
in
this
around
the
world.
A
A
So,
for
example,
if
your
maintainer-
you
don't
get
to
just
like,
submit
your
code
when
you're
doing
the
role
of
the
contributor,
you
still
have
to
go
through
the
process.
Your
code
gets
reviewed
by
other
maintainer
just
the
same
way
and
yes,
even
Solomon,
the
founder
of
darker
will
submit
PRS
the
same
way
and,
yes,
they
sometimes
get
rejected.
A
So
talking
about
your
company,
I
want
to
introduce
you
to
two
people.
The
first
one
is
actually
are
no
and
are
no
is
here
today
so
honor.
If
you
can
send
up
this,
is
our
no
honor
responsible
stay
up
stay
up
or
no
car?
No.
Is
it
possible
for
dr.
Anton
and
our
norio
maintainer,
okay,
I
want
to
use
my
own
advice
and
say
thank
you.
Thank
you
are
no.
A
One
interesting
fact
about
iron:
oh
by
the
way
you
gotta
checked
in
his
linkedin
profile.
If
you
haven't
already
cuz,
you
know
are
no
got
caught
on
camera
wearing
some
darker
swag
a
couple
of
times.
It
got
tweeted
and
you
know
his
friends.
A
dark
I
really
thought
he'd
get
a
good
job,
so
he
wanted.
They
voted
his
top
skill
in
LinkedIn
as
modeling,
so
go
check
it
out
and
add
to
that
anyway.
A
So,
on
the
other
end
we
have
Rashad.
Rashad
is
not
here
today,
but
Rashad.
He
was
responsible
for
one
of
the
commercial
teams,
a
docker
that
he
writes
commercial
software.
It
is
not
open
source,
so
Rashad
often
depends
on
the
engine
and
often
he
hits
a
bug
or
he
needs
a
feature
or
he
has
a
you
know
a
need
from
there.
So
in
a
very
traditional
way
of
working,
you're
gonna
pass
dependencies
back
and
forth
requirements.
A
Documents
you're
going
to
have
conversations,
align
roadmaps
all
of
these
kind
of
system,
but
in
a
community
way
of
working
you
just
submit
a
PR.
It
does
not
matter
you're
the
same
company,
it
goes
in
the
same
queue
so
when
Rashad
need
something
from
are
known
when
he
still
need
something
from
our
know,
they
just
submit
a
PR,
so
our
internal
community
is
just
the
community.
It
is
part
of
the
external
community.
Let's
actually
take
a
look,
this
donut
is
representing
first
of.
Are
you
hungry,
representing
breakfast?
A
The
second
thing
it
representing
is
that
you
know
the
contributions
to
the
darker
project
in
the
last
couple
of
months,
and
one
thing
you
will
notice
that
most
of
our
contribution
actually
come
from
the
outside
seventy-seven
percent
of
a
contribution.
The
last
couple
of
months
came
from
the
outside
and
that's
what
you
need
to
do
when
you
have
a
community
type
project
you
need
to
share
so
in
a
traditional
type
of
working.
What
do
you
do
when
you
have
projects
when
you
want
to
make
sure
it's
great
you
close
it?
You
protect
it.
A
You,
you
know,
make
sure
nobody
can
check
into
your
code.
You
put
all
these
locks
to
make
sure
you
can
be
really
responsible,
put
a
community
way
of
working,
it's
exactly
the
opposite.
You
open
it
up.
You
make
it
available.
Of
course
you
lose
some
control,
but
you
gain
so
much
by
the
way
talking
about
this
doughnuts,
it's
a
health
metric
to
run
a
successful
project.
You
need
to
monitor
and
you
need
to
look
at
the
metrics.
This
is
one
of
the
Health
metrics
we
keep
track
of.
A
A
We
in
our
project,
use
github
has
actually
the
central
piece.
When
you
submit
up,
we
are
in
kind
of
the
contribution
flow.
It
immediately
kicks
off
a
process
after
that
there's
a
variety
of
bots,
using
docker,
of
course,
that
kick
in
and
start
working
on
your
PR
and
they
scan
it,
and
they
will
immediately
give
you
an
answer
whether
it's
a
legit,
PR
or
not.
A
One
of
these
BOTS
is
the
Gordon
bought
and
I
need
to
pause
and
tell
you
about
Gordon
Gordon
is
a
turtle
and
I
always
say
it
is
a
real
turtle
or
is
a
turtle
like
that
then
Gordon?
It
leaves
a
darker.
It
actually
sits
not
far
from
me,
and
you
know
it
is
grass
likes
cactus,
really
awesome
turtle,
but
I
want
to
tell
you
this.
This
darker,
but
and
and
and
Gordon
they
work
hard
going
works
really
hard
for
you
should
come
and
check
it
out.
A
Would
you
say
thank
to
Gordon
to
I
think
there's
other
tools
that
you
need.
You
need
to
stay
in
communication,
so
you
have
tools
like
IRC
and
other
tools
that
you
use.
We
talked
about
trick,
so
you
have
some
metric
related
tools
and
you
know
again
the
whole
process
that
kick
off
at
the
end
of
the
release
and
when
I
say
tools,
I
also
mean
methodologies
and
process
release
process
in
our
release
process.
We
a
train,
so
we
leave
our
train
leaves
in
about
every
two
months.
A
A
But,
as
you
talk
about
tooling
you
don't
you
don't
want
to
be
lost
in
that,
because
we
already
talked
the
fact
that
community
is
about
people,
and
you
want
to
make
sure
you
engage
with
the
people,
and
sometimes
you
have
to
break
outside
of
the
computer
go
outside
of
the
cyber,
and
you
want
to
engage
with
the
people
in
real
life.
You
have
a
variety
of
ways
of
doing
that
and
here's
some
of
the
ways
that
we
use.
We
have
conferences
just
like
this
one
or
we
have
a
hack
days.
A
We
just
finish
a
three-day
hug
day
that
was
global
with
over
2,000
participants.
We
also
had
like
a
darker
open-source
atone
and
all
these
other
ways
to
engage
again.
It
doesn't
matter
how
you
do
that.
The
important
thing
is
that
you
engage
in
real
life
and
meetups
is
another
way
to
engage,
and
it's
an
awesome
way.
This
one
is
geared
more
toward
users.
Meetup
is
a
great
way
for
people
to
learn
from
each
other.
To
share
meetups
are
really
kind
of
done
by
the
community
for
the
community.
So
often
interest
group
will
start
a
meetup.
A
A
Again,
it
doesn't
matter
how
just
makes
you
engage
with
the
people
engage
with
the
community.
I
want
to
talk
about
other
things,
because
you
know
we
kind
of
said
a
lot
of
things
that
we
say
it's
like
you
know,
open
source
is
so
awesome.
This
is
so
awesome.
Everything
is
so
great,
but
you
know
there's
some
negative
parts
too.
First
of
all,
we
already
said
there's
a
lot
of
hard
work
involved
and
you
really
need
to
commit
to
that.
A
But
there's
even
a
dark
side-
and
you
know
there's
things
like
cyberbullying
and
you
know
people
that
can
really.
You
know,
really
affect
the
open
source
culture
and
the
experience
and
that's
not
good.
That's
no
cool
in
on
the
lighter
side
of
the
negative.
There's
other
surprises
that
you
get.
We
have
things
that
we
term
sometimes
PR
bombs
like
sometimes
you
get
a
PR
I'm,
just
rewriting
half
of
your
system
in
this
PR.
Can
you
please
accept
that?
So
how
do
we
deal
with
that?
A
And
then
you
know
when
you
get
PRS,
sometimes
to
get
rejected.
When
you
know
sometimes
you
have
to
deal
with.
Like
you
know,
working
with
people
is
working
with
people
and
when
you
work
with
the
community
just
like
a
new
order
of
magnitude,
so
you
know
like
for
you
when
you
submit
a
PR,
it's
like
your
pet,
you
grow
it.
You
really
like
it.
You
take
care
of
it
really
invested
in
it
and
then
you
go
and
you
submit
it.
A
You
think
it's
a
wonderful
idea,
but
then
it
goes
in
a
queue
with
hundreds
and
thousands
of
other
PRS
and
suddenly
it
has
to
work
within
that
umbrella
and
it
has
to
interact
with
all
these
other
PRS
and
it
has
to
make
sense
in
that
context
and
it
has
to
get
compared
to
them.
So
you
know
it's
sometimes
get
rejected
and
you
know
sometimes
people
not
happy
about.
Maybe
we
are
getting
rejected,
they're
just
unhappy
on
the
way
you
treat
the
community
and
then
they
tell
the
world
about
it.
They
will
tweet
about
it.
A
You
know
some
time
you
see
it
on
Hacker
News
who
sit
in
other
ways,
and
you
know
sometimes
they
belong
to
corporations
and
they
want
to
really
get
something
in
that's
really
important
for
their
company
and
maybe
for
a
really
good
reason
and
maybe
dad
didn't
get
in
so
guess
what
happened.
They
tilted
a
manager
and
the
manager
total
their
manager,
the
managers
of
the
manager
and
the
VP,
and
so
and
so,
and
then
they
call
our
CEO
and
ask
about
the
PR.
A
But
I
have
to
tell
you
something:
our
CEO
is
not
a
maintainer
you're
not
going
to
get
an
lgtm
for
our
CEO
and
guess
what
most
of
the
maintainer
czar,
not
even
part
of
dr..
So
you
have
to
call
a
lot
of
CEOs,
so
that's
not
going
to
help,
but
that's
where
we
go
back
to
the
nice
thing
about
the
community.
The
community
is
this
kind
of
community
code
is
kind
of
this,
even
even
in
the
leveling
the
playing
field.
A
When
you
part
of
the
community,
it
is
not
does
not
matter
your
title,
it
does
not
matter
where
you
from
does
not
matter.
You
know
nobody
has
to
review
your
resume.
Nobody
has
to
interview
you,
you
can
just
get
in
and
get
coding.
That's
amazing.
So,
overall
it
is
really
unbalanced.
It
is
really
awesome.
A
A
A
So
if
you
want
to
go
and
build
a
community
type
project,
you
might
want
to
remember
them.
The
first
thing
it's
about
the
people,
communities
about
people
and
they're,
not
all
equal.
The
second
thing
is
that
you
know
you
to
engage
with
people.
You
need
to
engage
with
them
in
cyber
and
out
of
cyber,
then
we
talked
about
tools.
Tools
are
really
really
critical
in
the
success
and
you
need
tools
and
you
need
processes
and
last
but
first
it
really
starts
with
great
idea
in
a
great
software.
A
Well,
maybe
you
were,
you
know,
running
a
community
project,
but
wherever
this
is,
you
know
if
you're
not
still,
there
go
get
on
github
and
start
exploring,
and
maybe
you
will
even
find
darker,
and
maybe
you
want
to
be
part
of
that
community
too,
and
we
will
welcome
you
with
open
arms,
but
it
doesn't
matter
what
community
you're
part
of
it
doesn't
matter
where
you
run
community
go,
do
it
and
if
you're
already
part
of
this
or
about
to
become
part
of
this
whole
world
of
communities,
I
want
to
really
say.
Thank
you.