►
From YouTube: SIG Contributor Experience Deep Dive - Nabarun Pal & Madhav Jivrajani, Marky Jackson, Kaslin Fields
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-21. Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
SIG Contributor Experience Deep Dive - Nabarun Pal & Madhav Jivrajani, VMware; Marky Jackson, Equinix; Kaslin Fields, Google Cloud
Speakers: Marky Jackson, Nabarun Pal, Kaslin Fields, Madhav Jivrajani
The Kubernetes Contributor Experience Special Interest Group (SIG) is tasked with developing and sustaining a healthy contributor community. It also provides an excellent place to get involved with the Kubernetes project, either through code, non-code, or both. Join us and learn about ContribEx's many programs that you can participate in, including mentoring, meetings, community infrastructure, moderation, elections, contributor events, the contributor site, and more. Whether you're interested in helping the Kubernetes project run smoothly, or you want to see how these programs can benefit you, or just have questions about how the project is organized, you'll find answers here.
A
B
A
So
let's
get
started.
So
let's
talk
about
like
how
big
is
the
kubernetes
community
or
who
constitutes
the
kubernetes
kubernetes
community.
So
one
of
the
figures
that
I
want
to
really
talk
about
here
is
the
number
of
contributors
that
we
have.
We
have
almost
like
73
000
contributors,
and
it's
growing
year
on
year.
In
the
last
one
year
we
have
had
10
000
new
contributors.
These
are
unique
contributors
who
have
ever
touched
the
code
base.
A
B
And
we
here
up
here
are
all
members
of
Sig
contributor
experience,
we'll
be
talking
more
about
what
the
special
interest
group
for
contributor
experience
does.
The
last
Slide
by
the
way
was
a
picture
of
our
contributor,
Summit
and
all
of
the
folks
in
the
the
contributor
community.
So,
while
we're
focusing
today
on
the
special
interest
group
for
contributor
experience,
we
all
Focus
very
much
on
our
contributor
community,
so
everyone
within
the
project,
whatever
they
may
work
on
within
kubernetes
our
goal-
is
to
serve
them,
as
we
kind
of
say
on
the
slide.
B
So
our
goal
is
to
make
sure
that
we're
creating
useful
processes
and
making
sure
that
our
contributors
in
the
community
basically
have
a
good
time
over
time.
Our
community
changes,
as
we
said,
it's
always
growing,
so
we
always
have
need
for
new
processes
for
contributors
to
be
able
to
do
their
work
more
efficiently
more
smoothly.
Also,
sometimes
we
grow
out
of
processes.
So
we
need
to
make
sure
that
we
are
retiring
old
processes
that
don't
work
for
the
community
anymore
and
replacing
them
with
new
ones.
B
If
you
are
interested
in
joining
our
group,
you
can
find
the
various
sigs
and
working
groups
on
khs.dev
kate's.dev
is
our
contributor
website.
So
we
try
to
post
a
lot
of
contributor
resources
and
information
there
so
check
that
out
for
our
list
of
groups
of
community
within
our
community
and
for
the
meeting
list.
B
So
one
of
the
big
recommendations,
if
you've
ever
if
you're
one
of
those
folks
who's
trying
to
get
involved
with
the
community
or
if
you've
ever
been
one
of
those
folks,
as
we
all
have
you've,
probably
heard
a
million
times
join
us
at
our
regular
meeting
and
you're
like
where
do
I
find
these
meetings.
We
do
have
a
list
of
all
of
the
meetings
that
are
happening
within
the
kubernetes
community,
not
just
a
single
Sig,
but
all
of
them
kind
of
in
one
place,
and
you
can
also
find
that
on
khs.dev,
so
very
useful
website.
B
So
within
Sig
contributor
experience
like
I,
said:
there's
a
lot
of
different
areas
that
we
focus
on
it's
kind
of
nebulous
to
say
we
help
communic
our
contributor
Community
do
the
best
work
that
they
can
and
do
it
smoothly.
So
here
are
a
few
of
the
areas
that
we
focus
on
and
really,
though,
the
way
that
we
accomplish
this
is
with
sub-projects,
which
we're
going
to
cover
in
a
little
bit
more
detail.
C
So
considering
the
scope
of
contributed,
experience
is
cross-sec
and
we
have
a
gigantic
amount
of
work
that
we
do
the
more
if
we
try
to
do
this
efficiently
by
breaking
our
work
down
into
what
are
known
as
sub-projects
and
each
subproject
has
an
amazing
set
of
contributors
who
take
it.
Forward
Define
road
maps
help
new
contributors
and
so
on
so
skimming
over
a
list
of
our
sub-projects.
Before
we
dive
deep
into
each
one
of
them,
we
have
the
community
subproject,
which,
as
the
name
suggests,
owns
and
manages
overall
Community.
C
We
have
a
kubernetes
community
repository,
and
this
is
what
the
sub
project
helps
manage.
Take
forward
even
deprecate
a
few
things.
Then
we
have
Community
Management,
which
manages
it
defines
policies,
changes,
policies
for
the
Upstream
community
group
and
we
have
contributed
documentation
which
is
one
of
my
personal
favorites
rights
and
maintains
documentation
around
contributing
to
kubernetes.
So
this
involves
things
like
how
do
I
run
tests.
This
involves
things
like
how
do
I
onboard
new
contributors
and
so
on.
C
C
We
have
events
which
creates
and
plans
events.
We
have
GitHub
management,
which
manages
and
controls
GitHub
permissions
for
repose.
We
have
nabaron
here
who
is
also
a
GitHub
admin
for
the
kubernetes
project.
We
have
mentoring,
which
is
probably
one
of
the
most
crucial
sub-projects
we
have
as
of
now,
which
overseas
and
develops
monitoring
programs.
We
have
slack
infrastructure
and
elections,
which
is
our
newest
sub
project
that
we
will
soon
talk
about.
C
Okay,
so
before
I
talk
a
little
bit
about
mentoring,
we
have
what
is
known
as
the
contributed
ladder
defined
in
the
community,
so
we
start
off
with
non-member
contributors.
So
these
are
any
folks
who
have
just
come
into
the
community
who
want
to
get
started
from
non-member
contributors.
You
contribute
you
help
out,
and
then
you
can
become
a
member
of
the
kubernetes
org.
What
this
essentially
allows
you
to
do
is.
C
You
to
move
ahead
in
your
contributor
journey
to
becoming
a
reviewer
to
becoming
a
reviewer
who
is
essentially
reviewing
PR's
review
code.
Non-Code
doesn't
really
matter
did
not
even
not
just
piaz.
You
are
also
helping
review
documents,
you're
also
helping
review
policies
which
eventually
make
it
to
one
of
the
GitHub
repositories
that
we
might
have
beyond
the
reviewer.
We
have
the
upper
river,
who
is
responsible
for
approving
certain
changes?
Who
has
the
final
sign
off
in
terms
of
okay?
This
is
a
valid
change.
This
makes
sense
for
our
community.
C
C
They
are
tasked
with
leadership
responsibilities
and
for
the
entire
repository.
Essentially,
so
in
the
mentoring
subproject,
we
have
a
few
programs
programs
and
initiatives.
Firstly-
and
this
is
really
exciting-
we
have
group
mentoring
cohorts,
so
these
are
semi-structured
group
mentoring
initiatives
with
a
small
set
of
people
who
are
paired
with
existing
reviewers
or
approvers
from
a
particular
group.
C
Very
interestingly,
in
the
past
month
we
had
six
clients,
say
gaps,
kickoff
group,
mentoring,
cohorts
which
was
a
really
big
milestone,
and
thank
you,
Paris,
atharva
and
purneshwar
for
helping
drive
this
forward.
We
need
more
sex
and
working
groups
to
do
this.
Essentially,
so,
if
you
are
a
sick
or
a
working
group
or
help
maintain
a
sub
project
that
would
want
to
run
one
of
these
group
mentoring
cohorts
to
Foster
the
next
set
of
reviewers
and
approvals
for
your
project.
C
Please,
please
feel
free
to
reach
out
to
us
on
the
sick,
contact,
slack
Channel
email
list.
Wherever
you
see
fit,
we
are
more
than
happy
to
help
out,
and
then
we
have
Shadow
programs
which
are
scalable
Apprentice,
a
print
ship
programs.
So
most
famously
the
release
team
ran
really
really
well
defined
and
well-run
Shadow
programs,
and
most
recently
sick
cornerbacks,
also
is
running
a
shadow
program.
All
of
us
are
shadows
here,
standing
in
front
of
you,
so
if
your
state
wants
to
run
a
shadow
program,
we
have
some
experience.
C
We
also
defined
a
third
party
mentorship
coordinator
role
recently,
who
essentially
helps
coordinate
what
third
party
mentorship
programs
that
exist
so
Google
summer
of
code
LFX
how
it
reaches
so
on
and
so
forth,
but
these
programs
can
only
be
done
if
we
have
sufficient
help.
So
you
know
help
is
always
wanted.
So
if
you
are
willing
to
coordinate
some
of
these
efforts,
reach
out,
you
know
like
just
Reach
Out,
regardless
it
doesn't
really
matter.
We
are
nice
people,
we,
a
big
win.
C
Was
we
worked
on
Hands-On
labs
for
onboarding
new
contributors,
so
this
wasn't
introduction
to
kubernetes,
but
this
was
introduction
to
how
to
contribute
to
kubernetes.
So
things
like
how
do
I
run
tests
on
my
on
on
changes
that
I
introduced
into
the
kubernetes
project?
How
do
I
see
these
changes?
In
effect?
How
do
I
test
these
changes
out
and
so
on
and
so
forth?
And
these
are
sort
of
tips
and
tricks
that
existing
contributors
and
maintainers
have
used,
and
these
were
compiled
by
our
LFX
mentee
harshita.
C
C
Github
management
kubernetes
loves
GitHub
because
of
which
we
do
cool
things
like
this.
We
have
Pro,
which
is
our
internal
CI
CD
system.
Well
CI
system
and
you
can
do
we
know.
Nikita
is
commenting.
Slash
woofier
like
this
is
one
of
my
favorite
things.
So
our
GitHub
management
project
manages
and
controls
GitHub
permissions
for
repos
and
groups.
C
C
In
GitHub
management,
we've
been
trying
to
improve
the
experience
of
Auto
closing
issues,
so
in
kubernetes
we
Auto
close
issues
that
are
still
for
more
than
30
days
without
any
activity
we
ought
to
close
PRS
as
well,
but
this
leads
to
understandably
leads
to
some
friction
in
terms
of.
Why
was
this
closed?
What
can
we
do
better
and
so
on
and
so
forth?
So
we've
been
trying
to
improve
on
that
part
of
that
was
adding.
Support
for
closing
issues
has
not
planned
and
better
handling
support
requests.
C
One
of
the
biggest
things
that
we're
working
on
right
now
is
the
approved
2
plugin.
This
helps
us
granularly
approve
code
changes
rather
than
doing
a
blanket
approval
for
each
directory.
This
lets
us
approve
on
a
file
level,
so
helps
us
delegate
reviewing
and
approving
better
helps
us
helps
us
delegate,
review
and
reviewing
and
approving
better
helps
us
handle
cases
such
as.
How
do
we
approve
dependency
changes?
How
do
we
approve
root
directory
changes
and
so
on
and
so
forth?
And
then?
C
B
Sure
I
am
there
are
a
variety
of
ways
that
we
kind
of
keep
the
community
moving
together
and
visible,
so
any
contributors
that
want
to
get
involved
with
us.
You
should
certainly
check
out
our
mailing
lists.
We
mentioned
the
calendar
earlier
so
on
kate's.dev
we
have
the
community
calendar
where
you
can
see
all
of
the
meetings
going
on
throughout
the
project.
We
also
have
our
Infamous,
perhaps
kadev,
which
is
our
mailing
list,
that
we
send
messages
out
to
basically
all
the
active
contributors
to
so
join
kadev.
B
We
recently
migrated
our
mailing
list.
It
has
been
updated
and
is
better
than
ever.
I
highly
recommend
joining
another
thing
I
wanted
to
mention
is
YouTube.
If
you've
ever
been
to
any
of
these
contribution
meetings
or
been
told
that
you
should
join
a
contribution,
meeting,
you've
probably
heard
that
they're
all
recorded
and
that
we
share
all
of
the
work
that
we're
doing
publicly.
B
B
We
also
have
a
community
repo
as
with
any
open
source
project.
We
do
a
lot
of
our
work
in
GitHub
and
that's
not
just
for
code
contribution.
That's
not
just
the
kubernetes
project
itself
here
in
contributor
experience.
A
lot
of
our
work
is
documented
in
GitHub
as
well
so
definitely
check
out
the
community
repo
it's
fairly
large.
It
has
a
lot
of
different
areas
in
it.
I've
learned
a
lot
by
just
exploring
that
repo.
B
We
use
zoom
primarily
for
our
meetings,
so
I
mentioned
that
we
record
them.
We
record
them
over
zoom
and
we
we
host
most
of
our
meetings
over
Zoom.
We
are
always
looking
for
help
to
automate
the
publishing
of
those
videos
to
YouTube
to
make
that
process
smoother.
So
if
that
sounds
like
something
you
might
be
interested
in,
let
us
know
we
have
discuss.kates.io,
which
is
a
community
Forum,
where
you
can
talk
about
all
sorts
of
things.
B
Kubernetes
related
and
I
also
mentioned
in
here
that
we
have
some
folks
who
helped
make
sure
that
the
videos
from
all
of
our
meetings
get
into
YouTube.
That's
one
form
of
moderator.
We
also,
of
course,
have
our
slack
like
I
mentioned.
We
need
moderators
in
there,
so
there
are
moderator
opportunities
all
throughout
the
community.
B
If
you're
interested
in
helping
to
moderate
discussion
in
the
community,
specifically
I
want
to
talk
a
little
bit
more
about
YouTube
moderation,
so
we
have
our
kubernetes
YouTube
channel
and
it
has
separate
playlists
for
special
interest
groups,
working
groups
and
user
groups.
The
meetings
from
all
of
those
different
communities
are
organized
into
these
playlists.
B
So
that's
a
lot
of
recordings
to
deal
with
and
a
lot
of
organization
that
goes
into
it.
We
also
do
recordings
of
regular
events.
We
mentioned
the
events
group,
so
one
regular
event
is
the
kubernetes
community
meeting,
which
is
a
monthly
thing
ish
not
this
month,
because
we're
at
kubecon
we
also
do
office
hours
and
we
like
to
do
meet
our
contributors
sessions
where
we'll
regularly
have
prominent
contributors
or
any
contributors
on
to
talk
with
the
community
and
answer
questions.
B
B
But
it's
a
relatively
few
simple
steps:
there's
not
as
much
really
intense
complex
time
involved
in
it
like
you
would
have
to
do
with
editing,
as
you
might
think.
So,
if
you're
interested
in
YouTube
Administration,
we
could
really
use
some
help
and
would
love
to
have
you
so
do.
Let
us
know
if
you're
interested
in
being
a
YouTube
administrator
or
admin
or
moderator
all
of
those
and
I
am
the
sub-project
lead
for
contributor
comms.
B
We
mentioned
this
a
little
bit
earlier
when
we
were
doing
the
overview
of
some
of
the
sub
projects,
so
in
contributor
comms.
Our
focus
is
on
making
sure
that
the
contributor
Community
knows
what's
going
on
and
also
that
folks
externally
can
see
the
awesome
work
that
contributors
are
doing.
The
kubernetes
project,
of
course,
has
our
regular
releases.
We
talk
about
the
features
that
we've
done,
but
there
are
all
sorts
of
really
awesome
things
that
contributors
are
doing
both
during
release
and
between
release
Cycles.
B
So
we
want
to
make
sure
that
people
are
being
recognized
for
their
awesome
work
and
that
contributors
know
about
contributor
events
like
the
community
meeting
and
changes
that
are
happening
to
processes
that
might
affect
contributors.
So
we
do
a
lot
of
work
around
that
one
way
that
we
communicate
is
with
Twitter.
B
If
you
haven't
already,
please
follow
the
Kate's
contributors
handle
on
Twitter,
we're
doing
a
bunch
of
tweeting.
During
the
conference
we
actually
have
a
way
to
scheduled
tweets
onto
that
account
not
really
schedule
to
get
tweets
onto
that
account.
Using
GitHub,
like
I,
mentioned,
a
lot
of
contributor
work
is
through
GitHub,
so
we
want
to
make
our
methods
of
communication
as
accessible
to
our
contributors
as
possible,
and
our
goal
with
this
Twitter
account
is
for
any
contributor
to
be
able
to
submit
a
tweet
to
be
posted
there.
B
So
we
have
a
GitHub
based
process
where
you
can
submit
an
issue,
it'll
turn
it
into
APR,
and
once
that
PR
gets
merged,
it'll
be
tweeted,
so
that's
pretty
cool.
We
also
have
a
new
tool
called
buffer
which
we're
using
for
more
complex
requests
for
tweeting.
So
if
you
get
involved
with
the
group,
we
can
get
you
familiar
with
that
tool.
B
Contributor,
focused
content
and
stories,
sometimes
we'll
write
blog
posts
or
create
videos
or
create
other
content
to
promote
contributor
activities,
bring
attention
to
areas
that
need
help
in
the
community.
When
the
annual
report
comes
out
every
year,
we
try
to
make
sure
to
highlight
The,
Help,
Wanted
sections.
B
B
C
Summit
is
the
primary
event
for
kubernetes
contributors
to
get
together
collaborate
just
catch
up,
and
also
you
know.
We,
we
also
host
a
steering
AMA
in
the
contributor
Summit,
where
we
have
questions
focused
more
towards
the
broader
health
of
the
community
more
towards
what
is
the
way
forward
in
the
next
year.
What
do
we
need
help
with
and
so
on
and
so
forth?
We
also
this
the
the
earlier
the
contributor
summary
that
we
just
had.
A
Okay,
so
this
is
a
very
new
sub
project
that
we
started
very
recently
to
give
you
some
context.
Every
year
we
run
one
public
election
where
every
contributor
votes
and
it's
the
steering
committee
elections,
because
the
part
of
the
steering
committee
rotates
every
year
and
back
in
history,
we
used
to
conduct
the
election
using
a
tool
called
saves,
which
is
the
condo
set
internet
voting
system.
A
But
the
operations
around
the
system
was
a
little
difficult
to
manage
for
the
community
as
in
how
do
we
sustainably
manage
them
and
are
there
like
concrete
processes
to
do
it?
What
we
instead
started
to
work
on
was
I
think
a
couple
of
years
back
was
a
tool
called
Electro.
It's
a
flask
cap
written
to
basically
manage
elections
using
git
artifacts.
A
These
are
like
good
to
have
improvements,
so
if
you
know
python
flask
or
in
general,
if
you
want
to
write
docs
around
the
election
system
feel
free
to
like
join
us
in
the
Sig
contracts,
elections,
Channel
and
start
discussing
with
us
like.
How
can
we
solve?
No?
That's
not
all
if
you
are,
if
you
have
been
a
member
of
the
community
and
know
of
the
elections
already
every
year
when
the
election
happens,
we
need
certain
election
certain
number
of
election
officers.
A
So
if
you
want
to
help,
do
come
to
us
right
away
because
even
for
the,
even
though
the
next
elections
are
almost
like
10
months
away,
we
really
like
to
start
preparing
early.
For
example,
casting
was
the
was
one
of
the
election
officers
this
year,
Josh
used
to
be
an
election
officer
until
last
year
and
Electro
has
been
created
by
Manish,
who
has
been
in
I,
think
in
LFX,
20
or
in
one
of
the
mentorship
programs
and
by
Josh,
thanks
to
all
of
the
contributors
who
have
contributed.
A
I
I
just
could
name
two
but
I
think
there
are
like
eight
or
nine
contributors
who
have
contributed
to
Electro.
This
is
a
really
great
thing,
as
we
say
like
not
all
of
the
kubernetes
community
requires
go
knowledge.
If
you
know
python
is
a
great
thing
to
contribute
to
moving
ahead,
contributed
documentation.
So
casein
mentioned
the
kubernetes
community
repo,
where
you
can
come
and
see
like
what
community
groups
we
have.
A
What
is
the
structure
now
I
have
to
I
want
to
mention
the
contributor
guide,
which
is
in
the
community
repo
that
helps
people
know
the
overall
architecture
of
the
community.
Now,
what
about,
if
you
want
to
get
like
in-depth
knowledge
of
how
do
you
run
tests?
How
do
you
set
up
the
project?
How
do
you
run
end-to-end
tests?
What
are
even
end-to-end
tests?
What
are
integration
tests?
A
Now
back
couple
cover
a
couple
of
years
back
what
we
realized
was.
We
need
to
have
a
Central
repository
or
a
portal
or
a
website
or
a
front-end
where
which
caters
to
contributors
of
the
community,
and
we
do
have
it
now
at
kts.dev,
you
can
go.
There,
have
a
look
at
what
community
events
are
happening.
There
is
a
calendar
as
well
where
you
can
go
and
see
which
events
are
scheduled
every
day.
If
you
want
to
join
them,
you
can
have
a
track.
We
have.
A
A
A
If
you
can
come
understand
what
we
have
written
and
re-implement
it
in
something
that
more
people
understand
and
which
is
like
more
testable,
I
think
that's
the
Mantra
that
we
go
by
in
the
community
like
if
we
just
write
something
and
then,
if
it
flies,
we
want
to
write
more
tests,
make
it
sustainable.
Just
come
on
board.
We
have
been
working
on
contributor
course
to
make
people
like
go
through
scenarios
of
how
do
you
contribute
to
kubernetes?
A
A
A
Have
been
asking
this
question,
you
keep
on
talking
about
caps.
Every
contributor
keeps
on
talking
about
caps
and
we
know
like
what
are
those,
but
if
I
have
to
go
through
history
and
look
at
like
what
got
implemented,
when
do
I
really
need
to
go
to
GitHub,
repo
or
maybe
use
search
engine,
but
then
the
results
may
not
be
in
text
like
you
want.
We
did
have
a
solution
to
this
all
this
while,
but
it's
just
that
we
needed
to
have
it
repackaged
as
a
good
front
end
that
can
be
consumed
by
end
users.
A
A
You
can
just
do
a
plain,
simple
search,
and
it
will
return
you
all
the
Caps
that
are
there
now.
We
need
a
lot
of
help
in
this
as
well,
so
this
is
just
the
first
iteration
on
the
top
of
my
mind,
one
Improvement
that
can
that
I
can
speak
about.
Is
that
right
now
this
doesn't
search
through
the
kept
contents,
so
we
need
help
like
enabling
that
feature
or
implementing
that
or
thinking
through.
How
do
we
design
such
a
feature?
A
C
I'm
gonna
go
a
little
faster
since
we
have
approximately
five
minutes
left.
Maintainers
is
probably
one
of
the
most
exciting
areas
that
I'm
looking
forward
to
in
the
next
year.
So
this
is
a
tool
that
one
of
our
community
members
dims
a
lot
of
you
might
know
him
wrote
this
is
this:
is
a
tool
to
provide,
contributed
statistics
to
try
and
help
gauge
broader
Community
Health.
It
passes
owners
files
in
kubernetes
or
any
repository
within
the
kubernetes
org
owners
fires
owner
aliases.
C
It
also
queries,
GitHub
and
Dev
stats
to
try
and
see
how
many
folks
are
active.
What
folks
are
present
as
reviewers
or
approvers,
who
have
not
been
active
for
a
certain
amount
of
time
and
doing
this
is
important,
because
these
are
folks
that
you
might
assign
to
your
contribution
in
order
to
get
it
approved,
but
if
they
are
not
active,
your
PR
goes
stale
and
that's
not
probably
not
not
the
best
thing
to
do.
C
We
are
also
trying
to
get
and
run
this
maintenance
tool
as
a
periodic
in
our
community
in
order
to
try
and
see
if
we
can
automate
some
of
these
things
and
basically
give
better
signal
to
six
in
terms
of
what
do
we
need
to
do
next,
and
so
all
that
being
said
explicitly,
how
can
you
contribute
right?
We
have
an
excellent
Community.
We
have
especially
like
say:
Quantum
breaks
is
one
of
our
favorite
ones,
favorite,
six
in
the
community
getting
involved.
The
first
step
is
attending
a
Sig
meeting.
B
B
So
if
you
are
interested
in
hearing
about
the
Sig
kind
of
as
a
whole
in
a
kind
of
General
sense
attend
that
bi-weekly
meeting
our
sub
projects
also
have
their
own
regular
meetings.
Contributor
comms,
for
example,
meets
every
week
on
Fridays,
so
check
out
that
community
calendar
for
all
of
them
or
go
to
the
specific
subprojects
to
learn
more.
All
meetings
are
uploaded
to
YouTube,
so
you
can
always
find
them
there.
B
B
So
if
you
want
to
attend
your
first
Sig
meeting
here
are
a
few
tips
to
make
it
worth
your
while
and
to
help
you
continue
contributing
if
you
can
go
with
a
buddy.
Sometimes
it's
useful
to
be
able
to
talk
about
the
meeting
afterwards
with
someone
else
that
you
know
that
can
be
really
helpful
for
remembering
what
happened
and
for
keeping
each
other
honest
if
you
want
to
contr
like
really
start
contributing
regularly
regularly,
is
always
the
hardest
thing
volunteered
to
take
notes.
B
I
know
I
for
one
have
a
horrible
memory,
so
I
need
to
take
notes
in
order
to
remember
what
happened.
It's
also
a
huge
help
to
the
community,
because
a
lot
of
people
have
that
issue
and
it's
useful
to
be
able
to
go
back
to
the
notes
and
see
what
happened
and
you'll
have
your
name
on
the
notes
in
a
particularly
prominent
place,
so
you'll
get
more
recognition
attend
regularly.
My
advice
to
new
contributors
is
always
just
to
be
stubborn.
B
If
you
want
to
contribute
regularly-
and
you
start
going
to
meetings
and
you're,
not
really
sure,
what's
going
on
and
you're,
not
sure
how
you
can
help,
nobody
gave
you
anything
to
do,
that's
how
it
always
starts
so,
but
the
more
of
those
meetings
you
attend
the
more
regular
of
a
face.
You
are
the
more
stuff
you'll
get
assigned
to
you
and
the
more
you'll
become
a
part
of
that
community,
so
be
stubborn.
B
Just
keep
attending
small
Dependable
contributions
are
what
we're
built
on
and
sigs
generally
try
to
have
good
first
issues:
there's
a
label
in
GitHub.
So
if
you're
looking
for
something
to
do,
you
can
look
for
those
oftentimes,
they
don't
use
that
label
as
consistently
as
they
should
so
definitely
chat
with
the
sigs
Don't
Be
Afraid.
Lots
of
folks
are
really
friendly,
so
reach
out.
If
you
want
something
to
do
next,
there
are
also
non-code
related
paths
available.
B
Like
we
mentioned
in
contributor
comms,
we
have
Twitter
and
we
have
a
variety
of
other
things
that
we
do,
that
don't
involve
coding.
We
also
mentioned
a
few
other
projects
like
Electa,
where
you
can
do
more
code
contribution
or
the
website
contribution,
so
there's
a
variety
of
opportunities
available.
Don't
let
your
feelings
about
your
skill
set,
keep
you
from
getting
involved
with
this
community
next,
what
are
the
most
important
areas
that
you
can
help
with?
Like
we
said,
mentoring
really
needs
help
right.
B
B
Help
with
running
the
community
meeting
is
also
something
that
we're
looking
for
right
now,
like
we
said,
we
run
those
meetings,
monthly,
there's
a
little
bit
to
coordinate
there,
because
we
try
to
have
folks
from
various
parts
within
the
kubernetes
community,
not
just
the
Sig
presented
those.
So
we
could
use
some
help
with
that
coordination,
more
immediate
areas,
the
kubernetes
annual
report,
so
the
annual
report
is
really
really
important
to
us
and
it
involves
a
lot
of
coordination
as
well.
B
Like
I
said,
my
number
one
tip
is
to
be
stubborn.
If
you
want
to
be
a
consistent
contributor,
find
a
spot,
docs
or
my
group
contributor
comes
I-
think
our
particularly
good
areas
for
new
folks
and
contributor
comms.
We
do
a
lot
of
stuff,
that's
very
broad,
with
the
project,
so
you
get
more
of
a
sense
for
how
the
project
Works
same
is
often
true
for
docs.
You
get
a
pretty
broad
overview
and
you
can
always
move
from
one
group
to
another,
so
don't
feel
stuck.
A
Addition
I
would
ask
people
to
be
sustainable,
decide
on
a
time
that
you
want
to
commit
to
the
community,
but
don't
think
like
you
would
be
able
to
commit
like
a
lot
of
hours
every
week.
It's
important
to
be
like
regular
across
time
and
not
like
sporadic
that's
really
important
in
the
community.
So
even
if
you
can
give
like
four
hours
or
five
hours
a
week
or
even
a
couple
of
hours
a
week,
that's
very
good,
but
you
should
be
like
consistent
and.
C
Oh
and
time
zones
are
always
an
issue,
so
don't
feel
free,
don't
feel
the
need
to
attend
all
meetings
because
some
might
be
late
for
you.
Some
might
be
really
early
for
you.
That's
why
we
have
the
YouTube
channel.
That's
why
we
have
the
notes.
All
of
that
async
is
more
than
okay.
Async
is
almost
preferred
at
this
point,
so
you
know
totally.
Okay,
no
matter
where
what
time
zone
you're
in.