►
From YouTube: Keynote: Stories that might make you a contributor
Description
The Cloud Native community has a large number of contributors, each with their own unique story on how they became a project maintainer or a community member. I want to share stories of a few of these key individuals while also highlighting how the CNCF helped them along their journey.
A
Hello
and
welcome
to
kubernetes
community
days
bengaluru.
My
name
is
jeffrey
sika,
I'm
commonly
known
as
gfe
across
the
internet,
and
I
work
at
the
cloud
native
computing
foundation.
I'm
really
happy
to
be
here
and
excited
to
share
three
contributors
stories
from
how
they
started
out
and
where
they
went
in
their
open
source
journey.
A
A
A
A
In
these
sessions,
there's
usually
a
pool
of
mentors
that
get
matched
with
a
much
larger
pool
of
mentees.
Once
you
get
matched
up,
you
sit
at
a
table
and
you
can
ask
questions
that
vary
from.
How
can
I
talk
to
my
manager
about
contributing
to
more
open
source
projects
to
technical
questions
about
kubernetes
api
server
performance?
A
It's
it's
a
wide
gamut
of
you
know
different
kinds
of
topics,
depending
on
the
mentee's
focus
they'll
get
paired
with
a
mentor
who
specializes
in
the
questions
they
want
to
discuss
after
the
session
ended
some
of
the
mentors
and
mentees
stuck
around
to
chat
while
deciding
what
sessions
to
attend.
Next.
If
we
wanted
to
go
and
grab
lunch,
including
person
a
and
that
kind
of
fostered
a
friendship,
there
was
a
relationship
there,
twitter
handles
were
exchanged,
memes
were
exchanged
and
fast
forward.
A
A
A
This
fund
exists
to
support
individuals
who
may
not
otherwise
have
the
opportunity
to
attend
in
one
of
three
categories:
it's
either
diversity
needs
based,
or
students,
person,
b
and
c,
both
applied
for
and
qualified
to
get
travel
support
to
a
kubecon
cloud
native
con
they'd
previously
both
been
off
and
on
contributors
to
kubernetes,
but
after
they
had
each
attended,
a
contributor
summit
hosted
at
a
kubecon.
This
is
where
their
stories
diverge.
A
Person
b
had
been
helping
out
in
contributor
experience.
Another
sig
within
kubernetes
sigmeen's
special
interest
group.
They
had
been
attending
weekly
meetings
and
helping
take
notes.
Some
time
later,
they
branched
out
to
help
with
the
kate's
info
working
group,
which
is
a
working
group
tasked
with
migrating
the
kubernetes
project
off
of
google-owned
infrastructure
and
onto
community-owned
infrastructure.
A
They
are
now
one
of
the
github
project
admins
for
kubernetes.
This
is
one
of
the
highest
trusted
positions
as
it
is
what
it
says.
You
have
admin
rights
over
all
of
the
kubernetes
orgs
and
repos
now
onto
person
c.
They
had
a
very
similar
path.
They
were
helping
out
in
contributor
experience,
but
soon
started
helping
organize
a
contributor
summit.
They
were
shadowing
one
of
the
previous
heads
of
registration.
A
A
A
A
A
A
This
is
just
saying
things
like
hey:
I've
been
contributing
for
the
last
three
months.
Things
are
happening
right
now
with
my
personal
life.
I
need
to
you
know,
take
three
weeks
off:
I'm
not
gonna,
be
at
the
meetings
or
things
like
hey,
I'm
getting
a
bunch
of
free
time,
and
I
know
that
there
is
this
effort
that
the
project
is
wanting
to
try
and
push
forward.
I
should
be
able
to
commit,
say
10
hours
a
week
to
it
and
likewise
something's
come
up.
A
A
The
hurdle
is
becoming
a
so-called
maintainer,
not
just
a
contributor.
Sometimes
those
are
interchangeable,
but
a
contributor
is
someone
that
has
just
submitted
a
pr
and
had
it
merged.
A
maintainer
is
someone
that
you
know
continues
coming
back,
they're
a
community
member
and
becoming
a
community
member.
That's
where
those
three
c's
come
in
so
becoming
a
maintainer
of
an
open
source
project
is
difficult
and
it
takes
time
it
takes
effort
and
it
takes
trust
on
the
part
of
others
in
the
project.
A
A
I
will
say
that
it
is
not
for
everybody,
but
I
think
it
is
again
one
of
the
most
gratifying
things
you
can.
You
can
strive
to
be
with
that.
I
normally
keep
my
talks
kind
of
shorter
so
that
I
can
interact
with
the
crowd
and
ask
questions,
or
rather
have
questions
asked
and
then
answer
them
and
can't
really
do
that
right
now.
A
A
A
A
If
you
are
interested
in
technical
writing,
we
need
more
technical
writers.
Everyone
needs,
you
know
docs
to
be
improved.
So
that's
that's
where
I
would
say
start
off
first,
so
that
actually
leads
into
a
next
common
question
that
I
get.
What,
if
I'm
not
a
technical
person
well,
first
off,
there
is
still
plenty
to
do
if
you
want
to
contribute.
A
Docs
is
usually
where
I
send
people,
because
everyone
knows
a
language.
Everyone
should
be
able
to
take.
You
know
these
these
technical
concepts
and
then
apply
them,
and
if
they
can't
there
might
be
something
wrong
with
the
docs.
Likewise,
if
you
are
bilingual,
being
able
to
translate
docs
between
languages
is
a
massive
massive
win
for
a
project
because
it'll
increase
adoption
and
it
also
grows
the
potential
contributor
base
by
increasing
adoption.
A
A
A
The
inability
to
focus
on
something
or
just
you
know
simply
being
throwing
your
hands
up
in
the
air
and
saying
I
I
can't
I'm
done
when
we
have
very
technical
and
kind
of
highly
cognitive
careers
and
jobs.
We
are
very,
very
susceptible
to
burnout
and
it's
kind
of
what
it
sounds
like
candle's
burnt
out.
There's
it's
hard
to
motivate
yourself.
It's
hard
to
you,
you're
in
a
rut
you're
in
a
pit
and
you're
trying
to
dig
yourself
out,
but
you
don't
have
a
shovel.
A
It's
it's
very,
very
difficult,
and
one
thing
that
I
can
say
with
certainty
is
being
an
open
source.
Maintainer
accelerates
that,
like
tenfold
compared
to
certain
people
that
just
you
know,
are
engineers
at
large
companies,
but
they
don't
contribute
to
open
source
outside
of
work
being
an
open
source
maintainer
and
also
trying
to
kind
of
double
dip
between
your
job
and
open
source
is
very
difficult
to
do
over
time.
A
So
that's
where
time
management,
skills
and
just
being
realistic
with
yourself
is
super
helpful,
being
cognizant
of
your
moods
being
cognizant
of
just
what
you
can
and
can't
do,
and
also
having
a
support
structure
in
place,
and
this
is
where
community
comes
in.
There
have
been
multiple
people
in
the
kubernetes
community
that
have
reached
out
to
me:
hey
are
you
doing?
Okay?
A
A
So
that's
burnout
is
usually
something
that
I
want
to
always
address
when
it
comes
to.
How
can
I
become
an
open
source
maintainer,
because
it's
something
that
everyone
is
going
to
have
to
deal
with
at
some
point
and
knowing
about
it
up
front
and
kind
of
being
open
about?
It
is
always
going
to
help
more
people,
and
with
that
that's
all
I
have.
I
am
so
excited
to
have
done
this
this.