►
From YouTube: Node.js Community Committee Meeting
Description
B
Good
minim,
we
had
a
meeting
last
week
for
the
website
redesign
initiative
and
we
talked
about
the
material
we
gathered
at
the
collab
summit
and
that's
in
the
process
of
being
distilled
into
more
process
information,
and
there
will
be
some
issues
around
what
kind
of
content
we
will
need
to
generate
hope
to
have
it
done
by
this
weekend.
A
C
Guess
there
was
a
good
user
feedback
session
with
the
tooling
or
group,
so
that's
ongoing.
There's
lots
of
good
discussion
and
we
came
up
with
some
concrete
steps
in
terms
of
you
know,
suggesting
things
that
that
group
ceases
as
very
useful
for
a
broad
number
of
people
on
the
FS
side
of
things.
So
I
expect
that'll
be
sort
of
the
next
outcome.
We'll
see
there.
A
D
E
D
Little
thing
that
I
wanted
to
add
to
that
is
I'm,
really
happy
that
bones
called
Chris
Hiller
is
beginning
to
sort
of
take
that
tooling
group
and
you
know,
go
and
build
out
independently
and
not
just
sort
of
anchor.
In
the
you
know
the
bi-weekly
cadence
meetings
so
I
see
that,
as
a
you
know,
growth
and
expansion
of
user
feedback,
which
I'm
very
happy.
D
A
Awesome
and
kind
of
in
that
vein,
I
was
because
I
was
in
that
meeting
and
I
just
kind
of
thought.
There
might
be
some
things
that
people
in
this
group
could
maybe
do
to
help.
Do
you
have
any
like
help?
Get
more
people
involved
in
that?
Is
there
anything
explicitly
you
Michael
or
Dan
would
like
to
call
out
for
ways
we
can
kind
of
help
continue
to
get
engagement
there
and
help
promote
it
more
I
guess.
C
If
you,
if
you
know
any
module
owners,
that
would
have
feedback,
certainly
encourage
them
to
join,
you
know,
I
think
we
we
had
a
couple
there.
We
could
have
used
more.
A
few
people
commented
that
they
missed
the
meeting.
So
just
you
know
continue
to
encourage
people
to
show
up
and
contribute,
and
then
I
guess.
Otherwise
you
know
just
the
will
probably
a
you
know
at
the
next
meeting
promote
that
again
and
through
tweets
and
whatever
other
ways
you
can
think
so
any
ways
you
can
help
out
on
that
front
make
sense
too
and.
C
C
Right
so
this
one
is
a
good
sorry,
I'm,
just
getting
cleaning
it
loads,
so
I
think
this
one
is
a
good
one
to
engage
in,
because
that's
where
a
lot
of
discussion
of
you
know
what
are
the
pain
points
for
the
have
have
already
been
commented
on,
and
so
it's
you
know
either
good
to
comment
in
that.
Yes,
those
are
big.
People
agree
that
those
are
you
know,
key
things
or
even
suggest
other
ones.
E
A
Cool
I
do
have
two
things
to
quickly
update
on
one.
Is
that,
as
a
result
of
one
of
the
meetings
at
the
collaboratory,
some,
what
we
actually
did
begin
to
kick
off
an
outreach
program
are
now
reach
initiative.
I,
don't
know
if
we're
technically,
it's
technically
an
initiative
yet,
but
you
know
that's
something:
we're
trying
to
kick
off.
A
F
The
idea
is
to
specially
get
to
folks
who
are
under-resourced
and
community
colleges
are
great
because
they
tend
to
have
space
a
little
bit
of
resources
in
the
way
of
you
know,
computer
labs,
so
that
folks,
who
don't
even
have
access
to
you,
know
a
computer
necessarily
on
a
regular
basis,
can
at
least
get
a
taste
of
this
through
the
know,
together
a
curriculum
and
then
you
know,
we
build
up
that
network
for
folks
to
be
able
to
go
from
there.
You
know
if
they,
if
they
don't
have
a
laptop
at
home.
F
A
F
You
know
it's
from
a
front-end
perspective,
but
a
lot
of
community
colleges
have
been
teaching
javascript
for
a
long
time.
Even
before
you
know,
universities
had
started
incorporating
it
into
their
like
classic
CS
curriculum,
so
we're
talking
about
people
who
are
potentially
already
a
little
bit
set
up
for
that.
You
know
yep.
A
For
sure
and
then
the
other
thing
I
wanted
anything
else,
anyone
want
to
say
on
that.
Ask
questions
anything
like
that
for
context
that
work
there
is
happening
in
I,
I,
don't
know
how
much
is
we
created
their
repo,
but
I,
don't
know
how
much
has
been
done.
Cuz
I
haven't
checked
in
recently
in
the
repo,
but
there
is
another.
G
A
A
F
F
F
I
was
asked
to
lead
that
because
of
my
prior
work
at
the
foundation
and
having
the
context-
and
it
will
be
an
interesting
conversation
in
the
next
meeting-
to
figure
out
again
address
if
that
needs
to
change,
because
one
of
the
things
I
thought
that
was
really
valuable
about
being
able
to
lead
that
subcommittee
as
a
community
member
in
the
project
was
having
a
balance,
the
board
member
reporting
and
also
an
on
board
member
helping
co-lead.
So
yeah
that'll
be
a
colors.
D
F
So
that's
a
little
bit
separate
from
director
position,
but
this
rhetoric
outcome
director
position
is
as
a
board
director,
but
also
as
a
community
representative
I
need
to
do
my
work
to
coordinate
with
Tierney
as
much
as
possible
to
make
sure
that
anything
that
we
need
to
ask
of
the
board
from
the
community
committee,
and
that
is
any
of
the
the
work
initiatives
that's
going
on
underneath
the
community
committee.
Not
just
this.
F
So
just
to
keep
that
in
mind
with
folks
I
will
try
to
make
sure
I
communicate
those
timelines,
especially
when
we
are
trying
to
you,
know
a
whole,
but
to
get
something
to
the
board
level,
and
hopefully
that's
not
too
often
anyway,
because
we
just,
we
should
always
make
sure
we're
understanding
what
leverage
the
project
has
to
be
doing
our
work.
You
know
and
and
not
need
requests
of
the
board.
H
H
If
you
can
visit
the
link
like
there's
people
from
the
Diagnostics,
the
modules
via
the
build
and
the
tests
with
the
node,
which
is
great,
so
people
can
be
mentoring,
people
to
contribute
more
to
node
itself,
but
we
don't
have
anyone
from
the
comm
come
at
the
moment
and
it's
what
we
all
some
to
have.
Someone
from
the
comm
come
back
mentoring
about
the
calm,
calm,
the
process.
We
have
lots
of
initiatives
so
yeah.
A
D
A
A
Yes,
so,
yes
for
calm,
calm
members,
the
the
link
is
in
the
chat
and
if
you're
a
compliment
workers
watching
this
in
the
future,
it's
not
the
nodejs
mentorship
repo
and
then
it
looks
like
there's
just
there's
a
bunch
of
things:
labeled
mentor
that
they're
looking
for
awesome.
Okay,
so
with
that
well
actually
get
to
the
agenda.
So
the
first
thing
on
the
agenda
that
was
requested
to
be
added
by
I.
A
William
and
Manila
is
the
issue
170
Before.
We
jump
into
discussing
that
I.
Do
want
to
note
that
there's
another
agenda
item
that
I
put
below
it,
that
is
for
us
to
actually
discuss
this
is
a
subgroup,
and
so
the
issue
is
put
it
in
the
zoom
chat
for
comic-con
members,
but
it's
around
individual
membership
is
responsibility.
As
a
community
committee.
B
Sure
I
can
I
can
start.
I
wasn't
present
for
the
discussion
around
it
the
last
time.
So
if
anyone
was
there,
it
would
be
great
if
they
jumped
in
at
some
point,
I
believe
that
the
meeting
that
you're,
copying
and
pasting
over
right
now
is
was
originally
the
membership
restructuring
meeting,
but
now
that
the
activity
and
that
one
has
mostly
been
codified
into
language.
It's
just
it's
going
to
be
reused
for
individual
membership.
F
B
I
wanted
to
propose
that
we
think
about
individual
membership
as
a
way
to
get
the
wider
noches
ecosystem
and
when
I,
when
I
mean
ecosystem
I
mean
people
say
who
make
packages,
things
that
work
wouldn't
know
then
rely
on
oat
give
that
turn
that
into
a
channel
for
people
to
participate
in
the
noches
organization
themselves,
because
they
have
an
active
stake
in
it.
I
just
want
to
open
up
the
discussion
at
this
point.
A
A
Yeah
I
thought
there
was
another
person
involved
in
that
as
well.
It
was
women
we
were
with
the
Mozilla
office.
It
was
better
okay
yeah,
so
you
know
having
I
know
Jace
accounts
and
that,
having
that
going
to
be
the
portal
to
it
may
be
a
good
approach.
That's
you
know
a
massive
technical
undertaking,
I'm
guessing
for
us
as
volunteers,
to
maintain
that.
But
it
is,
you
know,
wondering
one
moderately
good
approach
or
one
of
the
more
interesting
approaches.
I
guess
they
should
say
not
much
early
good,
I.
A
F
Just
for,
like
time
sake
too,
it's
good
to
know.
You
have
a
standing
meeting
on
the
node
calendar
for
addressing
membership,
the
membership-
sorry
our
membership
program,
where
we
can
also
use
that
time
to
talk
about
what
we
should
be
doing
moving
forward.
So
the
collab
some
at
work
right.
The
meeting
that
we
had
was
sort
of
an
onboarding
to
folks
in
the
community
committee
or
people
interested
in
this
type
of
work
to
figure
out
how
to
get
started
in
this
subgroup
right.
So
we're
gonna
be
meeting
moving
forward,
because
this
is
a
very.
F
This
is
a
big
undertaking
that
has
multiple
components
that
we
need
to
attack
and
we,
while
we
have
the
agency
right
to
audit
and
decide
what
we
think
provides
value
to
our
community.
What
our
community
actually
is
the
scope
of
this
one
of
the
board
members
Sarah
Novotny
has
asked
men
volunteered
to
also
attend
on
top
of
clearly
William
cap
Keys
role
as
individual
Membership
Director.
Having
a
very
unique
and
lots
of
experience.
F
In
considering
this
type
of
work,
we
have
to
figure
out,
like
you
know,
the
what
value
we're
providing
moving
forward
and
and
even,
if,
like
what
we
have
is
worth
keeping,
but
we
should
so
win.
Would
I
think
that
the
next
best
thing
here
is
like
what
is
that?
When
is
the
next
meeting
to
get
to
really
like
dive
into
this?
Yet.
I
So
crazy,
I
guess
I,
probably
should
have
opened
up
on
this
cuz
I
did
request
beyond
the
meeting
all
right,
so
there
was
a
meeting
that
I
understand,
happened
and
I
think
this
was
that
collaborator
summit.
It
was
scheduled
very
fast,
but
there
was
an
out
I
think
there
was
some
output
from
them,
because
now
there
is
a
calendar
item
like
you're
saying
so.
I
This
was
I
wanted
to
bring
this
to
this
meeting,
just
so
that
whoever
was
there
could
convey
like
what
was
decided
as
next
steps-
and
you
know
clearly
a
meeting
in
a
set
up,
but
I
haven't
been
able
to
find
anything
about
who's
on
this
committee,
who
was
in
attendance
in
the
meeting
that
was
head
before.
What's
the
plan
for
inviting
board
members
and
things
like
it
so
clearly
there's
context
and
I
I'm
hoping
somebody.
Let
me
fill
in
the
rest
of
the
compound.
G
Just
a
quick
word:
I
wanted
to
precise
a
bit
the
small
comment.
I
met
to
make
short
resume.
The
committee
meeting
I
may
have
expressed
myself
body,
but
we
did
not,
as
far
as
remember
decided,
to
take
any
action
apart
from
meeting
and
forming
the
subcommittee,
which
was
asked
by
the
body
I
think.
So
there
is
nothing
that
anybody
might
have
missed
since
we
haven't
done
worked
as
of
yet
so.
A
You
know
facing
off
that
we
did
meet
at
the
collab
summit.
There
was
myself
Tracy
I,
don't
know
if
Michael
was
in
the
room
miles,
Boren's,
Dan,
Shaw,
Ben,
I,
think
Patricia
was
also
there,
and
so
we
just
kind
of
tried
to
discuss
some
of
the.
You
know
the
approaches
and
got
some
historical
context
on
an
individual
membership
from
Dan
who
was,
you
know,
had
helped
create
individual
membership
and
the
foundation
was
created,
and
then
you
know
we
discussed
some
of
the
strengths
and
some
of
the
weaknesses
and
some
of
the
possible
approaches.
A
It
was
mostly
crafting
and
just
getting
an
understanding.
That's
it
there.
There
was
an
explicit
agenda
and
there
wasn't
Enix
besides,
you
know,
let's
begin
to
understand
this
and
then
begin
to
plan
for
what
we
can
actually
do
with
it
or
begin
to
figure
out
how
we
can
plan
and
then,
on
top
of
that,
you
know,
tear
your
questions
about
a
membership
and
participation.
A
If
you
want
to
come,
participate
cool,
you
can
come
participate,
it's
not
a
requirement
for
Gotham
club
members,
but
if
there
are
members
that
are
interested
in
participating,
that's
the
approach
that
I'm,
my
understanding
was,
it
will
take,
and
I
might
have
been
pulling
that
context
from
just
a
restructuring
effort,
and
that's
that's
so
that
said,
you
know
we're
not
trying
to
exclude
anyone
or
focus
this
on
a
certain
set
subset
of
people.
It's
more.
If
you're
interested
in
helping
out
great,
please
come
help.
I,
don't
think
we
have.
C
I
Of
the
context
is
that
the
subcommittee
there
was
a
request,
partly
by
myself,
that
that,
for
this
to
be
successful,
we
need
to
know
what
the
board
wants
out
of
the
individual
director
program
period.
So
without
that
context
like
we
cannot
be
successful,
putting
together
something
that
will
make
the
board
right
and.
I
F
Is
why
it
was
an
official
meeting
about
that
that
was
like
context
in
history,
because
we
need
more
than
just
some
board
members
to
to
know
right.
The
history
of
this
work
and
I
think
you
and
Ashley
there's
so
much
tribal
knowledge
there,
and
it
will.
You
know,
of
course,
essential
where
that
subgroup
can
be
successful
for
you
to
be
there,
as
well
as
some
of
the
board
quarters.
I
A
A
That
was
very
much
my
intent
with
that
is
to
you
know
and
invite
everyone
who
is
interested
in
willing,
but
yeah.
So
you
know
we
spent
a
lot
of
time
on
this
I'm
concerned
that,
were
you
know,
we
were
doing
a
lot
of
work
here.
They
should
be
done
in
that
meeting
and
that
you
know
we
should
kind
of
try
to
move
on
to
the
other
agenda
items
and
then
let
that
work
be
done
by
that
group.
If
that's
okay,.
J
A
A
E
It
started
out
as
what
I
was
calling
a
priority
document.
Now,
it's
more
so
being
called
a
wishlist
document.
We've
made
a
little
bit
of
progress
meeting
with
different
working
groups
and
stuff
trying
to
get
some
tasks
put
together.
I
don't
know
if
I
should
go
into
like
the
full
context
of
what
it
is.
I
discussed
a
previous
compound
meeting.
How
do
you
think
hey.
E
E
It
would
just
be
a
central,
centralized
location
for
me
to
follow
because
right
now,
I'm
the
only
person
that
would
be
monitoring
it
so
that
way,
I
could
just
follow
that
one
repo
or
subscribe
to
it
rather
and
anyone
who
needed
something
put
on
the
document
or
edited
or
removed
from
the
document
etc,
could
just
raise
an
issue
and
I
could
be
notified.
Take
care
of
it.
A
F
A
I
I,
don't
it
might
be
in
the
admin
repo
I'm
actually
not
sure.
If.
F
C
F
F
A
So
you
know
the
basic
ones,
I
think
are
you
know
the
code
of
conduct
which
you
can
almost
directly
copy
from
and
Dan
might
have
insight
into
this
because
I
know
he
did
a
lot
of
work
around
this
with
a
user
feedback
and
tried
to
figure
it
out
so
governor.
You
don't
need
governance,
yeah
code
of
conduct
may
be
contributing,
probably
contributing
and
then
I'd
add.
A
D
A
I
Was
trying
to
remember
sorry
because
I
did
go
off
to
my
honeymoon
for
a
while
I
didn't
remember
where
that
landed?
Okay,
so
yeah
the
leave
committee
did
did
meet
on
that
day,
come
to
a
conclusion
and
basically
the
MIT
license
does
does
cover
it,
and
that
is
the
suggestion
is
just
to
stay
with
that.
That's
that's
my
high
level,
but
I
do
encourage
you
to
follow
up
and
get
the
official
like
statement
of
of
what
was
happening
there,
but
we're
good
okay.
D
That
is
where
we
put
the
least
effort
into
sort
of
aligning
and
making
sure
that
you
know
all
the
things
were
put
in
place.
User
feedback.
I
tried
really
hard
to
get
everything
ducks
in
a
row
there
and
there's
a
lot
more
tea
in
there,
but
check
out
check
out
both
of
those,
and
you
know,
AJ
if
you
would
like
any
help
or
feedback
I'm
happy
to
help.
Thank
you.
I
I
Is
you
get
notifications
for
new
stuff
and
you
get
a
dedicated
workspace
for
alerts
and
actually
just
confirmed
on
the
private
repo
that
you
can't
subscribe,
specific
specifically
to
a
board,
it's
great
as,
like
a
posting
posting
a
board
for
everybody
to
see
or
hey
here's
tickets
that
need
help
not
so
much
for
something
you
can
subscribe
to
and
follow
as
a
knight.
Okay,.
E
I
So
the
the
boards,
everybody
in
the
project,
can
add
tickets
to
it.
If
you're
able
to
make
issues
and
manage
issues,
you
can
move
it
into
the
project
web
board
and
just
I
think
by
default.
So
individual
owners
of
repos
could
take
the
initiative
to
move
it
into
the
project
if
it's
moved
into
the
project's
Kanban
board.
Basically,
if
they
wanted
to
so
it
wouldn't
see,
one
person
manager.
A
A
A
Okay,
next
agenda
item.
A
A
H
I
The
YouTube
videos
are
pretty
low
bandwidth
already
because
there's
no
video
in
it
so
wouldn't
save
too
much
on
that
front.
But
you
know
the
opening
issue
is
just
that
having
an
offline
be
able
to
to
play
it
in
the
background
and
stuff
like
that
which
I
guess
having
a
YouTube
red
account,
I
am
yeah
I,
don't
really
know
what
it's
like
to
not
have
it
so
I'm
hearing
there's
some
deficiencies
so.
A
K
K
I
have
read
that
Google
as
it's
looking
into
opening
both
background
playback
and
YouTube
music
for
regular
users.
That
would
just
solve
this
whole
issue
also
for
the
original
poster.
Since
this
the
content
is
released
as
public
access
is
there
a
CC
license,
I
think
he
can
use.
You
know:
alternative
YouTube
off
lining
solutions
available.
A
K
F
A
Don't
think
we
want
that
might
be
something
that
we
could
ask
Ann,
Marie
and
Tracy
that
to
help
out
with
is
going
through
and
actually
figuring
out
how
we
can
you
know,
make
that
a
not
or
change
that
solution
over
time
and
make
that
go
back
and
retroactively
lis
undo.
All
that
so
I
think
we've
just
not
been
explicit
about
it
and
I.
Don't
think
zoom
is
explicit
about
it.
When
that
happens,.
A
A
C
Sorry
Firefox
is
updating
as
I
open.
It
no
worries
right,
I,
guess
this.
This
one
was
I
can't
give
some
contacts,
because
I
did
the
same
thing
in
the
TAC
meeting.
Basically,
it's
the
PR
was
to
add
in
something
similar
that
we
have
in
the
moderation
policy,
about
the
expectation
of
privacy,
so
in
the
moderation
policy
and
the
moderation
repo
it.
Basically,
no
there's
text
that
says:
hey
everything
here
is
private.
C
If
you
repeatedly
share
this
in
the
public,
there'll
be
consequences,
you
know
maybe
even
being
kicked
out
right
and
basically
this
PR
was
just
to
add
the
exact
same
test
text
into
the
collaborator
repo
which
your
collaboration,
repo
I
forget,
which,
which
was
called,
which
was
open
so
that
there
could
be
some
internal
discussions
on
the
TSC
side.
There
was
nobody
who
liked
strongly
supported
it
or
strongly
objected
to
it.
The
discussion
really
went
in
a
different
direction
more
talking
about.
Well,
we
should
be
doing
less
things
there.
K
So
I
proposed
something
different
to
explicitly
state
that
conversations
there
should
not
be
considered
private
and
and
that
the
current
limitation
is
an
implementation
limitation
by
github.
I
want
to
punt
this
to
Adam.
Why
are
the
team
their
conversations
not
available
to
the
public
to
nan
Orrock
members.
K
C
F
K
What
happened
as
people
are
starting
discussions
that
had
the
assumptions
of
privacy
in
the
team
discussion
view
and
we
wanted
and
then
in
suggested
some
explicit
guidelines
to
that
either
we
decide
that
those
conversations
should
be
considered
private
and
then
reflected
with
the
same
rules
as
the
moderation
Rico.
And
then
there
were
some.
You
know
people
saying
why
have
practical
session
where
there
are
not
strictly
needed.
K
F
The
collaborators
repo
needs
that
is
like
very
much
our
policy
that
anything
in
the
collaborators
repo,
regardless
of
whether
it's
team,
discussion
or
elsewhere,
has
to
be
scoped
to
the
collaborators
repo,
because
that
is
explicitly
a
private
repo
for
a
reason.
Other
repos
of
the
project-
yes
I,
would
say
as
a
policy
we
do
try
to
be
as
transparent
as
possible.
We
can't
tell
you
know
TSC
repos.
What
to
do.
We
can
recommend
just
like
we
tried
to
do
right.
F
A
Even
even
that
brings
up
a
in
governance
question
by
Michael.
That
brings
up
an
interesting
discussion
or
governance
question
for
me,
which
is
okay.
So
if
there's
an
initiative
that
isn't
like
an
independently
chartered
group,
is
that
permissions
level
decided
by
like
the
comm,
Guam
or
the
DSC,
or
do
they
still
get
to
choose
their
own
permissions
level
there
and
then
anything
there
is
a
working
group.
Do
they
choose
their
own
permissions
level?
I
mean.
F
Every
every
working
group
has
to
be
under
yes,
your
Hong
Kong,
and
if
there
is
an
independent
repo
that
doesn't
fall
under
either,
if
someone
from
the
TSE
are
calm,
calm
seas,
you
know
that
there
are
problems.
I,
think
that,
like
it
is
currently
from
the
way
the
policies
are
written.
Currently
the
TS
seas
purview
to
come
in
and
say
because
no
one
has
like
sanctioned
you
as
an
a
project
one
under
one
of
these,
like
you
fall
under
our
rules
right
to
get
everything
in
the
github
or
it
falls
under
some
ones.
F
K
Case
I
would
move
to
I
know.
I
can
revise
my
suggestion
to
the
team
discussion
policy
and
say
that
the
comm
come
in
general
recommends
highly
recommends
to
assume
that
team
discussions
are
public
and
each
repository
or
chartered
sub
group
can
enact
their
own
rules
regarding
team
discussions
and
then
I
can
fight
this
fight
with
the
collaborators
I.
K
A
K
Then
and
then
also
delegates
enforcement
to
them,
which
is
another
thing
we
wanted
to
stay
out
of
with
moderation
team.
So
this
so
in
general,
I
recommend
that
team
discussions
will
be
considered,
even
though
they
are
not
strictly
public.
They
should
be
considered
public
unless
stated
else
by
a
different
Charter
sub
body,
and
they
should
enforce
it
on
their
own.
K
F
K
I
think
that
they
will
support
that,
just
as
a
general
recommendation.
I
think
that
we'll
get
consensus,
nobody
really
is
pushing
for
private
conversations
more
pushing
for
an
explicit.
You
know,
policy
or
recommendation,
or
you
know
some
decision,
because
this
is
a
new
feature
and
it
is
a
gray
or
a
feature.
F
F
L
Big,
thank
you
on
that.
One
turned
out
really
cool
yeah.
That's
another
thing!
That's
a
side!
Note
I,
wanted
to
add
me
and
Tracy
are
working
on
like
adding
a
bunch
of
new
products
in
the
new
store
and
just
to
have
swag
in
case
you
guys
wanted
to
have
something
at
conferences.
So
if
you
have
any
other
designs
or
any
interesting
ideas,
let
me
know.