►
Description
[SIG ContribEx] Contributor Comms Weekly Meeting for 20230609
A
Hello
and
welcome
to
the
Friday
June
9th
2023
Sig
contribex
contributor,
comms
meeting
I
am
Chris
short.
Your
co-lead
and
host
with
the
most
for
today's
meeting.
Catalan
is
out
her
family's
in
town
friendly
reminder.
This
is
a
kubernetes
meeting
as
such,
it
is
going
to
adhere
to
the
cncf
code
of
conduct
and
please
don't
say
anything
that
you
would
want
your
mom
to
hear.
That's
just
basically
my
best
advice
I
can
give
y'all
all
right.
It's
a
small
group
of
us
today,
so
we
can
kind
of
plow
through
here.
A
If
you
haven't
made
any
updates
to
the
notes,
go
ahead,
I've
put
some
updates
in
here.
We
can
just
go
ahead
and
get
started.
I
will
mention,
updates
and
big
wins.
Progress.
Has
significant
progress
has
been
made
with
the
zapier
migration
to
the
point
where
it's
like
Nigel
looked
at
it
and
he
was
like
what
do
you
want
me
to
do
exactly
and
I
was
like
just
review
it
and
make
sure
it
looks
right
and
is
acting
right
and
then
flip
them.
That's
the
next
step.
A
B
A
A
Using
my
marketing
brain
right
like
or
no
came
to
us
came
to
a
meeting
told
us
what
he
needed
and
what
yeah,
four
weeks
later,
the
blog
was
published
less
than
four
weeks
later.
I
think
that's
pretty
good
yeah
right
when
you
talk
about
reviews
and
edits-
and
you
know
technical
stuff,
that's
really
good
for
such
a
critical
like
change
and
the
fact
that
we
were
right
come
too
early
enough
so
that
it
wasn't
like
emergency
cops
or
you
know
critical,
comms
kind
of
a
situation
so.
A
Right
yeah,
like
that,
was
that
literally
consumed
a
week
for
me,
yeah
Castle
was
out
Frederico
I
forget
where
you
you
got
involved
at
some
point
yeah,
so
the
yeah,
the
fact
that
this
happened
and
it
worked-
and
it
was
successful
and
like
it
would
just
smoothly-
came
out
I
think
like
that
is
worthy
of
a
potential
kubernetes.dev
article
or
blog
post
of
some
sort
right
like
we
could
get
Arno
and
dims
and
other
people's
opinions.
Well,
whoever
you
know
was
involved
in
the
process.
A
B
A
If
you
haven't
shared
the
article
go
ahead
share
it
give
it
a
little
context
on
social
media
right,
like
a
group
of
folks
came
to
contributor
comms,
you
know
very
important,
contributor
or
maintainers
I
should
say
very
important.
Kubernetes
maintainers
came
to
contributor
columns
with
an
issue
they
wanted
to
communicate
out.
Within
a
matter
of
a
few
weeks,
a
blog
post
was
published.
It
was
thoroughly
reviewed
by
everybody
and
got
exactly
what
needed
to
be
done
to
it
done
to
it.
So
could
we
speed
up
the
process?
You
know.
A
Are
there
Lessons
Learned
here
we
could
do
a
retro
if
we
wanted
I.
Think
but
there's
more
here
is
what
I'm
trying
to
say
if
you,
if
you're,
if
you,
if
somebody
wants
a
kate's.dev
blog
post
like
this,
would
be
pretty
cool
right
because
you
just
you
interviewed
you
interview,
Frederico,
you
interview
the
other
authors
and
then
you
just
talk
about
the
process
right
like.
B
Yeah-
and
it
would
also
help
us
and
as
as
you
mentioned,
we
do,
our
scope
is
constantly
adapting
to
the
things
that
need.
B
I
I
guess
that
this
could
be
something
that
we
should
add
to
our
role
book
as
well,
and.
A
Yeah
and
start
taking
more
ownership
of
right
right
right
right,
yeah
like
we
can
get
your
critical
Communications
out
in
a
scene
and
effective
manner,
yeah.
B
People
here
can
think,
can
sit
on
it
and
see
if
they
want
to
to
do
it,
perhaps
better
than
for
example,
me
me
starting
it
because
then
right.
B
A
C
B
B
Maybe
we
should
have
the
the
boards.
A
Yeah
I
was
gonna,
go
to
the
board
again,
if
you
haven't.
B
C
A
If
you
haven't
seen
it,
here's
a
link
to
the
article,
it's
pretty
awesome:
okay,
I'm
just
gonna,
go
through
these
real
quick
there's,
no
tweet,
PRS
or
anything
I
haven't,
checked
them
yet
so
not
sure.
There's
anything.
We
need
to
be
necessarily
worried
about
next
week.
B
A
B
Don't
see
anything
out
of
the
ordinary
role
and
although
I
I'm
I'm
more
focused
on
trying
to
learn
our
release,
notes
works
right
now
so,
but
but
from
the
discussions
in
the
in
the
channels,
I
don't
think.
There's
any
major
issue
on.
A
Cool
I
would
be
curious
to
learn
how
the
release
note
system
works.
If
you
ever
find
like
the
the
thing
that
teaches
you
that
or
shows
you
that
I've
always
been
fascinated
by
that
process.
A
A
Notes,
if
it's,
you
know
a
relatively
simple
process,
you
know
it's,
it
is
a
release.
Artifact
it'd
be
cool
if
we
got
involved
somehow
in
the
release
process.
True
true.
A
A
Well,
I
just
I
mean
it
was
I
think
it
was
a
year
ago
and
I
had
just
transitioned
jobs
here
in
AWS
and
it
was
like
yeah
I
was
really
like,
not
well
time
to
submit
my
application
for
a
show
Okay,
so
yeah
we've
always
wanted
presence
on
the
release
teams.
So
yeah
I,
don't
know
worth
worth
recruiting
for
I
feel
like
for
sure.
B
B
E
F
A
F
Our
role
as
a
as
a
group
in
the
release
process
is
to
just
promote
the
blogs
and
stuff
that
happens
at
the
end
of
the
release
right
or
are
we.
A
That's
our
role
right
now,
yeah
and
how
we
do
that
it's
the
same
way
we
are,
you
know,
do
all
blog
post
sharing
is
just
through
our
automation,
so
yeah,
like
that's
pretty
much
on
autopilot
right,
like
there's
yep,
that
problem
solved
I.
Think
having
us.
A
The
release
team
adds
skills
to
our
team,
essentially
where
people
will
just
naturally
come
to
us
for
comms
at
some
point
right,
because
so
many
people
go
through
the
release
team.
They
learn
about
us.
They
talk
to
us.
They
realize.
C
A
Cool
all
right,
there's
no
contributor
tweets,
let's
go
to
the
40
board.
Let's
see
which
board
is
the
board
on
there
we
go.
A
F
A
Spotlight
book
reading
club
any
update
there.
Folks,
no.
B
B
C
A
B
Like
it
happens,
excellent
so
yeah
I'll,
definitely
ping
you
with
that
I
I,
absolutely
I
was
also
sort
of
a
co-worker
when
he,
when
he
was
at
IBM
and
I,
was
also
at
IBM
right,
but
just
well
being
a
co-worker
in
different
continents.
Yeah.
B
That
but
yeah,
but
I'll
ping
you
with
when
I
I
I'm
going
to
send
him
something
today,
yeah
go
ahead
just
to
remind.
A
Problem,
you
mentioned
the
the
architecture
spot
line.
B
Yeah
we
so
some
content
is
starting
to
drip
in
and
we
have
two
of
the
six.
B
The
projects
with
answers,
another
one
one
or
two
are
partially
done
so
I
would
say
that
we
are
halfway
there
in
terms
of
content
and
and
well
there
is
one
there
are
two
of
them
that
are
still
with
without
anything
but
I'll
I'll
helping
people
to
to
remind
them.
Some
of
them
are
to
be
expected
because
people
are
told
that
they
were
out
of
office
or
out
of
office
in
general
in
vacations
right.
B
So
yeah
I
think
this
is
progressing
well
enough.
That
by
next
week,
I
I
kind
of
have
a
a
distance
view
on
what
kind
of
content
will
we
will
have
and
and
actually
then
discuss
with
all
of
you-
the
the
approach
for
this,
because
if
we,
if
I,
do
get
six
different,
sub-projects
questions
and
answers
and
if
I
add
an
additional
overview
discussion
with
with
the
leads.
This
is
like
substantial
in
terms
of
yeah.
B
Maybe
yeah,
maybe
a
series,
maybe
like,
with
all
the
answers,
I
I'll,
think
of
a
good
way
to
make
this
as
impactful
as
and
and
interesting
to
read
as
possible.
C
A
Let
me
know
if
you
need
help
with
any
of
that.
Absolutely
thank
you.
Cool,
so
add
all
use
cases
for
zapier
automation,
I
mean
we
have
this
app
here
account
my
update
was
Nigel.
Was
you
know,
looking
it
over
kind
of
thing
and
seeing
if
anything
needed
to
be
tweaked,
I
found
some.
You
know
now
that
we
can
have
multi-step
zaps
I
found
some
cool
ways
to
already
improve
our
existing
zap
years
so
or
zaps.
A
So
yeah
like
the
filters
and
everything
else,
the
multi-step
process
I
feel
like
with
this
account.
We
can
do
something
with
GitHub.
Finally,
I
just
haven't
had
time
to
Tinker.
A
If
somebody
else
wants
to
take
on
the
the
GitHub,
a
Twitter
thing
to
through
zapier
feel
free
to
raise
your
hand
and
help
out
and
I
can
get
you
going
with
Imran
if
need
be,
or
whomever
cool.
E
E
A
G
Yeah,
so
the
six
CLI
first
draft
is
almost
ready.
One
of
my
artists
so
do
I
have
to
make
a
PR
for
the
first
draft
itself
or
do
I
need
to
have
it
reviewed
by
someone.
A
B
You
so
yeah,
so
if,
if
you
have
the
the
content
there,
you
should
share,
share
it
in
the
state
that
it
is
either
on
Google
Docs
or
on
hack
MD
with
me
and
with
the
channel.
So
this
is
like
a
a
joint
effort
just
so
that
anyone
can
just
give
their
own
thoughts.
B
And
after
that
we
can
open
the
pr
and
Etc,
but
the
first
thing
about
the
the
content
itself
and
when,
when
you
think
that
it's
ready
for
for
from
your
point
of
view,
just
share
a
link
in
them
in
in
in
our
channel
in
slack
and
that
creating
a
threat
for
discussion
on
six
Spotlight
CLI
article
link
to
the
Google
Docs
or
fmd,
and
then
we
will
discuss
that
on
that
thread.
B
If
you
take
a
quick
look
into
the
this
is
slightly
different
because
the
CDN
article
was
for
the
website
not
for
kids.dev,
but
this
one
actually
is
for
boats.
So
that's
another!
That's
why
this
this
process
is
important.
You'll
see
that
I
have
like
stage
one.
Please
review
stage,
two
open
the
pr
stage.
Three
that's
published
in
this
specific
case.
B
We
will
have
more
because
this
will
be
published
on
both
kites.dev
and
also
on
the
website.
If
I
remember
correctly,
that's
the
default
approach
for
spotlight
articles
they
get
published
in
both
and
actually
the
understanding
that
we
have
and
that's
documented,
is
that
we
will
first
make
all
the
discussions
first
of
all
internal.
B
That's
why
you
should
share
it
in
the
Channel
with
all
of
us,
so
that
we
can
just
exchange
some
ideas
after
that
and
ideally
in
hack
MD,
if
you
can
just
to
make
it
as
close
as
possible
to
the
to
the
final
PR.
But
if
not
the
the
Google
Docs
is
fine,
then
the
pr
on
it
will
be
open
against
kites.dev
and
that's
where
the
substantial
revision
by
the
docs
team
and
others
will
be
done.
B
And
after
that
opening
the
pr
against
the
main
website
will
be
just
the
formality,
because
the
contact
itself
will
already
have
been
reviewed
first
for
the
kites.dev
website.
So
I
I
think
this
is
the
the
best
approach.
G
True,
so
maybe
by
Sunday
I
will
say
around
Google
doc
link
for
the
first
drop,
which
I
am
working
on
to
review.
Okay,
and
then
we
will
see
what
if
there
are
any
suggestions.
I
can
implement.
A
Awesome
I
haven't
added
my
notes
to
the
docs
yet.
G
Also
I
have
one
doubt
like
I
am
trying
to
edit
the
the
shadow
registry
for
where
the
shadow
rule
is
available
is
written
by
a
GitHub
account
name,
but
do
I
have
to
make
it
make
an
PR
for
that
or
do
I
need
to
like,
because
I
am
not
a
member
of
the
kids.
Also
I
cannot
edit
it.
C
B
Yeah,
that's
so,
let's
from
what
I
I
can
say,
this
opening
the
pr
itself,
it's
one
open.
The
pr
is
one
thing,
but
actually
having
your
name
in
the
commit
message
is
another,
so
even
if
I'm,
the
one
opening
the
pr.
B
Let's
assume
that
that's
the
case,
what
I
will
do
like
I
did,
for
example,
in
the
last
blog
article,
is
that
I
will
add
the
author
there
as
the
as
the
author
in
the
commits,
because
by
using
the
co-authored
by
log
entry,
and
what
will
happen
is
that
that
will
automatically
link
the
commits
to
the
GitHub
accounts
of
the
committer
so
for
any
purpose
related
with
kubernetes
contribution
statistics
Etc
that
will
directly
count.
So
I
think
this
is
important
just
to
be
just
to
that.
B
Everyone
is
aware
that
their
contribution
will
be
officially
registered,
regardless
of
of
anything
else.
For
the
other
part
of
the
question,
which
is
how
do
you
open
a
PR,
for
example,
yourself
without
being
a
member
of
the
of
kubernetes
organization?
I
I
was
not
even
absolutely
sure
if
you
need
to
be
a
member
of
the
organization
to
open
PRS.
B
Maybe
you
are,
but
if,
if
it
is
required,
what
I
just
said,
Works
I
or
anyone
else
can
open
the
pr
adding
you
specifically
as
the
author
and
you
will
be
you'll,
be
credited
for
the
contribution
which
will
then
be.
You
can
use
that
for
gaining
kubernetes
Arc
membership
if,
if
it
has
I
think
it
has
a
some
requirements
in
terms
of
amount
of
commits
or
something
like
that,
that's
my
take
on
it.
I
don't
know
Chris
what
you.
A
I
think
that's
the
probably
the
right
path
to
go.
The
commit
message
is
what
or
the
committer
or
committee
I
guess.
A
C
A
G
No,
but
only
in
this
that
I
am
trying
to
figure
out
how
to
get
that
done
because
Kathleen
last
time
told
me
to
add
my
name
on
the
social
media
Shadow,
so
that
folks
know
that
that
role
is
not
available
for
them
now,
but
maybe
I
cannot
open
the
pr
for
API.
So
maybe
I
will
ask
on
select
how
to
do
that.
A
Yeah
that'd
be
a
good
idea.
I
think
that'd
be
a
fun
issue
to
type
are.
F
G
Yeah
they
are
usually,
there
is
a
edit
button
to
edit
a
readme
file
if
I'm
not
wrong.
That
is
not
there.
A
F
G
A
C
A
Right
yeah.
E
A
F
A
E
C
A
A
C
G
No
after
I
am
seeing
one
edit
button
can
I
present
my
screen
now
that.
A
Is
okay
feel
free
hang
on?
Let
me
make
sure
you
can
do
that.
C
A
You
hit
commit
it's
in
the
table,
so
it
should
be
like
line
20,
something.
E
A
A
Question
I
mean
you
can
try
it.
It
shouldn't
hurt
since
like
this
is
your
only
Branch
so.
A
G
A
So
if
you
share
that
you
can
drop
it
in
chat
or
whatever
I
should
be
able
to
go,
see.
E
A
Click
that
it's
the,
what
do
they
call
it
contributor
license
agreement.
You
have
to
sign
this
before
you
can
commit
to
anything
in
the
Linux
Foundation.
So
it's
going
to
ask
you
some
simple
questions.
I
think.
C
A
That's
fine
right,
like
only
those
with
right
access
to
this
repository,
convergible
request,
which
I
have
so
you
still
have
to
do
this
CLA
somehow.
G
We
have
so
is
there
any
way
I
can
sign
the
contributed
guideline
or
yeah.
A
G
Out
so.
A
You
need
to
do
the
CLA
again,
so
if
you
go
to
the
guide,
it'll
take
you
to
assign
the
clh
section
which
actually
lands
you
here
in
this
next
link,
and
it
shows
you
how
to
do
the
process
of
making
that
happen.
If
you
get
another
500
error,
you
definitely
need
to
say
something
in
the
contribex
channel
right,
because
that
being
broke
is
like
a
really
bad
problem
and
we
need
to
fix
it.
A
A
G
G
Is
there
any
other
way
I
can
help
like
I
I
am
trying
to
find
issues
in
the
gates
organizations
so
that
I
can
gain
the
membership
on
my
own,
but
like
apart
from
documentation
like
I,
have
a
basic
knowledge.
Okay,
it's
deployments
and
Docker.
So
can
I
do
like
if
you
know
any
other
six
or
anything
that
so
they
need
these
kinds
of
contributors.
So
I
will
be
more
than
happy
to
help.
A
So
yeah
there's
there's
a
lot
of
cigs
out
there
and
like
Sig,
Kate's
infra,
like
there's,
usually
some
barrier
to
entries
the
highly
technical
ones
right
like
Sig
node.
You
kind
of
need
to
already
know
kubernetes
in
and
out
to
be
able
to
work
in
that
one,
but
there
are
other
ones
where
you
can
kind
of
just
jump
in
and
help
Kate's
infer
is
one
of
them:
I've
gone
and
done
random
PR's
for
them
before
I've
added
redirects
to
you
know
our
random
web
server
that
we
have
out
there
on
a
Case
cluster.
A
That's
doing
all
the
redirects
for
us
stuff
like
that,
is
super
easy
to
do,
there's
harder
stuff
and
the
stick
K104
that
you
can
work
your
way
up
to,
though
for
sure,
and
they
would
really
appreciate
the
help.
I
know
that,
like
other
cigs
there's
also
in
the
kubernetes.dev
site,
the
getting
started
guide,
I
think
there's
something
about
sigs.
A
C
A
All
the
sigs
but
yeah
Sig
docs
needs
a
lot
of
help.
They
have
a
lot
of
process
to
get
the
docs
out
the
door
in
a
quality
manner,
so
they've
got
a
lot
of
their
own
tooling
and
systems
in
place.
A
Helping
them
with
that,
like
architecture
is
hard.
If
you
worked
for
a
cloud
provider,
you
could
do
that
cluster
life
cycle,
you
have
to
know
kubernetes
docs,
you
don't
contributor
experience,
you
don't
instrumentation,
you
do
Kate's
infra!
You
can
get
into
that
pretty
easily
multi-cluster.
You
need
Kate's
knowledge
same
with
network
same
with
node
release
is
like
a
whole
thing:
it's
its
own
Sig
and
then
there's
a
release
team
for
every
release.
Those
are
two
different
things.
Just
keep
that
in
mind.
A
Six
scalability,
you
gotta,
understand
like
the
auto
scalers
vertical
horizontal
kind
of
thing.
Before
you
dive
in
six
scheduling,
you
gotta
understand
how
that
kubernetes
scheduler
works
really
well
same
with
security.
You
got
to
understand
like
attack
surface
within
kubernetes,
more
or
so
than
you
know
the
internals
of
kubernetes,
but,
like
you,
got
to
do
security,
reviews
and
stuff
like
that
too.
So
you
kind
of
have
to
know
both.
A
If
you
know
a
lot
about
storage,
you
can
probably
get
into
storage,
pretty
quickly,
testing
pretty
high
bar
to
clear
UI
I
feel
like
I.
Don't
know
like
you
could
maybe
get
into
that,
but
they
really
need
I.
Don't
want
to
say
it
on
I,
don't
want
to
say
anything
negative
on
video,
but,
like
UI
has
had
its
ups
and
downs
over
the
years.
I'll
just
say
that
where
they've
been
more
active
and
less
active,
so
they
could
be
less
active
right
now.
Your
mileage
may
vary.
A
Usability
is
always
a
good
thing,
but
you
got
to
have
like
accessibility
experience
and
all
that
kind
of
stuff.
It's
more
so
ux
and
design,
and
just
proper
practices
around
that
and
then
obviously
Sig
Windows.
You
would
have
to
know
windows
and
how
kubernetes
works
with
Windows.
There's
a
bunch
of
working
groups
too.
There's
you
know
you
can
do
all
kinds
of
things.
Just
if
you
know
there's
committees
higher
level
right
like
steering
security,
Response
Code
of
Conduct.
A
Those
are
all
things
you
can
work
your
way
up
to
you
know.
All
of
these
sigs
have
leads
and
shadows
and
everything
else
just
like
we
do
so
yeah
like
if
you're
into
batch
processing,
the
batch
working
group
is
pretty
dope.
A
There's
a
policy
working
group
that
has
members
from
a
lot
of
different
sigs,
so
you
know
you
should
look
at
it
like.
What
are
you
trying
to
gain?
You
know.
Are
you
trying
to
become
a
contributor?
Are
you
trying
to
become
a
maintainer?
What
is
you
know?
What
is
your
your
goal
in
the
community
once
you
figure
that
out?
That
makes
a
little
bit
easier
to
kind
of
narrow
down
like
which
direction
you
should
go
in
so
yeah
like
just
being
a
contributor.
That's
a
fine
goal
right,
that's!
A
Basically
what
I
am
and
now
I'm
a
co-lead
of
a
sub-project.
So
yeah,
do
you
just
work
your
way
up
the
ladder?
It's
it's
pretty
cool
right,
like
it's
very,
very
much
a
if
you've
done
the
work
you
get,
the
you
know,
leadership,
roles,
kind
of
thing,
so
yeah,
that's
my
little
Sig
Tour
on,
like
a
micro
level,.
A
All
right,
I
got
a
few
minutes
left
here.
Let's
go
back
to
whichever
board
I
was
on
there's
a
window
in
here
somewhere
I
swear
some
like.
Oh
it's
here,
the
the
yeah.
C
A
A
Working
on
that
to
show
you
here,
no
okay
whoa
do
that
Spotlight
signature,
X!
That's
and
chasmin's.
Court
update
storytelling
resources
to
belonging
resources;
fredericos
on
that
investigate,
Twitter
spaces,
I
haven't
done
any
investing,
I
mean
I,
know
all
I
know
about
Twitter
spaces.
Right
like
that
is
2B
to
be
determined,
I'll,
say:
Sig,
release.
A
C
A
E
Yeah
so
hello,
hello,
Chris
I,
think
we
talked
about
the
the
use
case.
Issue
of
these
appear,
so
is
it
free
to
take
this
up,
as
you
talked
about
mentioned
before,
for.
A
Mean
if,
if
you
want
to
grab
like
the
way
it's
been
done,
the
way
we've
usually
tested
stuff
with
zapier
in
the
past,
like
you
test
it
under
your
account,
see
if
you
can
get
it
working
or
like
a
dummy
account
and
get
in
some
cases.
If
you
want,
if
you
can
make
it
work
there,
then
it's
really
easy
to
pour
it
over
right,
like
we
just
copy
the
instructions.
E
Yeah,
so
yeah
I
went
to
work
on
that
also,
so,
if
you
can
help
me
out
or
like
otherwise,
I
think
is
what
he
works
with
his
lab
here.
So
we
can
also
yeah.
A
So
the
I
think
the
biggest
thing
is
just
like:
creating
a
test
environment
for
yourself
to
see
if
you
can
basically
we're
going
to
get
GitHub
issues
and
they're
try
to
turn
them
into
tweets
right.
So
like
we
need
an
issue
template
at
some
point.
We
need
whatever
zapier
needs
to
figure
out
what
the
content
is
versus.
What
the
metadata
is
like.
A
We
need
a
way
to
do
that
or
it
could
just
be
like
your
issue
must
be
exactly
your
Tweet
and
we
have
you
know
like
if
it
doesn't
go
out
that
invalidation
error
comes
back
to
the
contributor
at
account,
so
we
could
figure
that
out.
You
know
kind
of
thing
if
it
didn't
go
out
so
yeah.
The
automation
of
that
is
going
to
be
interesting.
Right,
like
it's
going
to
be
a
several
step
thing.
It's
going
to
be
like
okay,
GitHub
issue,
the.
E
A
Of
the
actual
issue
block
itself,
parse
that
into
a
tweet
length,
has
to
be
checked.
You
know,
like
you,
gotta
have
some
other
things
happening
there
and
then
go
to
buffer,
and
then
there
has
to
be
two
of
them,
because
you
need
one
for
each
account
and
buffer
Twitter
and
Mastodon,
but
figure
out
how
to
do
it.
First
is
the
hardest
part.
A
In
there
he
got
close
or
did
get
it
I
want
to
say
so
he
might
have
wrote
written
that
down
somewhere.
F
Yeah
I
think
he
was
able
to
figure
out
half
of
the
portion.
The
only
thing
which
is
the
integration
of
zapier
and
GitHub
thing:
okay,.
F
Done,
however,
the
the
talks
were
that
we
need
to
figure.
You
know
to
get
those
parameters
on
which
our
content
on
the
GitHub
issues
were
supposed
to
judged.
If
there's,
if,
if
we
want
to
send
it
to
buffer
or
not,
and
also
there
was
this
question
going
around-
that
you
might
there's
no
notification,
I
mean
we
want
a
loopback
thing.
A
Yeah
we
want
something
and
issue
itself
right
like
we.
We
have
to
be
able
to
use
the
issue
as
like
an
approval
process
too
right.
So
that's
the
other
interesting
part
and
then
like
the
feedback.
Oh
yes,
this
did
go
out.
Kind
of
thing
is
important,
but
those
are
very,
very
sticky
issues
and
I
could,
as
I
mean
we
have
support
I
feel
pretty
sure
through
from.
A
E
Can
always
ask
yeah
so
like
I
want
to
work
on
that
so
like
what?
How
can
I
get
the
whole
workflow
that
has
already
been
set
up
or
like
we
can
have
a
progress
to
how.
A
A
To
the
contributor
comms
section
in
the
community
repo
and
look
for
stuff
about
zapier
and
the
issues
and
I
feel
like
you'll
have,
if
you
go
through
the
closed
and
open
issues,
I
feel
like
you'll,
see
everything
that
we've
been
able
to
do
probably
multiple
times
a
Hoover.
If
you
want
that'd,
be
the
first
place,
I'd
start
and
then
I'd
just
start
working
with
a
dummy
account
on
a
dummy
repo
somewhere
to
just
kind.
F
F
A
E
A
Yeah
arpit
always
do
it
individual
unless
you
are
like
a
donating
or
contributing
on
behalf
of
your
employer
or
are
operating
clusters
for
consumers.
Basically
I
think
is
the
other
caveat.
A
No
problem
I'm
happy
to
help
out
anybody
with
us
at
any
point
in
time,
I
will
probably
take
a
snippet
of
this
video
and
turn
it
into
a
blog
post
somewhere.
A
I
feel
like
I
can
just
be
like
Chris
short
explains
X.
You
know
if
that's
like
something
I'll
I'll,
let
somebody
look
at
it
and
be
like
yo.
That's
a
good
idea
and
we'll
figure
out
where
to
publish
that
if
it
lands
on
my
own
blog,
fine,
no
big
deal
all
right.
It's
one
minute
till
the
end
of
our
show
or
not
show
meeting.
D
I
got
one
thing
for
last
minute:
yeah
as
far
as
I
remember,
I,
think
the
sage
Network
Spotlight
was
only
published
in
the
website,
not
in
the
kids,
dot
IO.
A
So
should
it
have
been
gone
to
the
case
that
I
know
I
think
the
spotlights
are
Dev
only
but
like
the
big
issues
like
registry
and
CDN
are
both
I
forget
how
that
works,
ping
Federico
on
slack,
he
would
know
it's
still
well
six
o'clock,
kids
time
so
yeah
yeah
just
ask
him
like.
Are
they
supposed
to
go
to
both
places?
Kristen,
no,
okay,
cool
everybody
have
a
great
weekend.
Thank
you
all
for
being
here
and
I'll.
Stop
recording.