►
From YouTube: Node.js Community Committee Meeting
Description
A
A
Let's
get
started,
I
will
note
at
the
beginning
that
we're
gonna
have
a
public
session
and
a
private
session.
The
private
session
is
going
to
be
time,
boxed
to
30
minutes,
and
so
we're
gonna
make
sure
we
make
room
for
that
in
the
normal
hour
that
we
have
so
no
further
ado.
Do
we
have
initiative
updates.
B
So
you
know
we
run
various
types
of
user
feedback
from
specialized
in
special
interests
to
a
general
feedback.
We're
circling
back
to
do
a
general
feedback
one.
You
know
the
irony
of
user
feedback
is
we
tend
to
get
a
lot
more
interest
in
engagement
with
focal
focal
points
and
niches.
Then
we
do
with
you
know,
opening
the
door
and
inviting
anybody
so
yeah
I'd
love
to
have
more
attendance
and
more
engagements
in
this
session.
So
far,
we've
gotten
a
ton
of
positive
feedback
and
engagement,
around
promises,
initiative
and
almost
zero
on
general
feedback.
C
A
D
Good
I've
got
two
large
updates
from
the
website
redesign
initiative,
so
we
just
pulled
in
finalized
well
final,
but
the
current
process
for
creating
document
new
documentation
RFC's.
So
this
we're
getting
started
guides
specifically
the
list
of
stuff
generated
at
the
collaboration
summit
in
issue
number
16
website
redesign.
We
now
have
a
process
and
a
place
for
all
that
to
live
inside
the
repo,
while
we're
iterating
on
actual
site
design
and
documentation
destron.
So
please
go
take
a
look
at
the
list
and
contribute
where
you
feel
like
your
domain.
D
E
D
A
F
Yeah
update
for
the
mentorship
project,
so
we
started
the
matching
process.
Currently
we
have
for
the
beta
around,
we
have
seven
mentors
and
all
of
them
are
from
the
know:
Jess
they're,
all
members
in
the
project,
so
we're
gonna
start
with
that,
and
hopefully
we
will
finish
the
matching
process
this
week
or
within
the
next
few
weeks.
A
Cool
with
that
I
think
we
can
move
into
the
agenda.
So
the
first
item
I
do
want
to
preface
this
by
saying
we
probably
won't
get
to
everything
on
the
agenda
so
with
anything
that
we
don't
get
to
will
be
tables
for
the
future.
A
future
meeting
so
first
item
on
the
agenda
is
review.
Member
onboarding
process
from
in
fact,
initiatives
and
working
groups
on
Alexander
opened
it
on
behalf
of
Keisha.
A
B
I
speak
to
this
I'm
running
process.
This
is
aa,
yes,
okay,
so
specifically
when
and
this
this
is.
Actually
you
know
right
along
the
edge
of
you
know.
Is
this
a
community
committee
concern
or
is
this
an
admin
concern?
B
So
today,
when
a
initiative
or
working
group,
you
know
gets
to
point
where,
as
if
someone
is
brought
in
as
a
collaborator,
we
have
to
basically
chase
down
tyranny
and
asked
here:
Nate,
hey
Tony,
you
know,
could
you
make
this
person
a
member
of
no
jest,
and
you
know
I
know
we
all
look
yeah
doing
whatever
we
do.
We'd
go:
ask
tyranny
and
there's
like
that's,
not
a
process.
That's
not
something!
That's
repeatable!
That's
not
something!
That's
scalable!
So
yeah!
That's
that's
why
we
created
this
issue.
B
A
I
didn't
actually
realize
that
was
the
context
of
this,
and
now
that
you've
said
that
I
know
that
how
this
got
to
this
I
entirely
agree
that
said,
I
I,
don't
know
if
it
is
I
mean
III,
think
you're
right.
It's
probably
an
adamant
thing.
I,
don't
know
if
this
is
something
that
we
need
to
enable,
because
it's,
if
someone's
a
member
of
the
org
already
it
shouldn't,
be
an
issue.
I
think
I've
gone
through
and
tried
to
consistently
update
and
maintain.
Who
is
a
maintainer
of
the
teams.
A
But
if
someone's
not
a
member
of
the
Orgel
ready,
then
they
have
to
be
added
by
an
owner.
We
that's
that's
the
barrier
and,
like
that's
a
barrier,
that's
been
in
no
js'
as
long
as
I've
been
around
it
early
since
since
I
ojs,
so
yeah
I
got
severally,
I
think
an
admin
say
because
we've
not
solve
that.
Well,.
B
You
know
I
do
think
that
our
new
policy
in
the
calm,
calm
about
you,
know
encouraging.
You
know
the
answer
point
you
know
in
the
initiatives.
It
puts
a
unique
light
on
our
particular
case.
Right
because
wait
wait,
you
know.
If
you
aren't
currently
a
member
and
we're
you
know
actively
enabling
folks
that
are
not
currently
members
to
come
and
be
a
part
of
the
the
project.
B
A
C
The
existing
process
does
specifically
say
to
Terry's
point
that
it's
because
he's
a
chair,
it's
not
because
it's
tyranny.
It's
that
way.
We
specifically
called
out
I
think
somewhere
in
the
administer
of
probably
needs
to
be
updated
to
include
the
director
representative
as
well.
It
doesn't
already
but
yeah
as
a
not
next
natural
progression,
you're
right
that
it
could
then
be
taken
from
there
as
well.
Well,.
A
E
I
just
gonna
say
the
reason
that
this
stuff
exists
is
because
we're
sort
of
right.
This
is
where,
like
the
tooling
gets
tangled
with
our
governor
and
swear,
we
have
github
work
management
and
then
we
have
like
the
administrative
work
of
each
of
the
you
know,
committees
and
such
the
this
was
dated
originally
for
a
reason
so
that
the
you
know
the
chairs
are
chairs
personally
for,
like
dealing
and
managing
with
the
administrative
work
of
each
of
these
committees
and
again,
that's
why
Tierney
has
been
you
know.
E
Targeted
is
the
person
to
go
to
for
that.
If
it
is
overwhelming
right
in
an
overwhelming
number
of
requests
for
that,
then
we
clearly
need
to
figure
out
another
means,
but
that,
as
far
as
I
know,
is
a
pattern
across
the
project
where,
if
you
are,
you
know
a
part
of
the
group
that
has
been
maintaining
that
area
of
the
org
part
of
your
responsibility
is
providing
that
piece,
because
you
have
the
context
to
know
whether
you
can
be
like
onboarding
someone
or
giving
them.
E
That
said,
yes,
if
there's
an
update
that
needs
to
be
made.
This
is
certainly
an
admin
conversation.
I
think
this
is
a
separate
conversation
than
the
one
that's
already
happening
around
github
org
sort
of
like
existing
rules
with
the
Charter
I
think
that's
happening
with
maybe
the
TRC
right
now.
Okay,.
F
B
So
I
I
link
to
the
policy
you
know
followed
up
and
found
the
policy
in
admin
I
linked
to
the
policy
in
the
the
chat
and
we'll
put
that
in
the
notes
and
I
also
dropped
that
in
the
issue
for
additional
follow-up.
E
G
That
specific
issue
well
three
comments.
One
is
there
is
a
plan
of
enabling
and
automating
this
specific
task,
it's
a
slow-burning
plan,
but
there
is
other
motivations
to
have
to
enable
that,
via
a
bot
or
some
sort
of
to
make
a
tool
that
knows
policy.
The
second
one
is
as
that,
their
management
policy
says
all
the
TSE
members
have
owner
rights,
I'm
sure
some
of
them
would
be
happy
to
help
in
this
case.
If
it's,
you
know
well
documented,
adding
people
just
to
the
organization
has
fairly
minimal
impact.
G
G
A
G
E
A
E
There's
so
much
surface
area
and
people
with
context,
because
I
also
feel
bad
for
the
TSE.
If
they're
gonna
end
up
getting
these
requests
and
don't
necessarily
have
the
context
to
know
whether
there
should
be
doing
it
and
again
I'm
talking
more
about
the
context
of
collaborators
and
not
just
general
yeah,.
A
And
I
mean
even
that
distinction
is
very
great
between
collaborator
and
Bing
and
dot.
Org
members,
okay,
I'm
gonna,
talk
about
this.
We
need
to
move
on
to
the
next
issue,
so
good,
except
for
now.
Next
issue
is
okay,
so
the
next
two
I'm
gonna
take
over
I'm
gonna,
run
through
them.
Real,
quick
they're,
both
PRS
first
one
is
create
onboarding
MD,
which
is
a
document.
A
That's
just
first
attempted
an
onboarding
docking,
Tracy
and
Menil
had
a
had
some
comments.
I
asked
for
some
clarification,
but
otherwise
the
the
you
know
there
seems
to
be
approvals
and
I'm
happy
to
continue
iterating
on
that
and
I
think
you
know
we
should
be
able
to
iterate
on
this
and
get
it
shipped
relatively
soon
so
excited
for
that.
This
is
more
of
a
please,
take
a
look,
and
let
us
know
you
know
feedback,
so
we
can
make
this
sell
it
as
possible
next
issue
or
an
xpr
I'll
link.
A
It
sorry
I
didn't
do
that
for
the
last
one
is
PR
three
five,
two
first
passive
partner
communities,
so
I
really
just
threw
this
out
there,
because
I
very
much
going
down
the
path
of
going
toward
having
partner
communities
rather
than
a
single
blessed
entity
of
this
is
no
js'.
This
is
what
we
use
as
a
platform
to
discuss.
So
node
slackers
has
already
kind
of
gone
down
this
path
and
we
have
some
prior.
A
You
know
questions
and
content
in
here
I
CV
Carl,
who
runs
another
nodejs
discord,
are
very
popular
and
much
more
popular
than
the
one
I
created
he's
already
asking
questions
to
be
able
to
get
begin
to
kind
of
engage
with
this
I'm
actually
really
excited
to
see
that
so
that's
really
good
contacts.
So
again,
please
take
a
look.
Please
share
any
comments.
A
Next
thing
is:
how
should
we
address
licenses
for
note
non
code
initiatives
and
projects
I
just
added
the
agenda
labels
to
this?
This
is
something
I
wanted
to
have
in
the
private
section.
Just
because
I
have
a
half
update,
that's
not
official
and
I,
don't
want
to
ensure
anything.
That's
not
official
until
it's
official,
so
I'm
gonna
actually
update
on
that
in
the
private
session
cool.
So
I
didn't
link
the
issue.
But
next
item
on
the
agenda
is
a
nodejs
node
issue.
Let
me
pull
it
up.
Real,
quick
and.
A
D
So
sooner
you
open
this
issue
and
I
comment
to
give
extra
context
below
to
just
kind
of
get
the
get
the
ball
rolling
here
and
and
enable
them
to
have
the
tools
they
need
to
get
this
proposal
together
for
how
to
add
runnable
snippets
on
the
nodejs
documentation,
because
this
will
be
a
fairly
large
large
task.
It's
gonna
get
the
ball
rolling
now
to
see
how
it
will
look
or
may
look
in
the
future.
Yeah
Junie
didn't
miss
any
context.
There.
A
I
realized
in
the
original
issue.
I
didn't
link
the
demo
that
they'd
built
I,
don't
know
if
it
got
linked
because
I
like
I,
didn't
look
at
it
till
today
and
there's
a
lot
of
context
there.
It
does
look
like
they
actually
went
in
and
linked
it
in
his
comment.
So
here's
the
link,
if
in
the
zoom
chat,
if
anyone
wants
to
see
it,
it's
actually
really
cool
I'm
super
excited
about
it.
So
it
it
looks
like
the
run
kit
stuff
might
have
degraded
on
Grace
or.
E
A
D
B
D
That
so
the
nice
thing
about
the
solution
here
for
augmenting
the
build
it
doesn't
actually
change
the
documentation
content,
it's
a
build
stuff.
So
it's
very.
If,
if
God
forbid
run
kid
disappeared
overnight,
it
would
be
an
easy
switch
to
flip
to
do
grade
back
the
old
solution
or
just
inline.
Markdown
code
gum
code
blocks,
yep.
A
And
on
top
of
that,
like
I,
that
was
one
of
the
things
I
was
super
adamant
about
making
sure
that
wouldn't
be
an
issue
is
like
graceful
degradation
like,
for
example,
what
just
happened,
all
Irish
I,
don't
know
if
it's
happen
are
on
anyone
else's,
but
the
code
blocks
degrade
very,
very
gracefully,
and
so
you
know
that
an
important
thing
you
for
shipping
docks
with
core.
If
that's
gonna
be
included
in
there
in
part
the
builds,
we
need
to
make
sure
that
you
know
it
can
run
offline,
what
it
can't
connect
to
and.
A
A
B
B
So
yeah
thanks
everything
we
that
I
shared
earlier
covers
the
general
feedback.
Please
invite
people
to
that
those
tweets.
The
other
is
a
user
feedback
that
we're
preparing
for
a
survey
so
part
of
the
you
know.
The
facilitation
process
that
we
enable
and
use
it
or
feedback
is
helping
folks
build
the
consensus,
not
just
you're,
providing
the
forum,
but
you
know
once
you,
you
know,
have
some
folks
attention.
B
You
know,
how
do
you
actually
build
a
consensus,
drive
change
and
that's
what
we're
in
the
in
the
process
right
now
of
facilitating
with
the
promises
some
promises
folks
and
so
either
you
know
promises
positive
or
negative.
You
know
whatever
side
of
the
aisle
you
meet,
you
may
sit
on
that
invite
folks
to
engage
in
that
process,
so
the
data
that
we
collect
it
will
meaningfully
inform
the
project
drop
link
that
thanks
for
your
attention.
A
Awesome
we're
gonna
in
the
live
stream.
Now
calm,
Co
members,
please
stay
on
I'm
and
foundation.
Members
as
well
are
welcome
to
stay
so
we're
gonna
end
the
stream
thanks
everyone
for
watching,
and
we
will
see
you
in
another
two
weeks
for
the
stream
and
I'm.
Looking
at
the
chat,
there's
no
questions
so
awesome
thanks.
Everyone.