►
From YouTube: Node.js Website Redesign Meeting
Description
A
B
Hey
everyone
welcome
to
the
noches
foundation
website,
redesign
initiative
meeting
on
the
first
of
March
2018.
We
do
want
to
walk
home,
we
haven't
done
a
roll
call.
Yet
in
our
previous
two
meetings,
I,
don't
know
if
you
wanna
start
now,
we
could
probably
just
do
a
quick
name
actually
I
think
we
have
to
call
just
like
shot.
What
call
just
everyone
say:
name
pretty
much:
okay,
I'll
start.
My
name
is
Olivia
I'm.
The
community
committee
champion
of
this
initiative
again:
honey,
I'm.
E
C
Context
we'll
be
happy
to
so.
We
left
the
last
meeting
with
a
an
action
item
to
hopefully
buy.
A
next
meeting
have
wireframes
up
that
we
were
able
to
discuss
two
weeks
in
between
I
and
I,
noticed
that
there
wasn't
any
momentum
on
it.
So
I
decided
to
take
it
upon
myself
to
go
and
make
a
take
a
first
pass
at
it.
C
Just
get
something
up
there
that
we
can
look
at
it's
just
something
tactile
that
we
can
actually
see
and
comment
on
and
sure
enough
when
I
put
it
all
together
and
stuck
it
up
on
envision
and
posted
it
in
a
github
issue,
as
a
first
pass
at
wireframes
and
open
for
comments,
there's
a
lot
of
activity
on
it.
She's
awesome,
I,
I,
think
always
having
something
visual
through
these
types
of
things
always
helps
to
increase
engagement.
C
So
we
definitely
got
a
lot
of
comments
on
the
this
first
pass
of
wireframe
and
I'm
gonna
have
time
this
Saturday
to
go
in
and
start
synthesizing.
Some
of
the
feedback,
and
hopefully,
under
this
weekend,
have
a
second
iteration
on
it
that
we
can.
We
can
post
again
and
keep
the
discussion
going.
There
are
a
lot
of
outstanding
questions
on
the
issue.
It's
issue
number
15,
the
website
redesign
or
anybody
streaming.
B
C
A
G
A
E
D
Yeah
I
guess
I'm
wondering
also
like
if,
in
previous
discussions,
there
be
talks
about
doing
things
like
including
user
personas,
doing
information
gathering
and
getting
like
analytics
information
for
like
what
pieces
of
content
are
most
widely
used
and
and
generally
maybe
taking
feedback
from
what
I
would
normally
do
in
the
real
world
is
like
asking
a
client
essentially
what
our
key
features
that
are
sort
of
required,
because
then
this
would
probably
dictate
also
like
content
structure,
which
I
think
was
I.
Think
the
right
next
pass.
I
think
a
lot
of
people
were
confused.
D
Maybe
in
that
thread,
because
it
is
a
very
I
would
say:
high
fidelity,
wireframe,
so
I,
although
I
totally
think
it's
great,
but
we're
sharing
like
design
sort
of
what
things
are
gonna
lay
out.
I
guess
maybe
also
prioritizing
content
and
and
discovery
of
what
is
actually
important
or
what
users
actually
need
will
help
dictate.
You
know
what
links
go
where
and
what
content
you
should
be
bubbling
up
on
something
like
the
home
page.
You
expect
yeah.
C
Those
are
two
points
I
actually
did
want
to
bring
up.
The
the
largest
discussion
was
around
how
the
download
CTA
called
the
action
on
the
home
page
functions
and
then
how
how
it
works
and
what
the
layout
is
of
the
current
releases
page
and
if
that
poem
at
works,
if
there's
a
better
format,
I
think
making
some
user
personas,
maybe
getting
a
few,
maybe
getting
a
few
users
who
fit
into
those
personas
that
were
targeting
and
seeing
their
responses
to
the
flow
laid
out
here.
C
There's,
not
a
consensus
on
how
to
layout
that
download
flow
command
installation
so
I
and
there's
still
some
resolution
that
needs
to
happen
between.
Are
we
still
crying
downloads
download
via
package
manager,
it's
allegedly
a
package
manager,
the
the
primary
way
to
install
node
that
we
want
from
our
carrots
and
that's
laying
at
the
technical
CSV
of
the
releases
committee.
They
provide
some
guidance
on
still
do.
A
We
have
analytics.
We
like
the
this
group,
doesn't
show
you
instantly.
I
am
happy
to
reach
out
to
zippy
the
nerdiest
foundation.
You're
gonna
manages
that
to
see
if
she
can,
there
sure
access
or
sure
context
so,
like
you
know,
share
screenshots
of
specific
bits
that
we're
interested
in
I
don't
think
they
have
a
problem
sharing
access
to
it.
It's
heard
like
sharing
the
context
and
sharing
the
numbers.
It's
just.
A
It
allows
access
to
other
things,
that's
that
that
are
critical
to
the
foundation
in
terms
of
like
rbac
type
stuff,
so
I
don't
know
if
they
would
able
to
easily
do
that
directly.
But
we
can,
you
know
they've,
always
been
extremely
open
and
willing
to
help,
especially
with
website
stuff,
since
they
also
want
this
eerie
design
happen.
So
I.
D
Did
be
open
to
giving
us
the
overall
sort
of
pie,
chart
or
breakdown,
you
know
centage,
wise
and
versus
pure
traffic
numbers
to
the
existing
pages
for
sure,
but
that's
what
I'm
kind
of
looking
forward,
because
then
that
will
help
us
make
decisions
about.
You
know
what
is
important
to
you
know:
drive
traffic
to
or
it's
a
NIC
easier
to
get
yeah.
C
I
I
would
I
would
maybe
caution
a
little
bit
against
putting
a
lot
of
weight
in
that
and
not
doing
further
user
exploration.
Sure
my
website
doesn't
handle
some
use
cases
and
a
lot
of
content
that
we're
thinking
about
laying
out
so
it
might
guide
it
might
misguide
us
because
it's
it's
not
some
software
word
working
I'm,
not
even
there
sure
so.
D
Again,
like
so
like
I
guess
what
I
didn't
see
and
I
was
trying
to
play
catch-up
looking
through
the
github
issues,
is
I
didn't
see
what
those
things
were
that
we
were
trying
to
achieve
right
like?
Are
we
trying
to
facilitate
more
downloads?
Are
we
trying
to
facilitate
learning
more
so
like
do
we
have
an
outline
of
the
things
that
we're
trying
to
drive
and
then
yeah.
A
So
I,
don't
I,
don't
know
if
we
necessarily
defined
out
specific
goals
like
in
terms
of
like
okay.
This
is
the
path
we
want
to
like.
We
didn't
drive
kind
of
personas.
Basically,
we
the
goal
that
we
laid
out
as
far
as
I,
please
anyone
correct
me
if
I'm
wrong
was
a
clearer
navigation
hierarchy
that
actually
surfaces
everything.
There
is
quite
a
few
things
that
haven't
been
surfaced
in
terms
of
like
resources
that
the
website
provides
that
actually
aren't
shared
and
also.
B
C
B
Okay,
so
one
of
the
things
we
discussed
issues
surfacing
as
to
other
places,
not
only
our
group
but
also
the
kumkum,
which
I
think
added
the
edit,
the
Hongkong
I've
added
it
to
the
agenda
or
something
for
a
next
come
come
meeting
and
something
like
that,
but
then
also
that
he
has
seen.
Obviously
the
website
working
group
which
doesn't
have
meetings
as
far
as
I
know,
but
a
lot
of
people
from
the
website
working
group
I.
B
C
As
far
as
for
when
and
how
to
surface
it,
I
would
love
to
get
a
second
passive,
doing
doing
a
revised
wire
frame
layout
since
there's
a
lot
of
good
feedback
there
already
and
then
bring
that
improved
wireframe
to
a
larger
group,
I
think
there's
there's
a
lot
of
actionable
tasks
there
to
work
on
so
possibly
by
next
week,
but
the
week
after
will
have
will
be
able
to
service
it
elsewhere.
Okay,.
H
B
G
B
Yeah,
if
no
one
else's
anything
we'll
move
on
to
the
voice
and
tone
guidelines
to
get
which
is
I'm
saying
ticket,
it's
an
issue
issue
number
thirteen
but
I.
Think
related
to
this
is
pull
request.
Number
14,
which
I'm
gonna
link,
which
is
needles,
wait
up
for
for
a
basic
sort
of
tone:
invoice
thingy,
vanilla,
I,
don't
know
if
you
want
to
like
give
any
more
information
about
this
I.
B
H
H
B
H
A
B
B
C
I
think
we
should
prepare
the
document
as
though
it
could
be
used
by
a
larger,
a
larger
group,
and
if
other
teams
choose
to
adopt
it,
adopt
it
as
their
voice
and
tone
guideline
for
any
content
that
they
write.
That
would
be
wonderful
when
we
can
actually
propose
to
shop
it
around
other
teams,
the
TSC
when
the
writing,
documentation
or
I.
You
know,
whoever
else
they
need
it,
but
for
now
it
did
I
think
the
website
redesign
would
be
the
good
testbed
for
this,
given
a
platform
to
launch
to
a
larger
audience.
C
C
Whenever
I'm
drafting
website
copy
or
website
content,
I
tend
to
err
on
the
side
of
casual
and
funny
or
I
attempt
to,
and
you
can
kind
of
see
that
on
the
releases
page
of
the
the
wireframe,
where
I
describe
LTS
current
and
nightly
so
I,
don't
know
how
the
rest
gives
you
feels
about
that
as
a
tone
for
the
website.
I
know
I
quite
enjoy
it,
but
I
also
rely
said
it's
I.
C
E
A
Gender
race
is
kind
of
a
normal
humorous
subject
that
really
doesn't
fit
along
with
what
we
are
trying
to
push
with.
No
genius-
and
you
know
having
it
be,
an
inclusive,
diverse
environment.
So
you
know
we
have
to
make
sure
to
define.
You
know
we
don't
want
to
be
us
centric,
but
we
also.
We
just
need
to
make
sure
it's.
You
know
if
it
falls
in
line
with
the
greater
message
of
the
noches
community
and
the
project,
and
then
there's
no
objections.
C
A
E
C
G
C
I
I
do
think
there
is
value
in
keeping
humor
as
a
core
tenant
on
the
on
the
voice
and
tone
for
the
site
like
it's,
it's
a
very
inviting
way
to
get
other
people
involved
and
feel
like
they're
part
of
the
community
I.
As
just
a
first
touch
point,
you
know
they
do,
they
feel
welcome.
If
you
do
it
right,
so
I
would
just
be
my
two
cents
on
humor.
I
B
Yeah
I
think
just
I
don't
want
to
like
elongate
this
discussion,
but,
like
my
my
take
on
that
as
its
asked
to
me
personally,
it's
kind
of
weird
when
sort
of
a
big
corporate
entity
has
like
this
tries
to
be
like
relatable
like
it's
like
I,
don't
know
if
this
would
fall
into
that
same
category
but
I.
Think
if
you
do
it
wrong,
it
could
very
well
be
and
it
could
potentially
alienate
a
lot
of
I
think
especially
young
people,
because
I
know
there's
a
lot
of
people.
H
D
I
would
go
back
to
my
original
comment
about
creating
user
personas
like
who
is
it
that
comes
to
the
website?
Who
is
it
that
comes
to
the
conference's
and
watches
somebody
give
a
presentation,
and
how
did
they
present
that
once
we
figure
out
what
the
audience
is,
then
you
can
really
tell
whether
or
not
they
would
be
open
to
any.
You
know
a
different
kind
of
tone
than
matter
of
fact.
C
D
And
there
it
may
change
also
depending
on
which
part
of
the
website
you're
on.
So
if
you're
like
inside
of
getting
involved
or
contributing,
potentially,
you
can
have
different
tone
for
that
type
of
audience
right
now,
compared
to
you
know
that
wants
to
know
about
the
security
risks
that
might
have
bubbled
up
and
why
there's
a
patch
to
know
you
know
so,
I.
B
Think
that's
already
explained
the
current
draft
of
the
document
that
menial
proposes,
if
I
recall
correctly
but
yeah.
That's
that's
in
okay,
I'm
gonna
kind
of
time
box
this
here.
Unless
anyone
has
anything
okay,
then,
let's
move
on
to
issue
number
12,
which
is
the
tech
exploration
for
inverse,
are
not
paper,
which
is
something
that
we've
discussed,
which
is
basically
sort
of.
We
have
an
on
the
website,
preferably
on
the
main
site.
B
We
have
a
little
sort
of
console,
slash
editor,
which
you
can
sort
of
test
the
capabilities
of
Nod,
which
should
ideally
one
in
browser
and
we've
I
believe
Adam
has
has
been
researching
some
stuff,
but
then
we
also
have
a
reply
from
Jen
Shifa
who
works
for
glitch,
whom
I
also
know
and
I
know
glitch.
So
I
can
maybe
give
a
little
bit
of
context
for
that.
I
haven't
used
it
in
an
embedded
setting,
but
I
think
what
she
proposed
us.
B
A
So
over
the
run
cake
over
for
me
came
up
over
the
past
week
actually
well
over
the
past
few
days,
because
there's
some
other
stuff
I'm
doing
and
that's
what
MPM
embeds
is
like
a
module
playground
by
default.
That
said,
I
think
I'm,
sad,
I
didn't
even
consider
it
earlier.
Glitch
is
probably
a
little
bit
of
a
better
solution,
especially
because
of
how
focused
they
are
on
node
yeah.
G
A
B
E
B
Value
and
oh
yeah,
okay,
so
like
yeah
glitch,
also
is
very
extremely
focused
on
which
kind
of
what
we
want
to
do
so
I
think.
Maybe
it
would
be
beneficial
to
have
a
steady
connection
to
people
like
just
for
the
costs
of
development,
so
he
can
maybe
try
and
coordinate
and
see
how
we
can
use
glitch
and
the
best
in
the
best
way.
Yeah.
D
So
I
actually
replied
to
the
original
thread
on
this
I
think
it
was
the
which
number
here,
number
nine
yeah
and
so
a
couple
days
ago
about
run
kick
because
I
have
been
looking
into
this
for
node
school
websites.
I'm,
sorry,
I
run
the
trial.
Note
school
chapter
here
and
I
wanted
an
easy
way
to
invent
and
show
examples
of
the
just
basic
note
practices,
and
so
I
did
a
lot
of
investigation
into
different
and
edible
runtimes
and
Ronquillo
I
would
say
it
was
by
far
the
best,
including
glitch.
D
D
C
Yeah,
taking
a
look
at
both,
they
do
both
look
like
viable
options.
I'd
love
to
see
like
a
pro
cons
for
each
one,
do
I,
actually
review
of
features,
yeah,
I
think
as
long
as
they
we
pick
something
and
invest
in
it
and
make
sure
it's
gonna
work,
long
term
process,
cousin
we'd
be
able
to
make
both
work.
So
it's
nitty-gritty
details
at
the
end
of
the
day,
I
yep,
yes,.
D
D
Package
JSON
files
or
directory
structure,
which
I
think
is
better
for
tutorials.
Unless
you
want
to
go
more
in
depth
with
full-on
full-blown
applications
which
I
think
goes
a
little
bit
beyond
the
scope
of
a
lot
of
the
examples
in
what
I
would
guess
would
be
the
done.
You
know
the
primary
dachshund
a
pets,
oh
yeah,.
C
E
C
So
I
think
there's
a
there's
a
feature
space
that
either
one
of
these
projects
will
will
attempt
to
fill
and
that
there's
only
so
many
features
that
you
can
pack
into
a
node,
embeddable,
editor
and
I.
Think
the
presence
or
absence
of
any
of
those
features
in
that
feature
space
will
be
important
depending
on
the
type
of
content.
C
I
think
we
can
probably
do
a
review
of
both
products
without
necessarily
knowing
the
content
we
want
present
well
at
the
same
time,
developing
content,
and
then
we
can
bring
both
the
table
and
say
okay,
which
one
it's.
What
we
want
to,
what
we
actually
want
to
make
better,
so
I
think
they
can
be
done
in
tandem
at
the
same
time,
if
anybody
doesn't
think
so,
then
you
please
chime
in
I'm
not
married
to
any
idea.
B
B
B
B
G
C
Agree
yeah,
so
this
is
a
little
bit
again
touched
on
the
wireframe
and
I
actually
have
a
call
out
saying
hey.
This
is
a
bunch
of
placeholder
content.
I
have
no
idea.
What's
gonna
go
here
on
the
learn
page
there's
a
QuickStart
section
where
you
know
I
made
some
made-up
headers
for
what
is
no
js',
installing
ojs
hello,
world
server
modules.
C
B
A
I
can
speak
to
a
little
bit
that
so
one
of
the
original
reasons
conga
was
created
was
to
kind
of
help.
Try
to
organize
efforts
like
that,
a
little
bit
better.
We
I
don't
think
we
ever
really
got
representations
from
them
just
because
we
didn't
really
do
outreach
and
they
didn't
come
to
us,
which
was
he
expected,
the
initial
expectation
that
clearly
didn't
pan
out.
So
you
know,
there's
no
official
relationship.
I,
don't
think
that
said,
there's
ample
numbers
of
no
school
runners
suppose.
B
A
B
A
D
If
you
can
think
of
that
in
terms
of
terminology,
I
used
to
talk
about
navigation,
and
so
when
I
was
doing
this
discovery,
I
was
trying
to
meld
these
three
organizations
together.
My
local
note,
school
organization,
with
the
note
school
work,
shoppers
that
we
used
to
teach
people
also
us
that
then
associate
themselves
with
the
note
documentation
and
expect
anybody.
That's
a
attendee
to
be
using
to
complete
these
workshops.
D
So
I
was
just
wondering
if
there's
a
way,
potentially
I
guess
within
the
getting
started
or
some
sort
of
handoff
that
could
happen
or
even
just
a
tighter
relationship
could
be
established
between
the
node,
nodejs
and
I.
Guess
this
website
and
the
work
that's
being
done
all
over
the
world
with
note
school.
B
Yes,
so
I
can
give
a
little
explanation
to
this,
because
I'm,
the
organizer
of
notes,
gobelin
and
also
a
sort
of
Co
workshop
on
maintainer
and
I-
think
that
if
we
do
anything,
definitely
the
first
step
that
needs
to
be
done
is
to
get
a
tighter
relationship
between
not
school
and
node,
like
the
node
project
foundation,
because
a
lot
of
the
work
shoppers
are
not
only
our
main
change,
which
is
one
problem,
but
also
outdated,
like
very
outdated,
like
not
version
4
outdated.
So
there's
a
couple.
B
The
the
core
workshop
is
like
learning,
node
and
Java
scripting
I.
Essentially
it
pretty
well
maintained,
but
then
there's
you
know
it's
open
source
project
so
nobody's
getting
paying
for
it.
So
it's
all
very
coincidental
whether
it's
maintained
or
not
and
I
think
it
would
be
nice
if
we
had
a
couple
of
workshops
that
we
took
sort
of
under
our
wing
and
we
provide
that
sort
of
an
official
maintainer.
It's
a
maintain
status,
stability
status
or
whatever
I
think.
B
D
I
think
I
would
be
really
important
because
I've
been
to
a
number
of
node
conferences
and
I've.
Seen
representatives
use
the
numbers
from
node
school
use,
the
number
of
meetups
that
are
happening
and
yeah,
basically
using
our
stats
yeah
that
to
pump
the
tires
of
node
and
saying
how
good
a
job
it
you
know
it
it's
embracing,
basically,
that
we
are
we're
helping
popularize
node
in
our
local
communities
and
yet
I
don't
see
like
money,
trickling
down
to
support
those.
You
know
yeah
we're
shoppers.
It's.
A
Definitely
not
a
lack
of
interest.
It's
a
lack
of
connection
I
I,
don't
I
think
there's
many
people
who
are
interested
in
having
more
of
an
official
relationship.
It's
just
that
there
has
not
been
a
path
created
to
do
that
and
and
not
from
like
it's
just
like
I
personally,
have
no
idea
how
even
go
about
doing
that
because
I
don't
know
who's.
He
maintains
a
lot
of
those
school
stuff
and
I'm
sure
there
are
members
of
the
community
committee
in
the
TSC
too,
but.
D
C
And
I
I
would
be
sad
and
a
little
surprised
if
we
had
to
write
all
this
content
from
scratch.
No
III
I
love
the
idea
of
using
this
as
a
catalyst
for
getting
a
closer
connection
with
note
school
as
a
project
and
all
the
contributors
I
yeah.
We
need
to
have
like
a
it
sounds
like
we've
spent
a
lot
of
time
chatting
about
this
connection.
Nobody
know
the
school.
Do
we
need
I,
have
like
a
dedicated
small
group
about
reach
to
it
or
like
what?
What's
that
word
here
to
help
Forge
those
connections.
B
A
It's
not
good
for
basically
anyone
else.
So
that's
or
you
know
anyone
who's,
trying
to
actually
figure
out
what
it
note
is,
but
not
might
not
know
certain
terminology-
that's
used
in
there
already.
So
that's
just
kind
of
something
that
we
should
keep
on
the
radar
and,
probably
can
you
know
finalized
once
it's
once
we're
kind
of
in
the
content
buildings
phase
rather
than
the
content
definition
phase,
so
yeah
I
think
I.
Think
that's
really
just
the
last
thing.
A
C
Personally
think
so,
from
the
from
the
work
that's
been
done
on
the
structure
side,
the
initial
site,
structure,
ticket
and
I
I
think
they're
about
to
value
in
codifying
what
we've
already
done,
because
I
think
a
lot
of
a
lot
has
just
been
in
in
passing
conversation
or
in
common
threads.
That
might
not
be
surfaced.
D
You
did
an
amazing
blog
post
about
it's
just
the
initial
redesign
thinking
even
bringing
pulling
some
of
that
stuff
in
into
some
sort
of
like
research,
folder
and
just
putting
a
bunch
of
documents
into
that
I
think
would
help
comment
like
having
threads
reading
through
threads.
Isn't
that
helpful
if
there
is
a
hard
cut,
yeah
like
if
there's
a
final
outcome,
it'd
be
nice
to
have
like
a
distinct
guide,
yeah,
even
I'm?
D
C
I
yeah
I
say
if
you
could,
if
you
could
get
the
the
bones
for
a
document
like
that
started
and
throw
it
up
in
a
PR
I
think
that
would
be
an
awesome
place
to
say:
I
agree
that
we
projects
like
these.
It's
it's
really
hard
to
keep
everybody
on
the
same
page,
especially
if
it's
spread
out
across
common
threads
yeah.
Since
everything
is
so
interconnected
everything
we're
talking
about,
I
I
agree.
We
definitely
need
that.
The
document
and.
A
Additionally,
I
think
like,
if
you
even
just
set
up
like
the
framework
of
how
that
could
be
structured
with
even
adding
content.
Unless
you
have
probably
specifically
like
to
add,
like
his
article
like
Adams
article,
you
know,
I
think
we
can
all
start
going
in
and
PRN
things
into
that
doc,
because
I
think
there's
context
that
we
all
have
that
we
can
go
at
again
and
like
make
sure
it's
fulfilled.
Basically
yeah.
C
It
would
be
awesome
too
if
anybody
joins
the
conversation.
A
little
later,
just
point
the
document
and
say
it's
all
there
you
can
get
updated
by
reading
it
come
come
chat
and
be
involved
in
Cocke.
That's
it
that's
exactly
what
I'm
thinking
yum
yeah,
that's
great:
okay,
I,
I,
think
for
targeted
areas
of
the
site.
I
think
we're
ready
to
start
iterating
on
content.
I
agree
like
we
can't
like
draft
the
whole.
C
C
Totally
no
I'm
happy
to
share
the
the
source
files
around
I.
Did
it
all
in
sketch.
So
if
anybody
wants
the
source
files
to
play
with
just
let
me
know
I
guess
certain
the
ticket
I,
you
know
we'll
have
to
coordinate
about
yeah,
that's
in
the
passing
the
source
files
back
and
forth
and
works
on
what
went
but
yeah
totally.
C
C
C
Yeah
yeah,
something
to
just
pay
attention
to
like
I
think
we
should
always
be
converging
on
a
single
wireframe
or
likes
large
mass
evaluation,
or
maybe
like
one
or
two
variants
and
certain
pages
so
we'll
just
we'll.
Keep
that
coordination
and
github
comments.
Yeah
make
sure
make
sure
we
keep
consolidating
on
one
part.
H
In
the
interests
of
cleaning
up
er
issues,
the
issue
number
four:
where
we're
talking
about
site
content
and
content
structure,
can
we
say
that
evolved
into
issue
number
fifteen
website
wireframes?
So
just
if
we
could
focus
this
discussion,
it
feels
like
it
might
make
sense,
but
I'm
not
sure.
If,
yes,.
A
B
A
A
D
H
D
B
B
J
C
A
A
J
A
E
A
B
F
C
A
G
A
G
B
C
A
A
A
I
think
that
may
be
another,
so
would
someone
want
to
create
a
doodle
is
what
day
has
the
most
available
times?
Whoever
creates
it
can
have
full
prejudice
and
times
that
they're
available
and
we
can
go
from
there,
but
I
I.
Think
trying
to
you
know
if
there's
not
an
easy
time
that
we
can
all
hit
may
be
going
through.
A
doodle
will
probably
help
us.