►
From YouTube: Node.js Website Redesign
Description
A
Cool,
we
are
live
awesome,
so
we
are
looking
at
issues
number
156,
which
is
the
meeting
issue
for
website
redesign.
Let's
say:
yeah,
let's
dive
right
in
so
first
thing
on
the
list
here
is
issue
number
155
in
website
redesign
repo.
This
is
for
CFP
for
collapse.
Summit,
it's
live,
so
we
have
an
opportunity
at
the
club
summit
to
have
a
breakout
session
where
we
get
to
meet
in
person
and
hang
out
and
chat
for
any
and
all
folks
who
are
gonna
be
over
in
Berlin
for
the
club
summit.
A
B
A
B
A
Well,
it
sounds
like
we'll
have
a
good
crew
there,
the
Warrens
sitting
down
and
chatting
in
person
I'm
hoping
by
then
it
will
be
a
lot
more
activity
on
pages
other
than
the
learn
page
talk
about
a
little
bit
later,
but
I
guess:
let's
have
a
few
minutes
a
kind
of
open
discussion
like
you.
Can
you
think
of
any
good
like
focuses
or
topics
right
now?
Are
we
a
little
too?
A
It
was
interesting
to
see
how
the
pace
changed
the
dynamic
of
our
typical
open
source
work
it
might
be
worth
exploring
and
seeing
if
there
were
any
workarounds
that
we
needed
to
do
that
modified
our
tip
process
and
made
sure
everyone
was
able
to
get
the
work
done
while,
like
still
operating
within
the
constraints
of
open
source
and
the
time
zone,
difference,
etcetera,
etcetera,
so
just
kind
of
a
check-in
to
see
if
we're
still
functioning
well.
Even
though
we
picked
up
the
pace.
A
A
C
Folks
outside
it
will
be
also
cool
to
do
some
sort
of
filing
a
workshop,
maybe
to
get
new
people
on
board
because
I
mean
gasp
in
react.
Well,
if
you
don't
know
nothing
about
react,
it's
of
course
a
bit
difficult
to
get
in,
but
I
mean
this
vector.
Development
is
not
as
sophisticated
as
C++
I
mean.
If
you
do
a
small
workshop
and
just
tell
people
a
bit,
maybe
we
can
motivate
them
and
earned
a
mass
contributor
yeah.
A
A
Awesome
well
will
at
least
submit
the
the
CFP
and
I
guess
we'll
write
it
generically
enough
that
we
can
figure
out
exactly
what
it
looks
like,
but
it
seems
like
people
are
interested
in
kind
of
a
more
public
like
open
session
for
recalibration
and
onboarding.
So
we'll
frame
it
in
that.
In
that
sense,.
C
We
should,
of
course,
prepare
maybe
some
small
issues
so
that
people
can
work
on
it
because,
just
just
showing
you
around
a
bit,
it's
not
that
motivating
I
guess
for
people.
But
if
you,
if
some
I
don't
know
some
of
the
people
that
can
I,
don't
know
solve
some
issues
and
it's
made
small
features,
I
think
it's
really
quite
much
waiting
thing
to
do
and
also
that's
the
best
place
where
we
can
get
where
we
can
meet
motivated
people
who
can
potentially
work
on
the
know.
Chess
death.
A
We're
likely
to
see
onions
of
people
who
are
already
in
the
project
as
its
the
collaborator
summit.
So
if
we
were
to
structure
a
sort
of
workshop
to
know
well,
if
we
were
to
structure
a
session
where
we
would
get
people
on
board,
we
can
assume
that
they
have.
There
are
somewhat
familiar
with
the
project
already
and
we
can
focus
on
our
specific
implementation
of
the
website
and
just
just
how
to
get
set
up
and
running
how
to
run
tests
and
how
to
put
in
your
first
PR
I.
A
Remember
one
of
the
first
sessions
I
was
in
people,
told
me
how
to
use
I
think
when
you're
committing
to
node
instead
of
running
the
whole
suite
of
tests,
you
run
the
specific
command
and
just
runs
the
test
in
one
part,
that
was
I,
don't
think
documented
very
easily,
and
that's
this
very
thing
that
people
find
useful,
also
depending
on
the
audience
that
we
have.
It
might
be
helpful
to
chat.
A
If
we
haven't
notes
already
by
then
about
how
we
are
about
how
we're
planning
to
rethink
API
Docs,
that's
gonna
be
kind
of
the
medias
change
that
we
probably
make,
and
the
first
pass
will
likely
just
be
a
kind
of
a
reskin
of
the
current
static
pages,
but
there's
a
whole
lot
more.
We
can
do
there,
but
that
involves
changes
in
core
and
it
involves
changes,
and
you
know
Howard
how
are
is
storing
information
on
API
Docs
to
begin
with,
so
it's
gonna
be
much
larger
conversation.
D
Yeah,
that's
that
was
actually
my
interest
in
joining
this
call
before
some
I
haven't
hello.
Everyone
I
basically
haven't
been
working
on
no
js'
the
last
few
months,
but
in
fact,
the
last
time
we
had
the
collaborator
summit
in
Berlin
I
was
working
on
getting
a
internationally
internationalization
and
localization
set
up
for
the
API
Docs.
So
we
basically
got
a
whole
integration
set
up
with
this
third
party
service
bump
crowd
in,
and
we
have
a
repo
and
some
automation
that
pulls
the
website.
D
Localized
API
documentation,
so
I
just
wanted
to
drop
in
and
first
say,
like
sorry,
I
haven't
been
working
on
it
for
a
long
time.
I
know
it's
kind
of
like
probably
on
the
back
burner,
but
I'm
still
interested
and
still
curious
here
it
supposed
to
have
new
thoughts
on
how
best
to
kind
of
like
consume
those
dots
and
different
languages
that
might.
A
If
we
could
discuss
it,
awesome
yeah,
thank
you
for
joining
Zeke
and
I
hope.
We'll
see
it
in
here.
Marcus
translations
are
gonna,
be
a
huge
part
of
YouTube
for
structure,
concern,
moving
forward
and
we'd
love
to.
We
have
to
leverage
all
the
work
that
you
and
the
ice
and
anything
we've
done
to
get
it
flowing
to
really
succeed
at
it.
A
So
yeah
we
we
have
a
we
kind
of
have
a
need
to
talk
about
that
right
now
like
this
is
a
infrastructure
point
that
I'd
like
to
get
fixed
sooner
rather
than
later,
since
we
already
have
a
whole
bunch
of
textual
content
in
the
real
I
yeah,
rather
than
spin
off
on
a
tangent
on
this
I
think
this
probably
warrants
its
own.
Like
sit-down
discussion
about
yeah
with
the
this
is
the
core
focus.
A
D
It's
there's,
no
there's
not
really
anything
going
on
I
think
Ben
Mitchell
was
kind
of
running
out
for
a
while,
but
then
he
got
a
full-time
job
and
you
know
I
think
it's
kind
of
just
petered
out,
but
I
think
we're
still
definitely
interested
in
helping.
But
we
need
to
figure
out
how
to
give
the
project
lit
enough
legs
that
it
can
continue
moving
without
you
know,
a
few
specific
individuals
being
kind
of
responsible
for
keeping
it
alive.
D
D
A
C
A
Should
totally
do
that,
I
mean
it
would
probably
move
everybody
on
the
on
this
call
to
have
an
understanding
of
how
that
item.
Workflow
works,
so
I'm
I'd
like
to
like
get
a
get
a
brain
dump
from
you
on
the
current
infrastructure
and
where
all
the
data
currently
closed,
and
then
what
the
ideas,
what
the
ideas
were
for,
how
to
publish
this
and
how
to
share
this.
And
then
maybe
we
can
come
up
with
that
data
contract
that
that
we'd
like
to
see
to
be
able
they'd
be
great
with
it
best.
I
find.
E
A
We
don't
have
a
defined
spec
sheet
or
data
contract.
Maybe
it
just
makes
sense.
You
have
this
separate
meeting,
be
about
that
and
include
I
teen
and
in
the
process
that,
because
that
would
be
a
core
part
of
how
we
do
define
that
as
a
whole,
I
mean
that
way
that
that
meeting
could
continue
on
its
own
cycle
until
it
was
defined
with
as
much
input
as
necessary
for
my
team
and
anyone
else.
Who
has
a
stake
in
defining
that
data
contract,
yeah
I,
remember
pretty
good
insider,
just
drop
to
the
wayside.
I.
A
A
Yeah
a
knight
speak
now
forever
holy,
be
cool.
Zeke
and
I
commissioned
you
to
get
that
when
it's
good
sent
out
or
doodles
sent
out,
and
we
can
get
that
extra
meeting
going,
they
just
drop
them
before
next
website
redesign
meeting.
We
can
maybe
commandeer
that
yeah
and.
A
Weeks
this
time
on
Thursdays,
so
we're
not
to
see
in
your
more
often
because
it's
yeah
whole
bunch
stuff
happening
and
the
more
active
happy
and
engage
folks.
We
have
the
better
right,
okay,
so
yeah
it
would
probably,
since
we
typically
have
a
good
amount
of
stuff
to
talk
about
here
anyway,
like
with
specific
spin-out
meaning
for
talking
shop
at
all
would
be
be
helpful
if
we
can
get
it
set
up
for
next
week.
Otherwise,
good
all
right
sounds
good.
A
E
Yeah
I'm
excited
I'm
excited
to
be
a
part
of
this
meeting.
I
have
learned
about
the
learn
about
the
a
what
design
group,
sometimes
back
and
really
gotten
a
chance
to
come
on.
The
meeting.
Also
recently
we
were
discussing
about
I
mean
I
saw
it's
it's
something,
that's
that
has
actually
pick
up
in
the
group
and
I
picked
interest
and
the
impact
of
this
or
some
group,
so
at
least
focus
on
the
18
at
the
EPI
arrangements.
I
really
appear
order.
Thank
you.
Follow
me
and
yeah
yeah.
E
A
Get
the
data
flowing
for
that
all
right
cool,
let's,
let's
bring
it
back
in
we're
still
on
issue
number
one.
This
is.
We
were
talking
about
issue
number
155
I
can
spin
off
conversation,
but
moving
back
in
and
just
closing
closing
loop
on
on
this
issue.
We
will
get
a
CFP
in
place
for
website
redesign,
so
we
I
will
leave
it
at
relatively
open.
I,
don't
think
that
to
decide
what
the
exactly
done
it
is
yet
come
on
you're
muted,
if
you're
trying
to
talk
right
now,
I
think
yeah.
A
A
Take
the
silence
as
a
resounding
no
to
remove
the
label.
Yes
remove
the
label
we
will
update
when
yeah.
Thank
you
hold
me.
Do
that
I'm
so
bad
at
removing
labels.
So,
as
we
go,
resolution
and
meeting
will
submit
CFP
Mineo.
Can
you
help
me
out
and
at
least
get
the
issue
opened
up
I
or
they?
The
CFP
is
submitted
with
just
a
bunch
placeholder
content.
Yeah
totally.
A
Do
we
before
the
next
meeting
so
within
two
weeks,
a
yes
that
would
be
awesome.
Let's
do
that.
Two
weeks
is
plenty
we
could
continue
discussing
in
here,
I
suppose
we
could
link
to
the
notes
from
here
and
then.
If
anyone
wants
to
drop
more
ideas,
you
can
feel
free
to
do
that
here.
It
doesn't
just
have
to
be
ideas
from
this
meeting.
A
So
this
is
issue
number
61
and
157
in
website
redesign
drop-in
links
in
here.
So
we
were
supposed
to
meet
our
brand
spankin
new
designer
today
in
this
meeting.
But
unfortunately,
our
design
team
turns
out
has
had
an
all-hands
at
this
time
at
LinkedIn.
So
for
those
who
don't
know,
issue
number
157
was
opened
up
by
Oscar
Gonzales.
The
designer
who
works
with
me
on
the
design
sisters,
team
at
LinkedIn
he's
an
awesome
guy
and
he
is
psyched
to
help
out
with
website
redesign
which
go
figure
when
you're
redesigning
website.
A
It
helps
to
have
a
designer
so
I.
He
opened
up
an
issue,
that's
it's
kind
of
in
the
same
spirit
as
issue
number
61.
We
had
wanted
to
do
a
bunch
of
user
feedback
and
a
kind
of
a
documentation
survey
for
a
while.
It
turns
out
the
user
feedback
group
is
a
little
low
capacity
right
now,
they're
busy
with
other
other
things.
A
That's
already
been
done,
but
he
wants
to
roll
it
back
and
and
talk
to
this
new
group
who
is
not
around
when
we
were
having
those
initial
discussions
and
just
make
sure
it's
all
on
the
same
trajectory
so
definitely
drop
any
and
all
opinions
to
see
I'll
pop
it
into
the
Google
Doc
for
those
on
the
stream.
The
Google
Docs
LinkedIn
action
number
157
website.
We
design
any
and
all
ideas
in
there
feel
free
to
use
it.
A
Here
we
might
reach
out
to
foundation
folks
and
see
if
we
can't
get
them
more
formal,
a
survey
blasted
out
on
social
media
through
the
node
node
accounts,
which
would
be
awesome
data
for
him
to
collect,
but
I'm
gonna.
Let
him
leave
those
those
data
collection
efforts.
A
A
He
actually
he
held
up
personally.
Gatsby
is
one
of
the
documentation
sites
that
he's
really
enjoyed
recent,
like
he's
about
the
developer
and
a
designer
its
design
work
versus
development,
but
he
has
a
good
understanding
of
the
the
space
and
of
open
source.
So
it's
like
I
have
a
long
word,
but
yeah
drop
in
there.
Any
other
examples
that
it's
kind
of
designed
inspiration
for
him
as
he's
moving
forward
exactly.
A
Yep
I
yeah:
that's
where
we're
gonna
have
a
fun
choice
to
make
coming
up
next
of
what
you
know,
what
age
do
we
want
to
work
on
next?
You
know
we
have
a
learn
page
right
now,
there's
a
lot
of
other
content
that
needs
to
go
on
this
site,
so
we're
gonna,
be
a
health
Isaac
yeah,
we're
gonna,
be
a
having
it'll
part
should
be
guided
by
design
I
think
by
what
Oscar
comes
up
with
next,
but
we're
gonna
have
to
choose
where
on
the
site,
we
expect
to
focus
our
attention.
A
A
A
A
C
A
Yeah
is
there
a
not
to
beat
a
dead
horse,
but
from
a
technical
standpoint
it
has
allowed
for
more
scalability?
Was
there?
Was
there
a
concern
why
we
wouldn't
want
to
execute
on
this
now,
just
from
a
technical
standpoint
or
well.
C
The
biggest
concern
was
from
Matt
because
he
said
he
I've
seen
a
lot
of
people
messing
up
with
a
yum
configs
I
mean
Richard,
yeah
I
know
he
also
didn't
know,
I
mean
if
that
will
be
enough
for
our
needs
or
not,
or
will
it
cover
all
of
it?
We
don't
really
know
what
no,
what
we
need
it's.
The
single
thing
we
need
to
think
about
is
that
we
can't
move
documentation
around
that.
C
A
G
A
Okay,
awesome,
I
removed,
the
label
will
will
tackle
it
and
the
iPhone
and
meeting
actually
do.
We
have
a.
A
To
spin
out
the
how
we're
gonna
consume
the
API
for
the
documentation-
and
that
includes
ICN,
and
now
this
one
as
well
awesome
yeah,
just
make
sure
to
reference
the
ticket,
so
they're
they're
linked
together,
yeah,
awesome
cool,
so
next
issue
on
the
agenda
will
prob
you
pull
up
this
issue.
Judges
sit
you
up
and
it's
been
a
fight
scene
and
meeting
just
to
talk
about
architecture.
A
bit
more
that'll
be
a
real
shop.
A
A
Anybody
have
other
tools
that
they
prefer
and
would
like
to
pitch,
or
should
we
just
kind
of
give
the
green
light
here
and
see
if
we
can't
get
all
like
that,
they
contribute
it
thumbs
up.
I
will
respond
here,
real
quick,
it's
not
the
spell
named
after
a
very
quick
discussion.
A
A
Cool
awesome,
I'll,
remove
the
agenda
label
here
and
we'll
keep
the
conversation
offline,
we'll
see
if
Holly's
interested
in
doing
it,
and
if
not
one
of
us
will
pick
it
up,
sweet
and
the
last
issue
y'all
and
then,
if
we
could
get
to
this
issue
with
enough
time,
I
can
give
a
quick
brain
dump
of
my
current
understanding
of
I-10
and
efforts.
So
we
can
go
into
the
next
meeting
with
with
some
context,
which
I
think
will
probably
be
helpful.
A
G
Personally
think
that
if
we
can
ask
Tierney
to
get
some
from
the
docs
team
at
Microsoft
to
join
in
contribute
on
this
part,
because
I
really
love
how
you
know
the
current
documentation
and
Doc's
got
Microsoft
know
how
the
amulet
is
smaller
images
like
that
all
the
articles
were
that
are
pulled
through,
for
example,
here's
the
here's
an
example
articles.
You
can
take
a
look
at
contributors
and
they're.
You
know
get
her
counseling's
and
images
from
group.
If
they
can,
you
know,
learn
that
infrastructure
as
an
open
source
inclusion
that
would
be
fun.
Yeah.
A
Totally
and
similarly
it's
a
bit
of
a
boulder
presentation-
the
web
pack
also
has
a
similar,
a
credits
section
at
the
bottom.
I
believe
they're
both
pulled
dynamically
from
form
editors
and
yeah.
We
should
we
should
be
doing
the
same
thing.
I
also
hear
the
the
considering
that
the
the
contributors
list
is
going
to
get
too
long
after
a
while.
A
I'm
wondering
if
that's
an
early
optimization
like
how
many
actual
contributed
to
individual
Docs
are.
We
gonna
have
and
is
it
gonna
get
to
the
like
20
30
40
person
range
I'm,
not
entirely
convinced
that
that's
the
case,
but
I
agree
if
we
start
appending
multiple
contributors
to
some
sort
of
list,
be
it
the
little
chap
heads
that
a
mod
just
put
an
example
on
or
just
names
like
mdn
does
at
the
very
popular
page.
G
B
B
A
A
C
Just
wanted
to
mention
is
I,
mean
I,
actually
I'm,
actually
quite
happy
written
by
github.
Does
it
I
mean
when
you
look
at
react,
readme
page
it's
almost
50
contributors
and
I.
Don't
know
they
listed
a
couple
of
them
and
then
just
with
a
link
and
others.
And
then
you
have
you
get
lists
because
I
don't
see,
there's
a
way
to
deal
with.
I,
don't
know
a
list
of
hundred
contributors.
A
I'm
thinking
we
can
have
the
two-step
solution,
a
partial,
partial
solution,
which
is
a
tweet
of
where
what
our
existing
processes
and
long-term
solution,
which
involves
an
automatic
process,
but
in
the
short
term,
we
might
make
it
part
of
our
convention
that
if
anyone
does
submit
a
PR-
and
they
do
follow
a
certain
PR
process
that
that
process
outlines
that
hey.
You
should
also
add
your
name
to
this
particular
part
of
it.
A
G
Thing
one
thing
here
is,
quite
you
know
apparent
from
webpack
Docs
that
I
didn't
see
earlier
instead
there
for
the
menuing
entries
of
contributors
at
14,
whereas
actually
there
could
be
four
in
one
particular
file
that
I'm
looking
at
so
definitely
moving
towards
an
automated
solution
might
be
a
better
idea.
After
looking
it
I
think
no
documentation
would
have
much
bigger
scale.
Then
what
webpack
has
right
now
and
if
they
are
like
sixty
percent
behind
I'm
keeping
up
the
manual
entry,
then
we
might
you
know
if
you
think
about
automating.
It
has
well
yeah.
A
It's
something
else:
I'd
love
to
get
is
the
actual
like
Gravatar
image
or
some
type
of
profile,
image
added,
and
so
it's
possible
that
our
automated
solution,
like
I,
unless
you
use
the
same
email
you
signed
up
for
like
Gravatar
with
didn't
you're
in
your
get
commits
like
it's
likely
that
we
won't
be
able
to
grab
image
data
for
those
folks.
So
it's
it's
possible
that,
like
the
manual
solution
will,
if
you
enter
in
your
name
manually,
you
can
provide
a
URL
for
your
your
profile
image
and
everybody
else.
We
pull
automatically.
A
C
C
Calls
or
something
and
we
need
to
have
in
the
ipi
key
and
stuff-
and
I
just
didn't-
want
to
make
it
over
complicated
and
just
does
the
job,
and
we
should
definitely
well
consider.
How
are
we
gonna
do
it?
Do
it
statically
I
mean
pull
them,
pull
all
the
images
before
building
the
page,
because
I
mean
we
can
I
guess
afford
it
to
send
thousand
of
requests
to
get
talked
for
every
image.
So.
A
G
A
B
B
B
A
We
can
also
we
can
get
and
I
like
the
node
project
has
an
API.
We
can
get
a
guy
tokens
for
the
new
project
here,
specifically
game
production
builds
like
in
I.
Think
we're
talking
about
this
a
little
bit
before
in
dev
mode
like
you
might
be
limited
and
we'd
have
to
have
a
good
fallback
in
that
mode,
but
for
the
production
but
those
we
can
inject
an
API
key
or
no.
G
Probably
we
could
build,
get
affection
here.
I,
don't
know
that.
Could
you
you
know,
do
it
automatically
for
every
PR?
So,
instead
of
doing
it
for
every
entire
for
entire
build,
we
could
just
take
care
of
one
single
fear
and
the
factory
documents.
So
I
got
affection.
Just
like
we
are
doing
with
you
know,
DCP
run
where
it's.
B
G
B
Yeah
people
who
have
our
repo
and
then
there
is
appear
from
their
own
fork,
therefore
RK,
not
a
4lk,
sorry,
okay,
it's
good.
A
Yeah,
the
nice
thing
about
reserving
preserving
profile
images
are
actually
having
user
images
or
just
like
the
hand,
registered
members.
So
if
we
go
with
both
solutions
like
one
we
pol
get
of
history,
we
can
get
to
the
list
of
names
and
the
other.
We
have
that
guy
and
I
hang
curated
containers
list
the
hand
curator
banners
list
can
point
to
actual
like
static
RL
on
github
that
we
can
that
we
can
like
to
settle
like
it
sits
on
you
to
provide
your
image.
A
C
C
C
G
A
G
H
H
C
C
G
H
A
If
you're
listening,
github
we
apologize,
okay,
cool
I
will
pick
that
to
you
I
think.
There's
another
issue
open
for,
like
I
believe
it's
listed
as
like
attribution
face
to
where
we
wanted
to
pull
from
github
and
may
repurpose
that
issue
since
it
sounds
like
the
github
solution
is
overly
complicated,
like
we
might
mix
that
and
I
might
just
repurpose
that
ticket
for
just
getting
profile
photos
on
there.
Yeah
I
do
that
work.
What
about
the
color
in
the
side
over
honestly.
C
A
I
can
do
I'll
do
that
after
the
call
good
admin
work
cool,
that's
a
good
resolution.
I
like
it.
That's
everything
on
our
agenda.
We
have
a
eight
minutes
left
I
can
either
give
a
quick
brain
dump
of
the
current
state
of
an
end.
To
my
knowledge
as
of
like
eight
months
ago,
which
I
think
is
pretty
quick
or
we
can
give
you
a
give
you
a
leave
mins
back
well,.
C
C
B
B
Yeah
I
remember
there
being
some
effort
being
put
in
by
the
renegade
folks
earlier
I
was
missing
in
action
for
a
while
for
a
couple
of
months.
So
I
don't
really
know
what
happened
to
that.
A
Yeah,
unfortunately,
relationship
didn't
quite
work
out.
I,
don't
think
we'll
be
getting
getting
support
moving
forth,
but
we
have
the
designer
my
friend
from
from
Millington,
whose
works
in
the
under
the
scientist
and
Steen
who
I'm
psyched
to
be
getting
help
with,
and
we've
been
getting
limited
support
from
from
glitch
as
well.
So
we
can
re-engage
with
with
the
glitch
folks
too,
as
they
keep
playing
with
the
need
for
embeddable
code
as
well.
So.
A
Right
now,
on
the
subject
of
when
we're
going
to
design
the
data
contract
and
loop
into
ITN
folks,
does
everyone
I
just
want
to
get
a
show?
Who
wants
to
be
pinged
for
that
one?
Then
I
can
ping
you
on
the
issue.
Otherwise
you
can
decide
later,
but
I
don't
think
everyone's
handles
are
in
the
meeting
minutes.
So
if
you'd
like
to
drop
them
there,
I
can
I
can
pull
them
off
there,
but
I
think
I'll.
Just
unless.
D
A
Has
objections
we'll
just
tag
everyone
in
the
meeting
whose
handles
I
can
find
in
in
the
meeting
minutes
yeah
and
please
put
your
handle
in
the
meeting
minutes.
It's
it's
how
we
know
you
attended.
We
actually
have
a
tool
that
goes
in
and
scrapes
all
the
meeting
notes
and
makes
like
an
attendance
sheet
for
meetings
across
the
node
project,
so
I
it
does
actually
matter
yeah.
It
helps
us.
G
A
Yeah
yeah,
so
it
needs
to
be
under
the
every
I
drop.
The
the
google
docs
link
in
the
the
chapter
and
there's
always
a
participants
or
a
present
section
and
I.
It
looks
for
anything
that
looks
like
a
github
handle
underneath
that
header
and
pulls
him
out
and
marks
as
much
as
president.
These
always
get
PR
it
into
the
main
repo
under
the
docs
folder,
so
they're
just
hanging
I
was
marked
down
and
I
believe
once
a
day,
this
tool
crawls
all
the
repos
and
reverses
the
docs
folder
for
for
new
meeting.
G
A
G
A
That's
also
a
place
where
you
can
go,
I'll
contribute,
I,
think
it's.
It
hasn't
been
touched
and
in
months
myself
and
one
other
person
acted
together
in
a
day
or
so.
So
it
has
a
lot
of
room
for
improvement.
I
yeah
I
mean
you'll
drop
the
link
to,
but
it's
nodejs
participation,
Heroku
app,
calm,
yeah.
You.
A
H
G
A
So
every
single
node
working
group
or
committee,
you
can
see
it
in
the
community
committee,
repo
I
just
pasted.
A
link
has
that
that
meetings
folder,
which
just
is
this
long
list
of
every
meeting
minute,
and
so
this
tool
will
go
and
crawl
that
folder
I
think
once
a
day
and
and
pull
out
attendance
from
certain
repos
across
the
entire
org
I
believe
that
repo
list
is
hard-coded,
which
is
why
you
only
see
a
smaller
number
of
them
in
there.