►
From YouTube: Node.js User Feedback Initiative Meeting
Description
A
A
A
Looking
at
how
we
can
we
can
collaborate
together
to
use
that
infrastructure
to
better
inform
ourselves
about
where
we're
known
as
going?
What
what
what
to
expect
when
teams
begin
to
update
to
the
latest
releases
and
then,
of
course,
to
give
back
to
the
community
to
share
that
insight
of
you
know
any
implications,
any
performance
implications.
You
know
oftentimes,
you
know
you
can
look
at
a
micro
benchmark
and
see
you
know
a
completely
different
story.
Then
the
impact
of
you
know
large-scale
I/o
or
you
know
any.
B
A
Factor
at
scale-
so
you
know
really
excited
about
about
that.
We
will
reschedule
the
next
session
in
419
sometime
in
January,
we'll
reconvene-
and
you
know
this
is
far
from
an
exclusive
group.
You
know
bring
bring
bring
your
team
if
you're,
you
know
deployments,
are
you
know
in
the
hundreds
to
thousands
of
services?
A
You
know,
and
you
know,
you're
dealing
with
do
some
of
the
challenges
of
an
enterprise
deployment.
Would
love
to
you
know,
have
better
more
diverse
use.
Cases
is
going
to
give
us
a
better
insight
and
better
enable
us
to
inform
the
e
the
project
any
questions
about
enterprise
that
should
be
fairly
straightforward,
I'm
going
to
mute
and
stop
my
video
for
a
second,
because
I,
my
nose
is
driven
while
I.
C
C
Updated
the
Google
document
that
was
in
that
issue
with
the
questions
that
had
been
put
forth
so
far,
there
was
some
commentary
on
the
questions
and
the
answers
and
such
that
I
have
not
been
able
to
fully
synthesize
but
we'll
work
on
that
when
I
get
a
moment.
A
few
other
people
made
some
comments
and
suggestions
on.
You
know
what
we
had
so
far.
C
So
I
will
work
through
to
kind
of
process
that
and
package
it
all
up
as
best
I
can
and
then
you
know
ask
for
any
other
input
before
we
move
forward
and
in
the
coming
days,
probably
next
week.
So
hopefully
you
know
we'll
move
forward
on
that
aspect
and
I
met
with
Tracy
and
Sophia
from
the
foundation.
I
think
it
might
have
been.
Yesterday
we
talked
briefly
you
know.
They're
ready
to
excuse
me
just
support
us
in
these
efforts
and
I.
C
Think
the
expectation,
too,
is
that
you
know
we
can
kind
of
formalize
this
process
so
that
we
can
apply
it
to
the
migration
and
upgrading
survey
that
has
been
mentioned
and
any
other
surveys
that
we
want
to
put
together
moving
forward.
So
yeah
progress.
A
little
slow
I've
been
a
little
busy
but
trying
to
get
some
progress
on
promises
in
particular
and
formalize
the
process.
So
we
can,
you
know
other
people
can
jump
in
and-
and
you
know,
take
the
reins
of
any
particular
survey
that
we
want
to
move
forward
on
so
yeah.
Some
progress.
A
C
Yeah
I'd
like
to
do
that,
if
possible,
so
I'll,
I'll
ping
them
and
see
if
they
can
help.
You
know
the
three
of
us
get
on
it.
Then
then
you
know
we
should
be
able
to
kind
of
ramp
it
up
pretty
quickly
and
feel
like
we've
got
a
strong
survey
put
together
great,
so
yeah
I
was
thinking
about
that.
Just
like
a
half
hour
ago
did
I.
They
volunteer
to
do
all
the
synthesis
or
just
to
move
it
forward.
So.
A
A
A
A
You
know
III
think
it's
fine,
we're
doing
it.
Yeah
we're
doing
this
obsessively
on
they're
having
on
Ben's
behalf
specifically
Julian
was
not
in
the
original
requesters,
though
I
know
that
you
know,
Netflix
is
really
doing
a
an
operational
push
into
no.10,
where
historically,
promises
have
been
no
bueno
for
their
observability
infrastructure,
and
you
know
now
with
the
adoption
of
ten,
they
feel
like
they're
you're.
Getting
to
the
point
where
a
post-mortem
analysis-
and
you
know
other
infrastructure
that
they
rely
on,
is
you
know
good
enough
to
to
greenlight
promises?
A
So
you
know
that
that
battle
was
fought,
but
you
know
it's
very
obvious
across
across
the
the
web
platform
ecosystem
that
you
know,
promises
are
here
to
stay,
and
you
know
we
can't
in
our
infrastructure
sort
of
push
that
down.
Yes,
you
can't
use
that
construct,
because
we
know
the
challenges
video.
We
knew
you
couldn't
use
that
construct
because
you
couldn't
see
inside
what
the
envelope
was,
and
so,
if
you
have
everything
in
a
big
promise
chain,
it's
a
pipeline
of
mystery
errors.
Yeah.
C
A
D
E
C
E
C
I
think
I
think
that's
a
good
point,
I
think.
At
the
very
least,
we
should
definitely
surface
this
survey.
Effort
around
promises
to
make
sure
we
get.
You
know
a
good
amount
of
input
on
it
before
it
goes
out.
I
mean
I
worry
a
little
bit
about
too
many
cooks
in
the
kitchen
and
then
I'm
getting
derailed
and
delayed,
but
I
think
we
should
definitely
make
sure
that
we
get
the
right
questions
asked
excellent.
A
Yeah
I
mean
I
hit
the
risk
there
is
you
know
if
we
don't
push
it
out
with
enough
context,
then
you
know
we
risk
doing
a
lot
of
effort.
You
know
if
you
don't
get
the
edges
sanded
off
a
little
bit
on
on
those
questions,
then
you
know
we
risk.
You
know
scrambling
and
you
know
having
to
backfill
contacts
that
you
know
maybe
may
be
obvious
to
some
of
our
subject
matter.
Experts.
C
A
A
That,
like
kind
of
the
last
day
of
the
last
baby
before
the
holidays,
it's
gonna
be
a
really
light
duty
for
for
me,
you
know,
I
I
have
no
objections
to
us.
You
know
what's
building
that
until
the
new
year,
but
you
know
I'm
also
open.
You
know
it's
it's
fairly
non-invasive
for
me
to
you,
know,
come
and
do
this
meeting
so
yeah.
A
A
A
A
C
D
A
C
A
A
Great
well,
that
is
the
balance
of
the
topics
that
I
needed
to
cover
today.
Does
anyone
have
anything
else
that
that
we
need
Sophia
yeah
as
we're
sort
of
trying
to
land
this
plane?
What
what
is?
What
are
we
looking
at
in
terms
of
the
technology
solution?
Do
we
have
a
bead
on
whether
it's
a
the
Foundation
SurveyMonkey
instance?
Are
we
gonna?
Do
we
have
a
tech
choice,
sort
of
lined
up
at
the
other
end
of
this
work.
B
Well,
I
I
put
it
the
notes
and
action
items
from
last
medians
on
Doc.
You
should
be
y'all
share.
If
not
tell
me,
and
that's
all
that
I
think
there
I
summarized
it.
Everything
I
still
need
access
to
the
last
survey
that
you
guys
did
because
I
was
kind
of
taking
notes
of
people
commenting
about
this
survey,
so
I
took
notes
about
what
they
say,
but
I
haven't
like
look
the
original
content,
you
know
so
I
think
I
can
come
up
with
new
things
once
I'd
look
at
it
less.
A
A
E
C
B
B
B
A
A
A
A
A
And
I
forget:
we
ran
this
at
the
same
time
as
the
foundation,
the
annual
foundation
survey,
so
we
had
to
be
a
little
bit
respectful
of
you
know,
making
sure
that
we
didn't.
You
know,
that's
that's
like
essential
data
collection
for
the
for
the
foundation
every
year,
so
we
were,
we
were
respectful
of.
B
B
But
yeah
we
have
some
Twitter
accounts
where
developers
go
for.
You
know,
updating
on
everything,
and
the
good
thing
I
think
is
that
everyone
loves
no.
Yes,
that's
something
that
doesn't
happen.
We'd
I
mean
some
people
can
say
that
there's
things
that
could
be
better,
but
nobody
says
that
there's
an
something
better
right.
B
C
A
B
A
A
B
A
C
E
Piggy
cup
so
I
think
that's
the
the
problem
here.
So
people
on
github
and
people
who
doesn't
use
the
github
as
per
day,
of
course
now
and
I'm,
not
talking
about
permission
or
something
or
restrictions,
but
I'm.
Just
talking
about
people
being
aware
of
what
is
going
on
on
foundation
and
on
different
issues.
Yeah.
A
B
B
A
Giuseppe,
you
know,
as
we
were
discussing
content
and
speaking
of
delegation,
you
know
as
you're
having
those
conversations
with
Ben
and
Julian.
You
know,
maybe
you
could,
you
know,
reach
out
to
them
and
ask
them.
You
know
if
they'd
be
willing
to
do
a
to
write
a
blog,
post
and
sort
of
tee.
This
up.
That's.
C
A
I
know
Ben,
is
you
know,
super
super
passionate
about.
You
know
high
performance
promises,
you
know
if
we,
you
know
let
them
sort
of
turn
loose
a
little
bit
and
you
know
tell
some
of
the
story
of
you
know
what
he's
been
working
on
for
the
last
couple
years
and
and
enabling
promises
in
the
project.
Then
you
know
that
could
be
really
interesting.
Yeah.