►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20230331
Description
[SIG ContribEx] Weekly Marketing Meeting for 20230331
A
Oh
hello
and
welcome
everyone
to
the
March
31st
edition
of
the
contributor
comms
team
meeting.
As
a
reminder,
we
do
operate
under
a
code
of
conduct
which
essentially
says
to
be
respectful
of
your
fellow
speakers
and
attendees
and
generally
be
excellent
to
each
other.
First
off.
We
try
to
start
out
these
meetings
by
offering
an
opportunity
for
anyone
who's
new
to
the
call
to
introduce
themselves
you're
welcome
to
unmute
you're,
welcome
to
post
and
chat
you're
also
welcome
to
say
nothing
at
all.
A
B
B
D
For
sure
so
my
name
is
Amy
and
I
have
been
working
as
a
software
engineer
for
more
than
four
years,
mostly
I
worked
with
golang
and
nearly
like
fun
years
ago,
I
started
to
work
with
kubernetes
and
most
of
the
time,
I'm
working
in
infrastructure,
not
in
age
with
the
client
and
customer.
So
that's
all
about
me
welcome
to
be
here.
Thank
you.
D
I
recently
started
to
contribute
into
kubernetes
actually
with
testing
fraud,
with
help
with
one
of
my
colleagues
and
actually
he's
working
a
red
hat
and
we
are
working
in
another
company.
He's
part
danger
and
yeah
I
started
to
work
in
testing
fraud,
but
recently
I
couldn't
find
any
issue,
but
I'm
just
looking
around
to
work,
the
more
I
contribute
more.
A
A
Yeah
I'll
just
go
ahead
with
ourselves,
then
as
well.
I
guess
yeah.
Why
not
folks
can
hop
in
hi
I'm
kazlyn
I'm,
a
developer
Advocate
at
Google,
where
I
work
on
gke
and
open
source
kubernetes,
and
one
of
the
things
that
I
do
is
being
one
of
the
co-leads
of
this
sub-project
a
little
bit
about
contributor
comms.
A
B
Yes,
thank
you.
Caslin
I
am
Chris
short.
I
am
also
a
co-lead
here.
I
work
at
AWS,
currently
I
I'm
kind
of
like
a
human
Swiss
army
knife
I'm
on
a
marketing
team
as
a
DEA
right
now,
so
that's
kind
of
interesting
to
help
them
along
it's
a
relatively
new
team
that
had
been
formed
here
at
AWS
for
kubernetes,
specific
marketing,
so
helping
them
understand
the
community.
Helping
them
understand
open
source
is
even
like
part
of
that
as
well.
B
C
C
I'm
I'm
Frederick
but
Fred
is,
is
fine.
I'm
I
work
at
SAS
as
a
cloud
and
architecture
lead
for
southwestern,
east
Europe,
our
analytics
and
Ai,
and
data
science
solution
runs
on
top
of
kubernetes.
So
that
is
where
the
work
and,
let's
call
it
pleasure,
mix
apart
from
that
I,
do
have
a
background
in
in
Linux,
open
source
and
free
software
involvement.
F
F
G
B
Update
some
big
wins,
so
this
is
kind
of
a
big
win.
Given
the
kind
of
stance
of
heckydorm
on
Foundation,
followed
or
projected
directed
projects,
they
have
a
account
verification
process.
So,
if
you're
an
open
source
project
a
company
whatever
they
want
you
to
go
through
a
verification
process
just
so
they
know
that
you're
here
and
what
you're
doing,
and
they
can
kind
of
be.
B
That's
an
approved
account
on
this
instance
of
Mastodon
called
hecky
during
Monday
Tuesday
I,
put
in
a
issue
to
get
our
account
officially
verified
with
some
very
strong
justification
as
to
how
we're
not
affiliated
with
cncf
directly
and
how
we're
more
focused
on
communicating
with
the
contributors
that
actually
kind
of
left
Twitter
and
it's
locked
to
Mastodon
and
particularly
hachydorm.
So
that
worked,
and
we
don't
have
to
worry
about
moving
instances,
because
the
LFX
instance
is
a
mirror
only
instance
I
doubt
we
were
going
to
get
picked
up
on
that.
B
F
B
B
Don't
want
it
rejected
so
basically,
like
Twitter
mirrors
to
Mastodon,
do
not
perform
well
right,
like
you
can
see.
Justin
Garrison's,
Cloud
native
Yoda
account
like
it.
Does
the
auto
posting
and
finds
like
the
usernames
on
Mastodon
and
cross
posts,
and
everything
doesn't
really
get
any
traction
so
yeah.
We
need
to
be
same
message
slightly
different
content.
Right,
like
I,
don't
know
need
to
be.
A
A
It
could
be
lots
of
people.
There
are
lots
of
possibilities.
Sure,
anyway,
we're
very
excited
to
get
Mass
John
sorted
out.
A
number
of
folks
in
our
community
have
moved
over
to
Macedon
one
of
the
reasons
we
have
so
many
different
tools
for
communicating
with
the
community
is
that
nobody's
in
one
place
we
try
to
get
folks
via
email,
but
some
people
play
pay
more
attention
to
their
email
than
others.
Even
though
you're
supposed
to
pay
attention
to
it,
lots
of
folks
are
on
Twitter.
A
B
A
F
B
F
B
A
G
A
C
B
F
C
A
B
F
A
B
D
F
B
B
B
We
have
a
lot
of
irons
and
a
lot
of
fires
and
to
make
matters
worse,
we
had
the
registry
change
this
time
as
well,
that
had
to
be
heavily
communicated
out
and
it
was
an
AWS
heavy
event
or
process
as
well.
So,
like
I
was
involved
in
multiple
angles
of
that
and
getting
that
comms
out
less
contributor,
some
it's
just
too
much
for
one
person
right,
like
Crisis
comms,
like
I
I,
do
well
with
that
maybe
I
shouldn't
have
concerned.
You
know
volunteered
to
lead
this,
but
Shadow.
B
A
If
you
would
like
to
be
a
lead
or
a
shadow
of
a
specific
area
for
the
contributor
Summit
planning.
You
can
say
that
in
your
comment
on
the
issue
for
the
release
team
Shadows,
that's
our
most
well-known
Shadow
program
and
most
structured.
There
is
an
actual
application
process
which
probably
is
going
to
be
opening
up
soon
for
the
next
one,
since
1.27
is
finishing
up,
so
we'll
need
to
be
posting
about
those
applications
once
they
come
out
as
contributor
columns.
Does
that
help
cool
yeah.
B
A
Alida
yeah,
so,
if
you're
interested
in
shadowing
rules
within
our
group,
let
us
know
and
also
for
the
release
team,
we
need
to
keep
an
eye
on
that,
so
that
we
can
let
people
know
about
that
and
contributor.
Summit,
of
course,
will
just
be
on
the
contributor
Summit
timeline,
any
other
new
items.
I
think
we
should
go
ahead
and
move
into
the
table
or
the
it's
not
a
table.
It
was
a
board.
That
is
what
we
call
this
item.
B
A
A
C
Okay,
so
I
will
give
an
applicator,
not
necessarily
with
all
the
information,
because
it
doesn't
make
sense
for
me
to
share
the
Google
Docs
link
because
I
use
it
with
editor
rights,
but
I
will
do
something
more
abstract
there
and
and
wait
for
for
answers.
So
that's
where
we
are
in
these
two
I
don't
know
is
sujay
here.
Doesn't.
A
A
C
C
Yeah,
sorry,
no
so
is
it
will
be.
It
will
be
quite
busy
until
the
4th
of
April,
so
I'm
not
saying
that
necessarily
we
have
everything
ready
in
the
fifth
of
April,
but
after
the
4th
of
April,
we
will
get
more
news
on
this.
I
would
put
it
like
this
I
don't
want
to
commit
a
deadline
that
they,
you
didn't
sign
up
for
I'll,
say:
goal
yeah
yeah
week
of
a
505
plus
it's
fine,
because
if
you
need
any
assistance,
I
can
also
drop
in
so.
A
C
A
Okay,
we
will
leave
it
be
for
a
bit
longer,
I
suppose
before
we
move
it
back
to
to
do
all
right,
add
all
use
cases
for
zapier
automation.
So
that's
still
in
progress.
Oh
I
meant
to
say
before
I
moved
on
from
the
spotlights
a
bit
of
background
on
spotlights
for
all
the
new
folks,
I
feel
like
I.
Do
this
every
time,
but
always
good
to
go
over
so
Sig
Spotlight
blog
posts
are
one
of
our
Evergreen
tasks
in
this
group.
A
We
have
instructions
in
our
repo
on
how
you
would
conduct
the
interview
and
put
together
one
of
these
blog
posts.
You
can
also
get
help
from
any
of
us,
particularly
Frederico,
who
is
the
blogging
lead
for
us?
So
if
you're
interested
in
writing
a
Blog
about
a
SIG,
you
can
ask
about
writing
a
spotlight
blog
post
in
the
slack
or
in
the
chat
or
whenever,
wherever
and
we'll
help
you
get
started
with
that.
A
However,
the
thing
that
we
could
most
urgently
use
your
help
for
is
the
kubecon
EU
tweets.
So
we
do
this
for
every
cubecon.
We
have
this
sheet
where
we
have
instructions
in
the
first
Tab,
and
then
we
have
other
tabs
which
have
all
of
the
past
tweets
that
we
sent
out
on
the
Kates
contributors
Twitter
account
during
the
event
and
once
again
for
EU
2023.
We
are
planning
tweets,
there's
already
a
good
number
of
these
in
here.
Yay.
F
A
A
A
You
can
read
the
instructions
if
you
want
to
I,
don't
know
that
anyone
ever
does
they're
way
too
long.
I
should
rewrite
them,
go
to
the
cubecon
eu2023
tab
and
take
a
look
here
at
all
of
these
rows,
particularly
in
the
description
column,
and
if
you
see
a
description
of
a
tweet
that
we
need
like
lightning
talks
are
starting
now
you
need
to
tweet
about
that.
A
A
What
you
would
need
to
do
here
is
you
put
your
Twitter
handle
in
as
the
owner
of
that
tweet,
and
then
you
would
write
that
tweet.
You
can
look
at
examples
up
here
for
other
maintainer
track
block
tweets.
You
can
also
look
at
previous
examples
from
other
years.
Essentially,
a
maintainer
track
block
tweet
is
during
the
1630
time
slot.
A
This
is
relevant
in
contributor
news,
because,
even
though
it's
not
just
kubernetes
contributors,
maintenance
maintainer
track
at
kubecon
is
just
maintainers
of
cncf
projects.
So
it's
all
very
contributory.
So
we
like
to
promote
our
fellow
contributors
work.
So
that's
why
we
do
these.
We
also
still
need
keynote
stuff.
I
often
take
those,
but
if
anyone
else
wants
to
do
them,
you
are
more
than
welcome
to
the
information
about
them
is
on
the
schedule.
A
Sig
meet
and
greet
I
need
to
write
that
one
and
closing
I
guess
I'll,
probably
do
so
mainly.
We
need
help
with
maintainer
track
block
tweets
still,
so
you
would
write
the
tweet
and
then
later
myself
and
sujay
and
natish
have
volunteered
to
help
me
out
are
going
to
go
through
these
and
put
them
into
our
tool
for
scheduling
them
to
go
out
on
Twitter
via
the
case
contributors
Channel
at
the
specific
times
listed
in
this
document.
So
you
don't
have
to
worry
about
the
Tweet
going
out.
A
A
A
C
C
A
A
C
Can
have
conversations
about
it
and
with
well
so
many
open
threads
Things
fall
down,
but
no
I
I.
Don't
think
that,
specifically
for
in
that
for
that
role
in
that
fashion,
I
I
do
I
do
have
well
Avinash
and
others
that
have
offered
to
follow
up
and
help
in
specific
tasks
and
but
but
I.
Don't
think
that
the
the
idea
is
is
to
to
be
a
shadow
in
that.
A
G
A
A
To-Do
list
items
I'm
kind
of
tempted
to
not
go
through
a
lot
of
to-do
lists
for
the
next
couple
of
weeks.
Since
we're
leading
up
to
kubecon.
We
probably
won't
start
much
new,
but
we
should
probably
go
through
it.
So
we've
got
folks
for
a
little
bit.
We
have
a
bunch
of
spotlights
here,
like
I
mentioned,
spotlights
are
an
evergreen
task.
Anyone
is
welcome
to
help
out
with
at
any
time.
Here
are
a
few
suggestions.
A
So
here
are
some
spotlights
we
would
like
to
do
at
some
point.
If
you
are
particularly
interested
in
any
of
these
topics
feel
free
to
let
Frederico
know,
and
he
can
get
you
hooked
up
on
how
to
get
started,
promote
new
contributor,
Workshop
content
still
on
hold,
because
we
are
waiting
for
the
new
GitHub
code
spaces
functionality
to
be
ready
so
that
when
folks
go
through
the
new
contributor
Workshop,
they
can
get
Hands-On
with
it.
A
Before
we
promote
that
someday,
we
would
like
to
create
better
guidelines
for
sensitive
security
topics
and
other
topics.
Honestly
sensitive
comms
Chris
wanted
to
hold
a
retrospective
on
the
work
that
we
did
for
the
registry
comms
because
there
were
things
there
that
could
be
improved.
So
we
need
to
do
that
at
some
point.
That
was
a
case
of
sensitive,
timely,
very,
very
important
comms.
So
there's
lots.
We
can
learn
from
that.
Experience
notify
comms
team.
When
a
new
issue
was
created,
there's
still
some
work.
A
We
want
to
do
with
making
sure
that
we
get
notified
properly
when
issues
or
PRS
are
created
in
places
where
we
should
know
about
it,
because
GitHub
can
be
a
little
difficult
to
track
those
things
in
at
least
for
me,
slackbot
still
having
issues.
As
far
as
we
know,
this
one
is
actually
particularly
relevant
at
the
moment.
Folks
wanted
to
use
the
slackbot
for
things
around
kubecon.
It's
usually
when
folks
want
to
use
the
slackbot.
We
had
a
conversation
going
on
in
slack.
I
should
add
this.
As
a
note.
A
So
there's
some
work
that
needs
to
be
done
on
understanding
how
The
slackbot
Works,
who
owns
it
and
how
we
work
with
it.
So
documentation
is
needed.
We
still
need
to
figure
out
a
lot
of
that
stuff
before
we
can
document
it
conversations
going
on
in
slack
in
Sig
contribex.coms,
if
you're
interested
in
that
topic.
A
Nothing
only
like
two
people
on
this
call
can
appreciate
that,
but
we
used
to
have
a
giant
table
in
our
dock,
where
we
tracked
all
of
these
items
and
we
recently
moved
back
over
to
a
board
in
GitHub
and
it's
really
cool
and
I'm
very
happy
about
it,
and
that
was
Frederico.
So
thanks
Frederica,
as
usual,.