►
From YouTube: Backdrop Design - 2021/02/11
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
on
youtube
today
is
thursday
february
11th,
and
this
is
our
fortnightly,
design
and
user
experience
meeting
before
we
get
into
the
agenda.
I'd
like
to
go
around
and
do
some
quick
introductions
see
if
you
can
share
what
your
name
is
where
you're
from
and
if
there's
anything
fun
you
want
to
share
with
the
group
in
30
seconds
or
less
that's
not
already
on
the
agenda.
We
can
go
ahead
and
do
that
I'll
start.
My
name
is
john
lampton,
I'm
joining
from
oakland
california.
B
C
D
D
E
No,
no!
It's
okay!
So
I
am
tim
erickson
coming
to
you
from
deerwood
minnesota,
where
the
weather
and
wildlife
report
is
the
turkeys
were
just
eating
but
left
they're
very
sensitive
because
it
is
minus
four
degrees
fahrenheit
at
two
in
the
afternoon
and
it's
minus
20
celsius
anyways.
So
I'm
staying
inside
today
and
working
on
backdrop.
A
All
right
at
the
beginning
of
our
agenda,
we
have
a
theme
initiative
update.
I
don't
know
if
there's
any
particular
information
you
want
to
share
with
us
luke,
but
we
have
a
couple
of
issues
to
review.
Also.
A
I
was
just
gonna
mention
that
we
have
some
ongoing
issues
that
we're
working
on.
One
of
them
is
to
get
promoted,
feature
complete
themes
right
now.
A
I
don't
think
that
issue
has
been
seen
very
much
activity,
but
it
is
issue
number
four,
four,
four:
five,
in
the
backdrop
core
queue,
and
that
is
essentially
the
ability
to
allow
people
to
find
themes
that
are
sort
of
production
ready
for
use
on
their
sites,
and
I
think
it
closely
parallels
our
similar
initiate
motive
to
promote
recommended
modules.
A
Both
of
them
are
just
going
to
require
a
checkbox
on
the
node
form,
on
backup,
cms.org,
special
placement
of
modules
that
have
that
box
checked
on
backtrack,
cms.org
and
then
special
placement
of
those
modules
in
the
installer
on
backdrop,
the
product,
so
that
would
be
on
the
install
modules
page
or
on
the
install
themes,
page,
some
kind
of
special
coloring
or
something
in
order
to
get
those
things
to
happen.
A
We
need
to
have
this
checkbox
better
supported
in
project
module,
which
is
the
tool
that
lists
all
of
the
modules,
themes
and
layouts
that
are
available
so
that
your
backdrop
site
can
check
that
list,
and
I
think
that's
where
we're
stuck
right
now
on
both
these
issues
is
that
project
module
does
not
currently
support
that
checkbox.
As
soon
as
we
can
get
that
support
into
project
module,
we
can
start
doing
different
things
based
on
the
checkbox
on
backdrop
cms.org
and
on
the
application
itself
tim.
A
This
is
another
one
of
these
issues
that
we
have
on
this
recurring
agenda
that
doesn't
get
a
lot
of
activity,
and
so
half
of
my
mind
is
like,
oh
maybe
we
shouldn't
talk
about
it
all
the
time,
but
I
also
feel
like.
If
we
don't
talk
about
it
all
the
time
it
maybe
won't
get
attention.
If
we
do,
maybe
you
want
to
make
will
be
like.
Oh
hey.
A
I
really
want
to
work
on
that
this
week,
so
I'm
50
50
on
that
one
as
to
whether
it
should
be
removed,
but
it's
here
today,
so
we
also
have
and
intent
to
make
all
themes
better.
By
providing
standard
elements
in
this
style
guide,
contributed
module
and
then
we
could
have
some
requirements
for
becoming
a
recommended
theme.
You
have
to
meet
all
of
the
stuff,
that's
in
the
style
guide.
A
Module
has
to
be
styled
for
your
theme
and
then
we
can
say:
okay,
you're
recommended
and
check
the
box
for
a
theme,
but
we
don't
currently
have
all
of
the
elements
we
want
in
the
style
guide.
A
So
we
also
have
ongoing
issues
for
that
and
the
style
guide
module
is
in
backdrop
contrib,
and
it
has
its
own
issue
queue
where
we're
working
on
stuff,
like
that
step,
four,
that
I
suppose
so,
if
anyone
wants
to
help
us,
make
style
guide
better,
that
will
eventually
end
up
being
what
we
use
to
determine
whether
a
theme
should
be
recommended
or
not.
A
We
also
need
to
document
this
stuff.
I
think
we
had
written
that
down
somewhere.
I
think
it
might
have
been
in
the
issue
4445
what
our
requirements
are
going
to
be
for
a
recommended
thing,
and
then
we
would
need
to
take
those
requirements
and
publish
them
somewhere,
so
that,
if
you
want
your
theme
to
be
recommended,
there's
a
place,
you
can
go
to
consult
that
that's
not
an
issue
in
the
queue
that
might
be
something
we
could
consider
adding
to
our
new
setup
documentation
on
the
docs
site.
At
some
point.
B
Okay,
so
so
I
have
something
that's
related
to
all
of
these
that
that
I
I
mentioned
in
zulu
to
try
to
get
into
the
the
agenda,
which
is
surprising,
and
I
we're
having
some
chatter
behind
the
scenes
and-
and
we
we're
kind
of
looking
into
the
general
issue
of
of
examples
and
and
that
that
made
me
my
my
question
was
specifically
about
showcase
so,
like
there
there's,
there's
a
showcase
menu
on
backdropcms.org,
and
I
I
was
wondering
where
we
are
sort
of
as
a
community
in
in
terms
of
like
having
having
a
set
of
built
sites
with
backdrop
that
they
can
be
subjected
to
some
analysis.
B
They
can
be
subjected
to
like
okay.
How
did
they
get
that?
You
know
what
what
did
they
do?
What
did
they
use,
what
were
the
pieces
and
and
and
try
to
sort
of
determine
what
what
what
makes
a
workable
site
and-
and
this
kind
of
like
cuts
across
all
these
things
right?
It
serves
like
a
or
an
issue
to
try
to
decipher
these
elements
like
like.
I
I
don't
want
to
you
know.
B
A
Yeah,
I
don't
know,
I
think
it
varies.
You
know
whenever
somebody
feels
like
taking
one
of
the
sites
they've
built
and
putting
up
there,
they
put
it
up
there
right
now.
The
showcase
section
is
intended,
mostly
for
like
marketing
purposes,
and
it's
sort
of
supposed
to
be
like
really
pretty
pictures,
and
you
know
why
you
chose
backdrop,
but
there
isn't
really
a
lot
of
like
technical
information
there.
I
think
it'll
be
really
interesting
to
include
that.
A
I'm
not
sure
it
needs
to
be
required
it
because
it's
sort
of
as
it
solves
a
different
need,
but
it
would
be
really
interesting
if
you
could
have
one
site
that
fit
both.
That
was
like.
A
Okay,
here's
the
you
know
showcase
you
pretty
pictures,
but
then,
if
there
was
some
kind
of
link
that
was
like
how
was
this
built
and
then
it
went
to
another
page
that
was
like
here's,
the
technical
information
of
like
the
node
types
and
then
layouts
and
whatever
modules
that
would
be
really
cool,
because
it
would
be
like
a
deep
dive
for
people
who
like
want
to
know.
I
saw
the
site.
How
did
they
do
that?
A
But
it
wouldn't
necessarily
be
you
know,
high
level
for
the
person
who's
like
what
does
backdrop
look
like
who
maybe
doesn't
need
to
know
that
yet.
B
I'll
I'll
say
like
savasi,
and
I
that
that
natalie
sebastian's
involved
he
might
do
it.
You
know
we
would
be
interested
in
in
sort
of
you
know
interviewing
the
the
makers
of
the
showcase
size
of
big
so
how'd.
You
do
that
or
what
can
you
tell
me
about
this
and-
and
we
can
see
if
that
that
can
kind
of
build
into?
I.
A
Think
that
would
be
fantastic
if
you
can
figure
out
what
that
looks
like.
Is
it
like
a
blog
post
interview
of
you
talking
to
the
person
who
made
the
site
or
is
it
like
a
whole
new
thing?
I
would
love
to
see
some
of
like,
even
if
you
just
do
the
first
one
and
they're
like
this
is
this
is
what
it
looks
like.
How
can
we
build
it?
That
would
be
great
yeah.
I
would
love
to
speak.
A
E
E
A
A
Maybe
should
that
go
into
the
issue
queue
on
factofcns.org,
so
we
don't
forget
about
it.
G
A
Okay,
I
don't
know,
look
if
you
have
time
to
make
that
ticket
too.
It
doesn't
have
to
be
fully
fleshed
out,
but
just
so
that
it
reminds
us,
and
then
we
can
come
back
to
it
later.
B
I
I
think
I
can
now
in
the
in
the
backdrop,
though,
in
the
backgroundcms.org
issue
right
yeah.
B
Okay,
it
can
serve
a
certain
notice
that,
like
anyone
who's
who
has
a
a
showcase,
I
shouldn't
be
surprised
if
they
get
a
message
from
me
asking
about
it,
I
I
mean:
are
they?
Are
they
lists?
Does
each
one
say
who
did?
It
is
their
context,
information.
A
A
There
might
be
a
like,
like
a
reference
to
or
supporting
organizations,
field
or
something,
but
I
don't.
E
E
Showcase,
let's
make
an
issue
to
do
that
at
least.
E
E
Yeah,
I'm
I'm
looking
at
one
of
the
actual
the
nodes
and
I'm
not
seeing
actually
even
a
you
know
a
hidden
field.
I
mean
we
have
whoever
added
it
authored
the
node,
but
there
is
no
like
hidden
field
that
says
who
built
the
neuter.
So
we
should
just
add
those
fields
and
display
them
and
have
them
be
optional.
A
All
right.
Only
other
thing
issue
in
the
theme
initiative
section
was
making
it
easier
to
preview
themes
on
desktop
and
mobile.
This
is
what
I
was
about
to
create
an
issue
for,
in
the
backdrop,
semester
queue
because
it's
on
this
agenda,
but
it
doesn't
have
a
link
to
an
issue.
I
searched
for
it
and
couldn't
find
one.
I
know
I've
talked
about
this
a
bunch
of
times.
I
might
just
be
looking
in
the
wrong
place.
A
The
goal
would
be
to
make
some
tool
that
allows
people
to
see
what
a
site
would
look
like
in
a
theme
that
is
not
putting
the
theme
on
their
own
website,
and
so
that
could
look
something
like
I
don't
know.
Themeforest
is
a
really
good
theme
tool.
The
wordpress
community
has
a
really
good
way
for
previewing
themes.
In
some
cases,
they
fire
up
entirely
new
websites
that
aren't
using
the
themes.
In
other
cases,
they
link
to
the
theme
developers
example
site.
A
It
would
be
great
if
we
could
just
figure
out
some
way
to
allow
people
to
preview
their
themes,
preferably
in
an
environment
where
you
can
either
resize
your
browser
or
click
a
link
from
a
phone
and
see
what
it'll
look
like
in
in
multiple
sizes.
Click
a
button
on
the
device
you're
using-
and
I
know
we've
talked
about
a
lot
of
different
architecture
for
how
that
could
be
done,
and
it's
a
lot
of
work.
A
And
so
it
hasn't
been
a
high
priority
for
us,
which
is
probably
why
I
can't
find
the
issue
for
it.
But
it
would
be
good
if
we
could
get
that
issue
created
somewhere,
so
that
people
who
do
have
interesting
ideas
about
how
to
set
it
up,
have
a
place
to
document
that,
because
I
know
we've
talked
about
it.
A
lot.
E
I'd
like
to
suggest
that
we
have
so
luke
has
done
a
lot
of
work
on
the
one
ready
to
wear
sight
and
I've
experimented
with
a
variation
of
that,
and
I
think
and
he's
we've
shown
them
during
these
meetings.
I
think
briefly,
but
I
think
it
would
be
helpful
to
take
an
extended
block
of
time
and
just
look
over
what
we've
done
so
far
and
get
feedback
like
on.
E
How
could
this
be
useful,
or
you
know
how
close
is
this
to
being
something
useful
or
in
this
ties
into
what
you
were
just
talking
about
jen,
and
I
don't
know
if
we
should
schedule
a
separate
time
for
that
or
if
we
could
dedicate
one
of
these
meetings,
maybe
in
two
weeks
to
sort
of
dig
deep
and
look
at
the
work.
That's
been
done
so
far
on
the
ready
to
wear
and
like
figure
out
how
to
bring
it.
To
a
close,
I
think
that's
what
luke's
been
struggling
with.
Oh
my
god
yeah.
E
E
So
does
anybody
have
thoughts
on
whether
we
could
schedule
a
separate
sort
of
ready-to-wear
meeting
where
we
did
that
but
luke,
and
I
have
done
that
on
really
short
notice.
When
we're
the
only
two
that
know
about
it
and
that's
not
helpful
so.
E
Any
thoughts
on
how
to
on
how
to
best
do.
A
E
Okay:
let's
do
that
there's
a
I'm
just
gonna
throw
something
out
we
have.
We
have
tried
to
do
this
on
tuesdays
before
next
tuesday
is
a
is
a
vug,
so
I'm
gonna
suggest
in
two
weeks
on
tuesday
beautiful
we
have
that
we
have
a
ready-to-wear
meeting,
we
get
it
on
the
agenda,
let
people
know
about
it
and
that
the
whole
point
purpose
of
this
meeting
is
to
sort
of
look
at
review.
The
work
that's
been
done
and
figure
out.
E
Good,
I
have
a
a
similar
request
and
I
might
just
I'd
like
a
volunteer
or
two
to
meet
with
me
and
it's
very
much
related
to
this.
I
would
like
to
create
a
new.
I
have
a
new
design
for
a
new
client
site
and
I
would
like
to
make
it
into
a
contrib
theme
and
I'm
I
need
feedback.
I
I
still
struggle
with
this,
like
what
should,
in
the
backdrop,
world
what
what
goes
in
the
theme
that
you
know
in
drupal
would
have
been.
E
You
know
like
the
positioning
in
drupal
in
a
theme
you
might
like,
have
a
position
for
a
specific
menu
and
you
hard
code
that
into
the
template.
That
came
with
the
theme
and
I
still
struggle
with
like.
Do
we
just
not
intend
for
themes
to
be
at
all
that
specific
or
if
we
do
that,
and
I
know
jen
you
and
I
have
talked
about
a
few
issues
and
you've.
Given
me
some
suggestions,
but
I
I
I
don't
know
what
to
do
with
them
and
right
now.
I
have
like
a
really
practical
example.
A
Yeah,
it's
interesting,
I
think,
like
as
a
contributing
maintainer
like
that's
sort
of
your
decision
and
I'd
be
happy
to
talk
about
it
with
you
just
to
be
like
well,
if
I
was
gonna
wear
this
theme,
this
is
how
I
might
want
it
to
work,
but
yeah
I've
seen
it
done
both
ways
where
sometimes
it's
like
you
get
this
thing
in
the
sidebar
as
part
of
this
theme,
and
if
you
don't
want
it,
there,
you've
gotta
like
uncode
it
or
sometimes
it's
like
this
theme
is
just
like
we're
really
loose.
E
A
E
Sort
of
get
that
on
a
broad
philosophical
yeah,
but
when
I
start
thinking
about
the
specifics,
then
it
gets
a
little
fuzzier
and
I
think
this
ties
back
to
what
we
were
just
one
of
the
earlier
items
which
is
like.
If
we
had
approved
themes
again,
does
it
you
know
to
be
an
approved
theme?
Does
that
mean
I
should
be
able
to
to
turn
on
any
layout
and
it
would
work
or
like?
A
Yeah,
I
don't
I
mean
I
don't
that's
another
thing
where
probably
would
be
a
case-by-case
plate
basis
for
the
theme,
but
I
haven't
seen
a
theme
where
I
don't
think
it
would
be
practical
to
support
all
four
layouts
that'd,
be
some
decisions
made
about
like
whether
your
style
elements
will
be
the
same
in
a
left
sidebar
all
the
time
or
if
the
left
sidebar
is
too
wide,
maybe
it's
not
gray
anymore
or
whatever,
but
it
seems
like
for
the
most
part.
If
you
do
nothing,
your
theme
should
work
across
all
layouts.
A
E
I
think
we
have
an
example
like
the
way,
I
think
it's
the
lateral
theme,
which
sort
of
assumes
that
you
have
stuff
in
the
left
column
and
then,
if
you,
if
you
do
like
a
two
column
layout,
suddenly
you've
got
this
really
weird
third
column.
That
just
looks
out
of
place
right.
So
could
that
be
an
approved
theme?
If
it
really
doesn't
look
good
in
that,
so
when
you
see
a
case-by-case
basis,
I
get
that
just
in
general.
But
if
we're
approving
themes
then
don't
we
lose
something.
G
A
No,
this
is
every
everyone
is
a
qualifier,
an
application.
That's
like
I
would
like
to
be
promoted
and
then
it
would
be
reviewed.
Then
we'd
say:
oh
you
know
on
this
layout.
You
maybe
haven't
thought
about
what
it
would
look
like,
and
this
is
a
screenshot.
How
do
you
want
to
handle
it
and
they'll
be
like?
Oh?
Maybe
this
style
applies
to
the
left,
one
or
the
right
one
or
whatever,
but
yeah.
A
I
don't
know
what
that
theme
looks
like,
but
I
would
say
that
would
be
part
of
the
review
process
and
even
if
just
like,
don't
style
this
layout,
that's
fine
right
leave
it
up
to
the
person
who
uses
the
theme.
I
think
that's
a
perfectly
fine
out
if
they
don't
want
to
support
anything
that.
D
You
know,
but
I
was
under
the
impression
that
one
of
the
quote
unquote
selling
features
of
the
backdrop
layout
system
is
that
the
way
that
whole
system
is
set
up
is
that
themes
were
layout.
Agnostic.
Things
were
designed
to
be
were
able
to
work
on
any
layout.
A
D
A
And
I
think
that
the
more
things
we
see
we
might
come
across
places
where
we
need
to
rethink
that,
or
maybe
like
core
issues
where
we
had
something
we
hadn't
considered,
and
I
think
that
the
only
way
we're
going
to
find
those
issues
is
by
reviewing
all
these
themes.
In
that
way,
does
everything
work
on
every
layout
or
are
there
cases
where
you
know
we
need
to
build
in
more
flexibility
in
core,
so
it
would
be
interesting.
A
Yeah,
that's
another
thing
too,
is
that
you
know
we
have
these
neat
contrib
modules
that
allow
you
to
take
things
that
are
like
defined
in
your
themes,
info
file
and
apply
them.
We
might
find
more
and
more
that
you
know
those
control
modules
are
necessary
and
maybe
they
should
become
part
of
core.
So.
B
Yeah
yeah,
I
mean
it
gets
pretty
quickly
into
sort
of
deep
product
philosophy
questions
right,
because
because
we
we
all
know
that
the
the
basic
structure
and
framework
is
is
incredibly
flexible
and
create,
you
know,
has
has
you
know
vast
amounts
of
custom,
customization
abilities,
but
all
that
customization
is
kind
of
intrinsically
overwhelming
to
to
anyone
coming
new
into
it.
So
so
exactly
what
those
landing
patterns
collect.
B
B
The
tree
gets
really
big
really
fast,
so
so
restricting
it
somehow
can
be
very
valuable,
but
you
know
fraught
with
peril
along
the
way
you
have
to
be
very
careful
to
to
not
unnecessarily
damage,
you
know
potential
and
possibilities,
and
that
kind
of
thing.
Those
are
the
questions.
I
don't
know
what
the
answers
are.
B
A
All
right
do
we
move
on
to
product
related
issues,
yep
all
right,
so
we
have
under
user
experience
issues.
We
have
this
moving
the
clear
log
messages
button
issue
which
I
think
is
waiting
escalation
to
pmc,
I'm
just
going
to
check
on
it.
It
doesn't
look
like
we've
made
any
progress
on
that
in
since
december.
E
A
The
available
updates
page
gets
noisy
with
too
many
projects
and
different
statuses.
This
is
a
follow-up
to
our
sorting
that
page
by
status,
project
or
something
I
know
gregory's
been
working
on.
This
looks
like
it's
currently.
Labeled
needs
more
feedback
and
there's
not
a
pull
request.
D
A
A
Title
block:
this
is
just
an
issue
where
we
are
asking
people
on
the
interface
for
the
same
value
in
two
different
places
and
there's
some
discussion
about
how
we
might
make
that
cleaner
to
the
user.
What's
actually
going
on,
there
could
be
some
feedback.
People
have
thoughts
on
it
and
then
text
change.
E
E
That's
opened
up
a
number
of
other
issues,
and
the
original
suggestion
was
that
we
simply
that
the
first
suggestion
was
simply
that
we
changed
the
default
from
user,
that,
if,
if
the
user
removes
the
home
path,
that
instead
of
defaulting
to
the
user
page
it
default
to
the
node
page-
which
I
think
is
what
drupal
7
did
yeah,
that
was,
that
was
not
intended
to
like
solve
all
the
problems,
but
it
was
just
like
one
step
in
the
direction
and
we
had
a
pr
that
worked.
But
what's
happened.
E
I
think,
is
that
this
issue
has
escalated
with
all
kinds
of
other
ideas,
and
I'm
just
wondering
if
you
know
we
have
a
working
pr.
That
did
this
original
thing.
Is
that
the
wrong
thing
to
do?
Or
can
we
go
ahead
and
do
this
one
thing
and
then
continue
with
the
other
ideas
right
now?
I
feel
like
this
just
totally
bogged
down
with
all
the
other
ideas.
A
Yeah,
I
think
maybe
what
we
should
do
is
create
a
separate
issue
that
just
goes
back
to
doing
that
one
thing
and
then
let
this
one
continue
because
everybody's
talking
here
about
other
options
but
yeah.
This
definitely
seems
like
a
bug.
Okay,
I
don't
think
it's
ever
supposed
to
go
to
user.
E
Okay,
so
then
we
would
like
the
title,
although
I
I
think
I
was
the
one
who
changed
it
at
some
point
along
the
way.
The
title
is
really
specific
to
this
solution
and-
and
I
think
so
you
know-
if
we're
going
to
create
a
new
issue,
then
I
don't
know
we
could
keep
the
same
title
create
a
new
issue
at
move.
The
have
to
have
the
pull
request
moved
to
the
new,
because
we
have
a
full
request
already
on
this
one:
more
requests.
E
To
discuss
I
mean
I
think
I
would
prefer
to
just
leave
this
issue
solve
it
and
close
it,
because
we've
opened
I've
already
already
opened
up
a
number
of
other
issues.
I've
crea,
I
created
a
meta
issue
on
on
this.
This
whole
thing:
it's
like
we
have
other
places
to
talk
about
this.
It's
just
that
people
keep
bringing
the
other
things
back
into
this
yeah.
A
A
Sometimes
I
I'm
not
sure
if
it's
worth
it
in
this
case,
but
when
I
create
a
new
issue,
I
go
back
through
the
old
issue
and
I
try
and
pull
all
the
like
relevant
comments
and
like
at
mention
those
people,
a
new
issue,
so
that
when
a
conversation
happens
over
there,
they'll
get
emails
so
that
they're
at
least
included.
They
don't
have
to
go,
find
that
issue
on
their
own.
It
sort
of
finds
them,
but
maybe
that
they've
already
found
them
forgotten.
I
don't
know.
E
Well,
that's
part
of
the
week
yeah
part
of
the
reason
I
brought
it
up,
though,
is
I
wasn't
sure
if
the
discussion
I
mean
originally,
there
seemed
to
be
consensus
that
this
was
a
good
move
to
switch
that,
but
I
was
it's
not
100
clear
to
me
that
maybe
that
idea
has
changed.
So
if
anybody
objects
to
that
it
is
like
one
step.
I
wish
they
would
very
clearly
state
that,
because
instead,
what
I
hear
are
these
other
ideas
which
leave
me
not
sure.
Are
you
objecting
to
this
change
or
just
suggesting
other
things?
E
A
A
Then
we
have,
if
anyone's
interested
in
user
experience,
issues
on
github.
You
can
search
this
uq
for
anything
with
capital.
U
capital,
x
and
square
brackets
and
you'll
find
all
of
our
user
experience
issues.
We
also
have
a
handful
of
design
only
related
issues,
and
that
includes
better
defaults
for
page
layouts.
Just
something
tim,
I
think
you've
been
championing
for
a
while.
E
Yeah,
that's
that
is
sort
of
hung
up
on
me
needing
to
talk
to
you
about
understanding
your
ideas.
Yeah.
A
I
think
also
this.
This
issue
will
probably
benefit
from
being
broken
down
into
a
bunch
of
little
smaller
ones.
Where,
like
let's
do
the
stuff,
that's
non-controversial
and
just
get
that
done,
and
then
the
stuff
that
is
controversial.
We
can
sort
of
have
that
crime,
because
I
think,
there's
a
lot
of
baby
steps
that
can
be
taken
here
too.
E
Yeah
well,
actually
it
is
so.
The
title
in
the
agenda
is
no
longer
accurate.
The
title
on
the
actual
issue
narrows
it
down
to
one
specific
change.
Let's
make
this
one
tiny
change.
The
problem
is,
I
think
you
have
some
ideas
about
how
to
do
that.
That
I
don't
understand
so
I
don't
know
what
to
do
next.
Okay,
so.
E
A
We
also
have
this
issue
about
removing
white
space
when
you
have
two
here
blocks
placed
next
to
each
other
that
are
not
in
the
top
region,
I
believe,
which
is,
I
think,
still
dependent
on
css
changes
in
core.
I
haven't
looked
at
this
pull
requests.
Do
we
even
have
one?
No.
A
This
might
also
be
the
kind
of
thing
where
if
we
have
a
pull
request,
the
change,
the
type
of
change
might
not
be
as
dangerous
as
we
think
it
is
so
it
might
be
worth
making
one,
and
I
know
there
was
a
couple
where
bw
panda
wrote
a
poll
request
and
I'm
like.
Oh
my
god,
it's
going
to
break
everything,
and
then
I
just
quoted
him
like
actually
it's
fine,
so
that
might
be
one
where.
If
we
had
a
pull
request,
it
would
be
easier
to
move
that
forward.
E
E
A
E
And
I
found
a
I
found
kind
of
a
workaround
to
it,
which
I
described
in
the
issue
where
you
can
add
a
class
to
a
to
a
block,
and
then
it
it's
yeah.
This
is
basically
effects
basis.
And
basically,
what
happens
is
if
you,
if
you
put
two
hero,
blocks
next
to
each
other
in
a
hero
region,
a
basis
doesn't
put
a
space
behind
them,
although
it
does,
if
they're
in
the
top,
if
they're
in
the
top
region.
A
A
I
think
that's
the
correct
fix,
but
that
would
have
more
far-reaching
implications
than
just
affecting
when
hero
blocks
are
like
when
you
have
more
than
one
a
block
in
a
region.
That's
not
top
that's
a
little
bit
of
an
edge
case,
but
everybody
is
going
to
have
a
main
area,
and
so,
if
we
just
add
extra
padding
to
it,
it's
a
little
yeah.
E
E
So
anyways,
I'm
I
don't
know
I'm
inclined
to
just
take
this
off
the
weekly
agenda,
because
I
don't
know
what
to
do
with
it.
I
I've
my
I've
moved
away
from
you
know
using
base.
I
won't
use
basis
for
something
like
this
anymore
because
it
just
has
too
many
quirks
like
this,
and
we
have-
and
we
have
no
consensus
on
how
to
fix
that.
So
for
now,
I've
like
de-prioritized
any
css
issues
on
basis
until
we
can
get
some
decision
and
I'm
focused
on
other
things,
just
making
contributions
that
solve
them.
G
In
tattoo,
yes,.
A
Yeah,
but
I
think
another
thing
too,
is
I
just
added
the
2.x
milestone
onto
there.
It
would
be
a
good
idea
if
we
could
have
a
collection
of
stuff
like
this,
where
it's
like
we're
debating
about
whether
we
can
change
it
from
one
to
x,
but
if
we
know
for
sure
we
can
change
it
into
x,
let's
just
like
okay
push
it.
A
If
it's
not
important
push
it
there
and
then
at
least
we'll
get
it
fixed
in
2.x,
and
we
won't
forget
when
2.x
comes
around
that
this
was
a
problem,
so
yeah,
interesting,
okay,
yeah
and
then
here's
this
how
to
change
css
safely
and
core
issue
4167,
which
is
complicated.
A
So
I
added
a
new
recommended
alternative
recently,
not
recently
it
was
in
early
december,
but.
D
A
We
have
a
lot
of
like
we
could
do
this
way
or
we
could
do
it
this
way.
We
do
it
this
way
and
nobody
seems
to
agree
with
100
with
any
of
them,
but
it
might
be
the
kind
of
thing
that
we
kicked
the
pmc
with
a
recommendation
for
one
of
them,
or
maybe
we
summarize
all
of
them-
I
don't
know
but
yeah.
A
If
anyone
hasn't
looked
at
that
recently,
I
would
encourage
you
to
weigh
in
on
the
supplemental
selectors
option,
just
different
than
supplemental
style
sheets
or
the
other
remember
what
the
other
solution
was,
but.
E
Yeah
one
of
the
things
that
happens
in
an
issue
like
this
right
is
every
idea
that
gets
thrown
out
people
criticize
the
problems
with
it,
but
but
then
some
people
don't
say
well.
This
is
how
I
think
we
should
handle
it
right
and
I
think,
to
some
extent
what
I
want
to
hear
from
people-
and
I
think
I
might
have
asked
this
before
and
gotten
some
answers.
It's
like.
Okay,
do
you
you
don't
like
any
of
these
five
options,
but
does
that
mean
you
prefer
the
status
quo?
Are
you?
E
A
So
far,
it
doesn't
look
like
there's
a
lot
of
negative
responses
to
the
last
month.
So
far,
it's
just
polanos
and
vw
panda.
So
I
want
to
make
sure
that
anyone
who
wants
to
have
a
chance
to
object
to
that.
A
Okay,
let's
see.
A
That's
it
for
today's
design
agenda,
which
is
good
because
it's
1
pm
or
it
has
been
an
hour
since
we
started
the
meeting
depending
on
where
you
are.
This
is
not
1pm,
so
I
would
say:
let's
see
if
anyone
has
anything
specific,
they
want
to
talk
about
and
if
not,
let's
wrap
this
up
and
move
on
to
dev
meeting.