►
From YouTube: [SIG ContribEx] BiWeekly Meeting 20210317
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
Okay,
we
are
now
recording
hello
everyone
and
welcome
to
the
march
17th,
well
bi-weekly
in-person
meeting
for
sick
computer
experience.
I'm
your
host
today,
bob
gillen
one
of
the
co-chairs
as
a
fyi.
I
think
everyone
is
quite
familiar
with
this,
but
we
abide
by
the
cncf
code
of
conduct,
which
essentially
boils
down
to
please
be
excellent
to
each
other.
These
meetings
are
recorded
and
get
posted
to
youtube
generally
within
24
hours.
So
you
know,
please
be
excellent
to
each
other.
A
With
that,
let's
see
up.
Okay,
laura
you
already
volunteered
for
notetaker
cool.
Is
there
any
do
you
want
to
do
a
few
intros?
Well
sure
I
kicked
off
allison.
Why
don't
you
go
next.
B
C
Going
to
toss
to
laura
hello,
hello,
I'm
laura
santa
maria-
and
I
haven't
been
here
in
probably
nearly
a
year
now
because
work
exploded
when
everything
went
sideways.
So
I'm
back
hi
and
if
you
need
me,
I
am
currently
trying
to
help
reboot
the
community
meeting.
But
that's
what
I
do
here.
D
Hi
all
chris
short
here,
cncf
ambassador
and
sig
controvex
member
for
a
long
time.
I
work
at
red
hat
and
here
to
help,
as
always,
mostly
always-
and
I
will
toss
it
over
to
the
wonderful
josh
burkas.
E
Yeah-
and
I
don't
know
why
the
so
I'm
josh
burkus
I've
been
in
this
sig
for
quite
a
while
work
on
various
things.
Although
I've
been
kind
of
overwhelmed
with
the
day
job
lately,
mostly
participating
in
the
mentoring
group,
but.
F
G
Hi,
my
name
is
alex.
I
don't
know
first
time
here
I
was
tempted
to
find
a
side
project
and
rather
than
resurrecting
my
self-important
blog,
I
asked
bob
how
I
could
help
and
bob
said
help.
So
here
I
am
trying
to
figure
out
what
it
is
that
I
can
do
to
contribute.
H
That
kicks
it
over
to
eddie!
Now,
oh
sorry,
all
right,
I'm
eddie,
zaneski
alex
I'm
sure
your
blog
is
filled
with
writing
about
how
you
deploy
your
blog
as
every
blog
is
destined
to
be
I'm
the
co-chair
of
six
cli
and
the
stars
have
aligned
because
I'm
usually
not
able
to
join
this
meeting,
because
you
move
the
meeting
time
to
overlap
at
6
00
so
glad
to
be
here.
H
No
I'm
matt,
I
like
peanut
butter,
which
is
not
opportune
when
introducing
yourself,
the
the
lead
of
the
subgroup
upstream
marketing
community
been
contributing
to
kubernetes
community
for
the
last
year,
helping
bootstrap
that
and
work
with
the
awesome
crew
there
to
get
great
stories
out
there,
and
we
have
a
mission
of
helping
non-code
contributors,
get
started
in
interesting
ways
and
and
see
that
they're
valued
in
our
in
our
community.
H
A
Okay,
that
should
be
everyone
with
that
we
can.
We
can
kick
things
right
off.
I
know
office
hours
happen
today.
I
don't
have
any
details
on
it.
Did
anyone
happen
to.
D
Watch
I
watched
like
the
first,
I
think
30
40
minutes
of
it.
I
thought
it
was
great
right
like
it
was
engaging.
People
were
asking
questions,
we
were
giving
answers,
it
was
awesome.
I
know
for
the
first
time
we
actually
had
too
many
volunteers.
C
And
that's
me
and
I
can
add,
notes
afterwards,
so
I
have
an
email
drafted
and
a
google
sheet.
I
dropped
it
last
week
in
the
threads
for
the
async
meeting
on
slack,
but
I
will
drop
it
also
into
sid
contrabax.
C
Obviously
I
don't
think
it's
happening
today,
because
you
know
we
don't
have
any
topics
to
talk
about,
but
the
basic
idea
is
we're
going
to
try
to
move
it
towards
more
of
a
discussion
based
meeting
about
like
let's
pick
a
topic,
that's
important
to
the
community
right
now
and
we'll
talk
through
it.
I
do
have
some
outstanding
questions
that
I
think
need
to
kind
of
get
addressed
mainly.
Do
we
pretty
much
open
up
the
zoom
to
everybody
and
if
so,
how
many
moderators?
C
Can
we
get
to
make
sure
that
the
code
of
conduct
is
taken
care
of
and
all
that
fun
stuff
and
ensuring
that
we
stay
on
topic?
Stuff
like
that?
So
I
don't
really
know
what
else
we
want
to
do
with
that.
I
know
we
did
want
to
try
to
get
announcements
in
the
kep
keps
cups
in
there
caps
keps.
C
So
I
know
that
those
are
two
things
we
want
to
keep
from
the
prior
format,
but
that's
kind
of
where
I
am
it'd
be
great.
If
people
can
proofread
the
email
which
I
will
drop
in
the
contrabax
channel
after
this,
so
that's
where
we
are.
A
Just
a
quick
note
on
the
moderation
and
zoom
meeting
and
all
that
we
we
can
repurpose
our
old
docs
about
it.
We
usually
have
just
a
host
and
co-host
and
that's
enough
to
actually
handle
the
the
moderation
tasks.
Okay,.
C
A
We've
been
pretty
good
with
it
being
like.
You
know,
with
people
coming
in
on
auto
mute,
and
then
you
know
it's
rare
that
we
actually
have
to
boot.
Someone.
A
Meet
our
contributors
hasn't
really
happened,
something
we
can
talk
about
like
at
the
the
end
of
sort
of
our
little
stand-up
type
thing
here
is
sort
of
going
through
that
sheet
a
little
bit
more
and
see
if
people
want
to
take
that
up
again,
but
again,
we
can.
We
can
save
that
one
for
a
little
bit
later.
A
E
Okay,
there's
been
a
call
for
mentors
and
projects.
I
don't
know
how
many
we
actually
got.
B
A
That
that's
that's
always
been
the
big
pain
point
like
lots
of
people
are
interested
in
getting
mentored,
but
we
have
few
mentees
we're
not
not
mentees
mentors
with
well-scoped
projects.
One
of
the
things
that's
come
up
multiple
times
now
is
just
like.
We
have
a
lot
of
little
things,
but
we
kind
of
need.
Like
an
actual,
you
know,
two-month-long
project
to
hand
off
to
someone.
G
A
It's
usually
like
we
tend
to
serve
as
the
shepherds
for
the
programs
and
we
try
and
come
up
with
some
ideas,
but
for
the
most
part,
we're
reaching
out
to
other
groups
to
see
you
know
like
hey.
This
is
coming
up.
This
is
a
great
opportunity.
Do
you
have
anything
in
mind?
Do
you
have
the
bandwidth
to
do?
This?
Bandwidth,
of
course,
has
been
a
very
big
problem
this
past
year.
You
know
it's
sort
of.
It
is
what
it
is
there.
B
It
is
next
week
on
tuesday,
I
believe,
hang
on.
Let
me
check.
Was
it
monday,
hang
on
it's
next
week
on
monday
at
3
pm,
gmt.
A
11
a.m:
pt,
so
8
a.m
or
sorry
11
a.m.
Et
8
am
pt
there
we
go.
A
8
am
mondays,
whoops,
actually
close
the
agenda,
one.
A
Sec:
okay,
any
questions
regarding
that
or
well.
We
can
dive
into
the
new
contributor
workshop.
A
Too
yeah
that
will
be
one
of
the
big
focuses
for
the
upcoming
mentoring
meetings.
The
new
computer
workshop
has
had
like
a
lot
of
stuff
sort
of
specked
out
in
the
scope
of
works
defined,
but
there's
been
an
sort
of
just
a
lack
of
people
being
able
to
record
and
produce
the
content
for
the
workshops
or
for
the
workshop.
Sorry.
C
A
Honestly,
like
both
it's
assembling,
the
like,
we
have
the
the
sort
of
stuff
scoped
out
for
the
slides,
actually
allison.
You
probably
know
this
a
little
bit
more
than
I
did.
You
want
to
update
this.
B
B
We
need
to
kind
of
go
back
and
re-evaluate
what
stuff
really
needs
to
be
like
a
video
and
recorded
talk
because
recording
talks
and
like
doing
this
kind
of
recorded
content.
It
is
a
high
overhead
in
terms
of
like
you
need
to
shell
out
time
and
do
multiple
takes
and
all
that,
whereas
some
of
the
smaller
bite-sized
areas
like
we
could
aim
for
doing
maybe
like
a
written
guide
like
a
written
kind
of
tutorial
learning
stuff
on
those
kind
of
smaller
parts
and
then
in
future
aim
for
those
to
be
in
videos.
B
So
that's
just
kind
of
like
a
bunch
of
thoughts
there
from.
I
hope
that
it
addresses
the
question
yeah.
E
It
wasn't
good
enough
and
then
I've
never
gotten
back
to
it
because,
like
I
just
spent
the
last
solid
week,
recording
stuff
for
red
hat,
and
if
you
look
at
who
volunteered
for
sessions
a
lot
of
it's
the
same,
the
the
one
exception
would
be.
The
new
zealand
team
has
taken
on
build
and
test
and
their
delays
they've
been
building
up
a
whole
infrastructure
to
actually
make
it
a
follow-able
thing.
So
they're
they're,
taking
on
the
really
hard
work
around
that.
But
that's
proved
to
take
a
lot
more
time
than
they.
D
B
A
Okay,
any
other
questions
comments
regarding
mentoring,
otherwise,
you
might
punt
that
entire
discussion
to
the
upcoming
mentoring
meeting.
A
Okay,
next
is
community
management
on
the
chair
need
to
know
email.
I
don't
know
of
any
other
immediate
things
that
should
does
anyone
have
anything
that,
like
the
lead
should
know
well
outside
of
I
should
say
outside
of
the
the
contributor
survey
and
the
annual
reports?
Is
there
any
items
that
people
can?
Think
of
that
should
happen
to
go
to
all
the
all
the
leads.
A
Okay,
I
don't
think
there's
also
been
any
apac
updates.
I
know
nikita
has
mentioned
that
that
has
kind
of
like,
along
with
the
apac
meeting,
has
kind
of
stopped
happening
just
because
people
have
lost
band
for
and
they're
trying
to
be
more
async
about
it.
A
Items:
okay,
that
will
take
us
to
dev
stats.
I
actually
have
a
update
here.
I
am
going
to
grab
a
link,
but
very
soon
devstats
will
be
able
to
have.
Oh
for
those
of
you
that
aren't
familiar.
Dev
stats
is
a
site
where
you
can
look
at
a
bunch
of
metrics
about
the
project
and
it
has
like
a
bunch
of
dashboards
and
other
useful
things.
A
But
the
problem
is
most
of
those
dashboards
aren't
useful
for
for
us
and
often
require
a
lot
of
like
teasing
stuff
out,
but
they're
going
to
be
implementing
changes
soon,
so
that
we
will
be
able
to
get
everything
down
on
a
per
repo
per
sig
and
for
those
of
us
that
happen
to
work
for
a
company
that
cares
about
the
number
of
contributions,
a
per
company
breakdown
that
is
being
tracked
in
that
issue
right
there,
but
yeah
it
should
hopefully
land
within
the
next
week
or
two,
the
oh,
the
one
other
come
on
the
dev
stats
and
dashboards
in
general.
A
The
other
thing
that
we
plan
to
do
and
this
sort
of
ties
into
the
kubernetes
contributor
site
a
little
bit,
but
we
want
to
actually
add
a
section
on
the
contributor
site
where
we
can
add
dashboards,
sort
of
with
our
like
annotations,
on
what
people
should
look
at
and
how
how
to
interpret
the
data
and
how
to
make
it
useful.
A
Essentially,
it's
it's
embedding
a
chunk
of
devstats
in
an
iframe
if
you're
familiar
with
that
sort
of
thing,
but
once
the
the
changes
land
in
dev
stats,
we
want
to
do
that
sort
of
thing.
There.
A
Stats:
okay,
marketing.
H
Hey
gang,
we
have
been
up
to
good
things
over
in
the
upstream
marketing
team.
H
I
just
wanted
to
give
a
quick
update
that
our
we've
kind
of
positioned
the
goal
of
the
group
is
to
have
like
a
no
code
way
of
contributing
to
kubernetes
and
really
encouraging
that,
and
just
want
to
report
back
that
that's
working
well,
we've
had
two
people
consistently
showing
up
and
now
being
active
contributors
now
that
they
know
that
they
don't
have
to
know
git,
they
don't
have
to
know
they
don't
have
to
open
github
issues,
we're
just
hanging
out
in
google
docs
and
I'm
managing
some
backlog
for
us
to
keep
track
of
stuff
and
a
couple
others
are
coming
in
and
out
based
on
availability.
H
H
People
can
have
consistently
when
it
comes
to
what
we're
working
on
the
contributor
survey
is,
first
and
foremost,
so
I
wanted
to
we've
sent
out
google
group
message
and
a
number
of
tweets
rajulo
is
on
point
there,
but
I
just
want
to
ask
it:
where
are
we
at
in
that
bob
or
others
that
have
access
to
the
survey
how's?
How
are
the
results.
A
I
have
not
looked
lately.
Josh
did
do
you.
I
know
I
asked
you
last
week
to
take
a
peek.
Do
you
have
an
idea
on
what
our
numbers
are
now.
E
H
Fair
yeah
we
can-
and
we
can
pick
that
up
and
try
to
do
a
little
bit
of
a
a
campaign
from
people
that
have
decent
followings.
Try
to
stretch
that
a
bit
further.
E
Yeah
I
mean
obviously
the
issue
is
that
we
only
actually
want
contributors
to
respond.
The
I
don't
know
if
in
yeah.
D
E
Potentially,
you
know
attracting
a
bunch
of
people
to
fill
out
the
survey
who
are
not
but
don't
clearly
indicate
that
they're
not.
H
E
I
I
think
most
people
are
just
not
filling
it
out,
because
you
know
this
is
our
third
one.
It
doesn't
really
have
anything
except
you
know,
sort
of
standard.
You
know
questions
on
it
that
people
have
seen
before,
and
so
I
think,
there's
no.
H
A
E
Think
sorry
josh,
I
was
gonna
say
I
don't
believe.
Surveymonkey
tells
me
this
I
it
would
be.
It
would
be
interesting
if
it
did
to
find
out
how
many
people
actually
started
the
survey
and
did
not
complete
it.
Yeah.
C
So
I
guess
my
question
would
be
like
could
maybe
we
just
explain
the
value
of
the
survey?
I
don't
know
if
we
have
already
but
like
if,
if
we
just
kind
of
put
up
an
informal
message
in
like
some
of
the
slack
channels,
just
saying
hey,
I
know
you've
seen
this
before,
but
here
or
here's
where
we
use
it
or
something
like
that.
A
The
other
thing,
I
think,
will
help
is,
like
you
know,
rajul,
and
I
were
talking
just
before
the
meeting
the
messages
to
all
the
slack
channels
about
the
survey
and
then
the
other
thing
was
essentially
messaging.
The
individual
mailing
lists.
A
We
wanted
to
try
and
get
most
the
leads
to
sort
of
push
that,
and
I
know
a
couple
sigs
are
bringing
it
up
in
their
sig
meetings
directly
p.s.
If
you
haven't
taken
the
survey,
please
take
the
survey,
but
that's
where
we
like.
I
think
we
will
get
more
actual
sort
of
follow-up.
A
That
was
the
the
individual
messaging
like
the
lists
and
the
things
that
slack
were
that
got
us
the
most
responses.
Last
year.
H
F
H
A
H
A
Make
that
happen
worst
case.
You
know
if
we
want
to
try
more
of
a
you
know,
blitz.
If
like
say
the
21st
rolls
around,
and
we
still
only
have
like
a
small
number
of
survey
respondents.
Then
we
extend
it
for
a
week
and
do
much
more
of
a
comms
blitz.
I
personally
would
like
us
to
get
at
least
130
respondents,
because
that's
10,
that's
roughly
10
of
our
work.
Members.
A
Ideally
more
but
again
10
if
it's
mostly
people
that
are
active
within
the
project,
I
would
consider
that
good.
H
Cool
very,
very
cool,
all
right
yeah,
and
we
want
to
I'm
going
to
continue
down
a
series
of
tweets
that
encapsulate
what
we
just
mentioned
from
the
kate's
contributors
twitter
handle
but
light
following,
but
very
retweeted,
by
important
people
in
our
community.
So
that's
awesome
but
like
giving
that
target
of
hey
we're
at
55
we're.
H
H
We
just
switched
back
over
to
a
project
on
github
and
using
just
like
the
little
lightweight
cards
that
you
can
put
into
there
to
track
it
as
opposed
to
github
issues
for
articles
that
way,
people
don't
have
to
manage
the
issue
and
it's
not
kind
of
attached
to
the
delivery
of
a
of
a
milestone,
because
it's
it's
a
slightly
different
flow
here.
So
we're
back
to
experimenting
with
that.
The
tldr
we've
got
a
very
cool
article
on
michelle.
H
That's
going
to
get
p
pr'd
in
this
week,
I'm
working
with
bart
who
wrote
it
he's
not
as
familiar
with
git.
So
we're
going
to
pair
on
that
and
get
it
in
and
then
we've
got
a
series
that
will
be
the
first
on
the
dev
domain.
Our
target
is
to
get
those
in
by
kubecon
eu
and
it's
about
your
contributor
contribution.
Wow,
that's
incredibly
redundant
it'll
be
more
interesting
than
that
sentence
about
the
first
one
out.
There
is
chris
short
on
how
he
contributes
as
a
non-code
contributor.
H
I
wrote
one
on
like
how
I
focus
my
contribution
to
four
hours
a
week.
That's
doing
well
on
another
publication
and
we'll
republish
so
just
more
of
those
stories,
and
if
you
are
interested
in
sharing
just
a,
we
can
go
from
a
couple
paragraphs
into
a
good
article
with
our
help.
So
please
reach
out.
If
you
have
an
idea
or
just
just
dm
me,
some
thoughts
and
we
can
take
it
from
there.
H
Last
but
not
least,
we
have
these
umbrella
issues
that
are
kind
of
more
programs
that
we
want
to
have
going
forward
like
the
con,
like
the
sig
highlights
type
articles,
so
we're
shifting
from
our
intention
is
to
archive
those
close
those
issues
in
favor
of
systems
that
you
know
if
you
show
up
to
in
upstream
marketing,
you're
like
I
want
to
write
something
we
send
you
to
a
google
doc
that
has
one
of
the
sigs
that
you
could
talk
to,
and
maybe
some
quotes
that
people
have
put
in
already
so
trying
to
build
more
systems
as
opposed
to
long
living
issues
that
will
probably
never
close.
H
Yeah
100
with
you
like
yeah,
our
yeah,
anything
that
gets
to
the
point
where
we're
like
hey.
This
is
a
thing
that
we
do.
It
should
absolutely
be
in
our
github
repo
and.
C
H
Intend
to
maintain
that,
like
as
maintainers
of
the
of
the
subgroup
or
my
goal
is
to
just
not
ask
new
contributors
to
go
pr
that
in
like
it's,
it's
a
heavier
lift
than,
and
it's
every
time
we
ask
somebody
to
do
that
they
don't
show
up
again.
So
I'm
just
you
know,
correlation
is
helpful
there,
but
I
hear
you
bob
yeah.
We
don't
want
to
leave
stuff
just
hanging
out
in
google
docs
and
on
personal
accounts,
we'll
we'll
document
it
better
than
that.
A
A
Okay,
that
kicks
us
over
to
contributor
docs.
I
don't
have
any
updates
regarding
the
guide.
The
developer
guide
audit
is
still
progressing
if
you
happen
to
be
involved
in
any
other
sigs.
A
And
then
I
gave
sort
of
the
contributor
site
update
earlier,
with
it
being
moved
over
to
the
kubernetes
kubernetes
org.
The
I
think
I
might
have
mentioned
this
before
being
recorded,
but
there
is
also
interest
in
localizing
that
content
and
that
will
probably
start
up
soon-ish.
A
Okay,
github
management.
I
think
the
only
big
thing
here
is
that
we
are
really
in
progress
with
the
renaming
the
repos
you
might
have
seen
some
comms
flying
by
regarding
kate's
dot,
dev,
slash,
rename
we're
still
sort
of
teasing
out
some
of
the
details
of
this
process,
because
there's
a
lot
of
like
little
conditionals
that
could
could
cause
more
problems
for
your
workflow
when,
when
migrating
your
default
branch
name
from
master
domain,
but
that
will
be
our
sort
of
canonical
source
source
of
true
truth
for
that
documentation.
A
Okay,
no
real
update
on
slack
infra.
A
Excuse
me
eddie.
You
have
something.
H
So
in
the
past,
since
code
freeze,
I've
had
a
bunch
of
new
contributors
pinging
on
pr's
that
have
been
approved,
postcodes
freeze
and
just
asking
like
hey
like
what
does
it
take
to
get
this
merged?
In
you
know,
obviously
it
will
merge
after
code
freeze
is
thawed,
but
have
we
ever
talked
about
adding
like
just
the
part
of
the
notification?
If
it's
approved
post
code
freeze,
we
can
have
a
note
in
there
that,
like
hey,
this
is
code.
Freezer.
A
Honestly,
people
don't
look
at
those
notifications,
we
have
enough
problems.
People
are
reading
our
messages
from
our
bots
as
it
is
the
other
thing.
A
Some
things
can
be
merged
in
those
are
our
bug
fixes
or
things
that
you
don't
need
to
be
cherry
picked.
A
H
You
know
I
would
kind
of
respectfully
separate
those
two.
I
think
eddie's
point
of
like
having
a
knowing
a
message
is
going
out
to
something
during
code
freeze,
even
if
it
is
amongst
other
messages
like
it'd,
be
nice
to
get
that
in
as
a
feature
and
then
like
there's
a
much
larger
effort
of
you
know
auditing
what
goes
out,
but
I
wouldn't
want
to
block
eddie's
request
on
that
personally,
just
slightly
different
scope.
For
me,
I
got
you.
A
C
C
They
might
not
know
we're
in
code
freeze,
even
though
it's
like
out
there,
it
might
be
hard
to
find
it
might
even
be
something
worthwhile
to
have
like
on
the
contributor
site
like
maybe
there
should
be
like
a
website
that
explains
how
code
phrases
work,
that
we
could
just
link.
C
C
So
if
it
might
be
easy
to
link-
maybe
that's
a
a
really
simple
thing,
saying:
hey
you're
new,
we
love
having
you.
Maybe
there
could
be
like
a
new,
a
new
bot
instead
of
just
all
the
notification
spots.
It's
like
a
new
bot
that
just
says:
hey
here's
a
link
to
more
information
about
where
we
are
in
the
code
freeze
process
and
something
like
that.
I
don't
know
it's
just
kind
of
a.
I
can
easily
see
somebody
going.
Where
do
I
go
to
find
this
information?
E
It's
been
about
a
year
since
I
was
on
a
release
team,
but
in
my
experience,
actually
the
largest
plurality
of
people
trying
to
push
feature
prs
without
filing
an
exception.
During
code,
freeze
were
actually
regular
contributors
who
had
been
gone
for
a
couple
of
months
and
had
come
back
and
not
realized.
We
were
in
code
freeze.
A
I
know
we've
talked
about
this
in
the
past,
but
maybe
like
essentially
like
a
banner
at
the
top
of
the
page
or
something
so
when
you
go
to
just
says,
like
hey
code
freeze
is,
in
effect
with
a
link
to
you,
know
the
the
details
about
about
the
freeze,
or
you
know,
enhancement,
freeze
or
something
like
that.
A
A
A
So
if
you
happen
to
miss
this,
we've
had
a
lot
of
issues
come
up
over
the
past
year.
Just
you
know,
people
had
to
re-prioritize
and
step
away
from
things,
but
that's
left
a
lot
of
areas
and
sort
of
like
in
our
projects
and
initiatives
that
haven't
been.
A
You
know
staffed
that
well
and
it's
sort
of
fallen
on
to
just
a
couple
people
or
in
some
cases,
no
people
to
maintain
it,
and
so
we
were
looking
at
sort
of
what
things
we
must
maintain
and
support,
and
you
know
make
sure
that
we
can
at
least
staff
those
up
to
a
good
amount.
A
A
good
example
is,
you
know
the
zoom
and
youtube
admin
for
the
a
large
part.
That
is
honestly
just
been
me
popping
into
into
youtube
and
pushing
you
know:
videos
live
and
it'd
be
nice
to
have
some
other
people
helping
out
with
that
again.
A
But
when
we
we
sent
this
out,
we
actually
got
a
lot
of
people
interested
in
you
know,
picking
up
in
certain
areas
and
helping
out
and
just
to
have
people
had
a
chance
to
like
take
this
spreadsheet
at
all.
I
just
want
to
make
sure
that
we're.
A
Yeah
automation,
instead
of
new
folks
yeah,
we
they
actually
have
for
some
of
the
stuff.
For,
like
the
zoom
and
youtube
thing,
we
have
an
outstanding
issue
about
automating
it.
It
basically
tried
to
get
away
from
splain
and
use
like
zapier
for
some
of
our
stuff.
D
G
A
But
in
in
any
case,
we've
got
a
lot
of
people
interested
in
helping
out,
which
is
awesome.
No,
I
think
it's
just
you
know,
sort
of
coordinating.
You
know
directing
the
new
effort.
G
I'm
I'm
a
little
lost,
but
this
is
exactly
what
I
meant
when
I
said
I'm
willing
to
help.
So
bob
tell
me
what
you
want
me
to
do.
A
Oh,
that's
awesome,
paris.
A
H
G
I
mean
sure
but
yeah
eager
to
help
and
actually
figured
I'd
join
here,
because
I
think
we
should
catch
everyone
who's
eager
to
help.
A
And
some
of
the
other
things
in
here
isn't
even
necessarily
staffing
it
up,
but
just
where,
like
we
have,
you
know
a
low
amount
of
active
approvers.
So
that's
getting
you
know
more
people
reviewing
it
in
some
cases.
Like
the
you
know,
the
contributor
site,
you
know
we
could
use
more
people
there,
but,
like
I
haven't,
spent
the
time
actually
speccing
out
all
the
issues
and
other
areas
where
people
can
help.
A
A
Okay,
well,
I
don't
have
anything
else
on
the
agenda.
Is
there
anything
else
that
people
want
to
talk
about,
at
least
on
the
record
on
this
call.
I
So
I
don't
know
if,
if
you're
cool
with
that
alex
or
if,
if,
if
you
don't
want
to
stick
around,
obviously
you
can
hang
up,
but
there
are
several
areas
I
feel
like
I
could
we
could.
I
could
staff
like
50
people,
easy
right
now
so
hold
on
alex
dude.
Tell
me
a
little
bit
like
I
didn't.
We
might
even
want
to
stop
the
recording
yeah.