►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220429
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220429
A
We
are
a
part
of
sig
contrerbex,
which
is
part
of
the
kubernetes
project,
which
is
part
of
the
cncf,
which
is
part
of
the
linux
foundation,
which
means
that
we
have
a
code
of
conduct.
Basically,
it
says
to
be
respectful
of
your
fellow
presenters
and
attendees
and
generally
be
excellent
to
each
other.
A
C
A
Oh
yeah
that
wasn't
too
bad
last
time.
Actually
one
update,
because
I
was
just
deleting
those
notes
which
was
actually
came
in
handy.
I
had
an
action
item
last
week
that
I
don't
think
I
actually
put
into
the
table
so
I'll
update
it
now,
which
was
we
had
a
blog
post
for
the
contributor
blog
kates.dev,
that
we
were
asked
about
scheduling
and
how
to
unblock
that.
That
was
the
one
josh
was
asking
about,
and
he
said
that
he's
a
he's
an
owner
on
that.
A
A
A
A
A
D
A
Cool,
so
we'll
just
do
it
that
way,
all
right,
so
any
other
updates,
big
wins
or
new
items
before
we
move
into
the
spreadsheet.
A
Another
new
item
that
I
just
remembered:
rey
posted
a
link
in
the
contribex
channel
and
pinged
at
contributor.coms
for
nigel's
blog
post
from
the
community
meeting.
E
A
A
This
is
what
happens
when
I
don't.
C
C
Yeah,
let's
just
where's
where's
the
the
doc.
C
C
D
A
D
B
B
B
B
Feedback
yesterday
to
change
the
commit
message
so
after
about
attempting
it
turns
out
that
I
was
like
60
commit
messages
behind
so
then
I
gave
up
on
that
initiative
yeah.
I
can
relate.
B
Didn't
even
think
of
that
so,
but
now
I
did
push
a
new
one.
I
I
basically
was
a
little.
I
moved
two
words
that
were
the
same.
It
was
the
same
exact
context
in
the
description
I've
updated.
It
did
not.
I
looked
at
the
lines
so
hopefully
now
it's
pending
reviewers.
Oh
no,
a
change
requested.
C
E
C
B
Oh
okay,
well!
Okay,
I
think
this
requested
change
is
from
my
initial
yeah
yeah.
Okay,
oh
the
change
requested
is
the
change
that
I
updated.
My
commit
to
so
hopefully,
this
was
submitted
yesterday
feel
free
to
take
a
look
at
my
sad
attempts,
but
my
fingers
are
crossed
this
time.
B
C
E
B
B
I
was
like
wait
a
second.
This
isn't
what
I've
done
in
the
past,
and
so
but
it's
great,
I
apologize
for
the
delay,
but
I
am
learning
I
spent
like
four
hours
setting
everything
up
yesterday
properly
and
learning
that
I
was
62.
A
B
A
A
B
A
B
C
A
Cool,
so
I
added
that
contributor
tip
tweet
idea.
If
anyone
wants
to
claim
it,
hillary.
A
C
Yeah
so
buffer's
awesome
in
the
sense
that
you
can
like
connect
if
this
and
that
or
n8n
or
any
of
the
other
big,
like
you
know,
open
source
or
closed
source.
If
this
and
that
type
things,
so
you
can
literally
just
say
like
do
that:
kubernetes.dev
index.xml,
please
post
to
twitter
and
actually
say
post
to
buffer
and
it'll
schedule
it
for
you
and
based
on.
A
C
Preset
schedule
which
we'll
have
to
figure
out
at
some
point
how
many
tweets
do
we
want
to
go
out
a
day
if
we
do
want
them
to
go
out
multiple
times
a
day
but
yeah.
I
think,
I
think
getting
a
hold
of
buffer.
Getting
all
the
funding
for
buffer
and
bob's
chasing
after
that
and
then
actually
getting
it
set
up,
will
push
us
forward
very
quickly
and
then
we
can
have
teams
where
folks
can
log
in
and
actually
tweet
that
aren't,
like
owners
of
the
twitter
account
themselves.
C
Yeah
it
had
a
draft
tweet
process,
so
it
sounds.
C
A
C
A
A
A
C
C
A
C
Activities
and
friday
and
last
friday
and
everything
yeah,
I
think
all
the
governing
board
and
steering
committee
folks
are
busy.
E
C
A
C
A
C
B
A
C
A
A
Anyway,
our
next
thing
on
this
list
moving
on
avinash
and
also
me
world
description
for
the
community
meeting
events
interface
role.
I
said
during
our
last
meeting
that
I
would
help
like
scope
that
out,
because
I
had
some
ideas
on
it.
I
didn't
have
time
to
do
that
in
the
last
week.
Imagine
that,
but
we
can
leave
it
there
and
avinash
isn't
on
so
I
mean
I
think
that
would
still
be
helpful
for
me
to
do
so.
I'll
still
try
to
do
that
next
thing
tweets
about
feature
blogs.
A
We
already
mentioned
this
briefly,
because
we
had
the
request
about
tweeting
about
the
release.
There's
going
to
be
two
blogs
coming
out
on
may
3rd,
about
the
release
that
we'll
need
to
tweet
about
history
of
docker,
shim
blog
is
going
to
be
coming
out
that
day,
as
well
as
the
regular
release
blog.
A
So
those
will
both
serve
as
good
points
for
us
to
talk
about
the
the
new
release,
1.24
release.
So
that's
going
to
be
soon.
You
said:
that's
tuesday,.
C
A
C
C
C
Yeah
I'll
add
that
to
my
list
of
all
the
sorry,
my
language
is
awful.
Today,
I'm
sorry
y'all,
it's
friday,
I'm
exhausted.
C
It
will
add
those
things
to
that
queue
and
then
send
them
out
at
those
times
now.
For
me,
my
cues
are
huge
right,
like
I'm
sending
out
like
100
or
so
articles
a
week
with
kate's
contributors
right
like
it's,
it
needs
to
be
like
nine
o'clock
every
day.
You
know
noon
every
day
and
then,
like.
C
Yeah,
I
don't
know
we'll
see
it's
pretty
cool,
how
we
can
glue
all
the
bits
together
and
have
it
all
just
work
for
us
yeah.
For
example,
I
have
45
things
in
my
linkedin
queue
right
now
and
I'll
just
send
them
out
every
30
minutes
until
I'll.
You
know
I
say
whatever
the
drop
time
is
for
today.
C
C
C
But
yeah
like
with
the
with
the
the
paid
version
you
have
a
calendar,
you
have
analytics,
you
can,
you
know,
create
a
start
page.
If
you
wanted,
like
you,
know
the
little
link
tree
things
we
can
create
one
just
for
like
new
contributors
and
existing
contributors
be
very
cool
yeah.
They
got
a
lot
of
good
stuff.
That's
basically.
C
Once
you
set
it
up,
it's
kind
of
set
it
and
forget
it
the
way
you
know
I've
got
it
set
up
right
like
I
just
share
things
into
a
certain
place
and
then
they
get
scheduled
and
queued
accordingly
through
automation,
and
this
will
be
more
direct
than
that
because
we're
only
posting
to
twitter,
but
we
could
add
other
accounts
as
we
go
too
that's
entirely
possible
and
then
you
know
we
could
have
campaigns
set
up
around
specific
things
like
kubecon.
C
C
Is
analytics,
I
think
there.
C
There's
always
twitter
analytics,
but
that
requires
you
to
have
like
the
actual
account
login
but
yeah.
There's,
there's
a
there's.
A
analytics
tab
and
twitter
is
under
those
tabs.
So
it
gives
you
things
like
how
many
tweets
you
did,
how
many
retweets
you
got,
how
many
impressions
the
engagements
the
replies,
the
clicks,
the
link
likes,
the
new
followers,
the
whole
nine
yards.
It's
all
in
here
under
your
channel
overview,
is
pretty
great
and
then
you
can
grab
granularly
get
down
into
individual
posts.
E
C
C
I
would
never
get
enough
out
in
a
week,
but
anyways,
there's
all
kinds
of
stuff
just
get
added
all
the
time
and
right
now
it
works
with
facebook,
instagram,
twitter
and
linkedin.
A
Exciting
new
tools
have
thoughts
excited
for
us
to
do
that.
So
we
can
come
back
to
that
and
do
the
demo
at
the
end,
because
we.
A
We've
only
got
a
few
more
items
when
we
have
plenty
of
time
today.
I
think
so.
Let
me
run
through
these
last
few
items.
The
next
one
is
reviewing
the
repo
and
looking
into
our
current
world
descriptions
and
updating
all
that
stuff.
We
had
to
sign
that
to
you
chris.
I
reassigned
it
to
me
last
week
and
then
didn't
do
anything
with
it.
So
now
it's
assigned
to
both
of
us,
I'm
just
going
to
do
it
that
way,
whichever
one
of
us
takes
a
look
at
it
and.
C
Go
back
to
the
notes,
hang
on
which
thing
nope,
that's
attendees
com!
That's
not!
This
watch
is
chris
papers.
A
C
Good,
lord,
oh
I
have
it
always
at
the
front
nevermind,
which
thingamajiggy
the
review
repo
look
into,
adding
a
description
of
what
roles
mean
to
us
and
new
roles.
Yes,
I
think
a
social
media
coordinator,
like
I'm
just
going
to
add
notes
over
here.
A
C
C
B
B
B
A
Always
open
for
suggestions,
we'll
figure
it
out
and
move
on
to
the
next
thing,
keep
kind
of
you
tweet
spreadsheet.
That
is
ready
to
go.
C
Of
comms
doubled
because
of
last
week's
decision
to
remove,
masks
and
then
read,
masks
so
yeah
there's
a
lot
more
tweets
going
out.
There's
emails
going
out
already
that
have
gone
out.
I
mean
it's
it's
a
lot
like
I
was
originally
assigned
to
it
and
I
asked
caslin
to
take
over
because
of
death
in
the
family,
and
now
I'm
just
glad
tasman's
here
to
keep
my
head
on
straight.
C
Yeah,
we
need
more
people
here,
yep
right
always,
I
think
we
talked
I
mean
we
were
talking
in
the
contributor
experience
meeting
and
I
don't
want
to
belabor.
This
tell
me
to
shut
up
if
you
want
me
to,
but
like
the
term
marketing
might
be
hurting
us
a
little
right
like
we
are
the
marketing
council.
We
should
see
ourselves
as
technical
marketers
right
like
we
have
to
know
how
some
of
this
stuff
works,
to
talk
about
it
and
to
actually
send
out
some
of
this
stuff.
So
I.
C
Same
and
maybe
that's
just
I
don't
know
if
that
helps
us
at
all,
though
right
like
as
far
as
oh
it's
com,
I
don't
want
to
deal
with
that.
Oh
it's
marketing!
I
don't
want
to
deal
with
that,
but,
like
everyone
here
knows
we're
doing
stuff
in
github
right
like
there's
code,
at
least
for
now
for
twitter
stuff.
A
Maybe
we
should
actually
change
our
our
github
repo
name
to
contributor
comms.
I
think
it
is
marketing,
isn't
it
it's.
A
C
A
Item
to
our
table
update
repo
to
contributor
com's
name
menu,
chris
ping,
bob.
C
Be
just
like
I
just
do
it
one
day
like
once,
we
all
sign
off
on
it
kind
of
thing
sounds
good
to
me
yeah,
but
we
could
ask
bob
now
to
do
it,
but
bob
is
very
busy.
A
C
A
It,
the
upstream
marketing
contributor
communications,
team,
contributor
comms
for
short,
is
part
of
the
community
management,
subproject
and
contributors
experience
view
our
charter
to
learn
more
about
us.
We
should
probably
put
more
into
that
blurb
but
summary.
The
mission
of
the
kubernetes
upstream
marketing,
contributor
communications
team,
contributor
comms
for
short,
is
to
elevate
the
hard
work
being
done
throughout
the
kubernetes
community
by
its
community
contributors.
A
A
C
A
B
A
A
Yes,
it's
what
the
the
contributor
report
the
is
supposed
to
do
basically
and
we're
supposed
to
be
promoting
the
information.
From
that
I
mean
we
could
add
a
project
to
share
sig
charters.
I
mean
the
sig.
Spotlights
are
one
thing
that
we've
done
to
promote
what
cigs
do
and
what
they
need.
C
A
B
B
A
C
A
Thing
we
talked
about
that
hashida
came
in
one
day
and
asked
for
a
review
on
the
katakota
that
she
created,
which
none
of
us
have
done.
I
certainly
haven't
had
time
to.
Nobody
has
had
time
to.
C
A
A
Going
that's
the
problem.
Anything
else
is
low
priority,
so
I'm
gonna
move
on
beyond
that.
Again.
If
you
want
to,
please
do
it,
but
it's
lower
priority
right
now
early
may
get
a
tweet
out
to
promote
the
batch
focus.
Colo
I've
got
a
few
tweets
in
our
spreadsheet
about
the
the
colos.
I
should
add
one
specifically
about
batch,
though,
and
tweet
about
upcoming
release
webinar,
which
will
not
be
for
some
time.
A
A
E
A
B
A
A
The
instructions
page
of
the
spreadsheet-
it
tells
you
what
this
document
is
for
who
to
contact,
which
is
me
if
you
have
any
issues
the
goals
that
we
have
for
this
work,
what
not
to
do
what's
in
the
stock
and
what
to
do,
which
I'm
just
gonna
go
over
right
now,
as
well
as
a
additional
couple
of
tips
there.
So
here
is
the
main
page
that
we're
going
to
be
working
off
of
cube
county
u2022.
A
Titled
sections
are
sections
that
you
need
to
fill
in
if
they're,
not
bold,
that's
something
that
I
have
already
filled
in
or
will
be
filling
in,
so
you
don't
have
to
worry
about
it.
So
the
first
one,
of
course,
is
the
tweet
we'll
come
back
to
that.
The
description
tells
you
what
you
need
to
figure
out
to
put
into
that
tweet,
the
most
formulaic
ones
I'll
say:
are
the
maintainer
track
block
ones
so
I'll
go
through
creating
one
of
those.
A
A
So
most
of
these
are
going
to
be
before
the
actual
thing
that
you're
going
to
be
tweeting
about
they're,
going
to
go
out
unless
they're
a
happening
now
type
tweet,
which
will
go
out
as
the
thing
is
actually
happening,
but
those
can
kind
of
help
you
get
a
sense
for
okay.
So
I'm
writing
a
maintainer
track
block
tweet.
It's
gonna
go
out
30
minutes
before
that
set
of
sessions
that
kubecon
starts.
A
So
it's
a
reminder
for
people
to
sign
up
for
those
sessions
if
they
want
to
see
them
the
next
one
here
is
oops.
Sorry,
the
next
one
is
fits
in
a
tweet.
So
once
you've
written
your
tweet
sorry,
I
thought
I
could
get
in
between
those
two,
but
I
can't
so
once
you've
written
your
tweets.
You
want
to
make
sure
to
put
it
into
twitter
to
make
sure
that
it
fits
in
a
tweet.
We
are
not
going
to
be
using
the
github
tooling
for
this,
which
has
issues.
A
So
if
this
were
in
github,
I
wouldn't
be
able
to
have
this
link
here,
because
the
tweet
would
be
too
long,
because
the
github
automation
doesn't
account
for
the
way
that
twitter
condenses
links.
So
it
would
think
that
this
is
too
long
when
it
actually
is
not
so
make
sure
to
check
these
in
actual
twitter,
rather
than
just
checking
the
character
count.
A
If
you,
especially
if
you
want
to
put
in
a
link,
if
you
don't
have
a
link,
then
you
can
just
check
the
character
account,
but
anyway
so
make
sure
that
it
fits
in
a
tweet.
If
you
don't,
I
will
and
I'll
reword
it
if
it
doesn't,
then
here
is
where
you
sign
up
for
your
tweets.
Look
through
the
list
of
descriptions.
If
there's
something
you
would
really
like
to
write
the
tweet
about
just
sign
yourself
up
for
that
and
if
you
would
put
your
twitter
handle
there
by
your
name.
A
I
would
appreciate
that
because
I
would
like
to
send
a
thank
you
out
to
anyone
who
helps
with
this.
So
if
you
have
your
twitter
handle
there
I'll
send
out
a
tweet
sometime
before
the
event
during
the
event.
After
the
event,
maybe
a
couple
of
those
saying
thank
you
for
writing
the
tweets
and
telling
people
that
if
they
wanted
to
create
their
own
tweets,
they
can
go
to
our
github
repo
and
do
that.
A
Scheduled
is
another
thing
for
me
to
fill
out
it's
when
you've
created
your
draft
tweet
you're
all
done
with
your
work.
I
will
go
through
and
mark
each
of
these
as
scheduled,
as
I
put
them
into
our
scheduling
tools
for
twitter,
either
twitter
directly,
because
it
has
that
capability
now
or
tweetdeck,
either
way,
they'll
go
out
on
time,
and
this
pst
column
is
for
me
to
translate
all
of
the
cest
times
to
pacific
standard
time.
While
I
put
them
into
the
tools,
because
otherwise
I
will
get
super
confused.
C
A
Yeah,
so
I
just
convert
them
all
to
pacific
time
as
I
go
good
call,
so
any
questions
on
the
basic
flow
or
shall
I
do
one
for
you
to
get
a
better
sense
of
it.
A
I
will
do
one
real,
quick,
I'm
gonna
grab
this
one.
A
A
A
First
one
11
cest
on
may
18th
and
we're
going
to
be
talking
about
container
d
project,
update
and
deep
dive,
cryo
secure,
performant
and
boring
as
ever,
emissary,
ingress,
intro
and
deep
dive
fluent
bit
open,
metrics
and
open
telemetry,
all-in-one,
longhorn,
intro
and
deep
dive
and
volcano.
A
A
Maybe
this
isn't
a
good
example
to
do
then.
Maybe
I
should
have
done
one
of
the
other
ones,
but
I
could
also
just
do
this
one
this
way
so
another
example
from
kubecon
in
a
it's
time
for
the
next
maintainer
track
block.
A
So
here's
what
I
usually
do
is
I
take
the
top
level
things
that
we're
going
to
be
talking
about.
Like
I
mentioned
longhorn
cryo,
container
d,
I'll,
try
to
grab
the
twitter
accounts
for
those
and
add
them
and
say
these
are
the
things
that
we're
going
to
be
talking
about
in
the
maintainer
track
in
the
next
block
check
it
out.
Here's
the
schedule,
if
you
want
to
put
them
on
your
schedule
and
that's
kind
of
what
I
do
for
a
tweet.
A
Cool
yeah
and
that's
pretty
much
it
so
I'm
gonna
grab
this
first
one.
Actually,
since
I
grabbed
the
first
one
change
this
to
eu
2022.
C
A
I
do
like
1730
for
these.
You
know
the
the
more
reasonable
way
to
do
time,
probably
rather
than
10
pm.
I'm
gonna
try
to
do
most
things
that
way
I'll
remove
that
schedule,
link,
grab
the
schedule
link
and
I
don't
actually
want
all
the
maintainer
track
stuff
on
it.
So
I
guess
I'll
just
refresh
this
page
does
that
do
it
no.
C
A
D
A
A
So
I'll
put
that
in
sure,
why
not-
I
might
change
this
later,
but
I'll
just
do
it
this
way
for
now,
because
we're
at
the.
A
E
A
E
A
C
E
About
creating
a
github
issue
so
that
those
we
would
redirect
them
to
them
and.
E
E
So
whenever
they
they
show
interest,
then
we
would
we
would.
We
would
create
a
message
that
we
need
their
email
id
and
you
could
just
send
it.