►
From YouTube: Node.js User Feedback Initiative - 2018-03-16
Description
A
All
right
great
so
welcome
everybody
we're
doing
a
regular
team
meeting
of
user
feedback
team
and
this
week
we
want
to
prepare
for
the
public
session
that
we're
going
to
be
doing
together
with
the
noches
tooling
ecosystem.
So
we
have
Christopher
Hiller
who's
joining
us
and
you
know
Chris
is
the
maintainer
of
mocha
and
Christy
you
you
mentioned
you
had
the
opportunity
to
reach
out
to
a
couple
folks.
You
know
how's
that
outreach
going
I've
got
some
folks
on
the
on.
B
A
So
what
we
do
with
user
feedback
is
bring
together.
You
know,
members
of
the
broader
community
and
members
of
the
community
committee,
the
calm,
calm
in
the
node.js
project
and
the
technical
steering
committee.
So
you
know
we
really
want
to.
You
know,
provide
insight
into
the
needs
of
your
end-users.
It
in
this
case
end
users
that
are
leveraging
node
to
build
tooling
yeah.
C
And
in
my
mind,
the
perfect
world
will
build
up
a
group
that
you
know
we
come
together
at
some
periodic
basis.
So
it's
not
like
a
one-time
here's
our
issues,
it's
like
more
of
a
here's,
a
group
of
people
that
we
can
regularly
keep
in
touch
with
we're,
making
a
decision
that
seems
to
you
know
affect
tooling.
We've
got
a
group
of
people.
We
can,
you
know
talk
to
in
person
as
well
as
sort
of
I
think
you
know
we
should
have
the.
C
B
C
And,
like
you
know,
your
earlier
question
is:
is
we
also
want
to
be
as
inclusive
as
we
can?
So
you
know
anybody
who
shows
up-
and
you
know
self-selects
as
a
representative
of
that
group-
is
welcome
to
come
and
participate
well
Steve.
So
it's
it's
good
to
you
know.
If
what
you're
doing
in
terms
of
you
know
finding
some
specific
people,
you
think,
would
be
good
participants
and
but
on
the
other
hand,
we
also,
you
know,
that's
why
you
saw
the
public
call
to
say
hey
if
anybody's
interested.
C
A
C
A
C
On
tolling,
or
is
it
part
of
our
service
team?
So
I
worked
it
quite
closely
with
him,
and
you
know
his
he's
got
an
interested
in
tooling,
of
course,
and
that
you
know
we
need
tools
to
support.
You
know
our
our
customers
and
you
know
he'd,
be
writing
some
tools
to
help
do
that
kind
of
stuff.
So
that's
where
his
interests
comes
from
great.
A
Right
they
wanted
to
categorize.
You
know,
folks,
a
bit.
You
know
if
they're
you
know
they're
to
participate
in
feedback
or
give
feedback
or
listen
to
feedback
versus.
If
they're,
you
know
actively,
you
know,
but
whether
the
you
know
in
the
situation
like
we
were
at
index
via
whether
they
would
be
on
stage
right.
Yes,.
D
C
C
D
A
C
Two
guys
who
I
had
in
that
effort
are
actually
a
little
bit
focused
on
other
things.
Right
now:
okay,
but
I,
we
will
be
like
I'm
looking
for
the
person
who's
gonna,
help,
pull
it
into
core
and
you're
right
that,
then,
that
person
would
be
the
right
one
to
just
sort
of
get
involved
from
that
perspective
to
you
so
yeah
I'll,
take
it
I'll,
take
an
action
to
figure
out.
You
know
who
we
can
get
on.
That
side
may
not
be
for
the
first
one,
but
it's
a
good.
Definitely
a
good
idea.
C
B
C
A
C
Know
I
that
was
so
right.
It
was,
and
I
was
actually
in
the
UK,
so
it
was
even
earlier
so
I
know,
I
didn't
make
it
I
guess
that
was
just
for
visibility
as
opposed
to
anything
like
hey
here's.
This
is
happening.
It's
well
know
somebody
to
mention
it.
Okay,
even
have
been
be,
let's
mention
in
the
meeting
today
that
might
have
been
the
model
modules
meeting.
Actually,
okay,
which
there
was
one
this
week
as
well,
which
also
didn't
make
because
I
was
traveling
but
I.
Think.
C
A
A
Sure,
okay,
and
actually,
when
I,
was
creating
this
issue,
you
know
I
was
typing
it
out.
You
know
I
really
had
that
realization
to
it's
like
yeah
I'm,
not
really
just
looking
for
TSE
I'm
looking
for
collaborators
to
engage
and
anyone
who's
working
on
core
to
have
insight,
but
you
know
notwithstanding:
I
am
particularly
you
know,
given
the
trajectory
that
the
you
know,
tooling,
team
would
like
to
take,
which
would
be
a
greater
involvement.
Your
tooling
folks
would
like
to
take
not
team.
Sir.
C
A
So
the
context
is,
how
does
tooling
you
know,
like
we've
seen
with
modules,
engage
with
the
technical
project
in
the
long
term
right?
So
you
know
this
is
a
dialogue
opener
and
we
don't
know
the
the
path.
There's,
not
a
lot
of
existing
patterns
beyond
modules,
for
you
know
where
the
ecosystem
interests
like
this
plugin,
you
know
so
you
know.
Is
it
calm,
calm?
Is
it
on
the
technical
side
of
the
house?
Is
it
admin
the
you
know?
Go
no,
but
you
know
what
what's
the
next
step?
C
A
C
So
yeah,
I
think
I
think
in
that
sense,
maybe
after
we
have
the
initial
discussions
and
you
know
you
and
I
understand
a
bit
better,
we
could
go
back
and
look
at
who
might
be
interested
and
then
you
know
ping
them
and
say
hey.
These
kind
of
discussions
are
happening.
You
know,
maybe
you
know,
can
you
spare
the
time
that
kind
of
thing?
What.
E
E
C
Mean
I
think
in
the
firt
life.
So
if
we're
thinking
about
the
net
the
meeting
next
week,
what
we
want
to
accomplish
I
mean
in
my
mind
it
would
be
great
to
you
know.
Obviously
yeah
you
understand
who
the
different
people
are,
who
are
gonna
start
to
participate
and
then
maybe
dig
a
little
bit
into
you
know.
What's
going
right
or
what's
going
wrong,
cuz
I
think
that
will
help
us
decide
what
what
we
need
to
do
going
forward
right
like
if
it's
a
we're
all
happy,
there's
no
real
problems.
Then
there's
not
necessarily.
C
You
know
well
I'm
sure
they'll
be
interesting.
Things
to
discuss,
but
it'll
be
more
of
a
we'll
have
to
come
up
with
you
know,
thoughts
of
you
know
what
kind
of
information
we
want
or
whatever,
but
if
there's
specific
things
there
like
here,
these
are
real
pain
points
that
will
give
us
some
direction
in
terms
of
like
okay.
Well,
if
we
want
to
start
working
on
some
of
those
pain
points
who
would
be
people
that
are
all
know,
that
kind
of
side
of
things
yeah.
A
B
A
D
C
B
B
B
D
D
Like
you
know,
miles
and
and
Jordan
they've
been
involved
in
the
project
for
quite
a
while
and
I
just
be
concerned
that
we're
you
know,
continuing
to
build
like
an
echo
chamber,
kind
of
to
ourselves
and
the
feedback
that
we've
already
gotten
I'm
and
elevating
those
voices
over
something
with
people
who
at
least
I've,
considered
I
had
conversations
with,
say,
I
feel
like
we're
kind
of
very
much
in
an
echo
chamber
in
a
very
exclusive
environment.
It's
hard
to
break
into
so
I
think
we
really
should
try
to
optimize.
D
A
Can
we
talk
to
through
that
a
little
bit
Michael?
What?
Where
would
we
you
know?
I,
don't
keep
my
concern.
I
guess
is,
you
know
we're
you
know
creating
space
for
this
discussion
and
then,
where
does
it
go
right?
It's
not
clear
that
lives
in
the
you
know,
calm
calm.
You
know.
User
feedback
is
not
an
incubation
space
for
initiatives
to.
C
Know
what
my
sort
of
thing
on
the
user
feedback
is.
It's
our
focus
is
to
keep
the
regular
contact
with
these
groups,
and
then
you
know
once
once
the
contacts
takes
place
if
there's
concrete
actions
that
need
to
happen
out
of
those
like.
So
you
know,
for
example,
it's
like
here's,
a
real
pain
point,
then
you
know
this
group
is
our
actions
to
figure
out
how
to
pull
in
the
other
people
who
can
discuss?
Maybe
that
specific
pain
point
have
a
specific
meanings
around
that
right.
C
You
know,
I
think
what
you're
thinking
is
well
like
do
we
need
to
immediately
go
to
a
strategic
initiative
around
this
or
a
working
group
or
I
could
see
that
being
useful
in
some
cases,
but
I
think
it's
equally
perfectly
reasonable.
If
we
just
have
like
you
know,
every
three
months
we
get
together,
the
group
of
you
know
in
the
different
user
representatives.
You
know
we,
you
know
this,
and
this
one
is
around
people
building
tooling
and
have
a
discussion.
C
You
know
cuz,
even
if
we
have
a
discussion
this
time
and
they
said
hey
you,
the
project.
What
you're
doing
everything
is
great.
We
like
what
you're
doing
you
might
say:
well
yeah,
but
okay,
that's
good
to
hear,
but
let's
come
back
in
three
months
and
we'll
just
make
sure
we're
not
doing
we
haven't
changed
anything,
that's
knowing
you
or
if
we're
gonna,
do
something,
and
we
think
it
is
good
enough
at
that
group.
We
can.
C
You
know,
pull
that
group
together
and
say:
hey,
let's
have
a
special
meeting,
because
this
is
what
you
know
fell
demand.
This
is
what
we're
doing,
get
the
feedback,
so
it's
it
doesn't
have
to
graduate
into
something
else,
not
that
it
can't
like.
If
there's
some
very
specific
things
you
might
say.
Well,
okay,
let's
finish
for
teaching
initiative
out
that
about
that
or
even
if
it's
you
know,
I
could
see
working
groups
making
sense,
I.
Think
the
working
group
sort
of
have
to
have
like
a
fairly
close
relationship
to
core
almost
right.
B
Great
yeah.
No,
but
you
know
I,
guess
I
guess:
I!
Do
fear
that
you
know
if
we
give
a
bunch
of
feedback-
and
you
know
it's
clear,
there's
some
actionable
items-
you
know
who's
who's
really
suitable
to
to
be
a
champion
there,
and
you
know
it's
just
I'm
sure
there's
somebody
in
in
on
the
TSU
that
works
more
with
with
command-line
tools
and
others,
and
maybe
that
would
be
a
good
person
to
reach
out
to.
B
But
you
know
until
then
I'm
certainly
I
am
I'm
trying
to
get
more
involved
in
core
myself
forget
reason,
and
so
you
know
I'm
kind
of
slowly
working
up
to
it,
but
yeah,
that's
kind
of
where
I
think
things
should
probably
go.
If
it
turns
out
everybody's
super
happy-
and
you
know,
there's
nothing
that
needs
to
be
done.
That's
that's
good
too,
but
yeah
I
don't
feel
like
there's,
there's
not
gonna
be
there's.
Certainly
gonna
be
you
know
some
some
things
that
yeah.
C
C
B
A
B
And
my
part
of
the
reason
that
that
that
that
I
thought
I'm
gonna
propose
this
idea
was
that
you
know
myself
and
some
others.
You
know
who
who
come
from
this
world
have
kind
of
you
know
felt
like
when,
when
they
proposed
an
idea
to
core
it's,
it's
it's
received
as
something
completely
out
of
left
field
and
that
sort
of
makes
sense.
If,
if
you
know
the
people
in
core
mainly.
G
B
Aren't
working
in
that
world,
so
it's
my
hope
that
we
can
kind
of
bridge
the
gap
and
come
to
a
better
understanding
of
each
other's
kind
of
needs
and
and
understand
that
you
know
what
what
may
be.
The
you
know
may
seem
like
a
strange
or
unnecessary
request
is
actually
very
important
to
it
to
a
certain
set
of
yeah.
C
And
I:
that's
exactly
if
we
can
use
this
to
bridge
the
gap
better,
understand
each
other
and
figure
out
how
to
work
together
on
the
things
that
are
important
and
yeah.
That's
exactly
because
yeah
I
think
you're
right.
If
you
just
open
to
PR
and
there's
no
context
and
no
discussion,
it's
easy
for
that.
Just
not
to
go
the
right
way!
Yeah.
D
B
C
C
I
think
yeah,
so
I
think
you
know
that's
the
path,
I
think
exactly
what
you
described
is
you
know
we
get
together.
We
have
this
discussion
with
the
User
Fee
group
feedback
group.
If
you
get
to
the
point
where
you
know
let
the
there's
enough
people
in
the
tooling
committee
like
actively
working
Beauty,
then
you
can
easily
see
it
forming
into
like
an
internal
working
group
or
something
like
that.
Yeah.
A
C
C
I'm
more
interested
in
like
before
we
go
out
and
actively
target
somebody
I'd
want
to
hear
what
the
group
is.
Gonna
say
because
it's
at
that
point
that
we'll
understand
you
know
who,
in
the
project
we
might
want
to
sort
of
convince
I,
don't
want
to
you
know
I,
certainly
don't
want
to
say
to
anybody,
don't
come
just
in
terms
of
actively
going
to
find
additional
attendees.
C
D
I'd
also
like
to
kind
of
cycle-
or
you
know,
turn
back
a
little
bit
and
refocus
what
I
reek
lair
by
what
I
said
earlier.
I,
don't
think
we
should
exclude
people
who
have
been
participating
in
this
kind
of
discussion
in
the
best
I
just
want
to
make
sure
we're
not
only
including
them
like
they're,
not
our
central
people,
that
we're
having
in
this
discussion
and
that
we're
actually
going
and
getting
people
that
are
users
that
haven't
participated.
In
addition
to
those
people
who
have
already
participated
that
these
discussions.
C
C
C
Cuz
I
can
kind
of
leave
it
at
data.
You
know
that
that
way,
if
anybody
who's
got
an
interest
in
truth,
they
hopefully
show
up
and
then
after,
if
if
we
you
know
once
we
see
what
the
conversation
has
and
what
the
kind
of
issues
or
you
know
where
the
conversation
goes,
we
can
be
more
active
to
see.
You
know
we
say:
oh
well,
this
person
I
know
does
work
in
that
area.
That
kind
of
thing.
C
C
That
and
that's
been
now
folded
into
that
group
and
I
think
you
know
that's
where
anything
around
that
area.
We
would
want
to
pull
them
in
so
so,
for
example,
if
the
you
know,
if
there's
she
went
with
the
the
tooling
or
provider
said
well,
you
know
you
really
make
it
there
like
with
you
know,
to
support
multiple
languages
and
stuff.
C
D
D
D
C
It's
interesting
in
that.
Well,
we
just
created
a
team
called
delivery
channels,
so
this
I
would
almost
like
and
I
could
be
completely
wrong
here.
But
initial
thought
is
a
different
group
of
end-users
they're
they're,
a
group
who
take
node
and
either
bundle
it
into
their
product
and
deliver
it
that
way
or
they
repackage
know.
Like
the
you
know,
the
some
of
the
installers
or
they
help
you
install
it.
What
p.m.
D
C
D
C
So
I
can
almost
us
having
you
know
that
being
another
end-user
group
that
we
could
you
know
having
it
happen,
you
know
having
in
the
list.
It's
just
a
matter
of
how
many
groups
do
you
want
and
how
big
they
should
be
and
do
you
want,
or
do
you
want
to
combine
like
things
in
again,
I
don't
know
off.
The
top
of
my
head,
if,
like
electron,
will
have
similar
concerns
to
MOCA,
for
example,
yeah,
but.
A
C
What
I
mean
the
history
behind
that?
Was
we
there's
a
refactoring
of
our
teams
within
no
GS
right
and
there
used
to
be
people
who
were
in
some
teams
or
the
overall
team
like
we
used
to
have
like
just
a
members,
we
refactored
they
got
dropped
it,
so
they
were
no
longer
on
any
team
or,
and
so
the
discussion
actually
happened
in
two
different
places.
One
was
sort
of
around
people
who
were
repackaging,
node
and
say
the
distribution
distributors.
C
Like
you
know,
the
Linux
is
who
we
used
to
be
node
electron
was
another
discussion
became
and
so
distribution
channels.
Kit
was
basically
the
best
name,
I
could
think
of
that
covered
all
of
it,
and
it's
just
an
aim.
So
it's
a
matter
of
like
if
we
do
something
that
we
think
affects
the
packaging
of
node
or
the
consuming
of
node
as
a
shared
library
like
electron,
does
or
anything
that
sort
of
affects
the
people
who
use
know
like
deliver
node
to
their
end
customers
in
some
way,
so
be
it
by.
You
know
an.
C
You
know
funneling
distributing
like
in
your
distribution,
it's
just
a
team,
we
cannot
mention
to
say,
hey
we're
doing
this.
Does
that
you
have
any
concerns.
This
is
gonna
affect
you
negatively,
that
kind
of
stuff,
and
so
now
there's
you
know
in
those
issues
we
had
an
initial
set
of
people.
We
should
probably
actually
publicize
it
a
little
bit.
B
C
C
D
C
A
C
I
think
that
one's
interesting
I
would
leave
it
to
the
end.
My
suggestion
is,
like
everybody
introduce
themselves
and
then
I
think
we
give
it
a
sort
of
an
open-floor
to
Chris
and
the
rest
of
the
people
to
kind
of
say.
Well,
what
are
the
kind
of
things
you'd
like
to
talk
about
and
then
and
then
at
the
end
we
can
say.
Oh
and
one
thing
we
know
from
the
node
community
side
that
we
are
interested
in
feedback
on.
Is
that
particular
one,
because
you
know
we've
taken
a
decision.
C
C
B
B
And,
and
if
you
have
any
like
specific
questions
that
you
want
to
ask
I
mean
I,
don't
know
it
seemed
like
at
index
Dan,
you
had
a
set
of
questions
you
wanted
to
ask.
So
if
you
have
anything
like
that,
we'd
love
to
know
about
them
ahead
of
time.
Also
on
the
on
the
buffer
thing,
you
know,
I
don't
feel
like
that
is
any
more
or
less
important
than
anything
else.
Necessarily
I
know
you
know:
I
I,
don't
use
buffer
very
much
unless
buffer
for
me
comes
into
play.
C
The
only
thing
there
would
be
it
could
be
as
simple
as
like.
Are
you
guys
worried
about
it?
No,
okay,
move
on
okay.
It
would
give
us
a
little
bit
of
validation
that
you
know
some
small
subset
of
the
module
owners
out.
There
really
are
not
bothered
versus
if
half
the
people
yell
up
and
down
saying
yeah
I.
Really
don't
like
that.
That's
you
know
it's!
It's
just
one
more
place
to
get
a
little
bit
of
feedback
on
that
on
that
one,
and
we
doesn't
need
to
take
very
much
time
at
all
necessarily
and.
B
C
C
I
I
think
it's
yeah,
the
I
would
mine
my
suggestions.
We
just
have
it
on
agenda
and
it
says
like
is
this
anything
that
you
guys
are
worried
and
want
to
talk
about
and
if
the
answer's,
no
we
move
on,
does
that's
basically
the
answer
sure,
and
if
there
is
a
discussion,
if
people
do
want
to
discuss
it,
then
you
know
it's
but
it
but
yeah.
So
that's
all
I'd
suggest
we
could
come
up
with
some.
Like
generic
questions
in
terms
of
you
know,
my
questions
would
be.
C
C
B
B
A
C
You
know
it's
it's
it's
I,
don't
have
any
specific
things
that
are
like
other
than
you
know,
the
that
yeah
I
don't
have
any
other
specific
things,
but
it's
more
about
sort
of
teasing
out.
Are
there
any
pain,
points
or
other
things
that
we
should
be
aware
of
going
forward
so
that
you
know
we
have
enough
knowledge
to
understand
how
we
might
affect
that
that
end
user
group
and
and
at
least
be
you
know
aware
of
it
when
we
do
things
yeah.
D
Chris
I'd
like
to
ask
if,
like
I,
could
just
like
DM
you
or
something
after
we're
done
here.
Just
so
I
I
can
make
sure
like
we're,
not
crossing
streams,
because
I
think
we're
talking
about
similar
groups
of
people
to
reach
out
to
so
I.
Just
wanna
make
sure
like
I'm,
not
creating
extra
turn
on
inviting
people
in
and
stuff.
C
That's
a
good
one
right.
We
could
write
some
of
those
down
in
the
agenda
if
we
want,
but
that's
kind
of
the
flavor
of
what
I
would
come
up
with
on
the
spot
and
then
yeah,
if
you,
if
you
guys,
come
with
a
particular
set
that
they
want
to
discuss.
That
will
give
us
some
more
concrete
things
to
talk
about
in
the
meeting.
Otherwise,
you
know
I
think
for
a
first
meeting.
C
B
B
C
D
A
So
do
you
think
would
be
constructive
to
do
you
have
a
broad
sort
of
opener
with
with
tooling
folks
just
to
get
you
know
set
a
baseline
with
like
describe
how
your
tooling
leverages
nodejs
I,
know.
That
would
be
interesting
to
me
personally,
but
I'm
not
sure
that
its
context
that
that's
relevant
to
the
broader
group
I.
C
Think
you
kind
of
got
a
I
think
that
what
sorry
I'll,
let
Chris
answer
too
but
I
think
it's
interesting
because
it's
kind
of
hard
to
understand
each
other.
If
we
don't
understand
what
the
modules
doing
and
what
you
know,
I
mean
some
of
them,
probably
like
NPM.
We
understand
pretty
well
right,
but
others
may
not
be
as
obvious
to
people
what
the
relationship
is:
an
innovation
dependence
all
that
kind
of
stuff
yeah.
A
C
It
does
well
what
it
does
make
me
think
of
is
like
every
meeting,
maybe
could
benefit
from
a
what's
new.
In
terms
of
you
know,
our
other
modules
planning
something
new
that
they
think
might
affect
noted.
Vice
versa,
right
like
because
it's
not
necessarily
a
one-time
thing
right.
You're,
like
you
know,
NPM,
is
introducing
something
new
hearing
about
that
upfront
and
it
won't,
you
know,
won't
just
be
the
people
in
the
meeting.
It's
whoever
else
wants
to
watch
the
meeting
afterwards
and
if
there's
something
particularly
interesting,
that
comes
out
of
that
we
can.
C
B
A
B
Yeah
it's
it's
like.
You
know
that
they're
traditionally
javascript
has
not
been
a
scripting
language
that
you
know.
People
are
gonna
reach
for
Python
or
whatever,
or
why
using
javascript
and
node
when,
when
you
could
have
done
this
with
a
shell
script
or
something
like
that,
yeah
I
think
that
might
be
kind
of
a
good
one
to
at
least
I
feel
like.
It
would
be
helpful
for
some
people
to
hear
the
answer.
C
B
Yeah
yeah
I
mean
yeah,
so
I
think
that
that
might
be
a
good
one.
Just
to
just
think
can
I
get
some
more
context.
I
feel
like
you,
it's
like.
Why
would
you
know
why
would
you
write
the
in
JavaScript
I
have
seen
not
necessarily
from
from
node
core
anything
like
that,
but
just
kind
of
this
general
sentiment
about
from
from
many
about
you
know:
what's
what?
Why
would?
Why
would
why
the
hell'd
you
want
to
do
that.
G
D
Their
projects
I
mean
you
know,
mocha
is
one
of
the
projects
and
so
is
webpack,
but
that's
probably
something
that
would
be
a
good
way
to
get.
You
know
this
is
basically
a
collected
list
of
people
who
are
already
doing
this
exactly
what
we're
talking
about
so
that'd
probably
be
a
nice
benefit.
There
yeah.
B
A
A
A
A
A
D
A
A
A
Okay,
so
that's
that's
the
big
rock,
then
I
have
request
from
me.
Hi
and
I've
heard
a
request
from
a
couple
of
the
folks
to
to
gather
the
enterprise.
You
know
some
of
the
representatives
from
the
enterprise
advisory
group
and
I'm
thinking
that
you
know
the
discussion
topic
or
one
of
the
main
discussion
topics
of
the
subsequent
meeting
so
a
month
from
now
right,
two
weeks,
two
weeks
from
now
sure
we
should,
you
know,
focus
on
that
see
where
that
is,
and
you
know
either
making
decision
one
way
or
the
other.
A
C
Got
the
tooling
end-users
we're
talking
to
you?
Could
you
know
delivery
channels
could
be
a
potential
another
one
and
the
enterprise
you
know,
maybe
the
name
right,
the
enterprise
advisory
or
not
to
something
like
you
know,
the
large
enterprises
order.
You
know
find
something
like
that
and
then
it
might
fit
my
quite
nicely
into
it
into
this
right.
C
And
you
know
in
that
case
like
because
yeah
I'm
not
sure
that
the
sort
of
run
out
of
steam
it's
just
we
haven't.
Quite
we
were
stuck
on
a
few
other
things
and
if
we
just
sort
of
get
past
that-
and
you
know
that
the
people
associations,
then
in
the
way
of
them
getting
together
and
having
these
things-
I,
don't
know.
You
know
as
long
as
the
same
kind
of
discussions
that
we're
having
now
makes
sense
right.
What.
A
B
C
E
Here
so
don't
you
think
it's
kind
of
mixed
so
we'll
have
the
public
the
tooling
session
in
two
weeks,
and
then
you
want
to
talk
about
the
enterprise
advisory
Gras
group.
Isn't
that
kind
of
mix
a
little
bit
mix-up?
Don't
you
want
us
to
come
earlier,
probably
to
meet
again
guys,
I
mean
what
I'm
thinking
is
to
put
a
meeting
for
ask
for
feedback
between
these
two
okay.
E
I'm,
probably
yeah
he's
just
like
somehow
they
are
mixed,
so
we
want
tooling,
then
in
two
weeks
again
we
want
something.
Yes,
this
is
somehow
mixed.
At
least
we
should
put
a
base
somewhere
so
just
or
or
I
proposed
meeting
or
probably
I
proposed
to
go
with
the
advisory
group,
maybe
delay
later
by
the
end
of
April.
C
What
I
think
would
put
actually
Dan
would
suggest,
maybe
that
it
was
like
we
have
the
public
feedback
session.
It's
two
weeks
from
now,
so
in
the
next
two
weeks
later
is
actually
just
a
planning
session,
and
then
it
would
be
two
weeks
later
that
we
would
probably
have
the
Enterprise
advisory
session
yeah.
A
Right
I
think
we're
aligned
there.
The
you
know,
the
only
thing
that
we
may
need
to
do
is
just
you
know,
riffing
on
what
my
high
saying
there
is,
and
we
probably
have
enough
space
in
our
meeting
to
do
this.
We
probably
oughta
you
know
in
that
subsequent
meeting.
You
know,
make
sure
we
make
time
to
you
know
digests,
together
the
user
feedback
session,
let's
breathe.
A
Cool
yeah,
that's
a
good
point,
yeah
great!
Well!
You
know
thanks
Chris
firmer,
you
know,
kicking
this
off
and
and
bringing
this
to
user
feedback
and
really
looking
forward
to
to
doing
this
session.
You
know
gotten
a
lot
of
great
results
from
you
know
just
having
this,
this
open,
dialog
and
you
know
looking
forward
to
sharing
that
with
everybody.