►
From YouTube: Backdrop Weekly - 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).
A
We
are
on
air
today,
it's
thursday
august
27th,
and
this
is
our
weekly
meeting
to
check
in
on
core
development
and
other
relevant
tasks
before
we
get
to
the
agenda.
Let's
go
around
and
have
everybody
do
introductions,
let's
start
and
in
the
last
meeting
we
did
this
fun
thing
where
the
person
who
was
introducing
themselves
called
on
the
next
person
to
introduce
themselves.
So
let's
do
that
again,
let's
start
with
greg.
B
C
Thanks
greg,
I'm
tim
st
paul
tim
in
deerwood
minnesota,
and
we
just
excited
about
a
excited
and
nervous
about
a
deadline
coming
up
here
for
us,
so
here
to
see
what
we
can
get
into
1.17
we've
got
a
few
days
two
in.
D
E
I'm
nate
lampton,
I
live
in
oakland,
california
and
yeah.
Like
tim
said,
this
is
the
last
meeting
before
code
free.
So
I'm
also
excited
to
see
what
things
we
can
get
in
before
then,
before
september,
1st
jen
have
you
gone
yet
nope.
A
I'm
jen
lambton
also
in
oakland,
california,
also
very
excited
about
code
phrase
and
a
potential
sprint
this
weekend,
so
yeah
all
right
before
we
move
on
to
anything
else.
I
want
to
thank
d
bond
for
porting.
The
cash
exclude
module,
so
we've
got
new
contributor
application,
which
is
exciting,
and
in
the
past
week
we've
had
two
new
contributed
modules.
Menu,
link,
weight
and
automatic
entities
were
both
released.
A
This
week
I
did
add
a
note
here
to
merge
and
deploy
the
pull
request
for
cleaning
up
the
tugboat
sandboxes
since
we've
been
hitting
limits
on
that
moore's.
Just
a
reminder
to
ping
bw
panda
since
he's
been
doing
work
on
our
sites
and
also
there's
a
note
here
for
the
api
site,
thanking
vw
panda
for
all
of
his
work
on
the
new
form
api
reference
page.
That's
a
page.
A
That's
really
really
valuable
to
module
developers
to
try
and
figure
out
what
what
your
form
elements
do
and
what
properties
are
allowed
on
them
and
when
he
first
recommended
redoing
the
page,
my
brain
like
exploded,
I'm
like
oh,
my
god,
there's
so
much
work.
I
think
tim.
You
also
were
commenting
on
this.
I'm
like
that's
so
much
work,
there's
no
way.
We
could
possibly
do
that
and
he's
been
plugging
forward
on
this
for
like
the
last
year
and
a
half
and
he's
got
it
to
a
point
now
where
it's
ready
to
start
entering
content.
E
All
right,
yeah
we're
continuing
to
plug
away,
even
though
117's
code
freeze
is
next
week
we're
still
planning
or
we're
still
going
through
a
lot
of
bug,
fixes
that
are
going
to
116..
So
of
those.
Let's
see,
it
was
brought
up
just
before
this
meeting
that
it's
becoming
increasingly
urgent
that
backdrop
properly
support
my
sequel,
8..
We
have
an
existing
issue
for
this
at
42.38.
E
My
sql
8
is
now
what
happens
when
you
do
apt,
install
my
sequel
on
debian
or
on
the
latest
version
of
debian,
and
it's
what
happens
if
you
have
the
latest
version
of
red
hat
or
centos,
so
that's
becoming
more
important.
The
patch
that
we
have
there.
There
is
a
there's,
there's
an
approach
used
by
drupal
7.
That's
also
in
review.
Right
now
over
on
the
drupal.org
issue,
queue
the
app
the
approach
used
in
this
version
is
slightly
different.
E
I'm
not
sure
if
we
need
to
adopt
the
drupal
7
approach
or
if
the
approach
that
is
used
in
4238
will
work
for
backdrop,
so
that
could
do
some
eyeballs
and
suggestions
and
testing
it
does
at
least
make
it
so
that
you
can
get
past
the
installer
and
backdrop
generally
works,
but
there's
a
lot
of
test
failures
that
I
haven't
looked
into.
That
could
use
some
examination.
E
So
there's
definitely
some
like
corners
of
backdrop
that
probably
still
aren't
working.
Let's
see,
update.php
throws
an
error
about
install.php
and
says
some
confusing
messages
about
the
configuration
directories.
That's
issued
38.46,
it's
been
marked,
rtbc,
just
a
real,
simple
fix
that
separates
those
messages
about
the
config
directories
into
two
separate
things.
I
said
there
was
also
a
follow-up
issue
that
was
created
that
notifies
users
if
their
staging
directory
isn't
set
up
just
all
the
time,
so
both
of
those
things
sound
good.
E
Let's
see
the
site
stuck
in
maintenance
mode
issue
is
has
something
to
do
with
when
you
run
updates
on
modules
is
assisting
in.
Actually,
this
hasn't
seen
any
activity
anytime
recently,
so
I
probably
won't
recap
it
again.
The
issue
is
39.56,
though,
continues
to
need
testing.
E
In
the
category
of
things
that
need
testing
issue,
2766
restore
the
view
that
the
pager,
by
date
plug-in
to
date,
module
that
has
some
updates
that
indigo
zella
added
automated
tests
to
that
issue,
which
is
great,
I
think
that
that
was
kind
of
one
of
the
holdups
here
at
this
point
now
this
just
needs
some
additional
code
review
to
make
sure
everything
looks
fine.
I
think
doc.
E
Wilmot
did
a
substantial
amount
of
testing
checking
to
make
sure
that
this
approach
used
by
core
is
compatible
with
calendar
module,
the
contrib
version.
So
I
think
we're
all
good
on
testing
here.
I
think
this
is
now
just.
It
needs
some
final
eyeballs
to
review
the
new
code
editions
for
tests.
E
Let's
see
that
that
feature
I
feel
like,
maybe
we
should
bump
into
117,
because
it's
adding
new
functionality,
I
get
that
it's
probably
marked
as
a
bug,
because
it's
been
missing,
you
know,
since
we
did
the
port
of
date
module,
but
it's
also
kind
of
a
new
feature,
something
that
wasn't
there
in
previous
versions
of
backdrop,
at
least,
even
though
it
was
then
drupal
7..
E
So
I
don't
know
we'll
see
about
that
one.
I
might
make
my
case
there
in
the
issue
and
update
the
milestone.
E
Let's
see
joseph
was
here
earlier
and
had
an
update
on
the
next
issue,
which
is
the
automated
phpcs
code
checks.
It's
issue
3213.,
he
and
doc.
Wilmont
are
working
back
and
forth
just
a
little
bit
on
this
one
or
sorry.
C
A
He
wants
to
do
about
branch
naming
there's
also
another
issue
somewhere
else
that
bw
panda
jumped
in
on,
and
we
were
brainstorming
how
to
handle
this,
where
there
was
another
suggestion
of
moving
the
php
cs,
integration
out
of
quota
review
entirely
into
another
project,
and
that
could
be
the
project
that
joseph
and
jeff
can
use
for
their
work
and
then
coder
review
could
include
it
like
bundle
it
like
an
external
library
and
then
that
way.
A
If
we
need
to
make
any
additional
changes
to
the
php
cs
stuff,
it
doesn't
get
held
up
on
what
to
do
with
the
module
so
to
make
things
even
more
confusing.
This
is
how
drupal's
doing
it
now.
Phps
is
an
independent
project.
P
the
php
cs
integration,
it's
still
called
coder
in
drupal,
so
there's
also
some
ideas
about
like.
Maybe
we
should
rename
it
and
backdrop.
So
it's
not
called
coder.
So
we'd
have
the
same
project.
A
Drupal
has
called
code,
but
we
might
call
it
something
a
little
bit
more
specific,
like
php
cs
integration,
so
people
would
know
what
it
was.
So
yeah
there's
been
sort
of
a
lot
of
discussion
in
the
community
about
how
we
should
handle
this
going
forward
like
what
is
the
best
position
that
we,
that
would
make
the
most
sense
point
and-
and
I
think
there
has
no
consensus
on
that.
So
if
anyone
has
any
thoughts
for
how
we
should
organize
these
projects,
that
might
be
helpful.
E
There's
also
automated
code
checks
for
javascript
that
we
may
want
to
implement
at
some
point
as
well,
because
we
have
coding
standards
for
javascript
as
well,
phpcs
only
scans
php
files
and
not
obviously,
that's
the
bulk
of
our
code.
But
whenever
we're
adding
javascript,
it
would
be
equally
nice
to
have
that
syntax
checked
for
our
coding
standards
as
well.
E
So
that
might
change
things
you
know
as
far
as
like.
If
we
want
to
have
a
new
project
that
contains
coding
standards,
it
might
eventually
contain
a
set
of
javascript
coding
standards
as
well
as
php
cs
coding
standards
and,
unfortunately,
the
syntax
for
those
two
things
are
entirely
different.
Phpcs
is
a
whole
crap
ton
of
xml.
E
E
E
E
Anyway,
just
a
thought:
okay,
next
up,
modals,
are
not
saving
in
source
mode
source
mode
of
ck
editor.
It's
issue:
12
59..
I
said
last
week
that
I'm
volunteering
to
take
a
look
at
this,
but
I
haven't
had
a
chance
to
do
that.
Yet
so
1259
still
needs
work
figuring
out.
E
We
know
where
the
root
of
the
problem
is,
but
we
don't
know
the
solution
yet
so
that
needs
some
some
eyeballs
or
not
some
eyeballs.
I
need
some
knowledge
there.
So
1259
currently
needs
a
pull
request.
E
E
First,
one
is
set
a
reasonable
max
input,
vars,
that's
a
php!
Setting
that
backdrop
doesn't
do
well.
If
you
have
a
lot
of
permissions
and
the
value
of
this
is
set
to
low,
which
out
of
the
box
is
1000.,
see,
there's
some
comments
here
about.
Oh
the
documentation
page,
that's
right
that
the
documentation
page
maybe
needs
a
couple
of
edits,
but
I
think
the
code
itself
like
we
can
make
changes
to
the
documentation
page
after
merging.
So
I'm
not
sure
if
this
one
actually
needs
work,
it's
the
documentation
that
needs
work.
E
John,
do
you
recall
what
needs
to
be
done
here?
All
right?
I
wasn't
paying
attention.
I'm
sorry,
okay,
which
issue
it's
not
critically
important.
The
max
input,
vars.
E
Okay:
okay,
next
up
is
removing
the
block
title
from
the
search
box.
This
one
is
also
mark
needs
work
because
it
looks
like
bw
panda
when
he
tested
it.
He
couldn't
actually
get
it
to
demonstrate
the
new
behavior.
E
So
maybe
another
review
on
that
could
help
that
possibly
bw
panda
missed
something
obvious
or
possibly
it's
not
actually
applying
the
fix
at
all.
It's
a
little
bit
unclear
curb
duel
was
the
last
one
to
touch
it
and
he
said
that
he
has
applied
fixes,
so
I'm
guessing
that
it
works
for
her
bill,
but
not
for
bw
bw.
E
Panda:
okay,
let's
see
next
up,
there's
an
issue
to
fix
the
or
behavior.
When
you
have
multiple
filters
applied
inside
of
views.
Issue
number
is
3415..
C
Quick
quick
question
about
that,
because
there's
another
issue
about
just
cleaning
up
the
appearance
of
that
filter
and
I
noticed
that
the
views
groups
either
between
them
has
to
be
all
or
or,
and
you
can't
have
or
and
and-
and
that
seemed
weird.
E
This
is
about
just
oring
issue,
oring
filters
together.
So
it's
not
about
grouping
ores
versus
ands,
but
you
should
be
able
to
group
ors
and
hands
within
views.
C
Well,
if
you
have
three
groups
right,
they
the
the
the
selector
between
the
groups,
there's
sort
of
a
ui
discussion
going
on
right
now
and
I
didn't
know
this
issue
existed
and
it
might
be
unrelated,
but
the
ui
shows
like
a
selector
for
and
or
between
each
of
the
groups,
but
in
reality
they,
if
you
change
one,
it
changes
all
of
them,
and
that
seemed
weird
to
me,
but
somebody,
I
think,
jason
checked
and
he
said.
Oh,
it
turns
out
that
drupal
does
the
same
thing.
C
B
C
E
Well,
thinking
off
the
top
of
my
head,
I
can
see
why
it
might
do
that
that
if
you
have
multiple
groups
say
you
have
three
different
groups
and
you
change
the
option
from
and
to
or
it
changes
all
you
know
the
or
between
all
of
them
to
or
and
and
that
would
be
possibly
because
unless
you
have
another
level
of
nesting,
the
operand
order
starts
getting
really
confusing
like
the
and
versus
the
or,
if
you
have
them
all
in
the
same
level,
I
mean
we
know
that
and
runs
before
ors
do,
but.
B
E
Okay,
thanks
for
bringing
that
up,
though,
it's
an
interesting
thing
that
could
use
some
thought.
E
Let's
see
the
next
two
issues
are
attempts
to
remove
some
sensitive
terminology
from
core
blacklist,
whitelist
master
and
slave.
The
issue
numbers
are
and
44
51
and
looks
like
there's
some
additional
discussion
going
on
here
in
the
first
one,
44
41.
E
Just
commentary
about
whether
or
not
the
effort
is
actually
worth
it,
but
I'm
not
gonna
rehash
that
here.
I
think
that
that's
the
discussion
is
is
pretty
good
in
the
issue
and
I
don't
think
we
need
to
go
over
it
again,
but
we
do
still
have
some
challenges
in
doing
the
implementation
that
in
some
places
this
may
affect
apis
in
some
places,
because
it's
built
into
the
name
of
some
functions.
E
So
I
think
that
this
first
one
4441
is
back
to
needs
review.
So
that's
where
we
are
on
that
one.
I
haven't
had
a
chance
to
take
a
look
at
it
recently
and
the
one
of
masters
and
slaves.
E
B
E
B
C
E
Okay,
so
anything
else
for
116,
okay,
so
117
117
its
feature.
Freeze
is
september.
1St
and
release
will
be
september.
15Th
this
year
is
a
little
bit
different.
The
past
several
years,
actually
september
first
has
fallen
on
labor
day
a
holiday
in
the
united
states.
It
didn't
happen
this
year.
Labor
day
is
instead
september
7th.
E
So
for
the
first
time
in
like
several
years,
well,
actually
he'd
be
having
future
freeze
on
september
1st,
which
is
oh,
which
is
tuesday
actually
interesting.
E
So
that's,
basically
just
things
are
going
to
proceed
as
planned
there.
There
is
no
postponement
of
the
code
freeze
this
year
or
for
this
release
and.
E
Yep,
that's
right
and,
like
tim
and
greg
have
mentioned
in
passing,
we
are
planning
at
least
I'm
planning
on
doing
a
little
extra
push
over
the
weekend
I'll
set
aside
some
time
to
do
a
code
review
on
the
issues
that
are
currently
slated
for
117,
which
are
pretty
minimal.
So
I'm
pretty
I'm
optimistic
that
we
can
get
a
couple
of
these
and
knocked
out.
B
Yeah,
I
think
that
we
should
focus
everyone
that's
doing
weekend.
We
should
focus
on
the
tickets
that
are
tagged
for
minor
and
the
117,
the
ones
that
are
being
milestone,
because
the
ones
that
are
for
116,
we
can
do
it
in
the
next
couple
of
weeks
until
we
have
to
find
the
release,
I'm
not
saying
neglect
those
but
yeah
focus
on
the
from
the
ones
that
come
in.
E
Yup,
that's
right.
I
agree
so
first
issue
that
we
have
here
is
this
issue
for
layouts,
adding
support
for
custom
contexts.
Issue
37.50.
E
I
took
a
look
at
this
one
doc
belmont
has
been
leading
the
charge
on
the
code
and
he's
the
advocate
for
it.
Everything
inside
of
this
issue
worked
exactly
the
way.
I
would
expect
it
to
functionality
wise.
It
does
exactly
what
it
says
it
does
and
it
makes
it
so
you
can
take
any
layout
that
doesn't
have
any
context
at
all
say
like
the
home
page
and
add
the
context
of
a
user
or
a
node
or
taxonomy
term.
E
So
if
you
wanted
to
pull
out
profile
information
from
user
number
one,
you
could
do
that
by
adding
user
number
one
as
a
context
to
the
home
page
or
any
other
fixed
path
page.
So
it
looks
really
good.
It
works
really
well.
E
My
feedback
in
it
is
that
it
has
some
small
changes
to
the
api
regarding
how
contexts
are
loaded,
and
I
think
that
those
changes
are
avoidable
and
I
have
some
suggestions
in
the
issue
37.50.
So
I'm
hoping
doc
willmott
will
come
back
in
and
make
those
changes.
But
if
we
don't
see
any
change
by
the
weekend,
I
may
file
a
pull
request
to
or
push
a
change
to,
the
port
request
that
make
those
backwards
compatibility
changes
and
then
we'll
need
a
review
from
someone
else
to
double
check
that
that's
all
okay.
E
It
would
really
be
great
if,
if
dr
wilma
can
come
back
in
and
take
a
look
at
them,
though,
because
I
don't
really
want
to
be
making
changes
to
something
that
he's
put
a
lot
of
effort
in
without
getting
his
approval
on
it,
but
that
one
is
looking
really
good.
I
I
don't
see
any
reason
why
we
can't
have
that
completed
before
this
weekend,
because
it
doesn't
seem
as
though
there's
any
substantial
problems
with
the
implementation
and
it
works
great
and
it
has
tests
so
yeah
we're
in
really
great
shape
on
37.50.
C
Again
not
trying
to
make
it
perfect,
but
just
trying
to
make
it
the
least
confusing
is
possible.
E
Yeah
yeah,
I
I
wonder
where
is
that
discussion
happening
in
that
issue
about
the
ui.
E
Okay,
yeah
I'm
unsure
about
that,
because
I
don't
find
it
confusing,
but
I
mean
I
wrote
a
lot
of
the
modules
so
and
I'm
familiar
with
with
drupal
7
and
so
yeah.
So
I
I'm
having
I,
I
need
feedback
from
other
people
in
order
to
understand
the
confusion
there
and
yeah.
I
don't
know
how
to
hide
it
honestly,
because.
E
Yeah,
would
you
put
permissions
in
there
too,
because
it
has
a
similar
level
of
prevalence
on
the
page.
E
C
C
E
So
it
might
be
better
to
separate
it
out
into
another
one
or
or
continue
the
conversation
until
it
gets
closed.
But
then
you
know
that's
just
kicking
the
can
down
a
little
bit.
E
Okay,
let's
see
next
up
removing
the
view
administration
theme
permission,
this
issue
4487.
E
I
haven't
had
a
chance
to
look
at
this.
One
recently
looks
like
indigo.
Zella
is
trying
to
take
a
look
at
it
jen
you
filed
the
pull
request
and
made
a
contrib
module
awesome,
but
indigozella
says
that
they're
that
it's
currently
failing
tests,
so
it's
possibly
not
really
worth
the
them,
taking
a
look
at
it.
Yet.
A
Yeah,
I
was
a
little
concerned
that
when
I
removed
the
code
from
core
that
nothing
like
not
enough
changed,
so
I'm
like
there's
got
to
be
something
in
here.
That's
using
this
that
I
haven't
found
yet
and
then
the
tests
failed
and
I'm
like
yep.
A
E
You
have
to
have
tests
to
make
sure
that
it
doesn't
break
if
something
else
was
using
it
yeah,
okay,
great
next
one
up
is
bw
panda's
issue
he's
advocating
for
securing
the
config
directories
with
hd
access.
E
It's
pretty
simple
change
since
we're
already
using
htaccess
to
protect
other
directories.
It's
just
adding
the
same
hd
access
file
to
the
config
directory,
it's
much
simpler
than
I
would
have
expected
actually
tuhin
you-
and
I
have
both
been
commenting
on
that
issue
today.
I
think-
and
I
think
that
I
said
it
in
the
issue,
but
I'll
say
it
again
here-
that
it's
a
good
idea
for
us
to
pursue
this
for
the
users
of
apache.
E
But
the
approach
of
securing
the
files
with
file
permissions
is
something
that
we
should
also
look
at,
that
we
can
separate
out
and
have
another
discussion
about
that
approach
as
well,
which
would
work
on
other
systems
that
aren't
apache
based
or
for
apache
users
that
don't
have
hd
access
turned
on.
B
So
I
are
you
referring
to
me,
though,
because
you
said
george,
you
mean
me
right,
honest
you,
oh
so,
yes,
I
know
that
ng
next
doesn't
support
it.
It
doesn't
mean
that
this
is
going
to
be
the
only
sort
of
like
measure
of
security
that
we
have
in
place.
It's
just
that
for
people
that
do
use
apache.
This
is
going
to
be
an
improvement.
It
doesn't
break
things
for
nginx
and
we
don't
solely
rely
on
that.
We
have
the
hash
in
the
config
directory
and
people
can
move
it
outside
the
docker.
B
E
Yeah
we
added
some
changes
that
defer
differ
from
drupal
7
as
well,
that
drupal
7
adds
hd
access
files
all
over
the
place.
No
matter
what
and
we
added
web
server
detection
to
backdrop
at
one
point
that
can
detect
whether
or
not
you're
running
apache
and
if
you're
not
running
apache,
it
doesn't
bother
making
those
htaccess
files
all
over
the
place
because
it
doesn't
want
to
give
you
a
sense
of
these.
E
Things
are
protected
when
they're
not,
and
so,
if
you're
not
running
apache,
it
just
doesn't
make
the
hd
access
files
at
all
it
kind
of
says.
You
know
you're
a
little
bit
more
on
your
own,
but
that's
always
been
the
case
with
nginx,
because,
like
clean
urls,
you
have
to
configure
the
web
server
in
nginx.
E
E
E
Yeah
yeah,
we
have
an
old
issue
about
settings.php
the
drupal
7
locks
down
the
permissions
on
settings.php,
and
we
changed
the
way
that
that
works.
It
would
be
good
to
go
and
take
a
look
at
that
issue
to
revisit
it
to
see
some
just
like
past
discussion
about
the
same
thing
about
setting
file
permissions
inside
of
backdrop,
because
I
I
know
I've
posted
some
thoughts
about
how
it
might
not
really
be
very
effective,
but
you
know
it.
E
A
Okay
and
one
question:
do
we
have
any
idea
what
the
usage
is
on
apache
versus
nginx?
I
just
did
a
little
bit
of
googling
and
it
looks
like
there's
generally
more
apache
usage
for
smaller
sites
and
more
nginx
usage
for
bigger
sites,
but
I
didn't.
I
also
like
I'm
not
entirely
sure
that
you
can
tell
what
web
server
people.
A
A
If
we're
able
to
detect
it,
I
mean,
could
we
detect
on
pantheon
or
aqua
that
it's
running
both.
C
E
So
what
what
backdrop
would
do
if
we
used
some
kind
of
telemetry
is
it
would
be
concerned
about
the
lowest
layer?
So
if,
in
the
case
of
like
pantheon,
where
they
have
both
backdrop
would
say,
you're
using
apache
because
htaccess
is
being
respected
and
the
fact
that
nginx
is
in
front
of
it
doesn't
really
matter
to
the
application.
E
D
But
we
have
to
make
it's
using
light,
speed
or
engine
x
or
apache
everything.
So
if
light
speed,
htxl
sparks
fine,
no
problem.
B
Yeah
so
efficiently
we
support
only
party
right
and
then
we
say
that
nginx
works
as
well.
B
E
You
know:
do
we
have
a
documentation
page
on
ngx.
B
Yes,
so
so,
if
you,
I
just
posted
a
link
on
the
chat
in
zoom
which
points
to
backdrop,
cms.org
class
requirements
and
if
you
go
to
the
web
server
section
nginx
has
a
details
link.
So
if
you
go
there.
E
This
formatting.
E
A
E
Yeah
well,
let's,
let's
move
on
to
the
next
issue
since
we're
running
out
of
time
here
this
is
a
newish
one
for
117.,
add
support
for
lazy
loading
images,
and
this
is
through
the
new
html.
What's
the
attribute.
E
Equals
loading
yeah
attribute-
I
only
saw
this
today,
so
my
feedback
might
not
be
super
valuable,
but
I
did
read
through
and
solve
that.
E
Olaf
was
thinking
along
the
same
lines
as
myself
that
you
know
if
we
blanket
so
the
way
that
the
implementation
is
right
now
it
adds
a
performance,
an
option
to
the
performance
page
check,
boxing
use,
lazy
loading
for
images,
and
it
just
adds
the
lazy
attribute
to
every
thing
that
runs
through
theme,
image
on
the
whole
site,
and
my
concern
is
that
I'm
not
sure
that
we
really
know
what
that
will
do.
F
It
depends
it
depends
on
not
only
google
ranking,
it's
also
make
website
faster
too.
Yes,.
E
Yeah,
I
wonder
yeah
I
yeah,
I
don't
know
I
I
feel
like.
I
need
more
more,
like
more
evidence,
more
studying
you
know
like
to
to
go
forward
with
it.
It
seems
like
you
know
that
there
are
two
links
to
some
like
here's.
Here's
a
general
overview
of
it,
but
those
those
articles
didn't
specifically
say
you
should
turn
this
on
for
absolutely
everything.
It
just
said.
You
now
have
these
options
to
do
these
things,
but
you
know
I.
I
have
a
feeling
that
we
might.
B
A
B
So
so
the
thing
is,
it
doesn't
add
that
on
all
images
loaded
on
the
page
right,
it
only
adds
it
to
user
uploaded
images,
so
it
won't
affect
the
in
the
theme,
images
or
whatever
bits
might
be
important.
It's
it
usually
will
benefit
people
that
are
creating
gallery
nodes,
for
example,
that
upload
10
images
or
things
like
that.
A
E
E
Yeah,
but
I
think
that
would
be
one
of
the
most
valuable
places
to
have
it
apply
is
inside
of
the
body
field.
You
know
on
that
content,
so
that
could
also
be
a
little
confusing
that
the
checkbox,
a
lot
of
people
might
say
it.
Does
it
isn't
working
if
it
doesn't
actually
apply
to
stuff?
That's
in
the
body
field.
A
E
But
it
it
might,
if
you're,
using
a
caption.
A
A
I
also
like
we
have
this
meta
issue.
That's
like
make
backdrop
perform
better
out
of
the
box
in
google
page
speed
rankings,
because
right
now
it
does
a
whole
bunch
of
stuff
that
just
it
doesn't
matter
how
fast
your
pages
load.
It's
like
you
get
a
bad
seo
score
if
you're
using
backdrop,
and
this
helped
that-
and
so
I
was
like.
Oh,
I
found
something
that's
going
to
make
backdrop
perform
better
and
so
immediately
I
was
like
we
should
do
this.
I
did
it
so
right
now.
A
I
have
overridden
theme
image
on
five
of
my
sites,
where
I
override
all
of
the
stuff
in
theme,
image
and
so
far,
there's
been
no
repercussions.
It
is
not
the
future,
it
is
still
a
present.
So
I
don't
know
if
there's
going
to
be
problems
in
the
future,
but
so
far
it's
been.
It's
been
great.
B
B
E
All
right
anything
else
that
we
should
discuss
on
that
one
yeah,
I
I
I'm
not
I'm
I
don't
I'm
not
like
throwing
up
a
block
on
it.
I'm
just
saying
I've
got
concerns.
That's
all
yeah.
E
E
I
don't
I'm
not
quite
sure
yet
there's
a
lot
of
places.
We
could
add
it,
we
could
add
it
per
field.
We
could
add
it
in
image.
Styles,
you
could
say
like
if
you
use
this
image
style,
the
lazy
attribute
is
always
added
or
you
can
even
make
it
so
there's
you
could
use
that.
What
was
the
opposite,
one
that
is
like
instead
of
lazy,
there's
like
aggressive,
bigger.
B
E
B
Regular,
that
was
no
it's
not
so.
Team
team
will
disagree
because
he's
created
pages
that
have
multiple
hearing
images
all
over
the
place.
So
some
sort
of
you
have
a.
E
B
E
B
E
Well,
it
might
be
interesting.
It's
been
noted
in
that
issue
several
times
that
backdrops
hero
images
aren't
affected
by
this
anyway,
because
they're
loaded
as
a
background
image
and
not
via
an
image
tag
which
could
be
good.
E
You
know
that
they
are
typically
at
the
top
of
the
page
and
they
don't
get
this
deferred
thing
on
them
right
now
anyway,
but
it
could
be
interesting
to
specifically
put
an
image
above
the
fold,
put
lazy
on
it
and
then
use
chrome
developer
tools
to
see
how
the
first
paint
is
affected,
if
at
all
like,
if
the
image
shows
up
later
than
it
does
with
it,
not
having
the
differ
attribute
on
it,
not
having
to
lazy
attribute
on
it.
I
mean.
B
So
I've
actually
yeah
I've.
Actually
one
of
the
articles
that
I
shared
has
a
video
screencast
of
a
page
with
like
dozens
of
images
vertically
and
they
have
the
browser
inspector
open
and
as
the
person
scrolls,
it
shows
the
resources
being
loaded.
So
basically
that's
what
it
does,
but
yeah
we
can.
We
can.
E
Okay,
yeah
so
more
thoughts
on
that
one
more
feedback
would
be
appreciated
on
issue
36.59
or,
I
think
would
be
most,
I
mean
sure
if
we
can
get
a
friend
an
expert
to
provide
feedback.
That
would
be
great,
but
if
we
can
just
find
more
references
to
where
use
of
the
attribute
is
appropriate.
That
would
be
the
best
thing.
I
think
I
get
how
it
works.
It's
like,
where
is
it
appropriate?.
E
Yeah,
okay,
let's
see
last
up,
is
adding
tokens
for
image
styles.
This
is
issue
3594.
This
is
the
building
in
of
a
contrib
module,
which
I
think
is
called
the
image
cache
token
yeah.
E
That
makes
it
so
that
tokens
right
now
you
can
display
an
image
but
using
using
tokens,
but
if
you're
on
an
image
field,
this
makes
it
so
you
could
also
display
a
particular
image
style
from
the
image
field.
As
a
token,
so
pretty
simple
in
concept,
it's
kind
of
a
big
set
of
issue.
35
94,
currently
needs
review
and
feedback.
A
Yeah
I
so
this
is
something
that
I
use
all
the
time
on
all
my
sites
and
I
was
always
really
frustrated
that
it
felt
like
it
was
left
out
of
triple
seven
and
so
there's
this
contrib
module.
You
have
to
add,
and
I'm
like,
okay,
it's
fine,
but
I
would
love
to
get
it
to
be
just
part
of
image,
styles
and
image
module
in
backdrop.
E
Okay,
well,
that's
those
are
the
issues
that
we
have.
Do
you
guys
have
any
other
issues.
You
guys
would
like
to
discuss
right
now
for
117.
B
B
You
cannot
render
the
there's
no
talking
for
you
to
render
the
username
as
a
link
and
there's
two
issues
for
it
on
total
field,
and
it's
just
three
lines
of
code
change,
which
adds
basically
a
token
that
says
node
column
after
caller
a
column
link.
Maybe
I
would
get
that
in
as
okay
for
that,
instead.
E
Okay,
yeah.
That
sounds
like
a
useful
additional
kind
of
complementary
to
the
other
token
enhancements.
E
Okay,
we
also
have
the
initiatives,
but
you
know
there
hasn't
been
any
update
from
jeff
recently
on
telemetry.
There's
no
way,
that's
gonna
happen
substantially
before
next
week
and
luke's
theme
development
work
is
is
outside
of
court
for
the
most
part.
So
I
don't
think
we
need
to
rehash
those
two
things.
E
C
Yeah,
I
think
we
should,
and
also
I
want
to
just
quickly
mention
bankrupt,
live
backrap.
Live
is
registration
is
live
backdrop,
dash,
live
dot
background,
cms.org.
E
A
E
Yeah
yeah,
I
might
I
I
might
say
just
taking
it
over,
but
it's
fine,
okay.
So
this
weekend
anybody
have
any
suggestions.
E
I'd
probably
say
I
I
kind
of
like
doing
it
during
the
day
and
not
so
much
in
the
evening.
So
like
saturday
day,
I
think
would
be
a
good
time.
C
C
E
Oh
okay!
Well
what
I'll
I'll
say
for
myself
is
that
I'm
committing
to
let's
I'll
I'll
be
available
during
my
afternoon,
and
maybe
if
everybody
says
you
know
they're
available
during
the
afternoon,
while
we'll
just
miss
each
other.
But
right
put
the
time
in.