►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20201218
Description
[SIG ContribEx] Weekly Marketing Meeting for 20201218
A
Hey
y'all
welcome
to
the
upstream
marketing
team
meeting
for
kubernetes
we're
in
the
sig
contributor
experience
as
a
subgroup.
Welcome
welcome,
happy
mid-december
for
many
of
us
going
to
be
celebrating,
or
at
least
taking
some
time
off
next
week.
So
that
is
a
great
way
to
start
this
meeting
so
remember
that
and
I'm
matt,
I'm
the
editor
for
this
group
and
the
lead
got
a
bunch
of
other
people
on
who
are
pretty
regular.
Anyone
else
want
to
introduce
themselves
if
they're,
new
or
just
say
hi.
B
A
Yeah
great
and
cut
the
knsc
you're
out
there
with
the
a
new
logo.
That's
pretty
awesome.
A
A
Cool
I'll
take
that
that
is
a
big
win.
Speaking
of
wins,
we
always
start
this
meeting,
so
you
know
I'm
gonna
start
doing
this
pretty
regularly,
just
as
a
reminder
to
get
it
get
the
cadence
out
there
that
our
goal
in
the
upstream
marketing
team
we
also
go
by
contributor
comms,
is
to
help
people
contribute
to
kubernetes
in
ways
that
are
non-code
contribution
and
to
spread
the
stories
of
people
contributing
in
all
ways
across
all
channels.
Gonna
be
that
glue
between
the
different
teams
be
helpful.
A
Where
we
can,
and
with
that
in
mind,
you
know
we're
rolling
into
the
end
of
the
year,
wanted
to
kind
of
reflect
a
little
on
what
we've
done
so
far
and
see
what
status
we're
at
on
a
couple
of
things
in
progress
and
yeah.
Just
get
get
ideas
like
how
how
we're
going
to
continue
with
that
mission
in
2021,
without
being
too
too
idealistic
about
how
the
year
will
go
like
what
are
some
little
steps
we
can
take
to
get
there,
but
we
always
start
with
kind
of
updates
or
big
wins.
A
I'm
not
sure
if
everyone
was
able
to
make
it,
but
the
the
kubernetes
celebration
last
week
was
really
pretty
awesome.
It
seemed
like
it
got
a
lot
of
a
lot
of
people
engaged
with
each
other
using
discord
and
talking.
Anyone
else
have
a
chance
to
participate,
play
some
games
or
hang
out.
A
That's
cool
for,
for
those
that
didn't
know
about
it.
Yeah
there
is
a
we
kept
changing
the
name,
not
the
best
for
marketing,
but
it
was
some
sort
of
cncf
bake
off,
hosted
by
paul
zurkowski,
and
I
was
one
of
the
hosts
with
a
couple
other
great
people
in
our
community,
and
there
are
eight
bakers,
including
paris,
who
was
amazing
and
so
fun
to
watch
like
bake
a
cake
yeah.
It
was.
It
was
a
lot
of
fun.
It
was
pretty.
C
And
yeah
sorry,
I
dare
attend,
but
I
guess
one
of
the
thing
that
I
felt
didn't
work
out
was:
we
didn't
have
anything
in
the
apac
time
zone
or
maybe
a
time
zones
for
that
matter.
C
E
For
her
as
well,
this
is
a
perpetual
problem
with
doing
anything
live
right.
Like
yeah,
I
have
the
same
problem
running
openshift
tv
right
like
it's.
It's
you
can't
hit
every
time
zone
with
one
live
thing,
it's
just
impossible
right,
yeah
I
mean,
and
I
feel
like
you
know,
if
we
had
like
a
breakout
team
to
handle
apac
and
like
a
few
of
us
to
kind.
E
Now
I
was
asked
earlier
this
month
find
a
time
that
works
for
central
time
in
japan
and
I'm
like
that
doesn't
exist.
E
A
E
C
A
A
Yeah
yeah
our
jokes
aside,
like
one
I'm
completely
in
agreement
that
yeah
we,
I
would
just
say
like
yeah,
we
dropped
the
ball
on
making
it
an
international
affair.
Right
like
we,
it
was.
B
A
Kubecon
n
a-
and
I
think
it
just
kind
of
defaulted
to-
let's
just
focus
on
kubecon
n,
a
like
north
america.
But
you
know
that's
not
that's,
not
our.
It's
not
a
terribly
representative
of
our
community,
so
something
to
keep
in
mind.
But
I
don't
want
to
just
keep
it
in
mind.
I
want
if
you,
if
you
have
ideas
on
yeah.
B
D
D
Yeah,
I
I
guess
that's.
I
wouldn't
call
this
as
a
mistake
or
like
didn't
work
out
thing
sure
this
is
probably
a
legend
learn.
Probably
I
mean
the
best
way
the
lesson
learned,
because
we
always
focused
on
the
contributor
meetings
and
contributor
stuffs
contributor
workshops
on
related
to
the
cube
con
and
the
place
where
it
is
happening
like
kubecon,
cubecon,
sorry,
cubecon,
eu
cubecon
na
I
like
that.
D
So
I
guess
that
was
that's
how
this
got
started
and
since
it
was
virtual,
like
we
thought
of
like
doing
it
looking
okay,
this
is
virtual.
So
let's
just
send
another
invite
to
the
k
community,
like
kk,
everyone
in
the
k,
dev
yeah.
Probably
if
I
may
add
something
suggestions,
sort
of
thing
like
we
have
the
contributor
sorry
kubernetes
days
in
india,
maybe
we
can
add
a
light
version
of
the
like
contributor
celebration
to
come.
Contribute
today,
like
community
sorry
kubernetes
days
in
india.
D
I
think
from
the
kubernetes
days
in
india
right
because
we
don't
have
a
kubecon
in
india
or
stuff
like
that,
so
our
cloud-native
conference,
I
mean
one
of
the
same.
So
we
have,
but
we
have
kubernetes
days
in
india
and
there
are
places
where
we
have
kubernetes
days
where
we
don't
and
we
cannot
really
put
a
full-fledged
conference
like
the
kubecon.
So
we
could
put
a
light
version
of
contributor
celebration
even
alongside
or
after
kubernetes
days,.
C
No,
it's
a
cncf
event
yeah.
So
it's
been
happening
for
past
two
years.
I'm
not
sure,
what's
gonna
happen
in
2021,
but
when
is
it
usually
I
forgot.
Oh,
it
usually
happens.
Beginning
of
the
year,
probably
february
march,.
E
A
A
A
Enjoy
it,
but
it
was,
it
was
quite
fun
and
it's.
The
coordination
is
not
too
bad.
It's
like
a
combo
of
obs
and
and
zoom
and
kind
of
invent
streaming
it,
but
anyway
we're
we're
jumping
ahead,
but
that
is
something
maybe
we
can
continue
to
build
like
a
little
bit
of
a
run
book
of
like
these
break
off
events
that
were
successful
and
really
fun
like
document
why
it
was
fun
how
it
worked,
what
we
did
to
support
it.
A
That's
I
I
think
I'm
getting
paul
to
write
up
what
he
did
to
manage
it
so
that
we
can,
maybe
you
know,
use
it
as
maybe
not
exactly
a
template,
but
just
an
example,
and
then
we
can
iterate
for
different
regions,
different
goals.
A
Yeah,
like
I
wouldn't
know
to
like
the
way
he
set
up
the
video
feeds
and
like
the
the
tools
that
are
used
to
get
it
together
and
like
the
way
he
had
us
all
use
green
screen
so
that
he
could
filter
behind
us
and,
like
there's
just
a
lot
of
little
touches
that
were
nice
great
and
they
might
not
work
elsewhere.
If,
like
with
bandwidth
restrictions
or
concerns.
B
A
You
know
you
can
make
other
things
work
great
well,
this
is
not
your
normal
meeting.
We
would
normally
go
through
and
go
through
like
are
there
articles
in
in
progress?
Are
there
pr's
that
we
need
to
talk
through,
but
I
did
want
to
like
kind
of
bring
us
up
into
the
kind
of
a
little
bit
of
an
end-of-year
conversation
of
how
do
we
keep
making
this
the
making
the
path
of
contribution
more
straightforward
for
people
in
the
new
year?
What
kind
of
what
are
you
all
thinking
about
things
that
we
need
to
do
progress?
A
We
need
to
make
on
different
parts?
I'm
thinking
specifically
on
like
how
we
can
lighten
the
the
barrier
of
entry
to
writing
a
blog
post
without
needing
to
code
as
much
and
writing
a
tweet
without
needing
to
code
or
other.
D
Right,
I'm
I'm
going
to
start
with
something
that
happened
like
a
couple
of
days
back,
so
I
had
a
meetup
event.
I
I
was
presenting
about
something
on
kubernetes
bangalore,
which
is
virtual
again,
so
there
were
a
couple
of
questions
popped
up
and
they
were
asking
like.
I
don't
know
anything
about
golang,
but
I
do
want
to
contribute
to
kubernetes.
How
am
I
going
to
do
that,
and
actually
I
spent
like
almost
five
to
ten
minutes
on
explaining.
D
You
must
not
need
to
know
golang
to
contribute
to
a
community
like
kubernetes,
and
I
was
explaining
all
the
kubernetes
repositories.
So
the
one
thing
I
understand-
or
I
learned
from
that
question
is
like
there
is-
there-
is
a
there-
is
a
good
amount
of
good
population
out
in
the
outside
world
in
the
market.
D
Like
they
don't
know,
these
are
the
repositories
that
they
can
contribute,
even
though,
if
they
don't
want
to
code,
there
was
also
a
question
like
what
is
a
release
shadow
thing
like
how
would
I
do
on
that
so
and
I
actually
forgot
to
talk
about
the
article
stuff,
but
I
did
talk
about
k,
community
marketing,
slack
infra.
All
the
all
the
non-coding
stuffs
that
we
have,
I
was
actually
explaining
them.
D
So
that's
one
thing
I
would
say
like
we
probably
need
to
have
a
more,
I
wouldn't
say,
like
an
aggressive
injection
of
the
information
into
the
population,
but
somewhere
like
a
welcoming
way
in
a
welcoming
way.
We
need
to
inject
all
these
informations
into
the
community
like
they
don't
need
to
know
golan.
If
they
know
java,
they
can
still
contribute
to
kevin
ada's
by
java
client.
If
they,
if
they
know
python
very
well,
they
can
contribute
to
python
client
if
they,
if
they're
good
at
testing,
they
can
contribute
to
pro.
D
So
something
like
that.
So
there's
if
they're.
D
D
Even
though,
like
okay,
I
I
don't
want
to
do
anything
on
the
contribution
side,
but
I'm
using
kubernetes
too
much.
I
just
want
to
tell
that
how
amazing
it
is
so
they
can
come
to
us.
They
can
tell
about
their
like
story.
They
can
tell
the
story,
or
I
just
know
the
coding-
I
don't
wanna
I
mean
I
have
say,
for
example,
in
a
scenario
like
I
am
too
much
occupied
in
my
company
in
my
day
job.
D
So
I
cannot
actually
contribute
to
the
code
side
of
that,
but
I
can
give
examples
of
the
yaml
documents
in
the
constructs
that
so
they
can
do
that.
We
have
an
example
repository
which
they
can
actually
contribute
and
make
more
easy
for
rest
of
the
users.
So
we
need
to
give
this
amount
of.
We
need
to
flood
this
information
amongst
to
the
community
and
the
the
population
that
there
are
like
kind
of
a
stakeholder
in
any
way
to
kubernetes,
and
then
we
it's
it's
one
way
of
welcoming
them.
D
A
D
Told
them
like
yeah
yeah,
so
I
gave
them
kids
dave
and
I
told
them
like
everybody
who
is
and
like
who
is
affiliated
with
kubernetes
dev
community
are
in
slack.
You
can
go
and
ask
even
do
a
dm
to
them.
They'd
be
like
very
happy
to
help
you
out
on
that,
like
join
slack,
cage
with
slack.
and
then
khdev.
That's
the
two
links
I
gave
them.
D
And
I
also
took
the
opportunity
of
asking
them
to
follow
khs
contributors
handle.
I
did
see
a
few
of
them
followed,
so
it
was
nice.
Nice.
E
Yeah,
I
wonder
if
we
could
do
a
blog
post
kind
of
thing
right,
because
there
are
like
levels
to
developer
skills,
but
there's
levels
to
like
community
skills.
Right
like
you,
we
could
say
like
not
entry
level
but
like
non-coder
right,
like
here's
all
the
things
you
can
do,
because
that's
me
right,
like
I
mean
I've
been
in
the
community
for
four
years,
I'm
not
a
coder.
You
know
I've
committed
code
or
you
know
changes
to
the
repos,
though
right,
like
you,
know,
there's
a
bunch
of
things.
E
A
I
think
I
think
the
thing
that
comes
to
mind
for
me
is
like
there's
a
kind
of
tyranny
of
choice,
there's
so
many
ways,
so
many
places
to
go
to
it's
such
a
massive
landscape
that
it's
really
you
know.
People
talk
about.
Architecture
like
like
when
marketing
simplifies
an
architecture
with
a
few
boxes
and
yeah,
that's
generally
inaccurate
by
some
definition
of
accuracy,
but
I
think,
like
that's
what
we
need
to
do
for
the
kubernetes
community.
We
need
to
create
a
boxy
101
introduction
to
where
do
I
go?
Hang
out?
D
D
Used
so
the
the
nabarro
was
also
part
of
that
he
was
also
john.
He
also
joined
there
like
he
also
shared
the
series
of
tweets
from
dims,
so
he
has
the
series
of
tweets
like.
Where
do
I
contribute?
Where
do
I
go
for
the
contribution
like
contribute
towards
given,
at
least
if
I'm
a
beginner
like
he
has?
He
has
that
pinned
in
his
profile
on
twitter?
A
Hey
if
I
could
abubarak
I
I
know
you're
you're
new
here,
I
don't
want
to
put
you
on
the
spot,
but
I
also
want
to
put
you
on
the
spot
because
you're
an
evangelist
so
like
that's
kind
of
your
job,
I'm
I'm
curious.
You
took
that
first
step
of
showing
up
to
a
meeting
and
being
here
so
like.
What's
on
your
mind
when
it
comes
to
taking
that
next
step
like
what
works,
and
what
are
you
hoping
to
to
do
now
that
you're
here.
B
Yeah,
I
think
I
have
experience
in
the
community
having
been
an
organizer
for
the
google
developer
group
and
google
cloud
developer
group,
so
it
it
can
be
down
to
not
first
to
when
coming
to
the
kubernetes
community,
because
just
like
pierce
has
been
mentioning,
everyone
thinks
you
need
to
be
a
developer
to
to
contribute,
and
that's
one
thing.
I've
also
experienced
personally
because
I
even
picked
up
some
courses
and
a
book
to
let
go,
but
work
hasn't
really
permitted.
B
So
I
think
the
main
parts
where
I'll
be
actively
participating
is,
I
think,
is
attending
meetings
like
this
to
see
where
probably
I
can
help
or
where
my
experience
or
where
my
or
where
there
are
openings
or
opportunities
for
me,
that
for
me
to
contribute
that
are
not
currently
being
met
in
a
meeting
since
probably
me
going
through,
issues
might
not
yield
much
result
or
I
don't
have
any
clear
direction
of
it
exactly
where
to
go
so
appearing.
E
B
A
Yeah,
that
is,
that's
beautiful,
that's
exactly
like.
I,
I
think
that's
a
really.
The
message
I'm
hearing
in
there
is
like
showing
up
is
contribution
and,
like
maybe
we
haven't
said
that
verbatim
out
like
out
there
like
that
to
show
up
is
a
great
first
step
and
it
could
be
the
step
that
you
stay
at
for
a
very
long
time
and
you
will
be
appreciated
because
you're
adding
knowledge
to
this
group
of
people.
B
D
Yeah
I
I
like
that
that
was
a
brilliant
idea.
Probably
we
can
say
like
whenever
we
are
saying
like.
Where
can
I
contribute
the
first
first
thing
we
first
statement
we
can
make
is
like
show
up
on
some
meetings
and
understand
like
what
they
are
doing
so.
D
E
A
B
B
B
F
C
B
C
There
is
contribution,
then
there
are
going
to
be
sub
projects
and
all
those
things
not
to
put
it
in
to
market
away,
but
we
need
to
make
sip,
contributes
more
sexy.
A
What
I
hear
is
like
make
it
more
attractive,
make
people
in
the
sense
like
they
gravitate
to
it
and
know
that
it's
their
home
and
know
that
they
can
add
value
there.
D
I
ca
so
I
I
have
a
slightly
mild
difference
in
the
opinion
with
abu
bakr
and
krish
both.
So
what
chris
said
is
like
you
have
to
figure
out
what
cig
you
want
to
go.
What
abu
bakr
said
is
like
figuring
out
which
cig
I
want
to
go.
Is
that
comes
with
an
experience?
So
that's
the
next
level.
So
what
I
would
say
is
like
both
of
them
are
right.
D
The
reason
abu
bakr
and
people
might
be
misrepresenting
or
misunderstanding,
but
the
reason,
abu
bakr
or
ph
might
be
thought
about
that
as
like,
going
through
all
the
six
and
reading
all
the
readmes,
because
when
chris
said
I
was
thinking
about
the
readme,
because
every
single
readme
of
every
single
six
has
its
own
scope
and
what
what
they
are
doing,
what
they're
gonna
do.
So
that's
yes
and
yes,
it
is
painful
to
go
through
all
the
sick
readmes
as
well.
D
Maybe
if
it
is
not
too
much
we
can,
we
can
ask
the
sig
leads
the
leads
of
every
single
sick
to
have
like
30,
to
30
seconds,
to
one
minute
of
a
video
where
they
can
actually
say
what
they're
gonna
do
or
what
they
are
doing
or
what
they
will
be
doing
and
put
it
in.
I
guess
this.
This
would
like
be
kind
of
making
it
sexy,
but
I
don't
know
but
going
through
a
video
of
a
minute
or
something
like
that
to
understand
what
sick
does
maybe.
E
Maybe
we
do
in
the
new
year
try
to
put
on
a
sig
meet
and
greet
like
live
and
just
have
like
there's
sig
members
on
every
like
region.
Right
like
just
have
somebody
sitting
on
a
call.
I
have
some
producer
in
the
background.
A
But
I
love
the
idea
of
making
it
asynchronous
and
permanent,
as
opposed
to
like
temporal,
and
you
have
to
show
up
in
this
time
zone
but
yeah
like
these
video
video
series
that
are
really
like
too
long
didn't
read,
but
abu
bakr.
What
were
you
going?
I
think
you're
going
to
say
something.
B
Yeah,
I
wanted
to
add
to
what
govind
said
that
the
videos
would
be
a
good
way,
but
I
think
if
we
can
have
something
like
a
persona
or
something
like
that
where,
if
you
are
a
writer,
these
are
the
places
you
might
want
to
go.
If
you
are
very
good
at
social
media,
these
are
the
things
you
might
that
might
need
your
help
or
might
need
your
assistance.
If
you
are
a
test
engineer,
these
are
probably
the
places
that
you
might
want
to
go
that
way.
A
Just
a
fun
side
story
here
I
have
been
lurking
in
the
kubernetes
community
for
three
years
and
I
only
started
contributing
during
covid,
because
I
wasn't
able
to
see
anybody
in
person.
I'm
like.
I
decided
that,
like
instead
of
going
for
quantity
and
like
spreading
myself
thin
like
I
normally
do,
I'm
just
gonna
try
to
go
quality
like
focus
just
here
see
if
I
can
add
value
and
if
it
fails,
you
know
at
least
I
tried
something
concrete
and
it's
been
phenomenal.
A
So
my
intention,
I'm
writing
an
article
I'll,
probably
get
a
publish
on
opensource.com.
Since
I
work
there
on
the
working
title
is
like
how
I
became
a
maintainer
of
kubernetes
with
four
hours
a
week
like
I'm
trying
to
do
some
sort
of
like
time-bound
thing
to
not
to
help
people
be
less
scared
about
it.
A
But
I'm
thinking
what
I'm
starting
to
think
about
is
like.
How
do
we
move
from
like
this?
This
really
powerful
discussion
into
each
of
us,
taking
if
we
have
the
time
like
some
step
to
share
our
own
stories,
because
I
really
do
think
the
gap
is
in
different
stories
on
different
places
and
ever
no
matter
what
you
write
about.
However,
you
write
about
it
like
chris,
you
saying
you're
a
non-code
contributor.
I
never
would
have
thought
of
you
that
way
like
that.
A
That's
a
really
cool,
like
you
claim
that
brand
in
a
very
positive
way,
when
it's
usually
sometimes
as
a
negative
connotation
and
like
I
want
to
do
a
time-bound
one,
because
I
feel
like
that's
the
stressor.
A
lot
of
people
bring
up
like.
A
I
don't
have
time
for
this,
but
my
intention
is
to
get
it
published
on
that
site,
because
I
kind
of
know
how
we
write
for
that
and
I'm
happy
to
coach
anyone
else
to
get
published
there
and
then
syndicate
it
so
republish
part
of
it
on
the
kubernetes.io
blog
and
link
them
together.
A
Does
anyone
else
like
based
on
what
we're
talking
about
whether
you
want
to
like
draw
a
flow
chart
of
like
how
to
contribute
or
maybe
pursue
getting
videos
from
some
sig
leads,
which
sounds
challenging
but
rewarding
any
any
concrete
ideas
we
should
write
down
at
this
point,
I
just
like
to
grab
those
throughout
the
meeting,
so
we
don't
lose
all
the
good
ideas.
E
E
A
You
know
personally
I'd
throw
the
pitch
that,
like
you
saying
like
how
I
see
myself
as
a
like,
we
need
more
non-code
contributors
like
that
would
be
maybe
like
the
working
title
and,
like
you,
explain
how
you
contribute
as
a
non-code
contributor
and
how
you
mentor
other
people
to
get
into
the
system,
whether
they
code
or
don't
code
like
you,
have
a
huge
impact
in
a
way
that
I
don't
think
people
would
realize
yeah.
I
think
you
have
a
great
story
there
personally.
E
F
Yeah,
so
I
just
have
a
quick
thing.
I
really
like
the
flowchart
thing,
so
I
was
thinking
so
different.
Six
might
have
different
contributors,
so
the
six
have
more
idea
of
what
kind
of
contributors
they
have
like.
Can
we
just
send
out
like
a
survey
asking
people
what
kind
of
contributions
they
receive
and
how
can
actual
people
contribute?
So
in
a
way
we
can
get
all
the
data,
different
sects
and
different
kinds
of
contributions?
Probably
then
it's
easy
to
make
a
flowchart.
A
A
A
Fuzzy
chef,
which
is
one
of
my
favorite
twitter,
handles
yes,
other
other
concrete
ideas
again
like
I
know,
there's
a
lot
going
on
over
this
time,
so
you
don't
have
to
sign
up
for
more
than
you
have
time
for,
but
I've
been
wanting
to
write
this
article
for
six
months
and
I
blocked
some
time.
A
A
Good,
all
right,
great
okay,
so
another
idea
that
was
floating
around
this
was
really
great
kind
of
broader
scope,
but
to
narrow
in
the
scope
you
know,
blogging
on
our
in
our
community
is
a
very
technical
feat.
Like
you
go
from
this,
you
get
an
idea
and
you're
not
sure
where
to
put
it
first
and
then
we
generally
guide
you
to
put
it
into
a
google
doc
and
then
it's
dot
dot
dot
through
a
wild
markdown,
pull
request,
review
process.
B
A
You
know
we
can't
fix
that
in
a
lot
of
ways,
but
maybe
we
could
fix.
Like
the
initial
step.
I
was
thinking
about
pitching
embedding
a
a
blog
submission
form
on
kubernetes.dev,
the
dev
community,
asking
specifically
for
contributor
content,
and
I
am
pretty
familiar
with
how
to
you
know
how
to
set
that
up
in
a
way
to
maybe
we
can
reject
the
spam.
You'll
always
get
spam,
but
just
to
provide
people
with
a
a
way
of
contributing
a
blog
idea
without
needing
to
know
exactly
where
to
be
in
the
kubernetes
community.
A
E
A
E
E
A
Interest,
but
you
know
just
put
all
the
disclaimers
where,
if
it's
not
from
a
contributor,
then
we
won't
even
respond.
We
review
it.
My
proposal
is,
we
review
it
once
a
week
in
this
meeting,
so
no
one's
on
like
constant
interruption,
duty
to
check
it
and
it's
very
optional,
but
yeah.
No,
I
hear
you
loud
and
clear.
It's
it's
definitely
kubernetes,
you
might
say,
is
a
big
deal.
A
A
D
I
think
it's
gonna
create
a
lot
of
spam.
That's
for
sure,
and
I
think
you
can-
I
mean
if
you're,
like
already
that's,
hosted
on
netflix,
so
we
can
actually
filter
it.
Whether
it
is
a
contributor
or
not.
The
submitter
is
the
author
of
the
content
test,
but
even
though,
if
we
do
that,
we
have
like
a
130
000
plus
contributors
that
are
part
of
the
kubernetes
organ
kubernetes
6,
so
it's
it's
gonna,
be
too
much.
D
That's
one
thing
I
would
like
kind
of
fear
about,
but
on
the
other
side
also,
yes,
it
would
get
a
lot
of
good
articles
as
well
a
lot
of
good
submissions
as
well.
So
the
the
process-
I
don't
I
don't
envision-
is
like
how
are
we
going
to
because
we
don't
have
a
full
time
fte
who
is
sitting
behind
that
form
and
filtering
manually?
Okay.
This
is
good.
This
is
bad
like
that,
like
we
don't
have
a
fte
to
do
that.
D
So
that's
only
one
thing
I
would
be
more
concerned
on
like
how
are
we
gonna
do
that
like?
If
we
have
good
funding,
we
could
use
the
full
capability
of
netlify.
C
Yeah
and
to
add
a
thought
right
rather
than
inviting
ideas,
why
don't
we
just
invite
people
to
you
know
kind
of
intern
with
us?
You
know
just
to
say
lack
of
a
better
word
like
the
release
team
does
right
every
release,
they
just
gather
up
people
and
they
do
the
work
right.
So
why
don't
we
get
some
people?
Let's
say
every
quarter,
six
months
or
whatever
it
is,
and
we
just
help
them
guide
them
through
writing
some
stuff
invite
applications
and
do
all
that
sort
of
thing.
C
Probably
that
can
be
formed
into
something
better,
but
that
would
at
least
help
us
filter
the
number
of
people
who
are
actually
writing
stuff.
A
That's
interesting,
so
I
I
really
enjoy
that
because
it's
the
something
I've
learned
from
working
on
publications
for
a
few
years
now
is
that
when
you
invite
somebody
they
feel
honored
and
like
that
is.
That
is
a
good
first
step
and
then,
if
we
offer
to
coach
them
through
the
process
and
reduce
the
friction
of
it,
you
know
I
feel
like
it's
got
a
decent
chance
of
having
results.
F
I
just
have
a
quick
thing
to
what
you
just
said:
yeah.
What
do
you
think
of
an
idea
of
like
a
shadow
program?
For
the
blog
say
you
cast
lynn
and
chris,
who
have
been
writing
blogs
like
we
can?
Just
we
have
a
lot
of
issues
for
the
blog,
so
we
can
just
pick
up
new
people.
We
can
coach
them
through
a
blog
and
then
they
might
coach
new
people
later.
So
we
can
just
create
a
cycle.
A
F
Probably
the
wrong
time
we're
trying
to
help
non-code
contributors
to
write
blogs.
So
say
there
are
people
who
have
technical
skills
who
wants
to
contribute.
So
we
have
a
lot
of
issues
for
blocks,
so
we
have
new
blog
ideas,
so
each
one
of
them
can
pick
an
idea,
so
one
of
us
can
actually
coach
them
through
how
to
do
it.
So
how
do
we
do
it,
the
hack
and
the?
F
A
F
B
A
So
I
the
the
thing
I'm
getting
caught
up
on
is
we
have
that
program.
We
have
a.
We
have
a
line
item
that
says
we
have
a
blogging
program
and
we
have
people
that
blog
and
we
have
you
know
to
cut
the
canyons
point.
130-Ish
thousand
people
around,
so
we're
not
flooded
right
now
and
we're
not
getting
interest
and
the
story,
I'm
telling
myself
is
because
it's
hard
like
people,
don't
know
where
to
start.
They
don't
know.
E
A
B
A
A
Yeah,
it
yeah
exactly
like
if
we
want
to
keep
our
if
you're
like
me
and
you're,
trying
to
like
keep
the
amount
of
time
you
spend
per
week,
contributing
to
this
pretty
tight
like
we
have
to
clearly
scope
whatever
we're
doing
or
it
will
just
leak
into.
You
know
if
some,
if
we're
now
helping
people
work
through
their
articles
and
we've
got
to
coordinate
with
their
calendars,
you
know
getting
an
article
over
the
line
can
take
eight
to
10
hours
over
a
couple
weeks
easily.
A
So
do
we
have
the
resources
like
do
we
have
the
documentation
of
of
how
this
works
in
the
right
place
and
then
for
me,
it's
like.
I
don't
really
know
what
the
steps
are.
Yet,
if
we,
if
we
can
define
clear
steps,
we
can
guide
people
through
them
in
like
a
reasonably
set
amount
of
time,
but
yeah
a
lot
of
moving
parts.
B
So
just
you
know
what
I
think
I
have
is
especially
around
people's
submitting
blocks,
suggestions
and
so
on.
If
we
can
use
the
issue
issues
in
the
project,
the
github
issues
creates
like
a
template
where,
once
you
create
a
new
issue,
you
have
a
template
of
things
to
fill
and
certain
labels
to
to
apply
and
that
way
we'll
be
able
to
filter
it
to
be
the
people
who
are
already
contributors
who
have
signed
the
cncf
agreement.
A
B
Able
to
create
issues
that
is
one
filter.
The
next
one
is.
They
have
to
specify
some
certain
levels
depending
on
the
kind
of
topic
they
they
will
be
talking
about.
That
way,
we
can
then
probably
say:
okay,
someone
should
probably
review
suggestions
that
are
maybe
kubernetes
or
storage
or
any
other
thing.
B
Now
we
we
are
able
to
reduce
spam
and
some
bots
or
something
can
be
used
to
do
some
other
things,
with
the
issues
to
make
managing
them
much
more
easier
and
and
better
and
also
discussions
will
happen
under
the
comments,
because
it's
in
the
public
view
more
people
can
probably
contribute
ideas
or
provide
more
suggestions
to
the
original
suggestion.
B
No,
I
mean
I
bought
probably
a
shot-
that's
connected
to
github,
to
probably
clean
up
based
on
labels.
The
way
the
same
way
it's
on
the
main
kubernetes
project,
where,
if,
after
some
time,
it
tells
you
that
okay,
this
issue
is
stale
and
so
on,
yeah,
something
like
that
to
probably
filter
spam
or
do
some
other
housekeeping
to
make
sure
the
conversations
are
moving
or
the
issues
are
being
handled
up
appropriately.
B
E
A
A
Cool
I
I
I
dig.
I
dig
that
abu
bakar,
this
idea
of
like
it's
very
important,
that
we
use
the
same
infrastructure
that
we're
already
using
and
not
branch
off
too
hard
that
will
somewhat
limit
people's
perception,
like
they
might
think.
A
If
I'm
submitting
a
github
issue,
I
am
coding-
and
that
might
scare
me,
but
if
we,
if
we
can
yeah,
I
I've
kind
of
had
this-
maybe
a
little
little
bit
of
a
far-fetched
idea
of
just
like
what
would
it
be
like
for
people
to
not
have
to
see
mark
down,
even
because
I
know
mark
learning,
markdown's,
not
trivial,
like
I,
I
know
it
feels
simple
once
you
know
it,
but
it's
it's
not
simple,
and
we
sometimes
you
know
in
technology
groups,
kind
of
trivialize
things
like
git,
which
kid
is
freaking
complicated,.
A
There's
a
really
really
good
one
built
into
the.
This
is
a
an
aside,
but
I
I've
been
following
it:
the
there's,
a
javascript
library
built
into
discourse,
the
open
source
community
platform,
and
I
have
been
trying
to
extract
the
javascript
from
it
just
for
how
they
convert
a
copy
paste
document.
When
you
paste
from
google
docs
in
there,
it's
perfect
mark
down
every
time
and
that's
crazy
hard.
I
don't
know
what
they
do
to
do
that.
A
A
C
B
Idea
of
using
google
forms
is
it's
also
a
great
one,
but
we
can
use
apps
script,
for
example,
use
google
forms,
then
in
apps
script
probably
make
api
calls
to
github
or
whichever
way,
to
automate
and
do
some
other
things
in
the
background
for
for
the
data
to
be
more
easier
for
the
team
to
manage
and
handle,
and
also
easier
for,
anyone
who
wants
to
contribute
to
do
it
as
similar
as
possible.
A
Yeah
no
you're
completely
right.
We
I
I
kind
of
forgot
to
consider
that
yeah
apps
script
is
a
very
powerful
automation
platform
built
into
google
docs.
If
you
need
to
basically
my
javascript's
pretty
terrible,
but
it's
it
could
be
a
step
to
like
yeah.
It's
a
filtering
like
just
being
like
hey.
If
you've
never
contributed
to
kubernetes,
we
will
not
even
review
this
submission,
so
go
submit
like
go.
Go
open!
An
issue
go
talk
to
somebody
yeah.
D
D
You
think
it
might
be
worth
to
get
some
insights
from
them
like
because
it's
okay,
it's
like
I
mean
kubernetes
dot,
io
and
the
case
studies
are
published
there.
So
there
should
be
some
existing
process
to
collect
all
the
case,
studies
from
all
the
kubernetes
users
and
the
companies
that
they
are
using
given
a
days.
B
A
D
A
Go
yeah,
so
I
think
we
we
end
ten
minutes
before
the
top
of
the
hour,
so
I'll,
just
kind
of
bring
us
to
a
close
by
saying
yeah
we're
going
into
a
new
year,
and
I
think
we
only
have
existed
for
about
six
months,
maybe
eight
months,
if
you're,
if
you're
being
generous-
and
we
have
this
group's
already
been
asked
to
help
in
the
blog
subgroup
of
documentation
to
help
manage
some
of
the
community
outreach
when
something
goes
right
and
when
something
goes
wrong.
A
We're
we're
being
asked
to
tweet
things,
which
means
people
actually
care,
what
we
tweet,
which
is
hard
to
do
so.
We've
really
kind
of
integrated
ourselves
into
the
kubernetes
community
in
a
meaningful
way,
and
it's
very
early,
though
so,
there's
a
huge
opportunity
to
clarify
how
we
integrate
into
other
teams
in
meaningful
ways
and
how
to
like,
reduce
the
friction
of
non-code
contribution
and
yeah
and
to
keep
writing
some
cool
code,
because
resula
does
that
and
karthik
and
you
do
as
well.