►
From YouTube: Backdrop Weekly - 2021/03/04
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
march
4th,
and
this
is
our
weekly
developer
check-in
meeting
before
we
jump
into
the
agenda.
Let's
go
around
and
do
some
quick
introductions.
I'll
start,
my
name
is
john
lampton,
I'm
joining
from
oakland
california.
I've
been
very
busy,
mostly
with
backdrop
stuff,
which
is
exciting,
and
I'm
looking
forward
to
looking
over
today's
agenda.
So
let's
turn
it
over
to
nate.
B
Hey
I'm
nate
lampton,
also
oakland,
california
and
yeah.
I
almost
have
caught
up
with
things
in
the
rtbc
list,
which
is
exciting
for
me,
and
there's
lots
of
activity
happening
that
we
will
be
talking
about.
Let's
go
to
joseph.
If
you
could
give
us
a
little
intro.
C
Hi,
I'm
joseph
I'm
from
las
vegas
nevada
back
in
developer.
Doing
actually
not
a
lot
of
backdrop
stuff
recently,
but
yeah
just
here
to
see
how
I
can
help
jason.
D
D
E
Hi,
I'm
tim
erickson,
st
paul
tim.
I
am
in
deerwood,
minnesota
and
totally
focused
on
backdrop,
live
and
sort
of
outreach
stuff
right
now,
so
just
haven't
really
been
in
the
issue
very
much.
So
I
don't
have
a
lot
to
add
to
that
this
week.
But
anyways
everybody
come
to
backdrop
live
next
friday,
jason
did
we
get
you.
A
All
right,
let's
see,
we
have
a
couple
of
new,
contributed
modules.
This
week
I
was
very
excited
to
see
classy
paragraphs
come
in
earlier
this
week,
so
that's
a
module
that
lets.
You
add
a
specific
class
to
your
paragraphs,
which
makes
it
nice
nice
tool
for
integrating
with
styles.
In
your
theme,
jitsi
meet
field,
which
is
exciting.
That
looks
like
a
probably
new
for
backdrop:
module
that'll
integrate
directly
with
titsy,
so
you
can
open
up
a
link
directly
from
somewhere,
which
is
pretty
cool
and
font.
A
Your
face
good
old
trusty
drupal
module
got
imported
over
this
week
too,
with
the
first
stable
release
for
tasks
related
to
backdrop,
cms.org
websites,
we
have
ongoing
issue
number
487.
In
the
backdrop,
cms.org
queue
for
supporting
more
information
about
a
module
or
theme
or
layout
in
info
file.
Documents
done
a
bunch
of
work
on
that
in
the
last
week.
A
A
You
can
go
there
and
register
for
backdrop,
live
which
is
happening
in
a
week
and
we
have
the
donation
form
up
so
the
way
it
works
right
now
is
first,
you
register,
and
then
it
redirects
you
to
a
donation
form
where
we
ask
you
to
make
a
donation,
but
if
you
cannot
afford
to
you
can
skip
the
last
step
and
then
I
think
that's
it
for
backdrop,
cms
or
properties,
there's,
obviously
a
bunch
more
stuff
that
we're
trying
to
do
everywhere,
and
I
would
encourage
anyone
who
wants.
C
E
B
All
right
product
updates,
118
is
our
current
release.
Of
fact,
118.1
and
118.2
will
be.
The
next
bug
fix
release
that
we
are
going
to
be
putting
together.
We
went
through
a
bunch
of
issues
this
week.
I
think
we
he
now
have
11
issues
merged
into
118.2.
B
I
was
just
looking
over
an
issue
that
indigozella
filed
earlier
this
week.
That
field
sets
can
sometimes
can
now
look
funny
in
the
latest
version
of
firefox
that
it
looks
like
we
actually
had
a.
B
So
thanks
for
taking
that
one
on
indigo
ozil,
that's
let's
see
what
issue
is
that
that
is
issue
49
71
that
is
already
rtbc.
So
I'm
looking
forward
to
getting
that
one
in
big
issues
that
we've
got
the
ck
editor
maximize
button
can
cause
content
to
be
unable
to
be
saved
issue
49.33.
B
We
do
not
have
any
development
yet
on
that
help
is
being
sought
to
get
that
problem.
Fixed,
probably
javascript,
related
issue.
B
Let's
see
next
up
language
names
are
not
translated
into
their
native
names
issue:
45
11..
That
issue
was
merged
this
week.
That
does
add
some
additional
api
capabilities
to
language
objects,
so
that
now
languages
have
their
name
as
they
are
written
in
english,
and
now
they
also
have
the
name
as
they
written
in
the
that
language.
B
So
that
is
still
it,
although
merged
in
it's
not
closed
yet
because
we
need
a
change
log
record
describing
that
new
capability
indigozo
took
a
stab
at
drafting
that
which
was
appreciated.
We
need
to
get
that
copied
over
into
the
docs
site
for
reference
next
up
is:
is
there
a
question
there?
No
okay.
Next
up
is
php
8
support
issue,
4772
joseph
put
in
a
bunch
of
work
on
this
a
couple
of
months
ago.
Now
it
still
needs
review
and
some
additional
testing.
B
It's
a
lot
easier.
Now
that
php
8
is
a
little
bit
more
widely
available,
including
on
lando,
which
can
help
local
testing
of
backdrop.
So
if
you
have
an
php,
8
environment,
we
would
love
it.
If
you
could
do
some
some
testing
there,
let's
see
and
lastly,
menu
active
trail,
gets
confused
when
the
same
path
is
used
in
menu
links
for
multiple
languages
issue
4798.
B
This
is
this
is
an
issue
that
has
a
pull
request
that
fixes
the
problem,
but
it
needs
test
coverage.
B
That's
it.
Those
are
the
items
that
we've
got
pulled
out
of
118.2
as
being
relatively
priority
issues.
However,
there
are
currently
79
issues
tagged
with
118.2,
so
that's
an
awful
lot
of
issues
that
we
could
potentially
get
in
much
sooner.
B
B
The
first
issue
that
we
have
in
the
119
milestone
to
discuss
is
a
changing
of
the
pads
issue:
48.99
the
role
edit
role,
menu
path,
we're
changing
that
to
be
configured
to
add
consistency
with
the
rest
of
the
paths
and
backdrops
that
use
configure
for
editing,
configure
sorry
for
saving
configuration
and
edit
for
editing
content,
so
that
pull
request
has
been
merged.
B
There
was
a
derivative
issue
related
to
that
that,
although
we've
changed
the
paths
from
edit
to
configure
in
the
event
that
those
paths
also
contain
wild
cards
such
as
the
name
of
the
role,
those
wild
card
pads,
are
not
redirected,
and
so
there's
a
sub
issue
for
this
2833
that
I've
picked
back
up
as
something
that
we
could
get
fixed
sooner
rather
than
later.
So
I
rerolled
that
pull
request.
Yesterday,
john
franklin
gave
me
a
pull
request
review
on
that
almost
two
years
ago,
which
was
very
helpful.
B
I
took
that
feedback
and
finally
incorporated
all
of
the
changes
there,
and
I
think
that
issue
is
now
ready
to
be
reviewed,
which
would
be
great,
there's
actually
a
lot
more
wild
card
redirects
now
than
there
were
at
the
times.
That
issue
was
originally
opened.
I
think
that
in
updating
that
pull
request,
there's
now
it
moved
from
like
three
wild
card
redirects
to
like
12
wildcard
redirects.
B
Lauren
is
the
advocate
for
it,
and
we've
tried
a
couple
of
approaches,
but
we've
hit
snags
in
those
current
approaches.
So
we
need
to
start
a
new
with
an
approach
that
solves
an
underlying
issue
with
having
nested
form
tags,
one
inside
of
the
other
there.
B
So
as
simple
as
that
sounds
it
actually
turned
into
something
that
is
a
little
bit
gnarly.
B
Next
up
is
advanced
caching,
adding
cache
tags
and
a
dynamic
cache
max
age.
Header
issue,
41
27.
joseph,
is
the
advocate
for
this.
It's
been
in
needs
review
for
quite
some
time.
I
have
not
had
a
chance
to
take
a
look
at
it
yet,
and
I
don't
think
there
have
been
any
comments
on
that
recently.
B
Okay,
yeah,
sorry,
I'm
on
a
little
bit
of
a
roll
here
and
I'll
pause
for
a
minute
here
to
let
jen
talk
about
her
next
issue,
which
is
ad
field,
has
value
visibility,
condition
issue
47-28.
B
B
B
E
B
B
B
B
The
the
status
of
that
issue,
though,
is
that
it's
still
in
development,
and
I
think
that
we're
just
basically
in
a
holding
pattern,
while
gregory
continues
to
work
on
that
issue.
B
B
However,
I
took
a
look
at
the
milestone
candidate
minor.
These
are
the
issues
that
people
think
should
be
added
into
a
near
release
of
backdrop,
but
have
not
officially
had
candidates
added
and
have
not
have
not
officially
had
a
an
advocate
added
and
so
they're,
not
in
the
the
next
milestone,
but
there's
56
of
them.
B
So
it's
quite
a
large
collection
of
features
that
we
would
like
to
see
in
the
near
future,
and
I
I
would
say
that,
if
you're
out
there
looking
for
an
issue
to
advocate
for
that's
a
really
great
place
to
take
a
look
under
the
milestone
candidate
dash
minor
tag
on
github
plus,
it's
also
great
to
just
go
through
that
list
and
see
yeah.
There
are
a
lot
of
things
that
are
rather
important
that
we
get
done,
and
maybe
some
that
aren't.
Maybe
we
could
clean
that
list
up
a
little
bit.
B
B
Initiatives,
initiatives
are
the
next
section
that
we
are
we
talk
about
every
week,
and
initiatives
are
long
spanning
projects
that
aren't
necessarily
tied
to
a
particular
release.
We
have
the
unofficial
initiative
for
documentation.
B
F
Yes,
I
saw
that
jen
had
set
up
feeds
to
copy
content
from
backdrop
cms.org
to
the
new
documentation
site.
I
have
a
look
and
I
think,
there's
some
tweaking
needed.
Like
the
sorry,
I
wanted.
A
I
pushed
an
update
to
that
after
the
fact
price
I
added
a
new
field
called
legacy
nid
and
use
the
node
id
on
the
old
site,
because
that
made
me
nervous
too.
So,
hopefully,
that
should
be
working
off
of
the
new.
The
new
unique
field
now.
F
Okay
yeah,
I
just
took
a
look
at
the
first
time.
I
saw
it
so
I'll
have
another
look
so
yeah.
So
now
that's
sort
of
copying
content
over.
I
think
we
just
need
to
then
work
out
how
to
set
up
the
menu
structure.
So
all
those
new
nodes
can
be
visible
on
the
new
dock
site,
and
I
was
wondering
how
to
go
about
that
like
if
we
want
to
make
a
change
to
documentation
like
someone
finds
a
typo
or
something
if
we
change
it
on
the
doc
site.
A
So
if
we
change
like
a
node
title
or
node
body,
it
would
be
reverted
when
this
stuff
comes
in.
But
if
you
add
it
to
a
menu,
it
shouldn't
be
changed.
A
We
could
so
there's
a
special
handling
for
what
you
want
to
do
when
updates
happen
on
the
source
file
and
right
now,
it's
just
set
to
overwrite
them,
but
we
could
probably
fiddle
with
that.
If
we
wanted
to
like
overwrite
the
body,
but
not
the
titles
or
something.
So
let
me
know
how
you
want
to
handle
that
and
we
can
account
for
it.
F
A
F
A
F
Oh,
the
other
thing
was
the
formatting
and
images
and
stuff
weren't
being
copied
over
at
least
the
first
time
I
looked
at
it.
I
don't
know
if
that's
been
changed
since,
but
when
I
compared
a
node
on
backdropsine.org
and
then
the
same
node
on
the
dock
site,
the
docks
that
was
basically
just
plain
text,
where
the
other
one
had
like
headings
and
images
and
formatting
and
stuff.
A
Yeah
I
so
I
set
up
a
new
text
format
on
the
docs
site,
but
I
did
not.
I
don't
think
I
configured
it.
So
that's
probably
why,
like
headings
and
stuff
are
missing,
I
should
probably
compare
those
to
make
sure
it's
the
same
and
then
images
I
did
not
copy
over.
So
we'll
need
to
see
where
the
images
were
on
the
old
site
and
copy
that
directory
over.
A
I
think
it's
probably
something
like
I
don't
know,
but
we'll
need
to
copy
the
images
over
and
I
need
to
make
sure
that
the
file
references
in
the
nodes
get
updated
so
we'll
need
an
update
hook
for
that
yeah.
A
B
All
right
thanks
peter
and
thanks
jen,
then
the
next
initiative
to
discuss
is
telemetry
collecting
the
way
backdrop
is
used
on
actual
sites
and
then
reporting
that
information
back
to
backdrop.
Cms.Org
tim,
you
are,
you,
are
the
initiative
lead?
Can
you
fill
us
in.
E
Sure,
as
I
posted
in
the
agenda
again,
no
updates,
I
think,
we'll
see
if
we
can
fit
that
into
the
backdrop.
Live
agenda
somewhere
to
maybe
do
a
report
on
where
we're
at.
B
And
lastly,
the
ready-to-wear
initiative
that
luke
mccormick
had
been
heading
up.
That
initiative
is
winding
down.
Work
is
being
done
on
a
final
report
that
will
include
some
recommendations
for
the
future
for
the
future,
but
other
than
that
it
is
pretty
well
complete.
That's
it
do
we
get.
Do
you
guys
have
anything
you
would
like
to
discuss
as
just
general
status
of
backdrop
banter
anything.
E
Well,
since
there's
some
time-
and
it
came
up
in
zulu
this
week-
we
could
talk
briefly
about
the
survey
that
we
did
about
things
that
people
wanted
to
see
in
backdrop,
and
some
people
are
now
saying
so.
Okay,
what
do
we
do
with
the
results
and,
as
we've
said
many
times
there
were,
there
was
never
any
promised
action
on
the
results
other
than
that.
E
Hopefully
it
was
useful
information
that
could
help
us
all
shape
where
we
put
our
our
focus
and
our
ideas,
but
I
think
in
and
well
I
don't
know
that
we're
we're
in
a
position
to
like
okay,
we're
going
to
take
our
number
one
on
that
list.
There
might
be
some
things
we
could
do
to
sort
of
help
from
a
discussion
perspective
move
those
issues
forward.
E
So
I
was
thinking
that,
maybe
over
the
course
of
the
next
few,
you
know
one
thing
we
could
do
that
wouldn't
be
a
huge
commitment
is
just
take
like
the
top
five
issues
in
that
survey
and
spend
some
time
talking
about
them.
One
are
they?
Are
they
actual
desirable
things
to
have
in
core?
How
big
are
they?
What
would
it
take
to
get
them
moving?
E
You
know,
I
don't
have
it
open
in
front
of
me
right
now,
but
I'm
going
to
it
quickly.
That's
what
like
the
top
five
were.
E
Number
one
was
field
group
functionality.
Decor
number
two
was
allow
multiple
file
image.
Uploads
number
three
was
that
reference
module.
Decor
number
four
was
add
a
recipe
project
type
to
backdrop
and
then
for
number
five.
We
have
a
three-way
tie,
add
an
icon
font
to
core
automatic
updates
and
expose
fields
to
visibility
conditions.
E
So
a
few
of
these,
I
think,
are
already
being
worked
on
and
have
substantial
progress
made.
At
least
one
of
them
is,
like
totally
vague,
add
add
recipe
project
type
to
backdrop,
that's
like
an
idea
that
what
that
would
look
like
you
know,
there's
a
lot
of
thought
that
would
have
to
go
into
that.
So,
but
it's
also
one
that
interests
me.
So
I
don't
know
any
thoughts
on
how
we
might
again
without
you
know,
without
the
resources
to
like
necessarily
a
a
mandate
focus
on
any
of
these.
B
One
idea
is
that
well,
one
idea
is
that
if
we
can
get
these
issues
completed,
that
we
talk
about
every
week,
that's
eight
advocates
that
then
could
take
up
another
issue,
and
so
I
I
think
that
we're
creating
our
own
bottleneck
in
a
way
that
we're
saying
that
everybody
can
only
advocate
for
one
issue
at
a
time
which
I
I
don't
think
is
a
bad
policy,
but
I
I
think
that
also
in
a
way
is
actually
discouraging
people
from
working
on
issues
generally,
if
they're
not
the
advocate
for
them,
you
know
if
they
can't
actually
add
it
to
the
next
minor
milestone.
B
So
I
guess
one
thing
I
I
would
say
is
that
you
know.
Perhaps
we
can
simply
encourage
people
to
pick
up
issues,
even
if
they're
not
an
advocate,
and
even
if
they're,
not
in
the
119
milestone
and
then,
if
it
came
down
to
it,
they
could,
you
know,
remove
themselves
from
one
issue,
add
themselves
to
another
issue,
and
then
that
would
change
where
our
focus
is.
When
we
talk
about
things
on
a
weekly
basis,
yeah
because
you're
not
wrong-
that
lots
of
these
issues
actually
already
have
really
pretty
solid
starts.
B
Like
reference
modules,
you
know,
there's
a
couple
of
different
approaches
in
contrib.
Multiple
file.
Uploads
is
something
that
doc
wilmot
worked
on
a
long
time
ago,
and
then
I
picked
up
for
a
little
while,
and
that
issue
is
actually
surprisingly
far
along
as
well.
B
E
B
Yeah,
we
we
put
in
yeah
a
lot
of
a
lot
of
great
work
there
too,
and
we
have
even
templates
on
which
we
can
base
further
work
like
there's
an
automatic
updates
initiative
in
drupal.
That's
also
been
happening,
although
mostly
and
can
trip,
but
there
is
now
an
automatic
updates
module
for
drupal
7
that
we
can
use
as
a
model
to
actually
get
through
the
last
remaining
hurdles
there,
which
I
think
primarily
is
how
do
we
run
update.php,
which
is
something
I
haven't
figured
out
yet.
E
B
E
Well
I'll
to
tie
this
to
back
and
make
another
plug
for
backdrop
live
next
week.
One
thing
that
can
happen
is
people
can
take
any
of
these
issues
and
suggest
a
discussion
about
them.
I
we,
I
know
we
had
really
good
discussions.
We
had
a
really
good
discussion.
I
thought
about
the
reference
module
at
the
last
backdrop,
live
which
was
just
you
know,
sort
of
about
like
what
work
needs
to
be
done,
and
I
think
we
have
some
good
notes
that
came
out
of
that.
We
just
haven't
got
anybody.
E
That's
undertaken
to
do
the
work,
but
this
is
you
know,
and
I
I
plan
to
do
it
to
talk
about
recipes,
because
that's
something
I've
been
doing
a
little
bit
of
work
on
and
contribute.
E
So
I'd
like
to
talk
about
that
in
backdrop
live
and
maybe
for
now
that
work
that
belongs
and
can
trip,
but
I
need
some
help
figuring
out
what
what
the
right
approach
is.
I've
just
experimented
like
with
one-
and
I
like
other
ideas.
F
Another
quick
question:
go
for
it!
Sorry
if
this
was
addressed
in
the
other
meeting
or
before
I
joined,
but
is
there
anything
happening
with
the
database?
Clear
log
button
issue
thingy
for
the
pmc.
E
Did
we
did
we
open
an
issue?
Yet?
John?
I
don't
know,
I
don't
know
I
don't
I
don't
remember.
We
should
check
yeah
we'll
check
the
the
pmc
has
had
a
little
more
activity
than
usual,
so
we're
sort
of
ramping
up
to
get
some
work
done.
So
that's
at
least
hopeful,
but
yeah
it's
been
a
little
bit
slow
there
in
the
bmc.
F
Peter,
can
you
remind
the
on
the
database
log
page
which,
like
the
watchdog
page,
it
has
the
button
to
clear
all
log
messages,
and
there
was
a
long
ongoing
discussion
about
where
that
button
should
be
at
the
top
of.