►
From YouTube: Keynote: Sustaining a Contributor Community’s Next Generation - Christoph Blecker, & Paris Pittman
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. 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.
Keynote: Sustaining a Contributor Community’s Next Generation - Christoph Blecker, Principal Site Reliability Engineer, Red Hat & Paris Pittman, Program Manager, Apple
A
Hello,
everyone,
sorry,
I'm
dancing,
I'm
paris.
A
We're
so
excited
to
be
here
closing
out
the
week
with
you
we're
going
to
be
talking
about
kubernetes
sustainability
through
our
lens.
It's
been
a
long
fun
intense
week
already
insert
your
adjective
here,
but
we've
made
it
through
together,
there's
still
more
to
do
and
everybody's
been
super
kind
in
the
process.
A
A
B
B
I
found
myself
not
only
fixing
issues
with
the
kubernetes
code
itself,
but
also
the
process
of
contributing
that's
how
I
got
involved
in
the
contributor
experience
sig
and
met
folks
like
paris
as
I
continued
to
work
in
the
community.
I
too
started
being
recognized
for
my
efforts,
paris
and
the
other
sig
leaders
at
the
time,
sponsored
me
to
become
a
tech
lead
years
later.
Both
of
us
grew
within
the
project
and
were
elected
to
the
kubernetes
steering
committee.
B
We
as
a
project,
had
to
make
significant
intentional
investment
in
our
automation,
testing
and
tooling.
In
order
to
scale
we
needed
to
be
able
to
delegate
abilities
like
running
tests,
merging
code
and
even
adding
folks
to
our
github
work
prow.
Our
ci
cicd
system
has
been
so
instrumental
to
the
success
of
kubernetes
that
many
other
organizations
and
projects
in
the
cloud
native
space
have
adopted
it.
B
B
B
If
I
didn't
diligently
decode
the
change
log
and
update
my
application
accordingly,
it
was
extremely
easy
to
suffer
an
outage
as
a
consequence,
production
readiness
reviews,
along
with
other
things,
we've
done
like
a
clear
api
deprecation
policy
to
stop
things
from
sitting
in
that
perma-beta
state
have
truly
made
kubernetes
a
better,
more
stable
piece
of
software.
A
Roles
like
this,
our
core
roles
like
reviewer
and
approver.
You
know
the
people
reviewing
40
000
pull
requests
a
year
are
also
scoped
and
documented.
This
is
required
for
contributor
communities
of
our
size.
According
to
nadia
ekbal,
an
open
source
researcher
we're
rare.
Only
three
percent
of
open
source
communities
are
like
this.
A
A
A
A
A
A
B
B
B
A
Digging
in
and
helping
with
help
wanted
issues
is
still
a
very
important
piece
to
contributing
here
and
building
trust.
We
need
deeper
than
that.
At
this
stage,
all
we
need
companies
to
collaborate
with
us
to
incentivize
and
support
reviewers,
approvers
plus
chopwood
carry
water
rolls
find
the
balance
between
your
new
enhancement
with
the
work
that
needs
to
be
done
to
increase
our
sustainability
as
both
a
technology
and
the
community.
A
Misaligned
incentives
is
how
we
get
to
burnout
contributors,
leaving
the
project
employee
turnover
in
order
to
get
more
support,
promoted
paid.
Whatever
many
of
you
justify
your
coupon
expenses
for
recruiting
talent,
if
you
want
to
be
competitive
start
with
upstream
support
and
incentives,
remember
the
belonging
is
high.
In
this
group.
A
A
A
How
do
we
pass
down
this
knowledge
in
a
world
full
of
casual
contributors
and
misaligned
incentives?
We've
heard
and
implemented
thousands
of
your
unique
use
cases
and
built
this
community
on
radical
collaboration
that
leads
by
our
values.