►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220506
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220506
A
Hello
and
welcome
to
the
friday
may
6th
edition
of
the
kubernetes,
contributor.coms
or
upstream
marketing
team
meeting.
We
are
a
project
of
sig
controbex,
which
is
part
of
the
kubernetes
project,
which
is
part
of
the
cncf,
which
is
part
of
the
linux
foundation,
which
means
that.
A
A
D
That's
right
and
I
believe
there
won't
be
a
march
one,
but
I
I
will
have
one
from
april.
A
And
it's
just
on
kates.dev.
B
Yes,
okay
yeah,
like
I
think
several
balls
got,
dropped
along
the
way,
but
I
think
we've
all
been
extra
busy
part
of
this
was
on
me
and
I've
been
out
as
well.
So
I
take.
A
B
A
A
F
D
Thank
you.
Yes,
the
124
was
released
on
tuesday,
so
the
cncf
release
webinar
is
scheduled
for
may
24..
So
this
is
a
little
bit
sooner
or
earlier
than
we
expected.
So
I
just
want
to
put
that
out
there
and
there's
a
link
out
to
the
webinar
site,
which
I
am
shocked
by.
A
A
On
the
ball
cool,
so
we
need
to
make
sure
that
we
tweet
about
that.
There's.
Also
a
few
other
release
related
tweets.
I
guess
I'll
go
ahead
and
mention
the
feature
blogs
are
going
to
be
coming
out
throughout
kubecon,
so
I
think
we
we
should
try
to
schedule
those
to
go
out
alongside
the
cube
connie.
You
tweets
if
we
can,
but
also
that's
kind
of
tricky,
because
I
don't
know
when,
in
the
day
the
blogs
will
be
out.
B
G
C
A
A
D
A
Find
that
out
mickey
did
tag
at
contributor
comms
in
a
message
in
sig
contribex,
which
I
guess
was
this
week,
where
he
listed
out
all
of
the
feature:
blogs
that
are
coming
up
and
their
prs.
So
we
have
all
of
the
pr's.
I
assume
we
can
find
the
previews
from
that
and
find
out
what
the
urls
will
be
from
that.
A
A
Okay,
we
will
come
back
to
that
and
chris
next
one
is
the
slack
channel
issue
that
you
opened,
which
yes,
a
little
bit
about
before
we
hopped
on,
but
yeah.
B
So
I
opened
an
issue
to
get
us
a
slack
channel
because
we've
gotten
to
that
point.
Where
we've
it's
like
five
people
in
a
dm
session
and
then
all
of
a
sudden,
we
need
to
add
like
three
more
kind
of
things.
So
a
slack
channel
makes
sense
in
the
actual
issue
that's
linked.
If
I
could
find
the
notes
which
are
right
here,
bob
brings
up
a
good
point.
It
should
probably
name
like
controvex
something
something,
but
then
I
realized
that,
like
recall,
we're
trying
to
align
everything
to
contributor
columns.
B
B
B
B
B
Yeah
so
anyways
yeah,
I
don't
know,
I
don't
know
how
I
feel
like
it
would
be.
The
only
thing
that
doesn't
explicitly
state
contributor
accounts
because,
like
I'm
gonna
change,
it's
contributor
counts
for
the
slack
handle
that
we
have
that
notifies
us.
I'm
gonna
up
that.
So
it
doesn't
say
upstream
marketing
anymore,
so
we'll
actually
say
contributor,
comms,.
B
Two
contributor
comms,
which
is
kind
of
that's
what
the
nexus
was
right
like
okay,
we
want
to
do
a
rename
all
right.
We
need
to
find
any
place
that
links
to
the
existing
marketing
team
repo,
which
I
have
a
tool.
It's
not
working.
I
think
I'm
doing
something
wrong,
I'll
figure
it
out,
but
the
tool
on
mac
is
called
integrity
and
it's
100
free
and
you
can
like
spider
websites.
If
you
have
other
tools
that
I
could
use,
I'm
more
than
happy
to
try
them.
B
I
also
need
to
just
like
maybe
do
a
curl
loop
searching
for
that
specific
phrase.
I
don't
know
I'll
figure
it
out,
don't
worry,
but
yeah
as
soon
as
we
update
the
github
repo,
we
need
to
go
in
and
find
those
those
links
and
have
pr's
ready
for
them.
Basically,
so
yeah,
it's
it's
a
little
bit
more
work,
but
I
don't
think
there's
many
places
where
we're
linked.
To
be
honest,
I
think
it's
literally
on
the
contrib
x
pages,
if
anywhere.
B
A
I
don't
think
we've
opened
one
already
any
other
updates.
Big
wins.
B
B
A
B
B
B
Yeah,
it
was
weird
the
dev
account,
so
google
groups
actually
do
some
email,
header
rewriting.
So
when
you
receive
them,
it
looks
like
it
was
like
intentionally
sent
from
you
so
like.
If
you
have
a
google
group
sending
email
to
another
google
group
like
I
do,
because
my
family
has
a
google
group
account
where
you
could
just
like
email
us
at
chrissworth.net
and
you'd
hit
myself
and
my
wife
and
then
when
max
needs,
email
he'll,
get
that
one
too.
B
So
when
you
do
google
group
to
google
group,
it
makes
it
look
like
it
came
from
your
google
group,
which
makes
it
even
worse,
because
you
really
don't
want
to
subscribe
from
your
own
thing
or
unsubscribe
I
mean
so
yeah.
Google
groups
do
say
weird
things
to
email.
B
There's,
I'm
sure,
there's
very
legitimate
reasons.
Why,
knowing
as
much
as
I
know
about
email,
probably
deliverability
being
the
number
one
issue
but
yeah.
B
A
Sounds
like
it.
That's
all.
I
know
about
email,
so
we'll
move
on
to
campaigns
in
progress
and
open
action
items.
Then
there
are
no
more
updates.
Big
wins.
A
Or
someone
else
put
it
in
for
him,
because
you
know
about
this,
but
anyway
atarva
very
kindly.
Thank
you.
Tarva.
Even
though
you're
not
here
very
kindly
created
an
issue
for
us
for
requesting
help
on
our
kubecon
eu
tweets
and
he
creates
created.
He
also
created
a
slack
thread
where
interested
folks
could.
Let
us
know
that
they're
interested
and
I've
been
pinging
those
folks
directly
to
get
them
all
of
the
instructions
that
they
need
to
help
us
out
with
our
kubecon
eu
tweets.
A
B
A
That's
awesome,
yay
and
I
initially
started
a
group
going
coming
back
to
the
the
slack
groups
conversation.
I
initially
started
a
group
with
the
few
folks
who
pinged
on
like
the
first
day
and
gave
them
the
information
and
then,
as
more
people
said
that
they
wanted
to
help.
I
realized
that
if
I
tried
to
add
them
to
the
slack
group,
it
would
create
a
new
slack
group,
so
I'd
have
to
redo
everything
for
everyone.
Yes,.
B
D
A
I
also
see
that
hina
is
like
in
our
notes,
but
not
here
got
a
few
people
today,
who
maybe
were
making
updates
in
here,
but
couldn't
couldn't
attend
today's
meeting
yep
go.
She
says
that
her
pr
is
waiting
for
review,
though
oh
yay,
so.
C
A
So
that's
been
getting
kind
of
bummed
for
a
while,
because
there
were
some
issues
with
getting
it
done
at
first
and
then
you
know
had
some
stuff
going
on,
but
now
we've
got
a
pr
for
it,
which
is
very
exciting
and
then,
once
that
team
is
in
place
on
github,
we
also
want
to
update
k
community
issue
template.
A
A
Cool,
oh
yeah.
We
were
talking
about
hina's
stuff
that
she's
needed
to
do
for
that,
and
we
were
mentioning
that
we
should
probably
create
a
tweet
about
squashing
commits
using
tide.
B
B
Contributors
or
whatever
it
was
designed
to
focus
on
that
slash
label
tied
thing
that
we
discovered
many
weeks
ago,
so
yeah.
D
And
there's
I
have
to
fight
in
slack
as
well.
I
think
it's
about
how
there's
multiple
people
contributing
to
a
pr.
If
tide
does
it,
it
loses
those
other
folks
and
only.
A
D
Pr
will
get
credit
for
it,
so
I
think
there's
some.
I
need
to
find
out
about
it,
but
there's.
D
B
B
D
A
A
I
guess
I'll.
I'm
thinking
about
things
that
I
should
do
on
at
the
contributor
summit.
I
should
probably
live
tweet
that
I
wonder
if
I
should
also
do
some
stuff
from
kate's
contributors,
while
I'm
doing
that
that
sounds
complicated.
G
G
G
A
A
A
B
A
A
A
A
I
promised
avinish
that
I
would
help
out
with
that,
and
I
still
haven't
imagine
that
kubecon's
coming
things
need
to
get
pushed,
but
I
know
avinesh
you're
in
the
middle
of
exams
as
well,
so
I
mean
there's
nothing.
B
A
Cool,
so
if
you
wanted
to
work
on
that,
you
could
like
I
said
I
was
gonna,
try
to
do
a
draft
for
you
and
I
very
much
apologize
that
I
haven't
managed
to
do
that.
But
I'll
try
to
do
it
cool
if
you
want
any
help
or
anything,
of
course,
ping
much
better
at
doing
work
when
I'm
pinged
about
it
honestly
as
much.
C
A
A
Yes,
anyway,
so
we'll
move
on
from
that.
Thank
you
very
much
avinesh
for
your
work
on
that
so
far,
and
for
what
you'll
be
doing
on
that
and
I'm
happy
to
help
out
with
that,
wherever
I
can
as
long
as
I
can
remember,
to
do
it
and
then
the
next
one
is
tweeting
about
feature
blogs.
A
I've
assigned
that
to
myself-
and
I
actually
did
something
on
it
totally
didn't
expect
that
I
had
something
on
here
that
I
made
progress
on
wow
here
we
go,
but
we
did
tweet
about
the
release
blog.
We
tweeted
the
docker
shim
history,
blog
yeah,
both
of
those
were
day
of
release,
and
then
there
was
another
blog
that
came
out
yesterday.
That
was
a
feature
blog
and
I
also
made
sure
to
tweet
about
that,
which
I
was
very
proud
of
myself,
for
because
I
was
just
manually
checking.
A
Long,
both
chris
and
I
look
at
something
that
makes
us
go.
Oh
my
gosh
at
the
same
moment.
So
I'm
working
on
that
if
anyone
wants
to
help
out
with
writing,
feature
blogs
like
we
said
we
do
have
the
schedule.
A
We
need
to
go
through
those
steps
to
figure
out
what
the
links
are
going
to
be
for
those
and
figure
out
what
the
timing
is
going
to
be
on
when
they're
going
to
be
out
so
that
we
can
figure
out
when
they
need
to
go,
probably
need
to
actually
schedule
them
instead
of
putting
them
into
github.
A
Moving
on
to
the
next
item,
caslin
and
chris
are
assigned
to
reviewing
the
repo.
I
assume
neither
of
us
have
made
progress
on
that.
This
week
we
had
some
other
stuff
that
we
got
done,
which
is
great,
so
yeah.
A
Clear
so
we'll
check
back
in
on
our
updating
our
repo
with
rolls
after
kubecon
sound,
like
good
plan.
A
A
Okay,
so
next
issue
is
our
kubecon
eu
tweet
spreadsheet,
there's
a
link
to
it.
There
also
a
link
to
the
issue
that
atarva
created,
which
we
talked
about
earlier.
We've
got
a
new
person
in
here.
Normally
we
have
some
time
at
the
beginning
for
new
folks,
but
we
didn't
have
anyone
new
in
at
the
time,
but
now
we've
got
rajesh.
Who
is
helping
out
with
the
kubecon
tweets
so
rajesh?
Would
you
like
to
introduce
yourself.
F
Yeah
definitely
thank
you
kathleen,
so
I
think
we
spoke
each
other
yesterday
so
regarding
this
so
yeah.
So
thank
you
for
well,
that's
so
myself
rajesh!
So
I'm
a
recent
or
a
newly
joined
contributor
in
the
sikh
contributor
experience
group
so
and
started
working
on
a
couple
of
the
tweet
tasks.
F
So
I
have
tagged
my
name
on
top
of
two
tweets
and
made
some
updates
and
also
updated
the
same
in
the
the
sheet
which
we
are
tracking
for
the
maintenance
tracks.
Basically
so
and
yeah.
I
got
some
help
from
the
adarwa
and
I
think
that
the
tweet
got
a
little
exceeded
the
character
limit
and
then
they
helped
me
to
trim
it
a
bit
and
then
yeah,
it's
all
good.
Now
so,
coming
to
my
basically,
I
am
located
in
europe,
netherlands.
F
So
I
work
for
a
telco
operator
or
customer
in
the
netherlands,
so
my
background
is
mostly
into
telco,
intra
architecting
deploymenting
and
designing
roles
so
looking
more
into
the
kubernetes
era
domain,
so
just
wanted
to
contribute
to
back
to
the
community
and
learn
from
the
community
and
yeah
going
with
the
journey.
Yeah
yeah.
A
C
A
And
the
kubecon
tweets,
though,
if
you'll
check
out
that
spreadsheet
you'll
see
that
most
of
them
are
actually
claimed,
and
we've
got
one
two:
three:
four:
five:
six:
seven:
eight
nine
ten
11
12
13
of
them
drafted
already
out
of
the
what
42
that
I
have
planned,
so
pretty
good
progress.
We
want
to
try
to
get
them
done
by
the
end
of
next
week,
at
least
because
I
need
to
schedule
them
before
I
leave
so
hopefully
get
them
done
before
friday.
Rajesh
has
at
least
one
that
I
need
to
review.
A
There's
several
in
here
that
I
need
to
review
and
I
haven't
been
able
to
get
it
done
this
week.
So
I'm
gonna
make
sure
that
I
make
time
for
that
today
and
also,
like
I
mentioned
earlier,
I'm
planning
to
get
all
the
folks
who
are
working
on
that
together
into
a
group.
We're
gonna
fix
that
once
we
have
a
channel,
but
I'll
probably
make
a
group
for
them
still
in
the
meantime
to
make
sure
that
everybody's
good
to
go
and
supporting
everything.
So.
A
But
also
you
don't
all
right,
so
that's
the
updates
on
cubecon
tweets.
If
anyone
wants
to
help
out
with
that
you're
most
welcome.
The
spreadsheet
is
right
there
if
you
need
any
help
reach
out.
A
So,
let's
move
on
to
the
next
issue.
Atarva
went
ahead
and
created
an
issue
for
the
kubecon
tweets,
so
I'm
gonna
get
rid
of
that
line.
A
Thank
you
very
much
to
atarpa,
even
though
he's
not
here
once
again,
the
next
one
is
chris
update,
github
repo
to
contributor
com's
name
working
on
that
actively
right
now,.
A
Pronunciar
is
not
here
at
the
moment.
He's
also
one
of
those
folks
who's
been
dealing
with
exams,
so
that
makes
sense,
but
once
he
gets
back
probably
after
kubecon,
he
said
on
hold
until
the
end
of
the
month,
but
he's
planning
to
create
a
new
sig,
spotlight
blog
post
review
for
those
who
are
not
familiar
with
it.
A
We,
since
our
inception
as
a
group
in
2020
we've,
had
this
ongoing
kind
of
background
project
where
we
try
to
regularly
not
regularly
at
all,
sometimes
create
blog
posts
where
we
interview
sig
chairs
about
their
sig
and
talk
about
what
those
things
do,
what
help
they
need
all
that
kind
of
stuff
and
put
that
into
a
blog
post.
So
that's
an
ongoing
open
action
item.
If
people
want
to
create
blog
posts
for
that,
they
are
welcome
to
you
should
reach
out
to
me
for
help
on
that.
A
A
B
A
But
once
the
answers
were
in
there,
I
could
just
copy
paste
them
into
the
blog
post,
which
is
most
of
what
I
did
so
makes
it
easy
anyway,
like
I
said,
if
you
want
to
help
with
that
ping
me
and
I'll
get
you
going
on
it,
but
we
probably
won't
do
anything
on
it
until
after
kubecon
so
cause.
I'm
not
gonna
have
that
much
space
to
help
until
then
at
least,
and
all
of
the
sig
chairs
are
gonna,
be
super
busy
until
after
kubecon.
C
A
Wonderful,
thank
you.
Avinish.
A
The
next
item
on
our
action
items
that
we're
viewing
is
katakana
review
for
harshita.
This
is
kind
of
low
priority
for
us
right
now
with
kubecon
coming,
so
it
hasn't
happened.
We
apologize
harshita
who's.
Not
here.
A
Hashita
is
one
of
the
mentors
from
from
the
mentoring
group.
I
think
who
created
a
katakota
for
kubernetes,
I
think
related
to
deb
abrada's
work
in
that
space
and
hasn't
been
on
for
a
bit
either.
I
think
he's
also
got
exams
anyway,
so
she
created
a
katakota
and
asked
us
if
we
would
review
it,
and
we
said
if
we
have
time
and
we
haven't
had
time.
So
it's
still
on
our
list.
A
C
A
A
B
The
event
page
for
it
yeah,
I
didn't
even
know
this
was
a
thing
why
batch
and
hpc
I
don't
know,
but
makes
sense.
I
guess.
B
A
A
A
B
B
Table
like
12
minutes
to
spare.
A
B
B
A
A
A
A
Very
nice,
very,
very
cool
issue,
walk
main
project
for
contributor
comms,
like
this
right
now
blog
posts
that
need
review.
That
is
something
you
should
look
at
more
regularly
check
repos
for
new
work.
A
I'm
not
gonna
do
those
right
this
second,
but
those
are
things
that
we
could
do
if
we
have
time,
but
I
want
to
see.
Does
anyone
have
any
questions
any
other
things
that
they
want
to
bring
up,
that
we
haven't
covered
in
our
session
today
so
far,.
A
Oh,
the
the
release
team
shadow
application
closes
today.
Yes,
I
should
do
another
tweet
on
that.