►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting 20210625
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
Happy
friday,
all
this
is
a
very
well-known
group
of
folks
to
each
other,
so
welcome
to
upstream
marketing,
and
we
are
doing
a
bit
of
a
working
session
today
start
by
presenting
just
so
we
can
get
everybody
on
the
same
page.
A
The
intention
was
to
write
a
blog
post
on
the
dev
domain
and
then
once
that's
published
to
email
it
to
the
sig
leads
as
a
reminder
that
they
should
also
go
through
this
and
look
through
the
lens
of
their
sig
for
improvement
opportunities
and
and
maybe
even
a
follow-up
blog
post
for
them.
If
they'd
like
did
I
get
that
right
from
last
week
last
week
was
a
long
like
many
months
ago,.
A
Cool
all
right
and
since
then
had
a
couple
requests
come
in
that
you
know.
I
want
to
leave
us
time
for
the
working
stuff,
but
we
should
probably
at
least
cruise
through
our
normal
agenda
because
they're,
as
we
noted
last
week,
we're
we're
kind
of
in
demand
now
and
that's
neat
got
new
items.
Gonna
have
this
okay,
so
start
from
the
top
any
any
big
ones
we
should
hit
on
that
have
come
up.
A
Oh
did
folks
get
through
their
review
of
kubecon
proposals,
because
I
feel,
like
a
lot
of
us,
were
on
the
hook
for
that
yeah
thumbs
up
and
in
the
future.
If
you're
interested
in
reviewing
kubecon
proposals,
just
let
either
caslin
me-
or
I
bet
bob
knows
this
too-
it's
a
pretty
it's
a
cool
opportunity
to
see
an
intersection
of
what's
going
on
there
and
it's
like
a
nice
way
of
donating
some
time
to
to
the
larger
project.
A
So
keep
that
in
mind
great
we're
going
to
skip
any
campaigns
because
there's
nothing
to
highlight,
except
what
we
wanted
to
focus
on
new
requests
got
a
message
from
ray
who
asked
us
to
share
about
the
security
third
party
external
audit
rfp
coming
to
a
close
on
july
6th.
A
Yes,
just
for
some
some
tweets
about
that.
So
I
was
hoping
we
could
scope
that
out
as
well
caslin.
If,
when
we
have,
you
know
like
a
week
or
so
to
go,
do
you
do
you
have
a
routine
of
doing
like
a
couple
and
just
auto
tweeting
them
through
tweetdeck.
B
B
A
Great,
so
if
anyone
has
is
feeling
inspired
to
draft
a
tweet
or
two,
I
added
kind
of
like
the
template,
I
told
ray
we
kind
of
use
but
and
the
cta
they'd
like
us
to
get
people
to
this
markdown
file.
That's
the
the
rfc,
I
guess
from
a
from
like
a
community
touch
point
point
of
view
like
we
can
send
them
here
to
review
it.
A
But
I
guess
I
want
to
make
sure
it's
clear
how
somebody
comments
on
it.
A
D
C
B
A
A
C
If
you
go
back
to
slack,
he
just
linked
yep.
A
Yeah,
I
see
that
so
the
question
being
like.
I
guess
we
want
to
make
sure
people
read
it
first
before
they
start
sending
feedback,
but
that
makes
me
think
the
call
to
action
is
the
form
not
the
markdown.
B
C
F
B
Views-
and
we
will
probably
still
get
some
of
those
comments
if
anyone
comments
like
I
want
to
add
this,
but
at
least
it'll
be
there
we'll
see
if
we
can
pr
it
in
there.
D
Does
the
project
board
like
get
changed
a
little
bit?
There
were
a
few
few
more
tasks
that
I
saw
last
time.
A
So
there
are
two:
there
are
two
boards.
One
is
intended
to
be
like
an
editorial
board
for
articles
in
progress,
and
I
think
that
includes.
A
Yeah,
okay,
cool
the
this
project:
39
is.
D
D
A
B
C
F
B
The
form
that
you
need,
okay,.
B
A
Yeah
I'll,
I
might
just
pr
and
update
to
that
rfc
to
see
if
they'll
accept
it
too,
but
in
the
meantime,
but
I'll
keep
the
header
the
same,
because
I
don't
want
to
mess
with
anything
any
linking
that
is
okay
questions,
one
two
to
crystal
clear
message:
this
works
for
now,
thanks
ray
cool,
very
fun.
A
A
All
right:
well,
I'm
gonna
stop
sharing,
so
we
can
see
each
other's
faces,
but
going
through
next
steps.
Yeah
our
goal
today
still
kind
of
help
along
this
community
report
and
get
it
visible
across
things.
There's
a
thread.
We
were
tagged
in
by
paris
in
slack,
there's
a
but
her
first
request
was
divya's
article
get
a
another
set
of
eyes
to
be
reviewed.
A
Normally,
blogs
blogs
are
the
ultimate
owner
here,
but
we
can
try
to
offer.
It
look
good
to
me
if,
if
tim
is
good
with
it.
C
B
Cool,
that's
one
thing
I
was
explaining
to
ian
last
week
when
they
asked
about
the
the
security
communications
conversation
that
we
had.
One
of
the
things
I
was
trying
to
explain
was
our
relationship
to
the
blogging
group.
I
feel
like
that's
something
that
could
confuse
a
lot
of
people.
Oh.
B
A
Yeah,
I
feel
like
in
a
nutshell
we
have
like,
like
in
a
completely
in
the
venn
diagram
of
us.
We
have
a
lot
of
scope
that
they
that
doesn't
fall
into
it
and
then
blog
has
a
very
clear
scope
of
owning
that
blog,
which
is
such
a
high
throughput
channel.
That
is
more
than
enough
scope
for
any
group,
but
like
we've,
slowly
shifted
more
and
more
over
to
to
be
relevant
in
the
blog
as
well.
A
You
know
my
intention
was
to
completely
separate
us
where,
if
it's
on
the
dev
blog
it's
ours,
if
it's
on
the
dot
com
blog,
it's
clearly
not,
and
if
we
want
to
participate
it's
outside
of
this
group,
but
I
don't
think
the
yeah.
I
don't
think
we
have
kept
the
clear
demarcation,
others,
thoughts
and
comments.
B
I
feel
like
it's
part
of
our
glue
work
where,
if
people
need
to
do
a
blog-
and
they
don't
understand
how
that
works,
because
we
can
all
relate
to
that,
then
we
can
help
connect
them
to
the
blog
group
and
help
get
that
through.
But
we
should
probably
clarify
that
in
some
of
our
our
documentation
and
stuff,
not
that
people
look
there,
but.
B
B
F
But
we
also
have
another
job
right
because,
like
the
other
thing,
I've
noticed
is
like
all
those
contributor.
Comms
messages
are
like
hey.
Can
you
help
us
either
tweet
something
out
or
get
the
message
out
about
something?
So
there's
there's
a
because
that's
where
I
got
confused
because
like
well
at
first,
I
was
confused
about
the
blog
thing,
but
that's
this
makes
a
lot
of
sense
right.
So
we'll
help
you
get
in
the
kubernetes
blog,
the
dot-com
blog
yeah.
F
C
A
Like
clear
communication
channels
like
that
was
what
we
were
solving
for,
that's
in
the
announcement
blog
post
of
this
working
group.
It's
that
one
of
the
the
number
one
complaint
of
contributors
is
that
they
don't
know
where
they
need
to
be
and
who's
telling.
What
message
when?
So,
we
did
a
lot
of
work
up
front.
It
was
jonas
rosalind,
myself
and
you
know,
paris
was
huge
in
that
bob
was
part
of
it.
A
Caslin
jumped
in
soon
like
we
basically
mapped
all
of
the
channels
out
and
set
some
default
ones
and
defined
like
levels
of
importance
so
that
it
felt
like
there
was
a
single
way
to
message
people,
but
it
kind
of
became
mostly
a
solved
problem,
and
now
we
just
remind
people
that
exist
and
kind
of
nudge
them
towards
those
channels.
A
So
that's
like
our
persistent
background
work
but,
like
the
larger
you
know,
mission
is
to
help
people
effectively
communicate
in
the
kubernetes
community
and,
and
that
is
as
like
castle
put
it
like.
That's
more
glue
work
than
anything
else.
We
don't
need
to
own
the
blog.
We
don't
need
to
own
a
website.
We
don't
need
to
own
a
channel
that
often
like
we
do
the
twitter
one
because
it
didn't
exist
and
we
mostly
just
want
to
help
people
get
to
the
right
place.
It's
this
fun
service
team
at
its
core.
F
Okay,
so
we're
like
not
quite
ombudsman
but
like
some
sort
of
like
so
yeah
all
right,
so
the
job
is
to
just
help.
People
help
people
get
the
information
they
need
to
do.
What
they're
trying
to
do
right,
yeah.
A
Yeah
work
we're
with
customer
service
team
with
a
marketing
problem
yeah,
but
I
think
that's
our
minimum
viable
team
like
if,
if
we
have
the
time
to
scale
up
and
and
grow
like,
we
could
be
setting
the
definitive
way
in
which
kubernetes
like
markets
itself
and
like
what
terms
we
use
and
how
we,
how
we
do
this
differently,
so
that
kubernetes
feels
cohesive
in
to
its
contributors,
so
that
they
can
better
articulate
kubernetes
value
and
the
values
of
being
a
member
of
our
community.
A
C
A
A
Tweeting,
especially
devblog,
is
partially
unowned
and
like
bob's,
basically
given
us
permission
to
claim
ownership,
and
we
started
to
and
honestly
I
lost
those
extra
hours
to
like
bring
that
campaign
all
the
way
through
to
the
sense
where
people
feel
like
it's
a
place.
They
should
contribute
to
and
they
know
how
to
contribute
there.
So
I
feel,
like
that's
a
stalled
project
that
we
still
have
the
opportunity
to
take
up,
but
it's
just
kind
of
mostly
existing
in
a
few
of
our
heads.
F
B
C
A
C
I
think
there
were
still
some
outstanding
comments
on
it,
but
for
the
most
part
it
was
pretty
in
pretty
good.
C
C
C
It
looks
like
the
last
comments
were
on
17
days
ago.
C
Just
minor
like
spelling
mistakes
and
spelling
mistake
some
capitalization
stuff,
so
it
should
be
pretty
close.
F
C
I
said
general
if
I
rolf
rolf,
dh
and
nate.
W
are
both
tech
writers
by.
C
A
Okay,
so
this
is
this
really
is
an
announcement
post.
It's
not
a
look
at
the
data.
It's
not
like
a
reflection
on
the
data
sick
usability.
Oh
my
bad!
I
was
looking
at
the
the
ones
titled
announcement
post,
okay,
the
community
group.
A
A
A
Sure
yeah
both
links
are
in
the
oh,
my
god.
There
we
go.
A
C
It's
it's
less
targeted
for
the
sigs
and
more
for
anyone
else
that
is
interested
in
well
it.
It
does
help
others
sort
of
learn
about
what
some
of
the
other
cigs
are
doing,
but
there's
a
general
call
to
action
in
the
bigger
annual
reports
of
just
like
the
areas
where
sigs
need
help
cool.
The
actual,
like
report
is
like
20
pages
long.
D
A
That's
what
I
would
love
to
spend
some
time
going
through
and
like
pulling
out
a
couple
factoids
that
make
it
exciting
so
that
people
read
through
20
pages
this
one.
It's
a
little
hard
to
put
my
finger
on
if
there's
a
way
to
make
it
like
pop
to
a
reader
like
answering
the
question
like,
what's
in
it
for
me
to
read
this
article.
A
F
A
A
Okay,
if
this
meets
the
need
of
what
the
team
needed,
then
then
it's
perfect.
I'm
just
like
going
through
my
sort
of
content,
feedback
questions
and
just
didn't.
Maybe
I
don't
know
what
we're
solving
for
on
that
one.
C
A
Yeah,
no,
I
I
think
as
scoped
it's
good,
I
think,
there's
just
a
completely
separate
scope.
I
have
in
mind
of
something
that
like
starts
to
consume,
that
elephant
of
a
report
into
pieces
that
will
excite
people-
and
you
know,
give
you
like
a
quick
taste
of
what's
what
our
curated
takeaways
would
be
from
it.
A
Exactly
yeah
and
it
gives
you
insights
into
last
year.
You
know
my
my
brain
goes
to
structure
so
so
that
people
can
see
the
different
sections
like
h2
headers
are
really
helpful
to
break
up
text,
but
I
couldn't
quite
I
don't
think
I
could
do
the
demarcation
on
this
one
without
restructuring
it
and
I'm
just
getting
in
too
late,
and
that's
that's
fine.
I
think
it's
good
as
this.
G
A
Kunal
is
he's
no,
he
had
a
drop,
but
his
post
on
usability,
pretty
pretty
rock
solid.
F
Yeah
like
in
in
in
future
right
like
based
on
what
paris
said
when
we
do
those
things,
we
should
go
back
and
reference
the
annual
report
and
make
sure
that
we
ask
them
when
we
interview
hey
like.
Can
you
elaborate
on
the
help
that
you
want,
but
that
was
that
happened
after
he
wrote
that
right?
So
I
don't,
it
doesn't
make
any
sense
to
go
back
and
change
it
now.
F
A
A
C
F
A
C
Or
you
open
an
issue
in
k,
org
in
the
root
of
the
k,
community,
repo,
there's
a
thing
on
community
membership.
Yes,.
F
A
A
A
Yeah,
I
think
that's
where
we
we
left
it
that
I
was
trying
to
get
a
see.
If
there
are
any
things
you
could
pr
in
just
so,
we
could
point
back
to
that.
C
F
C
A
F
F
Well,
I
can
also
add
I'll,
also
look
at
I'll
look
at
what
I
have
to
do
and
maybe
just
add
some
stuff.
I
don't
mind
I've
got
I
can
put
in
the
you
can
put
in
the
time
to
get
a
couple
other
things
there.
I
don't
like.
I
guess
my
problem
is.
I
don't
know
that
I
plan
on
which
the
org
that
I'm
joining
is
the
community
work
or
the
kubernetes
or
the
kubernetes
so
like
because
my
thing
is,
I
don't
think
I'm
going
to
be
contributing
regularly.
Kubernetes
right.
F
F
A
Yeah
but
I'm
gonna
send
you
I'm
gonna
dm
you
a
couple
things
make
sure
you've
gotten
these
done
just
so.
You
pass
that
bar.