►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting 20210618
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
y'all
welcome
to
upstream
marketing
meeting.
We
all
know
each
other
if
you're
watching
this-
that's
strange
but
good
for
you,
but
welcome.
A
What's
going
on
folks
any
I
I've
been
a
little
out
of
touch
in
the
last
week
or
two
got
some
stuff
going
on,
but
so
I
missed
any
big
news.
We
want
to
highlight
up
front
anything.
That's
been
cool
to
note.
A
What
yeah
thanks
yeah,
that's
partly
my
out
of
touchness,
I
I
was
signing
off
to
go
on
vacation
and
was
asked
to
jump
on
a
call
and
you're
like
well,
this
isn't
official
official.
Yet
but
yeah
I
got
a
a
good.
I
went
from
helping
run
an
editorial
to
running
the
whole
team
of
four
editorials
and
and
how
we're
connecting
into
a
growing
marketing
team
and
I'm
really
pumped
about
it.
It's
what
I've
been
wanting
to
do.
So.
Thank
you
very
much.
A
Yes,
yeah
yeah
I've
got
a
good
gig
at
red
hat.
I
like
what
we're
doing
what
else
is
going
on?
So
I
think
you
know
kubecon
is
is
cruising
along.
Is
anyone
either
heard
back
from
talks
or
do
on
the?
Well?
I
should
say
I'm
on
the
selection
committee
this
year,
which
is
pretty
cool,
so
I'm
I'm
reviewing
a
hundred
of
the
proposals
for
the
101
track
right
now,
so
that's
kind
of
neat.
Anyone
else
got
stuff.
They
need
to
do
for
kubecon
or
yeah.
What
are
you
doing.
A
I
love
it.
I
I
love
when
you
can
turn
give
people
an
honor
which
is
really
just
homework.
C
C
I've
been
working
with
this
other
group
to
like
help,
share
more
kubernetes
or
help
the
cncf
share
more
stories
about
folks,
achieving
business
outcomes
with
cncf
stuff
and
anyway
so
10.
At
the
same
time,
they
created
this
like
track
to
do
this
business
value,
business
value
like
stuff
and
then
we're
trying
to
get
involved
in
the
bit.
We
being
there's
this
business
value
subcommittee
under
marketing.
C
B
On
big
wins
for
that
are
actually
specific
to
this
group,
I
I
feel
like
usage
of
our
contributor
coms
handle
within
slack,
has
really
increased
recently.
I
know
josh
burkus
has
used
it
a
couple
of
times
ian
used
it
this
week
and
someone
else
whose
name
on
slack,
I
think,
starts
with
an
s.
I'm
gonna
have
to
go
back
and
check
used
it
to
help
to.
Let
us
know
that
they
wanted
to
promote
something.
C
What
are
we
like,
because
I
see
that
and
I
wonder
what
in
the
world
what
in
the
world
like?
Should
we
actually
like
do
in
that
half
like
right
now,
I'm
like
oh
well,
I
won't
worry
about
it
because
caslin
will
handle
it,
which
is
definitely
like,
definitely
reduces
personal
mental
pressure,
but
doesn't
also
feel
like
the
right,
like
necessarily
the
right
way
to
have.
This
go
long
term.
B
I
think
if
you
feel
like
answering
the
question
and
trying
to
help
you
can
always
pull
someone
else
in
if
it's
an
ask
for
something
that
you
don't
know
how
to
handle
or
want
help
handling,
but
I
think
feel
free
to
respond
if
you're
there
and
feel
like
it,
that's
kind
of
how
I've
been
looking
at
it.
What
do
you
think.
A
D
C
B
Have
a
note
in
our
in
our
meeting
notes
that
we'll
go
over
what
ian
wanted
a
little
later.
C
D
E
D
A
Yeah,
I
think
you
know
I
could
see
how
you
could
handle
this
if
we
were
doing
like
a
full
full
bore
team
system
around
it
of
having
like
an
on-call
rotation
or
like
a
auto
assigner
when
somebody
gets
added
for
that
for
people
to
follow
up,
but
I
think
we're
on
the
very
opposite
end
of
it
where
it's
like.
We
set
this
thing
up,
so
people
could
contact
us,
they
haven't
and
now
they
are,
and
it's
a
first
come
first
serve.
A
A
But
I've
realized
like
like
something
I'm
reorienting
this
week
in
response
to
that
is
like
I've,
de-prioritized
slack
and
prioritized
kind
of
content
for
our
team,
but
I'm
realizing
like
the
more
valuable
thing
I
could
do
with
my
time
is
to
pay
closer
attention
to
slack
with
the
time
I
have
and
let
the
content
be
secondary,
at
least
for
the
foreseeable
future,
as
people
ramp
up
getting
some.
How
are
you
feeling
about
that?
Caslin.
D
B
Has
been
pretty
quiet
on
slack,
like
I
mentioned,
like
people
haven't
been
using,
the
contributor
comms
handle
that
much,
but
I
do
think
it's
a
great
place
for
us
to
see.
What's
going
on
and
kind
of
catch
up
on
opportunities
for
us
to
help
so
can
relate
to
the
balancing
act
with
people
using
the
contributor
comms.
More,
hopefully,
it'll
get
a
little
bit
easier
for
us
to
see
what
we
need
to
help
out
with.
E
A
Well,
welcome
welcome
we're
just
getting
into
some
some
new
contact
points
from
people,
but
now's
a
great
time
if
you,
if
you
want
to
ask
your
question.
E
Oh
sure,
thank
you.
So
I
was
in
the
community
meeting
yesterday
and
I
missed
one
point.
E
So
there
was
a
post
or
like
and
asked
about
the
duplications,
and
then
there
was
a
tweet
and
at
that
time
it
didn't
hit
me
with
anything,
and
I
was
like
fine,
that's
a
good
way
to
publicize
and
everything,
and
someone
also
suggested
that
it's
a
nice
if
it
would
be
nice
if
we
could
put
a
blog
from
the
release
site
together
and
then
today
my
shadows
started
asking
questions
and
then
it
it
hit
me
like
we
like
the
tweetstargard
awesome,
but
we
also
want
to
make
sure
that
since
we
moved
from
four
releases
to
three
releases
in
a
year-
and
we
haven't
said
anything
from
our
site-
the
release
side
yet
so
we
just
want
to
coordinate
the
next.
E
If
there
are
any
more
tweets
coming
about
the
deprecations,
we
just
want
to
coordinate
and
make
sure
that
it.
These
are
good.
It
will
avoid
chaos,
but
we
don't
want
it
to
actually
cause
chaos.
So
that's
all
it's
not
a
question
per
se.
Probably
it's
a
request
or
ask.
I
should
have
framed
it.
Well,
no.
E
These
are
about
the
api
duplications,
actually,
the
it's
not
even
a
duplication,
it's
the
api
removal,
so
the
features
that
went
ga
already
and
they're
gonna
stop
using
the
beta,
the
beta
api
versions,
and
there
was
a
tweet
that
went
out
yesterday,
which
is
amazing
by
the
way.
Thank
you
for
doing
that,
but
we
just
don't
get
from
the
releases
side.
E
We
also
want
to
get
ahead
and
then
make
sure
that
we
are
doing
something
about
it
and
not
just
like
I
don't
know
we
just
want
to
avoid
more
confusions
or
anything.
We
haven't
said
anything
about
it
to
anyone.
We
aren't
even
tracking
those,
it's
understood
implicitly
that
once
the
feature
goes
ga
and
then
these
apis
will
be
the
bips
will
be
removed.
E
But
now
that
we
are
moving
to
longer
releases,
we
just
want
to
make
sure
if
there
is
any
processes
or
if
we
can
coordinate
between
the
teams
and
stuff
like
that,
if
there
is
an
opportunity
to
improve
the
coordination,
we
are
getting
a
little
better
at
coordinating
with
radio
6
and
everything.
So
I
want
to
throw
that
out
as
well.
B
D
B
Yeah,
so
that
was
a
request
from
david
eads,
who
gave
the
section
of
the
community
meeting
yesterday
about
the
deprecations
he
had
reached
out
to
us
nine
days
ago.
I
see
and
asked
us
to
do
that
tweet,
which
was
mentioned
in
the
in
the
community
meeting
for
everyone
who
didn't
attend.
I
took
notes
at
the
community
meeting.
Okay.
D
B
And
then
safita,
you
were
giving
the
release
team
update
there
right
yeah,
so
our
team,
if
this
is
the
first
time
you've
interacted
with
us,
we
try
to
help
with
communications
that
are
related
to
contributor
work
and
are
directed
at
contributors,
have
to
have
a
strong
contributor
relationship
of
some
form.
B
We
are
trying
to
build
a
stronger
relationship
with
the
release
team.
We've
had
a
couple
of
members
be
on
the
release
team.
I
think
yeah.
B
Yeah,
so
one
of
the
things
we
have
is
the
app
cates
contributors
twitter
account.
We
have
a
github
repo,
which
is
currently
in
a
bit
of
an
awkward
state
as
we
implement
some
new
ottoman
automation,
but
in
that
the
the
purpose
of
that
repo
is
that
it
has
some
automation
to
take
prs
into
it,
we're
working
on
making
it
issues
that
are
put
into
it.
B
Turning
those
into
tweets
once
they're
accepted,
then
they
would
be
tweeted
out
directly
from
that
kate's
contributors
handle
so
that
more
contributors
can
contribute
to
that
and
we
do
a
variety
of
other
things
to
like
helping
with
blogs
and
and
things
like
that,
matt
rajula.
Do
you
want
to
say
more.
A
Yeah
I
mean
we
are
a
subgroup
of
the
contributor
experience
team,
which
you
know,
mission
is
to
make
being
a
contributor
easier
and
more
fun,
and
part
of
that
is
like
there's.
So
many
of
us
and
it's
hard
to
get
information
out
through
all
the
channels.
People
are
looking.
So
the
first
thing
we
did
was
try
to
consolidate
channels
and
help
map
those
out
and
that's
still
part
of
part
of
our
long
term
goal,
but
short
term
like
yeah.
A
Let's,
let's
talk
through
what
we
need
to
do
to
plug
into
the
system,
so
that
you
know
it's
still
not
100
clear
on
how
we
could
be
helpful
in
this
case,
but
that's
completely
fine,
like
we'll
figure
out
what
what
messaging
and
verifications
or
just
cadence
or
whatever
the
right
angle
is.
E
Yeah
definitely
so
I
remember
seeing
the
post
like
nine
days
ago,
I
saw
the
post
on
country
breaks
and
I
was
like.
Oh,
this
is
a
good
thing,
because
I
was
just
thinking
from
one
perspective.
I
didn't
bring
it
up
it,
I
didn't
flag
it.
I
didn't
bring
it
up
to
my
shadows
or
anyone.
I
didn't
talk
to
anyone
about
it,
so
the
post
that
castle
mentioned
on
the
slack
channel-
I
just
simply
look.
I
always
miss
this
meeting.
E
I'm
subscribed
to
the
country
back,
so
I
just
read
through
the
messages
more
or
less
in
a
bulk,
and
I
came
across
this
and
I
was
just
following
that
and
I
was
like:
oh
that's
a
nice
someone
is
reaching
out
and
doing
this
blah
blah
blah
and
then
recently
someone
raised
a
flag
that
do
we
need
to
update
k
website,
because
these
apis
beta
api
is
gonna,
be
remote.
E
I'm
like
yeah,
that's
good,
and
then
I
talk
to
my
lead
shuttles
about
okay,
do
we
have
a
process
for
it
and
there
was
no
process
for
all
those
things.
That's
why
it
didn't
occur
to
me
when
I
was
I
was
in
the
call
yesterday
and
I
was
like:
oh
that's,
nice
blah
blah
blah
I'll
go,
read
you
retweet.
Whenever
the
tweet
comes
out.
So
from
my
I
was
the
same
from
my
perspective
so
and
I
talked
to
more
of
my
team,
and
I
got
to
hear
like
oh
this.
E
Could
this
might
potentially
cause
chaos
or
we
haven't
said
anything?
I
was
really
liking
the
idea
that
from
releases
side,
we
will
also
send
a
blog
out
telling
like
already
the
kubernetes
website
has
duplication
list,
it's
very
detailed
and
they
have
what's
going
to
be
duplicated
when,
but
it's
a
lot
of
change
for
the
contributors
right
now,
because
we
moved
from
three
four
to
three
releases.
E
We
extended
the
deadlines
for
certain
things.
We
for
certain
things.
We
shrink
the
deadlines
which
we
are
learning.
We
are
adapting.
We
are
taking
inputs
from
everyone,
it's
not
even
a
I'm,
just
throwing
all
the
things
out
like
I'm
thinking
like
I'm
thinking
with
all
of
you
because
yeah
I
have
no
marketing
experience.
My
twitter
account
just
has
retweets,
of
course,
retweets
of
kubernetes
stuff.
I
only
created
just
to
read
to
each
community
stuff,
that's
about
it.
I
so
like
you
can
help
us.
E
E
A
So
you
know
pretty
standard
marketing
flow
when
you're
working
with
the
product
is
product.
Roadmap
messaging
has
a
contact
point
with
whoever
product
manager
or
product
owner.
In
this
case
it's
very
much.
The
release
team
is
that
product
point
of
contact,
and
you
know
we,
let's,
let's
talk
through
how
we
do
that.
A
A
So
what
happened
was
like
castle
and
you
were
saying
we
got
a
request
in
on
the
repo
and
you
know,
and
we
tweeted
or
knows
from
contributor
comms
handle.
D
There's
one
other
thing
to
add
here
so
a
while
back
we
had
a
conflict
with
the
psp
block,
so
they
were
just
releasing
working
on
it
and
then
there
was
I
was
working
on
it
and
there
was
push
liaison
and
then
making
sure
of
it.
I
think
we
need
to
make
sure
to
avoid
testing.
That's
right
say
that
one
more
time
or
july,
I'm
just
thinking.
We
need
to
make
sure
that
we
want
to
have
a
conflict
of
people
working
on
the
same
thing
like
we
had
with
the
phps.
A
So
psp1
was
really
fun
because
we
well,
I
mean
we
got
to
star
in
a
in
a
presentation
about
it,
but
the
the
request
came
from
the
team
lead
for
the
this
for
contributor
experience,
so
we
collectively
try
to
write
up
what
we
saw
from
public
notifications,
the
the
team
building.
A
The
feature
said
like
that
is
scarier
than
what
is
actually
happening
because
there's
uncertainty
there,
and
that
was
where,
like
okay
lesson
learned,
we're
not
the
people
to
summarize
it,
even
if
we
could
help
it
get
get
along
faster,
so
we'll
slow
down
and
find
out
like
how
to
connect
with
people
who
are
building
the
feature
so
in
in
this
case.
So
we
got
this
request
on
this
one,
and
we
tweeted
was
the
person
that
requested
it.
In
slack,
are
they
involved
in
in
the
release
team
or
in
the
creation
of
this
feature?.
E
A
Okay,
so
somebody
is
responsible
for
feature
requested
us
to
share
then
update
on
the
feature
yeah.
So
in
my
current
logic,
that
would
totally
make
sense-
and
I
would
say
we
would
probably
send
that
so,
let's
update
the
logic
like
what
cevita
would
have
been,
what
you,
what
would
have
been
an
ideal
way.
We
responded
to
that.
E
So
the
I
really
like
all
the
intention,
everything
about
it.
It
was
more
like
we
had
an
it
heads
up
or
we
just
had
like.
If
we
had
a
netsub,
then
we
would
have
thought
about
stuff
in
this
case.
To
be
honest,
I
I
knew
about
it,
but
it
was
just
me
not
my
entire
team,
so
I
didn't
hear
the
perspective.
E
So
probably
it's
something
that
I
like
actually
that
I
might
have
to
put
in
the
retro
and
fix
it
as
well
a
little
bit
so
but
overall
heads-up
or
like
hey
release,
team
release,
team
or
just
put
it
in
our
we
meet
every
week.
So
just
put
it
in
our
agenda
or
like
we'll
just
bring
it
up
in
front
of
everyone
and
ask
if
they
have
something
to
talk
or
just
make
the
release
comms
team
a
contact
like
they
can
be
the
middle
man.
E
It
doesn't
even
have
to
be
the
entire
release
team,
so
they
can
bring
it
to
the
release
team
and
they
can
channel
back
with
the
contributor
communications
like
going
forward.
We
could
just
make
that
particular
team,
a
liaison
yeah
not
to
overwhelm
them,
because
they
already
have
important
stuff
like
talking
to
cncf
talking
to
everyone,
but
that
would
be
your
best.
That
would
be
the
the
first
go-to
person
because
they
are
already
aware
of
communications
and
stuff.
A
That
totally
makes
sense
that
I
mean
there's
already
a
dedicated
point
of
contact,
but
they
were
out
of
this
standard
flow
in
which
we're
going
right
now.
So
I'm
wondering
you
know
for
that
person
whether
they
would
like
to
be
either
a
added
to
the
contributor
coms
handle
on
slack,
so
they
see
the
messages
we're
sending
to
each
other.
A
That's
a
potential,
but
I
could
also
be
a
little
noisy.
I
guess
it's
not
used
a
ton,
maybe
max
five
times
a
week
or
b
when
something
comes
up
where
there's
a
request
and
it
has
to
do
with
a
feature.
We
have
a
place
to
look
for
them
so
that
we
can
grab
their
name
and
message
them
about
it.
E
So
it
can
go
either
way.
So,
for
my
concern
is
that
I
am
it
they
might
learn
when
I
wouldn't
call
it
noisy,
because
they
are
in
the
release,
comps
team
and
they
are
there
to
learn
and
contribute
and
grow
more.
That's
how
I
see
it
so
the
it
might
not
definitely
be
noisy,
but
it's
a
lot
of
overturn
for
your
team
in
that
way
that
we
would
have
to
update
and
delete
and
update
and
delete
and
update
and
delete
every
cycle.
A
To
actually
yeah
no,
I
actually,
I
consider
I
put
that
in
the
category
of
a
pro,
as
opposed
to
a
con,
because
it
puts
the
onus
on
us
to
actually
know
who
we're
talking
to
over
there
and
yeah.
So
I
I
think,
there's
like
a
little
bit
of
there's
a
feedback
loop
there,
where
oh,
we
have
to
update
this.
That
means
we
know
who
the
new
contact
is:
we've
had
a
conversation
about
them
joining
contributor,
comms
handle
and
it
I
feel
like
it
might
anchor
us
to
that
group.
A
E
Yeah
and
also
we
can
also
add
it,
so
we
can
also
proactively
do
it.
We
can
add
it
to
our
comms
handbook
if
rajula
wants
to
pick
it
up
since
he's
a
comps
team
member
right
now,
I'm
learning
how
to
not
pile
things
on
myself
and
I'm
I'm
becoming
a
little
better.
So
good.
E
Slowly,
I'm
getting
there,
so
I
added
two
comps
teams
handbook
just
to
make
sure
that
the
future
members
are
added
to
or
talk
to,
the
contributing
comps.
Once
we
have
a
like
list
that
we
could
update
or
like
we
could
add
more
details
into
it,
but
we
could
just
add
like
for
for
now
it
could
be
like
a
line.
There
line
item
make
sure
you
sync
with
the
contributor
comms
team
that
way,
since
the
one
is
just
not
in
the
contributor.com
stream.
E
The
onus
is
also
on
the
release
team
that
they
can
like
hey
in
case,
if
we
forgot,
because
every
four
months
there's
gonna
be
new
set
of
people
and
you
all
have
a
lot
going
on,
so
they
can
also
like
nudge,
hey.
We
are
the
newbies
and
we
are
here
and
we
want
to
make
things
better,
so
learn
whatever.
So
I.
A
Love
that
I
think
it
really
connects
us
like,
because
it's
part
of
your
workflow
and
it's
something
we
have
to
do
on
our
side,
which
is
an
immediate
like
a
quick
win
of.
Let's
get
you
hooked
up
into
the
system,
oh
by
the
way,
let's
tell
you
about
how
we
work
it's.
It's
almost
like
a
natural
kick
off
to
that
relationship,
and
then
I
think,
if
we've
learned
anything
in
kubernetes
land,
it's
like
if
you
establish
a
way
of
having
a
relationship.
The
other
stuff
flows,
pretty
naturally.
E
Yeah,
that
will
be
wonderful
and
to
be
like
in
the
start.
Rajula.
Please
correct
me
if
I'm
wrong.
In
the
start,
the
contributor
calms
teams,
like
the
release,
comps
team,
have
relatively
less
things
to
take
care
of.
They
are
getting
their
feet
wet
and
knowing
about
things
so
they'll
have
a
little
more
bandwidth
to
even
know
like
what
contributor
comms
is
doing.
You
know
it's
like
a
really
really
great
opportunity
for
them
to.
E
You
know,
probably
participate
in
the
meetings
or
like
come
provide
like
you
can
even
have
a
column
like
release
updates
once
every
two
weeks
or
like
once
a
month,
come
to
the
contributor
like
this
marketing
team
and
then
talk
about
whatever
they
are
doing
or
what's
going
on
in
our
side,
and
so
I
think,
that's
a
great
opportunity
for
them.
I
also
want
to
be
mindful
hope,
I'm
not
putting
a
lot
of
things
on
their
head
as
well
like
piling
on,
but
this
will
be
this.
A
Exactly
yeah
it's
what
they
signed
up
for
so
like
it's,
it's
it's
additive
value
and
it
would
really
help
us
all
stay
connected
and
and
make
sure
yeah
messages
don't
go
out
as
necessarily
like
as
urgent.
It's
more
like
the
message
is
seen
by
the
right
people
before
it
hits
a
new
channel,
which
I
think
is
the
thing
we're
trying
to
build
into
the
system
right
now
like
go
as
fast
as
we
can,
but
not
so
fast
that
we
miss
an
important
perspective.
E
A
I'm
really
happy
to
hear
that,
like
you
know
the
the
pitch
I've
had
when
I
I
got
involved
in
kubernetes
more
actively
because
paris
had
an
old
issue.
That
said,
we
need
like
a
marketing
team,
and
I
I
love
this
stuff,
because
I
think
great
marketing
is
really
just
good
community
leadership
like
clear
communication,
clear
channels
connecting
people
and
it's
it's
fun
when
we
do
it
well
and
it's
it
turns
into
a
great
talk
when
we
don't.
E
E
That's
so
wonderful,
I'm
like
oh,
I
see
captain's
name,
and
I
also
saw
that
one
of
the
blog
posts
that
he
is
trying
to
write
or
assigned
to
herself
from
like
the
releases
thing
which
was
like
it
was
on
my
plate
and
anna's
nrs,
another
release
team
member
on
both
our
plates
for
two
releases
and
we
haven't
gotten
it
out.
So
I
was
so
excited
when
I
just
clicked
through
stuff
right
now
to
see
I'm
like
oh
yeah,
I
might
just
I
might
just
reach
out
to
castle
later
and
say
hey.
E
These
are
the
things
that
we
had
in
our
mind,
so
just
like
feed
feed
information
so
that
it's
not
burdening
for
you
and
we
all
have
have
the
information,
and
I
just
don't
have
the
right
time
or
right
tool
and
I'm.
So
I
really
want
to
write
something
I
want
to
write
like
a
blog
or
something,
but
I'm
so
bad
at
it.
So
I'm
like
oh.
A
A
A
great
default,
if
you
ever
you're
just
like
I
want
to
write,
but
I
don't
know
about
what
our
default
kind
of
question
for
people
is
like.
Why
are
you
contributing
to
kubernetes?
How
did
you
get
here?
What
does
it
mean
to
you?
What
do
you
want
future
contributors
to
know
about
it?
I
mean
that's,
got
like
a
really
nice
beginning
middle
and
end
story.
A
It's
your
personal
experience,
so
you
can't
be
wrong.
So
it's
like
a
really
it's
a
great
way
to
kind
of
get
get
your
feet
wet
with
the
the
storytelling.
A
E
A
We,
this
is
the
best
when
we
can.
Actually,
you
know,
help
another
team
inside
kubernetes
like
we
keep
showing
up
every
friday.
We
talk
amongst
ourselves.
We
know
each
other
pretty
well,
but
like
we're,
always
hopeful
that
people
show
up
and
need
help.
So
thank
you
for
showing
up
that's
hard
to
add
to
the
calendar
and
very
helpful
go
for
a
castle
and
before.
E
B
Yeah
there's
one
other
thing.
I
want
to
add
to
our
notes
and
general
awareness
that
I
heard
here,
which
is
in
which
I'm
connecting
back
to
the
community
meeting.
We
talked
about
the
kep
in
the
community
meeting.
That
is
about
kind
of
restructuring
the
schedule
of
releases.
We
talked
about
we're
having
three
releases
now
and
how
that's
changing
part
of
the
cap
was
also
planning
out
the
release
schedules
farther
in
advance.
B
So
there
are
a
few
changes
that
are
going
on
there
and
I
think
that's
a
really
important
point
for
us
to
both
coordinate
with
the
release
team
on
and
to
help
communicate
to
contributors.
So
I
want
to
make
a
point
for
us,
as
the
contributor
comms
team,
to
work
with
you
all
at
the
the
release
team
to
help
communicate
those
changes
that
are
in
that
cap
and
that
are
happening
to
your
cycle
to
contributors.
It
doesn't
have
to
be
an
immediate
thing,
but
something
that
we
should
keep
an
eye
on
and
work
together
on.
E
That
would
be
nice
and
to
castlen's
point
so
they
want
to
publish
so
there
are
works
in
progress,
or
at
least
I
know
if
you
wanted
to
sign
up
for
it
I'll
give
you
the
name
so
that
it's
jeremy
and
james,
I
will
send
you
the
slack
handles
they
are
working
on
the
blog
and
it's
not
gonna
go
in
the
release.
E
It
doesn't
come
under
release
at
all,
so
they
want
to
publish
out
of
band,
but
they
are
working
on
it
point
final
contact,
so
I'll
send
send
the
idc
on
slack
or
probably
I'll,
just
maybe
open
a
dm
and
then
say
like
hey.
I
had
a
chat,
blah
blah
blah
whatever
and
if
I
could
find
the
post,
I
think
I
thought
they
created
an
issue
but
they
haven't.
But
if
I
find
the
issue,
I'm
gonna
send
it
your
way
so
that
you
are
aware
easy
to
track.
A
E
We
should
just
add
it
somewhere
like
if
you
have
something,
if
you
want
a
blog
and
if
you
want
the
marketing
team
to
be
involved.
This
is
the
process
go
through
this
process.
You
know
yeah.
A
Good,
well,
I'm
really
excited
about
that.
So
do
you
want
to
keep
cruising
along
the
agenda?
Does
that
sound
good?
Okay?
The
steering
issue,
I
think,
is
up
next
caslin.
Did
you
add
this
or.
B
Yeah,
oh,
is
this
about
the
the
contributor
report.
B
Yeah
she
pointed
me
to
this
last
week.
The
report
wasn't
out
yet
I
think
it's
out
now
we
talked
about
it
in
the
contributor
community
meeting
the
monthly
meeting.
So
I
think
that
that
report
is
out
now
she
asked
us
to
watch
out
for
the
blog
to
come
out
so
that
we
can
tweet
about
the
blog
coming
out.
If
we
look
at
our
meeting
notes
from
last
week,
there
might
be
more
notes
from
our
conversation
with
paris
on
that,
but
yeah.
B
A
Yeah
I
was
wondering
if
it'd
be
helpful,
if
one
of
us
reached
out
to
to
the
author
from
last
year,
I'm
trying
to
remember
who
that
was
was
that
divya.
A
B
They
want
us
to
keep
an
eye
on
it
and
maybe
look
through
the
contributor
report
ourselves
and
try
to
see
ways
that
we
can
help
alert
cigs
to
things
that
they
should
know
about.
Paris
is
very
into
the
report
and
thinks
that
a
lot
of
the
sections
and
it
could
really
help
ziggs,
do
more
things
more
effectively
and
help
companies
as
well
that
use
kubernetes
or
are
involved
with
contribution
to
to
learn
more
and
do
more.
So
there's
a
lot.
A
Why
don't
we
dedicate
a
chunk
of
next
week
to
kind
of
walking
through
that
collectively?
I
think
that'd
be
fun
as
an
exercise
together
actually.
B
B
A
B
A
B
Yeah
maybe
also
kate's
dot,
dev
blog
post
yeah.
A
A
That
way,
they're
not
trying
to
schedule
it
outside
of
their
other
hours
and
will
make
it
a
little
bit
more
likely.
A
B
Yes,
so
ian
was
just
like.
I
have
a
security
question
and
want
to
talk
to
someone
from
contributor
comms,
so
we
went
into
a
dm
and
chatted
and
what
they
were
really
looking
for
was
very
much
what
we're
talking
about
with
savita
today,
which
is
better
guidelines
around
the
process
for
when
we
help
out
with
communications
that
are
around
very
sensitive
security
information,
as
we
all.
D
B
There's
plenty
of
problems
and
things
that
can
go
wrong
there.
So
one
thing
one
suggestion
that
we
came
up
with
that
we
really
liked
was
for
us
to
create
a
security
communications
guide
for
us
to
put
in
our
repo,
which
would
be
a
best
practices
guide
that
we
collaborate
with
ian
and
tabitha.
The
co-chairs
of
sig
security
on
to
make
sure
that
anyone
from
contributor
comms
who's
working
on
any
kind
of
sensitive
security
communications
can
understand.
These
are
the
best
practices
that
you
need
to
follow
as
you're
working
on
this
communication.
B
So
I
included
one
that
they
mentioned
a
couple
times
in
our
conversation
and
said
that
we
should
reach
out
to
ian
and
tabitha
directly,
as
we
start
to
parse
this
out.
If
we
think
that
this
is
a
good
approach,
so
there
you
go.
A
I
that
sounds
fantastic.
No,
no.
I
mean
yeah
we're
getting
into
like
I'm.
I
guess
I'm
processing
like
we
don't
have
that,
but
it
really
just
comes
back
into
the
open
sourceness
of
the
open
source
like
we
don't
have
that
solid.
Let's
do
it.
I
mean
that
is
what
you
do
and
like
one,
you
usually
do
that
after
you
run
into
your
first
security
bug
at
a
startup,
and
I
guess
we
are
the
team
that
normally
works
with
teams
to
do
that
so
awesome.
A
B
D
A
E
I
can
help
as
well,
so
I
it
runs
a
project
for
security
documentation.
So
if
you
need
some
some
help,
but
my
replies
might
be
a
little
delayed
until
the
release
goes
out.
So
after
that
I
might
be
able
to
do
full
fledge
right
now
like
so
I'm
not
actively
signing
up
for
so
many
things.
But
just
keep
me
in
mind.
I
can
just
yeah.
A
E
B
It's
definitely
something
as
ian
said
in
there,
kubecon
talk,
there's
a
variety
of
cigs
that
need
to
be
more
more
collaborative
and
more
in
the
know,
as
these
types
of
things
are
being
communicated.
So
that's
a
great
point.
A
A
A
E
E
I
I'm
not
sure
hundred
percent,
but
I
think
that
is
the
like
point
of
contact
for
filtering
or
like
seeing
if
it's
actually
a
one
of
the
keynote
effects
or
like
it's
like
on
the
low
score
or
the
high
score,
I'm
not
totally
aware
of
the
process.
So
this
is
like
just
taking
the
grain
of
salt
sure
they
they
they
may
have
pse,
and
I
I
think
that's
it.
I
don't
know.
Probably
there
might
some
they
might
have
some
private
channels,
but
I'm
not
aware
of
those
any.
A
Sounds
great
I,
the
first
thing
I
I
found
when
looking
around
is
that
all
incubated
projects
in
the
cncf
have
to
have
a
security
vulnerability
response
policy
these
days.
So
I
think
we
just
we
existed
before
that
existed,
but
maybe
you
can
grab
some
stuff
from
there.
C
A
All
right
moving
right
along
we're
actually
just
two
minutes
to
the
top
of
the
hour
or
to
our
end
time,
with
some
breaks
between
meetings.
Anything
else
urgently
we
want
to
go
through.
I
know:
karthikane
had
a
big
update
to
the
the
code
base
for
automatic
tweets.
Any
quick
conversations
there.
D
Yeah
so
the
first
pull
request
did
crashed
our
previous
process,
but
let's
fix
now
so
because
then
you
can
test
it
out.
Sometime,
there's
one
other
problem
so
for
every
issue
that
we
want
to
be
made
into
a
pull
request
needs
to
have
a
label
called
tweet,
so
by
default,
kubernetes
reposts
don't
have
an
option
to
add
the
label.
We
want.
Oh
so.
D
C
D
D
D
D
B
Rajula,
I
don't
see
the
tweet
deck
checks
on
the
tweet
that
I
mentioned.
The
one
pull
request
request
that
we
have
in
the
repo.
B
B
D
A
C
A
Okay.
Well
thanks
all
this
was
a
really
exciting
and
fun
upstream
marketing
catch
up
great
to
see
you
and
catch
you
next
week,.
E
Exactly
I
hope
I
can
make
it
like,
apparently
my
calendar,
because
it's
I
am
going
out
of
this
meeting
happy.