►
Description
CNCF SIG Contributor Strategy Contributor Growth WG 2020-10-13
B
B
A
A
C
B
C
C
So
one
you
guys
just
walk
through
the
you.
Don't
have
rights
to
this
pr,
I'm
sorry,
it
says
repo
paris
doesn't
a
whole
bunch
of
people.
Don't
so
I
submitted
a
pr
to
basically
give
this
repo
the
same
permissions
as
the
other
revo
that
we
have,
and
so
this
will
add
you
and
paris
and
dawn
and
jennifer
and
josh
and
stuff
and
everybody
else
so
that
we
can
get
people
to
approve
these
pr's
that
are
submitted,
so
that
should
get
looked
at
pretty
soon
cool.
C
Okay
and
what's
kind
of
cool
about
that
is
now
when
someone
looks
to
read
me,
it'll
look
like
yeah
I'll
show
you
I'll
show
you
another
one
I'll
show
you
skeletor
it'll,
look
like
this
use.
This
template,
oh
cool,
yeah,
they'll,
be
able
to
like
clone
the
whole
thing,
really
nice
and
easy,
and
it
won't
quite
be
a
fork.
Then
it'll
be
like
their
own
standalone,
repo
forward,
which
is
nice.
I
added
a
code
of
conduct.
C
C
C
C
C
B
B
B
Yeah,
so
it
sounds
like
there's
a
few
like,
I
guess,
there's
like
a
few
different
sides
to
this
right,
because
there's
like
the
side
of
it,
where
it's
like
the
documentation,
which
is
what
you're
trying
to
provide
right
like
a
template
and
then
there's
like
the,
I
guess:
governance
side
of
code,
of
conduct,
things
and
okay
yeah.
I
was
just
wondering,
like
kind
of
where
those
talks
would
happen
if
it
would
be
within
the
state
or
not.
C
C
But
we
also
I
want
to
recommend
that
they
have
at
least
two
people
in
the
template.
I
don't
go
into
great
detail
into
why,
but
if
we
had
like
companion
advisory
guides,
you
know
the
reasons
are.
If
you
only
have
one
person,
how
do
you
report
that
one
person
yeah
recurs
yourself,
yeah
yeah,
you
can't
recuse
yourself
exactly.
You
can't
go
on
vacation.
C
What,
if
you're,
you
know,
there's
all
sorts
of
situations
where
you
need
more
than
one
person
to
be
able
to
handle
reports
yeah-
and
you
know
like
from
being
on
the
committee,
there's
a
lot
of
different
things
involved
with
it
beyond
just
having
this
document
right,
there's
no
training
at
all.
We
insist
as
part
of
the
scenes.
If
you
have
a
code
of
conduct,
we
don't
insist
that
you
are
equipped
at
all
to
know
what
to
do.
If
someone
emails,
you.
B
C
B
C
B
C
B
C
Who
is
responsible
for
the
repo
so
yeah
I
mentioned
it's
part
of
you
know
our
group,
you
know
how
to
click
on
the
button
and
use
it
and
then
what's
required.
Oh,
you
know
over
time
as
we
build
up
this
repository,
not
everything
we
put
in
here.
You
have
to
do
right,
some
things
may
be
for
incubating
or
graduated
or
just
a
nice
to
have.
B
C
Yeah
so
I
tried
to
add
things
and
just
be
like
this
is
what
you
have
to
do,
and
maybe
there's
some
advice
in
particular
to
a
template
that
we
could.
You
know,
give
people
further
information
on
and
then
I
thought
at
the
bottom.
We
could
there's
a
comment
here.
You
can't
quite
see
it.
Okay,
once
you're
done
reading
through
and
following
everything
we
kind
of
tell
you
to
rip
everything
out
at
the
top,
and
then
you
know
the
rest
of
the
read
me
is
yours.
C
B
B
C
Right
and
then
our
advice
like
the
documentation,
whatever
outside
of
the
template,
we
can
mention
that
and
say
like
hey.
If
you
really
need
something
different,
you
can
do
something
else,
and
some
of
that
falls
into
governance.
I
think
not
contributor
growth
yeah
or
for
like
the
contributing
document.
If
we
take
a
look
at
it,
they
don't
have
to
have
all
of
these
things
in
here.
You
must
have
a
contributing
guide
and
it
must
hit
on
certain
topics
right,
but,
for
example,
does
it
need
to
say
how
to
sign
your
commits?
C
C
C
C
B
C
B
C
C
C
But
we're
getting
we're
getting
there
the
contribution
ladder
and-
and
some
of
these
other
things
are
like
really
nice
things
to
have,
but
none
of
them
are
required
by
the
yeah
dncf.
Let
me
move
up
owner's
file
actually,
because
owners
is
in
governance,
owners
is
required
for
sandbox,
okay
and
governance
is
required
for
incubating
and
contribution
ladder
is
required.
Later
too
that's
for
incubating
as
well.
C
B
C
So
a
template
is
just
strictly.
This
is
the
output
file
that
that
you'll
need
in
your
repository
so,
for
example,
the
contributing
guide
or
the
contribution
ladder
right,
but
there
may
be
something
equivalent
to
just
the
web
page
that
we
may
have
or
or
markdown
file,
on
a
repo
that
that
just
has
guidance
that
we
talk
about
how
you
would
go
about.
C
Not
just
like
creating
the
content
in
that
file,
but
the.
Why
is
here
like
the
whys
and
then
the
how
of
implementing
some
of
this
stuff,
and
so,
if
we're
talking
about
the
contribution
ladder,
for
example,
we
may
talk
about
how
do
you
identify
people
who
look
to
be
ready
to
be
kind
of
encouraged
to
move
up
the
ladder
and,
and
what
do
you
do,
how
do
you?
C
C
C
B
C
B
B
B
C
B
C
B
C
B
B
C
Oh
yeah
look
at
it
in
raw
form,
otherwise
you
don't
see
you
see
the
word
to
do
and
you're
like
what
happened.
I
wrote
a
bunch
of
sex
so
like
there
there
is
bulleted,
but
we
still
have
more
than
just
a
line
of
attacks
like.
I
think
we
have
enough
outline
that
you
and
I
understand
it
but
they're,
just
like
requirements
right
or
like
follow
reviewing
guide
like
this,
isn't
enough
for
someone
other
than
you
and
I
to
read.