►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220826
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220826
A
B
B
C
B
A
Also
frederico
had
a
blog
yeah.
He
had
his
sig
doc's
blog
come
out
this
week,
which
is
also
an
exciting
win,
but
he
created
his
first,
our
first
tweet
through
the
approval
process
on
buffer
for
that
vlog,
and
so
that
went
well.
It
was
nice
because
he
scheduled
it
to
go
out
and
then
the
post
about
1.26
coming
out
came
out
and
in
his
post
he
had
mentioned
that
1.26
was
like
coming
out
soon,
and
so
I
updated
that
to
say
that
it
was
out
now.
A
A
A
A
A
B
A
C
B
C
C
A
A
A
B
B
A
And
that
actually
reminds
me
of
one
other
thing
I
want
to
talk
about
today,
which
I
might
as
well
bring
up
now,
which
is
there
is
a
open
pr
from
avinesh
for
the
events,
role
and
josh
made
some
useful
comments
on
that.
One
of
the
things
he
asked
about
on
that
is
a
promotion
for
like
third
party
events
like
kubernetes
community
days
and
stuff
is
what
I
was
thinking.
C
A
We
want
to
support
those
kinds
of
events,
and,
if
so,
what
might
that
look
like
my
thought
is
that
our
intended
audience
is
the
contributor
community.
So
if
it's
an
event
that
is
focused
on
the
contributor
community,
like
kubernetes
community
day,
we
might
be
open
to
doing
tweets
about
those
like
if
they're
requested.
I
guess
I
don't
think
we
need
to
seek
them
out.
B
B
Yeah
so
for
context,
there
was
an
all
mail
panel
announced
via
twitter
at
kubernetes
community
day,
which
is,
if
you
go
and
look
at
the
page
that
we
were
just
talking
about
is
explicitly
prohibited.
So
yeah,
that's
like
big
no-no,
so
we
kind
of
have
to
make
sure
we
have
the
process
in
place
for
kubernetes
community
days
or
anything
like
kcds
in
general,
or
at
least
a
reference
to
that,
so
that
we
don't
do
something
wrong
in
the
process
of
tweeting
for
them.
A
A
A
B
B
B
A
B
A
C
C
C
C
A
C
A
C
A
C
C
C
C
A
Sounds
good
and
yeah
like
I
said
that
pr
was
about
fixing
a
a
typo
and
I
merged
that
josh
used
it
as
an
excuse
to
make
sure
that
I
knew
how
to
do
squashes,
because
I'd
never
actually
done
a
squash,
even
though
we've
talked
about
them
so
many
times
in
here.
So
I
actually
applied
the
squash
label
and
approved.
C
A
Cool
we'll
move
on
from
that
eventually
I'll,
remember
whatever
that
was
about
and
next
item.
I
think
we're
going
to
skip
this.
For
now
it
is
kind
of
on
hold
frederico.
Also
isn't
here.
I
don't
think,
and
it's
no
no
rush,
but
it
is
about
squash.
So
eventually
we'll
do
some
tweet
about
that
or
something
who
knows.
B
A
A
A
B
A
A
A
B
A
C
C
C
A
C
A
A
B
A
A
I
think,
for
now
I'll
I've
been
kind
of
acting
as
the
social
media
coordinator,
and
I
will
continue
to
do
so,
but
if
folks
are
interested
in
the
social
media
coordinator
role
take
a
look
at
the
role
handbook
that
exists,
and
let
me
know
if
you
want
to
go
through
the
shadowing
bits
on
that.
I
have
them
kind
of
laid
out
in
the
the
role
handbook
and
as
we
go
along,
we
can
always
update
these
and
modify
them,
so
they
are
not
static.
C
A
I
think
it's
nice
to
track
them
all
here,
though,
so
that
we
know
which
roles
we
actually
have.
Technically,
we
also
have
a
storyteller
role.
That's
still
there
and
there's
some
other
role.
That's
in
that
handbook,
you
should
probably
list
those
I'll
find
those
eventually
or
something
the
events
coordinator
role
pr
exists,
like
I
said,
josh
had
some
useful
comments
there.
A
A
He
added
another
comment
that
I
hadn't
seen,
which
is
if
this
person
is
going
to
be
the
contact
point
for
all
things.
Events,
I'd
really
like
to
see
an
aggressive
and
documented
rotation
schedule
for
the
role,
that's
the
sort
of
role
where
you
have
to
change
out
more
than
once
a
year,
so
that
people
don't
get
overwhelmed
by
doing
all
of
the
events.
That's
a
pretty
good
point
too.
I
guess
I'll
chat
with
avenish
about
that,
and
then
anyone
else
have
any
comments
on
that
agree
with
that.
A
A
Wow,
but
it
still
is
a
considerable
amount
of
work,
we're
still
kind
of
figuring
out
how
much
work
it
is.
So
we
might
not
have
to
incorporate
this
rotation
piece
in
right
now,
but
we
might
want
to
think
about
it
for
the
future
and
if
more
than
one
person
is
interested
in
helping
with
events,
then
of
course
we
can
do
that
kind
of
thing.
A
A
A
A
So
we'll
move
on
from
that
and,
like
we
said
on
the
external
events,
piece
of
that
you
might
want
to
work
with
kubernetes
community
days,
keep
in
mind
that
our
audience
is
the
contributor
community,
so
maybe
proactively.
Let
events
know
that
specifically
pertain
to
the
contributor
community,
and
otherwise,
if
we
get
requests,
we
could
handle
that.
C
Yeah
english
is
not
my
strong
suit
sweetheart
today,
but
I'm
back,
and
I
think
maybe
this
week
I'll
be
able
to
I'll
ping.
You
with
my
thoughts,
I'm
still
trying
to
figure
out
how
I
can
add
value
other
than
moving
things
and
writing
things
down
in
a
table.
So
it's
still
going
to
be.
May
I
think
this
one
might
be
very
generic
and
then
evolve
into
something
more
concrete,
but
at
least
I'll
start
drafting
it.
When
the
words
in
my
mind,
don't
the
words
in
my
mind
are
english.
A
C
C
A
C
A
Yeah
and
one
of
these
roles
at
least
needs
to
be
the
primary
owner
of
running
the
meeting,
and
I
haven't
decided
what
role
that
should
be
or
what
that
should
look
like.
Yet
it
might
be
this
project,
an
element
of
the
project
manager
role.
It
might
be
this
approver
leader,
very
rough
concept
that
we've
been
discussing,
because
we
need
someone
who
has
like
ultimate
power
over
our
repos
and
helps
to
run
the
meeting
and
stuff.
So
that's
kind
of
what
I
was
thinking
about
for
the
leader
role.
A
A
C
A
C
A
Cool-
and
I
suggested
last
time
that
frederico
maybe
take
ownership
of
figuring
out
what
the
blog
lead
role
should
be,
because
he's
been
doing
a
great
job
of
writing
blogs
and
writing
that
new
page.
That's
going
to
be
going
into
our
repo
about
how
to
write
blogs,
I
think
it
it's
probably
already
in.
Actually
I
need
to
find
that
pr-
which
I
don't
have
a
link
to
here.
A
I
think
I
have
it
later
in
the
table,
but
he
wrote
a
page
about
how
you
decide
what
goes
to
kate's.dev
versus
what
goes
to
kubernetes.io
and
some
other
blogging
guidelines
which
tim
bannister
reviewed
and
so
like
it's
a
nice
set
of
guidelines,
regardless
of
what
we're
doing
so.
I
was
like
frederico
that
sounds
like
you're.
A
blogging
lead
so
I'll
work
with
him
on
that
further.
A
Cool
we're
making
progress
on
them.
I'm
very
excited
about
that
contributor,
coms,
name
change.
We
did
get
some
of
these.
Finally,
in
this
week
there
was
one
pr
that
needed
a
rebase
and
that
rebase
got
completed
this
week
and
then
I
pinged
josh
about
making
sure
that
all
of
the
ones
that
he
could
merge
were
merged.
Then
he
was
like
some
of
the
others
are
not
ones
that
I'm
the
owner
of
you're,
the
owner
of
them,
and
you
need
to
do
them,
and
then
I
probably
didn't
do
that
as
you
can
see
here.
C
C
B
A
A
C
B
C
A
A
A
B
B
C
B
A
C
A
A
B
A
A
A
C
C
C
A
B
A
C
A
B
A
C
A
I
did,
but
I
don't
think
I
said
anything
about
it,
but
anyway,
like
I
was
saying
earlier,
frederico
also
created
a
new
file
in
our
repo
in
marketing
team,
which
will
someday
be
contributor,
comms,
storytelling
resources,
blog
guidelines.
He
updated
the
blog
guidelines
with
a
whole
bunch
of
really
nice
stuff
that
he
learned
since
he
was
writing
blog
posts.
A
A
A
C
B
B
C
B
C
A
Yeah
cool
we've
got
five
minutes
left,
so
I'm
gonna
keep
going
through
these.
As
of
our
last
meeting,
there
were
six
tweets
left
that
we
should
do
about
the
annual
report.
Stuff
frederico
had
been
killing
it
with
going
through
those,
but
there
are
still
a
few
more
of
those
left.
I
haven't
seen
any
more
come
through,
so
sounds
like
there's
still
a
little
bit
more
work.
We
could
do
on
that,
but
we've
made
good
progress.
A
C
A
A
I
said
twice
already
that
someone
has
reviewed
the
blog
from
our
group,
so
there's
no
active
stuff
needed,
but
anyway,
two
minutes
keep
track
of
sig
doc's
blog
sub
project
process
changes,
omniscient
ray
are
not
here
at
the
moment.
Granted
we
do
have
those
updates
to
our
own
repo
about
the
blogging
process,
so
that'll
be
nice
and
it's
also
related
because
tim
bannister
was
involved
in
the
reviews
for
that.
A
A
Security
coms
guidelines
yeah:
this
is
a
concept
that
I'd
like
to
get
done
eventually,
but
is
not
a
high
priority
or
not
urgent.
Avinesh
said
that
he
was
interested
in
working
on
it.
Anybody
else
wants
to
work
on
it
as
well.
You
are
welcome.
I
can
explain
to
you
what
the
concept
was.
Basically,
we
want
to
work
with
sig
security
to
write
out
some
specific
blogging
and
communications
guidelines
for
security
items,
because
they're
such
sensitive
communications,
so
we'd
like
to
work
with
sig
security
to
do
some
guidelines
on
that.