►
From YouTube: Backdrop Weekly - July 30, 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).
A
Out
there
it
is
july
30th
2020-
and
this
is
the
weekly
backdrop
developer
meeting,
where
we
talk
about
the
current
issues
that
are
in
backdrop
from
a
developer
perspective
yeah,
and
we
highlight
issues
that
are
currently
being
active
and
working
on
worked
on.
A
So,
let's
see
first
off,
let's
start
with
some
introductions.
I'll
start,
my
name
is
nate
lampton,
I'm
a
core
committer
for
backdrop
and
I'm
coming
from
oakland
california
greg.
Can
you
introduce
yourself.
B
Yep
greg
I'm
joining
from
grace,
try
to
attend
every
weekly
meeting
to
see
how
I
can
help
you.
C
A
Let's
see
normally
of
updates
from
the
pmc
here,
I'm
going
to
bring
up
something,
that's
not
in
the
agenda
written
at
least,
and
that's
that
we're
currently
working
on
renewing
our
trademark,
which
is
pretty
exciting.
We
are
pursuing
using
the
software
freedom
conservancy.
One
of
the
services
they
provide
is
stewardship
of
trademarks
and
right
now,
the
trademark
of
backdrop.
A
Cms
is
held
by
myself
and
jen
and
we're
working
on
transitioning
that
into
the
software
freedom
conservancy,
as
basically
like
the
holding
organization
for
the
trademark,
and
it's
not
like
giving
away
our
trademark
to
like
some
other
entity.
It's
making
it
so
that
we
have
a
an
organization
that
can
provide
continuity
for
holding
the
trademark.
A
So
that's
an
interesting
thing.
We
have
a
whole
year,
at
least
to
get
that
renewed.
The
united
states
trademark
law
says
that
you
have
to
renew
in
between
the
fifth
and
sixth
year
of
having
acquired
a
trademark,
and
so
it's
been
about
five
years
ago,
since
we
got
the
trademark,
so
we
have
at
least
a
whole
another
year
to
get
that
all
sorted
out.
But
it's
an
interesting
thing.
I'm
excited
to
see
us
expand
the
use
of
the
software
freedom
conservancy
and
get
more
connected
with
the
organization
there.
C
A
C
B
A
Also
funny
the
way
the
trademarks
work
is
that
renewing
a
trademark
all
that
you
are
transferring
a
trademark.
All
that
is
really
involved
is,
as
the
current
holder,
you
just
don't
protest
if
someone
else
files
the
same
trademark,
which
is
slightly
dangerous,
because
that
means
anybody
anytime,
could
file
a
trademark
for
the
same
thing.
And
if
you
don't
contest
it,
then
you'll
lose
your
trademark
to
whoever
filed
it,
and
so.
A
A
So
we
get
a
fair
amount
of
junk
mail.
Regarding
that,
okay,
let's
see
so
in
the
world
of
contrib
projects,
we
have
some
new
releases
that
came
out
in
the
past
week,
replicate
ui
out
of
stock
notification,
use
conditional,
h5p
and
editable
views
all
had
new
releases
within
the
past
seven
days,
a
big
thank
you
to
module
maintainers
and
contributed
authors
that
are
regularly
updating
and
working
on
those
contrib
modules.
A
I
don't
have
anything
for
website
related
updates
in
the
agenda,
so
I'll
skip
over
that
and
proceed
into
the
product.
Update
so
backdrop,
116
is
our
current
release
and
we
have
a
number
of
bug
fixes
that
are
pending
and
getting
queued
up
here
for
correction.
A
One
issue
that
I
keep
bringing
up
that
really
needs
some
attention
that
hasn't
gotten
any
yet
is
the
views
or
visual
regression
on
the
text.
Format
order
form
it's
issue
4407,
and
we
have
had
a
regression
in
bachelor
116
ever
since
release
that
the
list
of
text
formats
on
that
interface
is
alphabetically
displayed,
instead
of
being
in
the
correct
order.
So
if
you
change
the
order
of
those
things
with
the
drag
and
drop
handles
and
then
save
it
looks
like
nothing
happened
because
they're
being
displayed
in
an
alphabetical
list,
it's
I'm
sure.
A
A
A
A
A
Because
of
a
really
minor
thing,
we
just
need
a
link
to
documentation
explaining
further,
like
in
the
status
report,
we're
telling
someone
you
should
have
a
higher
value,
but
then
we're
not
telling
them
how
to
change
that
or
why
they
should
change
it,
and
so
linking
to
off-site
online
documentation
is
something
that
still
needs
to
be
done.
So
I
think
that
that
probably
means
we
have
to
write
the
documentation
page,
I'm
guessing
that's
the
big
hold
up
there.
B
A
Let's
see
next
up
is
reviewing
the
block
title
for
the
search
box
block,
so
the
search
block
right
now
has
a
title
that
says:
search
on
it
and
then
there's
a
label
in
front
of
the
search
field
that
says
search,
and
so
you
get
a
lot
of
the
word
search
being
repeated.
A
The
issue
3476
just
makes
it
so
that
the
title
is
hidden
by
default.
For
that
search
block,
the
pull
request
has
been
filed
for
quite
some
time.
It
just
needs
some
eyeballs
on
it.
It's
currently
marked
needs
review.
A
15
views
has
some
strange
behavior
when
oring
together
filters,
and
that
has
a
pull
request
that
is
currently
marked
needs
review.
So
I
think
that
all
this
really
needs
is
usability
testing
to
check
to
see
reproduce
the
problem,
as
it's
described
in
the
issue
and
then
see
if
the
patch
correctly
fixes
it-
and
you
can
do
that
from
the
sandbox.
B
Yeah
from
memory,
I
think
that
there
was
a
respective
issue
in
drupal
and
this
was
not
working
as
expected
at
some
point,
but
then
the
fix
that
they
introduced
for
drama
was
also
committed
for
backdrop
and
then
now
this
works
yeah.
It
needs
a
little
bit
more
testing
than
just
yeah
to
confirm
everything.
So
this
method.
A
Okay,
another
another
one
that
was
an
easy
one
to
fix
is
that
ck
editor
was
not
respecting
the
language
of
the
site.
So
if
you
had
your
site
in
german,
for
example,
the
cq
editor
button
toolbar
should
also
be
using
german
words
for
the
hover
text
when
you
hover
over
each
one
of
the
buttons-
and
that
was
not
working.
The
issue
is
44.92,
but
that
one
was
merged
in
the
past
week,
so
it
has
now
been
fixed.
A
Let's
see,
also
related
user
register
is
not
translated.
I'm
not
quite
sure
what
this
is.
Oh
literally,
this
this,
the
the
title
for
the
user
registration
page
like
create
a
new
account,
is
not
translated.
Currently
because
it's
missing
a
t,
the
t,
the
t
function,
wrapping
around
the
title.
It
looks
like
I
haven't
seen
that
one,
but
that
one
is
also
marked
rtvc.
It's
issue
44.93.
A
A
Provides
syntax
highlighting
when
you're
looking
at
a
file
in
the
web
interface,
but
it
only
does
automatically
for
php
files
or
js
files
or
x
files
that
have
known
extensions
backdrop,
has
a
number
of
files
that
are
php
files
that
aren't
dot
php
files
like
dot
module
files
or
dot
install
files
and
a
recent
feature
enhancement
on
github,
was
that
you
can
now
create
a
do.
You
guys
know
what
the
name
of
the
file
is
that
makes
this
possible
yeah.
A
Yeah,
so
I'm
just
adding
a
get
attributes
file
makes
it
so
you
can
associate
an
extension
with
a
particular
coding
language,
so
this
makes
it
so
the
dot
modules.install.test.profile
files
within
the
backdrop
repository
get
identified
as
php
files.
So
that's
that's
great!
That's
crazy!
That's
also
marked
rtbc.
B
Before
we
go
just
related,
I'm
not
sure
if
I
created
an
issue
for
it
or
not
moving
the
readme
file
out
of
the
core
issue:
sorry,
the
core
folder,
so
that
github
picks
it
up
and
shows
it
in
the
sidebar
the
license
plate.
I
mean!
Oh
yes,
yes,
the
license,
so
I
thought
that
they
said
is
that.
A
Right
yeah,
but
we
moved
the
read
or
the
license
file
into
the
core
directory
when
we
were
removing
a
bunch
of
other
files
that
aren't
particularly
valuable,
but
now
that
github,
specifically
parses
for
license
files.
We
should
move
our
license
file
to
the
root
so
that
we
get
aggregated
with
other
gpl
software.
A
All
right
is
it
okay,
if
I
continue,
though
yep
sure
sure,
okay,
so
we've
got
another
really
simple
issue
that
everywhere
we
have
path
autocompletes
whenever
you're
making
a
link,
for
example
like
for
a
menu
item,
we
have
a
path
matching
that
auto
completes
for
particular
items,
and
this
issue
number
4478
makes
that
path,
checking
less
strict.
A
So
you
can
start
you
can
type
a
title
of
a
node
or
something,
and
it
will
match
on
the
string
that
you've
typed
anywhere
within
that
node's
title,
rather
than
you
needing
to
start
at
exactly
the
beginning
of
the
node's
title.
So
4478
is
that
issue
gregory,
and
I
have
been
talking
back
and
forth
in
that
issue
about
whether
or
not
that
should
be
a
setting
about
how
strict
the
matching
should
be.
My
current
opinion
on
that
is
that
we
should
just
go
with
the
looser
matching
and
see
what
kind
of
feedback
we
get.
A
And
then,
if
we
get
feedback
saying
that
this
needs
to
be
like
adjustable
the
level
of
strictness
on
the
path
matching,
then
we
can
make
it
a
setting
at
a
later
time.
A
Okay,
next
up
this
one
that
I
didn't
have
time
to
review
before
the
meeting,
but
tim
and
gregory
both
have
taken
a
look
at
it's
issue:
1259
ck
editor,
not
saving
when
it's
in
source
mode
tim.
Could
you
give
us
the
update.
C
Yeah,
so
right
off
the
bat.
We
ought
to
update
that
title
because
we
were
expecting
quickly.
The
the
bug
was
that,
when
creating
a
custom
block,
if
you
switched
to
source
mode-
and
you
made
a
change
and
then
save
the
node,
you
would
lose
that
change
unless
you
first
switched
back
out
of
source
mode
and
we
thought
that
was
a
ck
editor
bug.
But
at
the
last
meeting
it
was
hypothesized
that
maybe
the
problem,
because
if
you
create
a
block
that
well
I
don't
know
if
we
knew
this
at
the
time.
C
But
we've
since
confirmed
that
if
you
create
a
block
using
the
custom
blocks
page
where
it
doesn't
use
a
dialog
that
the
problem
doesn't
exist
and
it
does
so
it.
When
you
make
a
custom
block,
it
opens
a
dialog
and
and
that's
where
the
whole
process
is
taking
place.
And
in
that
case
this
problem
does
exist
and
the
additional
test
that
jen
had
suggested
was
trying
to
edit
a
text
block
on
the
header
of
a
view.
Because
it's
the
same
thing
that
uses.
C
That
uses
a
a
dialog
and
in
fact
the
problem
was
there
as
well.
So
it's
not
specific
to
blocks
it's
also
there
anyways
so
we've.
I
guess
I've
redefined
the
issue
now
to
just
you
know,
to
to
be
not
seeking
editor
specific,
but
being
that
when,
when
editing
with
ck
editor
in
a
well,
I
don't
even
know
is:
if
that's
is
that
switching
to
source
mode?
Is
that
part
of
ck
editor?
C
So
when
we're
using
that
in
a
dialogue
you
have,
you
have
to
switch
back
in
order
to
not
lose
your
thing.
So
what
I
would
I
think,
the
next
week
we
verified
that
the
next
step
is.
This
doesn't
feel
this
doesn't
feel
like
something
I
can
solve
myself,
but
I
would
like
to
help
provide
some
direction
and
I'm
hoping
either
nate
or
gregory
might
have
an
idea
that
I
can
put
in
the
issue
saying
here's
what
we
need
to
do
next
in
terms
of
debugging
and
or
coming
up
with
a
fix
for
this
any
ideas.
A
A
I
think
it's
called
dialog.ajax.js
that
deals
with
when
you're
submitting
a
dialogue
with
ajax,
that's
how
the
form
gets
processed
and
the
problem
is
likely
in
that
file
probably
around
when
it's
dealing
with
the
click
handler
on
the
submit
button,
and
so
my
my
theory
is
that
we
have
jquery
is
currently
acting
on
behalf
of
the
user
to
click.
A
The
real
submit
button
within
the
form
that
the
submit
button
within
the
dialog
is
is
actually
just
a
like
a
copy
like
it's
like
a
placeholder
that
when
you
click
on
that
javascript
clicks
on
the
real
button,
and
I
think
that
we
need
to
try
different
approaches
to
submitting
the
form
with
javascript
doing
different
things.
A
I
think
that
it
might
be
doing
something
like
trying
a
mouse
down
event
or
a
click
event,
and
we
might
need
to
try
other
javascript
events
to
see
which
one
actually
works
correctly
with
with
ck
editor,
okay
or
or
it's
possible
that
right
now
we're
telling
it
to
mouse
down.
But
maybe
we
should
be
telling
it
mouse
down
and
follow
with
click.
You
can
tell
to
do
multiple
events
like
in
a
row
and
that
might
be,
but
what
is
necessary.
C
A
A
Okay,
so
that's
an
interesting
one.
If
you
guys
don't
mind,
I'm
gonna
totally
take.
B
A
Down
a
little
side
track
here
into
a
wishlist
feature
that
I
don't
think
that
we've
discussed
before,
and
that
is
that
when
we
save
formatted
text
areas
right
now
we
save
the
the
markup
and
we
save
the
format.
A
A
I
would
like
to
throw
out
there
conceptually
that
perhaps
we
should
start
storing
an
additional
property
there
about
whether
or
not
that
was
saved
in
source
mode
or
not.
So
it
would
be
an
additional
column
in
the
database.
That
says
this
format
was
used.
A
This
is
the
markup
and
was
source
mode
enabled
at
the
time
that
it
was
saved
so
that
when
you
go
back
and
edit
that
piece
of
content,
it
could
toggle
source
mode
and
use
ck
editor
still,
so
that
you
want,
if
you
have
pieces
of
content,
that
you
want
to
have
the
text
format
of
ck
editor
and
all
of
the
controlling
rules
of
c
can
editor.
But
you
always
edit
that
piece
of
content
in
its
html
source
for
some
reason,
probably
for
a
level
of
control.
You
don't
have
to
make
a
new
text
format.
C
C
I
don't
need
source
mode
because
I'm
not
doing
anything
but
on
a
particular
page
I
I've
found
the
need
to
switch
into
source
mode
because
I'm
adding
a,
I
don't
know
an
iframe
or
something,
and
then,
when
I
save
that
next
time
I
come
back,
it's
going
to
remember
that
I
saved
that
in
source
mode
and
it
will
default
to
source
mode.
Then
yeah
like
when
I
go
to
edit
it.
So
I
don't
know
if
this
is
your
use
case.
C
I
lose
my
my
changes
and
I
think
that's
that
might
be
because
I
don't
have
my
filters
set
up
properly
or
whatever,
but
I
I
feel
like
this
would
make
that
less
likely,
because
right
if
it's
like,
if
I
added
that
iframe
in
source
mode
and
saved
it,
it
would
bring
me
back
to
source
mode.
B
A
One
thing
you
can
have
you
can
run
into
a
problem
with
multiple
text.
Formats,
though,
is
that
sometimes
a
second
user
has
different
permissions
than
the
first
one,
and
so
when
they
change
the
text
format
to
something
different.
The
original
author
might
go
in
and
try
to
edit
that
piece
of
content
and
they
don't
have
access
to
the
text,
format
that
it
was
changed
to
and
then
they
can't.
B
B
A
A
But
where
this
is
coming
from
is
that
wordpress
or
frequent
comparison,
software
doesn't
have
the
concept
of
text
formats
where
there's
like
different
levels
of
permission,
but
it
does
have
the
concept
of
rich
text
versus
like
plain
text,
editing
and
it
it
also.
It
does
remember
which
way
a
piece
of
content
was
saved.
A
B
A
But
it
could
also
cause
some
weirdness
again
with
that
two-person
editorial
situation,
whereas
the
original
person
might
have
edited
it
with
rich
text
mode.
The
second
person
might
have
switched
it
to
html
mode
because
they
find
it
more
intuitive
or
whatever,
because
they're
a
more
advanced
editor
and
then
the
first
person
comes
back
and
edits
their
content
again
and
now
it's
in
source
mode
and
they
would
be
like
whoa,
what's
going
on
here,
you
know,
but
maybe
they
would
just
click
the
button
again.
I
don't
know
I.
B
Think
I
think
we
had
we
had
a
similar.
I
remember
a
similar
thing
about
field
sets
collapsible
field
sets
and
whether,
like
some
people,
find
that
it's
a
trivial
task
and
by
default
they're
collapsed,
but
some
others
have
it
as
a
primary
action
for
some
sort.
A
A
That
counts
yeah
per
per
piece
of
content
wherever
it's
saved.
My
my
situation
is
that
there
are
certain
pieces
of
content
that
are
complex
and
very
long
and
using
seek
editor,
isn't
suitable
for
them,
but
I
don't
want
to
set
up
a
different
text
format
just
for
them,
because
I
want
the
permissions
to
be
the
same
as
seek
editors
text
format.
A
All
right:
well,
maybe
that's
one
of
these
things
that
needs
to
be
experienced
in
order
to
really
evaluate.
B
Yeah
well,
as
as
I
said,
we
are
sort
of
like
experiencing
getting
vid.org,
where
we
have
multiple
people,
contributing
to
the
articles
that
we
publish
like
user
guides
and
so
on,
and
the
solution
that
we
resorted
to
there
is
the
text
filter
one,
but
that's
it
under
the
assumption
that
everyone
that
has
access
to
edit
content
of
b.org
actually
has
access
to
those
text
formats.
A
Okay,
well
thanks
for
a
little
sidebar
there.
Next
up,
we
have
two
social
justice
related
issues.
Removing
blacklist
and
whitelist
from
core
is
issue
4441,
and
that
issue
currently
needs
review.
There's
a
poor
request
up
there.
It
does
have
some
impact
and
I
think
that
that's
why
it
needs
review
it's
kind
of
a
long
pull
request.
A
I
did
see.
I
think
this
past
week
that
linus
torvalds
has
has
also
committed
to
removing
these
terms
from
both
the
linux
kernel
and
from
the
git
software.
So
that's
very
exciting.
Just
I
think
that
I
think
this
is
a
trend.
That's
really
going
to
stick
like
you
know.
This
has
been
part
of
software
terminology
since
we've
had
software,
and
I
I
think
that,
finally,
some
recognition
of
some
harmful
terminology
is
finally
making
some
inroads
here
and
that
this
might
be
a
permanent
change
culturally.
Within
the
software
development
world.
B
Yeah
it
takes
a
few
generations,
it's
like.
We
now
look
at
movies
or
look
in
the
history
and
say:
oh
people
were
silly
back.
Then
they
were
burning
people
because
they
thought
they
were
witches
at
some
point.
I
think
that
their
kids
or
grandkids
would
say.
Oh
these
guys
were
silly.
They
were
smoking
or
whatever
and
one
one
of
those
things,
those
silly
things
that
we
did
would
be
using
those
words
it
doesn't
seem.
B
It
seems
that
to
to
most
of
us
that
are
socially
just,
it
seems
that
these
words
are
innocent
because
we've
gotten
used
to
using
them
and
so
many
years
but
yeah.
I
think
this
is
a
move
to
the
right
direction.
A
So
next
issue
we've
got
up
is
very
similar
to
that
one.
It's
removing
all
master
and
slave
terminal
terminology
from
core
it's
issue.
4451.
A
most
of
this
was
already
removed
from
core
a
long
time
ago
regarding
database
configuration
that
we
have
primary
secondary
instead
of
master
and
slave,
and
most
of
the
changes
in
this
issue
are
updating
documentation
that
still
mentions
the
older
terminology
or
uses
as
examples
and
stuff
like
that.
So
4451
has
already
been
marked.
Rtbc,
so
that'll
be
great.
I
think
we'll
probably
get
that
in
shortly.
B
All
right
before
you
move
on,
I
just
found
the
issue
about
moving
the
license.
File
is
44.85
and
I
smack
it
there
and,
as
I
say,
there's
nothing
to
test
or
review
just
moves
the
file
and
just
file
the
request,
real
quick.
Even
if
you
don't
want
to
commit
it,
and
you
want
to
sort
of
like
wait
for
what
is
the
timing?
B
A
Yep
making
a
comment
now,
so
thanks
thanks
that
poor
christmas
file
lesson
nine
minutes
ago,
well
done,
and
we
can
mark
this
as
a
milestone
and
give
it
pr
great
all
right.
A
Let's
see
we'll
move
on
down
to
running
out
of
time
here,
move
on
down
to
117
117
is
the
next
minor
release
of
backdrop.
That's
where
we
add
new
features
and
functionality,
we're
quickly
approaching
august,
which
is
our
kind
of
last
month
of
feature
development
before
feature
freeze
that
won't
be
happening
on
september
1st.
A
So
we
don't
have
a
whole
lot
of
things
that
are
in
the
117
milestone.
Currently,
one
big
feature
that
could
use
some
eyeballs
is
doc.
One
month's
work
on
adding
support
for
custom
contexts.
It's
issue
3750.
A
custom
contexts
make
it
so
that
we
add
or
restore
functionality
to
layout
module
so
that
you
can,
instead
of
having
a
context,
automatically
defined
for
you
when
you're
at
like
node
percent,
you
could
make
a
context
appear
out
of
thin
air
by
specifying
a
particular
node
from
which
you
want
to
pull
fields
for
example
and
then
place
blocks
from
that
node
place
fields
from
that
node
as
blocks
on
a
particular
layout.
So
3750,
I'm
excited
to
see
this
one.
When
I
get
a
chance
out,
I
will
takes
some
time
to
review
it.
A
It
currently
needs
eyeballs,
just
in
general.
I
think
that's.
C
Gonna
say
from
my
perspective,
what
it
really
needs
is
somebody
who
understands
it
to
to
create
some
better
description
of
what
it
does
or
use
cases,
because
a
few
of
us
are
really
like
sort
of
understand
it,
but
keep
getting
stuck,
and
we
just
need
better
use
cases.
So
if
anybody,
if
anybody
out
there
can
do
that,
please
it
would
be
so
helpful.
B
So
what
I've
done
is
I've
tried
a
span
of
a
follow-up
ticket
which
serves
as
a
collection
of
definitions
or
examples,
and
I'm
trying
to
put
some
documentation
together,
but
even
for
that,
I
would
like
eyes
on
people
just
to
re,
read
what
they
wrote
either
on
our
forum,
sorry,
on
our
chat
or
in
various
places,
and
just
confirm
the
terminology
being
used
so
that
it's
not
confusing.
B
A
Yeah
conceptually
it's
it's
a
complicated
thing.
Fortunately,
it
doesn't
impose
too
much
visual
weight
to
a
normal
user
using
that
part
of
the
site,
so
it's
definitely
targeted
more
towards
power,
user
or
site
builder
of
substantial
savviness.
A
It
does
make
me
think,
though,
the
complexity
with
which
or
the
difficulty
with
which
people
have
been
having
reviewing
this
functionality,
that
the
documentation
is
going
to
be
pretty
key
and
even
describing
it
verbally
has
not
worked
out
very
well
that
we
may
need
to
have
some
like
video
tutorial
or
something
like
that
to
actually
truly
demonstrate
what
this
thing
is
actually
doing.
C
But
I'm
you
know
like
adding
this
option.
The
layouts
ui
is
already
complex
and
a
little
bit
confusing
right
and
there's
a
part
of
me.
You
know
that
says
adding
like
you
could
say.
Let's
just
add
this
feature
and
worry
about
documentation
elsewhere
and
stuff
in
other
places,
but
in
terms
of
the
whole
backdrop
philosophy,
if
we're
adding
an
option
which
just
isn't
going
to
make
sense
to
most
users.
C
Is
that
a
problem
right
because
we're
trying
to
make
it
something
easy
to
use?
And
to
me
it's
like
if
I
open
that
up-
and
I
see
this
thing
context-
and
I
just
can't
wrap
my
head
around
it-
is
that
a
step
forward
or
a
step
backwards,
even
if
it
works
right,
even
if
it
works
for
those
who
understand
it,
even
even.
B
Describing
it
just
doesn't
cut
it.
I
think
that
the
agreement
was
that
we'll
add
some
people
are
good
at
learning
by
example.
So
we
said
that
the
documentation
would
include
two
or
three
real
world
examples,
so
that
would
help
people
get
it,
and
the
help
text
added
just
below
this
ui
element
would
have
a
brief
description
and
then
point
to
the
documentation
for
more
because
it
like
would
overwhelm
the
ui
with
so
much
documentation
like
it's
is.
B
Well,
as
nate
said,
it's
not
that
we're
imposing
it
right,
it's
a
feature
that
you
can
use,
and
I
know
that
a
question
that
I
wanted
to
ask
because
nate
described
it
as
in,
instead
of
so
when
you
were
describing
it
earlier
nate,
you
said,
instead
of
having
the
context
automatically
being
picked
up,
you
now
can
sort
of
like
make
the
context
magically
appear.
It's
not
instead,
it's
on
top
of
so
we
still
have
the
ability
to
automatically
detect
the
context.
B
C
Nobody
cannot
see
it
if
that
isn't
going
to
like
make
people
afraid
of
layouts,
because
they've
got
this
big
thing
there
that
they
don't
even
understand
right
and,
like
I
hear
us
having
discussions
all
the
time
saying
we
don't
want
to
do
that
right.
We
don't
want
to
scare
people
away
with
things.
They
don't
understand,
even
if
they
work
and
even
if
they're
not
hurting
anything
by
being
there,
then
maybe
I'm
wrong.
Maybe
we
do
that
all
the
time
I
don't
know,
I
don't
know.
C
B
When,
when
this
thing
was
first
introduced,
what
I
try
to
suggest
is
that,
if
there's
a
possible
way
to
it
seems
that
we're
introducing
a
developy
sort
of
like
thing
in
the
ui,
and
then
we
asked
people
to
guess
what
the
result
would
be,
or
let
me
rephrase
that
a
site
builder
would
have
something
in
mind
and
they
would
know
that
in
order
to
get
there,
they
would
need
to
add
the
proper
experienced
site.
Builders
know
how
to
do
that,
but
but
less
experienced
people
would
not
know
it.
So.
B
My
argument
back
then
was
that,
instead
of
having
that
workflow
of
knowing
somehow
what
you
need
and
then
adding
the
context
in
order
to
get
there,
why
not
reverse
that
and
ask
people?
What
do
you
want
to
do?
What's
the
end
result
and
then
generate
that
that
gets
too
complex?
It's
not
as
simple,
though
okay.
This
isn't
how
people.
A
Yeah,
we
have
a
different
issue
for
that.
That
approach
gregory.
I
think
right
that
that
we
wouldn't
show
people
anything
about
contexts
when
they're
setting
up
the
layout,
but
we
would
show
it
if
they
added
a
block
that
needed
a
context
that
didn't
exist.
A
Yes,
which
is
interesting
but
also
opens
up
all
kinds
of
different
problems,
and
it
also
makes
the
list
of
blocks
because
it
would
have
every
block
in
the
entire
system,
even
if
the
context
wasn't
available,
even
if
it
like
didn't
make
sense
to
apply
like
a
put
like
a
a
user's
profile
picture
on
a
node,
for
example,
because
it'd
be
like
where's
you.
Where
are
you
getting
the
profile
picture
from,
and
that
would
have
to
ask
you
where?
A
Would
you
guys
get
that
from
which
at
least
currently,
because
we
also
don't
have
relationships
right
now-
could
not
include
exactly
what
you
might
expect
like?
Oh,
I
can
put
a
profile
picture
on
there,
but
it's
always
going
to
be
exactly
of
user
id
number
10..
A
B
Okay,
yeah,
and
also
we
also
have
some
satellite
issues
around
that,
as
in
creating
layouts
from
a
content
type
which
will
apply
to
that
content
type
or
creating
a
layout
from
a
specific
node
which
will
automatically
figure
out
what
context
and
what
visibility
conditions
you
need.
But
these
are
follow-ups
all
and
I
don't
see
an
easy
way
to
simplify
that
part
of
the
ui.
That's
that's!
Okay,.
A
Yeah
and
for
existing
patterns,
like
backdrop
puts
itself
in
this
like
mid-market
space,
and
one
of
the
defining
features
of
backdrop
is
views,
for
example,
and
by
no.
A
It's
it's
that
trade-off
that
you
were
talking
about
of
like
this
is
powerful
enough,
that
the
complexity
is
worth
it
because
it's
necessary,
and
I
do
feel
that
this
is
one
of
those
areas
that
this
also
lays
groundwork
for
other
things,
like
the
relationships
that
I
was
just
talking
about
to
make
it
so
that
you
can
make
a
page
contain
pretty
much
anything
from
anywhere
starting
from
anything.
A
And
so
I
think,
as
we
as
we
get
more
towards
that
goal
like
there
will
be
some
additional
complexities,
but
the
layout
system
was
intended
to
have
those
complexities
built
into
it
eventually,
from
the
very
beginning,
considering
it
was
a
port
from
panels
from
drupal
7.,
and
so
this
is
in
a
way
taking
what
had
always
been
intended
and
in
some
places.
I
I
think
I've
said
before
that.
A
B
Yeah
I
was
about
to
mention
panels,
which
is
something
that
I
I
never
touched
in
d7.
So
it's
one
of
those
things
that
are
very
powerful
and
people
that
have
used
it
like,
cannot
live
without,
and
we
we
basically
with
layouts
with
a
layout
builder.
What
we've
done
is
we
introduced
a
simple
and
user-friendly
version
of
it
in
backdrop,
but
certain
aspects
of
it
will
sort
of
like
they
come
with
with
complexity
that
you
just
cannot
get
rid
of
it's
just
how
it
is.
A
We
do
have
that
in
places
honestly,
not
as
much
as
I
would
like,
like
four
views,
for
example,
would
be
really
excellent
if
we
could
have
more
off-site
online
documentation
that
showed
how
to
heck
to
actually
use
views
because
you
got
dropped
into
it
and
you
got
almost
nothing
as
far
as
help
is
concerned,
but
we
do
have
a
fair
amount
of
online
documentation
in
the
status
report,
which
is
funny.
A
We
just
mentioned
that
that
we
need
a
link
off
to
the
documentation
from
the
status
report,
because
a
lot
of
the
things
regarding
server
configuration
are
just
like
you
know.
That's
not
really.
It's
we're
not
we're
hoping
that
people
don't
run
into
that
problem,
but
if
they
do,
you
know
we
need
to
provide
extensive
documentation
for
it.
A
A
This
is
harry
yeah,
where
it's
where
it's
necessary,
I
mean
it's
the
best
option
we
have.
I
think
that
we
we
try
to
do
in-app
help
as
much
as
frequently,
but
that
help
is
usually
like
no
longer
than
a
couple
of
sentences,
usually
not
even
longer
than
one
sentence,
because
if
it's
too
con,
if
it's
more
complicated
than
one
sentence,
we
send
them
on
on
to
online
help
good.
I
think
that
seems
to
be
the
pattern
that
we've
been
pursuing.
B
Since
users
mentioned
a
good
example
of
simplifying
the
ui,
the
the
views
wizard
is
a
a
good
example
of
that.
So
for
a
person
that
just
wants
to
create
a
listing,
they
just
go
and
then,
when
you
create
a
new
view,
you
just
ask
them
very
basic
things
and
they
say
just
list
every
page
type.
That's
out
there
once
you
save
that
you
get
the
end
result,
but
if
you
want
to
tweak
further
you'll
just
have
to
dive
into
the
like
the
full
views.
Ui,
there's
no
other
way.
A
Okay,
I
lost
my
place.
Custom
contexts
all
right,
the
only
other.
Well,
let's,
let's
give
a
shout
out
to
using
the
administration
theme
for
the
login
form
issue.
4410
jen
has
been
heading
this
issue
up,
but
it's
been
stalled.
A
There's
just
some
complexities
here
around
showing
the
administrative
interface
and
layout
to
a
logged
out
user
that
we
need
to
figure
out
so
that
issue
is
currently
on
hold.
But
a
spin-off
of
that
issue
is
moving
forward,
which
is
removing
the
view
administration
theme
permission
which
is
issue
44.87,
so
that
issue
currently
needs
work.
A
There's
a
discussion
there
about
how
that
permission
doesn't
make
sense
in
the
current
paradigm
of
there's
the
administrative
backend
and
then
there's
the
end
user
front
end
the
concept
of
someone
being
able
to
access
the
administrative
backend
without
the
ability
to
view
the
theme
doesn't
make
sense,
and
so
that
issue
is
working
to
reduce
that
weird
conflict
that
can
occur
where
you
could
not
assign
the
permission,
but
still
give
someone
administration
powers.
So
44.87
is
that
issue.
I
think
the
concept
is
that
we'll
make
a
contrib
module
to
restore
that
permission.
A
A
B
A
All
right:
well,
that's
it
for
the
117
updates
the
initiatives
with
telemetry,
headed
up
by
jeff
and
ready
to
wear
headed
up
by
luke.
We
talked
a
little
bit
about
ready
to
wear
during
the
design
meeting
earlier
telemetry
we're
going
to
have
to
get
a
check
in
from
jeff.
I
think,
and
just
get
an
overall
status
report
from
them.
A
So
we
haven't
had
anything
to
report
on
that
for
a
couple
of
weeks
now
so
I'll
try
to
to
reach
out
to
him
and
see
if
we
can
get
just
a
status
update.
A
Okay,
we've
used
up
all
our
time,
mostly
with
me
talking
about
that
completely
off
the
wall
text
format
questions,
so
I
appreciate
you
guys
joining
the
meeting
today.
Do
you
guys
have
anything
that
you'd
like
to
mention
before
we
close?
Okay.
C
There's
one
thing,
but
it's
a
big
one:
can
you
go
this?
I
have
a
small
one
and
I
started
to
say
it.
I
was
muted,
you
it's
related
to
1.17
and
the
you
were
asking
earlier
like
how
the
initiative
might
affect
core
and
we
haven't
decided
this
sort
of
as
an
initiative.
But
one
thing
that
I,
where
I
place
one
thing
that
I
think
we
do
need
to
do
in
core
that
will
help
the
ready
to
wear
initiative.
C
Is
this
issue?
It's
excuse
me
it's
4167
and
it's
deciding
on
a
way
to
make
css
improvements
to
basis
without
breaking
sites,
and
I
want
to
start
focusing
on
that.
We
don't
need
to
talk
about
it
today
unless
anybody
has
any
quick
comments
on
it,
but
I
think
I
might
start
to
advocate
for
a
solution
to
this,
because
getting
that
into
core
is
going
to
be
helpful.
C
I
think
to
the
ready-to-wear
initiative,
and
I
but
I
it
it
so
I
had
proposed
in
the
the
issue
summary
there's
like
four
different
way:
options
that
we
outlined,
and
it
looks
like
as
I
quickly
summarize
it,
that
we
were
moving
towards
the
idea
of
a
supplemental
style
sheet
that
somebody
could
click
a
configuration
to
use.
C
So
by
default
you
would
get
the
you
would
get
basis
as
it
originally
was,
and
that
if
you,
if
you're
starting
a
new
project-
and
you
want
to
to
bring
in
all
of
the
updates
since
then
you
would
manually
click
a
button
and
there's
a
little
bit
of
debate
about
that.
Yet.
But
I'd
appreciate
feedback
on
that
or
anybody
that
can
help
implement
it.
C
It
doesn't
sound
like
it's
going
to
be
super
hard,
but
I
think
it's
going
to
open
up
there's
a
whole
number
of
issues
that
require
that
have
minor
changes
to
the
css
to
fix,
but
we
just
don't
know
how
to
do
them
without
breaking
existing
sites
anyways.
So
if
anyone
has
any
comments,
let
me
know
otherwise
we
can
move
on
and
I'll
bring
this
up
next
week.
B
Another
one
to
add
to
the
the
the
list
for
next
week
is
config
translation
for
dynamic
things
like
nodes.
It
was
brought
up,
I
think,
instead
of
by
ini
godzilla.
So
I
can't
remember
who
who
was
trying
to
translate
the
new
newly
introduced
token
supporting
author
and
date
field
that
we
added
for
its
node
type.
B
So
we
need
to
figure
out
how
we
we
will
introduce
that
chunk
of
code
that
allows
to
introduce
translatable,
strings
and
config
for
things
like
nodes,
so
I
had
yeah,
I'm
not
going
to
discuss
it
now.
Maybe
we'll
just
add
it
to
the
list,
because
it's
like
it's
a
long
discussion,
but
just
a
simple
question
is
that
all
that
it
will
take
just
figuring
a
way
to
add
this
chunk
of
information
in
in
the
case
of
nodes,
sorry
content
types
in
its
content
type
config
file.
Would
that
be
it.
A
So
yeah,
if
you're
talking
about
like
so
the
submitted
by
line,
is
now
stored
in
configuration
with
tokens
right
and
how
you
want
that
to
be
presented,
and
it
sounds
like
supposedly
that
that's
not
translated.
Currently,
it's
always
just
whatever.
A
It's
not
just
that,
but
yeah,
that's
a
great
issue
and
I
don't
think
it's.
It
is
the
perfect
situation
to
use
config
translation
and
they
should
update
the
config
file
and
say
like
this.
I
can't
remember
quite
what
the
string
is.
It's
like
underscore:
config,
translation
or
config
translation
strings
or
something
like
that
that
identifies
the
part
within
the
file
that
needs
to
be
deleted,
but
it
doesn't
automatically
when
it's
output
get
the
translated
version.
A
There's
a
new
option
in
a
config
object
that
normally
you
say,
config
arrow
get.
You
know,
config
value,
there's
a
another
method
called
get
translated,
and
so,
where
you
output
it,
you
also
have
to
say,
get
translated
and
then
that
gets
the
it
runs
through
the
locale
system
and
basically
runs
through
t
for
you.
So
there's
two
things
you
have
to
switch,
get
to
get
translated
and
you
have
to
add
the
line
to
the
config
file
so
you're
halfway
there.
B
A
But
yeah
that
would
be
great.
We
we
have
config
translation,
but
we're
not
using
it
very
consistently
throughout
all
of
core.
It
doesn't
matter
too
much
because
everything
ultimately
runs
through
t
anyway,
and
so
the
config
translation
is
an
alternative
that
is
superior
because
it
makes
it
so
that.
A
The
pot
extraction
module
the
like
translation
string
extraction
module
can
find
the
default
strings
that
are
pulled
from
config
files
and
without
it
we
can't
do
that.
We
just
get
t
being
run
on
a
variable
and
we
have
no
idea
what's
inside
of
the
variable,
and
so
you
get.
The
end
result
is
the
same
that
it
runs
through
the
t
function,
but
using
translation
with
config
makes
it
so
that
we
can
get
more
of
the
strings
accurately
represented
just
by
parsing
the
code,
and
we
can't
do
that
with
t
on
a
variable.
A
Okay,
anything
else
all
right
well,
thank
you
guys,
both
for
joining
and
thanks
everybody
out
there
on
the
internet.
We
really
appreciate
this
and
yeah
we'll
see
you
guys
around
thanks.
So.