►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20230324
Description
[SIG ContribEx] Weekly Marketing Meeting for 20230324
A
Hello
and
welcome
everyone
to
the
Friday
March
24th
edition
of
the
contributor
comms
team
meeting
a
reminder
we
do
operate
under
a
code
of
conduct
which
basically
says
to
be
respectful
of
your
fellow
attendees
and
speakers
and
generally
be
excellent
to
each
other
and
I
have
the
notes
up
for
today.
I
don't
see
anyone
new
in,
but
if
anyone
wants
to
introduce
yourselves
you're,
of
course
welcome,
you
can
either
use
the
chat
or
you
can
unmute
I.
Think
I
have
everyone
in
the
notes.
I
have
put
the
notes
in
the
chat.
A
C
Sure
yeah,
so
as
assigned
to
me,
I
did
manage
to
you
know:
transfer
the
data
from
the
table
to
the
board.
B
A
E
A
A
E
A
Yeah,
right
after
we
decided
to
give
up
waiting
for
them,
so
we
said
I
think
in
the
last
meeting
that
we
did
have
a
mastodon
account.
Yes,
so
now
we're
gonna
have
a
different
Mastermind.
We.
B
A
That's
it
for
what
I
had
in
here
there's
one
other
thing:
I
think
I
want
to
mention
right
now,
which
is
also
in
the
in
the
board.
So
I
didn't
need
to
mention
it
right
now,
but
I
want
to
which
is
keep
Connie
you
tweet
planning
that
is
ready
to
go.
We
mentioned
that
last
time.
Anyone
who
wants
to
get
involved
as
a
new
contributor
who
might
want
to
write
some
tweets
is
welcome.
A
If
you
want
to
share
that
with
your
networks,
say
hey
if
you
want
to
contribute
to
kubernetes
in
a
fun
way
by
writing
some
tweets
for
kubecon.
Let
us
know
in
the
contributor.com
slack,
Channel
probably
just
point
them
there
that
way.
They
have
a
place
to
ask
questions
and
we
can
point
them
to
the
dock
and
everything
so
feel
free
to
share
on
social
media
I,
usually
Post
in
Sig,
contribex
and
I.
Haven't
done
that
yet
very
welcoming
task
for
anyone
new
to
the
project.
A
A
A
So
yeah
we
need
to
get
that
done
and
we
need
to
so
we'll
need
to
collect
all
of
the
tweets
write,
all
tweets,
probably
within
the
next
two
weeks,
and
then
the
last
week
before
kubecon
I,
usually
tried
to
reserve
to
get
all
of
those
scheduled
in
buffer,
which
sujay
you
offered
to
help
with
nitish.
You
also
offered
to
help
with
this
so
I'll
reach
out
to
you
too.
A
E
F
Yeah
I
guess
we
have
started
planning
about
the
Tweet
planning
I
see
a
bunch
of
tweets
have
been
written,
although
I
shared
it
on
the
sick,
contrabix
Channel
as
well
and
I
was
planning
to
share
it
among
the
in-depth
Channel
as
well,
because
I
see
a
couple
of
new
contributors
can
get
involved
by
writing
the
tweets
for
the
coupon.
So
it's
a
great
way
and
just
wanted
to
mention
that
tweet
planning
has
actually
been
started.
So
it's
just
on
the
way.
A
A
Okay,
so
that's
all
the
updates,
big
wins
that
I
had
I
think
do
we
want
to
mention
any
updates
about
the
registry
change
that
happened.
B
This
week
anything
I've
got
I
mean
so
I
got
some
historical
data.
On
that
the
the
change
is
still
being
rolled
out.
There
was
the
delay
on
Monday
because
of
some
back-end
storage
like
syncing
issues
and
issues
as
well.
So
once
I
got
that
all
fixed,
they
started
the
rollout
again
just
a
little
bit
slower
and
then
it's
in
like
full
swing
right
now.
It's
almost
done
I
feel
like,
but
Ben
just
posted
an
update.
Let
me
go
check.
B
B
B
He's
been
very
good
about,
like
hey
I,
seen
something
weird:
does
anyone
know
anything
anything
about
this
and
you
know
I've
pulled
in
folks
from
jfrog
to
look
at
artifactory
and
yeah.
You
know
it's
just
right
now.
It's
just
like
watching
watching
the
bits
move
from
one
place
to
another
and
figuring
out
all
the
little
subtleties
of
things.
A
B
Yeah
like
this
is
long
overdue.
I
hope
folks
realize
that
right,
like
if
you're
ever
in
a
new
project
and
all
of
a
sudden,
you
join
a
foundation.
You
need
to
migrate
all
that
infrastructure
to
the
foundation
as
fast
as
possible.
Right.
So
just
keep
that
in
mind
like
this
is
geez
like
five
years
overdue,
I
feel
like
and
it
it's
gonna
just
still
be
a
problem.
I
feel
like
next
year
until
we
shut
it
off
or
whenever
that
happens,
yeah.
A
So
if
anyone
had
missed
that
context,
by
the
way
we
GCR
case.gcr.io,
what
it
is
was
the
old
registry,
where
we
put
all
of
our
images,
we
now
have
registry.case.io,
which
is
much
better
in
many
ways,
so
we're
trying
to
get
folks
moved
over.
So
this
week
we
did
a
redirect
of
the
old
URL
to
the
new
URL,
but
that's
only
a
temporary
fix.
We
really
need
people
to
change
things
to
specifically
mention
specifically
reference,
the
the
new
registry
and
it's
very,
very
important
for
the
project,
the
health
of
the
project.
A
So
if
you
can
help
spread
the
word
on
that,
please
do
all
right.
So
with
that
any
other
new
items
that
folks
want
to
talk
about,
we
gotten
any
oh
I-
did
see
a
a
PR
or
an
issue
came
in
I.
Think
it
was
a
PR
came
in
in
the
contributor
tweets,
repo
I
think
it's.
It
was
a
an
update
to
the
link
to
Twitter
together.
Apparently,
it's
not
in
the
creators
like
account
repo
anymore.
He
like
moved
it
into
a
more
like
public
location,
I
think
so.
A
The
URL
for
Twitter
together
changed
and
that's
referenced
in
our
doc,
so
I
can't
remember
exactly
who
it
was
right.
This
second
darn
it,
but
someone
very
kindly
made
a
PR
to
update
that
in
that
repo,
so
I
was
best
to
review
it,
but
anyone
with
reviewer
privileges,
approver
privileges
in
contributor
tweets,
could
check
that
out
and
approve
it.
A
So
you're
welcome
to
check
that
out.
If
anyone
wants
to
test
out
their
new
approver
privileges
in
contributor,
tweets.
C
There
was
some
survey
going
on
I,
don't
remember
exactly
I
did
share
in
our
Channel,
but
it
seems
that
we
are
supposed
to
promote
that.
Chris
is
something
involved
with
that.
So.
A
E
C
B
B
C
A
A
B
Yes,
there's
two
now:
okay,.
B
B
A
E
A
Thank
you
very
much
abnesh
for
calling
that
out
definitely
also
saw
that
come
by
and
then
did
not
look
at
it.
So
I
really
appreciate
that
we
have
folks
who
pay
attention.
B
A
Good
stuff,
all
right
we're
moving
into
the
board.
Hey
it's
23
minutes
in
that's
pretty
good
I!
Think.
B
I
moved
the
zapier
job
from
Nigel's
zapier
account
into
the
official
contributors
at
kubernetes.io,
zapier
account,
so
that
automation
is
better.
Yes,
that's
our.
B
B
E
H
E
E
B
H
A
Alrighty,
so
with
that,
let's
move
into
the
board.
D
So
I
would
say
pretty
much
the
same.
That
last
time
with
the
with
the
update
that
I
I
was
actually
missing,
sending
the
link
to
them
or
I
sent
the
wrong
link
to
the
cap
reading
club
contact.
So
obviously
it
didn't
do
anything
there,
because
that
was
meeting
so
I've
corrected
that
I
have
the
document
on
Google,
Docs
and
I
hope
that
that's
just
what
was
was
missing
because
there
was
no
feedback,
because
I
hadn't
added
the
questions
there.
D
Yet
in
Sig
architecture,
there's
work
work
still
being
done
on
the
questions
because,
as
I
said
last
week,
certainly
I
think
two
weeks
ago
as
well,
we
have
expanded
the
number
of
participants,
because
the
leads
have
delegated
to
the
sub
project
leads
and
we're.
D
We
we
were
discussing
if
we
should
do
like
a
mini
series
around
different
projects
in
Sig
architecture
or
just
one
and
whomever
had
the
availability
would
cover
those
ones
I'm
targeting
this
last
one,
because
I
think
it's
simpler
to
have
one
a
single
art
article,
but
I'm
still
finishing
up
the
new
questions
for
it.
So
that's
it
for
these
two.
B
D
I'm
I
those
ones
I
know
that's
the
the
networking
one.
It's
pending
a
a
a
final
review,
I
think,
but.
D
G
E
G
D
D
D
G
G
A
Yeah
and
if
you
want
to
share
the
link
to
the
issue,
you're
welcome
to
do
that.
I
know
that
I
need
to
respond
to
it.
Chris
I
think
you
are
going
to
also
sponsor
everyone
else.
B
B
E
A
I
think
I
can
log
in
through
my
work
profile
on
my
work
profile.
I
think
is
logged
in
so
I
will
just
do
that.
Real,
quick.
A
Commented
if
anyone
else
wants
to
add
their
plus
one
I
see
no
reason.
Why
not
well,
someone
wants
to
correct
me
on
that,
so
it
sounds
good.
It
looks
like
I
can't
thought
that
I
could
edit
the
notes
on
the
the
draft
for
the
Sig
networking
Spotlight,
but
I
guess
that
I
can't
so
Frederico.
If
you
want
to
update
the
progress
on
it,
I
think
that's
a
you
thing,
but
I
will
just
leave
it.
A
Oh
yeah,
that's
probably
why
gosh
dang
it
I'll
fix
that
later.
Moving
on
registry.kates.io
social
media
is
also
still
ongoing.
So
we'll
leave
that
in
in
progress
Spotlight
on
six
CLI
I
was
arpit.
Armpit
is
not
here.
A
You
have
had
some
more
folks
join
if
anyone
is
new
to
the
call
and
you'd
like
to
say
hello
and
tell
us
a
little
bit
about
who
you
are
and
what
you
want
to
do
here.
You
are
welcome
to
do
so
in
the
chat.
I'll
recommend
the
chat
for
now,
as
we
try
to
work
through
the
the
board,
but
I'll
probably
give
you
a
chance
later.
If
you
want
to
unmute
and
say
hello,
anyone
wants
to
do
that.
A
Oh
yeah
I
see
all
good
all
right
right.
I
already
mentioned
tweet
planning.
We
still
haven't
updated.
The
GitHub
team.
A
A
B
B
A
A
A
There
are
a
whole
bunch
of
spotlights
once
again,
if
anyone
is
new
or
looking
for
work
to
do,
you're
always
welcome
to
pick
up
one
of
those
Sig
spotlights
we
have
information
about
the
process
for
it
in
our
repo
and
you're
always
welcome
to
ask
in
the
contribexcoms
channel,
and
someone
will
help
you
learn
the
process
if
you
ever
want
to
pick
up
a
spotlight
promoting
new
contributor,
Workshop
content
also
still
on
hold
because
of
the
GitHub
workspaces
code,
spaces,
integration
code,
spaces
right,
that's
what
it's
called
so
we're
waiting
for
the
GitHub
code,
spaces
new
tooling,
to
be
integrated
into
the
workshop,
so
that
folks
can
like
do
the
Hands-On
Parts
through
GitHub
code
spaces
as
they
go
through
the
content,
so
we're
waiting
for
that
integration
before
we
promote
it.
A
Comms
guidelines
for
sensitive
security
topics
and
sensitive
topics
in
general
someday.
We
will
maybe
do
that
retrospective
on
registry
comms
still
ongoing,
so
I'm
not
going
to
do
a
retro
on
it.
Yet
probably
something
I
think
we
already
said
this
probably,
but
it
was
probably
something
that
we
could
do
at
the
contributor
summit,
though
you
won't
be
there,
so
that
okay,
we'll
figure
that
out
sorry.
A
Yeah
the
whole
shift
in
Day
Zero
events
is
interesting.
Let's.
B
Just
put
it
like
this,
I
had
to
buy
Six
lavalier
mics
this
week
just
cover
the
curve
balls
that
have
been
thrown
at
me
for
our
day.
Zero
event
like
it
went
from.
Oh,
we
should
have
a
watch
party
in
the
office
too
nope
we're
going
to
be
doing
original
content
in
the
office
mixed
in
with
your
day,
Zero
event,
and
it's
like.
Oh
my
God.
A
Slackbot
is
still
broken.
That's
that's
just
forever,
oh
and
notify
the
comms
team
when
a
new
issue
is
created.
That's
also
something
that's
still
on
the
back
burner.
Cool,
so
I
think
to-do
list
is
correct.
In
progress
list
is
correct.
There's
one
item
that
is
ready
for
review.
I
probably
should
have
started
with
that.
Honestly.
D
Yeah,
so
this
was
I
I
think
the
the
work
of
the
week.
Let's
call
it
like
that
to
have
something
advancing.
So
there
was
this
sharing
of
experience
from
zero
to
sub-project
leads
article
that
I
think
it
was
actually
Avinash
that
pinged
us
to
to
go
to
the
thread
where
it
was
being
discussed
in
Sikh
contrabands,
and
so
during
the
week.
D
A
D
Actually,
maybe
we
could
have.
This
is
a
bit
matter,
but
maybe
we
could
use
our
Twitter
and
and
Mastodon
to
actually
spread
the
word
in
that.
If,
if
anyone
wants
to
share
their
experience,
that's
whatever
they,
they
can
I
think
that
have
any
kind
of
landing
page
with
instructions,
but
I
I,
don't
think
that
that's
necessarily
needed,
maybe
pointing
them
to
our
Channel
or
something
would
would
suffice,
but
it
could
be
just
that
most
people
do
not
know
that
they
have
the
possibility
yeah.
A
A
D
No,
no,
no!
No!
No!
No!
No,
not
at
all,
also
because
I
think
that
that
could
be
also
an
issue
with.
Let's
call
it
low
efforts,
submissions
right
because
there's
a
lot
of
stuff
that
kubernetes
is
a
well-known
project
right.
So
there
are
multiple
ways
of
participating
and
some
are
just
like
picking
that
checkbox
I've
created
something
and
that's
not
exactly
what
we
we
are
after
right.
D
We
are
after
real
experiences
and
content
from
people
that
want
to
be
active
in
the
community
and
not
necessarily
those
that
just
want
to
have
here's
me
and
I,
like
kubernetes
article
right.
D
G
A
Our
group
can
be
part
of
that
triage
process,
so
sending
them
to
our.
A
All
right
so
I
think
that
is
it
for
the
board.
If
you
ever
remove
anything
to
done
that,
you
want
to
talk
about
probably
mentioned
in
updates.
Big
wins
because
I
don't
know
that
I
will
notice
it
in
here.
I
guess
the
registry.case.io
frequently
asked
questions
is
done.
I
think
we
did
that
last
time,
though,
and
then
what
you
need
to
know
blog
article
or
out
yeah,
we
moved
those
last
time
so
I'm
going
to
move
back
over
to
the
table
all
right.
Oh
there's!
So
little
of
it
left,
it's
wonderful.
A
Automatically
add
a
comment
and
GitHub
comms
team:
when
a
label
is
applied,
you
know
this
is
already
in
the
table.
So.
A
Perfect
I
was
just
wondering
if
you
had
removed
things
or
not
I
think
it's
better
not
do
so
so
that
we
can
go
through
it
together,
perfect,
so
that
would
be
which
one
is
that
done:
I'm,
seeing
when
an
issue
is
created
yeah,
it's
that
one
right
and
you
already
put
all
those
notes
in
here:
wonderful,
well,
a
bunch
of
nuts
perfect,
oh
and
I
can
edit
this
one,
oh
yeah,
because
I'm
logged
in
now
right,
that's
the
thing!
A
Yeah,
so
we
have
this
concept
tracked
in
the
the
board.
There's
enough
context,
I
think
there
for
us
to
get
going
it's
on
the
back
burner
anyway.
So
when
we
come
back
to
it,
we'll
have
to
figure
things
out
again
so
I'm
going
to
remove
this.
G
E
A
A
And
that's
in
there
so
delete
row
and
contributor
columns
gold
stars,
that's
a
cool
concept.
It'll
probably
never
happen,
I,
don't
think
that's
over
there,
but
that's
probably
fine.
C
A
Wonderful,
all
right
cool
so
with
that
I'm
gonna
run
over
to
contributor
tweets
real
quick,
so
that
we
can
look
up
that
PR.
That
I
mentioned
update
Twitter
together
URL.
This
was
castrojo.
Yes,.
A
H
A
A
H
E
H
F
A
You
said
shared
some
asynchronous
notes
for
us
for
our
last
meeting.
He
said
that
he
needed
a
dedicated
meeting
to
discuss
some
of
these
things.
Oh
did
we
actually
ping
atarva
about
the
links
issue?
A
A
When
one
of
our
big
issues
with
Twitter,
together
and
honestly
with
creating
couponing,
you
tweets
and
anything
pretty
much
that
we
do
with
Twitter
is
that
when
you
put
a
tweet
into
Twitter
to
post
it,
and
it
has
a
link,
you
can
put
a
pretty
big
Link
in
there
and
Twitter
automatically
shortens
it.
Yeah.
H
B
H
A
Be
so
that'll
be
an
issue
with
this
automation
as.
A
You
check
for
that
at
the
issue
stage.
You
will
also
have
the
link
issue,
but
also,
if
you
don't,
then
it
might
not
work
so
I
don't
know,
but
that's
something
to
discuss.
H
E
E
A
Access
to
buffer
to
be
able
to
use
that
workflow
is
the
goal,
so
if
they
want
it
scheduled
at
a
specific
time,
they
would
need
some.
H
A
C
Yeah,
so
whenever
we
are
sharing
the
forms
for
the
spotlight,
are
we
storing
those
forms
for
reference
future
references
or
something
on
our
drive
or
something.
C
So
usually,
we
share
a
form
in
order
to
get
response
from
the
leads.
Okay,
so.
A
A
A
So,
if
you
want
to
go
a
community
I'm,
just
gonna
find
our
repo.
This
way
communication
tutor,
comms,
storytelling
resources
in
here
you
can
see
an
example
interview.
This
is
for
a
spotlight.
This
was
the
one
that
I
did
for
Windows
yeah.
A
A
You
ever
want
to
share
the
interview
questions
that
you
used
for
a
spotlight
you're,
welcome
to
create
a
PR
with
the
file
and
toss
it
in
here.
These
are
examples.
They
don't
have
the
answers
currently,
but
I
mean
Up
For
Debate.
What
you
think
is
useful.
D
I
I
would
think
that
the
published
examples
end
up
being
so
it's
good
to
have
that
there,
but
having
a
pointer
to
pass
a
spotlight
I
think
it's
the
it's
the
best,
because
there
are
different
different
ways
to
do
it.
D
There's
not
one
single
approach
for
spotlights
each
person
will
certainly
add
their
own
attached
to
it,
and
I
think
that
we
have
a
collection
of
published
ones
which
show
different
ways
to
do
it,
so
anyone
reading
them
can
can
pick
and
match
whatever
they
they
want,
even
because
the
six
themselves
are
different
right,
but
it's
but
yeah,
but
we
need
to
make
keep
this
updated.
E
A
D
I'm
just
saying
that
the
this
is
like
completely
appropriate
for
the
spotlight,
but
then
we
also
have
that's
more
detailed
description
of
the
of
the
blogging
process.
That
also
relates
to
Spotlight
right
because
that's
what
they
are
so
yeah
I
I
would
say
that
this
is
a
separate
set
of
those
guidelines
with
a
bit
more
information.
A
Anyone
who
wants
to
contribute
to
blogs
you
can
find
the
information
in
storytelling
resources.
Maybe
we
should
rename
that
so
we
used
to
when
we
originally
started
this
group,
we
called
any
member
a
Storyteller
and
all
storytellers
can
write
blog
posts
and
create
social
media
and
do
all
of
those
types
of
things
where
we
communicate
things,
thus
being
storytellers,
but
I.
Don't
think
that
title
really
makes
sense
to
anyone
that
anyone
really
cares
about
it.
A
A
D
Yeah
I
was
going
to
say
at
least
I
can
have,
I
can
have
a
go
at
it
or
anyone
else,
but
I
I.
If
a
readme
is.
D
That
would
like
no
yeah
I
mean
true,
but
obviously
opening
this
up
for
anyone
that
wants
to
participate,
and
just
if,
if
we
just
add
and
read
me
there,
that
organizes
the
files
with
some
con
with
some
context
right
so
go
here
for
the
for
the
guidelines
go
here
for
the
blogging
guidelines.
Here
are
past
examples.
I
think
it
would
be.
It's
personally
I
always
find
it
helpful
to
have
like
this
structure
description
of
what
the
content
is.
D
Instead
of
a
list
of
file
names,
I
need
I
need
to
click
on
each
one
of
them
to
really
know
what
I
have
inside
so
I
think
this
would
make
that
that
part
of
the
resources
easier
to
use.
D
A
A
Now
we
have
two
minutes
left,
so
if
any
new
folks
want
to
introduce
yourselves
on
the
recording,
because
we
are
being
recorded
for
YouTube
say
a
little
bit
about
yourself
and
what
you're
hoping
to
get
out
of
being
here,
you're
welcome
to
do
so
now,
otherwise,
I
will
end.
The
recording
you're
also
welcome
to
do
so
after
the
recording
ends.