►
From YouTube: Backdrop Design - Jan 14th, 2021
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
All
right
we
are
live
today
is
january,
14th
2021,
one
day
before
our
next
new
feature,
release,
which
is
pretty
exciting.
A
Today's
meeting
is
a
design
meeting,
and
so
we
have
a
handful
of
design
and
user
experience
issues
to
talk
about
and
as
tim
mentioned
right
before,
we
started
the
meeting
because
we
have
24
hours,
ish
left
in
this
release
cycle.
We
do
have
the
opportunity
to
get
some
design
or
user
experience
issues
in
probably
more
user
experience
stuff
than
design
stuff.
A
At
this
point,
and
so
maybe
we
should
focus
today's
agenda
on
those
issues
or
at
least
start
there
and
see
how
far
we
get
before
we
get
to
the
agenda,
though,
let's
go
around
and
do
some
quick
introductions.
I'll
start,
I'm
jen
lampton
joining
from
oakland
california
and
I'm
really
excited
about
tomorrow's
release.
So
let's
go
to
greg.
B
Hi
I'm
greg,
I'm
usually
in
australia,
but
not
joining
from
greece.
I
haven't
joined
the
last
couple
of
weeks,
so
yeah
also
excited
about
the
release
tomorrow.
C
Tim,
I
am
tim
erickson
saint
paul
tim
coming
to
you
from
deerwood
minnesota,
where
it
is
snowing.
Today
it
looks
like
we
got
an
inch
or
two
of
fresh
snow.
D
Hey,
what's
going
on,
I'm
phil
out
of
wichita
kansas,
I
guess
maybe
talk
a
little
bit
about
layouts,
it's
kind
of
become
a
big
theme
since
the
last
meeting
outside
of
that.
Don't
really
have
too
much
to
really,
I
guess,
add
to
anything,
but
just
here
for
the
discussion
and
see
where
we
can
go
luke.
Take
it
away.
E
I
am
luke
mccormick
from
currently
coming
from
san
ramon,
california,
where
it's
beautifully
warm
outside
it's
like
60
degrees.
I
took
a
bike
ride
before
nice,
things
about
living
in
california.
E
I
I'm
excited
to
to
to
talk
design.
It's
kind
of
a
side
of
my
myself.
I've
I've
always
been
like
a
behind-the-scenes,
graphic
artist
and
and
oh
always,
kind
of
interested
in
in
in
hearing
like
getting
insights
into
into
actual
design
like
how
you
choose
colors
how
you
choose
fonts
what
spaces
are?
It
doesn't
come
up
in
this
meeting
a
lot,
but
if
it
does
that's
always
good
stuff
and
let's
start.
A
All
right,
so,
I'm
not
sure
if
all
of
these
issues
are
particularly
urgent
to
talk
about
today.
I
don't
know.
If
tim
you
have
anything
in
particular,
you
want
to
talk
or
if
you
just
go
through
the
list.
A
So
maybe
we
just
take
a
peek
promoted
modules
on
the
installer
issue.
3193
this
issue
is
marked,
needs
more
feedback
so
that
one's
probably
not
in
a
state
where
we
can
get
it
in
by
tomorrow.
A
Next
issue
move
the
button
to
the
bottom
of
the
database
log
messages
page.
This
one,
I
think,
was
recently
escalated
to
pmc
no
looks
like
there's,
maybe
emerging
consensus
on
that
issue,
but
I
don't
know
how
close
it
is
to
getting
in.
C
A
Okay,
next
one
is
better
help
text
for
the
layout
path
field.
This
one
is
fixed
which
is
fantastic
merged.
It's
already
in.
A
The
next
one
is
renaming
of
the
locale
module,
and
this
is
renaming
in
the
user.
Interface
only
looks
like
the
pull
request
is
marked,
needs
work
on
that
one.
It's
not
it's,
not
a
very
big
change.
I
think
there's
just
we
wanted
to
indicate
somewhere
what
the
previous
name
of
the
module
was,
so
that,
if
you
search
to
the
modules
page
for
local,
it
would
still
match
in
the
search.
So
that's
probably
something
that
could
get
in
by
tomorrow.
A
If
we
wanted
to
it's
just
adding
text
to
the
description
next,
one
export
import
tab
order.
I
think
this
one
still
needs
feedback,
so
this
is
on
the
configuration
management
page.
We
have
the
tabs,
are
sort
of
in
a
funny
order
right
now,
there's
a
recommendation
for
reworking
them,
not
just
by
swapping
the
order
which
was
the
original
intent,
but
swapping
single
and
multi,
rather
than
export
and
import.
A
So
there's
sort
of
maybe
a
quick
thing
we
could
get
in
by
tomorrow,
which
is
swapping
the
order,
and
then
a
follow-up
issue
would
be
rethinking
the
whole
thing.
So
we'll
see
where
that
one
goes.
A
Pull
request-
maybe
that's
not
close
enough,
then
either.
A
Then
we
have
some
support.
Sorting
the
list
of
available
updates
issue.
A
Look
then
we
have.
B
Before
we
move
on
on
that
yeah,
because
the
last
update
was
about
a
month
ago
and
before
that
from
back
in
september,
so
I
was
looking
for
some
feedback
with
regards
to
how
important
it
is
to
be
grouping
the
that
specific
page
that
grouping
the
modules
by
disabled.
You
know
having
separate
groupings
for
disabled
ones.
You
guys
think
that
this
adds
value.
B
My
feeling
is
that,
first
of
all,
nobody
will
see
that
grouping
unless
you
you
enable
the
setting
that
says
also
check
for
disabled
things,
modules
and
so
on
yeah.
So
I'm
guessing
that
if
someone
does
enable
that,
like
they
care
about,
you
know,
updating
those
disabled
projects,
so
having
alphabetical
might
make
more
sense
alphabetical.
I
mean
sorry
importance,
followed
by
alphabetical
and
when
I
say
importance
I
mean
security
updates
at
the
top,
then
pending
updates
and
then
up
to
date,
modules
listed
last,
not
modules.
A
I
haven't
looked
at
the
available
updates
page
in
a
while,
but
what
I
really
liked
was
where
it
had
like
red
to
like
urgent
stuff
at
the
top
and
then
less
urgent
stuff
at
the
bottom,
so
or
even
the
ability
to
only
show
stuff
that
needed
to
be
updated.
A
Like
I
don't
care
if
it's
a
modular
theme
or
a
layout
or
backdrop
before
so,
I
would
say
it
would
probably
be
best
to
group
by
urgency
and
not
by
type,
but
if
we
had
a
way
to
list
whether
it's
a
module
theme
or
a
layout.
That
would
be
good
so,
like
maybe
in
the
description
and
a
filter.
Module
theme
earlier,
could
also
be
useful
for
people
who
do
want
to
see
only
show
me
modules
or
you
know,
most
of
the
time.
A
B
This
was
raised
as
a
follow-up
for
issue
and
that's
that's
all
in
the
issue
summary
3132,
which
did
get
merged
and
with
that
change
we
do
make
the
security
updates
bubbler
and
then
we
have
the
updates
and
then
finally,
but
we
do
that
per
section-
that's
the
thing.
So
you
have
so
you
have
a
series
of
you
know:
security,
available
updates
or
up
to
date,
and
then
it
follows
again
from
the
themes,
same
thing
for
layouts
and
then
again
for
disabled
modules
and
for
the
disabled
themes
and
disabled
layouts.
B
Yeah
at
least
at
least
at
least
reduce
it.
Maybe
so
we
have
backdrop
is
special
case
like
the
core
is
at
the
top,
and
I
agree
that
it
should
be
at
the
top
right
yeah.
But
then,
then
you
have
modules,
themes,
layouts
and
at
the
very
least
we
should
you
know,
remove
the
groupings
for
disabled
modules,
disable
things
disabled
layouts,
and
then
we
can
keep
discussing
whether
you
know
remove
the
grouping
by
type
altogether.
A
Yeah,
I
also
think
like
if
you
have
something
that
needs
a
security
update
that
should
go
before
core
like
it
should
work
like.
I
feel
like
there's
a
page
like
this
somewhere
on
the
site.
A
Already,
yes,
sidesteps,
maybe
yeah
the
status
report,
where
it's
like
the
urge
and
things
go
at
the
top
and
then
all
there
is
like
an
inherent
order
where,
like
core
should
go
first,
but
if,
if
it's
a
security
update
that
should
go
before
anything
that
doesn't
need
security
update
just
so,
it
doesn't
get
missed,
because
if
you
had
like
a
layout
or
something
that
had
a
security
update-
and
you
had
all
this
other
stuff
that
didn't
need
any
updates,
you
wouldn't
want
to
have
to
like
scroll.
D
Was
gonna
say
real,
quick
for
my
workflow,
at
least
on
for
drupal
7,
when
I
visit
the
update
status
page
like
that,
the
first
thing
I
do
is
click
on
that
filter.
To
just
show
me
updates,
I
don't
care
about
everything
else,
that's
up
to
date,
so
yeah.
I
think
if
we
were
to
move
the
updates
to
the
top,
if
we
don't
have
a
filter,
you
know
I
think
that
would
be
good.
Sometimes
it
is
nice
to
go
through
and
kind
of
look
to
see.
D
If
there
is,
you
know,
maybe
I'm
on
version
two,
and
there
is
an
actual
version
three
but
version
two
is
a
recommended
or
a
stable
release,
and
so
it
still
shows
it
as
being
hey,
you're,
you're.
Okay,
you
don't
need
update,
oh
by
the
way,
there
is
actually
new
version.
Sometimes
that's
nice
to
be
able
to
see
that
too.
So,
anyway,
yeah.
I
know
I
think,
putting
updates
at
the
top.
I
think,
as
would
probably
work
for
now.
A
A
Is
you
have
a
documentation
file
that
lists
like
here,
all
the
contrib
modules
and
the
patches
and
when
you're
doing
an
update,
it's
really
useful
to
go
through
this
list
in
alphabetical
order,
find
the
module
go
to
the
documentation
file,
find
the
module
and
match
them
up
by
name,
and
so
I
think
you
know
having
the
ability
to
put
them
in
a
way
that
you
can
search
and
find
a
specific
name
is
going
to
be
valuable
right.
So
if
you
can
go
okay
well,
my
module's
name
is
google
analytics.
A
How
do
I
know
where
it
shows
up
in
this
list?
Is
it
going
to
be
in
modules?
Is
it
going
to
be
in
modules
disabled?
Is
it
going
to
be
at
the
top
in
the
update
section,
you
know
just
giving
people
a
way
to
find
information
about
a
specific
thing.
They're
looking
for
would
be
useful.
So
maybe
I
mean
I
don't
know
if
this
is
a
table.
A
I
don't
even
know
how
this
is
rendered,
but
trying
to
figure
out
some
way
to
give
people
the
tools
they
need
to
find
information,
not
just
in
a
like.
Occasionally,
I'm
going
to
look
at
this
page,
but
like
I'm
actually
looking
to
find
information
about
x,
figuring
out
what
the
x
is
and
how
to
get
them.
A
view
of
that
information
would
be
good.
B
Yeah
one
thing
that
is
annoying
that
I
keep
recalling
when
it
comes
to
the
disabled
beat
because
it
came
up
when
I
was
working
on
the
merging
the
update
basis,
the
the
whole
disabled
thing,
instead
of
being
done
like
during
rendering
on
the
theming
bit
the
theming
function,
it's
actually
being
done
on
the
functions
that
actually
calculate
the
updates
and
it
adds
it.
It
actually
updates
the
project
type
to
say
that
it's
disabled
ping.
B
Actually,
it
actually
updates
the
table
that
is
being
so.
The
array
that
has
been
returned
by
the
function
that
calculates
the
updates
so,
instead
of
the
disabled
property
being
something
another
property,
it's
actually
the
type
that
gets
updated
and
it's
now,
instead
of
it
being
a
module,
it's
a
disabled
dust
module,
something
like
that
which
is
annoying
for
other
things.
Yeah
anyway,.
A
B
A
B
A
A
Okay,
next
one
is:
this:
is
an
oldie
but
a
goodie
on
the
publishing
options
on
a
node,
we
have
a
giant
blob
of
help
text
that
tries
to
explain
everything,
there's
a
pull
request
that
separates
it,
so
that
each
bit
of
help
text
maps
to
the
thing
that
it's
explaining
and
then
that
made
it
a
little
confusing
for
grouping.
So
I
think,
there's
a
new
pr
that
adds
a
group
around
the
other
options.
I'm
trying
to
see
if
there's.
A
F
C
C
We've
seen
my
screen,
so
yes,
this
is
the
actual
issue
so
well
here,
I'm
actually
going
to
show
you
this.
This
is
what
the
page
looks
like
currently
publish,
now
draft
schedule
for
later,
there's
just
one
block
of
text
with
help
down
there.
If
you
do
that
that
opens
this
is
with
the
pr
I
can
go
back
and
we
have
the
issue
open
too.
C
What
happened?
Where
did
these
buttons
go?.
C
B
C
Got
it,
and
it
is
this
one
okay,
so
this
is
with
the
pr.
Let's
get
the
one
without
it.
B
The
only
comment
that
I
had
was
that
it
seemed
confusing
for
certain
people,
because
that
checkbox
of
show
option
for
scheduling
is
in
the
same
level
as
the
radio
buttons
just
above
it,
it
seems
kind
of
confusing.
I
think
olaf
made
that
comment.
I'm
not
sure-
and
I
think
that
we
discussed
this
c
tools
in
d7
offered
this
thing
of
intending
things,
so
it
made
it
clear,
clear
air.
C
Yes
issue
so
at
one
point
in
the
past,
and
it
could
be,
the
pr
has
changed
since
then
it
looked
like
nate
was
questioning
whether
or
not
this
was
an
improvement,
for.
I
think
the
reasons
that
you
might
have
been
just
discussing
that
that
it
kind
of
spread
this
out
too
much,
I'm
not
sure,
but.
D
I
do
I
I
don't
see
that
being
spread
out.
I
don't
really
see
that
being
too
much
of
a
problem.
The
one
question
I
do
have
the
current
text
on
the
publish.
Now,
if
you
can
flip
back
over
there,
access
yeah
you
just
had
it
go
back
to
the
pr.
D
Npr
published
content
can
be
accessed
by
all
site
visitors.
That's
given
the
permission.
There's
permission.
D
Short
term,
I
think
that'd
be
fine,
but
I
do
think
from
a
verbage
standpoint
it
we
might
want
to
look
at
yeah,
making
that
a
little
bit
more
inclusive
from
permission
standpoint.
B
Yeah
yeah
and
specifically
say
with
by
all
by
all
by
anyone
that
has
the
whatever
view
published,
content
permission
whatever
it
is.
D
C
So
well,
I'm
going
to
argue
that
if
it
seems
to
me
like
there's
some
complexity,
if
we
actually
specify
the
permission,
because
I
there
are,
there
could
be
complicated
scenarios
where
you
have
two
different
types
of
logged
in
users
and
one
of
them
can
and
one
or
two
of
them
can
and
one
can't.
I
don't
know
I'm
just
to
me
like
permission
to
simply
say
published,
content
can
be
accessed
by
site
visitors
with
permission.
A
Yeah,
I
feel
like
there's
a
hundred
possible
scenarios
where
you
could
have
access
control
and
you
can
have
like
any
number
of
things,
but
we
probably
should
assume
that
people
who
are
using
a
site
with
that
level
of
complexity
would
either
understand
that
their
site
is
special
or
you
know,
would
have
wouldn't
have
access
to
this
if
they
didn't
understand
it.
So
I
think
explaining
like
what
backdrop
core
does
out
of
the
box
is
going
to
be
useful
and
maybe,
if
there
is
a
contrib
module
out
there,
that
does
do
access
control.
C
B
A
C
Okay,
next
this
one
just
just
to
be
clear.
This
one
just
needs
a
code
review.
It's
marked
as
works
for
me
already,
yeah.
A
A
A
All
right
next,
one
issue
4563,
is
to
clean
up
the
page
title
block,
and
this
is
just
a
little
bit
confusing.
There
are
two
options
here
that
mean
the
opposite
thing,
and
so
I
think
my
my
current
recommendation
was
to
let
people
enter
whatever
they
want
in
the
form
and
then
just
update
the
interface
to
reflect
their
intent.
So,
for
example,
there
is
a
text
field
at
the
bottom
that
says,
if
left
blank,
the
default
title
will
be
used,
but
there
is
an
option
at
the
top
for
use
default
title.
A
A
Yeah,
it
already
does
that
if
you
choose
custom
page
title,
it
shows
the
text
field,
but
if
you
don't
choose
that
it
hides
it
okay,
but
what
happens
right
now
is-
and
this
is,
I
think,
leftover
from
drupal,
where,
when
you
don't
put
anything
in
a
box,
it'll
do
something
different
and
so
there's
a
lot
of
places
all
over
the
interface
where
it
does
that
in
backdrop,
we've
tried
to
add
these
options
before
that
that
are
like
hey.
A
Do
you
want
option
a
or
option
b,
rather
than
like
leave
a
blank
for
option
b,
and
so
this
is
the
place
where
we've
done
that,
but
we
still
have
the
leave
of
blank
for
option
b
text
there
and
the
behavior
there,
where
I
think
we
could
make
the
interface
a
little
slicker,
where,
if
you
left
it
blank
for
option
b,
when
you
hit
save
the
next
time
you
open
the
form,
it
will
say,
you're
doing
option
b.
So
I
don't
know,
that's
just
my
my
thought.
There.
A
A
E
All
right
well
tim-
and
I
did
some-
did
some
spiking
yesterday-
to
try
to
see
what's
needed
and
and
and
and
it's
funny
because
we're.
C
E
Sure
why
not
so
well
I'll
wait
for
the
pop-up?
Basically,
I
I
think
what's
needed
to
to
bring
it
home
as
as
kind
of
some.
E
I
guess
since
since
we're
on
youtube
recording
someone
might
be
coming
in
not
knowing
what
it
is
I'll
I'll
do
like
like
a
30
second
overview
of
the
of
the
idea
behind
ready
to
wear
and-
and
the
idea
is
to
try
to
make
it
easier
in
backdrop
for
people
that
don't
know
what
a
theme
is
or
how
to
theme
or
don't
really
necessarily
even
know,
css
or
anything
about
design
to
nevertheless
choose
from
some
menu
and
get
enough
of
a
design
in
play
that
they
they
can
concentrate
on
whatever
it
is
they're
good
about
good
for
so
so
what
we've
kind
of
come
up
with,
and
actually
tim,
if
you
can
scroll
up
the
the
top
part
of
this
page
is,
is
really
the
the
spot.
E
Well,
maybe
because
this
theme
has
has
a
very
large
header.
E
E
The
themes
that
are
that
are
designed
to
be
used
and
can
go,
live
without
necessarily
needing
any
modifications
at
all,
and
so
there's
there's
a
bulleted
list
over
there
here
we're
in
a
block
of
themes
that
basically
fit
the
this
profile
and
and
the
that
that
bullet
list
is
actually
a
a
variation
on
theme
switcher
there
that
I
wrote
that
that,
on
I
mean
I
did
the
fairly
minor
change
that
that
unwraps,
what
was
a
a
menu
form
element
and
makes
it
into
just
a
a
clickable
bullet
list
there.
E
E
That
completes
that
picture
is,
is
a
thing
to
apply
those
themes
to
so
so
the
the
next
step
is
is
to
make
a
set
of
pages
that
are
like
dummy
site
pages
and
have
a
bullet
list
of
like
okay,
here's
here's
how
you
can
see
the
currently
selected
theme
as
a
blog
as
an
e-commerce
page.
As
you
know
a
you
know,
use
case
page
and
and
and
so
so
I
think,
there's
there's
two
and
a
half
things
left
to
get
done
and
they're
all
they're,
all
pretty
straightforward.
E
I
think-
and
you
know
I
I
want
to
erase
this.
The
the
thing
I
need
to
add
to
this
is:
is
a
list
of
the
use
case
pages,
so
I'm
going
to
dummy
that
out
like
right
after
this
call
is
there
is
I'm
going
to
create
a
list
of
use
cases
and.
E
Flushing,
those
out
and
making
them
look
good
is
is
probably
to
take
some
some
detail
work,
although,
although
maybe
we
can
just
find
those
and
include
those
and
and
so
so
there
that's
one
of
the
two
and
a
half
pieces.
The
second
of
the
two
and
a
half
pieces
is
is
filling
the
gaps
it
is.
Is
writing
a
page
or
two
that
welcomes
people
to
the
page
and
kind
of
explains?
What's
there
and
tells
them
the
things
that
aren't
there
things
like?
Okay,
you
know
if
you're
designing
site,
you
know
here's
other
resources.
E
You
might
want
to
look
for
if
you,
if
you
want
to
know
about
colors,
if
you
want
to
know
about
fonts,
if
you
want
to
know
about
the-
and
you
know
just
some
stuff-
and
you
know
layouts
large-
you
know
looming
large
for
for
us
and
then
the
reason
I
was
asking
in
our
pre-meeting
things
about
one
on
crowdsource
is
specifically
for
these
available
themes
you
each
each
one
of
these
actually
goes
to.
E
I
I
made
a
little
node
page,
that's
kind
of
like
a
you
know
about
the
steam
page,
that
that
has
space
for
sites
that
are
implemented
using
using
those
themes
and
and
that
that's
kind
of
kind
of
the
the
question
that
that
I
I
want
to
know
that.
I
want
to
ask
that
that
I
don't
know
the
answer
to
is:
is:
are
there
sites
out
there
that
use
recognizable
versions
of
these
ready
to
go
themes
that
somebody
could
go
to
and
look
at
and
be
like?
Okay,
so
there's
there's
one.
E
I
know
that
pretty
in
purple
has
as
a
an
example
out
there
that
uses
it.
I
believe
pretty
much
out
of
the
box
right
pretty
and
purple
author
and.
B
Yeah,
so
it
might
be
hard
to
sort
of
like
automate
this
because
we
don't
like,
even
if
we
pull
data
of
where
these
things
are
being
used,
we
don't
track
which
sites
are
using
them,
so
it
would
have
to
be
a
manual
sort
of
like
processing
in
input.
I
know
by
the.
E
E
I
I'm
hoping
to
find
some
sites
that
are
out
there
using
themes
that
are
available
to
to
download
as
an
example
of
of
close,
but
but
no
no
cigar,
drupal
8
came
with
the
out
of
the
box
initiative
and
they
actually
include
a
beautiful
ready-to-go
theme
with
with
triple
eight
that
the
the
engine
engine,
so
you
can't
use
it.
E
It's
like
the
exact
opposite
of
that
that
I
want
I
I
want.
I
want
something
beautiful
and
pretty
and
be
like
yes,
go
ahead.
Use
this
and
you
know
wordpress
has
that,
although
I
mean
they're
they're,
not
fantastic,
but
like
the
the
20,
you
know
the
the
the
20xx
themes
all
all
are
like
each
year
they
come
out
with
a
new
like
here.
E
Use
this,
and
you
know
I
suspect,
half
the
wordpress
sites
in
the
world
uses
one
of
those
themes
on
modified
and
and
that
that's
kind
of
where
I
want
to
go
so
so
there
that's
that's
my
thing.
I
mean
there's,
there's
three
pieces
left
left
to
go.
E
You
know,
content,
you
know
sample
content,
descriptions
of
things
you
need
besides,
what's
on
there,
just
you
know,
also
needed
and
and
as
much
as
possible
sort
of
like
fleshed
out
friendly
information
about
what
the
themes
are,
and
I
mean
to
talk
about
design
things
like
one
of
the
things
that
I've
noticed
for
you
know
a
decade
of
being
dissatisfied
with
drupal
themes,
and
you
know
moving
into
this
is
that
theme
descriptions
are
so
unhelpful,
like
they're,
they
all
say
like
you
can
use
this
for
anything,
it's
good,
it's
nice
and
you
know,
the
kind
of
thing
I
would
want
to
see
is
is
like
what
it
does.
E
This
is
you
know
a
a
dense
theme
that
uses
you
know
black
colors
or
the
you
know
what
fonts
it
uses.
What
spacing?
What
are
the
design
decisions?
What
are
what
are
the
actual
things
that
the
theme
designer
had
in
her
mind
to
differentiate
it
from
other
things
like
what
is
actually
different
about
it?
That's
important
and
you
know
all
the
ones
I
always
found
were
always
like
technical
things
like
like
this.
This
theme
uses
you
know
the
the
dxjy
atomic.
B
E
You
know
I
eventually
if
like
this,
this
is
this:
is
the
market
proofing
right
like?
If,
if
this
seems
like
a
good
idea,
then
we
can,
we
can
shuffle
it
down
to
hey.
Why
doesn't
everybody
do
this?
But-
but
I
I
at
this
point
to
to
finish
this,
so
I'm
allowed
to
do
something
else.
I
I
I
I
just
want
to
have
like
like
a
minimum
thing.
B
We're
close,
I
find
it
helpful.
We
just
need
a
bigger
collection
of
things
which
will
happen
organically,
I
guess
over
time
and
as
luke
said
just
iron
iron
out,
like
the
final
details.
That
would
make
this
more
useful.
E
B
A
Yep,
okay!
Well,
I'm
going
to
stop
the
recording,
but
everybody
stick
around
if
you
want
to
hang
out
for
the
depth.