►
From YouTube: Node.js Mentorship Meeting
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
B
A
C
Yeah
I
think
I
mean,
for
starters,
I
think
we
do
just
need
to
get
a
feel
of
the
scope
of
the
projects
that
the
meant
mentees
would
like
to
work
on.
You
know
these
are
gonna,
be
project
based.
Did
we
ever
kind
of
really
come
to
a
conclusion
about
whether
we
want
to
have
you
know
just
help
them
land
a
few
disparate
pull
requests,
or
do
we
want
to
have
a
more
structured
process
around
it?
Maybe
that's
driven
by
the
mentee
themselves,
mm-hmm
I
think
it's
I
think
figure
out
what
they
want.
C
Just
for
starters,
cuz
I've
definitely
been
experienced
at
that.
The
mentorship
thing
I've
done
each
year,
there's
usually
a
few
folks
who
are
kind
of
more
interested
in
doing
their
own
thing
and
just
working
on
a
few
varied
projects,
and
then
there
are
definitely
are
a
few
people
who
are
more
project
oriented
and
want
to
work
on
a
bigger
thing.
So
I
think
feeling
that
out
would
be
good.
That.
B
B
B
B
B
B
C
B
B
Actually,
when
we
act
when
we
started
the
slack
channel,
some
people
did
not
like
the
slack
Channel,
because
it's
not
encrypted
I,
don't
believe
with
that
change
on
slack.
But
people
have
this
references.
Basically
what
we
have
wired-
and
we
should
address
that-
is
that
we're
gonna
have
an
issue
for
each
mentor
and
mentee
as
a
mentorship,
buyer
or
mentorship
yeah.
It's
an
issue
on
the
mentorship
team
on
the
mentorship
repo.
B
A
A
B
B
B
B
C
Gonna
I
was
just
kind
of
thinking,
thinking
out
loud,
but
I
bet
a
big
part
of
kind
of
the
first
couple
sessions,
especially
in
a
month-long
mentorship.
I
bet
it
will
just
be
getting
the
codebase
checked
out
and
compiling
for
some
folks
and
just
explaining
the
process
more
and
more
than
even
really
diving
in
months
of
pretty
short
time.
A
B
A
B
Actually,
like
I,
think
these
introductory
things
is
really
beneficial,
so
anyone
like
in
the
future
wants
to
see
like
how
the
build
process
happens
or
how
testing
happens
or
the
localization.
Usually
these
parts
are
not
well
documented,
so
having
them
as
videos
from
someone
that
knows,
the
project
is
really
good.
I
might
be
a
good
project.
B
A
B
C
B
I,
don't
think
we
can
put
them
on
the
repo
itself,
I'm,
not
sure.
If
there's
a
size
limit
on
github
actually
I
have
no
clue,
but
maybe
they
can
submit
them
as
pull
requests
on
github
or
just
really
have
the
links
to
somewhere
to
YouTube
or
Dropbox
or
something
we
can
also.
Let
the
mentors
and
mentees
figure
that
out
basem.
Oh,
they
see
fit.
Okay,
I.
C
B
A
A
A
B
We
should
also
let
the
mentee
and
mentor
decide
what
should
be
held
confidential
and
what
should
be
shared
between
the
two.
We
have
this
under
the
Code
of
Conduct,
so
we
should
like
highlight
it
and
make
sure
we
have
a
resolution
on
that
point,
because
if
there's
gonna
be
any
questions,
I
don't
want
it
to
be
in
that
area.
C
A
Could
possibly
even
facilitate
that
with
a
member
of
the
team
or
somebody
who's
interested
in
joining
for
that
purpose,
to
help
edit
videos
people
can
you
know,
declare
what
parts
they
don't
want
public
and
dedicate
the
video
could
be
edited
by
someone
before
it
gets
uploaded
or
yeah.
That's
just
a
thought.
C
B
C
A
C
A
Okay,
so
you
said
Dan
said
he
could
make
in
the
last
30
minutes.
So
we're
gonna
wait
around
for
do
you
think
we've
covered
everything
I.
B
B
B
B
I'm
sorry
I
thought
I'm
on
I
was
talking
about
I,
wasn't
in
it,
so
basically
what
we
did
is
we
covered.
What
we're
gonna
do
in
that
kickoff
meetings.
The
main
items
which
are
basically
give
a
quick
intro
about
the
mentorship
process
make
sure
that
they
agree
on
what
what
is
confidential.
What
is
not
what
else
yeah
also
the
pair,
should
agree
on
the
mentorship
schedule,
manage
the
expectations
and
goals
that
should
be
covered
during
this
me,
the
mentorship
and
also
they
should
agree
on
the
medium
of
communication.
I
hope
we
didn't
miss
anything.
B
Yeah
so
I
had
a
few
action
items
since
the
last
meeting,
so
basically
I
needed
to
open
an
issue
to
discuss
the
role
of
mentorship
team,
and
we
should
be
how
we
should
delegate
these
roles.
I
haven't
done
that
yet,
but
I
should
be
doing
that
since
Nick
opened
the
education
assistant,
it's
true
mainly
the
main
roles
are
covered
there,
so
I
will
derive
from
that.
A
It's
that
seems
like,
maybe
something
that
would
be
good
to
do.
It,
try
to
get
everyone
to
attend
a
meeting
and
have
that
in
the
private
session,
maybe
so
that
people
can
give
their
input
on
what
they're
interested
in
doing
or
willing
to
do
instead
just
kind
of
like
assigning
people
and
then
letting
them
know
what
they're
gonna
be
doing.
A
B
B
A
Yeah
it
was,
it
was
pretty
basic
I,
mostly
just
let
people
know
or
made
sure
they
understood
the
scope
that
they
were
going
to
be
mentoring
and
made
sure
that
was
okay
with
them.
Then
that
shows
what
mentor
I
thought
would
be
best
for
them
shared
a
link
to
that
mentors.
Bios
yeah
get
a
better
feel
for
who
they'd
be
working
with.
Let
them
know
that
we'd
be
setting
up
a
meeting
a
kickoff
meeting,
and
that
was
more
or
less
it.
B
A
B
B
Yeah
I
believe
it's
a
more
personal
experience
to
reach
out
to
them,
rather
than
have
like
an
automated
text
sent
out,
but
I
I
think
it's
a
good
idea
to
have
documented
at
the
moment
just
documentation
like
this
is
what
we
do
to
start
the
process.
This
way,
we
can
get
more
people
to
help
us
out
with
that,
if
you're
busy
or
we
need
more
capacity.
B
A
Yeah,
that
might
be
a
good
like
hybrid
approach,
like
have
a
document
that
we
can
link
to
when
we
contact
people,
so
that
I'm,
not
just
you
know,
whoever
isn't
just
typing
the
same
thing
to
every
person
manually
just
say:
hey
review
this
document.
This
is
the
outline
of
where,
where
we're
going
next
with
you,
so
these
are
the
things
to
look
out
for
and
then
here's
the
specific
information
about
you
and
your
mentor.