►
From YouTube: Node.js Community Committee Meeting
Description
A
C
C
There
have,
to
be
honest,
the
last
couple
weeks,
I've
been
relying
on
Zeke
and
and
other
folks
that
are
really
active
in
that
and
they've
been
trucking
along
and
tracking
along
I've
been
sort
of
in
preparation
for
like
having
another
kid.
Oh,
so
that's
like
kind
of
just
get
getting
along
here,
but
yeah
I
think
it
seems,
like
things
are
starting
to
stream
in
and
I'm
definitely
getting
a
crowd
and
alerts
for
translation.
So.
E
E
Caching
and
then
everyone
followed
him
to
his
next
sessions,
but
I
was
able
to
have
some
really
interesting
dialogue
with
some
folks
that
are
responsible
for
an
event,
LGS
Congress
and
they
expressed
an
interest
of
potentially
doing
some
user
feedback
tied
to
our
next
diagnostic
stomach,
which
the
VA
team
will
be
hosting
in
Munich,
apparently
in
February
of
next
year.
So
either
before
after
that,
we're
gonna
collaborate
to
do
some
outreach
to
bring
in
some
folks
specifically
around
talk
but
have
Diagnostics.
E
Diagnostics
of
it
so
the
Diagnostics
working
group,
we
did
a
diagnostic
summit
in
Ottawa
at
the
IBM
office
and
the
gathers
and
folks
together
to
collaborate
on
the
state
of
Diagnostics
in
the
platform,
and
it's
many
of
the
folks
that
are,
you
know,
responsible
for
the
the
VM
working
group
and
the
NI
BI
stuff.
So
it's
been
a
good
collaboration
amongst
a
bunch
of
folks
that
are
no
active
members
there
and
yeah
so
good
good
to
get
a
broader
community
participation
in
these
sessions.
F
A
E
Can
I
add
something
to
the
mentorship?
We
are
also
looking
for
more
mentors.
So
if
you
are
interested
in
getting
involved,
I
was
cajoled
and
coerced
into
signing
up
as
a
mentor
for
the
community
committee.
Most
of
the
the
mentors
are
from
signal
side
of
the
house
and
so
I'd
love
to
see
folks,
if
you
have
any
spare
cycles
that
are
helping
folks
come
in
and
become
active
collaborators
in
the
community.
E
F
A
Way:
okay,
okay!
Well,
if
there
are
no
other
initiatives
to
chat
through
right
now,
just
start
moving
into
the
agenda
for
the
meeting.
My
notes
are
a
little
bit
right
here,
but
I
think
the
first
one
is
individual
memberships
subgroup
meeting.
This
is
issue
number
337
in
the
community
committee
and
I
just.
A
G
D
Okay,
that
happened,
that
meeting
happened.
We
went
over
context
previous
context,
you
know
what
is
what
mean
we've
begun
to
try
to
dress
all
successful
I.
Don't
think
we
got
there
yet,
but
we
did
actually
end
up
with
a
pretty
substantial
set
of
what
we
think.
We
need
to
begin
to
do
to
actually
really
build
out
success
criteria.
That's
in
the
minute
stock,
that's
linked
at
the
top
of
that
issue.
D
I'm
sure
I
can't
pull
that
up
right
now,
but
you
know:
there's
a
pretty
substantial
I'm
going
to
work
and
I
think
we
have
a
pretty
solid
foundation
for
the
next
meeting.
I
did
send
out
a
doodle
to
the
group
who
expressed
interest
and
to
the
calm,
calm
as
well,
I
think
in
total,
so
that
that
meeting
will
be
coming
up
this
not
next
week
but
the
week
after
that
I
believe,
and
so
we
will
be
able
to
begin
to
dig
into
that
even
more.
There
I
don't.
A
D
Don't
think
is
any
updates
exactly,
except,
for
you
know,
you're
interested
in
participating
that
more
please
come
about.
We
really
appreciate
it.
This
is
something
that's
gonna,
you
know
be
a
compound
project
or
not
be
a
partner.
That's
what
we
decide
to
do
in
terms
of
like
sunsetting
it,
but
that
you
know
in
that
meeting,
actually
discuss
some
some
of
the
ramifications
and
implications
of
what
that
would
be.
If
we
did
come
to
sunset
it
so
yeah,
there's
some
interesting
stuff.
D
A
B
Right
I
went
ahead,
so
we
tried
to
keep
that
meeting
as
a
preliminary
meeting.
There's
as
Turney
said,
please
come
help
out,
there's
a
call
for
participants
and
I
believe
we
concluded.
You
know
this.
Is
you
don't
have
to
be
a
community
committee
member
or
anything
like
that
and
by
far
we
we
want,
like
the
TSC
folks
to
come
in
in
community
and
all
around
so
don't
feel
like
this
is
a
closed
group
and
that
that
was
kind
of
one
of
the
big
takeaways
that
I
wanted
to
echo
here.
Yeah.
A
Okay
to
the
next
point
begin
documenting
partner
communities
and
what
that
means.
This
is
issue
326
in
the
community
committee,
and
what
this
was
related
to
this
was
another
actually
that
B&B
started
just.
D
A
D
But
I
I
think
that
you
know
the
the
what
and
how
is
really
what
we
don't
have
yeah
and
that
you
know
that
includes
you
know,
defining
what
we
think
should
be.
You
know
a
partner
community.
You
know
our
events,
partner
communities.
Can
they
can
they
be
a
partner
community?
If
so,
what's
what's
the
benefit
there?
Why
would
they
want
to
be
a
partner
it
just
things
that
community
project
members
are
running
and
you
know
and
I
I
think
the
answer
to
that
we
came
up
with
is
yes
temporarily.
D
A
Yeah
I
think
one
thing
to
mention
about
this
is
that
I
definitely
see
that
there's
some
hunger
for
people
to
be
able
to
participate
in
communities
like
this
to
have
access
to
chats
and
be
able
to
to
join
in
so
the
like.
Definitely
the
interest
is
there
and
it's
just
about
defining.
What
are
what
are
the
requirements?
I
guess
how.
D
A
A
D
I
went
through
and
actually
graded
or
I
created
the
repo
and
I
believe
a
team
for
this.
Just
as
he
reached
out
to
me
and
said,
you
know
like
it
was
trying
to
get
help
on
it,
so
I
went
through
and
just
kind
of
helped
him
set
it
up.
So
I
believe
there
is
a
wishlist
repo
now
in
the
org
I've
not
taken
a
look
at
some
of
the
things
there
yet
like.
D
A
E
E
Next
Friday
yep
tomorrow,
but
the
the
following
week
and
we
are
gathering
some
folks-
we've
we've
begun
sort
of
delegating
and
empowering
members
of
the
community
that
are
participating,
bone
skull.
Christopher
is
taking
on
the
initiative
of
user
feedback
and
aggregating
feedback
around
tooling
and
has
begun
to
organize
meetings
outside
of
the
regular
cadence
of
user
feedback.
Very
happy
of
it.
How
that's
going-
and
we
have
two
groups
that
were
looking
to
sort
of
you-
know,
build
and
help
facilitate
meetings
around.
That
is
around
promises.
E
You
know
helping
out
Ben
and
others
that
that
are
looking
to
build
interest,
and
you
know
improve
the
the
platform
capabilities
around
promises
and
then
Achmed
is
a
note
in
there
who
is
the
chief
architect
over
tell
us
and
helping
him
draw
in
the
enterprise
user
community,
so
anybody
who's
interested
in
either
enterprise
or
promises
in
an
organizational
capacity,
and
you
know
drawing
and
end-users
around
that
we'd
love
to
have
you
join
us
next
week.
Thank
you.
E
E
E
That's
the
right
answer:
we'd
love
to
have
you
join
the
user
feedback
team
and
help
in
this
process.
We're
in
the
process
of
document
ending
that
and
we'd
love.
New
team
members
and
the
meeting
next
week
would
be
a
great
place
to
raise
your
hand
and
help
out
because
there's
a
lot
of
interest
here-
and
you
know
the
in-person
session
that
I
had
with
the
the
folks
at
Jazz
Congress
and
the
discussions
that
I
have
had
recently
with
little
Dan.
E
Who
is
on
the
tc39
committee
and
tc39
s,
interest
in
doing
similar
user
feedback?
There's
a
lot
of
interest
in
doing
that,
and
it
does
take
a
little
bit
of
facilitation,
but
it
I
find
it
really
rewarding
a
little
bit
of
facilitation
goes
a
long
way
and
we
always
need
more
folks
sort
of
helping
out
and
doing
outreach
to
make
sure
we
get
a
broad,
diverse
group
of
individuals
like
coming
and
joining
around
topics
that
need
feedback
so
well.
F
E
So
we
have
two
topics:
Enterprise
and
promises,
and
at
the
sort
of
internal
team
meeting.
This
is
not
a
public
session
focused
on
getting
useful
feedback.
This
is
a
team
session
about
setting
up
a
group
of
individuals
who
are
looking
to
gather
user
feedback.
So
it's
super
meta
and
it's
gonna
watch
this
face.
If
you're
interested
engaging
with
that
promises
story
in
a
subsequent
meeting,
we'll
have
a
public
user
feedback
session
where
we
want
to
engage
end
users
that
are,
you
know,
interested
in
seeing
improvements
in
the
platform
support
with
promises.
D
E
So
everything
that
we
do
is
all
know
streamed
on
YouTube,
but
you
know
we
have
regular
bi-weekly
every
two
weeks
we
meet
together
and
you
know
we'll
do
the
organizational
part
of
two
meetings.
Those
are
all
streamed
on
on
YouTube
like
we
did
with
all
our
meetings,
but
then
you
know
we
have
regular
meetings,
work
that
we
call.
You
know
public
meetings
where
were
inviting.
F
D
You've
done
a
great
job,
so
you
really
have
one
thing:
I
would
like
to
add
to
the
agenda.
I
opened
a
PR
not
too
long
ago.
It's
a
quick,
quick
I,
wouldn't
call
it
a
straw
man,
but
it's
a
quick
draft
like
I
was
talking
about
for
the
external
communities,
except
it's
for
calm,
calm,
member
onboarding
just
to
be
able,
because
I
I
know
we
have
a
lot
of
knowledge
that
is
contained
in
our
heads,
went
on
a
slowly
written
down,
including
stuff.
D
It
would
be
super
helpful
if
you
could
all
share
your
own
experiences
and
like
the
things
that
caught
you
up
with
pom-pom
members
joining
you
know,
even
from
when
I
joined
the
compound
it's
very
different
now
than
it
was
then,
so
it
would
be
super
helpful
to
get
your
input
on
that
and
get
add
things
to
it
and
be
able
to
make
it
a
complete
document.
So
I
just
want
to
get
everyone's
eyes
on
that.
It's
it's
a
it's.
The
latest
PRI
bleep
in
Tom,
Graham,
repo.
C
A
C
Know
Ming
Becker
coming
back
around
super
late
to
this,
since
we
did
an
initiative
updates
in
the
beginning,
I
was
a
little
frantic
when
I
got
in,
but
I
did
want
to
say
a
really
cool
update.
That
happened
recently
was
I
connected
with
little
Dan
Dan
in
tc39
and
we're
starting
to
see
cross-pollination
between
the
ECMO
4:02
meetings
I've
been
joining
in
there,
and
so
hopefully
we
can
represent
more
of
the
concerns
of
internationalisation
for
JavaScript
within
them.
D
C
Icu
these.
These
things,
you
don't
really
think
about
until
you
have
to
think
about,
like
the
internationalization
of
character,
sets
within
a
language
standard
and
how
that's
defined
so
TCE
area.
Ecmo
402
is
the
organizational
body
that
governs
the
specification
for
internationalization
within
JavaScript
and
there's
there's
sort
of
he
Dan
joined
us
when
we
were
at
the
collaborators
summit,
and
we
also
have
Steven
Loomis
in
our
group
too.
C
Who
is
a
member
of
the
TC
for
the
402
group,
so
we're
sort
of
in
a
period
of
time
where
we're
thinking
about
you
know
how
are
you
know,
we're
sort
of
representing
what
that
is
for
node
I
feel
like
within
our
working
group
at
the
moment,
since
it's
not
really
it's
not
really
like
discussed
in
other
places
like
in
the
TSC
as
far
as
I
can
tell,
but
it's
just
a
conversation
we
needed
to
explore
more
and
solidify.
As
far
as
how
we
you
know,
keeping
things
up
to
date
with
the
402
standard,
so.
D
G
A
E
There
are
couple
you're
watching,
but
there's
no
questions.
Okay,
yeah
just
shares
a
little
bit
more
stuff
about
the
ACMA,
not
tc39,
but
ACMA.
So
on
Tuesday
I
was
at
the
actually
Wednesday.
Was
the
General
Assembly
meeting?
Sorry
it's
couple
days
so
I
joined
the
the
General
Assembly
ACMA
is
in
a
real
tc39
is
a
real,
interesting
spot
where
you
know,
Aetna
is
kind
of
going
through
growing
pains
and
you
know
priorities
and
investments
in
standards
are
shifting
in
the
community.
E
The
Jazz
foundation,
however,
was
was
able
to
join,
and
you
know
III
think
that
no
no
Jess
foundation
should
make
the
effort
as
well
to
join
there,
and
you
know
kind
of
help,
move
the
state
of
you
know
the
entities
that
are
involved
in
tc39,
you
know
Ekman
would
love
to
see
their
membership
grow,
but
you
know
I,
honestly,
think
that
you
know
knowing
from
my
experience
at
note
source,
you
know
allocating
a
bunch
more
time
of
folks.
You
know
going
and
participating
in.
E
D
D
So
they
well
I've
talked
to
several
people
about
this.
Who
are
companies
who
sit
on
you
see
there
and
actively
attend
those
who
are
contributors
note,
and
they
said
it's
theoretically
impossible,
so
yeah
I'm.
All
for
that.
That's
a
lot
of
work
that
we
basically
have
to
kind
of
have
them
help
us
update
their
policies
or
whatever
yeah.
G
C
You
know
not
just
standards,
body
people
or
you
know
a
certain
vector
of
folks
like
they
they're
looking
for
more
diversity,
and
we
can
also
provide
that
on
in
individual
levels
as
we're
moving
towards
getting
the
node
fountain
or
the
node
foundation
integrated
within
that.
So
I
think
it'd,
be
you
know,
look
into
it
and
then
see
if
you
want
to
represent
there.