►
Description
Keynote: All of the People, All of the Time: A holistic approach to building empowered open source culture in your organization
As an ecosystem, open source has been making vast improvements in how we think about and design for community and contributor success. What's lacking is an investment, and common language needed to build healthy open source culture inside organizations; the success of which can have direct and lasting impact in communities, and the products we're working on together. In this talk, Emma will share how she evaluates and designs for a healthy, and inclusive open source culture within Microsoft using building blocks of empowerment, purpose, trust and belonging.
A
Hi
there
yes,
hello
and
welcome
to
my
talk,
titled
all
of
the
people,
all
of
the
time
to
kick
off
chaos
con.
I'm
really
excited
to
be
here
today,
also,
even
though
I'm
not
technically
there
or
is
the
day
that
I'm
speaking
the
day
that
you're
listening.
That
said,
I'm
going
to
be
in
the
chat
channels
and
we'd
love
to
get
your
questions
and
feedback
and
I'd
also
especially
love
to
learn
from
your
experiences
on
this
topic
and
again,
I'm
just
really
excited
to
kick
off
chaos
con.
A
I
have
deep
admiration
for
the
chaos
and
this
chaos
community
and
the
work
that
we're
doing
especially
around
people.
So
I
hope
that
your
time
spent
listening
to
me
inspires
even
more
work
in
some
way
so
hi
yeah,
my
name,
is
emma
irwin.
I
work
on
microsoft's
open
source
programs
office.
I
live
in
beautiful
british
columbia
on
vancouver
island
on
the
land,
the
unseated
territory
of
the
sioux
first
nation.
A
A
But
after
months
and
months
of
kind
of
being
in
in
the
area
that
I
lived
with
kobed,
I
think
many
of
you
can
relate
to
the
fact
that
that's
a
pretty
big
deal,
and
so
I
took
my
family
to
the
interior
of
british
columbia
just
on
the
border
of
alberta
in
canada,
near
and
in
the
middle
actually
of
the
rocky
mountains.
So
this
area
is
really
vast
and
wild
and
open
and
beautiful
and
was
different
than
than
where
we
live
by
the
coast.
So
it
was.
A
So
a
really
big
accomplishment
that
allowed
a
lot
of
trade
and
travel
and
that's
putting
it
lightly
and
what
was
so
interesting
in
this
area-
and
it
was
one
of
the
kind
of
claims
to
to
fame.
If
you
will
around
architecture
of
this
type,
was
that
the
railway
had
to
go
through.
These
rugged
passes
of
mountain,
where
ice
and
snow
collect
and
in
fact,
tunnels
were
bore
through
mountains
to
make
sure
that
the
train
could
could
pass.
And
so,
with
this
in
mind,
we
decided
to
to
learn
more
about
trains.
A
A
That
includes
human
human
cost,
and
you
know,
among
others,
so,
and
it
also
told
the
story
of
different
types
of
empowerment
between
people,
different
access
to
tools
and
nutrition.
That
made
this
actually
a
real
sacrifice,
real
story
of
sacrifice
for
all
of
the
the
shiny
accomplishments
that
we've
seen
so
far.
A
And
I
started
to
think
I
always
when
I
learn
something
new.
I
try
and
I
often
just
find
myself
thinking
about
how
I
can
apply
an
insight
or
something
I've
learned
to
the
work
that
I
do
every
day,
especially
thinking
about
people
and
technology,
and
I
thought
yeah
like
we.
We
do.
We
do
this
in
technology
all
the
time
and
have
the
same
kind
of
history
is
somewhat
parallel
and
that
we
love
to
talk
about
and
share
the
stories
of
what
things
we've
built
can
do,
how
beautiful
they
are.
A
You
know
how
we
can
enjoy
them
and
how
you
know:
they've
changed
users,
life
which
are
often
great
stories
on
their
own,
but
the
builders
are
tend
to
be
a
footnote.
If
not
invisible
a
release.
Note
just
tell
the
story
of
the
builders
and
by
builders.
By
the
way
I
don't
mean
it's
not
meant
to
be
specifically
engineers.
I
mean
all
the
different
people
and
all
the
different
skill
sets
that
result
in
the
technology
that
we
build,
but
to
tell
the
story
of
everyone
has
also
times
been
uncomfortable
and
sometimes
hidden
away.
A
People
have
told
their
stories
and
we're
we've
been
very
fortunate
for
that,
because
the
stories
these
stories
have
helped
us
start
to
see
change
happen
and
start
to
create
a
shift,
and
I
believe
I
think
chaos
is
one
of
the
special
places
making
a
difference
in
that
area
because
we're
looking
at
it.
The
chaos
project
is
looking
at
it.
So
systemically
right.
A
And
so
what
I
propose
is
maybe
not
hidden
away
but
more
like
it's
not
prioritized
as
much.
We
don't
talk
about
it
as
much.
I
think
it's,
the
people
internally
working
open
source
is
still
a
bit
of
a
footnote
when
we
talk
about
technology.
So
what
I
propose
as
a
next
step
and
we'll
share
some
of
the
things
that
we've
been
doing
at
microsoft
is
to
focus
our
accountability
on
the
experiences
and
the
impact
of
people
working
on
open
source
inside
our
organizations
that
thinking
more
holistically
about
how
our
culture
internally
impacts.
A
A
So
here's
a
photo
of
some
folks
from
mozilla
from
my
time
at
mozilla,
where
this
group
includes
employees,
it
includes
contributors,
interns
and
others.
There's
a
couple
faces.
I
don't
recognize
there,
but,
as
you
might
intuitively
know,
the
the
empowerment,
the
inclusive
inclusiveness,
the
behaviors
of
one
group,
one
group
being
community
or
contributors
or
staff,
will
directly
have
impact
on
the
other.
You
can't
have
an
empowered
culture
and
open
source
without
thinking
about
and
design
inclusively
for
both
and
another
example
or
another
photo
I'll
share
with
you
is
of
kubecon.
A
A
But
the
point
is,
is
that
you
know
if
we're
just
thinking
inclusively
in
designing
empowerment
for
one
group
that
doesn't
necessarily
mean
that
we
can
ignore
the
other.
So
we
need
to
think
holistically.
The
success
of
every
individual
of
every
company
and
community
is
dependent
on
the
other
and
vice
versa,
and
if
you
like
numbers,
here's
a
number
40
of
the
100
start
projects
top
100
start
projects
on
github
were
released
by
a
company.
A
So
I
think
that's
really
interesting.
So
that
means
that
you
know
it's.
Nearly
half
of
the
projects
were
released
by
people
working
for
a
company
or
organization,
and
then
I
start
to
ask
myself:
you
know
I
wonder
what
that
was
like
what
were
their
experiences?
Releasing
open
source
did
they
feel
ready?
Did
they
know
how
to
work
with
open
source
communities?
What
was
the
experience
of
the
open
source
community
engaging
with
those
folks?
A
How
well
was
everyone
set
up
for
success
and
I
hope
you're
starting
to
see
that
why
I
think
it's
important
to
focus
on
that
internal
culture
as
part
of
the
bigger
the
bigger
plan
and
opportunity
and
when
I
think
about
building
blocks
for
a
healthy
culture
inside
an
organization
I
think
about
these
four,
these
four
areas.
These
are
largely
based
on
the
culture
code,
which
is
the
book
I
suggest
reading.
A
Also,
if
you're
in
the
chat-
and
you
have
other
books,
that
you
think
people
should
read
or
or
talks
or
presentations,
tick
tocks,
whatever
I'd
love
to
to
to
hear
some
of
your
suggestions
as
well-
and
this
is
also
just
based
on
my
experiences
over
the
years-
building
culture
inside
and
outside
of
organizations,
so
belonging
is
really
is
really
about.
As
far
as
open
source
goes
in.
A
A
Well,
you
know,
and
part
of
this
question
might
be
coming
from
the
fact
that
you're
like
well,
you
work
at
a
company
with
thousands
of
engineers
and
and
that's
true
or
you
know
you
might
be
saying-
I
work
at
a
a
startup
or
within
an
academic
institution.
I've
also
worked
in
those
types
of
organizations
and
I'll
just
say:
there's
still
similar
types
of
roles
and
challenges
that
people
face
no
matter
the
size
of
the
organization,
no
matter
the
maturity
level
of
a
project
or
team.
A
So
by
community-facing
role
I
mean
I
mean
people
in
roles
that
in
any
way
interact
with
somebody:
that's
not
a
teammate
or
working
in
their
company.
That
could
be
someone
who
writes
a
blog
post
on
behalf
of
your
company
that
can
be
somebody
who's,
releasing
code,
releasing
open
educational
resources,
commenting
on
an
issue
testing
a
pull
request.
I
mean
there's
just
so
many
ways
if,
if
the
act
of
their
job
puts
them
in
front
of
people
who
do
not
work
for
you,
then
that
is
a
community-facing
role.
A
An
organization
should
have
support,
set
up
to
support
support,
to
make
sure
that
no
one
is
handling
difficult.
Behaviors
alone
may
also
have
people
that
don't
don't
understand
their
accountability
for
inclusion,
and
you
know
things
like
using
inclusive
language
and
and
thinking
about
diverse
perspectives
or
how
to
build
inclusive
spaces.
So
all
of
these
things
can
be,
you
know,
just
deficits
and
what
people
know
their
intentions
might
be
really
good.
Kim
creighton
who's
series
educational
series
on
racism
is
really
really
good.
A
A
Without
designed
structure
and
supportive
resources,
it
can
really
literally
be
chaos,
and
so
one
of
the
ways
that
we
try
and
support,
or
that
we're
being
strategic
in
avoiding
that
chaos,
is
to
provide
training
to
everyone
in
community
facing
roles,
and
this
this
is
like
think
of
it
like
a
first
aid
course
for
creating
healthy
and
inclusive
communities.
It's
not
the
paramedic
level.
It's
not
like
everything
you
need
to
know,
but
the
basics
of
what
people
need
to
know
to
be
successful
and
to
trust
the
organization
has
their
bag.
A
The
other
category
of
people
that
we
think
about
is
probably,
not
surprisingly,
those
using
and
releasing
open
source
software,
and
this
is
again
thinking
about
that,
the
block
of
empowerment,
making
sure
that
they
have
the
tools
they.
First
of
all,
they
understand
a
basic
understanding
of
compliance
and
tooling
and
security,
but
also
that
we
have
tools
set
up
to
support
their
success.
So
the
empowerment
is
very
squarely
in
the
tooling
space
here
and
I'll
share
with
you
a
couple
of
ways
that
we
empower
engineers
and
others
releasing
and
using
open
source.
A
The
first
I
mean
I
couldn't
do
a.
I
can't
show
you
all
the
steps
of
a
wizard,
but
this
is
the
main
page
for
our
github
wizard,
which
walks
people
through
the
process
of
creating
a
new
open
source
project
on
github.
It's
not
just
a
matter
of
creating
the
repository,
but
the
the
steps
also
trigger
business
review,
including
license
and
and
other
policies.
So
this
has
been
set
up
to
reduce
friction
for
engineering
practices,
just
to
make
sure
that
they
can
follow
a
series
of
steps.
They
don't
need
to
worry
about.
A
Who
needs
to
be
involved
because
they'll
be
automatically
brought
in
and
by
the
time
that
they
click
the
button
to
release
publicly.
That
they'll
know
that
all
that
they
have
been
fully
compliant,
and
this
takes
the
worry-
I
mean
a
way
for
a
lot
of
people
that
they,
you
know,
they
don't
have
to
to
ask
a
bunch
of
questions
or
worry,
they've
done
something
wrong,
because
they've
had
a
kind
of
sign
off
from
the
folks
that
are
involved.
A
We
also
have
something
called
the
component
called
component
governance,
which
reviews
microsoft
usage
detects
what
open
source
people
are
using
and
lets
people
know
what
information
about
that
project
they
need
to
know,
including
vulnerabilities.
So
I'm
going
to
give
you
a
quick
demo
of
component
governance.
B
At
microsoft,
it's
crucial
for
our
developers
to
be
able
to
manage
their
open
source
compliance.
The
main
tool
that
we
use
to
achieve
that
is
called
component
governance
component
governance
is
an
internally
developed,
azure,
devops
extension,
where
teams
can
register
and
review
their
open
source
usage.
As
most
microsoft,
employees
work
in
an
azure,
devops
ecosystem.
It's
crucial
that
our
compliance
systems
are
easy
to
use
and
meet
developers
where
they
work.
B
B
The
results
from
that
build
test
process
appear
in
a
repo's
components,
view
which
allows
teams
to
review
the
components
that
they're
using
as
well
as
information
such
as
when
they
started
using
it
component
government
supports
many
popular
package
managers
such
as
npm
nuget
hip,
and
go
to
keep
teams
secure.
The
system
also
calls
out
publicly
available
vulnerability.
Data
sets
such
as
github
advisories,
to
look
for
known
vulnerabilities
associated
with
a
component.
B
In
the
main
component
governance
alert
view,
this
gives
teams
a
centralized
view
of
any
potential
risk
to
their
repo
alerts.
Contain
information
such
as
the
name,
a
description,
the
severity
discovery
date
and,
in
many
cases,
recommendations
for
resolution
component
governance
also
maintains
a
set
of
custom
licensing
rules
that
have
been
developed
in
partnership
with
our
legal
team
to
alert
on
any
components
that
may
be
legally
risky.
These
appear
in
the
ui
as
legal
alerts.
The
most
common
type
of
legal
alert
is
that
a
component
needs
to
be
reviewed
further
by
microsoft's
legal
team
component.
A
A
A
So
it's
not
unusual
to
release
or
use
open
source,
but
encouraging
people
to
think
about
contribution
as
part
of
their
role
in
open
source
is
really
important.
But,
of
course,
there's
lots
of
legal
questions
there
as
well.
You
know
what
can
I
do?
What
can
I
say
and
and
as
well
as
a
lot
of
confidence
issues?
So
sometimes
people-
and
this
is
really
common
open
source,
generally
feel
that
you
know
if
they're
not
perfect
enough
or
that
they
might
not
represent
your
company
well
enough
and
so
miss
busting.
A
Some
of
the
the
ideas
of
what
it
means
to
work
openly
is
really
important.
Some
of
the
ways
that
we
handle
that
are
to
to
have
you
know,
really
honest
discussions
about
what
it
means
to
be
a
to
make
meaningful
contributions
in
open
source
and
especially
using
the
term
chopping,
wood
and
carrying
water.
I
think
most
people
are
familiar
with
that
kind
of
like
helping
with
the
non-glamorous
work
of
open
source
and
the
cncf
actually
has
an
award
around
it.
A
We
also
have
something
called
a
contribution,
business
review,
which
is
when
people
encounter
a
cla
or
have
bigger
questions
about
contributing
something
like
a
feature,
an
extension
that
we
can
trigger
a
business
review
process
again,
just
to
make
sure
that
that
everything
is
fine
on
there
and
then
they
don't
need
to
worry
at
all.
So
not
worrying
is
definitely
a
theme
in
in
a
lot
of
our
business
review.
Work.
A
Contributing
to
open
source
is
also
a
a
criteria
for
voting
in
our
boss
fund,
which
is
I'll
get
to
in
the
next
slide.
But
microsoft
gives
away
ten
thousand
dollars
every
month,
as
as
one
of
the
many
ways
that
we
try
and
give
back
to
open
source
and
in
order
for
people
to
vote
on
a
project
for
this
funding,
they
have
to
have
contributed
to
open
source.
So
we're
trying
to
encourage
people
to
do
that
and
we've
created
this
resource.
A
This
is
available
on
microsoft,
slash
foss
dash
fund
to
help
people
think
about
how
to
just
get
started.
So,
there's
information
here
about
the
good
first
bug
that
opening
an
issue
is
a
contribution,
documentation
and
writing
diversity.
Inclusion
and
sometimes
this
points
out
to
some
people,
they've
been
contributing
to
open
source
all
along
if
they're,
on
a
board
or
that
sort
of
thing.
So
we
have
this
really
easy
resource
to
help.
People
unblock
themselves
if
they're,
not
sure.
A
And
and
yeah
so
I
mentioned
the
microsoft
foss
fund.
As
of
this
moment,
we've
we've
sponsored
20
projects
in
the
last
year
or
so,
and
this
is
a
way
that
we
we
help.
Our
employees
help
give
back
as
the
nominations
come
from
our
employees
and
are
based
on
projects
that
they
use
and
care
about.
We
more
recently
have
added
diversity
inclusion
as
a
reason
that
people
can
a
project
that
is
working
on
diversity,
inclusion
as
another
criteria
for
people
nominating.
A
And
finally,
actually
not,
finally,
but
the
second
last
category
of
person
that
I
think
about
is
people
who
are
new
to
microsoft
or
new
to
open
source.
They
may
not
be
new
to
microsoft,
but
they
might
be
new
to
open
source
or
they're
new
to
both
of
those
things,
and
specifically,
we
think
about
onboarding.
You
know
meeting
people
at
the
door
at
the
beginning
and
helping
them
understand
a
lot
of
things
we
just
talked
about,
and
so
we're
starting
to
onboard
or
embed
onboarding
and
existing
programs.
A
So
open
source
onboarding
is
not
separate,
but
we're
trying
to
work
with
teams
that
are
already
already
doing
this
and
meeting
people
as
they
come
in
the
door.
So
they
have
a
very
basic
understanding
of
who
the
community
is,
what
the
tools
are
and,
most
importantly,
how
to
ask
later,
when
they've
had
a
chance
to
kind
of
orient
themselves.
A
A
If
you
want
to
watch
the
faces
flash
by
it's,
some
cool
animation
there
all
linked
to
people's
github
repositories,
so
just
letting
people
know
that
they
are
part
of
the
community
and
then
that
there's
touch
points
for
ongoing
touch
points.
So
it's
not
just
faces
on
a
website,
but
there's
meetups,
where
we
get
together,
there's
a
newsletter
that
shares
the
accomplishments
the
releases,
the
inspiring
stories
shout
outs
are
a
big
part
of
our
newsletter.
We
want
to
like
highlight
the
good
work
that
people
are
doing,
contributing
and
in
the
in
the
ecosystem.
A
We
also
have
course
chat
channels
which
most
people
do,
but
we're
defined
as
and
something
called
open
source
champs
program,
which
is
basically
a
membership
of
people
who
self-select
to
help
others,
which
is
really
great
expert
leaders
who
are
ready
to
help
people
avoid
pitfalls
or
and
connect
with
some
of
the
the
tools
and
resources
and
policy
that
will
make
them
successful.
So
community
touch
points,
and
then
training
is
a
big
part
of
things
so,
but
not
just
training
collaborative
learning.
A
So
we
have
a
series
of
workshops
that
we
run
called
open
source
maintainer
workshop
series.
This
is
for
people
on
boarding
to
microsoft,
but
as
an
ongoing
weekly
offering
we
do
about
a
20-minute
presentation
on
each
of
these
subjects,
and
then
we
have
breakout
rooms
with
activities
because
we
heard
that
people
really
wanted
to
meet
each
other
more,
which
makes
sense
with
covet
and
being
stuck
at
home.
So
we
try
and
get
people
meeting
and
talking
about
some
of
the
problems
they're
working
on
as
part
of
these
workshops
and.
A
We
also
have
all
of
this.
We
pull
all
this
together
in
a
github
project
board
where
we,
because
we
know,
as
people
are
coming
into
things,
there's
the
fire
hose
and
we
don't
want
people
to
have
to
check
back
to
some
list
or
some
chat.
So
we
have
this
github
for
open
source
at
microsoft.
Project
board,
where
there's
first,
steps
which
are
kind
of
really
important
and
and
really
mostly
around
the
community,
touch
points.
A
Second,
steps:
there's
specific
training
that
we
encourage
people
to
take,
including,
like
the
code
of
conduct,
one
that
I
mentioned,
is
really
important
and
so
on.
The
idea
is
that
people
can
move
their
their
tasks
over
to
the
done
column,
which
you
can't
quite
see
here,
because
the
screen
isn't
wide
enough
and
can
also
have
conversations
with
their
managers
about
the
types
of
things
they've
done.
All
training
is
recorded
in
our
learning
system,
so
as
well,
people
can
show
their
accomplishments
and
speaking
of
managers
and
manager.
A
Discussions,
there's
also
definitely
a
group
of
people,
if
not
everyone
who
wants
to
make
sure
that
the
things
that
they're
doing
in
open
source
as
part
of
their
role
connect
the
things
their
managers
expect
of
them,
and
they
have
the
words
to
you
know
pitch
how
open
source
works.
It's
not
just
just
being
able
to
describe
why,
but
to
pitch
that
you
know
we
should
do
this
more,
and
this
is
why
it
matters,
but
it's
a
very
common
question
to
get.
A
I
don't
know
how
you
know
how
to
draw
the
line
between
this
and
the
things
that
my
team
might
be
doing,
or
my
project
might
be
doing,
and
so
the
the
answer
to
this
one
of
the
ways
we've
answered
this
is
to
create
again
a
bit
more
training.
This
is
a
self-study
course
called
mapping
your
open
source
career.
A
So
the
idea
is,
by
the
end
of
this
course
and
the
end.
The
activities
associated
with
this
course
they're
able
to
have
those
conversations
with
their
manager
and
there's
real
clarity
between
teams
and
each
other
about
what
that
means.
So
this
is
one
of
my
more
favorite
resources
that
we
created
so
to
kind
of
wrap
it
all
up.
As
best
I
can.
I
think
that
creating
a
sense
of
belonging
in
your
organization,
around
open
source
is
really
critical.
Part
of
building
culture.
A
Empowering
those
people
by
reducing
friction
in
the
engineering
process
and
providing
opportunities
to
learn
and
grow,
learn
and
grow,
learn
and
grow
is
really
central
to
that
and
connecting
people
with
each
other
and
a
purpose
around
open
source
will
create
that
accountability
and
trust.
That
really
has
the
chance
to
accelerate
the
ecosystem.