►
From YouTube: Keynote: How Open Governance Influences Open Source & Inner Sou... Charlie Robbins & Jonathan Keslin
Description
Keynote: How Open Governance Influences Open Source & Inner Source at GoDaddy - Charlie Robbins, Senior Director Of Engineering, UX Platform & Jonathan Keslin, Director of Engineering, GoDaddy
A
Howdy
folks,
and
welcome
to
how
open
governance
influences
open
source
and
inner
source
at
godaddy.
My
colleague,
jonathan
and
I
today
will
be
talking
about
this
subject
for
those
of
you
who
don't
know
me
all
that.
Well,
I've
been
doing
node
for
over
a
decade
now
and
I've
written
many
many
open
source
libraries
that
you've
probably
written
in
another
life.
I
was
the
founder
and
ceo
of
a
company
called
nojitsu
and
we
were
acquired
by
godaddy
in
2015,
which
is
the
beginning
of
our
story,
which
I'll
talk
about
in
just
a
minute.
A
During
that
time,
at
godaddy
I
have
been
the
founding
board
member
of
the
node.js
foundation
and,
most
recently
founding
board
member
of
the
openjs
foundation,
both
at
the
gold
tier
now,
as
I
mentioned,
no
jitsu
was
acquired
by
godaddy
in
2015,
and
one
of
the
things
that
really
became
poignant
to
me
during
that
time
was
something
referred
to
as
conway's
law.
I
won't
spell
it
out
for
you
here,
but
it
basically
means
that
software
system
will
start
to
resemble
the
organization
that
it
is
created
within
or
as
drucker
puts
it.
A
A
Now
this
was
created
very
shortly
after
I
joined
godaddy
and
one
of
the
things
that
was
really
poignant
about.
It
was
that
we
wanted
to
push
decisions
to
the
engineers,
the
subject
matter:
experts
as
a
voice
to
sending
content
into
a
black
hole
or
to
get
approval
from
some
set
of
approvers
that
you
may
or
may
not
know.
A
We
actually
have
a
simple
release
process
that
allows
for
a
set
of
reviewers.
That
is
all
engineers
to
decide
whether
or
not
something
is
fit
for
release.
Obviously,
there
are
trademark
and
other
implications
that
need
to
be
reviewed
by
our
legal
team
as
necessary,
but
it's
really
been
a
very
successful
group
internally,
the
company.
A
Now
this
went
on
for
a
few
years
before
something
else
started
to
emerge,
and
that
is
emerging
open
governance.
More
broadly
specifically,
what
started
to
be
clear
is
that
the
volunteers,
because
this
is
funded
as
an
employee
research
resource
group,
as
my
colleague
jonathan
will
talk
about
shortly-
was
that
once
they
became
motivated,
they
stayed
motivated
because
they
understood
the
mission
of
the
working
group
that
they
operated
in
and
wanted
to
keep
going
and
go
deeper.
A
We
had
a
few
employees
who
wanted
to
organize
the
engineering
blog
themselves,
and
so
this
emergent
open
governance
became
true,
open
governance,
I.e
the
flattening
of
a
pyramid
structure
with
this
single
approver
into
a
graph
or
a
network,
pushing
the
decisions
down,
just
as
we
did
with
open
source.
Now.
A
B
Thanks
charlie,
as
our
internal
and
external
community
engagement
grew,
so
did
our
need
for
structure
and
governance,
so
we
created
gd,
open
gdopen
is
godaddy's
nexus
of
technology
and
community.
It
provides
a
model
for
open
and
formal
governance.
That's
extensible
and
repeatable,
and
it's
fostered
and
supported
by
leadership.
B
Structurally
gd
open
is
fairly
simple.
There's
a
top-level
steering
committee
that
handles
chartering
working
groups,
spinning
down
old
ones
and
supporting
programs
across
them,
but
the
real
work
happens
inside
those
working
groups
which
are
focused
on
driving
one
or
more
business
and
or
community
needs.
B
Gd
open
was
modeled
after
the
node.js
working
group.
Working
groups
go
through
a
lightweight
charter
process
to
align
on
purpose
and
processes
and
agree
on
a
set
of
metrics
to
target
starting
a
working
group
is
easy.
We
provide
a
github
template
that
includes
a
base
charter
and
metrics
statement,
as
well
as
process
docs
to
help
keep
things
consistent
between
the
working
groups.
We
require
at
least
three
members
to
form
a
working
group
to
make
sure
there's
enough
massive
interest
in
the
space
membership
is
documented
in
the
working
group.
B
B
So
let's
get
to
what
working
groups
are
working
groups
are
bodies
meant
to
drive
business
outcomes
or
policies
around
internal
and
external
technical
communities,
they're
often
formed
across
disciplines.
For
example,
our
engineering
blog
working
group
brings
together
engineering
pm
public
relations
and
even
recruiting
they
range
across
a
mix
of
technical
and
non-technical
areas.
B
Charlie
touched
on
the
history
of
the
open
source
and
blog
working
groups,
but
I'd
like
to
tell
you
about
another
one.
A
couple
of
years
ago,
I
helped
co-found
the
interviews
working
group
to
help
concentrate
efforts
to
hone
our
engineering
interview
process
to
try
to
make
it
more
of
a
delight
for
candidates
and
the
interviewers
driving
this
process
through
gd
open
gave
us
visibility
into
other
parts
of
the
company
working
towards
the
same
goals.
In
fact,
our
head
of
recruiting
is
a
member
of
this
working
group
today.
B
There
are
communities
for
folks
to
come
together
to
learn,
share
and
grow
on.
The
left
is
the
initial
set
of
gills
that
were
formed
over
time.
The
list
grew
new
languages,
new
technologies,
new
communities,
because
the
bootstrapping
process
is
so
lightweight
folks
felt
empowered
to
start
up
a
guild.
Whenever
there
was
common
interest
guilds
made
a
home
for
tech
talks,
demos
and
collaboration
guilds
have
kept
forming
some
starting
as
just
a
slack
channel
and
eventually
becoming
more
formal.
B
While
the
early
guilds
were
primarily
made
of
engineers,
some
newer
ones
are
being
formed
across
disciplines.
For
example,
product
managers
across
teams
came
together
to
form
the
navigation
guild
to
share
best
practices
and
new
developments
in
wayfinding
and
information
architecture.
The
desire
for
community
was
always
there.
The
guild
model
simply
provided
the
scaffold
for
these
communities
to
flourish.
B
B
B
All
of
this
is
managed
through
the
gd,
open,
open
source
working
group,
the
code
review
process
license
and
documentation
standards
and
the
nitty-gritty
logistics
of
posting
code
to
github
and
by
managing
this
process
in
gd
open.
It
sits
close
to
other
relevant
working
groups
such
as
our
engineering
blog
group,
so
we
can
announce
these
releases
broadly.