►
From YouTube: Backdrop Weekly - May 6, 2021
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
Hello
internet,
it
is,
may
6th
2020..
This
is
the
weekly
backdrop
developer
meeting
where
we
get
together
every
week
and
talk
about
the
latest
happenings
in
backdrop.
It's
an
exciting
week
this
week
because
we
are
post
feature
freeze
that
happened
just
on
sunday,
this
past
sunday
and
we
have
a
little
over
a
week
before
backdrop.
119
comes
out
on
may
15th.
A
B
B
C
Yeah,
I'm
olaf
grabianski
from
hamburg
in
germany
and
I'm
a
long
time,
drupal
and
backdrop
user
site
builder,
mainly
and
also
a
member
of
the
pmc
for
a
year.
I
guess
and
yeah
I'm
curious
what
is
happening
in
these
days.
A
Okay,
we
also
have
doc
welmont
andy
shellingford,
joining
with
us
lurking
right
now,
but
not
not
in
a
place
to
to
talk
so
great
to
have
everybody
here
we
will
go
on
to
project,
can
or
sorry
sorry
section
of
the
agenda.
First
thing
we
normally
cover
is
updates
from
the
pmc.
A
C
A
Okay,
thanks
a
lot
contributed
projects.
In
the
last
week,
we've
had
four
new
contributed
projects
have
their
first
releases
for
backdrop,
that
includes
a
port
of
the
image
magic
module
happy
to
see
that
ajax
comments,
module,
geoip
tokens
and
profile
registration
path.
Modules
are
four
new
modules
that
just
came
out
in
this
past
week
for
backdrop.
There
also
were
several
project
updates.
A
I
think
we
had
an
additional
five
modules
have
releases
this
week,
besides
those
always
great
to
see
continuing
activity
moving
forward
and
contrib,
and
thanks
to
all
of
our
contrib
authors,
who
are
out
there
making
modules
for
backdrop,
all
the
time
we'll
go
right
into
the
project.
The
core
project
update
our
current
state
of
things,
as
I
mentioned
in
the
beginning,
is
that
we're
in
this
short
period
in
between
the
feature?
A
Freeze
that
happens
the
first
of
the
month
before
the
release
of
backdrop
that
happens
every
four
months
so
may
15th
is
the
scheduled
release
date
for
may
or
for
for
the
119
version.
We
don't
see
any
reason
why
we
wouldn't
come
out
at
that
date
as
planned.
A
The
current
state
of
things,
let's
see.
Well,
let's
start
with
what
happened
with
the
issues
that
didn't
get
completed,
so
we
made
a
new
milestone
1.20,
which
will
be
the
next
version
of
backdrop
that
will
come
out
in
september.
A
The
carried
over
issues
that
didn't
get
into
119
include
exposing
a
file
name
filter
for
the
media
library
dialogue
issue
3293.
There
are
just
some
technical
challenges
there,
with
the
way
that
the
media
dialog
is
set
up.
A
That
makes
that
a
little
bit
challenging
the
advanced
caching
functionality,
adding
cache
tags
and
a
dynamic
cache
max
age
header
that
joseph
has
been
working
on
issue
4127
that
got
pushed
primarily
because
we
didn't
have
time
to
review
it
and
check
all
of
the
the
the
changes
that
it
it
makes,
which
has
far-reaching
implications
for
all
of
backdrop,
and
we
didn't
have
enough
time
to
review
those
changes.
I
should
say
that
yeah
we
didn't
have
reviewers
in
time.
A
I
should
say
there
was
plenty
of
time
for
the
issue,
so
no
no
faulting
on
joseph
there,
just
on
the
reviewers
such
as
myself,
that
didn't
have
time
to
look
at
it
and
lastly,
field
has
value
visibility,
condition
and
a
an
addition
to
layout
module
to
make
it
so
that
fields
would
provide
conditional
well
conditionals
to
hiding
and
showing
particular
blocks
issue.
A
4728
jen
lampton
was
taking
a
look
at
this
one,
but
I
don't
think
that
a
pull
request
ever
materialized
for
that
issue,
so
those
three
items
were
advocated
issues
that
got
bumped
into
the
next
release.
1.20,
we'll
probably
want
to
evaluate
if
those
things
are
feasible
for
this
next
release
and
either
take
them
off
the
slate
or
continue
pushing
for
them
to
get
completed
in
the
next
release.
A
A
We
pushed
forward
and
completed
three
of
the
remaining
features
that
we
were
hoping
to
get
in,
including
adding
support
for
relationships
to
layout
contexts,
issue
2134.,
doc.
Welmont
was
the
advocate
for
this
one
and
really
made
it
so
that
we
could
get
all
of
that
to
to
well
from
nothing
into
existence.
A
I
I
put
in
some
last
minute
reviewing
on
it.
So
did
herb
herb
duel
and
together
we
kind
of
got
that
one
over
the
finish
line
looks
great.
We're
super
excited
about
it.
The
new
functionalities
is
super
awesome.
A
It
lays
the
groundwork
for
a
lot
more
functionality,
though,
that
we
only
added
one
relationship
out
of
the
box
in
core
right
now,
and
that
is
the
ability
to
get
a
a
node's
author,
the
user
context
of
the
author
from
a
node
there's
lots
of
other
possibilities
for
relationships,
though
things
like
getting
the
file
entity
off
of
a
file
field,
taxonomy
terms
lots
of
potential
options
there,
so
we
have
some
definitely
have
some
follow-up
work
to
be
done
there,
but
the
base
functionality
of
relationships
is
now
in
core
which
is
very
exciting.
A
Let's
see,
there's
also
a
follow-up
issue
related
to
that
there's,
a
very
minor
ui
change
that
we're
trying
to
work
on
that.
Where
you
add
a
relationship
in
the
the
layout
ui,
there
there's
a
link
directly
above
it
that
says,
add
context
and
then
below
it.
There's
the
link
for
add
relationship,
the
new
button
and
the
way
that
these
are
printed
right
now
they
are
both
in
an
unordered
list
separate
and
they
should
be
in
one
unordered
list
side
by
side.
A
Instead,
so
it's
a
pretty
minor
ux
issue,
but
it
has
some
complexities
in
getting
it
fixed.
There's
an
issue
for
that
issue:
50
74,
that
is
kind
of
a
follow-up
for
that
that
we're
hoping
to
get
completed
in
the
next
couple
of
days
before
119
comes
out
very
minor,
though
we
also
got
in
the
issue
that
gregory
was
advocating
for
the
combat
combining
of
the
modules
themes
and
layouts
update
pages
into
a
single
page
issue.
2714..
A
I
like
this
issue
a
lot
because
it
makes
it
so
that
there's
like
less
clutter
on
things
like
the
modules
page
and
on
the
layouts
page
that
previously
there
was
a
multiple
tabs
up
at
the
top
for
listing
the
available
layout
templates,
installing
new
layout
templates
and
updating,
layout
templates
and
honestly
updating,
layout
templates,
updating
themes,
it's
kind
of
a
less
common
action
and
it's
making
noise
on
the
page
plus
you
had
to
go
to
three
different
places
to
check
for
updates
across
all
of
your
different
things,
whether
they
were
themes
or
modules
or
layout
templates.
A
Now,
there's
only
one
page
and
you
can
do
all
the
updating
from
that
one
new
page,
so
27
14
is
that
issue
number.
I
think
that
we
had
also
talked
a
little
bit
about
splitting
off
some
changes
to
the
dashboard
block
that
we're
holding
up
that
issue
for
months.
A
A
A
But
then
there
is
a
menu
item
for
system
and
inside
of
system
is
stuff
like
site
information
like
the
site
name
and
cron,
and
there
was
some
discussion
about
like
what's
the
difference
really
between
system
and
developer,
because
where
this
new
page
ended
up
was
under
system
there's,
some
argument
that
perhaps
it
should
have
been
under
developer,
like
is
updating,
are
updating
modules
and
themes.
A
developer
action
anyway.
A
A
But
I
don't
know,
there's
a
lot
of
things
to
to
look
at
regarding
like
what
are
these
things
actually
doing
so
anyway.
C
C
C
A
Yeah,
I'm
sure
that
if
we
got
into
it,
I
would
love
to
just
rant
a
little
bit
about
the
site
information
configuration
page.
And
what
exactly
is
that
page
trying
to
do?
Because
it's
like
the
site
title
and
the
site
slogan?
Okay,
that
site
information
for
sure.
But
then
it
also
is
responsible
for
what
the
paths
of
your
404
and
like
403
pages
are.
A
How
is
that
related?
That
is
clearly
like
very
developer
oriented
like
what
happens
when
you
go
to
a
404
page
as
opposed
to
what's
the
name
of
your
site.
One
of
these
questions
every
site
has
to
answer.
The
other
question
is
complete
edge
case,
so
putting
them
on
the
same
form.
Just
I
don't
know
it's
just
the
the
the
legacy.
You
know
the
baggage
that
we've
had
from
that
site.
A
Information
page
has
existed
since
the
dawn
of
drupal
really,
and
so
I
think
that
it's
just
kind
of
there's
there's
never
been
a
better
place
to
put
those
settings,
and
maybe
maybe
there
could
be
yeah
anybody
else
want
to
chime
in
on
just
their
random
thoughts.
On
those
pages.
C
That's
also,
I
think,
a
question
if
we
focus
on
people
coming
from
drupal
or
with
drupal
experience
or
or
on
new
people,
because
for
new
people
it
doesn't
make
many
sense,
but
many
of
us
are
so
yeah.
C
We
know
this
like
four
years,
and
so
if
we
change
it,
it
has
to
be
really
good
because
we're
so
used
to
it
and
every
time,
for
example,
when
I
switch
to
drupal
8
and
I
want
to
make
a
database
back
up,
I
look
in
system
because
I'm
so
used
to
it,
and
so,
in
my
opinion,
it
has
to
be
really
a
good
solution
and
if
we
change
it
because
many
people
come
from.
A
A
A
Okay
well
anyway,
that
was
all
spun
out
from
this
27-14.
The
updates
pages.
I
definitely
like
one
page
instead
of
three
different
pages
reduces
noise,
makes
everything
all
in
one
place
improvements
all
around.
A
That's
also
related
to
all
this
is
within
the
installer
module,
which
just
generally,
is
good
to
see.
Some
cleanup
happening
in
the
installer
module
that
module
was
moved,
not
exactly
wholesale
out
of
contrib,
but
it
definitely
was
like
put
in
functionality
first
and
then
like
let's
revisit
and
clean
up
later.
So
I'm
really
appreciative
to
see
some
of
that
cleanup
coming
to
pass.
A
Let's
see
and
lastly,
something
that
we
finished
up
over
the
code.
Sprint
is
initial
php
8
support,
so
that's
issue.
47.72,
the
initial
pull
request
has
been
merged
that
incorporates
a
lot
of
joseph's
work.
To
make
backdrop
just
like
install
and
function
correctly,
there
are
some
major
changes
needed
regarding
the
database
abstraction
layer
that
the
way
that
it
was
set
up
it
just
does
not
work
with
php8,
and
so
the
initial
patches
fix
the
database
layer
fix
some
other
notices
that
happen
basically
on
every
single
page
load.
A
We
also
had
some
backdrop
specific
fixes
that
needed
to
happen
because
of
date,
module
in
particular
was
something
that
had
a
lot
of.
A
Differences
from
drupal
because
in
drupal
land
they
don't
have
date,
modules
part
of
core
like
having
a
backdrop
date
object,
for
example,
the
backdrop
date.
Object,
extends
the
php
date
time
object
and
that's
where
a
lot
of
api
changes
have
occurred.
So
so
we
had
to
change
the
way.
The
date
time
object
worked
quite
a
lot
which
changed
a
lot.
How
the
database
objects
worked
quite
a
lot
because
they
also
were
extending
pdo
settings
or
pdo
objects
from
php.
A
So
anyway,
it
took
a
lot
of
work,
but
the
initial
pull
request
gets
backdrop
working.
You
can
run
the
tests
about
95
of
them
pass,
but
there's
still
some
edge
case
functionality
that
isn't
quite
working
on
php
8.
As
of
yet
we
decided
not
to
put
it
into
the
118
release
because
it
has
pretty
far-reaching
consequences.
A
So
we
only
put
it
into
the
119
branch
so,
instead
of
it
being
a
bug
fix
which
technically
is
because
it's
just
adding
support
for
php
eight,
that's
a
bug
not
supporting
it.
A
We
decided
to
only
put
it
into
119
because
it
has
kind
of
some
far-reaching
changes
to
some
of
the
the
deepest
levels
of
the
apis
of
of
backdrop.
So
that
is
to
say,
119
is
now
feature
complete.
A
A
It
includes
all
of
the
new
features
as
far
as
we
know
there
aren't
any
substantial
bugs
in
it.
But
that's
why
we
have
the
preview
releases
to
have
this
two-week
period
for
like
trial
testing
it
out,
seeing
if
there's
any
problems
so
that
we
can
get
those
issues
resolved
before
the
official
release
comes
out
on
the
15th.
A
Let's
see
there
was
that
minor
change
regarding
the
layout
ui.
That's
the
only
follow-up
that
we
have.
We
also
had
another
follow-up.
The
indigozella
raised
regarding
a
new
feature
that
we
added
in
to
backdrop
add
css
the
issue.
The
regression
issue
is
50
70
that
got
fixed
over
the
code
sprint
as
well.
A
Final
preparatory
tasks
that
we
have
for
119
include
the
blog
post.
We
have
to
draft
up
a
blog
post
listing
out.
All
of
the
changes
that
are
in
119..
Tim
usually
takes
that
on.
I
don't
think
that
we've
assigned,
or
had
a
volunteer
for
that
officially
yet,
but
we'll
try
to
get
that
in
place.
A
A
You
can
check
that
for
any
other
things,
that
there
are
none,
no
other
things
right
now,
but
if
there
are
other
things
that
get
pushed
into
like
emergency,
we
need
to
fix
this
before
we
make
the
release,
that's
where
they
would
be
under
the
119
milestone
on
github.
A
Usually
during
this
little
week-long,
lull
is
actually
what
it
is,
because
we
can't
put
in
new
features,
while
the
119
branch,
sorry
before
the
119
branch
is
actually
created.
So
right
now
the
latest
version
of
backdrop
1.x
is
going
to
be
119.,
so
for
the
next
couple
of
weeks
or
next
10
days,
we
won't
be
merging
in
any
new
features
because
we
haven't
branched
yet
for
the
1.20.
A
So
what
that
usually
means
is
that
now
is
the
perfect
time
to
go
bug
squashing,
so
118
is
actually
where
118
4
is
the
next
milestone
for
bug
fixes
and
if
you're
looking
for
things
to
do,
checking
the
118.4
milestone
is
the
best
place
to
go
to
try
to
find
things
to
fix
in
the
meantime,
so
bug
squashing
is
usually
what
happens
in
this
window.
Even
if
they're
not
bug
specific
to
the
new
version.
A
A
A
32
24
module
config
is
not
synced
on
install
and
joseph
raised
this
issue
as
being
important
that
if
a
module
wants
to
include
fields
that
we
need
to
fire,
these
config
hooks
so
that
the
related
database
tables
get
created
on
the
installation
of
the
module,
and
this
would
be
helpful
for
the
effort
to
make
it
so
that
backdrop
could
have
recipes
recipe
modules
where
you
turn
them
on
and
a
whole
swath
of
functionality
comes
over
from
the
config
directory,
so
issue
3224.
A
It
already
has
a
pull
request.
It's
been
tested
pretty
positively,
but
doc.
Belmont
is
absolutely
correct
that
we
need
some
automated
tests
to
get
test
coverage
on
this
new.
Not
quite
sure,
if
it's
actually
a
new
feature
but
on
this
bug
fix.
A
Also,
an
exciting
change
that
is
in
progress
is
issue:
50
46,
it's
a
performance,
related
issue
that
alan
mels
pulled
up
relating
to
the
admin
modules
page,
that
it
has
some
slowness
on
it,
because
it
has
a
recursive
file
system
check
that
is
getting
executed,
multiple
times
per
page,
and
it
really
only
needs
to
be
executed
once
so.
A
This
issue
5046
substantially
speeds
up
the
loading
of
the
modules
page,
which
is
pretty
great,
so
we
need
some
additional
review
on
this
issue,
50
46
for
anyone
that
has
the
time
available.
A
A
Oh
shoot:
it's
not
sorry,
it's
actually
118
4,
not
118.3,
sorry,
so
I'm
checking
118,
for
we
had
a
performance
fix
that
happened
this
past
week.
That
is
worth
mentioning
issue.
50
28.
A
joseph
found
an
issue
that
there
is
a
kind
of
an
obscure
function,
called
field
sync
field
status,
and
this
function
is
part
of
field
module
that
checks
to
see
whether
or
not
fields
are
turned
are
enabled
or
disabled
or
not,
and
it
also
has
to
do
with
like
cleaning
up
deleted
menu
entry
or
deleted
fields
and
and
things
of
that
nature,
so
fields,
sync
field
status.
Although
an
obscure
function,
it
gets
called
every
time.
Qran
is
run
every
time
caches
are
cleared
and
every
time
a
module
is
enabled
or
disabled.
A
So
three
pretty
common
use
cases,
especially
cron,
and
the
cache
clearing
he
found
that
this
function
also
gets
called
once
for
every
module
in
the
system,
and
it
really
only
needs
to
get
called
once
total,
and
so
this
performance
optimization
substantially
sped
up,
cron
runs
and
cash
clears,
which
is
great,
so
big
thanks
joseph
for
your
work
on
issue,
5028
really
exciting
to
see
that
in
great
performance
optimization
there
every
time
we
have
these
performance
optimizations,
I
get
there's
a
certain
part
of
me
that
really
just
absolutely
loves
them.
A
Like
performance
engineering
is
a
large
part
of
my
job,
and
so
I
I
feel,
like
backdrop
already
is
really
fast.
I
think,
especially
if
you
look
over
in
the
the
world
of
drupal,
where
things
are
not
fast
at
all.
I
just
get
but
like
making
backdrop
even
faster.
I
just
feel
like
you
know
it
just
it's
already
really
fast,
so
I
love
making
it
even
faster.
A
Just
certain
part
of
me
that
makes
me
so
happy
even
compared
to
wordpress
wordpress
is
slow
and
pokey
compared
to
the
speed
of
backdrop
like
it's
just
really
really
exciting.
I
love
seeing
that.
A
All
right:
well,
I've
been
talking
for
quite
some
time
now.
That's
the
end
of
the
updates
for
118
119
and
the
upcoming
120.,
I'm
gonna,
take
a
break
here,
pause
see
if
any
of
those
present
have
anything
they'd
like
to
add
or
talk
about
anything
before
we
go
on
to
like
initiatives
which
won't
take
very
long.
A
No
okay,
well
initiatives.
Initiatives
are
long-running
projects
that
span
multiple
releases.
Potentially,
the
only
initiative
that
we
currently
have
active
is
telemetry.
A
Telemetry
is
an
initiative
that
we'd
like
to
have
a
module
that
is
installed
on
backdrop,
sites
that
reports
backtobackdropcms.org
various
information
about
how
backdrop
is
configured
so
that
we
can
make
better
decisions
about
the
direction
of
the
project
and
so
the
initial
implementation.
We
just
collect
really
basic
statistics
like
the
php
version,
what
web
server
people
are
running
and
the
database
version,
so
those
three
things
are
in
the
initial
proof
of
concept
for
telemetry.
A
A
We
have
the
the
server
side
module
that
extends
project
module
that
we
would
install
on
backdrop
cms.org
next
steps,
for
this
primarily
are
making
some
server-side
enhancements
to
make
it
so
that
if
backdropcms.org
gets
sent
information
that
we
don't
want,
such
as
stuff
from
a
contrib
module,
then
we
discard
that
information
and
don't
save
it.
We
don't
want
to
get
into
situations
where
backdrop
cms.org
might
be
unwittingly.
A
Collecting
personality
personally
identifiable
information
from
modules
that
we
haven't
vetted
and
so
making
sure
that
we're
not
collecting
too
much
information
is
something
that
we
need
to
do
on
the
server
side
and
on
the
client
side,
we
need
to
work
the
new
telemetry
module
better
into
the
backdrop
installation
process.
So
right
now,
when
you
install
backdrop,
we
have
these
two
check
boxes.
A
Says
I
can't
remember,
actually
notify
me
of
security
updates.
I
think
check
for
updates
and
notify
me
for
security
updates,
and
I
think
that
that's
the
notify
me
for
security
updates
is
important
because
we're
sending
somebody
email,
even
though
it's
their
own
site,
sending
them
email
and
what
we'd
like
to
change
that
to
is
always
check
for
updates
by
default,
but
instead
replace
that
with
a
checkbox
that
says,
send
anonymous
information
to
backdropcms.org.
A
However,
we'd
also
like
to
make
it
so
that
you
can
have
your
site
check
for
updates,
but
not
report
your
module
versions
to
backdrop
cms.org,
so
that
one
checkbox
would
do
two
things.
It
would
either
enable
and
disable
the
telemetry
module
and
it
would
change
the
setting
and
update
modules
to
whether
or
not
your
site
was
recorded
in
the
usage
statistics
or
not,
but
updates
should
always
update.
Checking
should
always
be
enabled
it's
just
a
matter
of
whether
or
not
a
user
would
want
their
site
to
be
recorded
or
not.
A
So
that's
that's
the
changes
that
we'd
like
to
see
to
move
telemetry
the
telemetry
project
forward.
It's
been
stuck
kind
of
for
a
while
now
you
know,
we've
been
shifting
our
attentions
to
the
119
release,
but
now
is
a
great
time
to
get
back
into
the
telemetry
initiative,
because
119
is
now
feature
complete.
A
That's
all
I've
got
for
today's
update
on
everything
backdrop.
We
have
a
section
at
the
end
we
usually
allow
for,
like
q,
a
if
you
guys
have
anything
you
guys
would
like
to
talk
about
on
the
recording.
Now
would
be
the
time
so
I'll
open
the
floor.
A
A
Okay,
thanks
all
right.
Well,
I
think
that
we
will
end
the
official
meeting
then
thank
you
all
for
joining
the
meeting.
Thanks
to
all
of
our
backdrop,
community
members
that
have
been
rushing
towards
the
end
of
the
feature
thaw
and
we
had
a
really
successful
sprint
lots
of
participation,
and
I
really
appreciated
all
of
that
last
minute
effort
as
well.
So
thanks
everybody
out
there
we're
excited
about
the
119
release
coming
out
10
days
and
yeah,
we'll
see
you
guys
around
on
the
internet.
So
thanks
everybody
bye,.