►
From YouTube: Node.js Website Redesign
Description
A
B
It's
the
the
large
infrastructure
tasks
are
hard
too
hard
to
convince
people
to
jump
onto
because
they're
a
little
bit
more
open-ended.
So
once
we
once
we
knock
those
out
I
think
we'll
be
in
a
good
spot
for
contributors
to
start
coming
back
in
pick
up,
but
some
more
well
scope,
tickets,
yeah,
but
Oscar
I'll.
Let
you
take
it
away.
We
are
live
on
YouTube
for
those
folks
just
tuning
in
we're
doing
another
design,
walkthrough
getting
updates
from
Oscar
and
then
next
weekend.
B
Oscar
and
I
are
hanging
out
for
all
of
Saturday
we're
going
to
knock
out
some
giant
chunks
of
the
website.
I'm
gonna
post
an
issue
we'll
have
like
a
live
stream
thing
going.
What
people
can
call
in
and
hang
out
as
they
as
they
want
to,
but
the
plan
is
for
the
two
of
us
to
really
knock
out
a
good
chunk
of
the
major
of
structure
pieces.
So
we
we
can't
push
this
to
the
next
phase
with
the
design
we're
going
through
today.
So
this
is
kind
of
the
speak
up
or
forever
hold
your
peace.
C
So
yes,
I'm
just
going
to
walk
through
all
the
pages
and
what
I'm
calling
the
buckets
or
hubs
where
people
can
go
and
and
find
the
information
they
need.
So
this
is
the
entry
point,
it's
kind
of
like
the
marketing
homepage
site,
explaining
briefly
what
notice.
Also
this
is
a
area
we
might
not
be
able
to
do
next
Saturday
or
get
to
next
Saturday,
but
this
is
kind
of
like
I
was
picturing.
C
There's
like
what
you
had
on
your
envision
Adam,
where
you
had
the
thing
on
this
side,
and
then
you
would
convert
this
stuff
in
here
and
then
consume
api's
and
all
stuff,
so
it
would
be
cool
to
have
but
I'm,
not
sure.
If
what
you're
gonna
be
able
to
do
that,
Saturday.
C
C
This
is
what
we
just
talked
about.
This
is
kind
of
like
marketing
stuff.
This
is
to
join
a
community.
C
Some,
like
you,
know,
companies
that
use
it
and
then
some
entry
points
for
the
learn
page
as
well,
and
then
also
for
this
page
that
what
I
want
to
talk
to
you
guys
about
this
page
and
see
if
we
need
it
or
if
you
want
to
do
it,
you
know
next
on
the
next
generation,
so
so
yeah.
This
is
the
home
page.
Any
any
questions
in
here
John!
B
Only
comment
might
be
the
the
cat
one-two-three
punch,
marketing
pitch
no
income
says
so
much.
We've
gotten
some
feedback
that
you
know
three
three
TLD
hours
might
not
be
enough,
so
you
might
like
expand
that
the
six
or,
however
many
people
with
no
it's
calling
it
out
on
the
on
the
stream
here
for
people
who
might
not
pick
up
the
hand
right
away.
This
is
all
like
placeholder
content
for
language,
so
we're
like
well
we'll
probably
keep
some
lorem
ipsum
in
here
and
solicit
feedback
from
folks
to
fill
in
it
with
proper
content.
B
Online
I
yeah
it'll
be
in
a
this.
This
entire
bill
that
will
be
chilling
out
into
branch
who
can
go
and
play
with
it
and
actually
give
feedback
on
on
language
but
yeah.
So
that's
my
one
comment
there.
If
you
scroll
down
one
other
thing,
is
we're
probably
gonna
want
a.
We
have
a
on
the
old
foundation
website.
We
had
a
like
a
case
studies
page
or
it
holds
case
studies
from
companies
that
used
node.
They
like
self
submitted
them.
B
B
A
Guys
can
shove
that
into
the
resources
page
in
the
meantime,
basically
just
and
so
far
on
the
home
page
I
love
it
I
love
everything,
you're
talking
about
Oscar
and
and
definitely
it's
one
of
those
things
where,
like
the
best
way
to
get
the
right
answer,
yeah
on
the
internet
is
to
put
the
wrong
answer
out
there.
First.
A
B
A
I
was
just
looking
at
some
of
the
some
of
the
tickets
that
we've
been
you
know
discussing
from
like
for
the
past
couple
months.
Basically,
and
one
of
them
somebody
jumped
on
to
I
think
it
was
the
release
pages
and
they
were
like
hey
I
want
to
do
this,
but
their
first
questions
was
so,
should
I
create
a
page
using
this
Gatsby
node
approach
or
should
I
do
this
or
do
that
it
seemed
like
that
was
a
blocker
for
them.
A
C
C
C
So
in
here
we
have
kind
of
like
the
first
page
is
just
an
introduction
of
like
the
tutorials
and
kind
of
what
you
can
learn
and
I
broke
it
down
into
like
node
fundamental
note,
fundamentals,
intermediate
intermediate,
tutorials
and
then
advanced
tutorials,
and
each
section
is
displayed
here
with
their
specific
pages
right.
So
if
you
go
to,
for
example,
what's
note
like
it
would
just
show,
you
I
took
this
from
what
we
already
had.
C
It
just
takes
you
to
the
history
and
what's
now
it
and
then
it
kind
of
us
you
move
I'm
following
the
same
approach
of
the
check
box
appears
and
then
you
know
you
would
want
to
get.
You
would
want
to
get
the
big
check
like
this
one
right
and
then
this
one
I
did
keep
the
I
can't
remember
his
name,
but
he
was
in
the
last
yeah.
C
B
C
Yep
and
then
this
this
paragraph
is
just
just
it's
a
brief
description
of
the
tutorial
like
what
the
section
is
and
when
what
you
can
expect
to
get.
If
you
complete
all
of
these
things
right
like
if
you
know,
if
you
do
know
from
the
mentals
you're
kind
of
like
good
and
then,
if
you
do
intermediate
fundamentals,
and
you
know
you
can
get,
you
won't
explain
what
what
you
could
get
out
of
each
section.
A
A
That
should
be
that
way,
for
probably
all
of
the
learning
stuff
that
we
have
and
if
it's,
if
we
don't
have
that
for
the
learning
stuff
we
can,
we
can
edit
it
to
get
it
to
that
point,
but
I
love
it
so
far,
I
like
to
I
like
the
way
this
learned
page
is
set
up
one
because
you
know
I
think
one
of
the
big
things
is
like
JavaScript
verse,
nodejs
like
what
what
are
the
differences?
What's
the
you
know,
when
you
think
fundamentals
of
node,
what
is
it?
A
First,
the
browser's
in
there
I'm
sure
different
things,
will
change
or
we'll
have
we'll
be
able
to
add
things
and
take
things
out
whatever,
but
I
like
how
it's
broken
up:
fundamentals,
intermediate
things
like
the
blocking
down
blocking
that's
super
important
event:
loop,
timers
and
then
specifically
modules
I,
like
you
know,
I'm,
not
sure,
if
that's
just
copy
that
we
have
in
there
now
or
whatever,
but
I
love
that,
because
on
the
original
site,
it's
extremely
difficult
to
have.
There's
no
list
that
I've
been
able
to
find
so
far
of
all
of
the
built-in
modules.
A
C
Basically
what
we
already
have
and
then
put
it
in
a
way
that
it
makes
sense
from
from
from
a
learning
journey
right,
so
I
don't
know
if
John
you
want
to
take.
You
want
to
take
a
look
at
that
I,
don't
know
if
modules
would
be
good
to
have
in
the
documentation
or
is
it
more
appropriate,
learn
section,
but
yeah
I'm
gonna
need
some
help
with
that
with
like
breaking
down
what
what
you
need
to
learn.
Yeah.
A
A
B
So,
like
I
said
having
on
module,
section
is
certainly
nice
for
a
newcomer
John.
It's
it's
a
it's
the
actually
Oscar.
If
you
popped
back
over
to
the
documentation
page,
there
is
a
place
on
the
current
site
or
you
can
find
all
the
modules
it's
just
buried
in
pretty
thick
documentation.
That's
really
intimidating
for
Congress,
like
all
of
those.
It's
also,
you
know
not
delineate
it
as
hey
here's
the
modules
boom.
Here
you
go.
B
C
C
And
I
just
noticed
that
I
was
supposed
to
change
this
too.
So
this
is
supposed
to
say,
note:
fundamentals
like
you
have
here
and
then
you
know
media
fundamentals
or
intermediate
tutorials.
It's
okay
need
to
change
this
and
then
advanced
advanced
tutorials.
So
this
is
kind
of
like
yeah
I
need
to
fix
this,
no
I'm
making
note
yeah
something
else,
I,
really
like
what.
A
A
Week
and
we
can
definitely
look
to
other
sites
to
see-
you
know
like
a
good
example
of
like,
like
maybe
Ruby
or
whatever,
has
like
a
really
good,
getting
started
section
or
something
like
that.
But
what
I
see-
and
this
is
essentially
a
hierarchy
that
were
we're
starting
to
create,
which
is
you
know,
node
fundamentals
which
in
my
mind,
is
like
getting
started
like
start
here,
you
know
like
getting
started
content
in
terms
of
here's
basic
things.
A
You
should
understand
and
then
some
more
intermediate
tutorials,
which
are
going
to
be
explaining
some
concepts
which
are
just
a
little
bit
beyond
the
getting
started
stuff,
but
are
you
know
not
super
crazy?
And
then
we
can
have
more
advanced
tutorials
for
people
that
really
want
to
dig
into
you
know
like
creating
their
own
repple,
environment
or
stuff,
like
that.
Basically
so,
yeah.
C
Exactly
yeah
cuz
I
was
pretty
early
when
I,
when
I,
when
I
first
yeah,
when
I
first
started
like
doubling
into
into
dev,
and
they
told
me
to
download
node
but
I
had
no
pretty
clear
what
net
here
you
know
like
you
know
what
I
was
downloading,
so
it'll
be
nice
to
have
at
least
a
section
just
for
mode
idea.
Node
ID.
B
A
B
B
A
B
We
have
some
ideas
around
how
to
like
pull
it
automatically
from
github,
but
at
the
end
of
the
day
that
just
a
comment.
So
it's
complicating
the
builds
a
lot
and
it
doesn't
it
sorry
it
come,
gets
the
build
it's
hard
to
grab
the
like
the
Gravatar
image.
Sure
like
the
profile
image
from
github.
Specifically
that
way,
and
it
doesn't
allow
the
option
for
people
to
be
anonymous
if
they
want
to
some
people,
don't,
like
being
you
know,
I
don't
know,
face
plastered
over
the
Internet,
so
yeah.
C
Cool
so
for
community
I'm,
not
having
done
it
much
because
I
want
to
join
the
meeting
on
Tuesday
with
community
outreach.
So
you
can
talk
about
what
type
of
of
content
we
want
to
put
in
here.
I
did
kind
of
put
what
you
the
taxonomy
of
what
you
had
Adam
on
on
your
post
in
here.
So
there
might
be
some
things
that
we
don't
want
to
do
for
the
for
the
first
iteration
or
we're
just
we're.
Just
not
gonna
have
enough
content,
but
but
yeah
I
hadn't
worked
on
this
on
this
hub
yeah.
B
C
Then
the
resources
page
I
haven't
done
much
here.
Also
I'm
picturing,
this
hub
any-any
cool,
like
posts
that
people
have
done
I
know
we
have
a
lot
of
posts
in
the
current
site,
so
maybe
some
way
that
we
could
organize
these
here,
that'll
be
awesome
and
any
videos
or
anything
that
people
would
want
to
like
get
to
any
tooling
or
any
anything
pretty
much
that
doesn't
fit
into
these
three
hubs.
We
can
just
put
it
in
here.
B
B
C
B
B
B
Yes,
six
Indians,
this
probably
should
get
merged
with
the
modules
section
of
our
learn
page
like
it's
relevant
information
for
people
who
are
just
getting
started
like
hey
I,
know:
JavaScript,
hey,
I
know
what
commonjs
in
es6
is
now
what's
going
on
with
no
and
that
so
this
is
content
that
we
need
to
merge.
These
are
to
eight
more
API,
Doc's
picked,
that's
down
below
it
and
that's
16
and
12.9
guides
are
kind
of
like
the
advanced
guys
section
and
use.
You
have
to
see
a
lot
of
duplicate
content.
C
B
There's
a
page
on
flame
graphs
for
Diagnostics,
which
would
be
great
to
move
in
there
under
advanced
guides
like
profiling,
your
process
and
they're.
All
kind
of
in
that
same
thing
you
know
you
can,
you
can
see
actually
I
think
you
had
an
allele,
your
learn,
page
layout,
how
to
publish
an
API
package
and
then.
B
The
dependencies
section,
I
think
to
me
at
least
looks
like
another
advanced
guide
is
like
hey
under
the
hood.
What
the
heck
does
this
thing
use
and
then
we
say:
hey
look
it
actually
he's
built
that
C++
in
v8,
here's
all
the
magic
that
makes
it
run
under
the
hood.
You
want
to
read
more
here's
all
these
other
projects
stuff.
So
the
majority
of
this,
like
I,
mentioned
like
eight.
B
A
So
it
sounds
so
far
like
the
on
the
nodejs
dev
on
the
new
site.
The
docs
stuff
is
going
to
be
heavily
release,
driven
in
that
that
content
will
be
sourced
from
the
you
know,
different
releases,
etc,
the
dock,
the
docks,
their
version,
etc,
and
then
the
learn
page
will
be
highly
contributor
driven.
So
there's
gonna
be
a
lot
a
lot
of
content
there,
that's
gonna,
be
you
know,
changing
or
malleable
or
whatever
that'll
probably
survive
between
your
pieces
and
whatnot.
So
it
sounds
like
the
learn.
Page
is
going
to
be
pretty
freaking
important.
A
B
Crazy,
so
yeah
in
that
regard,
Oscar
I'm,
not
sure
what
other
types
of
content
we
were
thinking
about
for
the
releases
page
or
sorry
for
the
resources
page.
We
can
leave
it
as
an
option
moving
forward
if
you
find
it
on,
but
it
might
not
be
in
the
you
know:
p0
cut
of
this
site
before
yeah.
We
can't
find
something
to
put
on
it
by
next
Saturday
I
think
we're
looking
for
content
necessarily
if
we
don't
easily
have
it
accessible
to
us.
Yeah.
C
B
B
That's
the
logos,
colors
all
that
it
can
actually
be
a
little
like
design
system,
Z
type
names,
which
will
be
an
amazing
resource
for
other
people
come
around
to
the
project
later
on,
or
that
want
to
make
something
that
looks,
know
D
and
then
the
trademark
and
privacy
policy
which
linked-in
currently
in
the
node.js
org.
It's
not
about
section
rapidly.
Those
three
sections
don't
really
warrant
a
top-level
Navin
or
aren't
a
sub
page
of
a
top-level
nav
items
but
need
to
go
somewhere
further.
You
might
guess,
sounds.
C
B
C
Cool
and
then
the
other
thing
that
I
wanted
to
show
you
real
quick,
was
the
download
page
so
far,
so
I
kind
of
went
with
this
toggle
between
LTS
and
then
current.
It
shows
you
kind
of
what
just
shifts
pretty
much
the
same
thing
that
we
have
today
and
then
down
below.
You
have
the
individual
packages
so,
and
this
is
kind
like
what
it
would
look
like
if
you
hover
hover
states
of
it,
but
I
need
to
put
the
releases
in
the
release
roadmap
as
well
in
here
yeah.
B
B
B
B
C
B
C
I
completely
agree:
okay,
so
after
this
I'm
gonna
put
the
like
right
here,
I'm
gonna
put
the
roadmap
and
then
the
release
schedule
them
all
a
stuff.
So
people
know
what
they're
downloading
and
then
these
I'm
gonna
I,
like
the
the
I
was
kind
of
I,
was
I,
was
experimenting
with
doing
like
drawer
stuff
as
well.
So
I
have
some
experimentation
with
that
as
well.
So
I
think
I'm
gonna
go
with
that
for
these.
For
this
table
and
yeah
that's
pretty
much.
What
I
have
is.
C
A
C
B
B
A
Know
that
one
of
the
one
of
the
main
reasons
I
ever
ever
visit
the
releases
page
on
the
current
site
is
specifically
to
be
like.
When
is
that
next
version
hitting
LTS
like
what
when's
that
when's?
That
happening
like
we're,
coming
up
on
12
being
LTS
pretty
soon
and
like
maybe
October's
the
October
22nd?
So.
A
That's
at
least
when
I
I
would
fruit.
For
me,
I'm
curious
I
want
to
know
what
is
the
current
LTS.
Is
that,
in
my
mind,
is
the
that's
the
official
version
since
since
I
teach
people
no
js'
I
want
to
be
able
to
teach
them
like,
because
there's
always
experimental
features
that
people
are
playing
with
with
babble
and
things
like
that
or
experimental
features
within
the
current
releases.
A
But
once
once
you
actually
get
to
an
LTS
release,
then
you
know.
Typically,
you
get
features
from
previous
builds
are
no
longer
experimental.
They
don't
warn
you
in
the
console
or
anything
like
that.
So
I'm
always
curious
like
what's
what's
the
hottest
newest
thing,
I
can
use
without
it
being
experimental,
got
it.
Okay,.
C
C
A
C
C
A
It
says
LTS
here
I
mean
I.
Could
what
I'm
want
to
know
specifically
is
like
I?
Guess
it's
every
it's
well
now
that
I'm
looking
at
the
dates,
I
can
know
it.
So
it's
like
simple,
but
it's
every
year,
there's
a
new
LTS
I
believe
I
believe
that's
how
it
works
based
on
the
chart
I'm
looking
at
right
now,
but
so
what
kind
of
information
I
want
to
know
is
typically
like
and
I?
Could
that
could
just
be
me?
A
I
don't
know,
but
what
I
look
for
often
is
you
know
how
many
months
away
is
this
next
version,
like
you
know,
gonna
be
when
it
when
it
can
be
LTS
basically
got
it
yeah
I
want
to
see
like
the
timetable
of.
Like
you
know,
version
14
is
already
being
worked
on
when
that,
when
does
that
come
out
for
LTS,
that's
okay,
which
is
you
know
just
one
year,
etc,
but
and
then
there's
like
version
13,
which
doesn't
look
like
it's
scheduled
at
all,
who
it's
not
on
the
current
page.
It's
not
doesn't
see.
A
A
B
A
Yeah
and
to
clarify
real
quick,
my
concern
like
I
was
saying,
is
primarily
in
Windows
Active
LTS
start
because
for
me
and
the
content
on
writing
I
tell
people
the
current
LTS.
Is
this
and
so
I
needed
like
when
this
content
comes
out?
What's
it
gonna
be?
So
that's
just
my
particular
concern,
but
specifically
on
this
page,
the
important
information
is
initial
release
pretty
important.
Not
so
it's
more
historical,
active
LTS
starts
important
maintenance.
Lts
start
I
care
less
about
that,
but
end
of
life.
The
end
of
life
is
super
important,
in
my
opinion.
A
C
B
The
inspiration
that
mentioned
support
to,
but
I'm,
not
not
sure,
amber
amber,
doesn't
quite
this
is
pretty
well
for
how
they
like
announce
it
like.
The
first
thing
you
see
is
the
upcoming
release,
a
section
like
hey
here's,
the
pathway
to
the
next.
They
do
minor
version.
But,
since
you
know,
they're
major
versions
are
pretty
far
apart,
but
you
know
they.
They
have
a
pretty
decent
explanation
for
how
those
you
know
what's
coming
next,
okay,
if
we
look
at
they
remove
the
like
or
interesting,
they
changed
their
layouts.
This
last
time,
I
looked.
B
Mean
no
node
maintains
so
many
like
actives
released,
like
you
can
see
right
there.
There
are,
you
know
back
to
10,
is
kind
of
here
they're,
not
for
lease
line.
Yeah.
You
know
we
need
to
be
able
to
say
what's
in
maintenance
mode
like
node,
six
is
going
out
of
maintenance
soon,
which
is
like
that's.
The
other
reason
why
somebody
might
come
to
this
page
is
that
ancient
ancient
version
of
node
will
no
longer
be
maintained
period
ever
for
anything
like
that
even
period
its
and
so
like.
B
C
B
B
You,
you
won't,
you
know,
have
major
security
holes
if
you
stay
on
this,
so
like
a
lot
of
companies
are
gonna,
be
rushing
to
get
off
a
six
pretty
soon
and
having
that
visualize
having
that
end
of
life,
visualized,
somehow
or
communicated
clearly
somehow
on
the
site
would
be
helpful.
Much
for
the
same
reason
that
you
want
to
know
what
the
what
buildings
LT
s
is
what's
going
out
of,
mavens
go.
C
Ahead
but
but
you
picture
like
because
this
is
the
upcoming
upcoming
releases,
you're
sure
you're,
having
the
same
for
the
current.
B
Yeah,
so
the
amber
amber
release
page
what
they've
done
there
works
very
well
for
their
use
case.
Like
it's
a
it's
a
little
bit
less
of
a
complicated
support
cycle
right.
A
B
Can
have
that
single
line
onto
the
next
release
but
will
will
need,
will
new
would
be
nice
to
have
that
style
of
communication
or,
like
that
clear
communication
as
well?
So
it
won't
look
exactly
like
this,
but
they
the
way
that
they've
structured
their
their
release,
visuals
and
the
I
think,
more
importantly,
their
language
like
the
way
that
they
communicate
about
their
release
cycles
yeah
very
clear,
yeah
yeah.
So
it
will,
it
won't
be
a
straight
lift
for
the
node
site,
like
it'll,
probably
be
some
version
of
this
graphic
or
some
version
of
this
table.
C
B
A
C
A
C
A
A
B
Think
it's
whatever
language
were
used
like
we
want
to
be
consistent
with
how
everybody
else
talks
about
it,
and
it
looked
like
on
the
release,
the
current
releases
page
and
in
their
releases
repo.
They
use
the
word
they
it's
it's
odd.
Actually
they
they
use
the
word
current
right
now
for
that
they
also
seem
to
swap
out
the
words
LTS
and
active
interchangeably
which
I
don't
like
so
like.
Let's
make
the
decision
here
to
nix
the
word
active
because
it's
just
confusing
like
the
three.
B
The
three
phases
are
current
LTS
and
maintenance,
current
being
bleeding
edge,
currents,
kind
of
like
a
canary
I.
Guess
it's
hey
we're
developing
active
features
on
here.
We're
gonna,
try
or
damn
it's
not
to
break
it,
but
there
might
be
some
weird
stuff
in
there
LCS
is
we
ain't
gonna
break
this?
The
features?
Are
there
we're
not
going
to
make
major
right?
We're
not
gonna.
Do
yeah
we're
not
gonna,
make
the
major
changes
or
get
bleeding-edge
stuff
in
there.
B
B
C
Ready,
not
it
and
there's
no
way,
I
mean
yeah,
I
mean
I
would
want
to
keep
it
the
same.
The
same
rich
if
people
are
already
familiar
with,
but
you
mace
to
me
makes
more
sense
to
do
a
stable
and
then
I
don't
know
future
or
whatever.
So
people
don't
know,
they're
minded
that's
but
yeah
well,
I'll,
keep
it
I'll,
keep
it
the
same.
For
now,.
B
Yeah,
let's
keep
the
language
the
same
for
now,
since
we're
not
I
think
if
we
control
a
language,
it's
the
releases
working
group,
but
you
know
comes
that
if
we,
if
we
think
there's
a
good
and
actually
John's,
need
a
great
write-up
to
do
just
and
like
not
even
just
for
node
but
like
what's
the
language
we
use
across
major
projects
like
this,
for
communicating
release
lines
and
what
seems
to
work
well,
it
doesn't
seem
to
work
well
and
for
what,
like?
What
types
of
users
does
it?
And
does
it
not
work?
Well,
because.
A
B
Yeah
so,
but
meanwhile
LTS
doesn't
mean
anything
for
you
know
open
source
users
like
what
that
doesn't
have
latest
feature.
Why
am
I
used
to
this?
So
it's
a
yeah,
it's.
It
could
be
a
very
interesting
article
to
read
anime.
We
might
have
some
strong
takeaways
to
then
you
know
write
a
recommendation
to
the
releases
team
about
about
language.
There
wouldn't
actually
change
any.
You
know
technical
details
for
what
goes
into
a
release
like
this
is
what
we
consider
it
but
like
how
do
we
that
we
talk
about?
It
is
equally
important,
cool.
C
C
Yeah,
it's
it's
it's
on
the
top
area
yeah
and
you
could
also
access
it
from
here
and
I.
Think
I
have
I
had
a
button
somewhere
here
as
well,
or
was
it
here,
I
had
it
in
the
in
the
footer
as
well.
I
think
I
took
it
out,
but
I'll
put
it
back
in.
There
is
a
way
that
people
can
go
in.
Does
it
make
sense
to
you
John
or
will
you
put
it
somewhere
else?
Okay,
I.
C
B
C
C
B
A
C
B
C
C
C
B
C
C
A
B
C
B
B
A
B
B
Sweets
we're
coming
up
on
whoo-hoo.
We
have
one
minute
until
10:00,
good
timing,
Oscar.
It's
like
you
like
a
plan
that
yeah
yeah.
A
B
We'll
yeah,
so
anybody
online
make
comments
on
the
Sigma
board,
it'll
be
in
the
readme
in
a
couple
seconds
and
we'll
see
y'all
next
Saturday.