►
From YouTube: CNCF Project Paperwork Working Session - Josh Berkus, Red Hat, Carolyn Van Slyck & Dawn Foster
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. 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.
CNCF Project Paperwork Working Session - Josh Berkus, Red Hat, Carolyn Van Slyck, Microsoft & Dawn Foster, VMware
At each stage from Sandbox to Graduated, you’ll need to add community and process documentation – and there’s even more that’s good to have even if it’s not required. Let us help you create this “project paperwork” now instead of waiting for a deadline. With just a little planning, it doesn’t need to overwhelm you. SIG Contributor Strategy will walk you through required and desired community docs, how to use the new template repo, and which docs you need at which level. We’ll also be on hand to answer your questions and provide 1-on-1 help and editorial support. You can get your project ready, and we’ll show you how.
https://sched.co/ekG0
A
A
Now
the
format
of
the
session
is
going
to
be
a
little
bit
different
from
other
sessions.
You
might
have
seen
today
we're
going
to
spend
five-ish
minutes
talking
about
the
requirements.
Five
inch
minutes,
showing
you
some
examples
and
then
20
plus
minutes
on
q,
a
and
helping
you
with
your
particular
project
and
paperwork
questions
in
blockers.
C
The
cncf
contributor
strategy
sig
provides
a
place
for
us
to
collaborate
on
strategies
related
to
building
scaling
and
retaining
contributor
communities.
Our
goal
is
really
to
provide
resources
for
you
that
help
our
cncf
projects
grow
flourishing,
sustainable
communities
to
help
them
on
their
journey
throughout
the
cncf
project,
life
cycle.
B
So
for
the
contributor
growth
working
group,
our
main
focus
is
on
making
sure
that
we
have
a
steady,
sustainable
pipeline
of
contributors
coming
into
your
project
and
ensuring
that
there's
always
people
helping
to
work
on
things.
So
you
have
new
contributors
coming
in.
We
want
to
make
sure
they
feel
welcome
and
we
provide
templates
and
advice
for
how
to
make
sure
that
you
have
all
sorts
of
documents
that
you
need
related
to
that
provided
for
you.
Then
we
also
focus
on
contribution
ladder
activities.
B
A
Now,
when
you
look
at
the
requirements
for
the
cncf
you'll
notice
that
there's
three
maturity
levels,
starting
with
sandbox,
then
moving
through
incubating
and
moving
through
graduated-
and
this
is
the
common
path
for
most
projects
and
you'll
notice
that
the
number
of
requirements
goes
up
with
each
level
with
sandbox.
It's
like
five
requirements
with
incubating
it's
eight
we've
graduated
it's
13
or
59.
A
If
you
look
at
all
of
the
sub
requirements,
not
only
does
the
number
of
requirements
go
up
in
every
level,
but
the
sort
of
depth
of
each
requirement
goes
up
on
the
different
levels
like,
for
example,
at
the
sandbox
level.
You're
not
expected
to
have
any
referenceable
end
users,
because
you're
an
experiment
at
that
point.
B
The
toc
will
review
the
submissions
in
a
closed
meeting
every
couple
months,
maybe
two
to
three
months
and
then,
if
you're
accepted
you
get
to
start
the
onboarding
process,
which
is
great
you're
in
this
sandbox,
otherwise
you'll
be
able
to
watch
that
meeting
the
recording
of
the
meeting
review
any
written,
toc
feedback
and
then
resubmit
later
now,
once
you're
in
sandbox,
though
you're
immediately
going
to
be
asked
to
provide
a
whole
bunch
of
documentation
and
paperwork.
Essentially,
so
we
have
a
templates
project.
B
A
project
in
github
that
can
you
can
help
you
get
started
you
just
clone
it,
and
you'll
be
able
to
have
basically
an
entire
repo
with
all
the
various
pieces
of
paperwork
that
you
need
for
sandbox
ready
to
go
at
a
high
level,
though
you
need
a
license
and
it's
going
to
be.
Apache
2,
that's
required
by
the
cncf
you'll
need
a
code
of
conduct,
even
if
you
had
an
existing
one
you're
going
to
have
to
switch
to
the
cncf's
code
of
conduct
you're
going
to
on
your
readme
or
your
website.
B
C
And
then
the
next
step
in
the
process
is
the
incubating
stage.
So
at
this
point
your
project
will
need
to
have
at
least
three
independent
end
users,
which
shows
that
there
are
people
interested
in
using
your
project.
And
while
it's
good
to
have
a
governance
file
in
sandbox,
it
is
actually
required
in
the
incubating
stage.
A
So,
having
talked
about
a
lot
of
that,
let's
show
you
a
few
examples
to
help
you
meet
all
of
these
requirements
and
to
find
all
of
the
various
things
that
you
need
to
do
with
examples
of
how
other
projects
have
documented
them.
We've
assembled
a
checklist
for
project
paperwork
that
is
available
on
the
sig
contributor
strategy,
repository
it's
more
extensive
than
going
to
go
over
here,
but
we
thought
that
we
would
give
you
a
few
examples
of
the
things
that
you
need
at
different
levels
in
this.
B
Video
you
enter
sandbox
one
of
the
first
documents
that
you're
going
to
need
to
edit,
even
if
you
had
it
before
was
the
code
of
conduct,
and
this
is
what
your
new
code
of
conduct
should
look
like,
you're,
going
to
link
out
to
the
cncf's
official
code
of
conduct
and
then
you're
going
to
decide
who,
in
your
project,
is
going
to
handle
reports
about
your
code
of
conduct.
Ideally
that's
more
than
one
person.
If
you
don't
have
anyone,
though,
who
feels
ready
to
handle
something
like
this,
you
can
have
the
linux
foundation.
B
The
next
document
that
I
think
you're
going
to
spend
quite
a
bit
of
time
on
tweaking
and
updating
while
you're
in
sandbox,
is
your
contributing
guide.
Now,
there's
a
couple
different
things
that
you
may
already
have
in
here
or
you
may
not,
but
like
these
are
good
things
to
look
for
maybe
fill
in
the
blanks.
One
is
call
how
else
you
can
contribute
to
the
project.
B
Besides,
pull
requests,
usually
the
things
that
people
do,
that
aren't
code
is
some
of
the
most
time
consuming
things
for
maintainer
and
if
other
people
can
help
with
that,
that
would
be
great.
Let
people
know
how
you
can
find
issues.
How
do
you
label
your
issues?
Do
you
use
good
force
pr
and
things
like
that?
B
How
do
you
ask
for
help?
Do
you
want
people
to
hit
you
up
on
slack?
Do
you
want
them
to
use
the
mailing
list,
make
it
explicit?
Let
them
know
one
item
that
most
people
don't
have,
but
would
be
really
useful
and
we're
trying
to
encourage
is
saying
what
is
going
to
happen
when
you
submit
a
pull
request.
What
to
expect?
B
B
Make
it
a
little
easier
for
them
now?
Harper
has
a
great
example
of
how
to
ask
for
help
in
their
contributing
guide
where
they
call
out
how
you
can
join
meetings.
How
can
you
get
involved
with
community
and
then
directing
people
appropriately
to
the
dev
mailing
list,
so
they're
not
asking
for
help
on
the
general
end
user
mailing
list.
C
And
then
at
incubation,
as
I
mentioned
earlier,
the
governance
md
file
you
need
to
have
that,
and
one
of
the
things
it
needs
to
include
is
how
leaders
are
selected.
So
we've
written
a
handy
guide
for
you,
which
is
in
the
governance
working
group,
documentation
section,
and
it
has
a
bunch
of
different
ways
that
leaders
can
possibly
be
selected.
So
you
can
have
a
look
at
these
see,
what's
appropriate
for
your
project
and
use
one
of
them
if
it
makes
sense.
C
A
Now,
one
of
the
other
things
that
you
then
need
to
add,
if
you
are
applying
for
the
graduated
level,
is
this
adopters.md
file,
which
is
going
to
be
a
list
of
publicly
referenceable
users
who
have
adopted
your
technology.
This
is
to
demonstrate
that
your
technology
is
useful
and
is
broadly
interesting
to
a
large
group
of
people.
A
If
you
can
get
access
to
case
studies
or
articles
about
some
of
these
companies,
then
that
is
also
great,
but
really
it
just
needs
to
be
this
list
of
users
and
they
need
to
be
willing
to
be
referenced
and
to
say
that
they
use
your
project
if
they're
willing
to
join
the
cncf
end
user
council
as
well.
That
is
also
great.
The
much
bigger
requirement,
though,
is
the
cnc.
The
cii
best
practices
badge
now.