►
From YouTube: CNCF SIG Contributor Strategy 2020-08-13
Description
CNCF SIG Contributor Strategy 2020-08-13
A
A
C
E
E
G
H
G
C
F
C
C
F
C
F
B
G
C
E
H
F
C
I
H
E
E
E
E
The
that's
kind
of
the
big
next
step,
the
sort
of
smaller
next
step,
is
figuring
out
what
our
sort
of
feedback
loop
is
going
to
be
to
validate
the
badges,
the,
but
I
kind
of
want
to
hold
off
on
that
second
part.
Until
we
determine
what
badges
we're
going
to
be
doing
initially,
because
I
think
I
think
the
what
is
going
to
affect
the
how.
E
E
G
E
E
E
Oh
yeah,
that
is,
that
is
important.
Thank
you
for
remembering
that
yeah
the
so
this
actually
came
out
of
the
election
committee
for
kubernetes,
where
we're
doing
all
of
this
munging
of
voter
lists
and
getting
people's
email
addresses
out
of
get
et,
cetera
and
saying.
This
is
really
stupid.
A
computer
ought
to
be
doing
this.
The
and
the
suggestion
which
don't
remember
george's
suggestion
or
bob
suggestion
was.
You
know
we
should
just
really
get
the
cncf
to
hire
an
intern
to
create
an
online
version
of
sivs.
E
E
H
J
This
tells
you
how
many
people
voted.
Yes,
you
can
say
like,
as
the
votes
come
in,
it
won't
tell
one
won't,
show
you
what's
winning,
but
it'll
it'll
show
you
like
exactly
how
many
of
the
ballots
that
are
out
and
how
many
people
have
voted,
which
is
very,
very
nice,
and
I
did
not
realize
that
I
wanted
that
feature
until
I
did
not
have
it.
E
E
F
A
E
E
H
H
E
H
E
F
E
Know
just
didn't
occur
to
me
as
a
problem,
and
we
have
this
discussion
too,
because
I,
like
I
said,
I'm
doing
this
to
a
postgres
database.
I
can't
figure
out
a
way
to
have
another
member
of
the
election
commission
audit,
what
I'm
doing
to
double
check
it
and
we
couldn't
figure
one
out
and
then,
of
course,
that
paid
dividends.
E
E
F
I
also
wonder
if,
in
your
governance
guidance
that
you
give
to
projects
that
this
is
actually
something
that
they
need
to
watch
out
for
as
they
build
for
these
roles,
because
in
the
beginning
for
us
it
was
even
more
ambiguous
and
like
when
you're,
when
we're
building
for
like
roles
and
different
levels
of
maintainer
or
whatever
it
is
that
you
know
voting
members.
You're
gonna
need
to
do
things
like
collect
their
emails
or
have
voting
mechanisms
in
place
where
you
can
contact
them
and
get
them
and
like
the
ability.
F
So
I
guess
what
I'm
getting
at
is
the
ability
to
contact
these
said
people
in
the
roles
that
you
want
them
in
is
so
difficult,
I
think
in
open
source
in
general,
but
here
it
was
just
so
key
and
apparent
and
josh
as
you're
doing
it
now
you're
like
this
sucks
and
it's
like
yeah.
I
feel
like
it's
just
more
apparent
when
we,
when
we
do
activities
like
this,
that
we
really
don't
have
good
contact
methods
for
folks.
E
Yeah,
well
I
mean
in
the
case
of
kubernetes,
the
reason
why
we
want
to
have
authentication
via
github
is
that,
then
the
contact
method
issue
becomes
kind
of
a
non-issue
right.
Exactly
so,
because
I
mean
our
big
problem,
there
is
we
determine
who
can
vote
by
their
github
handle,
but
then
we
need
to
contact
them
via
email.
E
You
know
a
project
that
was
doing
everything
via
email
like,
for
example.
This
was
never
a
problem
in
postgres,
because
postgres
does
everything
by
email
and
has
a
very
complex
and
self-maintained
custom
email
infrastructure
to
support
this.
That
is
the
problem,
though,
is
that
that
projects
are
inventing
their
original
one-off
tools,
the
anyway
the
that's
here
yeah.
E
I
mean
that
said.
I
still
think
something
open
source
created
by
you
know.
Someone
working
for
the
cncf
would
still
be
a
better
solution,
among
other
things,
opa
vote
costs
per
election
and
per
voter
and
across
all
of
the
cncf
projects.
That
would
add
up
to
a
pretty
substantial
amount
of
money
pretty
quickly.
E
D
D
Of
course,
so
welcome
to
start
working
on
so
you're
welcome
to
put
your
proposal
late
august,
so
post
kubecon
will
launch
another
round
and
that's
it.
So
you
can
even
drive
that
as
kubernetes
project,
because
it's
primarily
for
the
kubernetes
project
needs
and
if
you
want,
you
can
scale
that
later
yeah.
The
estimated
time
for
for
the
intern
to
work
on
on
the
regular
project
is
around
three
months.
D
E
D
E
E
D
D
D
If
you
want
something
more
than
just
a
community
bridge
in
turn,
so
service
desk
ticket
will
be
required,
but
if
you
find
with
just
going
to
come
into
bridgeline,
so
we
have
the
mentoring
repo
under
the
cnc
organization,
where
we
track
all
the
proposals
so
I'll
open,
I'll,
open
the
q3
q4
around
soon
and
you'll
be
able
to
submit
your
formal
couples.
Also,
it's
done.
Similarly
to
that
way
how
people
are
proposing
proposals,
for
example.
So
everything
is
public.
You
you,
you
can
just
propose.
D
D
E
A
F
A
Yeah,
I'm
happy
too
so
the
links
in
the
links
in
the
doc
yeah.
Basically,
I
went
through
and
I
picked
some
measurements
that
so
the
idea
behind
the
stock,
let's
just
start
at
the
beginning,
was
to
get
people
away
from
thinking
that
stars
and
forex
measure
project
health
because
because
they
don't
they're
vanity
popularity,
metrics,
they're,
interesting,
but
not
not
from
a
health
perspective.
A
So
what
I
tried
to
focus
on
were
the
things
that
I
thought
was
the
most
important
with
an
eye
towards
helping
people
understand
why
it
might
be
important
to
measure
for
their
particular
project,
and
then
I
added
a
big
disclaimer
kind
of
towards
towards
the
top
here
to
address
a
lot
of
the
comments
in
the
you
know
throughout
the
doc
about
how
you
know.
They're,
not
one
size
fits
all
they're.
A
So
how
much
people
want
to
talk
about
this,
but
I
would
encourage
you
to
have
a
look
if
you
wanted
to
provide
some
feedback
today.
I
will
probably
try
to
pr
this
tomorrow,
but
it's
basically
broken
down
into
a
bunch
of
types
of
metrics
with
ideas
and
examples
for
how
you
might
want
to
measure
it,
along
with
some
best
practices
at
the
bottom.
F
F
A
G
E
F
And
then
the
meeting
on
tuesday
was
a
small,
a
small
meeting.
Toby
came.
It
was
a
new
contributor
added
a
ton
of
value,
actually
added
some
issues
about
the
idea
of
recognizing
contributors,
so,
for
instance,
how
some
projects
do
contributor
recognition
at
release
like
either
in
the
changelog
or
on
some
kind
of
website,
or
something
along
those
lines,
just
pretty
much
like
guidance
around
how
to
and
ways
best
practices,
ideas
etc
for
recognizing
contributors.
F
So
that's
an
issue
if
anybody
is
interested
in
picking
up
toby's
set
in
github
or
if
you
just
have
something
to
add
as
far
as
stuff
that
you
think
works
or
stuff
that
you've
seen
added
to
that
issue
as
well
container
d,
the
project
came
by.
They
are
looking
for
some
guidance
and
they're
willing
to
schedule
a
dedicated
project
meeting
for
us.
They
would
like
to
talk
about
how
to
set
up
roles,
for
instance,
security,
advisors,
reviewers,
different
types
of
roles
and
they're.
F
F
So
it's
cool,
I
feel,
like
the
outreach
that
we're
doing
is,
is
slowly
but
steady,
working
and
that's
also
just
a
side
note
to
all
y'all
to
to
continue
with
the
outreach
as
well,
but
that
was
pretty
much
it.
We
also
just
did
just
a
general
wow.
We
still
have
a
lot
more
work
to
do
stand
up,
but
that
was
pretty
much.
F
E
H
F
F
H
E
E
H
K
Okay,
I
think
sometimes
it
feels
weird
to
drop
into
someone
else's
meeting
and
not
be
on
the
agenda
and
just
kind
of
like
agenda
bomb
them.
Yeah.
Okay,
we're
gonna
talk
about
my
rando
thing,
so
I
think
sometimes
maybe
if
we
say
like
it's
totally,
okay,
like
we
have
time
carved
out
in
our
agenda,
for
you
to
come
and
talk
about
whatever
that
may
help.
A
A
Is
to
explicitly
call
them
office
hours
because
yeah
it's
it's
hard
when
people
like
you
said
I
always
I
always
feel
sort
of
guilty
like
dropping
in
on
somebody
else's
project
meeting
with
my
own
agenda,
to
ask
a
bunch
of
questions
because
that's
more
appropriate
for
office
hours.
If
we
did
that
like
once
a
month
or
something.
H
And
I
mean
if
we
want
something
of
a
structure
like
office
hours
is
good,
but
also
like
drop
into
like
actually
drop
yourself
onto
the
agenda
right.
So
like
shoot,
a
note
to
the
list
say
like
hey:
is
it
cool
that
we
drop
by
and
foo
date
and
then
put
up
actually
agenda
items
that
you
want
to
discuss
right?
That
way,
there's
some
structure
around
it
before
we
get.
H
F
H
E
I
I
think,
that's
a
thing:
that's
likely
to
be
a
lot
more
successful
like
there
are
the
requests
for
help
that
I've
gotten
I've
generally
gotten,
because
I'm
a
member
of
the
project
ecosystem
already
either
because
of
red
hat
or
because
you
know
it's
in
technology
area,
I'm
involved
in
so
like,
even
if
we're
gonna
do
say
an
official
once
a
month
office
hours.
I
think
we
would
want
to
go
to
ping
people
and
individual
projects
and
and
remind
them
of
it.
K
F
F
So
that's
where
we
are
with
maintainer
circle
right
now.
We
already
have
at
least
three
topics
in
the
queue,
including
inclusive
language,
and
I
know
stephen's
group,
the
working
group
for
naming
and
kubernetes
has
already
kicked
up
so
in
a
couple
of
months.
We'll
actually
have
probably
some
guidance
from
that
group
as
well
for
that
meeting,
and
that's
really
it.
I
have
not
made
any
progress
on
discussion
around
the
online
identity
of
the
thing,
meaning
maintainers.cncf.io
contributors.cncf.io.
F
F
F
Yeah,
that's
right.
I
need
to
follow
service
last
second,
because
I
think
that
would
be.
I
think
that
would
be
a
really
good
goal
for
us
to
have
for
launch
for,
like
a
kubecon
november
would
be
to
launch
like
a
contributors.cncf.io
and
then
have
like
the
project
templates
and
the
maintainer
circle,
and
you
know
a
link
to
the
toc
maintainers
public
thing,
and
you
know
whatever
else:
yadda
yadda.
C
F
Well,
I
did.
That
was
a
example
that,
like
I'm
gonna
like
do
a
doodle
and
like
we're
gonna,
throw
a
doodle
out
and
like
get
people's
preferred
times.
That
was
a
literal
example.
I
it
also
could
be
6
p.m.
Pt
for
dinner
for
pacific
it
could
be
and
then
late
night
meal
for
someone
else
it
could
that
mean
it
could
be
breakfast
in
their
time
zone.
F
B
F
It's
just
going
to
be
another
meeting
if
we
don't
necessarily
have
a
theme
to
it
like
it's
just
going
to
be:
oh,
it's
just
a
bunch
of
cncf
maintainers
getting
together
and
having
another
zoom
meeting.
So
that's
why
I'm
just
like
thinking
from
the
agenda
item.
It
would
be
everybody
everybody
gets
together.
F
F
H
K
I
have
people
excited
to
go
by
the
way
I
was
talking
to
the
home
maintainers
and
was
pumping
it
up
because
they're
having
trouble
promoting
and
finding
more
maintainers
and
contributors
and
people,
and
talking
about
some
of
the
troubles
they've
been
having
with
like
people,
camping
and
being
jerks
in
their
issue,
queue
and
stuff
like
that,
and
I'm
like.
Oh,
this
is
perfect.
Let's
talk
about
the
maintainer
circle,
so
we're
well,
we
have
people
excited
to
start.
That's
all.
I
want.
F
To
say,
I
wanted
to
kick
this
up
like
a
week
ago,
but
everybody
was
like
no
kubecon
and
then
I
was
like.
Oh
my
god.
It's
just
gonna
be
like
the
longest
launch
of
my
life
right
now.
It's
my
six-month
launch
because
we've
already
had
two
cube
cons
and
like
yeah,
I'm
just
ready
to
launch
this
yeah,
I'm
ready
to
go.
K
E
F
E
E
A
F
F
It
would
be
cool
if
we
could
have
more
curated
sessions
on
the
maintainer
track
about
topics
that
maintainers
want
to
hear
like
I've.
I've
been
trying
I've
been
talking
to
the
events
folks
about
this
for
a
couple
of
years
now,
where
it's
like.
Let's
have
a
contributor
summit,
but
the
maintainer
track
so
obviously
still
do
deep,
dives
and
intros,
but
things
like
governance
workshops
and
how
to
recruit
contributors
and
burnout
and
for
everyone
right,
not
just
necessarily
like
the
kubernetes
maintainers
that
we
that
we
service
that
content.
For.
F
C
J
C
C
C
F
F
H
F
F
What
you
mean
by
I
mean
I
literally
would
have
still
stood
up
the
maintainer
circle
next
week.
Literally,
I
asked
about
this
a
couple
weeks
ago.
I
said
hey,
let
me
stand
up
the
maintainer
circle
during
the
week
of
kubecon,
so
that
we
can
ride
kubecon
and
everybody
was
like
no
don't
do,
that.
That
takes
away
from
kubecon.