►
From YouTube: Node.js User Feedback Initiative Meeting
Description
B
My
goodness,
alright,
so
we're
off
and
welcome
to
the
user
feedback
initiative.
Today
we
have
a
team
meeting,
we're
going
to
be
revisiting
the
enterprise
enterprise
use
case.
You
know
that
there
was
a
request
by
some
folks
to
to
gather
together.
You
know
this,
this
enterprise
advisory
group-
and
you
know
a
little
bit
of
back
and
forth
on.
B
You-
know
the
Charter,
how
it's
going,
what
not,
how
we,
how
we
align
that
interaction
flow
with
the
know,
Jess,
you
know
meeting
model
which
is
to
meet
the
public,
and
you
know
you
continue
to
evaluate
that.
You
might
one
of
my
stated
goals
in
getting
this
user
feedback
group.
It
was
really
to
share
my
experience
with
you
know,
end
users
in
the
enterprise
and
it
bring
that
context
to
the
TSC
and
calm
calm,
because
you
know
folks
on
that.
You
know
this
star,
tip
and
other
things.
B
A
lot
of
the
enterprise
expectations,
especially
as
you
get
outside
of
technologies,
is
that
you're
using
technology
or
focusing
that
technology
on
the
delivery
of
business
value
and
the
norms
in
the
norms
in
open
source
is,
you
know
is,
is
is
almost
a
challenge
for
enterprise
users.
So
you
know
as
much
as
we
can
build
bridges
and
provide
forums
for
that
feedback.
I.
Think
the
you
know,
the
the
node.js
project
will
grow,
learn
a
lot
and
we've
already
learned
a
lot
in
our
engagement
with
with
end
users
and
we've
learned
a
lot
with.
B
You
know
our
engagement
with
the
the
folks
in
tooling
and
we
had
a
brief
foray
at
editing
index
where
we
got
to
hear
a
little
bit
of
one
big
in
fresh
user
Walmart,
and
so
we've
learned
a
lot.
You
know
and
we
we
have
yet
to
establish
a
cadence
so
yeah
on
the
27th,
so
April
27th
we're
on
a
bi-weekly
schedule.
We
are
scheduled
to
have
a
public
feedback
forum
on
that.
B
So
you
know
first,
then,
a
call
to
action
for
everyone
in
user
feedback
and
around
that
to
to
reach
out-
and
you
know,
engage
we
and
we
need
our
usual
representatives,
not
the
usual
people,
but
our
from
the
various
projects
inside
of
nodejs.
So
calm
calm,
you
know,
Mike,
there
are
chairs,
we
have
our
chairs
here,
represented
so
Tierney
and
Michael.
You
know
an
explicit
ass
to
both
of
you
to
seek
out
and
you'll
find
representatives
in
the
community
committee
and
the
TSC.
B
Hopefully
we
can
change
that
up
and
you
know
bring
some.
You
know
diverse
perspectives
that
are
going
to
be
representing
there.
You
know
beyond
yourselves,
you
all
do
a
great
job,
but
you
know
one
of
our
stated
goals
with
the
user
feedback
is
to
to
provide
that
perspective,
and
you
know
I
think
you've
both
seen
the
benefit
in
these
sessions,
of
how
how
how
useful
it
is
to
hear
that
perspectives.
D
D
C
D
B
Is
accurate
that
is
accurate,
so
my
intention
is
to
invite
everybody
in
the
enterprise
advisor
group
to
participate
in
an
end-user
session.
The
reason
being
is
this
model
is
working,
the
user
feedback
initiative
is
working,
we
do,
and
you
know
we
members
of
the
calm,
calm
and
feedback
from
the
TSE.
Everybody
seems
to
be
really
happy
with
this
model,
and
you
know
we
already
have
the
tooling
group,
which
is
you
know,
building
its
own
momentum
in
being
a
repeated
session
there.
B
So
you
know,
since
that,
an
enterprise
advisory
group,
it
really
hasn't-
had
the
name
of
the
championing,
and
you
know
the
right
forum.
What
I
want
to
do
is
test
with
that
group.
It'll
come
to
this
forum,
and
you
know
this
is
this
is
working
for
me
in
terms
of
facilitating
in
terms
of
good
use
of
my
time
you
know:
is
this
model
going
to
work?
C
B
You
know
it
may
turn
out
that
we
do
end
up
having
a
more
private
discussion
space.
For
you
know
an
enterprise
user
after
we've
gone
through
built
trust
in
the
community.
You
know
I'm
open
to
exploring
the
right
forum
for
the
enterprise
use
case
to
you
know.
Just
like
you
know,
we
have
you
know
the
tooling
I,
don't
expect
them
to
live
forever
inside
of
the
user
feedback.
A
group,
though,
will
always
be
a
forum
for
for
feedback
yeah.
My
hope
in
you
know
engaging
feedback.
B
C
A
C
They
form
their
own
group
and
direction
and
in
fact
you
know
they
have
somebody
who's,
champing
and
leading
it.
Maybe
it
still
makes
sense
to
have
them
sort
of
listed
under
user
user
feedback,
but
I
could
easily
hope
to
I
can
easily
see
and
hope,
like
you
do,
that
you
know
we'll
end
up
with
enough
groups
that
those
groups,
you
know
it'll,
be
two.
E
D
So
I,
you
know
I'm
very
happy
with
that
approach.
What
we're
doing
that's
it
I
would
like
to
ask:
how
do
we
go
about
the
enterprise
advisory
working
group
repo
and
back
like
the
proposal
there,
because
that's
stalled
for
months
now
and
I
have
gotten
questions
about
it?
I
mean
try
to
follow
up
on
it
and
get
you
know,
get
a
status,
but
I
haven't
been
able
to
do
that.
So
what
do
we
need
to
do
with
that?
And
how
does
this
supersede
that
I
think
that's
what
I'm
looking
for
or
should
we
I
think.
C
B
B
Rather
than
asking
folks
to
come
back
or
it
was
going
away,
you
know
what
we
could
do
is
say
all
right.
We've
gone
through
this
public
session
here
you
know
we
and
we've.
Given
everybody
in
that
enterprise
advisor
group
visibility
into
how
we're
doing
things
in
the
user
feedback
initiative,
then
you
know
III
feel
like
it
it.
It
probably
means
you
know
some
private
discussion
and
you
know,
even
though
you
know
this
was
a
lot
of
the
enterprise
advisory
group
was
done
on
behalf
of
the
group,
not
by
the
group.
B
F
Because
we
land
it
so
what
I'm
rising
to
you
guys
it's
about
that
time.
So
last
time
we
had
like
about
an
hour
and
15
minutes,
and
usually
people
are
aware
about
that.
If,
if
we're
my
proposal,
if
we
are
more
than
ten
people
in
the
beginning
as
a
organizer,
if
we
can
get
an
extension
for
15
or
20
minutes
more
entering
from
the
beginning,
I
think
the
people
will
appreciate
that
yeah.
E
F
B
So
what
I'm
proposing
for
for
the
private
session
is
that
it
would
be.
You
know
an
extra
15
minutes,
half
an
hour
afterwards.
I,
don't
know
that
I
think
we
better
served
in
the
public
session.
Just
limiting
ourselves
and
I
actually
have
a
proposal
that
I
that
I've
posted
before
the
meeting
to
you
know
try
to
keep
our
discussion
questions
that
we
actually
go
through
as
limited
as
possible.
B
D
Think,
like
I
said
at
that
meeting
as
well
timeboxing
and
then
having
people
let
themselves
rather
than
going
through
everyone.
Okay,
it's
probably
a
good
way
to
do
that,
just
because
having
self-selection
you
know,
people
might
be
more
have
more
to
say
on
one
thing
like
one
specific
topic
than
another
and
those
that
we
want
to
definitely
make
sure
we're
hearing
the
people
who
have
something
that
they
really
want
to
passionately
say
and
if
you
know
it's
more
of
a
no,
but
you
know:
I
have
a
little
bit
of
comment.
D
I
feel
like
people
feel
obligated
to
say
something
when
they
have
when
we're
going
through
everyone.
My
impression
was
that
several
people
felt
obligated
to
have
some
statement
and
they
didn't
necessarily
have
one
that
they
were
super
passionate
about,
but
they
felt
obligated
to
fill
that
time,
and
so
that's
that's
more
of
my
concern
is
making
sure
we
we
cover
all
the
subjects
and
making
sure
we
get
the
people
who
are.
We
hear
everyone's
opinions
on
the
things
that
they're
passionate
about
the
things
that
they
care
about
most
so.
B
You
know
the
counterpoint
to
that
journey.
Is
you
often
will
get
the
most
aggressive
voices
I'm
happy
I've
learned
how
to
to
power
through
a
meeting
and
I
can
be
louder
than
anybody,
and
you
know
so
I'm
I'm
personally
self-conscious
about
you
know
being
able
to
pave
over
other
folks
in
in
the
discussion
like
that,
and
my
worry
is,
you
know
folks
may
not
be
familiar.
We
have
the
you're
raising
hands
a
couple
of
things
that
we
could
model.
B
You
know
I'd
be
willing
to
to
try
that,
but
I
also
do
want
to
make
sure
that
we
do
encourage
some
of
the
folks
that
you
know
already
selected
they
they
know
by
participating.
They
believe
that
they
have
something
meaningful
to
contribute
to
the
these
sessions,
and
you
know
oftentimes.
It's
from
the
under
heard
voices
that
you
you'll
really
kick
off
some
of
the
they
are
the
most
interesting
discussions.
B
You
know
where
you
know
everyone's
it
gets
into
like
you
know,
vibing
on
the
cool
thing
and
you
know
get
someone
that
you
know
kind
of
lobs
out
a
contrarian
viewpoint,
and
you
really,
you
know,
dig
into
that.
Yeah
I
think
one
example
of
that
from
the
last
public
session
was
you
know
where
we,
where
we
were
able
to
get
into
the
the
bundlers
the
boomers,
the
integrators
Michael.
You
have
a
an
issue
and
a
proposal
around
this.
What
is
that
the.
B
D
B
D
And
so
you
know
having
so
many
people
in
the
group.
A
lot
of
people
have
a
lot
of
strong
opinions
and
it's
a
very
technical
issue
and
the
way
that
miles
Boren's
has
been
driving.
That
is,
through
the
raised
hand,
functionality
and
zoom,
and
that
does
really
seem
to
be
effective
because
it
does
allow
people
to
kind
of
raise
hand
while
passively
and
that's
not
necessarily
they
can
choose
whether
they
want
to
speak
or
not.
D
When
they're
selected,
the
hard
part
really
seems
to
be
moderating,
it
mediating
it
rather
and
making
sure
you're
hitting
all
everyone
since
yeah.
It
seems
not
easy,
but
I
do
think.
That's
I
I,
don't
definitely
don't
a
force
that,
on
this
group,
like
I
just
should
be
a
consensus
thing,
but
I
definitely
think
that
would
be
a
good
kind
of
intermediary.
Step
or
kind
of
compromised
is
to
write
one.
C
Thing
if
we
don't
like
so
if
we
don't
have
an
actual
enough
time
to
hear
from
everybody,
then
we're
not
going
to
hear
from
some
people.
So
I'm,
just
thinking
of
ways
to
sort
of
like
tyranny
was
saying,
walk
down.
The
middle
I
mean
we
could
ask
people
to
raise
hands
and
if
that
works
out
great,
if
it
doesn't
I
still
think
it's
reasonable
for
Dan
to
try
and
pull
out
some
of
the
people
who
aren't
talking,
we
don't
but
the
flipside
might
be.
C
D
I
think
that's
that's
one
thing
I
know
dan
is
good
at
is
selecting
people
and
pulling
them
into
a
discussion
and
I
think
like.
If
we
recognize
like
I,
can
you
know
message
Dan
or
something
and
say
hey
this
person
might
not
have
been
talking,
I
think
they
might
have
something?
Well,
you
will
say
here
or
they
just
haven't
been
talking
at
all.
We
should
like
reach
out
to
them.
Say:
hey,
you
know
Raphael.
What
do
you
think
so
I'm
totally
picking
on
you
here
I
feel.
D
But,
like
you
know,
that's
that's
the
type
of
thing.
That's
the
type
of
thing
that
I
think
we
could
kind
of
have
that
mill
ground
of
like
okay
get
the
voices
who
are
active
are
passionate,
but
also
make
sure
we're
pulling
in
those
people
who
aren't
necessarily
engaged
in
making
sure
we're
engaging
them
actively.
C
So
I
don't
know
if
it's
sort
of
like
saying
here's
our
time
box
for
the
question
you
know
we're
not
going
to
get
everybody.
So
please
put
up
your
hand
if
you
have
something
you
want
to
contribute.
If
we
get
to
the
point
where
it's
only
the
same
people,
you
know
I
think
we
could
say
well,
let
wait
a
sec.
We
haven't
heard
from
a
few,
the
other
people,
if
we,
but
if
we
run
out
of
time,
there's
no
expectation
so
that
we
haven't
left
people
out
or
anything
haven't
gone
through
the
SAP
mix.
B
B
D
C
Of
think,
though,
that
like
in
my
mind,
the
model
would
be
the
first
meeting
of
a
particular
group.
We
need
to
get
everybody
introduced
and
you
know
in
theory
these
are
not
one
meeting
right.
So
the
first
meeting
we
need
to
do
that.
Everybody
gets
to
know
each
other
a
little
bit
the
next
meetings.
We
wouldn't
do
that.
Maybe
if
there's
somebody's
new,
that's
joined,
we
could
say:
hey
you're
new
to
the
group.
Can
you
introduce
yourselves
not
that?
Would
that
would
be
the
way
I?
C
Would
you
know
I
think
it's
valuable
enough
that
you
need
to
do
it
at
least
once
because
you
got
to
have
a
Content,
some
context
for
people
yep
and
then
on
the
follow-on
ones.
It
would
be
like
yeah.
No,
we
don't
reintroduce
ourselves
this
were
we
already
did
that,
let's
we're
doing
our
second
meeting.
So,
let's
get
directly
to
whatever
the
agenda
is
right.
B
So
how
do
folks
feel
about
me
combining
that
everybody
introduced
themselves,
or
especially
everybody
in
you,
know
the
enterprise,
your
representatives,
introducing
themselves
together
with
you,
describe
your
your
use
case
kind
of
do
what
looks
for
me
one
only
one
time
where
it's
all
the
way
around.
You
know
that
the
group,
and
then
from
there
it's
it's
opt-in,
I,
think.
C
A
D
B
D
A
C
D
F
B
Plus
one
of
that
yeah
and
I
think
that'll
be
easier
for
us.
You
know
kind
of
you
know
the
readme
is
our.
You
know
overall
overview
for
the
world,
and
you
know
the
public
sessions
are
important,
but
you
know
not
everything
that
we
we
do
and
so
yeah
I
think
we'll
be
able
to
sort
of
collaborate
on
it.
Work
on
it.
Iterate
on
the
process.
You
know
in
an
independent
document,
you
can
link
off
our
readme
for
folks
that
are
interested
in
the
workings
of
how
we.
B
Alright,
so
continuing
the
discussion
around
you
know
the
the
topics
for
for
the
discussion.
You
know
I
I
kind
of
took
the
one,
the
one
question
that
I
asked
and
a
tolling
team.
You
know
that
went
a
little
bit
deeper
than
you
know
describe
what's
going
on
and
you
know
took.
That
is
the
the
second,
the
second
topic.
What's
working
and
I
condensed,
what's
working?
What's
not
you
know
down
into
single
one
to
give
folks
the
opportunity
to
you
know
go
either
direction
right.
There
was
there's
some.
B
You
know
feedback
a
little
bit
of
pushback
on
focusing
only
on
the
negative
if
folks
wanted
to
share
their
passion
and
and
excitement
of.
What's
going
on,
not
just
you
know,
kibbutz
so
I
that
that's
what
I've
put
forth
as
a
proposal
for
you
know
our
primary
the
primary
meat
of
of
our
topic
there.
What,
if
folks
think
about
that
right.
C
E
Great
great
sorry,.
B
B
So
you
know
one
thing
that
we
haven't
done
yet
in
any
of
our
sessions
is
sort
of
communicate
back.
You
know,
you
know,
having
some,
you
know,
calm,
calm
or
TSC
messaging
there.
There
is
an
interesting
opportunity
and
something
that
that
this
group,
you
know,
could
be
interested
in
hearing
if
we
think
we
can
fit
it
in
terms
of
time.
The
work
of
the
Diagnostics
working
group
in
the
end,
the
diagnostic
summit
and
the
prioritization
of
those
efforts,
are,
you
know,
keen
points
of
interest
for
enterprise
users.
Do
we
want
to
try
to
fit
in?
C
Love
to
get
that
feedback,
I,
don't
know
if
it'll
fit
in
that
won't
that's
my
only
thing
like
I
think
by
the
time
you
go
around
the
table
with
the
first
part,
you're
already
gonna
ask
people
that
stick
around
afterwards
as
well
right
right,
but
what
I
you
know,
I
think
what
we
do
need
to
do
and
some
of
the
things
I
put
on
the
agenda
for
this
issue
is:
we've
got
to
start
scheduling
the
next
meetings
mm-hmm
for
each
of
these
groups,
so,
like
I
could
say
you
know.
I
could
see
this
saying!
C
Well,
you
know
we
met,
but
now
what's
the
next
step,
what
are
the
concrete
actions
and
I
think
having
gotten
through
the
first
meeting,
where
they're
sort
of
getting
to
know
each
other
in
the
cons?
The
second
one
would
be
okay.
Now?
What
do
we
want
to
try
and
accomplish?
Let's
make
some
concrete
things
and
in
the
in
the
enterprise
one,
you
know,
one
of
the
suggestions
could
be
well
like.
Let's
look
at
the
diagnostic
side
and-
and
we
believe
that
that's
something
important
to
the
enterprise
use
case-
can
we
get
some?
B
And
you
know:
enterprise
users,
love
love
timelines,
and
you
know
one
thing
that
we
could
definitely
benefit
from
is
to
be
able
to
articulate
when
we
would
be
able
to
come
back
with
the
next
session.
So
that's
that's
probably
a
great
thing
for
us
to
align
around
before
we
wrap
today
on
when
we
could
potentially
reconvene
that
group
well
I.
You
know
I
feel
like
with
that.
We
can
you
move
on.
B
Basically,
you
know
call
to
action
to
everyone
here
and
you
know:
calm,
calm
and
TSE
invite
members
to
come
and
participate,
and
you
know
everyone
is
who's
here.
That
has
contacts
me
high,
Intel,
michael
IBM,
Tierney,
note
source.
You
know
Chris
IBM,
Raphael,
anybody,
you
know
Enterprise,
you
that
you
feel
like
would
benefit
from
coming.
Send
them
to
this
issue,
issue
52
and
ask
them
to
raise
their
hands.
Participate.
B
I'm
generally
inclined
to
not
limit
numbers
just
to
make
the
the
invite
as
broad
as
possible,
and
you
know,
adapt
from
there
I.
Don't
it
gets
to
preferential
if
if
we
agreed
the
other
way
around,
but
you
know
we
have
gotten
feedback
that
you
know
tan
is
you
know
you
know
getting
going
through?
All
this
discussion
tends
about
a
limit,
so
we
we,
we
might
have
to
make
decisions
on
yeah.
D
B
A
D
C
B
B
B
C
I
guess
those
two
it's
like
yeah:
what
do
we
do?
We
had
that
we
had
the
greet
meeting.
We
had
a
little
bit
of
discussion.
I
almost
think
we
need
to
say:
okay,
let's
schedule
the
next
meeting,
and
in
that
meeting,
it's
like
together
as
a
group,
form
the
what
are
the
priorities
that
we
want
to
work
on
right,
because
it's
a
bit
hard
in
the
initial
meeting
to
get
to
that
point.
We
spent
most
of
it
talking
about
generalities.
It's
like
okay,
we've
now
shared
a
bit
as
this.
You
know
as
that
group.
D
Good
way
for
us
to
prioritize
what
other
working
groups
and
teams
need
to
get
involved
with
what
what
other
working
groups
of
teams
we
should
invite
to
this
meeting,
like
you
know,
if
Diagnostics
are
super
important
to
the
enterprise
nodejs,
which
they
are,
and
we
get
that
feedback
cool,
we'll
start
and
we'll
send
out
an
invitation
to
the
Diagnostics
working
group.
If
it
turns
out.
Oh,
we
actually
also
really
can't
care
about
modules.
D
C
Very
good
Samaritans
yeah,
like
it's
one
of
the
things
it's
sort
of
like
what
are
the
next
things
to
work
at
and
I,
guess
and
explicitly
like
you
just
did
call
out
what
other
areas
of
the
project
do.
We
need
to
connect
you
with
and
make
sure
we
get
the
conference
like
to
be
successful.
Where
do
you
think
you
need
to
be
better
connected
and
what
can
we
do
to
make
that
happen
and.
B
Months
right,
you
know
unless
and
unless
we
go
to
a
more
frequent
schedule,
which
is
you
know
not
another
realm
of
possibility,
I
would
I
personally
would
love
to
to
see
the
mentorship
initiative
get
a
little
bit
more
seen
before
I
consider
committing
to
a
weekly
schedule
for
this,
but
I'm
totally
open
to
you
know
you're
having
other
people
facilitate,
and
you
know
expanding
this
team,
so
we
can
go.
Do
this,
we
can
get
there.
B
So
you
know
it
seems
like
an
issue.
Maybe
isn't
enough,
do
we
need
it's
similar
to
what
we're
doing
and
putting
down
the
process?
Do
we
need
to
begin
to?
You
know
capture
some
of
those
interest
areas
for
these
groups
in
to
document
where
we're
keeping
a
public
record-
and
you
know,
beginning
to
navigate
through
some
of
those
key
points.
Yeah.
B
C
We
can
make
it
concrete
enough
that
says
you
know,
here's
an
issue
which
is
like
these
are
the
next
actions
or
next
important
things
for
this
group.
You
know
not
just
yeah
something
outside
the
issue
for
the
particular
meeting
starts
build
for
each
group,
a
set
of
dot.
You
know
one
or
more
issues
that
are
here,
the
things
that
we're
trying
to
push
forward.
Yes,.
D
B
We
gave
everybody,
you
know
a
an
ongoing
log
where
we
over
captured
what
what
questions,
though
you
know
a
couple
of
details
that
we
could
put
in
there.
What
questions
we
got,
what
actions
we
came
out
of
and
just
you
know,
followed
the
log
and
you
know
we
wanted,
but
next
that
would
go
a
long
way
to
not
only
facilitating
what
we're
playing
in
the
future
but
being
good
record
of
what
we've
actually
accomplished,
which
you
know
yeah.
A
B
D
F
D
F
C
F
D
A
C
B
Yeah,
you
know
III
I'm
more
inclined
to
follow.
You
know
the
path
of
being
as
obvious
as
possible,
and
you
know
turning
suggestion
of
just
putting
it
in
the
top
level
of
the
repo.
You
know
right
now.
If
you
go
to
the
repo
you
know,
there's
there's
not
a
lot
of
depth
is
not
you
know
we're
not
competing
for
a
lot
of
yeah.
A
B
C
E
C
D
C
B
When
we
have
it
Leo,
we
have,
you
know
quite
a
few
more
than
three
active
hands
there
on
the
the
repo.
Yes,
oh
you
know,
I
I
think
we're
at
a
point
where
you're
landing
pr's
feedback
group
is
is
not
a
major
challenge
for
us.
It
is
nice
that
we'll
get
notifications
to
so
right
right
so
time
check.
We
have
ten
minutes.
I
want
to
make
sure
that
so
Timmy
had
this
session
about
values.
I
wanted
to
to
make
sure
we
got
yeah.
C
I'm,
a
bit
I'm
a
bit
like
I
I,
think
we
can't
I
don't
want
to
ignore
the
user.
The
general
one
in
terms
of
you
know
we
held
a
meeting
and
we
basically
let
it
drop
since
then,
like
I
can
agree
that
perhaps
you
know
if
one's
more
active
than
others,
we
should
schedule
more
meetings
for
one,
but
I
still
think
we
need
to
make
sure
it's
not
a
hey.
We
met
you
once
and
we
didn't
talk
again
so
like
at
this
point,
I'd
kind
of
propose
we
do
the
we
have
the
enterprise
next
week.
A
C
The
next
one
should
be
the
tooling
one,
and-
and
you
know
what
our
current
III
would
don't
think
we
necessarily
need
planning
ones
in
between
even
like.
So
that
could
be
like
you
know.
Next
week
is
the
the
enterprise,
then
two
weeks
after
that
is
the
general
and
then
two
weeks
after
that
is
the
tooling
one.
D
D
B
I
was
one
yes.
This
thing
I
agree
that
this
is
accomplished.
The
end
of
you
know
dealing
with
both
and
I'm.
Okay
with
that,
I
just
want
to
make
sure
we
have
the
the
forum
for
consensus
around
around
the
enterprise
advisor
group,
so
we
have
a
you
know,
there's
a
decision
point
that
we're
working
together
with
the
individuals
who
have
been
invited
to
the
enterprise
advisory
group
and
we've
said
that
we're
gonna,
you
know,
invite
those
folks
for
a
half
an
hour
after
the
the
user
feedback
session.
B
C
Terms
of
a
decision
if,
unless
the
the
enterprise
participants
disagree,
what
decision
needs
to
make
take
like
what
additional
decision-making
do
we
need?
Yeah
like
it
would
be?
If
my
feeling
is,
would
be
hey?
We
had
this
discussion
with
the
people
who
are
involved
the
enterprise
group.
They
you
know,
for
example,
they
they
think
that
yeah
I'm
folding
under
the
user
feedback
makes
sense.
So
unless
anybody
objects
we're
just
going
to
close
down
that
repo
move
forward
with
that
and
like
so
I,
don't
see
a
meeting
needed
for
that.
C
B
D
And
I:
don't
since
this
is
under
user
feedback,
I,
don't
think
there's
a
necessarily
need
to
move
it
up
to
the
compound
just
because
one
Enterprise
enterprise
advisory
groups,
I
forgot,
the
name
wasn't
ratified
like
it's,
not
natural
things,
so
there's
nothing
to
like
D
charter
D
initiative
and
then,
additionally,
if
you
know
the
user
feedback
group
is
making
decisions
to
do
that.
Do
you
work
themselves?
That's
fine!
I.
A
D
C
C
B
C
The
distribution
was
like
that
one
is
like
maybe
a
white
weight
to
you
till
we
get
to
that
in
agenda,
but
I'll
give
you
a
little
bit
more
context.
I!
Don't
see
that
as
something
that
we
need
to
be
as
active
like.
The
whole
group
needs
to
be
active
unless
we
want
to
be
like
I'm
anyway,
I'll
wait,
I'll,
stop
talking
and
wait
til
we
get
to
that.
But.
B
I
agree
to
transition
over
to
talking
about
that
I'm
comfortable,
so
that,
if
we
can
just
put,
you
know,
dates
to
those
sessions,
so
our
May
sessions
would
be
on
the
11th
and
the
25th,
and
so
we'd
have
general
users
on
the
May.
11Th
tooling
would
reconvene
on
the
25th,
and
you
know
we'll
work
asynchronously
in
the
issues
to
to
build
out
those
sessions
and
we'll
follow
our.
C
Yep
and
then,
like
you
know,
if
everything
works
out,
maybe
the
enterprise
one
or
the
enterprise
can
be
the
one
after
or
right,
like
you
know,
I
know
we're
not
leaving
this
place
to
get
together
and
talk,
so
we
may
want
to
squeeze
in
an
extra
meeting
or
something
but
I
think
we
can
sort
of
see
how
that
goes
right.
So.
D
B
Public
sessions
and-
and
you
know
everybody
here-
that
means
that
you
know
a
lot
of
attention
is
going
to
have
to
be
the
paid
to
doing
the
outreach
right.
You
know
the
most
challenging
things
that
we've
had
is
you're,
not
the
prioritizing
the
time
to
come
and
make
decisions
and
talk
about
it.
It's
the
amount
of
time
and
outrage
that
it
takes
to
go
and
and
make
sure
that
you
know
broad,
invites,
are
being
conveyed
and
folks
have
a
sense
of
what's
going
on
yeah.
C
C
So
so
it's
not
actually
like
distributions
is
actually
broader
than
what
I
was
trying
to
form.
This
group,
it's
basically
like
I've,
been
working
with
he
hung
on
support
for
shared
libraries
within
node
and
I
personally.
Feel
that,
like
being
able
to
embed
node
into
your
applications,
is
an
important
use
case.
C
You
know
people
like
electron
and
so
forth,
we're
getting
to
the
point
where
we'll
have
that
in
the
CIS,
at
least
to
it
to
a
limit
extent
where
it's
just
testing
like
the
core
node
tests,
and
the
next
major
thing
is
to
really
start
testing
the
use
cases
where
you've
done
the
embedding
and
they're
a
little
bit
different
right,
because
you
want
those
that
core
functionality
to
work
but
there's
also
tests.
There's
also
use
cases
that
are
specific
to
having
embedded
it.
How
do
you
start
scripts?
C
You
know
how
do
you
communicate
between
the
rest
of
your
application
and
the
node
runtime
stuff
like
that?
So
it
seems
like
a
good
time,
and
there
was
also
another
issue
open
where
some
I
think
some
students
that,
when
a
university
had
tried
extending
no
because
they
found
that
when
they
were
doing
the
embedding
there
was
things
missing
it's
it
seems
to
me.
It
would
be
a
great
time
if
we
can
get
some
people
interested
and
involved
in
defining
what
those
use
cases
are
like.
C
That's
what
I
see
the
modules
team
working
on
like
here's,
our
use
cases
and
from
that
you
can
drive
some
requirements.
So
what
I'm
hoping
to
get
is
find
interest
in
a
group
of
people
who
or
who
want
to
come
together
to
sort
of
document
those
use
cases
and
use
that
to
drive
requirements
and
at
least,
if
nothing
else,
for
the
testing
that
the
e
Hong
is
working
on
mom,
so
it
so
that
we
can
cover
those
in
the
node
testing
and
so
forth.
So.
E
C
I
I,
you
know,
debated
whether
I
should
just
open
an
issue
in
node
core
or
in
user
feedback
or
whatever,
but
I
just
figured.
You
know
node
core,
you,
you
click
on
the
link,
it
says.
Well
what
platform
are
you
on
whatever
it
just
didn't?
Give
me
the
initial
hey.
This
is
a
great
fit.
This
is
sort
of
a
meta
issue.
Kind
of
thing.
I
could
be
wrong
on
this,
but
I
figured
okay
well
use
your
feedback.
This
is
a
perfect
like
you
know.
C
It
fits
in
terms
of
we're
being
a
group
of
people
to
talk
about
a
particular
thing.
It
may
not
need
to
be
something
that,
like,
hopefully,
it
graduates
into
its
own
group
that
just
works
on
this,
and
so
it's
almost
my
ask
is
was
not
that
we
as
a
whole
group
start
driving.
It's
like
I'm
gonna
start
driving
this
under
under
and
I
opened
it
here.
If
everybody,
if
anybody's
interested
in
coming
but
I'm,
not
gonna,
necessarily
place
that
expectation
that
you
know
everybody
does
I'm,
just
gonna,
try
and
push
it.
C
B
C
I'm
I
wasn't
gonna,
that's
why
I
really
didn't
want
it
to
be
a
formal
thing.
Basically,
if
a
bunch
of
people
show
up
and
are
interested,
I
was
just
gonna
schedule,
a
meeting
on
my
own
outside
of
our
regular
schedule
and-
and
you
know,
get
them
together,
so
you'll
see
what
the
interest
was.
That
kind
of
stuff.
D
C
So
I,
just
I,
don't
know
like
you
know,
like
I,
said:
I
wasn't
exactly
sure
where
it
best
fit,
but
I
didn't
think
it
was
a
bad
thing
to
have
it
under
these
user
feedback,
and
you
know
if
it,
depending
on
the
the
interest
that's
shown
on
whatever
we
can
decide
what
to
do.
But
I'm
just
you
know,
happy
to
just
push
on
it
until
okay.
B
Well,
you
know,
don't
don't
let
you
know
me
be
a
limiting
factor
on
this
and
you
let
us
know
how
we
can
help
support
you
in
that,
and
you
know
like
it.
Like
I
said
you
know
the
earliest
that
I
I
think
we
could
get
into
our
regular
cadence
of
meetings
is
June
22nd.
So
if
you,
you
know
schedule
something
before
that.
Please
do
let
us
know
and
yeah.
C
I'll
likely
just
yeah
so
I,
don't
want
to
be
tied
to
the
the
sort
of
bigger
groups
were
like
I'm,
just
gonna,
try
and
see
what
kind
of
interest
I
can
get
going
and
I'll
schedule.
Whatever
meetings
that
I
can
get
people
to
come
to,
because
it's
something
that
I'm,
you
know
I'm
already
working
on
with
Yee
Hong.
So
it's
kind
of
a
logical
extension
of
saying:
okay,
let's
try
and
see
if
we
can
get
that
larger
feedback
and.
B
And
and
Christopher
you
know,
I
would
I
would
extend
that
to
yourself
as
well
right.
So
you
know
we're
beginning
to
see
the
cadence
of
what
this
team
can
can
do
to.
You
know.
Do
the
facilitation
of
the
tooling
group,
but
you
know,
if
there's
anything
in
the
interim
between
these
sessions,
that
we
can
help
facilitate
or
that
you
want
to
do
under
the
auspices
of
the
user
feedback.
I
would
love
to
help.
Make
that
happen,
and
you
know
not
be
I,
don't
want
to
be
the
gating
factor.
B
C
But
yeah
I
think
I.
Think
it's
a
valid
I
think
the
point
he's
making
is,
if
he
think
it's
useful
to
schedule
something
outside
the
schedule.
We
just
discussed
to
make
things
move
faster.
You
know,
feel
free
to
act
and
you
know
whoever
of
us
can
attend.
We
will
but
yeah,
don't
don't
make
it
that
the
process
or
anything
slows
things
down
artificially
and.
D
D
C
Yeah
I
mean
I
think
my
feeling
is
the
three
that
we
have,
or
probably
is
no
with
the
current
team
that
we
have
in
user
feedback
participating.
Now,
that's
probably
the
three
we're
gonna
need
to
focus
on
for
the
next
little
while
right,
like
I,
don't
have
others
that
and
even
if
I
had
others
I
think
it
would
dilute
it
a
little
bit
too
much
if
we
so
if
we,
but
so
so
other
people
that
are
watching
it's
like
hey,
we'll,
wait
a
second
there's
another
one.
C
B
A
A
What
what
what
is
needed
from
me
so
should
I
try
to
create
a
log
on
dot
MD
or
what
have
you
I'm,
not
sure,
exactly
what
that
should
look
like
I
know,
there's
there's
some
things
we
didn't
get
to
in
the
first
user
for
the
first
two
Ling
feedback,
meaning
that
we
would
have
wanted
to
get
to
so
I.
You
know
it
would
be
cool
to
write
those
things
down
somewhere,
but
yeah.
So
what
what
I
think.
B
B
D
C
C
D
B
It
great
well
look
forward
to
seeing
everybody
the
enterprise
session
and
bringing
that
you
know
that
initiative
around
the
enterprise
advisory
group
to
a
conclusion
and
yeah
I'm
real
excited
about
this
gauntlet
that
Dawson
has
sent
us
on
three
weeks
of
yep.
So
off
we
go
okay,
great
thanks.
Everybody
have.