►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting 20200205
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
all
happy
friday
welcome
to
the
upstream
marketing
meeting.
We
all
know
each
other,
but
for
posterity's
sake
I'll
say
we
we
follow
the
code
of
conduct
of
kubernetes,
which,
in
short,
is
be
excellent
to
each
other.
Please
add
yourself
to
the
agenda,
notes
and
add
any
agenda
items
you
have
on
your
mind.
A
Otherwise,
we'll
go
through
our
evolving
agenda
format,
which
hopefully
yeah,
I
think
is
pretty
fun,
and
I
guess
you
do
too,
or
you
wouldn't
have
shown
up
so
thanks
for
that
kick
off
from
the
start.
Normally
we
cover
any
big
wins
or
ways
in
which
the
marketing
community
was
able
to
help
other
parts
of
kubernetes
or
get
a
message
out.
A
A
I
have
a
to-do
of
taking
our
new
structure
and
adding
it
to
the
github
board.
We
don't
do
one-to-one
if
every
idea
as
a
github
issue,
it
gets
messy
very
quickly
and
it's
a
pain
for
the
release
team
to
manage
so
trying
to
set
that
up
on
a
rev2
in
the
meantime,
just
keeping
it
all
in
sync
here
in
our
dock.
A
So
why
don't
we
just
start
right
from
the
top?
You
know
a
brief
recap,
like
the
the
psp
article.
A
Is
it's
the
first
time
we're
really
we're
trying
to
get
a
message
out
before
we
have
all
the
answers
and
I
think
that's
very
clear
from
the
the
conversation
around
it
and
I
just
want
to
say
like
that
is
a-okay
like
we
are.
We
are
new
we're
trying
to
be
helpful
and
that
will
mean
being
patient
and
conversational
quite
a
bit
along
the
way
and
trying
to
like
draw
some
clear
scope
to
different
articles
so
that
we
can.
A
We
can
iterate
on
them
without
too
many
people
being
involved,
but
yeah
that
will
that
will
be
a
process
that
we
learn.
So
bob
anything
come
to
mind
for
you
that
you
want
to
jump
into
on
this.
B
Not
too
much
right
now,
the
the
big
thing
that
I
think
happened
was
just
like.
There
were
a
lot
of
different
people
working
on
sort
of
the
like
looking
into
doing
something
similar
and
the
story
hadn't
quite
firmed
up
in
sig
off
itself,
which
is
what
I
think
led
to
at
least
some
the
you
know
not
necessary
confusion,
but
the
parallel
efforts
to
sort
of
do
the
to
get
something
out
there.
C
Mean
I
take
some
of
the
blame
here.
I
I
did
notify
divya
that
okay,
there
is
already
article
in
progress
and
we
talked
to
cigars
and
those
folks
jumped
in
and
everything.
So
what
I
am
thinking
is
probably
we
should
have.
C
I
don't
know
I
mean,
as
you
said
right
probably,
we
should
have
a
clear
scoping
of
what
goes
into
for
the
release
comps
and
what
exactly
comes
into
contributor
count,
because
this
looks
like
something
that
the
leaves
comp
would
want
to.
Do
I
mean
it's
a
release,
feature
right.
Do
we
want
to
do
that
as
well
or
how
to
take
that?
B
I
I
think
that
there
there
definitely
should
have
been
like
more
more
communication
between
the
release
team
and
the
contributor.
Comms
is
a
good
idea,
and
I
think
it
was
yesterday
in
p.m.
Where
I
was
talking
I
had
mentioned,
we
should
add
contributor
comms
to
the
release
channels,
so
that
way
it
can
be
tagged
in
the
other
ones.
B
The
other
thing
that,
like
I
think,
would
be
a
great
idea
in
general,
is
if
contributor
comms
winds
up,
also
helping
the
release
comms
team
when
it
comes
to
proofing
and
editorial
work
for
their
posts
and
and
the
earlier
that
starts
the
the
better,
especially
after
la
I
think
it
was.
B
I
don't
remember
if
it
was
last
cycle
or
119
cycle
where
all
the
posts
came
in
like
just
a
couple
days
before,
and
it
was
real
hard
as
a
like
blog
review
member
to
like
get
those
in
and
get
those
out
on,
the
the
the
in
the
time
that
was
required,
and
I
I
like
there's
a
lot
of
overlap
between
the
blog
sub
project
and
sort
of
some
of
the
efforts
a
contributor
comes
so,
like,
I
think,
it'd
be
great.
B
Like
you
know,
if
you
know
matt
castle
and
a
couple
of
the
the
other
people
would
be
interested
in
being,
at
least
you
know,
reviewers,
for
for
the
blog
and
getting
more
looked
into
the
release
team,
some
of
the
release
processes,
I
guess
or
like
the
comms
processes
around
it.
A
Okay,
so
maybe
we
can
take
a
a
step
back
to
clarify
so
the
initial
goal
of
writing
this
psp
article-
it
was.
It
was
a
working
session
a
couple
weeks
ago,
bobby
brought
up
that
it
was
an
important
change
and
maybe
an
opportunity
for
us
to
get
ahead
of
a
message
that
might
be
confusing
to
people,
and
you
were
already
starting
to
see
signs
of
that
confusion
in
the
community.
B
I
I
think
so
I
know
that
there
are
a
couple
tweets
going
about.
I
said
I
have
to
go
back
and
watch
the
recording
and,
like
you
know
I
I
was
the
one
too
that
likes
well.
Chris
mentioned
the
psp
thing
and
we
brought
it
up
in
in
the
in
the
meeting
as
it'd
be
a
good
thing
to
do
so,
like.
B
I
don't
know
if
I
didn't
realize
too,
that
the
release
team
was
already
working
on
something.
A
B
A
B
The
one
thing
sorry,
oh
you're,
good.
A
Yeah,
I'm
just
I
was
just
trying
to
do
like
a
little
bit
of
a
retro
of
like
how
do
we
get
here?
A
What's
our
what's
our
a
healthy
objective
to
go
forward
yeah
like
because
if
the
answer
is
like
hey,
it's
not
the
right
time,
we're
not
the
right
writers,
let's
kill
the
pr
and
convey,
but
I.
B
I
actually
like
really
like
the
phrasing
some
of
the
stuff
in
the
pr.
What
I
think
would
what
might
be
better
is
if
the
sig
off
and
sig
security
are
still
sort
of
teasing
out
which
proposal
they
want
to
go
through
because,
like
they
actually
are
working
on
a
potential
replacement
for
psps
and
they
start
deciding
which
avenue
they
want
to
go
right
now,
and
I
suspect
that
they
will
like
that.
They
will
have
that
done.
B
You
know
we
can
ping
like
jordan
or
tim
and
to
see
like
if
when
they
expect
to
sort
of
know
which
way
they're
going,
but
if
they
lean
towards
you
know
one
proposal,
other
that'd
be
a
great
thing
to
toss
in
there.
Just
like
you
know,
we
are
looking
at
a
as
an
essentially
an
in
a
kubernetes
native
potential
replacement.
B
But
like
honestly,
the
blog
post
is
great
as
written
it's
it's.
I
I
think
it's
a
little
bit
more
feelings
than
anything
that
else
that
got
wrapped
up
in
the
in
in
some
of
the
the
psp
post
or
the
the
stuff
around
the
psp
post.
B
No
yeah,
just
I
I
think
you
know
people
were
put
back
just
because
there
were
simultaneous
efforts.
Some
people
were
involved
in
different
ones.
B
A
Yeah
yeah
in,
like
my
my
takeaway,
was
like
my
perception
of
the
perception
which
is
getting
into
dangerous
territory,
but
the
idea
being
that,
like
publishing
a
post
that
doesn't
offer
a
recommendation
on
what
replaces
psp
will
cause
more
concern
than
not
publishing
it.
B
Yes,
yeah
because,
like
part
of
it
is,
if
you
go
look
at
like
all
the
security
best
practices,
they
tell
you
to
use
psps.
B
In
fact,
it's
even
part
of
like
the
csi
score
for
which
is
like
a
I
think.
It's
government
run,
but
essentially
it
establishes
a
security
score
for
your
thing
and
how
to
basically
do
security
right
and
like
psps
are
part
of
that.
So
I
think
that
you
know,
at
least
in
this
case.
Without
you
know,.
B
A
A
I
feel
like
you're
at
the
the
intersection,
not
in
a
it's
your
fault
way
like
as
a
you're
in
the
best
place,
to
recommend
some
next
steps.
So,
what's
standing
up
to
you.
C
Right,
I
mean
the
way
I
see
it
is
for
release
specific
thing.
The
only
thing
I
believe
is
we
can
wait
till
enhancement.
Freeze,
I
mean
that's
the
point
where
we
get
a
bit
clearer
picture
of
what
exactly
is
going
in
the
release,
or
you
know
I
mean
I
know
we
don't
get
to
know
until
code
freeze,
but
at
least
still
enhancements.
C
We
get
to
know
that
you
know
these
things
are
changing
and
at
that
point
we
can
at
least
you
know,
link
about
those
kps
that
okay,
you
know
this
is
something
that
is
that
might
happen
this
leader
that
might
not
happen
or
whatever
it
is,
but
at
least
we
have
something
to
throw
out
right,
rather
than
just
saying
that
okay
psp
is
deprecating,
we
don't
know
what's
going
to
happen
next,
but
at
least
by
that
time
we
would
have
some
idea
of
you
know
what's
going
to
happen
next,
does
it
happen
in
this
release?
C
Does
it
happen
in
next?
Is
you
know
that
again
depends
on
how
fast
that
code
goes
in,
but
I
mean
in
general
for
related
blocks.
I
think
that
makes
more.
C
I
think
I
think
this
looks
good,
as
I
guess
bob
mentioned.
Probably
we
could
just
wait
a
couple
of
days
until
segat
has
a
clear
idea
of
what
they
are
gonna
do
next
and
once
we
have
that
we
can
just
mention
that
and
wash
it
out.
I
don't
see
any
other
constraint
from
the
release
comp
side.
At
least
I
mean
we
are
good,
as
as
release
calm,
we
are
happy
that
you
know
the
blog
is
up
and
you
know
ready
to
go
out.
B
One
other
possible
thing
on
that,
too,
is
like
if
sigoth
wants
more
opinions.
That's
just
like
you
know.
Sigoff
is
evaluating
two
proposals
as
potentials
entry
replacements,
we
would
love.
You
know
if
you
are
interested
in
this,
please
either
come
to
our
meetings,
see
this
mailing
list
thread
or
comment
on
our
docs,
so
that
might
be
something
to
poke
like
jordan
or
tim
about.
B
If
they'd
like
to
potentially
solicit
more
public
opinion
on
it,.
A
Cool
okay,
moving
along
other
sort
of
campaigns
in
progress
and
well
within
our
control,
which
is
a
nice
distinction.
It
are
the
contributor
stories,
so
we've
gone
on
a
series
of
steps
to
for
people
to
share
their
story
of
like
how
they
contribute
first-person
narratives.
How
do
they
do
their
thing?
And,
oh,
I
definitely
mix
some
of
them
up
looks
like
one
of
those
stories
in
here
is
bob
eventually
sharing
how
kubernetes
is
shifting
to
async
meant
to
have.
A
Chris
short
has
one
on
how
he
contributes
quote
unquote
as
a
non-code
contributor
and
then
ph
offered
a
great
one
on
his
journey
that
we're
gonna
zoom
in
on
I've
got
mine,
that's
ready
for
somebody
to
review
on
being
a
maintainer
in
four
hours
a
week
kind
of
that
pitch.
A
I
think
we're
at
a
point
where
chris's
is
ready
for
a
pull
request,
and
it's
on
me
to
to
do
that.
Unless
somebody
else
wants
to
volunteer
too,
I
need
a
reviewer
for
mine
and
ph
needs
some
copy,
editing.
E
Being
new,
I
feel
that
I
can
take
on
copy
editing
without
messing
anything
up.
So
let
me
let
me
do
a
copy
edit
task
for
you.
Yeah.
A
And
when
we're
on
the
on
that
first
run,
we
were
looking
for
flow
grammar.
You
know,
if
you
know
everyone's
gonna
have
their
own
unique
style,
but
definitely
like.
If
it
just
the
parts,
don't
make
sense
or
like
hey,
you
jump
from
a
to
b.
I
don't
know
how
you
got
to
b.
Could
you
put
a
plus
in
there
would
be
great,
so
I'll
write
you
down
as
do
a
copy
edit.
For
me,
that's
wonderful.
Thank.
A
Oh
she's
settling
into
the
lap
we're
good
now
great,
and
this
is
a
future
just
knowing
that
we
started
a
dock
with
bob
on
his
work,
to
move
towards
more
asynchronous
communication
in
in
our
sig,
which
will
be
really
cool,
but
no
action
required
right
now
and
then
non-article
campaign.
That's
in
progress
would
be
a
the
contributor
survey.
Rajula
has
been
supporting
that
any
updates
on
on
where
they
are
in
the
process.
B
B
A
F
B
It's
just
honestly
me
or
josh,
going
into
the
cncf
surveymonkey
account
and
actually
doing
the
survey.
But
after
that,
that's
when
we
can,
we
start
blasting
out
coms,
okay
and-
and
that
will
be
one
that
we
do
want
to.
You
know
hit
every
sig
list
individually.
B
The
only
thing
that
I
would
definitely
like
hold
off
on
is
we
don't
send
it
out
before
enhancements.
Freeze,
okay,
so,
let's
see
freeze,
I
think,
is
yeah,
so
we
we
would
probably
hold
off
to
sending
out
until
the
10th
at
the
earliest,
because
everyone's
gonna
be
focused
on
enhancement
sprees,
which
is
tuesday.
B
A
B
No
okay,
I
didn't
realize
I
was
unmuted.
Oh.
A
No
you're
good,
okay
cool
the
next
sort
of
area
we
go
into
is
or
if
there
are
any
inbound
requests
for
marketing
to
help
out
in
different
places
and
any
anyone
know
of
anything
new.
Let's
come
up.
C
D
F
F
A
Okay,
so
yeah,
it
requests
a
message:
it's
from
wren
who
contributes
to
our
marketing
community.
It
is
related
to
their
work,
and
you
know
I
don't
think
we've
we've
come
up
against
like
the
the
work
and
contributor
space
too
much
just
want
to
leave
some
space
to
talk
about
it
like
our.
B
This
one,
I
honestly,
don't
know
we've
I
was
looking
through
the
main,
the
kate's
contributor
account
and
I
don't
think
we
like
we've
like
we
have
not
tweeted
anything
that
directly
features
like
someone
else.
That's
not
kubernetes
like
a
kubernetes
sponsored
event
in
some
way,
shape
or
form.
A
A
Okay,
so
kind
of
past
presidents
is
tbd
but
leaning
towards
we've,
we've
stuck
to
vendor
neutral
messages.
I
guess
it
would
be
not
webinars
related,
even
if
it
is
related
to
contributing
today.
B
A
Says
we
we
can't
and
but
we
can
certainly
use
our
discretion,
let's
I'll
respond
to
the
initial
poster
and
let's
give
it
another
24
hours
from
this
conversation
to
see.
If
there
are
no
further
points
made
by
our
community
of
contributors,
then
we'll
move
forward
and
and
if
we
do
have
questions
like
we'll
we'll
address
them.
Does
this
thing.
B
B
A
A
My
my
bias
would
be
to
be
comfortable
celebrating
that
that
rin
is
speaking
on
their
contribution
to
contributor
experience
and
linking
to
it,
but
keeping
vendored
twitter
handles
and
hashtags
that
aren't
relevant
to
us
out
of
it.
That's
not
documented
anywhere.
That's
just
my
past
experience,
so
I'm
very
open
to
the
discussion
there.
C
Again,
my
reservation
is
how
I
mean:
where
do
you
draw
the
line
in
those
cases
I
mean
that
the
talk
is,
I
understand,
the
talk
is
about
contributing
to
kubernetes,
but
most
of
these
talks
in
the
end
actually
turn
out
to
be,
as
you
said
right,
they
might
not
be
vendor
neutral.
C
Somebody
might
be
pitching
something,
and
then
you
know
unknowingly.
We
become
party
to
that
rather
than
you
know,
just
just
trying
a
view
from
our
side.
We
would
want
to
enhance
contribution,
but
that
would
become
a
vendor
pitch.
So
I
don't
know
I
mean
it
feels
like
setting
up
a
bad
precedence,
but
yeah.
A
Yeah
and
that's,
where
being
like,
really
crisp
on
what
the
decision
making
factors
are
like
in
the
ones
that
are
coming
to
mind
for
me
is
like.
Are
you
an
active
contributor
to
say,
contributor
experience
and,
and
if
so,
have
you
requested
that
we
elevate
a
message
and
then
third
like
have
you
confirmed
that
it's
vendor
neutral
enough,
where
it's
appropriate?
A
A
A
B
Yep,
I
I
I'm
a
little
uncomfortable
with
it
in
in
general
because,
like
even
think
about
the
scope
of
it,
as
like
google
does
a
thing
called
like
google
open
source
live,
they
did
a
kubernetes
one
where,
like
everything
about
it,
was
essentially
upstream
kubernetes,
and
you
know
that
was
something
we
did
not
like.
B
A
Okay,
so
if
we're
so
bob
in
the
context
of
you
know
as
a
subgroup
for
sick
contributor
experience
like
I
feel
like
this
is
one
of
those
decisions
that
I
understand
correctly
shouldn't
be
made
in
real
time
on
a
meeting,
so
that's
more
inclusive
of
other
members
contributing.
Is
there
an
appropriate
channel
to
should
I
message
this
out?
Is
there
well?
What's
the
right
pathway
there
would
you
say.
B
The
one
thing
that
I
should
also
do
is
poke
the
other
leads
yeah.
I
think
they
will
sort
of
be
alive,
but
yeah
either
way
there
should
be
a
artifact
someplace
of
of
that.
That's
not
not
in
the
meeting.
A
Yeah
I
mean,
as
a
result
of
the
conversation
on
that
issue,
we
could
open
a
pr
that
clarifies
that
further
in
the
social
media
guidelines,
like
so
yeah.
F
A
Definitely
get
a
permanent
item
from
it.
I
just
want
to
make
sure
we're,
including
I
feel
like
if
we're,
including
the
leadership
of
the
sub
group.
It
should
be
sufficient
to
make
a
decision.
We
have
rajula
kazlin
yish
yumi,
it's
pretty
pretty
much.
The
gang
paris
advises,
so
maybe
we'll
we'll
add
at
them
as
well.
F
D
A
A
Good,
okay,
moving
right
along
a
conversation
from
the
contrib
x
meeting
on
wednesday
was
talking
about,
like
you
know
what
happened
to
sig
profiling
like
the
kind
of
sig
blog
posts
that
were
featuring
them
if
they're
wha.
What
and
what
could
happen
in
the
future
just
want
to
bring
that
up.
An
interesting
idea
popped
up
out
of
there,
but
you
know
I
also
want
to
take
a
second
like
caslin.
A
You
did
more
of
those
than
anyone
else,
so
I
think
you
did
two
and
they're
out
of
the
40
or
so
that
were
listed.
I
think
you
did
the
most.
D
D
D
A
Yeah
those
basically
like,
if,
if
so
an
idea
that
came
up
was
like
what,
if
we
did
something
that
kind
of
do
from
an
article
point
of
view
for
my
day,
job
where,
like
we
have
a
long-standing
dock
of
like
all
the
different
sort
of
headline
devices,
we're
going
for
and
leave
room
for
people
to
be
quoted.
A
A
So
either
you
as
a
lead
or
delegate
to
somebody
else
add
a
few
lines
in
there
and
we'll
turn
it
into
an
article,
see
if
maybe
centralizing
it
could
give
it
some
more
momentum
and
basically
like
it's
a
little
bit
of
a
buckshot
approach
like
we
send
it
to
everybody
and
let
them
opt
in
and
we
we
go
to
where
people
are
are
showing
up
as
opposed
to
feeling
like
we
have
to
chase
down
one
at
a
time.
D
A
Okay
cool,
so
I
think
the
action
so
I
I
signed
up
for
the
action
of
bringing
it
up
today,
so
I'm
going
to
check
that
box
in
my
head.
I
think
the
next
step
would
be.
I
don't
have
the
issue
in
front
of
me,
but
there's
an
issue
that
lists
every
single
sig
I'd
be.
I
would
love
to
turn
that
into
like
h2
or
h3
headers
in
a
google
doc
and
like
with
a
table
of
contents
at
the
top
and
like
some
text,
saying
like
what
we're
trying
to
do.
A
It's
like,
if
you're
interested
in
an
article
about
you
and
add
some
of
your
thoughts
here
and
message
us
here.
You
know
it's
all
pretty
vague.
It's
just
like
a
I.
Some
sort
of
structure
needs
to
go
around
it.
If
anyone
would
either
want
to
either
collaborate
with
me
on
that
or
feel
like
that,
somewhat
coherent,
rambling
isn't
enough
to
go
from.
D
A
A
Cool
all
right,
we're
at
the
sort
of
improvements
and
recurring
items
tail
end
of
things.
I
haven't
quite
adopted
that
and
I
keep
tidying
up
this
agenda
as
we
go.
We
have
a
couple
bots.
We
use
one
of
them
regularly
any
any
sort
of
updates
or
things
in
progress
there
that
we
should
talk
about
on
the
infrastructure
side.
A
Cool
any
major
events
happening
on
the
calendar
where
we
should
respond
by
tweeting
or
posting
or
emailing
more
frequently.
A
B
The
release
team
has
has
been
sending
stuff
out.
The
only
thing
that
would
probably
be
worth
would
be
getting
an
additional
tweet
out
about
it.
B
This
is
like,
I
think
we
talked
about
a
long
time
ago,
but
having
some
templates
for
some
of
the
big
like
release
milestones
for
various
tweets,
and
all
that
would
be
awesome.
Just
that
was
just
like
enhances,
freeze
is
coming
up.
It's
this
date
hit
the
button.
Do
the
thing.
A
B
B
C
I
guess
this
year
they
have
enhancement
as
opt-in
right,
so
people
have
to
add
their
announcements
to
attacking
sheet,
and
only
those
enhancements
would
be
tracked.
So
it's
not.
I
mean
it's
not
a
polling
kind
of
a
thing.
It's
more
of
you
know.
People
have
to
tell
that.
Okay,
these
are
the
announcements
we
want
to
finish
in
this
release.
So
there
is
a
tracking
sheet
if
anybody
can
go
and
edit
that
that's
that's
the
idea
and
just
to
add
to
that,
we
are
doing
the
same
for
release
comms
as
well.
C
A
Okay,
I
think
the
next
step,
if,
if,
if
you
could
write
a
first
draft
tweet
of
what
you
just
said
about
the
the
blog
and
bob,
if
you
can
extend
on,
is
there
somewhere
to
link
that
talks
about
enhancement
freeze,
there
must
be
somewhere.
A
Okay,
okay
and
then,
but
if
those
come
together,
send
them
over
to
caslin
and
she'll
queue
them
up.
Maybe
we
archive
them
in
the
contributor
tweet
repo
for
later
reference-
or
I
don't
know,
you're
better
at
documenting
this
stuff
than
I
am
pop
it
where
you
think
would
make
sense
for
reuse.
D
A
A
D
There
are
some
that
I
haven't
put
in
yet
because
I've
been
in
an
event
all
week
and
it's
been
very
tiring,
but
I
have
three
tweets
that
I
need
to
get
into
the
tweet
repo
which
are
about
kubecon
scholarships,
the
addition
of
pronouns
and
the
slack
awesome
joel
you
have
that
on
here
today.
I
need
to
remember
to
do
that
myself,
so
I
enjoyed
seeing
that
and
then
crd
and
admission
web
hooks
there's
a
thing
about
that
that
I
need
to
tweet.
D
So
I
have
a
list
nice,
hopefully
later
today
I
will
get
those
drafts
into
the
repo
at
least,
and
some
of
them
can
be
later
than
others,
so
we'll
figure
out
when
to
hold
and
when
to
push
and
get
that
all
done.
A
A
It
might
be
worth
doing
out
of
the
hand
on
on
hootsuite.
F
F
A
Yeah
open
issues
possible
for
tweet
to
embed
media
and
I've
got
some
pictures
of
it.
Rajula
looked
into,
it
seems
like
the
card.
Support
has
to
be
enabled
from
the
website
through
html
tags,.
A
F
A
Well,
okay,
you
can
close.
That
issue
then
sounds
like
you
already
solved
the
problem
and
or
maybe
actually
a
pr
to
the
read
me
say
like
mentioning
that
if
there's
a
maybe
like
an
faq
section.