►
From YouTube: Node.js User Feedback Initiative Meeting
Description
B
A
C
A
Carrying
forward
some
agenda
items
on
surveys-
and
you
know
last
time
we
had
a
bit
of
a
discussion
of
you
know
whether
or
not
we
should
sort
of
say,
there's
no
capacity
what
to
do,
and
she
has.
A
B
So
I
call
the
the
framework
that
I
was
trying
to
work
on
yeah,
so
I've
got
a
poor
quest,
I
believe
still
for
issue
templates
or
I
guess.
Maybe
one
issue
template
for
if
someone
wanted
to
create
an
issue
for
initiating
a
survey
and
it
tries
to
make
clear
the
expectations
from
the
outset,
you
know
what
what
what
they
would
need
to
do
to
follow
it
through
and
it
looks
like
Dan
just
posted
up
there.
Perhaps
you
know
and
it's
the
the
stuff
you'd
expect
you
know
who's
going
to
own
it.
B
What's
it
about
maybe
some
expectations
and
potentially
a
link
to
a
Google
Doc
to
it
to
work
through
the
questions
so
I
think
it's
a
good
starting
point
for
any
future.
B
Surveys,
I
also
have
been
trying
to
think
through
or
thinking
through,
whether
like
a
pull
request.
Template
would
be
good
too.
I
I've
never
worked
with
a
pull
request.
Template
so
I'm,
not
sure
how
you
know
normally
I
just
open
a
pull
request,
because
I
have
the
files
already
so
I'm,
not
sure
how
pull
request
template
works.
So
I'll
look
into
that,
but
it
seems
like
it
would
make
sense
that
we
would,
at
a
minimum,
have
sort
of
a
format.
B
A
You
know
I'd,
like
to
sort
of
you
know
emphasize
in
in
the
template,
is
the
concept
that
we're
sort
of
crystallizing
with
the
survey
owner,
so
you
know
having
no,
basically
shifting.
You
know
how
we're
working
with
the
other
work
groups
from
you
know.
Kenny.
Can
you
do
this
for
us
all
right
if
you're
gonna
come
with
a
request,
someone
on
you
know
in
the
contingent
of
folks
that
you're
representing
is,
if
you're,
going
to
be
actively
participating
through
the
entire
arc
of
that
thing,
and
you
know
that
that
will
give
us.
A
You
know
the
right
leverage
to
say
hey,
you
know
it
looks
like
the
you
know.
The
original
poster
has
moved
on.
You
know.
If
the
owner
goes
silent,
then
then
we
have
a
corsten
that
can
sort
of
clear
our
clear
our
responsibilities
and
you
know
get
back
to
you
know
collaborating
across
the
rest.
They're
the
you
know
the
group
to
help
those
who
you
know
are
able
to
carry
forward.
That's
yeah.
B
A
B
B
A
No,
you
know
sure
you
know
my
perspective.
You
know
from
you
know,
operating
as
a
PayPal
person
that
expanded
purview
would
actually
be
interesting
to
to
me
in
and
how
I
know
engage
but
I
think
in
sort
of
just
you
know
as
the
the
champion
for
this
project.
This
initiative-
and
you
know
the
maturity
of
our
framework
and
the
ability
to
take
and
apply
it
to
you
know.
A
A
A
B
I
think
that
totally
makes
sense
and
I
think
probably
I'm
expecting
that
the
timing
might
line
up
anyway.
You
know
they're
still
really
yeah
and
then
also
you
know,
one
thing
I've
been
thinking
about
is
is,
and
it's
something
that's
been
discussed
a
little
bit
in
terms
of
the
foundation.
Is
you
know,
working
with
the
standards,
bodies
or
body
or,
however,
and
this
could
be
useful
in
in
those
sorts
of
efforts
as
well.
You
know
I.
E
They'll
definitely
be
one
of
the
things
to
figure
out
is
like
I,
think
some
of
the
user
feedback
stuff
we've
done
should
stay
focused
on
node,
but
there
are
some
things
and
the
surveys
is
a
pretty
good
example
where
that
can
apply
across.
So
we
should
should
keep
our
keeper
as
we
go
through
the
sort
of
bootstrap
of
the
new
foundation,
because
they
that
make
sure
that's
on
the
radar
to
figure
that
out
yeah.
A
A
A
F
A
Yeah,
there's
no
other
path
to
empowering,
especially
as
we
you
know
get
into
empowering
other
individuals
who
are
not.
You
know
in
these
meetings,
they're
able
to
attend.
You
know
our
regular
sessions.
The
only
way
that
you
know
I,
see
a
being
able
to
scale
out
to
that
is
to
have
a
well-articulated
programs
and
processes.
F
G
B
Going
yeah
it's
a
good
question.
Something
I
was
I,
haven't
done
much
with
issue
templates,
so
something
I
was
just
learning,
so
there's
a
dot
github
directory
in
the
repo,
the
user
feedback.
Repo
ends
up
being
a
hidden
directory.
If
that's
your
settings,
but
in
there's,
you
can
have
issue
templates.
I
followed
the
node
core
model
of
having
you
know
an
issue
templates
folder,
because
you
can
have
pull
request
templates
as
well,
and
perhaps
other
data,
so
there'll
be
another
folder
in
there.
B
D
G
B
So
it
sits
in
there
I'm
sorry,
I,
don't
have
the
screen
open.
Do
you
have
a?
Let
me
look
here.
Yeah
there.
It
is
so
dot.
Github
issue
templates
is
the
directory
and
then
that's
you
know
one
user
feedback
and
then
they
are
I
believe
displayed
according
you
know
to
alphabetically
or
numerically.
So
that's
why
I
have
a
one
there,
but
it
could
be
changed
later
on
or
whatever,
but
so
there
is
a
directory
in
the
dot
github
directory
for
issue,
template.
A
B
A
You
know
we
have
our
one
big
success,
which
was
the
build
working
group.
I,
don't
go
working,
benchmark,
working
group
survey,
which
we
brought
back
to
the
benchmark
working
group.
So
the
event
our
working
group,
you
know,
came
to
us
we're
looking
for
prioritization.
We
need
community
insight
into
where
we
should
prioritize
our
time
and
effort
in
improving
the
benchmarking
for
for
the
project.
So
we
shared
that
back
out
and
share
the
data
with
them.
So
the
detailed
data
you
know
in
that
survey
there
were
numerous.
B
Dan
they
interrupted
yeah
directory,
so
we
can
kind
of
see
what
it
looks
like
to.
While
we're
talking.
A
So
this
data
that
we
got
back
is
and
then
then
it
ended
up
getting
you
know,
deposited
in
our
directory,
but
I
think
you
know
just
taking
it
in.
You
know
depositing
it,
and
we
asked
the
the
node.js
foundation
team
to
do
a
you
know.
Personally,
the
file
information
scrub,
so
we
removed
out
any
email,
addresses
I
believe
the
survey
gave
folks
the
opportunity
to
you
know
insert
their
their
email
address.
They
wanted.
A
A
I,
you
know
in
you
know,
in
terms
of
you
know
best
value
delivered.
It
was
that
it
was
that
you
know
sharing
back
the
data
and
really
you
know
getting
you
know
coming
together
in
a
session
and
going
through
the
day
dated
together.
You
know
that
was
that
was
really
insightful,
and
you
know
honestly,
if
you,
if
you're,
if
folks
you
know,
are
really
curious,
you
can
go
back
and
watch
the
YouTube
sessions.
Cool
I
almost
never
do.
B
I
mean
that
could
even
be
like,
so
what
I'm?
What
I'm
thinking
about
is?
Maybe
we
have
maybe
we
changed
that
directory
instead
of
data,
have
it
be
like
surveys
and
then
a
directory
for
each
one
that
we
execute
on.
That
can
be
where
the
pull
request
is
made
to
you.
That
can
be
where
the
data
is
stored
and
then
also
like
a
readme
in
there.
That
does
have
like
a
link
to
the
session
on
YouTube
or
what
have
you
you
know,
try
to
gather
as
much
as
we
can.
A
Nice
thanks
yeah
and
yeah
having
that
link
back
to
the
survey.
Sorry,
the
YouTube
video
is
really
like.
That's
that's
definitely
missing
here
and
that
would
empower
anyone
who's
coming
back
and
making
use
of
that
data
to
really
get
the
context,
because
you
know
a
few
data
files.
You
know
what
what's
what's
really
going
on
here.
A
C
There,
it
is
sorry
about
that.
Yeah
I
think
the
the
last.
The
last
step
we
need
before
we
can
send
out
an
announcement
email
to
the
folks
who
expressed
interest
is
making
sure
that
we
have
a
blog
post
ready
so
that
we
can
point
them
to
it
and
put
it
there,
there's
a
minor
task
of
listing
them
in
the
and
the
repository
as
well
I.
So.
D
A
Great
yeah
so
I
know
we'll
Blankenship
got
back
to
me
that
he
has
that
permission.
You
know,
I,
don't
expect
any
issues
you
know
with
Aaron,
Heckman
and
I
know
in
our
last
session.
Michael
requested
that
you
know.
Yes,
we
want
to
have
those
active
members.
There's
folks
that
have
come
forward
and
are
active
now
recognize
what
we
also
want
to
make
sure
that
we
aren't
asserting
that
this
is
somehow
a
bounded
group
that
you
know
please,
you
know,
come
and
participate.
You
know
your
active
participation
would
give
you.
You
know
Andre.
That
group.
A
F
You
know
again
April
25th
right,
so
we're
not
doing
April
1st
so
should
I
put
it
on
my
action
item
to
bug
I
guess
maybe
Ockman
you're
gonna
be
like
the
last
reviewer
and
I
just
put
it
on
my
to
do
to
make
sure
that
you
get
that
to
me
in
a
week.
What
do
you
think
I.
F
Like
you
know,
let's
aim
for
like
four
or
five
latest
for
15
and
we
want
to
publish
on
that
on
the
general
will
publish
on
the
general
node
blog
yep.
C
H
C
A
Yeah
I
think
you
know
Tracy,
you
know
tied
this
up
and
get
this
out.
The
door
then
be
amazing.
Yeah.
A
E
A
A
A
F
C
I
think
there's
a
quick
thing.
We
can
resolve
just
there's
a
question
about
naming
of
the
group,
which
I
think
is
a
valid
point
about
avoiding
confusion.
Should
we
talk
about
that?
Yes,
so
just
looking
at
the
issue
comments,
enterprise,
user
feedback,
subgroup
and
dobrze
use,
node,
Enterprise
feedback
group
I'm,
suggesting
maybe
just
keeping
the
user
feedback
group
as
the
highlights,
maybe
adding
a
suffix
of
some
sort
like
enterprise
chapter,
maybe
yeah.
A
E
A
C
C
G
E
G
E
G
C
C
A
E
I,
don't
I
don't
see
that
needs
to
be
tied
to
github
or
anything
like
that.
It's
just
to
in
terms
of
the
its
it
can
all
be
part
of
the
user
feedback,
team
and
I
think
it
could
share
the
repo.
Like
you
know,
we
could
create
a
directory
or
something
like
that
which
was
focused
on
the
you
know
the,
and
maybe
that
makes
sense
is
like
you
know
you
could
have
sub
teams
and
then
a
directory,
which
is
the
stuff
where
you
put
I,
didn't
I.
Think
it's
really
just
like.
D
E
C
B
E
A
And-
and
you
know
in
terms
of
one
of
the
main
things
that
the
readme
offers
us
is
attribution
recognition.
So,
yes,
we
want,
to
you,
know,
sort
of
make
it
publicly
visible
for
newcomers
to
come,
but
we
also
want
to
recognize
the
individuals
who
are
you
know,
carving
out
their
times.
Do
this
hard
work.
A
H
C
B
E
C
D
E
A
Do
you
want
to
take
a
stab,
you
know
kind
of
maybe
PRN
what
that
would
look
like.
You
know
in
this
section
that
I've
highlighted
on
the
screen,
so
you
know
let's
try
to
land
it
within
this
category
right.
So
it's
it's.
You
know
everybody
is
included
there,
but
you
know
we're
going
to.
You
know,
call
folks
out,
as
you
know,
being
focused
on
certain
areas
if
they
are
only
focused
on
those
areas
right,
so
you
know
the
sort
of
counterpoint
of
you
know.
A
C
A
F
F
E
I
I
the
thing
that
comes
to
mind
is
we
might
say
why
don't
you
start
scheduling
them
at
just
after
that,
so
you
can
validate
the
deck
that
we
have
with
the
first
one
and
then
a
you
know
following
that
time,
we'll
have
a
deck
that
we
used
it
that
one
that
you
can
reuse
in
terms
of
the
you
shall
be
be
open.
All
that
kind
of
stuff.
So.
E
F
Okay
and
then,
if
you
can
look
at
the
heart
to
article
thanks,
Michael
for
reviewing
this
I
feel,
like
all
I've
been
doing,
is
passing
you
things.
F
F
Kind
of
like
laid
out
the
how
to
write
like
here's.
What
we're
doing
here
is
this,
and
this
is
something
that
we
can
also
publish
on
the
blog
as
well
thanks,
but
you
know,
I
will
need
an
extra
set
of
eyes.
I
was
just
kind
of
going
through
at
us
hey
what
would
it
look
like
if
I
ran
it
know
how
to
run
it?
G
I
mean
I
have
all
the
trust
in
the
mentorship
team,
but
yeah,
because
here
we
need
to
be
aware
also,
we
need
to
treat
everybody
as
a
customer.
So
all
the
issues
needs
to
be
in
the
same
place
somehow
because
they
are
going
to
be
all
around
the
world
all
around
the
world
different
issues
and
we
want
to
capture
everything
in
the
same
place
as
possible.
Of
course,.
E
E
E
Site,
there's
definitely
some
automation
used
by
the
security
working
group
and
things
that,
like
you
know,
there's
some
Travis
stuff,
that's
running
and
all
that
I
don't
know
how
how
much
work
effort
whatever
that
would
be
to
get
the
about
running
I've
never
done
one
but
I
mean
that'd,
be
great,
I!
Think
short
of
that.
If
we
had
a
tag
and
all
the
members
when,
where
they
were
looking
at
it
and
saw
the
new
ones
added
the
tag
that
would
probably
be
pretty
effective,
too
I
mean
from
the
title.
It's
going
to
be
fairly
clear.
F
So
if
yeah
so
I
mean
you
know
if
I
mean,
if
there's
an
issue,
template
amazing
cuz
that
solves
all
our
problems.
Yeah
since.
A
F
So
can
somebody
or
Joe
can
you
create
an
issue
for
yourself
as
an
action
item
to
do
that
before
the
next
meeting,
and
then
I'll
say
the
issue
template
labeled,
X
to
Cree
issue
and
then
I?
Let's,
let's
see
if
I
can
be
Joe,
what's:
okay,
Joe,
don't.
F
Well,
if
we
have
any
session
materials
and
then
user
feedback
mentor,
who
I
think
we
can
just
add
in
I,
don't
know
if
we
should
have
this
one
I'm
trying
to
thank
you
publishing
times
this
right
here,
but
whoever
we
decide
you
can
be
found
on
github,
I,
guess.
F
D
F
Mean
it
isn't
done
yet,
but
I
think
we
can
do
for
sure
like
it's
like.
Oh
hey,
you're
interested,
so
I
think
what
I'll
be
doing
is
I'll,
be
sending
out
an
email
and
I'll
be
introducing
introducing
like
Gary
in
that
email
and
also
pointing
them,
pointing
them
to
the
issue
where
we're
starting
to
gather
things
and
the
draft
blog
post
and
slide
deck
as
well.
F
E
Yeah,
like
that
one's
basically
tied
to
what
our
content
would
be
for
the
first
one,
so
I
think
we
just
want
to
reword
it
to
be.
You
know,
ask
questions
about
the
topic.
For
example,
you
know
the
first
one.
If
it's
on
challenges
with
you
know,
I'm
moving
up
to
the
neck
current
release,
that's
what
some
of
the
the
questions
would
be
about.
E
A
E
E
A
Hopefully
we'll
have
the
blog
post
out
the
door,
but
if
any
any
final
touches
on
that,
you
know
make
sure
we
have
that
out
and
then
I
can't
do
the
12,
but
I
could
potentially
do
the
Thursday.
So
that
would
mean
our
meetings
for
all
of
April
would
shift
from
the
our
regular
Friday
of
schedule
2
to
Thursday,
because
the
meaning
for
the
tropics
is
moved
to
cover
the
enterprise
session.
A
A
Right,
and
so
we
for
the
enterprise
focus
group,
have
moved
to
a
sort
of
neutral
time
at
1:00
p.m.
Eastern
time,
rather
than
noon
Eastern
again
like
10:00
a.m.
Pacific,
which
is
an
occupied
slot.
You
know
the
alternating
week
of
the
calm.
Calm
is
the
website
design
initiative,
sir,
that
noon.
Eastern
nine,
a
m--
pacific
slot
is
not
open,
so
we
would
be
targeting
a
1
1
p.m.
Eastern
time,
math.
E
F
A
A
We'll
do
a
run,
you
know,
maybe
in
the
blog
post
you
know
we
couldn't
bite.
I
really
like
to
have.
You
know
some
external
validation
on
that.
So
you
know
if
we
can
invite
folks
to
that
session,
to
provide
feedback
on
or
feedback
template.
Actually
you
know
who
the
audience
there
is
Tracy.
It's
our
beautiful
tassels.
A
A
We
should
invite
those
meetup
organizers
on
the
11th.
You
know
anyone
who
can
make
that
that
time
to
join
us
and
provide
feedback
on
the
template
that
that
we're
gonna
make
everybody
that
way
they
get.
You
know
a
pass-through
of
you
know
seeing
how
it
works
and
we'll
have
have
the
opportunity
to
see
at
least
two
two
sessions
being
run
before
they're
running
their
sessions
in
June.
So.
G
A
F
A
A
And
make
sure
the
mic
is
that
feedback
and
we
get
that
taken
care
of
all
right.
So
the
the
are
meeting
for
the
12th
has
been
moved
to
11th
and
our
meetings
in
April
will
all
be
shifted
to
10:00
a.m.
Pacific
1:00
p.m.
Eastern
on
the
Thursdays
of
the
week.
So
just
a
heads
up
there
make
sure
you
check
your
calendar
and.
B
A
Going
forward
just
you
know,
to
accommodate
the
the
dry
run
of
our
user
feedback
session
and
the
and,
and
it
just
so
happens.
We
already
shifted
the
the
meeting
on
the
26th
to
the
25th
for
the
enterprise
focus
session.
So
you
know
just
call
out
hey.
You
know,
by
the
way,
April
looks
like
all
of
our
dates
that
we
would
normally
be
meeting
have
been
moved
to
Thursday
instead
of
Friday's,
but
not
it's
not
a
go
forward
plan.
Okay,
cool
cool.
I
B
So
the
web
site
group
have
been
talking
about
a
survey
I'm
trying
to
get
them
to.
You
know
work
with
me
to
flesh
out
this
survey
framework,
use
it
as
a
vessel
and
then
also
I've
emailed
a
little
bit
with
Benjamin
about
the
promises
survey,
but
he's
been
a
little
non-responsive
via
email.
He
was
enthusiastic,
but
then
just
hasn't
returned
my
messages.
I
may,
since
I'm
gonna
start
working
on
promises,
stuff
and
core
I
may
just
take
it
over
and
try
to
Shepherd
it
myself
on
how
much
time
I
have.
E
A
E
Put
out
as
an
IBM
thing
and
then
as
an
IBM
blog
post
and
then
have
it.
Hopefully
we
reposted
as
a
community
thing
as
in
order
that
we
want
to
ask
for
feedback.
You
know
it's
a
new
feature,
that's
gone
out
experimental
and
what
I
want
to
do
was
get
an
issue
open
somewhere
to
capture
that
feedback
and
good
candidates
are
obviously
the
user
feedback
repo
or
we
could
do
it
in
the
diagnostic
repo,
so
I
said,
I'd
bring
it
up
here
to
figure
out
which
we
think
is
best
and
then
create
the
issue.
A
A
E
E
A
Help
chair
awareness,
but
you
know,
as
we
aligned
with
you,
know,
modules
and
you
know
the
module
feedback
group.
You
know
having
the
folks
that
are
focused
on
actually
solving
those
problems.
Let's
try
to
you
know,
take
the
the
questions
as
close
to
the
folks
that
are,
you
know,
going
to
be
able
to
use
that
feedback.
Yeah.