►
From YouTube: 2021/12/09 - Backdrop Weekly Dev Meeting
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:
everyone-
it
is
december,
9th
2021.
All
of
the
dates
are
a
little
bit
hard
for
me
to
believe.
Right
now
and-
and
this
is
the
weekly
backdrop
developer
meeting-
we
get
together
every
week
to
talk
about
the
main
priorities
and
features
that
are
happening
mostly
around
backdrop
core,
but
we
also
touch
on
other
parts
of
the
project
as
well.
B
A
Quick
on
the
internet,
core
commander
for
backdrop,
alejandro
is
only
gonna,
be
here
for
a
minute.
So
maybe
if
you
could
give
us
a
quick
introduction
and
then
we'll
go
to
robert.
D
I
am
tim
erickson.
I
am
otherwise
known
as
saint
paul
tim
and
coming
to
you
from
deerwood
minnesota
today.
A
Thanks
we'll
go
to
greg
and
then
we'll
finish
with
joseph.
E
Hi,
my
name
is
greg.
I'm
joining
from
greece
yeah
generally
interested
in
anything
related
to
backdrop
in
any
way
that
I
can
help
yep.
That's
it.
A
Nevada
all
right
awesome.
Well,
thanks!
Everybody,
let's
see
contributed
projects.
We
always
like
to
talk
about
the
new
projects
that
were
reported,
sometimes
the
ones
that
were
updated
in
the
contrib
world.
A
There
are
five
new
projects
in
the
last
week,
volume
pricing,
a
sub-module
for
ubercart
basic
entity,
plus
example,
which
is
like
a
demonstration
infotester
theme,
which
I
think
is
purely
a
a
test
case
theme
because
there's
some
other
updates
that
we'll
talk
about
later
in
the
meeting.
A
That
seems
to
be
related
to
that
and
then
there's
a
new
theme
called
scenery,
which
is
exciting.
We
also
were
talking
briefly
before
the
meeting
started,
that
there's
a
new
module
called
talk,
dot
two,
which
is
a
chat
bot
like
application.
It
seems
like
and
that's
an
integration
module
alejandro.
It
looks
like
I
think
you
were
a
part
of
the
porting
of
that
module.
Is
that
right?
Oh.
A
Okay,
well
one
thing
that
I
found
really
exciting
about
talk
to
the
implementation.
There
is
that
one
of
our
community
members
started
porting
the
module
reached
out
to
the
provider
to
ask
some
questions
and
the
provider
was
like:
oh
you're,
making
a
backdrop
module.
We
want
to
be
part
of
that,
and
then
they
did
a
lot
of
the
working
and
the
porting
and
then
put
it
up,
published
a
release
and
listed
themselves
as
the
primary
maintainer
for
the
module
so
very
exciting.
A
To
get
first
party
support
directly
from
a
provider
like
that,
and
they
just
like
yeah.
They
just
jumped
right
into
the
community
and
were
able
to
participate,
and
I'm
excited
just
that
well
that
they
did
that.
But
I'm
excited
that
the
process
of
like
a
first
party
vendor
coming
in
and
then
within
a
couple
of
days.
You
know
they
already
had
a
github
account.
They
created
a
new
project.
A
Then
they
published
a
release
all
within
a
very
short
window
of
time,
so
very,
very
cool.
I
like
to
see
our
processes
working
there.
A
Let's
see,
okay,
that
does
it
for
the
contrib
updates.
The
big
news
coming
out
of
the
past
week-
maybe
not
so
big,
but
we
had
a
release
on
friday
last
week.
It
was
a
little
bit
late
in
the
day,
but
we
got
out
1.20.3
as
expected,
and
1.20
to
3
is
a
pretty
big
collection
of
bug.
Fixes
actually
looks
like
about
a
dozen
bug
fixes
and
two
minor
changes.
There's.
A
Actually
we
actually
added
a
new
views
handler
so
a
new
capability
to
filter,
I
think
on
aliased
paths,
and
then
we
also
removed
a
bunch
of
ancient
hook,
help
implementations
which
aren't
used
anymore,
so
yeah
nice
little
collection
of
bug
fixes
there,
let's
see
let's
actually
go
to
before
we
move
too
far
away
from
the
contrib
updates.
The
infotester
theme.
A
That
was
one
of
the
items
that
robert
put
into
the
forum
post
for
this
week
that
there's
some
exciting
things
happening
around
the
capability
of
putting
more
information
in
dot
info
files
and
then
having
that
reflect
stuff
on
backdrop,
cms.org-
and
I
think
infotester
theme
is-
is
a
part
of
that.
So
robert
could.
Could
you
fill
us
in
on
the
what
what's
been
happening
there
and
if
you,
if
you're,
if
you're
familiar
with
the
contrib
project,
what
exactly
it's
doing.
C
Yeah,
so
the
info
tester
theme
is
really
just
a
demonstration
that
the
data
can
be
carried
in.
It's
it's
probably
going
to
get
deleted
before
too
long,
but
but
this
is
relates
to
a
couple
days
of
work.
The
last
this
last
week
by
doc,
wilmot
I
held
the
ladder
and
handed
him
screwdrivers,
but
he
was
doing
all
the
work
that
results
in
you
can
put
tags
in
your
info
file
and
those
will
get
carried
over
and
appear
on
the
on
backdrop.org
with
themes
you
can
there's.
C
C
You
can
also
add
screenshots
to
the
project
that
one
can
use
for,
let's
say
expanding
the
the
info
page.
You
include
screenshots
in
line
and
those
two
will
now
be
on
the
project
note.
On
b
and
the
last
thing
is
with
themes
you
can
select,
you
can
choose
the
colors
for
the
themes
and
those
show
up.
Then,
on
the
theme
page
and
the
info
tester
theme,
dummy
theme
illustrates
that,
with
with
a
couple
of
colors,
so.
E
Can
I
can,
I
ask
something
I
saw
the
maintainers
tag:
does
that
carry
along
like
to
user
names
in
beat.org
so
that
we
can
yes.
G
C
Yeah,
the
maintainers
also
come
over
there's
a
field
now
on
v.org
that
lists
the
maintainers
and-
and
I
think
that
info
testing
theme
has
those
fields
populated
so
most
of
the
work.
This
last
week
was
getting
the
handshaking
with
github
to
work.
C
We
need
to
document
all
these
things
and
also
work
on
the
presentation
of
how
and
where
they
show
up
there's
an
another
issue,
separate
issue:
that's
in
the
queue
on
that
was
raised
about
making
letting
people
search
or
filter
theme
to
filter
projects,
modules,
themes
layouts
according
to
various
criteria,
such
as
tags,
layouts,
and
so
that
too,
is
something
still
to
come.
A
Yeah,
that's
awesome.
Yeah.
I
didn't
see
that
the
colors-
that's
pretty
cool
that
that's
added
now,
but
yeah.
It's
not
actually
useful
for
finding
things.
Quite
yet,
but
that's
super
cool
that
that's
actually
that
that's
actually
being
added
we've
we've
had
support
for
images
haven't.
We
is
that
that
actually
brand
new.
E
We've
we've
had
it:
we've
had
it
in
the
project
browser
within
the
the
product
itself.
So
when
you
were
trying
to
install
themes,
they
would
bring
up
the
the
screenshot
files,
but
I
don't
think
that
these
were
declared
in
the
dot
info
files
that
were
screenshot
subfolder.
I
think.
A
E
That's
that's
what
the
ui
and
what
the
ui
of
the
module
that
you're
using
like
that's
what
they
do
in
dribble.org,
like
you,
see
a
screenshot
of
the
module,
and
then
you
get
an
idea
of
what
how
it
sort
of
changes,
the
ui
and
what
it
provides
as
features.
C
Think
the
the
there's
two
screenshot
fields
there's
a
single
field
which
is
just
for
the
for
the
feet
and
it's
for
the
themes
screenshot,
which
is
stored
in
the
usual,
the
possible
theme
places,
but
there's
also
this
projects
screenshot,
which
is
there
for
every
type
of
project,
modules,
themes
and
layouts,
and
that
can
be
used
as
to
accomplish
what
greg
describes.
E
Does
it
accept
multiple
ones
so
that
you
can
have
eventually
in
the
future,
like
pop-ups,
with
slideshows
of
the
the.
A
Yeah
so
there's
it
looks
like
there's
one
field,
that's
like
the
primary
screenshot
that
has
one
value
and
then
there's
a
multiple
value
screenshots
that
takes
multiple
yeah,
so
you
get
the
one
that
is
the
the
primary
and
then
then
other
ones
yeah.
This
is
this
is
fantastic.
This
has
been
a
long
time
coming.
You.
H
A
C
All
the
work
all
the
work
was
was
doc
wilmot.
I
just
pulled
things
to
the
server
and
erased
and
reported
back
if
it
was
showing
up
or
not.
Okay,
so
holding
the
ladder
and
handing
in
screwdrivers.
A
Oh
well,
that's
wonderful.
I
mean
yeah,
but
doing
the
deployment
has
always
been
a
big
hold
up
for
us.
So
thank
you
for
facilitating
that
and
a
big
big
thanks
to
andy
dromont
for
for
doing
the
work
on
the
implementation.
That's
that's
fantastic
because
we
get
stuck
on
this
stuff,
all
the
time
where,
when
there's
coordination
that
needs
to
happen
between
core
doing
stuff
and
the
backdrop
cms.org
website,
we
get
stuck
frequently
there.
A
So
I'm
really
yeah,
I'm
really
thrilled
to
have
you
guys
working
together
to
overcome
that
that
that
that
barrier-
hey,
that's
awesome.
D
E
A
Yeah
welcome
peter
sometimes
peter
is
you
know
just
listening.
Peter
is
bw
panda
on
the
internet.
Also
a
court
committer.
A
Joining
from
australia,
I
believe
all
right,
yeah,
that's
so
exciting.
Thank
you
for
the
update,
robert
and
thanks
again
doug
wilmot
for
your
work.
There.
A
Let's
see
another
thing
that
was
added
in
the
forum
post
for
this
week
into
gozala
posted
kind
of
an
unexpected
update
happening
over
in
jquery
ui,
that
a
new
release
of
jquery
ui
came
out,
and
she
says
that
you
know
we
should
work
towards
first
of
all
incorporating
the
new
version
of
jquery
ui,
because
it's
just
bug
fixes,
but
also
you
know.
A
If,
if
we
can,
we
should
start
looking
again
back
at
our
like
our
jquery
version,
we're
still
running
the
last
version
of
jquery
one.
We
should
try
to
work
towards
upgrading
towards
jquery
3
as
soon
as
possible.
Jquery
is
still
fully
supported.
Jquery
ui
is
kind
of
it's
kind
of
like
in
a
weird
spot.
Now,
actually
it
seemed
like
it
wasn't
going
to
get
any
more
updates,
but
now
they've
started
back
up
again,
also
exciting
kind
of
relevant
to
the
earlier
conversation
about
github
easing
the
development
processes.
Jquery
has
moved.
A
Jquery
ui
is
moved
on
to
github
for
the
first
time
ever,
which
I
think
will
probably
result
in
like
better
like
interaction
from
community
members
and
better
support,
I
think
just
because
getting
off
of
their
own
infrastructure
onto
github
will
lower
a
lot
of
barriers
for
them
as
well.
A
So
I'm
excited
that
that
development
backdrop
still
uses
jquery
ui
in
quite
a
few
places
and
because
backdrop
one
is
going
to
last
for
a
long
time.
You
know
through
what
was
it
2027?
I
think
we
were
saying
so
having
our
underlying
supporting
libraries
jquery
is
the
biggest
one.
Having
it
be
supported
for
a
longer
period
of
time
is
very
beneficial
to
us.
A
So,
yes,
you
didn't
really
go
into
anything
else
other
than
we
do
have
an
issue
for
upgrading
jquery
ui.
It's
3106.
I
think
we
should
probably
update
that
title.
Oh,
it
does
say
3.x
if
possible,
yeah.
E
Yeah
and
I
think
in
our
roadmap
page
where
we
list
so
we
list
the
current
version,
the
the
next
planned
version.
So
the
current
version,
which
is
120
the
next
one,
which
is
121..
E
We
have
goals
for
one
dot
x
and
then
goals
for
2.0
and
then
there's
a
big,
bold
sort
of
like
line,
which
is
a
link
to
the
the
forum
that
says
I'll,
actually
get
you
the
link
to
the
to
what
I'm
talking
about
which
says
black.
E
It
is
please
there
was
a
pmc
decision
that
was
to
settle
on
a
date
and
then
once
that
happened,
we
had
a
blog
post
and
then
I
linked
it
from
the
roadmap
page
to
posterity.
A
Okay,
yeah,
the
I'm
not
sure,
there's
been
too
much
discussion
discussion
on
this.
The
the
big
thing
with
jquery
is
that,
like
we
can
go
through
our
existing
code
base
and
find
the
deprecated
functionality
and
switch
our
code
base
from
jquery1
syntax
to
jquery,
3
syntax,
because
it
works
in
both
places
like
jquery
also
did
the
thing
where
they
deprecated
a
bunch
of
things,
and
you
need
to
switch
them
over
to
something
equivalent
in
the
newer
versions.
A
A
really
good
example
of
that
is
that
our
code
base
still
uses
the
bind
method
in
a
lot
of
places,
and
you
just
have
to
switch
that
to
the
word
on
instead
and
that
would
make
it
be
jquery
3
compatible.
That's
like
the
most
widespread
problem
that
I
know
of,
although
I'm
sure
that
there's
lots
of
other
things
in
there
as
well
so
going
through
our
code
base
and
making
it
jquery
3
compatible,
would
be
a
really
good
first
step.
There.
A
That
does
it,
I
think,
for
that.
The
items
from
the
forum
does
anyone
else
have
an
odd
and
not
an
odd
topic,
but
a
new
topic
they'd
like
to
discuss.
Otherwise
we
can
kind
of
go
into
like
a
status
update
round.
A
D
Tim
I'll
just
mention
I
did
that
we
announced
it.
Last
week
we
have
a
blog
post,
where
anybody
can
list
two
or
three
issues
that
they're
most
interested
in
for
the
next
release
and
that's
out
there,
it's
published
about
seven
people
have
added
some
topics
to
that,
and
I've
seen
some
progress
on
some
of
the
topics
that
were
added
to
that.
A
Yeah
I
haven't
looked
at
this,
yet
I'm
pulling
it
up
now
I'll
actually
share
my
screen,
so
we
can
actually
I'll
take
a
look
at
this
here.
We
are
so.
A
D
Actually-
and
let
me
point
out
that
I
believe
the
the
first
one
all
the
flips
did
says
it
needs
a
pr,
and
I
believe
it
has
a
pr
now
so,
which
I
you
know
hopefully
had
something
to
do
with
the
fact
that
this
blog
post
yeah
there's
a
pr
there.
A
Yeah,
it
looks
looking
great,
that's
exciting,
inline
formers.
That's
actually.
You
know
something
that
oh
wait,
not
inline
formers
this
one
custom,
validation,
error
message,
isn't
required.
E
E
Yeah
yeah,
so
so
I
had
a
second
review
from
bug
folder
and
then
I
fixed
something
and
then
yeah.
The
code
does
look
good,
but
it's
still,
I
think
I
broke
something,
so
I'm
still
trying
to
fix
things
anyway.
I
haven't.
I
haven't
gotten
the
chance
to
take
it
again
in
the
last
couple
of
days,
but
the
main
point
is
that
this
issue
is
basically
sort
of
like
a
prelude
to
1040,
which
is
the
inline
formers
and
there's
other
satellite
issues.
E
So
so
there's
some
cleanup
that
needs
to
happen
in
the
form
api
in
some
form.
Api
related
oddities
that
that
will
sort
of
like
make
it
easier.
So
I'm
not
sure
if
I'm
going
to
be
able
to
make
it
into
working,
I'm
not
saying
no.
I
could
there's
plenty
of
time
into
the
actual
inline
errors,
but
I'm
hoping
to
get
it
as
close
as
possible.
E
Like
lay
do
the
ground
work
for
it.
E
Yeah
and
the
other
one,
the
other
one,
is
it's
not
listed
there?
It's
because
it's
a
task.
I
think
it's
the
one
to
automatically
trim
spaces
from
start
and
beginning
of
text
fields
like
on
the
form
api
level.
A
Oh,
that's
right,
yeah
and
then
robert's
list
here
this
first
one
has
me
really
excited
actually,
which
I
haven't
been
keeping
super
close
tabs
on
this.
But
I
really
like
the
concept
here,
especially
we
have
this
problem
right
now
that
it's
really
hard
to
place
a
contextual
link
for
editing
the
layout
of
a
page,
because
the
entire
page
is
the
layout
conceptually
here
trying
to
find
a
good
screenshot
here
we
are.
A
It
adds
this
option
here
for
editing
things
that
are
on
this
particular
page
of
which
there
can
be
lots
of
things
that
could
be
happening.
You
know,
you've
got
the
current
node
you've
got.
The
current
layout
looks
like
the
current
theme
is
being
in
here.
Yeah
robert.
Is
there
more
that
you'd
like
to
say
about
this
one?
I
I
hope
I'm
summarizing
it
correctly.
I
haven't
read
it
too
deeply
into
it.
C
Yeah
just
that
we
have
to
actually
have
two
approaches
that
this,
the
one
that
you're
on
right
now
is
one
that's
peter's
put
together,
which
puts
it
in
the
admin
bar
other
approach
was
to
do
it
as
a
contextual
length,
and
it
sounds
like
the
ground
swell
of
opinion
is
moving
toward
the
admin
bar
approach
so
but
that
sounded
like
it
was
pretty
close.
C
Oh
after
run
remind
myself,
let's
see
yeah,
so
this
one.
These.
A
That's
great
speaking
of
oh
well
complexity,
field
group
functionality
in
core
tim's,
going
big
here
as
being
a
primary
advocate
for
this.
This
issue.
D
I
primarily
felt
like
I
wanted
to
put
one
from
our
our
survey.
This
is
the
top
one
on
our
survey
and
I
I
felt
like
I
wanted
to
get
one
of
those
on
here.
I'm
getting.
D
I
haven't,
seen
any
movement
on
this,
so
I'm
getting
the
sense
that
this
is
probably
not
going
to
happen
in
the
next
release
unless
some
miracle
happens
in
the
next
week.
So
my
you
might
pull
that
off
this
list
because
I
just
don't
know
be
practical.
If
anybody
thinks
it
is,
you
know,
because
we've
got
a
couple
of
weeks.
D
I
don't
know
how
you're
aware,
but
there's
been
a
bunch
of
work
on
the
my
understanding
for
the
field
group
functionality
and
core
was
that
we
didn't
want
to
include
the
field
group
module,
but
there
has
been
a
bunch
of
work
happening
on
the
field
group
module,
as
well
as
the
the
other
reference
module,
and
I
it's
unclear
to
me
if
there's
some
folks
that
think
we
should
put
the
field
group
module
into
core-
or
I
don't
know,
but
that's
maybe
another
reason
why
this
isn't
going
to
happen
quickly
because
there
may
be
differing
opinions
on
it.
D
A
Yeah,
it
is
kind
of
like
a
like
entity.
Reference
module
herbdull
has
been
been
doing
a
lot
of
work,
refactoring
that
module
to
make
it
so
that
it
could
conceivably
be
put
directly
into
core,
and
the
same
thing
could
be
done
with
field
group,
module
and
contrib
that
it
could
be
refactored
in
a
way
that
would
prepare
it
for
better
inclusion
directly
in
core
yeah.
A
I
don't
I
don't
know
the
status
of
this
it'd
be
like
I
think,
field
groups
like,
I
honestly
think,
it'd
be
a
little
bit
weird
to
be
able
to
turn
off
the
field
group
module
like
once
it's
there.
It
seems
like
it
should
just
always
be
there.
You
know
it
seems
like
that
would
be
a
strange
thing
to
selectively
have
available
on
some
sites,
but
not
others,
but
I
guess
that
that's
also
the
case.
For
you
know
some
of
our
field
modules,
for
example,
like
turning
some
of
them
off,
might
also
be
unusual.
A
Joseph.
Do
you
want
to
add
something.
F
Yeah,
so
for
the
there's
kind
of
a
lot
of
things
with
the
field
group
module
and
also
the
display,
suite
module
and
then
greg
at
one
point
was
talking
about
working
to
integrate
some
of
the
features
from
a
drupal
module
called
dream
fields,
and
I
feel
like
it
would
be
better
to
actually
do
like
an
overhaul
of
the
field
ui.
Rather
than
throwing
a
bunch
of
contrib
modules
in
that
kind
of
tack
things.
On
top
of
it.
A
Yeah,
that's
a
that's
a
really
good
point,
because
there
has
to
be
some
pretty
significant
altering
on
that
form
to
to
make
it
work
yeah.
I
think
I
think
this
was
the
same
sort
of
thing
when
we
did
editors
like
ck
auditor,
in
core,
we
had
the
same
sort
of
issue
where
there's
the
filter
module,
which
provides
all
of
the
filtering
capabilities
in
the
world
of
drupal.
They
made
a
second
module
called
editor
module
that
modified
the
behavior
filter
module
to
like
it
changes
the
names
of
the
menu
items.
A
Interesting,
I
wonder
what
that
would
mean
for
the
contrib
module,
then,
in
the
event
that
we
did,
that
reworking
yeah,
we
need
to
find
make
sure
that
both
continue
to
work.
A
All
right,
let's
see,
provide
hidden
path,
content
type
and
core
needs
feedback.
How's
this
one
coming
along
tim.
This
is
the
basically
adding
a
card
content
type.
D
Yeah
so
good
question:
we
I've
got
a
new
draft
of
this
with
more
content,
which
is
kind
of
the.
I
think
our
biggest
obstacle
will
be
just
settling
on
the
right
content
that
we
want
to
add.
But
there
is
a
kind
of
a
blocker
that
some
of
us
tried
to
address
last
week,
whereas
I've
included
some
images
and
we
need
to
create
some
content.
D
So
we
create
some
sample
content
and
we
import
the
images
and
I
got
it
working
on
my
local
laptop,
but
there
seems
to
be
some
issue
with
tugboat
and
the
way
temple
builds
the
the
issues
that
the
the
pr
or
the
sandboxes
are
not
building
the
content
correctly.
Specifically,
the
images
we're
having
problems
with
these
images
and
I
had
doc
wilmont
robert
bw
panda.
D
All
the
help
trying
to
help
me
solve
this
in
in
the
office
hours
two
weeks
ago,
and
none
of
us
could
figure
out
what
was
going
on.
I
don't
know
if
anybody's
that
was
helping
has
had
any
further
thoughts
since
then,
but
I
can't
update
the
pull
request
until
I
figure
out
why
the
tugboat
isn't
creating
these
images.
The
way
we
need
them.
D
I
will
provide
a
screenshot
in
the
issue,
so
we
can
at
least
talk
about
the
content
from
a
screenshot,
but
it
would
be
nice
to
figure
out
the
problem
with
the
tugboat
and
I
believe
those
of
you
who
were
there
agree
that
the
problem
is,
I
think
we
we
kind
of
did
enough
debugging
to
realize
that
tugboat
was
doing
something
weird,
but
nobody
quite
understood
what
was
going
on
robert
does
that's.
C
How
you
were
there,
do
you
remember
yeah?
The
problem
was
that
when,
when
the
code
ran
to
copy
the
images
into
the
managed
files,
the
urls
that
apply
to
the
image
were
scrambled
or
didn't,
didn't
make
sense,
and,
and
so
it
was
unable
to
to
perform
that
file
copy,
to
get
the
file
into
the
right
place
on
tugboat.
G
I
think
also
specifically,
to
do
with
install
profile,
because
when
you're
in
a
pull
request,
sandbox
website
in
the
interface
and
you
enable
a
developer
module
and
you
run
the
php
code,
you
can
print
out
like
the
root
directory
and
it
works
fine.
It
shows
the
proper,
proper
urls,
but
in
the
install
profile,
I'm
wondering
if
that
hasn't
been
set
up
properly
at
that
point
in
the
process
yet-
and
maybe
that's
had
an
issue
so
the
install
profile
along
with
tugboat,
doing
something
a
bit
weird.
A
All
right
well
yeah,
it's
possible,
maybe
even
probable,
that
you
know
if
it's
causing
a
problem
for
tugboat.
It
could
also
cause
problems
on
various
environments,
so
yeah.
I
think
it's
it's
important
and
good
that
we
get
that
figured
out
the
process
for
getting
those
images
created
initially
would
be
important
for
the
first
time
experience
of
all
new
users.
So,
okay,
let's
see
and
then
this
negative
visibility
condition
for
roles.
I've
not
heard
of
this
feature
before.
D
F
A
Yeah
we'll
keep
going
here
yeah
this
issue,
599
trim
summary
on
word
boundary.
That's
the
issue
that
peter
is
advocating
for
here
already
has
a
poll
request
that
is
in
a
needs,
review
state.
I
say
already:
this
is
opened
back
in
2020,
but
it's
definitely
seen
a
lot
of
movement
and
activity
right
now.
So
this
is.
This
is
moving
forward
pretty
quickly.
G
A
That's
great,
let's
see
and
then
two
from
laren
view
mode,
not
accessible
from
user
or
comment
field
templates.
A
I
don't
quite
understand
that
from
the
comments
but
well,
it
looks
like
there
hasn't
been
anyone
else
that
has
looked
at
this
yet,
but
we'll
need
to
take
a
look
at
this.
Larry
has
filed
a
pull
request
for
it
hide
the
run.
Database
updates
slash
next
steps
if
there
are
no
next
steps
boy,
what
a
great
idea.
A
There
is
a
good
reason
to
have
it.
There
be
a
button
that
the
button
clears
the
caches,
even
if
there's
no
updates,
because
sometimes
even
if
there's
no
updates
a
cache
clear
is
necessary
after
doing
an
upgrade
between
versions.
So
the
button
actually
still
does
something,
even
if
it
says,
there's
no
updates.
So
we
might
need
to
look
into
that,
but
yeah
I
I
this
is
the
first
time
I'm
looking
at
this
issue
so.
A
Yep
yeah
there's
lots
of
things
that
are
incorrect
about
this,
though,
like
how
it
like
stops
on
the
third
step
you
know
like
in
the
sidebar.
It
would
be
nice
if
it,
you
know,
put
you
on
the
last
step.
If
there
was
nothing
to
do,
you
should
be
done
right.
You
shouldn't
be
stopping
before
you
get
to
step
four
and
five.
E
There's
a
similar
bug
in
the
installer
when
you
install
modules,
I
either
have
filed
an
issue
or
it's
like
one
of
my
pet
peeves,
where
it
says
install
modules,
install
things
and
then
I
don't
know
enable
them
right
at
the
end.
So
these
two
steps,
the
enable
install
modules
and
themes
are
shown
all
the
time
independently
of
whether
you're
installing
a
theme
or
not.
A
E
So
so
it's
just
small
tweaks
in
the
user
experience
that
don't
make
sense
or
they
make
things
look
you
know
broken
or
not
accurate.
I
should
say
not
not
broken.
A
Yeah,
well
that
does
it
for
the
blog
post.
Thank
you
tim
that
that
is
very
helpful.
To
have
those
things
and-
and
like
you
say,
a
lot
of
these
things
have
moved
forward,
even
since
they
were
put
into
the
blog
post.
Let's
see,
there's
more
issues
here
yet
that
are
in
the
1.21
milestone.
E
A
I
know
this
one
we
really
want
to
get
in
as
soon
as
possible.
That
document
has
added
a
search
or
quick
filter
to
the
testing
page,
which
is
super
helpful,
so
yeah.
We
want
to
get
this
one
in
as
soon
as
possible.
I
also
like
that
doc.
Mulmon
has
has
put
in
the
time
to
do
this
on
the
simple
test
page
because
it
also
there
are
other
places
that
could
use
these
quick
filters
like
the
permissions
page
and
try
and
think
of
some
other
other
ones.
E
Have
issues
actually
yeah
another
issue
for
us
I'll,
try
to
find
it,
and
this
is
not
listed
there,
but
the
meta
issue
was
more
about
provide
a
consistent
way
of
doing
it,
so
provide
a
single
mechanism
that
even
module
developers
could
take
advantage
of
in
core.
Instead
of
having
to
you
know,
custom
code,
these
filters.
A
Yeah,
which
my
opinion
on
this
may
or
may
not
be
feasible,
but
yeah
because
really
like
we
want
it
to
be
on
all
places,
and
if
it's
consistent,
you
know
that
would
be
great
and
better,
but
if
it's
not
consistent,
just
getting
it
getting
this
functionality
out,
there
would
be
priority
over
making
it
generic
so
yeah.
So
so
great
example
here,
like
we're
not
going
to
hold
up
the
generic
implementation
or
hold
this
up
on
the
generic
implementation,
we'll
go
ahead
and
merge
it.
A
Let's
see,
I
saw
also
that
this
issue,
5.6
dropping
support
for
5.6
and
lower,
has
been
herb.
Duels,
like
you
know,
let's
go
ahead
and
move
forward
with
this
yeah
which
I'm
not
really
opposed
to,
but
I
do
think
that
it's
worth
like,
we
need
to
discuss
like
how
we're
going
to
communicate
this
like
when
we'll
need
to
do
it
soon.
If
we're
going
to
drop
it
in,
you
know
the
release
coming
out
in
january
tim.
Do
you
have
any.
D
E
Yeah,
I
think
nate
back
to
the
point
this.
What
triggered
her
bill
to
make
this
comment
is
that
indie
godzilla
again
mentioned
that
we're
running
nine
tests
now
so
three
for
each
php
version,
and
she
was
sort
of
like
concerned
that
we
especially
now
during
the
period
when
we
have
this
rush,
pre-pre-release
brush,
that
we're
going
to
have
releases
being
blocked.
Sorry,
if
the
pipeline's,
the
the
gitlab
run,
is
run
for
too
long
like
you
can
queue
things
up,
but
if
they
wait
for
too
long,
they
get
cancelled.
G
I
don't
know
much
about
this
issue,
but
just
when
you
set
about
having
to
try
and
get
this
done
quickly
to
get
into
the
next
release,
I'm
wondering
if
it
would
be
better
to
something
like
this
for
a
dropping
support
for
a
whole
version
that
people
may
still
be
using
if
it's
better
to
make
it
one
of
the
first
things
we
commit
after
the
next
release.
So
that
way,
there's
a
whole
dev
cycle
where
people
can
upgrade
the
dev
version
to
test
it
before
we
officially
drop
it
in
the
next
version.
E
Yeah
and
actually
I
wasn't
suggesting
that
we
drop
support,
we
make
it
like,
we
don't
eventually
break
things
for
them,
but
we
sort
of
like
stop
testing
it,
so
potential
breakages
might
come
in
and
and
we
make
it
a
best
effort
policy.
So
we
still,
if
it's
an
easy
fix,
we
still
fix
it
and
support
it,
but
we
don't
have
our
infrastructure
run
tests
on
it.
We
don't
yeah.
A
Yeah,
I
think
I'm
not
sure
I
would
agree
with
that.
I
think
that
if
we're
dropping
support
for
it,
because
there's
some
pretty
there's
some
things
that
are
really
easy
to
do
in
the
newer
versions
of
php,
like
the
short
syntax
short
array-
syntax,
for
example,
that
if
it
gets
encountered
like
it,
will
completely
die
on
an
older
version
of
php,
and
so
I
think
that
I
mean,
if
we're
gonna
support
it
on
like
a
best
effort
basis.
A
That's
almost
what
we're
doing
right
now
is
supporting
on
a
best
effort
basis,
because
yeah
either
either
we
support
it
or
either
we
drop
support,
and
then
we
can
start
using
the
new
syntaxes
or
if
we
say
that
we're
supporting
it
on
our
best
effort,
then
we
kind
of
still
need
to
run
the
tests
on
it
because
otherwise,
we'll
inevitably
break
something
like
it's
just
gonna
happen,
because
nobody,
I
say
nobody,
none
of
the
developers.
The
core
team
is
running
those
old
versions
of
php
at
all,
and
so
the
only.
E
Yeah
and
that's
that
was
the
counter
argument,
so
the
country
argument
was
that
php,
7
and
8
are
so
similar
that
why
should
we
have
tests
for
both
seven
and
eight?
We
should
only
be
testing
latest
age
and
then
still
support
the
tests
for
five
point
six.
So
the
goal
that
indeed
godzilla
suggested
was
that
we
reduced
the
the
tests
from
from
nine
to
six
either
way
we
would
achieve
that.
We
just
need
to
decide
which,
which
sort
of
like
set
of
tests,
we're
going
to
drop
the
five
ones
or
the
seven
ones.
D
A
Yeah,
I
I
think
it
would.
I
would
feel
a
lot
better
about
it
if
pmc
did
vote
on
it,
but
I
called
on
you
because
it
has
to
do
a
lot
to
do
with
communication,
and
you
know
telling
our
users
hey
we're,
dropping
support
for
an
old
version,
several
versions
of
php,
and
I
think
that
that's
really
important
that
we
communicate
that
with
lots
of
runway.
A
So
I
I
also
maybe
this
is
marked
you
know
for
the
next
release,
purely
because
we
don't
have
to
a
milestone
for
two
releases
out,
yet
it's
either
1.21
or
it's
2.x,
and
I
think
that
we're
saying
you
know
this
needs
to
happen
sooner
than
2027.
D
Let's
check
in
with
the
pmc
on
this
one,
but
two
you
know
what
I
think
the
pmc
is
going
to
want
is
advice,
sort
of
from
the
core
team
as
well
in
terms
of
what
what
they
think
and
what
the
implications
are
and
what
the
process
would
be
right.
Because,
if
we're
going
to
vote
on
this
like
yeah,
I
mean
I
do
think
it
seems
to
me
like
anything
like
this-
should
have
a
couple
months
lead
time
right.
G
Yeah,
I
agree,
I
think
once
if,
if
or
when
the
pmc
makes
a
decision
to
drop
support
for
whatever
old
version
make
a
decision
at
a
date
for
whichever
release
it
matches
up
with
and
then
say,
hey
and
then
start
putting
out.
Communications
like
on
this
date
we're
going
to
drop
support.
So
not
necessarily
this
next
release,
but
a
future
one
and
then
start
telling
people.
E
D
Think
I
think
indigozella's
point
was
maybe
that
this
was
a
temporary
change
in
how
we
tested
things
until
after
the
rush
just
because
it's
going
to
be
more
of
a
problem
right
now,
but
it
hasn't.
Apparently
it
hasn't
been
a
problem
for
the
last
two
months
right
but
she's
concerned
that
we're
getting
into
this
rush
and
it
will
be
a
problem.
I
think
there
have
been
one
or
two
instances
of
it
happening
already
and
she's
just
envisioning.
It's
gonna
start
happening.
E
More
is
there,
is
there
any
plan
upgrade
plan
on
github
that
we
could
be
sort
of
like
upgrading
just
on
these
periods,
just
to
make
sure
that
we
don't
run
out
of
resources
and
then
scale
it
down
or
is
that
what
we
get
from
the
free
thing?
Does
anyone
know.
A
We
have
yet
to
reach
out
and
ask
if
we
can
have
more
runners
than
that.
The
the
thing
I
know
is
that
github,
regardless
of,
if
you're,
paying
them
or
not
only
has
one
speed
of
runner,
so
this
runner
speed
will
stay
the
same,
but
it's
a
matter
of
how
many
you
can
run
concurrently
and
we've
not
asked
to
see
if
we
can
increase
that
at
all.
A
So
far,
I
personally
haven't
seen
it
be
much
of
a
problem
because
the
limit
is
20,
and
so,
even
with
our
current
thing,
we
can
still
test
two
pull
requests
at
a
time
and
the
and
the
total
testing
time
is
about
seven
or
eight
minutes.
So
it's
not
really
been
too
bad.
As
far
as
needing
to
wait
long
periods
of
time
for
your
tests
to
execute.
E
That's
why
I
asked-
and
I
added
a
comment
to
ask
and
then
indicazella
said:
yes,
she
saw
it
happening
at
pull
requests.
He
was
waiting
for
other
pull
requests
to
finish,
and
then
it
was
just
canceled
because
it
reached
the
timeout.
I
think,
of
two
hours
or
one
hour
or
something
like
that,
and
then
it
sort
of
like
the
tests
never
run.
A
All
right,
well,
first
thing:
I
do
think
it's
important
that
we
get
this
php
version
one
sorted
out,
I'm
not
sure
about
skipping
php7
and
leaving
the
gap
there
in
the
middle,
but
yeah
we
could
try
it
and
see.
If
that's
preferred.
A
A
The
number
reduce
the
number
of
tests
being
run.
D
Should
open
a
github
issue
just
talking
about
what
how
to
handle
this
in
that
we
should
mention
the
option
of
reaching
out
to
get
up,
and
maybe
that's
the
first
step,
but
we
have
to
be
prepared
that
this
could
become
a
big
problem
a
few
days,
maybe
as
people
gear
up.
Maybe
it
won't
and
if
it
is,
what
are
we
going
to
do
until
we?
D
B
A
Well,
let's,
let's,
let's
come
back
to
that,
I
think
let's
see,
I
don't
think
that
there's
really
much
else
on
the
milestones
to
discuss.
I
mean
we
do
have
getting
telemetry
enabled.
I
think
that's
really
important
that
we
sort
that
out.
Maybe
updates
on
that.
Yet.
D
Right,
I
mean,
I
think
there
is
a
there's,
a
technical
aspect
to
that,
but
there's
also
a
policy
issue.
I
think-
and
if
I
understand
correctly,
we
really
need
the
pmc
needs
to
make
a
policy
decision,
and
that
is
being
discussed
right
now,
although
we
need
to,
I
think,
push
a
little
harder
on
getting
that
decision
made
quickly,
but
yeah,
I'm
pretty
sure
that
that
that
that
we
can't
do
anything
on
this
without
a
pmc
decision.
D
But
I
don't
know
what
technically
has
to
happen
as
well,
probably
well,
if
the
main
issue
is
whether
it's
on
or
off
by
default,
that's
probably
pretty
trivial
right.
A
Yeah,
I
think
that
that's
the
key
thing
I
I
had
forgotten
that
until
you
mentioned
it,
that
this
is
about
a
policy
decision
about
whether
or
not
something
should
be
opt-in
or
opt-out
right
right.
B
A
Yep
and
yeah,
I
don't
think
that
technically
there's
anything
challenging
there.
There
is
the
I
mean
that
separate
issue
about
where
the
check
boxes
go.
You
know
that's
a
technical
thing,
but
we
already
have
the
implementation
ready
over
there
as
well
like
if
we
were
to
go
that
route,
so
I
don't
think
there's
any
large
technical
challenges
here.
It's
really.
A
D
Nate,
are
you
in
a
a
rush
after
the
meeting
or
I
have
because
I
have
another
question,
but
I
don't
know
if
you
have
time
to
answer.
A
Yeah,
let's,
let's,
let's,
let's
maybe
wrap
up
the
meeting
and
then.
D
B
A
Well,
yeah,
it
is
like
it
is
the
top
of
the
hour.
Now
we
got
through
a
lot
of
stuff
today,
there's
very
exciting
things
happening
in
the
contrib
space
on
backdrop,
cms.org
in
the
core
space
we
have
a
new
release
for
the
bug
fix
version.
It
was
a
very
busy
week.