►
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
A
Mean
I
guess
I
can
talk
about
an
internship,
that's
what
we're
talking
about
awesome,
sure
yeah.
So
these
last
two
weeks
is
a
pretty
big
for
a
mentorship,
because
we
got
our
first
like
new
onboarding
through
the
whole
process.
So
we've
gone
through
the
call
for
applications
got
a
whole
bunch
of
applications.
A
Think
yeah
look
at
30
somewhere
between
20
30,
set
up
criteria
for
how
we
wanted
to
evaluate
them.
Then,
as
you
know,
team
we,
we
went
through
basically
cut
down
to
the
shortlist
based
on
you
know
who
you
know
qualified
or
didn't
right.
So
one
of
our
big
price
criteria.
For
for
this
one
was
communication,
and
so
during
the
application
they
had
a
lot
of
opportunities
to
write
a
lot
and
just
show
off
that
they,
you
know,
could
articulate
about
themselves
and
and
other
more
I
guess
hard
cutoff
one
that
was.
A
Could
they
set
up
a
github
repo?
Could
they
create
an
issue?
Could
they
create
a
pull
request
that
closed
that
issue?
Things
like
that.
So
we
went
through
the
list
first
and
did
a
filter
pass,
and
so
anyone
who
couldn't
set
up
the
repo
or
you
know
gave
like
a
one
one-line
answer
or
something
to
our
questions
and
then
from
there
we
had
the
shortlist
and
then
we
ranked
them
and
we
came
up
with
our
decision.
A
So
we
have
no
we're
gonna,
be
talking
to
our
new
team
member
tomorrow
at
our
first
meeting
since
the
the
decision,
which
is
pretty
awesome,
it's
Adam,
Ola,
Tsubaki
I,
don't
know
if
I'm
pronouncing
the
name
correctly
yet
they're
from
West
Africa,
I
think
which
is
pretty
cool
anyway.
It's
very
promising
to
go
through
one
iteration
and
so
then
we'll
be
getting
them
up
to
speed
and
then,
ideally
working
with
the
examples
team,
which
is
pretty
pretty
exciting,
awesome
cool.
B
Any
other
I
have
a
quick
update.
I
have
a
quick
update,
so
we
had
a
photo
website
redesign
team.
We
are
switching
to
bi-weekly
meetings.
Now,
instead
of
bi-weekly,
we
did
give
out
a
poll
to
our
group
of
people
like
the
developers
who
come
to
our
meetings.
The
poll
is
done.
We
are
still
we
have
two
options:
either
Thursday
at
4
p.m.
or
Friday
at
the
afternoon
at
12:00.
B
B
A
A
I'll
just
give
one
from
examples
to
effect:
I've
not
had
a
bunch
of
time
to
to
actually
spend
on
being
examples.
I
had
I
have
been
mostly
focusing
my
effort
on
trying
to
get
folks
to
submit
their
examples
and
lowering
that
barrier
rather
than
doing
like
shouldering
to
work
myself.
So
you
know
I've
spent
time
with
a
couple
people
in
the
project
who
either
maintain
a
different
project
who
could
potentially
create
an
example
or
who
worked
at
it
like
a
provider
that
you
know
would
be
interested.
A
It
should
be
an
example
for
that
provider,
like
their
destiny
for
subject
matter
expert
for,
like
a
different,
a
different
thing
like
a
paid
service,
which
is
include
like
in
the
scope
of
examples.
So
then
try
to
do
that
and
just
kind
of
following
up
with
them
to
make
sure
you
know
it's
potentially
helpful
to
get
that
in
and
I
haven't
made
that
progress
on
actually
getting
those
BRZ,
but
moving
toward
that.
So
that's
good
yeah.
D
I'll
just
add:
this
initiative
moved
from
node
up
to
the
open,
J's
foundation,
but
I'm
happy
to
say
that
user
feedback
has
a
user
feedback
survey
request
from
the
nodejs
project
regarding
unhandled
promises.
So
that's
kind
of
cool
share
that
a
bit
and
then,
if
there
are
no
other
initiative
updates
I
can
give
a
update.
That's.
D
D
D
D
We,
the
calm,
calm
and
focus
on
the
TSC,
did
not
have
an
objection
to
that
becoming
more
of
an
open
community
seats
to
any
member
of
any
project.
We're
still
working
out
the
details
of
that
from
the
cross
project.
Council
and
you
know
hopefully
we'll
have
more
progress
there,
and
the
good
news
is
that
you
know
node
is
very
active,
so
it
very
likely
could
be
another
person
from
the
node
project,
but
you
know
we'll
see
help
at
all.
A
A
A
Collaborator
QC
member
band
and
obviously
that
made
the
user
following
obnoxious,
insulting
offensive
issues
that
we
ended
up
word:
acting,
we've
locked
a
possible
fought
for
posting,
meaningless
content
that
didn't
make
sense
and
then
unblock
them
so
just
for
context
most
if
not
all
of
these
are
logged
in
moderation
issues.
So
if
you
do
want
to
audit
that
feel
free
to
go
to
the
moderation,
repo
I
think
the
exception
there
is,
there
wasn't
an
issue
for
the
500
errors
that
was
reactionary
as
it
was
happening.
A
A
A
Okay,
so
the
agenda
item
we
have
is
IOT:
google
account
access.
This
is
a
normal
thing
that
we're
supposed
to
do
often
or
well
every
year.
So
this
is
like
your
old
issue.
I
think
we
did
a
bit,
but
this
is
currently
undergoing
I
would
consider
this
more
as
a
heads
up,
but
there
it
does
look
like
there's
a
proposal
from
Brian
Warner
21
days
ago,
which
I'm
surprised
I,
guess
I
was
in
the
last
case
here
called
our
meeting,
which
makes
sense.
A
A
And
it
looks
like
that
has
moved
on
and
I
believe.
Brian
also
mentioned
this
in
the
open,
GS
foundation
meeting
succeeding.
So
I
think
this
is
progressing
and
I
guess
this
is
serving
bit
more
as
a
heads
up
right
now,
I
don't
know
if
we
still
need
the
agenda
on
this,
but
I
yeah
I'm,
any
any
opposition
to
taking
off
or
any
ones
taking
off
the
agenda.
I
don't
for
now
sorry,
it
doesn't
seem
like
there's
anything
to
update
here.
No.
A
D
Perhaps
a
related
question:
are
there
changes
happening
in
in
the
way
that
we
do
some
of
these
things
and
when
I
say
these
things,
I'm
thinking
about
calendars
and
the
meeting
generation
and
agenda
generation
kind
of
process,
the
question
was:
are
there
changes
that
need
to
be
done?
No,
are
there
changes
that
are
happening
like
I,
like
from
the
package
maintenance
work
like
a
man,
kind
of
bot
and
things
like
that
or
they're
just
happening
overall,
so.
A
I
think
changes
is
probably
a
strong
word.
It's
status
quo
right
now.
The
the
thing
that's
happening
is
package,
so
I
started
independently
working
on
a
tool
and
West
Todd
started
independently
working
on
a
tool
that
we're
both
get
up.
Actions
based
that
are
basically
meeting
generation
tools,
so
it
like
a
kind
of
server
acts,
mimic
a
replacement
for
the
tool
that
Michaels
built.
A
That's
brilliant
from
good
of
actions,
so
we
wouldn't
have
to
maintain
we've
maintained
a
yellow
file
and
then
our
templates
in
our
repo,
rather
than
in
be
centralized
the
one
that
Michael
Michael
has
I
believe
that's
the
create
meeting
notes,
there's
something
create
meeting
items
or
something
like
that
in
the
node
work.
I
I'm
kind
of
currently
start
like
I,
am
very
much
intent
on
working
that
I'm
currently
stalled
on,
so
that
yext
it's
the
way.
It's
set
up.
A
I
can't
really
test
a
PR
like
I
can't
test
if
it
works
or
not
because
of
how
the
release
of
cooling
is
set
up.
Basically,
with
kind
of
actions
you
have
to
include
node
modules
and
part
of
the
release
process
is
to
bundle
node
modules
in
the
release,
which
doesn't
work
for
be
ours,
so
it's
kind
of
like
gonna
catch
22
and
I'm,
mostly
waiting
right
now
for
a
fix
on
that
I'm.
Not
seeing
any
progress
on
that
recently
so
TVD.
A
It's
currently,
you
know
going
forward
as
normal,
but
that
is
something
that
does
exist
in
the
pkg
ejs
goetaborg.
It's
the
repos
called
meet
so
pkg
pkg,
jsg
/
me.
That's
what-
and
you
know
if
folks
want
to
contribute
to
that.
Please
do
you're
more
than
welcome
to
one
of
the
things
the
things
I'm
doing
on
that
are
just
reducing
the
JavaScript
penis
of
it
and
making
it
more
user
friendly
for
just
writing
work
down
in
text.
Oh.
D
Yeah,
thank
you
for
that
update,
yeah
I'm
reminded
of
another
update.
That
perhaps
is
an
initiative.
A
I
mean
so
the
current
status
of
that
is
that
it's
been
accepted.
It's
a
similar
to
moderation.
It's
a
admin
group
I,
don't
know
if
that's
the
real
term
for
it,
but
that's
the
one
I
can
think
of
it's.
Currently
an
admin
group
in
basically
manage
the
same
way
as
a
moderation
team.
You
have
to
have
unanimous
approval
from
calm,
calm
and
TSC
with
no
Midas
ones,
no
indirect
minus
ones
to
get
into
it.
A
Just
because
of
like
how
high
impact
it
is
the
platform
that
the
project
has
so
I
I
have
gone
through
that
process.
Now
and
I
am
the
only
member,
so
yeah
definitely
feel
free
to
take
a
look
at
that
I've
been
managing,
except
for
one
one
tweet
the
date
that
was
not
unscheduled,
I've
been
managing
the
no
jest
Twitter
for
the
last
week
or
so,
and
then
also
LinkedIn
and
Facebook
cool,
so
yeah.
A
Thank
you,
yeah,
sorry,
based
on
that
in
the
updates
section,
cool
any
I
think
we're
probably
done
with
the
auto
Google
account
access.
Any
other
comments,
questions
thoughts,
feedback
on
that
one
cool
that
is
removed
from
the
agenda
now
rejoining
compound.
So
this
is
an
issue
from
Rachel
white.
She
is
a
former
comb
comb.
A
Member
former
chairperson
and
former
Co
chairperson
of
the
pom-pom,
did
a
bunch
of
work
for
kumkum
and
is
requesting
to
rejoin
so
I'm
going
to
ask
comic-con
members
now
I
believe
we
have
one
two,
three,
four
five,
five
cool
we
do
have
a
quorum.
Is
there
any
objection
to
this
and
this
this
is
this
is
a
vote
so
I
guess
I
should
not
say
objection
I'm
going
to
do
a
vote,
I
guess
I,
don't
know
this
is
like
I.
Don't
think
that
the
way
vote
is
to
find
here
is
the
way
we've
typically
done.
A
A
It's
it.
This
is
like
a
weird
one
of
our
one
of
our
or
earlier
things
of
adopting
language
that
does
not
does
not
necessarily
follow
exactly
how
we
practice,
which
is
something
that
we
should
probably
update.
Okay,
cool
I'm,
not
seeing
any
objections
in
the
chat,
I
am
going
to
presume,
accepted
and
I'm
going
to
merge
this.
We
also
have
plus
ones
from
other
people
who
thumbs
ducks
so
yeah.
We
should
be
good
here,
I'm
going
to
merge
this.
A
I'm
just
leaving
a
comment:
real,
quick
and
I
have
merged
at
so
we
we
should
be
good
down.
I
will
I
will
take
the
steps
necessary
after
this
meeting
to
onboard
Rachel.
Yet
awesome
next
agenda
item
is
update
scope
of
nodejs
collection
608,
your
issue,
6
le
I,
am
NOT
I
hope
I
didn't
have
any
to
do.
Is
I'm
personally
I
do
enjoy
this
elite.
Oh.
C
C
After
that,
we
need
to
decide
what
we
do
about
the
initiative
itself
and
that
effort
self.
Do
we
keep
the
pod
we
archive
it
or
we
also
keep
initiative
alive
or
we
just
like.
Stop
it
and
notice
the
comm
come
members.
The
TSE
members
can
keep
approving
the
the
submissions
to
the
notice
collection
block
like.
E
A
A
A
E
E
To
speak
about,
basically,
we
need,
we
have
some
doubts
about.
What
we
should
should
supposed
to
do
is
the
length
page
on
the
home
page.
It's
basically
to
have
the
proper
set
up,
so
the
proper
info
I
think
everyone
agree
with
the
what
you
posted
there,
with
JavaScript,
open
source
and
everywhere
I
think
we
just
need
confirmation
and
I,
don't
know
just
hammered
catchy.
E
Yeah
for
this
issue,
particularly
I,
think
it
is,
but
since
you're
talking
about
marketing
test
for
home
page,
my
guess
that
we
could
also
review
the
entire
home
page,
you
know
if
there
is
something
that
you
wanna
rim,
remove
or
add,
I
think
it.
This
is
the
proper
issue
to
deal
with
all
the
change
that
you
won
on
the
home
page
I'm
going
to
post
hit
the
figmas.
So
if
anyone
I
wanna
know,
what's
the
home
page,
look
like
yeah.
A
I
think
so
one
of
the
things
I
know
we
did
early
on
was
we
kind
of
like
took
a
look
at
a
lot
of
what
other
projects
were
doing
and
minutes.
That
I
guess
is
the
kind
of
basis
for
what
we
were
gonna
try
to
do,
give
him
that
we
now
don't
miss
necessarily
have
the
we
do
have
some
time
right,
yeah
we
have
some
time
so
I
don't
feel
too
bad.
Taking
some
time
to
talk
about
this
is
everyone
else?
B
A
A
One
of
the
things
that
I,
you
know
we
did
early
on
was
going
to
kind
of
look
at
what
other
websites
do
the
email
saying
you
know
we
don't
really
have
an
email
thing,
but
maybe
perhaps
driving
people
to
the
open
to
his
foundation
slack
in
the
node.js
channels.
There
could
be
a
replacement
for
that
of
like.
Instead
of
setting
up
you
set
up
an
email,
let's
go
to
the
slack.
A
I
am
sure
people
are
going
to
very
strongly
disagree
with
me
that
that's
something
we
should
do
so
take
that
with
a
grain
of
salt
for
context.
That's
a
discussion
that
we've
had
for
years.
That
has
always
ended
badly,
so
be
cautious,
pushing
that
and
then
for
the
bottom
section
of
like
who's
using
it
right
now.
We
have
companies
there
in
this
staging
site
that
we
don't
have
in
the
production
site,
because
we
don't
necessarily
have
licensing
for
those
logos,
but
perhaps
a
different
way
to
frame.
A
That
is
if
we
can
go
to
projects
that
people
use
so
like
babel
or
web
pack
or
others,
and
follow
their
branding
guidelines
and
get
permission
from
them,
like
you
know,
get
get
+1
that
it's
okay
to
use
their
stuff
used
by
all
of
these
things
that
you
already
know
is
a
good
social
proof
in
the
same
way,
in
the
same
way
that
you
know
all
of
these
companies
that
you
already
know
miss
a
good
social
group.
So
that's
potentially
an
additional
thing
there
to
kind
of
get
more
more
content
in
their
journey.
E
A
Their
logos,
yeah
and
then
additionally,
perhaps
I,
don't
think
we're
here
yet,
but
perhaps
I
I
kind
of
wish.
We
had
our
release
notes
as
a
Jason,
feed
and
I.
We're
I
think
we're
very
far
out
from
that,
but
you
know
being
including
release
notes
or
the
most
recent
blog
posts
on
the
blog,
which
are
generally
release
notes
would
potentially
be
a
nice
addition.
E
A
E
A
Also
has
like
what
this
thing
is
and
how
to
learn
more,
and
you
know
multiple,
multiple
avenues
to
get
to
all
of
those
things
and
right
now
it
like
the
current
Sage
excite,
because
we
did
have
to
chop
it
down
a
bit
is
download
and
then
what
is
which,
like
I,
think
we
could
probably
hopefully
find
some
ways
to
kind
of
move
into
a
path
where
we
have
additional
kind
of
those
branching
paths
to
get
people
to
places
that
they
want.
I
mean.
B
A
A
F
A
A
A
B
So
would
it
would
it
be
more
beneficial
like
if,
if
like
for
the
next
website
redesign
meeting
there
is
discuss
because,
like
we
do
not
have
any
discussion
about
like
a
thoughts
about
it's
more
about
features
rather
than
like
you
know,
did
go
into
and
checking
out
with
the
design
and
all
that
stuff.
So
I
think
that
if
we
do
have
a
discussion
of
that
sort,
I
think
it
would.
It
would
be
beneficial
because
I
I
such
don't
want
to
finish
the
page
and
then
be
like.
B
Oh,
we
need
to
make
all
these
other
changes,
which
would
reflect
a
lot
more
so
because
I've
got
him
set
up,
but
I
haven't
actually
added
the
content
like
I
got
I
got
the
sidebar
and
then
the
main
page.
That's
all
I've
done
so
far,
because
I
wasn't
I
was
still
like
working
with
others.
Other
issues
as
well,
but.
E
B
I
really
I,
don't
I.
I.
Think
that
the
point
you
bring
up
is
very
good
because
we
have
so
many
people
working
like
that.
The
problem
I
feel
not
the
problem,
but
the
thing
is
happening
right
now.
Is
that
you're
getting
more
issues
and
features
fixed,
then
actually
figuring
out?
What
actually
needs
to
be?
A
I'm
happy
for
the
state
to
come
in
and
participate
in
that
way
and
I
could
probably
do
that
pretty
consistently
like
I
can
I
can
make
the
effort
to
start
coming
to
this
I
I
guess
you
know
you
brought
up
the
community
page
and
there's
not
like
really
a
heading
entry
for
that
right
now
and
I.
Think,
potentially
you
know
based
on
the
information
architecture
work.
We
did
like
that
massive
amount
of
work.
A
At
this
point,
cuz
like
we
do
have
content,
that's
not
just
selling
news
there,
but
going
through
and
doing
that
would
potentially
also
help
because,
like
the
community
page
I'm
sure
we'll
have
a
bunch
of
content
that
we
can
point
to
from
the
homepage
and
like
have
a
community
section
on
the
home
page
and
like
kind
of
get
people
out
into
that
part
of
the
site
as
well,
rather
than
just
the
base,
you
know
download
node
and
what
is
there?
Okay,.
E
B
One
other
thing,
I
just
came
to
my
mind:
do
you
think
if
you
want
to
get
more
user
engagement,
would
it
be
beneficial
to
include
some
stuff
from
like
note
school
or
something
like
that,
like
a
get
started
guide
or
like
somewhere,
people
can
actually
go,
and
you
know
learn
a
bit
more
about
node
and
do
things
like
I
know.
We
have
meet
ups
and
stuff
related
to
that,
but
in
circumstances
that
these
people
can't
really
meet
or
get
that
mentorship,
but
at
least
they
can,
you
know,
take
advantage
of
this
tool.
A
Reaching
out
to
node
school
and
working
like
you
know,
I
I'm,
a
node
school
chapter
lead
for
New
York,
and
you
know
the
maintainer
zuv
note
school
themselves
are
all
you
know,
relatively
close
to
the
ecosystem
and
the
project.
Even
so
I.
You
know
working
with
them
like
closely
to
make
sure
that,
like
one,
the
content
is
something
that
actually
is
something
that's
good
for
a
remote
like
I
personally
had
a
relatively
bad
experience,
trying
to
use
node
school
on
my
own.
A
You
know
when
I,
when
I
was
learning
node
but
like
validating
that
and
going
through
and
making
sure
and
finding
things
that
we
can
do
together.
I
think
is
positive
and
I.
Think
that
will
take
work
and
I
would
recommend,
at
least
for
shipping
this,
that
we
leave
that
to
a
separate
scope
that,
like
once
we're
done.
That's
another
thing.
A
Much
like
like
once
we
are
kind
of
completed
with
the
design
and
the
content,
and
you
know
we're
basically
ready
to
push
this
into
production
and
do
push
it
into
production,
that
that
is
when
website
redesign
should
go
out
and
say,
like
hey.
Alright,
we
should
probably
jump
before
this,
like
we
shouldn't,
launch
everything
and
say:
hey
we're
now
we're
going
to,
but
like
the
time
to
kind
of
maybe
work
when
that
would
be
later.
At
least
that
would
be
how
I
would
approach
it
and
others
couldn't
definitely
think
I'm
wrong.
So
I.
F
A
And-
and
you
know
in
that
vein-
I
think
you
know
we
do
have
examples
to
some
extent,
although
you
know
completely.
Admittedly,
it's
relatively
empty
right
now
and
then
we
do
also
have
like
other
community
sites
that,
like
we
have
our
benchmarking
site
and
our
weight,
metrics
and
benchmarking,
which
I
don't
know
if
benchmarking
is
still
out.
Michael.