►
Description
Watch all previous events here → https://goo.gle/OSSLive
A
Hello,
everyone
and
welcome
to
the
very
first
google
open
source
live.
We
are
really
really
excited
to
be
here
with
you.
This
is
the
first
of
a
monthly
series
of
sessions
led
by
google,
open
source
experts
and
community
leaders.
We
really
miss
seeing
everyone
in
person,
but
we
feel
like
this
virtual
setting
is
going
to
be
a
great
way
for
us
to
share
updates
on
all
things
open
source.
A
B
Hi
and
I'm
dustin
ingram,
I'm
coming
to
you,
live
from
austin
texas,
stephen
and
I
are
both
developer
advocates
here
at
google
and
we
love
bringing
contributors
like
you,
together
with
information
and
big
ideas,
it's
one
of
our
favorite
parts
of
our
job.
I
work
on
python
and
developer
tools
for
google
cloud.
B
Today's
session
is
going
to
be
all
about
open
source
and
open
source
foundations,
and
it's
going
to
be
led
by
four
superstars
from
google's
open
source
team
who
will
share
their
tips,
their
tricks
and
how
to
make
the
most
out
of
your
experience
in
the
open
source
community.
So
let's
go
ahead
and
introduce
today's
speakers.
A
So,
first
up
we're
going
to
have
megan
birdsenicki,
who
is
a
senior
program
manager
for
the
open
source
programs
office
here
at
google
she's
going
to
be
kicking
things
off
with
be
the
leader
you
want
in
open
source
software
up
next
after
her
is
going
to
be
aaron
mckean,
who
is
a
docs
advocacy
advocacy
program
manager,
who's
going
to
share
five
simple
things.
You
can
do
to
improve
your
open
source,
docs.
A
So
before
we
get
started
with
the
actual
talks,
I
want
to
cover
a
couple
quick
housekeeping
items.
So
this
is
a
live
event.
If
you
want
to
ask
a
question
during
the
event,
you
definitely
should.
All
of
our
speakers
are
going
to
be
available
via
chat.
So
if
you
just
take
a
look
underneath
the
video
player,
you
should
see
a
little
box
that
you
can
put
in
questions
and
comments
dust
and
I
are
going
to
be
live
watching
twitter
as
well.
B
B
B
C
C
C
People
were
a
little
aggressive
in
these
different
channels
and
they
were
talking
at
a
higher
level
than
what
a
newcomer
might
be
used
to,
and
so
this
person
just
did
not
know
how
to
engage
and
didn't
feel
comfortable,
starting
the
process
for
contributing,
and
unfortunately,
they
waited
an
entire
year
before
they
made
their
first
commit,
which
is
really
unfortunate,
but
they
realized
the
situation
they
were
in,
they
had
a
goal
and
they
took
the
right
steps
to
move
forward.
They
reached
out
to
a
mentor
and
asked
this
volunteer
if
they
would
provide
help.
C
I
mean
with
just
this
contributor
alone:
they
lost
400
commits
a
year
and
then
how
many
contributors
did
they
lose
because
people
just
couldn't
break
through
the
way
this
one
contributor
did,
and
the
answer
is
just
too
many
and
it
doesn't
have
to
be
this
way.
It
people
don't
want
it
to
be
this
way.
It's
just
that
often
many
people
step
up
to
help
and
open
source
as
you
do,
but
they
don't
realize
they're,
actually
stepping
into
leadership
roles,
and
it's
not
identified
that
way,
and
it's
not
clear
how
to
conduct
yourself
when
you're
in.
B
C
Leadership
roles
and
it
can
start
to
get
a
little
messy
and
confusing
for
everyone,
and
that's
why
I
like
to
provide
this
kind
of
training.
So
people
are
more
self-aware
of
how
to
conduct
themselves
how
to
lead
others
how
to
get
things
done
in
a
healthy
way,
with
an
open
source,
and
so
I'd
love
to
just
use
the
story
to
kind
of
unpack.
C
What
leadership
is
because
there's
a
lot
of
leadership
stories
in
here,
so
the
first
one
is
who
were
the
leaders
in
this
story?
And
the
answer
is
the
forum
moderator
the
people
working
in
the
issue
cues
they
were
helping,
but
they
were
also
leading.
They
had
great
influence
over
the
project
and
what
was
happening
in
these
channels.
C
So
it
is
about
influencing
bringing
people
along
in
a
journey
so
that
they
want
to
do
something
with
you
and
achieving
something
together,
something
they
all
want
to
achieve
together.
That's,
ultimately,
what
leadership
is,
and
leadership
is
sometimes
better
defined
by
what
it
is.
Not
so
leadership
is
not
a
title:
it's
not
a
role!
You
don't
need
to
be
a
ceo
vp.
Whatever
title
you
know,
project
lead
in
order
to
be
a
leader.
C
C
It's
also
important
important
to
point
out
that
leadership
is
not.
Management.
Management
is
about
making
sure
everyone's
following
policies
and
process
and
rules
and
budgets,
and
things
like
that.
Leadership
is
different
and
it
is
not
about
power.
It
is
not
about
getting
people
to
do
things
because
you
have
power
or
authority,
it's
truly
about
influence
and
there
are
different
kinds
of
leadership
types,
there's
leading
organizations.
C
So
in
a
company
that
might
be
a
ceo
and
a
project
it
might
be,
the
project
lead
could
be
an
executive
director
at
a
foundation
for
an
open
source
project
and
there's
leading
others.
So
managers
lead
others
on
a
team
or
product
managers
work
across
many
teams
to
build
and
release
a
product
in
open
source.
You
have
someone
who
might
be
in
charge
of
all
of
the
forum
moderators
or
the
issue
cues
or
the
mentors,
and
then
the
third
one
is
leading
yourself,
and
this
is
what
the
contributor
was.
This
is
some
you
know.
C
C
C
You
focus
on
a
measurable
result,
so
you
all
know
when
you've
achieved
it
together
and
you
foster
innovation
and
learning
throughout
the
process.
So
you're
constantly
taking
insights
from
all
these
people,
you've
brought
together
and
as
you're
doing
this
you're
able
to
lead
yourself
you're
able
to
really
self-regulate.
Your
emotions
I'll
talk
some
more
about
that
and
the
contributor
very
much
did
this
had
a
vision
of
contributing
with
a
goal
of
one
commit
and
the
strategy
was
to
go,
get
help
and
he
recruited
a
mentor
to
go.
Do
that
and
there
was
a
goal.
C
It
was
one
contribution
and
he
did
have
a
learning
mindset
and
he
was
able
to
do
this
again
and
again
and
that's
what
made
him
be
a
top
contributor
and
that's
what
leaders
do
and
they
need
a
lot
of
skills
in
order
to
do
it.
And
if
you
look
at
this
list
from
some
harvard
business
review
research,
you
can
see
that
the
skills
required
range
from
inspiring
and
motivating
others.
Communication
collaboration-
you
don't
really
see
technical
skills
to
be
a
good
leader,
does
not
mean
you
need
to
be
a
great
coder,
great
mentor.
C
You
just
need
to
know
how
to
work
with
others
through
influence
and
actually
more
research
shows
that
leadersh
two-thirds
of
leadership
depends
on
emotional
intelligence.
That's
really
the
skills
that
you
need
to
be
a
leader,
and
so,
if
you
want
to
lead
yourself,
you
want
to
lead
others.
You
ultimately
need
to
work
on
emotional
intelligence.
C
Knowing
how
you're
reacting
to
something
and
self-regulation
is
saying
like,
I
know
how
I
feel
right
now,
I'm
gonna
adjust
to
have
the
best
outcome
possible.
So
a
great
example
is
you've
just
had
a
rough
day,
you're
trying
to
work
with
people,
maybe
it's
through
slack
and
something
makes
you
so
mad.
C
But
you
know
you
are
self-aware.
This
thing
made
me
mad
and
you
know
you
want
to
have
a
positive
outcome,
so
you
do
what
you
need
to
do
you
self-regulate,
and
then
you
choose
a
response
that
gives
you
a
better
outcome.
Maybe
you
end
up
having
a
I'm,
not
sure
I
understand
this,
why
don't
we
go
to
a
video.
B
C
So
mindfulness
could
be
meditation,
it
could
be
yoga,
it
could
be
journaling,
and
I
know
google
focuses
on
this
a
lot.
We
have
meditation
rooms
in
our
buildings
back
when
we
used
to
be
able
to.
You
know,
use
our
buildings
and
we
also
have
a
big
initiative
called
search
inside
yourself,
which
I
encourage
you
to
check
out,
and
I
know
for
myself
and
others
I
talk
to,
they
think
mindfulness
sounds
pretty
hokey.
Why
would
I
just
sit
down
and
do
this
to
become
a
better
leader
beyond
the
reasons
I
just
gave?
C
C
Thought
processes
so
something
came
up.
I
was
a
little
bit
more
strategic
because
I
was
just
creating
more
space
to
think.
Instead
of
react,
I
prioritize
better
and
overall,
it
just
helped
me
move
through
some
hard
situations,
a
lot
better,
and
so
I
certainly
encourage
you
to
look
into
mindfulness
as
a
way
to
grow
your
emotional
intelligence
and
therefore
your
leadership
skills,
and
you
know
just
to
help
kind
of
bring
it
home.
I
think
tara,
brock
she's
a
buddhist-based
psychologist
out
of
washington
dc
here
in
the
u.s.
C
It's
also
mindfulness
that
helps
us
keep
that
space
ready
so
that
we're
not
struggling
all
the
time
we're
more
resilient
in
the
face
of
any
kind
of
stimulus
or
conflict.
That's
coming
at
us
all
day
long
and
it's
really
important
that
we're
resilient
and
open
source
and
that's
because
of
the
nature
of
the
way
we
work.
We
work
with
online
communication
and
collaboration
using
github
and
slack
and
twitter
and
our
brains
are
actually
not
wired
for
online
work.
We
are
designed
for
face-to-face
interaction,
reading
each
other's
body
cues.
C
It
really
does
trigger
the
brain
in
a
much
different
way,
and
so,
when
we
do
this
online
work
together,
it
starts
to
trigger,
what's
called
a
disinhibition
effect
and
there's
a
couple
elements
to
it.
Two
that
I
think
are
really
important
to
call
out
are
when
we
have
online
communication,
we
have
a
lack
of
eye
contact
and
when
we
have
a
lack
of
eye
contact
that
reduces
empathy
for
each
other,
we're
just
wired
to
read
body
language
and
emojis,
they
don't
cut
it.
C
C
So
for
resetting,
you
can
count
to
ten.
If
something's
triggered
you,
you
can
take
some
deep
clearing.
Breaths
comes
the
nervous
system.
If
you're
a
tea
drinker,
you
can
sip
hot
tea
because
it
takes
time
to
sip
tea.
You
don't
want
to
burn
yourself
and
actually
the
act
of
taking
in
the
tea
is
calming
to
the
nervous
system,
and
then
last
but
not
least,
you
can
always
just
take
a
walk
around
the
block,
collect
your
thoughts,
come
back
to
your
computer
and
decide
how
you
want
to
respond
and
there's
a
lot
of
strategies
for
responding.
C
One
way
I
like
to
use
is
yes,
and
it
comes
from
the
improv
world,
and
somebody
can
say
something
to
you,
and
maybe
you
don't
necessarily
agree,
but
you
can
say
yes,
I
hear
you
and
here's
another
approach
as
well,
and
what
that
does
is
it
builds
on
ideas
rather
than
saying
no
and
cutting
that
person
off
and
then
trying
to
convince
them
about
your
idea.
That
gets
you
into
more
of
like
a
battle
of
ideas.
C
Another
approach
is
the
design
approach
I
like.
I
wish.
I
wonder
so.
If
somebody
sends
you
an
idea,
you
could
say
I
like
this
proposal.
I
wish
it
had
focused
a
little
bit
more
in
this
other
area.
That's
you
know
interesting
to
me,
and
I
wonder
if
you
talk
to
sally,
if
you
two
might
be
able
to
coordinate
on
filling
in
that
area
again,
it's
not
about
cutting
off
ideas.
It's
about
designing
a
conversation
and
a
path
forward.
C
C
So
a
lot
of
times
when
we're
interacting
we're
not
we're
we're
so
focused
on
our
ideas
and
where
we
want
to
go
next
with
the
conversation,
we're
not
always
engaged
in
truly
listening
and
the
person
doesn't
always
know
if
they've
been
heard.
So
before
you
take
a
conversation
down
a
whole
nother
path,
it's
really
important
to
use
active
listening,
asking
questions
like
well.
C
C
C
C
Well
is
super
important,
so
you
want
to
practice
your
strategies
to
reset
when
something
makes
you
upset,
and
that
way
you
know
how
to
respond
versus
react,
and
I
hope
that
you
will
use
these
different
techniques
because
we
really
do
need
more
leaders
in
open
source
and
we
are
really
excited
for
you
to
get
more
involved
and
share
your
skills
and
talents
with
all
of
us.
So
I
hope
that
you
will
start
being
the
leader
that
you
need
in
open
source
and
that
we
all
need.
B
Thank
you,
megan.
That
was
a
really
great
talk.
One
of
the
things
I
really
loved
about
megan's
talk
was
this
thought
that
anybody
can
lead
as
long
as
you
learn
how
to
act
like
a
leader
before
you
actually
are
one,
you
can
become
a
leader
as
well,
and
that's
one
of
the
things
I
love
about
open
source
as
well.
Like
no
one
told
someone
all
the
open
source
leaders
that
you
know.
No
one
said
okay.
Today,
you
are
a
leader
like
going
at
it.
B
A
B
I
think
I
found
most
of
my
mentors
just
through
the
open
source
code
that
I
was
reading
not
directly
interacting
with
anyone
but
sort
of
just
learning
from
what
people
had
already
done
and
written
yeah
mentors
are
great
and
it's
it's
one
of
the
best
ways
to
generate
more
leaders
for
open
source.
We
always
need
more
leaders
in
open
source.
B
D
Hey
folks,
thanks
so
much
for
having
me
here
today,
I'm
very
much
looking
forward
to
talking
with
you
all
about
things
that
you
can
do
in
open
source
documentation,
so
I'm
erin
mckean
and
I
work
on
docs
advocacy
in
google's
open
source
programs
office.
So
my
job
and
it's
a
very
fun
one
is
to
help
open
source
projects
have
better
docs.
D
D
Now
I'm
focused
here
on
open
source,
because
that's
what
I
work
on,
but
I
can't
imagine
that
closed.
I
can't
imagine
that
closed
source
software
has
less
of
a
need
for
good
docs
and
lack
of
documentation
was
the
top
reason
that
developers
surveyed
by
digitalocean
in
2018
gave
for
deciding
against
using
an
open
source
project.
D
D
So
when
I
tell
people
that
I
work
on
making
open
source
stocks
better,
they
often
tell
me
great.
We
need
better
docs.
So
then
I
ask
okay:
well,
what
are
you
doing
to
help
your
projects?
Have
better
docs
in
open
source
stocks
have
to
be
everyone's
responsibility,
and
so
in
this
talk
I
want
to
give
you
five
ways
that
you
can
help
make
open
source
documentation
better
and
yes,
definitely
there's
work
ahead
and
you
might
be
thinking
well.
D
You
will
never
know
less
than
you
know
today.
Now
this
might
sound
like
I'm
joking,
but
one
of
the
problems
in
writing
a
documentation
is
that
once
you
understand
something,
it
can
be
really
difficult
to
put
yourself
in
the
mindset
of
someone
who's
new
to
it
beginner's
mind
is
actually
a
precious
resource.
D
So
friction
logging
is
basically
just
doing
stuff
while
paying
attention
so
find
a
project
you'd
like
to
try
and
follow
the
instructions,
whether
that's
for
a
tutorial
or
a
quick
start,
just
find
something
that
you
can
do
and
then
write
everything
down,
write
down
what
you
tried
write
down,
what
you
expected
write
down
what
worked
and
especially
write
down
what
didn't
work
and
what
you
did
to
get
past
that
little
broken
step
and
on
to
the
next
thing.
I
find
that
even
writing
down
whatever
search
terms
I
use
to
try
to
diagnose
the
problem.
D
Helps
me
a
lot
when
I
go
back
to
my
friction
logs,
to
figure
out
how
the
heck
something
worked,
then
keep
going,
keep
going
until
you've
either
finished
the
tutorial
or
the
quick
start,
or
it's
so
broken
that
you
just
can't
get
any
farther
and
then
share
your
friction
log.
You
can
raise
an
issue
in
the
project,
repo
and
add
a
link
to
your
friction
log
or,
if
you
can't
find
anybody
to
share
it
with
in
the
project.
A
friction
log
makes
a
great
blog
post.
D
Another
thing
that
you
can
do
to
help
open
source
documentation
is
to
go
spelunking
in
the
closed
issues
a
lot
of
times.
There
are
closed
issues
in
a
project
where
the
answer
was
missing
from
the
docs,
but
somebody
shared
it
in
the
issue
to
help
the
person
who
was
having
the
problem
and
a
lot
of
the
time
that
help
never
gets
put
back
into
the
docs.
D
D
So
how
do
you
do
this?
How
do
you
play
and
match
the
issue
to
the
docs
first
check
out
a
project's
closed
issues
then
look
for
solutions
in
the
closed
issues
that
aren't
reflected
in
the
docs
and
write
the
solutions
that
are
shown
in
the
issues
in
a
way
that
they
fit
into
the
docs
and
open
a
pull
request.
It's
pretty
straightforward.
D
But
it's
really
important
a
project
with
a
lot
of
open
issues
can
be
seen
by
developers
as
having
incomplete,
documentation
or
being
not
very
well
maintained,
and
by
helping
to
replicate
issues
replicate
bugs
in
issues
that
are
just
kind
of
lying
around
or
stagnant.
You
can
really
help
maintainers
with
their
burden
and
by
replicating
issues.
You
give
other
people
a
step
up
to
improve
the
documentation
around
those
issues.
D
Now,
especially
issues
where
the
original
person
isn't
responding.
It's
probably
not
because
they
fixed
the
problem,
it's
probably
because
they
moved
on
to
something
else
and
for
every
person
who
bothers
to
file
an
issue.
There
are
a
lot
more
who
just
went
straight
onto
the
find
something
else
part
now
once
you've
worked
on.
Friction
logs
for
a
little
while
and
on
adding
documentation
from
issues
and
replicating
bugs
and
issues.
The
next
logical
step
is
to
start
working
on
tutorials.
D
Not
all
tutorials
have
to
be
fancy.
Some
of
the
most
useful
tutorials
are
the
most
basic
and
tutorials
really
help
you
grow
as
a
developer,
because
you
can
never
really
know
something
until
you've
explained
it
to
somebody
else
so
to
write
a
tutorial.
I
think
the
first
place
to
start
is
to
think
about
what
did
you
get
excited
about
lately?
What
were
you
happy
that
you
learned
and
then
think
about?
How
would
I
explain
this
to
somebody
else
and
if
you
kept
a
friction
log,
this
is
great
for
writing.
D
Tutorials,
because
you
could
go
back
and
look
at
every
step
that
you
did
and
everything
that
did
and
didn't.
Work
now,
then
think
about.
Okay,
well,
you're
excited
about
this
thing
and
you
know
how
to
do
it,
but
why
would
somebody
else
want
to
do
it?
What
makes
it
cool
what
problem
will
it
solve?
How
will
it
help
someone
else
to
know
how
to
do
this
thing?
D
If
you're,
if
you
need
a
little
extra
motivation,
find
a
friend
each
of
you
write
a
tutorial
and
then
pair
up
and
swap
tutorials
try
to
work
through
the
other
person's
tutorial
and
make
sure
that
it
works.
Also
having
a
friend
to
do
this
with
adds
a
little
bit
of
accountability,
just
in
the
same
way
as
having
a
friend
keep
you
accountable
for
exercise
does.
D
D
What
could
you
copy
over
in
terms
of
types
or
the
structure
of
docs,
not
the
actual
content,
obviously
from
the
project
that
has
good
docs
to
the
project
that
needs
a
little
bit
of
doc's
help.
It
is
100,
okay
to
look
at
other
projects,
documentation
as
a
model
for
your
own
docs.
You
can
just
treat
them
like
a
coloring
book.
The
headings
and
the
structure
are
the
lines
that
you
fill
in
with
your
own
content.
Crayons.
D
So
when
you're
trying
to
copy
docs
from
one
project
to
another
project,
first
pick
a
project
that
you
like.
You
won't
be
motivated
to
do
docs
for
a
project
that
you
don't
like
and
then
make
a
list
of
what
kinds
of
of
documentation
it
has
or
it
needs.
Does
it
have
a
readme,
but
it
needs
a
quick
start.
Does
it
have
good
concept
documentation,
but
no
tutorials?
D
You
can
also
use
doxy.dev,
which
is
the
documentation
template
for
the
hugo,
static
site
generator
and
then
use
the
templates
you
found
to
help
create
better
docs
for
the
project
you've
chosen
now.
I
know
I
said
that
I
was
going
to
give
you
five
ways
that
you
could
help
make
better
open
source
documentation,
but
I'm
kind
of
going
to
give
you
a
bonus
round.
D
D
D
D
D
What
would
someone
need
to
know
in
order
to
decide
whether
or
not
to
use
the
project
and
then
include
your
explanations
in
there?
So
this
is
really
hard
to
explain
in
the
abstract.
So
I'm
going
to
give
you
a
concrete
example:
I'm
working
on
a
project
to
demonstrate
documentation
templates,
the
project
is
called
chronolog
and
it
helps
time
travelers
convert
between
different
calendars
for
more
precise
time
travel.
Yes,
this
is
a
joke
project.
It
does
not
work
so
a
concept
doc
for
chronolog
would
involve
explaining.
D
Why
would
a
time
traveler
want
to
use
this?
What
is
meant
by
the
by
the
phrase
calendrical
system,
what
a
calendrical
system
conversion
program
does
and
so
forth,
and
at
the
end
of
that
concept,
doc
someone
would
be
able
to
say:
oh
yeah,
I
time
travel
all
the
time
and
boy.
I
would
really
like
to
be
able
to
like
convert
between
the
mayan
and
the
julian
calendar
more
easily
or
they
say.
Oh,
you
know
what
I
hardly
ever
time
travel.
D
I
don't
need
this
project,
so
I
believe
that
everyone
can
contribute
to
open
source
stocks
if
they
are
sufficiently
motivated
and
they
have
some
of
these
places
to
start
everyone
is
a
beginner
at
something
if
you've
been
holding
back
from
contributing
to
open
source
documentation,
there
is
no
better
time
to
start
than
today
and
now
there's
one
other
thing
that
I
wanted
to
mention
some
of
the
pushback
I
get
from
people
about
why
they're
not
contributing
to
open
source
docs.
Is
they
say?
Oh
I'm,
not
a
writer.
D
Now
I
totally
understand
it
is
scary
to
work
on
things
and
to
do
things
that
you
feel
like
you
might
not
be
very
good
at,
but
almost
everyone
working
in
software
development
has
spent
more
time.
Writing
non-code
that
they
have
spent
writing
code.
They
spent
more
time
talking
than
they
have
writing
code,
and
as
long
as
you
can
reasonably
express
yourself,
you
can
help
with
software
documentation.
D
D
D
Please
feel
free
to
ask
me
questions
in
the
live
chat.
I'm
always
happy
to
answer
what
I
can
and
to
try
to
find
links
to
what
I
don't
know
and
speaking
of
links.
I
have
some
links
for
you.
So,
first
of
all,
there's
a
really
good
blog
post
on
friction
logging
that
I
recommend
that
you
read
it's
more
from
a
product
point
of
view,
but
it
has
a
lot
of
helpful
tips
for
people
who
are
friction
logging
in
open
source.
D
Again,
I
cannot
recommend
wizard
docs
by
julia
evans
highly
enough.
The
comics
are
great
doxie.dev.
Is
the
documentation
focused
template
for
the
hugo
static
site
generator
that
I
mentioned
it
is
set
up
from
the
perspective
of
someone
who's
trying
to
create
docs
for
developers.
The
good
docs
project
on
github
is
trying
to
make
documentation
templates
for
open
source.
D
It's
still
very
early
days
as
an
open
source
project,
so
enthusiastic,
enthusiastic
participation
is
welcome
and
if
you
can't
think
of
your
question
right
now
for
the
live
chat,
you
can
always
reach
out
to
me
on
twitter.
I'm
just
ima,
keen
I'm
a
pink
robot
on
twitter.
So
if
you
don't
see
the
pink
robot,
that's
not
me
and
thank
you
so
much
for
spending
time
with
me
today
to
learn
about
how
you
can
help
in
open
source
documentation.
A
A
B
Yeah
absolutely
friction
logs
are
really
core
part
of
our
internal
product
advocacy.
So
when
I'm
testing
a
new
feature
or
a
new
product,
the
very
first
thing
I
do
is
write
a
friction
log.
It
gives
me
that
beginner
mindset
that
she
was
talking
about
that's
so
precious
and
helps
me
categorize
everything.
I've
been
doing
as
I
interact
with
this
product
for
the
first
time,
so
that
the
product
teams
you
know
know
where
the
friction
is,
they
know
what
to
fix
and
what
to
make
smoother.
For
next
time.
A
B
A
Awesome,
well,
I
hope
everyone
out
there
is
having
fun
and
enjoying
google
open
source
live
today.
If
you
haven't
already
put
anything
in
the
chat,
definitely
go
ahead
and
say
hello
or
say
where
you're
watching
from
one
silver
lining
of
everyone
being
online
is
that
we
can
actually
reach
out
to
kind
of
everyone
across
the
world.
We
can
include
all
of
our
global
colleagues,
which
is
really
really
nice.
A
I
guess
we
do
that
in
open
source
fairly,
often,
though
so,
but
it's
always
good
to
take
an
opportunity.
There's
a
question
in
the
chat
about
the
slides,
there's
going
to
be
all
the
videos
are
going
to
be
online
on
the
youtube
channel
after
the
event.
So
take
a
look
in
the
chat
for
the
link
for
that
up.
Next
we
have
caslin
fields
and
seth
vargo
with
a
fireside
chat.
They
are
going
to
be
discussing
open
source
models
and
contributor
engagements
over
to.
A
E
E
F
Yeah
so,
like
I
was
just
saying
today,
honestly
most
of
my
day
is
spent
working
on
exposure
notifications
on
the
server
component.
So
this
is
a
joint
effort
between
google,
apple
and
microsoft.
To
help
stop
the
spread
of
covid,
we
have
a
server.
The
server
is
open
source.
It's
at
github.com,
google
exposure
notification
server
and
it's
written
in
go,
which
is
also
an
open
source
project
programming
language,
so
there's
kind
of
a
double
dipping
there,
a
little
bit.
You
know,
prior
to
that.
F
I've
worked
on
a
number
of
open
source
projects
at
google,
including
like
gcr,
cleaner
and
burr
glass,
and
then,
before
that
bg
before
google.
I
worked
at
hashicorp
for
a
number
of
years,
which
is
a
company
largely
based
on
open
source
software
tools
like
baker,
packer
surf
console,
nomad
vault
did
a
lot
of
work
in
the
the
vagrant
and
fault
ecosystems,
and
you
know
before
that.
F
I
worked
at
chef
software,
which
is
also
a
company
based
on
open
source,
primarily
doing
a
lot
of
ruby
development
and
ecosystem
development,
but
my
first
open
source
project
ever
was
actually
when
I
was
an
undergrad
at
carnegie
mellon.
I
wrote
a
small
little
rubygem
that
could
query
the
isbn
db
database
so
that
you
could
look
up
a
text
textbook
by
its
barcode
number
for
a
little
startup
that
we
were
working
on
that
ultimately
failed.
But
you
know
you
live,
and
you
learn
what
about
you
and
how
did
you
get
involved.
E
Yeah,
so
I
mentioned
that
I
do
kubernetes
things,
I'm
involved
in
the
special
interest
group
within
the
kubernetes
project.
That's
focused
on
contributor
experience,
specifically
a
team
that
focuses
on
kind
of
internal
upstream
marketing.
So
I
take
the
things
that
contributors
are
doing
within
the
kubernetes
project
and
I
help
other
contributors
see
what
they're
doing
that
can
help
inspire
people
to
find
a
new
project
to
work
on
that
they're
really
interested
in
it's
a
great
way
to
learn
about
all
of
the
different
types
of
projects
that
are
going
on
within
kubernetes.
E
It's
a
broad
spectrum
of
areas
and
types
of
projects.
So
I'm
really
excited
to
get
to
see
all
these
sorts
of
like
broad
categories
of
things
that
people
are
doing
within
kubernetes
and
I'm
also
a
cncf
ambassador.
So
that's
the
cloud
native
computing
foundation
and
with
them.
I
do
a
lot
of
things
to
kind
of
help,
promote
their
community
help
kind
of
organize
things.
I
volunteer
at
conferences
and
help
with
webinars
and
things
like
that.
E
So
I'm
I
do
a
lot
of
things
that
are
related
to
open
source
community
cool
awesome,
which
kind
of
brings
up
an
interesting
point
that
we
might
want
to
talk
about
is
open
source
communities
and
how
does
open
source
work?
I
think,
in
the
current
situation
of
the
world,
there's
a
lot
of
interesting
things
that
we
can
learn
from
the
way
that
open
source
does
their
work.
F
Yeah
for
sure
I
think
you
know,
with
the
the
current
situation
with
covid
traditional
nine
to
five
and
commuting
to
and
from
an
office
every
day
is,
is
pretty
much
non-existent
and
for
that
reason
many
people
have
reinvented
the
way
that
they
work.
Whether
that's
because
you
have
you
know
family
or
loved
ones,
at
home
or
new
pets
and
new
furry
friends.
You
know
you
may
be
working
at
really
odd
hours,
two
hours
here,
two
hours
there.
F
F
That
requires
you
know
very
rigorous
points
in
time
and
checkpoints
for
things
to
move
throughout
a
system,
and
I
also
think
that
this
situation
is
giving
people
an
opportunity
to
explore
contributing
to
open
source
more
because
they
might
be
branching
outside
of
their.
You
know
regular
day-to-day
work.
Some
people
are
finding
that
they're,
more
productive,
actually
by
working
from
home
or
working
outside
of
the
office
with
less
distractions
and
that's
giving
them
additional
time
to.
You
know:
explore
open
source
projects
and
open
source
communities
and
ways
that
they
might
get
involved.
E
Yeah
an
important
thing
that
I
want
to
point
out
there
that
I
am
involved
a
lot
with
in
my
role
with
kubernetes
is
that
these
projects
are
often
global,
especially
kubernetes
such
a
large
project.
They
have
the
opportunity
for
people
all
over
the
world
to
contribute
to
kubernetes
and
that
can
pose
all
sorts
of
different
challenges
that
a
lot
of
folks
might
be
dealing
with
today,
as
well
in
their
work
having
to.
E
Since
everyone
is
staying
home,
you
might
have
to
collaborate
with
people
in
different
time
zones
and
then
all
sorts
of
different
places
in
the
world
and
a
lot
of
open
source
communities
are
just
used
to
that.
They
do
it
all
the
time
and
they're
they're
familiar
with
all
the
challenges
that
poses,
and
they
have
come
up
with
their
various
solutions.
F
Yeah,
I
think,
like
open
source,
has
been
remote
largely
from
the
beginning,
because
of
the
way
that
you
know,
contributors
come
from
different
backgrounds
and
time
zones
and
countries
and
languages
that
you
know.
Not
only
has
there
not
really
been
an
interruption
to
the
velocity
at
which
open
source
software
is
being
developed,
but
I
think
it's
quite
the
opposite.
I
think
we've
seen
an
acceleration
as
more
and
more
people
get
involved.
F
So,
honestly,
anyone
can
contribute
to
open
source
oftentimes.
We
talk
about
open
source
software
and
we
talk
about
the
s
word
the
software
and
that
that
tends
to
lead
like
to
developer
or
software
engineer,
and
that's
something
I
really
want
to
dispel
is
like
you,
don't
have
to
be
a
software
engineer
and
you
don't
have
to
be
writing
code
in
order
to
contribute
to
open
source.
You
don't
have
to
be
a
software
engineer
to
write
code
and
you
don't
have
to
be
writing
code
to
contribute
to
open
source.
F
All
of
these
things
are
incredibly
welcome
in
open
source
projects
and
don't
require
you
to
write
code
or
you
know,
be
an
action.
An
engineer,
there's
also
a
ton
of
other
things
that
build
an
open
source
community
things
like
logos
and
graphics
and
swag,
and
you
know
pre-covered,
meetups
and
local.
You
know
local
human
human
interaction.
I
think,
like
a
really
good
example
of
this
is
like
go
go.
The
programming
language
is
also
an
open
source
project,
an
open
source
community.
They
have
this.
This
cute
little
kind
of
mascot.
F
Is
it's
a
gopher
and
there
have
been
folks
from
you
know
the
community
who
have
taken
that
and
turned
it
into.
You
know
amazing,
cute
little
artwork,
that
you
know
people
have
stickers
on
their
laptops
and
backgrounds
on
their
computers
and
that
dramatically
improved
the
continuity
of
community,
but
didn't
involve.
You
know
to
the
best
of
my
knowledge.
Writing
any
you
know
go
code,
and
these
are
you
know
just
a
few
of
the
ways
that
you
can
get
involved
in
open
source.
F
Obviously
you
can
write
code
nothing's,
stopping
you
from
doing
that,
but
I
really
dislike.
Whenever
I
hear
people
say
like:
oh
I'm,
just
a
tech
writer.
I
can't
really
contribute
to
open
source.
That's
really
not
the
case.
I
would
argue
that
your
contributions
might
even
be
more
important
than
code
contributions,
especially
you
know
for
a
more
mature
project
because
ultimately
you're
starting
to
get
people
who
aren't
directly
familiar
with
the
technology
and
they
really
need
that
documentation.
In
order
to
be
successful.
E
And
also
with
the
current
situation
of
the
world,
there
are
so
many
people
at
home
right
now
who
are
trying
to
learn
new
languages,
learn
all
sorts
of
different
technologies
and
tools
and
a
lot
of
the
information
they're
getting
comes
from
the
documentation,
it's
a
primary
source
of
of
knowledge
on
any
open
source
project.
So
those
contributions
get
a
lot
of
a
lot
of
views,
they're
very
visible
contributions
and
they're
very
highly
valued.
E
So
that's
a
really
important
way
that
people
can
contribute,
even
if
they're,
not
as
comfortable
doing
code,
and
maybe
if
they
want
to
learn
how
to
code
or
they
want
to
start
contributing
to
a
project
in
those
kinds
of
ways.
Documentation
is
also
a
great
place
to
start,
because
you
can
learn
so
much
about
what
the
project
does
and
how
it
works
and
the
use
cases
of
it,
and
that
can
be
great
for
informing
your
efforts,
as
you
start,
to
contribute
to
the
project
in
code
as
well.
If
you're
interested
in
that.
F
Yeah
and
if
you
are
just
going
to
jump
straight
into
code,
you
know
another
thing:
that's
really
important
is
you
know,
read
the
contributing
guidelines
and
you
know
do
take
some
time
to
understand
the
goals
of
the
project
right,
if
you're
contributing
an
open
source
project
that
you
know
is
designed
to
open
and
close
a
garage
door,
and
you
know
you
contribute
functionality
that
makes
it
also
cook
you
an
omelet.
That's
probably
what
we
call
scope
creep
and
you
know
you
really
want
to
stay
true
to
the
the
core
principles
of
the
project.
F
It
may
include
things
more
on
the
legal
side
like
signing
a
contributor
license
agreement,
but
you
also
just
want
to
make
sure
that
your
change
or
your
contribution
or
suggestion
is
in
line
with
the
goals
of
the
project
and
some
projects
intentionally
limit
their
scope
to
be
very,
very
small,
either
because
they
don't
have
the
resources
and
staffing
to
support
a
broader
scope
or
because
they
really,
you
know,
follow
the
unix
philosophy
and
just
like
want
to
do
one
thing,
and
do
it
really?
Well,.
E
F
Yeah,
so
oh
boy,
there's
so
much
so
there's
two
main
components
that
I'm
involved
in
in
the
day-to-day.
We
have
two
server
components.
Both
of
them
are
open
source
on
github.
The
first
is
the
actual
exposure
notification
server.
This
is
the
server
that
your
android
or
ios
device
actually
publishes
temporary
exposure
keys
to,
and
then
we
have
a
verification,
server,
also
open
source.
F
That
is
typically
run
by
like
a
public
health
authority
which
verifies
that
when
your
device
is
uploading,
these
keys
that
you
were
actually
seen
by
a
medical,
professional
or
a
clinic
or
if
you
did
a
self-diagnosis.
You
know
with
a
test
at
home
that
there's
metadata
attached
to
that,
but
the
entire
system
is
open
source
for
two
reasons.
First,
is
we
wanted
people,
and
particularly
security,
reachers
researchers,
to
be
able
to
look
and
find
any
vulnerabilities
we
have
in
the
code?
F
Look
at
the
code
is
very
important
if
you're
concerned
about
privacy,
you
can
actually
go
audit,
the
code,
the
code
that
is
running
on
device
and
the
code
that
is
running
in
the
server
and
you
can
see
that
we're
following
privacy,
preserving
principles,
and
this
is
really
important
and
one
of
the
ways
that
I
don't
think
we
talk
about
very
much
in
open
source.
Is
you
know
the
code
is
available?
You
can
look
at
it.
There's
lots
of
security
kind
of
talks
around
it,
but
there's
also
the
privacy
bit
as
well.
F
Is
you
know
you
can
look
at
this
code
and
you
can
see?
Is
it
phoning
home?
Is
it
publishing
metrics?
Is
it
you
know,
logging
my
ip
address
somewhere
and
all
of
that's.
You
know
available
and
visible
out
in
the
open,
with
the
work
that
we're
doing
on
the
exposure
notification
server,
and
then
we
have
a
very
similar
thing
on
the
client
side,
there's
a
sample
reference
architecture
and
application
available
on
the
android
side,
but
I'm
not
directly
involved
in
that.
So
I
can't
speak
too
much
about
what
that
looks.
Like.
E
F
Yeah,
so
I
think
businesses
have
learned
for
better
or
worse
that
there's
a
growing
need
and
a
growing
trend
where
these
businesses
just
refuse
to
operate
closed
source
software,
and
this
is
interesting
because
in
the
past
you
know
an
organization
would
just
buy
an
off-the-shelf.
You
know
software
appliance,
they
would
run
it
and
give
it
an
ip
address
and
like
boom,
it
works,
but
then
what
they
would
find
is.
It
was
very
difficult
to
upgrade
that
software.
It
was
very
opaque.
They
had
no
visibility
into
how
it
worked.
F
They
couldn't
extend
it,
they
couldn't
go,
integrate
it
with
the
hr
system
or
the
social
media
system,
because
there
was
no
visibility
into
the
system.
It
was
entirely
opaque,
no
transparency
and
worst
case
scenario.
If
the
company
that
provided
that
software
no
longer
existed,
they
couldn't
get
the
support
that
they
needed
and
oftentimes.
These
were
you
know,
critical
core
business
functionality,
so
oftentimes
businesses
are
looking
to
open
source
because
it
provides
a
safety
net.
They
know
that
if
the
the
company
or
the
community,
that's
supporting
the
software
under
the
hood
were
to
go
away.
F
F
We
can
request
approval
through
our
open
source
programs
office
and
we
have
10
and
20
projects,
but
we
also
have
googlers,
who
are
employed
full-time
to
work
on
open
source
projects.
Kubernetes
and
go
are
are
two
really
good
examples,
also
istio,
where
we
have
googlers
who
it's
their
full-time
job,
to
go.
Work
in
open
source
software.
E
Yeah,
that's
a
really
important
thing
that
a
lot
of
people
who
are
just
getting
started,
learning
about
open
source
might
not
know
about
is
that
there
are
people
who
start
doing
open
source
in
their
free
time
outside
of
their
work.
It
could
be
completely
unrelated
to
their
normal
work,
but
then
there
are
also
people
who
do
open
source
as
their
jobs
or
as
part
of
their
jobs.
F
Yeah,
so
there's
there's
people
who
you
know
are
employed
full
time
to
do
open
source
and
they're,
typically
employed
by
a
person
or
a
foundation
who
supports
that
work.
There
is
a
new
funding
model,
that's
starting
to
emerge
where
people
are
self-funded
github
has
a
program
called
github
sponsors.
There's
you
know,
services
like
patreon
and
even
just
venmo,
where
you
can
ask
people
to
donate
or
make
contributions
to
pay
your
salary
so
that
you
can
work
on
open
source
as
an
independent.
F
F
Some
people
are
working
for
a
company
and
the
company
pays
them.
This
is
part
of
their
salary
and
some
people
are
doing
it
on
a
volunteer
basis.
You
know,
especially
in
light
of
covet
people
are
working
odd
hours,
like
I
said
earlier,
the
nine
to
five
is
kind
of
dead,
so
maybe
you're
contributing
to
an
open
source
project
in
the
evenings
or
on
the
weekends.
Maybe
you're
learning
a
new
language
and
you
found
a
project.
F
That's
using
it
and
that's
a
great
way
to
marry
those
those
two
things
that
you're
exploring
and-
and
you
know
when
you're
doing
that.
I
think
another
reason
that
people
contribute
to
open
source
is
it's
more
than
code
right?
There's
a
community
around
it,
whether
that's
you
know
slack
or
discord
or
disqus,
or
you
know,
getter,
and
all
these
various
chat
forums.
Ultimately
open
source
communities
are
community
in
their
network,
and
you
know
some
people
are
feeling
a
little
bit
uncertain
in
their
job
security.
F
We've
seen
a
lot
of
layoffs
and
a
lot
of
people
are
getting
involved
in
open
source
because,
speaking
from
personal
experience,
you
can
actually
get
a
job
working
in
open
source.
You
can
network
with
companies
and
people
at
companies
who
can
give
you
referrals
and,
if
you're,
a
hiring
manager
at
a
company
that
has
head
count
and
is
actively
hiring
going
and
looking
at
open
source
projects
and
finding
people
who
are
doing
the
work
that
you
want
them.
F
That
you
think
is
valuable
to
your
company
is
a
great
way
to
you
know,
build
a
list
of
potential
candidates
and
get
them
into
an
interview
loop.
So
I
think
we're
also
seeing
a
little
bit
of
an
explosion
with
open
source
there,
because
it
does
give
people
a
bit
of
a
resume
and
it
gives
people
some
visibility
and
allows
them
to
network,
and
you
learn
a
whole
lot
more
about
how
people
work
with
one
another,
and
you
know
their
technical
ability,
whether
that's
coding
or
writing,
or
communication.
E
E
Oh
wow,
what
am
I
interested
in
with
open
source
right
now?
You
know
I've
been
looking
a
lot
at
service
meshes
lately.
The
various
technologies
involved
with
service
meshes
envoy,
linker
d
istio.
All
of
those
types
of
things
are
really
interesting
to
me,
so
I'm
excited
to
get
into
those
more
that's
something
that
I
really
want
to
get
involved
with.
F
So
I've
been
following:
there's
a
new
technology
called
cadence
from
a
company
called
temporal
that
was
spun
out
of
uber
they're
doing
this
workflows
as
code
thing.
That
I
think
is
really
interesting.
I
think
it's
really
ahead
of
the
curve
and
they
have
some
really
cool
technology,
but
the
the
cool
part
to
me
is
like
the
community
that
they've
been
able
to
build.
E
A
A
Thank
you
so
much
caslin
and
seth.
It's
crazy
to
think
about
how
many
different
ways
there
are
to
get
involved
and
contribute
to
open
source
software,
and
I
love
the
idea
that
open
source
and
work
from
home
actually
go
together
so
well
in
terms
of
kind
of
aligning
the
opportunity
with
the
possibility
and
the
demand.
So
that's
such
a
cool
idea
and
one
of
the
things
that
you
talked
about
was
this
idea
of
new
and
open
source
projects
that
we're
all
excited
about
and
so
dustin.
B
A
Yeah
I
I
love
whenever
we
can
come
up
with
kind
of
better
ways
of
storing
a
new,
better
patterns
for
developer
experience.
There
there's
two
projects
that
I'm
looking
at
right
now
one
is
called
nest
js
and
the
other
one
is
called
scully
and
they're
in
the
web.
Space
trying
to
make
developers
lives
easier
to
achieve
the
search
results
they're
looking
for
as
always
as
we
continue
here
to
our
last
session.
A
Please
put
your
questions
in
the
chat,
as
you
think
of
them,
and
start
getting
pumped
for
the
after
party,
where
we're
going
to
be
live
and
engaging
with
everyone.
We've
got
one
segment
left
to
go
before
the
after
parties
and
we're
coming
full
circle.
Here.
Megan
is
going
to
be
back
to
talk
to
us
a
little
bit
about
sustainability
in
open
source
over
to
you.
A
C
Hi,
I'm
megan
byrd,
sanechi
and
I'm
a
manager
at
google's
open
source
programs
office,
and
I
am
so
glad
that
you
are
joining
me
today
for
this
important
topic,
open
source
sustainability-
and
I
want
to
thank
you
for
making
time
because
we
all
use
open
source
so
heavily.
Now,
it's
really
important
that
we
make
sure
it's
future-proofed
and
sustainable
moving
forward,
and
we
can
only
do
that
together.
C
C
And
when
you
don't
have
that,
then
what
happens?
Is
you
start
to
see
cracks
in
the
project?
And
unfortunately,
the
project
starts
to
fall
down
on
its
ability
to
deliver
great
code,
and
it
can
eventually
just
die
on
the
vine
as
they
say,
and
so
you
really
do
need
these
ingredients
to
be
healthy
so
that
they
are
resilient
in
the
face
of
change
and
that
change
can
come
the
form
of
many
forces.
C
The
other
force
that
creates
change
and
impact
in
a
project
is
how
a
project
goes
through
different
stages
through
life
cycle
stages.
So
it
starts
small
and
might
just
be
a
few
people
working
on
it,
and
then
it
gets
bigger
and
bigger,
and
it
starts
to
need
governance
to
tell
people
how
to
work
well
together.
It
needs
more
process,
it
needs
different
kinds
of
talent
and
if
it
doesn't
have
the
right
ingredients
at
each
stage,
it's
just
not
going
to
progress
to
the
next
stage.
It
might
even
go
backwards.
C
C
Another
common
area
that
creates
a
lot
of
change.
Disruptive
change
are
global
trends
and
the
most
common
one.
The
most
recent
one
right
now
is
covet
covet
started
and
projects
that
were
relying
on
in-person
events
and
the
funding
from
those
events
found
that
they
had
to
cancel
the
events
and
they
were
scrambling
to
find
money
to
keep
their
foundations
afloat
to
pay
for
servers.
C
C
And
so
there's
lots
of
headwinds
like
this
and
others
that
I
haven't
mentioned,
but
it
is
true
that
projects
have
to
deal
with
a
lot,
whether
they
realize
it
or
not,
as
they're
getting
started
and
moving
through
their
journey.
It's
also
important
to
note
that
no
projects,
sustainability
needs
are
the
same.
C
Everyone
is
in
different
places
and,
unfortunately,
there
isn't
a
tool
out
there
to
just
tell
the
community
oh
you're,
having
resilience
issues,
and
this
is
where
you're
starting
to
see
cracks
in
the
system,
and
this
is
what
you
need
to
do
that
doesn't
exist.
You
have
to
rely
on
people
being
very
engaged
in
your
project
and
actively
identifying
these
and
there's
no
training.
C
F
C
Languish
and
there
might
be
great
ideas
in
some
of
those
pull
requests
that
just
never
get
to
see
the
light
of
day,
because
there's
just
no
one
there
to
take
it
to
the
next
level.
You
might
see
other
issues
like
a
toxic
community,
because
there
just
hasn't
been
time
to
really
create
a
welcoming
space
with
good
values
and
good
ways
of
interacting
with
each
other
good
governance,
to
ensure
that
happens,
a
code
of
conduct
things
like
that.
C
You
can
also
have
challenges
with
end
users.
They
eventually
might
just
lose
trust
of
your
project.
Maybe
they
have
security
concerns
or
they
start
seeing.
There's
lower
engagement
with
your
community
and
they're
like
yeah.
I
don't
know
if
I
want
to
invest
in
a
project
that
has
declining
community
members
and
engagement,
because
that
is
a.
E
C
Another
area
is
code
infrastructure.
So
when
a
project
isn't
resilient
and
they
don't
have-
let's
say
enough
funding-
they
may
not
be
able
to
get
the
infrastructure
they
need
to
support
the
project.
They
may
not
be
able
to
pay
for
servers
or
the
tests
that
they
need
and
it
could
impact
their
release.
Cadence.
C
Another
area
where
you
might
see
challenges
is
the
foundations
that
support
the
community
and
a
lot
of
it
has
to
do
with
funding
challenges.
If
they
just
don't
have
enough
funding,
they
can't
serve
their
mission
to
support
the
community
or
help
accelerate
innovation
within
the
community,
and
perhaps
they
aren't
able
to
fund
the
legal
and
financial
support
that
they
need
to
be
a
healthy
organization.
C
C
You
need
a
welcoming
safe
community
that
has
values
in
place
and
governance
and
culture
that
supports
diversity,
and
you
need
to
be
very
intentional
with
your
outreach,
not
just
asking
your
friend
to
join
but
really
reaching
out
to
recruit
community
members
so
that
you
truly
have
a
diverse
member
base
and
there's
so
much
more
that
you
can
do
on
this
front
that
I
won't
have
time
to
get
into.
But
I
highly
recommend
you
go
to
all
the
many
resources
that
are
out
there.
C
The
other
axis
on
diversity
is
different
types
of
contribution,
and
I
like
to
use
a
pretty
standard
frame,
which
is
time,
talent
and
treasure.
You
want
your
contributions
diversified
in
these
three
areas,
and
this
is
a
framework
that
comes
from
the
nonprofit
world
and
it
applies
pretty
well
to
open
source,
and
the
reality
is
is
that
when
you
focus
on
diverse
contributions,
you
actually
get
an
even
more
diverse
community
member
base.
So
let
me
explain
what
I
mean
so
diverse
time
and
talent
come
in
lots
of
different
ways.
C
Like
I
mentioned
before,
you
don't
want
just
to
focus
on
code
and,
of
course
you
have
to
build
code,
but
a
project
requires
so
many
other
talents.
You
need
those
tech
writers
to
write
documentation.
You
need
mentors
to
help.
People
learn
the
contributor
experience.
You
need
event
planners
to
do
meetups
and
conferences.
C
You
need
board
members
that
have
board
experience
and
so
many
other
talents.
You
simply
cannot
have
a
successful
project
with
just
coders.
You
also
need
to
be
mindful
of
where
the
contributions
are
coming
from.
Are
they
hobbyists?
Are
they
people
that
work
for
open
source
vendors
using
the
project
or
end
users
using
the
project?
C
It's
important
to
get
people
from
around
the
world
to
contribute
so
that
you
end
up
with
an
end
product
or
an
end
project
that
serves
a
global
base.
That
will
want
to
adopt
this
software
and
you
can
really
lower
barriers
when
you
have
more
of
a
global
community
base,
so,
for
example,
they
can
write
translations
so
that
end
users
around
the
world
can
really
grab
that
software,
read
the
translated
documentation
and
put
it
to
good
use.
C
A
C
C
We
saw
this
with
kova
the
projects
that
did
rely
on
this
too
heavenly
heavily
found
that
they
were
really
struggling
for
survival
and
had
to
come
up
with
new
ways
to
fund
their
mission
work.
And
so
you
want
to
think
about
events,
but
you
want
to
think
about
memberships
and
donations
and
grants.
Maybe
you
want
to
have
a
product
and
there's
other
things
about
treasure
as
well,
but
when
you
diversify
treasure
time
and
talent,
and
you
think
about
that,
you
ask
what
your
project
needs
now
and
into
the
future.
C
C
It's
the
right
thing
to
do
and
it
also
future
proofs
the
open
source
projects
we
rely
on
and
we
have
nearly
12
000
googlers
who
are
contributing
to
projects
and
that
doesn't
even
include
people
beyond
code
and
tech
writer.
So
it
doesn't
include
our
staff
members
that
are
serving
on
boards
or
planning
events
and
we
create
thousands
of
open
source
projects.
And
today
we
currently
manage
2600
active
projects
and
we
rely
on
a
lot
of
external
projects
as
well
and
we're
actually
active
in
70
000,
github
repositories.
E
C
C
You
end
up
just
focus
too
much
on
the
daily
drama.
We
just
didn't
want
that,
and
so
we
invested
in
moderator
training
so
that
we
could
help
moderators
with
effective
communication,
conflict
resolution
code
of
conduct
enforcement,
and
we're
really
excited
to
empower
these
people
to
be
much
better
leaders
in
these
spaces
and
make
sure
we
have
a
welcoming
environment
so
that
we
can
attract
diverse
community
members
and
we're
looking
forward
to
rolling
this
out
to
other
projects.
C
Example,
another
project
that
was
developed
by
google
and
has
a
community
created
around
it
and
we
intentionally
wanted
diverse
community
members
as
part
of
this
project.
It
does
not
do
anyone
good
if
it's
just
googlers
working
on
this
project.
We
need
input
from
so
many
perspectives,
and
so
we
intentionally
designed
our
governance
so
that
our
special
interest
groups
always
had
a
balance
of
googlers
and
those
that
don't
work
at
google
and
that
way
decision
making
has
much
more
perspective
and
balance
and
ensures
that
we
are
committed
to
having
this
diverse
community
base.
C
So
we
do
provide
these
kinds
of
services
for
the
projects
we
create
and
manage,
but
we
also
have
lots
of
programs
to
help
make
projects
sustainable
both
the
ones
we
create
the
ones
we
rely
on,
that
we
don't
create
and
even
ones
we
don't
use
and
these
programs
we
just
want
to
share
broadly
because
we
care
about
open
source,
the
whole
industry's
sustainability
and
health.
So
a
few
projects
or
programs
that
you
might
want
to
check
out
are
oss
fuzz,
which
uncovers
security,
vulnerabilities
and
stability
issues,
and
we
have
google
summer
of
code.
E
C
Is
season
of
docs?
It's
a
lot
like
summer
of
code,
but
it's
about
matching
tech
riders
to
projects
and
making
sure
that
these
projects
accelerate
good
documentation.
So
they
can
grow
adoption
of
their
other
software
out
in
the
marketplace
within
users
and
there's
lots
of
other
programs
that
you
can
check
out
and
you
can
go
to
opensource.google
to
find
out
what
they
are.
C
And
so
we
have
these
long-standing
programs
and
approaches.
But
we
also
know
that
things
creep
up.
These
forces
have
changed
like
covet
just
come
out
of
nowhere,
and
we
are
this.
We
attempt
to
be
as
nimble
as
we
can
to
help
out
when
these
challenges
arise.
So
for
kobe
we
did
a
couple
things
we
reached
out
to
the
projects
we
rely
on
and
simply
said:
how
can
we
help
and
we
sent
resources
in
to
help
where
we
could?
C
We
also
knew
that
many
people
had
to
take
a
break
from
their
projects
because
they
were
suddenly
doing
child
care
or
elder
care
or
finding
a
new
job.
So
we
transitioned
our
internship
program
to
bring
more
students
into
projects
and
assign
the
mentor,
so
they
could
take
on
some
of
the
load
of
the
work
and
also
learn
about
open
source
and
how
that
can
be
a
future
career
path
for
them.
C
C
You
know,
heard
the
call
and
came
out
and
contributed
time
and
talent
to
projects
like
coveted
act
now
and
next
strain
and
schema.org,
and
we
also
helped
a
lot
of
projects
shift
from
in-person
events
to
online
events
like
this
one.
We
did
it
by
creating
a
guide
and
sharing
it
broadly
with
the
open
source
community.
C
C
So
these
are
you
know
the
things
that
we
do,
but
if
you
want
to
get
started
and
contributing
to
open
source,
you
can
do
it
today
and
you
don't
need
to
be
part
of
a
big
enterprise
to
make
a
difference.
Everything
counts.
So
here
are
a
few
pro
tips
that
you
might
want
to
try
right
away.
First
is
just
going
to
the
project
you
love
and
use,
and
asking.
How
can
I
help
trust
me?
C
People
will
point
in
the
right
direction,
but
if
you
don't
want
to
do
that,
just
go
over
and
start
answering
issues
or
see.
If
there's
any
languishing
pr's
that
you
can
close
out
and
you
can
always
fund
a
project,
you
could
buy
a
membership,
you
could
donate,
you
could
even
buy
a
t-shirt.
That
kind
of
money
helps
too,
and
you
can
look
at
our
sustainability
programs
on
opensource.google
and
see
which
ones
might
help
your
project
and
apply
for
all
of
them.
We're
happy
to
share
our
resources
and
we
really
want
to.
C
Another
pro
tip
is
to
learn
more
about
sustainability,
and
you
can
do
so
with
this
great
resource
that
nadia
eggball
wrote
with
the
ford
foundation
called
roads
and
bridges.
That
really
explains
the
basics
of
sustainability,
and
so
I
hope
you'll
check
that
out.
I
hope
that
you
will
start
thinking
of
ways
that
you
can
contribute
because,
like
I
said,
every
little
bit
matters,
and
this
is
how
we
keep
open
source
alive
today
and
into
the
future.
B
Anytime,
thanks
megan,
that
was
a
really
great
talk
as
a
maintainer
of
the
open
source
project.
Actually
multiple
open
source
projects.
Sustainability
is
definitely
my
number
one
concern.
I'm
always
thinking
about
it
with
the
projects
that
I
work
on.
This
is
also
a
perfect
way
to
wrap
up
our
very
first
google
open
source
live
event.
So
now
we're
going
to
be
moving
to
the
after
party,
you
should
be
automatically
shown.
Two
links
to
watch
live
on
the
event
page
and
today's
speakers
will
be
available
to
answer
questions
and
chat
with
you.
B
We'll
also
have
some
q
a
for
you
all
as
well.
We'll
do
some
quick
polls
just
to
see
what
everyone's
experience
and
with
open
source
has
been.
The
links
for
the
after
party
will
also
be
shared
in
the
chat
throughout
the
sessions
and
we'll
help
you
join.
We
do
have
limited
spots
available
at
the
after
party,
so
we'll
be
on
a
first
come
first
serve
basis,
we'll
do
our
best
to
accommodate
everyone,
and
I've
had
so
much
fun
today
doing
this
event,
how
about
you
stephen?
I
I've.