►
From YouTube: Node.js Community Committee Meeting - 2018-01-11
Description
A
A
A
E
A
G
A
A
A
J
A
Today's
agenda
is
in
issue
queue,
13
I,
don't
know
if
everyone
can
see
it
so
I'll
post
it
again,
I,
don't
know
how
long
it
keeps
the
chat
for,
but
that's
today's
issue
and
the
agenda
is
in
there.
We
have
quite
a
few
items
I'd
like
to
try
to
push
through
these
gret
moderately
quickly.
So
first
on
the
agenda
is
the
the
Charter
expectations
and
responsibilities
of
enterprise
advisor
of
the
enterprise
advisory
group.
A
A
There
was
quite
a
bit
of
discussion
further
discussion
yesterday,
but
since
this
does
fall
under
the
compound,
we
have
to
kind
of
approve
this.
So
you
know
we
have
to
just
make
the
decision
and
help
help
this
through,
as
it
goes
so
I
definitely
like
everyone
to
go
through
and
review
this
and
review
the
thread.
A
E
E
E
So
you
know,
after
getting
the
you
know,
user
feed
back
off
the
ground.
You
know
weed
weed,
pink
folks
and
you
know
folks,
we're
finally
ready
to
you
know:
hey
let's:
let's
do
this,
so
we
held
sort
of
the
the
initial
introduction
session
with
with
folks
in
the
advisory
group.
All
of
these
folks
are
senior
management
level.
They
don't
spend
their
time
in
github,
so
in
laying
this
out
there's
a
lot
of
proxying
to
you
know
help
those
individuals
engage
in
our
github
process.
So
you
know
the
enterprise
advisory
group.
E
Is
you
know
the
the
first
attempt
to
put
down
into
words
a
definition
of
what
this
charter
could
look
like
under
the
user
feedback
and
therefore
under
the
community
committee-
and
you
know
it
has
gotten
a
lot
of
resistance
and
expression
of
concern
and
who
is
accountable
to
to
whom?
And
you
know
much
of
that
concern.
Is
you
know,
ahead
of
any
actual
activity
or
reality?
You
know
we're
at
a
point
in
the
project,
the
initiative
where
we're
just
trying
to
define
what
it
looks
like
and
you
know
then
begin
to
operate.
F
F
So
I
think
we
probably
like
to
me
here.
The
next
step
is
like
I,
think
the
making
sure
is
there
any
acknowledgement
that
the
all
in
okay
yeah.
So
it
is
okay,
so
you
mentioned
the
end-user,
the
feedback
initiative,
which
is
great,
because
I
think
that
that's
really
important
to
clarify,
like
the
the
enterprise
advisory
group,
is
one
you
know
part
of
the
strategy
of
the
user
feedback
initiative,
because
we
have
so
many
user
types,
an.
F
F
I
think
we
need
to
sort
of
call
out
the
folks
who
have
put
in
suggestions
see
if
they're
at
a
point
where
they
think
that
it's
okay
I
know
that
there's
been
some
recent
like
there's
activity
from
yesterday
on
there,
but
I
think
it's
definitely
tightened
up
quite
a
bit
and
what
I
think
the
final
piece
for
me
that
I'd
be
okay
with
plus
wanting
this.
It
is
having
some
sort
literally
a
tiny
bit
of
language.
We
have
very
similar
in
the
TSC,
as
well
as
the
comm
come
governance,
which
is
around
company
representation.
F
F
E
F
E
E
F
A
I'd
like
to
add
to
that
that
I
did
leave
a
review
comment
of
something
one
of
the
things
that
I'd
like
to
see
her.
This
is
a
big
thing
that
I'd
like
to
see
for
this
to
move
forward,
which
is
just
adding
in
a
small
section
about
you
know,
since
this
doesn't
all
we
think
in-house,
like
that's,
that's
kind
of
a
part
of
that
point
of
it
is
that
it
doesn't
live
and
a
lot
of
our
processes
are
built
around
github
and
like
having
accountability.
That
way,
just
that
you
know,
accountability
made.
A
Contents
and
communications
and
stuff
be
able
to
be
engaged
by
the
TSC,
the
calm,
calm
and
the
moderation
team,
the
moderation
team.
Obviously,
for
that
reason,
but
you
know
make
this
entirely
transparent
and
enabled
each
of
the
groups
level
the
ones
that
are
benefiting
from
this
and
try
to
engage
with
it
to
fully
participate
and
have
that
full
context.
That's
really
just
one
of
my
asks:
I
mean
that
III
do
think.
A
We
should
probably
try
to
figure
out
something
around
where
this
falls,
because
it
does
seem
like
one
of
the
big
confusion
points
that
I've
seen
at
least
is
it's
under
user
feedback
initiative,
but
like
the
way
our
org
is
set
up.
Like
a
group,
a
group
can't
be
under
initiative
and
happy
like
chartered
because
Charter
is
like
pass
is
having
a
charter
is
more
privileged
than
being
an
initiative.
A
So
that's
like
a
weird
structure
of
like
having
a
more
privileged
thing
under
a
less
privileged
thing
under
the
compound
and
that
even
in
the
discussions
that
were
happening
yesterday
around
it,
it
did
seem
like
there
was
confusion
about
whether
it
was
a
working
group
or
not.
Where
previously
been
stated,
it
wasn't,
and
then
people
are
saying
it
is
so
I
think
we
really
need
to
kind
of
make
sure
to
make
sure
that
part
of
it
is
clear
just
for
everyone's
understanding.
A
E
E
E
C
Think
in
this
case
the
you
know
looking
at
the
remediate
it
it's
not
stating
that
it's
a
group,
a
working
group
or
anything
like
that
and
but
I
don't
know,
I
mean
on
the
TSC
side,
we've
kind
of
fallen
back
to
two
working
groups
and
teams,
and
so
there
are
a
number
of
things
which
are
teams,
but
not
working
groups.
So
I
don't
know
if
it
helps
to
call
it
the
enterprise
advisory
team
to
avoid
that
can
because
and
the
distinction
being,
that
a
group
has
been
delegated
formal
authority
for
something
and
I.
C
E
C
E
A
I
E
Okay,
those
are
very
different
questions:
the
level
of
commitment
that
the
organization
is
going
to
provide.
We
are
going
to
meet
with
them
regularly
and
I.
Think
that
is
the
depth
of
the
commitment
that
we
guarantee
there
will
organize
regular
meetings
and
then,
in
those
meetings
we
will
seek
to
invite
TSC
members
and
Kham
Kham
members
and
engage
with
that
group.
But
that's
the
only
sort
of
level
of
commitment
that
we
offer
to
this
team,
a
group
that
does
that
make
sense,
Rachel
yeah.
I
G
E
I
say
something
really,
quick
and
I'll.
Be
brief
is
again
you
know
I
I
just
wanted
to
following
the
path
of
least
surprise
in
letting
folks
know
we
are
planning
on
holding
a
meeting
just
to
keep
the
momentum.
Keep
these
folks
engaged
sometime
this
month,
I'm,
not
sure
whether
to
you
know,
publish
the
minutes,
since
you
know
folks,
we're
concerned
about
this
last
time
I'd
prefer
to.
But
you
know,
as
we're
passing
this
out.
I
would
prefer
to
keep
this
group
engaged,
so
we
don't
lose
the
momentum
and
end
up
losing
this.
This.
E
A
Guess
a
good
asset
that
is
published
the
minutes
and
also
in
might
have
an
open
invitation
to
calm
calm.
Thank
you
in
the
calm,
calm
repo
to
invite
members
like
just
so.
It's
you
you're,
both
mentioning
and
making
it
very
obvious
that
it's
there
have
an
invitation
in
the
common
repo
I
think.
That's
it
not.
A
C
It
limited
as
the
chairs
of
the
the
TSC
and
Kham
Kham
and
director
representatives,
along
with
a
couple
of
foundation
representatives
that
actually
was
never
enacted.
So
we've
we
basically
stuck
with
what
we
had
before,
which
was
you
know
the
TSC
members
being
the
owners
and
rich.
You
know
rightly
pointed
out:
well
wait
a
sec,
we
just
you
know.
We
may
have
landed
this,
but
we've
never
respected
it.
So,
let's
actually
document
what
the
actual
case
is
and
the
suggestion
was
to
revert
back
to
what
it
was
before,
which
was
basically
just
the
TSC
members.
C
Some
discussion
III
ended
up,
pushing
talking
it
over
with
rich
and
pushed
on
a
commit
that
changes
it
to
be
the
TC
members,
plus
the
calm,
calm
chairs.
My
personal
feeling
is
that
you
know
we.
We
made
that
commitment,
so
we
should
follow
through
on
that
and
I
think
you
know
we
discussed
it
in
the
TAC
meeting
earlier
this
week.
C
The
remaining
kind
of
issues
would
be,
is
you
know,
should
we
be
adding?
You
know,
representatives
from
the
foundation,
which
was
the
suggestion
in
the
previous
version
that
had
landed,
and
just
you
know,
describing
the
rationale
for
that
as
well.
As
you
know,
it's
still
not.
You
know
all
kumki
members,
all
TSE
members.
There
has
been
some
discussion
in
terms
of
you
know
the
there's
sort
of
a
differing
level
of
I.
C
Don't
know
what
to
exactly
call
it
but
like
in
the
comic.
If
you,
if
you
participate
in
the
in
the
meetings,
you
know
you
basically
become
a
member,
and
so
there
may
be
a
different.
So
there's
still
some
some
issues
to
discuss
on
there.
Whether
it
makes
sense
to
say
like
just
include
all
Club
members
or.
F
D
F
D
F
Really
understand
to
be
part,
to
be
quite
honest
to
me,
what
that
feels
like
is
folks
feeling,
like
they're
the
best
authority
of
the
project
as
an
existing
github
is
code,
and
that
makes
sense
for
the
team
members
to
have
that
access.
Now
the
community
committee
members
are,
as
we
see
here,
moving
very
quickly
and
growing
very
quickly
and
need
more
than
just
our
two
chairs
happens
to
be
able
to
do
work
if
there
is
an
onboarding
process
in
order
to
like
filled
that
trust,
then
I'm
very
open
to
that
any
sort
of
training.
F
C
I'm
I'm,
an
agreement
that
you
know
it
was
just
an
interim
step
to
add
the
chairs
and
and
I
agree,
like
part
of
the
reason
that
we
didn't
implement.
What
was
written
down
before
is
because,
like
you
know,
it
would
have
removed
access
for
the
rest
of
the
TSC
members
and
we've
generally
worked
in
the
project
with
you
know
we
want
to
give
whatever
privileges
you
need
to
get
your
job
done.
C
E
C
C
D
D
A
A
A
D
A
A
One
thing
that
the
TSE
that
the
project
is
pushing
on
right
now
is
any
forcing
two-factor
authentication
for
all
members.
That's
just
a
general
security
thing
that
people
should
be
doing,
but
specifically,
if
you
have
any
kind
of
right,
access
to
and
OGS
repo,
that's
something
that
has
been
discussed
that
I
believe
we're
pushing
along,
and
this
helps
kind
of
that
story
along
a
bit
further
and
then
membership
in
members
gives
X.
This
is
a
private
moderation,
repo
which
you
know
if
you're
not
actually
active
in
the
project
could
be
an
issue.
A
So
those
are
generally
the
points
and
then
they
that
are
the
positives
like
points
in
favor
to
copy
what
rich
said.
So
it
would
be
helpful
if
we
could
get
a
calm
calm.
A
read-through
of
this
I
looks
good
to
me.
I
don't
have
an
issue
and
I
know
Olivia
commented,
but
it
would
be
helpful
if
we
could
get.
You
know
more
calm,
calm
representation
in
this
and
get
feedback
from
us.
I
I,
don't
know
if
there's
gonna
be
anything
negatives,
but
even
just
plus
ones
will
be
helpful.
Yeah.
C
E
C
A
D
Sure
so
this
stems
from
a
discussion
we've
been
having
for
a
long
time
is
to
finally
redesign
the
official
not
just
website.
We
have
a
thread
on
this
in
the
not
just
Luke.
We
poor
issue
number
one,
five,
three,
four
anyone
once
we
do
it.
Basically,
we
came
to
the
conclusion
that
we're
gonna
start
a
statute
initiative,
that'll
sort
of
stale
this,
so
we
don't
lose
speed.
So
that's
you
know
it's!
It's
cleared
on
an
organizational
level
and
yeah.
D
A
A
But
I
I
would
like
to
ask
because
I
know:
I
talked
it
a
little
bit
about
this
with
Tracy
a
while
ago,
but
is
Mark
Stone
the
luckiest.
So
if
we
were
to
go
the
route
of
like
professionally
getting
a
design
like
a
paid
design,
what
would
would
there
be
any
barriers
for
that
mark
requesting
funds
on
the
foundation?
No.
H
F
You
just
have
to
write
it.
You
just
have
to
like
build
a
proposal
right
like
so.
Some
will
probably
need
to
represent
it.
You
know
you
can
you
talk
to
mark
about
it
and
then
sort
of
having
like
a
written
written
statement
of
justifications
for
the
cost
rate
estimate
from
whoever
would
be
doing
the
work?
Okay,.
H
D
A
A
A
B
Yeah,
definitely
so
after
professor
Matt
on
Tuesday
and
came
to
the
consensus
on
a
current
direction
for
this
working
group,
a
technical
solution
that
we
think
is
appropriate
and
you
know
everything
for
internationalization
I,
don't
know
if
people
saw
the
drive-by
comment
that
Zeke
left
on
the
localization
issue,
but
we
think
that
the
electron
project
has
come
up
with
a
super
elegant
solution
and
our
yeah.
We
like
it
and
think
it
would
be
appropriate
in
our
case,
so
I
have
a
little
chart
that
I
made
here
I'm
going
to
post
into
the
chat.
B
B
It
abstracts
the
process
for
people
for
translators
from
github,
so
they're
not
dealing
with
any
complexities
within
the
workflow
that
we're
already
used
to
in
github,
but
they
they're
able
to
just
clearly
see
a
list
of
the
untranslated
documents
on
the
left
and
the
percentage
of
translation,
and
that
exists.
An
ongoing
translation
of
documents
on
the
right
I
can
use
what
it
looks
like
for
electron,
I'll
post
that
in
the
chat
as
well.
B
So
there's
that
it's
that
the
greatest
thing
about
this
is
you
know,
yeah
like
get
localized,
does
something
similar.
However,
Pradhan
has
automated
PR
and
updates
so
pr's
and
updates.
So
like
it's,
you
know
when
we,
whenever
an
update
to
a
document
happens,
you
know
we'll
be
able
to
have
that
go
to
a
node
internationalization
module
repo
this.
This
is
like
the
coolest
thing,
I
think
and
I'm
going
to
post
this
in
the
chat
too.
B
So
electron
has
this
internationalization
module
where
they
basically
populate
the
whole
thing
with
every
translation
of
every
language
and
that
it
you
just
import
that
into
we
would
import.
We
would
do
something
similar
import
that
into
no
J's
itself
and
be
able
to
use
that
where
we
need
like
for
for
our
documentation
and
that
sort
of
thing,
documentation
or
site.
B
You
know
all
those
types
of
things
come
so
I
think
this
is
a
great
way
to
go
and
in
with
whenever
something
is
not
translated
within
a
given
localization
and
language,
it
should
just
gracefully
fall
back
to
English
on
the
site
or
in
the
documentation,
wherever
it's
being
used.
So
I
think
the
the
more
like
the
combination
between
Crowden
and
a
internationalization
module
rifo
is
powerful
and
will
allow
us
to
just
kind
of
streamline
this
process
and
I.
Think
that
is
a
good
way
to
go
so
yeah.
B
D
B
E
B
We're
going
yeah
so
there's
that
and
then
I
think
the
general
help
and
the
big
things
that
we're
going
to
need
are
reaching
out
to
the
existing
internationalization
groups
and
asking
for
a
translation
where
we're
probably
going
to
need
to
formulate
some
kind
of
ongoing
request
for
volunteer
translators
and
I.
You
know,
I,
don't
know
it's
definitely
what
that
might
look
like
you
know
if
we're
gonna,
like
you
know,
put
it
out
on
Twitter
or
whatever,
but
we're
gonna
have
to
kind
of
continue
to.
B
You
know:
ask
people
to
help
us
with
that
in
one
way
or
another,
but
the
biggest
one
I
think
that
you
know
most
the
biggest
one
is
developing
the
the
module.
So
we
can
begin
the
process
of
integrating
with
node
yeah.
So
I've
got
a
internationalization
working
group,
MVP
repo
thing
that
I'm
almost
done
within
a
blog
that
I'm
almost
done
with
and
I'll
have
that
coming
out
by
the
end
of
the
week
for
y'all
and
I
will
need
somebody
to
review
that
and
hopefully
pull
that
into
Hong,
Kong
and
yeah
I.
C
C
B
C
E
B
I
mean
as
long
as
it's
a
document.
You
know
as
long
as
you
have
a
directory
tree
structure
and
you're
able
to
you,
know
populate
your
popular
I
haven't
available
org
or
our
repo
and
crowd
in
you
can
have
you
know
anything
is
translatable
as
long
as
it's
a
you
know,
a
viewable
document
has
it
I
mean
that
literally
like
it
just
it
cleanly
separates
that
for
the
translators,
so
I
wouldn't
see
there
being
any
problem
with
being
able
to
translate
error
messages.
Okay,.
B
Yeah
well
so
the
thing
is
the
translators
go
directly
to
crowdin,
so
they
they
don't
have
anything
to
do
with
the
repo
right
so
like
there
should.
There
just
needs
to
be
a
clean
separation
between
people
who
are
like.
Oh
yeah,
I
want
to
help
out
and
I'm
a
translator,
and
then
you
know
they
don't
need
to
have
anything
to
do
with
with
github
itself
and
so
yeah.
Basically,
we
send
all
our
translators
to
crowd
in
and
then
the
the
module
is.
D
B
E
B
I,
don't
want
to
do
that
I.
What
I'd
like
to
do
is
probably
send
some
kind
of
like
general
email
or
something
to
you,
know,
whoever
we
can,
that
represents
those
groups
and
saying,
like
you
know,
y'all
are
awesome.
We
appreciate
all
of
your
contribution
and
we
want
to
invite
you
to
to
help
us
out
with
with
the
ongoing
work
that
you've
been
doing.
I
feel
like
it
might
be:
there's
a
probably
cross
over
text
for
a
lot
of
people.
B
You
know
in
localization
groups
to
be
able
to
like
more
more
or
less
copy
the
work
that
they
did
and
integrate
it
into
Crowden.
You
know
so
I,
don't
think
it's
gonna
be
I.
I
just
think
like
getting
those
people
are
like
the
first
priority.
These
these
groups
like
requesting
help
from
them
saying
you're
awesome.
Thank
you
for
for
doing
this.
We
think
this
you
know
presenting
this
the
same
structure
that
I
just
did
to
everyone
now
and
you
know
saying
like
we
love
for
you
to
join
us,
I.
C
Might
say
it
instead
of
we'd
love
you
to
to
join
us
as
like
I'd,
be
asking
like.
Do
you
think
this
is
a
good
idea?
Do
you
think
this
is
a
good
way?
They
say
yes,
okay,
let's
move
on
this
together,
as
opposed
to
the
sort
of
you
want
to
join
this
sort
of
makes
it
like.
Well,
if
you
say
no,
then
right,
oh.
B
Right
right,
yeah,
yeah
and
no
way
in
no
way
do
I
mean
to
indicate,
like
you
know,
exclusion-
and
this
is
like
you
know,
take
it
or
leave
it
kind
of
thing.
So
yeah,
that's
that's,
definitely
a
great
point
and
it
would
be
good
to
continue
a
conversation
with
those
localization
groups.
You
know
to
sort
of
see
to
see
if
they
agree
with
this
general
structure.
Yeah
yeah.
C
A
A
A
So
I'm
just
gonna
drop
that
issue
in
we
don't
have
I,
don't
think
we
have
time
to
fully
discuss
it,
but
basically
they've
requested
that
we
have
technical
editors,
come
help
them
and
you
know
they're
they
just
comments
for
from
an
hour
ago.
It
was
basically
she
was
open
to
this
example,
but
more
generally
can
be
worked
framed
as
recruiting
problem.
How
do
how
does
a
group
with
it
writing
tech,
I,
think,
mutation,
factor,
I,
discover
opportunities
like
this
and
get
involved?
I
am
open
the
I'm
calm
perspective.
A
This
is
the
thing
to
focus
on
lines
nicely,
with
calm,
calm,
goals
of
increased
participation,
increasing
contributions
from
diverse
skill
set
talents.
It
also
nicely
with
other
initiatives
like
number
203,
which
is
I,
don't
know
which
one
that
is,
but
if
recruiting
is
a
high
priority,
how
does
a
website
redesign
accommodate
it
gotcha?
So
that's
the.
A
K
K
K
A
C
Like
I
think
it's
fits
under
the
comp,
calm
and
I
I.
Don't
hear
anybody
else
on
the
TSE,
so
I'd
like
I'd
added
it
to
the
agenda
as
I
think
I
had
an
action
to
a
while
back
and
we
I
was
finally
at
a
meeting.
So
I
basically
just
gave
the
fifth
fYI
that
it's
starting
up
and
people
should
go.
Take
a
look
but
I
didn't
I
didn't
really
hear
anybody
saying
hey.
C
We
should
be
leading
why
I
did
not
hear
that
you
know
anybody
there
stepped
up
and
said
we
should
be
leading
them,
be
leading
it
or
that
they,
you
know,
want
to
be
a
leader.
You
know
I
guess
what
I'm
saying
is
I
think
it
going
into
the
comm
come
fits
with
what
my
expectation
would
be
and
kind
of
where
we've
got
people
interested
to
drive
it
so
far.
Okay,.
C
K
Yeah
exactly
this
is
a
second
point
which
is
kicking
off
the
mentorship
program.
So
these
are
the
like
the
points
I
thought
we
have
to
discuss.
Basically
I
opened
an
issue
to
discuss
like
the
process
and
make
sure
that
it's
open
for
everyone
for
discussion.
Just
before
we
start
I
opened
an
insurance,
a
link
in
the
chat.
K
Yeah,
so
basically
the
process
with
a
diagram
at
the
bottom
of
the
comments
I
see
like
jasmine,
said
the
bench
review
on
that
solo.
Do
not
start
so
I
believe
like
it's.
Fine
second
point
is
about
the
slack
channel,
because
I
thought
the
program
that
we
have
to
open
a
slack
channel
to
facilitate
and
make
it
easier
for
people
to
join
and
see
the
movement,
so
maybe
I'm
not
sure
push
it
open.
The
slack.
A
A
A
lot
of
people
here
have
contacts
on
it,
so
teams
have
been
something
we've
consistently
discussed
as
a
part
of
the
project
and
it's
generally
been
and
I
think
we're
in
a
better
position
to
start
assessing
that
again,
especially
with
no
them.
There
is
a
moderation
team
that
operates
in
slack,
and
there
is
also
the
no
together
project
which
has
its
own
slack.
That's
a
core
part
of
the
project.
We
probably
need
to
assess
that
at
least
having
a
policy
for
that
under
the
calm.
A
C
C
A
C
L
I
want
to
say
that
there
is
a
very
popular
select
option
out
there
for
the
node
community.
It's
if
you
go
to
node
slackers
comm.
It
currently
is
thirty.
Thirty,
six
hundred
people
that
are
already
there,
so
people
are
free
to
join
free
to
create
rooms
or
whatever
they
called
channels
and
just
use
it.
It's
not
an
official
node
foundation,
sponsored
thing,
but
you
know
it's
there
and
it's
working
people
using
it
and.
A
F
In
the
discussions
that
we
had
last
year
around
like
what
are
the
official
communications
like
communities
for
node,
the
slack
and
IRC
stuff
came
up
and
I
think
the
result
of
that
discussion
was.
We
just
come
up
with
a
minimum
set
of
guidelines,
and
that
should
probably
be
an
issue
that
like
crosses
you
know,
maybe
the
admin
repo
in
moderation
team,
so
that
TSE
and
kumkum
can
weigh
in
but
like.
F
There
just
needs
to
be
some
minimal
things
there
right,
like
the
ability,
the
code
of
conduct
that
you
have,
that
in
a
public
place
that
everyone
can
see
that
they
need
to
abide
by
it
and
then
enforcing
it.
So
they
just
need
to
know
how
to
enforce
it
and
I
know
that
the
organizers
of
the
slack
that
will
mention
are
happy
to
do
that.
We've
just
never
gone
through
the
process
of
setting
up
that
official
sanction.
All.
L
F
G
F
Generally
speaking,
with
moderation
practices,
we
tried
to
have
people
who
are
a
part
of
like
the
existing
group,
have
someone
from
that
group
sort
of
take
on
that
instead
of
inserting
someone
from
outside,
because
that
tends
to
end
up
having
sort
of
a
conflict
between
length.
You
know
like
you,
may
not.
E
So
Aquaman
I,
you
know
we've
gone
out
into
the
implementation
detail
of
you
know
how
to
go
and
engage
with
potential
mentees
and
potential
sort
of
broad
communities.
You
know
III
I'd,
like
to
suggest
that
you
know.
Maybe
there
are
a
couple
really
important
things
that
you
want
to
consider
before
you
sort
of
open
yourself
up
to
to
that
work.
You
know.
First,
is
team
building,
you
know
we.
We've
landed
the
plane
in
terms
of
getting
the
mentorship
initiative
inside
the
the
project.
Yeah
Bravo
well
done
now.
E
You
know
who
are
the
individuals
that
are
going
to
join
that
team,
and
you
know
work
with
you
to
to
you
know,
build
out
the
the
mentors
and
then
I
would
say
there
that
that
team,
their
next
step
is,
you
know,
essentially
you
know.
The
next
team
is
the
mentors
who
are
the
individuals
that
are
interested
in
it
available
to
come
and
mentor,
and
then
you
know
serving
the
mentees
sure.