►
From YouTube: Bckdrop Weekly - Sept 3rd - 20202
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
we
are
live
today
is
thursday
september
3rd,
and
this
is
our
weekly
meeting
to
check
in
on
active
issues
for
backdrop
core
and
other
related
things.
This
is
our
first
meeting
post
feature
freeze
for
backtrack
117,
so
we've
got
a
bunch
of
exciting
updates
coming
up
before
we
get
to
that.
B
Thanks
greg,
I'm
joining
from
greece
excited
about
the
upcoming
17th
release
and
trying
to
help
hiring
things
out
in
the
next
couple
of
weeks
and
fix
some
bugs
as
well
team.
Next
got
you.
C
Off
guard,
no
I'm
ready,
I'm
kim
st
paul
tim,
I'm
in
deerwood
minnesota,
and
there
were
just
20
minutes
ago,
two
deer
walking
by
but
they're
gone
now,
so
it
it
was
very
exciting,
release
and
fun.
I
feel
like
I've
gradually
got
more
and
more
involved
and,
like
I
feel
like
I
know
more
about
this
release
than
any
previous
release
of
the
release
that
I've
been
involved
in,
and
that
was
interesting.
So
oh
well
is
matthias
participating.
I
think
he's.
A
E
I'm
nate
lampton,
also
in
oakland,
california,
and
yeah
117,
got
a
whole
bunch
of
things
in
it
that
kind
of
as
usual,
like
deadlines
make
things
happen.
So
I'm
excited
to
talk
about
all
those
things
today.
A
All
right
before
we
get
into
all
the
exciting
things
that
happened.
I
want
to
just
mention
that
we
have
two
new
contributed
modules.
This
week,
paragraphs
mapper
in
single
image,
formatter,
so
always
stuff
happening,
which
is
great
and
then
let's
turn
it
over
to
nate
talk
about
what
went
into
117.
E
No
worries
all
right,
so
117
117's
feature
freeze
was
tuesday
day
before
yesterday,
and
so
we
had
a
really
productive
code
sprint
over
the
weekends,
and
there
was
also
a
lot
of
activity
that
continued
on
through
monday
and
tuesday
to
get
things
all
wrapped
up,
big
thanks
to
our
reviewers
out
there.
They
would.
We
had
lots
of
really
super
reviewers
that
were
coming
in
constantly
and
we're
getting
stuff
reviewed
like
in
10
minutes
stuff
was
coming
back
and
the
feedback
loop
was
was
super
positive.
E
There
also
big
thanks
to
core
committers
bw
panda
and
herb
dual,
who
both
were
actively
like
reviewing
and
merging
things
as
well.
It
was
super
cool
with
bw
panda
in
australia.
We
had
kind
of
like
round
the
clock,
merging
action
happening
for
the
past
several
days,
which
is
really
cool.
E
E
That
issue
is
merged
in.
We
do
have
some
ongoing
conversation
about
the
way
that
we
achieved
backwards.
E
Compatibility
might
cause
some
confusion
when
you
start
creating
complex
contexts,
but
core
doesn't
have
any
of
these
complex
contexts
so
far,
and
so
when
we
get
to
that
situation,
we'll
decide
if
we
need
to
add
additional
support
for
making
it
so
that
those
things
work
consistently
or
if
the
current
approach
is
confusing,
then
we
can
address
it
then
so
3750
got
merged
in
that's
really
great,
although
it's
kind
of
a
power
user
feature,
it
does
open
us
up
to
some
interesting
possibilities
and
layouts
kind
of
starting
to
make
layouts
fully
realize
the
the
capabilities
that
panels
had
in
drupal
7,
because
there's
still
one
or
two
things
that
layouts
and
doctor
don't
fully
support,
and
this
is
one
step
closer
to
that.
E
Let's
see
next
up
bw
panda
advocated
for
this
security
enhancement
that
we
should
be
adding
htaccess
files
to
the
config
directories.
The
private
files
directory
has
a
little
security
enhancement,
although
it's
recommended
that
you
move
your
private
files
directory
outside
of
the
web
route.
If
you
don't
backdrop
tries
to
secure
that
directory
with
an
htaccess
file
which
works
for
apache,
and
we
have
the
exact
same
recommendations
for
config
that
config,
we
recommend
you
move
it
outside
of
the
web
route.
E
But
if
you
can't
right
now,
it's
only
protected
by
obscurity
that
it's
given
a
completely
weird
random,
md5
hash
name,
and
this
enhancement
makes
it
so
that
the
same
way
that
we
secure
the
private
files
directory,
we
do
the
same
thing
to
the
config
directory.
E
So
in
the
event
that
you
can't
move
your
config
outside
of
the
web
route,
this
adds
an
additional
security
enhancement
on
top
of
it.
So
that's
great,
let's
see
this
next.
One
is
really
crazy
because
it
came
out
of
just
this
past
couple
of
weeks:
lazy
loading
for
image
tags
issue
3659.
E
As
of
a
week
ago,
we
had
an
approach
that
was
trying
to
add
this
loading,
equals
lazy
attribute
globally
across
the
entire
site,
but
it
wasn't
actually
being
global,
and
so
this
issue
pivoted
really
quickly
from
having
a
global
setting
to
moving
it
to
a
per
image
field
setting
instead.
So
now,
when
you
configure
the
display
formatter
for
an
image,
you
can
decide
whether
or
not
it
loads
lazily
or
not.
E
E
So
if
you
have
a
situation
where
you
put
an
image
up
above
the
fold,
you
can
specify
in
that
display
formatter
that
it
should
be
loaded
eagerly
saying
that
it's
a
critical
part
of
the
page,
so
that
was
great.
That
was
a
real,
great
compromise
and
and
switch
to
the
way
that
that
works,
that
it's
not
only
works
consistently.
It
also
it
provides
more
flexibility
than
before.
So
I'm
really
pleased
with
the
way
that
that
issue
3659
turned
out.
E
Except
there
is
a
feature
from
date:
module
that
had
been
removed
in
its
port
to
backdrop
and
issue.
2766
restores
the
views
pager
by
date
that
got
completed.
E
It
had
been
marked
potentially
as
a
116
issue,
but
being
so
close
to
minor
release,
and
it
really
being
a
new
feature
that
hadn't
been
previous
versions
of
backdrop.
It
was
merged
only
into
the
one.x
branch
for
117.,
so
2766
restores
that
functionality.
It's
great
to
see
that,
and
then
we
have
a
number
of
issues
that
we've
never
mentioned
during.
These
team
calls,
because
we
only
really
cover
stuff
that
has
an
advocate
during
these
calls,
but
there's
a
number
of
other
issues
that
got
merged
in
the
last
week.
E
That
are
also
worth
mentioning,
even
though
they
never
specifically
had
an
advocate,
or
at
least
they
didn't
before
this
week.
E
So
one
of
them
is
expanding
image
tokens,
formerly
the
functionality
of
the
image
cache
tokens
module
in
drupal
7.,
it's
issue,
3594.
E
That
enhancement
makes
it
so
that
you
can,
when
placing
a
token
you
can,
you
can
specify
individual
image
styles
to
be
represented
in
that
token
now
as
well.
So
that's
a
cool
enhancement,
enforcing
basic
password
constraints,
issue,
42.65,
herb
dual
really
put
in
some
really
solid
effort
on
making
this
possible
that
we
reached.
There
was
a
lot
of
back
and
forth
in
this
issue.
E
I
think
we
had
like
130
140
comments,
but
we
reached
a
pretty
good
compromise
that
there
is
now
just
a
simple
single
checkbox
on
the
user.
Account
settings
forms
that
allow
you
to
reject
weak
passwords.
So
there's
just
one
checkbox
that
says:
reject
weak
passwords,
and
if
you
check
that
box,
it
will
not
allow
users
to
use
the
username
use
their
username
as
their
password
use
their
email
address
as
their
password
or
have
a
weak
password
per
the
the
password
strength.
E
So
that's
really
cool.
It
also
has
some
under
the
hood
enhancements,
because
what
a
weak
password
is
really
can
fluctuate
and
the
system
for
determining
weak
password
is
extensible
so
that
a
contrib
module
could
in
theory,
add
additional
enhancements
on
there
to
identify
what
weak
passwords
are.
The
most
obvious
candidate
is
like
there's
certain,
like
the
the
list
of
the
top
100
passwords,
for
example,
isn't
something
that
we've
built
into
core,
but
can
trip
could
easily
exclude
certain
things
like
the
word?
E
Password
is
one
of
the
most
common
passwords
and
in
backdrop
that
might
pass
the
weak
password
indicator,
but
if
you
had
a
black
or
sorry
had
a
block
list
of
of
bad
passwords,
then
that
that
password
would
be
considered
weak
so
anyway,
it's
it's
a
really
great
compromise.
There's
also
some
flexibility
in
there
freaking
trip
to
extend
it
further.
E
E
45-58,
there's
some
pretty
strong
enthusiasm
in
there
in
that
issue.
For
that
new
functionality
that,
when
you
place
a
block
in
backdrop,
it
auto
generates
a
description
in
the
preview
area
like
when
you're
editing
the
the
layout,
and
if
you
place
the
same
block
multiple
times,
then
it
can
be
really
confusing
like
they
could
be
configured
differently
and
be
displaying
differently,
but
the
admin,
description
and
label
on
those
blocks
are
all
the
same.
This
lets
you
add
a
custom
description
and
label
on
each
one
of
those
instances
of
the
block.
E
So
you
can
tell
what
the
difference
is
between
them,
so
yeah,
some
site
builders
very
excited
that
will
make
managing
complex,
layouts
a
lot
easier
for
them.
E
And,
lastly,
a
new
issue
is
the
an
enhancement
to
the
admin
content
listing
slash
admin,
content
that
that
listing
was
converted
to
a
view
within
backdrop,
but
in
that
conversion
it
lost
the
ability
to
show
the
new
or
updated
marker.
Next
to
each
piece
of
content.
We
restored
that
in
issue
2350,
so
the
view
is
now
configured
to
show
that
indicator
when
viewing
that
listing.
So
if
you're,
an
administrator,
you
can
see
new
content
that
has
been
created
since
the
last
time.
You
viewed
that
page.
E
That's
it
for
the
list
of
things
that
got
into
117
this
week.
It
was
super
great.
We
got
on
all
kinds
of
things,
sorry
about
my
cat
meowing
we
didn't
get
in
the
view
we
were
trying
to
remove
the
view.
The
administration
theme
permission,
that's
issue
44.87.
E
It
never
got
tagged
in
the
117
milestone
because
it
never
got
seconded,
and
so
I
think
that
made
it
so
that
we
lost
track
of
it
a
little
bit.
But
that's
fine.
A
Yep,
I
have
questions
on
that.
So
the
reason
we
wanted
that
in
117
is
because
it
was
blocking
the
ability
to
add
a
checkbox
to
use
the
administration
theme
on
the
login
form
issue.
So
we
want
to
do
this
one
in
117.
So
we
could
do
that
one
in
118
but
question
for
core
committer.
Can
we
still
get
them
both
into
118,
even
if
they're,
in
as
long
as
we
get
them
in
the
right
order,
or
do
we
have
to
bump
the
next
one
at
119.?
Okay,.
F
E
Yep
so
that
one
got
bumped
to
118,
I
believe
44.87,
it's
actually
not
in
okay,
it's
still
just
a
milestone
candidate,
it's
not
even
in
118
yet
so
speaking
of
those
milestone
candidates,
our
recap
for
our
general
process
here
is
that
whenever
we
want
to
put
something
in
the
next
minor
version,
we
mark
it
as
a
milestone
candidate,
minor
and
then
another
person
has
to
come
in
and
second
it
as
saying
yes,
this
should
be
in
the
next
minor
bug
release,
but
we
haven't
been
real
good
about
agreeing
or
perhaps
not
people,
just
don't
necessarily
think
certain
things
should
be
in
the
next
race,
but
we
currently
have
56
issues
that
are
all
candidates
for
the
next
minor
issue.
E
So
there's
just
a
lot
of
issues
there
that
potentially
we
could
whittle
that
down
a
little
bit
either
saying
no.
I
don't
think
this
is
a
good
candidate
for
the
next
version.
A
E
E
Yeah,
so
we
have
lots
of
potential
issues
that
could
go
into
one
118,
which
would
be
the
next
minor
version
all
right.
Well,
that's
the
the
status
on
117..
Do
you
guys
have
anything
else?
You
would
like
to
add
regarding
the
next
minor
version,
or
this
minor
version
that
we're
working.
E
E
All
right
so
116
116
is
the
bug,
fix,
release
and
116
continues
to
accrue
lots
of
bug.
Fixes,
let's
see
one
of
them
is
this
error
about.
Update.Php
throws
a
message
telling
you
to
delete
your
configuration
if
your
staging
config
directory
isn't
ready,
it's
a
confusing
sounding
issue,
but
it's
a
simple
fix.
3846
this
one
has
been
marked
rtbc.
E
There's
an
issue
where
the
site
gets
stuck
in
maintenance
mode.
If
you
update
a
module
through
the
ui
issue
39.56,
there
hasn't
been
any
updates
on
this
in
a
couple
of
weeks,
but
the
current
issue
has
a
pull
request
and
just
needs
review.
E
This
automated
code
checks
issue
that
uses
phpcs
to
check
the
code
style
of
issues.
It's
a
code
style
of
your
code.
It's
issued
32
13.,
there's
progress
happening
on
this,
but
the
issue
itself
hasn't
been
updated
because
it's
happening
in
different
different
issue
trackers,
and
so
I
unfortunately
not
really
well
prepared
to
give
it
an
update
on
quite
where
that
is.
E
Anyone
else
want
to
comment
on
that
one.
The
php
cs,
one:
okay!
Well,
if,
if
joseph
flatt
watches
this
video,
I'm
sorry
that
I
can't
remember
the
status
of
things
because
I
know
you're
working
on
it
and
I
appreciate
it,
but
maybe
let's
get
an
update
on
that
issue,
so
that
way
we'll
be
able
to
give
summaries
in
the
future.
E
Let's
see
and
then
lastly,
in
this
kind
of
general
list,
we
have
this
issue
where
ck
editor
was
not
saving
when
in
source
mode
when
in
a
dialog.
So
this
most
frequently
occurred
when
you
were
editing
a
custom
block
that
you
would
add
a
custom
block,
switch
to
source
mode
and
then
save,
and
it
wouldn't
save
your
changes
so
issue
1259.
E
Is
that
one
we
found
a
fix
for
it
and
it
has
been
merged
much
to
tim's
relief,
because
he
says
that
he
runs
into
that
one.
All
the
time.
E
Let's
see
other
things
that
are
in
the
almost
done
category,
setting
a
reasonable
max
input,
vars
php
variable
it's
issued
38-24.
We
got
a
re-roll
on
that
issue
just
today.
It
currently
needs
review
and
we
still
need
to
update
the
documentation
that
it
links
to
to
accurately
reflect
recommendations,
but
that
one's
getting
real
close,
removing
the
block
title
from
the
search
block.
E
Actually
it's
funny
because
they
they
said
this
is
how
it's
working
is
that
correct
and
columnist?
You
came
in
and
said
yes,
that
is
correct,
so
it's
actually
been
tested
by
two
different
people
saying
that
it
works
the
way
that
we
expect
it
to,
but
they
weren't
actually
sure
if
that
was
correct
or
not
so
that
one
is
probably
ready
to
be
at
least
works
for
me,
possibly
rtbc.
So
that's
great.
E
Oh,
it
is
labeled
works
for
me,
okay,
great
and
then
last
about,
like
I
said.
Lastly,
views
the
or
behavior
can
be
a
little
bit
strange.
It's
issue,
34
15,
haven't
been
any
any
updates
in
this
issue.
We
still
have
a
pull
request
and
still
just
needs
review.
E
Okay
and
then
last
now
really
for.
Lastly,
we
have
remove
blacklist
and
whitelist
from
core
issue
4441
and
remove
master
and
slave
terminology
from
court
4451.
E
Yep
and
that's
what
I
was
going
to
say
next-
is
that
we
have
this
two-week
lull.
E
If
you
will
in
between
now
and
the
release
of
sorry,
just
keep
forgetting
what
current
version
we're
on
117
and
so
117
comes
out
on
september
15th
and
we
won't
be
putting
in
any
new
features
between
now
and
then,
but
we
will
still
still
be
doing
bug
fixes
that
exist
in
both
the
117
version
only
and
in
the
current
116
version,
so
116
3
will
come
out
on
the
15th
as
well,
and
so,
if
we're
looking
to
make
progress
on
fixing
things,
there's
there's
no
reason
to
wait
like
now
is
a
great
time
to
get
additional
enhancements
in
for
the
last
version
of
116.
E
If
you
would
like
to
do
that,
and
all
the
enhancements
we
put
into
sorry
all
the
bug
fixes
we
put
into
116
will
also
be
in
the
117.0
version
that
comes
out
on
the
15th,
so
the
160,
all,
that
is
to
say,
if
you're
looking
for
things
to
fix,
look
at
the
1163
milestone
and
that's
probably
where
the
the
bulk
of
new
work
will
be
happening
for
the
next
couple
of
weeks.
E
B
I
wanted
to
mention
that
we
want
to
encourage
people
in
this
to
read
the
testy
prerelease
version,
but
we
don't
provide
an
easy
way
for
them
to
do
it.
Similarly,
as
we
do
for
the
demos
so
there's
been
some
discussion,
developers
can
get
the
one.x
branch
and
set
it
up
on
the
local,
but
we
should
encourage
more.
B
You
know
everyday
users,
so
eventually
we
should
either
get
a
second
button
on
the
demo
page
to
say
that
we
can
publish
and
publish
as
a
peer
releases
come
out
or,
as
dr
wilmot
suggested,
we
should
have
a
button
that
always
has
the
the
latest
head
version.
E
B
E
Speaking
speaking
of
that,
are
we
planning
a
newsletter
before
the
release
of
117.
C
Yes,
because
of
bankrupt,
live
yeah;
okay,
it
probably
went
after
as
well
yeah.
I'm
thinking
there'll
be
like
two
in
the
next
week,
two
weeks
like
one
as
soon
as
possible,
and
then
another
one
right
after
the
release
and
right
before
backdrop
live.
That
would
be
great.
A
D
Oh
sure,
justin
christopherson,
I'm
in
denver,
colorado
and
I'm
probably
gonna-
make
some
tickets
to
update
the
servers.
For
you
know
it's
been
a
little
while
so
that's
about
all.
I
have.
B
C
A
I
think
the
sandboxes
that
we're
failing
are
all
the
ones
on
gorge
server,
so
we
don't
actually
have
any
control
over
that
so
like
we
have
control
over
well,
I
don't
know
about
this.
Actually,
we
have
control
over
the
ones
on
backdrop
cms
to
work
where
you
click
the
button
are
those
the
ones
that
were
failing.
C
A
Yeah
those
are
gores
and
we
don't
have
any
control
over.
What's
going
on
over
there.
C
E
Yeah,
we
do
have
the
option
if
we
want
to
switch
our
sandboxes
over
to
tugboat,
like
that
is
a
an
option
that
we
have
available
to
us.
A
We
might
want
to
ask
tugboat,
though,
for
more
space
before
we
do
that,
because
we're
out
using
the
normal,
like
button,
push
process
and
if
we're
going
to
add,
like
a
thousand
pull
requests
to
that.
We
want
to
make
sure
we
have
the
ability
to
do
that.
C
Yep,
maybe
we
want
to
schedule
a
meeting.
You
know
use
one
of
these
meetings
to
talk
about
that
whole
process,
because
I
know
I
mean
I
don't
count
myself.
I
was
frustrated
by
them,
but
it's
not
my
biggest
priority,
but
I
was
sensing
from
some
other
people
in
the
queue
that
this
is
getting
to
be
something.
A
It
has
even
worse
with
time,
and
I
also
noticed
that
our
tests
are
failing.
Now
too,
we
don't
have
another
alternative
for
tests
at
the
moment,
so
yeah.
It
would
be
good
to
get
some
of
gore's
attention
on
that,
at
least
to
look
at
the
test
stuff.
Even
if
we
can
say
we
can
switch
over
sandboxes,
but
maybe
if
we
get
his
attention,
he'll
fix
the
sandbox
do
so.
B
I
don't
know
the
sandboxes
were
failing
this
past
week,
I
guess
or
two
and
the
ones
that
were
failing
were
really
old
ones.
So
I
understand
that
maybe
the
same
way
that
that
board
sort
of
like
purges,
the
old
ones.
Maybe
that's
what
happened,
and
then
we
get
redirected
to
those
pages.
I'm
just
saying
there
were
brand.
B
So
it
didn't
happen
for
me,
what
has
been
annoying
me
for
years
is
the
the
test.
As
you
say,
they
randomly
fail,
and
sometimes
they
fail
in
the
details,
link
just
links
nowhere,
so
I
have
no
visibility
and
I'm
forced
to
close
and
reopen
pull
requests
to
make
that
go
away,
and
it
doesn't
happen
on
the
first
time
either
like
you
might
take
several
times
before
that.
E
E
All
right
well,
do
we
have
any
other
topics
or
anything.
I
will
often
justin
yeah
there
we
go.
G
And
yeah
I've
an
old
one,
just
wanted
to
ask
about
the
status
of
the
issue.
It's
one
of
the
one
16.3
milestone
about
the
transliteration
nate.
I
guess
you
remember
it
it's.
G
G
We
are
quite
okay
with
the
current
approach,
and
so
after
you
expressed
your
concerns,
we
didn't
hear
from
you
and
so
as
as
the
next
release
is
approaching,
I'm
wondering
what
we
want
to
do
there
yeah.
We
continue
a
discussion.
E
I'll
take
a
look
and
and
comment
yeah
that
you
guys
wrote
tests.
That's
awesome
thanks
into
gozella
for
doing
that,
and
it
looks
like
the
current
approach
that
you
guys
are
taking
is
the
same
approach
that
drupal7
had
used.
So
it's
not
changing
anything
even
though
there
might
be
a
a
better
way
to
do
it,
but
you
know
it's,
it
could
be
more
complicated
so
anyway,
I'll
post,
a
comment.
Sorry
for
my
neglect
on
this.
B
G
G
E
All
right:
well,
let's
wrap
it
up,
then
no
need
to
stretch
things
out.
So
thank
you
guys
all
for
coming.
I
really
appreciate
it
and
yeah
we.
We
had
a
really
really
great
week.
I
I'm
really
happy
and
pleased
with
what
the
work
everybody
did
and
so
much
cross-collaboration
and
different
groups
working
on
different
things.
It
was
just
really.
E
It's
really
been
been
something
where
we're
moving
out
of
like
the
small
community
category.
It
feels
like
into
like
the
medium-sized
community,
because
there's
just
a
lot
of
things,
there's
there's
more
things
going
on
than
any
one
person
can
really
process,
except
for
maybe
gregory.