►
From YouTube: Node.js User Feedback Initiative
Description
B
Great
well
hi
everybody
thanks
for
joining
us
today.
This
is
the
no
just
user
feedback
team
meeting.
Were
you
know
a
member
of
the
node.js
community
committee
and
we're
focused
on
helping
connect.
End
users
to
you
know
just
project
in
in
all
its
capacities.
It
was
that's
the
the
the
calm
calm
or
whether
that's
providing
feedback
to
our
technical
members
to
technical
steering
committee.
B
So
today
we're
having
our
team
meeting
and
next
month
we're
gonna
have
our
first
open
public
user
sessions,
so
we're
gonna
take
our
meeting
every
two
weeks.
Bi-Weekly
and
you
know,
use
that
that
cadence
to
share
with
a
broader
audience,
you
know
and
elicit
feedback
around
know.
Jess,
specifically,
we
have
been
working
with
the
benchmarking
working
group,
so
the
the
working
group
inside
of
the
node.js
project
that
is
responsible
for
handling
benchmarking
and
maintaining
our
benchmarks
benchmark.
B
So
let
me
go
ahead
and
share
my
screen
and
get
the
agenda
up
and
in
front
of
us
actually,
but
before
I.
Do
that,
let
me
go
ahead
and
take
a
roll,
so
Mihai
has
agreed
to
take
notes
day.
So
I
really
appreciate
that
I'm
Dan,
Shaw
and
I'll
go
around
the
zoom
list
here
and
I
introduce
the
other
folks.
So
we're
joined
by
the
siren.
B
Great,
so
today's
general
I
got
a
bunch
of
a
bunch
of
topics
that
we're
working
through
and
go
ahead
and
start
with
the
art
are
key
initiatives.
So
we've
been
running
the
benchmarking
working
group
survey.
It's
one
of
the
sort
of
kickoff
projects
that
that
started.
This
initiative,
the
the
benchmarking
working
group,
has
reached
out
to
the
community
committee
for
help
doing
a
survey
and
the
user
feedback
initiative
took
that
and
yeah
we've
had
quite
a
few
submissions.
I
think
we're.
You
know
approaching
150
160
on
that,
and
it's
been
been
very
productive.
B
We
are
almost
done
with
that.
So
we
have
what
is
it
five
more
days?
And
you
know
last
last
week
I
sent
out
the
the
update
and
reminder
terney
you.
You
had
said
that
you
wanted
to
take
the
next
round
of
promotion
there.
So
can
you
take
an
action
you're
following
this
meeting
I
guess
to
send
out
the
the
last
straw
and
remind
folks
that
the
last
day
sub
to
submit
feedback
in
the
benchmarking
working
group
survey
will
be
January.
31St
do.
B
A
C
B
B
B
B
I
want
to
share
a
bit
of
sort
of
process,
frustration
around
doing
the
the
outreach
you
know.
We
have
a
a
spreadsheet
that
we're
putting
you
know
names
into,
and
you
know,
I
think
we
need
to
try
to
explore
something
a
little
bit
more
online,
but
not
necessarily
through,
not
necessarily
through
github.
B
B
Is
for
end
users,
so
you
know
individuals
like
dwell
and
and
now
folks
that
are
using
node
but
aren't
necessarily
plugged
into
the
the
node.js
project
and
to
be
plugged
in
your
typically.
You
know
spending
time
and
engaging
in
the
project.
Github
and
I
think
you
know
eventually,
as
folks
get
active,
they're
gonna,
you
know
we're
gonna
want
them
to
be
on
github
yeah!
B
A
B
A
B
B
D
D
B
D
D
B
You
know
in
in
dueling
out
rates
to
individuals
who
are
end-users
and
are
not
necessarily
on
github
all
the
time.
So
most
of
the
activity
and
actions
that
we
take
in
the
node.js
project
are
for
better
for
worse,
you
know
plugged
into
github.
You
know
one
of
the
challenges
that
we've
experienced
with
the
community
committee
is,
you
know,
we're
doing
a
lot
of
the
community
and
out
rates
actions
and
activities
engaging
the
private
community
around
noches,
and
you
know
that
makes
a
little
less
sense.
B
Then
you
know
when
we're
talking
about
and
aligning
on
on
technical
projects.
So
the
joel
is
just
wondering
you
know
if
you
had
any
suggestions
on,
you
know
how
we
might
be
able
to
engage
better
with
you
and-
and
you
know
your
team's,
you
know
through
new
tools
that
are
better
are
going
to
be.
You
know
easier
to
to
engagement
right.
D
So
currently,
I
think
thought
only
really
for
us
to
make
any
kind
of
a
communication
channel
with
no
chairs
the
core
team
or
the
narrative
element
is
through,
is
going
to
github
and
very
is
the
only
channel
that
I
know
of
in
the
moment
and
obviously
and
Twitter
so
I
mean
I,
follow
all
the
old
indulges
I
can
but
developers,
kool
members
and
you
on
Twitter
and
I.
Look
at
Twitter
every
day,
so
any
any
any
kind
of
noches
that
comes
on
Twitter,
I
I
would
spend
a
few
minutes
to
look
at
it
to
see.
D
What's
going
on
and
like
particularly
in
in
things
like,
if
there's
any
security
related
things
or
any
improvement
updates
to
performance,
I
would
I
would
look
at
them
the
first
thing
and
so
like
in
Twitter,
it's
been
a
workout
working
out
well,
but
typically
only
for
people
like
me
who
has
a
keen
interest
in
anything
happening
in
notice,
but
for
our
for
the
the
rest
of
the
developers
at
Walmart
Labs,
most
of
them.
They
they
they.
They
take
news
for
me
on
our
internal
slack,
because.
D
I'm
thinking,
maybe
like
slack
or
something
like
data
chat
rooms,
but
I
I
know
that
people
don't
actively
join
those
things.
Yeah
and
I
mean
then
the
next
next
thing
is
part
of
email
and
but,
like
you
said,
and
it
like
even
know,
is
these
days
like
I'm
looking
at
my
company,
email
I
have
30,000
and
ripped
email
exactly.
D
So
far,
the
the
most
effective
tool
and
the
medium
for
me
to
communicate
with
external
developers
and
out
and
like
to
the
channel
to
make
the
connection
between
external
and
our
internal
development
developer
community
is
actually
github.
We
have
you
know
we
have
our
internal
github,
we
have
our
internal
slack
and
a
couple
of
us
is
actively
monitoring
all
the
external
channels
and
anything
that's
interesting.
We
immediately
related
back
to
our
internal
community.
D
B
Great
rhythm,
so
you
know
one
thing:
if
you
are
aware,
we
have
begun
officially
embracing
in
the
community
committee,
the
the
node
slackers
slack
and
you
many
of
us
are
active
there.
So
you
know
you
know
I
I'd
like
to
begin.
You
know
plugging
in
there
a
bit
more,
so
we'll
try
to
see
if
that
that
is
a
form
that
folks
will
use
to
need.
You
know
off
the
top.
Your
head,
the
the
invite
link
from
for
no
slackers
slackers.
C
B
B
C
A
A
A
B
B
B
We
can
expect
over
the
next
couple
weeks
the
initial
steps
of
in
organizing
the
next
meeting.
So
you
know,
that's
been
slow
and
and
I
think
the
cadence
will
be.
You
know
fairly
lengthy,
so
you
know
kind
of
a
quarterly
cadence
just
because
of
the
individuals
that
are
involved
and
I.
Think
the
cat
herding
involved
in
and
getting
everybody
in
that
group
set
up
and
and
making
sure
that
that
the
context
of
what's
happening
is
being
broadcast
to
everyone.
The
project.
A
B
B
Genda,
bash
and
you'll
find
it's
time
that
folks
can
do
that.
So
you
know
as
a
high-level
I'm
thinking
that
it's
gonna
be.
You
know
the
first
couple
weeks
of
March
that
we
do
that
and
you
know,
have
some
ideas
around
when
we
could
get
together
in
May
as
well.
So
that's
making
it
like
the
rough
sketch
of
when
those
wood,
wood,
wood,
land,
sure.
B
Alright,
so
you
know
thanks
Mihai,
it's
great
to
have
you
on
as
a
full
team
member
landed
the
the
the
PR
around
that
and
thank
you
tourney
for
going
through
and
and
setting
up
everything
you
know
me:
I
should
be
full
member
added
to
the
user
feedback
team.
I
checked
that
and
everything's
looking
good.
So
it's
been
great
having
you
in
involved
with
the
this
project.
Since
its
inception
me
hi,
and
you
really
appreciate
all
that
you
do
to
keep
this
moving
forward.
Yeah.
B
Michael
Dawson
requested
in
and
the
team
meeting
here
that
we
add
a
meeting
template
journey
when
I
was
reviewing
this
request.
I
saw
that
you
have
added.
You
know
templates
for
the
community
committee.
Can
you
share
a
little
bit
of
context
about
what
what
this
the
PR
templates
are
trying
to
achieve.
B
B
A
It's
it's
a
pain
to
maintain
and
used.
So
my
understanding
is
that
this
tool
is
a
kind
of
automatic,
automated
version
of
that
that'll
just
submit
meetings
per
her,
yes
submit
create
the
issue
for
the
next
meeting
automatically.
So
if
the
process
was
pretty
easy
for
the
most
part,
I
just
looked
at
there,
there's
four
different
types
of
files
and
I
looked
at
each
of
the
files
of
a
different
group
and
just
kind
of
copied
that
and
replace
the
context
for
the
community
committee.
It
was
pretty
pretty
lightweight.
Okay,.
B
A
So
yeah,
it's
it's
not
too
bad.
The
only
thing
is
with
onboarding.
You
have
to
make
sure
that
this
is
a
part
of
the
process
is
updating
the
Doc's,
because
I
guess
we
have
observers
at
the
community
committee,
but
there
is
observers
for
this
as
well.
You
will
need
to
update
that
when
you
want
to
observers
to
be
added-
or
you
know
whatever.
If
you
want
members
dwelle
members
are
automated
by
team
engine
so
that
doesn't
need
to
be
managed
as
much
but
yeah
it's
it's
pretty
just
copy-paste.
B
A
D
A
B
I
mean
that's,
that's
it
definitely,
you
know
being
a
cumbersome
part
of
figuring
out
how
to
do
that
and
honestly,
you
know
as
a
programmer.
It's
like
all
right.
You
know
how
do
I,
how
do
I
help
automate
this
Michael
Dawson
has
thankfully
automated
this
and
I
look
forward
to
seeing
how
that
works.
Awesome.
Thank
you
me
hi,
for
you
know,
taking
the
the
past
there
at
at
landing.
That
and
attorney
would
would
you
you
know.
If
me
has
any
questions,
would
you
be
available
to
help
yeah.
A
B
Alright,
so
taking
user
feedback
into
the
real
world,
so
you
know
in
that
story
of
hey
we're,
gonna
go
and
do
user
feedback.
You
know
one
of
the
first
areas
was
the
the
surveys
and
we
set
up
the
the
public
meetings
through
this
channel
and
early
on.
We
really
were
excited
about
sort
of
taking
this
in
to
meet
space,
and
you
know
getting
getting
feedback
in
person
and
also
you
know
doing
outreach.
So
you
know
folks
that
are
in
the
community
are
aware
of
some
of
the
attacks
points
that
they
can
engage
with
this.
B
So
in
February
at
index,
2018
IBM
doesn't
like
to
text
the
name
I
guess
to
this
this
thing,
but
it
is
an
IBM
organized
event
intended
to
be.
You
know,
for
the
community
by
the
community
so
interesting,
I
plan
on
attending
this
is
this
is
right
in
San
Francisco,
so
easy
for
me
to
attend
and
if
you
kind
of
follow
the
two
items
here,
you
know
you'll
be
able
to
to
see
the
the
event
overview.
B
D
B
So
yeah
be
fantastical
if
you
could
join
and
maybe
bring
it
folks
a
couple
folks
on
the
team.
You
know
be
good
to
have
your
folks
that
are
out
there
already
have
some
some
context
about.
You
know
what
we're
doing
the
user
feedback
initiative
to
this
will
be
the
first
conversation.
This
would
be
the
first
public
conversation
that
we
have
so
we'll
be
experimenting
with.
You
know
what
works
and,
and
then
you
know
the
additional
challenge.
I
guess
is
the
best
way
to
articulate
it.
B
There's
no
challenge
that
we
will
have-
and
this
has
been
a
challenge
for
us
for
quite
some
time
in
the
noches
project
we'll
be
taking
those
you
know
real
world
experience
and
bringing
that
back.
So
you
know
I
see
that
as
being
one
of
the
the
single
biggest
challenges
for
us
in
doing
these,
these
in-person
meetings
is,
you
know,
capturing
the
the
the
context
of
what
happened
at
the
the
meeting,
bringing
them
back
into
essentially
github
space.
B
A
It
foundation
members
that
are,
you
know,
cuz
I,
know
I
I'm,
coming
to
it
to
help
engage
with
this
organizing
what's
happening
there
like
what's
happening
this
issue,
but
I
don't
know
to
what
extent
so
getting
more
a
little
bit
more
clarification
for
Michael
would
be
helpful
just
on
that
and
what
the
fund
needs
would
be.
But,
yes,
absolutely
so.
B
You
know
Mihai,
if
you
you
know,
if
you're
available
during
this
time,
you
would
like
to
come.
Join
this
session
there.
There
is
a
mechanism
in
the
project
to
to
allocate
funds
for
project
events
like
this,
so
I'm
sure
we
can
get
the
tickets,
but
it
would
be
zoom
support
for
the
travel
and
accommodation.
So
if
you're
interested
and
available
on
February
20th
through
22nd-
and
you
would
like
travel
assistance,
you
know
I
can
help.
You
know,
fund
and
and
put
the
request
in
to
the
admin
repo
yeah.
C
D
B
B
Okay,
so
last
but
not
least,
the
February
9th
we're
gonna
have
our
first
public
user
feedback
meeting.
There's
some
some
great
context
in
the
issue
that
Michael
Dawson
shared.
So
you
know,
since
the
benchmark
working
group
will
not
have
had
time
to
digest
the
results
of
of
the
survey
you
know
Michael
wanted
to.
You
know
you
know
limit
as
much
of
the
sort
of
results
sharing
and
you
know,
focus
on.
B
You
know
why
the
questions
were
asked
and
you
know
discussion
around
what
were
benchmarking,
what
we're
trying
to
accomplish
in
benchmarking-
and
you
know
the
direct,
the
the
potential
directions
that
we're
looking
for
and
you
know,
articulate
you
know,
what's
going
on
and
try
to
get
some
feedback
on.
What
folks
needs
are
around
benchmarking,
and
you
know
how
folks
are
leveraging
their
awareness
around
benchmarking,
and
you
know
all
the
performance
gains
that
we're
seeing
through
the
work
of
your
project
numbers-
and
you
know,
we've
we've
actually
seen
a
ton
of
improvement.
B
You
know
over
over
the
last
six
months,
or
so
from
you
know,
JavaScript
optimizations,
that
the
the
VA
team
have
been
putting
into
place
so
really
excited
about.
Sharing
this
we'll
be
doing
this
through
our
our
this
same
channel,
so
we'll
be
broadcasting
and
inviting
attendees
in
through
zoom
and
broadcasting
on
to
YouTube.
B
When
is
it?
It
is
February
9th
during
this
time.
So
two
weeks
from
today,
so
it's
going
to
be
a
remote
video
session
like
remote
like
we
are
today,
but
we're
gonna
have
representatives
from
the
benchmarking
working
group
sharing.
You
know
a
lightweight
presentation
and
you
know
then
you
know
we
really
want.
You
know.
What's
more
than
me
running
my
mouth
yeah,
you
do
providing
feedback
and
you
know
engaging.
You
know,
members
of
our
user
community,
yeah
I'd
love
to
join
that
and
I
look
forward
to
it.
Awesome
great.