►
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
Welcome
welcome
to
another
wonderful
friday
of
the
upstream
marketing
crew.
We
are
happy
to
have
you
here.
It
looks
like
our
usual
squad,
so
we'll
skip
the
formalities
and
roll
right
into
it.
So
we've
got
some
cool
things
going
on
I'd,
say
I
before
we
jump
to
the
really
exciting
thing
from
rajula,
not
to
say
the
other
isn't,
but
I'd
say
the
launch
of
the
the
dev
community
site
or
the
contributor
site
launch
is
huge.
A
So
congratulations
bob
and
many
other
people
that
are
supported
that
process.
But
you
were
on
point
for
a
lot
and
yeah.
Congratulations!
That's
you.
A
I
hope
we
can
get
into
a
little
bit
of
strategy
there.
I
want
to
see
what
we
can
do
going
forward,
but
I
think
what
definitely
deserves
a
focus
to
start,
because
it's
been
such
a
herculean
effort
by
rajula
is
getting
this
slack
announcement
bought,
live,
it
is
officially
merged
in
leaves
us
with
we're
almost
building
the
voltron
or
the
pieces
of
the
puzzle
together
to
be
able
to
communicate
in
like
one
fell
swoop,
so
huge
congrats
rajula
that
was
awesome,
dope
and
yeah.
A
A
Oh
good,
okay,
cool!
So
since
we
try
to
be
editorially
focused
we'll
just
kick
it
off
with
the
editorial
calendar
and
by
calendar
I
mean
loose
kanban
of
things
we
hope
to
maybe
write
about
is
more
realistic
and
be
supportive
of
in
the
process.
To
the
best
of
my
knowledge,
I
haven't
talked
to
lubano,
I'm
clicking
on
how
to
say
her
name
exactly
right,
but
where
there's
a
article
on
usability
and
progress,
but
I
haven't
connected
back
with
the
author,
but
can
work
on
that.
I
think
caslin.
A
C
A
Okay,
yeah
I'll
just
send
her
a
little
pink
see.
If
there's
anything,
we
can
do
to
be
helpful.
Yeah
did
got
very
busy,
so
that's
probably
on
hold
and
I
don't
think,
there's
anything
else
that
was
sticking
out.
A
A
D
Yeah
so
finally
we
got
it
deployed,
so
I
think
the
next
steps
are.
We
need
to
first
decide
on
the
name
of
this,
the
display
name
on
the
display
picture,
so
that
is
the
first
thing
and
then
actually
put
down
all
the
instructions
in
the
meeting
document.
I'm.
A
Can
you
remind
us
where
where's
the
home,
where
like,
where
does
it
live
in
github.
D
Oh
yeah,
I
can
link
that
for
now.
Like
all
of
you,
if
you're
part
of
the
user
group,
you
should
be
able
to
see
that
in
the
shortcuts
button
on
the
left
on
the
bottom,
oh
cool
yeah,
I
put
up
the
instructions
how
to
post,
I'm
still
not
sure
if
we
can
post
in
the
announcements
channel,
because
it's
only
for
admins.
B
Yeah,
I
think,
to
do
that.
We'd
have
to
promote
it
to
admin.
I
can
also
individually
add
it
to
be
able
to
do
so.
D
A
Yeah
and
yeah,
we
don't
exactly
want
to
explode
into
announcements
with
some
tests,
so
yeah
having
a
little
bit
of
a
game
plan
will
be
quite
helpful.
A
B
The
the
next
thing
would
be:
usually
our
announcements
are
strictly
for
releases
or
when
there's
a
security
vulnerability,
so
we
can.
Actually.
I
don't
think
there
hasn't
been
a
announcement
yet
for
119
in
there
yet
so
it
might
be
well,
it's
a
little
late.
B
You
might
be
able
to
test
it
with
a
release
post
for
a
119
or
release.
You
know
message
for.
A
Sure
so
I
guess
maybe
we
take
a
a
step
back
from
the
specific
test
for
announcements
and
talk
about
like
what.
What
are
what
have
been
the
colloquial
like
rules
of
who
has
access
to
announcements
and
who's
kind
of
accountable
for
making
sure
announcements
get
out.
B
So
it's
it's
only
the
slack
admins
and
then,
when
someone
has
something
that
they
want
to
post,
usually
it's
a
vulnerability.
We
promote
them
like
we
can
explicitly
add
permissions
for
them
to
be
able
to.
You
know,
talk
in
that
channel
for
a
brief
period
post
that
channel
for
a
period
of
time.
B
B
A
psc
product
security
committee
so
like
anytime,
there's
a
cve
it
gets
announced
in
there.
It's
all
supposed
to
discuss
something
like
kdev.
It's
probably
our
largest
announcement
channel
like,
inter
like
avenue
for
not
avenue,
item
item
that
gets
like
broadcast
everywhere.
A
Yeah,
well
I
mean,
and
that
that's
perfect,
we
can
kind
of
reverse
engineer.
How
are
these
channels
used
so
that
if
we
create
tooling
around
it,
it
is
in
support
of
that
usage,
not
in
contrast
of
it,
or
we
can
clearly
differentiate
like
why
somebody
would
want
to
announce
something
like
I've
seen.
A
You
know
chris
and
he
he
posts
in
there,
but
he's.
B
Yeah,
that
was
just
for
for
kubecon,
that's
the
other
thing
that
gets
possible
is,
like
you
know,
keep
con
is,
is
the
dates
posted,
but
if
you
scroll
back
through
like
it
is,
it
is
fairly
limited
in
what
we
post.
A
B
Yeah,
it's
usually
messages
targeted
towards
end
users,
not
contributors.
Most
contributors
just
meet
the
channel.
A
D
D
B
Catherine,
I
actually
did
did
most
of
that
herself.
She
spun
up
her
own
slack
to
test
everything
with.
D
Okay,
so
there
is
one
thing
with
us
blackboard,
so
we
are
using
a
paid
api,
so
the
user
group
says
not
in
the
free
version
yeah,
but
I
did
do
most
of
the
testing.
So
we
can
just
do
a.
A
So
I'm
I'm
having,
as
as
we
talked
about
the
announcement
channel
kind
of
getting
to
a
question
of
what
it,
what
is
the
right
usage
of
this
spot
and
based
on
what
we've
said
so
far
and
are
understanding
the
announcement
channel.
Ironically,
I
don't
know
if
announcement
bot
would
make
sense
to
be
used
with
the
announcement
channel,
maybe
at
all
right
like
it.
So
it's
kind
of
a
question
of
when
do
we
use
this
and
why
the
multi-channel
communication
is
a
nice
feature
of
it.
A
But
like
is
there
a
channel
just
for
contributors
that
we
want
to
regularly
announce?
To?
I
don't
know.
A
D
Very
good,
I
think
it
comes
back
to
what
do
we
name
the
part,
because
it's
really
misleading.
If
you
name
an
announcement.
A
Yeah
yeah,
but
I
think
we
have
to
get
to
that
answer
by
understanding.
What's
the
point
of
the
bot
like
it's,
it
won't
be
to
announce
two
announcements
so
yeah
there
will
be
a
bit
of
a
conflict
of
term
there
and
our
intention
is
like.
When
are
we
going
to
use
this
and
why?
If
we
can
answer
those,
we
can
figure
out
the
name
and.
B
The
places
where
I
think
most
the
communication
be
targeted,
it
would
be
kdev
other
things
like
the
contributor
summit
channel.
There
are,
we
will
sometimes
blast
messages
to
all
the
individual
sig
channels.
B
This
was
like,
I
think
it
was
the
survey
or
there
was
something
like
christoph
went
back.
I
forget
what
it
was
for,
but
he
literally
went
into
every
channel
and
sent
a
message
and
then
like
every
mailing
list
and
sent
a
message.
B
D
B
A
Yeah
code
free
is
coming
up,
so
survey
requests,
so
this
is
shockingly
not
shockingly
aligned
to
our
overall
com
strategy
of
like
when
do
when
is
action
required
so
like
if
we
use
our
own
that
thing
that
jonas
and
I
worked
on
with
paris
like
what
are
like
the
four
types
of
messages
that
we
send
send
out
and
when
or
when,
and
where
do
we
send
them
out?
So
like
I'm,
loving
this,
but
I
need
to.
B
What
what
might
be
worthwhile
would
be
bringing
it
up
on
the
release
team,
like
you,
know,
taylor's
on
the
well.
No
I'll
rather
release
team,
but
jeremy
is
and-
or
you
know,
specifically
the
you
know-
comms
team,
although
comms
does
tend
to
be
later,
but
you
know
change
the
role
books
that
they
have
to
file
an
issue
for
announcement
regarding,
like
enhancements,
free
enhancement,
freeze
or
anything
like
that
for
messages
to
be
blasted
out
to
slack
they
will
handle
the
the
kw
email.
B
Yep
they
they
tend
to
handle
the
the
kdev
email
and,
like
sometimes
the
posting,
to
the
leads
list,
but
they
are
not
saying
anything
in
slack
outside
of
you
know
a
couple
channels
that
have
the
sick
or
these
people
in
them
and
and
be
like
hey
freeze,
is
coming
so
that
might
be.
A
This
is
so
cool
yeah,
I'm
starting
to
realize,
like
the
user
of
this
tool
is
probably
not
us
like
we,
we
may
very
rarely
need
to
use
it
but
like
if
we
can
offer
it
as
a
service
to
the
right
people
like
we
kind
of
need
to
socialize
it
I'm
hearing,
we
need
to
socialize
it
with
a
few
different
groups,
release
security,
steering
especially
see
if
it
resonates
for
any
of
them
and
that
they'd
be
willing
to
have,
like
their
permission,
set
aligned
to
the
spot
and
then
basically
say
you
know,
use
it
with
these
kind
of
guidelines
like
we
set
the
guidelines,
we
offer
the
tool
but
like
we
don't
own
comms
in
that
way,
because
that's
kind
of
not
how
kubernetes
works
cons
is
from
people
to
people
like
not
through
a
single
mouth
yeah.
A
B
A
A
A
It
says:
multi-channel
comms,
if,
if
anyone
needs
a
reminder,
what
that
is,
we
kind
of
have
four
classifications
of
action
required
priority
information,
feedback
appreciated
and
in
case
you
missed
it
as
like
the
don't
worry
about
it
too
much
and
intentionally
broke
it
out
into
those
different
ways
and
like
the
goal
from
kind
of
day,
one
of
this
group
has
been
to
can
we
make
a
meaningful
connection
between
like
these
different
categories
of
conversation
and
the
different
channels
of
communication
that
people
need
to
need
to
hear
in
acknowledging
that
like
for
many
things,
people
might
need
to
hear
it
more
than
once
and
they're
not.
A
A
So
all
right
yeah,
I
think,
maybe
a
little
bit
more
drawing
out
how
these
dots
are
going
to
connect
anyway.
That
clearly
gets
me
more
excited
than
everybody
else.
So
I'll,
I
think
I've
got
the
action
of
kind
of
like
trying
to
communicate
the
vision
of
how
this
connects
into
our
multi-channel
okay.
So
what
are
the
other?
You
call
them
ais.
Don't
you
bob.
A
A
C
D
New
user
groups,
so
it's
easy
to
get
access
to
other
teams.
A
E
D
So
in
that
case,
once
we
give
access,
so
we
can
have
ask
them
to
create
a
github
issue
or
something
when
they
need
some
feedback.
So
we
can,
let's
go
on
from
there.
A
That's
fantastic,
okay,
cool!
I
was.
I
was
curious
about
that
in
another
technical
question
playing
around
with
it.
Is
it
possible
to
have
like
a
like
a
single
select
like
choose
all
channels
kind
of
from
the
pick
list.
B
Maybe
one
possible
idea,
as
a
sort
of
feature
request
would
be
like
have
groups.
A
Yeah,
I
guess
I
mean,
like
all
cigs.
I
don't
think
that
starts
with
sing,
because
we
I
just
look
394
channels
and
that's
insane,
but
also
normal
when
you
have
like
50,
000
or
100
000
people
in
one
place.
B
One
thing
that
we
can
potentially
do
if
there
is
grouping
capability
added,
is
when
a
sig.
When
we
make
changes
to
six
dot
yaml,
we
could
update
the
generator
to
automatically
add
the
you
know
list
of
the
sig
to
something,
but
that
also
would
mean
it's
configured
have
to
be
in
k
community.
So
I
don't
know
about.
D
A
Yeah,
I
think
the
slack
support
grouping
multiple
channels
as
a
single
yeah
technical
question,
slack
support
grouping.
B
D
A
Okay,
usually
we'll
check
that
out.
B
The
the
other
big
ai
was,
you
know,
talking
to
sig
release
essentially
having
a
discussion,
or
you
know,
secretly
slash
the
release
team.
A
B
A
Yeah,
does
anyone
feel
you
may
not?
You
don't
have
to
know
all
the
answers
of
what's
going
on
here,
but
is
anyone
interested
in
participating
in
this
group
as
more
of
a
like
kind
of
a
marketing
manager
like
and
and
wanting
to
reach
out
to
sig
release
figure
out
how
to
communicate,
tell
them
how
we
can
help
or
report
back
to
us,
and
then
we
can
work
on
that
as
a
team.
F
So
I
I'm
not
volunteering,
I'm.
D
F
Is
like
to
familiarize
working
group
naming
amongst
the
k-8
contributors,
so
I
proposed
like
we
could
use
our
contributor
tweets
to
push
it
out
loud,
and
they
also
wanted
to
know
like
how
to
reach
out
to
that
and
that's
the
reason
like
we
are
like
the
one
thing
like
we
are
ending
with
is
like
the
process
is
for
rest
of
the
working
group
or
rest
of
the
six
to
reach
out
to
us
to
submit
a
tweet
and
it
would
be
like
automatic
or
it
would
be
manual
because,
as
far
as
I
know,
I
guess
like
even
today,
like
the
shoutouts
were
sent
out
by
kaislyn
like
castling
manually,
if
I'm
not
wrong.
F
So
that
is
one
like
there
is
one
group
I'm
working
with,
as
I
am
like
part
of
that
working
group.
A
Yeah
there
there's
a
there's
a
lot
of
different
ones
that
play
in
in
our
community.
So
no
it's
it's
smart
to
focus
just
for
your
own
sanity.
We
don't
have
to
get
somebody
to
own
this.
This
action
item
right
this
moment.
I
think
it's
it's
kind
of
good
for
us
to
iterate
it
out
and
we'll
we'll
slow,
yeah
we'll
creep
our
way
there.
C
A
Yeah,
you
were
absolutely
right,
that's
literally
what
he
wrote
today
and
is
like
three
lines
down
from
where
I'm
typing.
So
I
think
we
can
tell
chris
to
do
something
and
see
if
it
works.
I.
A
F
F
Totally,
that's
great
is
it
is
it?
Is
it
worth
creating
an
issue
on
having
checkboxes
across
against
all
the
sigs
listed
there,
and
probably
we
could
reach
a
lazy
consensus
after
like
a
couple
of
weeks
or
like
a
couple
of
months
after
that
to
just
to
track,
because
if
there
is
no
issue,
we
would
like
definitely
miss
the
list
of
sigs
that
there
are.
A
Sir,
I
I
didn't
follow
why
why
we
need
to
list
out
all
the
sigs?
What
were
you
thinking.
F
So
that
we
can
like,
if,
if
that,
should
it
wouldn't
happen?
But
if
crazy
is
not
part
of
the
release
team,
then
we
need
like
at
least
we
can
amongst
ourselves
like
pick
five
or
four
different
sets
and
independently.
F
We
can
reach
out
to
them
and
like
we
can
collect
the
data
and
tell
them
what
we
are
trying
to
do
and
like
get
the
sentiment
from
them
and
then
we
can
update
in
the
issue
and
they
say:
okay,
I
have
reached
out
to
the
sick,
and
this
was
the
update
from
there
and
we
can
pick
it
up
from
like
we
can
take
it
from
there.
As
a
group.
A
Cool
yeah,
I
completely
follow
what
you're
saying
I
I'm
kind
of
happy
to
start
with,
like
I
don't
my
only
resistance
to
it.
I
think
it's
a
great
overall
idea
is
like
I
don't
want
to
be
on
that
issue.
That
sounds
like
really
really
tedious,
and
I
don't
know
if
we're
we,
as
like
a
team,
know
what
we'd
want
to
say
yet.
So
there
are
enough
steps
ahead
of
that
that
I
feel
like
that's
a
little
further
ahead
of
like
what
are
we
communicating,
how
I
think
off
the
top.
A
My
head
right
now
is
like
we
have
some
cool
tools
and
we
have
a
like
kind
of
a
philosophy
on
comms,
but
I
don't
think
we
all
know
it
equally
well
and
we
don't.
We
haven't,
come
to
a
consensus
on
internally
of
how
all
the
pieces
fit
together
and
if
we
kind
of
keep
doing
what
we're
doing
individually
and
get
to
a
place
where,
like
those
pieces,
fall
together
and
we
can
all
communicate
them,
then
we
go
out
and
disseminate
that
information.
That
sounds
fantastic
yeah.
A
I
just
feel
like
yeah
we've
got
those
steps
ahead
of
us.
I'm
vaguely,
holding
on
to
the
like
I'll
I'll,
be
responsible
for
putting
the
pieces
together.
Result
is
deep
on
the
technical,
and
I
think,
each
of
us
individually,
doing
really
anything
valuable
to
this
group
is
valuable
in
and
of
itself.
A
F
F
Trying
to
yeah
no,
no,
no!
I
was
just
trying
to
like
plant
those
thoughts
so
that
we
could
come
to
the
consensus
and
that's
what
we
are
doing,
and
this
is
fair
yeah.
Definitely
this
is
this
should
be
fun
and
yeah.
Introducing.
A
A
You're
totally
right
that
that
is
a
goal
I
I
guess,
yeah.
D
No
marketing
at
the
group,
the
marketing
team
to
all
the
stuff,
yeah
yeah.
I
think
I
think
we
can
actually
like
maybe
use
the
bot
post
and
multiple
six
channels
tell
them
that
we
are
so,
and
so
we
have
a
word.
You
want.
A
A
Maybe
if
we
get
some
air
coverage,
like
you
know
what
we'll,
if
we
can
get
the
regexi
type
thing
together,
we
we
run
the
message
by
bob
and
maybe
get
like
another
sign
off
like
some
consensus
in
contrib
contributes
that
this
is
kosher,
and
then
we
send
like
one
blast
message
and
we're
like
we'll.
Never
do
this
again,
but
just
know
that
we
exist.
D
D
Also,
keep
tweeting
a
lot
about
ourselves,
yeah.
B
The
reality
of
the
situation
is
that
is
not
always
the
case.
A
Okay,
well,
that
was
a
lot
of
bop
thinking.
What
anyone
else
have
any
thoughts
on
that
before
we
kind
of
put
it
aside
for
a
minute
and
kind
of
keep
working,
we'll
keep
working
on
the
ais
that
we
already
listed
out,
but
kind
of
move
forward
to
the
next
part.
A
Okey
doke
need
tweet
for
apac
sig
contrabax
meetings.
A
Oh
shoot
yeah
that
got
stuck
in.
B
A
Added
that,
so,
let's
do
that
after
so
see
somebody
added
the
neat
tweet
for
apac
sig
meetings.
What
can
we
do
to
help
there?
Who
added
that
in.
E
Yeah,
I
edited
it.
I
guess
I
forgot
put
my
name
in
there
right,
so
we
are
having
these
bi-weekly
meetings
for
apac
contrabax
group
and
the
trouble
that
we
have
is.
We
are
not
seeing
much
traction
right,
I
mean
we
have
got
couple
of
people
joining
in,
but
it's
always
those
two
three
people
that
come
over
and
we
had
a
call
yesterday-
and
I
was
just
wondering
if
there
is
a
way
we
can
amplify
that,
of
course,
tweeting
is
one
way.
A
Absolutely
yeah,
so
I
wonder:
do
you
have
access
to
well?
Okay,
whether
you
have
access
to
merger
or
not?
I
think
it'd
be
great.
If
the
first
thing
comes
to
mind
is
like
submit
tweets
to
the
spot.
C
E
This
happens
during
apac
day
time
right,
so
we
need
to
make
sure
that
you
know
it's
around
that
time
so
that
you
know
when
people
see
it
they
can
just
come
over
and
join
it.
Yeah.
F
So
I
have
a
little
update
and
really
like
a
quick,
quick
demo
on
the
poc
that
I've
done
for
the
tweet
automation.
F
Let
me
share
the
screen
and
okay:
oh
yeah,
okay,
let
me
know
if
everyone
can
see
my
screen.
What
I
did
is,
as
I
said
as
I
was
like
trying
to
explain
on
the
other
day
having
having
created,
so
we
change
the
temp
and
we
can
change
everything.
However,
we
would
like
to
when
I
click
on
the
issue,
so
I
have
a
sample.
F
I
have
created
it
so
very
simple.
B
F
F
A
F
F
Requests
right
so
when
I,
when
I
say,
get
started
it
is
the
issue
template
basically,
so
I
have
given
some
comments
and
I'm
using
this
as
later
limit
for
parsing.
So
technically,
when
I
say
something
like
this.
C
B
F
A
F
Yeah,
so
I've
shot
that
url
already.
I
can
share
it
again
so
when
you
create
a
tweet
content
there,
what
I'm
doing
is
like
I'm
parsing
the
content
file
and
essentially
putting
merging
it
back
into
the
same
tweet
folder
like
regular,
is
expecting
with
a
certain
like
function.
Certain
configuration,
like
you
can
say,
like
dot
tweet
like,
however,
the
extension
you
want
and,
however
the
naming
of
the
file
you
want
so.
D
F
Share
the
url,
please
yeah
great,
oh,
I
don't
see
the
comments
or
the
discussion
board
in
the
slack.
Oh
sorry
in
the
zoom,
so
I'll
share,
I'm
just
opening
up
this
slack
now
so
once
you
create
that
I'm
pausing
it
and
I'm
actually
pushing
it
into
the
repository.
D
F
So
I'm
gonna
add
it
here.
Thank
you.
So
what
I
was
thinking
about
the
scheduling
process
is
like
in
github
issues
like
we
can.
Actually
again
we
can
run
cron
job
kind
of
actions,
so
we
can
run
one
in
30
minutes
to
figure
out
like.
Is
there
any
tweets
that
are
supposed
to
go
out
in
that
30
minutes
window
and
we
can
execute
that
tweet
to
turn
the
handle.
A
F
F
The
corresponding
scheduled
time
and
then,
if
the
schedule,
the
time
is
within
that
current
13
minutes
window
it
just.
D
A
F
Right,
so
what
the
entire
internet
workflow
would
be,
a
user
would
be
coming
in
and
they
would
be
like
kind
of
creating
an
issue
with
the
present
poc.
What
I'm
doing
is
like
once
the
issue
is
created,
I
am
merging
it,
but
what
we
can
do
is
like
once
we
say
like
close
or
something
like
that:
the
first
houses
some
come.
We
can
merge
with
dot
v
in
the
folder
and
then
with
the
corresponding,
like
user
friendly
specified
by
the
creator
of
the
issue.
F
This
particular
round
job
would
run
and
like
checks,
whether
if
that
particular
time
zone
is
time,
specific
time
is
within
the
30
minutes
window
and
then
it
will
just
send
it
to
it.
A
D
Yeah,
I
think
it
really
helps
test
the
merge
process,
so
once
you
verify
and
then
it's
merged,
I
think
it's.
This
is
a
better
way
to
schedule.
Trades.
D
Just
one
quick
question:
when
you
are
converting
from
an
issue
to
a
pull
request,
so
we're
going
to
have
to
use
it,
do
it
through
a
bot
or
a
new
github
account,
so
that
github
account
should
have
signed
the
cla
and
everything
for
the
browbot
and
everything
to
work.
So
we
need
to
figure
that
out.
I
see
oh
okay,.
F
B
The
bot
will
have
to
be
added
to
like
the
kubernetes
sig
org,
and
then
we
have
some
other
stuff
when
it
comes
to
setting
up
ignores
for
bot
accounts.
The
other
thing.
F
Sorry
so
so
currently,
what
I
was
doing
is
I'm
using
the
github
actions
and
the
secret
from
the
github
actions
and
modulating
it
via
github
actions.
So
there
is
no
bot
involved
in
there.
B
This
is
mostly
just
for.
Actually,
I
need
to
think
about
that.
I
think
we
can
probably
get
around
it.
A
Could
we
take
a
like
we're
getting
towards
the
top
of
the
meeting,
so
I
just
want
to
throw
out
there?
Could
we
maybe
carthage?
A
Can
you
write
out
how
this
works
a
bit
in
the
readme
like
that
way,
we
can
take
a
little
bit
more
time
to
think
about
the
workflow
of
it
and
what
steps
it
might
might
need
like
what
credentials
it
needs,
whether
it's
responding
to
them
to
the
merge
request,
action
or
just
the
file
existing,
because
I
I'm
getting
a
little
lost
in
it
and
then
like
we
can
all
asynchronously
think
about
how
it
could
work
into
the
flow.
But
it's
absolutely
an
awesome
awesome
extension
to
what
we're
planning
to
do
so.
A
Oh
great
great
call
yeah
if
you
could
yeah,
throw
it
on
youtube
or
whatever
and
yeah
we'll
we'll
be
able
to
walk
through
there
yeah.
I
just
there's
a
lot
of
nuance
going
on
and
it's
really
thoughtful
and
I
don't
want
us
to
lose
it
by,
like
rushing
towards
the
end
of
the
meeting,
make
sense
cool
all
right,
we'll
keep
going
there
contributor
site.
I
have
a
very
short
like
how's
it
going
in
your
opinion.
Can
we
be?
How
can
we
be
more
helpful
with
it.
B
Honestly,
I've
I
have
not
been
keeping
a
track
right
too
much
since
actually
launching
it
just
because
I've
been
busy
myself,
the
we
have
the
blog
there.
So
if
we
want
to
have
any
contributor
focus
blogs,
so
things
like
tips
and
tricks
for
contributors
like
that
would
be
a
very
good
resource,
just
to
sort
of
keep
the
content
like
flowing
there.
B
There
is
currently
one
open
pr
to
the
blog,
with
a
story
of
how
our
contractors
that
have
been
working
on
improving
the
developer
guide,
sort
of
how
they
got
involved
with
contributing
the
once
we
sort
of
have
an
idea
of
all
the
services
the
marketing
team
wants
to
offer
one
of
the
ais
or
like
open
issues
I
have
is
like
essentially
putting
together
a
list
of
all
the
services
that
we
sort
of
collectively
offer
not
just
marketing.
But
you
know,
like
here's.
B
How
you
request
a
repo
here
is
how
you
request
a
netify
site.
So
we
could
also
add
into
that.
You
know:
here's
how
you
request
a
tweet
or
here's,
how
you
you
know,
request
comms.
Just
that
way,
it's
all
in
that
one
sort
of
central
location,
our
our
documentation,
you
know,
is
scattered
across
like
a
number
of
repos
and
a
number
of
other
things
that
aren't
like
indexed
well,
and
that
was
one
of
the
reasons
why
we
created
the
contributor
set
was
to
bring
that
all
together
into
one
place.
A
Userland
kubernetes.dev
will
be
kubernetes
contributor
land
which,
yes,
so
we
may
be
pivoting
our
attention,
and
this
might
be
the
most
natural
kind
of
separation
from
the
docs
overlap
that
we
have
so
frequently
because,
like
docs
definitely
owns
the
main
site
and
this
new
site
they
may
be
involved,
but
we
could
be
more
responsible
for
the
content
going
out
of
that.
B
For
that
specific
yeah,
yeah
yeah,
specifically
for
some
of
the
the
stories
that
we
want
to
tell
regarding
sigs,
that
might
still
be
worth
posting
on
the
main
contributor
website,
just
because
that
has
much
broader
reach.
If
the
goal
is
to
get
more
contributors
there
or,
like
you,
know,
new
people
interested
in
it,
that
would
probably
be
a
better
target.
B
F
A
Like
one
of
the
I
I'm
hearing
you
that,
like
we
still
have
a
main
distribution
channel
and
don't
that's
not
going
to
change
like
kubernetes.I
o-
is
the
main
distribution
channel.
So
we
could
talk
about
differentiating
kate's
dev
by
maybe
it's
more
kind
of
playful
content
like
how
to
set
up
your
ide
for
kubernetes
contribution
like
favorite
tool
for
kubernetes
contribution
like
make
it
more
practical.
B
I
watched
a
really
yeah,
like
I
watched
a
really
good
demo,
the
other
day
of
using
you
know,
github
hub
the
cli
tool,
for
you
know
just
quickly
doing
workflow
stuff
without
having
to
go
through
the
ui
and
making
that
work
with
sort
of
the
kubernetes
workflow.
So
even
you
know,
even
things
like
like
that.
That's
I
see
like
would
be
much
better
served
on
the
contributor
site.
You
know
stuff
that,
like
helps
contributors
become
better
at
contributing.
D
Were
you
going
to
say
yeah
so
from
what
I've
seen
in
the
cup
the
the
things
with
the
bot?
I
think
things
like
how
to
get
into
a
slack
user
group
things
like
how
to
get
a
bot
review
right.
The
whole
process,
things
like
only
bob
someone
like
them
knows
everything,
so
I
think
we
should
list
that
out
on
the
creative
tab.
D
A
Yes,
absolutely
so
who's
kind
of
on
point
for
that
site.
Is
there
someone
on
point?
Oh,
it
is
still
you,
okay,.
A
A
B
D
B
C
A
Few
words
were
too
anyway.
That
sounds
like
a
good
place
to
pick
up
next
week.
I
want
to
leave
some
people
some
time
between
hours
per
our
usual
goal,
so
krakagan
congrats
again
on
getting
a
working
demo.
It's
awesome,
I'm
sorry!
Our
internet
is
being
rude
to
you,
but
looking
forward
to
watching
your
video
and
reading
the
box,
we're
just
a
huge
congrats
on
getting
that
merged
and
we
will
figure
out
how
to
find
find
the
right
audience
for
it.
A
So
awesome,
and
I
hope
everyone
has
a
good
rest
of
the
start
of
their
weekend
or
end
of
their
friday,
depending
on
what's
going
on.
Thank
you
all
ph.
Also
like
I
don't
know
if
we
answered
your
question
nearly
enough.
If,
if
if
we
can
continue
in
the
slack
chat
and
kind
of
help,
you
get
the
word
out
more
effectively,
we
don't
have
to
wait
till
next
friday
to
do
so.
We
want
to
be
helpful
now
so.
E
Yeah
I
mean
so
the
call
is
bi-weekly
right,
so
the
callback
happened
next
to
next
week.
We
had
the
one
yesterday,
so
we
still
have
two
weeks
time:
okay,
oh
yeah,
oh
yeah.
Let's
keep
firing.
D
B
We
canceled
yeah,
so
it's
probably
gonna
be
happening
next
week,
but
we're
making
a
huge
change
to
contributor
workflow,
at
least
in
kk,
and
then
we're
adding
like
a
new
label
needs
triage.
So
one
good
example
of
a
blog
post
might
be
an
overview
of
how
to
use
it.
You
know
essentially
effective
issue,
triage
yeah
in
it
and
sort
of,
in
addition
to
our
documentation
and
all
that.
B
A
A
Oh,
I
definitely
sent
a
tweet
out
through
our
tooling,
but
I
I
don't
know
I
yeah.
I
kind
of
dropped
the
ball
and
reporting
back.
C
A
Yeah
yeah
exactly
and
some
cousin.
Would
you
mind
I'll
comment
on
this
and
if
you
could
maybe
schedule
a
few
more
tweets
manually,
that
would
be
good
just
so
we
can
report
back
that.
We
hit
people
up
for
the
last
few
weeks.
A
Good
deal,
I
think
that
kind
of
got
through
that
julia
anything
else
you
wanted
to
cover.