►
From YouTube: Backdrop Weekly - Dec 24th, 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
All
right
we're
online,
it
is
december
24th,
and
this
is
our
weekly
developer
check-in
meeting
before
we
jump
into
the
agenda.
Let's
go
around
and
do
some
introductions
I'll
start,
I'm
john
lampton
joining
from
oakland
california,
and
very
excited
about
all
the
progress
everyone
else
has
been
making
on
backdrop
for
lately.
So
thank
you,
everybody.
Let's
kick
it
to
me
next.
B
C
I
actually
did
a
little
module
developing
this
week
that
I've
dipped
my
toes
into
a
little
bit
working
on
the
switch
theme
module
adding
a
piece
to
it.
So
let
me
throw
it
over
to
justin.
D
E
Greg
yeah
hi,
I'm
greg,
usually
in
australia,
but
now
joining
from
greece
interested
in
anything.
That
has
to
do
with
backdrop
and
in
any
way
that
I
can
help
joseph.
A
Yep
all
right
so
since
our
last
meeting
people
have
been
going
bonkers
in
contrib,
we
have
a
ton
of
new
projects,
including
google,
auth
search,
api
search
pages,
solar
search,
random
front,
page,
simple
api
paragraphs,
jquery,
ui
accordion,
published
content,
snazzy
real
name
and
faq
field,
and
most
of
those
were
done
by
robert
lang
and
ray
burgess.
So
thank
you
both
for
all
of
your
amazing
prolific
module
creation.
B
All
right,
so
first
thing
we'll
go
over
is
117.5.
The
current
bug
fix
release
that
we
are
working
on.
B
There
is
one
regression
that
has
been
in
place
since
we
added
my
sql
eight
supports
and
one
seventeen
two
that
is
issue
4745,
that
database
prefixes
do
not
work
when
doing
queries
across
databases,
and
this
particularly
affects
civic
crm
and
the
views
integration
looks
like
jen
added
rtbc
to
the
to
the
issue
there.
So
that
looks
great
that
we
could
potentially
proceed
with
that
approach.
B
So
that's
good
next
up
is
regression
on
field
set
css.
The
collapsible
css
in
the
seventh
theme
is
a
little
bit
wonky
at
times,
and
the
issue
is
47.66
currently
has
a
pull
request
that
needs
review.
That
seems
to
fix
the
problems
with
collapsed
field
sets
so
that
looks
great
next
up
is
site
stuck
in
maintenance
mode
issue.
B
3956.
This
happens
when
you
update
a
module
through
the
ui.
Of
course,
you
can
just
turn
off
the
maintenance
mode
and
that's
fine,
but
it'd
be
good
to
get
that
fixed.
B
B
Let's
see
next
up
set
reasonable
max
input
vars,
this
is
not
the
correct
title
should
be
throw
a
warning
if
max
input
farce
is
not
set
properly.
Is
this
issue
still
going
back
and
forth?
Looks
like
there
hasn't
been
any
updates
in
the
past
week.
B
Okay
and
lastly,
adding
automated
code
checks,
issue
30
to
13
still
no
issues
or
progress
on
this
item,
we'd
like
to
use
github
actions
more
extensively.
B
Actually
I
guess
we
don't
have
any
so
we'd
like
to
introduce
the
use
of
github
actions
to
do
automated
code
style
checking,
but
currently
we
don't
have
any
any
progress
on
that
on
that
approach,
I
think
the
issue
that
we
ran
into
mostly
was
we
need
other
things
besides
just
core
to
run
the
the
code
checks,
and
so
where
do
we
put
those
things
and
how
do
we
download
them
into
the
actions
is
kind
of
the
sticking
point.
B
That's
it
for
the
117.5
milestone.
Do
you
guys
have
any
other
bug
fixes?
You
guys
would
like
to
bring
up.
E
I
think
there's
an
issue
that
integra,
I
don't
have
a
ticket
number
I'll,
find
it
that
idi
goes
ella's
been
working
on
with
how
numbers
are
being
calculated
so
for
sorry,
the
validation
for
numbers
numbers
for
decimals.
E
E
It's
just
that!
There's
too
much.
The
testing
has
to
do
with
math,
which
is
nice
and
not
hard,
but
the
possibilities
of
what
the
test
are
endless.
So,
especially
when
it
comes
to
decimals
so
yeah.
I
think
it's
pretty
close,
though
it
seems
that
it's
working
for
people.
B
What's
the
summary
of
the
current
problem
with
the
validation.
E
B
E
E
B
E
Actually,
maybe
I'm
not
indicating
discuss
again
so
the
issue
number
is
37.92
single
decimals
failed
to
pass
validation
and
into
godzilla
has
had
a
request
up
been
improving
on
it,
team
tested
and
lauren
tested
as
well,
and
they
both
have
it
marked
as
words
for
me.
We
just
need
a
code
review.
B
Okay,
that's
it
for
the
current
bug
fixes,
of
course,
there's
lots
of
other
issues
in
the
117.5
milestone,
there's
still
seven
rtbc
issues,
although
I
did
see
bw
panda,
had
been
going
through
and
merging
a
couple
of
things
this
week,
which
is
great
but
there's
still
additional
rtbc
issues
that
we
can
work
through.
There's
also
65
open
issues
in
the
117.5
milestone,
which
honestly
65
issues
seems
a
little
bit
less
than
before.
B
I
think
we
haven't
been
adding
as
many
things
to
the
bug
fix
milestone
as
we've
done
so
well,
it's
just
nice
that
that
number
has
been
decreasing.
I
think
the
the
items
that
we,
the
number
of
items
we
had
in
the
bug
fix
milestone
like
two
or
three
releases
ago,
was
like
upwards
around
90
or
so
so.
We've
been
working
downwards
on
the
items
that
are
tagged
for
the
next
bug,
fix
release,
which
is
great,
of
course,
there's
there's
always
more
so
118.
118
is
the
next
minor
version
of
backdrop.
B
It's
right
around
the
corner.
Feature
freeze
for
118
is
january,
4th,
that's
the
first
week
day
after
the
holiday,
so
january,
1st
or
the
first
before
the
release
is
usually
when
we
have
code
freeze
and
if
that
lands
on
a
holiday,
then
we
move
it
to
the
first
non-holiday
day
afterwards.
So
it's
january
4th
this
year,
the
actual
release
will
be
january,
5th
or
sorry,
15th
january
and
yeah
that
that
will
be
the
next
version.
B
So
we've
got
a
number
of
features
that
are
currently
closing
in
on
completion
or
at
least
making
a
lot
of
progress,
so
we
can
go
through
each
one
of
those.
First
one
is
the
newest
issue
that
we've
added
herb
dual
is
advocating
for
an
option
to
skip
deleting
the
staging
config
files
after
running
the
config
sync,
the
issue
is
4447..
B
It
is
looking
really
good.
It's
marked
works
for
me.
It
does
what
it's
it
says.
It's
going
to
do
the
only
thing
that
has
test
coverage,
even
the
thing
that
is
lacking
here
is.
We
just
need
an
update
hook
to
set
the
default
value
of
that,
even
though
it
defaults
to
false
and
having
it
not
be
present
results
in
the
same
functionality
as
it
being
absent.
We
should
still
have
an
update
hook
to
set
that
value
just
so
that
we
don't
have
any
unexpected
like
oops.
This
thing
was
null
instead
of
false
issues.
B
A
B
Even
worse,
yeah
so
definitely
needs
an
update
hook.
What
either
way.
A
But
it's
amazing:
I've
been
using
it
on
the
site
that
I've
been
doing
config
syncs,
both
from
dev
to
the
server
and
the
server
down,
and
it
has
made
like
the
amount
of
times
I
don't
have
to
type
get
checkout
staging
is
making
me
so
happy,
I'm
just
like.
Oh
my
gosh.
I
think
I've
got
like
hours
of
my
life
back
from
having
this
patch,
so
I'm
really
excited.
B
B
B
It
looks
like
everything
is
working
currently,
but
the
code
needs
some
review
and
if
I
recall
it
had
some
kind
of
questionable
things
in
the
way
that
it
was
built
out,
it
works,
but
it
seems
like
it's
a
little
bit
hacky,
so
this
could
use
some
additional
code
review
and
feedback
on
the
way
that
it
functions.
E
B
E
Yeah
so
indie,
gosella
and
others
have
been
testing
it.
It
works
as
expected,
but
then
indie
gazelle
pointed
out
that
we
have
the
updates
block
the
available
dates
block
in
the
dashboard.
So
I
this
was.
This
also
had
links
to
both
the
the
available
updates
reports
page
and
the
installation
page.
So
it
was
listing
every
single
project
that
had
an
update
and
it
was
pointing
to
the
respective
update
modules,
update
themes,
update
layout
space.
So
now
it
wouldn't
make
sense
for
every
listing
in
the
page,
to
point
to
the
same
thing.
E
So
I've
added
a
single
link
change
the
style
of
the
block
to
resemble
the
being
in
a
on
a
table.
Instead,
the
the
only
problem
now
is
that
there's
a
failure,
a
test
measure
and
it's
reproducible-
the
code
that
the
block
uses
is
the
same
as
the
the
code
that
is
being
used
to
generate
the
list
or
the
update
page,
and
it
all
point
boils
down
to
the
update
get
available
function.
E
I
was
using
that
without
it
has
a
flag
which
is
called
refresh
and
it
probably
defaults
to
false,
so
even
setting
it
to
true
doesn't
solve
the
problem.
So,
even
if
I
refresh
the
data,
the
last
comment
by
idigozella,
which
is
basically
install
an
out
of
date
intentionally
out
of
date,
module
go
to
the
run.
E
Chrome
go
to
the
updates,
the
dashboard,
the
update
block,
looks
just
fine,
but
if
you
then
disable
and
install
the
sorry,
this
yeah
disable
and
install
the
module
when
you
visit
the
dashboard
page
without
running
chrome
or
checking
for
updates
again,
it
just
presents
the
list
with
an
empty
with
empty
names
and
things.
It
could
be
something
in
the
logic
but
yeah.
That's
that's
the
bit
that
works,
so
my
the
feedback
that
I
want
for
that
is.
Should
we
leave
that
for
a
follow-up.
B
Is
this
issue
with
the
update
block
an
existing
problem
that
we've
just
discovered
or
is.
E
E
No,
it
doesn't
it
doesn't.
It
doesn't
the
the
the
pr
and
the
state
that
it
was
initially
before
the
problem
with
the
the
sorry,
not
the
problem,
but
the
styling
issues
with
the
dashboard
block
were
mentioned
and
then
andy
gozale
said
it
would
be
nice
to
get
this
fixed
at
the
same
time
so
that
it
matches
the
the
single
page
that
we're
introducing,
which
is
a
great
idea
right.
But
then
breakage
has
started
happening
and
I
can't
pinpoint
what's
working
differently
in
the
layouts
page
in
the
dashboard
page.
E
B
Up
all
right,
let's
see
next
up,
is
adding
a
setting
for
setting
where
the
break
point
occurs
for
the
hamburger
menu.
It's
issue
46
4663,
this
one
is
proceeding
nicely
it's.
Let's
see.
I
saw
that
bw
panda
noted
something
in
zulip,
saying
that
it
had
one
small
issue,
but
indigozella
said
that
it
looks
like
it'll
be
easy
to
fix
so
currently,
as
mark
needs
review,
but
I
think
there's
one
additional
item
in
there.
B
B
Lastly,
or
not,
lastly,
changing
the
name
of
full
html
into
raw
html
issue.
44.99
tim
is
the
advocate
for
this,
although
he
couldn't
make
the
meeting
today,
it's
marked
rtbc,
and
this
is
just
changing
the
label
of
that
text-
format
in
the
standard
profile.
B
That's
the
only
change
that
actually
does,
but
he's
gone
through
and
updated
all
of
the
documentation
and
everywhere
that
we
reference
the
label
raw
or
full
html,
and
so
that
one
is
on
the
cusp
cusp
of
completion:
let's
see
advanced
caching,
adding
cache
tags
and
cache
max
age
to
core
issue.
4127
joseph
has
been
working
on
this.
Do
we
have
any
updates
this
week,
joseph.
F
Not
a
lot,
I've
been
working
on
the
actually
implementing
the
changes
in
the
core,
and
I
created
a
branch,
although
I
haven't
created
a
pull
request
yet
because
it's
it's
not
actually
ready.
Yet
I
came
up
with
what
I
think
is
a
solution
that
will
work
which
is
rather
than
rather
than
implementing
these
into
the
main
cache
func
class,
creating
another
cache
class
that
wraps
that
one
and
then,
if
you
need
to
disable
cache
tags
for
any
reason,
you
can
just
switch
back
to
the
old
one
or
if
you
want
to
use
a
different.
D
F
Yeah-
and
I
was-
I
made
a
new
interface
for
basically
a
taggable
cache
backend
that
extends
the
interface
for
a
normal
cache
backend
and
changed
the
method
signatures
and
it
seems
to
be
working
so
like
I'm
hoping
that
I
don't
have
to
change
that.
F
I
think
that's
it.
Okay,
it's
still
probably
still
gonna
take
a
little
while
before
I
finish
that.
B
A
We
talked
about
it
last
week,
but
essentially
it
is
a
condition
that
lets
you
check
if
a
field
has
a
specific
value,
and
so
if
you're
on
a
node
specific
layout,
you
can
say
is:
does
the
image
field
contain
preview.ping
or
whatever,
and
it's
based
off
of
a
panel's
visibility,
condition
that
didn't
make
it
into
layouts
duckwell
wrote
a
contrib
module
that
handles
it.
A
So
if
anyone
needs
it
urgently,
you
can
use
that
and
it's
we're
trying
to
figure
out
how
to
give
it
a
slightly
better
user
interface
than
is
in
the
contrib
version.
I've
got
a
stab
at
it
for
core,
but
it
doesn't
do
the
visibility.
Checking
that
the
conversion
does
we
sort
of
have
to
take
the
best
of
both
the
user
interface
and
the
functionality
and
put
them
together.
D
B
Well,
that
does
it
for
the
118
milestone.
Do
you
guys
have
any
other
issues
that
have
been
surfaced
that
we
have
missed
here.
E
Just
mentioning
that,
if
we
merge
teams
the
issue
that
team
is
advocating,
maybe
he
can
focus
and
advocate
for
a
smaller
another,
smaller
future
in
the
next
week.
Maybe
an
easy
win
so.
C
B
Into
the
easy
win
portion
of
the
release
as
well
that
this
is
when
we
wrap
up
the
things
that
we're
working
on
or
not,
and
then
we
like
pivot
to
all
of
the
easy
things
that
that
need
a
minor
version
so
yeah.
Well,
I'm
sure
that
there
will
be
something
new
by
next.
B
Meeting
next
up,
we
have
initiatives.
We
can
run
over
them
really
quickly
because
I
think
theme
development
normally
gets
done
during
the
design
meetings.
I
know
outreach
was
this
week,
but
luke
do
you
want
to
give
us
any
update
on
the
ready
to
wear
initiative.
C
Sure
sure
I'll
I'll
do
it
quick.
I
I've
been
bouncing
back
and
forth
with
with
tim,
putting
together
sort
of
the
the
site.
That's
going
to
be
basically
the
initial
mvp
deliverable
for
it.
I
I
finally,
this
week
you
know,
did
something
I've
been
pondering
for
a
while,
which
was
was
do
actual
module
coding
in
the
switch
theme
module,
because
I
want
a
different
interface.
I
wanted
a
bulleted
list
rather
than
a
pop-up
menu
for
the
things
and.
C
It's
helping
me,
you
know,
make
it
not
suck
to
some
extent,
but
but
I'm
I'm
optimistic,
I
I
I
want
to
bring
this
home
before
the
end
of
the
year.
Do
we
have
we
have
one
more
meeting
right
or.
C
E
B
B
Let's
see,
let's
see,
we've
got
the
telemetry
initiative
as
well.
That
telemetry
is
where
we're
trying
to
collect
information
about
how
people
are
using
backdrops,
so
we
can
base
decisions
upon
it.
We
haven't
had
any
update
on
that
or
any
progress
on
that
recently.
B
I
was
saying
before
the
meeting
started.
I've
been
doing
some
of
the
development
on
that
and
I've
got
a
big
open
stretch
of
vacation
in
front
of
me.
So
when
I'm
not
doing
the
code
reviews-
which
I
think
will
take
up
the
bulk
of
my
time,
if
I
have
an
opportunity
to
push
anything
forward,
I'll
be
helping
on
telemetry
the
next
step.
B
There
is
we're
hung
up
on
testing
that
it's
it's
hard
to
test,
and
I
think
that
we
could
clear
things
out
substantially
if
we
install
if
we
merge
the
changes
into
project
module
and
then
install
the
new
version
of
project
module
on
backdrop
cms.org,
and
that
would
make
testing
a
lot
easier
because
we
can
just
use
backdrop
cms.org
the
final
location
as
the
testing
location.
And
then
we
can
send
data
to
it
and
make
sure
that
everything's
all
all
coming
in
okay.
A
Sounds
really
good
greg
and
I
have
some
other
issues
for
project
module.
We
might
want
to
get
wrapped
up
too
if
we're
going
to
be
pushing
stuff
to
backup
seamless
or
we
could
test
like
the
promoted
modules
thing
and
stuff,
so
that
could
be
fun.
B
Yeah,
I
imagine
project
module.
I've
actually
seen
a
couple
of
things
stack
up
there,
so
when
we
make
that
when
we
put
it
in
the
work
home
project
module
we'll
probably
also
run
through
the
issue,
queue.
B
A
The
devel
module
has
a
couple
of
php
php7
issues
and
there
are
merge
full
requests
there,
but
it
needs
a
new
release
if
you
have
extra
time
on
your
hands.
B
Okay,
let's
see
documentation,
also
an
initiative,
I'm
not
sure
when
this
one
was
added,
but
jen
or
gregory.
Do
you
guys
know
if
this
was
pmc
approved
at
some
point
in
in
the
recent
past.
E
Well,
it's
not
official,
but
it
should
be
one
of
those
long-term
things
ongoing
things
I
should
say-
and
we
discussed
previously
in
the
outreach
meeting-
that
there
were
some
people
that
mentioned
they
couldn't
find
points
or
our
documentation.
A
handbook
in
the
main
site
was
mentioning
things
that
either
got
renamed
or
they
weren't
there
anymore.
So
in
general
we
should
there's
people
that
are
going
through
the
documentation
and
they
maybe
they
don't,
have
author
access
to
update
it.
E
One
of
them
is
service,
free
and
then
team,
and
I
are
also
keen
on
soliciting
more
help
from
the
community,
because
recommendation
is
always
like
an
adding
screenshots
or
things
like
that
is
always
like
a
an
easy,
a
relatively
easy
task.
It
doesn't
require
coding,
but
still
requires
time
and
effort,
and
if
people
have
the
energy
they
can
help
us,
and
the
other
thing
is
that,
as
we've
had
regular
releases,
there's
new
features
that
we
added
since
the
documentation
was
written
and
we
haven't
gone
back
to
update
the
documentation
with
those
added
features.
E
One
thing
that
we
discussed
that
maybe
we
need
your
input.
Your
thoughts
make
with
regards
to
that
is
that
I
mentioned
that.
Drupal
has
certain
gates
before
a
feature
gets
seen,
and
the
the
general
consensus
from
the
previous
meeting
seem
to
be
that
we
shouldn't
be
holding
out
features
just
because
recommendation
is
not
ready
because
we're
a
smaller
community
and
that
might
take
longer.
E
And
also
yeah
to
the
point
to
answer
your
question:
is
that
yes,
sorry,
no,
it
hasn't
been
officially
approved
by
the
bmc,
but
this
one
will
not
require
sort
of
like
coding
assets.
B
Yeah
related
to
documentation
jen,
you
did
some
documentation
work
this
week
on
the
api
site.
Is
that
something
that's
relevant
here.
A
It's
not
related
to
this,
but
I
think
I
I
ended
up
on
some
issue
where
I
think
greg
you
and
might
have
been.
Opie
were
talking
about
how
we
removed
the
not
front
class
in
backdrop,
and
so
I
went
to
go
to
the
theme
page
to
add
the
doc
block
that
you
recommended.
That
was
like.
A
Oh,
if
you
want
this
back,
here's
how
to
do
it,
and
when
I
got
to
the
theme
porting
the
theme
page,
it
was
left
over
from
like
before
we
added
the
bootstrap
layouts
to
core,
and
so
there
was
a
lot
of
stuff
there.
That
can
be
done
differently
now,
and
so
I
added
a
whole
bunch
of
text
to
that
page.
I
just
fell
into
the
rabbit
hole.
It
was
like.
A
A
But
then,
when
I
went
to
that
section,
I
realized
that
it
referred
to
the
layouts
as
layouts
and
not
layout
templates,
and
then
so
I
started
updating
all
the
documentation,
so
it
was
layout
templates
and
then
the
next
thing
you
know
like
four
hours
have
gone
by
and
I'm
like.
Oh
my
gosh,
I've
just
been
documenting
stuff,
but
it
felt
good
to
get
it
updated,
but
it
was
not
relevant
to
anything
else.
It
was
just
a
rabbit
hole.
If
I
went
to.
E
Do
we
have
flexible,
layouts,
layout
templates?
Sorry,
I
should
say
documented
or
not.
E
Yeah,
so
I
don't
think
we
do
see.
This
is
one
of
the
features
that
yeah
it's
it's
huge
and
it's
like
yeah.
We
have
the
api
pages
on
how
people
can
code
layouts
themselves,
but
there's
an
easier
way
to
do
it
via
the
ui
yeah,
and
we
haven't
exposed
that.
As
far
as
I
know,
maybe
maybe
someone
did
but
not
aware
of.
A
B
Okay,
well,
let's
call
it,
then
those
are
all
the
items
that
we
have
for
the
initiatives.
Do
you
guys
have
any
last
questions
or
anything
else?
You
would
like
to
bring
up
I'm
trying
hard
to
finish
before
midnight.
Gregory.
B
Okay,
all
right!
Well,
let's
wrap
it
up.
Then.
Thank
you,
everybody
for
joining
us
on
this
holiday
of
christmas
eve.
We
really
appreciate
it.
We'll
see
you
guys
all
next
week
on
new
year's
eve,
so
I
mean
not
making
assumptions
we
will
be
meeting
next
week
on
new
year's
eve
feel
free
to
join.
If,
if
it
suits
you
so.
B
Everybody
out
there
thank
you
for
for
working
hard
on
backdrop,
especially
all
those
new
contrib
modules
that
came
in
very
exciting,
and
thank
you,
everyone
for
yeah,
for
putting
in
all
of
your
work
and
for
spending
your
holidays
with
us.