►
From YouTube: Node.js Community Committee
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).
A
Great
thanks
everyone
for
joining
us
for
a
another
community
committee
meeting.
This
is
for
august
wow.
I
am
so
I'm
exposing
myself
there.
I
usually
have.
I
usually
go
up
to
my
mac
toolbar
and
look
as
I'm
saying
that,
and
it's
changed
in
mac
os
11..
It's
august.
A
B
Just
so
one
I
do
have
a
quick
update.
Past
couple
weeks
website
redesign
a
lot
of
progress.
A
lot
of
things
have
been
done,
a
lot
of
merging
like
a
lot
more
asynchronous
activity.
I've
been
very
happy
because
I
there's
there's
a
lot
more
people
getting
involved
and
that's
what
we
need.
We
have
the
meeting
today
at
2pm,
so
I
am
hoping
that
we
do
have
a
lot
more
participation
in
that
where
we
can
actually
tackle
some
of
the
issues
and
get
merge.
Requests
closed,
like
pull.
E
Can
someone
resend
me
a
reoccurring
calendar
invite
for
that
meeting?
I
don't
seem
to
have
it
right
now,
unless
there
isn't.
B
A
F
I
can
give
the
update
for
the
mentorship
initiative.
In
our
last
meeting,
we
worked
on
finalizing
the
blog
post,
announcing
the
position
for
the
examples
initiative.
We
also
worked
on
finalizing
the
code
challenge
for
that
opening.
F
F
Also,
we
acquired
a
new
member
for
initiative
or
we're
trying
him
out
it's
a
a
person
that
david
knew
from
another
project
he
works
on.
His
name
is
alex.
He
just
attended
our
first
for
his
first
meeting
last
week,
and
I
have
with
me
today
ademola
who
was
our
mentee
from
going
through
our
process
and
he
has
joined
the
team
and
he
is
this
is
his
first
comic
con
meeting
and
we're
going
to
be
taking
turns
he
I
david
and
probably
alex
eventually
on
giving
these
initial
updates
thanks.
D
Excellent
welcome
and
that's
it
great
tierney's
having
some
internet
trouble
so
I'll
help
kind
of
drive
some
of
these
things.
I
don't
think
we
have
much
of
an
agenda
list
today,
but
regardless,
let's
stick
with
the
initiative
updates.
Are
there
any
other
updates
from
initiatives
or
anything.
D
If
not,
I
can,
I
can
jump
into
the
cross
project.
Council
updates
lots
of
stuff
going
on
there.
We
are
amidst
the
election
for
what
we're
calling
the
community
seat.
The
secondary
cpc
board
director
seat.
The
way
it's
set
up.
We
have
the
primary
seat,
is
elected
from
regular
members
of
the
cross
budget
council
and
the
secondary
seat
is
open
to
anyone.
Who
is
what
we
call
an
active
openjs
collaborator
and
the
definition
of
that
is
in
the
in
the
repo.
D
But
it's
essentially,
if
you
are
working
in
a
project
or
in
the
cross
project
council's
work
or
any
of
the
sort
of
related
spaces,
then
you're
openjs
collaborator
and
are
eligible
for
the
seat.
We've
got,
I
think
five
or
six
people
stepped
up
and
they're
all
really
great
people
active,
engaged.
Folks
who
are
you
know,
I'm
really
glad
to
see
such
a
great
roster
of
people
who
nominated.
I
believe
that
is
ongoing.
The
voting
ends
on
monday.
D
I
think
voting
members
for
the
cross
budget
council
will
be
voting.
We
decided
that
that
would
be
the
best
thing,
because
that's
representation
across
all
of
the
projects
equally
or
you
know.
D
Equally,
as
we've
defined
it
and
so
yeah,
so
we'll
have
some
news
on
that
next
meeting,
also
making
some
progress
on
the
code
of
conduct
work,
we
had
a
a
working
meeting
last
week
that
was
productive,
and
so
I
think
we
are
working
out
some
of
the
initial
hurdles
and
then
can
start
to
really
document
things
and
move
forward
there.
There
are
a
couple
of
sticking
points
like
essentially
what
what
does
an
escalation
path
mean,
and
things
like
that,
so
there's
progress
there,
which
is
great.
D
What
was
the
other
thing
I
was
thinking
about
earlier?
I
think.
C
Think,
well,
I
think
I
mean
was
based
on
discussions
that
jury
had
had
with
tierney
as
the
suggestion
and
it's
it's
basically
the
concerns
with
the
escalation
path
was
to
were
around.
C
You
know
if,
if,
if
somebody
was,
for
example,
banned
from
a
project
or
something
like
that
that
then
that
would
be
overruled,
and
so
it's
the
clarifications
are
around
that
it's
it's.
The
escalation
is
really
the
only
there
for
cases
where
you
know
the
the
reporters
or
the
vic
or
the
you
know
the
people,
the
reportees
or
whatever,
that
you
want
to
call
that
group.
C
You
know
feel
that
it
it
wasn't
addressed
properly,
in
which
case
the
foundation
can
get,
can
be
involved
and-
and
you
know,
work
with
the
project
hopefully
come
to
it
to
come
to
a
good
resolution.
So
I
it
it
made
sense
to
me
I
think,
and
it
kind
of
like.
I
can't
really
see
that
the
foundation's
saying
to
a
project.
No,
you
have
to
take
a
person
back
that
you
don't
want
to
work
with.
Would
work
versus
the
oh,
you
know,
there's
something
happened
and
you
know
it's
it's.
A
Yeah
and
I'm
as
the
person
who
brought
this
up,
is
a
concern
while
doing
onboarding
for
electron.
I'm
relatively
happy
with
that,
like
the
concern
is
like
cool.
If
we,
if
you
know,
if
node
or
electron
bands
someone
for
like
you
know,
being
a
racist
or
something
I
mean,
there's
a
low
there's
like,
I
assume
that
their
the
cpc
wouldn't
like
force
us
to
like
unban
them,
but
it
the
way
it
was
kind
of
asserted.
A
It
was
a
possibility
and
that's
like
not
really
a
possibility
that
I
was
okay
with
or
like
comfortable
with.
I
guess
just
because
it
kind
of
this.
I
brought
this
up
in
the
other
meeting
if
this
very
much
feels
like
states
rights
which
feels
like
a
weird
topic
to
me,
and
that's
definitely
not
what
I'm
going
for,
but
it
you
know
it's
a
community
safety
thing
and
it
was
something
I
wanted
to
make
sure
we
did.
We
got
right
so
yeah,
I'm
happy
with
the
progress
there.
D
Yeah,
I'm
glad-
and
I
think
community
safety
is
really
the
guiding
principle
there
right.
We
don't
want
to
be
an
appeals
court
for
offenders,
but
we
want
to
make
sure
that
the
community
feels
safe
and
and
that's
any
concerns
they
have
are
adjudicated.
You
know
thoroughly
yeah,
so
yeah,
that's
that's
good
progress
that
we
are
all
on
the
same
page
there
and
can
document
some
things
there
and
related
to
that
cool.
So
I
I
think
one
other
thing
I'll
mention
is
we've.
We
we
meet
weekly
at
the
cross
project
council.
D
I
I
always
hope
that
we
have
less
work
and
and
don't
need
to
meet
weekly,
but
it
continues
on
at
a
pace
we're
we're
trying
a
new
time
that
is
a
little
more
european
friendly
and
maybe
beyond
so
we're
going
to
meet
at
1400,
utc
and
1800
utc
for
east
coasters,
that's
10
and
two,
and
and
what
was
that
1400
utc?
What
was
the
other
one?
D
D
So
I
want
to
raise
awareness
there.
I
feel
like
there's
something
else
that
I'm
missing,
but
I
can't
remember
what
it
is
so,
but
I
don't
know,
do
you
have
anything
else,
michael
or
anything
from
the
blog.
C
I'll
just
add
this
tomorrow,
actually
is
the
the
board
meeting.
I
don't
know
of
any
outstanding
asks
from
the
node
project.
In
particular,
we'd
had
a
vote
on
on
some
at
the
cpc
level
for
some
change.
C
Yeah,
not
getting
the
words
out
today,
a
small
change
to
the
charter
for
the
cpc
that
that
was
done
through
email
and
confirmed
and
the
the
only
other
one,
that's
sort
of
outstanding.
That
I
know
of
is
the
collaboration
network
proposal.
Where
there's
some
discussion
and
some
clarification,
we
need
to
add
in
terms
of
the
recommendation
for
the
the
default
license
to
be
used.
D
Yep
and
wow
okay,
my
brain's
not
working
either.
I
had
something
to
add,
and
now
I
just
totally
forgot
it
good
times.
D
Shoot
yeah
totally
lost
it
if
I
think
of
it,
I'll
I'll
I'll
bring
it
up
later.
So,
oh,
yes,
now
I
remember
the
other
thing
I
guess
worth
mentioning
well.
First
of
all,
we've
got
some
new
members.
Cpc,
which
is
great
mary
martini
from
the
no
tsc
got
a
couple.
Other
people
nominated
that
you
know
we
leave
them
open
for
a
week,
but
I'm
glad
to
see
more
people
getting
involved,
and
then
we
we
added
a
new
project
into
the
incubation
process.
Ajvjs
json
validator.
D
So
that's
that's
cool
too.
So
I
think
that's
most
of
the
news
cool.
So
anything
else
before
we
get
into
our
agenda
without
any
agenda
items
and
if
so
or
if
not,
what
should
should
we
talk
about
any
particular
issues
that
are
open
that
are
not
on
the
agenda?
I'm
thinking
of
one
in
particular.
A
So
I
do
have
just
one
quick
update
that
I
missed
the
window,
like
my
brain,
took
a
little
bit
to
to
a
little
too
slow
for
the
updates.
I
just
wanted
to
do
a
quick
update
on
examples.
I'm
working
on
reviewing
the
ibm
example
so
somewhat
I
went
through
created.
A
A
bunch
of
examples
are
issues
requesting
examples
for
various
platforms
that
I
know
have
employees
who
would
probably
come
and
write
those
examples,
because
that's
part
of
the
goal
is
to
kind
of
bridge
the
gap
between
hello
world
and
you
know
deploying
a
static,
app
or
spa
rendered
on
aws,
with
s3
buckets
or
whatever,
like
go,
bridging
the
gap
between
hello
world
and
the
full
node
experience.
So
I
went
through
and
created
a
bunch
of
issues.
A
The
ibm
folks
have
been
super
helpful
in
that
I
have
been
trying
to
make
time
to
review
the
examples
there.
Unfortunately,
I
have
been
stacked
on
other
other
things
I
have
to
prioritize,
but
there
there
are
two
examples.
So
there's
one
from
a
node,
I
I
believe
he's
a
tsc
member,
but
one
of
the
the
core
contributors
slash,
maybe
tsc
members
from
ibm.
C
A
Yes,
yep,
yes,
and
he
submitted
a
express
example
and
then
there's
an
ibm,
static
or
ibm
cloud
functions,
I
think,
is
the
name
example,
that's
very
comprehensive
and
just
trying
to
help
get
that
into
a
shape.
That
is
the
same
as
you
know,
the
the
structure
of
the
repo,
but
it
should
be
relatively
low
barrier
so
excited
to
move
forward
on
those
yeah.
So
I
just
wanted
to
make
sure
to
give
that
update
any
questions
on
that
one
before
I
answer
the
other
half
of
this
question
I'll.
D
Just
ask
really
quickly,
I
think
matt,
maybe
pulled
matt.
Who
did
the
cloud
function
stuff?
He
pulled
in
a
different
direction
at
the
moment.
So
if
there
are
updates,
maybe
just
mention
me
and
I'll
help
to
try
and
get
that
over
the
punchline.
A
Yeah
happy
to
help
work
with
you
on
that
at
all
cool,
so
the
other,
the
other.
The
agenda
item
thing
one
we
have,
we
do
have
I'll
just
speak
since
my
internet
seems
to
be
being
okay.
We
do
have
the
chairperson
election.
I
created
that
three
days
ago,
so
that
is
currently
sitting
in
the
comcom
repo.
It
does
have
the
cc
agenda
label
on
it,
but
I
did
not
go
through
and
like
do
the
copy
paste
into
the
agenda.
A
So
my
bad
so
yeah
there
is
the
agenda
thing
or
the
election
thing
open.
If
you
are
a
comco
member
and
interested
in
being
chairperson,
please
feel
free
to
self
nominate
yeah.
So
that's
there
and
then
there
is
an
additional
issue,
which
is
the
one
that
I
created
a
few
minutes
after
that
one
that's
about
inactivity
in
the
comcom
and
it's
and
it's
future,
and
I
don't
want
to
read
the
whole
thing.
A
But,
like
you
know,
it's
just
discussing
some
of
the
points
I've
been
thinking
about
for
a
while
here.
So
I'm.
D
Sorry
to
interrupt
you
tierney.
I
think
that
we
should.
We
should
definitely
spend
some
time
on
that
issue.
I
just
maybe
wanted
to
quickly
check
in
on
another
issue
before
we
get
into
that
one
should
renaming
the
default
branch
in
this
repository
a
couple
of
responses,
but
I
wanted
to
okay,
I
like
that
for
folks
and
not
responses
but
like
thumbs
up
thumbs
up
yeah
so
for
folks
who
you
know
want
to
just
take
a
peek
I
pasted
into
the
chat.
D
A
Yeah,
so
if
there's
there's
two
congo
members
who
thumbs
a
thumbs
up
it
just
okay,
no
there's
three!
So
you
know
if
we,
if
we
could
just
get
a
you
know
thumbs
up
on
that.
It's
like
I
can
do
this
in
10
seconds.
It's
I've
done
it
100
times
at
this
point,
it's
pretty
easy
and
not
gonna
really
impact
anything
well.
D
A
You
would
just
you
would
just
pull
down
the
the
main
branch.
You
don't
need
to
delete
anything.
I
I
don't
know
about
forks.
I
don't
know
how
the
interaction
is
there,
but
I
think
I
assume
it's
pretty
straightforward.
I've
not
seen
any
pain
you
do
have
to
retarget
prs.
So
they're
like
the
two
open
pr's
right
now.
Are
I
assume
targeting
master
it's.
I
can
do
that.
I
would
do
that
as
part
of
it.
Previously.
They
did
not
have
support
for
get
up
pages.
A
We
don't
use
that,
but
they
also
ship
that.
So,
if
that's
something
we
did
use
that'll
get
fixed
all
of
our
action
we
might.
If
I
don't
think
we
have
any
actions
right
now,
but
if
we
did
have
actions
you
would
need
to
just
use
the
default
branch,
rather
the
master
or
hardcoded
into
main
it's
pretty
straightforward.
Okay,.
D
Yeah,
if,
if
and
when
you
make
that
switch,
maybe
let
me
know-
and
we
could
both
just
kind
of
mess
around
with
it
and
see
if
that
pops
up
sounds
good
great,
all
right
so
on
to
the
the
bigger
issue
that
you
had
mentioned:
issue
639,
you
know
this
is
something
that
I
I
know
has
been
bothering
tuning
for
a
while
and
and
he
and
I
both
discuss
it
regularly.
I
had
commented
not
long
before
the
meeting
that
tierney
and
I
were
having
a
regular
kind
of
meeting.
D
It
was
actually
called
com
com-
revitalization,
because
we
both
been
thinking
about
this.
So
you
know,
I
think,
there's
just
some
concern
about
activity
and
and
making
sure
that
it
it
continues
to
make
sense
to
have
a
community
committee
and
the
you
know
overseeing
the
initiatives
that
are
under
its
purview
and
general
activity
in
the
space.
D
And
I
I
think
you
know
it's
it's
activity,
but
it's
also
like
I
mean
I
guess
this
relates
activity
we
we
need
to
go
through
and
update
documentation
and
things
like
that
as
well.
There's
there's
work
to
be
done
to
kind
of
sort
of
spring
cleaning
or
dusting
off
or
freshening
lots
of
documentation
in
com
com
as
well.
D
I
don't
know
what
what
are
your
thoughts
tierney?
Do
you
want
to
kind
of
sum
up.
A
Yeah,
so
it's
just
like
one
other
thing
I
mean
this
is,
I
think,
generally
a
problem
in
node
and
how
node
is
set
up.
So
I
I
don't
think
this
is
a
comcom
specific
thing
like
I
don't
think
it's
specifically
our
fault,
but
like
the
way
com,
where
the
way
there's
a
few
things
about
how
we've
set
up
comcom,
how
node
is
set
up
that
lend
to
inactivity
and,
like
I
don't
want
to
say,
like
exponential
growth,
but
like
something
along
those
lines.
A
There's
there's
a
word
that
I
can't
think
of
at
all,
but
basically,
like
you
know,
one
of
the
fundamental
things
when
iojs
was
starting,
which
I
for
those
who
aren't
familiar,
I'm
feeling
old
now
for
those
who
aren't
familiar
iojs
was
a
fork
of
node
and
that's
where,
basically,
all
of
our
current
practices
in
node
came
from,
we
iojs
merged
back
into
node
for
node
four,
and
that's
when
the
node.js
foundation
was
created,
which
got
merged
into
the
js
foundation,
is
now
the
open.js
foundation.
A
So
all
of
our
practices,
or
almost
all
of
them,
except
for
some
things
like
initiatives,
are
from
iojs
and
one
of
the
the
challenges
or
one
of
the
fundamentals.
Fundamental
values
that
I
just
had
was
like.
A
If
you
come
and
do
the
work
cool
you're
in
and
then
we
don't
ever
remove
you
so
like,
or
we
don't
ever
kind
of
audit
that,
like
retroactively
and
address,
like
inactivity
and
like
that,
was
definitely
impactful
in
evangelism,
because
we
had
a
bunch
of
people
who
were
interested
for
a
bit
and
then
weren't
able
to
continue,
and
so
it
literally
became
just
me-
and
I
I
think
that
that
has
kind
of
spread
throughout
the
project.
A
That's
a
different
subject,
but
I
think
there
is
there
were
some
attempts
to
address
that
in
compcom.
So
in
arch
I
believe
it's
the
charter,
it
might
be
governance,
but
in
one
of
the
two
there
is,
you
know
the
check
check
membership.
A
The
chairperson
is
to
check
membership
every
six
months
with
with
members
in
reality.
That's
something
I've
done
generally,
I
don't
know.
If
adam
did
it,
I'm
not,
I'm
not
sure,
but
I
know
that
I've
done
that
as
often
as
I
can,
I
generally
don't
do
six
months.
I
do
inactive.
A
So
folks
who
are
like
you
know,
haven't
been
around
or
haven't
been
participating.
I
you
know
ping
them
and
see.
You
know
if
they're
interested
in
continuing
we've
had
you
know
some
of
the
folks
who
have
stepped
back
step
back
because
of
that
just
because
they,
you
know,
realized
that
they
didn't
have
time
anymore
and
they
wanted
to
do
that.
But,
like
you
know,
we've
also
had
folks
who
stay
on.
That's
totally.
A
Fine,
that's
how
the
governance
works
right
now,
but
like
rethinking
that
and
like
considering
activity
and
like
automating,
that
basically
is
because,
like
the
required
requirement,
there
is,
if
they
say
yes,
cool
they're,
still
a
member
and
that's
imp
perpetuity
so
like
considering
an
activity
and
activity
and
stuff
like
that
is
also
something
we
tried
to
do
with
originally,
and
I
believe
we
moved
away
from
that
a
bit
because
of
how
one
of
our
values
is
like
code
commits.
A
Aren't
contributions
like
that's,
not
the
only
way
to
contribute,
and
so
it's
kind
of
hard
to
define
that
I
think
we're
in
a
better
spot
with
that
now.
But
you
know
there's
a
lot
of
stuff
around
that
and
I
think
that's
one
area
that
we
really
need
to
kind
of
refresh
another
is
just
cleaning
it
like.
A
You
know,
like
just
said,
cleaning
up
the
docks
like
there's
a
lot
of
outdated
or
incorrect
or
somewhat
broken
information,
one
of
the
things
I've
tried
setting
up
and
I
don't
think
I
don't
think
it's
going
to
work
for
us
right
now,
because
we
have
like
700
links
to
github
but
is
markdown
link,
checking
just
to
make
sure
that
old
links
aren't
broken.
There
are
definitely
broken
links,
but
we're
currently
getting
rate
limited
by
github
when
we
run
it
like
severely
rate
limited.
A
A
Despite
us
not
having
the
observer
class
anymore,
and
it
like
linked
to
an
issue
that
like
that
was
a
good
example
of
how
to
like
create
that
issue
to
become
an
observer
and
people
would
comment
on
that
saying,
like
hey,
I
want
to
be
an
observer,
which
is
fair,
like
I
can
see
how
that
was,
maybe
potentially
a
little
bit
misleading,
if,
like
english,
isn't
your
first
language
or
something
but
like
we.
A
That
was
in
there
for
quite
a
while
after
and
we
were
still
getting
comments
after
so
like
that
kind
of
basic
content.
Maintenance
is
something
that
I
think
I
think
we
can.
You
know
we
we
we
need
to
do
a
little
bit
a
little
bit
of,
and
maybe
you
know,
set
a
every
six
months
we
go
through
and
do
a
cleaning
or
something
along
those
lines.
A
So
yeah,
that's
that's
generally,
like
it's
just
kind
of
upkeep,
and
I
mean
another
thing:
is
I
don't
know?
I
don't
know
how
other
com
club
members
feel,
and
I
don't
know
like
I-
I
would
love
to
hear
from
y'all,
but,
like
I,
I
end
up
doing
a
lot
of
maintenance.
A
The
repo
so
like
going
and
closing
stale
issues
or
merging
the
pr's
like
I
I
think
I
end
up
doing
most
of
that
and
I'm
I'm
fine
doing
that
work,
but
I
also
I
I'm
not
sure
if
that's
cause
like
I
am
the
one
who
like
I
don't
know
if
it's
like
a
seeming,
a
perceived
expectation
or
if
it's
just
like
oh
yeah
he'll,
do
it
or
if
it's
just
not
not
thought
of
at
all,
I
don't
know
so.
A
E
E
It's
okay,
would
it
be?
Would
it
be
beneficial
to
maybe
define
the
kind
of
work
that
we
need
collectively
to
be
done
not
like
so
much
as
in
a
role-based
situation,
which
I
feel
like
is
what
you're
saying
you
think
that
some
people
are
kind
of
maybe
having
the
assumption
that
it
falls
under
your
jurisdiction
being
like
the
chairperson,
but
since
we
don't
necessarily
have
those
kinds
of
clear
roles
that,
like
usual
organizations,
have
in
terms
of
you
know.
E
I
don't
know
I'm
thinking
of
like
a
treasurer
and
that
kind
of
yeah,
but
I
I
think
it
would
probably
be
beneficial
to
make
a
list
of
the
like
usual
maintenance.
That
needs
to
be
done,
and
just
just
kind
of
like
checking
in
on
things
so
that
we
can
have
that
kind
of
like
chore
list
and
have
people
you
know
self-volunteer
for
the
things
that
they
can
handle.
E
Maybe,
as
just
like
an
initial
attempt
to
kind
of
even
out
the
workload
and
like
I
I
know,
I
commented
on
the
issue
saying
that,
like
I
have
now
the
time
and
availability
to
take
on
some
of
that
work,
so
that
you're
not
burdened
from
it.
But
I
see
what
you're
saying
in
terms
of
you:
don't
want
people
to
feel
like
they're,
not
able
to
do
certain
things
I
feel
like.
Maybe
people
just
don't
know
what
they
can
and
can't
do.
A
Yeah,
that's
that's
totally
fair
and
I
think
documenting
that
is
probably
a
good
thing
and,
and
potentially
that
could
be
part
of
us
going
through
and
cleaning
cleaning
up
all
of
our
documentation
as
it
currently
stands,
because
you
know
there's
a
lot
of
outdated,
stuff
and
stuff
like
that,
and
so
having
that
kind
of
update
and
bundled
into
that.
I
think,
would
be
good
as
a
way
to
kind
of
agree
on
how
to
move
forward
move
forward
from
there.
D
And
what
about
the
idea
of
you
know?
Maybe
an
off-week
meeting
too
to
just
work
on
some
of
these
things.
I
mean
tierney
and
I
started
a
document
that
has
a
list
of
of
things
that
we
found
and
some
ideas
and
and
even
some
things
kind
of
potentially
outside
of
comcom,
like
the
nodejs.org
get
involved
together.
A
D
I
haven't,
I
haven't
shared
that
hackmd.
Yet
if
you
want
to
chat
well
yeah,
I
mean
oh
yeah,
yeah,
okay,
so
here's
a
hack
md
that
that
tierney-
and
I
did
three
months
ago
so
yeah
like
like
like
they
said
it's-
it's
a
little
bit
outdated.
But
there
are
some
ideas
here
and
and
and
maybe
we
take
this
and
start
to
break
into
issues
or
maybe
one
issue
with
with
a
checklist
or
I'm
not
sure
the
best
way
to
manage
things
that
we're
finding.
D
And
I
think
some
of
this
is
even
beyond
some
of
the
core
things
that
that
that
tyranny
was
mentioning
but
yeah
thinking
about
ways
to
improve.
I
think
I
guess
I'll
just
say
really
quickly.
Michael
one
interesting
thing
that
that
that
tierney
and
I
have
found
ourselves
discussing
often
is
that
com
com
is
different
than
other
spaces
because,
like
the
tsc
has
tsc
work
around,
you
know
technical
questions
and
and
work,
whereas
the
comcom
is
really
meant
to
sort
of
oversee
its
initiatives
so
like
being
in
the
com.
D
Com,
isn't
really
as
important
as
getting
the
work
done
in
in
the
other
areas
as
well.
Sorry,
michael
go
ahead.
C
I
I
was
just
thinking
like
you
know
that
there's
some
specific
things
here,
but
the
real
challenge
in
my
mind,
I
think,
is
like
that.
We
need
active
champions
who
push
on
the
areas
that
I
think
are
not
being
pushed
forward
right
and
that's.
The
fundamental
thing
is
that
we
can
come
up
with
all
sorts
of
lists
of
things
we'd
like
to
do,
but
it's
more
about
you
know.
C
How
do
we
find
encourage
people
who
are?
You
know
have
time
and
are
excited
to
to
lead
certain
areas
forward,
because
I
think
everywhere
you
know
all
the
the
teams,
the
working
groups,
I'm
involved
in
there's
always
somebody
who's
helping
to
to
push
them
forward,
make
sure
the
meetings
happen
and
that's
what
kind
of
seems
to
make
the
progress
come
forward.
So
it
almost
be
like
you
know,
I
don't
know
on
the
the
comcom
side.
Is
it
worth?
You
know?
C
C
Yeah,
you
know,
or
even
is
it
time
to
start
to
think
about?
You
know
I
I
don't
know
like
I
think
we'd
want
to
come
up
with
like
here's.
The
things
we
think
are
the
most
important
and
you
know
if
we
haven't
managed
to
get
them
to
work
under
the
comcom.
Do
they
fit
at
all
with
the
openjs
cpc,
or
you
know
I
don't
know
like
think
outside
of
the
box
as
well
in
terms
of
trying
to
get
those
important
things
accomplished.
A
Yeah,
no,
I
agree
and
I
think,
like
you
know,
I
think,
we've
generally
done
the
the
ladder
model
there
of
identifying
things
and.
A
Not
having
the
people
not
having
someone
who
well,
I
think
one
of
the
challenges
we
have
is
you
know
we
have
someone,
we
might
have
someone
who
comes
in
and
wants
to
do
a
thing,
but
largely
because
this
is
not
like.
A
You
know,
working
on
node
core
work,
it's
harder
to
get
people
to
be
able
to
do
that
in
a
way
that
is
not
like,
like
you
know,
a
tenth
of
their
avail,
their
total
time
right
and
like
a
lot
of
the
things
we
do
need
to
do
are
more
than
like
you
know,
they're,
basically,
part-time
and
so
the
way
to
fund.
That
is
people's
jobs.
A
And
that's
that's
the
thing
that
I
think
we've
struggled
with
in
getting
people
to
getting
the
people
who
could
do
that
to
come
in
and
do
that
so
yeah
like,
I
think,
that's
a
big
struggle
for
us
in
that,
like
we
have
people
who
can
we
we
having
people
who
can
spend
a
large
amount
of
time
on
this
stuff
is
not
something
that's
been
easy
for
us
yeah.
I
don't
know.
A
I
I
think,
that's
that's
our
primary
challenge
and
that's
definitely
not
to
say
that,
like
the
work
that
people
do
isn't
appreciated
or
like
valuable,
I
think
to
see
the
results
that
we
want
to
see
it.
There
does
need
to
be
involvement
of
people
who
can
spend
a
lot
of
a
lot
of
time
on
this
to
be
able
to
see
them
as
fast
without
getting
people
without
burning
people
out
or
draining
them.
A
C
B
C
Right
and
so
kind
of
like
in
in
the
in
the
role
of
the
comcom,
you
know,
and
it's
it's
the
same
on
the
technical
side
with
the
tse
there's
like
lots
of
strategic
initiatives,
I'd
love
to
see
take
place,
but
they
they
require.
You
know
a
champion
who
has
time,
and
so
they
kind
of
happen
if
somebody
does
have
time
and
they
don't
if
they
don't,
and
it's
kind
of
like
are
there.
C
So
it's
that
are
there
things
that
we
think
should
happen
that
are
critical,
that
aren't
and
if
maybe
we
can
focus
on
that
set
to
see
yeah.
You
know
and
the
others
are
like.
Well,
that's
just
the
nature
of
an
open
source
project.
We'd
love
to
have
more
of
this.
But
you
know
until
there's
somebody
who
has
time
that's
the
way
it
is.
D
I
think
another
kind
of
side
to
the
coin
is:
is
the
on-ramp
or
or
the
visibility
of
how
you
get
involved
as
well
to
you,
which
you
know
maybe
isn't
as
important,
because
we
can
talk
to
people
and
stuff,
but
I
feel
like
if
things
were
clearer,
when
when
some
random
person
came
to
com
com
about
what
comcom
is
and
how
to
get
involved
and
the
status
of
things-
and
I
don't
think
it's
that
far
off,
but
I
think
it
could
use
some
help
as
well.
C
C
C
F
A
So
generally
the
current
I
mean
helping
out.
No,
I
mean
the
current.
I
believe
documented
path
is
working
on
initiatives
and
then
initiatives
or
people
will
self-select
up
into
comcom,
but
like
doing
work
in
the
comcom
repo,
no
there's
I
you
like
anyone,
can
come
in
pr
stuff
and
do
do
the
work.
Okay,
so
that
could
be
like
their
starting
point
is
to
like
help
work
on.
D
Yeah
working
on
working
on
com,
com,
stuff,
as
well
as
initiative
stuff
for
sure
and,
like
you
know,
the
website
redesign
is
a
great
example.
You
know
we
got
a
couple
people
there,
divya
and
ben
who
are,
you
know,
focused
on
trying
to
get
work
done
there,
but
there's
a
lot
of
work
to
get
to
get
done,
and
I
think
you
know
frankly
there's
some
like
management
work.
D
That
needs
to
happen
as
well,
so
to
really
kind
of
keep
keep
the
ship
moving
forward
in
a
great
way
so
like
being
able
to
help
people
be
successful.
There,
I
think,
is
also
important
as
one
example.
D
But
I
think
there's
a
lot
of
opportunity
too.
You
know
I
I
there
there
are
other
things
that
we've
thought
about
in
the
past.
You
know
I
wonder
about
like
a
a
content
team.
You
know
we
have
a
social
team
now,
but
I
I
wonder
about
you
know
the
the
node.js
collection
has
been
kind
of
stale
and
lingering
and
the
new
website
redesign,
and
and
should
there
be
more
content
coming
from
the
you
know.
D
My
thinking
was
that
the
the
node.js
website
could
be
a
canonical
place
and
we
could
have
content
coming
from
there
and
syndicate
out
to
dev2
and
medium
if
we
want
as
well,
but
you
know,
there's
there's
nobody
really
to.
We
would
need
a
few
people.
I
think,
to
kind
of
help
manage
something
like
that.
C
C
Like
a
content
team-
and
you
know,
individuals
might
focus
more
on
content
for
specific
projects,
but
kind
of
as
a
you
know.
If
you
span
projects,
you
might
have
a
chance
of
getting
a
few
more
people
and
therefore
a
bit
more
critical
mass,
and
I.
G
H
We
we
discuss
a
lot
of
that
stuff
at
the
marketing
committee
meetings,
which
everybody
that's
an
open
meeting,
so
projects
members
are
all
encouraged
to
attend.
So
that
might
be
a
way
to
you
know
to
discuss
some
of
those
things.
If
you
know,
if
that's
kind
of
the
the
audience
that
you're
looking
for.
C
A
Yeah
and
that's
that's
kind
of
what
I
was
trying
to
do
for
I
had
to
make
sure
I
wasn't
muted
that's
kind
of
what
I
was
trying
to
do
with
the
okr
stuff
that
we
did
at
the
opengs
world
in
december
november
that
you
know
maybe
we
didn't
get
as
high
attendance
as
we
had
hoped,
or
I
hoped,
but
you
know,
working
on
that
kind
of
stuff.
I
think
that's
potentially
a
good
way
to
do
that.
A
Just
trying
to
get
that
stuff
out
there
and,
like
you
know,
set
goals
for
ourselves
that
we,
you
know,
collectively,
agree
on
and
want
to
do,
and
you
know
refining
that
every
year,
maybe
every
six
months
and
saying
you
know,
did
we
accomplish
this?
How
we're?
How
are
we
successful?
What
can
we
learn
from
what
we
did
and
then
refining
that
into
okay?
What
do
we
want
to
do
in
the
next
year?
I
think
that's
kind
of
the
the
goal
with
that.
D
Yeah,
that's
interesting.
I
I
shared
it
in
the
chat
and
one
of
the
the
four
objectives
is
really
focused
on.
Essentially,
content
publish
create,
create
a
positively
impactful
contents.
Key
result:
publish
five
practical
tutorials
with
community
members,
run
three
amas
with
folks
from
our
ecom
system
and
feature
five
non-core
repositories
in
various
official,
officially
published
media.
C
Have
yeah,
I
I
think
right,
like
rachel's,
been
helping
to
drive.
I
C
H
Yeah
and
we,
you
know
those
are
available
to
all
projects.
However,
if
there's
an
interest
in
no
doing
specific
ones,
we
can
discuss
that,
although
there
have
been
node
specific
ones.
H
H
Yeah,
I
want
to
say
that
the
node
project
has
probably
done
the
most
out
of
all
of
the
projects
and
they're
all
very
well
attended.
We
get
good
participation
and
replay
views,
so
it
seems
like
a
good
outlet
for
this
community.
A
And
I
just
for
what
it's
worth
on
that
that
objective,
I
believe
that
was
largely
focused
on
node.js
collection
and,
like
you
know,
the
tutorials
make
sense
in
that
context
and
the
I
think
the
non-core
repositories
was
relatively
intentionally
vague
in
that
it
could
be
like
twitter
or
or
the
blog
right
and
so
yeah.
That's
that
that
has
we
have
evolved
out
of
or
away
from
the
collection
so
like
that.
A
You
know
that
would
be
something
we
look
back
on
like
well,
we
did
these
things
with
the
foundation
which
worked
well,
but
you
know
this.
This
is
like
we've
evolved
this
and
maybe
don't
want
to
structure
it
in
the
same
way,
because
this
thing
we
assumed
would
be
around
is
not
around
so
yeah.
That's
yeah,.
A
D
A
C
Yeah,
normally
we
do
too
and
that
that
is
something
I've
thought
about
once
or
twice
have
done
nothing
about,
my
preference
would
still
to
say
bs.
A
Yeah
for
what
for
what
it's
worth,
I
don't
think
we
should
do
the
same
system.
We
did
last
time.
I
would
be
happy
to
share
some
of
the
contexts
around
like
what
electron
just
did
that
worked
very
well,
but
yeah.
I
would.
I
would
recommend
that
we
don't
use
the
same
system
as
last
time
like
I
was
not
really
able
to
participate.
D
H
We've
been
collecting
a
lot
of
feedback
and
our
you
know
you
are
perfectly
aligned
with
what
with
what.
D
I
I
would
be
curious
about
the
electron
experience,
but
that's
probably
for
call
or
something.
A
Yeah
I
mean
the
the
tl
dr
is:
we
did
zoom,
plus
the
I
think
it's
called
mira
or
miro
yeah
mir
miro,
like
miro.com,
which
was
just
virtual
whiteboards
that
give
you
sticky
notes
and
you
can
use
those
and
we
kind
of
did
the
whole
structure
around
that
it
worked
pretty
well
but
yeah.
So
you
know
I
could
have
jacob
come
and
jacob
groundwater
come
and
talk
about
that.
If
you
wanted,
but
that's
you
know,
it
worked
pretty
well
for
us.
D
Yeah-
and
I
think
it
would
be
great
to
do
one-
you
know
potentially
around
node.com
for
you
or
sometime
in
that
sort.
C
Yeah,
I
don't
know
rachel,
you
were
active
in
the
summit
planning
group
right.
Was
there
any
discussion
of
doing
a
second
one?
There.
H
I
would
have
to
double
check
with
with
jory.
She
was
really
leading
not,
but
I
know
that
historically,
that
has
been
what
we've
done
so.
D
Yeah-
and
I
I
wonder
about-
and
I'm
just
kind
of
thinking
out
loud
here,
but
we
did
the
the
last
one
in
what
june
I
wonder
about
doing
one
in
a
time
that
people
might
be
less
active
at
work,
because
I
feel
like
maybe
around
the
time
of
note
comfy.
U,
there
might
be
a
lot
going
on,
but
maybe
like
january
or
february,
the
dead
of
winter
people
might
have
more
free
time
or
something
I
don't
know
if
that's
accurate.
But
I
I
wonder
about.
C
C
A
B
I
do
have
one
quick
thing:
I
just
remembered
that
we
might.
A
I
I
think
I'm
glad
y'all
are
open
to
that,
like
I'm
really
glad
to
hear
that.
A
So
for
context,
I,
if,
if
there's
someone
who's
willing
to
do
that,
we
should
absolutely
try
to
help
enable
that.
However,
we
can
one
of
the
pieces
of
context
that
I
guess
I'd
like
to
share
is
we.
A
We
definitely
tried
to
do
that
early
on
in
comcom
and
had
very
little
success,
getting
people
who
were
able
to
do
that
in
a
in
a
successful
way
or
a
way
that
would
that
they
were
happy
with
in
so
I
I,
if
there's
someone
absolutely
I'm
happy
to
spend
extra
time
on
trying
to
help
make
that
work
and
get
that
through.
I
would
not
hold
your
breath,
is
I
guess
the
best
I
can
say
just
because
of
experiences
with
how
that's
gone
in
the
past.
A
I
also
realized
I'm
completely
foreshadowing
and
like
or
not
foreshadowing,
but
like
being
super
negative.
So
apologies
I
I
will
you
know,
as
I
said,
I'm
more
than
happy
to
help
enable
that.
However,
I
can.
D
Yeah
and
frankly,
I've
been
trying
to
to
jump
in
and
help
there,
but
it's
just
I
don't.
I
one
don't
have
a
lot
of
free
time
and
two,
I
think
the
the
meeting
time
directly
conflicts
with
another
important
meeting.
I
have
and
I've
even
asked
around
internally,
because
we
have
a
lot
of
gatsby
and
typescript
folks
internally,
but
I
haven't
I'm
scrolling
right
now
to
see
if,
if
I've
gotten
any
responses,
but
I
haven't
seen
anything.
A
D
Two
ideas
that
I
have,
I
guess
one
particularly
related
to
this-
is
maybe
we
have
an
off
meeting,
bi-weekly
or
whatever
that
you
know
tierney
and
and
me
and
and
rachel.
I
think
you've
expressed
interest
and
and
divya
and
ben
kind
of
get
together
and
huddle
and
see
where
things
are
and
make
sure
we're.
Staying
focused
on
you
know,
like
mvp
kind
of
related
tasks,
obviously
open
source.
D
Sometimes
people
are
going
to
just
do
what
they
are
drawn
to,
but
if
we
can
try
to
focus
on
getting
some
hurdles,
clearing
some
hurdles
and
maybe
we
can
make
more
progress
and
make
the
path
for
people
to
help
more
clear
and
beneficial
I'd,
be
open
to
that
and
then.
D
Similarly,
as
I
suggested
in
the
issue
around
an
activity
in
com
com
and
thanks,
rachel
romoff,
you
know,
maybe
we
should
have
a
regular
meeting
to
work
on
comcom
related
things
to
start
with
the
okrs
and
go
from
there
too.
B
Yeah,
I
think
I
think
that
would
actually
be
a
good
step,
a
first
step
in
the
right
direction
and
then,
as
we
progress
or
build,
we
can,
you
know,
see
what
next
steps
to
take
and
in
the
meantime,
if
you
know
as
turning
you
mentioned,
I
think
that
you
know
you're
you've
been
helping
us
and
I'm
I'm
very
grateful
for
that,
because
it
was
just
me
and
ben
a
couple
weeks
ago
trying
to
run
everything
and
do
stuff
as.
I
B
And
we
were
kind
of
lost,
but
now
that
we
have
more
people
involved,
I
think
you
know
that
that
gives
us
more
confidence
in
moving
in
the
right
direction.
So
definitely,
let's
set
up
a
meeting,
and
that
would
be
great.
I
think.
D
Cool
yeah
yeah,
I
think
if
we
could,
if
we
could
highlight
like
mvp
related
issues
and
have
like
a
project
board
and
drive
people
directly
to
that
too,
would
be
great.
You
know
to
really
get
get
some
some
movement
in
the
right
direction.
D
Sounds
good
I
I
have
to
drop
as
well
so
yeah
so
well,
maybe
I'll!
Maybe
we
should
have
an
issue
for
a
com
com
related
off
meeting
and
and
maybe
an
issue
and
website
redesign
about
a
a
project
management
do.