►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20221111
Description
[SIG ContribEx] Weekly Marketing Meeting for 20221111
A
As
usual,
please
remember
that
we
do
have
a
code
of
conduct
which
says
essentially
be
respectful
of
your
fellow
speakers
and
attendees
and
generally
be
excellent
to
each
other
and
usually
here
at
the
beginning
of
the
meeting.
We
offer
the
opportunity
for
any
new
folks
on
the
call
to
introduce
themselves
so
if
you're
new,
totally
optional.
But
if
you
would
like
to
say
hello
and
tell
us
a
little
bit
about
why
you're
here
we'd
love
to
meet
you.
D
A
D
E
G
E
A
G
I
I
wanted
to
say
hi.
My
name
is
Maldonado
I'm
a
station
in
Costa
Rica
I
used
to
be
part
of
Linux
communities
in
the
past,
but
it's
been
a
long
while
since
I
don't
contribute
so
I'm
here
to
put
my
two
cents
wherever
I
could
be
helpful,
I
have
a
full-time
job
autistic
doing
Courtney
these
things
and
I've
been
using
kubernetes
just
for
around
two
years
now.
D
I
J
You
I
can
go
next,
so
hi
there,
so
my
name
is
Imran,
so
I
also
joined
this
sig
like
three
months
back.
I
got
the
membership
for
kubernetes
and
for
the
city
as
well
and
yeah.
So
I've
been
working
basically
on
the
technical
aspects
for
this
one
and
started
a
little
bit
on
the
blogging
part.
So
just
learning
and
doing
some
stuff
around
the
city,
so
I'm
also
like
daytime
and
like
PPM
for
the
Continental,
it's
automative
company,
so
I'm
happy
to
share
and
learn
together
with
everyone.
A
K
Hi
everyone
so
mrf
and
back
I
guess:
I
have
been
interested
in
kubernetes
for
a
long
time
now.
That's
basically
the
idea
of
something
I'll
just
go
and
say
it
in
the
clay
man
most
play
terms
as
possible,
see
the
idea
of
an
orchestration
engine
just
used
to
fascinate
me
and
I
had
not
actually
worked
on
that,
so
the
company,
when
I'm
working
used
to
be
on
Docker
swarm
and
now
we
have
shifted
on
kubernetes.
So
it's
good
that
I'm
actually
getting
some
Hands-On
on
on
that
earlier.
K
I
had
once
joined
I,
don't
exactly
remember
which
Sig
meeting,
but
it's
been
many
many
many
months
now,
but
yes
I
hope
to
keep
joining
these
meetings
so
as
to
get
an
idea
of
what
the
actual
community
that
is
driving
that
thing
that
so
many
people
use
functions
as
and
I
would
be
very
happy
if
I
am
able
to
contribute
in
any
any
way
possible.
I'm
stationed
in
India-
and
so
that's
it
hello.
Everyone
welcome.
D
A
A
Since
we
have
so
many
new
folks
on
the
call,
it
might
be
a
good
idea
for
us
to
actually
go
over
what
our
group
does
for
once,
which
we
do
periodically
when
we
actually
have
a
number
of
new
folks
on.
So
this
is
the
contributor
comms
team.
We
are
a
sub
project
of
the
special
interest
group
for
contributor
experience.
A
So
since
we
do
all
these
things
in
the
community
specifically
targeted
at
the
contributor
Community,
we
need
to
make
sure
that
folks
know
what
those
things
are
and
how
to
get
involved
with
them
and
how
we
help
them.
So
Communications
are
an
important
part
of
that.
So
the
charter
of
our
team,
as
the
contributor
comms
team,
is
to
make
sure
that
the
contributor
Community
knows
what's
going
on
in
the
community
and
to
make
sure
the
external
Community
knows
about
the
wonderful
things
that
our
contributors
are
doing.
A
We
can
we
have
a
slack
bot
granted
I
think
it's
still
not
quite
working
right
at
the
moment
where
we
can
ping
a
bunch
of
the
special
interest
groups
within
the
kubernetes
project
to
let
them
know
about
important
things
that
are
happening.
For
example,
the
annual
report
work
is
going
to
be
coming
up
soon,
so
we
usually
try
to
make
sure
that
the
community
knows
about
what's
in
the
community,
the
annual
report,
and
sometimes
we're
asked
to
help
make
sure
that
the
Sig
leads
and
folks
know
to
contribute
things
to
the
annual
report.
A
So
that'll
be
a
thing
coming
up.
We
also
have
the
Kate's
contributors
Twitter
handle.
So
we
try
to
report
the
news
on
there
for
kubecon.
We
queue
up
a
bunch
of
tweets
about,
what's
going
to
be
happening
at
the
conference
to
go
out
during
the
conference,
and
we
also
finally
have
automation
to
tweet
out
whenever
there's
a
new
blog
post
on
the
relevant
sites
like
kubernetes.dev
and
the
main
kubernetes.io
website.
A
So
we
have
a
few
different,
oh
and
we
can
also
email
Folks
at
kdev,
so
I
said
kdev
earlier,
because
I
always
think
kadev,
because
it's
kubernetes.dev,
but
kdev
generally
refers
to
the
the
mailing
list
that
goes
to
all
kubernetes
contributors.
So
sometimes
we
need
to
send
notifications
out
that
way
as
well.
So
there
are
a
number
of
different
tools
that
we
use
to
communicate
with
the
contributor
and
external
communities
and
that's
kind
of
us
anything
else.
You
want
to
add
Chris.
A
And
we
like
to
have
fun
so
anytime,
you
feel
like
popping
in
and
adding
your
thoughts
or
asking
a
question.
Please
do
we're
here
to
help
make
sure
that
you
are
having
a
good
time
in
the
community
and
are
having
fun
with
us.
A
lot
of
us
are
volunteers.
I'm
excited
to
hear
that
several
of
you
are
on
your
second
or
Beyond
attempts
and
getting
involved
with
the
kubernetes
community.
D
A
A
Each
group
is
a
little
bit
different,
especially
as
we're
mostly
Volunteers
in
the
contributor
Community,
each
group
kind
of
Finds
Its
Own
Way.
So
the
way
we
do
it
is
we
have
this
table
up
at
the
top
of
like
ongoing
action
items
that
we
need
to
check
up
on.
But
before
that
we
do
kind
of
a
general
check-in
which
is
noted
below
the
table.
A
D
A
A
A
A
So
the
regular
cfp
is
for
most
of
the
tracks
at
kubecon,
but
there
is
a
separate
maintainer
track,
which
is
just
for
the
open
source
projects
of
the
cncf,
and
that
is
a
totally
separate
cfp
and
process
for
getting
those
talks.
In
so
several
times,
our
group
has
had
a
talk
as
part
of
the
maintainer
track.
We
didn't
in
in
a
I
have
doubts
that
we
will
in
EU,
but
Sig
contribex
at
least
will
so
there
will
be
Sig
control,
X
content
at
capecon
at
the
very
least,
most
likely.
D
A
D
D
J
K
J
A
It's
a
weekly
meeting,
but
is
a
water
balloon
on
the
community
calendar,
because
so
many
folks
from
the
community
are
there
and
it's
such
a
big
lift
that
around
kubecon
folks
are
also
often
busy.
So
not
normal
happens
twice
a
year,
but
yeah
granted
the
holidays
are
coming
up,
so
we'll
be
missing.
Some
more
meetings.
A
D
A
A
D
And
that's
where
it's
kind
of
like
do
we
do
we
need
to
do
a
live
component
like
should
somebody
be
on
the
Twitter
talking
about
their
experiences?
I
guess
is
kind
of
the
better
question
for
the
group.
How
do
we
feel
about
that?
Well,
let's
just
think,
let's
just
you
know
put
in
the
notes
and
what
it
says
for
now,
but
you
know
maybe
next
time
we
can
or
next
in
a
or
when
you
know
we
could
maybe
set
a
goal
to
have
some
kind
of
yes
live.
E
D
I
mean
yeah
I
would
be
okay
of
like
setting
up
a
social
media
like
hangout
kind
of
thing,
if
we
had
to
and
people
just
pick
it
up
for
hours
at
a
time
or
days
at
a
time.
However,
we
do,
but
it's
an
idea,
because
I
do
feel
like
there's
a
lot
of
noise
being
made
during
cubecom,
but
it's
all
massively
broadcast
at
like
everyone,
not
specific
contributors,
not
like
hey
I,
went
to
this
awesome
talk
about
this
in
this
sig
and
I
learned.
D
A
A
D
A
A
E
A
A
That
was
gonna,
be
a
breaking
change
for
some
users,
not
a
lot
of
users,
but
a
few
and
I
don't
yeah.
I
know
right
need
some
more
information
on
that,
but
they
were
working
on
a
blog
post
about
it
and
wanted
us
to
help
Shepherd
that
through
I
told
him
to
reach
out
to
Frederico,
and
then
I
didn't
hear
from
him.
After
that,
did
he
reach
out
to
you
yeah?
Yes,.
H
H
There
was
still
discussing
the
actual
content
of
the
blog,
so
it's
not
like
it's
ready
on
their
side,
so
the
there's
still
discussion,
there's
still
adjusting
and
I
I
I
said
that
we
would
think
then
later
on,
when,
when
I
think
that
they
have
the
so
that
at
least
according
to
them,
the
the
content
is
good
enough
or
at
least
technically
gets
the
approval
of
everyone.
Then
we
would
follow
up
with
yeah.
D
A
A
D
A
So
we
do
have
a
new
solution
which
is
registry.khs.io,
but
we
can't
just
get
rid
of
GCR
no,
which
most
people
are
pointing
to,
and
we
can't
redirect
it.
I
talked
about
that
with
people
the
other
day,
so
we
need
to
just
like
tell
people,
please
start
using
registry.case.io
instead
of
the
old
URL,
where
you
would
get
those
images.
H
A
D
But
one
thing
for
folks
to
remember
is
that
a
lot
of
times
developers
kind
of
get
stuck
in
their
ways,
and
you
know
helping
spread
this
message,
even
if
it
like,
even
if
you
don't
understand
the
reason
behind
it,
if
some
developer
in
a
company
sees
this,
it
will
benefit
them
right.
This
is
one
of
those
interesting
use
cases
where
getting
this
out
there
in
a
big
way
helps
the
entire
community,
and
it's
one
of
those
few
things
that
you
can
actually
say.
D
A
And
to
reiterate
how
important
it
is
we
almost
ran
out
of
budget
in
November
and
the
whole
project
would
have
come
to
a
halt,
because
we
wouldn't
have
had
any
more
budget
for
all
of
the
things
we
do
to
improve
the
project
because
of
all
the
money
we're
spending
on
people
downloading
these
images.
So
we
really
need
people
to
move.
A
A
A
D
I
E
I
D
D
A
H
Yeah
I
I
also
as
part
of
the
pr
push
I,
also
volunteered
to
make
the
markdown
version
of
this,
because
that's
the
way
that
it's
going
to
get
published
right.
So
that's
another
reason
to
be
sure
that
the
discussion
is
is
done
in
the
in
the
Google
Docs,
so
that
we
don't
have
to
extensively
change
things
afterwards.
A
Sounds
like
we're
good.
We
do
have
20
minutes
left
and
our
table
is
long.
It's
probably
a
good
idea
to
move
on
all
right,
oh
gosh,
why
is
it
so
long
so
first
thing
hina's
work
which
Hina
isn't
here
today,
but
what
are
we
working
on
here?
Yes,
so
Hina
did
some
work
for
us
earlier
this
year,
where
she
put
together
a
new
team
for
us
in
GitHub.
A
So
we
have
folks
who
are
regular
contributors
to
this
team
in
the
team
in
GitHub
and
the
idea
for
that
is
to
be
able
to
notify
most
of
the
folks
on
the
team
when
there
are
issues
or
PR's
that
need
our
attention.
So
a
second
part
of
that
is
making
sure
that
we
actually
do
get
notified
when
those
things
exist.
So
I
think
Tina
did
update
the
k,
Community
issues
template
so
now,
when
you
create
an
issue,
it
has
us
tagged
in
there
when
you
create
an
issue,
that's
like
directed
toward
our
team.
A
A
A
D
A
D
E
A
A
H
I
can
yeah
no,
it
is
open.
I
read
so
after
the
last
major
change
that
I
did
I
also
committed
some
additional
stuff.
So
for
my
sides,
I'm
I
think
that
I
just
need
to
Ping
workers
again
just
to
be
sure
that
it's
good
to
go.
His
last
comment
was
in
that
direction.
So
that's
I
just
need
to
know
exactly
what
else
is
is
needed
to
to
to
close
it.
H
G
A
I
say
that
a
lot
in
this
meeting
all
right
so
we'll
move
on
past
that
if
you
need
any
help,
you
know
where
to
find
us
on
Slack
update
the
owner's
file.
So
this
is
one
of
the
GitHub
updates
that
I
need
to
do
now
that
it's
after
kubecon
I
was
hoping
to
do
these
things
yesterday,
but
imagine
that
didn't
get
to
it
today,
I'm,
just
like
helping
out
with
a
customer
meeting
all
day
where
I'm
just
on
call
for
questions.
A
A
A
Okay
and
Avinash
offered
to
help
with
that
as
well,
so
I'll
reach
out
to
him
moving
on
slackbot.
So
we
tried
to
use
the
slackbot
during
our
steering
committee
election
that
was
just
like
a
month
ago
or
something
not
even
but
the
slackbot
had
been
broken
by
some
changes
that
were
going
on
and
then
it's
back
up,
but
it's
not
actually
in
all
the
channels
that
it
needs
to
be
in.
So
you
need
to
add
the
bot
to
the
channel
for
the
bot
to
be
able
to
post
in
the
channel.
J
J
So
I
have
to
check
as
well
so
I
don't
have
the
permission.
So
that's
the
problem
so
I
get
my
slack
yeah
I
want
to
test
it
and
see
how
it
actually
works,
because
rajula
has
the
permission
and
atharva
has
them
to
add
me
into
a
channel
so
that
I
can
you
know,
test
them
and
see
how
it
actually
works.
I,
don't
know
if
Chris
are
canceling
a
part
of
the
group,
so
yeah
I
have
to
have
a
Hands-On
on
it,
so
it
would
be
great
if
some,
either
rajula
or
atarama
could
add
them.
J
J
D
A
B
A
J
Yeah
exactly
so
I'll
create
issue
for
it,
so
at
least
let's
say
the
issue
is
to
add
the
bot
manually
to
all
the
X
number
of
Channel
n
number
of
channels
that
are
select.
I'll
just
add
the
issue.
If
you
find
automation,
it's
good
enough,
if
not
also
we're
going
to
make
the
task
need
to
be
accomplish
so
that
before
the
next
big
announcement
or
something
happens,
we
have
it
in
place.
So.
D
D
E
J
A
Review
repo
look
into
adding
role
descriptions,
we
do
have
role
descriptions
now,
I'm
going
to
change
this,
to
update
repo
with
role
descriptions,
so
we
basically
spent
months
where
every
one
of
these
meetings
we
debated,
what
roles
we
should
have
in
our
group
and
how
we
should
Define
them
and
things
like
that,
and
then
we
had
individual
members
of
the
group
write
out
the
definitions
of
those
roles
who
mostly
folks,
who
are
doing
that
work
anyway.
So
as
I
was
mentioning
earlier,
I
need
to
get
update
the
GitHub
repo.
A
This
is
another
one
that
I
need
to
highlight
pink
foreign,
so
we
have
most
of
our
roles
defined.
Our
roles
are
not
super
strict.
They
aren't
the
only
thing
that
you
do
if
you
are
a
lead
in
a
certain
area.
You're
welcome
to
help
out
in
other
areas,
you're
welcome
to
change
and
move,
but
they
are
guidelines,
for
these
are
types
of
work
that
we
need
to
have
done
and
we
need
someone
to
own
that
work.
A
So
that's
kind
of
the
purpose
of
our
roles
and
the
roles
that
we
have
are
social
media
coordinator,
which
I
guess
is
basically
myself
right
now
that
role
is
defined
and
in
our
repo,
but
we
still
need
to
update
the
main
page
of
the
repo
if
who
is
serving
as
that
lead,
each
of
these
also
the
handbook
has
information
for
shadowing.
So
if
any
of
these
tasks
or
roles
sound
interesting
to
you,
you
can
Shadow
those
roles
and
become
that
lead.
A
We
also
have
Avinash,
who
will
be
our
events
coordinator
I
mentioned
that
Sig
contribex
has
a
lot
of
events
that
go
on,
so
there
are
individual
coordinators
for
those
events
at
the
higher
Sig
contribex
level,
but
those
events
also
need
comms
and
to
make
sure
the
contributor
Community
knows
what's
going
on
for
those.
So
we
wanted
to
assign
someone
in
our
group
to
kind
of
keep
an
eye
on
the
landscape
of
events
going
on
in
the
contributor
Community
to
make
sure
that
we
are
getting
those
Communications
out.
So
Avinash
is
our
main
person
there.
A
A
A
A
J
Contribution
made
after
some
time
so
it
seems,
but
I
need
a
little
help
on
this.
One
I'll
say
like
I,
need
really
help
on
this
one,
because
I'm
not
progressing
much
as
I
would
have
expected,
because
I
was
hopping
on
the
document
which,
which
is
the
new
contributor,
Workshop,
bhakman
or
the
course
which
they
have
been
gonna,
come
up.
It's
not
at
live
so
I've
seen
the
preview
and
also
the
document,
but
it
has
little
info
for
this
particular
task.
J
A
J
J
A
See
what
I
think
might
be
a
good
approach
for
this,
so
the
contribex
Sig
as
a
whole
is
working
on
updating
some
of
their
own
roles
and
they're
working
on
making
sure
that
we
have
a
tech
lead
role
at
the
Sig
level
as
well.
So
maybe
this
would
be
a
good
question
for
our
Tech
lead,
which
I
think
is
still
kind
of
being
worked
out.
So
maybe
ping
in
Sig,
contribex
and
say.
E
E
A
A
And
to
all
of
you
out
there,
if
you
see
Upstream
marketing
around
somewhere,
please
update
it
to
contributor
comms
I'm,
going
to
move
on
past
that
to
another
thing
that
would
normally
take
us
a
while,
but
we
only
have
three
minutes,
which
is
six
spotlights.
So
we
have
this
running
project
where
we
it's
open
to.
Anyone
who
joins
us
in
these
meetings
or
generally
wants
to
help
to
create
a
blog
post,
where
you
shine
a
spotlight
on
a
special
interest
group
within
the
kubernetes
project.
A
A
Yeah
we've
done
a
number
of
them
recently,
which
is
really
exciting,
but
there
are
so
many
cigs
in
kubernetes.
There
are
plenty
more
to
do
these
take
a
really
long
time
to
do
because
they
do
require
collaboration,
so
you
would
reach
out
to
that
Sig
in
slack
and
say
hello,
I'm
part
of
the
contributor
comms
team
I
want
to
write
a
blog
post
about
your
Sig.
Who
should
I
talk
to
usually
that's
going
to
be
the
chairs,
so
you'll
reach
out
to
the
chairs
to
interview
them.
A
We
usually
recommend
doing
that
asynchronously
in
a
Google
doc.
It
often
takes
them
a
while.
The
1.26
release
is
coming
out
in
December
we're
already
in
code
freeze,
so
Sig
chairs
are
going
to
be
busy,
but
it's
always
good
to
get
the
process
started.
If
you
want
to
do
one
of
these
and
then
you
would
conduct
that
interview
and
turn
that
into
a
blog
post
and
Frederico
has
laid
out
our
blogging
guidelines
so
that
you'll
understand
how
to
go
through
that
process.
So
anyone
who's
new
to
the
group.
A
If
you
are
interested
in
learning
more
about
the
sigs
within
kubernetes.
This
is
a
great
opportunity
for
you
to
do
that
and
get
some
public
content
out
there
as
well
reach
out
to
us
in
slack,
if
you're
interested
in
that
and
I'll
kind
of
leave
it
there.
Since
we
have
one
minute
left
updates
to
the
blogging
instructions,
this
is
done
right,
so
I
can
just
remove.
This
line.
Can
I
remove
one.
A
Migration
from
katakota
to
GitHub
spaces,
as
folks
may
know,
katakota
is
gone
now,
so
we're
looking
at
moving
to
GitHub
code
spaces,
which
is
a
new
thing,
we're
just
kind
of
keeping
an
eye
on
that.
We
noted
that
it
needed
help,
but
also
it
doesn't
need
help
immediately,
not
quite
ready
for
help.
Yet.
A
A
There
was
a
Blog
that
needed
to
be
reviewed.
It
just
needs
digox
review.
It
doesn't
need
anything
from
us.
Keep
track
of
Sig
Doc's
blog
sub
project
process
changes
Ray
wanted
to
actually
kind
of
emulate.
What
Frederico
has
documented
for
the
Sig
docs
blog
sub
project
as
a
whole,
which
is
exciting
security,
comms
guidelines,
so
when
we
have
to
do
Communications
about
security
incidents
or
things
like
that,
those
Communications
are
very
sensitive,
we'd
like
to
have
more
documentation
on
how
to
conduct
those
Communications
appropriately.