►
From YouTube: Backdrop Weekly Meeting - April 1, 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
Let's
see,
even
though
we're
a
bit
of
a
small
crew
today
we
can
go
ahead
and
do
introductions.
I'm
nate
lampton
from
oakland
california,
court
committer
and
I
don't
have
anything
to
bring
up
today
that
isn't
on
the
agenda.
Gregory.
B
B
A
All
right,
let's
see,
updates
from
the
pmc
gregory
your
only
resident
pmc
at
the
the
meeting
in
this
meeting.
I
know
that
there
is
a
in-person
pmc
in
person
by
live
meeting
happening
tomorrow
to
address
a
number
of
things
that
have
been
creeping
up.
I
don't
know
if
there's
anything
really,
that
should
be
publicly
noted,
but
I
guess
we'll
have
a
bunch
of
things
to
be
publicly
noted
after
the
meeting
occurs.
Is
that
right.
B
Yeah,
so
that's
that's
the
on
the
announcement
for
now,
just
a
small
base,
again
things
to
be
finalized
and
links
to
be
added
everywhere.
Is
that
we
sort
of
like
finalize
the
decision
of
adding
the
a
link
to
the
code
of
contact
into
the
actual
product
which
has
happened.
There's
a
mesh
request,
there's
no
actual
release
of
backdrop.
B
That
includes
it
in
the
readme
as
we
speak,
but
the
next
bug
fix
release
and
the
next
major
sorry
minor
release
will
include
it
and
we're
looking
on
ways
to,
on
the
best
way
to
add
a
link
to
the
code
of
contact
on
the
main
side
as
well.
A
B
And
we
have
some
tasks
and
ideas
of
tweaking
and
improving
it
a
little
bit
further
and
the
reason
why
it's
on
a
github
repo
is
that
we
track
changes
and
then,
if
there's
major
changes
done
not
just
typos
or
anything,
we
plan
to
communicate
those
changes
to
people
with
announcements
so
that
there's
transparency,
yep.
A
There's
also,
it's
not
quite
pmc,
it's
not
a
pmc
announcement,
but
it
is
an
announcement
in
the
lesson
that
is
that
the
timing
of
these
meetings
that
happen
every
week
will
be
changing
starting
next
week
so
april
8th.
A
We
have
shifted
to
use
the
same
time
year
round
that
things
will
be
at
hang
on.
Let
me
double
check
this.
It
was
also
in
the
newsletter
that
was
sent
out
earlier
this
week,
which
is
the
design
meeting,
is
8
pm
utc
same
as
the
outreach
meeting
they
just
alternate
weeks
and
then
the
developer
meeting.
A
That's
this
one
is
at
9
00
pm
utc,
and
I
think
what
that
means
is
that
this
meeting
for
those
of
us
in
north
america
is
going
to
change
times
next
week,
and
I
think
that
means
I'm
not
even
going
to
say
it
because
I
don't
know
which
direction
it
moves,
but
do
the
conversion,
because
utc
does
not
acknowledge
daylight
savings
time,
so
it
will
change
during
the
summer
and
the
idea
is
that
by
using
utc
globally,
it
makes
it
so
that
we're
not
giving
preferential
treatment
to
a
particular
area
of
the
world,
because
right
now
we've
been
scheduling.
A
These
meetings
always
based
upon
the
united
states
time
zone
handling,
which
is
different
than
everywhere
else's
time
zone
handling.
So
this
will
make
it
so
that
it's
not
actually
like
consistent
for
everybody.
Now
it's
basically,
everybody
is
equally
going
to
be
off
like
disrupted
by
this,
because
everybody
has
some
kind
of
daylight
savings.
It's
just.
They
have
different
daylight
savings.
So
anyway,
it's
an
experiment
and
we're
gonna
see
how
it
pans
out.
B
Yeah,
it
was
more.
People
in
australia
basically
were
affected
by
one
hour
moving
one
hour
forward
or
back
and
then
after
a
week
or
two
they
would
move
another
one
one
hour
so
yeah.
So
what
we're
doing
is
we
are
spreading
the
effects
of
the
daylight
savings.
A
Okay,
let's
see
also
just
speaking
of
that
newsletter
that
came
out
is
really
excellent.
If
you
haven't
signed
up
for
the
newsletter,
you
can
do
that,
of
course,
through
the
the
backdrop
homepage,
but
you
can
get
a
link
to
the
latest
newsletter
from
the
agenda
notes.
I
posted
a
link
there.
It's
really
great
right
up
on
what's
been
happening
in
the
backdrop
world
just
generally,
and
also
pulling
out
a
couple
of
nice
blog
posts
that
have
been
written
recently.
A
All
right
community
updates,
we
don't
have
any
new,
contributed
projects.
This
week,
however,
there
have
been
update,
updates
to
contrib
projects,
photoswipe
instagram
feed,
php,
excel
mosaic
grid
and
chosen
modules
all
had
new
releases
this
week,
so
I
definitely
see
and
appreciate
the
ongoing
maintenance
that
has
been
going
on
by
our
buyer
community
members.
A
Let's
see
backdrop
cms,
we
recently
released
backdrop
118,
2
and
all
of
the
flagship
sites
are
all
of
the
sites
that
are
running.
Backdrop
have
all
been
updated
to
the
latest
version.
Justin
just
last
night
went
through
and
did
server
updates,
just
updating
all
of
our
software,
the
underlying
software
on
the
lynodes
we
had
been
having
some
swamp
issues
related
to
maintaining
download
usage
and
thanks
to
justin's
wizardry
configuring,
php
and
server
adjustments.
A
That
seems
to
have
now
been
mitigated
and
solved
for
the
time
being
anything
else,
you'd
like
to
bring
up
about
server
updates,
justin.
A
Yeah,
that's
right.
We
had
at
one
point
ci.backdropcms.org
a
server
that
we
decommissioned
a
while
back,
but
we
had
a
dns
entry
that
was
still
pointing
at
that
ip
address
and
leonard
reallocated
that
ip
address
to
someone
else.
So
then
we
had
our
domain
pointing
at
someone
else's
site,
which
was
not
what
we
wanted.
I
I
don't
even
think
it
was
is
actually
slight,
but
we
noticed
that
it
was
pointing
at
something
that
wasn't
ours
and
you
cleaned
that
up
too,
which
we
appreciate.
A
Thank
you,
okay,
that's
it
for
community
and
website
updates.
We
can
move
into
the
product
updates.
So
this
week
it's
been
pretty
quiet
on
my
side
of
things.
118.3
is
the
next
bug
fix
release.
We
just
came
out
with
118
2
the
week
before,
and
118
3
items
will
be
aggregated
into.
You
know
the
next
release
and
merge
when
ready.
A
A
jenna's,
been
pushing
jen
lampton
has
been
pushing
for
this
issue
for
a
couple
of
months.
I
have
a
feeling
she's
gonna,
have
a
new
fire
lit
regarding
this
issue,
because
she
just
got
bit
by
again
on
one
of
her
drupal
7
projects,
which
means
that
instills
a
new
sense
of
rage
and
hurt
to
get
it
fixed
within
backdrop.
A
A
We
have
a
pull
request
that
joseph
has
been
had
put
up
quite
a
while
ago.
Php
8
is
now
much
more
widely
available
on
a
variety
of
platforms,
and
this
should
make
testing
a
lot
more
easily
accessible.
A
The
pull
request
currently
needs
review,
and
it
has
been
that
way
for
a
while
now
so
we're
in
a
little
bit
of
a
review
bottleneck
and,
lastly,
there's
an
issue
with
the
active
trail,
the
breadcrumb
handling,
if
you
have
a
translated
menu
that
has
links
to
the
same
piece
of
content
in
different
languages,
issue
4798
this
one
actually
has
a
pull
request
that
works.
It's
just
missing
test
coverage.
B
Since
we're
talking
about
php
8
support,
I
might
as
well
bring
up
issue
nine
three
one
has
to
do
with
my
sequel
eight.
So
there
seems
to
be
a
breaking
change
that
has
happened.
I
think
after
eight
zero
nineteen
1980
22
one
of
the
versions
which
manifested
itself
as
a
an
issue
with
translated
translation
of
file
names.
In
on
backdrop,
we
didn't
see
anything
else
breaking,
but
the
issue
now
is
that,
at
least
for
people
like
myself
that
are
using
lando
lando
only
offers
up
to
by
default
8.0
19..
B
So
I
cannot
test
the
fix
as
it
is
now.
I
did
file
a
an
issue
with
them,
but
if
anyone
is
comfortable
with
installing
parts
versions
and
testing
yeah,
we
could
use
some
help
going
forward
with
that
issue.
A
Okay,
also
another
183
item
in
118.2.
We
did
a
couple
of
accessibility
improvements.
We
made
it
to
the
block
interfaces
navigable
with
the
keyboard
and
we
added
an
aria
announcement
api.
A
However,
one
of
our
objectives
with
that
was
to
make
the
blocks
interface
fully
accessible
to
non-sighted
users
and
the
follow-up
issue
that
kind
of
ties
together.
Those
two
pieces
is
five,
zero,
two
one
which
makes
it
so
that
the
the
drag
and
drop
arrangement
then
uses
the
new
backdrop
announce
api
to
alert
the
user.
A
So
there's
no
pull
request
yet
for
that
one,
and
that
it's
not,
but
it's
not
a
particularly
challenging
thing
to
do
to
make
those
announcements
after
the
changes
have
taken
place.
A
Okay,
anything
else
for
118
to
any
other
favorite
bug
fixes
or
things
that
should
be
brought
up.
B
Contributing
to
that
milestone
and
see,
there's
just
small
ones
like
file
usage,
has
a
bad
link
which
is
issue
four,
nine
five
zero
there's
a
lot
of
oh
but
that's
rtbc,
actually
so,
there's
quite
a
few
issues
that
are
not
either
as
a
tbc
works.
For
me.
A
Yeah
lots
of
works
for
me
stuff.
Okay,
let's
see
I
see
peter
has
joined
us
bw
panda.
I
won't
call
on
you
but
peter.
Please,
just
let
us
know
if
there's
anything
in
particular
to
talk
about
as
we
go.
A
119
119
is
the
next
minor
version
of
backdrop.
It
will
be
coming
out,
may
15th
with
feature
freeze
one
month
from
today
may
1st
2021..
A
We
have
several
issues
or
several
features
that
have
already
been
merged
into
119.
You
can
check
those
out
in
the
119
milestone
and
the
closed
items.
At
this
point
we
really
only
talk
about
the
things
that
are
still
in
flight,
so
looks
like.
There
are
seven
issues
that
are
currently
in
progress.
Actually,
six
issues,
one
of
them
is
been
merged,
but
just
has
a
change
record.
That
needs
to
be
done,
so
we
can
go
through
each
one
of
them.
The
exposed
file
name
filter.
A
We
would
like
to
add
a
filter
to
the
media
library,
dialog
issue.
3293.
lauren
is
the
advocate
for
this
one,
we're
still
stuck
kind
of
where
we
have
been
on
this
one.
That's
we
need
a
developer
to
take
a
look
at
it.
A
Advanced
caching
support
adding
cache
tags
in
a
cache
max
age.
Header
issue.
4127.
joseph
is
the
advocate
for
this
one.
He
has
done
a
pull
request.
Herb
tool
has
done
a
code
review
on
said,
pull
request,
but
we
need
testing
like
user
testing
on
this
functionality
and
checking
to
see
that
it
works.
I
haven't
even
done
an
architectural
review
on
it,
yet
so
definitely
an
area
in
which
we
need
reviewers.
B
A
Yeah,
that
would
that's
a
great
point
that
perhaps
what
we
really
need
is
we
need
testing
instructions
and
that
would
help
get
tests,
get
get
testers.
Trying
things
out
my
understanding
of
what
should
be
happening.
There
primarily
has
to
do
with
turning
on
the
page
cache.
Actually,
the
page
cache
is
already
on
opening
up
an
incognito
window,
that's
logged
out
and
a
logged
in
window
as
well
saving
content
and
then
seeing
if
that
content
is
immediately
refreshed
in
the
incognito
window.
A
That
I
think
that's
the
the
baseline
testing
that
we
would
like
to
get
coverage
on.
There's
more
advanced
stuff
like
checking
the
http
headers
and
seeing
that
the
home
page
listing,
for
example,
every
node
that
is
shown
on
the
home
page
should
have
a
header
tag
that
says:
node
id
10,
node
id
12
node
id
14
and
enumerates
every
node.
That
is
on
that
page
as
an
http
header,
so
that
reverse
proxy
caches
could
clear
or
could
invalidate
their
caches
based
on
those
headers.
A
Let's
see
next
up
is
field,
has
value
visibility,
condition
for
blocks
issue
4728.
I
don't
believe
there
are
any
updates
on
this
issue
recently.
Jen
lampton
is
the
advocate
for
this
one.
Although.
A
Yeah
interesting,
I
saw
that
there
was
another
issue
filed
by
jen
lambton
that
got
moved
into
the
119
milestone
and
that
is
adding
the
save
draft
module
to
court
jen
filed
this
issue.
It's
issue
3157,
but
I
looked
at
it
just
now.
I
thought
jen
was
maybe
shifting
her
advocacy,
but
I
see
that
bw
panda
is
the
advocate
for
that
issue,
so
peter
I
didn't
put
that
into
the
agenda
yet.
But
this
is
a
new
development
just
happening
breaking
news.
A
Oh,
the
save
draft
module
in
core
I'm
just
curious
about
to
hear
hearing
your
plans
or
hopes
for
that
issue.
B
A
Yeah
and
this
issue,
if
I
recall
the
safe
draft
module
or
what
this
issue
entails,
isn't
necessarily
what
I
had
thought
it
was
based
on
the
title:
can
either
gregory
or
peter?
Can
you
summarize
what
it
is
that
this
issue
actually
covers
yeah?
Can
you
hear
me.
B
E
Okay,
so
yeah
so
basically
normally
backdrop
just
has
a
save,
or
I
think
it's
just
a
save
button
at
the
bottom
of
the
node
form,
and
that
is
there,
regardless
of
whether
you
tick
published
or
draft
or
scheduled
or
whatever
the
save
draft
module,
basically
adds
which
I
think
it
might
change
the
label
of
the
button,
but
it
adds
other
buttons.
So,
for
example,
instead
of
having
checkboxes
or
radio
buttons
for
published
or
draft
or
scheduled,
you
have
buttons.
E
Instead,
so
when
you're
creating
a
node,
you
can
either
tick
on
like
press
the
publish
button
at
the
end
of
after
filling
it
out
or
you
can
tick
on
press
the
save
draft
button
and
that
will
determine
whether
it
saves
the
draft
or
published,
and
I
think
that
just
makes
it
easier
to
see
what
you're
doing
makes
it
more
of
an
action
rather
than
like
a
checkbox
sort
of
thing
and
yeah.
E
E
B
Yes,
this
started
off
like
there
were
some
baby
steps
in
drupal
land
as
well,
where
they
exposed
the
published
checkbox
instead
of
having
it
hidden
between
the
metadata,
the
vertical
tabs
or
whatever
it
was.
It
was
a
checkbox
immediately
above
the
save
button
which
was
saying
published,
but
but
yeah
it
didn't
make
ux
wise,
didn't
make
sense.
They
have
a
checkbox
for
as
peter
said,
for
something
that
is
actually
an
action.
So
yeah.
A
Yeah
got
it
so
if
I
recap,
what
this
does
is
the
radio
buttons
stay
as
they
are
where
it's
like
published
draft
schedule,
but
as
you
change
those
radio
buttons,
it
changes
the
label
of
the
save
button.
So,
instead
of
just
saying
save
now
all
the
time
it
would
reflect
the
action
that
you're
about
to
take
by
clicking
that
button.
Does
that
sound
right.
E
B
A
Interesting,
okay,
well,
looking
forward
to
see
how
that
shapes
up.
Let's
see
that
again
is
issue
3157.
A
Okay,
next
up
is
adding
support
for
relationships
to
layout
context.
Issue.
2134.
drawmont
is
the
advocate
for
this
one.
He
updated
the
pull
request
a
couple
weeks
ago
and
that
new,
updated
pull
request,
needs
review
and,
lastly,
merging
together
the
various
update
pages,
update
core
modules,
themes
and
layouts
into
a
single
update,
page
issue.
2714
greg.
Could
you
give
us
an
update.
B
Yeah,
so
I've
been
saying
for
weeks
now
that
I'll
get
back
to
it.
I
finally
started
reviewing
it
and
I
have
a
long
weekend
because
of
public
holidays
ahead.
I
did
look
at
the
comments.
Finally,
that
eddie
gozella
has
left
in
the
pull
request
which
they
suggest
how
to
move
forward
with
the
issue
that
I
was
having.
So
hopefully
we
think
this
weekend,
I'll
I'll
get
all
that
sorted
and
it
will
be
ready
for
review
again
yeah.
B
So
looking
good,
perhaps
I
can
get
another
advocate
for
another
issue
there's
another
month
or
so
so
cool.
A
All
right,
that's
it
for
the
119
updates.
As
always,
if
you
would
like
to
have
an
issue
in
119,
the
process
is
pretty
simple.
You
find
a
feature
and
you
edit
the
summary
and
put
advocate
colon,
your
name
there,
and
then
that
allows
you
to
put
it
into
the
119
milestone,
and
then
we
talk
about
it
during
these
weekly
meetings.
A
Let's
see
next
up
is
initiatives.
Initiatives
are
large-scale
projects
that
aren't
necessarily
tied
to
a
particular
release.
Number.
We
have
two
active
initiatives
right
now:
documentation
and
telemetry
peter
is
heading
up
the
documentation,
and
I
saw
that
there
were
a
number
of
updates
that
peter
posted
into
zulip,
although
peter
now
that
you're
here,
if
you
could
just
give
us
a
verbal
update,
that
would
be
greatly
appreciated.
E
Yeah
so
yeah
I've
been
working
on
this
the
last
week,
so
basically,
the
migration
that
jen
had
done
from
vietnam
to
the
new
doc
site
was
set
up.
There's
a
few
issues
with
it,
which
I
fixed
up
to
make
it
so
that
html
was
being
copied
over
correctly.
So
now,
the
headings
and
images
are
showing
up
properly
on
nodes,
which
is
all
working.
E
One
thing:
I'm
not
sure
how
to
fix
is
the
inline
images
on
the
docs
sites
of
the
migrated
content
they're
showing
up
and
they're
referencing
the
image
on
the
files
and
the
docs.
That's
all
fine,
but
I
think
because
they're
not
managed
files.
It
means
that
when
you
click
on
a
like,
if
you're
editing
a
node
and
you
click
on
an
image
and
use
the
ck
editor's
image
button,
it
doesn't
show
up
as
being
editable.
It's
asking
you
to
upload
a
new
image,
so
I'm
not
sure
how
to
fix
that.
E
E
Other
than
that,
the
menu
structure
has
been
reorganized,
as
per
my
proposal.
So
that's
all
been
done,
and
the
thing
I'm
currently
working
on
is
the
book
navigation.
So
we
used
to
use
the
book
module
to
have
the
little
navigation
like
pager
links
at
the
bottom
of
each
node.
We
can
click
to
go
the
next
page
or
the
previous
page,
but
I
realized
that
that
was
basically
duplicating
the
hierarchy.
That
was
also
in
the
menu
like
the
right
hand,
main
menu.
E
So
anytime
you
added
a
new
node
or
edited
a
node.
You
had
to
tell
it
where,
in
the
book
hierarchy
that
node
was
and
then
separately,
where
in
the
menu
hierarchy
that
node
was
and
they're
basically
the
same
thing,
so
I'm
currently
working
on
porting
a
d7
module
that
gives
a
pager
to
nodes
based
on
where
they
are
in
the
menu.
So
that
way
we
just
have
to
define
the
menu
hierarchy
and
then
they'll
have
the
pager
options
based
on
the
menu
rather
than
the
separate
book
setup.
E
B
Yeah,
I
think
that
the
book
module
in
general,
like
early
on
and
drupal,
was
intending
for,
as
you
said,
the
to
the
menu
structure
or
the
pager.
But
then
the
other
thing
is
that
you
couldn't
give
people
permission
or
you
didn't
want
to
give
people
permission
to
edit
the
menus.
But
we
don't
have
the
problem
with
documentation
site
because
the
the
people
that
are
granted
access
to
edit
and
create
documentation.
They
also
have
access
to
real
business.
So.
A
Peter
for
the
update,
let's
see
and
the
other
initiative
we
have
ongoing
is
telemetry
which
st
paul
tim
is
the
advocate,
for
he
left
a
note
here,
nothing
new
to
report.
It's
on
my
agenda
as
soon
as
I'm
able
to
make
time
thanks
tim
and
that's
it.
That
brings
us
to
the
end
of
the
agenda.
We
have
some
time
here.
If
there's
any
thing,
you
guys
would
like
to
bring
up
or
discuss.
A
B
There
was
an
issue
since
we
had.
We
do
have
time.
There
was
a
small
issue
that
I
did.
That
is
a
feature
request
and
I
haven't
touched
for
a
year
or
more
now,
which
is
adding
generating
automatically
generating
thumbnails
for
flexible
layout
templates
when
they
are
being
generated.
Oh
yeah,
and
there
was
a
sub
issue
there
to.
B
Let
me
locate
the
issues
so
that
I'm
not
talking
like.
I
can
also
point
to
that
was
related.
There
was
a
a
respective
issue
indeed.org,
which
is
with
regards
to
busting
the
cash
for
images,
and
we
were
contemplating
on
that
issue
whether
we'd
need
to
do
that
for
managed
and
non-managed
images
or
not,
and
this
is
where
it
pretty
much
got
stuck.
B
So
I
would
like
to
revive
that,
because
the
the
images
that
are
being
generated
by
the
the
codes
that
are
created
for
that
those
thumbnails
fall
into
that
category,
so
there
was
a
an
issue
with
when
you
edit.
So
basically
this
is
you
came
up
when
you
were
editing
an
existing,
flexible
template
and
tweaking
the
the
layer.
Sorry,
the
regions
upon
save
the
thumbnail
was
cast,
so
it
wasn't
updated.
There's
a
workaround
which
sort
of
like
suggested
by
then.
B
I
think
that
it's
okay
to
add
a
like
a
randomized
number
at
the
end
of
the
image,
the
actual
file
name,
which
is
a
workaround.
But
I
would
like,
since
this
is
a
broader
issue,
and
it's
also
like
an
on
the
radar
for
drupal.
I
think
that
we
should
sort
it
out
or
make
a
decision
at
least
but
yeah
I'll
try
to
find
the
issue.
B
A
This
has
probably
been
mentioned
in
that
issue
too.
You
could
add
a
hash
to
the
file
name
or
you
can
also
add
a
query
string
after
the
file
name.
Just
like
you
know,
question
mark
time
stamp
and
that's
something
else
that
I've
seen
used
from
time
to
time.
B
Yep,
I
can't
find
the
issues
now.
I
found
the
meta,
but
I
can't
like
I'm
skimming
through
it
now
generated.
So
I
found
it
so
the
the
issue
that
I
was
referring
to
with
automatically
generating
icons
which
I'm
hoping
to
get
back
to,
because
it's
here
listed
as
a
task.
B
A
task
actually
is
four
one:
zero,
four,
that's
the
one
about
generating
the
the
images
and
then
the
other
issue
that
I
was
referring,
which
is
sort
of
like
related
to
that
and
it's
a
feature
request
is
four
one:
zero,
seven,
so
yeah
I'll
get
back
to
those
as
well,
and
I
would
like
some
feedback
from
others.
B
A
Okay,
well,
I
think
yeah
I
wouldn't
mind
wrapping
up
a
little
early
today.
I
think
we
can
say
thank
you
for
everybody.
It's
been
a
little
bit
of
a
hectic
week
for
myself
and
others.
So
hope
everybody
takes
care
of
yourself
out.
There
really
appreciate
the
work
you
do
for
backdrop,
but
take
care
of
yourself
first,
so
thanks
everybody,
I'm
gonna
end
the
in
the
broadcast
and
in
the
meeting
see
you
guys
next
week
and
on
the
internet.