►
From YouTube: Contribex: Weekly Marketing Meeting 20200131
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).
B
Think
it's
our
third
installment
of
the
kubernetes
upstream
marketing
team
meeting.
My
name
is
Paris.
It
looks
like
for
those
on
the
line
right
now
we
have
our
regulars,
which
is
awesome,
no
intros,
that
we
need
to
do
but,
as
always,
be
excellent
to
each
other,
but
feel
free
to
be
casual.
This
calls
only
a
few
of
us,
so
we
can
have
some
cool
discussions
feel
free
to
butt
in
cut
me
off
whatever
it's
only
six
of
us
right
now,
so
no
worries
there.
B
B
Once
we
have
the
roles
smoothed
out,
like
your
names
here
kind
of
thing,
and
then
our
focus
areas
so
that
people
can
see
that
a
little
bit
clearer
and
then
what
I
did
was
ended
up
putting
the
resources
that
are
at
the
top
of
this
agenda
in
there
as
well.
For
you
and
everyone
that
can
kind
of
see
what
we're
working
with
for
some
like
helpful
resources
and
things
like
that,
so
we
actually
have
a
ton
of
fresh
PRS
in
the
next
one
is
so
fresh
that
I
haven't
even
gotten
a
link
yet
for
it.
B
C
B
So
this
is
our
charter
again,
it
definitely
doesn't
look
as
extensive
as
a
cig
charter.
That's
the
exact
point:
it's
not
extensive!
It's
just
a
quick
summary
at
those
vision,
goals,
things
that
are
out
of
scope
and
then
we
have
a
lot
to
do
in
the
governance
sections
which
I
think
is
going
to
flesh
out
once
we
start
writing
a
little
bit
more
of
the
guidelines
and
a
handbooks,
and
things
like
that.
B
You're
gonna
start
to
see
that
your
workflows
are
going
to
need
to
include
certain
stakeholders
anyway,
naturally,
so
this
is
the
first
edition
of
the
PR.
So
if
everybody
could
not
necessarily
right
now,
let's
get
through
the
rest
of
the
meeting,
but
take
a
look
at
that
provide
comments
on
the
PR.
If
we
have
time
at
the
end
of
this
meeting,
let's
go
ahead
and
just
get
through
those
get
through
those
comments
and
potentially
check
this
in
today.
But
any
questions
concerns
comments
right
now
about
the
Charter
that
you'd
like
to
discuss.
A
B
Facing
yes
all
right
and
then
we've
got
an
open
PR
for
contributor
blog
guidelines.
Tunde
worked
on
this
thanks,
Tunde
I
added,
actually
I,
already
reviewed
and
I
forgot
to
add
in
that
the
blog
should
also
be
reviewed
by
the
people
being
mentioned
in
the
piece
we
don't
have
that
listed
in
there
and
I.
Don't
know
if
that's
actually
skimmed
of
the
same
Doc's
guidelines
as
well.
B
I,
don't
think
that's
in
there
as
they
are
guidelines,
but
it
should
definitely
be
ours,
for
instance
like
when
we're
quoting
people
from
SIG's
that
they're
giving
you
a
quote
or
if
it's
like
about
the
sig
chairs
or
if
it's
about
the
sake
itself.
Maybe
the
chair
should
approve
its
just
giving
people
a
nice
heads-up
of
here's.
What
we're
writing
about
you
just
from
like
journalistic
standards
right.
So
if
everybody
on
the
line
could
take
a
second
and
check
those
out
well
a
same
deal
as
as
the
Charter.
B
D
D
B
B
If
we're
shouting
you
out
giving
you
me
me
like
even
giving
you
cube
contech
it's
kind
of
thing
or
like
giving
you
certain
rewards
and
your
name
should
be
like
in
lights,
and
your
expectations
at
that
point
is
one
blog,
a
quarter,
so
I
thought
that
was
reasonable.
That's,
like
four
blogs
a
year.
Tell
me
what
you
all
thought
about
that.
What
you
do!
We
think
it
should
be
three
three
three
year,
not
one
a
quarter.
I.
B
E
D
F
D
B
B
B
So
this
was
the
original
issue
that
was
like
kicking
off
hey.
We
should
probably
do
contributor
blog
series,
so
what
I
went
and
did
was,
at
the
end
of
this
edited
for
a
list
of
some
of
the
groups
that
we
should
talk
about?
First
sort
of
a
punch
list,
I
was
hearing
from
blogging
folks
last
meeting
and
other
meetings
that
like.
B
If
we
had
just
like
a
punch
list,
then
folks
could
just
assign
themselves
either
their
names
on
the
issue
or
or
just
punch
out
a
new
issue
from
this
and
then
check
it
off
so
bloggers.
So
you
feel
like
this
is
cool
for
you
or
like
especially
from
a
process
standpoint.
What
do
you
think
here
and
then
this
would
just
sort
of
the
our
our
umbrella
rolling
issue.
B
Okay,
cool
all
right,
so
that's
settled
moving
on
there,
alright,
so
we
are
down
already
to
open
discussion
and
questions,
so
social
I
had
first
listed
actually
tagged
in
Bob
because
again
Bob
sitting
on
quite
a
few
Twitter
handles
so
Chris
and
other
people
who
are
interested
in
social
media.
These
are
the
the
handles
that
bob
has
in
comments.
It's
all
one
word:
kubernetes
dev,
Kate's
contributor,
Kate's
contributors.
H
H
B
C
Contributor
Nettie's
as
much
as
I
want
to
like
say
it
is
not
gonna
work.
It's
just
not
a
good
handle
for
Twitter
right
like
misspelling.
It
would
be
like
an
easy
thing
case.
Community
sticks
out
to
me,
Kate's
announced,
could
work
and
the
capes
contributor
or
contributors
works,
and
none
of
these
are
particularly
bad
other
than
what.
B
B
Two
were
viable:
here's
why
I'll
say
Cates
announced
isn't
viable
because
that
sounds
like
it
could
be
end-users.
It
could
be
anything
announcements
related
to
kubernetes
kubernetes
comm.
One
is
like
super
weird
sounds
like
Ready
Set.
What
ready
player
one
heats
community
is
bad.
Actually
because
again,
we're
describing
one
persona
of
the
community
here,
which
is
contributors
so
end-users
again,
who
affiliate
or
or
take
take
like
belonging
to
that
word,
would
associate
that
with
them.
B
Hates
contributors,
I
think
is
good.
Kate's
contributor
is
singular.
We
want
to
talk
about
the
hole
and
then
kubernetes
dev
I
think
is
the
next
viable,
but
I
hesitate
on
that,
because
dev
is
one
persona
of
a
contributor
which
obviously
is
the
majority
like
that's
not
a
lie,
but
it's
still
only
one
type
of
contributor
so
now,
which.
B
The
two
are
Cates
contributors
and
kubernetes
dev,
and
then
I
will
also
I'll.
Let
you
know
I
have
paws
on
Cates
as
well
I
paws
on
Cates,
because
a
lot
of
new
contributors
don't
understand
what
Cates
means
yet
and
that's
usually
like
the
first
kind
of
date.
Keeping
thing
that
we're
accused
of
I
think
is
like
what
the
heck
is
Cates.
What.
I
B
Out
of
that
list,
that's
what
I
personally
think
is
viable
and
what
my
what
my
thought
process
there
is
now.
The
other
thing
is,
it
doesn't
have
to
end
here.
There's
other
variations,
I'm
sure
that
we
can
put
out
of
this
right.
So,
let's,
let's
get
some.
Let's
get
some
juices
flowing
right
now:
I'm
gonna,
open
up
Twitter.
B
E
J
E
B
B
B
Alright,
the
next
question-
and
this
is
again
for
this-
is
for
everyone.
So
now
everybody
has
a
little
bit
more
clarity
around
our
foundation.
What
we're
doing
here,
why
we're
doing
it-
and
you
even
probably
have
something
of
a
I
probably
like
to
do
that
at
this
point?
If
not,
you
already
have
what
you're
doing
at
this
point.
So
the
question
is
what
tools,
processes,
guidelines,
policies
or
the
another
thing
I
didn't
include
in
there
is
permissions.
B
C
B
C
B
That's
I
feel
like
that's
where
kubernetes
io
should
yeah
everything
should
go
there
like
this
yeah
so
anyway,
all
right
so
you've
got
action
to
go
to
start
of
social
guidelines
yeah
and
then
also
everybody
on
the
phone
that
what
is
interested
in
social,
like
tag
team
with
Chris
and
I
on
these
things.
This
isn't
just
like
a
Chris
and
I
show
so
feel
free
to
jump
in
and
help
us
with
those
and
then
what
else
anything
else
so
say
meet
our
contributors
is
next
month
and
we
want
you
to
post
it.
B
K
C
Like
we
need
to
have
like
an
overall
marketing
team
like
goals
for
the
year,
we
might
be
a
little
too
early
in
that
process.
Right
like
to
align
yeah
everything
towards
a
goal
like
we
know
like
we
want
people
to
write
blogs
already.
We
know
we
want
people
to
help
certain
SIG's.
So,
like
those
are
like
two
things,
we
can
just
start
out
with
right
like
goals
right
there.
B
J
B
So
when
you're
writing
your
guidelines,
think
of
them
think
of
them
from
a
bootstrap
perspective
of
immediate
needs,
and
then
we
can
grow
from
there
cool,
and
so
that's
why
the
bootstrapping
guidelines
won't
be
big.
Could
just
be
something
to
get
you
off
the
immediate
ground
and
then
that's
why
every
meet
mean
every
week
we
meet
because
you'll
just
keep
building
on
them:
cool,
alright!
So
Taylor,
what
about
you
so
you're
going
to
do
some
blog
stuff
for
me,
sort
of
our
liaison
with
the
sigdoc
steam?
E
I
feel
good
I
feel
like
it's.
The
only
thing
I
need
is
to
do
the
work.
That's
I
think
that's
the
only
thing
that
I
could
I
could
see
in
the
immediate
future.
Otherwise,
I
think
it
is
just
kind
of
you
know,
grabbing
some
of
the
documentation
and
process
things
down
them
to
our
charter
and
then
currents
and
things
out
in
there,
but
that
shouldn't
take
me.
You
know
I
should
be
able
get
that
done
by
early
next
week
at
the
latest.
All.
G
B
G
G
B
B
D
We'll
cut
more
than
regarding
what
we
need
for
internal
comms
for
I,
think
yeah,
building
out
the
the
calendar,
of
course,
making
sure
that
people
can
ping
us
when
they
have
something.
So
we
don't
have
to
hunt
for
times
they
want
to
make
noise
about.
I
think
that's
the
most
important
one,
so
yeah
having
a
way
for
them
to
reach
out
to
us
and
make
sure
that
they
do
so.
We
don't
miss
things.
I.
B
I
dig
it
and
then
yeah
and
same
thing
with
you
all.
If
you
uncover
that
there
might
be
something
we
need
to
either
spend
money
on
for
like
a
what
maybe
something
like
a
one-time
shot
or
a
subscription
whatever.
Let
me
know,
ok,
especially
something
that
could
do
like
mountains
of
good,
alright
and
then
Tunde.
That's
not
cloud
automation.
K
Yeah
I
would
say
that
you
know,
like
I've,
been
just
an
idea
of
the
messages
that
we
want
to
get
out
from
the
maybe
walking
group
or
community
that
we're
writing
about.
You
know
like,
for
example,
if
we're
gonna
write
about
six
scalability.
What's
the
impression
we
want
to
leave
on
on
the
audience
like
whoever
is
going
to
read
this
yep.
F
L
B
L
B
Mean
one
of
the
most
immediate
impactful
need
that
we
have
right
now
is
probably
blogging,
because
it's
the
clearest
that
we
have
I
mean
as
far
as
excuse
me,
guidelines
and
scope,
and
things
like
that.
So
if
you
wanted
to
just
do
something
to
hit
the
ground
running,
that
would
probably
be
your
best
bet.
But
then,
if
you
want,
we
can
either
talk
offline
or
later
on
about
some
of
the
other
things
that
need
to
be
scoped
because
they're
so
ambiguous.
B
So
right
now
we're
working
with
like
four
very
high
level
and
big
ewis
concepts
that
we're
trying
to
kind
of
mold
out
into
functions,
and
things
like
that.
So
if
you
want
and
they're
interested
in
some
of
those
things
like
especially
G
suite
automation,
like
we've,
really
we
have
a
G
suite
account
and
there's
like
so
many
really
cool
things
that
you
can
do
with
with
like
recipes
and
stuff
like
that,
like
get-ups.
L
B
All
right
and
then
I
think
I
got
everyone
I,
don't
think
I
missed
anyone
all
right.
So
that's
good.
It
sounds,
like
everybody
at
least
has
or
knows
of
something
that
they're
going
to
hit
the
ground
running
within
the
next
couple
of
weeks,
which
is
awesome
again.
We
are
working
with
Isaac
ambiguous
topics
to
bootstrap,
so
thanks
everybody
for
that
all
right.
The
next
item,
which
Kris
and
some
folks
learn
hit
on
which
is
sort
of
goalie,
and
where
do
we
want
to
be
milestones?
Roadmap,
ish
stuff?
B
So
it
sounds
like
we
already
have
some
things
in
the
works
right,
so
let's
say:
we've
got
more
social
guidelines
coming
down
the
pipe
we've
got
event,
probably
events,
calendars
and
processes
for
how
to
get
news
and
announcements
that
Jonas
and
team
are
gonna
work
on.
Would
we
would
it
be
fair
to
say,
like
we'd,
have
like
monthly
milestones
and
have
these
things
kind
of
work
out
like
have
like
functions,
get
molded
every
milestone?
What
how
do
you
all
want
to
shape
this
so
like
this
is?
This?
B
C
I,
don't
want
people
to
feel
pressured
into
doing
things
right.
So
if
we
have
like,
if
we
overdo
this
and
overcome
it
like
I,
want
no
one
to
overcommit,
basically
or
feel
like
they
have
to
over
commit
to
do
anything.
But
with
this
group,
I
mean
monthly
milestones.
I
think
right
now
we're
fine
right
like
we
need.
You
know
certain
Docs
flushed
bad.
We
need
proposals.
C
F
B
And
it
might
be
worth
it
because
if
we
want
to
push
out
like,
for
instance,
like
ever
anytime,
a
cube
con
hits
if
we
want
to
push
out
major
communications
around
that
time
period
and
like
kind
of
like
updates
and
what
we've
done
and
like
even
reporting
at
cube
con
on
things
like
that.
I'm
wondering
if
that
might
be
a
good
milestone
for
us
as
well.
Yeah.
C
I
mean
we
definitely
need
like
a
30
60
90
day
plan,
pre
Q
calm
like
what
we
should
be
doing
right,
Mike
and
I
guess
they
are
close
enough
between
two
three
of
them.
Although
I
don't
know
if
China
is
gonna
happen
this
year,
that
like
that,
would
fill
a
calendar
basically,
but
with
that
being
said,
I
have
worked
on
event-driven
marketing
teams
and
it's
not
very
fun.
Yeah
I.
B
F
Mean
I
think
you
know
the
the
Mousehole
thing
just
like
just
like
Chris
said,
you
know
nothing
like
too
much
pressure.
You
know
right
now,
but
something
likes
like
a
lights
milestone
like
you
know.
It
really
helps
to
keep
things.
You
know
more
grounded
in
terms
of
the
fight.
It
doesn't
have
to
be
something
every
like
it.
Okay,
by
the
end
of
the
month.
You
know
we
should
have.
You
know
gotten
this
done
nothing
to
Evie
at
this
point,
people
feel
more
comfortable
now,
once
I,
easy
and
I
get
into
the
action
of
the
team.
F
A
B
So
I
keep
saying
you
know
I'm
here
for
I'm
here
for
three
months:
that's
not
true.
I
mean
I'll,
obviously
like
do
something
and
take
a
role
eventually
or
whatever,
but
from
a
bootstrap
perspective,
I
envisioned,
okay,
it's
gonna,
take
us
three
months
to
bootstrap
right.
So
what
does
bootstrap
mean
and
how
do
you
eat
like
what's
that
goal,
and
maybe
that
could
be
technically
our
first
milestone
right?
B
So
what
does
unbootable
I?
What
does
launch
look
like
for
this.
C
B
So
we're
when
our
bootstrap
holes
right
now
are
all
comes
in
place
that
we've
identified
all
guidelines
in
place
that
will
about
over
the
next
couple
of
weeks
and
all
rules
identified,
which
will
also
come
about
within
the
next
couple
of
weeks.
If
not
some
level,
some
have
already
been
identified,
but
Don
everybody
and
not
all,
and
then
also
we
should
probably
add
in
either
put
on
either
shadows
I
need,
or
we
have
some.
We
have
a
recruitment
strategy
shadows
is
that
fair
I
mean
because
technically
yeah.
B
Right
yeah,
so
we
need
to
either
have
shadows
in
place
or
I've
already
started
some
kind
of
recruitment
campaign
for
shadows.
If
folks,
don't
have
shadows
all
right
cool.
Any
other
comments.
Questions
concerns
about
project
manager,
things
I
have
a
question
in
there.
That
said,
should
we
set
up
a
project
board?
Guess
what
I
already
did
it?
We.
C
B
B
Just
first
up
meeting
notes
your
nose,
alright
project
board
right
there
and
then-
and
of
course,
if
you
want,
we
can
change
that
headings.
How,
if
whatever
makes
sense
for
marketing
teams,
if
any
of
you
use
project
boards
for
marketing
teams,
and
things
like
there's
like
some
amazing
way
to
do
this,
please,
like
same
with
any
of
the
project
management
stuff
that
we're
doing.
B
If
you
see
your
marketing
teams,
do
some
like
really
wild
cool
stuff
like
tell
us,
show
and
tell
us
kind
of
thing,
and
then
that
was
pretty
much
it
for
what
we
had
to
cover
in
the
meeting
today.
So
I
know
we
have
some
things
that
we
that
we
park
that
we
put
on
the
parking
lot,
but
does
anybody
else
have
any
other
questions
concerns
comments
that
they
want
to
bring
up
before
we
hit
the
parking
lot
items
I
desperately.
C
B
B
Did
okay
well,
I
did
put
a
note
out
to
the
mailing
list.
I,
don't
think
I
include
social
specifically,
so
I'll
just
respond
to
that
and
say:
oh
PS,
social,
too,
but
ya
know
you
have
me
on
your
team
for
a
while,
like
I
I'm
on
most
people's
teams.
Here
you
offer
for
a
while.
So
don't
think
like
you,
don't
have
an
extra
resource,
cuz
I'm
happy
to
be
here
for
you
and
then
yes,
we
will
get
you
a
shadow.
E
B
B
So
with
the
Charter
we
did
have
a
lot
of
to
do's
and
the
governance.
So
as
a
crew,
we
should
make
a
decision
on
the
following
one:
should
we
check
in/check
this
in
with
the
two
dues,
as
is
an
iterate
and
go
forward,
or
should
we
leave
it
open
for
another
meeting
and
see
if
we
flush
out
more
of
the
titties
and
then
check
it
in
at
that
point,
I.
A
B
B
B
D
B
B
B
If
not
I'll
ask
one
of
you
for
your
LG
TM
and
improve
when
I'm
ready
all
right?
Oh
my
gosh.
All
we're
gonna
have
like
three
three
things
pushed
up
today.
That's
freaking
awesome
all
right,
and
then
there
is
one
more
thing
that
I
did
not
put
on
the
agenda
that
I'm
so
lucky,
I
looked
in
slack,
for
this
is
a
blog
post.
Actually
that
needs
to
be
reviewed.
B
Let
me
share
my
screen,
so
Alex,
who
was
once
upon
a
time
helping
us
out
with
blog
stuff,
did
take
a
crack
at
the
first
cig,
which
was
scalability,
so
we
do
have
his
blog,
but
the
thing
is
it's
not
in
the
correct,
markdown
format
and
I.
Think
that's
what
Bob
and
folks
and
Taylor
I
think
you
reviewed
this
one
as
well.
So
the
question
is
a
does
this
meet
our
standards
right
because
this
is
again
before
we
had
standards
right
B?
B
What
do
we
do
in
the
case
when
someone
may
not
be
around
anymore
again,
and
we
could
lean
on
Taylor
from
the
sig
blogs
team,
because
I'm
sure
this
happens
a
lot
to
them
when
hey
someone's
not
around,
we
do
with
this
blog
post.
How
do
we
make
edits
to
it?
Should
we
list
them
as
a
co-author
and
then
list
us
as
the
other
co-authors
that
edit
it
so
open
discussion
y'all?
What
do
you
think.
B
C
E
I'm
gonna
be
fine
and
then
I
do
like
that
as
well.
I
like
having
that
attribution-
and
you
know
if
we
put
something
at
the
bottom
like
edited
by
or
improvements
offered
by,
you
know,
because
we
could
have
a
mean
author
or
set
of
authors
and
then
at
the
end
you
know
just
put
the
also
helped
by
you
know.
Photo
credit
goes
to
wood.
That
type
of
that
type
of
attribution
might
might
be
somewhere
helpful.
B
Tunde,
you
might
want
to
add
something
around
this
in
the
blog
guidelines
as
well.
Does
the
sink
Docs
blog
team
have
any
guidelines
about
that?
I
didn't
read,
I,
don't
remember,
reading
anything.
Is
there
any
title,
I,
don't.
E
Think
there's
anything
there
in
terms
of
specifically
to
that
attribution
context,
but
we
do
we
will
have
people
leave
and
then
you
know
kind
of
thing.
I'm
like
someone
will
get
a
blog
post
halfway
through
and
then
just
you
know,
never
never
show
up
again
and
then
we'll
close
the
pr's
out
at
that
point
in
time.
So
we
do
I,
don't
think,
there's
a
set
timeline
on
that.
It's
usually
just
like
as
we
meet
and,
as
you
know,
gut
feel
feels
versus
reals.
E
C
B
That's
why
I'm
like
I'm
wondering
if
it's
more
around
in
like
it's,
not
necessarily
around?
If
someone
abandons
it
or
can't
get
ahold
of
them,
I
guess
the
language
would
probably
be
around
like
just
collaboration
in
general,
so
like,
for
instance,
like
you
know,
if
you
know
we'll
always
try
to
attribute
everyone
that
works
on
the
piece
to
I,
don't
know
something
like
equal.
C
E
A
B
K
B
B
I
I
I
agree
all
right:
some
okay
and.
B
I
L
B
My
life
and
y'all:
are
it
alright
and
then
anything
out
come
on?
Let's
just
keep
going
I.
B
Like
things
that
are
just
you
just
know
it,
you
know,
that's
like
that's
the
hard
part
about
Twitter
now.
Is
that
no
so
that
stuff
is
taking
it's
like
just
you
just
know
it
that's
what
I
like
full-blown
kubernetes
contributors,
but
it's
just
so
long
like,
but
you
know
right
there.
It's,
like
you
know.
B
Alright,
well,
let's
continue
to
think
and
then
I
think
what
we
should
do
next
Friday
is
definitely
have
a
shortlist
and
then
prepare
a
community
vote,
because
that
thing
will
be
cool
if
we
engage
Eddy's,
deaf
and
like
how
to
top
three.
So,
like
you
know,
here's
the
marketing
teams,
three
we've
parked
you,
you
tell
us
which
one
you
want
and,
like
you
know,
maybe
we
can
engage
the
community.
That
way
is
that
a
good
had
a
good
time
line
for
that.
Yes,.
C
B
I
G
K
B
So
it's
like
you're,
a
journalist
with
the
Washington
Post,
tell
a
story
about
this
SIG
the
scaleability
like.
Why
would
we
care
like?
Why
does
why
does
kubernetes
care
about
this
say
gleich?
Why
is
it
so
important
like
you
should
make,
like
everyone
sound,
so
important
right
by
portent
so
yeah
the
blog
team
thing
about
that
thing
about
some
of
those
questions
and
then
maybe
next
Friday
we'll
have
like
sort
of
a
like
a
question:
script
/
like
question
Bank
that
you
can
build
off
of.
Is
that
cool?
If
you.