►
From YouTube: November 5, 2020 - Design and UX Meeting
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
Really
silly
all
right
we're
going
hello,
everyone,
it
is
the
backdrop
weekly
or
bi-weekly
design
and
ux
meeting
or
usability
meeting.
It
is
november
5th
2020.,
and
this
meeting
we
normally
get
together
to
talk
about
design
related
tasks,
but,
moreover,
probably
user
interface
related
tasks
considering
those
in
attendance
are
not
actually
designers.
A
So
so
we
do
what
we
can,
but
we
always
reach
out
and
try
to
encourage
anyone
that
has
those
design
related
skills
to
join
these
meetings
and
speak
to
some
of
the
makers
of
backdrop
directly
and
if
you
have
suggestions
and
want
to
discuss
things
that
are
related
to
design,
then
this
meeting
is
a
holding
place
for
that
discussion
to
happen.
A
This
week
we
went
through
the
agenda
beforehand
and
we
have
a
whole
bunch
of
ux
related
issues
and
some
design
related
issues,
but,
generally
speaking,
the
issues
are
mostly
all
just
in
discussion
phases
and
there's
they've
also
been
discussed
heavily,
but
they're
all
rather
inconclusive
a
couple
of
them
like
a
really
simple
one.
Moving
the
clear
log
messages
to
the
bottom
of
the
watchdog
messages.
Page
issue
2353,
for
example,
has
been
proposed
to
move
to
the
pmc
I
was
like
just
like.
A
Can
we
get
an
answer
on
this,
because
the
waffling
has
gone
back
and
forth
enough,
and
so
some
of
these
other
issues
we
might
also
start
seeing
some
more
of
those
things
just
going
to
kind
of
executive
decisions,
one
of
which
is
something
that
tim
is
interested
in
discussing
today,
which
is
the
safe
handling
of
css
changes
to
our
existing
themes,
and
that's
something
that
we've
kind
of
gone
back
and
forth
on
different
options.
B
Yes,
so
basically
the
idea
examples
are-
and
we
just
talked
about
this
one
before
before
the
meeting
is
the
the
issue
rate-
the
agenda
right
before
the
white
gap
between
two
hero
blocks
and
the
idea
is
you
sort
of
have
two
hero
blocks
with
a
background
color
on
them
on
in
basis
right
now
out
by
default?
There's
a
white
gap
between
them
and
the
goal
was
to
to
fix
that
so
that
you
could
get
rid
of
that
gap
with
css
without
breaking
any
existing
sites.
B
B
Personally,
I
had
kind
of
I
put
a
lot
of
effort
into
this
issue
for
a
while
and
then
just
decided
to
back
off
and
focus
on
other
things,
but
now
I
I'm
seeing
this
keep
popping
up
anytime.
Somebody
raises
an
issue
that
even
touches
on
this.
It's
like
well,
you
know
we,
we
don't
have
a
solution
for
that.
B
I
went
back
and
looked
through
the
discussions
earlier
this
week
and
I
think
it's
not
so
clear
to
me
one
that,
even
even
on
the
specific
solution
of
I
mean
someone
when
you
have
a
problem
with
three
or
four
multiple
solutions
out
there,
it's
sometimes
really
hard
to
come
to
a
consensus,
because
people
are
sometimes
like
talking
about
the
merits
and
demerits
of
a
specific
idea.
B
I
think
there
were
three
or
four
that
or
maybe
up
to
half
of
them
had
sort
of
unequivocally
said
sure
that
would
you
know
they
may
not
love
the
idea,
but
it
would
be
okay,
there's
one
or
two
that
might
be
sort
of
strongly
opposed
to
it.
B
But
there
were
a
few
people
who
were
sort
of
like
well,
I
don't
like
it,
but
they
didn't
really
say
no
and
I'm
wondering
if
we're
not
closer
to
a
possible
consensus
here
and
even
or
I
guess
my
suggestion
was
that
we
tried
to
more
aggressively
before
taking
this
to
the
pmc,
which
maybe
we
need
to,
but
before
doing
that,
if
there
isn't
some
way
that
we
could
sort
of
pull
people
and
and
get
a
more
clear
statement
of
exactly
where
they're
at
and
make
sure
that
we're
not
sort
of
that.
B
It's
it's
not
getting
a
roadblock
just
because
of
some
opinions,
for
example
gregory.
You
know
you
have
definitely
said
you,
don't
love
the
supplemental
style
sheets,
but
I
don't
know
that
you've
ever
said
one
that
you
have
a
preferred
like
there's
a
better
solution
or
two
that
borrowing
a
better
solution.
You
wouldn't
accept
this
solution
right.
Yes,.
C
B
B
Yeah
and
sort
of
I've
been
taking
that
as
a
vote.
No,
but
maybe
that's
too
strong,
and
maybe
I
should
give
you
a
chance
to
clarify
that
at
least
on
the
supplemental
idea.
So
anyways.
B
Nate
during
the
last
release
cycle
you
and
I
had
a
long
discussion
about-
I
mean
I
think,
you've
had
reservations
about
the
supplemental
style
sheet.
But
again
I
don't
think
you
said
no
completely
either.
A
Yep
same
thing,
where
I
didn't
really
have
any
any
better
ideas
to
to
do
that,
can
you
can
you
recap
what
the
supplemental
style
sheet
idea
is.
B
Yes,
I
mean-
and
let
me
do
this
quick
first,
two,
I've
sort
of
summarized
what
I
think
are
the
the
basic
different
options,
one
of
which
is
supplemental
style
sheets.
Some
people
have
proposed
adding
a
new
theme
and
I
think,
actually
nate
you.
B
B
But
there
are
one
or
two
people
who
have
sort
of
advocated
in
this
discussion
for
adding
a
new
theme
that
fixes
these
problems,
and
I
think
another
proposal
has
been
to
just
make
these
changes
and
like
again,
most
of
them
aren't
super
they're,
not
even
if
they
affect
some
people,
they're
not
going
to
affect
a
lot
of
people.
So
some
people
have
said
we
should
just
go
ahead
and
make
changes.
B
We
should
you
know
announce
it
tell
people
what
change
we're
making
and
then
let
them
deal
with
it,
and
I
guess
the
the
default
sort
of
answer
is
we
don't
do
anything?
The
supplemental
style
sheets
option
is
basically
that
we
create
sort
of
a
release
based
a
set
of
new
changes
to
css
that
is
identified
and
that
we
track
when
people
installed
their
backdrop
site
that
that
become
a
config
option
and
that
when
any,
if
anybody
look
creates
a
new
site,
we
basically
check.
I
don't
know
that.
B
Okay,
they
basically
that
we
only
we
add
these
supplemental
style
style
sheets
to
sites
that
have
been
created.
So
if
we
create
a
1.18
style,
supplemental
style
sheet,
it
only
gets
used
on
sites
that
were
created
in
version
1.18,
and
we
we
have
experimented
with
ideas
of
a
ui
where
the
in
the
ui
you
could
set,
which
version
you
wanted.
But
I
think
the
latest
proposal
is
that
we
don't
even
provide
a
ui
for
it.
It's
just
automatic.
B
So
if,
if
there's
a
1.18
supplemental
style
sheet
and
in
a
1.19
yeah,
basically
you
you
only
use
those
on
the
version
and
then
the
we've
got
a
pr
that
seems
to
work
and
do
that
and
it
some
people
have
complained
that
it's
complicated,
but
the
code
is
not
complicated.
A
Yeah,
that's
I
I
I
still
I'm
still
striving,
I'm
sure
everybody
is
for
some
elegant
technical
solution
to
this
problem.
It
just
like.
Usually
that's
the
way
things
eventually
work
out.
Sometimes
it
just
takes
a
brain
wave
to
get
there.
A
And
I
I
think,
maybe
first
we
can
look
at
the
the
things
that
we
don't
necessarily
like
about
this
solution
and
see
you
know,
discuss
like
how
could
we
possibly
eliminate
that
problem
that
we
don't
like
right,
and
I
think
I'm
just
taking
a
guess
here
that
perhaps
the
problem
with
that
suggestion
is
that
you
end
up
with
a
lot
of
style
sheets
that
are
just
like
this
version
of
stylesheet.
A
This
version,
you
know
1.18
1.19,
1.20
style
sheets
and
that
what
had
been-
and
it
could
be
even
worse-
that's
possibly
where
our
style
sheets
are
already
like,
componentized
and
so
potentially,
like
one
release
of
backdrop,
might
result
in
four
additional
style
sheets,
one
for
each
component
or
something
like
that.
That
got
a
new
additional
change
in
the
latest
minor
release.
B
I
don't
know
if
that's
the
primary
concern,
it's
been,
probably
the
common
one.
I
think
that
jen
and
I
have
argued
that
we
don't
see
that
happening,
but
there
is
no
guarantee.
So
I
understand
why
people
are
afraid
of
that.
B
I
think
some
it's
just
sort
of
speculation
that
there
could
be
a
lot
of
style
sheets,
we've
sort
of
proposed
that
you
know
there'd
be
sort
of
a
policy
that
I
mean
we
wouldn't
even
that
we
would
do
maximum
one
per
minor
release
and
we've
even
suggested
that
we
could
do
it
just
once
per
year,
just
sort
of
a
policy
decision
that
we
wouldn't
be
adding
these
style
sheets
willy-nilly
right.
B
We
could,
if
that,
if
the
concern
is
just
a
plethora
of
of
style
sheets,
that
there
are
ways
to
sort
of
control
that
through
discipline,
but
that's
not
a
technical
issue
right.
A
Yeah,
I
wonder
so
the
user
interface
for
like
selecting
additional
style
sheets
initially
like
even
just
saying
it,
I'm
kind
of
like
that
doesn't
sound
good.
I
I
could
see
like
we
have
a
reasonable
place
to
put
something
like
that.
It
would
probably
be
on
the
theme
specific
settings
page.
You
know
you
go
to
the
appearance
page
and
you
control.
A
But
what
I'm
trying
to
think
through
here
is,
I
wonder,
if
it's
possible
to
like,
instead
of
as
new
stuff
gets
added,
that
would
mean
new
additional
style
sheets
would
be
kind
of
permanent
until
backdrop
2.0.
You
know
that
all
the
118
or
119
style
sheets
you'd
be
adding
more
and
more
style
sheets
for
people
that
installed
the
backdrop
fresh
from
a
new
site,
and
I
don't
think
this
is
possible.
A
But
I'm
I'm
trying
to
make
this
technically
like
exploratory
like,
would
it
be
possible
to
have
backwards,
compatible
style
sheets
instead
of
adding
additional
ones?
A
So
if
you
install
backdrop
fresh,
there's,
no
additional
style
sheets,
and
it's
only
when
a
new
release
comes
out
that
there's
like
here's,
the
backwards
compatibility
for
118.,
here's
the
backwards,
compatibility
for
119.,
so
you're,
adding
additional
stylesheets
for
backwards
compatibility,
not
to
get
the
latest
version,
and
so,
if
you
wanted
to
as
a
user,
you
could
say
just
fast
forward
me
to
the
version
that
has
no
supplemental
style
sheets
and
all
the
backwards
compatibility
ones
are
just
not
added,
and
that
way
the
out-of-box
behavior
isn't
to
have
a
whole
bunch,
more
style
sheets.
A
It's
to
have
fewer,
and
if
you're
updating
your
site,
you
get
supplemental
ones
to
maintain
the
compatibility
that
would
that
seems
like
that
could
possibly
work.
Then,
as
a
more
aggressive
person,
you
could
also
potentially
say
just
always
use
the
latest
and
never
bother
with
the
supplemental
ones,
because
me
as
an
end
user,
I
haven't
sub
themes.
I
haven't
done
any
customization
or
work
arounds.
I
just
want
whatever
course
providing
to
be
the
latest
and
if
that
changes
the
way
my
site
looks
I'm
okay
with
that.
A
So
that
would
just
make
it
so
that
all
of
the
modifications
we
made
to
core
files
would
just
always
be
in
place.
However,
I
can't
figure
out
how
that
would
work
like,
because
you
can't
have
backwards,
compatible
style
sheets
that
provide
additional
rules.
What
you
need
is
rules
not
to
exist
at
all,
and
so
you
need
to
like
take
out
the
rules
from
the
old
sheet
and
I
don't
think
css
is
capable
of
doing
that.
Right.
C
So
back
in
august,
where,
when
I
was
on
leave,
I
had
a
little
bit
of
thought
of
that.
So
I
started
thinking
about
different
solutions
and
considering
the
the
things
that
people
proposed
in
the
issue
in
the
queue
so
sorry
for
the
brain
art
now
and
excuse
my
language
I'll.
Try
to
recall
what
I
thought
there
first
thing
is
that
the
goal
here
is
that
we
don't
load
the
code
for
new
installations
and
the
the
idea
is
that
new
installations
should
have
the
fix.
C
So
in
the
case
of
the
the
hero
blocks,
the
right
the
the
right
thing
to
do
is
to
fix
the
problem
right
now.
The
concern
is
that
how
do
how
we
won't
break
the
existing
sites
for
people
that
already
built
with
the
previous
problem
and
have
accounted
for
that
right
right
and
then
I
started
thinking
of
of
existing
features
or
ways
that
backdrop
works
inherited
from
trouble.
That
would
help
us
with
that
right.
One
of
them
is
sub
things,
which
is
a
cleaner
way
than
according
to
me.
C
Well,
that's
a
personal
opinion.
You
can
argue
right.
The
other
way
that
I
was
thinking
about
it
is
that
we
usually
like
bw
panda
mentioned
something
about
overlays
and
dialogues
last
week.
So
this
brought
to
mind
the
thing
that
if
we
want
to
remove
a
feature
from
core
that
comes
from
the
birth
of
backdrop,
from
d7
right,
we've
removed
certain
modules
and
what
we've
done
is
we
moved
those
into
contrib
retaining
the
names,
so
people
can
install
them
and
I
already
checked-
and
we
have
a
project
called
basis-
underscore
contrib
in
contrib.
C
So
I
thought
that
maybe
we
could
create
a
basis
being
in
country,
but
I
know
that
it
would
have
conflicts,
but
in
theory
it
should
be
able
to
be
installed
right
and
maybe
with
each
release.
If
we
break
things,
we
also
create
a
release
for
that
contrib
module
and
we
already
have
the
project
installer,
which
automatically
does
things
so
we
can.
C
But
the
other
idea
was
that
maybe
when
we
do
the
update
we
copy
the
existing
basis
theme
into,
we
ask
people
to
copy
it
into
the
contrib
basis.
Sorry
con
to
the
theme
folder
so
that
they
keep
the
existing
basis
thing.
Yeah.
A
C
Contrib
contrib
country
takes
precedence
of
the
core,
so
but
our
instructions,
our
installation
instructions,
say
rename
the
core
folder
and
add
the
new
folder
like
extract
the
new
core
folder.
So
now
our
instructions
need
to
say,
like
there's
a
lot
of
manual
things
that
need
to
happen
and
we
need
to
account
for
the
manual
installation
versus
the
the
the
automatic
installation
that
we
have
in
core
anyway.
So
these
are
raw
ideas
and
I
hope
I
didn't
confuse
people.
C
There
were
many
ideas,
but
there's
other
solutions.
I
haven't
fleshed
everything
out
because,
as
I
said,
I
hit
I've
hit
roadblocks
it's
time
that
I
was
thinking
about
things
but
see
how
we
have
some
screenshots
in
the
issue
team,
where
we
have
a
drop
down
that
people
select
the
styles
into
supplemental.
This
resembles
a
lot
like
the
project
installer.
If
there's
many
versions
of
the
country
project,
people
can
select,
which
version
they
want.
So
we
already
have
a
mechanism
in
place
that
we
can
reuse
anyway.
C
A
You're
you're,
suggesting
gregory
of
you
know
changing
the
instructions
to
like
you
know
copy.
The
entire
theme
gave
me
an
idea
that
I
don't
think
anyone
will
like,
but
I
I.
A
It
out
there
that
what,
if
like
to
solve
this
problem
of
like
oh
we're,
going
to
break
people's
existing
sites
and
break
existing
sites
is
all
based
upon
the
premise
that
they
have
sub
themed
or
add
additional
css
on
top
of
basis.
A
What,
if
we
take
that
away?
What
if
there
is
no
sub
theming
of
core
themes
like
if
the
premise
of
the
problem
is,
is
that
core
can't
make
fixes
or
changes
to
its
themes
because
of
the
potential
of
sub
theming
like?
If
you
want
to
sub
theme,
something
it
has
to
be
in
your
themes,
directory
the
stuff?
That's
in
core
can't
be
sub
themed
like.
A
If,
if
it's
in
contrib,
then
it
can,
and
then
that
enforces
a
new
behavior
where,
if
you
want
to
make
money
minor
changes
on
top
of
basis,
you
can
sub
them
it
if
you
copy
it
into
the
contrib
directory
first
or
if
you
want
to
just
copy
it
and
then
just
hack
on
it.
That's
also
a
sanctioned,
valid
approach
to
doing
stuff
and
it
would
just
change
the
paradigm
around
what
basis
was
originally
created
for
because
it
was
literally
called
basis
because
it's
made
to
be
a
base
theme.
A
But
we
could
solve
the
problem
of
core
can't
make
changes,
at
least
for
the
theme.
I'm
not
really
sure
about
all
of
the
modules,
because
you
could
still
have
all
of
the
problems
of
as
a
module,
I'm
providing
some
theme
stuff
and
then,
as
a
theme.
I'm
making
assumptions
about
that.
But
that
seems
less
frequently
a
problem
than
like
basis
making
changes.
And
we
would
just
want
to
fix
some
problems
and
basis.
And
we
can't.
C
So
people
people
in
gov
cms
land,
where
I'm
a
support
agent,
have
concluded
to
that
same
sort
of
like
solution.
They
used
to
provide
a
static
kit,
ui
kit,
where
people
would
sub
theme
it
and
it
would
come
with
the
distributions,
but
for
a
different
reason.
They
actually
wanted
to
stop
supporting
it
and
they
said,
look
we're
removing
it.
It's
not
going
to
be
in
the
distribution
anymore.
C
If
your
theme
is
based
on
that,
here's
a
ripple,
take
a
copy
of
it,
put
it
in
your
folder
and
then
it
would
still
work,
but
we
don't
maintain
it
anymore.
So
this
is
not
the
case
for
us
and
basis,
but
it's
a
similar
conclusion
to
or
solution.
I
should
say
to
what
you
just
proposed,
that
if
you
want
to
sub-theme
it
and
its
core,
you
know
that
we
will
be
changing
it
so
that
future
sites
are
fixed
properly
right,
and
that
is
all
good.
C
B
Want
to
interject
here,
though,
that
I,
my
own
personal
use
or
concern
about
this
most
people,
think
this
is
about
breaking
sub
themed
sites
and
for
me,
that's
not
the
case
for
me.
I'm
much
less
concerned
about
people
who
are
sub
theming
bases
one,
because
I
think
they
have
the
technical
skill
to
fix
these
problems.
If
they
do
come
up
two,
I
think,
if
you've
something
basis,
it's
likely
that
your
override
is
going
to
override
whatever
we
do
in
court
anyways
or
at
least
it's
possible.
So
it's
less
likely
to
be
a
problem.
B
I
spend
a
lot
of
time
trying
to
figure
out
ways
that
I
can
take
back
backdrop
out
of
the
box
and
make
it
look
good
without
doing
any
sub
theming
without
adding
contrib
themes
right,
and
I
would
like
for
basis
to
be
very
flexible
and
useful
to
somebody
who
isn't
doing
a
sub
theme,
and
my
fear
is
that
somebody
who,
for
example,
that
wants
to
do
this
two
hero
blocks
next
to
each
other.
They
can't
do
that
right
now
without
a
sub
theme
I
mean
they
can.
B
You
know
by
adding
extra
spaces
or
or
putting
their
text
closer
to
the
margin,
to
compensate
for
the
fact
that
there's
space
there
that
shouldn't
be-
or
you
know,
those
kinds
of
hacks
and
that
if
we
update
basis
it's
going
to
affect
their
site,
even
though
they
have
no
sub
theme
or-
and
they
you
know
so
now,
they've
got
to
go
through
and
like
figure
out
a
half
to
fix
what
we,
but
that,
maybe
that's
just
the
wrong
use
case
right.
B
B
I
would
like
recommend
that
if
you're
trying
to
just
create
an
out
of
the
box
configuration
and
you're
doing
a
lot
of
customizations,
don't
you
know
basis
is
better
for
sub
theming,
don't
use
it
for
that
kind
of
stability
go
to
contrib
and
I
have
like
been
making
all
of
these
changes.
I
want
to
make
to
the
tattoo
theme.
Other
people
can
as
well.
We
could
use
you
know
we
could
go
ahead
and
update
the
basis
concrete
theme
you
know
for
those
people.
B
So
that's
one
solution,
I
kind
of
don't
like
it,
but
it's
a
valid.
It's
a
valid
idea
to
say
that
you
know
basis.
Just
isn't
going
to
be
that
stable
out
of
the
box.
A
C
So
so
the
thing
is,
these
ideas
are
seemed
like
more
clean
from
a
code,
a
maintenance
perspective,
and
I
know
that
there
is
a
way
to
do
it.
My
problem
was
that
how
do
we
automate
that
for
the
people
that,
like
don't
care
about
the
specifics,
people
that
are
so
problem,
one?
Is
that
no
problem
fact
one
is
that
we
need
to
fix
broken
things.
As
you
said
in
core,
it
is
actually
a
broken
thing.
We
need
to
fix
it.
No
one
disagrees
on
that.
We
we
know
what
the
solution
is.
C
C
As
you
said,
there's
people
that
are
knowledgeable
enough
and
they
know
how
to
fix
it,
but
there's
those
that
don't
or
it
could
be
a
site
owner
who
has
learned
enough
to
update
the
site,
but
does
not
he
needs
to
or
not
he.
They
need
to
engage
a
developer
partner
which
costs
money
right
so
and
this
is
why
people
choose
backdrop
right
stability
and-
and
this
is
what
we
claim
in
our
principles
that
we
value
right.
So
I
don't
expect
us
to
find
a
solution
today.
C
It's
good
that
we
sort
of
like
rehashed
the
the
possible
solutions,
but
I
think
we
should
like
some
of
these
are
really
like.
Some
of
these
ideas
have
really
good
prospects
and
we
should
try
to
see
like
to
solve
it
in
a
way
that
is
both
elegant
and
less
and
painless
for
end
users,
that's
what
I
was
saying
so:
yeah
yeah.
Sorry.
It
needs
a
little
bit
of
time
and
thought
we
should.
We
should
not
rush
into
a
solution,
but
you
know
think
a
little
bit
more.
B
About
it,
this
is
this
has
been
useful
and
I
have
heard
some
interesting
some
ideas
that
give
me
things
to
think
about
I'd
like
to
spend
people
running
out
of
time
already
to
talk
about
how
to
unstuck
this
issue
or
or
what's
what's
our
policy
for
now
right,
because
so
my
fear
is.
B
Another
issue
came
up
well
the
issue
of
of
of
providing
a
break
point
for
menus.
There's
a
pull
request
for
this
problem.
It's
not
a
hundred
percent
clear
to
me
that
this
pi
that
the
p,
the
pr
for
that
pull
request
involves
adding.
If
you
know
you,
you
can
create
a
custom
setting
for
the
break
point
for
a
menu,
and
if
you
do
that
it
adds
some
css.
B
It's
not
clear
to
me
that
that
that
issue
should
be
tied
into
this
issue,
because
I
think
that
issue
is
kind
of
you
know
it's
self-contained
and
it
doesn't
have
backward
compatibility
problems,
but
immediately
somebody
raised
the
point
that
maybe
it
does,
and
we
can't
really
solve
that
problem
until
we
solve
this
one-
and
I
don't
know
if
that
should
be
true
or
not
yet,
but
I'm
afraid
yeah.
So
it
is
it,
it
is.
B
Other
other
issues
are
going
to
keep
getting
muddled
with
this
one,
whether
or
not
they
should
be,
especially
as
long
as
there's
no
policy
right.
If
we
don't
so
that
was
one
of
my
concerns,
and
so
the
question
is
like:
what
do
we
say
in
the
meantime?
You
know
it.
You
know.
Maybe
we
just
have
to
hash
through
that
other
issue
and
determine
that.
B
Should
it
really
be
connected
this
one
or
not,
and
maybe
you
know
and
do
that
work-
that's
fine,
but
I'm
afraid
it's
going
to
keep
coming
up
like
if,
as
long
as
this
is
so
ambiguous,
one
of
my
thoughts
was
well
this.
So
one
of
my
thoughts
was
maybe
we
weren't
as
far
away
from
a
consensus
on
supplemental
style
sheets,
as
I
thought,
but
but
this
conversation
reinforced
to
me
the
opposition
to
this
idea
of
supplemental.
B
B
I
was
going
to
propose
that
we
first
of
all
just
put
that
we
list
several,
what
the
current
options
are
and
we
sort
of
give
everybody
a
chance
to
like
rank
them
or
say
you
know,
with
with
one
option
being
you
know
like
do
nothing
to
get
a
better
sense
like
of
whether
or
not
how
close
we
are
to
some
sort
of
a
consensus
and
not
to
call
that
binding
right,
but
but
just
to
give
everybody
a
chance
to
write
to
not
because
too
many
people
have
said.
B
I
don't
like
this
solution
without
saying
how
they
would
solve
it,
and
so
what
I
guess,
what
I'm
proposing
is
that
we
say:
hey
we're
thinking
about
sending
this
to
the
pmc,
but
before
we
do
that,
we
want
to
give
everybody
a
chance
to
sort
of
come
down
definitively
and
on
where
they're
at,
because
maybe
we
don't
need
to
send
it
to
the
pmc.
Maybe
push
come
to
shove.
We
can
get
behind
a
common
solution.
It's
just.
We
haven't
asked
people
to
do
that.
Yet
that
was
once.
B
However,
this
conversation
has
reminded
me
that,
like
if
we
tried
to
do
that
today,
there
might
be
solutions
that
we
haven't
thought
of
yet,
and
it
might
you
know
the
two
of
you
might
have
things
in
your.
You
know
that
you're
still
muddling
in
your
brain
so
that
that
might
be
a
better
solution
and
I
don't
want
to
prematurely.
C
So
the
thing
so
I
agree,
but
two
things.
What
most
people
vote
for
is
not
necessarily
going
to
be
the
best
solution
and
there's
the
the
dilemma
thereof.
It's
these
are
three
actual
problems,
the
one
with
the
alignment
of
the
images,
the
one
with
the
hero
blocks
and
the
one
with
the
menu
breakpoints.
So
these
are
the
the
three
that
came
to
mind
that
are
all
related
to
that.
We
need
to
fix
them.
We
need
to
fix
them
properly
but,
as
I
said.
B
Right,
I
don't
think
there's
even
consensus,
though,
that
we
need
to
fix
them,
as
I
said,
I
think,
there's
at
least
one
person
in
the
issue
queue
who's
actively
saying,
and
I
think
a
little
bit
of
it
comes
down
to
how
you
view
the
purpose
of
basis.
I
think
some
people
view
it
as
a
simple
theme:
that's
there
to
something
right
and
and
sub
themers
can
fix
all
these
problems
on
their
own.
We
don't
need
to
right.
B
B
How
what
is
our
intended
use
of
basis
I
have
an
intended
use,
which
is,
I
believe,
basis,
should
be
a
flexible
tool
for
a
beginner
site
builder
to
create
a
an
attractive
theme
without
having
to
something
or
without
having
to
go
to
contrib,
because
the
thing
is,
it's
like
a
lot
of
people
might
say:
well,
why
not
just
do
this
and
contrib
and
I'm
like
we're
95
of
the
way
there
in
core?
Why
should
we
push
somebody
to
contrib
for
something
that
we're
so
close
to
being
able
to
do
in
core
right?
C
Yes,
and
I
think
from
memory
I
can
recall-
I
think
at
least
olaf
and
another
person
from
europe
that
have
mentioned
that
they
are
basically
something
places
all
the
time,
that's
what
how
they
built
their
sites.
So,
as
I
said
again,
you
have
groups
of
people
that
are,
as
you
said,
some
people
are
using
it.
Some
people
don't
care
about
it
and
they
just
create
their
custom
things.
So
my
my
main
goal
is
how
to
disturb
the
the
general
community
a
little
bit
less.
C
I
mean
people
like
olaf,
sort
of
like
they're,
the
the
what
you
call
it,
the
faithful
followers
of
bachelor
they're
not
going
to
be
upset,
and
they
will
know
how
to
solve
their
problems.
But
still
I
don't
want
to
upset
the
the
broader
community.
If
that's
what
they're
doing
right,
if
they're
submitted,
if
they're,
actually
something.
B
C
To
sum
it
up,
as
I
said,
it's
like
we're
not
objecting
again,
we
all
think
that
these
things
should
be
solved.
We
don't
diminish
the
importance
of
coming
up
with
either
a
policy
or
a
solution
for
that.
It's
just
that.
I
wouldn't
want
us
to
rush
into
things.
C
Maybe
if
it
was
an
initiative,
people
would
push
more.
I
don't
know
it's
like,
I'm
not
sure,
and
it
comes
down
to
time
and
you
know
figuring
out
the
the
golden
solution,
as
I
would
say,
but
yeah.
I
agree
that
we
should
give
people
the
the
what
you
call
it
allow
allow
them
either
time
or
I
don't
know
to
express
the
pros
and
cons
because
yeah,
it's
a
it's
a
hard.
It's
a
hard
thing
see
even
even
late.
Now
is
just
thinking
about
things
how
to
solve
that.
A
More
options:
yeah,
yes,
see
yeah
yeah
like
do
you
want
to
hear
another
one.
A
So
another
one
is
that
using
contrib
we
could
make
revive
the
basis
project
and
make
a
new
version
of
basis
at
every
single
minor
release,
beta
basis,
118
basis,
119
basis
120,
and
they
would
just
be
locked
copies
of
basis.
At
that
version
of
backdrop,.
A
If
you
used
core
basis,
it
would
always
just
be
the
latest
basis,
and
if
you
wanted
to
lock
into
stability,
you
could
download
the
contrib
version
that
was
locked
into
your
current
release
whatever,
and
that
would
make
it
so
that,
basically
it
I
mean
we
could
maybe
promote
it.
Somehow
saying
this
is
an
alternative,
but
also
if
somebody
retroactively
was
like,
I
updated
to
120
and
it
broke
my
site
because
of
changes
in
basis.
They
would
have
an
immediate
course
of
action
of
downloading
the
contrib
version
of
119
and
that
would
fix
their
site.
C
C
C
B
So
my
final
thoughts
on
this
for
today
I
think,
are
I
I'm
interested
in
some
of
these
solutions.
However,
I'm
skeptical
that
any
of
them
are
going
to
suddenly
build
a
consensus,
yeah,
and
so
I'm
still
my
question
in
my
head-
is:
how
do
we?
How
do
we
ever
come
to
a
decision
on
this?
You
know
how
do
we
decide
at
what
point
to
like
push
it
to
the
pmc
or
at
what
point
to
have
a
you
know
to
do
kind
of
a
vote
even
if
it's
non-binding
but
anyways.
B
So
it's
like
how
do
we
come
up
with
some
sort
of
at
least
a
policy
or
a
statement
about
where
this
issue
is
going?
That
will
make
life
easier
for
us.
So
again,
let's
not
try
to
answer
that
right
now,.
A
Okay,
well,
let's,
let's
maybe
leave
it
actually
at
that
we're
at
one
o'clock,
which
is
time
for
one
o'clock
pacific
time
for
the
next
meeting,
which
is
the
dev
meeting.
Are
you
guys,
okay,
with
leaving
this
discussion.
C
A
Yep,
okay,
anything
else.
You
guys
want
to
talk
about
or
mention
before
we
end
okay.
Well,
then,
thank
you,
everybody
out
there
on
the
internet
for
watching.
We
really
appreciate
you
guys
views
and
do
let
us
know
if
you
have
additional
thoughts
based
on
this
conversation.
What
is
the
issue
number
for
this
css
overrides
issue
just
for.