►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20211203
Description
[SIG ContribEx] Weekly Marketing Meeting for 20211203
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
hearing
from
welcome
to
the
december
3rd
upstream
kubernetes
community
meeting
or
upstream
marketing,
meeting
yikes,
it
has
been
a
long
week
here.
I
hope
you're
all
doing
well,
just
a
friendly
reminder.
This
meeting
is
being
recorded
and
the
code
of
conduct
applies,
which
essentially
means
be
awesome
to
everyone.
A
Since
we
missed
this
last
time,
I'm
gonna
do
it
first.
Are
there
any
new
people
here
that
would
like
to
introduce
themselves
or
have
not
said
anything
previously
but
have
been
attending.
A
I
will
say
that
tawan
did
finish
his
sig
multi-cluster
blog
and
wants
us
to
review
it.
So
I'm
gonna
at
least
put
that
in
the
notes.
A
A
Multi-Cluster
profile
that
has
taken
a
long
time
to
come
together,
let's
see
anything
from
last
week.
B
B
B
Yeah
so
yeah,
I
have
added
two
pias
that
are,
you
have
to
merge,
but
then
we'll
have
an
updated
readme
and
also
there
is
an
integration
that
needs
to
be
done.
So
I
think
kristoff
and
charles
figured
that
out
yeah.
A
B
Josh
since
it
comes
under
like
what
do
you
say,
my
mentoring,
subproject.
C
Nope
we're
good
okay,
as
far
as,
if
there's
something
on
there
as
a
permanent
thing,
it
can
just
be
removed.
Okay,.
A
Yeah,
it
just
says:
steering
committee
support
in
the
template,
so
just
slap
an
n
a
on
it.
At
least
we
went
over
it
new
items.
Last
week
we
were
talking
about
the
contributor
celebration.
This
morning
I
banged
out
real
quick
comms
for
a
comms
update
for
that.
Let
me
get
the
link
to
it
in
case
folks
want
to
see
it
so
many
md
files,
hack,
md
files
open.
I
can't
find
it
so.
That's
fun.
A
We
have
awards
to
figure
out.
We
have
the
the
devops
party
game
happening
to
bake
off
if
you're
interested,
please
sign
up
all
those
things
are
in
flight
right
now
and
they
found
the
link.
C
That
actually
reminds
me
for
the
awards,
which
would
be
a
great
person
to
work
with
on
this,
would
be
to
stage
all
the
tweets
for
the
awardees.
D
D
We
do
and
I've
tried
to
look
for
twitter
handles
already.
I
have
not.
Everyone
has
twitter
handles
so.
A
In
that
case,
I
think
it's
safe
to
just
put
their
name
right
like
if
they
don't
have
twitter
at
all.
Just
put
their
name
right
and
just
say
thank
you
for
your
support,
move
on
right,
like
if
you
can't
find
it
after
the
first
search
or
two
don't
spend
more
time
on
it
than
that
who
should
we
share
that
list
with,
or
I
mean
me
and
caslin,
have
typically
been
the
twitter
peoples.
Okay,
I
think
that's
safe
to
say
that
anybody.
C
A
A
A
C
Actually
other
thing
on
the
subject
of
tweets
is
the
twitter
automation
broken.
I
remember
seeing
a
message
around
that.
B
The
thing
is,
after
the
change
from
the
master,
to
main
I
guess
there
is
an
issue,
the
the
automation
is
not
working
and
the
moment.js
or
tweet
that
has
to
go
manually
yeah.
I
was
just
going
to
mention
that,
so
there
is
a
pr
that
we
merged,
but
it
didn't
work.
Also
the
issue
creation
isn't
working
then
so
rajula
has
created
this
issue
after
I
pointed
that
there
was
an
issue
like
I
tested
a
few
times
variety
of
ways,
but
it
didn't.
A
C
A
Yes,
okay,
that
I
can
fix
too,
so
I
will
take
that
pr
as
something
that
needs
to
be
done
to
the
forks
I
go.
A
A
C
Email
announcement
I'd
be
doing
it
earlier,
but
was
also
looking
at
the
settings.
B
Regarding
this
contributor
celebration,
I
just
forgot
that
the
blog
post,
like
I
don't
know
what
will
be
there
just.
I
have
put
some
current
content
in
that
you
know
hi
md
file,
so.
B
Yeah
about
the
events
and
activities,
so
I
didn't
had
anything
for
the
devops
games.
I
took
it
from
the
comps
that
you
wrote
just
I
took
from
the
calendars
that
were
available
and
I
don't
know
how
much
descriptive
we
need
to
be
here
or
like.
A
Conscious
about
not
being
too
verboten
in
the
email
so
feel
free
to
be
verbose
in
the
blog
post
right
like
yeah,
I
mean
I
know
I
put
in
a
wall
of
text
to
describe
the
devops
party
games,
but
it
was
literally
the
description
from
their
website.
So
that's
why
I
put
it
in
quotes
and
so
forth
so
on,
and
that
just
makes
sense
to
me,
but
if
you
want
to
shorten
it
feel
free
so
in
the
blog
post
feel
free
to
go
like
as
lengthy
as
you
want.
Just
use.
B
A
C
Oh
honestly,
like
it
might
be
a
good
thing
to
stage
for
like
next
week,
because
we
want
to,
we
will
want
to
send
more
comms
out
next
week
as
well.
So
if
we
send
the
you
know
one
announcement,
we
have
right
now
out
today
and
then
followed
up.
You
know
next
week
with
a
blog
and
more
links
and
potentially
like
any
other
updates,
because,
like
one
other
thing
for
the
blog
post,
that
might
be
good
one
of
the
is
there
still
might
be
a
hackathon,
but
that
we
won't
really
know
till
monday.
C
So
that
would
be
a
good
thing
to
include
as
well
so
I'd
say,
hold
off
on
the
blog
post
to
hey
ray,
which
day
is
the
official
release
day.
Is
it
tuesday,
it's
tuesday
yeah?
So
I
ideally
monday
but
monday,
would
what
monday
would
be
the
ideal
time
to
publish
the
blog
post
because
tuesday,
after
will
be
several
blog
posts,
yeah.
B
I
guess
just
just
skeptical
about
the
schedule.
The
schedule
is
not
prepared
yet
so
we
have
a
link
for
the
schedule
in
the
blog
post.
So
what
do
we
do
about?
It.
D
D
Be
today
and
merged
by
sunday
for
sure,
whatever
the
issue
to
kick
off,
the
freeze
will
be
on
monday,
I'm
not
sure
what
time
but
typically
24
hours
so
usually
monday
morning.
C
A
C
A
One
thing
I
noticed
this
week:
well,
sorry
completely
tangential.
Are
we
done
with
this
conversation?
Well.
C
I
think
the
the
one
thing
with
code
freeze,
I
would
still
like
in
a
lot
I
would
probably
opt
to
publish
it
on
the
kids.dev
blog
instead,
is
that
sort
of.
B
C
It
could
be
better
okay,
so
that
just
that
removes
the
code.
Freeze,
blocker
and
we
should
hopefully
get
like
we'll
know
on
monday
by
the
summit
meeting
whether
there
will
actually
be
a
hackathon
or
not,
and
that
will,
I
think,
will
be
the
either
go.
No
go
for
the
blog
as
is
or
append
and
add
a
little
section
for
the
hackathon.
B
Okay,
all
right
that
works.
Oh
the
block
part,
I
guess
events
and
activities
so
I'll,
add
more
on
to
the
devops
party
games
a
bit
and
the
back
office.
I
guess
fine,
but
like
there's
a
lot
of
instructions
there,
but
instructions
on
who
is
hosting
and
what
the
charges
were
there
last
time.
So
if
we
get
that
on
monday,
we'll
add
them
otherwise
we'll
go
as
it
is.
A
A
B
A
A
A
B
A
A
A
A
B
I
guess
regarding
this:
we
had
a
discussion
in
the
last
last
meeting.
Somebody
started
a
service
process
without,
like
you
know,
taking
the
official
like
there
is
something
boss
mentioned
about
it
and
he
was
quite
skeptical
about
like
we
should
send
comps
to
all
the
six.
B
Regarding
that
we
have
a
server
process
and,
like
this
thing,
is
not
visible
to
people,
so
that
was
the
main
agenda
of
the
end
this
issue,
so
I
don't
know
how
do
we
solve
it
and
like
that's
why
I
guess
no
one
is
assigned,
because
there
was
no
clear
cut
for
you
on
how
to
like
work
on
this.
So
I'm.
C
Going
to
thank
sorry,
no
go
ahead.
Bob
one
follow-up
on
that
one.
That
survey
should
never
have
gotten
like
the
that
should
have
gotten
shut
down
by
the
blog
team
immediately.
It
never
should
have
been
even
considered
so
that
the
it
was
from
an
external
party.
It
was
associated
with
a
specific
vendor
and
it
was
a
very
badly
phrased
survey.
C
A
A
We
have
like
we
have
a
issue
template
right,
for,
if
you
want
a
tweet
here's
how
to
do
it,
it'd
be
nice.
If
we
had
do
you
want
a
survey
and
like
that
was
either
like
an
open
issue
here
in
the
when
I
say
here,
I'm
looking
at
the
requesting
survey
doc
there,
there
is
actually
an
issue
template
for
requesting
a
survey.
A
C
A
C
A
The
thing
that
happened
have
happened.
Yes,
shouldn't
have
happened.
It
might
be
good
just
in
our
repo
to
literally
copy
pasta.
What's
here
on
this
case.dev
link
and
just
tell
people
to
go
to
that,
do
you
need
a
survey
there's
already
a
process
for
that
code
here,
yep,
so.
A
A
A
A
All
right,
if
anybody
want
to
take
that,
take
that
card
and
go
with
it,
so
let
me
know
I
will
help
you
if
you
need
it,
if
you
don't
know
how
to
take
it
over
an
issue
and
run
with
it,
let
me
know
I
can
also
help
you
with
that.
So
that's
there.