►
From YouTube: Backdrop Weekly 2021/04/29
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
Hey
we're
live
on
youtube
today
is
thursday
april
29th,
and
this
is
our
weekly
developer
check-in
meeting
before
we
get
into
the
agenda.
We
should
go
around
our
virtual
room
and
do
some
quick
introductions.
I
will
start.
I
am
jen
lampton,
I'm
joining
from
oakland
california
and
I'm
very
excited
about
all
of
the
exciting
stuff.
That's
happening
in
backdrop
land
these
days.
Let's
see
tim,
do
you
want
to
go
next
tim
looks
frozen.
B
E
Am
I
still
frozen?
Oh
no,
you're,
good!
That's
weird!
I
can
hear
you
guys:
okay!
Well,
I'm
tim,
apparently
I'm
having
some
connection
issues
today.
Sorry
about
that,
I'm
from
deerwood
minnesota
and
I've
been
super
busy,
just
launched
a
backdrop
city
crm
site
today,
which
is
cool
and
have
another
one
coming.
A
A
E
And
yeah,
I
think
that's
everybody.
A
That's
great
thanks.
Everyone,
before
we
jump
into
our
issue,
queue
I'd
like
to
talk
about
a
couple
of
contributed
projects
that
have
had
new
releases
this
week,
so
we
have
a
new
project,
smart
menu
options,
which
allows
extensions
for
the
smart
menus
library.
A
That's
in
backdrop,
four
also
a
menu
attach
block
module
which
allows
you
to
attach
blocks
into
your
menu
and
leaflet
widget
for
geofield,
which
looks
really
exciting,
and
I
think
last
week
we
mentioned
flag,
clear
and
web
forms
to
be
serum
inner
integration,
but
it
looks
like
they
were
released
on
thursday,
so
I
wanted
to
mention
them
again
in
case
we
didn't
get
to
them
during
our
last
meeting
and
thanks
to
all
of
our
contributors,
to
keep
working
on
importing
modules
from
drupal
and
creating
new
modules.
A
Specifically
for
backdrop,
it's
great
to
see
all
the
activity
that's
happening
in
contrib
all
right.
Let's
turn
it
over
to
nate
to
talk
about.
What's
going
on
in
core.
B
All
right,
well,
a
couple
weeks
ago,
I'd
say
we'll
go
over
the
bug
fix
version
first,
before
we
get
to
the
minor
release
that
code
freezes
for
in
a
couple
of
days,
so
the
bug
fix
version.
We
released
one
18.3
a
couple
weeks
ago.
It
was
a
security
release.
So
118.4
is
our
next
bug
fix
version
that
we
will
be
putting
out
big
thing
that
we
have
on
our
bug.
Fixed
radar
is
php.
8
support
this
year
is
47.72.
B
I
did
take
a
look
at
it
this
week
and
joseph
did
most
of
the
the
beginning
work
on
that.
It
looks
great.
All
of
the
code
that
was
in
the
current
poll
is
in
the
current
pull
request
was
all
pulled
over
from
corresponding
drupal
7
issues.
B
Now
that
lando
supports
php
8
on
my
local,
I
I
just
flipped
lando
to
use
php
8
and
then
rebuilt
and
then
ran
the
tests
through
lando
that
made
checking
things
a
lot
easier,
but
since
we
don't
have
the
test
spot
running
on
php
8,
it's
unclear
how
many
failures
we're
still
getting
on
on
php
but
running
things
locally.
B
There's
still
a
few
or
fair
number
of
of
test
failures,
but
my
perspective
on
this
now
is
that
I
did
a
bunch
more
porting
of
of
issues
from
drupal
7
that
add
php
8
support,
as
well
as
some
additional
fixes
that
drupal
7
doesn't
have
directly
in
core
things.
Like
date,
module
reported
from
contrib
and
there
are
no
php
eight
support
date.
Support
patches
in
the
contrib
module
queue,
so
we
have
to
do
some
of
those
fixes
separately
from
from
what
the
drupal
core
team
is
doing.
B
So
I
compiled
some
of
the
additional
fixes
into
the
existing
poll
request
and
that
gets
us
a
little
bit
further
along
as
to
fixing
full
test
coverage,
but
we
still
have
a
ways
to
go,
and
so
what
I'm
thinking
on
this
now
is
that
some
of
the
remaining
issues
are
particularly
gnarly,
like
they're,
big
they're,
big
patches,
and
so
I
feel
that
we
should
merge
the
pull
request
that
we
have
into
core.
B
The
backdrop
is
usable,
like
you
can
install
backdrop,
all
of
the
normal
functionality
works,
but
there's
probably
some
situations
where
you'll
run
into
an
error
if
you're
running
php,
8
and
backdrop
right
now,
so
I
wouldn't
recommend
that
in
like
a
in
a
production
environment,
but
we
should
merge
that
pull
request
as
is
and
then
make
more
follow-ups,
is
where
I'm
getting
with
this,
and
it
would
be
nice
if
we
could
say
that
the
backdrop
119
is
php8
compatible,
even
though
that
wouldn't
necessarily
be
like
a
like
a
new
feature,
because
it
would
also
go
into
118,
but
the
timing
is
usually
pretty
good
if
we
can
get
a
big
thing
into
the
bug
fix
release
that
corresponds
with
the
new
minor
release.
B
We
can
pitch
it
as
a
minor
release
feature
so
yeah
anyway.
It's
looking
really
good
more
testing
would
be
greatly
appreciated.
On
that
pull
request.
I
don't
think
we
want
to
push
more
fixes
into
it
at
this
point
unless
there's
something
that
you
run
into
like
immediately
after
install
or
doing
a
normal
thing
like
saving
a
piece
of
content
so
and
then
one
bit
and
then
we'll
compile
other
patches
that
still
need
to
be
applied
with
the
objective
of
getting
full
test
coverage.
Passing
on
php
8.
B
All
right
that
also
brings
up
again
that
we
need
to
do
some
work
on
our
test,
bot
our
testing
infrastructure,
to
get
it
so
that
we
can
run
more
versions
of
php
right
now.
We're
only
running
5.3,
like
the
oldest
version
that
we
support
and
php
7,
which
used
to
be
new
and
now
is
quite
old.
So
we
need
to
be
running
like
newer
versions
of
php,
7
and
php
8
now
and
probably
means
that
we
need
to
introduce
at
least
three
php
version
testing,
the
oldest
version
of
php
php7
version
and
a
php.
B
Good
question:
I
think
that
probably
the
latest
version
of
php
is
probably
the
the
latest
version
of
php
7
is
where
we
should
be,
because
php
got
increasingly
strict
from
seven
to
seven
point
one
to
two
three
and
then
four
that
that
if
we
run
the
latest
version
of
php
seven,
I
think
that's
likely
to
cause
the
most
problems,
all
right,
yeah,
I'm
not
sure.
Well,
I
am
sure
that
we
have
an
issue
number
for
that,
but
I'm
not
sure
what
number
it
is.
B
B
That,
okay,
let's
see
and
the
only
other
issue
we
have
slated
for
118
for
that
we're
talking
about
during
these
meetings-
is
47.98
an
issue
with
menu
links.
If
they've
been
translated
into
multiple
languages,
the
active
trail
can
get
confused.
B
A
B
Okay,
let's
see
so
119
119
is
the
next
minor
version
that
we
are
working
on.
It
will
be
coming
out.
May
15th
may
hang
on.
Let
me
double
check
this.
So
may
1st
is
usually
code
freeze
day
it
falls
on
a
saturday
this
year,
which
makes
it
so
that
may
2nd.
The
end
of
the
weekend
on
sunday
is
the
end
of
code
freeze
exactly
when
that
time
is,
is
always
a
little
bit
fuzzy
but
yeah,
probably
in
the
evening
of
of
sunday
may
2nd,
will
be
kind
of.
B
When
we
finalize
like
the
last
changes
in
there,
then
usually
what
that
means
is
that
the
following
day
we
release
the
preview
release,
so
119.0
dot,
pre
or
dash
preview
will
be
coming
out
on
the
third,
and
that
will
be
the
version
that
we
kind
of
encourage
people
to
do
any
testing
on
to
make
sure
that
we
didn't
introduce
any
regressions
before
the
two
weeks
are
up
and
we
release
119
officially
on
the
15th
119
on
the
15th.
B
B
B
So
it's
not
a
bad
issue,
but
it
is
something
that
was
introduced
due
to
the
the
addition
of
this
new
attributes
array
on
css
files.
So
5070
is
that
issue
that,
right
now
it's
only
just
been
filed.
B
We
do
need
kind
of
some
steps
to
reproduce
the
issue,
but
yeah
and
and
we'll
need
a
pull
request.
On
top
of
that,
eventually,
let's
see
next
up
more
features,
exposed
file,
name
filter
for
the
media
library,
dialogue
issue,
3293.
B
B
B
Issue
3293
is
that
issue
that
needs
some
help:
issue
4127
advanced
caching,
that
is,
support
for
cash
tags
and
a
dynamic
cash
max
age.
Header
issue,
4127.
B
joseph,
is
the
advocate
for
this
one.
Let's
see
looks
like
we
haven't
seen
any
updates
on
this
issue.
Recently,
the
pull
request
really
has
been
a
state
of
need
and
review
for
quite
a
while
joseph
do
you
have
anything
that
you'd
like
to
add.
D
B
Okay,
that's
quite
fine
yeah.
I
think
this
one
has
such
far-reaching
repercussions
that
it's
really
unlikely
that
we
would
be
able
to
get
it
sorted
out
in
the
next
couple
of
days
like
this
will
probably
require
not
only
getting
some
adjustments
to
the
code
to
get
it
core
ready,
but
then
extensive
testing
to
make
sure
that
we
don't
have
any
side
effects.
B
Yeah.
Let's
see
next
on
the
list
here,
adding
support
for
relationships
to
layout
contexts,
issue
2134.,
doc,
drumline
is
the
advocate
for
this
one
herb
dual
and
myself
both
gave
this
code
reviews.
Recently
we
both
have
some
minor
suggestions
to
make.
There
was
a
renaming
that
still
hasn't
been
completed
there,
that
just
naming
of
the
class
to
something
else.
B
That
is
a
little
bit
more
specific,
but
I
didn't
in
my
full
re-review
that
minor
renaming
was
one
thing
and
then
I
also
had
a
suggest,
a
suggestion
that
one
of
the
new
functions-
that's
added,
really
should
probably
be
a
method
instead,
and
so
we
just
need
to
move
the
code
from
one
place
to
another.
So
both
of
those
issues
fundamentally
are
naming
convention
issues,
but
that's
it
like.
B
Technically,
there's
no
real
barrier
there
to
getting
that
one
completed,
so
I'm
optimistic
about
21
34
and
I
think
that,
just
with
some
minor
changes
we'll
be
able
to
get
that
one
over
the
finish
line.
B
B
An
issue
has
an
issue
with
the
update
block
on
the
dashboard
that
is
holding
up
the
whole
pull
request
that
the
functionality
to
merge
all
the
update
pages
into
a
single
page
is
has
been
complete
and
has
been
approved
by
several
people,
but
the
dashboard
block
has
a
problem
that
seems
to
be
holding
up
the
works
so
gregory's
route
on
that
one.
B
He
said
that
he
will
just
roll
back
the
dashboard
block
changes
and
we
can
get
in
the
sink,
the
the
single
page
merging,
which
would
be
great
so
that
pull
request
currently
needs
work.
I
know
gregory
has
been
super
busy
if
someone
were
to
pick
that
up
and
do
what
he
has
advised
and
remove
the
dashboard
block
changes
and
make
a
new
pull
request.
That's
just
the
update
pages.
I
bet
that
he
would
appreciate
that
to
get
it
unstuck.
B
Let's
see
and
lastly,
field
has
value
visibility,
condition
issue.
4728
jen
is
the
advocate
for
this
one.
It
says
no
updates.
Is
there
anything
else,
you'd
like
to
add
jen.
B
Okay,
let
me
check
the
119
milestone
to
see
if
there's
anything
else
looks
like
no
okay,
that's
it
for
the
status
of
119
features.
I
mean
we
have
some
features
that
already
got
merged
in.
These
are
the
ones
that
are
outstanding
and
that's
kind
of
where
we
are
between
now
and
sunday.
B
B
Let's
see
next
up
on
the
agenda,
we
have
initiatives,
initiatives
are
longer
reaching
features
that
may
span
multiple
releases,
I'm
going
to
skip
over
documentation
and
ready-to-wear
initiatives,
because
those
are
kind
of
in
the
wrapped
up
state
telemetry
is
the
only
active
initiative,
the
idea
being
that
we
will
collect
usage
and
usage
information
on
people's
backdrop,
sites
and
report
them
centrally
on
backdrop,
cms.org
things
like
php
version,
web
server
version
and
in
the
future
the
way
that
they
like
which
options
they
have
turned
on
or
off
for
certain
features.
B
B
It's
a
little
bit
unlikely
that
such
a
thing
would
occur.
Just
we
I,
I
don't
think
we
really
have
the
time
at
this
point.
B
Yeah
anything
else
tim
that
I
I
haven't
checked
in
on
telemetry.
Otherwise,.
E
B
B
Okay,
we
have
a
couple
of
issues
that
indigozella
raised
in
zulip
that
we
also
could
discuss.
It
looks
like
there's
some
performance
issues
regarding
the
modules
page
so
issue.
5046
is
the
original
issue
that
alan
mels
filed
about
two
weeks
ago
and
it's
a
question
about
the
function
system
rebuild
module
data
which
my
understanding
is.
That
is
the
function
that
recursively
searches,
every
module
in
the
modules
directory,
trying
to
find
what
modules
are
installed
and
on
the
modules
page.
B
That
list
is
regenerated
because,
if
you've
dropped
a
new
module
in
your
modules
directory,
it
should
show
up
on
the
modules
page
when
you
visit
it.
But
it
appears
as
though
from
this
bug
report
that
it
should
only
do
that
refreshing
once
per
page
load
and
that
potentially
it's
doing
it
lots
of
times
per
page
load.
So
alan
mouse
is
describing
this
issue
as
the
there
is
a
static
cache
inside
of
this
function
that
doesn't
seem
to
be
working.
B
B
I
haven't
had
time
to
read
this
whole
issue,
so
I'm
trying
to
summarize
it
real
quickly,
but
it
looks
like
overall
there's
a
problem
here
and
that
it
is
fixable
so
issue.
50
46
is
an
issue
that
could
use
review.
It
looks
like
it
would
really
substantially
increase
the
loading
of
the
modules
page,
which
would
be
great
there's
a
follow-up
issue
that
indigozelle
also
split
off
from
that
it's
issue.
5052
questioning
about
like
should
this
function
be
using
static.
Caching
in
the
first
place,
so
this
follow-up.
B
So
indigozala
is
saying
that
it
really
should
only
be
called
once
per
page
load,
so
it
shouldn't
need
static.
Caching
in
the
first
place,
so
I'm
not
quite
sure
what
the
repercussions
of
that
is
that
the
first
issue
says:
if
we
fix
static
caching,
then
everything
goes
faster.
B
Second
issue,
indigozal
is
saying:
should
we
even
need
static?
Caching
at
all,
possibly
that
means
that
we
shouldn't
have
been
calling
it
multiple
times
in
the
first
place,
so
so
interesting,
two
related
issues.
The
first
one
is
solving
the
performance
problem.
The
second
one
looks
like
it
is
suggesting
that
we
do
some
restructuring
to
make
it
so
that
that
function
shouldn't
be
getting
called
so
many
times
in
the
first
place.
I
think
that
sums
it
up.
Jen
you
looked
at
this
a
couple
hours
ago-
is
that
does
that
sound
yeah.
A
A
But
I
think
the
examples
they
were
testing
were
modules
page,
but
that
function
is
called
a
whole
bunch
of
other
places,
and
so
the
static
cache
might
not
have
been
added
for
the
modules
page,
where
it's
only
called
once
it
might
have
been
added
somewhere
else
where
it
might
be
in
a
loop
and
they
would
kind
of
wanted
to
make
sure
it
wasn't
called
more
than
once.
But
I
haven't
looked
at
all
those
other
17
implementations
or
whatever
they
are,
but
yeah
it
is.
The
caching
issue
is
fascinating.
A
I
also
mentioned
the
other
one
where
we
could
add
some
benchmarks
before
and
after
calling
that
cache.
If
we
can
figure
out
the
other
places,
it's
called
and
see
if
it
makes
a
difference
or
not.
B
Yep
yeah
I'd
love
to
get
some
profiling
on
this
like
just
before,
and
after
with
the
static
cache.
However,
it
seems
like
it'll,
be
pretty
clear
like
if
it's
regenerating
multiple
times
how
that
would
be
detrimental,
because
it's
doing
a
full
directory
recursive
scan
to
try
to
find
modules.
B
I
think
if,
if
we
can
just
show
that
it's
getting
called
multiple
times,
it
would
be
obvious
that,
of
course,
it
would
be
slower
if
it's.
B
A
B
Yeah
we'd
have
to
do
some
scouring
to
see
what
functions,
call
that
function
and
then
work
backwards
and
see
posted.
B
All
right
well
issue,
5046
alan
melz
is
hoping
that
we
can
get
some
more
eyeballs
on
it.
Let's
see
that
was
two
days
ago,
he
was
hoping
for
some
more
feedback,
since
this
hasn't
received
anything
in
the
past
10
days.
B
So
yeah
thanks
to
gosell
for
surfacing
that
as
an
issue
that
we
should
take
a
look
at.
I
do
love
performance
fixes.
I
know
joseph
does
too.
Hopefully
his
ears
are
bringing
a
little
bit
saying.
Oh,
your
performance
fix
it'd
be
great
to
get
your
eyes
on
that
joseph
okay.
I
can
take
a
look
at
that
thanks
so
much
and
that's
it
that's
all
we
have
for
on
the
agenda.
Sorry
kind
of
really
blitzed
through
it
today.
C
D
Into
the
next
release,
it's
issue
3224,
which
is
to,
and
basically
I
made
a
pull
request
for
that
and
what
it
does
is
it
call
it
calls.
It
is
a
module
in
vocal,
for
I
think
it's
hook,
config
create
which
the
field
module
uses
to
trigger
its
creation
of
new
database
tables,
and
what
that
would
do
is
it
would
allow
the
field
module
to
create
new
database
tables
when
you
enable
a
module
that
has
a
field
definition
in
its
config.
B
Yeah,
let's
see
I'm
taking
a
look
at
this
right
now,
maybe
I'll
post
a
comment
on
the
pull
request
actually,
rather
than
talking
about,
because
it's
a
little
yeah
deeply
technical,
I'm
not
quite
sure
what
the
answer
would
be
on
this,
but
yeah.
This
is
a
great
issue.
This
would
help
a
lot
with
the
concept
of
like
recipes
or
install.
B
Or
or
modules
that
include
field
config,
because
without
this,
a
module
that
includes
a
field,
export
won't
create
the
database
tables
and
it
wouldn't
be
particularly
useful,
yeah,
so
yeah.
This
is
a
great
issue.
B
It
is
marked
for
118.4
and
looks
like
it.
The
pull
request
just
needs
review.
B
B
D
B
Okay,
awesome,
okay!
Well
I
guess
maybe
we
should
wrap
it
up
for
today.
Then
thank
every.
Thank
you,
everybody
for
joining.
I
really
appreciate
it
as
always,
and
we've
got
a
couple
more
days
to
get
in
a
couple
more
issues.
Some
things
like
php
8
supports
they're
not
necessarily
held
to
that
deadline,
because
they
can.
It
can
be
completed
anytime
before
the
15th,
but
of
course,
the
sooner
the
better.
So
all
right
anything
else.
D
B
Yeah,
if
you
haven't,
if
you
haven't,
tried
lando,
it's
really
a
good
way
of
of
managing
it.
It
only
took
me
I
had
to
update
lando
to
get
to
the
new
version,
but
it
wasn't
too
bad.
Like
you
know
I
I
know
your
computer
is,
is
totally
bonkers.
My
computer's
new,
but
it's
a
laptop
and
it
can
run
the
whole
thing
with
a
concurrency
of
10
in
about
10
minutes.
So,
okay,
not
not
horrible.
D
So
the
in
in
the
test
suite
when
you
run
it
through
the
command
line
it
can-
or
I
think
I
made
it
so
the
ui
does
this
too.
It
converts
all
the
tables
to
my
isam
inside
a
try
catch
loop
so
that
if
it
fails
it'll
just
not.
B
Error:
okay,
so
I'm
not
actually
sure
whether
it's
doing
it
or
not,
then
yeah.
B
Running
the
normal
backdrop,
recipe
of
lando
and
then
just
swapping
out
the
php
version
to
php
eight
all
right.
D
As
because
on
my
desktop,
it
fails
to
do
that.
For
some
reason,
it
just
doesn't
support
converting
our
tables
to
my
icm,
and
I
don't
know
why.
I
think
it's
something
in
the
my
mariadb
version
that
I'm
using,
but
it
basically
causes
all
schema,
alters
to
be
locking,
and
so
essentially
concurrency
does
nothing.
B
For
me,
yeah,
yeah,
yeah,
okay,
yeah
well
then
great
thing
about
using
lando.
Is
that
it'll
be
the
same
for
both
of
us
right,
so
it
doesn't
matter
what
version
of
my
my
sequel
or
maria
you're
using
because
landa
will
make
it
the
same.
Yeah!
B
Okay!
Well,
thank
you
guys
so
much
we'll
catch.
You
guys
on
the
internet
and
see
you
next
week
post
feature.
Freeze,
okay,.