►
From YouTube: Node.js Mentorship Meeting
Description
A
A
A
Yeah,
so
our
agenda
is
very
small
today.
I
just
want
to
review
that
the
number
of
responses
that
we
have
and
those
so
I
want.
There
was
a
question
on
the
mentorship
channel
about
when's
the
last
day
for
filling
the
form
and
I
want
to
get
your
opinions
on.
When
that
should
be,
should
we
wait
a
week
or
maybe
until
we
have
I,
don't
know,
500
people
look
like
what
do
you
think
I.
B
C
C
A
No,
no
last
time
I
checked,
we
had
around
20
I
will
double-check
now,
but
it's
been
almost
a
week
and
we
only
announced
on
slack
so
from
the
previous
round.
We
have
around
1,500,
so
we're
gonna
send
those
people
an
email
to
tell
them
that
the
new
round
is
opened
and
we
also
didn't
announce
it
on
Twitter.
Yet
by
far
twitter
has
like
the
most
engagement
for
mentorship.
So
whenever
we
do,
we
do
announce.
C
So
I,
don't
you
know,
seems
like
maybe
after
a
week,
just
call
that
you
know
or
I
don't
know
what
you
feel
about
giving
some
kind
of
public
timeline
like
telling
about.
You
know
the
public,
saying
after
week
we're
going
to
use.
You
know
how
our
mentees
are
going
to
sync
up
with
their
men.
Our
mentors
are
going
to
sneak
up
with
their
mentees.
That.
A
D
A
D
A
That's
a
good
question
personally
I
feel
like
after
we
do
vanishes
filtering
was
basically
the
initial
filtering
was
just
gonna.
Be
we're
gonna
make
sure
that
the
list
of
mentees
is
diverse
enough.
It
has
enough
like
levels
of
skills
from
beginners
to
experts
or
members
already
in
mode
after
that.
We're
gonna
filter
based
on
the
Dementors
that
the
mentees
chose.
A
So
each
mentee
will
choose
their
top
three
selections
for
each
mentor
and
will
be
something
useless
to
each
probably
will
hide
the
email
and
the
date
that
they
submitted
cause
it's
irrelevant
and
we'll
keep
the
Kitab
handle
and
the
other
free
text,
information
and
we'll
have
to
talk
to
each
mentor
to
choose
from
there.
Probably
the
mentors
will
need
a
week
to
choose
I'm,
not
sure.
A
Yeah
for
now
and
I
think
it's
the
model
we're
gonna
stick
to
for
a
while
is
just
one
to
one
I
believe
I
believe
I
wanted
to
say
that
yeah.
Actually,
you
and
another
inventor
then
said
that
you
don't
mind
one
too
many
I'm,
not
sure.
Maybe
it's
a
good
idea
to
hear
your
opinion.
Cysts
you're
gonna
be
mentoring.
C
C
You
know
at
least
on
that
level
or
that
scale
just
to
focus
in
like
the
how
they're
going
to
so.
As
far
as
like
you
know,
in
mo
for
this
time
period,
I
feel
like
that
makes
perfect
sense,
I
think
over
over
time.
It
would
be
interesting
to
explore
once
and
many
since
there
are
a
lot
of
people
who
are
looking
for
mentorship
and
more.
The
interest
of
being
able
to
you
know,
meet
the
broader
needs
of
the
community
over
time
and
support
them
as
best
as
we
can.
C
C
Ten
is
a
lot,
but
it
doesn't
make
sense
to
mentor
more
than
like
ten
people
in
a
group
setting
at
a
time
and
that's
that's
because
he
lose
the
ability
for
everyone
to
make
to
be
able
to
feel
like
they
make
a
connection
or
are
able
to
ask
the
questions
they
want
or
feel
comfortable
enough,
because
you
have
different
personalities
and
some
a
louder.
Some
may
be
quiet
or
something
be
more
apt
to
share
than
others
in
like
a
broader
group.
C
So
if
you
did
consider
doing
they
want
too
many
mentoring,
I
would
you
know,
but
I
would
put
a
hard
cap
on
like
you
know
how
much
pretty
intentionally
like?
Let's
not
do
more
than
like
you
know,
I
mean
five
would
be
great.
You
know,
I
would
be
pretty
like
and
maybe
as
soon
as
that
occurs,
but
just
figuring
out
like
like
how
many
people
you
can
do
at
a
time.
C
A
C
A
A
Yeah
I
also
want
to
say
that
I
have
updated
the
the
mentorship
repo
because
we
announced
it
and
I
didn't
want
to
wait.
I
just
merged
the
pull
request
directly
to
master
I,
just
added
the
line
that
the
second
cohort
is
now
open.
It's
the
second
line
in
the
readme
file
scan
code
is
now
open
for
mentees
and
I
linked
the
application
form.
C
A
C
So
is
there
any
expectation
around
for
mentors
around
like
documenting
what
they're
doing
and
you
know
providing
those,
possibly
as
because
what
would
be
ideal?
Is
it
like?
We
were
documenting
what
we're
doing
in
that
surface
saying
useful
resources?
You
know
that
we
can
keep
you
in
a
repo
and
stuff
like
that.
I'm
sure
you
all
have
already
thought
about
all
that
kind
of
stuff.
I
just
don't
know
yeah.
D
C
Awesome,
that's
super
great
I
think
a
funnel.
If
you
essentially
create
a
funnel
through
this
repository,
where
people
can
see
each
representative
of
each
different
working
group,
they
would
be
able
to
reach
out
to
get
involved
immediately.
Is
that
something
I
get
asked
all
the
time,
especially
in
meetups,
is
like
if
I
wanted
to
get
involved
in
helping
out
with
a
specific
working
group.
Like
you
know,
I
can
see.
There's
a
lot
of
people
there.
I
can
look
at
recent
commits
or
whatever
and
see
like
the
people.
C
A
But
he
also
suggested
the
same
idea
that
he
wanted
to
create
some.
Some
kind
of
some,
like
someone
from
the
security
working
group
coordinate
for
the
future
rounds
to
actually
have
a
way
to
recruit
mentors
on
the
way
to
recruit
people
in
the
security
working
groups
through
the
mentorship
program,
which
I
believe
is
something
that
we
should
try
to
focus
on
for
the
next
round.
A
It
will
be,
it
will
be
a
grantee
that
we
know
we
have
this
number
of
mentors
for
each
round
from
each
working
group,
which
is
something
that
we
really
need
to
work
on
and
also
yeah.
It
will
be
a
viable
strategy
to
bring
more
people
to
know
it
through
a
like
a
systematic
process
instead
of
just
bringing
mentors
and
then
I
think
for
different
people.
Yeah.
D
D
You
could
start
out
as
a
frequently
asked
questions
list
and
then,
eventually
you
could
end
up
having
each
working
group
having
like
you
know
the
best
contributing
MD
documents
in
the
world
or
something
you
know
where
we
direct
people
to
different
places
for
each
thing,
with
all
kinds
of
documents
that
way
out.
You
know
how
the
overall
structure
is,
and
you
know
all
that
kind
of
stuff
that
that
could
all
just
kind
of
naturally
evolved
from
something
that
could
start
out
really
simply.
Yes,.
C
Like
I
mean
figuring
out
like
that,
can
also
be
a
sort
of
initial.
If
someone
wanted
to
get
involved
in
a
working
group
in
there
heart
of
the
mentorship
program,
like
an
initial
task
or
initial
you
know,
homework
would
be
to
like
create
some
kind
of
document
or
abstraction
of
life.
You
know
just
like
a
description
of
what
that
working
group
is
with
an
abstraction
and
that
kind
of
stuff,
and
then
we
don't
you
know
and
then
to
give
that
we
already
have
that
and
then
we
could
just
you
know
like
you
use
it.
C
You
know
so
that
could
be
really
cool.
I
was
also
thinking
about
it
from
the
other
side,
forgetting
meant
like
strategy
for
getting
mentors
involved
and
like
I,
think
you
know.
Obviously
the
next
step
would
be
to
like
to
fill
out
the
contributing
guide
we
have
here,
but
I
feel,
like
you
know,
there's
a
lot
of
great.
There
are
a
lot
of
great
people
in
the
node
ecosystem
that
have
a
lot
of
talent.
C
You
know
that
can
help
and
do
that
sort
of
thing
and
everyone's
bandwidth
is
they
all
have
so
much
bandwidth
and
that
kind
of
thing
and
that's
always
hard
but
I,
feel
like
if
we,
you
know
strategize
around
criteria
a
little
bit
in
a
non.
You
know
like
a
non-exclusive
way
or
anything
like
not
like
you
know.
You
know
you
must
have
these
qualifications
to
do
that.
C
That's
not
what
I'm
saying,
but
just
like
figuring
out
a
way
to
communicate
that,
like
the
what
you
know
like
general
criteria
like
hey,
have
you
been
involved
in
the
know
project?
Do
you
have
any
experience
like?
Oh
you
know,
because
some
people
might
think
that
they
have
to
you
know
have
like
years
of
experience
before
they
can
jump
in
or
something.
But
that's
not
the
case
like
if
you're
involved
and
you're
doing
stuff,
that's
awesome
and
I
feel
like
people
up.
D
That's
a
great
point:
I
have
never
made
a
code
contribution
to
node.
The
way
I
got
involved
is
kind
of
in
this
mentorship
program
is
kind
of
what
you
mentioned
earlier,
I
just
kind
of
jumped
into
a
discussion
and
put
out
this
really
long
document
of
like
here's.
The
things
y'all
are
talking
about.
Here's
my
viewpoints
on
each
one
of
them
and
the
pros
and
cons
of
each
approach
and
there's
some
other
ideas.
I
had
and
they
were
just
like
hey,
you
want
to
get
involved.
D
C
Absolutely
man
and
and
I
feel,
like
you
know,
it's
just
like
being
able
to
communicate
that
and
how
simple
it
is,
has
been
my
biggest
challenge
with
getting
people
involved.
In
note,
I
mean
it's
like
the
threshold
for
most
people
they're,
like
you
know,
cuz
people
usually
have
this
idea
in
their
mind
that
oh,
you
know
like
you're,
contributing
to
a
large
project.
That
means
that
you
had
to
accomplish
something
you
had
to
like.
You
know,
have
X
Y
Z
blocks
like
that.
You
contributed
and
that's
like
never
the
case.
Yeah.
C
It's
like
getting
involved
in
any
project
is
waiting
into
a
stream.
You
know
it's
like
the
more
involve
you
are
like
the
deeper
you
go
and
like
the
less
you
know
like
well,
I
mean
you
know
if
you
have
to
wade
out
of
the
stream
for
a
while.
That's
okay,
you
know,
like
people
have
limited
bandwidth,
but
like
it's
just
like
going
in
and
out
of
the
stream
like
that.
First
thing
to
do
is
get
your
feet
on
the
water
like
and
that's
just
by
showing
up
so
I
feel
like
the
more
we
can
help.
C
People
feel
that
and
know
that
for
mentors
and
mentees
that
better
so
yeah,
that's
awesome.
This
is
really
really
great
and
we
excited
for
this
y'all
and
excited
be
a
part
of
this
and
looking
forward
to
helping
one
person
out
and
that
many,
maybe
many
you
know
in
a
couple
of
sessions.
I,
don't
know.
D
But
if
we
focus
more
on
getting
people
involved
in
non-code
ways
like,
for
instance,
these
these
type
of
discussions
we
have,
if
we
just
invite
the
community
to
be
involved,
some
way
I
like
just
posting
something
on
github
that
people
can
chime
in
on
and
kept
like
just
make
an
issue
like
here's,
what
we're
thinking
about
doing
and
then
direct
the
slack
or
Twitter
whoever
say
hey.
D
We
put
this
issue
up
with
love
feedback
from
anybody
and
everybody
about
this,
and
that
could
be
a
good
way
to
like
he
said,
get
people
to
wade
into
the
waters
and
say
hey
I
am
contributing
to
know
it
already
and
there's
nothing
else.
I
have
to
do
and
they're
responding
to
me
and
I'm
being
involved,
and
you
know
from
there
they
can
take
the
next
steps
or
feel
more
empowered
to
take
the
next
steps.
Yeah.
C
Yeah
absolutely
I
also
feel
yeah.
On
top
of
that,
I
feel
like
the
mentor
list
is
a
lopsided
in
that
way.
So
like
for
contribution
to
note
I
feel
like
when
I
first
looked
at
the
mess
realist
I
was
like
oh
okay,
this
is
about
no
core,
you
know
that's
what
I
saw
when
I
saw
it
and
you
know
I
I,
think
I'm.
The
only
community
committee
have
heavy
purses
in
this
round,
so
I
think
finding
that
balance
where
people
know
that
it's
you
know
like
yeah.
C
Of
course,
there's
going
to
be
a
lot
of
people
who
want
to
jump
into
committing
a
core.
That's
great.
You
know,
there's
also
opportunities
for
people
who
want
to
contribute
through
the
community
committee,
or
you
know
other
non-code
ways
as
well.
If
they
want
not,
if
you
like,
just
finding
a
way
to
balance
that
and
get
that
reflected,
you
know
like
in
the
in
the
mentor
list
and
obviously
we're
working
with
volunteers.
C
You
know
so
it's
just
like
well
who's
going
to
volunteer
well
a
lot
of
people
who
are
in
the
Corps
volunteer
at
this
time.
That's
great!
You
know
you
know,
maybe
if
we
see
that
it's
lopsided,
maybe
maybe
push
it,
you
know
put
the
pressure
on
community
committee
a
little
bit
more,
something
to
help
us
find
mentors
that
reflect
that
too,
or
you
know
something
like
that
over
time,
but
I
feel
like
trying
to
try
to
ride
that
balance
of.
Like
you
know,
technical
and
non-technical
contributions
is
really
good.
D
C
C
It
would
behoove
us
to
recognize
people
who
are
contributing
more
and
like
are
getting
and
putting
in
time
and
recognize
those
things,
and
if
it
you
know,
if
they,
if
they
are
growing
and
really
contributing
like
we
could
give
them
the
opportunity
to
become
to
be
mentors
as
well.
You
know
so
like
something
that
maybe
we
should
keep
our
eye
out
for
is
you
know
we
kind
of
I
think
the
ideal
scenario
is
to
be
mentors
that
mentor
mentors
you
know
and
so
like.
C
If
you're
mentoring,
mentors
and
they're
able
to
then
you
know
their
mentors
and
we're
grading
like
you
know
a
large
base
of
mentors
over
time
that
can
can
help
us
out,
and
you
know
like
be
engaged
and
involved,
and
so
anyways
I
think.
Maybe
this
is
my
opinion,
but
it
would
be
really
awesome
to
make
that
to
get
that
in
the
core
message
somewhere,
where
you
know
like.
If
people
are
really
if
the
individual
is
really
growing
through
their
mentorship
to
get
through
the
mentorship
and
they
come,
you
know
they
also
have
the
you
know.
C
B
Totally
I
mean
isn't
so
you
know
something
that
we've
kind
of
covered
before
which
is
which
is
really
like.
How
are
we
setting
up
this
process?
And
you
know
if
you
think
of
it,
as
inputs
and
outputs,
to
get
like
to
achieve
the
goal,
which
is
really
to
get
more
people
into
you
know
contributing
to
node
either
core
or
other
ways.
The
limiting
factor
really
is
mentors,
and
you
know
your
your
comments
before
about.
Oh,
this
is
really
heavily
skewed
towards
you
know
core.
B
It's
like
you
know,
yeah
I
mean
that's
just
what
we
could
get
really.
We
want
all
the
mentors
that
we
can
get,
because
that's
that's
our
bottleneck,
you
know
the
the
limited
resource
really
is
people
who
are
experienced
enough
to
be
mentors
and
you
know
I,
don't
think
it
has
to
be
anybody.
You
know,
who's
landed,
a
commit
and
no
door
had
working
on
a
committee
for
a
while.
B
There
is
a
minimum
level
of
experience
required
and
those
people
who
tend
to
have
that
experience
also
tend
to
have
limited
bandwidth
and
are
not
you
know
they
don't
really
have
as
much
time
vailable
to
mentor.
So
you
know
what
you're
getting
at
is
completely
the
idea,
which
is:
how
can
we
make
new
mentors
and
if
we
can
do
that
through
our
own
process?
D
Again,
this
is
pretty
far
out
there,
but
from
what
we've
been
discussing
in
the
past,
but
one
thing
I
could
see
doing
that
is
I
know.
We've
previously
explicitly
stated
we're
not
about
general
mentoring,
like
programming,
for
instance,
but
depending
on
what
kind
of
resources
we
can
come
up
with.
Maybe
it
would
make
sense
to
do
some
of
that
type
of
mentoring
if
we've
got
a
bunch
of
people
in
our
slack
channel
who
haven't
contributed
to
node,
but
they've
been
programming
for
40
years.
D
You
know
why
not
let
them
mentor
some
people
in
programming
if
they
want
to
and
that
can
at
least
get
them
involved
in
the
node
ecosystem
and
talking
to
the
people
who
are
in
with
node
and
say
hey.
These
are
really
cool
people
and
they're
really
helpful
and
now
I
feel
comfortable
asking
them
these
more
node
specific
questions-
and
you
know
it's
kinda
like
been
said,
a
funnel
in
a
way.
So
that's
another
idea.
C
C
A
Yeah
I
agree.
It
would
be
awesome
to
share
this
video
with
mentorship
channel
and
github
to
get
more
ideas,
see
who's
interested
in
getting
involved
on
deeper
level
regarding
like
bringing
people
who
are
experienced,
but
not
members
in
nodes,
I
I,
totally
like
the
idea
and
I
initially
started
thinking
about
it.
But
there
was
a
concern
about
people
who
are
not
members
already
in
node.
They
don't
know
much
about
like
the
code
of
conduct
and
it
will
bring
all
all
these
things
that
we
faced
earlier.
A
Do
it
like
when
we
first
started
the
program,
it
was
the
first
challenge
on.
How
will
we
keep
this
environment
safe
for
mentees
and
matters
without
without
needing
to
have
like
some
sort
of
really
tight
crosses
to
make
sure
that
there's
no
friction
between
ministers
and
mentees,
and
our
current
solution
is
just
to
bring
people
who
are
already
members
and
notes.
Maybe
we
can
figure
out
another
way
to
do
that.
That
would
be
really
interesting,
but
yeah.
This
is
the
main
issue
why
we
didn't
pursue
that.
D
C
Codifying
these
things
in
the
contributing
guide
is
going
to
be
super
vital
as
we
discuss
and
go
along
and
make
sure
that
they're
there
so
I
there
yeah
there
would
be
a
concern
if
people
are
coming
from
outside
organizations,
but
you're
going
to
need
some
kind
of
acclamation
process.
You
know
you're
going
to
need
some
kind
of
like
if
you're
going
to
be
a
contributor,
then
we
require
that
you
read
through
this
code
of
conduct
with
us
and
you
know
I
mean
maybe
essentially
we
want
to
be
safe
about
mentors
and
mentees.
We
require
that.
C
Maybe
a
renew
mentor
comes
to
one
of
these
meetings
or
something
you
know.
So
we
can
not
only
you
know
like
and
that
they're
required
to
read
the
code
of
through
the
code
of
conduct
and
maybe
sign
an
agreement
or
something
I.
Don't
know
if
want
to
sign
an
agreement,
but
you
know
I'm
saying
just
like
some
kind
of
some
kind
of
like
hey.
We
can
see
that
they
have.
You
know
agreeing
to
our
code
of
conduct,
we've
seen
them.
C
We
don't
just
want
to
turn
people
that
you
don't
know
or
haven't,
had
any
interaction
with
loose.
You
know
and
I'm
primarily
talking
about
people
who
are
coming
from
outside
of
node.
You
know
that
sort
of
thing,
but
it'd
be
nice
to
just
like
you
know,
say
hey
if
you're
new
contributor
make
it
to
one
of
our
meetings
and
yeah.
D
D
C
I
mean
what
makes
a
mission
you
know,
but
we
have
a
couple
action
items
from
this
meeting
and
yeah.
Those
can
become
issues
and
I'll.
Just
be
able
to.
You
know,
like
I
mean
one
one
is
like
get
some
general
stuff
in
the
contribution
guide.
You
know
like
how
to
be
a
mentor,
or
you
know
things
like
that,
but
yeah.
C
C
I
mean
in
general,
in
given
the
platform
that
worries
me
to
github,
and
how
note
is
you
know,
that's
eternally
bonded
to
get
home.
I
think
that
we
should
it's
a
great
platform
for
like
if
you,
if
you
have
a
suggestion
or
something
make
an
issue,
we'll
talk
about
what
we
can
discuss
it
in
text
there
we'll
have
a
history
of
it.
Everyone
will
see
it.
D
C
C
I
think
I
think
just
a
basic
definition
of
you
know
like
how,
if
you're
contributing
as
a
mentor,
and
if
you
can,
you
know,
if
you're
contributing
as
a
mentee.
What
does
that
mean?
You
know
I
think
having
two
basic
definitions,
for
that
would
be
a
good
place
to
start
and
then
moving
on
from
there
also.
C
Great
stuff
happening
and
I'm
super
excited
for
this
round.
I
mean
great
a
really
great
team
here
and
people.
You
know
like
super
positive
about
you
know
just
like
where
this
is
going
and
people
are
going
to
get
stoked
and
involved
in
it
like
I,
think
something
that's
really
cool.
Just
maybe
a
last
thought
for
me
that
some
of
that's
really
cool
thinking
about,
like
the
mentors
mentoring,
mentors
kind
of
thing
is
that
why
people
can
I.
C
D
D
D
A
C
It's
exciting
like
for
mentors
I,
mean
there's
a
lot
well
I
think
you
touched
on
something
you're
saying
about
like
getting
people
getting
people
involved
and
seeing
the
outcome
for
node
I
think
that
that's
one
side
of
it,
but
the
other
super
exciting
part
is
grow.
You
know
like
personal
growth,
so
it's
just
like
the
mentors
get
to
reinforce
like
important
aspects
of
of
their
understanding
and
their
growth
by
being
able
to
teach
others,
and
so
I
think
that
that's
what
I
mean.
Maybe
that's
what
I
thing
that
I
lost
was
like.
C
If
people
learn
you
know
to
get
involved,
then
they
can
turn
back
around
and
for
reinforce
their
learnings
reinforce
than
I
understanding
by
teaching
it
again,
you
know-
and
so
that's
like
that's-
definitely
a
really
awesome
value
for
for
the
mentor
in
this
and
I.
Don't
like
it's.
It's
definitely
not
just
a
self
sacrificial
thing
and
I'm
like
we're.
Building
up
no
we're
growing
for
some
for
some
people,
it
may
may
just
be
an
opportunity
to
really
get
ferment
or
some
in
terms
that
may
be
a
good
opportunity
just
to
get
really
comfortable
with
teaching.
D
What
we
do
we,
we
take
one
person
and
put
them
with
one
person,
and
they
do
this
for
this
number
of
weeks
and
then
everybody
goes
on
their
way,
I'd
liked
it
to
be
a
place
where
a
mentor
could
be
like.
Hey
I
have
been
mentoring.
This
person,
it's
really
taught
me,
I,
really
love
teaching.
So
I
made
a
course.
It
looks
like
great
we've
got
a
website,
we'll
put
it
up
for
you,
and
we've
got
this
community,
that's
already
interested
in
learning
stuff,
so
we'll
direct
them
to
it.
D
A
That's
a
good
idea
also,
because
not
everyone
has
the
capacity
to
mentor
for
10
weeks
straight,
so
maybe,
like
a
few
people
are
interested
in
contributing
for
a
week
or
two
weeks.
This
way
they
can
contribute,
maybe
in
content
or
other
other
areas,
not
just
actual
one-on-one
mentorship,
so
yeah
to
be
an
interesting
thing
to
think
about
how
we
can
get
that
into
the
program
and.
D
Now
that
we've
kind
of
started
automating
our
program,
a
bit
more
that'll,
give
us
time
during
the
cohorts
to
have
these
kind
of
discussions
more.
Instead
of
just
trying
to
figure
out
the
specifics
of
how
the
mentoring
is
about
to
happen,
we
already
got
that
worked
out.
So
now
we
can
just
you
know,
explore
fun
ideas
and
talk
about
where
we
can
go
from
here.
C
A
We
kind
of
have
multi-threading
under
flag
I
can
share
link
to
the
docs,
but
javascript
is
single
threaded,
so
anyways
I
may
have
joined
this
live
video
late.
What
I
want
you
to
know?
How
can
I
register
for
the
mentorship
program
go
to
the
mentorship,
repo
node.js,
/
mentorship
and
there's
a
link
to
the
application?
The
second
line
and
their
ad
file
welcome
I'm,
looking
for
some
articles,
which
can
read
the
files
containing
contents
using
node.js.
A
Maybe
you
have
more
experience
with
that,
but
my
personal
experience
is
just
going
to
the
node.js,
slash
node
repo
and
trying
to
figure
out
the
JavaScript
way
like
the
JavaScript
sides
and
C++
side
and
how
they're
communicating
the
file
structure
there's
good.
First
issues
that
are
really
easy
to
get
started
with.
This
is
how
I
person
started
I'm,
not
sure
if
you
have
other
ideas,
the.
C
C
A
I've
linked
it
in
the
in
the
mentorship
channel
a
few
times.
It's
really
great,
you
just
say
I
want
to
contribute
to
not
jazz
sound.
You
got
a
list
of
good
first
issues,
it's
not
a
good
start.
Also:
tyranny
shared
the
he
wrote
a
blog
about
all
the
aspects
of
node
like
calm,
calm,
the
all
the
working
groups
and
how
to
contribute
how
to
get
started.
It's
a
really
great
article,
I
always
share
it
as
well.
So
that's
a
good
place
to
start
yeah
thanks
for
chiming
in
guys,
YouTube.