►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220204
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220204
A
Hello
and
welcome
everyone
to
the
upstream
marketing
meeting
or
contributor
comms,
whatever
people
like
to
call
us
for
friday
february
4th,
I
think
it's
still
february
4th
in
other
parts
of
the
world
as
well.
A
Yes,
in
2022,
remember
that
this
is
a
meeting
of
the
kubernetes
project,
which
is
part
of
the
cncf,
and
we
do
have
a
code
of
conduct
which
essentially
says
to
respect
one
another
and
be
excellent
to
each
other,
so
please
be
respectful
and
we
have
some
nice
stuff
on
our
schedule
to
cover
today.
A
A
And
that's
about
to
start
going
through
our
our
tasks
for
today.
A
All
right,
let's
start
with
updates
and
big
wins.
Then
I
assume
this
was
you
type
of
prada?
Do
you
want
to
talk
about
it.
C
C
So
me
and
mother
would
be
mentoring
that
so
yeah
anyone
wants
to
apply
if
you
could
go
ahead
and
apply,
will
have
a
three
four
months
of
long
run
and
will
be
reaching
out
to
six
to
ask
their
requirements
of
what
a
documentary,
what
part
of
their
documentation
they
want
to
create
scenario
on
and
also
we
have
identified
five
or
six
part
of
documentation
that
needs
to
get
into
caterpillar
scenario.
So
we'll
be
working
on
that.
I
have
added
few
issues
today,
so
yeah
feel
free
to
go
through
them.
D
A
A
Looks
like
the
sig
multi-cluster
article
has
been
put
up,
so
we
used
to
have
this
umbrella
issue
where
this
was
a
type
of
evergreen
content
that
we
would
try
to
regularly
create,
which
is
blog
posts
that
profile
the
various
special
interest
groups
within
the
kubernetes
project.
A
So
we've
got
a
spotlight
on
sig
multi-cluster,
that's
up
on
the
blog
now,
if
you're
interested
in
learning
about
what
sig
multi-cluster
does
and
where
they
might
need
help,
definitely
check
out
that
blog
post
also
an
update
from
last
week
that
I
will
bring
up
again.
A
Deb
abrada
has
taken
on
a
shadowing
role
with
me,
so
we
were
discussing
some
things
yesterday
on
that
and
the
sig
profiling
evergreen
content
is
something
that
we
brought
up
and
that
we're
going
to
try
to
create
some
better
guidance
around
so
that
folks
can
do
more
of
those
blog
posts.
A
B
B
We
tried
it,
you
know
because,
like
we
did
it,
I
recorded
it.
I
had
the
transcript,
I
had
the
whole
nine
yards
and
it
was
just
really
hard
to
make
it
into
like
a
narrative
format
if
that
makes
sense.
So
if
we're
going
to
do
video,
we
publish
the
video
if
we're
going
to
do
text,
let's
ask
the
questions
via
email
or
something
that's
probably
the
right
mechanisms
for
us.
I
think.
A
E
Yeah
one
question:
I
did
see
a
pr
on
k
websites.
I
know
the
blog
is
up
on
k
on
the
k
desk,
yeah.
B
So,
for
seo
reasons
we
have
a
umbrella
issue
for
seo.
Right
now
of
the
kubernetes.dev
site,
everybody
I
talk
to
doesn't
know
that
kubernetes.dev
exists
and
I'm
not
the
only
person
that
noticed
this.
So
the
idea
is
for
blogs
that
make
sense
to
publish
to
kubernetes.io
but
are
focused
on
contributors
specifically
like
this
group's
purview,
we'll
publish
them
on
kubernetes.dev
and
then
later
on,
publish
them
on
kubernetes.io
both
on
blogs,
but
the
canonical
link
will
point
back
to
the
dev
site
to
help
with
seo
this
way.
B
The
dev
site
gets
some
love.
The
content
gets
out
there
in
multiple
forms,
there's
no
penalty
for
cross-posting
stuff.
As
long
as
you
indicate
that
you
have
cross-posted
it
and
that
canonical
url
will
do
that.
So
it's
part
of
that
seo
strategy
we'll
see
how
it
pans
out,
but
basically
the
more
articles
and
blogs
we
can
put
out
the
better
because
they'll
get
re-published
on
the
I
o
site,
which
gets
tons
of
traffic
cool.
Thank
you.
No
problem.
A
Cool,
so
I
guess
we'll
move
on
to
campaigns
in
progress.
I
feel
like
there's
something
else
I
was
going
to
mention
about
the
seo
thing,
but
I
mean
it
was
pretty
well
covered.
So
it's
fine
that
I
forgot
that
so
campaign's
in
progress.
We
have
an
editorial
board
and
a
general
subproject
issue
board
that
devrata-
and
I
were
talking
about
yesterday-
do
you
want
to
cover
what
we
were
talking
about
there.
C
Yeah,
so
what
we
were
discussing
yesterday
is
we
have
two
boards.
One
is
the
editorial.
One
is
for
the
copy
editing
of
blogs
like
which
we
had
regular
regularly
before,
but
now
I
see
like
you
know
there
are
like
per
month.
C
We
hardly
get
one
or
two
blogs,
so
we
were
talking
of
if
we
could
merge
this
to,
like
you,
know,
sub
project
e
support
and
educated
report
into
one
and
every
meeting
we
discuss
on
that
like
what
are
the
progress
on
the
board
so
that
you
know
anyone
who
hops
into
seek
contributes.
Let's
say
interested
in
upstream
marketing
would
know
what
is
going
on
in
the
sick
as
the
boards
are
not
maintained
at
present
and
because
of
two
boards.
C
A
A
So
let
us
know
in
the
comments-
I
guess,
if
you
have
any
opinions
on
that
personally,
I
am
very
much
in
favor
of
merging
them
if
you're
not
familiar
with
the
boards
by
the
way
they're
like
kanban
boards,
if
you've
ever
seen
that
before
basically
a
way
for
us
to
track
our
issues
and
what
status
they're
in.
If.
A
B
A
F
F
F
B
A
A
Perfect
so
another
thing
that
we
talked
about
last
week
was
the
need
for
some
kind
of
active
list
of
evergreen
tweet
content.
We
talked
about
how
umbrella
issues
are
not
really
sufficient
because
we
used
to
have
a
lot
of
umbrella
issues
for
things,
but
there
are
a
lot
of
problems
with
those
specifically
that
apparently
the
person
who
posted
the
issue
can
update
it.
I
didn't
know
that,
but
but
anyone
else
who
like
does
something
for
the
umbrella
issue
and
then
they'll
comment
that
they
did
it.
But
then
the
issue
itself
doesn't
update.
A
A
So
I
went
ahead
and
gave
it
a
shot.
I
created
a
draft
similar
to
what
I
created
for
the
kubecon
tweet
storm
that
we
worked
on
last
time.
So
it
has
instructions
for
how
to
basically
navigate
this
doc,
how
to
create
your
tweets
and
how
to
make
sure
that
it
gets
tweeted
and
it
has
separate
tabs
for
separate
topics
which
I'm
actually
going
to
add
one
to
dev
stats.
A
A
Lovely-
and
we
had
a
well
we'll
get
to
that
in
a
minute
getting
ahead
of
myself.
Let
me
add
that
at
the
bottom.
C
B
F
A
Thank
you
for
adding
the
the
link
about
the
easy
cla
too.
By
the
way,
I
will
add
that
additional
information
into
our
notes
and
spreadsheets.
E
F
B
Interesting,
it's.
F
One
other
tweet
that
should
go
out
today.
I
don't
know
if
this
is
on
the
schedule
is
today
is
enhancements.
Freeze,.
F
Until
the
next
cycle,
1800
like
it's,
it's
for
this
release
so
like
there's,
no
other
features
that
are
going
to
this
release.
F
Correct
it
is
at
6
p.m.
Pacific
time
today.
A
The
like,
what
did
we
call
it.
A
A
B
A
B
Yeah,
absolutely
there's
gonna
be
not
like
a
significant
shift,
because
it's
not
like
I've
done.
A
ton
of
work
but
like
aws
will
benefit
from
me.
Fixing
that
for
sure.
H
B
We
talked
about
that
right.
Yeah
9
a.m,
eastern,
so
I've
set
my
just
to
let
you
know
caslin.
I
set
my
reminder
to
go.
Look
it
for
open
tweets
for
9am
as
well.
I
probably
need
to
back
it
up
like
855.
Given
this
morning,
I
found
like
a
missing
space.
You
know
that
kind
of
thing
so
yeah
I
will
fix
that
make
a
little
bit
earlier.
H
F
A
B
A
A
Unfortunate
not
a
huge
deal
but
noted
all
right.
Let's
start
I've
been
avoiding
moving
through
each
of
these
tasks,
but
let's
go
ahead
and
do
it.
Avinish
is
avenish
on.
A
I
To
laura
about
the
country
team
meet
the
community
meeting
and
I
think
she's
quite
busy
and
she's
not.
She
has
not
yet
responded
to
my
dm,
so
maybe
chris,
if
you
can
help
me
out
with
it.
I
Oh
technical
problem,
the
community
meeting,
so
in
the
previous
meet
we
discussed
yeah.
F
F
F
B
B
A
A
I
don't
know
we
used
to
call
it
military
time
because
we're
ridiculous
in
america.
Apologies.
A
But
I
should
use
it
more
regardless
anyway,
so
that's.
A
Anyway,
time
zones,
aside
next
thing
was
assigned
to
anash
sinash
here
doesn't
look
like
it.
That
issue
was
how
sig
kate's
infra
are
asking
asking
about
how
labels
work
and
tweeting
about
how
labels
work.
I
assume
this
was
kate's,
proud
bot.
Labels
have
to
go
back
and
look
at
our
notes
because
there's
the
whole
issue
where
they're
not
in
every
repo.
A
I
know
that
there's
some
guidance
for
that
on
the
prowbots
site.
We
were
wondering
if
there
was
like
a
guide
or
something
that
we
should
tweet
out
to
contributors
is.
F
A
F
It
should
only
be
in
kk
and
k
website
right
now,
plus.
A
F
Oh,
actually,
it
triage
accepted
should
exist
in
all
repos.
It's
just
the
needs.
Triage
one
is
okay,
it
looks
to
be.
A
Yes,
we
were
discussing
it
last
time
because
we
were
talking
about
this
idea
of
creating
a
series
of
tweets
about
prabot
commands
that
are
useful.
That
contributors
might
not
know
about,
and
triage
accepted
was
one
of
the
first
ones
that
we
were
discussing
and
we
went
ahead
and
sent
out
a
tweet
on
that.
One.
F
But
both
meets
triage
and
triage
accepted
do
exist
in
contributive
tweets.
It's
just
the
automation
to
automatically
add
like
needs
triage,
and
all
that
is
not
active
in
contributor
tweets.
A
A
A
Okay,
so
I
noted
that
triage
accepted
his
in
all
repos,
which
we
already
tweeted
about
so
that's
good
needs.
Triage
is
also
in
all
repos,
but
we
don't
have
automation
for
it,
which
supposedly
exists
in
another
post,
cool
stuff.
A
D
B
D
B
A
A
Did
I
everyone
on
the
internet
can
view?
Let
me
change
it
to
everyone
on
the
internet.
Can
edit
sorry.
F
Set
it
invite
the
community
contributor
experience
group
to
have
edit
rights.
A
A
E
A
A
H
Wonderful,
yes,
I
have
a
like
similar
issue.
I
faced
like
when
I
drafted
my
tweet
and
just
to
check
like
I'm
within
the
world
limit.
I
tried
to
put
it
in
my
twitter
draft
and
it
showed
that
it's
okay,
it's
within
the
limit,
but
when
I
tried
to
bring
it
in
the
issue
which,
on
the
board
sure
that
it
exceeded
the
world,
I
don't
know
what
happened
really.
Did
you.
A
Have
a
link
in
it
that'll
do
it,
because
the
link
will
do
it,
because
twitter
automatically
shortens
links
when
you
put
it
into
twitter.com,
but
our
bot
doesn't
know
how
to
do
that.
So
if
you
try
to
put
a
link
into
your
tweet
that
you're
doing
through
our
github
automation,
it
may
fail
due
to
length,
if
there's
a
link
in
it
when
it
wouldn't
on
the
website.
A
A
C
And
just
an
update
the
to
creative
migration
to
it
had
to
be
gone
way
before
in
january,
but
it's
now
february
4.
So
I
guess
this
has
to
be
done
immediately
or
so.
A
C
No
because,
in
the
umbrella
issue
from
the
paris
I
saw
that
the
tweet
was
supposed
to
go
in
january,
three
january,
8th
or
9th,
but
it's
pro
now
a
month
passed.
A
You
think
I
figured
it
would
be
worth
mentioning,
because
I
know
that
I
don't
pay
that
much
attention
to
the
mailing
list
as
one
of
those
people
who
does
spend
more
time
on
twitter.
So
there
could
be
other
folks
like
that
who
would
still
benefit
from
being.
B
B
B
A
Lovely,
thank
you
so
much
for
helping
us
do
the
best
we
can
with
our
missed
sla
here.
C
D
D
D
A
B
B
No
you're
not.
I
am
also
ridiculous.
We
did
briefly
touch
on
the
fact
that
there's
several
other
github
actions
out
there
now
for
twitter,
where
there
wasn't
when
we
first
started
this,
so
it
might
be
worth
looking
at
something
different,
but.
B
A
Even
though
we
love
to
chat
cool
once
again,
thank
you,
tarpa,
mentoring,
subgroup.
We
were
saying
that
this
would
be
another
great
topic
for
us
to
have
evergreen
content
on
and.
C
Last
last
we
discussed,
I
went
into
the
mentoring
meeting
and
what
josh
suggested
is
they
need
help
with
making
people
aware
about
like
when
the
mentorship
program
starts
like
lfx
or
gsoc,
or
something
because
it's
always
the
last
date
people
choose
to
and
many
people
are
not
aware
about
it
happening.
So
there
are
places
where
we
need
folks
to
contribute
so
yeah.
That's
that's
the
only
thing
like
we
need
to
send
comms
regarding
when
the
cycle
starts
or
something
like.
C
A
A
C
A
A
A
Exactly
so,
there's
the
tweet,
though
from
contributorcoms.
If
you
want
to
retweet
it
now
next
one
moving
on,
we
also
want
to
start
communicating
to
contributors
what
they
need
to
contribute
to
the
annual
report.
Atarva.
We
had
asked
you
to
check
in
with
paris
on
this
any
updates.
C
A
F
A
B
B
A
C
A
number:
yes,
I
think
the
validate
command
is
broken.
C
I
think
rajula
is
there
in
the
meeting
like.
G
A
So
the
actions
on
updating
the
contributor
comms
list,
in
slack
anyone
who
wants
to
be
added
should
do
their
own
pr.
Do
we
want
someone
from
the
group
to
own
submitting
the
new
pr's
opinions.
B
Yeah
where's
where's,
my
sign
hang
on
here
we
go.
A
A
Thank
you
so
much
rajula.
You
are
a
fountain
of
knowledge,
which
is
much
appreciated,
alrighty
and
thank
you
tarva
for
bringing
that
up
and
for
checking
in
with
paris
on
that.
So
we
will
get
that
sorted
out.
The
contributor
calms
be
sorted
out
and
then,
if
you
would
like
to
own
pinging
the
site
six,
you
can
do
that
or,
if
you'd
like
to
pass
it
off,
do
you
have
a
preference.
A
Okay,
I'm
noting
that
you
own
both
and
both
checking
in
and
the
message
awesome
so
we'll
get
you
added
to
that
list
so
that
you
can
make
that
announcement.
Thank
you
so
much
and
the
next
one
we
already
talked
about
this
brada
myself
and
we
figured
dewan,
would
also
have
some
input
here.
We
want
to
make
sure
to
actually
get
that
sig
profile
guide
done,
which
is
in
our
board
as
something
that
me
and
matt
were
supposed
to
do,
which
we
did
a
few
things
on
and
then
didn't
really
finish.
A
So
we'll
work
on
getting
guidance
up
for
anyone
who
would
like
to
create
a
blog
post,
profiling,
a
special
interest
group,
and
even
without
that,
if
you
would
like
to
do
that,
just
let
us
know
we
would
love
to
help
guide
you
through
that
there's
already
example
questions
that
you
can
use
to
chat
with
sig
co-chairs
about
what
their
sig
is
doing
and
that's
kind
of
the
core
of
it.
A
So
that's
in
our
contributor
comms
repo
within
the
community
section
of
kubernetes
k,
community
standard
disk,
yeah
or
cool
yeah
right,
there's
more
links
in
the
chat
that
I'm
not
going
to
read
right
now,
because
I
don't
have
brain
capacity
for
it.
I
think
the
rest
of
this
stuff.
We
already
went
over
yep.
This
is
all
stuff
that
I've
added
while
we've
been
talking,
so
I'm
not
going
to
go
over
it
again.
Unless
people
have
questions
or
comments.
A
The
next
thing
that
came
from
my
conversation
with
this
week
was
that
abrada
suggested
that
maybe
we
should
talk
with
the
release
team
about
their
shadow
application
process,
because
there's
so
many
people
who
apply
to
become
the
shadows
and
then
are
rejected,
but
they
might
be
great
members
of
this
group
if
we
would
like
to
reach
out
to
them
and
let
them
know
that
we
exist.
A
F
A
F
I
would
still
be
careful
with
that.
I
think
the
there
is
a
standard
message
that
gets
sent
out
to
everyone,
so
maybe
add
something
the
standard
message
that
goes
out
like
if
you're
not
accepted
for
the
lease
team.
F
F
Outside
of
more
applicants
honestly
like
it
is
a
big
time,
commitment
and
yeah
like
unless
you
can
really
be
there.
It's
like
it's
neat
ray
can
probably
speak
a
bit
more
to
some
of
this.
That's.
E
Some
of
the
processes,
like
bob
said,
will
likely
change
as
well
in
terms
of
the
release
team
selection
process
and
how
that
goes
about,
don't
want
to
say
anything
until
it's
actually
concrete,
but
we
do
get
a
lot
of
questions.
We
not
a
lot.
We
get.
We
always
get
a
few
questions
like
what
else
you
know
I
didn't
get
selected.
How
can
I?
E
How
can
I
contribute,
and
we
we
kind
of
generally
have
a,
I
guess,
a
standard
or
more
of
a
standard
like
you
know,
you
could
contribute
to
to
various
sig
secret
dims
actually
has
his.
He
has
his
own
github
file
for
a
list
of
like
ways
he
could
contribute.
So
that's
something
that
we
could.
We
could
add,
link
to
don't
know
where
the
proper
place
for
it
to
be,
but
there
is
a
release.
E
Team
selection,
markdown
file,
that
talks
about
the
selection
process,
but
we
don't
have
anything
like
you
know.
If
you're
not
selected,
it
could
contribute
in
this
way,
yeah
just
trying
to
figure
out
where,
where
the
best
place
for
that.
E
I
think
a
resource
in
the
dev
center
blog
post
would
be
great.
I
could
help
work
on
that
for
sure.
B
E
So
yeah
and
I
kind
of
have
my
standard
slack
message
on
how
to
contribute
and
where
to
contribute
and
where
to
go.
So
I
could
add
that
as
well
yeah,
I
think
if
we
even
have
don't
know
if
we
have
it
on
kdap
just
so
I
know
we
have
the
the
releases
page
on
kdev,
but
don't
know
if
you
have
like
we
don't
really
broadcast
the
release
team
selection
anywhere,
except
for
github,
don't
know
if
we
should.
E
E
E
A
B
Fair
enough
yeah
I
got
I
mean
I
can
help
you,
I
just
I'm
crazy
busy
at
work
and
I'm
also
going
to
be
writing
a
book.
This
year.
It
looks
like
so
yeah
exciting.
B
A
A
Thank
you
so
much
ray
for
your
insights
and
for
weighing
in
on
that
I
think,
there's
something
nice
that
we
can
do
for
people
there
yeah
exciting
tweet
for
eccla.
We
already
discussed
that
I
think
yeah.
So
I
also
added
that
to
our
spreadsheet
of
evergreen
tweet
information,
the
the
change
that's
coming
well,
that
has
happened
with
ecclesia.
A
B
B
Bye
bob,
I
can
do
it
on
kind
of
like
a
cadence
if
need
be,
if
they're
good,
to
go.
C
Yeah,
you
just
need
to
approve
an
lg
team.
I
guess
bob
and
my
tweets
are
very
short
and
I
guess
the
validate
is
broken.
So
we
have
to
change
the
street.
That's
also
good
to
go.
D
C
C
B
B
A
B
H
All
right
just
a
small
question-
I
put
it
in
the
chat,
I
guess
it
was
skip
like
do
you
have
the
credentials
for
the
kids
concepts
account
twitter
only.
A
H
I
was
thinking
like
maybe
we
had
to
try
the
accepted
that
went
out
earlier.
Maybe
we
should
retweet
it
with
the
new
content
about
the
needs
trial
thing
which
one
I
like
it.
The
needs
price
thing
that
we
discussed
today
like
it's,
it's
triage,
it's
triage,
yeah,.
A
Sorry,
thanks
ray,
we
had
to
leave
what
we
tweeted
out
before
was
triage
accepted,
and
this
is
a
separate
label
that
needs
triage.
So
I
think
we
could
do
a
separate
tweet
for
it
granted
that
our
twitter
automation
does
not
have
the
capability
to
create
threads
itself,
we
would
have
to
have
someone
with
the
keys
to
the
castle
going
every
single
time.
We
wanted
to
say
something
about
prowbot
if
we
wanted
to
put
it
into
a
thread,
so
I
think
we
just
give
up
on
the
thread
idea
and
just
tweet
yeah
yeah.
C
C
C
A
C
A
So
rajula
talked
with
the
folks
who
said
that
they
were
interested
and
if
it
seems
like,
there's
plenty
there,
which
there
definitely
is,
but
if
it
seems
like
there's
enough
there
that
we
could
mentor
someone
to
do
it,
yeah,
let
us
know,
and
let's
try
to
set
it
up
as
a
gsoc
linux
foundation.
Mentorship
thing,
cuz
that'd
be
super
cool.
A
G
A
So
we
are
five
minutes
over
we're
pretty
much
through
ever
all
of
the
core
things.
There's
a
few
more
links
here,
of
course,
for
working
session.
Obviously
don't
have
time
for
working
session
today,
but
if
you
want
to
go
through
those
links,
of
course,
you're
always
welcome,
and
we
have
this
new
spreadsheet
now
that
we're
still
figuring
out
and
trying
out
for
evergreen
tweet
information
we're
trying
to
make
it
so
that
there
will
be
things
for
people
to
claim
and
go
in
there
and
just
do
a
tweet.