►
From YouTube: Node.js Build WG meeting - Dec 18 2018
Description
B
B
E
D
A
B
C
B
E
E
F
E
A
E
A
E
It
I
mean
possibly
the
not
make
sense
I
feel
the
bit
I
feel
we
detach
from
the
Mac
in
further
than
you
make
infer
so
having
more
assistance
to
help
with
those
machines,
probably
a
good
thing
I.
But
we
have
to
be
conscious
here.
That
I
mean
a
lot
doing
this
for
a
large
company,
as
we've
said
before,
is
it's
easier
because
we
have
this
chain
of
responsibilities
so
that
if
somebody
who
works
for
an
IBM
screws
up
our
staff,
they
can
be
held
liable
through
their
employment.
E
So
so
that's
an
easier
chain
of
responsibility
and
accountability,
but
we
have
to
be.
We
have
to
be
sure
that
we
can
be
clear
about
those
access
rules
and
those
those
reasons
so
that
when
we
have
others
saying
we'll,
hang
on
I'd
like
access
to,
because
I'm
really
good
at
this
stuff,
which
need
a
lot
of
people
are
I
mean.
We've
got
some
really
good
people
who
don't
work
for
big
companies.
E
E
Think
so,
until
we
have
a
real
problem,
I'm
not
sure
we
have
had
a
real
pro
with
the
main
stuff
yet,
but
I
certainly
I
think
we
should
be
have
a
mind
to
that,
to
expanding
that
sure
and
having
and
having
a
mechanism
whereby
we
can
expand.
The
number
of
people
have
access
to
these
things
and
have
a
chain
of
can
ability
yeah.
So
let's
figure
out
a
model
for
them.
Yeah.
A
B
D
D
F
E
D
E
So
I
of
us,
I,
think
you've
started,
have
started
an
effort
to
move
us
over
to
went
to
1604
it
when
I
got
caught
because
there's
something
in
our
make
file.
That
is
specific
to
that
didn't
work.
Oh
look
not
on
FreeBSD,
ok
and
I.
Don't
recall,
I
think
it
was
John
also
tried
to
do
this
as
well
and
I'm
surprised
that
we're
still
looking
at
it
now
surprise
we
still
on
it.
So
obviously
he
got
caught
as
well,
but
it
would
be
nice
to
move
off
FreeBSD
10,
so
maybe
I
actually
know
this.
B
E
A
C
E
E
E
B
A
Mean
my
understanding
of
it
so
far
is
that
while
I
was
away
the
CI
job
stopped
working,
I've
read
through
very
briefly,
but
not
had
time
to
read
in
more
detail.
It
sounded
like
there
was
a
commit
that
somehow
broke
the
generation,
the
coverage
possibly
related
to
the
add-ons,
not
the
tests
not
running
or
something
like
that,
I,
don't
think
Benjamin.
You
had
a
bit
better
look
at
what
was
going
on.
Can
you
hear
me?
Okay,.
F
Yep
I
yeah
on
my
computer.
It
seems
to
be
running
fine
and
I.
Think
from
the
the
thread
it
sounded
like
it's.
Maybe
a
build
error
happening
as
the
as
the
tests
are
basically
deployed
on
the
server
and
someone
was
commenting
in
the
thread
as
well.
I'd
have
to
open
up
the
thread,
but
it
sounds
like
this
happened
a
couple
months
ago
and
there
was
a
similar
fix.
Perhaps
yeah.
A
F
Well
I
was
gonna
say
that
one
recommendation
have
I've
been
kind
of
just
itching
to
get
the
v8
coverage
being
used
in
node
so
that
we
wouldn't
even
have
to
do
that
instrumentation
then
it
would
mean
that
I
test
coverage
is
just
as
fast
as
regular
tests,
so
you're
close
to
as
fast
as
regular
tests.
Right,
if
we'd
be
open
to
that,
the
the
one
limitation
right
now
is.
It
misses
some
lines
of
code
in
return
statements,
because
chromium
doesn't
see
that,
as
a
doesn't
see
the
term
a
line
as
having
been
executed.
A
A
F
F
A
F
A
A
E
F
A
A
You
know
I.
It
would
be
good
to
get
that
patch
see.
If
we
can
have
you
know,
I
could
tweak
the
CI
job
or
we
could
make
a
clone
CI
job.
Actually,
that
you
know
basically
would
apply
that
patch
and
then
generate
the
rest
of
the
you
know:
go
through
the
rest
of
the
steps
and
see
what
it
reports
and
if
it
reports
you
know
similar
data,
then
we
can.
You
know
what
we're
one
step
closer
to
switching
over
as
well
yeah.
F
F
A
F
A
F
A
Yeah
so
I
think
I
think
you
know.
Basically,
if
we
can
work
on
the
the
the
change,
the
the
patch,
which
basically
changes
the
the
coverage
target
to
do
what
we
need
to
do
with
the
new
zing,
a
patch
that
chain
that
applies,
the
change
to
Chrome,
then
I
can
help
set
up
a
CI
job
that
you
know
mirrors
what
we've
got
for
the
existing
CI
job.
We
can
sort
of
test
those
out
and
manually
apply
the
patches
until
they're.
A
F
A
F
Do
you
know
what
I
should
have
brought
up
the
one
sorry
to
interrupt
the
one
thing
worth
mentioning
is
the
rapper
stuff
that
there
is
a
prefix
in
in
node
code
that
adds
a
few
bytes
and
causes
coverage
to
be
off.
I
think
we
can
work
around
that,
though
it's
just
annoying,
but
we
will
just
need
to
take
into
account
headers
on
files.
Basically.
A
A
B
B
A
A
Opening
that
again
to
sort
of
rear,
A's
the
discussion
of
well,
how
do
we,
you
know
one
the
suggestion
there
is,
and
you
know
it's
been
used
by
other
projects
and
been
discussed
before
we
never
come
to
consensus,
but
I
thought
it
was
worth
discussing
again.
Is
you
know
one
one
approach
is
to
actually
have
Foundation
resource,
who
is
call
and
can
help
with
core
things.
You
know
not
not
everything,
but
with
things
that
people
need
immediately,
as
opposed
to
can
wait
for
when
somebody
has
time
to
work
on
them.
Yeah.
B
B
I
imagine
rich,
could
probably
fill
us
in
a
little
bit
more
because
I
was
a
bit
knew
when
this
was
happening,
but
it's
kind
of
the
implication
of
we
want
people
to
almost
be
on
call,
but
obviously
it's
a
voluntarily
so
process,
and
it
can
be
a
little
bit
hard
to
get
those
people
in
place.
I
guess
to
always
be
there
to
support
the
infra
when
it
when
it's
most
critically
needed.
D
You
know
I,
don't
I've
I've
always
had
mixed
feelings
about
this
I'm
sure
rod
has
some
mixed
feelings
or
maybe
not
mixed
feelings
that
he
can
articulate
because
he's
spoken
about
this
specific
issue
eloquently
in
the
past,
if
I'm
not
mistaken,
did
I
answer
I
mean
I.
Don't
really
know
that
I
really
have
any
more
insight
on
the
moderation
team
page
of
Duty
coverage
thing
than
you
do
George.
There
wasn't
really
a
whole
lot
that
went
on
there.
I.
A
E
A
E
But
but
it
is,
is
mixed
feelings
really,
because
I
I,
don't
I,
don't
want
to
be
on
the
hook,
for
you
know
for
any
random.
That
wants
to
tell
me
that
stuff's
breaking
too
drop
what
I'm
doing
and
go
and
fix
stuff
forget
I'm
nobody's
paying
me
to
work
on
load
right
now
on.
You
know,
I'm
mr.
limbo,
so
that
causes
some
mixed
feelings.
I.
You
know
I'd
like
to
see
more
companies
like
IBM
step
up
and
put
resources,
and
maybe
that's
something
we
can
work
on
and.
A
E
E
I
mean
look
at
look,
we've
got
like
150
hosts
in
CI.
We
could
certainly
trim
that
we
could
be
and
we
could
be
more
aggressive
with
the
way
we
support
things.
I've
been
trying
to
do
that,
a
bit
actually
on
the
build
rebuild
you
know,
putting
in
issues
for
removing
dude,
older
versions
of
Linux
quicker.
C
A
F
D
A
D
E
It
works
really
well
now,
and
we
really
have
issues
that
are
armed,
v6
and
seven
specific.
We
could
just
accept
that
and
say:
well,
it's
going
really
well.
We
don't
need
to
be
so
comprehensive
in
our
testing
and
we
need
to
start
trimming
resources
all
we
could
move
to
do
some
emulation
or
I.
Don't
know
what?
Oh,
maybe
you,
maybe
maybe
maybe
at
some
point
soon,
it's
time
to
say,
arm
v6
support
is
gone,
I
mean
that's
reasonable,
I
think
v8
on
the
verge
of
doing
that.
E
Probably
so
we
start
actually
being
aggressive
here
as
well,
but,
like
I,
think
this
is
part
of
a
bigger
discussion
about
rationalization
of
resources.
Let's,
let's
actually
admit
to
ourselves
that
it
is
a
cost.
The
this
camp,
complex
architecture
we
have,
and
we
did
it
because
we
could
not
because
we
needed
it,
and
maybe
we
don't
need
it.
Yeah.
E
A
E
E
From
our
experience,
my
my
hunch
is
that
it's
it's
very
tightly
correlated
with
number
of
machines,
the
more
machines
we
have,
the
more
probability
of
one
of
them,
having
a
trouble
like
that,
you
know:
CentOS,
7,
I'm,
64,
machine
rich.
That
was
having
trouble.
That
was
just
a
matter
of
cleaning
it
up.
Fewer
machines
means
fewer
of
those
kinds
of
problems.
That's
my
guess,
but
perhaps
there's
something
more
structural
to
the
way
we're
doing
things.
Perhaps
it's
to
do
with
the
way
we're
utilizing
Jenkins.
E
Maybe
we
need
to
have
some
some
internal
strategic
initiative
looking
at
and
measuring
pain
points,
maybe
we
need
to
do
better.
Logging
of
pain,
I
really
and
we've
looked
at
that
we've
looked
at
that
a
lot
in
the
past.
How
do
we
record
these
things
and
we're
not
we're?
Still
not
doing
a
very
job
of
it,
I
mean.
D
I
guess
like
put
down
on
a
piece
of
paper
like
this
is
a
pain
point.
It's
very
what's
difficult
is
is
quantifying
it.
You
know
like
like
how
much
pain
like
how
what
is
the
cost
of
you
know
say,
like
you
know
the
the
aforementioned
AIX
issues
of
the
last.
You
know
a
few
days
slash
week
versus
the
raspberry
pie,
pain
of
yesteryear.
You
know
like
what
you.
A
D
D
D
D
Is
it
really
that
platformers
the
plat
war
is
the
test
buggy
and
the
platform
is
actually
doing
the
right
thing
by
forcing
us
to
fix
our
or
tests
or
our
code,
so
it
all
gets
pretty
fuzzy
pretty
fast,
but
and
and
it
will
be
difficult
to
collect
that
kind
of
information,
but
it
could
be
collected
in
a
pretty
narrow
way
like
just
like
one
day's
worth
of
data
could
probably
be
pretty
manageable
question
is
how
much
use
would
that
be
cuz?
You
know,
that's
the
other
thing
is
that,
like
you
know,
you.
D
A
I
mean
I,
don't
I,
don't
think
we
want
to
say
what's
our
problem
this
week
or
last
week,
it's
like
what
continually
causes
us
grief
and
if
it's
you
know
so,
if
it's
like
that,
there's
always
some
random
machine
and
it's
a
different
platform
different.
Whatever
then
looking
at
how
we
reduce
numbers
helps
I
mean
in
terms
of
the
performance
like
I,
you
know,
George
is
looking
at
adding
an
AIX
machine
to
try
and
help
the
throughput
side
of
things
which
kind.
F
D
I
think
automating,
it's
gonna
be
a
really
difficult,
because
you
know
a
lot
depends
on
whether
a
particular
failure
is
because
the
platform
is
yeah.
You
know
actually
I've
been
showing
you
yeah
I
bet,
I
could
work
with
Joey
or
at
least
use
some
of
the
tooling.
She
wrote
to
kind
of
make
this
manageable,
because
I
go
slip,
require
human
intervention,
but
a
human
just
needs
to
look
and
say
you
know.
You
know
this.
This
wasn't
infra
issue.
This
was
like
a
thing
that
rebooted
and
nobody
rebooted
it
for
seven
hours.
D
So
for
seven
hours
we
have
failing
tests.
You
know
like
that's
like
that's
that's
a
pain
point
as
opposed
to
this
was
somebody
somebody,
you
know,
landed
a
bad
commit
and
then
it
was
broken
for
seven
hours,
because
somebody,
you
know
cuz,
because
that's
how
long
it's
to
figure
that
out
and
revert
that's
the
CI
doing
its
job.
You
know
that
does.
A
It
like
right
exactly
like
it's
because
I
think
our
struggle
or
we're
you
know
the
reason
I
open
this
issue
in
the
first
place.
Is
it
it's
the
the
not
being
not
responding
like
not
being
able
to
respond
on
call
quickly
enough
to
things
like
you
said,
like
a
machine
just
needs
to
be
kicked
and
it
takes
seven
hours.
E
E
E
D
D
Like
you
know,
I
mean
Michael
you're,
just
over
committed,
I
mean
in
terms
right,
I
mean
billed
as
builders
are
really
you
know
under
resourced
thing,
and
there
is
some
I
mean.
This
goes
back
to
that
issue,
one
three,
three,
seven
that
we
were
talking
about
before
that
you
know
there
is
some
element
of-
and
this
is
a
loaded
term
and
I
apologize,
but
there's
an
element
of
gatekeeping
that,
like
you
know,
you
know,
some
people
are
allowed.
D
F
E
No
I'm
actually
not
sure
that
you're
right
with
that,
because
we
know
we
do
have
members,
we
do
have
people,
but
we
don't
have
a
uniform
way
of
getting
the
attention
of
people,
so
some
people
know
they
can
go
on
IRC
and
you
can
get
certain
people.
Some
people,
though,
that
if
you
go
on
github,
then
they'll
be
more
respect.
We
have
a
channel
problem,
I
think,
but
we
also
have
a
problem
of
I.
E
Think
I
think
we
do
have
a
lot
of
people
that
could
solve
a
lot
of
these
problems,
but
they
are
they're,
not
I.
Don't
they
don't
feel
like
they
can
step
up
and
be
frontline
or
they
wait
for
someone
else
to
do
it,
but
I
think
we've
got
plenty
of
people
with
access
like
the
test.
The
test
key
will
will
solve
a
lot
of
things.
Yeah.
E
Who
can
access
CMC
a
Jenkins
CI
that
the
test
CI
as
admins?
There's
this
a
bunch
of
people
that
can
do
this
stuff
is
I.
Just
don't
think
we
have
a
uniform
way
of
notifying
or
getting
attention
or
even
prioritizing,
because,
like
I'll
I'll
I'm
on
IRC
I
can
get
I
get
as
notifications
on
my
phone,
but
often
it's
like
I,
see
notifications
and
I'm
out
and
I'm
like
I,
don't
even
know
whether
that's
important
or
not.
You
know
that
kind
of
problem
yeah.
D
Actually,
so
that's
a
that's
a
really
good
point:
we
don't
we
don't
have
a
single
uniform
way
like
like
the
the
issue
tracker
in
the
build
repo
is
no
I
mean
like
I
I,
never
like
using
it,
because
I
feel
like
it's.
You
know
like
anything
I
put
in
there
is
probably
going
to
be
ignored
or
nor
these
for
at
least
for
you
know
several
days
before
somebody
looks
it
and
that's
and
that's
you
know
like
and
and.
B
D
Like
you
know,
I've
done
systems,
administration,
I,
think
I
know
how
to
have
it
had
a
handle
so
but
like
I
I,
don't
know
how
to
like
I
I,
don't
know
how
to
do
half
the
stuff
that
needs
to
be
done
and
I
don't
know
who
to
ask
necessarily
you
know
and
I,
don't
know
that
anybody
has
the
bandwidth
to
train
and
so
and
so
there's
a
lot
of
also
siloing
there
where
it's
like
you
know,
if
you
want
Windows
stuff,
you
know
your
hopes.
Your
hours
around
you
know,
yeah.
D
So
yeah
and
and
and
then
there's
you
know
and
then
and
then
some
of
the
IBM
stuff
is
is
is
sufficiently.
You
know
not
widely
understood
that
you
know
you
really
want
an
IBM
person
to
look
to
look
at.
You
know
like,
like,
thank
goodness,
gracious,
looking
at
those
those
those
crashes
that
we
see
on
all
platforms,
but
we
see
especially
on
it.
You
know
X,
probably
you
know
just
because
of
a
particular
peculiarity
of
the
way.
You
know
the
timing
of
certain
things
on
it.
D
It's
probably
you
know,
X
is
probably
behaving
exactly
appropriately,
but
there's
it
just
happens
to
be
behaving
in
a
way
that
happens
to
trigger
a
bug
that
we
haven't
found
yet,
but
anyway
you
know
like.
If
we,
you
know,
you
know
like
I
I,
don't
think
any,
but
you
know
like
Gabriel
Hoff
is
trying
to
like
help
out
with
that
and
everything
more
than
that.
You
know
I,
don't
there's
anybody
outside
of
IBM
who
could
possibly
really
be
effective.
D
A
D
And
it's
good
that
we're
testing
on
it
like
that's,
not
a
bad
thing,
but
but
yeah
I
mean
and
then
the
last
thing
is
that
our
our
is.
That
is
that
you
know
we
keep
having
these
initiatives
to
like
improve
our
documentation,
get
it
more
complete,
make
it
more
organized
and
they
kind
of
keep
stalling
out
and
I.
Think
people
kind
of
burnout
on
doing
that.
A
E
I
think
that's
probably
a
good
thing
to
do.
I
think
Google's
could
certainly
contribute
more,
although
they
in
the
past,
their
contribution
is
being
able
to
form
our
well.
If
you
do
it,
this
new
new
fancy
way
that
we
want
to
do
it
and
you
can
really,
but
that's
probably
something
we
could
do
because
there
and
we-
and
we
could
actually
in
doing
that,
we
could.
We
could
make
a
statement
about
how
IBM
and
Microsoft
are
the
ones
putting
up
a
lot
of
the
resources
right
now
and
Google's.
A
Right
and
I'm,
even
just
thinking
a
little
bit
like
it,
would
firm
up
if
it's
a
corporate
commitment
instead
of
individuals
it
sort
of
firms.
Ups
as
well,
the
motivation
like
it's,
not
it's,
not
you
as
an
individual,
saying
hey.
This
is
the
right
thing
to
do.
Can
I
contribute
it's
different.
If
the
company
is
saying
hey,
we've
committed
people
to
contribute.
Can
you
do
this
for
us
and.
E
E
A
B
B
B
And
we
sat
down
and
we
were
really
going
through.
What
and
all
of
these
common
cleanup
tasks
were
a
lot
of
these
are
very
simple
commands.
I
mean
the
Libby
V
gos
job
that
I
cleaned
up
the
other
day.
I
must
have
done
that
seven,
eight
nine
times
every
time,
I
run
the
same
command,
and
this
really
goes
with
that
whole
column
and
support
our
concept
of
if
we
could
create
something
that
was
safe
for
collaborators
to
run.
That
would
absolutely
and
yeah
exactly
click
a
button,
and
it
does
it
restarts
to
Jenkins
agent.
B
A
E
Think
about
Windows
if
we
had
tasks
for
Windows
to
do
cleanup
that
none
of
us
are
comfortable
doing
the
I.
Think
of
the
IBM
platforms,
like
I'm,
I'm,
afraid
of
touching
AIX.
It's
just
have
no
idea.
So
if
we
had
a
button,
I
could
click
to
say
do
the
things
that
I
bien
people
would
do,
but
clear
rich
could
do
the
same
on
any
other
platforms.
Where
he's
not
comfortable
doing
since
a
youngster
I
think.
A
B
We
can,
rather
than
rather
than
putting
aside
people
time
and
saying
I,
want
to
have
X
number
of
people
working
around
the
clock
to
ensure
that
area
X
and
Windows
work.
We
can
actually
put
that
resource
in
the
direction
of
the
saying.
What
is
it
that
those
IBM
people
time
you
know
I'm
sure,
there's
going
to
be
issues
where
we
do
need
those?
You
know
low
levels,
C++
experts
on
a
particular
platform
to
have
a
look,
but
a
lot
of
the
Machine
issues.
F
A
Still
thinking
that,
even
if
we
even
if
we
can
do
that-
which
I
think
is
some
area
we
should
focus
on,
I
still
wonder
if
somehow
trying
to
go
back
to
the
foundation
and
get
more
sort
of
you
know
say
is
the
foundation
members.
We
need
support
more
support
for
the
build
infrastructure
from
those
members
make
sense
yeah.
You
know
if
they
say
yes,
then,
and
and
one
of
the
things
they
can
help
do
is
to
build
those
scripts.
That
makes
everything
easier.
That's
a
great
thing,
too
right,
yeah.
B
Either
way,
either
way
we're
winning
right.
We
probably
need
more
of
that
expertise
there,
but
if
we
can
also
automate
some
of
that
out
and
we're
making
everyone's
life
easy
and
as
I
say
what
I
really
like
about.
That
is
that
you
know
we
could
really
open
it
up
to
collaborators
or
anybody
to
come
in
and
click
a
button
and
very
safely.
You
know
clean
a
machine
without
even
actually
needing
SSH
access,
I,
yeah
well.
C
C
E
Because
we're
chasing
our
tails
on
a
complex,
infinite
infrastructure
that
we
have
it's
a
road
for
our
own
backs,
so
I
think
as
any
question
of
strategic
initiative
to
to
look
at
this
strategically
like.
Let's
be
rational
about
what
resources
we
have,
what
we
want,
what
resources
we
want
to
be
able
to
spend
on
these
these
stuff
and
and
what
our
ability
to
take
on
volunteers.
All
that
stuff,
I
think
would
be
a
good
thing
to
do.
I'm
I'm
interested
in
that,
because
I
don't
want
to
be
I,
don't
think
I'm
gonna,
be.
E
This
is
this
stuff's,
a
hobby
for
me
and
I
I'm,
very
unlikely
to
be
paid
to
do
this
next
year,
wherever
I
land,
so
I
would
like
to
still
be
able
to
treat
it
as
a
hobby
and
not
something
where
I
have
just
like
I
spin,
it's
been
a
bunch
of
hours
yesterday,
cleaning
stuff
up
catching
up,
and
that's
that's
not
a
good
sign
that
volunteers
need
to
spend
hours
of
their
time
doing
it
so
maybe
rich
you
and
I
should
kick
off
something
in
the
new
year.
I.
B
A
B
Right,
so
one
of
the
main
issues
is
obviously
that
we've
only
got
the
two
X
machines,
so
when
one
goes
down
the
backlog
piles
on
pretty
quickly
yeah.
The
other
thing
is
that
the
current
host
of
those
machines
is
pretty
old.
It's
not
particularly
well
configured
so
obviously
that
those
machines
are
currently
slow,
yeah.
It's
it's
just
not
ideal.
I,
usually.
D
Doesn't
take
much
for
a
machine
for
a
1dx
machines
to
become
unavailable
because
we
run
carrying
online
on
ax
and
you
know,
and
then
and
then
there
are
the
reasons
that
I
can
get
into
it
and
then
I
think
I'm
wondering
if,
like
C
cash
might
have
been
I
keep
mean
to
look
at
this.
If,
like
C
cash
isn't
running
on
it
or
something
because
like
like
even
like
the
last
bill
took
over
an
hour,
seems
like
like
it's
the
longest
of
everything,
and
that
just
seems
the.
A
A
A
machine
one
of
the
you
know
a
pair,
so
we
should
have
three,
hopefully
within
the
not-too-distant
future,
and
then
we
are
what
we
have
a
massive
machine
which,
if
we
can
just
get
it
there
will
give
us
the
flexibility,
add
lots
and
lots
of
machines,
so
I
think
we've
got
the
action
to
do.
We
can
on
that
front
yeah.
B
A
A
In
terms
of
talking
going
to
the
foundation
to
I,
don't
know
see
if
we
can
do
you
think
that
that
makes
sense
like
do
we,
you
know,
go
back
to
them
and
say
we'd
like
to
ask
for
more
direct
help
on
this
front
from
you
know
the
foundation
members
is
that
worth
the
shot,
as
well
as
part
of
that
or
separately
I.
Don't
know,
dallisa.
D
As
the
first
thing
to
do
might
just
be,
the
like,
you
know,
have
you
know
miles?
Is
the
TSC
director
or
someone
else,
it's
kind
of
bring
it
to
the
board
that
look.
Build
is
really
understaffed
and
here
are
the
thing
or
rather
under-resourced,
and
here
are
thing
that
could
help
people
machines,
etc
and
and
just
and
and
see
what
see,
what
the
member
companies
actually
like.
A
A
X
because
otherwise
you
know
it's
sort
of
like
okay,
we
recognize
the
problem.
What
do
you
want
us
to
do?
What?
What
I
don't
think
we
want
us
to?
What
we
don't
want
is,
like
somebody
say,
oh
yeah.
Well,
we've
got
all
this
different
technology.
Why
don't
we
switch
over
to
that
I?
Don't
think
that
helps
us
in
the
short
term,
at
least.
E
E
Unless
we
trim
out
you
sorry
trim
our
scope
unless
we
get
more
resources
to
maintain
current
scope.
Maybe
we
put
it
that
way
and
we're
going
to
be
looking
at
that
in
the
new
year.
If
there
are
companies
in
the
member
companies
that
wish
to
contribute,
then
we'd
like
to
hear
from
them
now.
So
we
can
take
that
into
account
something
yeah.
A
E
Think
a
stronger
ask
actually
needs
us
to
be
clear
about
what
we
need
in
need.
So
that's
what
I'm
saying
if
we
want
to
do,
if
you
want
to
ask
now
it
has
to
be
we're,
gonna
be
looking
at
this.
You
have
to
list
know
if
we
want
to
do
a
stronger
art,
so
let's
wait
until
we've
done
actually
this
accounting
and
think
what
we're
doing
what
we're
doing
what
we
need
and
then
we
can
go
back
to
and
say
look.
This
is
where
this
is
the
state
of
play.