►
From YouTube: CNCF SIG Contributor Strategy 2020-05-07
Description
CNCF SIG Contributor Strategy 2020-05-07
B
B
B
B
E
B
E
No,
it's
fine!
This
is
just
TL
DR
an
update.
This
is
pretty
much
when
we
give
to
TOC
update
as
well.
We
had
a
TOC
update
on
Tuesday
many
folks
here
that
work
that
are
on
the
line
right
now
we're
there,
but
this
is
just
kind
of
like
what
we
should
be
using
and
folks
asked
us
what
we're
up
to
so.
Obviously
many
of
us
are
in
like
45
other
communities,
so
I'm
gonna
get
into
a
good
habit
of
regularly
at
least
once
a
month.
E
B
F
B
The
okay,
that's
actually
all
for
mailing
list
items
so
very
briefly,
whoops.
That
was
not
what
I
wanted
to
do
very
briefly
for
governance
working
group.
Next
steps
April's
not
on
this
Cole
right
now,
but
we're
gonna
have
our
first
meeting
of
the
governance
working
group
on
Monday
May
11th
in
the
afternoon
Pacific
time,
because
right
now
there
are
only
two
members
of
the
working
group
and
that
works
for
both
of
us
main
thing
is.
B
This
is
going
to
be
to
kind
of
organize
the
working
group
and
also
start
work
on
our
actual
stuff,
which
falls
into
two
main
areas.
One
is
preparing
our
recommendations
on
governance
requirements
to
go
to
the
TOC,
who
have
indicated
that
they
want
to
increase
governance
requirements
at
the
various
graduation
levels,
I
and
as
well.
You
know
outline
all
of
the
things
that
we
need
in
our
guide
for
helping
projects,
develop
governance,
I,
so
there's
an
invitation
to
that
on
the
mailing
list.
E
I
have
a
question,
I
think
and
I
just
put
contributor
growth.
That's
what
that
was
me
typing,
violently:
a
contributor
growth
on
the
agenda
from
the
contributor
growth
working
group.
We're
definitely
going
to
have
some
probably
project.
Remember
that,
like
that's
what
the
section
is
called
in
the
Graduate
project,
probably
gonna
have
some
project
recommendations
that
necessarily
aren't
like
governance
related,
so
I
feel
like
is
that,
okay,
if
we're
just
like
pushing
a
TOC,
multiple
recommendations,
or
should
we
like
package
them
up
into
a
bow
and
send
them
together?
D
B
We
should
maybe,
in
that
case,
bubble
up
the
requirements
through
this
meeting,
so
that,
when
more
than
one
working
group
has
separate
requirements,
recommendations
at
the
same
time,
we
can
send
them
together,
agreed,
okay,
and
particularly
with
contributor
growth
and
governance.
In
particular.
A
lot
of
those
recommendations
are
gonna,
be
directly
related
to
each
other
cool
yeah.
E
B
Yeah
I
mean
one
of
the
things
I
haven't
worked
out
and
that
we'll
be
discussing
on
Monday
and
that
sort
of
thing
is:
how
would
you
this
thing
is
because
you
know
the
TOC
will
have
some
moving
set
of
standards
for
projects
yeah
and
we're
basically
making
change
recommendations
to
those,
but
their
documents
are
also
changing
in
the
process.
Haven't
quite
figured
that
out
yet
the
because,
of
course,
their
stuff
is
going
to
be
in
a
different
repository.
B
E
E
What
we're
trying
to
define
is
a
maintainer
and
again
that's
a
a
wider
net
of
contributor
than
what
the
CN
CF
technically
describes
is
maintainer
and
for
purposes
of
toc
election,
and
we
can
argue
about
that
at
another
time.
Sigh
you
know
side
side
argue,
but
for
the
purpose
of
this
casting
a
wire
net
for
people
who
make
like
official
reviews
and
who
are
building
that
trust
within
their
projects
and
really
talking
about
project,
structure
and
organization,
and
things
like
that,
so
that's
it.
B
E
And
that's
on
and
I've
got
that
only
agenda.
That's
honestly,
I
feel
like
I
I.
We
us
should
be
like
have
some
kind
of
nice.
Even
that
gets
sent
to
all
the
project.
Maintainer
xand
introduced,
says:
hey,
look
at
this
we're
planning
this
thing,
I
included
the
link
in
the
in
the
agenda
to
the
hack
MD
as
well.
I!
Think
I
did
it's
just
and
it's
just
a
skeleton
of
what
I'm
thinking
about.
So
it's
just
less
coming
out
of
the
gate.
E
Saying
hey
we're
doing
this
thing,
we'd
love
to
have
you
also
adding
in
like
a
survey
and
a
focus
group
option
which
I
started
a
github
issue
about
as
well?
So
we
can
really
start
to
get
some
information
back
from
other
projects
as
to
like
even
what's
working
for
them,
because
we
want
to
collect
that
information
too.
E
B
E
E
B
E
B
E
D
A
G
B
C
Come
we're
saying,
come
well.
We'd
have
to
do
one
of
two
things
like
change.
The
calendar
invites
right
to
say
there
should
be
like
two
separate
ones
where
one
is
the
planning
meeting
when
it's
like
the
sake
planning
meeting
that
you're
welcome
to
come
to
you,
but
the
the
the
second
one
for
the
month,
which
is
the
third
or
the
fourth
Thursday,
is
the
AMA
maintainer
Circle
shindig.
E
G
C
B
F
B
It's
true
VM
well
in
the
first
half
hour
of
the
meeting,
yeah
would
have
to
get
all
of
our
stuff
done,
the
which
also
brings
up
something
for
maintainer
participation
that
we
can
start
out
this
way,
but
eventually
you're
going
to
need
to
move
that
around
the
clock,
because
for
maintainer
x',
who
are
in
China
or
Finland
that
11:00
a.m.
Pacific
is
a
very
bad
time.
I.
B
B
G
E
H
H
B
E
What
are
things
that
you
want
to
know
from
some
of
these
other
projects?
And
again
it
doesn't
necessarily
mean
bad
things.
That
can
mean
good
things,
so
you
can
like
compile
best
practices
or
whatever,
but
this
is
also
especially
relevant
for
contributor
growth
and
maintainer
circle,
and
things
like
that
so
trying
to
keep
the
survey
as
light
as
possible,
so
think
of
like
some
umbrella
questions
that
would
benefit
you,
I
already
put
like
some
general
on
there
so
again,
I'm
trying
to
keep
this
as
light
as
possible,
also
build
some
trust.
B
Which
means
that
maybe
we
should
just
ask
questions
about
where
the
documentation
is
just
have
questions
where
people
can
put
links
via
what
I
really
love
about
the
whole
RTFM
thing
is
that
I
will
tell
you
80%
of
the
projects
where
a
maintainer
has
told
the
RTFM.
The
manual
did
not
in
fact
exist.
Oh.
E
H
B
Yeah
I
guess
after
I
have
to
do
some
hard
thinking
about
how
we
make
questions
that
are
general
enough,
that
all
projects
could
potentially
answer
them,
but
still
get
useful
information
out
of
it's
a
little
bit
challenging
because
projects
can
have
some
pretty
you
know.
Some
of
them
are
gonna,
have
documentation
for
governance,
and
some
will
not.
You
know
I.
B
E
B
E
G
G
B
E
Right
wait
for
the
governance
meeting
then
before
shipping
any
kind
of
email,
but
I
would
like
to
for
as
far
as
like,
where
we
are
I
mean
we
should
definitely
at
least
give
a
weeks
notice
to
invite
them
to
the
next
meeting
so
I'm
thinking.
We
should
definitely
try
to
mail
something
off
by
mid
next
week.
B
B
B
C
H
C
A
C
C
B
H
B
G
C
A
B
They
there
aren't
oh
at
least
the
last
time
I
touched
CN
CF
SurveyMonkey,
which
was
about
three
actually
longer
than
that.
Like
November,
there
were
not
teams
and
that
sort
of
thing
survey
monkeys
for
their
paid
accounts.
They
have
a
pretty
steep
tier
structure
and
and
CN
CF
is
not
at
the
upper
tiers.
Okay,.
H
C
B
B
E
Look
at
projects
when
they
come
in
and
things
like
that
and
I.
That's
why
I
was
pinging
Jared
offline,
because
I
know
box
projects
and
stuff
like
that
and
I
was
like
I
wonder
if,
like
every
meeting
here,
we
should
talk
about
some
of
the
specific
projects
that
are
coming
in
and
see
like
kind
of
a
consultative
approach
that
we
can
give
to
them
sort
of
like
what
the
other
things
are
doing
at
the
TOC
level.
B
B
The
I
mean
so
far,
I've
kept
all
of
our
language
in
terms
of
recommendations
and
stuff.
In
that
we
are
actually
providing
recommendations
to
the
COC.
The
TOC,
like
what
we
have
in
our
initial
read
means
that
were
providing
recommendations
to
the
other
SIG's
in
the
TOC
and
only
directly
getting
involved
in
reviewing
stuff
on
request.
C
So
I
would
I
would
say
the
reverse
I
guess.
Oh
no,
sorry,
now
I've
exactly
what
Josh
said.
I
I
would
be
reluctant
to
open
up
that
possibility.
I
think
that's
yeah,
exactly
what
she
said.
People
are
gonna,
be
willing
to
offload
that
work.
I
think
what
we
should
do
is.
Maybe
you
read
out
of
what
has
been
like
what's
new
with
the
TOC
kind
of
situation,
right
where
we
understand,
what's
been
floating
around
the
mailing
list
and
provide
recommendations
based
on
that
stuff?
Okay,
that's
feasible,
yeah
yeah,.
E
We
just
need
I,
feel
I
need
a
TOC
like
connection
now
because
now
we're
past.
It's
like
meta
sage,
so,
like
the
last
update
I
gave
this
week
and
TSA
was
like
all
right,
we're
off
and
so
now
I'm
just
like
all
right
now,
we
need
to
I
guess,
make
those
connections
with
TOC
in
some
way.
So
I
guess
we'll
also
have
the
governance
requirements
and
things
like
that.
So
all
right.
B
E
E
That's
right
and
that's
right,
that's
where
I
was
going
with
when
I
asked
earlier
about
the
like.
Should
we
all
you
know
package
this
up
as
our
like
our
one
shot
of
you
know,
recommendations
or
are
we
or
we're
just
gonna
constantly
iterate
we're
just
constantly
pushing
recommendations
to
that
kind
of
thing,
I.
B
Projects
will
get
reviewed
that
sort
of
thing
either
there
will
be.
You
know
an
open
question
for
a
whim
for
about
a
project
where
it's
really
not
clear
or,
alternatively,
the
you
know,
CN
CF
and
TOC
will
decide
that
they
want
to
change
things
right.
Like
maybe
they'll
decide,
hey,
sandbox,
incubating
and
graduated
isn't
enough.
We
want
to
have
another
tier,
at
which
point
we
need
to
prepare
a
whole
nother
set
of
recommendations.
H
B
B
D
B
H
Didn't
know
it
we
should
we
need
to
say
fashion
for
ya,
PR
piece
for
gr
pc.
We
briefly
had
like
a
working
group
for
nail
polish
colors
cuz.
We
were
looking
for
like
the
perfect
gr,
PC
teal
shade
so
yeah.
These
are
important
things
that
go
on.
Yes,
we
should.
We
should
list
this
under
swag
best
practices,
not
that
we'll
ever
be
in
a
place
to
give
anyone
swag
ever
again,
but
yeah.