►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20211112
Description
[SIG ContribEx] Weekly Marketing Meeting for 20211112
A
Welcome
welcome
thanks
for
joining
the
contributor,
comms
upstream
marketing
team
meeting
on
friday
november
12th.
I
would
love
for
you
to
hop
right
in
and
add
yourself
to
the
attendees
list
on
the
agenda.
Thank
you,
josh,
for
sharing
it
and
like
we
always
do
we're,
starting
with
the
updates
and
sort
of
big
wins.
A
I
gonna
steal
the
beginning
of
the
mic,
and
just
say
this
is
my
last
time
hosting,
as
I
mentioned
on
the
mailing
list,
I'm
stepping
down
from
the
program
lead
of
this
amazing
group
of
people,
and
we
have
a
bunch
of
really
talented
people,
including
chris
and
caslin,
and
a
couple
other
regulars
who
are
all
interested
in
co-chairing
and
are
thinking
through
that
model
going
forward.
But
I
guess
just
want
to
pass
it
to
you
know
chris
and
caslin.
How
are
you
all
thinking
about
who's
hosting
next
week.
A
Cool,
I
just
want
to
confirm
it
right
at
the
top
that
this
is
going
to
keep
happening.
So
thank
you,
chris,
and
thank
you
all
for
coming
here.
It's
really
really
awesome
to
see
a
great
group
of
people
and
that
we've
created
a
space
that
people
feel
they
can
contribute
to
kubernetes
and
also
we
can
help
kubernetes
contributors
talk
to
each
other,
which
has
always
been
the
theme
and
is
really
valuable.
A
See
there's
a
link
to
the
contributor
comms
reorganization.
This
is
a
oh
really
looks
like
there's
a
little
bit
of
adjustment.
Justin
just
left
me
to
fix
it
up,
but
the
goal
of
or
stephen
augustus
I
mean
so.
The
goal
of
this
one
is
to
just
capture
all
of
what's
been
working
about
this
group.
We
had
an
idea
of
what
it
would
look
like
about.
A
Oh
my
god,
almost
two
years
ago,
and
that
was
a
great
premise
and
what
we
found
is
it
worked
a
little
differently
in
practice,
so
I
wanted
to
kind
of
sign
off
by
making
sure
I'm
checking
the
box
of
documenting
what
we've
learned
and
and
mapping
it
into
where
it
is
in
the
repo,
and
that
is
that
one.
If
you
want
to
look
through
it,
I'm
going
to
try
to
get
that
merged
as
soon
as
possible
and
just
a
reminder
like
you
can
always
keep
improving
everything.
A
There's
a
ton
of
documentation
here,
we've
done
our
best
to
intentionally
link
it
to
each
other
and
not
have
stuff
contradict
each
other.
But
inevitably,
with
this
many
people
contributing
to
something
this
large
there's
going
to
be
drift
and
when
you
see
something,
definitely
feel
free
to
jump
in
and
update
it
or
open
an
issue
to
fix
it.
A
Only
thing
holding
it
back,
I
think
it
was
it
needed
to
go
through
the
a
review
that
paris
was
helping
us
get
through
with
the
steering
committee,
and
it
has
done
so
and
folks,
like
it
and
steven
just
found
a
couple,
typos
slash
like
smaller
requests.
He
wants
me
to
tidy
up,
and
I
think
after
that
it
should
be
be
good.
A
I'll
poke
in
and
make
sure
that
keeps
happening,
but
definitely
this
is
also
a
really
interesting
case.
If
you're
new
and
you're
you
don't
mind
if
you're
github
friendly,
you
don't
have
to
know,
get
and
get
commands
in
order
to
be
part
of
this
group,
but
if
you're
interested
in
like
what
does
a
review
process,
look
like
this
is
a
really
textbook
example
of
a
lot
of
people
tagging
in
and
getting
the
review
necessary
to
make
sure
things
click.
A
So
if
you
have
questions,
you
can
always
come
back
with
them,
but
yeah
I'll
keep
working
through
that.
D
It
was,
you
know,
crash
caslin.
They
once
said
they
will
review
it.
So
did
you
guys
see
through
it?
Also
I
took
reviews
from
few
of
the
folks
and
according
to
dims
for
the
new
repository
and
the
new
integration
that
is
required.
D
So
we
have
to
put
this
new
issues
in
org.
There's
a
template
for
that.
So
I'll
put
that
but
yeah.
This
is
my
first
time
not
creating
new
repositories.
D
You
know
security
contacts
and
all
those
things,
so
I
need
help
with
that.
A
Okay,
great
so
well,
first
off,
congratulations
going
through
this
for
the
first
time
is
a
milestone
and
that's
really
awesome.
Two!
Okay,
so
you're
saying
you
need
some
help
kind
of
navigating
this
any
who
here
has
kind
of
gone
through
that
sort
of
review
cycle
before
and
maybe
could
help
abroad
get.
D
Yeah
also,
it
needs
third-party
integration,
so
we
also
have
to
open
an
integration
for
the
categories
in
other
authority.
So
that's
also.
E
D
That
is
okay
yeah,
I
put
it
in
the
docs,
so
you
go
to
this
link
and
there
are
one
scenario
for
option:
contributors
just.
A
So
to
break
down
the
different
requests,
because
this
is
a
pretty
big
project
and
that's
great
they're,
just
it's
helpful
to
be
clear
about
what
we
need
to
what
degree.
I
think
the
one
is
helping
with
a
review
of
the
actual
content
of
the
scenario
scenario,
but
you're
also
asking
like
new
repo
needed
wants,
help
getting.
D
Yeah,
I
I
did
that
yeah
also
yeah
bob
suggested
me
to
come
up
with
the
you
know
this.
The
ownership
will
bc
contribute.
So
I've
talked
about
this.
Just
I
needed
this.
You
know
co-owners
and
the
security
contract,
so
I
was
confused
about
that
and
the
review
are
being
done
by.
C
Yeah,
okay,
you
brought
it
up
here,
I
would
say,
also
put
it
into
contribute
slack
and
that
sort
of
thing,
because
in
a
lot
of
ways
the
catacota
thing
is
more
of
a
mentoring,
subproject
task.
A
F
C
Had
a
a
self-paced,
you
know,
you
know,
learn
how
to
do
kubernetes
contributions
technically
before.
A
So
yeah
and
to
recap
the
reason
it
started
here
was
it
was
a
content
review
of
like
hey
is
the
grammar
of
this.
Is
the
flow
of
this
good
which
but
yeah
it's
a
one
of
those
fits
across
the
whole
spectrum
of
contributions,
and
we
don't
have
like
a
great
one-stop
shop
use
this
guide
and
you'll
get
through
it,
but
we
will
help
you
get
through
it.
So
just
keep
keep
at
it
sounds
like
next
step
might
be
to
to
share
it
and
contrib
acts.
D
Yeah,
so
there
there's
something
called:
seek
ownership
required,
so
bob
recommended
that
I
say
contradicts
will
take
the
ownership
so
yeah
it's
done
so
now
I
will
put
a
in
the
mailing
list.
I'll
put
this
say,
contribute
mailing
list
as
well
as
in
the
slack,
and
you
can
see.
A
Okay,
yeah
and
we'll
just
keep
checking
in
on
it,
and
this
meeting
is
as
needed
or
async
in
our
our
slack
channels
and
yeah.
If
we
keep
checking
along
if
it
gets
stuck,
somebody
will
tag
in
and
help
get
unstuck.
A
A
A
A
Well,
take
some
of
the
credit
and
but
give
it
to
everybody
else
too,
for
sure
great
work,
great
any
sort
of
articles
and
progress.
We
want
to
check
in
on.
E
So
I
I
created
the
first
draft
of
the
sig
multi-cluster
spotlight
and
I
set
the
send
the
editable
version
to
chris.
It's
a
bit
different
because,
like
I'm
narrating
from
from
a
speech
to
text,
so
I
wanted
to
get
chris's
take
on
the
first
two
answers
I
added
and
based
on
on
his
inputs.
I'm
gonna,
I
guess,
frame
the
the
later
questions
and
my
goal
is
once
I
have
chris's
review
on
that
I'll,
pass
that
on
to
jeremy
and
then
start
the
formal
prv
review
process.
E
No
rush,
so
I
added
like
the
intro
and
the
answers
to
the
first
two
questions.
So
if
you
could
kindly
check
like
if
those
answers
seem
okay,
based
on
your
discussion-
and
you
can
add-
actually
comments,
I
added
a
hack,
md
link,
you
can
add
comments
there
and
then
yeah,
maybe
maybe
once
you
do
that
I'm
gonna
add
the
other
questions:
okay,
cool,
yeah,
yeah,
okay,.
G
C
Yeah
I
wanted
to
put
that
on
there
just
because
so
this
is
something
sig
node
is
doing.
Is
the
writer
of
the
blog
post
on
this
call?
I
don't
think
they
could
make
it.
C
Yeah,
okay:
this
is
something
signature
is
doing,
because
there
was
obviously
a
big
stir
in
some
unfortunate
ways
about
the
docker
shim
removal
when
it
was
first
deprecated,
but
we
now
have
the
actual
removal
date
looming
in
one
two.
C
It's
what
allows
you
to
run
kubernetes
on
top
of
regular
docker,
which
was
never
designed
to
be
a
component
in
a
system
and
the
and
we're
not
going
to
support
it
anymore
because
for
people
who
still
want
to
use
kubernetes
with
docker.
As
far
as
we're
concerned,
the
answer
is
container
d.
Docker
shim
is
extremely
painful
to
maintain
and
nobody
wants
to
work
on
it.
C
You
know
so,
regardless
of
what
people
want
to
use,
is
the
runtime
they're
going
to
have
to
take
action
in
124?
If
they
have
been
using
docker
shim
in
the
past,
they
can
switch
to
docker
cri.
C
They
can
switch
to
apparently
there's
a
fork
of
docker
shim
being
maintained
by
mirantis.
I
believe,
but
none
of
it
is
just
install
124
and
keep
running
the
so
node
wants
to
get
delay
of
the
land.
I
mean
with
the
surveys.
They
want
to
delay
the
land
and
one
of
my
questions
for
this
group.
In
addition
to
you
know,
I
suggested
that
they
do
a
small
blog
post
as
a
reference
to
the
survey.
B
Absolutely
I
mean
you
know
the
case
contributor
handle.
We
can
always
go
ask
cncf
to
retweet
whatever
at
some
point
but
like
getting
out
to
end
users.
We
don't
really
have
a
great
way.
Do
we
yeah.
B
C
A
C
A
I
think
relation
we
should
really
lean
on
cncf
in
this
heavily.
I
I'm
sure
we
could
get.
You
know
chris
to
to
share
something
publicly.
Maybe
we
start
by
sharing
on
our
twitter
and
then
use
that
as
a
way
of
saying
and
ping
people
behind
the
scenes
like.
Could
you
please
amplify
this
message
for
users
and
just
really
make
sure
the
language
is
sculpted
to
be
like
users
of
kubernetes
like
this?
This
is
coming
up
and
we
really
need
your
feedback.
It's
urgent,
like
you,
know,
make
it
as
obvious
as
possible.
A
C
F
And
maybe
maybe
ask
them
to
post
a
20
second
video
or
something
like
whatever
is
feasible
for
them
and
how
they
connect
with
their
audience
so
like
end
users
and
who
are
trying
out
the
kubernetes
platform.
So
it's
going
to
be
a
big
reach
because
we
have
a
very
powerful
ambassadors.
So
that's
going
to
be
a
good
one.
C
The
okay:
that's
a
really
good
idea:
yeah,
yes,
yeah!
If
nobody
from
node
is
directly
an
ambassador,
I
can
always
take
it.
B
A
C
F
F
E
G
A
A
Would
you
like
to
introduce
yourself
further
and
I
don't
want
to
mispronounce
your
name,
so
could
you
pronounce
your
name
for
us.
F
Yeah,
I
am
hello
everyone.
This
is
my
first
time
being
here.
I
am
narendra.
That's
my
full
name,
that's
my
indian
name,
so
you
can
shortly
call
me
as
naren
so
yeah.
I
am.
I
started
my
kubernetes
journey
last
year,
mostly
because
of
chris
and
all
the
amazing
people
with
the
red
hat
which
openshifted
at
twitch
and
all
the
same
kubernetes
slack
people.
So
I've
been
a
self
learner.
So
right
now
I'm
doing
all
things
in
kubernetes
and
preparing
myself
to
do
the
cka
and
cka
dnc
certifications.
F
So
that's
me
yeah
happy
to
be
here
and
I'm
trying
to
become
an
active
contributor,
then
user.
So
we
are
taking
my
steps
baby
steps,
one
by
one
one
by
one,
so
start
attending
sick,
contributex
meetings
and
sick
dogs
meeting
simultaneously
so
to
get
into
the
ecosystem
and
know
how
things
work
properly,
how
things
are
going
and
to
know
the
feel
of
how
things
are
happening
so
yeah?
That's
it
welcome
yeah.
Thank
you.
D
Yeah
I'll
go
if
nobody
else
is
here
so
hi,
I'm
srikaran,
but
people
generally
call
me
as
free
or
current,
because
I
guess
too
many
syllables
yeah,
so
my
kubernetes
journey
started
by
because
I
found
a
bunch
of
people
on
twitter
that
were
really
really
interesting.
I
mean
shout
out
to
dan
pop.
I
found
a
bunch
of
those
people
that
were
active
in
the
whole
ecosystem
and
I
started
trying
to
learn
about
what
kubernetes
is,
and
you
know
whether
I
could
get
involved
right,
as
I
was
doing
that
I
think
bill.
D
C
Okay,
yeah
go
for
it
I'll.
I
a
lot
of
the
regulars
know
me,
but
here
I'm
josh,
burkus
I've
been
in
sick
contributor
experience
for
a
long
time.
I
don't
usually
make
this
meeting
because,
to
be
honest,
friday
is
usually
my
only
day
when
I
don't
have
to
get
up
early
the
so
because
I'm
on
the
u.s
west
coast,
the
and
relevant
to
this
group,
I
am
involved
in
a
couple
of
things,
one
of
which
I
put
on
the
agenda
so
we'll
discuss
that
later.
C
On
the
other
one
is
I'm
one
of
the
two
writers
of
last
week
in
kubernetes
development,
which
is
actually
a
sub-project
of
this
group.
Although
it's
been
pretty
much
exclusively
me
and
noah,
if
somebody
ever
feels
like
getting
involved
in
lwkd,
that
would
be
fun.
C
F
Lwkd
is
there
any
page
or
something
like
that.
C
C
It
started
out
as
a
newsletter
that
I
wrote
originally
internally
for
the
red
hat
openshift
teams
to
help
them
keep
track
of
what
was
going
on
across
the
project
and
realized
that
actually
the
content
was
not
particularly
red
hat
oriented,
and
so
I
made
it
public
and,
and
then
it's
been
going
since
then,
and
so
it
sort
of
complements
coupe
weekly,
which
is
a
separate
newsletter
that
covers
what's
going
on
in
the
kubernetes
ecosystem,
and
lwkd
is
just
what's
going
on
in
the
kubernetes
code
base.
Basically,.
B
C
You
know
I
we
would
love
to
have
extra
contributors-
okay,
but
obviously
we've
been
putting
it
out
for
the
last
two
years
with
just
me
and
noah.
So
it's
going
to
keep
coming
out.
It's
just
that.
Sometimes
what
happens
is
I'm
at
a
conference
and
noah
is
slammed
with
sre
work
and
you
end
up
with
a
very
light
or
non-existent
issue,
so
it
would
be
lovely
to
have
a
third
writer
on
it.
A
C
C
Times,
if
no
other
time
what.
B
C
Up
with
me
on
slack,
because
basically
we
have
a
very
simple
process,
which
is
we
start
on
the
issue
on
mondays
and
start
writing
it.
You
can
kind
of
see
the
format
there.
So
if
you
wanted
to
try
writing
for
it,
then
we
would
just
coordinate
on
which
portions
you
were
going
to
take.
F
F
C
We'd
be
into
ideas,
for
you
know,
because
we've
been
kind
of
in
the
existing
format
for
the
last
two
years.
So
if
you
we'd
be
into
ideas
about
other
things
that
we
should
add
or
change
or
whatever
the
existing,
the
current
format
exists
because
it's
easy
for
me
and
noah
to
put
it
out,
and
people
seem
to
like
it.
A
A
F
I'm
entering
maybe
a
mentoring
would
be
a
good
thing
for
me
as
well,
because
you
you
are
in
the
system
like
you,
are
doing
it
for
three
and
a
half
years,
but
right
now
I'm
coming
here.
Like
I
don't
know.
Where
do
I
look?
What
do
I
look
and
how
do
I
look
so
I
might.
C
F
D
I
mean
I'd
love
to
work
for
the
newsletter
as
well
write
for
the
newsletter
as
well,
but
I'm
curious.
What
does
the
work
look
like,
because
I
I
mean
I
can't
imagine
it
being
an
easy
task
to
figure
out
exactly
what
has
been
going
on
over
the
last
one
week
right
so
any
inputs
on
what
you
folks
actually
do
when
when
it
comes
to
writing
how
many
sources
do
you
need
to
check
with
that
kind
of
stuff.
C
A
So
yeah
I
mean
it
is
a
great
question.
I
I'm
with
yeah
the
quran
that
I'm,
I
don't
actually
know
like
how.
How
are
you
aggregating
that
so
that
you
know
what
to
filter
and
some
operations?
Okay,.
C
I
mean
it's
yeah,
I
mean
it's
actually
pretty
simple,
because
the
thing
is
that
the
the
other
thing
that
kind
of
fed
into
it
was.
I
was
on
the
release
team
a
bunch
of
times
right.
So
the
you
know
you
can
see
there.
It
has
several
sections,
one
is
announcements
which
is
stuff
we
know
about
that
has
been
announcement
for
contributors,
the
oh,
the
other
thing
this
group
should
know
actually,
which
is
if
we
have
something
that
we're
trying
to
get
out
to
contributors
in
general.
C
I
yeah
and
you
know
the
rest
of
the
channels
are
putting
it
out
on
say
tuesday
or
something
and
you
want
it
in
lwkd.
For
that
reason,
then
just
go
ahead
and
ping
me
or
noah
the
and
the
you
know,
because
we
take
just
basically
things
that
we
know
from
the
community
and
announcements
of
that
church.
C
So
anything
that's
been
sent
to
kubernetes
dev,
you
know
already
or
put
on
the
blog
that
is
contributor
oriented
put
it
there,
followed
by
information
about
the
current
status
of
the
release,
because
that
was
kind
of
an
important
part
of
it,
and
obviously
that's
coming
from
the
release
team
and
release
engineering
for
patch
releases
and
then
followed
by
the
whole
set
of
what
got
developed
in
kubernetes,
and
so
that's
a
combination
of
things.
I
generally
do
the
summary.
C
I
pull
everything
that
has
a
release
note
on
it
that
was
done
in
the
last
week
and
provide
summaries
of
any
of
those
that
are
not
too
obscure,
and
the
definition
of
too
obscure
is
either
it's
a
minor
bug
fix
or
it's
a
bug
fix
or
something
else
on
something
that
doesn't
apply
to
most
of
our
users.
Like
a
specific
cloud
provider,
the
I
mean
as
far
as
I'm
concerned,
all
the
cloud
provider
stuff
is
past
due
to
get
out
of
court
anyway,
and
so
I'm.
C
In
reporting
on
it,
the
and
and
I
also
look
for
deprecations-
I
try
to
actually
have
fairly
comprehensive
reporting
on
deprecation,
simply
because
it's
something
that
a
lot
of
folks
have
complained
that
they
don't
become
aware
of
until
stuff
stops,
stops
working,
the
and
and
then
usually
it's.
C
A
Know
others
I
would
I
would
love
to
like-
have
a
screen
recording
of
you
two
or
going
through
these
sources
and
like
just
one
of
us,
volunteering,
to
to
write
down
what
you're
doing
like,
because
I
feel
like
linking
to
each
of
those
things
linking
to
the
views
of
the
world
you're
going
to.
I
mean
it's
second
nature
to
you
after
three
years
for
sure,
but
it
is
far
from
nature
to
me
and
I
think
that
would
be
a
big
help
to
getting
more
contributors
out
of
this
group.
In
my
mind,.
A
I'll
leave
it
to
chris
to
coordinate
something
as
he
steps
into
kind
of
managing
the
program
here,
but
there's
there's
a
there.
There
there's
there's
something
we
can
scratch
at
and
get
you
a
backlog
of
potential
contributors,
and
I.
B
I
wrote
for
my
own
newsletter
like
a
writing.md
file
that
spells
out
exactly
the
step-by-step
process
that
I
do
in
case.
I
need
to
actually
hand
it
off
to
somebody
at
some
point
right,
so
you've
got
a
good
contributing
md
here,
it's
just
the
you
know
the
rest
of
it
kind
of
deal,
how
you
get
to
the
issues
or
features
yeah.
C
The
well,
I
don't
want
to
cement
it
too
much
right,
because
we
got
a
new
person.
One
of
the
things
I
would
hope
to
get
with
a
new
contributor
would
be
some
ideas
for
other
other
kinds
or
other
sort
of.
C
C
Now,
because
it's
what
it's,
what
noah
and
I
can
each
produce
in
like
an
hour
and
a
half
every
week,
so
the
but
a
new
person
would
actually
potentially
have
other
stuff,
which
would
be
wonderful.
A
C
Of
stuff,
so
one
of
the
other-
many
hats
that
I
wear
is
I'm
a
survey
geek
and
so
I've
kind
of
taken
over
handling
official
surveys
for
the
project.
C
Also
because
of
the
cncf's
account
status
for
surveymonkey.
We
cannot
have
multiple
people
have
access
to
the
surveymonkey
account
only
one
person
at
a
time
so
currently
that
one
person
at
a
time
is
me-
and
it's
usually
me,
although
I
can
hand
it
off
to
somebody
else.
Yes,
they
really
need
it.
It's
just
the
the
handoff
process
is
exclusive,
and
so
it
has
to
be
coordinated.
C
The
and
one
of
the
things
that
came
up
this
last
week
is
we
wrote
this
up.
We've
got
it
under
comms
the
document
of
how
to
request
a
survey.
We
have
a
template
in
the
kubernetes
community,
repo
for
requesting
a
survey
at
the
time
that
we
started
this.
C
And
so
I'm
wondering
you
know,
is
there
any
good
way
that
we
can
make
people
more
aware
that
there
is
a
process
for
surveys
and
and
and
why
it's
important
not
only
for
getting
maximum
impact
on
surveys
by
by
actually
distributing
using
the
right
tools?
There's
also
the
issue
that
if
something's
gonna
be
official
community
survey,
there
are
standards
like
it
has
to
be
gdpr
compliant
right.
C
The,
and
that
was
actually
a
big
issue
with
the
recent
student
survey
that
that
that
I
think
we've
got
open
as
a
ticket
where,
where
they
actually,
they
wanted
a
blog
post,
et
cetera,
and
I'm
like.
We
can't
distribute
this
through
officially
through
the
community,
because
it
doesn't
say
who
the
survey
belongs
to
or
who's
going
to
see
the
data
or
how
the
data
is
going
to
be
used
or
how
to
remove
yourself
from
it,
which
is
by
the
way
for
those
who
are
not
familiar.
B
B
B
Not
under
under
resources,
I
think
you
could
totally
put
that
there
right,
because
services
and
requests
are
in
there.
We
could
okay,
and
you
know
we
could
either
add
it
to
the
services
and
request
page.
B
C
The
problem
is
just
that
surveys
are
not
something
that
any
sig
does
frequently
and
you
know,
and
by
not
frequently
I
mean
like
they
do
it
once
every
two
years,
and
so
as
a
result
when
they
get
around
to
doing
a
new
one.
They
just
don't
remember
that
there
was
an
actual
community
process
for
this.
The
and.
B
C
B
C
C
B
F
Regarding
the
service,
like
the
few
things
that
I
observed,
you
know
to
get
a
good
survey
from
the
developer
circles,
let's
say
flutter
or
with
the
world
of
front
understand
they
put
up
for
a
period
of
time.
Let's
say
for
a
week
for
a
one
week
or
two
week
they
put
up
a
pop-up
in
the
actual
website.
If
you
are
doing
something
with
react,
then
they
want
to
connect
to
the
user
in
their
docs
page
or
whatever
they
react
under
react.devourreact.com.
F
Whatever
the
page
you
go,
there
will
be
a
power
coming
out
asking
you
to
do
a
survey,
so
that
kind
of
thing
we
can
also
use
in
terms
of
kubernetes
so
like
as
a
pop-up
like
whatever
the
kubernetes
page
you
go
like
kubernetes.com
or
under
kubernetes.you're,
going
over
there,
a
pop-up
like
for
that
one
session.
That's
a
single
talk,
not
like
not
an
import
like
every
page.
You
go
you
get
get,
so
we
need
to
like
have
a
cash
on
it
or
it's
a
country
garden.
F
So
for
the
first
visit
you
will
show
your
pop-up
so
that
the
user
they
want
to
know
it.
They
can
fill
it
up.
If
not,
they
can
take
it
off.
So
that
is
one
thing
they
can
do,
and
other
thing
is
like
in
terms
of
flutter
flat
edited
awesomely.
They
did
it
with
their
web
website
as
well
as
splatter
has
a
vs
code
plugin.
F
So
through
that
plugin
they
had
a
pop-up
coming
up
and
then
asked
people
to
just
to
read
it
out
just
by
putting
the
stars
or
whatever
this
needed
so
yeah
simply
like
that,
we
can
do
it
yeah.
We
can
get
ideas
from
other
communities
who
are
doing
it
superbly
and
we
can
try
to
implement
it
here
as
well.
So
yeah.
C
C
A
That
means,
if
people
aren't
using
that
path,
they
either
there
isn't
either
there's
an
opportunity
to
have
clear
ownership
so
that
we
say
everywhere
like
one
of
the
things
hey,
we
do
contributor
coms
and
also
that
surveys,
but
I
don't
know
if
we
want
to
centralize
that
ownership
or
if
we
like
people
feeling
like
that,
but
you
are
suggesting,
like
there's
a
requirement
to
get
a
consultation
in
order
to
send
a
survey
and
I'm
trying
to
figure
out
like
yeah
like
what
what
is
the
nuance
there
so
that
we
can
nail
the
messaging
and
then
we've
got
to
go
figure
out
like
how
do
we
get
a
message
to
permeate
the
contributor
community?
A
We
have
some
playbook
there
of
ctas
wherever
people
might
go
for
the
survey,
and
you
know
a
little
bit
of
a
bonus
on
us
of
like
every
six
months,
have
a
blog
post
about
why
surveys
are
so
cool.
It
sounds
kind
of
cheesy,
but,
like
you
could
write
that
in
your
sleep
and
it's
fascinating
people,
don't
know
how
good
of
a
tool
it
is.
But
what
do
you
think
about
that
josh
of
like
like?
What
do
you
want
it
to
be
owned
like?
A
C
Yeah
the
so
I
mean
I
feel
that
somebody
needs
to
come
to
if
it's
going
to
be
like
a
community
survey,
somebody
needs
to
come
to
contributor
comms
for
an
actual
editorial
review
of
the
survey
before
it
goes
out,
because,
particularly
this
last
thing,
with
the
student
survey,
where
you'd
literally
started
sending
it
out
on
sig
channels,.
A
C
Having
had
anyone
else,
look
at
it,
you
know
we
also
have
spammers
that
do
that,
and
and
and
given
the
contents
of
that
particular
survey,
it's
impossible
to
tell
the
difference
so
the
so.
To
that
degree,
I
think
it
actually,
you
know,
should
be
owned.
I
mean,
I
think,
part
of
the
messaging.
A
C
Monkey
account
which
looks
much
more
official
and
much
more
polished
than
than
google
forms
does
yeah,
and
you
know
we
can
get
it
broadcast
in
more
channels,
so
you
get
more
recipients
et
cetera,
but
then
follow
up
with.
Oh
also,
if
you
want
this
to
be
a
community
survey,
if
you
want
to
do
a
survey
on
behalf
of
the
kubernetes
community
or
you
know
to
the
whole
kubernetes
community,
it
has
to
go
through
contributor
columns,
because
you
know
we
do
have
requirements
to
prove
you're,
not
a
spammer.
C
The,
because
there
are
lots
of
you,
know.
Marketing
departments
for
individual
companies
who
would
love
to
use
official.
C
So
so
so
I
also
want
an
ownership
message.
I
also
want
to
say
you
know:
hey,
we
can
help
and
also,
if
we
don't
help,
you
don't
get
to
use
the
official
channels.
A
Right
so
another
thing
you
keep
using
the
word
official,
which
makes
me
happy
because
it
also
tells
me
another
like
marketing.
Product
marketing.
Playbook
tool
is
to
brand
it
like
to
literally
stamp
it
like
hey,
there's,
official
surveys,
and
if
you
don't
see
the
official
survey
stamp
on
it
signed
off
by
josh,
then
it's
not
actually
official.
Don't
don't
answer
it.
That's
that's
spam
like
we
can
make
it.
B
B
B
F
Yeah,
please
go
for
it
yeah
for
surveys
right.
So
when
you
have
you
guys
seen
these
certificates
that
also
show
the
domain
name
on
them.
So
if
we
had
official
kubernetes
surveys,
we
can
put
certificates
with
the
domain
names
on
them
and
we
can
get
these
certificates
they
put
like
you
know,
google,
I
mean
sorry
kubernetes
or
like
a
lot
of
banking
websites,
also
have
it.
F
B
Those
are
extended,
validation,
certificates,
it's
not
necessarily
something,
I
think
actually
chrome
is
going
to
deprecate.
That
feature.
To
be
honest
with
you
last,
I
heard
because
the
way
you
get
the
name
in
the
certificate
like
you
just
basically
buy
it
right
like
it's,
not
there's.
No,
like
the
official
process.
B
Is
you
have
to
verify
that
you're
with
the
company,
but
the
official
process
is
just
send
me
an
email
too,
so
we'll
need
to
check
into
that,
but
I
don't
necessarily
want
to
muck
with
ssl
certificates
to
get
surveys
out,
because,
if
we're
using
yeah.
C
C
F
Yeah
but
yeah
you're
right
about
domains,
also
you're
right,
I
mean
if
we
can
restrict
it
to
a
domain
like
kubernetes.
I
think
everyone
who's
going
to
be
signed
up
to
a
mailing
list
will
see
that
kubernetes
domain
in
the
address
bar,
so
anything
that
spam
should
not
technically
have
a
kubernetes
domain
right
on
any
spam.
C
A
Right
cool
all
right,
I
just
want
to
make
sure
we
heard
your
your
suggestion,
because
yeah
it
doesn't
sound
like
the
the
path
we're
going
to
take,
but
thank
you
for
thinking
through
it
and
sharing
it
yeah.
I
think.
F
These
bank
surveys
have
that
sorry
bank
websites
have
that
certificate
with
the
company.
A
A
A
D
D
Yeah
first,
who
exactly
does
the
request
need
to
go
through?
Contributor?
Comes
yes,
but
who
are
the
two
people
josh
and.
C
C
So
yeah,
so
it's
more
that
it
needs
to
go
through
contributor,
comps,
right,
yeah,.
A
A
C
C
B
B
F
F
D
Hey
sorry
for
the
interruption,
but
I
have
something
a
long
pending
issue
on
you
know
this
awards
and
all
those
things
for,
since
we
were
exploring
about
seo
like
improving
the
issue
of
the
kts.website
and
coming
up
with
new
contents.
So
I
found
this
one
like
I
put
it
in
the
docs.
G
D
About
documenting
the
awards
and
how
what
awards
are
presented
to
the
contributors?
So
since
the
contributor
summit
is
coming
up
and
the
work
is
going
on
on
that,
I
guess
we
don't
have
any
such
documentation
on
what
awards
are
getting
like
awarded
and
some
awards
are
given
in
coupon
also.
So
if
we
get
that
documented
under
the
kdp
site,
so
it
could
be
good.
D
I
think
I
talked
with
paris
regarding
this
this
week
I
actually
see
only
come
up
has
come
up
with
this
issue
and
it
has
been
like
you
know,
pending
since
a
long
time.
What
I
use
on
this.
D
A
A
I
just
kind
of
check
back
in
on
like
is
this
something
we
want
to
link
to
and
replicate
on
a
page
on
the
dot
dev
site?
I
also
don't
see
20
21
in
here,
so
it's
one
of
those
yeah
the
year
we
forgot
yeah,
I
it's
it's
going
to
be
a
challenging
one,
but
if
you
want
to
explore
it,
that's
where
I
would
start
by
asking
like
is
this
the
information
we
would
want
on
the
dev
site?
A
F
F
A
In
there
that
the
the
core,
what
we
do
is
we
focus
on
helping
other
contributors
communicate
to
contributors.
So
the
very
first
thing
we've
been
doing
is
like
we
have
a
lot
of
writers,
so
people
come
in
and
we
say
if
you're
willing
to
write,
we
can
set
you
up
with
an
assignment
to
go.
Talk
to
some
sig
leads
and
document
a
story
about
them
and
get
published.
A
Some
of
us
build
some
tools
on
the
side
to
support
that
mostly
rajula
think
thankfully,
and
some
people
that
are
following
in
his
footsteps,
but
I
I
think
that's
really
the
core
of
it
like
if
you're
asking
like.
What's
your
first
possible
deliverable
like
for
me,
showing
up
and
adding
your
opinion
like
you've
already
contributed
like
you've,
helped
a
lot
today.
Number
two
like
the
next
place
down.
Your
funnel
of
contribution
would
be
like.
A
Do
you
want
to
write,
and
if
so,
we
actually
have
a
plan
in
progress
for
kubernetes.dev
and
we
are
yeah
if
you're
interested
come
back.
Next
week
and
we'll
talk
through
that.
A
Bet
no
definitely
thank
you
all
right
for
to
kind
of
be
respectful
of
people's
time.
We
say
this
stops
10
minutes
before
the
hour
and
we're
five
of
so
there's
just
too
many
good
questions
and
really
wonderful
people.
So
thank
you
for
being
here
we'll
follow
up
in
github
issues
for
official
documentation
and
in
slack.
If
you
want
to
casually
catch
up
or
continue
conversations,
please
do
great
to
see
you
all.
Thank
you
so
much
and
have
a
wonderful
weekend.