►
From YouTube: Node.js Community Committee
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
B
I
can
go
for
mentorship
cool
yeah,
so
making
some
good
progress
on
the
challenge
for
examples
for
finding
that
mentee
we've
created
a
reference
solution,
API
that
does
a
lot
of
things
that
you
and
I
talked
about
Tierney
and
so
we'll
probably
get
that
turned
into
like
actual
challenge
repo,
along
with
the
the
you
know,
application
form
the
next
week
or
so,
which
is
pretty
cool
and
then
other
than
that
our
mentee
Adam
mola.
He
drafted
up
a
blog
post.
That
should
be
pretty
good.
B
C
Time
so
me,
so
our
updates
have
been
that
if
for
me
and
Ben
right
now,
what
we're
doing
is
we
have
been
doing,
instead
of
so
when
we
have
the
website
redesign
meetings.
Since
the
past
couple
of
weeks
we
haven't
been
getting.
Anyone
has
just
been
me
and
Ben,
so
what
we
have
been
doing
is
we've
been
making
it
as
a
working
session.
C
So
we
work
through
issues
and
problems
that
we
are
trying
to
solve
and
we
have
been
pushing
to
get
our
to
get
new
members
and
and
spoke
with
me
and
Joe
actually
had
a
conversation
last
week
about
it,
Joe
cat
villain
and
we
have
been
trying
to
see
what
what
ways
we
can
actually
get
more
people
involved.
So
we
have
been
clearing
up
issues
but
also
been
trying
to
solve.
You
know
the
issues
that
are
already
exist
for
us.
D
Yeah
I
would
say
in
terms
of
getting
new
folks
in
I,
think
that
the
best
thing
to
do
would
be
to
have
clear
on-ramps
for
folks
who
are
getting
started
and
I
know
that
that
takes.
You
know
some
efforts
and
planning
some
some
kind
of
working
through
where
you're
at
in
different
areas
and
having
issues
clearer
for
folks
to
jump
in.
D
If
you
want
to
talk
about
that
pigmy
offline-
and
you
know,
if
you
feel
like
you,
have
that
in
place
or
when
you
feel.
If
we're
when
let
me
know
and
I,
can
try
to
help.
You
know
drive
some
more
folks
to
the
effort.
You
know
knowing
that
there's
clear
ways
for
them
to
get
involved.
Sure
we'll
do
great
thanks,
Divya
I,
think.
E
Also
be
taking
you
up
on
the
some
time
soon
Joe
to
work
towards
active.
You
know
more
active
participation,
but
I'll
give
an
update
on
the
internationalization
efforts
kind
of
break
down
real
quick
between
the
three
concerns,
which
are
international,
localization
and
globalization.
So,
on
the
internationalization
side,
we've
had
some
steady
work
on
the
infra.
Things
were
pretty
much
set
up
between
crowd
in
and
in
our
repository,
but
there's
a
long
way
to
go
to
you
know,
have
a
steady
integration.
E
You
know
getting
a
better
contributing
guides
and
funnels
for
localization
participants
to
get
involved
primarily
through
crowding
is
the
best
way
so
I'm,
imagining
like
you
know,
making
a
contribution,
documentation
and
videos
and
that
sort
of
thing
or
just
making
a
contributing
guides
better
is
a
good
first
step,
but
people
are
gonna
since
they're
not
gonna,
be
living
in
github
they'll
need
you
know
something.
A
little
bit
more
accessible
for
them.
You
know
there
are
other
resources
like
how
to
manage
a
localization
group,
etc.
E
Things
like
that
and
then
after
that
the
general
outreach
and
funneling
into
you
localization
work
and
then
on
the
globalization
side.
Steven
Lewis,
who
has
been
one
of
the
sole
folks
working
on
I,
see
you
in
node
is
shifting
focus
since
he
has
left
IBM
and
is
now
working
in
Unicode
or
working
on
contract
Unicode.
So
he's
gonna
be
working
primarily
on
the
cldr
project,
but
and
he's
trans.
E
We
are
transferring
ICU
modules
or
there's
an
issue
open
issue
and
it
seems
like
he
has
general
approval
and
consensus
that
we
can
transfer
some
of
the
ICU
modules
that
he's
been
working
on
into
the
node.js
project.
However,
that's
going
to
create
the
need
for
sparking
more
reciprocity
around
supporting
ICU
and
though
so
we're
going
to
be
working
I
and
hopefully
other
people
will
be
working
with
Steven
to
create
contributing
resources
to
get
involved
with
you
know
it's
like
maintain
better
participation
for
globalization
and
node.
E
F
A
I
have
a
cow
I
have
a
couple
and
like
I,
also
don't
know
where
the
realization
probably
update
I
like
I,
normally
shoved
moderation
into
like
this
space,
so
I
will
quickly.
Do
moderation
then
also
do
social
team,
since
that's
something
that
we
haven't
really
established
like
a
process
for,
but
it's
something
we
should
probably
do.
A
Let
me
open
up
the
moderation
log,
real,
quick,
just
quick
log
update,
as
as
we
are
supposed
to
do,
we
blocked
up
a
bot.
We
took
a
few
actions
against
a
specific
user
in
moderation
issue.
Three
five:
four:
we
received
a
CSE
report
from
a
user
regarding
interaction
on
social
media.
We
received
a
email
to
note
the
report
email
address
about
the
OLM
page,
asking
if
we'd
be
willing
to
expand
it
to
the
important
prod
and
decided
not
to
engage
after
this
discussion
with
the
team
block
to
spam.
A
A
So
there's
two
people
and
the
workload
is
spread,
which
is
nice,
I,
think
we're
still
relatively
getting
a
grip
on
things,
I'm
trying
to
figure
out
to
kind
of
approach
it
as
a
project
voice
rather
than
a
foundation
voice,
because
very
fundamentally
different
things.
I
think
we're
doing
an
okay
job
so
far,
and
I
would
also
like
to
share
that
there
is
now
the
tweet
repo
I
have
gone
through
and
set
up
the
proper
tooling
gone
through
and
connect
to
the
API
stuff.
A
So
that
is
now
a
thing
that
works.
If
say,
someone
wants
to
tweet
hey.
We
have
good
first
issues
in
internationalization
or
something
else.
You
can
just
go
ahead
to
notate
a
slash
tweet,
there's
a
tweets
repo,
so
it's
tweet
slash,
tweets
I
like
tweets
I,
don't
know
why
that
just
I
love
that
so
much
I
works
like
that.
But
yeah
you
just
create
a
dot
tweet
file
and
there's
you
know
basically
guiding
the
readme
there
and
it
will
the
readme
of
that
subdirectory
and
it'll
kind
of
guide
you
through
how
to
do
that.
A
A
D
Say
on
this
topic
real
quickly
that
we're
trying
to
figure
out
certain
things
about
like
whether
we
should
have
like
a
digest
or
anything
like
you
know,
Michael
you're,
on
the
call
and
there's
always
stuff
to
you,
know
the
different
meetings
and
things
like
that.
We're
trying
to
figure
out
the
best
way
to
promote
those
and
maybe
pre,
promote
those
rather
than
post,
promoting
things
like
that.
So
we're
just
wanted
you
to
know
it
specifically
Michael
that
we're
thinking
about
these
sorts
of
things,
yeah.
G
B
G
It's
it's,
you
add
them
all
up
for
across
all
the
meetings.
It's
actually
a
fair
amount
of
interaction,
so
I
think
it's
good
to
make
sure
that
we
keep
promoting
those
and
letting
people
know
that
they're
there
and
they're
open
and
because
that's
sort
of
one
of
our
core
values
is
like
to
make
sure
it's
open
and
transparent.
Yep.
A
Yeah
so
Joe
and
I
have
been
talking
through
a
few
different
ways.
We
can
do
this
and
I
think
you
know.
One
way
we're
talking
about
is
doing
a
skit
like
tweeting
out
the
schedule
at
the
beginning
of
the
week,
and
then
you
know
with
thinking
through
various
ways.
We
can
kind
of
thread.
The
context
together
is
kind
of
a
batch
rather
than
like,
incrementally
doing
it
throughout
the
week
and
they're
having
having
it
be
more
noise
for
folks
rather
than
signal,
if
that
makes
sense,
yeah.
G
I
do
that
I
do
think.
There's
some
value
like
you
know
if
somebody
stepped
up
to
be
the
lead
of
a
particular
working
group
or
something
there's
some
value
of
helping
them.
Why
you
know
like
it,
it's
kind
of
like
the
releases
that
we've
had
recently.
It
would
be
good
if
the
releasers,
who
did
the
work,
were
the
ones
who
got
who
did
the
message
and
got
the
tweets,
because
sometimes.
A
F
G
E
Two
things
in
the
tweet
repository
that
maybe
we
could
add
more
language
around,
which
is
like
the
use
of
images
and
gifs
and
videos
might
be
a
thing
also
like
I,
don't
see
a
lot
of
right
language
around
retweets
so
like
if
you
wanted
to
propose
a
retweet,
maybe
or
whatever
the
thoughts
around
that
might
be.
You
might
have
already
discussed
it.
I
don't
know
yes,.
A
This
is
brought
up
in
in
Michaels
stuff.
The
current
tule
I,
don't
know
like
you,
I,
don't
think
the
tooling
right
now
currently
supports
retweets
but
like
if
that's
something
and
you're
totally
right
that
we
could
have
better,
maybe
perhaps
better
language
around
this
one
of
the
things
that
I've
been
suggesting.
People
do
and
I
can
document
that
here
is
just
putting
that
in
the
Z
Channel
the
nodejs
social
Channel
in
open
jazz
foundation.
A
G
Why
they
mentioned
me,
because
I've
been
posting
to
to
the
various
meetings
that
are
happening
in
that
channel
is
so
but
you're
right
that
I
I
did
have
that
same
thought
that,
having
that
that
suggestion,
documented
I
mean
it's,
it's
it's
actually
a
nice
low
overhead
way
right
like
as
opposed
to
having
open
a
peer
or
anything
like
that.
So
I,
don't.
A
G
H
On
the
social
thing,
like
I,
think
not
saying
this,
as
we
should
definitely
take
a
look
at
it,
but
I
think
it
would
be
a
good
idea
to
kind
of
sort
of
look
for
feedback
using
the
Twitter
account
like,
for
example,
asking
people
which
was
the
last
project
a
bit
with
node
or
what
was
the
last
problem.
They
had
that
keeps
reoccurring
in
different
node
projects.
I
think
it
would
be
a
fun
in
you
know
more
social
way
to
use
it,
then
just
how
you
use
it
right
now.
Yeah.
F
A
Totally
agree
with
that
I
also,
one
of
the
things
I
would
try
to
avoid.
There
is
soliciting
a
bunch
of
feedback
and
then
not
putting
it
not
having
it
be
something
that
the
project
can
act
on
or
one
and
kind
of
making
people
feel
unheard
because,
like
if
you
know
we
say
hey,
what's
something
that
you're
hitting
a
pain
point
with
and
that
we're
not
able
to
actually
meaningfully
direct
that
to
you
know
relevant
folks
in
the
TSC
or
something
like
that,
or
have
them
actually
go
and
say.
A
A
H
Like
what
like,
what
I
meant
is
to
not
use
that
as
a
feedback
channel,
because
I
know
this
is
exactly
what
you
say:
I'm
going
to
reinforce
that
that
this
is
something
that
is
going
to
happen,
but
what
I
kind
of
meant
by
that
was
to
kind
of
resurfacing
what
people
are
doing
with.
Would
you
know
not
feedback
style?
But
you
know
what
are
you
doing
with
node
I
think
yeah?
H
A
D
D
I
think
I
think
to
like
to
Tierney's
point
the
way
that
we
could
have
it
be
not
just
like
an
open
call
and
then
I
would
not
do
anything.
But
if
we
you
know
Kyra
and
I
were
aware
sort
of
social
teams
we
should
be,
but
we
could
respond
to
different
people.
You
know,
hopefully
all
the
people-
and
you
know
say:
oh
that
sounds
great
or
whatever
you
know
so
that
there
is
some
engagement
and
not
just
this
random
call
that
doesn't
have
anything
Blom,
not.
E
Something
that
might
be
interesting
to
consider
like
with
integrations
between
you
know
like
like
an
integration
between
you,
know,
Twitter
and
slack
wherever
the
the
meaningful
dump
is,
but
somehow
it
would
be
ideal
if
there
were
a
particular
conversation
about
you
know
that
involves
a
particular
working
group
like
to
fund
all
the
responses
from
you
know
that
particular
tweet
to
a
particular
channel.
Like
the
you
know
like
the,
if
it's
a
within
the
website,
you
know
if
it's
a
tweet
about
the
website
to
have
that
end
up
in
the
website.
A
A
A
D
You
know
to
Ben's
point
I
think,
maybe
a
way
that
that
we
could
kind
of
go
down.
That
path
is
if
a
working
group
or
initiative
has
a
particular
question.
They
want
to
pose
number
one.
It's
always
great
to
have
the
person
you
know
from
that
group
tweeted
and
we
could
amplify
it.
But
if,
like
if
people
working
on
that
issue
are
prepared
to
follow
up
on
the
tweet,
you
know
like
say
if
it's
a
request
for
so
we're
working
on
a
survey
for
how
to
handle
unhandled
rejection,
promises
and
promises.
D
You
know
if
the
people
working
on
that
were
prepared
to
respond
to
people
that
tweeted
responded
to
the
tweet,
then
it
would
be
like
some
really
good
natural
engagement.
That
I
think
would
be
very
valuable,
so
I
think
along
those
lines.
We
should
encourage
initiatives
and
working
groups
to
consider
the
social
channel
or
a
resource.
As
long
as
we
are
prepared
to
engage
on
any
requests
that
they
may
have
yeah.
E
H
About
a
github
tag
that
you
know
something
like
you
know
like:
we
have
that
a
gender
tag.
How
about
something
like
that?
We
could
probably
use,
for
example,
like
I'm
thinking
of
a
very
specific
context
here,
like
in
the
web
design.
We
have
this
issue
or
PR
that
I
created
stuck
for
quite
a
while,
because
I'm
not
a
designer.
Probably
we
are.
We
don't
have
many
designers
on
there
contributing
and
we
want
a
Sweezy
icons
for
three
different
things
with
it.
H
You
know
a
flexible
license,
maybe
you
know
we
could
attack
that
issue
for
the
social
team
and
they
could
tweet
out
that
if
you
are
a
designer
and
want
to
contribute
three
icons
to
new
website
for
node.js
for
dev,
you
could
totally
do
that
on
this
thing.
I
think
that
would
be
quite
an
interesting
use
case.
Yeah.
D
And
I
think
that's
a
good
example.
I,
don't
know
about
the
tooling.
That
brings
the
tweets
right
into
the
issue,
but
I
think
if
we
reference
the
particular
issue
and
had
a
particular
request
and
the
team
working
on
that
we're
prepared
to
moderate
that
tweet
and
the
responses
that
come
to
it.
That's
exactly
you
know
what
I
was
thinking
as
well
and
I.
Think
was
a
good
use
case
and.
A
I-I-I-I
will
be
reiterate
my
caution
around
signing
people
up
signing
us
up
for
plans
like
this
that
we
generally
have
not
been
able
to
execute
on
in
the
past
just
because
of
inability
to
dedicate
and
time
and
energy
to
it
and
not
trying
to
be
a
downer
but
like
that.
That
is
something
that
I
have
experienced,
and
you
know
if
we
can
have
someone
who
does
that
work
great,
but
you
know
until
we
can
commit
to
getting
that
done.
A
H
Yes,
exactly
so
you
could,
you
know
automate
that,
for
example,
all
of
the
all
good
tag
particular
issues
for
social
team
to
look
at
and
they
get
aggregated
in
the
social
teams.
You
know
github
repository
and
they
can
just
pick
and
choose
and
tweet
something
about
them,
but
encourage
that
conversation
related
to
these
things
should
happen
or
not,
because
that
would
become
you
know
quite
redundant,
an
extra
load
but
social
team.
A
Is
the
thing
the
thing
I'd
say
there
is
that
that,
like
thinking
from
the
perspective
of
the
social
team
that
then
like,
if
I,
if
someone
puts
a
label
on
something,
I
have
to
go,
get
context
of
why
they
put
that
on
or
what
they
want
from
it.
Like
that
specific
set
of
context
or
I
have
to
go.
I
like
you
know,
I
have
to
just
say
like
hey.
A
Why
do
you
do
this
and
I
think
how
we
have
it
set
up
now,
basically,
is
either
you
come
and
put
submit
a
PR
which
you're
writing
you're
writing
the
thing
in
like
you're,
crafting
it
in
a
way,
that's
more
effective
to
what
you're
trying
to
communicate
or
you're
sharing
it
in
the
social
channel
which
you
know
is
getting.
You
know
it's
opt-in,
of
course,
but,
like
you
also
have
to
come,
share,
hey
here's.
A
H
A
A
D
D
We
are
one
of
the
main
things
we're
working
on
is
getting
the
board
seats
sorted
from
the
CPC
perspective.
We
potentially
have
up
to
three
board
seats.
There's
the
primary
CPC
director,
there's
like
a
secondary
one
as
well,
and
then
there's
a
third
one,
that's
tied
to
the
membership
program.
So
the
first
two
we
are.
You
know
our
active.
D
The
the
primary
one
comes
from
the
CPC,
essentially
directly
directly.
The
second
one
was
granted
to
the
nodejs
project
for
the
first
year,
and
you
know
we
discussed
that
beyond
the
first
year
and
I'm
gonna
make
it
more
open
to
the
entire
community
with
an
open
dais,
so
we're
just
clarifying
some
of
that
through
documentation
and
then
we'll
take
nominations
and
process
an
election
very
soon.
Hopefully,
in
the
next
couple
of
weeks
we
need
to
get
board
approval
on
Friday
and
then
can
kind
of
move
some
things
forward.
G
The
key
thing
to
mention
on
that
is
like
earlier,
you
know
the
first
year
the
node
project
got
one
of
the
representatives
represented
representatives
and
that's
not
the
plan
for
this
next
year
yeah
and
we
discussed
that
before
I.
Don't
think
it
should
be
a
surprise,
but
it
was
kind
of
just
the
you
know.
If
that
was
gonna,
be
the
case,
the
ask
was
to
let
people
know,
and
so
that's
the
case,
yeah
and
part.
D
Of
the
thinking
there
too,
or
just
part
of
it
and
that's
natural
is
that
note
is
pretty
active
and
the
work
that's
going
on.
So
you
know
it's
likely
that
we
would
have
a
couple
of
people
from
node
valence
here.
So
there's
still
a
very
good
option,
a
very
good
chance
that
it
would
still
be
a
millon,
but
regardless
trying
to
breeze
through
this
to
not
take
up
too
much
time.
But
one
thing
I
want
to
point
out
is
that
changes
to
digital
ocean
services
for
open
J's
foundation
projects.
D
They
recently
announced
that
they're
migrating
they're
free
for
open
source
accounts
to
a
credit
based
account,
so
I
think
notice,
one
of
the
places
that
that
that
is
used.
So
we
want
to
just
make
sure
that
people
are
aware
of
that.
We
don't
expect
that
they
will
get
charged.
But
if
anyone
does
get
charged,
if
you're
using
digitalocean
droplet,
let
us
know
and
we'll
get
that
so
yeah.
G
D
Going
through
here
updates
to
CLA
to
an
apache
ICL
asp,
CLA
is
being
worked
on,
we're
fleshing
out
the
individual
membership
program,
which
is
something
that's
you
know
started
in
the
node
foundation
and
it's
been
being
worked
on
for
a
long
time,
but
we
have
Sara
Chipps
as
a
champion
there
and
she's
been
doing
really
great
work
at
moving
that
forward.
So
that's
really
exciting.
The
third
board
seat
is
tied
to
that.
So
that's
also
very
interesting
and
then
kind
of
just
working
through
the
other
things
that
you
know
are
our
typical
cross-project
council
work.
G
From
the
like,
on
the
board
front,
there
is
a
board
meeting
this
week.
I
can't
make
it
but
I'm
syncing
with
Chris.
There
isn't
anything
that
I
know
specifically
that
we
need
to
bring
from
the
node
front.
But
if
there
is,
let
me
know,
the
one-pass
task
was,
like
you
know,
information
about
what's
going
on
in
the
membership,
so
one
thing
on
that
front
is
github
has
taken
over
an
PM's
membership
at
the
Silver
level
and
I
just
posted
the
link
to
the
current
members.
If
you
want
to
go,
take
a
look.
A
A
A
I
just
updated
the
doc
a
bit
just
because
there's
a
updated
issue
doc
there.
So
we
only
have
two
agenda
items
today.
There
I
guess
moving
into
the
agenda.
We
only
have
two
agenda
items
today.
We
have
the
champion
for
the
website
I'm
currently
blocking
this,
because
champions
need
to
become
core
members
or
need
to
have
active
comp,
comm
member
as
a
liaison.
G
A
G
G
G
So
it's
kind
of
like
in
my
mind
either
either
we
think
that's
critical
and
then
we
kind
of
need
to
make
not
to
say
the
reporting,
but
I.
Think
in
my
mind,
was
like
the
supporting
the
effort
yeah
cuz
might
because
I
guess
where
I'd
go.
The
other
way
is
if,
in
terms
of
reporting,
we
could
change
it
so
that
the
champion
is
somebody
who
regularly
comes
to
the
calm,
calm
meeting
and
provides
an
update
and
and
I
think
we
have
that
yeah.
I
E
If
there's
a
for
whatever
reason,
there
is
a
problem
with
you
know,
the
liaison
thing
I
think
there's
enough
crossover
with
internationalization
that
for
some
kind
of
time
period
until
some
you
know
until
we
find
someone
who
would
like
to
champion
you
know
I
would
be
happy
to
report
what's
going
on
in
the
website
redesign
but
yeah.
What
were
you
gonna
say?
Might
I.
G
E
A
Yes,
I
mean,
if
you,
if
you
want
to
step
into
being
the
Billie's
on,
then
it
doesn't
like
dairy.
You
know
that
doesn't
necessarily
mean
you
need
to
report
it
but
like
if,
if
folks,
who
were
actively
and
they're
doing,
the
work
are
but
just
being
there
as
a
resource
for
them
and
being
able
to
communicate
their
needs.
E
In
order
to
understand
the
crossover
between
how
we're
gonna
create
meaningful
milestones
for
internationalizing
stuff
on
the
website,
so
I'm
gonna
be
there
in
some
regard,
anyways
some
time
soon.
So
I
think
like
it
makes
sense
in
this
time
period
you
know
and
I
guess
we
can.
We
could
revisit
as
time
you
know
goes
on.
It
would
be
nice
to
see
you
hey
Ben.
C
Quick
take
if
you
want
like
I
could
I
could
assist
you
as
well
cuz
right
now,
like
I,
you
know
help
out
with
all
the
website.
Redesign
meetings
right
now
and
and
I
am
always
like
at
the
compound
meeting.
So
if
you
want
like,
we
could
I
could
fill
you
in.
If
it's
anything
and
we
could,
we
could
kind
of
do
like
a
you
know.
We
could
take
it
offline
and
I
could
fill
you
in
with
what's
happening.
What's
not
know,
yeah.
D
E
I
A
A
Well,
lead,
it
is
the
one
about
the
collection
we
discussed
this
last
week
a
bit
and
basically
generally
in
the
meeting,
said
we're
okay
with
the
suggestions,
their
suggestion
or
suggestions
and
are
fine
generally
fine
to
move
forward
with
them.
We,
you
know,
didn't
really
get
any
more
feedback,
so
I'm
gonna
say
that
that's
generally
approved.
A
F
I
was
not
in
that
meeting.
Sorry
I
just
thumbs
up
from
Joe,
because
we
discuss
some
things
in
like
weeks
some
weeks
ago
about
how
we
can
improve
but
I.
Think,
though,
things
can
be
done
separately,
then
this
step
we
can.
We
can
move
forward
from
here
and
if
we
want
to
improve
like
adding
the
blog
of
a
new
flip
side
that
can
be
discussed
as
a
separate
discussion.