►
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).
B
C
D
I'll
go
if
the
mentorship
from
our
updates.
We
finish
it.
The
we
finished
a
forum,
application
for
the
new
meter,
the
new
Mightiest
replicate
and
we
are
doing
a
draft
beer,
a
test
on
ourselves
to
get
new
a
new
applicant
and
we
were
testing
the
new
process.
So
you
guys
I'm
going
to
know
they've
to
get
me
as
our
our
mentorship
champion
that
we
will
talk
more
ability
from
what
we
are
trying
to
do
and
more
stuff.
B
Yeah,
okay,
yeah
I
guess
I
can
elaborate
on
that
a
little
bit
since
I
guess,
I
guess
right
around
the
beginning
of
the
year,
we
decided
to
take
a
look
and
at
what
we
were
trying
to
accomplish
and
decided
that
it
was
worth
experimenting
with
a
new
direction.
So,
instead
of
just
having
a
general
mentee
pool
and
trying
to
get
as
many
mentors
as
we
can
and
and
do
the
matching
up
that
way,
the
thinking
was
to
be
more
focused
on
the
value
that
we
could
be
providing
directly
to
different
working
groups.
B
So,
following
that
it
would
be
okay.
What
are
the
different
areas
that
could
use
help
with
or
to
some
extent
could
could
define?
You
know
focused
focused
area
to
work
on
using
that.
We
would
then
create
what
you
might
easily
as
most
easily
compared
to
like
a
job
application
where,
where
it
would
be
or
a
job
description,
it
would
be
much
more
about
the
types
of
skills
that
are
required
so
for
a
lot
of
these.
That
just
might
be
some
familiarity
with
github
and
opening
closing
pull
requests.
B
You
know
these
basic
skills
or
these
basics
experiences
and-
and
those
are
not
the
types
of
things
that
our
mentors
needed
to
be
teaching.
So
a
lot
of
the
mentors
within
node
have
a
lot
more
specialized
experience
that
they
can
be
can
be
sharing
and
helping
with
people
and
then
there's
a
lot
more
general
skills
that
the
mentees
can
be
learning
on
their
own
and
that's
not
to
say
that
once
a
mentee,
a
potential
mentee
sees
one
of
these
job
descriptions.
They
wouldn't
be
able
to
learn.
What's
required,
they.
B
You
know
a
lot
of
these
things.
They
could
do
it,
but
we
wanted
to
save
a
lot
of
the
time
and
energy
of
the
mentors
for
teaching
the
things
that
the
mentor
actually
has
specialized
knowledge
of.
So
all
of
that's
to
say
is
that
the
way
that
we're
organizing
it
now
is
that
we're
trying
to
create
specific
roles
first
and
then
go
out
to
the
broader
community
mentee
candidates
to
then
find
people
who
can
fit
those
roles
better,
rather
than
just
trying
to
do
it
more
general.
B
Now
to
test
this
new
approach,
we
decided
to
do
a
little
bit
of
dog
fooding
and
see
how
it
would
work
for
our
group
mentorship
team.
So
before
going
to
other
working
groups,
we
figured
we'd
try
and
test
as
much
of
the
process
as
we
could
so
to
do
this,
we
created
a
new
form
with
a
you,
minimal
job
description
for
the
mentorship
team
and
put
it
out
there.
B
We
got
an
applicant
through
this
I
think,
unlike
the
past,
the
channel
that
we
used,
which
is
literally
just
the
the
slack
mentorship
channel,
doesn't
actually
get
a
whole
lot
of
visibility,
and
so
we
didn't
get
very
many
applicants,
which
is
a
pretty
good
thing
to
to
learn,
but
overall
I
mean
I,
think
we're
making
really
good
progress.
We're
definitely
learning
things
and
I.
Think
the
the
next
steps
for
us
would
be
to
maybe
widen
the
net
for
our
first
test,
trying
to
find
a
mentee
for
the
mentorship
team.
B
I
think
there's
also
some
things
that
we
want
to
discuss
about
possibly
slack
permissions.
If
we
do
continue
to
use
the
slack
channel
as
our
primary
way
of
communicating
with
potential
mentees,
we
might
want
some
additional
permissions
like
being
able
to
like
at
here
or
at
Channel
and
then
on
a
related
topic.
We
noticed
that
the
open
Jas
slack
as
opposed
to
the
node
slackers
slack
seems
to
be
I.
C
C
Think
in
terms
of
calm,
calm,
calm
initiatives,
probably
examples
and
website
are
gonna,
be
good
ones
that
could
potentially
benefit
from
mentees,
but
for
working
groups
that
are
under
the
TOC
I
think
you
know
finding
that
figuring
out
the
folks
who
are
active
in
respective
working
groups
and
then
reaching
out
to
them
directly
whether
it's
over
like
Twitter,
DM
or
email,
I,
guess
or
you
know,
or
oboe
jazz
foundation,
DM
and
then
in
basically
saying,
like
you
know,
explaining
what
you
explained
to
us.
C
E
C
E
B
B
B
D
Say
that
the
main
problem,
the
main
issue
that
we
are
trying
to
fix
is
that
we
were
using
the
same
spec
to
future
apply
pairs
from.
It
is
a
mattress
Trevor
and
we
should
be
the
idea
to
use
a
more
customized
filter
because
there
is
a
lot
of
groups
and
a
lot
of
matters
and
the
requirements
should
not
be
the
same
for
every
applicant
right.
So
this
is
one
of
the
issues
that
we
are
trying
to
fix
from
what
we
learn
from
the
previous
cohorts.
Right
matching
the
right
people
with
the
right.
D
Yes,
but
that
doesn't
mean
that
the
the
rule
will
increase
is
just
that
it
will
be
depends
on
each
each
group,
each
group
necessity.
The
main
idea
is
that
if
you
guys
I,
don't
know,
let's
suppose
they're
not
model
asleep
short
stuff
and
they
need
someone
to
help
them.
So
the
idea
is
to
work
in
a
way
that
we
can
help
find
it
as
treatable
motivated
person.
True
join
them,
so
not
only
the
person
you
meet
will
be
they
meet.
You
have
some
tutoring,
but
also
your
contribute
directly
to
the
working
group.
C
D
Hasn't
I
just
posted
the
true
issues
and
down
below
in
the
initiative
updates.
No
true
mentorship
should
I
put
inside
the
in
the
documentation
side,
the
mentorship
or
less
now.
I
just
put
the
two
issues
with
the
labeled
come-come
agenda.
Basically,
we
need
the
as
lack
permission
to
send
at
channel
or
adhere
inside.
They
decide
only
the
chain
of
the
mentorship
so
to
broadcast
news,
and
we
need
to
update
the
the
owner
permissions
beyond
the
github
repository
because
Ahmed
being
retired
I,
don't
know
the
proper
English
word,
but
he
stepped
down.
C
D
Okay,
okay,
well,
Saturday
now
had
our
hackathon
from
the
node.js
redesign
and
we
started
the
release
page,
who
are
ready
to
be
30%
of
that
of
that
page
and
we
change
the
approach
of
the
hackathons
instead
of
marlak
team.
Instead
of
discussing
we,
we
discovered
that
was
not
getting
us
where
II
wish
should
be
going,
and
then
we
change
our
heads
own
wife,
Sharon's
with
ABS
codec
spirits
where
everyone
joins,
and
anyone
and
each
each
developer
picks
up
component
or
assignment
work
in
the
same
page.
D
So
on
the
release
page,
we
already
did
the
them
in.
Besides
the
make
on
the
header
of
the
main
container
inside
the
releases
page
with
the
navigation,
the
download
description,
the
balanced
row
select,
which
operating
software
in
the
forego,
H
dot,
long
LG
s
are
correct,
but
we
only
did
30
percent
because
it
took
a
long
time
first
root
figuring
out
how
to
work
everyone
together.
But
this
give
us
an
experience,
so
we
can
go
faster
on
the
next
Saturday.
D
That's
it
I
believe
in
through
our
three
three
three
weeks,
we'll
finish
the
data
releases
page
and
it's
by
doing
this
approach,
we
I
think
we
could
go
faster
if
the
not
the
release,
but
the
design
of
every
everything
that
spended
only
one
things
I
need
to
talk
of
believe
with
Rachel.
If
we
are
going
to
I,
don't
know
broadcast
this
via
Twitter
or
it's
I,
don't
know.
C
I
was
just
say,
I
think
the
kind
of
to
do
from
the
last
meeting
was
to
just
reach
out
to
Rachel.
Before
that's
gonna
happen
with
like
what
to
share,
and
you
know
she
said
I
believe
she
said
that
she'd
be
willing
to
share
it.
Just.
G
If
you
want
to
send,
if
you
wanna,
you
can
either
DM
the
the
node
Twitter
handle,
you
can
find
me
on
email.
However,
you
want
to
send
me
that
information
I'm
happy
to
to
get
to
get
that
info
out.
F
F
So
the
group
has
been
experimenting
with
a
lot
of
different
things,
including
hackathons,
and
one
new
thing
that
we're
trying
out
is
mouse,
toning,
the
opioids
that
we
have
to
check
out
what
that
looks
like
there's
a
project
board
in
the
repository
other
than
that
it
all
comes
down
to
delivering
whatever
we've
listed
in
the
okay.
Ours
is
the
basic
key
results
for
this
cycle.
That's
all.
H
This
AJ,
with
the
mentorship
team
I
just
thought
of
this
off
the
top
of
my
head,
but
before
I
started
working
with
the
mentorship
team,
I
headed
up
an
initiative
called
wish
list
and
the
direction
we've
taken
with
the
mentorship
team,
now
kind
of
supersedes
that
and
I
didn't
ever
get
any
time
to
work
on
that
bin.
That
I
got
a
full-time
job
right
after
that
got
started
so
that
initiatives
could
probably
be
shut
down.
I
say
which
one
specifically
wish
list:
okay,.
C
C
E
B
C
I
I
So,
unfortunately,
a
lot
of
power
contribute
now
be
busy
now,
with
this
current
in
stock,
but
I'm
trying
to
convince
everyone
to
do
something.
So
as
much
as
we
have,
we
done
a
lot
of
stuff
for
last
month,
we
are
connected
an
OG
s
website
to
our
okay.
In
general,
we
are
using
crowding
for
translation,
our
content
and
before
we
are
used
just
for
API
Docs,
but
for
now
we
are
finally
connected
with
no
GS
website
content
and
we
also
fix
it.
I
The
problems
that
we
have
with
the
commentation
content
so
for
now
we
are
like,
can
translate
everything
for
no
GS
dog
park
and
for
API
Docs
and
it's
everything
connected
everything
works
and
we
can
like
start
inviting
translators
to
our
system.
But
I
would
like
to
postpone
this
process
for
a
few
weeks
until
we
are
test
everything
and
everything
works
well
and
out,
everything
will
be
automated
because
for
now
it's
a
bit
manual
still
and
I'm
working
on
that,
but
like
in
general,
we
are
making
big
steps
and
we
are
like
ready
to
translate
everything.
I
So
it
was
decided,
maybe
a
year
ago,
probably
or
two
years
ago,
is
to
not
push
any
translation
content
to
originally
paano
GS
/
node
like
not
make
some
noise
for
that
and
create
a
mirror
called
an
OGS,
a
IAT
n
repo
just
to
make
nightly
synchronization.
It's
also
implemented
for
is
nightly
sync
all
content
from
original
repo
to
this
repo
and
then
push
it
to
crowd
in.
So
all
translated
content
is
based
on
on
this
repo
ie
GM,
and
we
are
using
it
for
that.
I
I
For
now
it's
like
next
steps
for
us
for
me,
especially
to
understand
the
build
process
of
Doc's
website,
because
it's
like
seen
it
seems
different
from
no
GS,
but
not
no
G
at
that
org
website
it's
built
somewhere
else
and
I,
don't
know
where
and
so
I
need
to
research
about
it,
but
we
it's
it's
not
connected
to
online
website.
It's
like
just
placed
on
repo
in
markdown
files
in
that's
it,
but
I
hope
we
will
find
a
solution.
How
we
can
push
everything
and
build
everything
to
our
online
website
in
near
future.
Right.
E
I
J
E
J
C
E
I
I
I
Perfect
that
that's
how
it
working
now
but
as
I
said,
I,
need
to
investigate
into
building
process
of
current
Docs
original
dot
and
then
connect
in
some
way
translations
because,
as
I
said,
I
never
seen
the
beauty.
But
probably
someone
can
give
me
a
piece
of
advice
where
I
can
found
it
like
how
we
generate
the
docs
pages
for
website.
E
C
Right
answer
your
question:
a
bit,
we
I
believe
that's
built
from
node
and
then
deployed
it's
like
on
the
same
domain,
but
it's
not
the
same
website.
It's
like
a
different
website
on
a
different
path.
Basically,
it's
like
the
sub
path
of.
Like
you
know,
the
language
in
the
docs
is
its
own
website.
That's
like
independent
from
the
core
system
and
I
believe
they're
just
deployed
to
the
same
place.
If
that
makes
sense,
I
I
could
be
very
wrong
on
that.
But
that's
that's
my
understanding.
The.
E
Thing
is,
there
is
I'm,
pretty
sure,
also
that
the
code
to
do
the
conversion
actually
like
you
can
run
make
doc
in
the
node
tree.
Yeah,
yeah
I,
assume
that's
what
happened
so
probably
somewhere.
Basically,
you
know
we
must
run
make
doc
and
then
the
output
from
that
gets
merged
into
the
nodejs
Doc's,
or
it's
even
on
the
website
that
it
would
call
the
right
branches
and
do
that
even
yeah,
which
which
is
interesting
for
the
translations,
because
if
they're
not
in
the
main
repo
they'll
need
to
be
extra
steps
to
do
that.
E
E
H
B
C
G
C
A
A
Yeah
so
let's
see
on
the
CPC
side,
I
guess
the
you
know.
One
of
the
important
things
to
highlight
is
that
we
had
elections
for
members
voting
to
voting
members.
That
would
be
the
representatives
for
the
non-impact
projects.
The
growth
at
large
and
incubating
projects,
toby
Langille
from
who's
been
representing
the
amp
project,
as
well
as
chris
hillier
who's
been.
Who
is
the
lead
maintainer
on
mocha
we're
both
elected
as
voting
members
representing
those
projects
all
of
the
non
impact
projects,
I
should
say
so.
A
That's
a
big
recent
news,
we're
continuing
to
work
on
code
of
conducts
aspects,
I,
guess,
you'd
call
it
we're
looking
to
have
a
comic
panel
that
would
do
any
sort
of
moderation.
That's
escalates
up
to
the
foundation
of
the
cross
project,
Council
we're
hoping
to
do
a
working
session
soon
to
iron
out
some
of
the
code
of
conducts
bumps
in
the
road
that
we
found
and
it's
primarily
process
related,
not
necessarily
like
detail
oriented
so
hoping
to
have
that
happen
soon
and,
let's
see
the
event
is
still
scheduled
to
be
in
person.
A
A
E
For
the
first
year,
the
nodejs
project
was
was
given
one
of
the
two
CPC
board
seats,
but
that's
not
necessarily
seen
as
a
permanent
thing,
and
so
the
question
is,
you
know:
what's
the
node?
Yes,
this
project
feeling
on
that
this
year?
Is
it
like?
Oh
we're
comfortable,
you
know,
we've
been
through
the
process.
We've
had
our
CPC
rep.
We
believe
we
can
get
everything
done
through
that,
don't
think
we
need
a
board
rep
specifically
for
note
anymore
or
on
the
flip
side.
E
E
Don't
think
we
need
an
answer
like
we
don't
need
to
make
the
answer
now,
but
it's
I
think
Joe
is
just
putting
it
on
the
agenda
or
on
people's
radars
to
say
we
should
have
a
discussion
and
come
up
with
what
we
think
and
you
know
the
TCE
and
the
comm
come
together.
Should
you
know,
say
here's
our
opinion.
You
would.
E
E
A
E
G
C
C
Have
gone
through
and
done
a
lot
of
the
work
on
examples
that
repose
now
up
I've
also
tried
to
incorporate
some
feedback
and
kind
of
adapted
some
feedback
from
Chile
for
and
Matteo
Kalina.
Some
Matteo
submitted
a
furor
for
you
know,
JD
the
test
slightly
and
then
really
give
some
feedback
on
repo
structure
and
thinking
ways.
Things
could
be
a
little
bit
more
clear,
so
those
I'm
both
landed
and
then
mostly
now
trying
to
socialize.
Please
come
submit
examples:
it's
not
something.
C
I
can
ously,
do
all
myself,
so
I,
mostly
trying
to
kind
of
invest
my
time
in
working
with
other
people
to
get
them
to
come
and
submit
examples
rather
than
me,
writing
them
myself,
just
as
a
way
to
kind
of
make
it
more
of
a
community
effort
rather
than
a
charity
effort,
so
yeah.
If
you
are
interested
in
that
more
than
welcome
to
come,
and
so
you
know
we
would
submit
and
work
on
examples
very
happy
to
help
people
through
that
and,
of
course,
it's
an
initiative
and
I'm,
currently
the
only
like
initiative
member.
C
So
if
you
also
want
to
be
a
member
of
it
that
definitely
reach
out
and
like
if
you
know
you
want
to
come
work
additionally,
there
is
the
social
team
PR
that
I've
put
up.
So
this
is
the
culmination
of
a
few
months
of
off
and
on
work.
Basically,
you
know
a
while
ago,
Rachel
brought
up
that
there's
the
possibility
of
handing
over
the
nodejs
socials
to
the
project
rather
than
the
foundation.
C
Maintaining
them
and
I
now
have
the
PR
up
for
that
proposal
in
issue
494
and
adds,
and
so,
if
you
all
could
review
that,
like
you
go
to
read
and
stuff,
I
would
really
appreciate
that
just
so,
we
can
kind
of
hopefully
move
that
along.
It
seems
like
it
there's
general
consensus
so
far,
Michael
made
some
really
useful
feedback,
but
yeah
you
know
getting
to
it,
but
that
would
be
super
super
helpful
yeah.
So
that's
the
things
I
have
any
comments,
questions,
thoughts
and
those.
D
D
C
C
C
Happy
that
we
had
so
many
I
guess
is
a
good
way
to
put
it
cool.
So
first,
the
first
agenda
item
is:
do
we
need
a
newsletter
I
believe
we
talked
about
this
last
week
and
this
may
have
been
kind
of
answered
to
some
extent
yeah?
We
did
I
believe
we
addressed
this
by
stating
there's
no
grand
plan
as
design
or
web
commented.
C
C
C
F
C
D
That's
well,
I
guess
is
the
this
raises
two
questions,
the
first
one
we
are
using
the
node
slackers,
so
everyone
from
the
metric
ship,
everyone
that
how
they
make
T's
dominators
work
until
now
or
address
it
to
join
this.
No
J's
slack
channel
this.
The
question
that
I
have
assist
know
to
become
open
GS.
My
question
is:
should
we
should
we
move
to
open
Jas?
Should
we
maintain
both?
C
Your
first
question
I
would
recommend
I
would
recommend.
You
know,
of
course,
passing
it
through
the
the
folks
in
the
projects
to
see
or
the
initiative
to
see
what
the
how
they
feel
I
the
the
biggest
benefit
that
I
see
to
open,
Jas
and
I
honestly
would
recommend
just
thing
where
you
are,
if
it
weren't,
for
this
would
be
to
basically
it's
a
paid
sock,
so
your
history
will
not
go
away
and
that
the
noches
slackers
slacked,
like
every
time,
I
open
it
like
the
channel
that
whatever
is
open
these
just
blown
away.
E
E
C
In
that
we
theoretically
do,
we
have
not
maintained
it,
but
the
node
slackers
is
part
of
the
that's
the
initiative
thing
yeah
I
remember
we
have
so
I
guess
we
do
have
a
couple
people
who
might
be
able
to
do
that
for
you
right.
Yes,
it's
part
of
the
partner
communities
it
theoretically.
The
person
I
believe
before
was
Dan
and
then
Dan
is
no
longer.
C
You
know
a
member
of
come
come
and
then
it
was
Tracy,
I,
believe
or
Tracy
took
over
from
Dan
on
that
and
Tracy
is
no
longer
part
at
a
compound
and
I
believe
Tracy's.
Where
it
currently
stands.
Sorry
dude
need
to
actually
follow
up
on
that,
but
Jordan
LJ
harm
is
I've
been
there
and
it
supposedly
involved
in
foundation.
Stuff
I
think
he's
the
primary
owner.
So
you
know
he
is
the
person
that
I
would
end
up
reaching
out
to.
D
B
H
B
D
D
C
H
D
H
B
C
I
mean
for
what's
with
you,
can
totally
reach
out
to
Jordan.
He's
I
see
that
he's
online
in
the
note
slackers
right
now
and
say
like
either
hey,
could
we
get
the
permissions
to
do
this
or
a
could?
Could
you
do
this?
I
is
a
potential
way
to
resolve
that
for
the
mentorship
channel
and,
like
you
definitely
don't
have
to
make
that
decision.
C
J
D
J
C
That
make
sense
and
we
can
get
that's
totally
fine
and
I
guess
a
question
since
we
have
you
three
here
and
since
we
have
ten
minutes
that
we
can
maybe
talk
about.
This
isn't
like
a
complex
question,
but
will
one
or
two
or
three
or
any
of
you
you'll,
be
able
to
kind
of
consistently
join
meetings,
conquer
meetings
to
share
updates-
and
you
know
the
reflecting
to
the
state
of
things
yeah.