►
From YouTube: Node.js Website Redesign
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
Awesome
we
are
live
on
YouTube,
so
hi
everybody
tuning
in
and
welcome
to
another
episode
of
website
redesign
yeah.
So
the
agenda
item
is
the
agenda.
Is
issue
number
146
and
website
redesign
Rico.
You
know
follow
along
there,
but
quick
before
we
even
get
started
with
going
through
agenda
items.
First
and
foremost,
congratulations,
everybody!
We
hit
the
hot
dev
lunch
deadline,
I
like
that
is
amazing
that
we
turned
around
such
a
slick
whip
inside
so
fast
and
we're
able
to
get
it
up
and
live
on
Nijs
dev.
It
is
awesome.
A
Let's
do
that
thing
up
in
live,
I,
think
that's
when
we
can
all
be
very
proud
of
I,
so
let's
keep
making
it
even
better
I,
yeah
I'll
say
on
that
and
we
pat
yourself
on
the
back
cool
starting
at
the
top
and
going
down.
Since
we
got
a
lot
of
process
to
talk
about
today,
chunk
through
it
and
then
at
the
end
we
will
start
looking
at
other
untagged
issues
and
triage
some
of
the
project
board
if
we
have
extra
time.
A
But
first
item
on
the
agenda
is
issue
number
103
over
in
know
das
dev.
This
is
mostly
just
an
announcement,
since
it's
already
done,
although
we
do
need
to
write
a
little
paragraph
describing
our
merge
preferences
here,
a
notification
that
miles
turned
off
the
merge
button.
We
should
all
be
rebasing
and
squashing
if,
if
possible,
to
keep
up
in
the
history,
clean
I
will
personally
take
up
a
task
of
just
going
in
and
adding
this
to
the
the
readme
before
how
we
prefer
to
get
merged
in
and
I'll
close
a
stick.
A
C
C
A
A
So
the
player
RC
formatting
rules
added
number.
Ninety
still
look
fairly
slim,
so
it's
a
pretty
loose
enforcement.
It
looks
like.
Are
there
more
restrictions
that
we're
interested
in
putting
on
there
or
should
we
like?
Are
we
happy
keeping
it
slimmer
right
now?
I
know
that
there's
a
bunch
of
linting
rolls
like
the
industry
standard
is
the
Airbnb
of
linting
rules.
I,
don't
know,
there's
a
prettier
RC
like
Airbnb,
packaged
that
we
can
install.
E
So
in
here
is
the
we
have
a
few
things
that
are
actually
redundant
like
semi
is
true.
By
default.
We
don't
need
to
include
that
and
then
bracket
spacing
is
also
true
by
default,
so
we
could
cut
that
out.
The
last
one
is
a
little
debatable
jsx
bracket
same
line,
I
personally
find
closing
it
on
a
separate
line
to
be
more
readable
and
matter
of
personal
preference,
but
in
the
default
that
comes
with
prettier
is
it
actually
puts
closing
brackets
on
a
separate
line.
C
E
E
A
And
I,
so
the
I
know
that
semi
and
and
the
other
feature
flags
are
default.
True,
but
I
don't
know
if
there's
harm
and
keeping
it
explicitly
called
out
in
the
prettier
RC
like
new
folks
coming
in
and
looking
at,
it
will
like
very
explicitly
see
what
we
have
enabled.
So
if
we
feel
like
this
isn't
a
happy
place,
I
think
we
can
probably
close
the
ticket
and,
let's
say,
there's
objections
from
anybody
else.
If.
E
F
E
A
Know
that
we
have
the
TS
link
and,
like
our
our
current
es,
lilin
config,
extends
that
Tia
sled
config
prettier,
which
will
I
think
bounteous
went
into
abiding
by
a
prettier
config.
But
if
there's
a
plugin
that
will
auto
rewrite
our
typescript
to
adhere
to
TS
length.
Is
that
what
you're
saying
then?
We
should
probably
use
that
because.
E
B
A
C
A
A
So
there's
there's
configuring
TS
link,
so
you
get
linked
warnings
that
are
in
line
with
the
prettier
config,
so
I
think
jessalyn
config
prettier
only
I
will
take
the
prettier
config
and
make
sure
your
TS
don't
configure
Gray's
with
it.
I
think
what
owner
is
saying
is
there's
a
prettier
plug-in
which
will
read
your
TS
line,
config
and
rewrite
based
on
that.
If
that
exists,
and
if
it
plays
well
with
the
eslint
like
we
should
experiment
with
it.
Well,
it
sounds
I
go.
B
A
B
A
A
Misspoke
I'm
sorry
didn't
see
I,
but
yeah
yeah
go
ahead
and
play
with
it
open
up
the
PR
if
it
seems
to
work
pretty
smoothly
and
we'll
discuss
it
in
the
issue
cool.
So
we
are
just
changing
JSX
same
line
to
false,
and
then
we
can
close
this
ticket
right
cool,
and
so
we
will
rerun
number
97
with
the
updated
config
to
make
sure
that
that
bracket
rule
is
captured.
And
then
we
can
sounds
like
a
win.
We
can
merge
that
in
as
well
one
block
that
large.
A
C
B
B
A
Just
I
was
telling
Aguirre
that
I
was
meeting
him.
Cuz
he's
got
a
lot
of
background.
My
second
area,
okay,
moving
on
I
cool,
so
next
issue
is
issue
number
127.
How
do
we
want
to
add
new
members?
I?
Think
it's
fairly
settled.
I
just
want
to
make
sure
we
have
done
census
in
the
meeting
and
then
we'll
write
it
up
in
our
governance,
so
miles
open
up
a
very
good
question.
How
do
we
want
to
bring
new
members
into
this
group
and
get
people
commit
bits?
A
A
A
E
C
A
B
B
A
A
Awesome
I
will,
in
my
PR,
for
adding
new
members,
also
include
an
attendance
policy
which
we
can
comment
on
in
the
PR
and
in
policy.
A
A
There
we
go
cool
next
issues:
number
150
over
nodejs
dev,
we
yeah
so
no
periods
at
end
of
commit
messages.
I
personally
have
no
objections
to
this.
It
was
in
the
config
that
I
copy
pasted
over
from
another
project
that
work
on
I
I.
Don't
think
anybody
does
anybody
feel
strongly
in
any
one
way
or
the
other
about
this
yeah
I
think.
C
C
A
A
It
was
from
a
while
back
where
we
captured
all
the
content
that
we
might
want
to
migrate
onto
a
full
site
from
the
current
foundation
website.
A
lot
of
our
previous
plans
for
foundation,
site
integration
with
the
new
site
ia
got
kind
of
upended
by
there
by
the
foundation
merger.
So
this
is
just
a
capture
the
bare
minimum.
A
What
we
might
want
to
migrate
over
in
the
merged
foundation,
world
I
think
it's
possibly
a
little
too
early
to
be
talking
about
this
still
and
I'd
like
to
see
what
what
we
can
get
from
a
designer
for
sure
to
get
all
in
and
a
lot
of
it
actually
already
fits
into
where
their
current
wireframe
is.
So,
if
people
only
need
to
talk
about
this,
a
little
more
I'm
happy
to
to
dedicate
some
time
to
it.
Otherwise,
I'd
like
the
punk
did
for
when
we
have
some
more
site
structure.
Conversations.
No
more
can.
C
G
A
My
my
personal
hope
for
this
this
page
and
what
do
we've
chatted
about
with
with
miles
and
another
folk
is
no
js'.
Dev
will
kind
of
be
the
staging
ground
for
the
next
version
of
the
node.js
website.
I
think
we
can
all
agree
that
the
current
node
website
is
not
a
part
with
what
we
expect
of
a
large
open
source
project
at
the
moment.
A
So
I
was
very
excitable
miles
approached
us
with
with
the
dev
offer
from
Google,
because
it
gives
us
an
official-looking
space
to
start
iterating
on
a
next
version,
so
we
needed
to
get
the
learn
page
out
as
just
initial
content,
just
to
get
it
out
in
time
for
the
dot
that
lunch,
but
from
here
on
out
I
want
to
start
releasing
more
and
more
sections
of
the
site.
A
read
of
remade
site
on
node.js
dev
there's
been
a
good
chunk
of
work
already
on
site,
IA
and
wireframing.
A
So
I'll
drop
these
links
again
in
the
chat
folks
listening
online.
These
are
in
old
issues
in
the
website
redesign
we
go,
but
a
lot
of
this
started
out
with
a
rather
meaty
medium
post,
reduce
link
to
in
the
chat
it
evolved
into
an
information
architecture,
discussion
and
the
website
redesign
repo
and
a
envision
project
board
with
full
wireframes.
A
So
my
hope
is.
We
will
continue
to
implement
or
execute
against
these
the
the
envision
wireframes
it
just
link
to
which
now
that
I
finally
found
a
very
excited
design,
resource
sue,
I,
work
right
next
to
and
can
you
know,
keep
on
task
I'm
excited
to
push
forward
of
this
yeah,
that's
the
eventual
plan
and,
and
once
sorry,
once
we
have
kind
of
content
parity
with
with
the
current
site.
My
hope
would
be.
We
switch
over
the
website
and
make
for
the
content.
We
have
another
guest
dev,
the
official
node
website,
building
board.
C
So
basically,
we
have
this
unique
opportunity.
We
can
move
toward.
You
know
all
of
the
developers
to
have
domain
and
just
you
know,
move
the
dot
or
domain
to
more.
Like
a
foundation's
website.
People
interested
in
deviating
to
the
toward
event
put
join,
and
you
know
read
about
what
feeling
to
just
you
know,
remember
the
side
and
put
it
on
dot
instead
of
yeah.
A
I
think
there's
we
need
to
talk
with
the
current
website
working
group
to
talk
about
how
how
we'd
want
to
be
planning
that
switchover
I'm
I'm
personally,
not
sure
what
will
be
the
best
option,
you're
switching
to
redirecting
to
dev
for
redirecting
devs
org
down
the
line
there,
but,
to
be
quite
honest,
I
think
we're
we're.
Often
they
were
two
months
out
from
from
having
to
worry
about
that.
So
there's
a
lot
of
time
to
talk
about
that
switchover,
yeah,
I,
I,
don't
know
what
the
best
approach
would
be
for
that.
G
D
Know,
I
personally
think
we
should
leave
the
discussion
for
the
websites
team
to
see
how
a
foundation
that
no
joke
so
moving
everything
towards
no
judge,
that's
every
character
you
know
should
not
be.
The
discussion
was
finishing
of
the
projects
and
everything
later
you
know,
key
foundation
is
being
made:
what's
our
status
of
all
the
DOJ's
al-assad
foundation
website
or
our
redirects
and
everything.
So
as
the
tech
I,
don't.
A
You
know
face
of
the
the
current
nodejs
website
and
he's
I
think
open
to
a
whole
slew
of
different
options.
So
we
can
I'd
love
at
some
point
down
the
line
when
we
have
a
more
content,
parody
site,
it's
actually
sit
down
and
have
a
like
a
dedicated
conversation
on
we're,
starting
to
think
about,
like
we're
almost
ready
to
do
sometimes
yeah.
C
A
C
A
Don't
want
to
approach
this
and
have
this.
You
know
a
holistic
conversation
on
it
with
the
yes,
exactly
right
website
couple
maintained
errs
exactly
yeah.
That
would
be.
That
would
be
my
thought
for
the
using
node.js
org
as
a
foundation
site
I.
Think
that
would
make
a
lot
of
sense
if
the
node.js
foundation
wasn't
going
through
this
big
merger
process.
A
Right
now,
it's
likely
they'll
take
a
new,
a
new
and
identity
and
they'll
start
having
they'll
have
a
new
property
in
place,
so
we're
kind
of
waiting
for
the
cards
to
fall
on
that
to
see
what
what
resources
will
be
needed,
yeah,
so
TL,
BR
dot
dev
is
the
current
staging
site
for
the
new
the
new
website
and
we're
gonna
figure
out
in
the
coming
months.
What
a
switchover
plan
might
look
like.
C
I
want
people
to
go
to
dot
dev
in
actually,
you
know
have
some
sort
of
a
live
demo.
Sort
of
things
very
note
is
already
installed
and
instead
of
you
know,
fundamentally,
node.js
website
has
always
been
about
just
downloading
node.
So
maybe
we
could.
You
know
further,
along
in
the
recession,
mock-up
spin,
that
designer
friend
you're
talking
about
it'll,
move
towards
erection,
mm-hmm.
A
Yeah
I
really
want
the
new
website
to
be
a
resource
for
learning
in
education
and
community
as
much
as
download
buttons.
I
think
both
are
very
important,
but
one
has
been
very
underserved,
so
I'm
excited
to
see
where
we
can
take
it,
but
yeah
we
read
through
if
you
haven't
already
anybody
on
the
call
or
anybody
listening
in
right
now,
I
definitely
read
through
that.
Medium
are
that
first,
medium,
article
I
posted
it
kind
of
it
was
really
fun
to
do
this
competitive
analysis
of
like
ten
different,
big
industry
coding
there.
A
You
know
language
websites
I
and
compare
and
contrast,
features
and
pick
and
pick
and
choose
what
will
work
best
for
node
moving
forward
and
everything
in
there
is
thoughts
and
ideas
and
nothing
is
set
in
stone
like
where
we're
gonna
make
something
awesome
together.
This
is
just
a
starting
point,
but
at
all
I
think
it'll
give
a
good
idea
for
what
the
what
the
longer
term
vision
for
for
dev
is
moving
forward.
We
also
get
to
have
that
fun
conversation
of
what
does
the
dot
the
property
turn
into
after
a
potential
site
switchover
I.
A
C
A
Are
we
working
off
of
already
so
we'll
just
ensure
that
it
doesn't
get
dropped
as
we
keep
moving
forward
number
61
and
website
redesign,
so
this
has
been
open
for
a
while
as
well
I
failed
miserably
in
taking
this
to
the
user
feedback
working
group
a
long
time
ago.
We
wanted
to
start
getting
some
feedback
on
how
people
think
the
docs
can
be
improved
and
we
had
a
whole
survey
prepared
we're
gonna
start.
You
know
collecting
feedback
and
information
from
folks
about
their
ideas.
A
A
Yeah
leave
feedback
for
it
in
line
and
the
issue
and
I'm
sure
it's
a
little
bit
out
of
date,
but
the
the
folks
in
the
user
feedback
section
will
also
have
some
context
on
what
in
how
we
should.
We
should
ask
these
questions.
There
is
currently
a
Google
Form
draft
created
with
a
whole
bunch
of
questions.
Yeah
I
yeah,
like
I,
said
I'm
sure
it's
a
little
out
of
date
for
where
we
are
now
in
the
process.
C
Yeah
one
other
thing
that
I
have
been
looking
at
different
documentation
teams
for
sample
at
Regis
and
at
the
documentation
of
Asia
is
constant
ability
to
you
know
having
that
edit
at
github
link
getting
the
community
to
not
just
only
contribute
to
improve
the
documentation
right
after
its
release.
C
For
example,
I
maintain
this
shade
of
pervious
core
and
whenever
and
you
release
happens
more
probably
one
or
two
setting
from
the
theme
color
reference
is
missing
and
I,
hey
I,
somehow
ended
up
always
contributing
that,
so
we
can
kind
of
convert
the
community
to
not
only
start
contributing
by
having
also
you
know
kind
of
have
that
feedback
in
this
form.
That
is,
that
important
to
you
to
have
an
edit
on
github
button.
Inside
of
you
know,
whatever
yeah.
A
C
A
Yeah,
we
landed
the
edit
this
on
github
link,
as
it
was
page
on
github
link.
I
would
love
to
see
it
more.
Prominent
and
I
might
just
go
and
take
a
pass
at
styling
it
up
and
maybe
sting
it
at
the
top
of
the
document
instead
of
the
bottom,
because,
like
yeah,
that
is
a
very
important
feature
to
drive
community
engagement.
A
D
A
A
Some
chugging
right
along
issue,
number
147
in
website
redesign,
I
literally
just
opened
this
and
I
figured
I'd
just
get
the
conversation
started.
We
originally
started
this
initiative
in
the
website
redesign
repo
in
no
js'.
We
spun
out
a
separate
repository
for
working
on
the
node.js
dev
site,
but
now
the
center
of
gravity
has
been
a
little
split
between
the
two
repos
and
I've
encountered.
A
A
So
we
have
a
single
source
of
truth
for
both
development
and
administration,
and
we
don't
have
this
weird
split
between
repos
I
could
also
see
the
argument
for
the
counter
where
we
want
to
leave
dev
as
full
development
like
why
I
have
admin
tickets
in
there.
Why
clutter
it
with
meeting
minutes
and
have
the
admin
specific
repo
and
website
redesign
and
just
document
the
heck
between
the
two
and
make
sure
that
the
distinction
is
clear
for
what
they
are
so
I
see
arguments
for
both
but
I
think
we
should.
E
E
C
Like
to
having
a
single
source
of
only
be
easy
for
everyone
to
manage,
but
also
I,
think
having
meeting
nodes
and
all
of
this
admin
stuff
and
that
node.js
developer
would
you
know,
encourage
more
people
to
engage
and
those
you
know,
meeting
notes
are
more
opinions
and
be
more
inclusive
overall,
maybe
we
end
up
with
more
contributors
just
by
having
that
in
there.
So
definitely,
yes.
A
Awesome
anybody
have
counter
pinions
it
can.
We
say
general
consensus
on
this.
Call
that
merging
sounds
like
the
preferred
solution
for
folks
here.
Sweet
I
will
run
it
by
mini
Laswell,
who
I
don't
think
we'll
have
too
many
objections,
fingers
crossed
and
then
well
yeah
I'll
go
through
the
process
again
that
switched
over
there's
some
I
infer
work
on
in
for
tweaks.
D
The
meeting
the
meeting
notes
in
notice
that
the
just
leaves
concern
around
it
once
will
be
clustering,
the
actual
repo
it's
so
many
steps.
I
said
that
concern
I
think
is
really
really
cool.
Putting
everything
in
one
place.
It's
the
initio
plan
for
workday
website
redesign
initiative
was
supposed
to
be
closed.
Maybe
after
we
are
doing
with
website.
A
Redesign
right,
yeah
I
think
this
would
just
be
kind
of
moving
the
center
of
gravity
for
where
work
is
being
done,
a
lot
of
a
work
and
as
long
as
I
think
as
long
as
our
archive
admin
files
don't
step
on
any
of
the
website
source
code
files,
which
I
think
we
should
be
fine
with
just
I'm.
Looking
at
the
file
structure
here,
I,
don't
see
a
reason
why
it
would
cause
problems
for
the.
C
G
A
A
little
bit
of
tooling
in
place
for
like
automatic
attendance
tracking
that
relies
on
the
meetings
folder
being
top
level
and
and
accessible
when
possible,
but
we
can.
We
can
definitely
look
into
that
as
well.
Something
else
that
I've
seen
done
is
for
documentation
and
read
those
like
this
turn
it
into
a
mono
repo
and
have
different
homes
for
different
resources
here,
which
we
could
also
consider,
and,
in
fact
early
on
Myles
and
I
chatted
about
you.
A
A
I'll
open
a
separate
issue
and
we
can
talk
offline
about
about
mono
repo
stuff,
specifically
something
it
might
be
a
little
bit
too
early
since
we're
almost
in
one
Gatsby
project
hanging
out
and
doing
doing
on
a
single
website,
but
I
could
see
a
need
for
it
later
on,
especially
as
we
start
extracting
out
utilities
here
to
make
it
work
a
bit
better,
but
we'll
see
it
might
be
overkill.
This
early.
A
A
A
A
B
Yes,
it
is,
unfortunately,
I
ended
up
in
working
for
all
those
issues
in
one
PR,
because
in
factor
being
I
needed
to
do
because
of
the
dynamic
degenerated
pages
I
needed
to
actually
I
want
to.
Do
them
well
be
safe.
That
my
approach
is
correct
because
I
totally
changed
it
Gatsby
graphical
Oliver,
question
and
all
the
things
and
deleted
the
learn
page
and
made
a
template
offered
out
of
it.
So
we
have
static
packages
so.
B
A
B
Thing
about
this
fetching
profile
pictures:
do
we
have
any
guidelines
about
api's
because
we
won
it
doesn't
matter
in
this
PR
on
the
relationship
into
the
problem
that
we
get
blocked
from
the
github
API
because
of
the
weight
limit
without
API
key
is
about
sixty
island
things
that
would
work
and
with
an
API
keys,
I
guess
about
five
thousand.
So
that
would
be
okay,
though
we
need
to
take
care
of
Jia
Jia
Jia
bit
yeah.
C
A
C
There
are
multiple
ways
we
can
tackle
it:
either
we
can
write,
you
know,
user
image,
operator,
downloader
inside
of
gates,
and
you
know
here
tapi
only
once
and
just
use
the
cache
or
we
can
move
on
to
Riveter,
not
sure
if
you
have
it
but
like
every
service.
But
all
you
have
to
do
is
upload
an
image
against
your
email
id
and
but
we
will
have.
B
So
go
on
now,
go
for
it
actually
doesn't
matter
as
soon
as
we
touch
the
profile
pictures
from
github
API.
It
doesn't
matter
if
we
touch
all
them
and
built
into
a
static
page
I
mean
include
them
in
a
static
page
or
them
from
client-side,
as
matter,
because
it
will
be
definitely
more
than
60
quite
soon.
D
A
You'd
only
make
a
request
if
you
have
a
new
contributor
to
the
docks,
because
once
you
once
you've
grabbed
someone's
profile
image,
it
can
be
on
disk
and
we
can
validate
against
that
before
making
the
API
call.
You
wanna
do
a
problem
with
how
like,
if
somebody
changes
the
profile
image,
how
do
you?
How
do
you
catch
bust,
but
I,
don't
know
if
that's
a
huge
issue,
we
can
also
look
into
I
know
we
we
can
have
different
behavior
in
in
Devon
and
in
actual
production
builds
because
I'm
pretty
sure
in
production
builds.
A
We
can
use
two
valid
API
key
I'm
sure
note
has
one
or
two
we
could
go
now
or
at
least
get
one
fourth,
a
node
project.
We
couldn't
obviously
have
those
API
keys
available
in
mode,
but
we
can
have
them
on
the
the
CI
box
and
we
can
chat
with
miles
about
getting
that
integrated
with
CI.
So
for
production
builds,
we
can
go.
We
can
always
just
pull
every
image
for
every
production
bill
to
the
site.
We
can
maybe
pull
from
a
cache
or
have
dummy
placeholder
images
in
dev.
B
A
A
There
I
thought
there
was
like
a
text-only
example
of
another
site
doing
this,
but
it
looks
like
I
remembering
wrong,
but
for
now
I
think
keeping
it
text
only
for
a
contributor
attribution
is
is
fine.
We
can
worry
about
complex
image
logic
as
a
separate
task.
I'd
rather
get
the
feature
out
so
that
we
can't
get
Flavio
of
his
attribution
on
this
site
since
he
donated
most
of
it
I
rather
than
block
on
your.
What
is,
admittedly,
a
rather
complex
feature
yeah,
and
maybe
we
can
do
it
as
a
follower.
A
C
C
A
That's
the
intent,
I
think
of
that
field.
We
can.
We
can
codify
that
in
it
might
already
be.
There
is
a
in
the
documentation,
folder
there's
a
like
document,
contribution,
process
and
I
believe
it
might
already
because
be
written
in
there
as
your
github
username.
If
not,
we
can
modify
that.
Take
a
look,
no.
C
C
A
A
Owner
you
have
a
lot
of
tickets
assigned
you
I,
think
about
there's.
The
learn
path
briefly
shows
404.
This
is
also
going
to
get
resolved
with
your
refactor
PR
right
yeah,
you
say
working
on
a
fix.
This
will
also
be
looked
in
and
issue
number
24
content
sections.
This
is
also
included
in
your
documentation.
B
It's
also
mentioned
in
the
issue:
I
mean
now.
It
is
a
bit
not
nice,
then
we
want
to
edit
documentation
in
between.
Then
we
need
to
move
I
mean
we
named
all
the
following
documents:
it's
really
it
would
all
come
up
within
another
PR
for
soon
with
a
Young's
Yemen
structure
and
where
we
can
put
everything
everywhere
and
link
just
why
it's
locking
the
US
as
it
comes
in
all
today.
Awesome.
A
Looking
forward
to
it
issue
number
18
on
this
is
Ahmed
the
h1s
h2s
h3,
this
one's
assigned
to
you
I
believe
still,
and
they
you
had
interest
in
in
tackling
this.
This
is
making
by
a
Gary.
This
is
making
headers
and
actual
anchor
links
instead
of
their
current
fake
State.
Have
you
gotten
a
chance
to
talk
with
this
guy.
C
I
have
been
looking
at
different
ways
to
handle
this.
Did
you
happen
to
have
you
know?
You
know
some
sort
of
fur
or
do
I
have
to
take
in
through
the
past
versions,
where
you
people
had
that
cable
of
pointing
before,
or
was
it
deployed
and
in
any
particular
branch.
What
I
was
looking
at
that?
Otherwise
I
was
having
the
same
issue
because
ESP
and
gets
me
the
you
know,
anchor
falling
thing
is
a
bit
period
and
when
I
was
lost
using
it
I
use.
C
So
I
think
this
additional
obviously
go
ahead
and
you
know
take
another
located
in
come
up
with,
but
I
learned
and
it's.
C
A
Appreciated
yeah
I
don't
think
there
was.
You
broke
up
a
little
bit
in
the
middle
layer
for
me,
but
yes,
that
there
was
an
older
version
where
this
was
working
in
a
branch
or
something
I,
don't
think
it
ever
this
never
worked.
This
is
just
a
dummy
like
I
made.
The
before
item
have
the
pointer
indicator
because
I
knew
we
wanted
at
some
point
like
that's
the
expected
behavior,
but
it
was
never.
We
never
I
never
got
around
to
implementing
it.
This
first
rapid
pass
so
yeah.
A
However,
you
you
see
best
to
execute
on
it
cool.
The
last
thing
in
the
must
do
column
over
here
is
that
site
navigation
side,
scroll
bug
owner
since
you're
doing
oh
I'm,
sorry
lead
or
offered
to
take
this
away.
Is
he
on
the
conversation
right
now?
No,
it
doesn't
look
like
it.
Cool
heipo
stood
some
info
on
what
I
think
the
bug
is
I'm.
Also
again,
this
was
hacked
together
in
a
night
to
get
it
looking
nice,
so
I'm
open
to
all
types
of
suggestions
on
how
to
make
it
work
better
and
differently.