►
From YouTube: [SIG ContribEx] Weekly Marketing Meeting for 20201204
Description
[SIG ContribEx] Weekly Marketing Meeting for 20201204
A
Welcome
to
the
weekly
kubernetes
contributor
coms
marketing
meeting.
We
are
one
week
away
from
the
contributor
celebration,
and
that
is
definitely
the
thing
that's
going
on
the
most
at
the
moment,
so
that
stole
some
attention
this
morning
and
it's
pretty
damn
exciting.
We
can
jump
into
anything
else.
People
have
on
their
mind,
so
just
add
that
to
the
agenda,
which
I'm
throwing
in
chat
right
now,.
A
B
A
C
A
A
A
A
Yeah
all
right
cool.
Well,
it's
been
a
little
bit
since
we
got
together.
It
was
a
quiet
week
last
week
and
before
that
it
was
kukan,
and
next
week
is,
is
a
event
coming
up.
So
that's
really
the
first
and
foremost
thing
to
keep
in
mind
that
I'm
certainly
planning
to
cancel
this
next
week
because
we'll
have
an
all
day
celebration
event
at
kate's,
dot,
dot,
dev
celebration:
you
can
go
sign
up
for
it,
and
that
is
the
biggest
thing
on
on
our
mind
is
getting
the
word
out.
A
It's
getting
some
momentum
and
there
are
some
fun
games.
If
you're
a
baker,
there
is
going
to
be
a
great
british
bake
off
style,
kubernetes
bake
off
on
saturday,
so
not
friday,
the
next
day
and
paul
zarkowski,
I'm
good
friends
with
him,
and
I
probably
pronounce
his
name
wrong.
He
will
be
hosting
it.
I'm
gonna
jump
in
as
a
judge
or
something
like
that,
but
it
looks
really
fun.
Are
any
of
you,
bakers,
by
chance.
D
D
A
Adding
that
to
chat
perfect
I'll,
add
that
below
I'll
do
some
there's
like
one
big
thing
on
our
mind
as
a
community
that
came
up,
we
may
not
solve
it,
but
I
definitely
want
to
spend
a
chunk
of
time
talking
through
it
and
that's
a
issue.
That's
got
a
lot
of
traction
around
communications
on
deprecation.
A
This
is
very
much
like
in
the
wheelhouse
of
what
we
want
to
talk
about
in
this
group
so
wanted
to
see
the
conversation
we
don't.
We
probably
could
talk
about
it
for
a
long
time,
but
get
it
out
there
that
it's
something
to
talk
about,
and
then
there's
been
some
conversation
about.
You
know
what
we
uniquely
do
when
rajula
kazan
and
I
presented
at
kubecon.
We
had
to
put
some
pieces
together
and
I
just
wanted
to
offer
a
draft
of
what
that
looks.
B
Actually
matt,
I
I
really
want
to
know.
Is
there
any
document
where
you
know
from
the
issue
tracker
to
treating
so
how
this
process
you
know
flows
from
beginning
to
end?
Is
there
any
document
where
I
can
go
through,
and
you
know
just
to
know
how
how
you
people
are
tweeting
tweets
and
doing
this
stuff.
E
B
A
This
is
in
as
a
result
of
you
know
the
the
quite
a
bit
of
information
that
popped
up
around
what
the
removal
of
the
docker
shim
means
for
kubernetes
users,
1.20
introduces
the
removal
of
docker
shim,
and
it
has
confused
most
people
because
they're,
like
will
docker
files,
not
work
anymore,
will
containers
not
run
the
same
way?
What
does
it
really
mean?
So
this
is
a
pretty
fascinating
conversation
of
like
how
do
we
get
ahead
of
communications?
A
Are
there
places
in
our
ecosystem,
where
it's
easy
to
understand
that
beyond
beyond
the
change
logbn
beyond
the
code
log
of
it
and
are
there
behaviors,
we
should
be
taking
to
support
this
along
the
way
paris
tagged
us
in.
Can
we
be
added
to
the
release
team
coms
role
to
assist
with
promotion,
amplification
and
education?
C
F
C
A
A
C
Right-
and
I
think
I
mean
it-
is
it's
a
you
know,
common
human
psychology-
you
add
a
new
feature.
Probably
people
won't
be
that
excited,
but
if
you
take
something
away,
they
are
going
to
panic
right.
You
have
a
bit
cautious
when
we
are,
you
know
talking
about
deprecating,
something
just
add
a
time
frame
to
that,
so
that
you
know
it
adds
a
consolation
value
that
okay.
This
is
not
going
away
right
now,
but
there
is
a
thinking
that
this
might
go
away
at
some
point
of
time.
A
Fair
yeah,
I
I
followed
the
deprecation
of
python
2
like
pretty
closely
and
they,
I
think
they
kind
of
have
a
the
python
community
documented
that
very
well,
and
it
focused
very
much
on
like
on
this
date.
It
will,
we
will
no
longer
be
supporting
it.
That
said,
people
still
freaked
out
so
like
there
is
an
element
of
like
we
have.
That
was
going
to
happen
no
matter
what
and
the
question
is
like.
C
Yeah-
and
I
mean
we
can
probably
take
some
input
from
that
messaging,
I
mean
I
knew
pretty
long
back
that
I
mean
the
community
knew
for
a
very
long
time
that
it
was
going
to
be
replicated.
It
was
not
like
one
day,
a
tweet
pops
up,
saying
saying
that
you
know
python.
2
is
deprecated
and
everybody
started
panicking.
So.
D
Most
of
those
tweets
are
from
the
kubernetes
users
and
not
from
the
kubernetes
administrators
because,
as
he
said
like
they
knew
what
it
means,
and
only
it
just.
The
word
docker
like
triggered
the
panic
in
everyone,
and
I
I
I'm
not
sure
it
was
in
the
dock
or
it
was
in
the
issue
they
were
like
someone
saying
like
it
should
be
six
months
before,
prior
to
the
deprecation
or
prior
to
the
stuff
that
we
should
be
like
prior
to
taking
that
feature
out.
D
We
should
be
saying
like
this
is
going
to
be
gone
for
on
this
particular
answer
timeline.
And
I
guess
that's
what
we
are
doing
here,
because
document
is
going
to
be
completely
removed
from
that
by
123,
not
from
121,
though,
because
that's
where
the
duplication
we
are
doing
and
the
only
thing
is
like,
as
he
said,
I'm
just
recording
his
point.
That
is,
this
got
amplified
so
big
because
just
it
involves
the.
D
D
B
A
I
I
really
like
yeah,
I
really
like
what
you're
saying
and
like
I.
I
could
completely
see
us,
like
you
know,
using
classic
communication
tactics
on
top
of
this
right,
like
docker,
is
also
an
organization
that
we
have
friends
in
that
work.
There
like
we
could
collaborate
with
them,
make
sure
they're.
They
have
a
blog
post
about
this
as
well.
D
Correct
correct,
because
the
moment
when
we
published
in
the
blog
that
we
are
going
to
duplicate
docker
shim,
if
docker
would
have
also
published
that
it's
not
going
to
stop
any
of
your
dev
utility,
the
productivity,
it's
just
that
it
is
not
going
to
run
within
the
kubernetes
cluster,
but
still
docker,
like
images
produced
by
docker,
are
also
ocl
compliant.
So
you
can
run
any
osa
compliant
images
anywhere
in
the
cluster.
I
mean
you
know.
A
D
The
cluster,
so
if
docker
would
have
also
published
to
some
sort
of
blogs,
or
at
least
a
tweet
from
the
docker
official
handle,
then
it
would
have
also
helped
a
lot
in
surprising.
The
panic
like
they
will
be
saying:
oh
yeah,
you
know
there
is
duplication
and
yeah.
Docker
is
also
saying
like
yes,
it
is
actually
gonna
work
and
then
at
least
people
would
get
interested
to
know.
A
D
With
some
most
of
the
questions,
because,
if
you
look
at
yesterday's
tweet
like
all
of
those
like
cats,
stephen,
like
all
of
those
kids,
not
kelsey,
I
haven't
seen
any
tweets
from
kelsey.
Like
he
just
mentioned.
Docker
shim
is
gonna
defecate.
I
guess
most
of
them
are
trying
to
explain
what
it
means
for
the
end
users
of
the
kubernetes
cluster.
So
it
was
like
kind
of
a
session
for
most
of
the
twitter
twitter
user.
A
Yeah,
yeah,
exactly
and
and
also
a
healthy
reminder,
like
our
communities,
has
a
strong
bias
towards.
You
know
how
people
are
reacting
on
twitter,
which
does
not
represent
the
whole
world,
but
definitely
is
an
important
channel
for
us
to
talk
about.
So
one
of
the
takeaways
I
have
from
this
is
not
necessarily
like.
We
could
use
this
as
an
opportunity
to
refine
and
like
basically
integrate
our
team
more
effectively
into
the
communication
path,
but
like
one
of
the
communications
that
we
could
focus
on,
getting
out
is
actually
the
don't
panic.
A
Philosophy
right
like
people
are
gonna
react,
no
matter
what,
when
you
remove
something
that
has
the
word
docker
in
it
or
yeah,
or
when
a
huge
kubernetes
thing
lands,
there
could
be
a
little
bit
of
a
you
know
if
we
just
power
people
with
some
language
around
it
make
sure
they
have
the
assets
already,
like
hey
glad
you
care
about
this.
Here's
what
it
really
means
read
this
article
like.
If
that
could
be
like
a
little
text
that
we
already
have
ready
for
people,
they
can
feel
more
confident
and
less
concerned
as
well.
D
Right,
I,
I
also
think
like
it's
it's
on
the
it's
like
kind
of
gamble
that
we're
gonna
play,
because
when
you
are
duplicating
as
pos
mentioned
like
when
you're
taking
away
something,
users
are
certainly
going
definitely
going
to
panic,
and
shout
about
that.
I
think
for
an
example
like
we
had
the
heapster
removed
by
I
mean
heapster
took
over
by
metric
server.
Hipster
was
the
first
matrix
collector
we
had
and
everybody
was
using
it
and
there
were
a
lot
of
implementation
based
all
of
that.
D
But
when
metric
server
was
implemented,
it
was
so
easy
than
heapster
and
everybody
started
allowing
it.
So
it's
it's
like
whether
the
product
that
gonna
fill
the
void
because
of
taking
away
some
of
the
features
how
familiar
how
familiar
it
is
with
the
end
users
is
the
like
is
the
game.
Actually
I
guess
I
mean
this
is
my
opinion.
A
Yeah
yeah
exactly
you're
right.
I
think
yeah
pierce
nailed
this
one.
We
when
we
think
about
personas
right,
like
the
operator
user
persona,
which
are
often
a
lot
of
contributors
in
kubernetes,
they
were
fine.
They
like
knew
basically
this.
They
they
understood
the
nuance
of
the
the
daemons.
It's
the
developer,
persona,
which
also
very
important
group
of
people,
maybe
less
contributing
to
kubernetes
day-to-day
or
maybe
don't
know
the
nuance
that
had
to
come
up
and
were
reacting
to
the
news,
because
what
I
saw
is
people
thought
docker.
A
Removal
of
docker
meant
the
removal
of
compatibility
with
docker
files
like
that
is
the
interface
by
which
a
lot
of
people
think
they
like
is
docker
and
that
that's
such
a
there
are
so
many
layers
to
explain
to
get
to
that
point,
and
but
that's
the
opportunity.
If
we
want
to
write
about
any
of
this,
that's
good
and
we
have
team
members
already
writing,
like
there's
a
great
article
on
our
site,
there's
great
article
on
docker
and
there's
more
to
come
cool
any
yeah,
please.
If.
E
I
can
add
something,
so
I
just
have
a
very
generic
comment
say
say
any
deprecation.
Anything
first
thing
I
understand
is
that,
like
you
said
at
what
we
you
said,
there
are
two
different
kind
of
audiences.
One
is
contributors,
the
other
is
users
for
contributors.
I
think
there
are
already
enough
slack
messages
going
on
enough
posts
in
the
google
groups
that
that
keeps
going
on
about
applications.
E
E
We
already
do
that,
but
like
in
different
places,
it's
not
in
a
single
place
which,
which
makes
it
easy
for
us
to
actually
market
or
market
it
to
either
contributors
are
users
and
also
like
save
for
python
or
anything.
So
you
keep
getting.
I
think
the
dollar,
the
the
the
code
tools,
already
keep
displaying
the
messages
saying
this
is
deprecated.
E
This
is
being
replicated,
so
we
we
can.
We
can
ensure
that
that's
happening
and
we
can
maybe
periodically
keep
doing
tweeting
about
it
beforehand.
In
a
general,
I'm
just
trying
to
bridge
a
communication
gap
say
a
deprecation
is
coming
so
every
every
month,
every
week
we
keep
reminding
people
about
it,
but
this
is
all.
This
is
mostly
for
a
end
user
perspective,
but
the
whole
framework
we
have
now
is
for
contributors,
so
we
might
have
to
do
better.
A
Great
point:
yeah
exactly
this
kind
of
stretches,
our
scope,
we've
really.
Our
goal
has
been
to
amplify
contributor
experience
and
this
scenario
is
one
of
like
contributors,
communicating
deprecation
effectively
yeah
so
far
beyond
our
initial
scope.
So
there's
kind
of
like
part
of
my
brain
that
says
well,
let's
focus
on
our
main
scope
and
make
sure
we
support
contributors
by
them
having
the
messages
they
need.
So
they
don't
feel
stressed
when
you
know
something
like
this
blows
up
or
is
perceived
to
blow
up
and
then
secondarily
we
can
talk
about.
A
D
So,
like
rajula
said
when
rajula
was
mentioning
like
we
should
periodically.
I
mean
frequently
tweet
about
that.
Like
one
instinct
struck,
my
head,
like
the
helm
to
duplication
like
matt
farina
was
continuously
like
tweeting
about
that
and
most
of
the
helm
core
contributors
were
actually
tweeting
about,
like
helm2
support
is
gonna
going
to
be
end
up
left
by
number
13.,
and
I
remember
the
november
13th
date,
because
I
have
saw
so
much
of
feats
about
that
yeah.
F
D
As
I'm
gonna
just
gonna
say,
the
same
thing
like
as
rajula
said,
like
its
contributors
is
for
contributors
handle
and
if
these
kind
of
tweets
are
hap,
if
these
kind
of
duplications,
if
you
want
to
reach
out
to
the
wider
bigger
audience,
we
also
need
the
kubernetes
handle
as
well
to
be
like
kind
of
supported.
So
because,
if
you
look
at
its
contributors,
it
is
totally
for
the
contributors
and
the
people
who
subscribe
to
that
are
like
most.
D
D
A
Yeah,
we
have
the
connections
to
do
so.
We
we
don't
own
the
kubernetes
handle,
but
we,
the
cncf
team,
does-
and
we
have
friends
in
that
space
where,
if
we
told
them
basically
to
help
prevent
concern
around
deprecation,
please
retweet
one
of
these
tweets
each
week.
All
we
have
to
do
is
find
out
where
to
email
them
to
get
them
to
do
it
and
or
whether
we
at
them
to
do
it
it'll
happen.
A
That's
I
mean
that's
a
really
important
message.
I'm
glad
you
said
that,
like
you
reinforced
that
idea
like
that
see,
that's
a
pattern
that
other
people
can
look
to
us
to
teach
them
they're
like
how
do
we
when
def,
if
we
do
get
pulled
into
the
into
the
release
team
when
they
ask
like?
So
how
do
we
do
this
better?
It's
like
okay,
create
a
frequent
tweet
strategy,
and
what
does
that
mean?
A
E
Adding
to
what
you
said
matt,
I
think
I
think,
coming
to
the
the
whole,
the
gita
bishop,
which
started
this,
I
think
we
really
need
to
have
a
whole
skeleton
framework
of
our
deprecation
happens
like
how
how
do
we,
as
communications
are
part
of
the
whole
release
cycle
like
what
like?
What
is
our
role?
What
do
we
get
as
input?
What
do
we
do,
or
what
do
we
give
and
put
us
to
some
other
team?
So
maybe
we
have
to
define
something
like
that.
A
Yeah,
I
you're
absolutely
right
and
a
a
healthy
reminder.
This
is
our
first
release,
as
with
this
team
existing
in
any
substantial
form,
so
yeah,
I'm
super
impressed
that
people
know
we
exist,
which
was
our
first
goal
and
that
and
also
that
they
want
us
involved
in
the
future.
Our
second
goal
we're
doing
it
we're
winning.
D
It
gives
a
quick,
I
guess,
a
quicker
one,
for
that
would
be
like
figuring
out
the
checklist
for
all
the
working
group
and
the
deliverable
checklist
for
all
the
working
group
and
inject
ourselves.
On
top
of
that,
saying,
like
inform
to
this
particular
subgroup
like
what
is
that
going
to
be
like
either,
and
we
can
use
that
as
for
as
a
source
for
our
twitter
tweet
as
well
so
say,
for
example,
if
secretly
is
gonna
hold?
D
Okay,
the
this
is
the
first
cut
that
we
are
doing,
or
this
is
the
freeze
date,
so
they
should
be
like
informing
that
the
first
check
checkbox
is
that
they're
going
to
check
off
is
like
okay,
I
informed
of
the
sponsor
community,
the
next
check
box.
If
you
need
a
tweet,
raise
an
issue
here
and
like
say,
sig
docs
is
gonna
hold
something
for
like
they're
gonna.
Do
some
changes
on
the
documentation
on
the
the
ui,
the
look
of
the
ui,
for
example?
D
A
I,
like
a
lot
of
what
I
heard,
I
I
will
say
like
we
are
a
very
optional
part
of
people's
workflow
and
the
way
we
become
non-optional
is
because
we
add
value
and
everything
you
just
said
will
add
value,
and
I
think
if
we
can
get
on
the
same
page
as
a
team
on
how
we
capture
those
practices
put
them
into
a
repo.
So
they
can
be
repeated.
A
I
mean
under
the
the
comms,
I'm
gonna
message
it
in
chat.
If
you
go
to
our
repository
in
kubernetes
community,
I
could
see.
I
can't
quite
tell
whether
it
would
just
be
a
single
new
markdown
file,
where
you're,
just
you're
walking
through
like
how
we
support
feature
changes
per
sig
like
that
as
a
playbook.
A
But
we
we,
I
want
to
find
out
like
what
is
the
methodology
like
what
is
the
way
in
which
we're
organizing
our
thoughts
as
a
team
and
putting
them
and
documenting
them
here,
because
whether
we
call
them
playbooks
or
campaigns
or
whatever,
like
we
have
these
strategies
that
if
we
write
them
down,
we'll
be
really
good
at
them.
And
then
we
can
easily
make
an
issue
saying
like
support
this
community
through
this
process
for
the
next
x
months
and
and
boom,
we
become
like
a
real
service
organization
that
is
organized.
That
way.
D
A
I
was
saying
everything
you
just
listed
would
go
into
a
markdown
document
in
here
and
then,
when
something
pops
up
well,
either
we
proactively
go
find
groups
that
are
are
adding
new
features
and
we
use
that
strategy
to
like
you
are
the
shepherd
for
the
next
architectural
change
and
you
make
a
copy
of
that
check
all
the
boxes.
As
you
go
yeah
I
don't
know,
I
don't
totally
know
the
workflow
yet,
but
I
think
there
is
like
we're
starting
to
build
these
practices
just
just.
A
Yeah
a
great
point
that
caps
are
the
source
of
truth
here,
but
if
we
need
a
translator
for
that
source
of
truth,
we
could
rely
on
the
release.
Engineering
team,
like
that's
what
their
job
ultimately
is
to
know
what
that
means
and
how
to
message
it.
So
they
could
do
the
immediate
translation
raise
the
alarm
to
us
and
then
we
can
based
on
what
they
are
saying.
We
could
then
put
put
in
place
the
strategy
to
make
sure
that
information
is
known.
A
Yes,
I
I
don't
I
like,
for
those
that
are
interested
in
the
very
technical
nuance
part
of
it.
You
are
more
than
welcome
here,
of
course,
and
you
can
go
read
the
caps,
but
my
hope
for
this
group
is
that
we
get
further
and
further
away
from
code
contra
contribution
as
a
requirement
and
deep
kubernetes
expertise
as
a
requirement
and
really
try
to
make
a
space
where
non-code
contributors
who
enjoy
marketing
and
enjoy
communicating,
can
help.
A
Others
tell
great
stories
so
kind
of
jump
into
the
next
section
there,
but
I
I
think
we
can
do
that.
Like
I,
the
more
I
talk
to
people
in
kubernetes
communities
and
the
response
we've
got
from
that
talk
last
a
couple
weeks
ago.
Rajula
the
feedback
I
got
was
people
were
mostly
excited
about
the
idea
that
there's
a
place
for
people
where
they
don't
have
to
feel
like
they
are
in
the
wrong
place
because
they
can't
code.
A
A
E
Yeah,
adding
to
everything
I
understand
that
we
might
have
to
get
involved
in
the
process,
more
get
more
understanding
in
order
to
jot
down
the
strategies.
I
think
I
think
this
really
cycle
chris
was
by
as
a
shadow
probably
like.
We
can
get
more
feedback
from
you
and
understand
how
things
happen,
or
maybe
one
of
us
can
understand
the
communication
in
the
next
release,
like
probably
by
more,
involving
ourselves,
probably
we'll
understand
how
things
work
internally
and
then
we
can
clearly
chart
on
the
strategies.
A
Cool
I
I
like
that
as
a
that's,
a
fantastic
point.
We
I'll
I'll
check
chris's
schedule
see
if
he
can
join
next
week
and
we
make
that
kind
of
the
future
topic
of
let's
focus
on
his
experience
being
a
release
shadow
and
we,
you
know
just
make
it
a
working
session
where
we're
taking
notes
on
what
he
found
and
seeing.
If
there
are
places
we
can
plug
in
yeah
yeah.
A
Cool
all
right:
let's
transition,
I'm
gonna
start
making
this
a
very
hard
transition.
So
people
know
if
you
are
here
to
talk
about
more
marketing
things
you
can
drop
at
this
point.
If
you
are
interested
in
how
we
make
the
sausage
of
the
the
bots
that
help
us
communicate
stay
on,
it
will
talk
about
code,
but
you
don't
have
to
so.
With
that
in
mind,
karthi
kane
love
to
start
with
yours,
because
I
think
getting
to
the
next
step
of
the
contributor
tweets
where
it
is
a
non-code
contribution
would
be
incredible.
A
D
D
Cool
right
all
right,
I'm
going
to
click
that
and
then
share
my
screen.
So
what
I've
did
here
is
like
I
kind
of
used.
The
skeleton
like
rajula
did
and
it's
a
simple
javascript
coding
that
the
kind
of
an
actions
file
that
creates,
so
you
all
you
want
to
do
is
like
you're,
going
to
start
creating
a
tweet.
D
What
we
want
is
a
template
for
asking
the
users
to
provide
the
tweet
content
so
once
they
provide
the
tweet
content.
The
very
simple
thing
I
am
doing
here
is
just
to
validate
whether
it
is
exceeding
the
tweet
length
or
not.
I
was
actually
using.
I
was
also
planning
to
implement
the
scheduler
tweets,
but
it's
kind
of
little
hard
for
schedule.
The
tweets
to
implement
on
a
free
user
free
normal
generic
twitter
account.
D
D
I
didn't
expect
that,
so
it
passes
the
tweet
content
and
then
it
says
like
okay,
this
is
the
tweet
content,
and
this
is
the
pr
and
it
uses
the
github
actor
username
to
cc
the
pr
as
well,
and
it's
it's
unassigned
at
this
point
we
can
actually
add
options
for
assigning
it
to
anyone.
Currently,
what
I'm
doing
here
is
like
I'm,
not
adding
anything
for
the
merge
process,
so
the
merge
must
happen
manually
once
you
merge
it.
The
the
twitter
feed
together
stuff
that
rajula
brought
in.
D
So
that
is
the
same
actions
that
I'm
using
as
well.
So
once
the
merge
happened,
that
particular
action
will
automatically
take
care
of
the
tweeting,
and
this
merge
is
something
which
is
manual.
We
can
actually
automate
that,
but
one
thing
what
I
want
is
like
what
I
thought
in
my
perception
is
like.
We
need
a
gatekeeper
for
doing
that
so
yeah,
so
that
merge
should
happen
with
the
gatekeepers
approval,
so
we
can
actually
add,
approve
or
something
like
that
as
a
command.
But
for
now
it's
like
click
on
merge
button
and
then
merge.
D
D
D
Tweet
is
like
you
also
ask
a
human,
readable,
tweet
time
in
the
issue
and
then
like
what
I
was
thinking
is
like
okay,
pass
that
file
and
store
it
in
like
up
to
tweet
or
something
like
that.
In
a
same
in
the
same
repository
using
ci
cd
like
using,
you
have
actions
checking
that
file
in
the
ci
and
then
one
in
a
different
format
like
not
in
the
dot
tweet,
because
when
you
have
a
dot
tweet
file,
the
twitter
put
together.
D
Ci
will
automatically
tweet
that
if
there
is
a
new
dot,
tweet
file,
so
once
the
time
is
up
for
the
tweet
pull
that
file,
rename
it
and
say
like
dot,
tweet
and
put
it
in
the
folder,
where
you're
actually
having
it
and
then
delete
it
from
the
previous
folder.
And
once
you
check
in
once,
you
merge
auto,
merge
that.
Then
this
should
kick
in
and
then
it
should
automatically
tweet.
A
A
D
D
E
A
I
just
I
just
want
to
add
yeah
it's
it's
cool
ph.
I
want
to
make
sure
that
you
have
permission
to
merge
so
that
you
can
merge
things
in
your
local
time
zone
as
well,
so
that
that's,
if
that
isn't
the
case,
if
you
don't
have
permission
on
the
the
repo
yet
please
open
an
issue
in
contributor
tweets,
saying,
like
you
need
permission
to
merge
it
and
we'll
follow
that
up.
A
D
A
Cool
that
is
that's
perfect
and
I
I
think
you
know
I
want
to
be
respectful
of
time.
I
think
we
try
to
end
at
10
before
the
top
of
the
hour,
so
gonna
wrap
up
this
call
and
say
any
any
last
closing
thoughts
on
how
far
we
got
there's
a
lot
to
keep
talking
about,
but
we'll
same
bat
channel
same
bad
place
in
a
in
a
couple.
A
B
A
F
B
A
Good
y'all
all
right
well,
thank
you
so
much
for
joining
thanks
for
the
the
awesome
progress
looking
forward
to
seeing
updates
in
the
kubernetes
community
space
and
mark
your
calendar
for
next
week,
there's
stuff
that
is
very
time
zone
friendly
and
it
should
be
pretty
goofy,
and
I
want
to
play
video
games
with
at
least
a
few
of
you.
So
regional
we've.