►
From YouTube: Contribex: Weekly Marketing Meeting for 20200925
Description
Contribex: Weekly Marketing Meeting for 20200925
A
A
We
we
took
a
break
last
week,
so
I'm
sure
we'll
have
to
wake
up
our
brains
a
little
bit,
but
I
ideally
we
can
kind
of
I've
got
a
little
bit
of
a
proposal
to
to
show
people
that
I
want
to
sneak
into
the
agenda
talk
through
where
we're
at
it
connects
into
the
the
bots
in
progress
but
kind
of
a
vision
for
communication
on
the
scene.
I
said
I'd
get
a
draft
together
and
I've
got
a
the
draft
of
the
draft
coming
up
coming
along
hey
castle.
A
D
A
A
A
A
D
A
D
F
D
E
C
B
D
C
A
D
C
A
Yeah
he's
in
the
wrong
ignition:
oh
gosh,
okay,
cool!
Well,
I'm
I
I'm
always
happily
surprised,
you're,
not
surprised,
but
just
it's
always
happy
to
like
reflect
on
things
that
we've
we've
done
recently
and
realized.
Like
oh
wow,
we've
made
some
huge
progress
and
kind
of
connected
dots
across
not
just
kubernetes
but
across
the
regions
of
kubernetes,
which
is
ph.
Thank
you
for
holding
that
flag
in
caslin
for
standing
the
gap
there.
That's
awesome,
cool
all
right,
normal
routine,
look!
Throughs!
A
What's
going
on
with
the
editorial
in
progress,
we've
kind
of
been
quiet
on
the
storytelling
front,
I
personally
haven't
done
anything
and
I
think
that's
okay.
I
think
we've
been
focused
on
operationalizing
communications,
which
is
definitely
my
folk.
My
interest
we're
here
we're
happy
to
support
other
people.
Writing,
but
yeah
things
kind
of
stalled
out
there
anything
anything.
I
missed
nope,
okay,
lots
of
progress.
A
We
we
know
that
both
the
bots
launched
the
twitter
bot
and
the
the
slack
admin
bot
and
then
there's
the
addition
to
the
twitter
bot
to
be
able
to
schedule
things
that
we've
got
a
presentation
on
last
week.
But
we
don't
have
the
lead
on
that
here
today.
So
we'll
just
move
right
along
and
release
team
needs
shadow
for
comms
for
120
chris.
Take
it
away.
What's
going
on.
D
There
so
I
am
on
the
release
team
as
a
shadow
for
coms
this
cycle
and
the
whole
premise
was
to
help
figure
out
how
to
connect
the
release
team
to
this
team.
So
getting
those
like
points
automated,
because
they
do
a
release
blog
post
every
time
they
do
all
these
things
every
time
and
it'd
be
nice.
You
know
I
mean
we
are
the
blog
writing
people
if
we
could
take
that
over
for
them
kind
of
thing
to
an.
A
C
D
C
On
the
marketing
team,
the
release
team,
I
would
probably
still
keep
those
separated
because
they
like-
and
we
definitely
want
to
sort
of,
like
you
know,
make
sure
that
they're
marketed
and
there's
coordination
right,
but
it
is
a
good
amount
of
effort
to
actually
write
it.
Yes,
well,
it's
kind
of
like
writing,
just
like
even
tracking
the
people
down
and
getting
getting
them
to
work
with
you
on
writing
the
blog
posts.
D
A
D
D
C
D
C
D
C
C
C
D
D
A
D
C
D
Right,
that's
the
thing
right
like
they
need
to
be
on
auto
hold
so
that
we
can
go
back
and
edit
if
necessary,
right
like
we
can
generate
them,
but
we
need
to
have
that
hook
into
the
release
team
to
be
like
hey
by
the
way.
There's
this
thing
here
that
you
need
to
put
on
hold
at
this
step
in
the
process,
and
that's
where
I
was
going
to
try
and
like
add
on
to
the
release
team,
not
necessarily
add
on,
but
just
like
remind
the
release
team
that
this
possibility
is
here
now
right.
A
I
think
templates
are
different
from
automation
in
my
mind,
of
like
automated
posting
versus
like
automated
preparation,
but
it
seems
like
there's
a
good
demarcation
available
there,
and
then
I
guess
I
maybe
chris,
if
you
could
kind
of
just
sketch
down
like
what
are
you
seeing
as
the
opportunities
to
connect
like
what
are
their
roles
and
responsibilities
and
ours
and,
like
you
know,
list
out
like
I
would
like
this
person
in
marketing
to
do
this
or
be
ready
to
do
this.
But
can
I.
D
D
Changes
yeah,
like
the
the
timeline,
is
already
like
out
there
and
established
right,
so
we
could
auto,
hold
or
auto
generate
the
those
tweets
they
just
haven't
been.
You
know
done
done,
but
yeah
bob
just
dropped
in
the
chat.
The
case.dev
release
right,
like
just
reminding
folks
that
that
exists,
would
be
a
good
thing
right,
like
there's,
there's
so
many
points
of
contact.
That's
why
I
volunteered
to
shadow
right
like
there's
a
lot.
C
A
C
D
A
C
The
other
thing
is
like
in
the
comms
handbook
they
get
literally
just
like
in
the
event
of
a
date,
change
or
deadline
change,
just
be
sure
to
you
know:
either
open
an
issue
or
notify
open
a
pr
or
something
of
that
nature.
Yeah
yeah,
because
whoever
is
on
the
coms
team
in
the
future
will
be
more.
You
know
in
the
know,
on
any
of
that
stuff
right
yeah,
I'm
going.
D
A
No,
no,
don't
don't
you,
derby!
Sorry,
that's
exactly
why
we're
here:
it's
like
figure
out
how
to
connect
dots
across
teams
so
that
that's
perfect.
It's
definitely
inspiring
to
update
the
readme
on
the
the
tweet
github
actions
thing
so
that,
like
it's
framed
towards
people
other
than
ourselves,
because
we'll
probably
use
it
sometimes,
but
I
think
this
is
like
where
other
teams
would
benefit
from
knowing
it
exists
and
us
directing
them
there.
So
let's
keep
keep
an
eye
on
these
and
keep
bringing
up
ideas
do.
A
Thank
you.
Thank
you,
cool.
I
wanted
to
sure
this
is
really
well
aligned,
so
I'm
just
gonna
bring
up
an
old
presentation
from
when
we
were
kicking
off
this
group.
The
thing
that
I
showed
paris
to
kind
of
give
an
idea.
So
anyway,
I
want
to
take
a
moment.
I
won't
like
fully
present
this
to
you
for
for
all
we'll
leave
it
in
the
casual
version,
but
initially
when
we
were
putting
together.
A
So
this
is
this
part,
like
you
know,
what
does
it
mean
to
have
feedback
appreciated
or
to
be
in
a
in
case?
You
missed
it
stat,
like
that's
all
in
our
github
repo
now,
but
what
I
wanted
to
start
to
get
to
is
an
understanding
of
what
our
bots
are
doing
and
why
so
I
just
started
sketching
this
out
here
of
I
grabbed
a
cute
image
and
took
her.
A
This
flow
is
what's
been
on
my
mind,
and
I
just
wanted
to
socialize
that
idea
of
as
we
talk
about
these
channels
and
these
tools
that
we're
building,
if
you
can
think
through
the
sort
of
the
story,
we're
telling
ourselves
of
how
the
pieces
fit
together,
so
that,
as
we
continue
to
iterate
on
bots,
they
they
kind
of
serve
a
bigger
purpose
of
things.
Fitting
together,
I
started
to
write
out
stories
not
like
in
a
strict
product
management
type
way,
but
just
like.
E
Bots,
I
know
that
when
rajula
put
up
the
twitter
bot,
we
had
discussed
how
I
would
help
out
with
the
readme
and
kind
of
add
in
some
of
that
detail,
and
then
we've
been
kind
of
discussing
how
people
are
going
to
use
it.
So
I
haven't
really
touched
that
in
a
while,
but
you
talking
about
that
reminded
me
that
I
want
to
go
back
into
that.
Read
me
and
add
in
some
more
detail
about
kind
of
the
use
case
kind
of
the
story
line,
how
it
works.
A
Great
yeah-
and
I
bet
you
know-
people
aren't
gonna
like
find
that
repo
like.
Oh
you
know
what
I
want
to
do
right
now
send
a
tweet.
So
it's
like
I'm
not
so
worried
about
that
readme.
I'm
actually
really
motivated
by
like
chris
working
with
the
release
team
and
being
like
hey.
Can
I
tag
you
into
writing
a
tweet
through
here?
A
E
Yeah,
I'm
thinking
that,
like
as
we
start
to
learn
how
people
are
using
it,
we
can
update
the
readme
and
that's
kind
of
a
makes,
our
efforts
scalable
so
that
when
we
start
getting
new
people
into
this
process,
we
can
point
to
that
and
be
like
here's
what
you
need
to
know.
So
I
figured
it'll
kind
of
develop
over
time.
C
A
D
C
D
C
C
One
is
actually
like
on
the
list
of
of
topics,
so
I
won't
dive
into
that
necessarily
right
now,
but
there
there
are
some
things
that
like
have
been
surfacing
where,
having
you
know,
information
about
stuff
for
contributing
would
be
very
useful.
Like
you
know,
how
do
I
get
it
like?
One
was
just
like.
I
have
an
idea
for
a
feature.
C
What
do
I
do
and
and
that
process
like
is
not
very
discoverable
right
now
so
not
like
and
has
a
lot
of
other
like
little
issues
that
aren't
documented
like
in
the
enhancements
repo.
So
we
wanted
to
write
something
about
that
sort
of
like
overall
overall
journey
and
then
then
blog
that
one
I
think
laurie
was
actually
spearheading
that.
C
A
F
F
D
A
That's
a
an
older
school
thing
that
used
to
impact
people
if
you
copy
and
paste
the
exact
content.
But
if
you
link
back
to
the
original
article
through
syndication
like
google,
the
algorithm
understands
like
okay.
This
is
a
legit
connection
point
we
do
that
with
a
lot
of
success
across
our
ecosystem,
and
I
I
like
to
think
about
it
like
use
70.
A
A
C
Okay,
so
there's
going
to
be
a
kubernetes
wide
change,
that's
going
to
be
rolling
out
soon.
I
need
one
more
sign
off,
but
at
this
point
it
will
probably
be
on
like
monday
or
tuesday,
but
is
it
work?
It
is
essentially
a
set
of
new
labels
and
how
they're
used
in
the
korean
kubernetes
repo.
I
can
link
details
on
it
and
says
sort
of
like
rambling
about
it,
but
that
is
something
we.
We
definitely
need
to
essentially
socialize,
quite
a
bit
more
just
so.
People
are
aware
of
it.
A
A
A
We
still
don't
quite
have
the
sound,
so
this
is
actually
a
fun
exercise
to
think
through.
Like
there's
a
big
thing,
what
do
we
do
with
it?
How
do
we
you
know
how?
How
do
we
handle
it
so
slack
we
have
a
bot
that'll,
help
us
post
to
multiple
channels,
but
really
we
need
a
message
and
to
know
what
channels
we
want
to
post
to
so
what
anyone
have
thoughts
on?
What
that
should
look
like.
C
For
this
it
would
probably
just
be
the
kubernetes
dev
channel
in
slack.
Well,
you
know
more
sigs,
and
everyone
should
know
about
it.
I'd
just
be
hesitant
about
dumping
it
directly
in
there,
because
it's
also
sort
of
dependent,
like
some
of
the
stuff,
that
the
sigs
are
sort
of
implementing
their
own
workflows
around
these
labels
that
we're
going
to
be
pushing
out.
A
C
F
F
B
A
Yeah,
I
guess
I
guess
I'm
gonna
throw
an
idea
out
there
and
tell
me
if
it's
way
off
but
like
what,
if
we
post
into
kubernetes
dev
and
then
have
a
post.
That's
like
hey!
This
is
a
a
big
impact
and
make
sure
to
talk
to
your
sig
about
it
and
it
links
to
the
kdev
post.
But
then
we
use
the
bot
to
send
that
to
every
sig.
C
I
think
there
will,
I
think
there
would
honestly
probably
be
a
pushback
from
most
of
the
sig
leads
dumping
it
in
all
their
channels,
so
that
is,
that
is
something
actually.
We
should
send
a
email
to
the
leads
leads
that
creates
the
io
list
to
see
if
people
like,
if
they
would
be.
Okay
with
that
sort
of
thing.
A
C
That
that
yeah,
the
survey-
I
really
like
that
idea.
Okay,
the
the
other
thing
sort
of
going
back
to
the
the
issue,
triage
thing
and
announcement.
It's
also
like
tweet
and
then
you
raised
have
slack
channel.
We
will
probably
wind
up
with
a
follow-up
blog
post
to
sort
of
tie
everything
together,
essentially
like
you
know
how
walking,
through
the
process
of
actually
using
that
sort
of
thing,
so
linking
all
the
those
together
in
some
coherent
way,
at
least
like
you
know,
tweeting
or
or
something
to
sort
of
do
something.
A
C
E
D
E
E
A
That's
fine,
I
mean
that's.
That's
partly
I
mean
that's
kind
of
the
biggest
goal
in
mind
for
me
is
like
the
huge
opportunity
of
like
kind
of
finding
the
intricacies
here
and
building
a
system
that
doesn't
feel
like
so
like
ad
hoc
all
the
time,
but
in
the
meantime,
it's
kind
of
fun.
We
got
each
other's
back
the
and
for
me,
it's
actually
more
confusing,
because
if
multiple
people
get
asked
the
same
thing
like
who's
got,
the
next
action
is
always
tricky.
A
A
D
A
Cool
okay.
That
makes
sense
to
me
great
thanks
for
working
through
that
with
this
bob
and
yeah
I'll
I'll,
take
one
of
that
action
to
think
through
it
and
I'll
review
it
with
that.
If
you
need
help
with
copyedit
shoot
it
our
way.
My
way
directly
is
great,
unless
other
people
want
to
be
involved.
I'll
just
take
that
action,
but
what's
up.
C
C
C
A
C
It's
just
like
it's
stuff,
you
are,
you
want
to
get
done
within
the
next
release
cycle.
Things
have
been
a
little
weird
this
year,
just
because
you
know,
119
was
extended.
Normally
it's
about
a
quarter.
So
essentially
it's
just
like
what
do
you
want
to
try
and
accomplish
this
quarter
and
what
th
this?
C
One
of
the
things
that's
honestly
been
kind
of
a
problem
in
the
past.
Is
it's
not.
You
know
like
what
what
did
you
actually
do
this
quarter
and
by
being
able
to
just
like
here's,
our
milestone,
here's
literally
everything
that
got
done
during
that
period.
Just
just
helps
with
like
external
visibility,.
A
E
Yeah
we've
already
been
talking
about
this
the
whole
time.
So
that's
awesome,
but
the
one
thing
I
was
gonna
mention
is
the
tweet
that
went
out
about
the
the
apac
meeting
when
it
first
got
pr.
It
was
slightly
off
on
the
times
for
the
meeting,
and
I
tried
to
check
that,
but
I
didn't
do
a
very
good
job
of
it.
A
E
Yep,
especially
with
things
like
that,
it's
pretty
minor,
I'm
sure
we
will
find
all
kinds
of
issues
with
tweets
as
we
go
along,
which
there
may
be
other
solutions
to.
I
don't
know,
but
that
is
kind
of
our
our
baseline
right
now
is,
if
there's
an
issue
with
the
tweet
generally,
I
will
tweet
a
reply.
I've
also
had
one
where
I
messed
up
the
at.
I
was
adding
someone
in
it
and
that
got
messed
up
in
the
tweet,
so
it
didn't
actually
add
them.
So
I
did
a
reply
with
the
actual
ad,
so.
A
A
E
A
A
Good
all
right,
well,
just
looking
over
the
action
items
that
we
had,
it
seems
like
really
I
assigned
one
to
myself,
which
is
the
only
one
so
I'll
I'll,
follow
up
with
you
bob
and
help
along
with
the
the
new
labels,
but
other
than
that.
I
think
we're
good
to
go
hope
you
all
have
a
great
weekend
in
whatever
you're
doing
and
yeah,
thanks
for
being
here
on
a
friday
morning
or
evening.
Your
time
see
y'all
bye
from
josie.