►
From YouTube: Backdrop Weekly - May 13, 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
13
2021,
and
this
is
the
weekly
backdrop
developer
meeting.
We
get
together
every
thursday
to
talk
about
the
latest
and
greatest
happenings
in
backdrop.
This
is
the
last
weekly
meeting
before
the
may
15th
release
of
backdrop
1.19,
it
will
be
coming
out
on
saturday
may
15th
so
very
exciting.
A
Before
we
get
started,
though
we'll
do
introductions,
my
name
is
nate
lampton,
I'm
a
quick
sketch
on
the
internet
and
I'm
a
core
committer
and
I
think
I'll
start
the
chorus
of
I'm
excited
for
the
next
release.
B
Okay,
my
name's
tim,
st
paul
tim,
I'm
here
in
deerwood
minnesota,
I'm
feeling
a
little
guilty
because
I'm
not
at
all
involved
in
this
release.
I've
been
so
busy
with
other
things,
but
if
I
can
find
a
little
time
this
weekend
to
help
with
the
the
final
release,
I'll
do
my
best
so
gregory.
C
Hi,
I'm
greg,
I'm
usually
in
australia,
but
now
joining
from
greece
excited
about
the
release
as
well.
I
at
the
very
last
minute
or
week
I
should
say,
got
in
one
of
the
features
or
tasks
that
I
wanted
to
get
in
since
I
don't
know
two
years
ago,
merging
the
update
pages.
C
So
that's
super
exciting
to
see
that
get
in
and
I've
missed
and
I've
missed
the
two
or
three
last
weekly
meetings
so
happy
to
join
in
keep
up
with
what's
going
on
and
try
to
help
as
much
as
I
can
and
I'm
gonna
pass
it
on
to
robert.
E
I'm
justin
I
just
volunteer
with
some
infrastructure
when
I
can
in
denver
colorado.
F
One
jen
lampton
joining
from
oakland
california,
I'm
really
excited
about
all
the
great
user
interface
improvements
in
the
next
one
gregory.
Thank
you
for
pushing
forward
on
that
issue.
For
so
long,
I'm
excited
to
see
those
update
pages
merge
too
back
to
you,
nate.
A
All
right,
let's
see
actually
before
it
goes
back
to
me,
we've
got
updates
from
the
pmc.
We
have
an
announcement
this
week.
Let's
see
tim
or
jen
or
or
gregory,
I'm.
C
Yeah
I
can.
I
can
announce
that
so
the
big
announcement
is
that
we
have
two
new
court
committees
being
on
boarded
lauren
and
joseph
joseph
flatt
and
larry.
I'm
not
gonna
even
try
to
pronounce
your
surname
because
I
don't
know
I'll
get
it
wrong.
Probably
but
yeah.
Both
of
these
people
were
long
time,
members
of
the
community
and
they
have
proven
their
commitment
to
the
community
and
the
project
and
divided
by
the
community.
So
we're
very
happy
to
have
them
help
us
out
so
yay.
A
Yeah,
I
definitely
really
appreciate
the
adding
of
new
core
committers.
That's
going
to
be
very
exciting.
A
I
always
had
hoped
that
we
would
be
able
to
have
enough
core
committers
to
distribute
the
responsibility
to
make
it
so
that
no
one
would
feel
like
their
life
was
consumed
by
the
responsibility
of
managing
pull
requests
into
into
backdrop.
We've
always
tried
to
promote
people's
personal
health
as
being
a
priority,
trying
not
to
put
too
much
pressure
on
people.
Let
people
know
it's.
A
Okay,
things
don't
get
in
and
I
really
hope
that
continuing
to
distribute
that
with
more
core
committers
makes
it
so
that
it's
easier
for
more
core
committers
to
join
in
the
future.
So
that's
our
hope.
We're
getting
there
so
that'll
be
exciting
to
have
the
assistance
of
laryn
and
joseph
going
forward
in
the
future.
A
Okay,
let's
go
to
the
progress
reports,
as
I
mentioned
at
the
beginning
of
the
meeting
backdrop,
119
will
be
coming
out
day
after
tomorrow.
I
thought
there
was
a
question
in
zulip
about
like
that
lands
on
a
saturday.
Does
that
get
pushed
to
the
end
of
the
holiday
answer
is
no
for
preview
releases.
A
We
kind
of
allow
the
deadline
to
be
a
little
malleable
to
move
over
holidays
and
weekends,
but
for
the
official
releases
they
always
come
out
exactly
on
the
day
that
is
scheduled,
so
that
will
be
coming
out
on
saturday
actual
time
on
saturday
that
part's
a
little
bit
flexible.
Sometimes
it's
a
nice
in
the
middle
of
the
day.
If
there's
nothing,
that's
happening,
sometimes
there's
a
last
minute
thing
that
makes
it
so
that
we
kind
of
push
it
to
be,
like
you
know,
maybe
may
15th
hawaii
time.
You
know.
A
Which
is
kind
of
what
we
did
for
the
preview
release
that
I
remember
we
were
pushing
that
all
the
way
until
the
very
end
of
end
of
the
day.
Let's
see
so,
I'm
gonna
do
this
in
kind
of
reverse
order.
Today
talk
about
what
we
got
into
119
and
what
items
remain
and
then
we'll
go
backwards
to
the
bug,
fixes
and
then
we'll
finally
finish
up
with
120..
A
So
what
got
into
119?
I
think
I
covered
all
of
these
last
week,
but
I'll
do
them
again.
Nonetheless,
php
8
support
the
initial
pull
request
for
that
issue.
4772
was
merged
into
the
one.x
branch.
That
means
that
php
8
support
we
decided
not
to
back
port
into
118
because
it
did
have
to
change
an
awful
lot.
Some
of
the
database,
abstraction
layer
in
particular
got
modified
around
and
so
there's
kind
of
a
high
level
of
risk
there
that
we
didn't
want
to
put
into
a
bug
fix
release.
A
So
the
backdrop
119
preview
release
includes
that
functionality
and
highly
encourage
everybody
to
try
out
the
preview
release,
make
sure
that
things
continue
to
function.
You
don't
have
to.
Obviously,
you
don't
have
to
use
php
8,
but
you
can
now,
if
you,
if
you
so
wanted
to
there's
a
follow-up
issue
opened
at
50
76.
That
is
a
now
a
meta
issue
for
full,
comprehensive
php
aid
support
4772
made
it
so
that
you
can
install
backdrop
run
it
most.
Everything
works
in
the
that
you
would
do
on
a
day-to-day
basis.
A
However,
we
do
not
have
100
test
coverage
passing
yet
there's,
probably
still
20
or
so
tests
that
are
failing
for
various
reasons
and
issue.
50
76
is
to
get
us
to
the
point
that
we
can
get
every
one
of
those
tests
passing
and
then
we
can
actually
claim
full
php
support.
A
Let's
see
big
issues
that
got
in
adding
support
for
relationships.
The
layout
context,
issue
2134
stockwellmont's
issue
for
119.
that
was
merged
in
very
exciting
there.
There
is
a
follow-up
issue
related
to
that
one.
That's
really
minor!
It's
just
an
aesthetic
thing
about
the
links
that
are
displayed
in
the
administrative
interface
that
there's
now
a
link
that
says
add
context
which
is
already
there
and
then
there's
another
link.
A
Saturday,
let's
see
we
merged
together
all
of
the
updates
pages
issue:
27
14.
gregory.
You
were
the
advocate
on
this
one
and
you
mentioned
there's
some
follow-ups.
Can
you
give
us
a
summary
of
the
state
of
things
there.
C
Before
I
do
that,
I
would
like
to
thank
indigozella
for
their
patience
with
this,
pushing
this
pushing
me
to
push
this
to
the
end,
so
we
finally
got
it
in
so.
C
The
two
things
that
remain
is
there's,
there's
a
setting
about
the
core
self
updates,
which
was
sitting
under
the
the
form
that
holds
the
settings
for
how
frequently
dates
are
being
checked
which
belong
to
the
updater
module,
so
that
form
was
basically
saving
had
two
field
sets
with
settings,
one
for
the
two
for
the
updater
module
and
one
for
the
installer
module.
C
So
one
of
those
issues
is
moving
the
setting
that
corresponds
to
the
installer
to
a
new
settings
page
under,
I
should
say
a
secondary
primary
tab
next
to
the
plates
and
the
other
one.
Was
this
one
confusing
that
one
and
the
other
one?
What
was
it?
I
forgot.
What
that
was
just
bear
with
me.
C
Oh
yes,
and
if
you
disable
the
core
self
updates,
then
you
have
the
list
of
enabled
modules
and
core,
or
rather
the
any
modules
or
core
which
need
modulo
manual
updates,
be
presented
like
in
a
secondary
table
and
there's
a
lot
of
text
explaining
what
you
need
to
do
manually,
so
that
page
seems
really
busy.
C
So
what
I've
done
is
I've
merged
that
into
the
main
table
and
then
I've
added
a
something
that
we
have
as
a
common
pattern
in
the
modules
page
and
the
status
report
page
a
more
or
less
link
a
toggle
that
sort
of
like
expands
the
instructions
for
manual
updates.
So
it's
a
little
bit
more.
You
know
easy
to
the
eye.
A
Yeah,
that's
issue
50
85
that
second
one
yeah
they
both
look
really
good.
Thank
you
for
posting
screenshots
into
these
issues.
50
84
is
the
first
issue.
5085
is
the
second
one
yeah.
They
both
have
screenshots
that
demonstrate
what
it's
doing,
basically
more
like
putting
stuff
where
it
makes
sense
and
simplifying
some
user
interfaces.
Yeah.
It
looks
great
yeah
the
the
list
of
available
updates,
I'm
so
glad
that
you
took
that
on
because
it
was
kind
of
like
just
everywhere
all
over
the
place.
A
Speaking
of
of
that,
I'm
going
to
jump
a
little
bit
around
that
there
is
issue
50
46
that
has
been
causing
a
little
bit
of
a
contention.
That's
a
issue
about
performance
on
the
modules
page
that
alan
melz
opened
that
included
some
back
and
forth
between
indigozella
doc,
welmont
and
alan
melz
about
like
how
best
to
fix
this
problem,
and
I
think
that
we've
kind
of
arrived
at
how
we're
going
to
fix
the
problem
that
there
is
a
performance
problem,
it's
related
to
update
module.
A
Actually,
the
update
module
on
certain
administrative
pages
displays
this
big
error
across
the
top.
If
there's
a
security
update
that
happens
on
slash
admin,
admin
modules,
page
the
themes,
page,
the
layouts
page
and
a
couple
other
ones,
basically
the
most
important
pages.
In
the
backdrop,
administrative
interface
have
these
big
red
errors
across
the
top.
If
a
security
update
is
needed,
it
turns
out
that
update
module
like
doing
checking
if
that
message
needs
to
be
displayed,
requires
an
extremely
intensive
process
where
it
has
to.
A
It's
already
doing
that
process
once
to
display
the
module
listing
and
with
the
update
module
it
does
it
twice,
and
so
I
opened
up
well,
first
of
all,
this
issue
5046
fixes
that
doing
it
twice
part,
at
least
so.
That's
that's
the
performance
enhancement,
but
I
opened
up
a
second,
a
spin-off
issue
from
this
issue.
5083
that
proposes.
A
Maybe
we
don't
display
that
big
red
error
all
over
the
administrative
pages
anymore.
We
have
a
lot
more
places
thanks
to
some
of
your
work,
gregory,
that
we
now
warn
people
about
security
updates.
We
now
have
so
we've
got
the
red
dot
in
the
notification
bar
in
the
admin.
A
Maybe
we're
telling
people
that
there's
security
updates
in
enough
places
already
that
we
can
remove
one
of
the
legacy
ways
of
notifying
people
of
things
plus
I've
always
hated
that
message
like-
and
this
is
my
personal
bias
coming
into
this-
I
admit
that
that
big
red
error
at
the
top
of
the
page
it
like
it,
drives
people,
or
at
least
it
drives
me
to
turn
off-
update
module
entirely.
Just
because
it's
so
obnoxious
like
yeah,
I
mean
the
red
dot
is
is
enough
of
a
like
hey.
A
I
need
to
go
check
this
out
and
it
can
be
really
embarrassing
if
you're
like
displaying
something
to
a
client
and
there's
a
security
update,
you've
reviewed
it,
it's
not
very
important,
perhaps,
but
for
like
a
day
or
two
like
you've
got
the
big
red
banner.
I
guess
that's
the
thing
is
that
it
it's
so
embarrassing
that
I
guess
it
drives
people
to
update,
but
I
it
drives
me
to
turn
off
the
module
so.
C
One
one
thing
that
so
I
have
some
comments,
I'll
put
them
in
the
in
the
cube,
but
I
have
also
a
question.
So
one
comment
that
I
want
to
point
out
is:
do
we
first
of
all,
do
we
show
that
message
to
everyone
we
shouldn't?
We
should
only
show
it
if
the
person
that
is
logged
in
has
the
what
you
call
it
permission
to
manage.
Updates.
A
C
That's
horrible
and-
and
the
other
thing
is,
is
the
performance
issue,
because
we're
doing
the
check
it's
time
that
we
load
that
message
because
working
working
with
the
those
two
issues,
the
50,
84
and
5085.
I
noticed
that
we
have
a
threshold
like
a
free,
frequent
frequency
when
we
check
for
updates-
and
that
says
daily
and
weekly-
isn't,
doesn't
it
then
make
it
redundant
to
be
doing
that
tech
all
the
time?
C
Should
we
be
doing
that
check
if
there's
actually
any
any
new
and
caching
that
somewhere
or
having
a
flag
or
states
that
says
yep
since.
A
So
that's
actually
the
point
of
contention
in
the
previous
thing
about
fixing
the
performance
thing
is
like
what
is
this
actually
doing
and
there's
two
parts
here
that
there's
the
checking
for
updates
from
the
internet,
and
that
indeed
does
do
it
on
the
schedule
and
it
does
it
on
cron
or
when
you
check
for
updates
using
the
button,
but
that's
one
part
of
it.
A
The
second
part
is
that,
once
you
have
the
cached
list
of
updates
from
backdrop
cms.org,
then
you
have
to
compare
it
against
what
is
currently
installed
and
the
comparison
is
what's
happening
on
like
slash
admin
and
on
the
modules
page
and
caching,
that
this
is
this.
This
is
what
the
where
the
problem
was.
A
The
version
on
disk
and
then
went
to
the
modules
page
and
checked:
did
the
module
get
updated
and
if
there's
no
like
I
mean,
there's
lots
of
other
things
that
would
have
also
cleared
it.
If
you
would
have
cleared
the
caches,
visited,
update.php
and
run
updates
or
a
number
of
other
things.
But
if
you
just
updated
a
module,
there
were
no
updates
and
you
knew
there
were
no
updates.
And
then
you
went
to
the
modules
page.
A
It
would
still
show
the
big
red
error
there's
a
security
update,
even
though
there
wasn't-
and
so
that's
what
the
expensive
check
is
is
checking
did
the
has
the
module
actually
been
updated
since
I
displayed
this
message,
so
it
tries
to
just
make
it
so
that
it's
up
to
date
all
the
time
that
it's
not
displaying
something.
That's
not
true
anymore,
but
that's
really
expensive
to
manage
the
accuracy
of
that
message,
and
so
I
mean
it's
not
for
the
performance
reason.
A
There
hasn't
been
any
other
discussion
about
that
yet
other
than
my
initial
filing
of
the
issue,
so
I'm
sure
well,
I'm
not
sure,
but
I'd
like
to
hear
people
disagree
with
that
jen
I
saw
posted
into
the
chat.
It
causes
panic,
oh
and
then
she
said
love
it.
I
think,
meaning
that
she.
A
Great
okay,
so
that
was
all
spun
out
of
the
updates
update
module
just
in
general.
It
also
would
just
be
great
to
modernize
update
module
just
a
little
bit
more
like
the
way
that
it
checks
and
displays
that
message
and
the
way
that
it
caches
everything.
The
whole
thing
is
like
really
kind
of
gnarly,
so
it
would
be
nice
to
just
revisit
that.
A
Let's
see,
I
guess
feature-wise,
I
don't
have
anything
else
to
really
pull
up.
There
are
a
couple
of
things
that
need
to
be
done
before
119
is
released,
including
a
blog
post,
covering
the
new
features.
A
We
have
one
change
record
that
needs
to
be
written.
We
added
a
new
capability
to
backdrop,
add
css
that
now
you
can
put
attributes
on
your
css
files
when
they,
when
they
display
that
can
be
useful
for
certain
libraries
that
require
like
attributes
on
the
css
file,
like
like
a
font,
for
example.
That
needs
to
have
a
special
attribute
on
it
and,
let's
see
and
oh
and
then
that
minor
change
that
I
mentioned
about,
layouts
that
that
that
issue
is
50
74
about
the
add
relationship
link
so
really
minor.
A
In
the
meantime,
so
that
really
means
that
we
only
have
like
one
or
two
things
that
need
to
be
done
for
the
119
release
that
we
know
of.
Of
course,
if
more
regression
bugs
come
in,
we
haven't
seen
any
so
far.
I
saw
some
people
have
actually
been
testing
and
reporting
that
the
php
8
patch
has
not
caused
any
problems
for
them,
which
has
been
highly
appreciated,
but
as
of
now,
we
don't
really
have
anything
else,
major
that
needs
to
be
addressed
in
the
next
two
days.
A
But
let's
talk
about
what's
not
major
that
could
be
addressed
in
the
next
two
days,
so
118
4
is
the
the
last
bug
fix
release
for
118
and
what
usually
happens
in
this
little
window
between
code,
freeze
and
or
feature
freeze,
and
the
release
of
a
new
minor
version
is
that
we
frequently
turn
our
attention
to
bug
fixes
because
bug
fixes
can
still
be
completed
between
releases
so
or
between
between
this
time
frame.
A
F
A
Open
issues
I
think
indigozala,
it
was
suggested
that
maybe
we
should
have
like
a
session
or
a
meeting
where
we
like
groom
the
1175
list
and
get
it
down
to
something
a
little
bit
more
meaningful
because
we
have
a
process
for
putting
things
into
a
milestone.
But
we
don't
have
a
process
for
taking
them
back
out
like
if
something
isn't
feasible
or
is
more
difficult
or
whatever.
Maybe
we
should
take
it
back
out
of
that
milestone
and
give
a
little
bit
more
meaning
to
or
a
little
bit
more
focus
to
the
developers.
C
Yeah
and
when
we
say
we
move
it
out,
we
just
revert
to
the
milestone
tag.
Instead,.
A
C
A
Yeah
anyway,
so
in
the
184
milestone
a
couple
of
issues
that
are
of
note,
there
was
that
performance
issue
on
the
modules
page
issue,
50
46,
it's
marked,
needs
review
right
now.
I
think
it's
actually
ready
to
go
as
it
is,
but
I
was
waiting
for
additional
feedback
there,
because
that
was
a
an
issue
that
had
some
contention
in
it.
A
The
module
config
directory
is
not
synced.
On
the
install
of
new
modules
issue.
A
3224
joseph
has
been
mentioning
this
issue
as
something
he'd
like
to
see
because
it
would
move
forward
the
recipes
concept
that
turning
on
a
module
could
install
fields
and
then
have
the
database
tables
created
along
with
those
so
that
it
has
a
pull
request
over
at
32
24.,
and
then
this
past
week,
there's
been
a
lot
of
activity
on
drupal
cross
ports
from
triple
seven
there's
an
issue
50
42
that
covers
drupal
7.65
to
7.69
gregory,
you've
been
working
on
that
one.
A
lot.
C
Yeah,
so
there
were
like
maybe
30
commits
there
and
I
went
maybe
a
month
ago
I
went
through
all
of
these.
Most
of
them
were
not
applicable
to
backdrop
and
then
for
those
that
were
applicable.
I
just
filed
pull
requests
and
eddie
gozella
went
ahead
and
reviewed
them
yesterday.
C
What
I
need
with
that
is
a
second
pair
of
eyes,
at
least
to
go
through
the
issues
that
sorry
the
commits
that
we
marked
as
not
applicable
and
confirmed
that
they
are
not,
and
then
some
code,
reviews
or
feedback
on
the
comments
that
indiegogo
has
already
left
there.
I
should
point
out
that
some
of,
like
most
of
them,
are
very
small.
Like
there's
you
know,
one
line
or
three
line
fixes.
A
Yeah,
that
would
that
would
be
great.
Are
there
any
issues
that
are
kind
of
exciting
or
neat
or
like
overly
useful
that
you're,
just
like
oh
yeah?
That
would
be
really
nice.
C
I
think
there's
two
that
require
change
records
because
they're
api
editions,
but
it
was
kind
of
exciting
to
see
that
certain
things
got
into
d7.
After
all,
like
it's
getting
some
attention
when
things
need
to
be
fixed
but
yeah,
it's
tidying
up
things
based,
basically
or
making
things
easier.
A
Yeah
super:
let's
see,
I
also
have
one
more
issue.
I
think
it
was
related
to
the
code
sprint
that
there
was
a
lot
of
activity
happening
and
when
there's
a
lot
of
activity
happening,
then
people
notice,
when
our
tooling
isn't
working
correctly.
A
So
we
got
some
more
noise
about
zen,
ci,
failing
to
run
the
tests
correctly,
and
especially
when
there's
a
deadline
and
people
are
like
running
the
test
again
and
again
and
again
and
we're
just
like
you
just
have
to
keep
running
it
until
zencia
doesn't
fail
on
you
like
randomly
and
it's
not
a
random
test
failure.
A
It's
just
like
the
test
results,
just
didn't
come
back
and
you
got
a
page
not
found
over
on
the
results
page
and
so
that
spurred
yet
again,
a
discussion
about
like
can
we
start
investigating
alternatives
and
the
most
likely
alternative
in
my
mind,
is
github
actions,
because
it's
free
it's
built
into
github
and
it's
what
we'll
probably
use
for
some
other
features
and
functionality.
A
I
also
think
github
actions
has
almost
become
the
de
facto
standard
because
it's
built
into
github.
I
can't
imagine
the
other
ci
providers
all
panicking,
because
their
entire
business
is
built
upon
providing
a
feature
that
github
didn't
have
that
github
is
providing
it
the
future
well-being
of
a
lot
of
ci
platforms.
I
think
is
probably
in
question
anyway,
so
providing
or
working
with
github
actions
there's
a
proof
of
concept
issue
over
at
47.53.
A
A
Is
that
github
actions,
although
free
and
although
built
into
github
the
runners,
are
not
particularly
powerful,
the
runners
that
they
give
us
and
give
everybody?
Actually
github
only
has
one
size
of
runner
and
it's
a
two
core:
seven
gigabyte
of
memory,
machine
virtual
machine,
of
course,
and
the
runtimes
are
pretty
bad
compared
to
zen
ci.
A
They
can
run
our
entire
php
seven
test
suite
in
under
five
minutes
with
no
tweaking
it
takes
more
like
40
minutes
on
github
actions
and
with
some
tweaking
we
can
get
it
down
to
around
30
minutes.
But
that's
php7.
A
We
haven't
even
tried
to
run
php
5.3,
which
had
usually
took
like
you,
know,
40
50
more
time,
so
it's
possible
that,
like
php
five
runtimes
might
end
up
being
like
around
45
minutes
or
even
an
hour.
But
the
great
thing
is:
is
that
github
actions
doesn't
have
a
timeout.
A
I
mean
not
not
one
that
will
affect
us.
The
timeout
on
github
actions
is
six
hours,
but
of
course
we
don't
want
to
wait
anywhere
near
that
long
for
test
results.
So
I
don't
know
it's
it's
kind
of
it's.
It's
a
fodder
for
discussion.
A
I
think
we
need
to
check
I
kind
of
feel
like
we've
done
this
evaluation
previously,
maybe
when
we
moved
to
this
nci
that
we
were
looking
at
all
of
the
other
ci
providers,
but
that
information
is
now
woefully
out
of
date.
You
know.
C
A
Years
out
of
date,
yeah
yeah,
I
I'm
sure
that
there
are
ones
that
are
faster.
A
Another
weird
option
is
that
github
allows
you
to
self-host
your
runners
as
well,
and
so
we
could
set
up
like
a
lenode
that
is
more
powerful
and
have
github
actions
run
our
tests
through
github
actions
api,
but
on
our
own
hosted.
F
A
A
There
are
just
absolute
monsters,
which
wouldn't
surprise
me
either,
but
he
did
something
smart
where
they're
only
they're
only
spun
up
and
then
torn
down
like
while
the
test
is
actually
running,
so
we're
not
paying
for
them
all
the
time,
the
leno
approach
and
or
the
github
actions
approach
you
would
be
paying
for
the
server
like,
regardless
of
whether
or
not
you
were
using
it
so,
but
it
might
be
useful
just
to
see
how
big
a
server
we
really
need
in
order
to
get
an
adequate
test
result.
A
Speed,
yeah,
my
initial
testing
on
that
I
didn't
get
anything
that
seemed
to
have
very
good
results.
Quite
yet
so
anyway,
that
issue
47
53,
is
kind
of
looking
at
that
option.
It's
not
quite
the
home
run.
I
think
I
was
hoping
for,
but
yeah
it's
possible,
maybe
with
some
more
trickery
we
might
be
able
to
get
those
runtimes.
A
Down
all
right,
let's
see
we're
coming
up
at
the
top
of
the
hour.
We
have
a
little
bit
of
time
to
talk
about
1.20
1.20.
A
The
features
that
will
go
into
1.20
are
decided
in
the
same
way
as
they
were
in
119,
where
issues
that
we
have
individuals
who
are
willing
to
advocate
for
those
issues
they
can
mark
an
issue
miles
are
a
milestone
candidate,
minor
and
then,
once
that
label
is
there,
they
can
add
themselves
as
an
advocate
and
then
a
second
person
will
come
along
and
say
yeah.
I
think
that
would
be
great
and
that's
how
things
get
moved
into
1.20
or
into
the
next
minor
milestone.
A
We
also
usually
have
some
kind
of
planning
session
a
couple
weeks
after
the
release
to
get
together
and
we'll
schedule
that
usually
tim
helps
us
with
coordination
there
and
announcements
and
communication
about
when
that
planning
meeting
is
it's
usually
in
the
place
of
this
weekly
meeting?
A
I
would
expect
that's
probably
I'm
just
taking
a
guess
that
might
be
like
june
3rd,
based
on
our
previous
timelines,
but
actual
date
to
be
determined,
and
that
meeting
is
more
just
like
a
working
session
of
like
what's
important
to
us.
Can
we
get
anybody
to
volunteer
for
these
particular
things?
A
There's
also,
of
course,
the
survey
site
that
tim
set
up
survey.backdropcms.org.
That
kind
of
gives
us
a
general
idea
of
like
what
community
members
are
interested
in.
Seeing
and
there's
some
really
familiar
features
in
there
that
people
have
been
wanting
for
a
long
time,
but
let's
not
focus
too
much
about
1.20.
A
A
Let's
see
I
do
want
to
mention
since
robert
you're
here-
and
you
mentioned
at
the
beginning
of
the
call
that
you're
already
advocated
for
a
1.20
issue-
issue
50
67,
and
if
you
want
to
give
us
a
short
summary
of
what
that
issue
is.
That
would
be
great.
D
Yeah
so
the
issue,
the
initial
driver
for
it
is
moving
node
specific
code
to
select
the
layout
for
node
preview
pages,
which
used
to
be
residing
in
the
layout
module.
D
And
so
the
intention
is
that
that
will
then
be
a
platform
to
expand.
The
ability
to,
for
example,
use
the
same
layout
on
multiple,
widely
different
paths
and
various
other
things
along
that
people.
A
Yeah
that
might
open
up
the
door.
I
know
that
you,
you
maintain
the
layout
wildcard
module.
I
think
that's
the
name
of
it.
Yeah
yeah.
I
wonder
about
moving
that
functionality
into
core.
You
know
directly
as
well.
I
mean
it
is
nice
that
it
can
trip
will
be
able
to
more
officially
support
that,
but
we
could
also
move
it
move
a
lot
of
that
functionality
into
core.
I
think.
D
Yeah
and
I
sort
of
pictured
layout
wildcard
can
in
a
way
be
a
prototyping
ground
to
test
things
out
that
we
might
consider
before.
For
example,
there's
one
feature:
that's
that's
currently
in
layout
wild
card,
which
I
have
given
the
name
of
ancestor
matching,
but
basically
it
it
matches
a
layout
to
any
ancestor
of
the
current
path,
which
makes
some
things
easy,
but
it
also
creates
lots
of
unexplainable
behaviors
when
people
don't
realize
that
there
was
an
ancestor
that
matched
and
the
wrong
layout
is
showing
up
and
so
for.
D
I
think,
because
that's
been
in
there
since
version
1.1,
it
probably
should
stay
in
future
versions
of
layout
wildcard.
I
plan
on
implementing
a
checkbox
to
let
people
turn
it
off
on
and
off,
but
but
that
wouldn't
move
into
core.
I
think
that's
something
that
should
stay
in
a
contrib
contribution.
A
Yeah
all
right.
Well,
I
think
we
we've
run
up
out
of
time
to
discuss
any
further
on
things.
I
think
that
we'll
have
to
call
it
today
again
I'll
just
express
some
gratitude
to
everybody
that
has
done
a
lot
of
work
into
getting
119
all
together.
We
just
got
a
couple
more
days
left.
I
think
we
could
probably
fit
in
you
know
a
couple
of
these
last
fixes
we
can
get
our
blog
posts
all
ready
for
release
and
then
yeah
we'll
be
pushing
that
out
on
saturday.
So
it's
very
exciting.