►
From YouTube: Backdrop Design & UX - August 27th 2020
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).
B
All
right
today
is
thursday
august
27th.
This
is
our
weekly
or
actually
fortnightly,
meeting
on
design
and
usability
issues
before
we
get
to
things
in
the
agenda,
let's
just
go
around
and
do
a
quick
set
of
introductions
tim.
Let's
start
with
you,.
C
Hi,
I'm
tim
st
paul
tim
from
coming
from
deerwood
minnesota,
I'm
still
reluctant
to
say
from,
I
still
feel
like
I'm
from
minneapolis-st
paul,
but
but
I'm
up
in
deerwood
in
this
green
tent
and
here
to
talk
about
some
usability
issues
that
we
want
to
get
into
the
next
release
in
two
weeks
just
over
two
weeks.
B
A
Hi,
I'm
greg
I'm
joining
from
great
story
about
the
dog
barking
outside
I'm
joining
us
every
week,
just
to
see
how
I
can
help
with
design
and
everything
related
to
bachelor
joseph.
E
B
Yep
I'm
jen
lampton
calling
from
oakland
california
and
I'm
excited
about
all
of
the
issues
gregory
and
tim
about
at
the
agenda
today.
First
section
of
the
agenda
is
the
theme
initiative
update.
I
don't
know
luke
if
you
want
to
say
anything
at
this
time.
D
It
hasn't
moved
in
a
couple
of
weeks.
I
I've
been
busy
with
my
new
day
job,
so
feeling
feeling
the
pressure
that
I
get
something
done
so
the
moment
it's
stall
like
it's,
it's
actually
kind
of
generally
installed.
I
I
need
to
figure
out
a
way
to
start
it
up
again.
B
Okay,
there
are
three
issues
that
we
have
on
our
agenda
specifically
related
to
the
theme
initiative.
It
doesn't
look
like
there's
been
any
progress
on
any
of
them
recently.
B
Does
anyone
know
if
we
actually
have
an
issue
created
in
the
backdrop
semester
or
queue
for
some
solution
for
previewing
themes,
or
have
we
talked
about
that
so
far?
Only
in
meetings
I
couldn't
find
the
link,
we
don't
know,
okay,
we'll
look
for
it
if
it
doesn't
exist,
we'll
make
one
well.
C
I'll
remind
you,
we
also
set
up
an
issue
to
call
like
a
demo
issue
queue,
that's
separate
for
that's
for
this
project
and-
and
I
created
a
couple
issues
there
that
I
haven't
looked
at
in
weeks,
but.
B
Okay,
if
you
could,
could
you
find
a
link
to
that
issue
queue
and
just
throw
it
into
this
agenda
yeah
so
that
we
can
follow
up
on
those
weekly
as
needed?
B
B
I
haven't
done
anything
on
these,
I'm
going
to
check
and
see
if
anyone
else
has
been
working
on
them
lately,
nope,
so
that
one
has
a
lot
of
moving
parts.
We
know
about
next
one
move
the
clear
log
messages
button
to
the
bottom
of
the
db
log
page.
That
issue
has
more
than
100
comments
on
it.
People
feel
very
strongly
about
it.
B
B
That
would
be
a
good
idea.
I
also
think
we
have,
I
think
we
talked
about
it
in
the
pmcq
about
how
the
project
management
committee
could
help
issues
so
that
they
don't
have
to
go
on
for
100
comments,
and
I
think
the
process
we
decided
is
that
at
some
point
someone
should
ask.
Does
anyone
here
want
this
escalated
to
the
pmc
for
a
decision?
And
if
the
answer
is
yes,
then
we
open
a
pmc
issue
saying?
Can
we
please
help
this?
B
I
think
asking
a
designer
would
be
great
if
we
have
anyone
in
the
community
that
wants
to
weigh
in
on
that,
but
I
think
that
might
also
like.
Sometimes
we
ask
a
designer
and
then
they
give
us
another
option
like
we
hadn't
considered
and
it's
hard.
So
I
think
maybe
it
would.
B
To
escalate
that
and
be
like,
let's
just
get
a
decision
do
something
close
this
issue
and
then,
if
we
have
more
stuff,
we
want
to
do
later
open
another
issue
and
at
least
just
try
and
make
some
progress
on
it,
so
that
we
aren't
kind
of
spinning
our
wheels.
I
think
that
spinning
the
wheels
thing
can
cause
burnout
so
gregory,
I
don't
know
if
you
want
to
be
the
one
to
ask
if
that
should
be
escalated,
but
that
might
be
helpful.
A
Yeah,
I
probably
can
add
a
comment
there.
Okay,.
C
B
I
think
that's
fine,
I
think
in
that
case
I
rolled
the
most
recent
pr
and
I
don't
really
have
any
strong
feelings
on
it,
but
I,
if
especially,
if
it
is
one
person,
that's
been
like
continually
redoing
stuff
asking
them,
would
be
good
most
of
the
case.
When
that
happens,
it's
usually
like
doc,
wilma
or
bw
panda
or
something,
and
so
I
think
you
know
as
long
as
it's
one
of
the
people.
That's
no
like
not
going
to
be
offended,
then,
if.
B
C
B
In
the
minority
that
might
also
create
some
conflict,
I
don't
know,
I
think
it
would
just
be.
A
Jen,
yes,
I
see,
I
see
only
there's
three
ers
in
there
there's
an
old
one
by
opie,
one
by
me
and
then
one
that's
been
closed
by
indy
godzilla
and
that's
closed.
So
I
think
that
the
only
open
ones
currently
are
mine
and
all
these
do
you
have
another
one.
B
I
thought
I
just
saw
a
comment
in
there
that
said:
I'd
re-rolled
it,
but
maybe
not.
I
might
have
misread
it.
That's
fine
yeah!
So
if
you
want
to
specifically
adjust
the
people,
who've
created,
pull
requests
for
that
and
ask
them
if
they
wanted
to
escalate
it
to
them
pmc.
That
would
be
fine.
B
B
C
Do
is
this
one?
I
have
a
pull
request
already,
no
it,
but
no,
but
it
has
some
suggested
text
yeah.
Let's
talk
about
that.
One
really
quick,
because
a
good,
a
pull
request
is,
is
minutes
of
work,
and
but
I
opened
that
issue
right,
so
it.
I
guess.
If
I
put
this
on
the
agenda,
I
forgot
I
had,
which
is:
is
this
the
current
one
in
the
first
screenshot?
Or
is
that
my
suggestion?
C
Oh,
I
think
my
so
I
wanted
to
do
a
taxonomy
term
path
and
I
struggled
for
too
long.
I
should
have
figured
it
out
much
quicker
and
it
just
occurred
to
me
that
there's
like
three
or
four
really
commonly
used
paths
other
than
node
and
we've
got
some
ui
ideas
that
will
eliminate
this
problem
in
the
future.
But
in
the
meantime,
just
having
like
a
taxonomy
example-
and
I
think
I
put
a
com-
or
I
suggested
user
and
taxonomy
and
gregory
added
comment
as
well.
C
So
these
are
the
four
that
are
being
discussed
for
that
other
issue
as
well
yeah,
and
I
think
other
people
have
suggested
that
something
like
that
would
be
helpful
to
them
and
I
don't
think
we're
going
to
fix
the
other
ui
problem
in
the
next
few
weeks.
So
you
know,
does
it
make
sense
to
do
a
quick
help,
text
improvement.
A
I
also
remember
that
zen,
you
said
that
we
should
remove
the
word
wildcard
because
it
gets
confusing
with
for
people
for
the
percentage
thing
just
added.
F
B
C
Well,
it
sounds
to
me
like
at
least
both
of
you,
gregory
and
jan,
and
if
anybody
else
has
any
opinions
would
support,
even
a
temporary
quick
fix
to
the
this
help
text
and
you
both
made
some
suggestions.
So
why
don't
I
do
a
pr
that
incorporates
your
both
of
your
comments
and
and
then
hopefully
we
can
get
some
feedback
on
it.
It'll
be
easy
to
modify
and
fix
yeah.
A
Were
you
were
you
thinking
to
put
the
the
examples
just
in
a
single
row
of
help
text
or
mention
them
on
like
a
list?
I
hadn't
thought
it
through
that
far.
Do
you
have
a
preference,
okay.
A
B
C
So
in
general
I
mean
this
that
like
how
much
if
three
or
four
of
us,
if
nobody
objects,
if
I
do
a
pull
request
and
nobody
objects-
is
that
kind
of
enough
unanimity
or
do
we
need
to
get
more
people
to
comment
on
this.
B
I
think
that's
probably
enough,
because
a
core
committer
will
come
and
comment
on
it
too.
It's.
B
B
General
with
most
changes
in
backdrop,
it's
better
to
make
them
and
then
make
more,
rather
than
like
try
and
hold
something
up
for
more
feedback.
Only
when
like,
if
there
are
people
who
don't
agree,
then
it's
good
to
get
more
feedback
if
you've
got
like
three
people
are
like
looks
good,
then
I
think
it's
probably
fine.
A
A
Okay
yeah,
it
may
seem
that
some
people
are
of
the
opinion
that
you
shouldn't
move
to
a
pr
until
we
have
the
acceptance
criteria
or
whatever
specified,
but
I'm
with
the
opinion
that
file
two
or
three
separate
pull
requests.
People
can
play
and
choose
and
then
we'll
pause,
the
relevant
ones.
A
C
Yes
do
should
I
explain
that
one
quick,
do
you
understand
it.
C
Right
so
the
thing
is,
I
mean,
I
think
it's
a
different
bug
and
it's
a
different
issue
is
that
by
default
backdrop
always
shows
comment,
titles,
regardless
of
whether
this
checkbox
is
checked
or
not.
So
to
me
this
is
really
misleading.
What
what
this
really
means
is
allow
the
user
to
set
a
custom
comment
title.
So
if
this
is
not
checked,
then
backdrop
just
makes
up
its
own
comment
title.
If
this
is
checked,
the
user
has
the
option
to
change
it.
C
But
there's
going
to
be
a
comment
title,
no
matter
what
you
can't
prevent
that
which
I
think
is
a
bug,
because
it's
really
stupid
to
have
a
one-line
comment
that
basically
gets
repeated
twice.
You
know
as
a
title
and
a
comment
and
I'm
sure
you
can
hack
the
templates.
You
know
easily
to
fix
that,
but
through
the
ui
you
can't,
as
far
as
I
can
tell
so
that's
a
different
issue
which
probably
won't
get
solved
in
the
next
week.
But
in
the
meantime
we
could
at
least
just
clarify
this
button.
B
There's
a
question
there
about
like:
if
the
bug
is
that
the
comment
title
is
shown
when
it
shouldn't
be,
then
this
label
is
fine,
but
if
the
question
is
like
do
you
want
to
customize
the
title
and
then
this
label
is
wrong.
So
I
think
we
need
to
decide
like
what
we
want
backdrop
to
do
before
we
can
decide
what
the
label
of
the
action
should
be
so
like.
B
A
How
does
it
work
on
in
drupal
7,
or
is
that
checkbox
missing
completely
there.
A
C
You
know
what
it
does
say:
indigo
azalea
I'm
trying
to
get
that
right,
put
a
comment
and
she
said
alan
males
originally
reported
this
and
in
the
gazelle
looked
and
it
says
interesting
question
the
setting
allow
comment.
Title
really
only
handles
the
ability
to
set
subjects
manually.
It's
not
meant
to
handle
the
display.
So
apparently
the
code
is
not
set
up
to
you
know
to
to
really
hide
titles.
C
C
D
B
B
You
know
we'll
have
an
opportunity
to
be
like
this
will
hide
the
display
of
your
comment
title
or
it
could
be
like
a
hidden
setting
somewhere
that,
like
new
installs
get
it
not,
you
know
the
way
we
want
it
and
all
the
cells
get
it
the
way
it
is
now.
A
Yeah
and
hiding
it
sounds
like
a.
We
have
a
common
display
on
its
node,
so
it
sounds
more
like
a
place
for
that
part
of
the
ui
the
admin
ui,
whereas
this
checkbox
now
resides
on
the
content
type
settings,
so
I
think,
and
the
rest
of
the
settings
there
are
allow
users
to
do
that.
Allow
users
to
do
that
or
hide
it
or
force
the
user
to
do
that.
Basically,.
C
Well,
I
opened
another
issue
for
allow
admin
to
hide
the
title
and
comments
and
I
think
what
we're
talking
about
now
goes
into
that
issue
and
yeah,
and
we
should
deal
with
that
later.
But
for
now
so
I'll
do
you
know-
and
I
I
just
suggested
instead
of
allow
comment.
Title
allow
custom
comment
title.
Actually.
I
think
lml
suggested
that
and
I'll
do
a
pull
request
with
that
in
mind,
and
if
anybody
has
an
improvement
on
it,
then
that's
fine.
We
can
make
it
better,
but.
B
Nice,
okay,
so
that's
all
of
our
usability
issues.
Unless
greg
you
have
a
handful,
you
want
to
throw
in.
A
I
always
have
just
let
me
just
randomly
go
through
the
pikachu,
so
one
that
was
recent
was
that
about.
I
think
I
mentioned
it
during
the
the
part
we
were
discussing
before
we
started
the
recording,
so
there's
there's
one
about
allowing
an
admin
label
on
all
blocks.
This
is
an
old
sort
of
like
plane.
That's
issue
number
four
double
five:
a.
C
Oh
yeah,
do
you
have?
I
think
this
is
this.
Is
the
one
that
that
document
just
did
the
pull
request
for
right,
yeah
yeah?
This
is
a,
I
think,
a
great
issue
to
fix
doc.
Willmott
did
a
a
really
quick
fix,
but
it
turns
out
it's
a
flawed
approach
and
I
you
know
it'd
be
nice
if
we
could
modify
it,
but
I
don't
know
how
complicated
that's
yeah
do
you
have
an
idea,
gregory
what
the
better
yeah.
A
Yeah,
so
so
it's
not
it's
not
a
flawed
approach.
It's
more
that
it
didn't
take
into
account
that
there's
for
a
specific
kind
of
blocks,
which
is
the
reusable
blocks.
We
already
have
an
administrative
title,
so
if
we
were
adding
that
arbitrarily
to
old
box,
including
those
reusable
ones,
there
would
be
some
duplication
of
asking
people
to
do
a
similar
or
mostly
similar
thing.
A
C
A
So
there's
there's
depending
on
how
much
consistency
we
want
to
have,
because,
because
the
the
the
one
that
was
added
to
all
blocks
is
just
the
field
so
that,
at
the
end,
after
the
visibility
conditions,
which
is
just
fine
but
then
the
the
current
one
that
we
have
the
reusable
blocks
is
just
below.
I
think
the
content-
I
can't
remember,
I
think,
just
before
the
after
the
content,
the
rich
text
editor
and
it
gets
disabled
once
you
enable
it
as
it,
you
cannot
remove
it.
You
cannot
reset
it.
A
So
there's
an
easy
fix.
You
can
check
if
the
block
is
a
reasonable
block
and
then
don't
render
that
field
set
at
all
and
don't
save
another
time,
but
I
haven't
actually
worked
on
it.
So
yeah
it
shouldn't
be
extremely
odd,
but
yeah.
C
A
B
A
That
makes
sense,
so
my
my
proposal
there
is
for
consideration
is
that
a
field
set
maybe
at
the
very
end,
is
it's
maybe
too
much,
because
the
the
only
thing
that
the
field
said-
and
you
pointed
it
out
as
well-
that
it's
a
field
set
and
it
has
the
same
field
title
and
then
the
same
label
for
the
single
text
field
that
is
there.
So
views
handles
that
in
a
nice
way.
Just
below
that
I
have
a
screenshot
there.
A
What
it
does
is
you
give
a
view
a
name,
and
then
you
have
an
option
for
picking
a
box,
a
text
box
which
says
description,
and
that
reveals
another
text
box
which
you
can
add
where
you
can
add
a
thing.
So
this
this
also
solves
another
pet
peeve
of
mine,
because,
with
the
current
design
we
say
defaults
to
the
block,
title
is
left
blank.
I
don't
like
how
this
is
a
drupalism
and
I
would
like
us
to
get
rid
of
all
these
things.
A
A
A
B
C
Yes,
basically,
it
was
more
complicated.
I've
simplified
it
to
simply
move
the
breadcrumbs
above
the
page
title
only
on
news
sites.
So
this
this
is.
It
basically
changes
the
the
the
base
of
the
standard
install
profile.
C
C
And
I
don't
know
that
any
this
is
again
one
of
those
this
seems
like
you
know,
I
don't
know
like
we'd,
want
a
certain
amount
of
people
to
agree
that
this
is
a
good
idea.
I
think
jason
might
be
the
only
one
who's
come
out
clearly
in
favor
of
this
jen
you've
like
yeah,
originally
sort
of
objected,
but
now
it
seems
like
you're
sort
of
in
the
you
know,
whatever
yeah.
C
B
I
also
don't
have
like
design
vision,
I'm
like
design
blind
and
so
for
me.
I
was
like
well.
Obviously
that
was
just
a
design
decision
that
was
made
and
there
are
people
who
don't
like
the
design
decision,
but
tim
has
cut
you're
like
no.
This
might
go
beyond
design.
This
is
like
now.
B
This
is
like
it's
weird,
rather
than
just
being
like
quirky
or
something,
and
I
have
no
opinion
on
whether
I
think
it's
weird
or
not,
because
I
can't
see
that
so
yeah
I
mean,
I
think
it's
fine
if
we
want
to
move
it
for
new
sites.
As
long
as
there
are
a
few
of
you
who
believe
that
it's
better
the
way
it
is
in
the
future,
rather
than
what
it
is
right
now
so.
C
C
I
think
it
was
this
issue.
Isn't
it
this
one
that
where
the
the
the
block
ids
the
block
ids
in
core
in
the
core
default
layout
are
hard
coded,
so
I
just
copied
and
used
hard-coded.
I
actually
had
to
create
a
new
block
and
I
just
hard-coded
a
a
layout
id
and
gregory
was
suggesting
that
we
should
randomly
generate
it,
and
I
don't
have
strong
opinions
about
this.
I
don't
know
if
there's
a
good
reason
to
do
that,
but
I
guess
I
don't
also
have
a
reason
not
to.
A
Yeah,
it
wasn't
a
concern,
so
much
was
nitpicking,
I
would
say,
but
yeah,
okay
well.
C
B
B
Okay,
generating
a
random
uuid,
what
was
it
before
was
it
always
that.
C
Well,
I
so
part
of
doing
this
was,
I
think
breadcrumbs
was
their
own
block,
but
the
title
was
the
automatically
generated
title
block,
so
I
had
to
create
a
title
block
and
and
for
creating
the
title
block.
I
think
I
just
sort
of
made
a
site
and
then
copied
the
uuid
from
that
and
hard-coded
it.
C
B
B
I
have
no
feelings
on
this.
I
think
like
it
maybe
gregory.
We
should
have
a
separate
issue.
That's
like
generate
random
unities
for
all
blocks
and
do
it
site-wide,
rather
than
just
doing
it
once
in
one
block
here,
okay
and
then
that
way,
we
can
have
like
core
developer
feedback
on,
whether
that
it's
better
to
do
that
or
to
have
a
common
one,
because
if
we
have
a
common
one,
if
we
need
to
make
a
change
to
a
block
at
least
we'll
know
if
they've
changed
it
or
not.
B
I
don't
know
if
that
matters,
but
maybe
they
have
feelings
on
it.
I
do
have
feelings
about
this
page
title
combo
block,
though
I
feel
like
we
shouldn't
be,
and
this
might
be
a
2.x
issued
him,
but
I
feel
like
we
should
not
be
placing
that
block
to
replace
things
that
are
in
the
templates.
B
The
right
solution-
and
we
can't
do
this
in
one.x-
is
to
move
the
things
where
we
want
them
in
the
templates
so
that
the
block
doesn't
have
to
exist
at
all.
So
I
have
a
little
concern
about
placing
a
block-
that's
like
kind
of
a
workaround
for
a
problem
with
our
templates,
but
I
don't
know.
Let
me
think
it
through
and
add
a
comment
because.
C
Well,
yeah,
I
thought
briefly
about
it.
I
you
know
again,
I
don't.
C
I
don't
see
a
problem
in
doing
it.
I
recognize
your
your
concern
again
we're
not
so
much
trying.
I
don't
see
it
as
we're
trying
to
fix
a
problem
in
core.
This
way
is
we're
just
providing
an
alternative
default
settings
because
you
know
the
expectation
is:
is
that
the
user
is
going
to
manually
change
these
settings
so
we're
just
sort
of
helping
them
out
and
doing
it
and
it's
it
really
doesn't
change
core
as
much
as
it
just
gives
them
some
some
alter.
You
know
a
different
set
of
defaults.
B
Yeah,
I
think
page
title
is
weird
page
title
tabs
and
that
only
two
messages
are
the
things
that
are
a
little
weird,
because
they
are
hard
both
hard
coded
in
the
template
file
and
we
provide
a
block,
and
so
I
feel
like-
and
this
might
also
just
because
I
have
so
much
experience
with
like
theme
system
and
drupal
and
backdrop
that,
like
using
a
block
to
fix
the
theme
system,
bug
feels
weird
to
me,
and
I
might
not
feel
this
way
after
I
talk
it
all
the
way
through
right.
B
B
That
might
be
another
problem
we
need
to
fix.
Could
we
but
yeah
same
with
messages
like
you
couldn't
like
not
print
validation,
messages
on
a
form
by
removing
the
block
on
that
page?
So
there's
like
stuff
that
you
can't
not
have,
and
so
the
reason
it's
in
the
template
is
because
it
needs
to
always
appear,
and
then
the
block
does
this
crazy
thing
where
it's
like?
If
the
block
is
in
the
render
pipeline,
then
like
hide
the
other
render
stuff.
B
A
So
we
have
another
about
10
minutes,
there's
a
few
issues
that
I
would
like
to
bring
up.
Maybe
we
could
don't
have
the
time
to
discuss
every
single
one
of
them,
but
maybe
bring
the
attention
that
needs
feedback.
C
B
I
think
so
this
might
be
something
where
have
we
had
a
core
developer?
Look
at
it,
yet
it
would
be
good
to
get
a
core
committer
to
do
a
code
review
and
get
their
feedback,
because
I
think
that
might
also
color
the
opinions
of
other
people
who
are
thinking
that
it's
too
complicated
if
a
core
developer
comes
in
and
says:
oh,
no,
it's
fine,
then
maybe
they're
like
oh
okay,
never
mind
has
bw
panda
looked
at
it
since
we.
A
B
B
B
I
don't
know
if
they
still
feel
that
I
don't
know
if
they've
looked
at
the
pull
request
or
not,
and
then
there
was,
if
we
do
decide
to
do,
that
is
do
we
let
people
opt
in
or
out
and
then
from
a
core
developer
like
dx
perspective,
there's
also
the
way
that
I
did
that
was
by
setting
the
default
like
install
version
like
at
what
point?
Did
you
install
backdrop
which
I
thought
might
be
useful
to
have
anyway,
but
then
I
used
that
to
do
the
conditional
setting
of
the
style.
B
D
A
We
could
we
could
avoid
having
something
in
the
ui,
but
still
have
a
setting
for
it
and
then
allow
people,
because
now
we
have
overrides
setting
of
rides
in
settings.
Php
allow
at
least
developers
or
people
with
advanced
knowledge.
Some
means
for
people
to
just
override.
B
B
C
C
B
Yeah,
so
I
would
see
if,
if
bw
panda
hasn't
had
a
chance
to
look
at
both
recent
pull
requests,
he
would
be
the
first
person
because
he's
already
looked
at
it
he's
a
core
committer
and
he
had
strong
feelings
against
it
and
maybe
if
he
sees
some
code,
his
appeal
feelings
might
change
and
then
maybe
we
get
someone
else
to
look
at
it
from
a
complexity
standpoint
to
another
court
committer
and
see
what
we
think
we
can
ping
doc,
willmott
or
someone
else
who's
been
on
the
issue.
A
Yep
I
have,
I
have
a
few
issues
like
four
of
them.
Let's
or
five,
let's
get
them.
I
want
to
get
an
easy
one
out
of
the
way
yeah
it's
four
five,
six
two,
which
is
renamed
locale
module
to
interface
translation.
I
don't
think
that
locale
as
a
as
a
word,
makes
sense
to
non-english.
Speakers
like
it
seems
odd,
and
the
description
of
that
module
is
that
it
translates
the
built-in
user
interface.
So
d8
has
changed
that
to
interface
translation,
and
I
think
that
we
should
change
that
as
well.
A
B
B
I
think,
as
long
as
the
machine
name
doesn't
change,
I
am
in
favor
of
making
things
make
more
sense
from
the
ui.
We
might
get
pushed
back
on
core
developers
about
there
being
a
mismatch
there,
but
yeah
we'll
see.
A
A
Exactly
I
was
about
to
say
that
I
hate
the
fact
that
the
permissions
page
is
a
strong
word.
The
permission
page
says
node
still,
instead
of
content,
which
I
didn't
buy
module.
Yes,.
A
But
it's
the
next
one,
let's
decide
about
this
one
all
right!
I
have
another
one,
that's
short,
but
I'm
not
sure
if
we're
gonna
be
able
to
discuss
it,
maybe
I'll
just
mention
them
quickly.
All
these
issues
have
needs
more
feedback.
So
it's
just
a
call
for
people
to
just
chime
in
it's
two
one,
eight
five,
it's
a
an
issue
that
you
started
back
in
2016
and
it's
about
export
import
and
their
order
in
the
ui.
A
A
B
A
Then
the
other
thing
that
needs
more
feedback
is
four
five.
Seven,
five.
A
Which
is
the
available
updates
page
that
gets
too
noisy,
so
we
we
had
an
issue
that
has
been
merged
and
that's
to
sort
the
modules
and
things
so
that
the
ones
that
have
security
updates
and
updates
bubble
up
on
top
of
the
the
ones
that
do
not
have
any
updates
that
they
are
up
to
date
and
then
indie
gosella
mentioned
that
had
a
good
point
there,
that
and
others.
A
Why
should
we
include
the
ones
that
are
up
to
date
in
that
page
and
obviously
that
they
prefer
that,
and
then
we
have
a
separate
issue
about
adding
a
filter
on
that
page
which
would
serve
both
these
opinions
and
people
could
switch
to
whatever
they
like
and
then
someone
so
I
I
was
about.
I
was
halfway
to
typing
and
commenting
and
saying
technically.
A
Hi
and
then
what
I
was
about
to
say
was
that
just
bear
with
me.
I
lost
my
trainer
yeah
that
the
page
is
called
available
updates
so
technically
people
that
don't
want
to
see
the
up-to-date
things
they
have
like
a
valid
argument
there,
and
then
we
have
those
issues
that
where
the
update
modules
page
includes
horror
and
so
does
the
update
themes
and
update
layouts.
So
we
have
an
issue
about
merging
all
those
things
into
a
single
page.
A
If
there
was
a
page
that
was
called
available
updates,
that's
what
I
would
expect
to
see.
I
would
expect
to
see
a
list
of
all
the
updates
that
I
have
my
checkbooks
to
check
them
and
then
update
my
site.
If
I
was
to
rename
this
page,
I
would
call
it
components,
update
status
or
something
because
that's
what
it
does
it.
It
shows
you
all
the
status
of
all
modules
or
projects,
but
yeah.
A
I'll
I'll
I'll
finish
that
comment
that
I
have
halfway
so
that
I
have
all
my
thoughts
there
and
I
I
would
like
more
people
to
comment
on
it.
B
Okay,
I
love
the
idea
of
putting
a
filter
on
here.
Yes,
I
don't
know
if
any
of
our
other
reports
have
filters,
but
this
one's
a
little
different
and
I
would
also
like,
can
you
cross-link
the
other
issues
about.
B
The
pages
and
stuff
because
I
think
it
would
be
good
to
think
about
this
holistically
from
the
perspective
of
like
what
are
we
gonna,
do
with
all
of
the
mess
on
the
modules
section
in
the
theme
section,
the
layout
section
as
well
as
this
page,
because
if
this
page
remains
a
report
and
we
end
up,
I
think
you
had
a
recommendation
to
actually
create
a
new
menu
item
called
like
updates.
And
that's
where.
B
A
Yeah,
so
in
the
in
the
comments
that
I
have
written,
that's
what
I'm
saying
but
then
at
the
end
I
conclude
with,
but
if
you
have
two
pages
that
bother
them
list
modules
and
both
of
them
list
their
date
status,
one
of
them
doesn't
lead,
doesn't
include
the
updated,
but
it
offers
checkboxes
for
you
to
actually
update.
Then
why
not
merge
all
that
into
a
single
page.
B
D
B
There
are
kind
of
different
level
tasks
and
I
think
also
like,
what's
on
the
page,
is
going
to
be
determined
by
what
it's
intended
for,
because
if
it
is
a
report,
you
do
want
to
see
everything,
and
if
it's
a
page
that
just
helps
you
update,
you
don't
want
to
see
everything,
and
I
think
that
the
problem
we're
having
right
now
is
that
this
page
does
both.
And
so
that's
why
you
get
people
with
both
opinions,
trying
to
figure
out
like
what
is
this
page
for
what
should
it
do?
B
So
maybe
we
end
up
with
one
page
with
filters
and
permissions
and
buttons,
or
maybe
we
end
up
with
two
pages,
one
that
remains
in
reports
and
one
that
remains
active,
but
I
definitely
think
right
now.
We
have
four
pages.
A
And
and
three
of
them
show
core
updates
as
well,
which
doesn't
make
sense,
because
they're
titled
yeah,
whatever
yeah,
really
quickly.
I
would
like
to
mention
another
two
issues.
Just
I
want
to
feedback
on
those
one
is
includes
a
pull
request
that
I
filed
it's
issue
31.222,
it's
again
an
issue
that
you
have
started
back
in
may
2018
jen,
and
this
is
about
separating
the
help
text
for
publishing
options.
A
So
we
have
a
huge
piece
of
text
at
the
end
of
three
radio
options,
I
filed
the
pull
request.
I
haven't
said
that
to
needs
code
review
or
needs
testing
yet,
because
maybe
I
should
because
I
need
more
feedback
like
I
have
updated.
It.
A
A
A
Should
have
that
yeah
we
should
have
that
nesting
thing
that
we
talked
about
multiple
times,
how
c
tools
used
to
nest
things
and
intend
them
a
bit.
So
there
was
more
yeah
anyways,
but
until
that's
that
that's
done
yeah.
Maybe
that's
a
good
compromise
anyway.
There's
a
lot
of
things.
I
need
feedback
on
and
then
I
can
get
that
okay
and
then.
Finally,
then
final
issue,
somewhere
related,
is
4563
again
about
help
text
and
radio
options
and
yeah.
B
So
this
is
for
the
page
title
block.
Yes,
okay,
clean
up
options.
A
B
A
B
A
B
How
it
works,
maybe
not
best.
A
B
So
there's
a
couple
things
we
could
do
like
if,
if
we
just
decided
the
text
was
wrong.
What
we
could
do
is
like
when
you
saved
this
block,
we
could
change
it
back
to
default.
Page
title
like
if
you
hit
save
without
a
value
in
there,
so
that
the
ui
would
then
be
a
little
bit
clearer
or
if
we
wanted
to
change
the
behavior,
that's
a
little
bit
more
complicated.
B
I
also
think
that
is
a
little
trickier
when
you
have
existing
sites,
because
you
don't
want
to
you
know
them
to
have
assumed
it
would
work
one
way
and
then
all
of
their
default
page
titles
disappear
and
become
blank
or
something.
But
if
we
did
decide,
we
wanted
to
be
no
title.
Then,
when
you
saved
this
block,
we
could
have
it
set
the
no
title
value
instead
of
the
custom
page
title
value
so
yeah,
but
then
we
could
remove
the
text
because
the
interface
would
become
more
accurate,
yep.
B
So
yeah
interesting,
okay!
Yes,
thanks.
B
Do
we
have
conditional
required
nope.
A
No
so
states,
if
you,
if
you
place
this,
the
required
attribute
to
a
form
element
via
states
all
it
does,
it
adds
the
asterisk.
It
doesn't
add
validation.
So
you
you
add
that
conditionally
and
then
you
do
custom
form,
validation,
handler
validation,.
B
Okay,
interesting:
okay,
do
you
have
other
issues.