►
B
A
B
So
you
know
predictably,
light-duty
meeting
I
wanted
to
go
ahead
and
and
hold
this
meeting
today
because
of
the
benchmarking
working
group
survey.
So
we
you
know
decided
in
the
user
feedback
meetings
to
go
ahead
and
you
know
get
the
benchmarking
working
group
survey
built
out
and
published
over
the
holidays.
The
benchmarking
working
group
reached
out
back
in
October
for
to
somebody
pre
predates
the
user
feedback
initiative,
so
we
reached
back
back
in
October.
B
Get
up
github,
amazing
television,
so
here's
the
the
benchmarking
working
group
survey,
issue
and
user
feedback
and
if
we
go
from
there,
there's
the
URL
for
the
benchmarking
working
group
survey.
So
yeah
really
nice
built
out
if
I
hit
this
three
or
four
times.
If
you
hit
this
page
and
it
looks
terrible
turn
off
your
ad
blocker
you've,
you
know
gone
crazy
over
this
journey.
B
B
So
yeah
learn
that
and
building
out
the
survey
along
the
way.
So
a
few
questions
here,
some
open-ended
questions
very,
very
technical
and
you
know
I'm
excited
to
balance
out.
You
know
if
you
look
at
what
the
node.js
foundation
and
NPM
inks
surveys
are
trying
to
accomplish.
You
know
those
are
really
trying
to
set
a
baseline
of
business
market
understanding.
B
You
hear
our
market,
you
know
were
sort
of
identifying
folks
and,
and
you
know
getting
a
better
understanding
of
what
the
consistency
is,
and
this
benchmarking
survey
is
very
much
a
you
know,
technical
overview
and
a
desire
to
get
feedback
from
from
folks
building
knowjust
apps
across
the
industry,
and
you
know
capture
that
that
conduct,
so
the
benchmarking
group
can,
you
know,
really
be
measuring.
B
You
know
today's.
No
it
apps.
You
know
we
have
the
inspiration
of
the
v8
team.
Who's
really
drastically
changed
their
focus
on
how
they
optimize
the
the
developer,
experience
for
you
know,
chrome,
developers
and
and
v8
developers.
You
know
that
is
fueled
by
the
insight
of
the
broader
JavaScript
ecosystem
and
sort
of
optimized
as
much
as
possible
to
that
that
broad
reality,
you
know
the
fact
is,
with
the
open
source
project
nodejs,
we
don't
have
you
know
Universal
kilometer.
B
We
don't
have
phoning
home,
we
don't
know
what's
going
on
inside
of
your
application,
so
we
have
to
rely
on
your
feedback
to
to
make
that
possible.
So
you
know
and
invite
you
to
check
out
the
benchmarking
working
group
survey
to
provide
feedback
here
on
issue
22
and
user
feedback
and
help
us.
You
know
this.
This
point,
you
know:
we've
prepared
the
survey
you
know
we're
reaching
out
to
the
community
community
in
the
band.
B
So
it's
a
working
group
inside
that
just
project
to
you
know,
share
the
you
know,
share
the
information
that
the
the
survey
exists
and
yeah
we
did.
We
need
to
disseminate
this
probably
run
this
for
just
over
a
month,
and
you
know
I
know
I
know
the
benchmarking
worker
groups
excited
to
see
that
input
and
get
your
feedback
awesome.
B
B
You
know
no
expectation
that
folks
are
around,
you
know
doing
things
or
promoting
yeah.
You
know
the
project,
you
know
I,
guess
you
know
both
you
and
I
out,
evangelizing
things.
If
you
can
take
a
second
to
tweet
about
the
survey
that'd
be.
B
A
B
A
Send
them,
you
know
a
tweet
idle
know
with
some
content
that
they
should
either
share
retweet
or
something
so
that's
usually
a
good
way
to
get
in
touch.
Even
if
you
don't
know
who's
being
active
right
now,
I
knows
if
he
and
Tracy
used
to
handle
it
Tracy's
no
longer
at
the
foundation
and
zippy
is
on
holiday,
I
believe
just
looking
at
the
issue
after
the
holidays,
Greg
asked
if
she
could
put
it
out
on
Twitter,
so
yeah.
If
you
know
just
ping
it
and
whoever's
actually
managing
it,
could
probably
help
cool.
B
B
Yes,
the
twelfth
had
hoped
to
do
you
know
the
first
of
our
sort
of
public
feedback
sessions.
You
know
in
terms
of
how
we're
seeing
our
meetings
layout,
you
know
we're
on
a
bi-weekly
it.
So
every
every
two
weeks
we
meet
on
on
Friday
9:00
a.m.
Eastern,
we've
kind
of
anchored
that
time
you
know,
as
as
our
group
grows,
we'll
get
into
more
crazy
schedules
like
the
TSE
in
there
you
know
Omni
around
the
world
time
zone,
but
we
get
together.
B
You
know
every
two
weeks
and
we're
going
to
start
having
sessions
that
have
actual
end
users
on
that.
So
we
have,
you
know,
send
out
some
messages
inviting
folks
to
to
self-identify
and
to
engage
and
we've
gotten.
You
know
a
couple
dozen
feedback
from
that
William
cap
key
was
you
can
try
to
to
get
a
session
for
the
twelfth
around.
B
New
users
that
just
started
using
node
but
unfortunately
won't
be
available
on
the
twelve
so
we'll
run
a
normal
meeting.
You'll
continue
the
promotion
of
the
benchmarking
working
group,
and
then
we
have
a
enterprise
group
session
that
Michael
Dawson
is
coordinating
in
February.
So
we're
gonna
have
a
public
meeting
in
this
forum
where
we'll
have
end-users
providing
feedback
through
this.
You
know
foundation
mechanism
so
excited
to
kick
that
off
as
we
head
into
to
2018
dan.
A
B
Right
so
data
protection-
we,
you
know,
have
basically
relied
on
the
abstraction
of
the
node.js
foundation
right,
so
we
leaned
on
Greg
Wallace
of
the
noj's
foundation
to
create
the
survey
on
behalf
of
the
user
feedback
initiative,
and
so
that
way
you
know
the
data
lives
in
the
foundation.
So
any
personally
identifying
information
is
no
captured
sort
of
in
official
foundation,
employee
space,
and
then
we
will
go
and
basically
ask
for
that
data.
So
I'll
document
that
yeah
we
took
the
sort
of
easy
path
for
now.
A
B
And
yeah
I
I
think
we
will
have
the
opportunity
to
get
more
sophisticated,
but
you
know
these
sort
of
shared
identity
things
before
we
went
live
Tara
and
I
were
you
know,
commenting
on
the
no
Jess
foundation
calendar
and
you
know
getting
access
to
that
in
Google.
Yeah
Google
Calendar
is
a
bit
of
a
pain
and
you
know
we'll
work
towards
a
way
to
do
that.
Better
yeah.
B
A
B
Well,
thanks
Tierney,
for
taking
the
time
out
of
your
holiday
to
get
this
set
up
thanks.
Everybody
for
joining
us
go
to
to
issue
number
22
and
user
feedback,
and
you
know
check
out
the
the
benchmarking
survey
and
shared
around,
especially
if
you
have
friends
and
colleagues
with
large
snow
just
moments,
you
know
be
keen
to
get
that
feedback
great.