►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220325
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220325
A
Hello
and
welcome
everyone
to
the
contributor
comms
meeting
on
march
25th
2022
a
reminder.
We
are
part
of
the
kubernetes
project,
part
of
the
cncf
part
of
the
linux
foundation.
So
we
work
under
a
code
of
conduct
which
basically
says
be
respectful
of
your
fellow
participants
and
speakers
and
everyone
in
the
meeting
and
generally
be
excellent
to
each
other.
A
So
we
have,
as
I've
mentioned
a
couple
times
before
I
started,
recording
a
lovely
table
now
in
our
note
stock
for
putting
in
action
items
and
tracking
progress
on
action
items
so
go
ahead
and
start
putting
your
stuff
in
there
or
in
our
notes,
and
we
will
get
to
that.
We
have
a
special
guest
visiting
us
today,
who
needs
to
go
a
little
bit
early.
So
we'll
do
his
part
first,
so
mickey
from
the
release
team.
What's
up.
A
B
B
A
B
Awesome,
yes,
and
I've
already
gotten
a
lot
of
feedback
from
from
tim,
but
if
any
of
the
folks
on
this
call
wanted
to
also
take
a
spin
at
it-
and
you
know,
make
suggestions
for
what
to
change
I'll,
be
happy
to
intake
all
those
and
do
those
changes
on
monday
or
tuesday
next
week
or
or
earlier.
If
I
ended
up
having
time.
A
D
A
B
Actually,
yes,
yes,
there
is
a
doc
that
cat
has
been
working
on,
which
is
a
new
and
great.
You
may
know
if
this
is
already,
I
don't
know
been
discussed
with
folks,
but
there's
there's
a
what
to
do
now
with
kubernetes
1.24
to
make
sure
you
have
a
running
cluster.
So
I'm
not.
I
I
imagine
that
cat's
already
done
her
own
sort
of
promotion
process
for
this.
But
if
not,
I
wanted
to
get
that
on
your
radar.
A
B
C
A
B
C
C
B
C
Yeah
so
it
looks
like
it's
on
the
31st
and
I'm
totally
okay
publishing
two
things.
In
one
day,
I've
talked
to
to
the
other
blog
folks,
like
tim,
and
that's
all
right.
Typically,
we
do
prefer
one
blog
post
a
day
just
so
it
goes
up
the
the
blog
list,
all
right,
yeah,
so
because,
because
in
order
for
this
to
change
to
the
30th
or
or
29th,
we
would
have
to
change
the
file
name
as
well.
Oh.
C
B
B
B
B
B
A
A
D
A
D
C
A
Okay,
so
for
the
feature
blogs
and
the
webinar,
we
can
go
ahead
and
assign
people
to
those
action
items
later,
but
for
the
upcoming
two
blogs,
we
need
people
on
both
of
those
we
can
assign
them
to
debba
in
his
absence
since
he's
a
member
of
the
release
team
this
time
or
if
someone
else
wants
something
to
do.
Oh
no
deb
is
here
now
darn
it
we
were
talking
about
you.
A
E
A
A
A
F
C
A
C
A
A
I
reached
out
and
said:
hey.
We
have
this
blog
post
you'll.
Remember
that
we
worked
on
it
a
long
time
ago.
It
kind
of
fell
by
the
wayside
due
to
a
few
reasons.
We
apologize
for
that
and
we
want
to
know
if
you
want
to
continue
with
releasing
this
blog
post
and
she
said
that
she
was
not
really
comfortable
with
it
going
forward
right
now,
so
we
can
go
ahead
and
let
that
action
item
fall
off
of
our
list,
so
I'm
gonna
go
ahead
and
remove
that
from
our
tracking.
D
A
A
Oh
cool,
so
british
had
a
cool
update
here,
which
I
think
is
a
big
one.
There
was
a
bug
in
the
zoom
cloud
of
sig
testing,
petition,
noticed
it
and
opened
an
issue
which
is
now
fixed.
Wonderful,
thank
you,
british,
for
that
wonderful
contribution
to
the
kubernetes
project,
love
to
see
people
doing
stuff
in
other
parts
of
the
project
too.
E
D
D
The
other
small
piece
of
feedback
I
got
was
that
m
broberg
should
be
removed
because
they
stepped
away
from
the
community,
and
so
I
was
wondering
in
slack
he'll.
There
will
be
a
ping,
but
does
that
have
to
match?
So
if
it
doesn't
I'll
remove
from
the
list
remove
the
name
from
the
list,
but
then
also
this
is
a
heads
up
that
every
time
there
is
a
ping
in
slack,
they'll
get
an
alert
and
brokeberg
will
get
an
alert
well.
A
D
A
So
this
is
actually
a
good
point.
He
might
want
to
be
removed
from
the
slacklist
for
now
or
he
might
want
to
stay
on
it
because
I'm
guessing
it,
it's
not
unlikely
that
he'll.
He
might
eventually
come
back,
but
who
knows
how
long
that
will
be.
So.
This
is
a
good
note
and
we
should
add
an
action
item
to
check
with
matt
on
whether
he
wants
to
be
removed
from
the
contributor
comms
list.
I
think
for
now
don't
add
him
to
the
pr
as
recommended
and
we'll
see
about
the
list.
D
A
Furnace
here
so
you've
heard
the
issue
and
we'll
need
to
get
you
sorted
out
on
that
jason.
We
can
leave
for
now
because
he
hasn't
been
on
our
meetings
for
a
while.
So
I
wonder
if
we
should,
he
hasn't
like
explicitly
stepped
away
from
the
project
right
now,
just
he
hasn't
been
on
in
a
while.
So
I
don't
know
if
he
should
be
really
removed
from
the
contributor
comms
list
or
not,
so
it
might
be
another
good
one
to
check
it
on
and
for
matt.
I
could
check
in
with
him
if
you
want,
because
all.
D
D
A
A
Yeah,
I
think,
that's
great
well.
I
think
we
should
add
it
to
the
repo
as
well,
because
we
have
roll
descriptions
there.
So,
if
the,
if
we
have
a
meeting
host
role
and
someone
is
filling
that
role
for
the
week,
then
there
should
be
a
guide
on
github
granted.
No
one
will
probably
ever
look
at
it,
but
as
long
as
it's
there
that
should
say
that.
So
I
should
do
that.
D
And
that
also
takes
me
into
my
next
action
item
is
blocked
on
the
first
one.
So
no
updates
there,
because
it's
blind
what
was
that?
One
updating
the
k
community
issues
template
to
alert
the
team
when
a
new
marketing
issue
is
completed
or
created,
so
the
group
would
have
to
exist
first
or
I'm
assuming
the
group
would
have
to
exist.
First.
A
A
Awesome
so
prince.
Why
take
a
look
at
that
link
in
the
chat
and
I'll
put
it
in
the
notes
here
in
a
second
as
well?
There
are
some
requirements
for
joining
the
org,
including
enabling
two-factor
authentication
on
your
github
account
and
subscribing
to
the
mailing
list
and
stuff.
So
you
should
have
all
of
this
stuff.
Basically,
and
then
you
need
to
open
an
issue
against
the
kubernetes
org
repo
saying
that
you're
requesting
org
access.
A
A
A
D
D
A
F
A
A
F
A
A
A
A
And
then
the
issue
about
writing
a
blog
post
after
the
community
meetings.
Avinish
has
already
updated
us
that
that's
probably
going
to
be
a
little
bit
while
we
go
through
a
couple
of
iterations
of
the
community
meeting
the
next
one
is
like
I
don't
know
next
week
or
something
isn't
it
soon,
speaking
of
which
we
probably
need
to
do
tweets
for
that.
F
F
F
A
A
For
the
contributor
com
side,
often
when
we're
helping
to
guide
people
through
creating
blogs,
we'll
suggest
that
they
do
it
in
like
hack,
md
or
google
doc
first
and
do
a
first
round
of
review
with
us
if
they
want
us
as
reviewers,
so
that
when
it
goes
to
the
blogs
group-
and
you
actually
have
a
pr
for
it-
hopefully
reduce
the
amount
of
edits
that
you
actually
have
to
make
through
the
github
interface.
Since
that
can
be
a
bit
cumbersome.
A
C
Yeah
I
just
look
at.
I
do
do
some
reviews.
Typically,
you
also
merge
it
and
it
has
to
be
published
on
the
dev
site.
First,
then,
then,
it
goes
to
the
kubernetes.ios
websites
like
the
latest
one,
the
victor,
the
latest
kubernetes
blog
post
was
actually
initially
from
the
dev
site
and
it
is
the
meet
our
contributor
say:
pack,
the
australian,
new
zealand
region,
blog
post.
A
C
A
A
There's
all
sorts
of
folks
who
read
that,
whereas
dot
dev
is
meant
for
the
internal
kubernetes
contributor
audience
and
that
site
we're
trying
to
improve
the
slo,
not
slo
what
it's
8
a.m,
the
search
engine
optimization
the
seo
on
that
site,
so
having
the
the
blogs
linked
to
each
other,
well,
yeah,
having
the
blogs
linked
to
each
other
and
posted
on
both
helps
to
improve
the
seo
of
the
dev
site.
So
it's
much
appreciated
if
you're
working
on
a
blog-
and
it
seems
like
it
could
go
on
both.
A
A
A
A
Draft
a
blog
post,
okay,
so
this
is
talking
about
creating
a
blog
post.
So,
like
we
were
saying
earlier,
there
are
going
to
be
feature
blogs
coming
out
after
the
release.
That
sounds
like
around
the
timeline
for
this
one,
probably
because
they're
just
kind
of
throwing
around
the
idea
right
now
of
creating
a
blog
post
on
this
update
in
1.24,
we'll
probably
want
to
tweet
about
this
blog
when
it
gets
posted.
A
A
A
A
A
A
A
D
A
Thank
you
for
the
note.
What
else
do
I
have
it's?
A
good
idea
to
review.
Checking
with
matt
should
be
easy,
but
adding
a
note
to
the
repo
might
not
actually
happen
this
week,
but
it's
still
a
good
action
item
for
me
to
have
on
here
for
a
little
bit
later,
and
the
retweet
is
also
going
to
be
like
two
seconds
I'll
do
both
of
these
two
right
after
this
call,
so
it
should
be
good.
A
D
A
You're
welcome
to
just
not
show
up
you've.
Let
us
know
here
which
I
think
is
a
good
good
enough
notification,
which
I
mean
it's
not
like.
You
have
to
notify
us.
It's
it's
volunteer
work.
Sometimes
people
don't
show
up
and
that's
fine,
but
if
you
want
to
check
in
on
what
happened,
you
can
always
check
out
the
note
stock
or,
if
there's
anything
particular
to
you,
we'll,
try
to
make
sure
to
ping
you
and
otherwise
you
can
just
catch
up
the
following
week.