►
From YouTube: Contribex: Weekly Marketing Meeting 20200424
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
All
right,
everyone
welcome
to
today's
April
24th
edition
of
the
extreme
kubernetes
meeting.
My
name
is
Paris.
Thank
you
all
so
much
for
coming.
It
looks
like
we
have
most
of
our
crew
here
today.
That
is
regular.
However,
if
you
are
joining
this
call
as
a
first-time
attendee,
whether
it's
to
contributor
experience
related
projects
or
this
marketing
project
feel
free
to
introduce
yourself.
A
B
Think
I
might
as
well
introduce
myself
again
I
called
in
for
the
first
time
last
week.
So
I
don't
know
if
anyone
has
changed
from
last
week.
Yes,
hello,
everyone,
I'm,
Kasim
fields,
I'm,
a
developer
advocate
at
Google
I've,
been
working
with
kubernetes
and
containers
for
a
long
time
and
I
keep
trying
to
get
into
contributing,
but
it
keeps
not
working
out.
But
I
was
talking
to
Paris
about
this
group
and
the
work
that
you
all
are
doing
sounded
really
exciting
and
interesting.
C
C
E
C
Effective
way
to
specific,
specifically
focusing
on
the
Ipek
time
zones,
helping
people
with
shorter
is
to
help
everything
trying
to
replicate
what
contracts
did
for
the
globally.
But
right
now
we
are
starting
with
blog
post
because
there
seems
more
feasible
to
do
and
somehow
there
is
a
notion
that
contributors
in
the
APEC
market
don't
want
to
come
on
the
videos.
They
will
be
more
comfortable
written
text,
you
know
a
stuff.
C
A
C
A
C
We
haven't
decided
on
timeline,
yet
we
are
currently
just
listing
down
that
how
many
authors
we
have
and
how
many
contributors
we
have
so
I
already
talked
to
one
of
the
contributors
he
comes
in.
So
we
have
that
dev
steps
right,
so
we
thought
okay,
we'll
just
pick
it
up
from
there.
He
is
apparently
busy
till
May
first
week
with
some
really
stuff,
but
he
said
he
would
be
free
after
that,
so
I'm
assuming
by
May
15.
We
should
have
something
exactly
does.
A
A
F
A
Well,
there
are
social
media
updates
that
I've
been
pushing
with
steering
steering
that
does
have
to
approve
digital
assets,
so
we
have
been
in
a
process
with
steering
to
get
that
approved
and
specifically,
the
guidelines.
I
will
include
the
github
link
in
here-
that's
not
in
here
right
now,
but
this
is
mainly
the
concern
was
mainly
around
caps
and
how
we
advertise
caps
and
for
folks
online
without
context
when
a
cap
is
that
is
a
kubernetes
enhancement
proposal.
If
you
want
to
talk
about
features,
that's
how
we
land
features.
A
The
steering
committee
was
very
concerned
that
if
we
tweet
caps,
it
will
encourage
pylons
in
comments,
and
there
is
one
condition
only
that
we
can
post
caps
and
it's
in
the
guidelines,
it's
very,
very
strict
and
it's
ground
rules
so
Chris
make
sure
that
you
read
those
understand
those
cazellnu
one
sec
I'm
getting
those
out
here.
It
is.
A
Copy
here's
chat
and
then
here
is
on
the
agenda.
He
are
submitted,
yeah.
A
So
right
now,
what
we're
waiting
on
is
steering
approval
and
I've
given
steering
the
time
box
of
this
Sunday
meaning
if
they
don't
comment
any
further,
then
it's
approved,
lazy
consensus
and
ideally,
we
send
our
first
real
tweet
on
Monday
and
we
can
talk
about
what
the
real
tweet
looks
like
in
the
discussions,
but
that's
it
for
social
right
now
again
the
deal
with
social.
We
cannot
tweet
any
more
until
steering
has
approved
our
guidelines
officially,
but
once
that's
set
we'll
be
ready
to
roll
all
right.
A
E
A
G
A
A
All
right,
I'm,
going
to
into
the
editorial
stand-ups,
because
we
do
have
a
lot
Maps
issue-
was
that
the
editing
workflow
is
rough
right
now.
What
can
we
learn
from
sig
Docs
to
make
it
better?
And
how
do
we
know
this?
We
know
because
we,
because
Matt
decided
to
use
my
blog
post
for
his
first
time
in
the
workflow
for
for
the
website
for
kubernetes,
slash
website
and
that's
where
the
blog
lives
blog
being
kubernetes
at
I/o.
It
does
not
live
in
the
community
repo
community,
repo
and
the
website
have
two
different
workflows.
A
A
So
when
we
talk
when
we
go
I
guess
into
big
discussions,
we'll
talk
a
little
bit
more
about
what
that
official
kind
of
workflow
should
and-
and
you
know,
we'll
look
like
we've
also
done
the
editorial
board.
Well,
Matt
I'm,
not
we've
met,
has
done
an
editorial
board
for
us
to
kind
of
go
over
I'll
share
my
screen.
A
H
This
is
going
in
so
the
cluster
life
is
almost
I'm
working
on,
so
maybe
by
Monday
or
Tuesday.
I
should
have
something
for
review,
so
maybe
I
had
ridden.
If
you
have
time
volleyball
all
you,
if
you
have
time,
we
can
be
slow
to
our
tailor,
but
as
table
is
like
ladies
dude
I,
don't
know
how
can
I
get
his
cycles,
but
yeah
I'll
try
to
see
I
try
to
get
some
help
from
either
of
them
just
finalized
and
and
then
I'll
for
the
time.
A
D
G
H
Thanks
Hollywood,
that's
this
this
and
the
road
also
I
think
I
have
to
have
an
interview
slot
with
the
team.
If
they
have
committed
it,
but
I
think
they
are.
They
got
busy
so
I'll
follow
up
on
that
to
nail.
Tony
also
want
to
work
on
that.
So
I'll
initiate
that
note
that
this
week
again
Monday
and
then
see
when
I
can
get
the
slot
for
the
interview
from
the
channel.
So
that's
the
update
on
those
two
I
got
a
drop
at
10:30,
but
before
that
I
would
I
just
want
to
pitch
in
two
things.
H
A
H
A
A
G
A
B
And
I
could
update
to
last
week,
I
also
took
on
a
task
of
working
on
a
cig
like
spotlight,
piece
on
cig
windows
and
I've,
been
working
on
getting
like
my
CLA
in
order
and
getting
my
contribution
environment
set
up
with
it
on
my
machine,
so
I
haven't
really
started
doing
much
with
that.
Yet,
but
I'm
not
blocked
or
anything
just
slow
to
start.
Okay,.
A
And
that's
all
good
as
well
we're
here
for
you.
Let
me
know
if
you
need
anything
at
all
to
get.
You
started
alright.
So
I'll
put
this
Alfa
feature
posts,
Taylor.
D
Why
do
you
betcha
so
119
is
upon
us
I?
Guess
one
comment
around
that:
we've
had
a
lot
of
discussion
this
week
in
dealing
with
the
pandemic
and
everything
else
going
on
in
everyone's
lives.
We've
pushed
out
some
of
those
timelines.
So
that's
not.
You
know,
there's
not
just
this
huge
cognitive
load
on
people.
D
We
want
to
reduce
stress
and
kind
of
make
this
a
little
bit
easier
of
a
release
and
just
kind
of
as
a
general
statement,
and
so
we're
slow
in
a
couple
things
down,
and
you
know
just
really
trying
to
work
with
communities
that
nobody
feels
at
a
place.
During
these
unprecedented
times
with
slightly
okay,
Subway
transitioning
over
to
the
Alpha
features
in
the
blog
post,
we
noticed
that
not
a
lot
of
alpha
features
get
there
tied
in
the
Sun,
so
to
speak,
and
so
this
is
something
that
I
was
talking
with
Bob
about
killin
mr.
D
Bobby
tables
about,
and
this
would
be
a
great
concept
to
kind
of
work,
with
the
different
SIG's
on
and
be
a
great
place
for
them
to
highlight
out
what
their
alpha
features
do
and
explain
what
their
use
cases
and
contexts
will
be
to
the
community
and
do
so
in
a
cohesive
way
and
that
being
through
a
blog
post.
So
that's
kind
of
at
the
heart
of
this
issue.
D
We
are
just
starting
to
kind
of
firm
up
the
enhancements
and
get
an
idea
of
what's
going
into
119
and
what
people
are
going
to
sign
up
for
so
as
those
get
a
little
bit
more
solid,
then
we'll
have
a
list
of
topics
that
will
have
those
potential
options.
At
that
point
in
time
we
can
reach
out
to
those
SIG's
and
those
groups
and
then
see
who
would
want
to
take
advantage
of.
You
know.
Writing
a
post
and
kind
of
working
with
us
on
this
trend
so.
A
I
I
feel
like
this
might
actually
go
under
the
same.
A
steering
issue
that
is
going
on
with
social
and
promoting
caps,
so
I
would
make
sure
whatever
we
do,
for
blog
posts
with
caps
matches
tweets,
meaning
the
guidelines.
So
the
steering
is
requiring
that
the
author
of
the
original
cap
in
the
metadata
literally
like
that's
drilling
them.
A
We
can
only
take
the
requests
we
cannot
reach
out
to
them.
So
in
this
case
we
could
put
out
an
email
to
ke
dev
that
says
SIG's.
If
you're
interested
in
this,
you
can
come
to
us,
but
we
cannot
solicit
them,
and
so
this
is
us
where
we're
gonna
have
to
educate
people
on
how
we
work
here
in
like
the
marketing
department
as
well.
The
other
thing
is
so
the
author
has
to
explicitly
approve
and
apply
the
label
area,
slash
contributor
coms
to
the
enhancement
and
then
on
the
issue
itself.
A
F
No
I
I
completely
understand
the
bad
experiences
and
I
definitely
don't
want
people
to
pile
on,
but
like
I
just
made
the
comment
in
the
PR
just
like,
as
this
is
written
I'm,
never
going
to
feel
100%
comfortable,
tweeting
a
cap
so
right
now
the
process
is
so
involved.
I
would
just
rather
them
come
to
us
and
say
please
tweet
this
as
opposed
to
saying.
Oh,
we
want
you
to
tweet
something
about
this,
and
then
we
have
to
make
it
up
and
then
get
their
approval.
No,
no!
You
build
the
tweet.
F
F
F
A
A
A
So
that's
why
we
want-
and
this
also
honestly
goes
back
to
storytellers,
quoting
as
well
like
if
you're,
quoting
people
it
explicit
approval,
if
you
are
like
get
consent,
consent
is
awesome
and
like
that's,
how
I
feel,
like
our
whole
entire
crew
here,
should
think
in
general,
like
every
one
of
our
functions,
I
feel
like
has
some
kind
of
consent
involved
dead
it
explicitly
if
you
have
to
like,
if
you're,
not
sure
of
something
get
it
in
writing.
Hey
can
I
use
this
thing.
Hey
can
I
use
this
diagram.
Hey
I,
see
this.
A
F
A
F
Very
clear
yeah
to
be
clear.
My
my
goal
would
be
that
the
approval
process
late
is
managed
and
we
just
you
know,
check
the
box
like
the
Oh
yep.
They
did
all
the
right
things:
okay,
here's
the
tweets,
you're
good
with
that,
go
right
like
less
effort
on
our
part,
more
effort
on
the
cap
writer
part
if
they
want
to
actually
get
it
tweeted,
because
we
know
getting
tweets
to
caps
as
a
problem.
F
D
I,
like
that
and
I
like
being
able
to
kind
of
cut
like
you
said,
you
know,
I
definitely
see
things
go
to
the
wayside
and
I
think
it
makes
sense
to
better
form
that
and
then
we
can
set
up
a
nice
template
and
make
it
I
think
Christy
report.
We
can
make
it
easy
and
capture
all
that
relevant
info
as
well,
and
so
I
can
have
the
best
of
both
worlds,
like
like
a
like
a
great
show
for
the
company
I
work
for.
A
Alright,
so
back
to
stand
up
really
quick:
we've
done
a
couple
things
with
the
workflow,
obviously
be
it,
let's
see
what
else
editorial
board
state
articles
or
work-in-progress
workflow.
This
is
me
reading
Matt's
notes
by
the
way
workflow
for
alpha
articles
filling
out,
okay
and
then
the
next
part
for
editorial
stand
up.
Is
me
moving
to
emeritus
advisor
steps
so
for
those
that
don't
know
I'm
just
wrapping
this
fun
thing
right
here
for
us
to
get
this
off
the
ground
Matt
is
going
to
be
taking
over
as
editor,
and
what
does
that
mean?
A
We
don't
have
any
guidelines
around
that
right.
Now
we
don't
have
any
guidelines
around
succession
and
things
like
that,
so
I've
kind
of
written
is
out
in
the
discussion
section.
So
that's
my
stand-up
is
pretty
much
that
the
steps
have
been
identified.
They're
not
that,
like
liquidy
anymore,
now
that
we
now
that
I've
seen
everybody
kind
of
start
rolling,
I'm
getting
really
super
comfortable
with
it
and
I
think
everything's
going
awesome
with
that
said,
the
work
in
progress
right
now
is
executing
on
those
Emeritus
steps.
A
A
lot
of
those
steps
involve
everybody
on
this
call,
whether
it's
to
get
the
official
guidelines
P,
Arden
or
what-have-you,
but
it
involves
everybody
on
this
call.
So
the
help
that
I
need
there
is
from
each
one
of
you
to
just
either
build
out
a
skeleton,
template,
etc.
That
you'll
hear
about
in
a
second
from
the
discussion.
A
So
that's
editorial!
That's
what
we've
been
working
on
and
that's
stand
up.
So
let's
go
back
into
the
discussion
topics.
We've
got
several
that
are
at
least
five
to
ten
minutes,
long,
editorial
social,
let's
start
with
editorial
first
I,
don't
want
to,
but
it's
actually
going
to
feed
nicely
into
the
social
discussion.
A
I
think
instead
of
being
choppy,
so
the
editorial
flow
that
we
saw
that
Matt
saw
in
particular
is
something
that
we've
learned
and
Taylor
can
explain
as
well
and
say
Doc's
a
long
time
ago,
which
is
you
should
probably
not
upload
anyone
else's
story
for
them,
because
once
you
get
into
the
back-and-forth
of
review,
it
gets
super
super
hairy
and
that
person
yeah
it's
I,
see
Chris
shaking
his
head.
Matt
Matt
littered
Matt
put
a
I'm
gonna,
say
a
blog
post.
A
That
was
maybe
80%
done
on
my
end
into
the
word
flow
and
we
had
like
80
comments
on
it
and
it
was
like
whoa.
I
was
only
like
80%
done
anyway,
kind
of
thing.
It
was
just
a
lot
ton
of
back-and-forth
and
then,
like
my
get,
blew
up
and
I
couldn't
look.
It
was
just
anyway
TLDR
there
in
the
discussion
point
and
Taylor
I'd
like
for
you
to
talk
as
well.
The
cig
docks
experience,
storytellers
and
everybody
that's
rating
blog
posts,
which
should
be
everybody.
If
you're
gonna
write
meadow
blog
posts
about
what
we're
doing.
A
Should
there
be
a
rule
in
our
workflow
process
that
everyone's
submitting
does
it
on
their
own
or
theirs
submitting
a
final
version,
meaning
in
the
case
where
someone
might
not
be
familiar
with
git
or
github,
or
you
know
first-time
or
something
like
that.
They
would
be
submitting
a
final
version
to
you
so
that
you
do
that
it
would
only
be
late
edit
Taylor.
You
want
to
talk
about
your
sig,
Docs
experience
and
then
also
talk
and
then
also
story.
Tellers.
D
D
So
all
that
to
say,
I
think
Google,
Docs
and
hack
MD
have
been
the
best
tools,
I've
seen
so
far
to
kind
of
work
with
that
before
something
goes
live
and
if
anyone
needs
any
help,
I
do
want
to
put
that
out
there
I'm
more
than
happy
to
kind
of
help,
walk
through,
gets
markdown.
Anything
of
that
nature
and
just
kind
of
either
help
write
out
documentation
on
that
or
just
you
know,
sit
with
you
and
work
with
you
on
that.
If
it's
something
you
want
to
go
through,
I
can.
G
A
G
A
Is
anyone
in
disagreement?
How
about
this?
Is
anyone
in
disagreement
or
have
a
slight
edit
to
the
notion
of
final
version
required
if
you
are
not
submitting
it
by
yourself
to
github,
meaning
like
at
the
top
of
either
your
hack
MD
or
your
Google
Doc,
it
says
final
and
then,
if
you
do
know,
github
you're
required
to
submit
your
own.
A
I'll
take
silence
as
agreement,
so
what
we
should
do
is
we
should
just
make
that
very
clear
in
our
blog
guidelines
and
storyteller
guidelines
and
things
like
that,
all
right,
so
story,
color
approval
sounds
like
we've
got
it.
I'll
follow
up
with
everybody
as
well
offline
with
those
blog
guidelines
and
love
to
have
storytellers
approves
that
PR.
A
All
right
next
discussion
is
my
steps.
These
are
the
steps
that,
as
soon
as
I
feel
like
we
have
covered
them,
I
will
PR
myself
in
as
emeritus
Matt
will
take
the
reins,
Matt
will
and
then
that
will
pretty
much
take
it
from
here.
So
what
these
steps
are
one
every
role
book
should
have
at
least
a
skeleton
stage.
A
What's
the
process
looked
like
for
internal
comms,
meaning
should
this?
Should
this
be
some
kind
of
native
process
where
people
come
to
us
and
say:
hey
I
need
this
thing,
amplified
highlighted
written,
etc,
and
then
the
last
is
same
thing
with
what's
the
social
intake
process.
What's
that
look
like?
Is
it
documented,
etc?
And
the
outcome
here
is
that
a
everybody
is
in
agreement
with
my
steps
and
it's
cool
with
them
in
steps
and
I.
A
A
A
So
if
we
feel
like
there's
roles
that
aren't
necessarily
formed
yet,
but
we
want
to
write
down
those
ideas
and
if
other
people
come
to
the
crew
and
see
kind
of
like
what's
available,
and
things
like
that,
we
can
write
that
here.
So
this
is
the
skeletons.
Do
folks
have
any
questions
about
skeletons
or
handbooks,
or
anything
like
that.
F
A
A
F
A
A
I
did
put
in
the
editor
and
I'm
happy
to
put
in
the
social
media
that
minimum
requirement,
Bok
was
saying
no
yeah,
so
I
think
you
should
put
that
in
there
as
well
as
long
as
and
I,
even
but
I
put
up,
I
put
a
stipulation
behind
it,
which
is
as
long
as
you
back
up
with.
Why
so
meaning,
you're,
okay
with
saying
no
and
then
you're.
Okay,
with
you
mean
a
justification
as
to
why
so
I
mean
because
if
you
just
say
no
you're
right.
J
F
A
A
What
time
lines
of
succession
look
like
for
you
so,
for
instance,
leads
I
feel
like
3e
in
it
in
a
release
team.
If
folks
are
you
know
familiar
with
release
teams
here,
they
it's
every
12
weeks,
so
they
have
that
3
month
period
and
then
they
roll
off
that
roll
off
that
role.
So
for
us,
though,
I
feel
like
3
months
of
nothing
I
feel
like
6
months
should
probably
be
the
minimum
for
a
lead,
but
at
the
same
time,
that
seems
like
a
very
long
time
for
a
shadow
so
DISA.
A
This
is
the
open
discussion.
I
wanted
to
have
with
y'all
as
far
as
duration
should
it
go
baby
even
by
function.
Maybe
we
don't
have
a
blanket
statement
of
shadows,
let's
say
six
months
or
something
maybe
it's
by
function.
So
the
functions
again
that
has
shadows
social
media,
internal
comms,
editor
I,
think
those
are
the
only
ones
right
now.
Cuz
storytellers
y'all
can
just
come
in.
Do
your
thing,
if
you
you
know,
obviously
you
can
only
do
one
every
every
now
and
then
you're,
just
a
drive-by
storyteller.
A
If
you
do
want
a
quarter
you're
a
part
of
the
crew
kind
of
thing,
so
y'all,
don't
necessarily
have
shadows
so
I
want
the
leads
to
kind
of
start.
Thinking
about
that.
This
is
the
most
important
thing
that
I
think
I
need
in
order
for
me
to
roll
off
like
I,
want
to
know
that
this
is
the
self-sustaining
crew
and
they
all
can
sustain
yourselves
cool,
so
I'm.
D
A
Yeah
Chris,
this
is
definitely
you.
You
have
to
think
about
like
carrying
the
torch
in
a
consistent
way,
but
also
not
holding
the
torch
for
too
long
and
get
burped
or
you
know,
Hoggett.
So
that's
kind
of
the
goals
right.
So
that's
the
role
books
as
everybody
in
agreement
and
cool
with
a
the
idea
of
rule
books,
handbooks
having
one
I,
see
thumbs
up.
That's
awesome:
Thank,
You,
Taylor,
that's
I,
honestly.
That
was
the
most
visual
like
validation.
A
Thank
you
soon,
I,
don't
know
that
way.
That's
it!
That's
a
new
one,
because
before
I
look
at
my
little
hand
in
the
corner
like
it
was
just
like
BAM
em
in
my
face.
Alright,
so
internal
calms
is
in
here,
but
this
affects
actually
everybody
on
this
call.
So
I
do
want
to
open
it
up
for
discussion,
a
tad
which
is
what's
the
our
internal
process
for
comms.
So
I
did
do
some
example
personas
and
use
cases.
So
you
can
kind
of
see
what
we're
what
we're
working
with
here
right.
A
So
internal
comms
are
gonna,
be
doing
things
like
promoting
our
events.
Potentially
you
know
potentially
promoting
caps.
As
long
as
like
you
know,
those
guidelines
and
conditions
are
met,
things
like
that
which
trust
me
there
will
be
some
times
and
then
any
kind
of
like
steering
committee
announcement
like
steering
committee
elections,
things
like
that
or
internal
comms
right.
So
here
are
some
example
use
cases
we
get
pinged
in
slack
at
contributor
comms,
like
somebody
did
last
night
by
accident.
Thinking
like
that
was
taken
Trebek,
they
say,
I'm,
gonna,
say,
chair
and
I
want
this
news.
A
You
know
and
news
retweeted
and
or
help
within
our
networks.
What's
next
for
them,
so
that's
what
I
mean
by
a
process
right,
because
this
is
the
firehose
that
I'm
talking
about
once
we
start
really
getting
involved
and
getting
into
this,
the
firehose
will
probably
happen
in
slack.
It's
probably
not
a
great
place
to
happen
for
a
firehose,
so
another
persona
use
case
is
there's
a
new
male
that
just
hit
kubernetes
dev,
it's
some
kind
of
braking
change,
or
maybe
it's
some
mentoring
thing.
Whatever
it
is,
it's
a
new
nail.
A
It
hits
our
canonical
source
of
truths,
which
is
the
kubernetes
dev
mailing
list.
What
next
doesn't
get
retweeted-
and
this
is
this-
goes
with
Christmas
thing
like?
Does
everything
get
retweeted
that
goes
on
kubernetes
dev?
What's
the
decision
tree
they're
like
if
I,
for
instance,
write
a
email
to
K
dev,
and
it's
like
something
we
did
in
steering
committee
and
hey?
We
did
this
thing
now.
What
does
they
get
a
blog
post
like?
Do
the
storytellers
come
in
and
say?
Oh,
this
is
worthy
of
a
story.
This
sounds
like
a
story.
A
What's
that
process
of
like
right,
same
thing
with
slack,
so
new
message
hits
lack
same
thing
would
like
to
comms.
Maybe
they
don't
tag
contributor
comms,
but
the
new.
The
new
message
is
in
kubernetes
dead,
slack,
which
5,000
contributors
are
in.
Should
that
be
boiled
up?
Where
should
that
go?
Should
that
maybe
go
to
the
mailing
list
again?
What's
the
process
there?
How
do
we
know
what
gets
tweeted?
How
do
we
know
what
we
need
to
amplify
as
a
crew?
What
does
that
process?
A
J
A
A
F
F
A
Of
like
yeah,
so
yeah
so
I'm
just
saying
for
you
to
think
scope
as
well
on
some
of
this
stuff,
anybody
else
like
storytellers
or
they
think
about
intake
right
leg.
You've
obviously
had
you
at
you
all.
Have
these
themed
issues
right,
but
you
can
think
outside
of
that
box
too.
Right,
like
you,
don't
have
to
like
the
themes
are
nice
because
you
can
just
come
in
and
out
and
pick
one
and
check
them
out,
and
you
know
punch
them
out
and
do
that
kind
of
thing.
Is
there
any
other
process?
A
A
D
A
I
said
the
word
native,
because
one
of
the
things
we're
trying
to
do
here
is
obviously
up
contributors
come
to
us
in
some
fashion,
especially
in
the
case
of
caps.
Again,
you
know
eating
eating
the
cab-horse
in
the
case
of
the
cups
we
absolutely
have
to
have
them
come
to
us,
so
we
need
some
kind
of
system
where
we
are
getting
things
in
math.
So
obviously
we
also
have
a
contributors
at
kubernetes
email
that
the
internal
marketing
team
uses.
A
So
I
don't
know
if
maybe
there
that
you
know
on
that
decision
tree
that
Chris
was
mentioning
I,
don't
know.
If
maybe
there
that
first
stop
shop,
everybody
emails
contributors
at
right
and
then
maybe
that
sets
off
them
to
do
an
issue.
So
there's
things
like
that
that
we
can
work
through
I
think
from
a
workflow
perspective.
A
That
would
still
be
very
good
for
us,
so
I
don't
want
to
necessarily
dictate
this
to
you,
although
so
I
want
to
I
want
to
just
reiterate
that
something
has
to
happen,
though,
like
I,
don't
want
to
let
the
floodgates
open
without
it
and
the
floodgates
like
it
could
be
everything
from
a
advertise.
My
pink
door
to
something
super
specific,
so
that's
kind
of
all
I
wanted
to
cover
with
that.
A
A
All
right,
so
that
brings
us
to
social
right,
so
we
just
talked
about
intake.
We
have
this
thing
called
Twitter.
Now
it's
up,
it's
semi
approved
I,
mean
I'm,
sure
I'm
sure
steering
would
be
like
do
whatever
you
want.
Does
not
keps
right
now,
for
instance,
to
get
us
live,
so
we
don't
necessarily
have
to
worry
about
that.
So
my
discussion
for
y'all,
a
what's
our
first
tweet
look
like
when
is
it
be,
should
the
profile
avatar?
This
is
a
kind
of
an
idiot.
A
The
profile
avatar
picture,
rotate
with
the
design
of
the
last
contributor
summit,
shirt
logo,
that's
sort
of
a
logo,
that's
tied
to
us
as
contributors
for
folks
that
don't
know
every
time
you
do
a
contributor
summit,
either
Tim,
Hawkins
or
Josh
Burris
creates
a
special
exclusive
logo
just
for
the
contributors,
so
I
thought.
Maybe
we
could
rotate
that
in
and
out
as
the
profile
photo
and
then
last
but
not
least,
what
exactly
did
we
say
in
our
bio?
Yes,
this
is
important.
What
links
do
we
link
to,
and
things
like
that?
F
F
F
As
far
as
where
we
link
to
right,
like
I,
think
either
a
like,
we
link
to
the
the
github
repo
right
now,
I
think
Paris
and
I.
We
might
have
talked
about
that
originally
like
where
to
link
to
it
was
like
to
me
it
was
either
the
repo
a
kubernetes
that
I
owe
or
the
blog
Wow.
You
know
it's
it's
up
to
us.
I
just
want
consensus
on
it.
At
the
very
least,
it
should
tell
people
where
to
go
to
find
out
more
about
contributing,
if
that
makes
sense
right
like
yes,
how
to
contribute.
F
As
far
as
bio
goes,
anybody
can
tell
me
I'm
wrong
here,
but
some
points
to
hit
are
this
is
for
the
contributors
right
like
it's.
The
key
contributors
informed
who
it's
run
by
and
normally
you
would
like,
give
some
kind
of
indication
of
what
to
expect
from
this
account
and
the
bio.
So
something
like
blogs,
updates
on
events,
contributor,
driven
content,
kind
of
thing
right
like
that,
should
also
be
stated
in
the
bio,
and
it
needs
to
be
pretty
simple
and
clean.
As
far
as
you
know,
language
goes
so
people
can
have
a
you
know.
F
A
F
F
Is
a
pen
tweet
might
be
you
know,
could
you
have
the
option
to
keep
a
tweet
penned
at
the
top,
your
your
timeline
or
whatever?
That
might
be
the
best
option?
I.
The
anecdotally
I
have
found
that
that
is
a
very
good
way
to
get
people
to
come
see
stuff
because
they
look
at
your
bio
and
then
they
scroll
down.
Oh
you
have
a
pen.
Tweet
I
should
go
read
that
so
that
I
think
is
a
good
idea.
A
A
What
some,
where
our
thoughts
for
linking
directly
to
our
marketing
team,
or
do
you
feel
like
the
community
repo
is
better
since
that
better
speaks
to
the
people
that
will
probably
be
clicking
the
link
anyway.
Any
that's
just
a
discussion
at
that
point.
I
personally
think
the
community
repo
is
probably
best,
but
I
just
wanted
to
also
throw
that
out
there
as,
like
a
you
know,
a
probably
another
place
that
could
be
reasonable
to
point
to.
A
F
A
C
A
A
F
A
So
you
know
if
you're
like
I'll,
just
do
this
one
to
do,
don't
feel
like
you
have
to
do
all
the
titties.
Just
in
your
you
know,
in
your
PR
say:
hey!
This
is
just
the
first
to
do.
I
know
there's
more
to
do
something
like
that
and
then
the
reviewers
like
myself
and
that
and
others
will
know
that
you
know
we're
not
going
to
knit
you
and
say
hey
Mussina
to
do.