►
From YouTube: Node.js Mentorship Program team meeting - Oct 18, 2019
Description
A
A
This
is
the
first
like
the
reason
why
I
joined
the
kumkum
in
the
first
place
to
be
able
to
do
this,
but
yeah
going
forward.
We
have
discussed
what
we
what
we
need
to
do
since
I'm
leaving
and
we
might
need
like
a
process
to
escalate
stuff
where,
if
we
need
any
extra
privileges
or
access,
we
need
someone
from
the
kumkum
to
be
able
to
be
this
person
to
help
us
out.
A
So
I've
opened
the
pull
request
in
the
comm
and
we're
yet
to
find
like
to
figure
out
who's
gonna,
be
that
person,
but
it
seems
that
we
can
just
like
open
issues
on
the
comm
command
have
like
folks
from
the
kumkum,
helps
out
yeah.
So
I.
Don't
think
that
should
affect
us
much
but
yeah.
It's
something
I
thought
you
should
know.
A
A
B
A
Yes,
oh
and
in
the
pull
request,
I
already
asked
for
that,
and
yesterday
was
meeting
and
I
did
like
raise
this
issue
and
we
did
discuss
it
and
I
also
had
a
meeting
with
Tunney
BnB
to
to
see
how
we
can
go
from
there.
So
basically,
a
person
needs
to
be
a
member
in
the
comm
come
to
be
able
to
act
as
that
person.
A
A
B
A
So
I'll
leave
a
comment
and
in
the
pool
requests
for
like
changing
my
status
and
the
calm,
calm.
So
I'll
say
if,
like
I
say,
if
I
can
fill
in
this
spot
to
provide
updates
or
if
we
need
anything
yeah
and
we
can
go
from
there.
I
think
someone
from
the
kumkum
needs
to
give
an
OK
about
this,
but
definitely
I
would
love
to
have
you
act
as
that
person,
because
you
engage
with
the
program.
A
So
we
have
many
items
actually
to
discuss,
but
I
would
love
to
have
this
meeting
just
to
discuss
the
agenda
item
that
we
had
last
week,
which
is
like
bringing
more
people
to
the
mentorship
team.
So
Sal,
though
you
are
not
and
last
meeting
so
just
like
to
bring
context
for
you
and
for
anyone
watching
so
basically
we're
trying
to.
A
So
we
had
four
main
needs
that
we
want
to
identify
it
basically
we'd
love
to
have
someone
to
respond
on
issues
and
like
the
slack
Channel
and
just
liked
all
outside
of
the
program,
people
that
are
trying
to
engage
with
the
program
or
ask
questions
or
understand
like
what's
the
status,
and
all
of
that
so
I
believe
you've
been
doing
this
mostly
so.
Look
yes,.
B
A
A
Well,
let's
discuss
it's
after
I
finish
like
the
needs
that
we
have.
The
second
need.
We
have
is
someone
to
talk
with
the
mentors
and
mentees,
so
we
can
have
this
as
one
person
or
two
or
two
people,
and
basically
we
need
someone
to
just
make
sure
that
the
mentors
and
mentees
are
doing
okay
in
the
program.
They
need
to
reflect
any
feedback
or
any
concerns.
We
need
them
to
have
like
this
listen
gear,
to
be
able
to
escalate
the
issues
or
help
with
a
round
itself,
and
the
third
need
we
have
is.
A
So,
by
weekly
checking
on
mentees
to
make
sure
everything
is
okay
inside
the
program,
so
I
believe
yeah.
So
this
can
be
like
one
one
person
and
we
can
like
divide
it
into
like
two
separate
to
suppress
things
in
the
future.
If
we
find
like,
we
don't
have
enough,
like
the
person
doing,
this
doesn't
have
enough
time
to
follow
up
on
both
mentees
and
mentors
inside
the
program.
A
Which
we
might
need
to
like
make
clearer,
or
we
just
need
someone
to
be
indirect
code
process
and
have
like
more
people
responsible
for
the
matching
process.
Last
time
we
all
contributed
to
the
matching
process.
So
if
we
just
find
another
person
that
can
help
us
also
on
that
I
think
we
don't
need
that
get
a
new
person
just
for
that,
we
can
have
them
like
contribute
to
the
process
and
to
the
mentorship
team
in
general,
but
they
can
help
with
that,
like
a
plus
one
or
oh
yeah,.
B
A
A
B
So,
from
my
point
of
view,
I
believe
they
are
mouths.
They
are
both
relatively
important
because,
if
I
meet
you,
how
can
I
say,
address
the
community
and
be
aware
of
everything
that's
going
on
and
cetera.
It
helps.
It
helps
me
to
understand
and
write
the
notes
on
the
subjects
that
we
are
dealing
and
creating
the
issue
agenda
and
whatever
you
need,
so
you
can
provide
the
information
for
the
community.
A
E
A
A
Yeah
I
think
like
saw
those
already
doing
this
in
offcially,
so
we
can
have
this
like
on
you.
So
yeah
sounds
good,
so
I
think
so
it
was
not
here,
but
we
agreed
to
once
we
finalize
this
for
in
this
meeting,
we
agreed
to
announce
it
somehow
that
we
need
two
more
people,
but
I'm,
not
sure.
If
opening
an
issue
and
tweeting
on
Twitter
is
enough,
and
also
I'd
like
to
have
like
some
kind
of
discussion
about
what
exactly
we
should
say
in
the
tweet
or
in
the
issue
that
we're
gonna
open.
A
B
Have
a
concern
about
the
visibility
of
the
program.
You
know
a
lot
of
things
that
are
already
public
and
how
can
I
say
well
environment
on
the
mini
nodes
and
it's
like
channels
and
whatever
and
people
are
some
some
kind
of
limit
is
that
applied.
They
are
not
aware
of
the
current
status
and
have
the
same
same
old
questions
and
also
I'm
concerned
about
the
visibility
of
the
program
and
how
we
are
provided
as
information
for
the
general
public.
A
So
I
think
for
anyone
that
is
like
not
fully
up-to-date
with
the
program
which
I
believe
most
people
are.
They
find
the
toil
like
they're
not
going
to
read
the
meeting
minutes
and
see
like
the
latest
updates
on
the
program.
I
think
we
can
help
like
improve
that
by
putting
something
on
the
top
of
the
readme
file,
we're
updating
the
description
of
the
mentorship
channel,
I'm,
not
sure
if
you
have
any
ideas
or
any
age,
every
David
or
Eva.
A
So
sad,
oh,
like
afraid
to
act
as
the
person
responding
to
the
issues
outside
the
program
on
the
mentorship
Channel
and
on
the
issues
and
the
mentorship
repo
and
replying
on
asking
like
any
any
concern
about
the
program
or
when
it's
the
correct
ones.
The
next
round
or
this
kind
of
stuff.
So
solos
asking
so
most
of
the
people
live
on
all
the
stats
with
problem.
And
we
are
looking
for
it
because
posed
to
like
make
this
more
visible
like
currently
we're
in
the
second
cohort
and.
A
C
C
C
D
A
E
Hold
on
I
think
someone
correct
me:
if
I'm
wrong,
we
might
be
talking
about
different
things.
I
think
part
of
this
thread
has
had
is
about
getting
the
word
out
in
general,
but
I
want
to
make
sure
that
maybe
I,
misunderstood
I
thought
this
original.
It
was
about
people
being
a
little
bit
unclear
about
all
the
information
when
they
arrived
at
the
repo.
E
E
B
E
The
same
questions
over
and
over
so
for
me,
like
you
know,
this
thread
is
okay.
Does
anybody
have
any
ideas
about
that?
And
so
first
thing
that
comes
to
mind
is
okay:
let's
go
to
the
mentorship
repo
and
pretend
I
know
absolutely
nothing.
What
am
I
gonna
start
to
see
so
there's
the
general
github
stuff
at
the
top,
which
isn't
really
doing
anyone
any
favors.
If
they
don't
know
anything,
and
so
on
my
laptop,
it's
probably
the
very
first
I
mean
it's
like
really
at
the
bottom.
E
That
I
actually
see
any
information,
so
anything
of
interest
is,
is
gonna,
be
below
called
no
matter
what,
but
at
the
very
bottom
I
see
no
js'
mentorship.
It
was
the
h1
welcome
to
the
no
defender
ship
program,
okay
status.
Second
cohort
is
currently
in
progress
check
the
mentorship
journal
for
more
details.
This
project
is
bound
by
a
code
of
conduct
and
then
everything
else
is
off
the
screen.
E
So
the
only
things
like
like,
as
far
as
we're
concerned,
the
most
important
things
that
that
we've
told
people
that
we
have
control
over,
because
all
the
other
real
estate
is
github
files
and
stuff
is
the
name
of
the
thing
node
mentorship.
Okay.
Whatever
welcome
to
the
node
mentorship
program,
okay,
I
think
that
could
be
improved
status
and
then
check
the
mentorship
journal
for
more
details.
E
E
Mindset
and
then
the
mentorship
program
structure,
so
that's
pretty
far
down
now,
mentorship
duration
will
be
ten
weeks.
So
what
like,
are
these
the
questions
that
people
are
asking
the
mentorship
direction
like?
What's
the
mentorship
duration,
it's
like
how
far
down
in
this
readme
is
the
information
that
people
are
asking
most
like.
Do
we
want
to
trim
this
down?
Do
we
want
to
put
the
those
most
important
things
up
top?
Is
it?
Is
it
really
like
a
simplification
and
focus
that
is
gonna
solve?
The
issue
might
have
been
about.
C
C
B
Like
to
say
that
we
always
have
new
comers
and
there
is
it's
not
a
problem
theory,
they
are
asking
question,
that's
not
the
point.
The
point
is
that
we
every
time
we
see
we
are
the.
What
raises
the
flag
is
that
I
believe
we
are
not
provided
them?
How
can
I
say
we
are
not
spreading
the
word
correctly
I
sort
of
speaking
I.
Don't
know
we
are
reaching
the
main
trees
and
the
people
you
see.
That's
I
believe
that's
the
primary
point:
how
to
do
that.
A
B
For
example,
the
we
are
we
are
trying
to
collect
feedback
from
the
amenities
that
are
applied
but
were
not
selected.
I
only
had
one
wanna
reply
on
email
and
the
communication
I
used
was
this
like
channel.
So
from
the
point
I
see
the
I,
don't
believe
people
are
I
stay
turn
it
on
the
slack
channel
and
following
the
current
updates,
so
that
when
I
say
I
don't
know
if
the
selection
is
the
best
way.
B
C
A
D
A
My
person,
like
observation,
I,
see
the
most
common
question.
Is
people
asking
when
is
gonna?
When
is
the
next
cohort
gonna
start,
and
this
is
something
we're
not
adjusting
like
we're
saying
we're
in
the
second
cohort,
but
we're
not
addressing
like
just
something
simple
like,
even
if
we
don't
have
a
time
for
the
next.
A
So
like
a
time
estimate
for
the
next
cohort
I
think
we
should
just
state
that
by
I
think
having
a
list
of
the
most
common
questions
that
are
being
asked
on
the
mentorship
channel
on
maybe
Twitter
and
even
sorry
even
github
issues.
We
can
actually
like
filter
those
like
talk
most
common
questions
and
have
them
in
the
readme
file.
A
I,
really
like
the
idea
of
having
something
on
the
website
just
to
bring
more
visibility,
and
we
can
also
have
some
of
these
like
questions
addressed
on
them
on
the
know
site,
but
I
think
it
serves
more
as
like:
hey,
let's,
let's
bring
more
attention
to
the
program
rather
than
people
who
are
already
like
they
already
know
about
the
program
and
they
have
questions
I.
Think,
like
updating
the
readme
file
and
maybe
like
doing
some
stuff
on
the
mentorship
channel
like
if
we're
gonna
start,
for
example,
our
bi-weekly
meeting.
A
We
can
just
post
something
that
hey
this
we're
gonna
start
the
meeting.
If
you
want
our
TuneIn
I,
believe
age
I
used
to
do
that,
and
we
used
to
have
a
lot
more
engagement
on
the
YouTube
channel.
On
the
comments
section,
when
AJ
used
to
announce
that
we're
gonna
start
the
live
stream,
I
guess
we
dropped
that
just
because
we
had
so
many
technical
difficulties
and
putting
something
on
YouTube
for
a
long
time.
C
A
That's
a
good
question,
so
we
I
guess
yeah.
We
do
have
it
very
like
the
end
of
the
readme
file
and
in
the
poor
when
you
apply
trauma
mentee.
We
also
connect
you
to
a
slack
channel,
but
that's
about
it
like
you
need
to
dig
deep
to
find
the
non
slackers
channels,
the
section
stay
updated
and
the
readme
file,
which
is
almost
at
the
end
of
the
page.
Next
to
the
slack
channel
and
no
Twitter
account,
and
we
say
like
started
reporting
to
get
updates.
A
Yeah
I
agree
yeah,
so
just
to
summarize
I
guess
so
since,
although
you're
the
communic
team
Juna,
so
you
can
and
like
feel
free
to
like
have
other
ideas
or
change
stuff,
but
as
somebody
for
what
we
discussed
just
like
announcing
on
the
slide,
like
the
slack
channel,
maybe
like
we
can
show
you
the
meeting
notes
or
just
before
the
meeting
starts,
we
can
announce
that
we're
gonna
we're
going
live.
If
you
want
our
children,
I
don't
think
is
having
this
list.
A
This,
like
shared
document
that
you
just
put
like
questions
that
you're
getting
from
these
different
channels
and
the
last
thing,
which
is
something
like
we
need
to
do
continuously
I
believe,
is
updating
the
readme
file
to
become
more
relevant
for
people
that
already
know
about
the
program
and
oh,
they
just
saw
the
program
and
they
want
to
like
see
the
stats
that
they
they
have
some
questions
so
yeah.
We
can
definitely
bring
note
slackers
on
top
of
the
page
and
have
like
almost
above
the
food
content,
more
relevant,
like
they
would
say,
I
think.
F
A
A
A
A
Yeah
for
now
at
least
No
yeah
I'm,
not
sure
if
we
need
like
a
separate
document
for
mentors
and
mentees
and
have
the
mentees
one
and
the
main
readme
file,
which
is
something
like
AJ
proposed,
is
to
have
the
main
frequently
asked
questions
and
the
main
readme
file
and
just
linked
to
other
readme
file.
Mcduff
are
evil.
A
A
Which
brings
us
to
like
the
main
point
that
I
would
like
to
continue
discussing
this
meeting,
so
we
really
need
like
more
like
people
putting
ours
and
the
mentorship
team,
hopefully
like
after,
like
resigning
from
the
kong-kong
I'll,
have
more
time
to
contribute
to
the
mentorship
and
also
my
time
is
a
little
bit
for
you
now
in
general,
but
yeah.
We
definitely
need
those
three
or
at
the
moment
to
or
one
person
which
is
someone
to
follow
up
with
the
mentees
and
our
mentors.
A
A
A
A
C
A
Yeah,
my
my
hope
at
least,
is
that
if
we're
gonna,
announce
it
like
on
Twitter
or
on
the
slack
channel,
we're
gonna
get
lots
of
people
raising
their
hands
to
contribute
to
help
us
out,
hopefully,
but
I,
think
lots
of
people,
especially
because
they
applied
as
mentees
and
they're
already
like.
We
were
already
targeting
people
who
are
interested
in
the
program,
I
think
and
hope
we're
gonna
get
like
lots
of
people
who
are
willing
to
help
out.
I.
C
C
B
A
C
This
but
yeah
I
agree.
Let's
like
let's
get
it
on
Twitter.
Would
you
like
me
to
ask
Rachel
to
put
it
out
on
the
note
account.
A
E
E
D
A
D
F
F
A
E
Okay,
so
we
can,
we
can
just
talk
about
it
again,
real
quick.
So
should
we
start?
What's
the
most
important,
the
mentor
manager,
mentee
manager,
the
you
said:
you
have
the
number
for
the
round
corporation
mashing,
you
kickoff
meeting,
so
we
don't
need
that
one.
So
the
only
two
left
are
meant
to
our
manager,
mentee
manager,
which
one
should
we
discuss.
You.
A
A
E
A
I
can
try
to
recall
what
we
want
to
be
discussed,
so
basically,
the
person
who's
gonna
like
be
in
contact
with
the
mentees
they're
gonna,
like
pink
them
on
like
intervals,
let's
say
every
one
week,
every
two
weeks
and
but
this
personal
connection
that
they
can
like
contact
this
person
at
any
time
and
be
able
to
raise
any
issues
like
hey
I'm,
not
comfortable
with
what's
happening
or
something
wrong
has
happened,
or
everything
is
great
and
I.
Have
this
like
feedback
or
just
like
everything
is
fine,
and
so
we
need
to
have
this.
A
Like
two-way
communication
or
personal
connection
being
built
between
the
this,
we
can
call
it
men
danger
or
something
yeah,
so
this
is
basically
for
the
mentors
for
the
mentees,
for
the
mentors
is
less
slightly
different
that
basically,
the
main
thing
that
we
need
from
mentors
is
collecting
feedback
to
make
sure
that
we're
like
paying
attention
to
their
concerns.
Things
like
my
mentee
is
not
replying
on
my
emails
or
they're
not
being
responsive
and
also
we
need
to
so.
This
is
like
a
continuous
process
that
we
always
need
to
get
their
feedback
and
improve
the
program.
A
D
A
D
And
then
you
know
trying
to
maybe
compile
that
for
us
or
use
it
to
direct
our
decisions,
which
I
do
agree,
that
it
would
be
preferable
if
those
were
two
separate
people
between
the
mentors
and
mentees
and
we,
depending
on
how
much
of
a
response
we
get
could
potentially
be
for
different
people.
You
know
mentees
support,
mentor,
support,
mentee
feedback,
mentor
feedback,
that's
how
I'm
kind
of
seeing
it
so
far.
I.
C
D
C
D
A
C
F
A
So
I
guess
having
one
person,
especially
because
when
we
initially
start
so
the
next
round,
I
I,
don't
think
we
should
aim
to
bring
like
lots
of
mentors.
Maybe
just
like
this
round
like
five
to
10
people,
so
20
people
in
total,
so
I
think
this
could
be
handled
by
one
person
and
I.
Think
if
that
is
not
the
case,
we
can
then
ask
for
one
more
person
after
we
initialize
like
the
process
of
recruiting,
like
the
first
person
in
the
first
place,
yeah.
A
A
This
way,
we
can
ensure
that
we
have
a
pro
just
to
ensure
that
these
people
are
like
this
person
that
has
joined
this
meeting
a
certain
criteria,
so
we
can
have
like
on
like
when
we
start
each
meeting.
We
can
have
this
like
checking
if
this
person
did
actually
like
fill
up
and
provide
us
like
their
updates,
and
we
can
actually
like
have
them
as
members
after
a
certain
like
period
or
a
number
of
meetings
or
a
certain
like
level
of
contribution.
D
A
Yeah
I,
agree,
I,
think
I
think
it
makes
sense
to
just
check
like
on
each
me
like.
When
we
start
each
meeting,
we
can
have
the
status
check
that
okay,
okay,
bye,
yes,
I-
guess
like
having
a
small
process
to
just
make
sure
that
this
person
is
I,
think
that
we
expect
yeah
I,
think
that
makes
sense
before
we
like
invite
them
to
become
official
members,
especially
because
we
had
this
experience
in
the
past.
So
we
had
Conrad.
A
D
I
know
it's
kind
of
unreal,
a
time
in
know-how
and
relay
it,
but
the
the
four
positions
are
different
and
the
fourth
one
is
not
really
the
same
as
the
people
that
contact
mentors,
but
they
do
fit
better
into
the
goal
of
bringing
someone
on
board
like
there's
no
harm
in
letting
someone
join
the
meetings
and
try
to
help
us
plan
and
facilitate
how
we're
gonna
do
the
next
round
and
that
kind
of
stuff.
So
if
we
could
bring
people
on
in
that
regard,
just
have
them
sit
down
on
the
meetings
and
give
their
input.
D
D
E
F
A
D
Even
needs
to
go
to
the
meeting
ends
I
did
want
to
mention.
We
probably
need
to
update
the
readme
as
far
as
members.
Salo
is
not
even
listed
and
we
don't
have
any
titles.
So
we
could
put
the
community
manager
thing
for
silo
and
potentially
formalize
what
we're
having
Eva
do
with
the
kumkum
color
or
coming
liaison,
or
something
of
that
sort.
Yeah.
A
Yeah
I
think
we
should
like
put
a
code
team,
core
team
and
community
manager
so
under
identified
we
do
have
the
team
members
but
they're
not
specified
on
the
next.
My
name
project
lead
and
community
committee
champion,
which
needs
to
be
updated
now,
anyways,
so
yeah
I
think
it
makes
sense
to
do
that.