►
From YouTube: Node.js User Feedback Initiative Meeting
Description
https://github.com/nodejs/user-feedback/issues/90
September Node.js Online Meetup organized by the Node.js User Feedback team.
Schedule:
* 5pm ET - Gather and socialize
* 5:30pm to 6:30pm ET - Talks
* 6:30pm to 7:00pm - Open discussion
Talks:
* Michael Dawson, Node.js TSC Chair and CommCom Member - @mhdawson
* Rich Trott, Node.js TSC - @trott
Talk 1:
Introduction to Node.js Initiatives, working groups and teams and how to get involved
with Michael Dawson
Get to know the Node.js initiatives, working groups and teams (including Community Committee and TSC initiatives) and how to get involved.
Talk 2:
A Response To “Design Mistakes in Node”
with Rich Trott
What should we do about design mistakes in Node.js? A non-inflammatory (I promise!) review and response to an event that prompted headlines like "Node.js Creator Blasts Node.js".
A
A
And
a
high
level
user
feedback
is,
you
know,
exists
to
create
a
bi-directional
channel
to
end
users.
It's
bi-directional
in
the
sense
that
our
job
is
not
done
just
by
sort
of
bringing
an
issue
to
the
the
TSC
or
you
know,
building
awareness,
but
you
know
part
of
that
is
also
you
know
continuing
to
serve
whomever.
Maybe
they
are
looking
to
get
feedback,
so
we
don't
leave
folks.
You
know
hanging
everyone
here
and
the
noches
projects
are
volunteers,
so
you
know
when
we're
providing
connective
tissue.
A
We're
looking
to
you
know,
build
and
support
that
all
the
way
through
the
lifecycle
of
feedback
in
order
to
sort
of
focus
our
time
and-
and
you
know,
engaged
with
various
audiences-
we've
broken
things
down
into
into
new
focus
areas.
So
you
know
we
can.
We
can
build
those
communities
together.
Currently
those
focus
areas
are
the
general
user.
The
enterprise
use
case-
and
you
know,
Achmed-
has
taken
the
lead
on
the
enterprise
user
feedback.
We
have
a
group
that
is
get
formed
around
tooling
and
I.
A
Haven't
had
had
an
opportunity
to
follow
up
with
Christopher
Hillier
to
see
if
tooling
has
graduated.
You
know
the
the
the
the
tooling
group
that
just
formed
inside
of
the
node.js
project-
you
know
came
to
us
first
and
we
helped
them
bootstrap
and
you
know
Chris
took
over
the.
You
know
the
the
organizing
of
that
tooling
group
and
we
were
able
to
help
them
land.
Some
changes
into
FS.
A
Been
including
node
modules
and
every
project-
and
you
know
like
why
isn't
this
just
just
a
core
API
brought
that
to
the
the
TSE
and
now
that
group
has
under
github
that
Tom's
last
node,
yes,
less
tooling,
formed
a
new
group,
so
yeah
III
I'm,
actually
not
sure.
Yet
what
the
relationship
is
going
to
be
with
that
tooling
groups
and
the
user
feedback
team
will
always
be
here
in
terms
of
facilitating
and
helping.
You
know
build
build
bridges
and
connect
with
the
broader
user
community,
but
you
know
that's
still
an
open
thing.
Yeah.
B
I
mean
from
my
perspective,
I
could
see
it
being
one
of
two
like
it
could
be
that
yeah
they
just
want
to
be
a
group
that
operates
and
covers
reach
and
the
internal
sort
of
technical
work
in
core,
or
they
might
still
see
it
as
like
that
that
team
is
focused
on
the
technical
work
and
the
outreach
is
kind
of
a
separate
issue.
So
right
either
way
it's
it's.
It's
great
to
see
that,
and
you
know
I
guess
I
just
wanted
to
add
to
the
original
descriptions.
B
You
know
our
goal
is
to
form
the
sort
of
long-standing
relationships
with
end
users,
so
that
we
can,
you
know,
repeatedly
get
feedback
and
like
sort
of
test
ideas
as
well.
As
you
know,
on
a
regular
basis,
hear
what
those
groups
concerns
are
in
terms
of
things
that
we
should
be
thinking
about
in
the
project,
make
sense.
A
So
this
past
week
we
had
the
the
evolution
of
general
user
feedback.
So
if
we've
found
that
focused
topics
perform
much
better
than
it'll
come
have
a
discussion.
Yeah
have
a
discussion,
just
doesn't
have
enough
draw
or
enough,
you
know,
focus
energy
and
we
found
the
general
use
case
kind
of
drifting
from
engagement.
A
A
You
know
the
the
meetup
through
meetup
comm,
which
was
pretty
cool
so
coming
from
you
know,
broader
affinity
groups
and
using
the
meetup
me
up
is
quite
good
at
you
know.
A
couple
things
yeah
so
broadcasting
to
folks
and
an
audience
interest
area
and
creating
group
recurring
attendance
so
that
that
is,
you
know
something
that
meet
up
calm
as
a
tool
in
you.
B
Know
I
think
I'd
add
the
while
there
was
like
40
registrations
and
maybe
20
people
that
join.
We
also
got
a
hundred
and
forty
people
who've
joined
the
group,
so
I
think
that's
a
really
good
sign.
Just
in
terms
of
that's
now,
a
larger
community
that
we
can
message
and
zippy
did
reach
out
to
me
and
I
assume
she's
gonna
reach
out
to
you,
Dan
in
terms
of
doing
more
promotion,
even
through
through
our
regular
channels,
but
even
without
that,
it's
great
to
see
that
we
got
like
a
hundred
and
forty
people.
B
Hopefully
that's
like
a
hundred
and
forty
who
weren't
from
we
wouldn't
have
gotten
to
our
regular
channels.
So
I
don't
know
if
there's
other
ways
to
promote
your
meetups
and
stuff
that
you
know,
because
that
seems
to
be
one
of
the
one
of
the
reasons
we
went.
This
way
was
to
try
and
get
out
of
our
own
bubble
right
and
so
I.
Don't
know
if
there's
like
more
standard
meetup
ways
to
promote
things,
but
we
should
see
if
we
can
take
advantage
of
those
two
well.
A
I
mean
there's
also
just
the
promoting
a
thing
right
and
you
know
in
terms
of
this
past
iteration,
you
know
we
got
the
the
minimum
slice
of
a
little
bit
of
Deshawn
etwork
traffic
and
you
know,
what's
on
meetup
calm,
that's
about
it.
So
you
know
what,
when
we
come
back
for
the
next
one,
I
was
gonna
reach
out
to
zippy
anyway,
to
ask
her
to
help.
A
So
you
know
that
that's
something
you
know
there
just
needs
to
be
there.
The
physics
of
time
and
schedule
laid
out-
and
you
know
with
that-
you
can
drive
promotion.
You
know
you
know
it
is
you
know.
The
promotional
part
is
a
whole
task
in
and
of
itself
yeah,
and
you
know
that
that
is
definitely
something
that
as
we
take
on
you
know
this
new
sort
of
responsibility
that
I
am
NOT
out
of
my
league.
A
But
out
of
my
capacity
to
to
really,
you
know,
continue
to
think
to
drive
because
the
the
set
up
organization
of
the
meet
up
and
then
running
the
meet
up.
You
know
it's
probably
20
hours
of
fiddling
and
work.
It's
just
just
to
get
that
that
up-
and
you
know
realistically,
if
you're
gonna
do
a
good
job
of
promoting
and
getting
the
word
out.
You
know
we're
gonna
need
to
blog
post
we're
gonna
need
to
tweet,
and
you
know
social
media
posts.
B
A
A
I
mean
you
know
some
of
the
things
that
that
we
want
to
do
well,
first,
get
out
of
get
out
of
Twitter
right.
Well,
what
one
get
on
nodejs
Twitter
right!
There's
you
know
you
and
I
and
all
of
our
you
know
social
tweets.
But
you
know
the
nodejs
Twitter
is
super.
You
know
meaningful
and
as
a
huge
following,
so
you
know
making
sure
that
we're
scared
tweets
with
zippy.
A
B
A
C
A
D
A
A
So
you
know
in
sort
of
building
out
this
next
next
pass
of
promotion.
First
and
foremost,
we
need
to
give
ourselves
enough
time
to
promote
right.
Oh
you
know,
I
I,
don't
think
we
should
come
back
in
October
we're
going
to
be
all
at
node
plus
yes
interactive
anyway,
during
the
second,
you
know
is
right
there
in
the
middle
of
of
no
Jess
interactive,
and
you
know
the
we
can
give
ourselves
more
time
to
organize
and
more
time
to
promote
by
just
let's
schedule
for
for
November
at
the
earliest.
B
A
A
You
know
we
have
the
the
noches
brand,
but
you
know
it's
gonna
help
a
lot,
but
you
know
in
terms
of
you
know,
drawing
folks
in
and
directing
topics
of
conversation.
You
know
the
selection
process
that
we
have
is
it's
definitely
going
to
affect
the
you
know.
The
attendance
one
thing
that
that
you
know
I
I,
think
could
be
interesting.
I
haven't
had
had
an
opportunity
to
engage,
I,
don't
know
if
anyone
else
has,
but
the
node.js
foundation
did
just
kick
off
a
speaker's
bureau.
Has
anyone
interacted
with
that
yet
or
both.
B
B
B
A
B
I
mean
I
think
that's
that's
a
group
of
people.
What
I'm,
still
my
my
biggest
interest,
is
to
figure
out
how,
as
opposed
to
doing
presentations,
how
we
can
get
people
telling
you
know,
feeding
us
information
versus
the
you
know,
it's
it's
great
to
get
information
out,
but
I
think
our
biggest
challenge
is:
how
do
we
get
information
in?
Because
that's
sort
of
you
know
I
think
that's
for
the
user
feedback
team.
A
B
Right
exactly
and-
and
you
know
what
I
have
in
mind
is
not
necessarily
like,
so
presentations
may
be
the
way
to
do
some
of
that,
but
it
wouldn't
necessarily
be
from
the
community,
like
our
from
our
core
project
to
the
community.
We'd
want
to
engage
the
community
and
coming
and
presenting
on
a
topic,
that's
important
to
them
that
you
know
other
people,
but
plus
the
project
members
can
can
learn
about
it.
If
you
know
what
I
mean
yep.
B
B
I,
just
I,
just
you
know,
what's
raising
because
it's
easy
sort
of
fall
into
the
hey
here
are
the
easy
ones
we
can
get
just
want
us
to
keep
front
of
mine
that
we
want
to
get
to
that
point
where
we
can
find
some
people
out
in
the
community
there
and
say
hey
what
would
you
find?
What's
the
topic
that
you
know
think
is.
We
should
be
talking
about
right.
A
Yes,
so
in
setting
up
the
SF
node
meetup
model,
you
know
III
laid
that
out
as
having
one
advanced
topic
and
one
beginner
topic
to
make
sure
that
that
we
remained
beginner
friendly
and
as
well
as
you
know,
retaining
your
participation
of
more
sophisticated
end
users,
and
you
know
that
models
has
has
worked
well
for
many
years.
You
know
we
could
consider
something
similar
where
we
are.
You
know,
maybe
having
you
know
someone
from
core
or
someone.
You
know
sort
of
well-known
in
and
notes
basis,
plus
a
community
presentation
to
balance
that
yep.
B
Works
yeah
like
a
we
could
you
know
if
we
did
one
like
that,
and
then
you
know,
even
in
the
steady
state,
if
we
had,
you
know
one
which
was
a
project
to
community
and
then
at
one
which
was
community
to
project
that
would
that
still
might
be
a
fine
balance
but
and
I
agree.
Bootstrapping,
you
know,
could
be
a
little
different,
but
just
always
something
to
keep
forward
of.
A
So
I'd
like
to
talk
through
some
of
the
the
components
of
of
what
we
did,
what
worked,
what
didn't
so
the
the
meetup
is
structured
as
a
two-hour
event,
and
you
know
leveraging
some
of
that.
You
know
meet
up
style
socialization
and
you
know
using
that
to
you
know,
potentially
draw
out
user
feedback
discussions.
I
thought
the
the
initial
opening
round
of
discussion
was
was
quite
interesting,
so
you
know
rat
rather
than
you
know,
just
completely
opening
the
floor
and
and
getting
silence.
We.
A
We
went
around
and
had
everyone
introduce
themselves
so
I
think
we
had
10
to
14
folks,
you
know
live
at
any
one
time,
so
you
know
that
very
much.
You
know
that
was
solid.
20
minutes
of
you
know
about
as
fast
as
I
could
get
through
that.
So
you
know,
as
we
ratchet
up
I,
don't
know
that
that
process
will
scale.
Oh,
but
yeah,
that
was
a
nice
icebreaker.
A
B
I
I
agree,
and
if
we
do,
you
know
so,
for
example,
if
we
had
a
hundred
people,
we'd
have
difficulty
going
through
all
100,
but
I
would
still
say
that
you
could
pick
like
random.
You
know
and
we
could
say
that
up
front.
You
know
at
the
beginning,
at
random,
we're
gonna
ask
10
to
20
people
to
do
that
right.
So
we
continue
to
get
a
flavor
of
the
people
who
are
attending
and
what
they're
interested
in
and
why
they're
there
great.
A
In
terms
of
going
out
and
doing
the
outrage,
because
that
you
know
as
you're
setting
up
as
I'm
talking
and
you
know,
running
the
show
going-
and
you
know
reaching
out
to
vote-
and
you
know
it
in
chat-
I,
don't
I,
don't
know
that
we're
gonna
be
able
to
do
that.
So
real-time
spoken,
you
know
that
that's
gonna
be
challenging.
We're
gonna
have
to
go,
and
you
know
reach
out
to
folks-
and
you
know
ping
them
on
chat
like.
B
It
just
seems
to
me:
we
have
a
list
of
a
hundred,
we
could
say
well
we're
gonna
do
every
fifth
one
in
the
list,
assuming
it's
not
alphabetically-ordered
or
something
just
to
every
fifth
one,
somebody
you
know
you
could
do
the
intro
somebody
you
could
assign
somebody
else
who
just
looks
at
the
list.
First,
one:
hey,
Michael,
hey:
can
you
give
us
a
quick
outline
of
what
you're
doing
blah
blah
they're
done
next
one?
Next,
you
know
five
down
next
go
yeah.
A
A
A
A
A
A
B
And
and
and
maybe
we
should
wait
till
we
have
the
problem
of
having
too
many
like.
We
can
do
something
simple
like
that.
If
it
is
a
huge
number
of
people,
mm-hmm
and
I,
don't
know
it
did
like
you
know,
I'm
just
agreeing,
because
I
agreed
with
you
that
dot
like
I,
don't
know
it's
gonna,
be
very
difficult
to
just
have
an
open
conversation
right
right.
A
A
And
I
was
really
happy
that
we
had
Michelle
from
Microsoft.
You
know
there
to
listen
to
her
user
feedback
on.
You
know
Windows
system
issues
yeah.
That
was,
you
know
perfect,
like
that.
That
is
exactly
the
kind
of
thing
that
that
you
know
I'd
like
to
see
more
of
you
know
looking
for
feedback,
and
you
know
coming
and
engaging
with
folks-
and
you
know
it
it'd
be
nice
to
have
Michelle
come
and
present
next
time.
Actually,
that
would
really
that
really
sort
of
get
that
ball
rolling.
A
A
Then
we
had
our
two
talks:
Michael
Dawson
shared
an
overview
of
the
project
and
rich
trot
shared.
You
know
some
feedback
in
responses
to
Ryan
dolls
presentation
at
J's
confit
you
about
the
regrets
around
node,
really
good
presentations.
You
know
I
had
a
full
hour
on
that
and
we
basically
you
know,
took
up
that
that
that
whole
hour
with
with
two
talks,
I,
don't
think
we
can
get
any
more
than
those
two
talks
in
the
time
that
we
have
there
sorry.
A
You
know
it's
it's
it's
in
you
know
my
Twitter
backlog
and
I
just
go
there
and
look
for
a
notice
online
meet
up
cool,
so
yeah,
no
real
concerns
or
feedback
there.
You
know
my
big
biggest
takeaway
is
you
know
I
I'd
slot
it
in
you
know
two,
maybe
three
and
I
would
say
that
you
know
two
is
about
all
that's
gonna
fit
into
two.
It's
didn't
to
an
hour.
B
Just
my
earlier
one
that
like
try,
try
to
make
sure
that
some
of
them
are
on
the
the
broader
community
in
the
end-users,
presenting
on
issues
that
are
that
that
they're
facing
or
things
that
they're
doing
as
opposed
to
just
the
project
you
know
what's
going
on
in
the
project.
That's
awesome,
yeah,
that's
my
main!
You
know
that's
the
main
thing
can.
F
You
hear
me
guys:
yes,
okay,
so
I'm
still
aware,
with
the
two
hours
thing
I
in
my
my
opinion,
I
think
two
hours
kind
of
too
long,
I,
don't
think
so.
Many
people
from
higher
management
are
going
to
join
that
so
or
we
shouldn't
expect
people
to
stay
for
two
hours.
That's
for
sure
that
is
going
to
be
expected,
I
think
so
one
thing
it's
probably
or
just
put
a
note
guys,
it's
okay!
F
If
you
stayed
for
one
hour
bottle
and
before
before,
we
need
to
have
a
clear
agenda,
so
this
is
going
to
be
the
first
presentation.
This
is
going
to
be
the
next
presentation.
I
think
that
the
other
the
listing
should
be
a
minimum,
because
the
people
don't
expect
up
the
high
management
to
stay
for
two
hours.
So
that's
my
opinion
right.
A
No
I
agree,
but
I
also,
don't
think
that
this
is
necessary.
This
is
general
user
feedback.
So
I.
Don't
necessarily
think
that
you
know
that's
necessarily
our
target
a
target
audience.
You
know
that
matches
my
experience
and
you
know
just
meetups
as
well.
You
know
that
you
know
evening
time.
You
know
after
work,
you
know
very
you
know,
I'm
often
the
more
senior
yeah.
A
And,
and
and
the
in
you
know,
in
structuring
the
you
know,
the
meet
up,
you
know
that
that
time
before
is,
is
really
necessary
in
making
sure
that
the
the
presentation
is
a
good
experience
right.
It's
allowing
folks
to
get
in
get
settled,
you
know
usually
compensating
for
you
know
physically
arriving
at
a
thing.
We
don't
have
that
in
the
online
space,
but
yeah
that
you
know
we
always
have
in
these
meetings.
You
know
good
solid.
A
You
know
five
ten
minutes
before
we,
you
know,
can
really
kick
things
off
anyway,
so
we
may
be
able
to
shave
that
down,
but
that's
going
to
be
our
ability
to
say
you
know
at
this
time
you
want
to
just
come
swoop
in
for
talks.
You
know
come
at
this
time,
if
we
only
buffer,
for
you
know,
folks,
arriving.
A
Then
you
know
the
part
that
I
was
least
happy
about.
Was
you
know
the
final
half
an
hour
after
after
we
were
done?
You
know
that
is
a
bit
more
of
an
open
discussion
forum.
I
thought
I'd
squeezed
about
as
much
discussion
as
I
could
in
the
the
first
discussion
block-
and
you
know
we
had
a
few
things
to
go
through,
but
we
wrapped
up
I
think
about
15
minutes
early
like
that
10-15
minutes
early.
A
No,
so
you
know
that
that's
the
that's
a
space
where
you
know
I
I
thought
we
might
get
into
a
deeper
user
feedback
discussion
right.
We
could
mail
layer
in
specific
questions,
like
maybe
drop
some
survey
like
questions
at
that
point.
You
know
I
I,
don't
know.
If
the
you
know,
we
should
lean
heavily
on
that
side
of
things
or
try
to
include
that
those
sorts
of
things
at
the
beginning,
while
folks
are
getting
settled,
I.
B
Think
it
might
have
worked
if
the
topics
were
one
where
it
was
something
where
you
could
then
have
a
discussion
on
the
topic
afterwards,
mm-hmm
right
because
I,
don't
you
know
the
getting
involved,
you
might
have
like
discussion
about
hey
I'm
interested
Dave
dive
more
into
a
particular
area,
but
it
wasn't
like
a
topic
where
somebody
could
say:
oh
yeah,
that's
how
I
have
that
same
problem.
Let's
sort
of
dive
into
the
you
know
the
challenge
that
that
was
outlined
there,
mmm-hmm
so
I
think
if
it's.
G
Was
saying
I
think
that
tying
in
and
by
the
way
other
than
on
the
phones?
My
audio
works,
yep
I
was
saying.
The
tying
in
the
topic
is
key,
but
going
back
to
a
dance
point
like
as
far
as
a
higher
level
of
coordination
and
planning
and
doing
those
things,
and
then
he
can
do
the
survey
upfront
at
the
opening
and
then
keep
referring
to
it
as
the
topic
and
amusing.
As
the
talk
continues
to
re-emphasize.
A
B
Like
you,
could
you
know,
for
example,
if
you
think
about
promises
in
a
survey
you
could
basically
say
you
know
here
are
some
questions.
We
want
to
try
and
answer.
You
could
then
have
a
presentation
on
the
promises
and
then
that
would
lead
quite
a
bit
to
you
know,
basically
having
a
good
discussion
on
that
afterwards.
A
A
E
C
A
In
terms
of
the
questions
you
know,
the
the
folks
at
the
foundation
are
happy
to
help
us
do
that.
You
know
they.
They
spend
a
lot
of
time,
making
their
surveys
repeatable
and
systole
valid,
and
you
know
that
really
involves
a
fair
amount
of
work
in
crafting
questions.
So
either
you
can
get
a
good
guess
or
no
answer,
or
it
drops
into
a
you
know:
multiple
choice.
You
know
that
that
can
be
consistent
over
multiple
surveys.
You
know
open-ended
questions,
and
you
know
lots
of
broad
variation
in
topics
are
really.
A
You
know
not
the
best
fit
for
for
surveys,
so
that
there's
a
bit
of
shaping
and
validation
that
needs
to
be
done
there
and
you
know,
then,
the
the
generation
and
creation
of
of
the
survey
we've
chosen
to
have
the
nodejs
foundation
hosts
and
run
the
survey,
because
through
that
we
can
ensure
user
privacy
and
we
don't
have
to.
Since
you
know
the
know,
jess
and
linux
foundation.
Contractors
have
you
know
a
specific
contract
with
the
organization.
A
A
There's
a
a
typescript,
strong
typing
survey,
request
that
you
know
we
requested
back
in
May,
but
hasn't
you
know,
really
generated
that
momentum
as
we
saw
with
with
promises,
and
you
know
it's
going
to
need,
you
know
needed
sort
of
the
development
of
you
know.
What
are
the
questions
that
we
need
to
ask
and
you
push
that
a
little
bit
further.
So
you
know
there's
not
quite
enough
there
to
sort
of
take
on
the
challenge
or
get
critical
mass,
but
we
could
definitely
schedule
something
with
those
folks
and
continue
that
conversation.
G
My
only
my
only
worry
with
that
topic
is
it's
too
broad
mm-hmm.
How
do
we
narrow
it
down
something
meaningful
that
can
be
action?
What
I
mean
by
that
is,
you
know
strong
typing
in
a
programming
language
as
a
general
topic,
it's
not
so
much
about
typescript
IntelliJ
is
just
some
typing.
It
seems
to
be
the
kree
a
skier
right,
the
very
broad
topic,
I.
G
To
I,
don't
know
what
a
good
idea
to
narrow
it
down,
so
it
can
be
actual,
but
it
sounds
like
you
know.
It
might
also
be
a
risk
of
bit
of
a
opinion
ORS.
If
you
open
up
that
conversation
saying
you
know
who
wants
typescript,
who
doesn't
want
a
script
and
then
it
doesn't
really
drive
a
discussion.
You
know
it's
beating
law,
but.
B
I
Drive
it
more
and
like
in
terms
of
the
survey
I
think
it
was
driving.
It
was
trying
to
get
a
better
feel
for
how
much
usage
there
is
out
there
and
possibly
like
if
there's
different
things
that
you
could
imagine
doing
a
node
that
would
support
typescript
or
not
what
level
of
supporter
demand
there
would
be
for
those
like,
for
example,
would
it
be
useful?
B
I
mean
I,
know,
bindings
are
maintained
separately,
but
should
bindings
be
bundled
in
with
no
and
I,
don't
know
if
that
makes
sense
or
whatever,
but
that's
the
kind
of
question
where
you
could
see
asking
people
and
you'd
have
to
come
up
with
some.
You
know:
I,
don't
you'd
want
to
pull
out
some
subtleties.
Like
you
know,
do
you
see
value
in
it
being
bundled
in
versus
pulling
it
out
from
a
separate
module,
but
we
could
I.
B
Think
there'd
be
some
things
that
once
you
had,
that
dated
back
should
be
quite
interesting,
but
you
are
right.
You'd
have
to
be
quite
careful
in
terms
of
the
questions
like
it's
I
wouldn't
be
saying:
hey
you
know,
do
you
are
you
for
or
against
typing
right?
It's
it
would
be
more
like
you
know,
would
it
add
value
to
you
if
there
was
typing
supported,
you
know,
or
something
I
mean.
G
B
A
Got
it
so
yeah
I
was
gonna
reference,
the
46%
of
MPM
users
are
using
typescript.
You
know
when
I
first
yeah,
that
which
is
a
number
that
Laurie
has
been
sharing
recently.
You
know
I
originally
interpreted
that
as
46
percent
of
packages
in
NPM
are
using
typescript
and
that
isn't
absolutely
not
what
that
number.
That
number
is
yeah.
A
A
G
So
we
left
this
conversation
a
while
ago,
but
with
the
context
of
node
and
Jas
Interactive
coming
around
the
calendar,
so
that's
very
close,
but
not
too
close
so
October.
There
are
please
everything
around
there.
So
I
want
to
solicit
some
ideas
as
or
not.
We
should
tie
those
things
together
or
keep
them
separate.
G
Same
time,
right
just
thinking
out
loud
as
we
have
a
big
collective
of
nodejs
users
in
the
enterprise
space
coming
to
a
big
conference,
is
there
more
meaningful?
There
are
reasons
to
actually
invest
more
energy
and
trying
to
do
something,
perhaps
in
person
or
at
the
events
or
adjacent
to
the
events
to
be
more
accident.
G
A
I,
like
that,
a
lot,
that's
that
you
know
I
I,
think
a
great
way
to
build
the
conversations
and
we'd
you
know
feed
what
types
of
conversation
folks
want
right.
It's
it's
not
a
lot
of
folks
are
are
used
to
this
mode
that
we
have
and
nodejs
of
like
putting
yourself
out
there
and
you
know
being
on
video
and
committing
to
a
thing.
You
know
that
can.
A
And
so
having
that
in-person
discussion
and
you're,
just
getting
folks
chatting
you
know,
mix,
makes
it's
on
a
sense,
and
then
you
know
potentially
coming
back
and
and
scheduling
in
you
know
in
the
following
weeks:
you're-
probably
not
too
far
off
that
maybe
at
the
end
of
October,
you
know
having
end
of
October
beginning
of
November
how
those
days
line
up
you
know,
don't
want
it.
Do
you,
you
know,
you're
gonna,
gather
momentum
and
you
know,
connect
folks
and
then
you're
gonna
want
want
to
give
them
a
date.
G
B
Mean
I
think
that's
that's
fair
enough
and,
like
our
whole
goal,
is
to
be
public
and
transparent,
but
I
don't
think
we
should
all.
On
the
other
hand,
I
don't
think
we
should
let
that
shut
us
off
from
feedback
from
certain
certain
cases.
So
you
know,
while
I
think
we
want
to
you
know
we
don't
want
most
of
our
stuff
to
be
private.
I
wouldn't
be
opposed
to
having
some
subset
of
the
calls.
You
know
more
private
if
that
helps
us
hear
from
more
people
right
right,
yeah,.
G
You
know
we
opened
it
up
and
we're
trying
to
get
it
going
and
by
people,
and
they
haven't
seen
it
or
gotten
to
understand
the
value
out
of
it.
So
a
bit
hesitant
to
be
participants
I,
don't
think
right,
facilitated
by
doing
doing
things
privately,
but
just
know
probably
defeats
the
purpose,
but
using
an
opportunity.
Like
the
conference,
that's
happening,
people
who
are
physically
there
we
do
have.
We
can't
have
that
opportunity
doing
something
else.
Physical,
get
together
and
show
them
that
there's
value
so
that
they
can
continue
contributing
different.
A
Austin's
point,
if
you
feel
like
you
know
folks
do
end
up
reaching
for
a
private
session.
You
know
the
pattern
that
we
usually
have
is
an
open
forum
and
then
we'll
go
and
you
know
carve
out
some
of
the
time
at
the
end
of
the
meeting
for
private
session.
So
you
know
you
could
schedule
it
that
way
too,
and
you
know
just
turn
off
the
live
feed
and
you
know
let
them
share
a
little
bit
more
openly
with
without
any
recordings.
G
A
B
G
B
D
A
Yeah
so
I
have
a
room
and
a
presentation
scheduled
I'll
get
the
time,
for
you
know
public
user
feedback
session.
Maybe
what
we're
gonna
do
is
piggyback
on
that
and
say:
hey
come
to
this
and
then
afterwards,
we'll
we'll
say
and
and
we'll
go
and
you
know
have
shots
together.
I
like
that
even
better!
Yes,.