►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20220902
Description
[SIG ContribEx] Weekly Marketing Meeting for 20220902
A
A
So
for
updates
and
big
wins
today.
I
went
ahead
and
put
in
a
couple
of
updates
about
the
projects
I'm
acting
as
comms
lead
for
for
the
contributor
Summit
for
kubecon
North
America.
The
initial
announcement
went
out
last
week.
I
also
did
an
update
to
that
announcement
this
week
about
the
swag
deadline
and
with
some
details
on
the
schedule.
A
So
if
you
want
to
make
sure
that
you
get
the
size
that
you
want,
then
go
ahead
and
register
by
then
I
also
put
together
a
high
level
task
list
for
all
of
the
folks
who
are
shadowing
me
for
this
role
and
it'll
also
help
with
tracking
all
of
the
action
items
that
we'll
be
doing
as
part
of
this
activity
and
a
few
of
the
the
shadows
for
this
are
in
this
group.
So
I
figured.
That
was
a
good
thing
to
share
the
other
project.
A
A
B
Yeah
so
I
have
a
castle
so
regarding
the
scheduling,
the
blog
post,
so
that's
that
was
a
feature
for
a
long
time.
It
was
a
bug
in
contributors.
Side
got
fixed,
so
Tim
was
quite
helpful
and
yeah
it.
The
logic
was
pretty
much
like
we
do
in
kubernetes,
IO
or
the
main
website,
and
so
now
we
can
also
schedule
blog
post,
even
with
the
provided
date.
So
it's
still
working.
A
We
have
for
some
context
for
everyone:
we've
been
wanting
for
a
while
to
increase
visibility,
especially
the
SEO
of
the
search
engine,
optimization
of
the
contributor
site,
and
one
part
of
that
is
putting
blogs
on
it
more
frequently
so
I'm
trying
to
use
the
contributor
Summit
as
an
excuse
to
do
that
yeah
all
right.
Any
other
updates,
big
wins
that
folks
want
to
talk
about
before
we
go
into
the
the
table
or
any
new
items.
C
Yeah
so
I
wrote
a
good
job
to
do
the
knowledge
transfer
thing,
but
there
was
a
bug
with
Return
of
the
watch,
so
I
actually
wanted
to
demo
it
so
I
guess
I'm
blocked
because
of
that,
and
also
not
all
of
the
folks
responded.
So
I'll
give
more
time.
I
will
schedule
one
next
week
or
later
yeah,
but
I
also
found
out
more
stuff
that
we
can
work
on
so
I
start
creating
issues.
C
A
A
A
C
C
A
A
A
Hina
has
some
work
going
on
for
that
for
now,
like
I
said,
and
always
honestly,
it's
always
good
to
let
us
know
in
the
slack
Channel.
If
you
want
us
to
see
something
because
I
know
that's
a
lot
easier
for
me
to
track.
At
least
that
item
is
kind
of
on
hold
Auto
generating
blog
tweets.
This
is
all
done.
I
wanted
to
post
something
in
the
contribbeck's
main
Channel
about
that,
but
I
haven't
yet
so
I
guess
I
could
keep
that
around.
For
now,.
A
Though
I
think
it's
kind
of
obvious
at
this
point,
so
I
might
just
delete
that,
but
I'll
leave
it
for
now
review
repo
look
into
adding
descriptions
of
new
roles,
so
we've
been
doing
this
Avinash.
Do
you
have
any
updates
on
the
events
coordinator
role,
the
social
media
coordinator
role
is
in
our
repo.
B
Yeah
I
think
you
can.
You
focus,
can
hear
me
right.
Yes,
okay,
I
I
did
see
some
updates
on
the
issue.
There
was
some
conversation
between
you
and
Josh
related
to
the
shadowing
or
something
so
I'm,
not
wrong.
I
didn't
miss
the
previous
video,
so
maybe
if
we
can
just
let
me
know
what
all
discussion
was
going
on.
Oh.
A
A
A
We'll
talk
about
that
more
later-
and
you
know
it's
not
here.
The
concept
of
the
project
manager
role
is
also
very
rough,
so
no
need
to
update
there
approver
leader
role.
This
role
is
also
still
very
rough.
It's
got
a
bunch
of
high-level
Concepts
about
what
it
could
be,
there's
still
more
stuff
that
we
kind
of
have
to
figure
out
there
contributor
sites
Imran.
Have
you
done
anything
very.
A
B
Just
started
the
macron
I
just
yeah,
okay,
nice,
so
he
took
your
templated
social
yeah
even
contributor
work,
the
role
which
already
in
GitHub
so
started,
working
on
it
I
have
yeah
I
need
to
contact
Chris
on
it.
I
need
some
help
on
it,
so
I
need
to
contact
him.
I
know
the
pieces,
support
that
Tech
requirement,
but
actually
which
direction
we
need
to
find
help
or
how?
What
are
the
themes
we
need
to?
B
You
know
we
need
the
colleague
or
the
the
contributor
to
help
on
us
to
work
with
us
that
we
need
to
get
the
theme
so
I'll
I'll
increase,
probably
next
week
this
week,
I
didn't
have
time,
but
I
just
started
with
the
template.
Maybe
next
week,
once
I'm
done
with
her.
Maybe
a
rough
draft
I'll
contact
him
awesome.
A
Thanks
thanks
that
sounds
like
it's
moving
along.
Well,
then,
you
know
where
to
find
us
whenever
you
need
help.
Of
course,
as
we've
said,
Chris
is
the
most
familiar
with
the
space.
But
if
you
have
questions,
you
can
always
ask
any
of
us
and
we'll
try
our
best
and
there's
also,
this
concept
of
the
tech
lead
role,
which
might
be
a
con.
A
combination
of
roles
that
have
Tech
leadership,
including
the
contributor
site
role
and
regula
I,
think
the
knowledge
sharing
documentation
that
you're
working
up
might
be
a
component
of
the
tech
lead
role.
A
C
A
A
D
A
A
B
A
A
They
would
make
sure
that
review
and
other
blog
tasks
that
are
on
our
radar
are
getting
completed.
Working
with
folks
who
are
writing
blogs,
so
Frederico
has
been
really
on
top
of
doing
a
lot
of
blog
work
lately
and
he's
also
writing
a
guide,
an
updated
guide
for
our
group
on
how
we
create
blogs,
so
I
thought
he
would
be
a
good
fit
for
that.
So
I
still
need
to
chat
with
him
more
about
what
he
thinks
about
that
concept
and
that's
our
lead
concepts
for
now.
A
A
A
A
There
we
go
cool
yeah
if
you
all
want
to
take
a
look
at
those
you're.
Welcome,
of
course,
I
think
the
first
couple
of
these
had
an
issue
that
we
talked
about
last
time.
Yeah
it
has
a
hold
on.
It.
Has
some
checks
not
successful?
We
looked
into
those
a
little
bit
last
time,
so
they
require
a
little
bit
more
jigging,
but
the
other
two
I
just
need
to
put
an
a
proof
on
I
think
so
there
are
two
that
have
issues
and
two
that
are
okay.
A
A
Sig
architecture
Frederico
had
sent
out
a
interview
for
them.
I,
don't
think
he's
on
today,
yeah
so
I
assume,
that's
still
in
the
same
spot.
I
know
that
he
had
been
having
some
trouble
getting
them
to
respond
or
kind
of
getting
that
rolling.
That's
totally
common
totally
normal
for
this
project,
and
then
he
also
wanted
to
do
an
onsig
security
but
hasn't
been
able
to
get
that
one
rolling
either.
So
this,
like
I,
said,
is
pretty
common.
A
A
D
A
D
Actually,
the
one
of
the
sick
docs
co-chair,
we
love
new
contributors,
feel
free
to
reach
out
on
the
Sig
docs
slack
Channel
as
well.
We
also
host
a
monthly
new
contributor
meeting,
slash
workshop
and
that's
actually
coming
up
in
the
first
Wednesday
of
the
month.
So
if
you
join
the
stick,
Docs
Google
group
you'll
get
the
invite
for
that,
and
that
is
very
APAC
friendly
time
zone.
D
Meeting,
ISD
friendly
time
zone
meeting
as
well
so
just
join
the
Sig
Docs
Google
group
and
you'll
get
the
invites
for
that.
First,
Wednesday
of
the
month,
I
forgot
what
time
it
was,
and
also
just
reach
out
to
Doc,
slash
Channel
and
if
you're
looking
for
starting
two
ways
to
to
look
at
the
good
first
issues,
which
is
a
label
on
our
issues.
So
if
go
k,
slash
websites,
good
issues,
filter
out
for
a
good
first
good
first
issue,
then
that's
a
good
way
to
start.
B
A
And
to
give
some
context
on
this
group,
we
do
contributor
Communications,
so
as
you've
seen,
we
do
things
like
writing
blog
posts.
We
have
a
Twitter
account
case
contributors
where
we
post
news
that's
happening
in
the
contributor
Community.
Sometimes
we
help
with
events
that
need
Communications,
such
as
helping
with
emails
to
go
out
to
the
main
contributor
mailing
lists,
all
of
that
kind
of
stuff,
so
we're
closely
related
to
docs
but
kind
of
tangential.
B
A
A
B
A
A
So
if
you
did
want
to
review
his
updates
to
the
blogging
instructions
which
I'll
probably
be
sharing
with
my
Shadows
for
for
the
contributor
Summit
since
we're
trying
to
work
in
a
bunch
of
blogs,
you
can
find
those
here.
I
think
I
posted
that
in
one
of
our
chats
and
I
probably
need
to
do
that
again.
I
was
going
to
find
that
you
know
what
I'm
gonna
do
it
now,
foreign.
A
A
A
It's
kind
of
a
separate
update,
but
there
is
a
GitHub
issue
about
the
katakoto
deprecation
which
has
led
to
this
whole
thing.
There
hasn't
really
been
anything
in
particular
for
us
to
do
on
it,
but
we
like
to
keep
up
with
it,
because
it's
an
interesting
thing,
that's
going
on.
So
are
there
any
updates
from
that
Ray
or
abiness,
or
anyone
else,
who's
involved?
No.
D
A
D
A
The
annual
report
tweets
Frederico,
did
a
great
job
there
for
a
while
getting
all
of
those
tweets
together.
There
were
six
left
as
of
the
19th
and
I.
Don't
think
that's
changed
if
you
wanted
to
help
with
these
I'll
leave
this
on
here
for
now,
certainly
because
it
would
be
good
to
get
through
those.
There
is
a
dock
that
outlines
all
of
them.
I
just
know:
I
never
have
time
to
go,
look
through
it
and
understand
which
ones
still
need
tweeting.
A
B
A
A
A
A
A
D
Actually,
for
on
the
sick,
docs
point
of
view
for
the
blogs
we're
actually
applying
the
same
flow
as
well,
a
hack
in
the
Google,
Doc
I
think
there's
a
crate
initial
or
create
work,
create
your
draft
first
hack
in
the
Google
Doc
create
an
initiative
track
your
blog
link
it
to
the
hack,
MD
Etc,
and
then
the
process
is
kind
of
formulated
by
both
the
contributor
site
and
kubernetes.io
blog.
So
it's
kind
of
kind
of
work
together,
nice,
so
I
wonder.
D
A
D
A
D
A
A
A
A
A
B
A
Rashid
you
had
a
concept
on
squashing
commits
you
had
some
experience
there.
You
thought
you
might
be
able
to
share
this
isn't
urgent,
but
if
you
wanted
to
write
a
tweet
or
an
article
on
that,
I
need
to
get
you
set
up
with
buffer
I.
Don't
know
if
I've
done
that
yet!
But
if
you
wanted
to
pursue
this,
you
know
where
to
find
us
if
you
need
any
help.
All.
B
B
A
A
A
Last
two
items:
this
is
still
kind
of
an
ongoing
concept.
It
might
take
a
while
to
get
done
security
comms
guidelines.
So
whenever
we
have
communications
that
we
need
to
get
out
about
security
issues,
those
are
very
delicate.
So
the
concept
here
is
to
work
with
Sig
security,
to
make
sure
that
we
have
some
specific
guidelines
in
place
for
when
we're
communicating
about
security,
Avinash
had
volunteered
to
take
that
on.
A
D
A
Oh
yes,
this
thing,
so
the
the
GitHub
workflow
will
not
be
going
away.
We
have
adopted
a
new
tool
for
getting
tweets
out
via
on
the
Kate's
contributors
account,
which
is
much
smoother,
and
it
has
allowed
us
to
do
the
blog,
Automation
and
everything.
So
it's
quite
wonderful,
but
we
do
sometimes
get
requests
from
folks
outside
of
contributor
comms,
who
don't
need
access
to
be
able
to
write
tweets
regularly.
A
So
we
want
to
make
sure
that
we
keep
the
GitHub
workflow
in
place,
because
that's
a
nice
workflow
that
mimics
the
regular
contribution
workflow
that
other
contributors
go
through,
but
it
has
the
issue
of
it
doesn't
handle
links
very
well
and
also
it
can't
actually
schedule
tweets
because
of
the
way
that
we
do
our
PRS
here
in
kubernetes.
So
we
have
an
issue
open
with
the
creator
of
the
tool,
Twitter
together
to
add
support
for
us
to
be
able
to
schedule
tweets.