►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220422
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220422
A
All
right,
hello
and
welcome
everyone
to
the
april
22nd
2022
2022-2022
edition
of
the
kubernetes
upstream
marketing
team
or
contributor
comms
subproject
of
sig
contrib
x.
We
are,
of
course,
a
part
of
the
open
source
kubernetes
project,
which
is
part
of
the
cncf,
which
is
part
of
the
linux
foundation.
So
we
do
have
a
code
of
contact
that
we
follow,
which
basically
says
be
respectful
to
your
fellow
attendees
and
speakers
basically
be
excellent
to
each
other.
A
A
I
already
posted
our
note
stock
in
the
in
the
chat.
I
think
just
about
everybody
was
here,
for
that.
Does
zoom
actually
keep
your
chat
even
when
people
aren't
there
yet
google
me
doesn't,
but
I
think
zoom
does
so.
I
think
everyone
should
have
the
notes-
and
I
guess
we'll
go
ahead
and
hop
into
it
and
we
usually
start
out
with
updates
and
big
wins
looks
like
avinish.
You
have
something.
B
Yeah
so
in
the
table
above
in
the
notes
itself,
there
was
an
action
item
on
me
which
we
had
to
have
a
new
role
of
community
meeting
from
comms
team.
But
while
having
a
conversation
with
laura
paris
actually
suggested,
suggested
us
to
have
a
new
comms
event
role
rather
than
having
a
community
meeting
for
a
role
so
yeah.
We
need
to
have
a
discussion
on
that.
A
A
A
Like
we'll
talk
about
kubecon
in
a
little
bit,
I've
got
the
spreadsheet
for
that.
Just
about
ready
to
go
so
that's
technically
an
event
thing
so
that
might
fall
under
this
roll,
but
we'll
have
to
decide
what
we
want
the
what
the
load
of
this
role
might
have
to
be
for
the
person
who
takes
it
on
and
of
course,
our
roles
are
pretty
flexible
too.
A
We
can
put
things
under
this
role,
but
if
the
person
who's
filling
that
role
doesn't
have
time
to
do
them
or
needs
help
with
them,
they
can
always
ask
for
help.
So
I
think
it's
a
good
idea
and
I
think
we
can
iteratively
build
this
over
time.
Starting
with
the
contributor
meeting
stuff
is
basically
my
opinion.
A
A
B
I
do
have
a
update
on
something
sure,
one
or
two
weeks
before
there
was
a
tag
on
comms
from
jo
from
paris
in
a
thread
where
josh
and
other
folks
were
discussing
about
lwkd,
so
they
wanted
new
contributors
to
come
and
contribute
there,
and
I
reached
out
to
josh
and
this
this
monday,
the
release
that
went
out.
I
had
some
part
which,
which
was
written.
It
had
some
part
which
was
written
by
me,
so
the
features
and
merges
merges.
I
wrote
the
those
part
so
yeah.
That's
an
update.
B
A
Last
week
in
kubernetes-
and
you
said
it
was
a
specifically
a
portion
about
the
release
yeah,
it
was
I'll
give
the
link
of
that
portion.
Yeah
that'd
be
great.
This
is
really
exciting
to
me,
because
josh
had
mentioned
that
he
wanted
help
with
last
week
last
week
in
kubernetes
lwkd,
whatever
the
d
stands
for
you
mentioned
that
he
wanted
help
with
that
newsletter
publication,
whatever
we
want
to
call
it
a
while
ago
and
had
reached
out
to
us
for
that
help,
but
then
nothing
really
ever
came
of
it.
A
We
didn't
get
more
information
about
how
we
could
help
or
what
he
wanted,
that
tradition
transition
to
look
like
if
he
wanted
us
to
take
over
more
responsibility
for
that.
So
this
is
exciting,
because
it's
progress
on
that
item
that
we
had
a
long
time
ago.
Not
I
mean
kind
of
a
long
time,
so
I'm
excited
to
see
someone
doing
a
little
bit
of
work
with
last
week
in
kubernetes
and
you
can
maybe
build
on
that
to
to
help
us
if
we
start
taking
on
more
of
that
work
as
well.
A
A
C
A
A
Oh,
you
can
talk
about
that
new
items.
I
think
I'll
actually
do
that.
I
think
I'll
move
our
campaigns
in
progress,
section
of
our
notes
to
below
new
items,
because
I
feel
like
we
tend
to-
I
at
least
tend
to
end
up
skipping
new
items,
because
I
get
distracted
by
campaigns
in
progress
which
is
big
these
days,
because
we
have
our
table
to
track
it,
which
I
love.
A
So
I'm
going
to
move
on
to
new
items.
I
can
always
come
back
to
updates
and
big
wins
if
anyone
thinks
of
anything,
because
there
was
a
new
item
in
the
slack
kind
of
hoping
chris
might
join
since
I've
seen
him
doing
some
things.
I
thought
I
would
like
to
ask
him
about
this,
but
I
might
ask
him
separately,
but
there
was
an
ask
in
slack
there's
a
blog
post
that
they
want
to
post
on
the
contributor
site
which
I'm
not
super
familiar
with.
A
A
A
A
And
cousin
to
unblock
I'll
add
that
into
our
action
items
table
after
we
go
through
them.
Are
there
any
other
new
items
that
people
want
to
talk
about?
I
think
there
were
a
couple
of
there
was
at
least
one
other
request.
I
think
that
came
in
on
contrib
x
this
week,
but
I
think
it
was
like
a
tweet
that
I
just
went
ahead
and
did
for
like
the
meet
our
contributors
or
something
like
that.
It's
like
meet
and
greet.
C
C
A
A
I
think
there
was
a
bit
of
that
in
that
workflow,
which
I
think
I've
said
before
is
why
we
try
to
help
shepherd
these
blog
posts
for
a
lot
of
folks
who
write
them.
They're
contributors,
who
may
not
have
worked
with
the
blog
before
and
they
might
be
very
intimidated
by
it.
So
having
someone
to
help
guide
them
can
be
helpful,
even
though
a
lot
of
us
have
not
actually
posted
blogs
there
before
either.
So
that
can
be
a
little
bit
tricky.
A
A
Oh,
there
was
one
update
actually
that
I'll
come
back
to
rajula
messaged
me
this
morning.
I
guess
and
said
that
he's
had
to
take
some
time
off
for
a
little
bit,
but
he
should
be
back
next
week,
so
we
will
get
to
his
action
item
in
a
little
bit.
I
think
a
couple
of
you
were
working
on
working
with
him
on
the
automation,
blog
blog
tweet,
automation
thing.
A
D
D
A
Yeah,
well,
we
appreciate
you
hanging
out
with
us,
even
though
you
can
only
hear
our
voices
and
I
think,
we're
okay
on
that
pr.
For
now
there
was
one
ask
I
think
that
came
in
where
someone
created
an
issue
and
then
they
pinged
us
on
slack,
because
they
couldn't
find
a
way
to
ping
us
in
github,
which
is
what
this
issue
will
fix.
A
D
D
D
A
So
sounds
good,
we'll
check
on
that
again
next
week
and
the
one
below
it
is
same
same
thing
really
so
we'll
leave
that
be,
and
this
is
the
ritual
thing
I
mean
she
said
that
you
asked
him
for
updates.
I
think
rajula's
offline
right
now
anyway,
so
I'm
guessing,
he
didn't
respond
to
you
and
also
wouldn't
have
responded
with
anything
beyond
what
he
said
already
I'm
guessing
is
that
right,
I'm
guessing
you
don't
have
anything.
A
It's
good
for
him
to
know
that
you're
looking
forward
to
doing
that
work
with
him.
So
has
it's
been
so
we'll
check
in
that
and
in
on
that
again
next
week
as
well,
I
kind
of
like
this
by
the
way,
but
we
have
some
items
in
our
table
that
live
for
multiple
weeks,
but
they
remind
us
to
keep
checking
on
them,
which
can
be
a
real
issue
if
you're,
not
tracking
things.
Well,
if
you
just
stop
checking
in
on
something,
then
it
doesn't
happen.
A
A
D
Sometimes
and
it
everything
works,
75
percent
of
the
time,
sometimes
we'll
like
leave
a
note
that
says
revisit
in
may,
but
it's
always
at
the
note
and
so
we'll
talk
about
it
and
then
in
my
this
is
actually
a
very
fresh
example.
In
my
mind,
where
we
have
the
discussion
and
then
we
come
to
the
end
and
we're
like
oh
yeah,
we
just
discussed
that
we're
not
gonna
bring
this
up
until
early
june
anyway.
D
A
A
Yeah
the
other
issue
here,
though,
is
that
the
person
indicated
that
it
may
not
make
sense
to
have
this
in
twitter
together.
So
we
may
still
need
to
look
into
other
solutions
like
github
actions
or
something
like
that.
That
was
what
he
recommended
too.
So
there's
got
to
be
a
solution
there.
I
just
it's
not
something
that
I
spend
time
trying
to
figure
out
yeah
in
the
may.
A
A
So
normally
we
would
hold
a
pr
in
order
to
effectively
do
this
scheduling
piece
honestly,
so
we
would
type
slash
hold
in
a
comment
post
that
and
then
the
bot
puts
a
hold
on
it,
so
it
won't
actually
be
merged
until
we
unhold
it,
even
if
it
has
everything
that
it
needs
to
be
able
to
go.
So
what
I
think
the
action
would
look
like
would
be
something
that
could
do
an
unholed
action
via
the
the
bot
at
a
specific
time,.
A
But
it
would
take
some
work
looking
into
would
that
solution
actually
work?
What
would
it
look
like?
All
of
that,
I
think
everyone's
pretty
busy
with
either
school
life,
stuff
or
other
stuff
right
now,
so
I
won't
assign
anyone
unless
someone
is
like
I'm
absolutely
going
to
spend
time
on
that
this
week,
but
we'll
come
back
to
that
next
week,
sound
like
good
plan.
A
A
B
So
it's
what
I
think
from
this
parts.
Past
experience
of
community
meeting.
There
are
four
only
four
ways
of
promoting
this
event:
either
four
or
three.
I
guess
why
I
tweet
kdev
and
a
blog
yeah.
So
three
apart
from
that,
I'm
not
able
to
figure
out
what
else
we
can
do
in
order
to
promote
or
in
order
to
help
the
community
meeting
team.
A
And
also
just
interfacing
with
whoever
is
running
the
community
meeting,
both
from
like
organizational
making
sure
the
meeting
gets
scheduled
standpoint
as
well
as
hosting
the
meeting
just
interfacing
with
those
people
is
a
chunk
of
responsibility,
as
well
as
owning
these
different
types
of
communications,
which
totally
makes
sense
for
our
group
tone.
So
I
think
that's
it
honestly.
A
Cool
so
you'll
want
to,
should
I
remove
that
yeah
so
we'll
want
to
just
record
in
our
repo,
like
the
person
who's
filling.
This
events,
role
with
regard
to
the
community
meeting
will
need
to
make
sure
that
a
tweet
goes
out
before
the
meeting
make
sure
that
a
tweet
goes
out
after
the
meeting,
something
like
that
sends
an
email
out
to
kdev
similar,
to
give
an
example,
maybe
and
helps
to
shepherd
through
a
blog
and
maybe
link
to
some
information
about
blog
processes.
A
A
C
A
I
don't
remember
any
of
the
stuff
that
I
learned
about
that
anymore.
So
it's
really
better.
If
we
don't
have
something
like
that,
because
it's
something
else
to
manage,
but
for
kdev
I
think
it's
fine
to
just
send
it
from
whatever
account
you
use
to
watch.
The
list
is
what
I've
experienced,
but
good
to
know
that
others
are
not
like
that.
A
Yeah
and,
like
I
said
usually
we'll
put
like
a
the
one
that
I
sent,
I
said
from
caslin
on
behalf
of
whatever
I
was
talking
about
group
on
behalf
of
the
community
meeting
organizers
or
oh,
I
did
contributor
summit.
So
it
was
like
on
behalf
of
the
contributor
summit
planning
committee
or
whatever
we
call
ourselves,
so
that's
a
tip
for
you
and
that
we
should
probably
put
into
the
responsibilities
that
we
put
on
github.
Maybe
I
should
help
you
with
that,
since
I'm
already
having
ideas
about
that.
A
A
A
Yeah,
actually
thinking
about
it,
if
they
haven't
scheduled
it
yet
or
like,
would
have
been
scheduling
it
around
now
they
might
not
have
been
able
to
schedule
it
because
the
cncf
is
so
underwater
with
kubecon
right
now
yeah,
so
it
might
not
get
scheduled
for
a
while.
So
we
might,
if
they
don't
get
it.
If
you
get
a
response
and
they
don't
have
anything
right
now,
we
should
just
say
check
in
on
this
in
june
yep,
because
it's
not
going
to
move
until
after
con.
A
A
I
dream
of
spending
time
to
figure
that
out
maybe
someday
I
will
or
someone
will
okay,
so
we'll
check
back
in
on
that
next
week
we
said:
we'd
discuss
it
again,
because
next
week
is
going
to
be
right
before
that
happens.
So
it'll
be
a
good
time
for
us
to
start
getting
that
together,
we
could
at
least
actually
go
ahead
and
create
that
vlog
and
put
a
hold
on
it
like
I
was
saying
and
then
unhold
it
at
the
time
if
we
want
to,
but
we
don't
need
to
do
that
right
this
minute.
A
So
we'll
talk
about
that
next
week,
review
repo
and
look
into
adding
a
description
of
what
roles
mean
to
us
and
new
roles
crystal
course
has
been
out.
Since
I
was
saying
I
would
help
you
out
agnesh
anyway.
I
should
work
on
this
as
well.
So
I
will
assign
this
to
me
signing
myself
a
lot
of
stuff.
It
might
not
all
get
done
this
week,
but
at
least
it's
an
attempt.
A
The
next
one
is
something
I
wanted
to
talk
about
and
a
few
people
have
already
dropped
off,
but
kubecon
eu
tweet
spreadsheet.
There
is
a
link
in
the
doc
or
in
our
notes,
to
the
doc
that
I
use
for
that.
It's
just
about
ready.
If
you
wanted
to
go
ahead
and
sign
up
for
some
things,
I
think
that's
okay,
but
the
one
thing
that
might
change
is,
I
haven't,
actually
checked
the
schedule
for
the
times
of
the
maintainer
track
blocks
or
how
many
there
are
in
each
day.
A
But
if
you
wanted
to
go
ahead
and
sign
up
for
things,
I
mainly
worked
on
getting
the
pre-event
tweet
information
down
like
we
need
to
have
a
tweet
that
kubeconius
beginning
registration
opens
up
on
saturday
or
sunday
may
15th,
and
a
notice
that
the
contributor
summit
is
happening
on
may
16th
and
then
information
about.
What's
going
on
on
the
16th,
with
some
reminders
about
what's
happening
on
the
17th.
A
So
a
tricky
thing,
with
the
tweets
that
we've
set
up
for
kubecon
that
I
was
thinking
about
as
I
was
creating
this
is.
We
need
to
do
some
reminders
as
well
as
some
like.
This
thing
is
happening
now,
so
I'm
trying
to
note
in
the
description
if
we
are
doing
a
reminder
that
this
thing's
going
to
be
happening
in
the
future
or
if
it's
a
this
thing
is
happening
now
cubecon
day,
zero.
Colo
events
probably
put
some
notes
in
about
that.
I'm
really
excited
that
lightning
talks
are
coming
back
obvious.
A
A
Yeah
there's
some
issue
with
the
way
that
we
hear
in
the
kubernetes
project
do
prs
because
of
the
way
that
we
have
to
fork
the
the
repo
and
then
bring
it
back
in
that
like
breaks
the
scheduling
capability
that
was
already
in
twitter
together.
Somehow
I
don't
remember
exactly
how
that
works,
but
you
might
figure
that
out
and
understand
it
better
than
the
rest
of
us
with
what
you're
doing
with
it.
A
A
A
So
the
basic
idea
of
these,
of
course,
is
like
if
you're
doing
a
maintainer
track
block
tweet
then
go
look
at
the
schedule
for
what's
in
that
maintainer
track
block
and
summarize
that
into
a
tweet.
However,
you
see
fit
and
you
don't
have
to
capture
everything,
but
whatever
you
think
is
interesting
in
that
block
and
people
might
want
to
know
about
and
we'll
tweet
about
it.
A
So
I
actually
put
these
in
manually
into
like
tweetdeck
or
twitter
and
schedule
them
before
the
event,
so
we'll
have
a
deadline
on
getting
all
of
these
drafted
like
a
week
or
a
few
days
before
I'll
have
to
leave
for
the
event,
because
we'll
need
to
get
all
of
that
done.
So
this
will
need
to
be
done
sometime
around
the
week
of
may
10th,
because
I
fly
out
that
weekend.
A
A
Or
anything
I
think
I'll
at
contributor,
comms
in
slack
once
I've
gotten
the
rest
of
the
details
sorted
out
for
this
sheet.
So
if
you
want
to
wait
until
then
to
put
yourself
in
as
an
owner,
that's
perfectly
fine
but,
like
I
said,
a
good
amount
of
this
is
pretty
nailed
down.
So
if
there's
anything
you're
like,
I
absolutely
want
to
do.
The
tweet
for
the
keynotes
on
thursday
you're
welcome
to
go
ahead
and
own.
That.
A
A
So
the
next
thing
is
there
was
a
request
for
a
review
of
a
new
katakota
that
harshita
had
made
nobody.
I
figured
that
nobody
would
really
have
time
last
week.
I
know
that
I
didn't
so
I
put
it
as
whoever
is
available
and
just
put
it
on
there.
But
does
anyone
want
to
review
this
catacota
this
coming
week?
A
A
A
A
A
A
A
A
Hopefully
I'll
just
remember
from
that,
and
I
want
to
make
it
another
section
in
the
table
that
I
need
to
reorganize
so
I'll-
try
to
do
that
after
this
meeting,
all
right,
so
that
was
that
the
one
other
thing
we
can
do
is
go
through
our
I
mean
there's
plenty
of
other
things
we
can
do,
but
another
thing
that
we
probably
should
do
more
often,
though
the
table
in
our
notes,
has
kind
of
taken
it
over
is
look
over
our
tasks
board.
So
I'll.
Look
over
that
real,
quick.
A
A
B
B
A
A
A
A
Possible,
though
the
nice
thing
about
having
them
in
the
table
is
that
I
know
that
we'll
go
over
the
table
every
single
day
if
we
had
far
out
items
in
the
task
board
that
doesn't
change
the
cadence,
that
we
need
to
look
at
it
with.
If
that
makes
sense
like
we
might
miss
them.
If
we
like
aren't
looking
at
the
task
board
regularly,
because
those
tricky
thing
with
like
far
out
items
is
that
you
need
to
remember
them
when
you
need
to
remember
them.
A
A
A
All
right,
so,
oh
yeah,
we
used
to
also
always
do
a
calendar
walk
to
see
what
was
going
on
in
the
community
to
see
if
there
was
more
stuff
that
we
needed
to
pick
up
like
like.
If
there
was
a
community
meeting
coming
up
and
we
didn't
have
anyone
that
was
engaging
with
the
community
meeting
stuff,
we
could
see
it
on
the
calendar
and
then
put
stuff
on
our
to-do
list.
Based
on
that,
we
have
enough
work
as
it
is
right
now,
so
I'm
going
to
continue
to
not
do
that,
but
also
organizational
note.
A
That
is
the
thing
that
we
used
to
do
and
could
always
bring
back
if
we
felt
that
we
needed
it,
I
feel
like
we
actually
hear
about
things
pretty
well
now.
People
know
that
our
group
exists,
so
they
ask
us
for
stuff
and
that's
great
tweet
draft
prs.
I
should
check
on
that
with,
with
chris
being
out
lately,
I've
been
trying
to
be
a
little
bit
better
about
checking
the
contributor
tweets
repo.
It
seemed
like
he
sent
out
a
tweet
this
week,
which
I
thought
was
interesting.
A
A
So
this
is
what
hina's
action
item
is
going
to
fix.
Hopefully
is
we
will
have
a
group
that
can
be
tagged
on
github,
so
we'll
get
notifications
about
these
things,
instead
of
having
to
actually
go
and
look
at
them,
which
clearly
we're
not
actually
doing,
and
I'm
going
to
leave
it
that
way
for
now,
because
it
is
8
53.