►
From YouTube: Backdrop Weekly Dev 2021/09/30
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,
it's
september
30th
2021,
and
this
is
the
weekly
backdrop
developer
meeting
we
get
together
every
week
to
talk
about
the
latest
happenings
in
backdrop.
Talk
about
priorities
unblock
any
issues,
possibly
and
yeah.
We
have
a
short
little
meeting
here
today,
we'll
start
off
with
some
introductions.
My
name
is
nate
lampton,
I'm
quick
sketch
on
the
internet,
I'm
in
oakland
california,
and
we
have
some
fun
stuff
to
talk
about
today.
Let's
go
to
robert.
Can
you
give
an
intro.
C
Hey
I'm
tim
erickson,
I'm
paul
tim
on
the
internet
and
I
am
well
the
big
thing
for
me
this
week
is
a
backdrop
live.
So
that's
my
focus
three
weeks
from
tomorrow
is
the
next
edition
of
backdrop
live
so
start
getting
ready.
Folks,
I
wasn't
paying
attention
who's
next.
D
Joseph
hey,
I'm
joseph
I'm
from
las
vegas
nevada,
I'm
back
in
developer,
just
helping
where
I
can
justin.
E
Justin
christopherson
in
denver,
colorado
and
I
help
out
as
where
I
can,
as
well,
usually
with
infrastructure.
A
And
I'm
not
sure
if
you're
available
to
speak.
F
I'm
gonna
try
john
lampton
joining
from
sacramento
california
today
and
thanks
tim
for
all
your
work
on
backed
up
live
and
thanks
robert
for
all
your
work
on
the
doc's
site.
I'm
excited
to
look
at
that
later.
A
A
I'll
keep
going
through
the
agenda
here
jen
unless
you
wanna,
take
your
normal
parts.
I've
already
prepared
sections.
A
All
right
community
update,
we
have
a
new
contrib
application.
Human
shoe
0007
has
filed
a
application
to
contrib
application
request,
so
we
we
will
get
that
started
in
flight.
It's
a
little
bit
unclear
what's
actually
happening
with
this
request,
but
they
did
open
a
request
so
or
an
application.
So
we'll
try
and
move
that
along.
A
A
A
Let's
go
ahead
and
go
to
the
forum
post.
We
have
a
a
forum
post
every
week,
soliciting
ideas
for
things
that
we
should
talk
about
during
this
meeting
and
we
go
through
those
usually
first
one
issue
that
jen
raised
yesterday
or
maybe
the
day
before
was
issue
5251.
A
There
is
an
issue
in
backdrop
1.20
that
came
out
two
weeks
ago
that
the
listing
of
custom
blocks
is
pretty
badly
broken
when
we
were
making
the
machine
name,
changes.
Machine
names
now
consistently
styled.
Throughout
all
of
backdrop.
A
There
was
a
slip
up
in
the
implementation
there
that
made
it
so
that
the
listing
of
blocks
got
messed
up
pretty
badly,
but
the
fix
was
really
simple.
There
was
just
a
line
that
was
deleted
that
reset
an
array
back
to
an
empty
value
that
was
deleted,
and
so
we
restored
that
line
and
that
that
issue
has
already
been
merged
and
fixed.
A
I'll
go
ahead
and
skip
ahead
to
an
update
from
the
the
bug
fix
version.
So
1.20.1
is
the
next
bug
fix,
release
and
I've
gone
ahead
and
already
scheduled
the
release
for
taking
place
tomorrow
between
10
and
2
p.m
like
10
and
1
p.m.
Pacific
time,
so
that
issue
is
52
67..
A
We
usually
want
to
get
out
releases
of
the
bug,
fix
release
of
backdrop,
two
weeks
after
the
release
of
a
minor
version
anyway.
So
the
timing
is
all
working
out.
We
have
this
kind
of
big
problem
fixed
already
and
we'll
just
get
it
all
fixed
up
tomorrow.
A
Let's
see
also
indigozala
continues
to
push
forward
on
phpcs
code
style
linting
on
pull
requests.
That's
issue
5245..
A
The
latest
update
on
that
is
that
last
we
spoke
on
this
we'd
hoped
that
jeff's
repository
jeff
sarin
deputy
had
made
upgrades
to.
We
hoped
that
he'd
upgraded
his
repository
of
coding
standards
to
use
the
latest
version
of
phpcs
instead
of
the
old
version,
that's
actually
from
2014
that
drupal
7
uses,
but
unfortunately
his
repository
is,
is
also
just
a
fork
of
the
drupal
7
code
base.
A
It's
not
really
any
different
and
it
still
hasn't
done
the
upgrades
so
we're
at
this
point
where
we
need
to
kind
of
decide
if
we
want
to
bite
the
bullet
and
upgrade
our
php
cs
coding
standards,
there's
a
bunch
of
classes
that
determine
how
the
the
code
is
parsed,
whether
we
want
to
do
the
work
to
upgrade
them
to
the
latest
version
of
phpcs
and
hold
off
on
the
github
integration
or
if
we
want
to
go
ahead
and
use
github
integration,
it
goes
l
already
has
it
working,
there's
not
really
any
big
hold
ups
there
other
than
where
we'll
pull
the
repository
from.
A
Whether
we
want
to
go
ahead
and
use
the
integration
that
we
already
have
working,
that
already
does
a
lot
of
useful
things
for
us,
however,
uses
the
old
version
of
phpcs
or
if
we
want
to
do
the
work
of
upgrading
to
the
latest
version
of
phpcs
before
we
start
building
things
on
top
of
it,
so
that
issue
52
45
yeah.
It
would
be
interesting
to
get
some
other
thoughts
in
there
as
to
which
direction
we
should
take
it.
A
My
guess
is
that
indigozella
has
been
pushing
this
forward,
but
I
don't
think
that
she'll
want
to
put
forth
the
effort
to
do
the
upgrade,
because
it's
probably
a
substantial
amount
of
work,
but
she
got
us
into
a
great
place
here
where
it's
like.
Once
we
have
a
version
of
php
cs
that
we've
decided
on
like
we're,
we're
in
a
good
place
here
to
integrate
it
into
the
issue:
queue
all
of
the
integration,
the
github
action
and
stuff
like
that,
that's
all
ready
to
go!
A
All
right,
let's
see,
I
thought
I'd
put
it
into
the
end
of
the
agenda
here,
but
I'm
not
seeing
it
robert.
You
raised
an
issue
about
contextual
menu,
quick
access
for
editing
things
like
layout
theme,
etc.
The
issue
is
26
26,
a
nice
number.
B
Yeah,
so
the
issue
is
whether
to
create
a
contextual
set
of
contextual
links
for
the
layout
that
you
know
with
a
little
gear
icon
in
the
upper
right
corner,
that
you
can
click
on
and
go
to
configure
or
manage
blocks
or
from
a
suggestion
from
clonos
that
would
actually
list
what
layout
you
happen
to
be
on
and
so
for
site
builders.
It's
a
way
to
quickly
go
tinker
with
the
layout
of
the
current
page,
and
so
I've
gotta
change
prn
to
port.
To
implement
that.
B
However,
there
is
a
conflict
with
basis
theme,
because
the
the
standard
way
of
creating
contextual
menu
links
is
you
it
wraps
in
some
divs
around
the
content
that
that
the
link
applies
to
and
basis
tweaks
the
adds
a
negative
margin
to
the
top
of
the
body,
so
that
if
one
uses
the
default
placement,
contextual
links,
it
would
be,
it
will
be
covered
up
by
the
admin
bar.
B
So
choices
are
to
push
down.
The
content
can
just
for
basis
push
down
the
contextual
links
or,
for
everyone,
push
it
down
by
far
enough
to
not
conflict
with
basis.
But
then
it
comes
out
a
little
lower
on
seven
and
other
links
or
tweet
the
basis
code,
so
that,
if
you
have
both
an
admin
bar
and
contextual
links,
visible
things
come
out
in
the
right
place
and
but
but
that
has
a
cost
because
it
means
the
even
for
really
short
windows,
the
there's
still
a
scroll
bar.
B
B
Just
because
I
guess
there's
two
concerns
some
people,
think
contextual
links
are
a
little
confusing
and
don't
want
to
add
more
and
the
other,
and
maybe
this
functionality
should
be
in
an
admin
bar,
and
the
other
issue
is
the
concern
that
when
we
add
the
html
that
wraps
the
layout
it
it's
essentially
inserting
a
wrapper
layer
around
the
layout
and
that
might
mess
up
themes
or
css.
B
That,
for
example,
was
assuming
that
the
first
thing
you
encounter
after
the
body
tag
is
the
layout
tag.
So
that's
where
we're
at
there's
people
doing
pros
and
cons.
I
mean
people,
people
on
most
of
both
sides
advocating,
should
we
put
it
in?
Should
we
not
if
one
of
the
options
for
not
putting
it
in,
is
to
make
that
in
a
contrib
module-
and
I
got
a
draft-
contribute
module
that
I
posted
a
link
to
in
the
issue
queue
so
so
that
folks
can
try
it
out.
A
Yeah,
I'm
not
sure
I
can.
I
can
answer
this
directly,
but
my
thoughts
is
that,
if
basis
has
a
particular
need
because
of
some
css,
that
it's
added,
where
it's
adding
a
negative
margin
or
something
like
that
basis
should
also
include
in
its
code
any
adjustment
for
things
like
the
admin
bar
or
in
this
case,
contextual
links.
So
so
contextual
links
would
do
its
normal
thing
and
then
basis
would
also
include
we'd.
A
Add
new
css
to
make
it
adjust
the
contextual
link,
that's
there,
and
if
somebody
had
overridden
basis
or
used
a
sub
theme
or
something
that
override
that
wrote
that
css
file
well,
that
contextual
link
would
be
hidden
behind
the
admin
bar
and
that's
not
a
horrible
trade-off.
Jen.
You
want
to
say
something.
F
Yeah,
I
just
wanted
to
say,
like
basis,
is
a
really
good
barometer
of
how
hard
this
is
going
to
be
for
existing
sites
to
deal
with
a
change
and
the
fact
that
basis
has
to
implement
something
special
to
get
around
something
new.
We
add
in
core
should
be
a
huge
red
flag
that
you
know.
A
huge
number
of
contrib
teams
are
also
going
to
need
to
do
something
to
get
around
whatever
we
put
in
for
so.
If
we
are
going
to
put
something
in
that,
we
know
is
going
to
break
contrib
themes.
F
A
really
good
example
of
that
is
like
what
we
did
with
the
dismissible
messages
where,
if
by
default
it's
hidden
and
then
we
add
something
to
make
it
show
up,
then
at
least
we
don't
break
existing
sites.
We
make
the
new
feature
sort
of
optional,
and
that
might
be
one
way
that
we
could
address
that
problem.
A
Yeah,
a
pardon
me
that
thinks
that
this
might
minimize
impact
a
little
bit.
Maybe
not
minimize,
but
reduce
impact
is
one.
Nice
thing
is
that
contextual
links
themselves
are
like
always
administrative
only
so
we
won't
be
affecting
anyone's
public
front-end
presentation
and
I'm
not
really
sure
how
that
weighs
in
you
know
like
we
don't
have
a
calculator
for
like
backwards
compatibility
impact
calculator.
That
might
be
a
kind
of
cool
thing
to
put
together.
That
says,
like
is
this
a
change
acceptable
or
not?
I.
A
Yeah
yeah,
it's
kind
of
a
funny
idea.
Isn't
it
you
know
that
this
does
lessen
the
the
amount
of
impact
that
this
has.
A
I
think
that
this
is
a
big
gaping
hole,
though,
that
we
don't
have
any
way
to
see
what
layout
you're
on
and
to
just
edit
the
layout.
I
think
one
of
the
most
early
hacks
that
I
learned
in
the
very
ver
first
versions
of
backdrop
was
that
when
I
want
to
edit
a
layout,
I
edit
a
block
instead
and
then
I
close
the
dialogue
right
and
that's
just
like
yeah.
A
B
B
That
says
whether
you
want
to
push
down
the
the
contextual
links
for
the
default
theme
or
the
admin
theme,
and
so,
if
you
use
basis
or
a
sub
theme
of
basis,
you
can
just
check
that
box
and
it'll
get
pushed
down
and,
and
things
will
be
happy
and
we
could
conceivably
do
that.
If
it
were
in
core,
we
could
also
have
that
sort
of
a
a
checkbox
setting.
A
Yeah,
that's
what
I
was
going
to
say.
Describing
that
setting
is
sounds
hard
and
confusing
like
do
you
push
it
down
or
not,
but
actually
saying
do
you
want
contextual
links
on
layouts
at
all?
It
seems
like
a
better
question
to
be
asking
people
that
they
would
be
able
to
understand
and
that
this
gets
me
to
my
next
thought,
which
is
what
if
there
was
a
way
to
enable
and
disable
contextual
links
everywhere
they
are.
You
know
like.
A
I
want
to
turn
them
off
on
comments,
because
I
think
that
that's
stupid
having
them
on
comments.
You
know,
or
you
know,
I
want
to
turn
them
off
on
blocks
layouts
like
provide
an
option
to
turn
on
and
off
contextual
links
everywhere.
We
have
one
of
them
and
give
an
option
everywhere,
but
I
don't
know
if
that's
too
granular
or
unnecessary.
D
A
thought
so
in
drupal
7
there's
an
in-place
editor
for
panels
that
when
you
are
looking
at
a
panel's
page,
it
just
has
a
little
bar
at
the
bottom
with
a
button,
and
it's
just
the
normal
page
normally,
but
you
click
it
and
it
adds
drag
handles
and
style
things
and
buttons
to
all
of
the
elements
on
the
page.
A
It
does
do
that
yeah.
It
does
that
for
the
purposes
of
making
it
touch
accessible
because
the
hover
you
know,
contextual
links,
aren't
available
if
you're
on
a
touch
device
whatsoever.
A
So
yeah,
but
but
I
think
triple
is
still
like
backdropping
that
it's
dependent
upon
a
lot
of
rappers.
So
the
rappers
are
at
it
regardless.
A
But
then
it's
just
like
displaying
like
hide
or
show
the
the
little
edit
icon
on
everything.
A
A
If
you
did
turn
it
on,
it
would
probably
be
hidden,
and
you
know
same
as
if
you
were
hovering
over
with
the
mouse.
D
A
Okay,
well,
anyway,
those
are
some
thoughts.
You
know,
maybe
this
whole
like
having
a
setting
for
everywhere
that
you
turn
these
things
on.
Maybe
that's
also
like
going
too
far
with
things.
Maybe
we
just
need
some
mechanism
to
granularly
control,
which
contextual
links
are
turned
on
and
off
and
I'm
not
quite
sure
what
that
is
like
it
even
could
be
like
documentation,
like
maybe
here's
how
you
use
hook.
A
You
know,
contextual
links,
alter
or
something
like
that.
You
know
to
say:
here's
how
you
can
turn
it
off
easily
or
work
around
the
problem.
I
don't
know.
B
So
would
it
be
to
if
we,
if
we
just
consider
we're
going
to
turn
it
on
or
off,
would
it
be
too
broke
to
just
have
a
config
page
for
layouts
and
then
put
that
checkbox
on
that
config
page.
B
F
We
used
to
have
a
settings
page
for
layouts,
but
it
got
removed
with
the
flexible
layout
template
because
the
only
thing
on
there
was
the
layout
list.
So
the
slash
settings
page
isn't
actually
a
settings
page
anymore,
but
we
could
there's
an
issue
to
fix
that
and
put
one
back
so
that
this
could
be
a
good
bonus
to
do
that.
A
A
part
of
me
wants
to
make
a
setting
for
contextual
links
like
a
settings
page
for
contextual
links,
just
because
we
only
have
one
administrative
settings
page
on
the
whole
site
and
that's
the
settings
page
for
admin
bar,
and
so
when
you
go
into
the
admin
bar
and
you
go
under
administration,
there's
only
one
item
inside
of
there
and
it's
it's
admin
bar.
So
I
know
it's
a
little
confusing
me
saying
it,
but
admin
bar
is
the
only
settings
page
under
that
category.
In
the.
A
B
So
then,
and
then
we
use
books
for
other
modules
could
add
their
own
contextual
link
related
settings
to
that
page.
So
you
know
so
blocks
could
turn
on
and
off
their
contextual
lines.
A
Yeah,
I
I
haven't
looked
at
how
contextual
links
are
set
up
any
time
recently.
A
It
would
be
nice
if
modules
declared
when
they
were
adding
contextual
links,
but
I
don't
think
that's
the
case
right
now.
I
think
right
now
modules
all
just
say:
you
know
that
they
implement
hook,
contextual
links
or
something
like
that,
and
they
just
do
it.
You
know
that
there's
no
listing
of
all
of
the
possible
places
links
are
enabled.
F
A
A
But
yeah,
I
would
think
something
that
would
be
an
info
hook.
That
says
these
are
the
things
that
I
have
and
then
contextual
links
module
would
loop
over
all
of
them
and
just
provide
a
global
setting
like
turn
this
on
or
off.
So
each
module
wouldn't
need
to
like
alter,
provide
its
own
form.
There
would
just
be
like
every
module
would
say:
I'm
declaring
these
contextual
links,
because
some
of
them,
like
layout
module,
have
multiple
right
like
do
you
want
them
on
blocks
and
do
you
want
them
on
layouts?
A
You
know,
so
we
can't
just
turn
it
off
on
and
off
per
module.
We
need
to
actually
have
a
setting
like
per
place
within
that
module.
A
F
Well,
I
mean,
I
think,
like
the
problem
with
solving
is
a
huge
one
right,
like
layout's,
not
being
discoverable
and
not
knowing
which
layout
you're
on
that's
like
a
huge
issue,
especially
for
people
coming
from
drupal
who
don't
know
what
layouts
are
anyone
new
to
backdrop
who
just
can't
figure
out
which
page
they're
on,
and
I
think
that
having
a
solution
for
that
is
going
to
be
great.
F
My
only
answer
is
how
we
can
do
it
in
a
way
that
is
not
going
to
negatively
affect
existing
people,
and
I
think
we
talked
about
a
couple
of
options
of
the
ways
that
people
can.
We
can
work
around
that
and
I
think
that
moving
forward
with
it
on
any
of
these
directions
is
good.
B
Yeah,
so
how
about
if
we
sound,
like
we
put
the
put
the
contrib
module
out
there
now
or
and
but
say
this
is
going
to
migrate
into
core
fairly
soon,
and
then
that
gives
us
some
breathing
room
to
discuss
further
try
out
other
other
things.
We.
C
B
Oh
well,
since
the
module
hasn't
been
released.
Yet
if
there's
a
way
to
put
in
a
detection,
you
know
put
in
the
code
now
the
way
of
detecting
whether
it's
in
core.
Well,
I'm
not
sure
how
to
do
that
just
yet,
but
it
seems
doable
so
that.
F
I
mean
we
have
a.
We
have
a
process
for
moving
modules
into
core,
where
we
add
them
to
like
an
array
somewhere
and
it
when
the
like
update
hook,
runs
it'll,
disable
the
contrib
module
and
replace
it
with
core,
because
we've
done
this
with
a
bunch
of
stuff
like
ck
editor,
and
so
I
think
I
think
that's
not
going
to
be
an
issue
when
we
get
to
it.
C
A
Yeah
just
poking
through
here
it
looks
like
a
file
module
layout,
module
menu,
module,
node
module
and
views
module
are
the
ones
that
provide
contextual
links.
Why
isn't
comment
module
in
here?
That's
weird,
I
know
comment
module,
has
contextual
links
that
I
really
say.
Maybe
they
don't
in
backdrop.
I
don't
know
I
don't
like
them,
though
I
find
it
odd
because
there's
always
the
edit
link
everywhere.
You
see
a
comment,
and
so
it's
like
it's
weird
that
there's
two
two
ways
like
right
next
to
each
other.
A
Yeah
that
that
issue
that
was
raised
in
the
in
in
this
issue,
you
know
that
we
should
do
something
else,
other
than
contextual
links,
I
think
totally
should
be
like.
Let's.
E
A
That
into
a
separate
thing,
because
I
think
that
if
there's
an
alternative,
something
that
puts
up
in
the
admin
bar
or
something
like
that,
I
think
that
would
be
awesome
but
sounds
like
they
would
mostly
be
alternatives
to
each
other.
You
know
this
contextual
links,
module,
you'd,
turn
that
one
off
you'd
turn
on.
You
know
admin
bar
edit
or
whatever.
You
know
that
that
switches
that
behavior
into
admin
bar
yep.
B
So,
oh,
there
is
one
one
issue
as
part
of
that
pr.
There
is
a
bug
fix
to
contextual
module
which,
which
manifests
I
mean
manifested
in
this
development,
but
I
think
it's
a
real
bug
in
the
module,
which
is
that,
if,
if
you
have
nested
contextual
links
and
something
with
contextual
links,
wrapped
around
something
with
contextual
links,
the
current
behavior
pushes
the
inner
one
down
so
that
the
gears
don't
overlap,
which
is
good.
But
if
the
inner
thing
happens
to
be
really
narrow.
B
B
Maybe
that
should
be
a
separate
issue
just
for
that
behavior
in
a
separate
bug,
but
then
bug
fix
pr
just
for
that
behavior
and
so
pull
that
out
of
the
current
issue.
A
E
A
Okay,
well,
let's,
let's
move
on
from
that,
I
think
all
right!
Next
up,
let's
see,
we
don't
actually
have
any
other
issues
from
the
forum
post.
We
had
some
things
about
backdrop
cms.org
the
docs
website,
but
we're
separately
we're
gonna,
move
that
discussion
outside
of
the
meeting.
A
No
problem:
well,
we
just
wrapped
up
an
extensive
conversation
about
contextual
links
and
now
we're
on
to
other
items.
Let's
see,
and
where
was
I
going
next,
we
are
going
to
have
the
release
date
tomorrow
for
1.28.1
and
we
don't
really
have
any
other
1.2.1
issues
that
are
raised
here,
other
than
full
php
support
issue
5076,
but
there
hasn't
been
any
update
on
that
issue
this
week
for
1.20,
sorry,
1.21,
that's
the
next
minor
version
that
will
be
coming
out
january,
15th
2022,
yes,
tim.
C
Can
I
ask
about
the
bug
fix
release?
I
believe
that
the
little
new
notification
and
the
notif,
the
change
to
the
notifications
panel,
I
think,
was
rtbc
didn't
get
into
the
last
release.
Is
there
any
chance
of
getting
that
in
or
is
there
a
problem
with
that?
One?
Do
you
know
which
one
I'm
talking
about.
A
I
don't
know
which
one
I'm
sorry.
C
Me,
and
so
it
basically
just
puts
a
little
new
recent
flag,
or
so
no,
it
adds
the
date
to
the
notifications
in
the
the
dashboard
notifications
panel.
C
And
I
thought
it
was
rtbc
it
didn't
get
into
the
last
release.
It's
not
like
critically
important,
although
if
we
did
get
it
in
soon,
it
would
help
maybe
flag
people
about
backdrop
live.
A
Okay,
let's
see
so
1.21
that
comes
out
in
january
2022,
we
had
an
issue
that
was
moved
into
that
milestone
this
week
and
much
to
my
so
much
to
probably
everybody's
surprise,
the
issue
was
opened,
pull
request
was
filed
and
it
was
merged
all
together.
So
so
I
guess
I'm
just
gonna
say:
hey.
We've
got
a
new
feature
in
for
the
next
release
already
and
that's
a
cross
port
of
adding
a
anchor
option
to
the
scale
and
cropped
image
effect.
Issue
is
50.
A
80.,
gregory
and
herb
dual
just
tag:
teamed
that
one
and
knocked
it
out:
real,
quick
where
it's
a
simple
cross
port,
adding
new
feature
to
an
image
style
that
yeah
it's
a
real
real,
simple
fix,
but
it's
a
nice
new
feature.
A
All
right,
and
then
we
have
a
wish
list
item
here-
that
jen
added,
I
think,
issue
5044,
add
additional
css
classes
to
regions
for
flexible
layout
templates.
A
This
one
doesn't
have
an
advocate
yet
so
it's
not
officially
in
the
next
milestone,
but
I
think
maybe
jen
you're,
just
soliciting
hey
it'd,
be
nice.
If
someone
involved
yeah.
F
It
got
tagged
with
the
milestone,
even
though
it
didn't
have
an
advocate,
and
so
I
wanted
whoever
tagged
it
to
know
that
I'd
removed
the
tag
until
it
gets
an
advocate
so
that
if
they
want
to
be
an
advocate
for
it,
it
could
get
its
tag
back.
They
didn't
want
that
to
just
disappear
and
people
to
wonder
why
it
wasn't
in
the
release,
but
I
think
we
talked
about
it
enough.
We
can
take
it
off
the
weekly
agenda.
A
A
Well,
we
don't
have
any
other
big
milestone
items
in
1.21,
yet
the
idea
is
that
next
week,
we'll
have
a
more
of
a
planning
meeting
to
discuss
like
wish
list
items,
maybe
give
a
little
bit
of
prioritization
to
some
solicit
advocates
for
new
issues.
That
sort
of
thing
during
next
week's
meeting.
A
The
only
thing
left
on
the
agenda
for
today
is
we
have
one
active
initiative.
That's
telemetry
telemetry
has
clearly
moved
forward
quite
a
lot
in
1.20
we
have
the
telemetry
module
sites
are
reporting.
Now
I
haven't
checked
backdrop
cms.org
to
see
how
many
sites
are
reporting
yet,
but
I'm
just
going
to
go
good
luck.
Backdrop
telemetry.
G
It
seems
like
it's
collecting
mysql,
but
it's
not
exactly
collecting
whether
or
not
it's
marry
a
db
and
then
version
numbers
are
kind
of
goofy
on
the
database
side
of
things.
Because
of
that.
G
Looks
like
yeah,
it
seems
like
the
other
day,
the
the
10.1
or
10.1
10.2.10
they
weren't,
showing
up.
So
the
fact
that
they're
now
showing
up
is
good.
Maybe
we
just
didn't
have
enough
to
be
able
to
collect
those.
I
think.
For
the
most
part,
it's
probably
fine
on
the
version
for
now,
but
it
might
be
something
down
the
road
I
guess
to
differentiate
whether
it's
marry
a
db
or
an
actual
mysql.
A
Couple
of
other
things
like
the
github
action
that
we're
using,
for
example,
that
installs
different
versions
of
mysql
the
same
way
that
we
install
different
versions
of
php
for
our
automated
testing,
takes
one
setting
for
my
sql
version,
but
you
can
pass
in
10.2
or
10.5,
and
it
knows
that
that's
marie
db
or
you
can
pass
an
eight.
A
A
Very
true-
and
I
think
that
that
was
yeah-
I
didn't
even
think
about
procona.
A
Yeah,
I
wonder
if
we
should
start
segmenting
those
you're
totally
right.
We
can,
I
think,
separate
them,
but
I'm
not
totally
sure
how
that
would
work
like
because
all
of
them
all
use
the
my
sequel
driver,
like
backdrop
doesn't
know
or
care
really,
if
you're
using
mariadb
or
mysql.
It's
just
like
it's
the
same
too.
It's
all
using
the
same
php
like
pdo
driver.
It's
all
just
my
sequel
and
there's
only
one
database
abstraction
set
up
in
backdrop
and
that's
for
mysql.
A
D
The
database,
the
database
string
that
gets
reported
to
backdrop
has
the
version
the
which
program
it
is
in
it.
A
G
I
do
have
a
quick
question
regarding
telemetry
and
php
any
idea
if
there's
a
way
to
basically
ask
the
system
what
versions
of
php
are
available
on
the
system.
So,
for
example,
a
cpanel
sent
os,
you
can
have
multiple
versions
of
php
and
then
you
can
kind
of
flip
back
and
forth
between
them.
Is
there
any
way
to
query
the
system
and
say
yes,
I
know
you're
using
php72.
A
G
Okay,
yeah,
I
didn't
know,
if
maybe
at
least
on
the
linux
side,
if
there
would
be
some
kind
of
a
shell
command
that
could
be
run
or
something
to
just
do
a
quick
check,
whatever
the
output
is
then
be
able
to
return
that
back
for
telemetry.
The
idea
here
is
sure
we
can
figure
out
what
version
is
on
that
the
system
is
running
on
or
that
the
the
site
is
on.
G
We
may
have
a
lot
of
hosting
providers
out
there
that
the
site's
on
a
slightly
older
version,
but
it's
capable
of
much
newer
versions
and
greg,
brought
up
the
topic
of
trying
to
increase
the
minimum
requirement
for
php
to
at
least
five
six
everything
else
behind.
It
is
best
effort.
G
Personally,
I'd
like
to
see
that
pushed
up
to
seven.
But
again,
it's
kind
of
this
is
where
I
was
kind
of
like
hey.
Can
we
collect
telemetry
on
this
and
try
and
figure
out
do
these
people
that
are
still
on
version
five?
Do
they
have
access
to
seven?
Could
they
move
their
system
to
seven,
and
they
just
don't
know
that
they
can,
or
maybe
they're
scared?
G
I
don't
know
just
being
able
to
collect
more
data
to
be
able
to
make
more
informed
decisions
on
whether
or
not
we
could
move
the
minimum
requirement
up
without
impacting
a
lot
of
people.
I
guess
is
where
I
was
going
with
this,
but
it
may
be
too
early
in
this
discussion
to
even
try
to
go
that
route.
It's
just
kind
of
a
thought
that
I
had.
A
I
think
that
it's
a
good
idea
to
try
to
figure
out
ways
that
we
can
upgrade
the
php
version
because
really
like
in
the
past,
we've
kind
of
delayed
this
decision
because
we're
like
well
what
we're
doing
is
we're
supporting
the
oldest
version
of
php
that
is
supported
by
a
linux
vendor,
and
what
that
had
been
is
that
it
been
sent
os
has
the
longest
life
cycle
of
any
distribution
of
linux
and
centos
had
a
version
of
php
that
was
supported
up
until
like
the
end
of
last
year,
or
something
like
that,
and
now
multiple
things
have
happened
for
one
that
version
of
cenos
and
os6,
I
think,
is
now
completely
end
of
life.
A
So
php
5.3
has
zero
support
from
absolutely
anyone
at
this
point
and
second
of
all,
cenos
itself
has
been
discontinued,
so
so
the
longest
life
cycle,
linux
distribution-
is
now
basically
not
there.
So
it
probably
shortens
the
window
of
all
php
support
to
a
short
to
a
smaller
amount.
Now
also.
A
Yeah,
but
there
was
still
the
like.
The
lts
versions
of
linux.
Distributions
were
kind
of
where,
like
they
had
like,
debian
is
still
a
good
example
that
debian's
support
for
php
extends
past
the
support
window
for
php
itself.
So
php
only
officially
supports
it
for
like
a
year,
but
debian
will
support
it
for,
like
a
four
year
window,.
G
Now,
I'm
since
I'm
not
in
that
particular
side
of
the
industry
15
years
ago,
when
I
started
getting
into
this,
I
think
it
was
around
php,
5
5.1,
you
know
back
then
the
mentality.
The
mindset
was
you
get
on
that
version.
G
I
don't
know
exactly
what
they
have
done,
but
it's
more
of
almost
like
a
systematic
revisioning
kind
of
like
what
a
lot
of
things
are
going
to
in
the
industry
to
where
yeah
you
can
do.
These
incremental
upgrades
on
version
7
and
not
worry
so
much
about
things
just
completely
blowing
up,
but
the
enhancements
of
moving
from
seven
to
seven
one
to
seven
two.
It's
a
speed
boost
like
a
twenty
percent
speed
boost
each
incremental
version,
so
it's
kind
of
like
me
is
the
site
builder.
I'm
like
no.
G
G
I
don't
know
if
you
guys
have
kind
of
noticed
that
with
yourselves,
if
that's
kind
of
what's
going
on
with
the
industry,
maybe
it's
just
me.
I
don't
know
what
are
your
thoughts
on
that.
A
Well,
I've
noticed
that
tools
generally
like
cpanel,
like
you
brought
up,
are
way
more
flexible
now
than
they
used
to
be
like
moving
between
php
versions,
isn't
nearly
as
difficult
as
it
used
to
be
so
at
least
the
process
has
gotten
a
lot
easier.
A
Like
you
say,
there's
a
lot
more
carrot
now
that
things
are
generally
better
in
the
new
versions
of
php
and
a
lot
faster,
but
they
also
increase
the
stick
a
little
bit
by
shortening
those
support
lifetimes
so
yeah
the
php
is
definitely
pushing
everybody
towards
you
need
to
be
moving
faster
as
application
developers
like
you
know
they
they
don't
want
us
to
be
using
the
older
versions
of
php.
A
But
as
for
like
is
it?
Is
it
easier
and
or
like
what?
What
is
our
mentality
on
it?
I
don't
know
it
depends
on
the
hosting
provider.
I
think
a
little
bit
because
I
know
like
backdrop
cms.org,
which
runs
on
linux,
like
we've,
got
justin
who's,
maintaining
our
servers
for
us,
but
it's
not
running
a
fancy
infrastructure
like
a
platform
as
a
service
like
pantheon,
where
you
can
just
switch
it
and
then
it's
like
done.
It
actually
takes
like
a
fair
amount
of
effort.
E
E
A
Yeah
well
thing
I
think
is
is
clear:
is
that
we
need
to
revisit
our
minimum
php
version
and
possibly
our
policy
around
php
versions,
because
right
now
like
it's
getting
to
the
point,
it's
kind
of
like
internet
explorer
support
where
it's
like
it's
getting
ridiculous.
Like
we've
done,
our
we've
done
our
job.
A
You
know
supporting
these
old
things
as
long
as
possible,
and
it
really
is
like
time
for
us
to
consider
moving
forward,
even
within
even
within
the
one.x
release,
because
our
plan
for
the
2.x
release
is
that
it
won't
come
out
for
another
two
years.
Probably-
and
that's
it's
just
getting-
I
mean
it's
already
ridiculous.
Waiting
two
more
years
is
just
even
more
so.
G
We
had
a
perfect
world
we'd,
be
able
to
do
it
all,
but
it's
kind
of
one
of
the
things
right
now.
We
just
don't
have
the
overhead
to
be
able
to
handle
that.
So
I
I
love
that
we've
got
telemetry
going
because
I
think
that's
going
to
give
us
some
really
really
good
direction
on
making
decisions.
Hard
decisions
like
this.
So
that's
that's
freaking,
awesome.
A
C
Okay,
I
you
know
I'd
like
to
caution
us
to
realize
that,
like
for
php
versions,
it
might
be
a
year
or
two
before
it's
helpful
in
this
kind
of
backward
looking
way,
because
a
lot
of
the
people
that
are
using
really
old
versions
of
php
will
probably
not
be
you
know,
adding
telemetry
to
their
site.
So
we
won't
really
know
how
many
people
are
using
the
old
versions.
However,.
C
C
Now
we're
sort
of
in
policy
decisions
making
mode
there's
some
discussion
going
on
sort
of
at
the
pmc
level
about
you,
know,
opt-in,
opt-out,
stuff
and
all
of
that
and
how
we're
gonna
handle
that
I've
been
wondering
if,
if
the
telemetry
initiative
is
always
is
officially
like,
if
the
initiative
was
to
get
it
into
core
and
now
that
initiative
could
could
fade
away
and
we
could
just
continue
to
develop
it
or
if
we
need
to
continue
the
telemetry
initiative
to
develop
it.
C
I'm
not
sure
about
that,
but
anyways
yeah,
I
I
don't
have
answers
about
the
status
of
the
the
telemetry
initiative.
Really
right
now,
questions
because
we're
in
this
transition
period,
and
I
think
we
can
well.
I
I
feel
like
pretty
much
everything
is
going
to
be
I've.
I've
written
a
blog
post
to
a
draft
blog
post
sort
of
announcing
telemetry,
but
it
also
is
a
little
bit
on
hold
because
I'm
not
there's
some
policy
decisions
that
I
feel
like
need
to
be
made.
So.
A
Okay,
well,
I
think
many
initiatives
are
the
decision
point
of
when
it's
done
is
decided
by
the
lead.
So
that's
you
so
you've
got
to
decide.
You
know
if
the
initiative
itself
is
done
or
not,
but
yeah.
I
do
think
that
blog
post
is
a
good
idea,
but
definitely
a
good
idea
to
be,
like
you
know,
a
conclusion
point.
If
we
want
to
wrap
it
up
at
that
point,
that
would
be
a
good
place
to
just
put
it
all
together.
C
C
If
you
haven't
seen
it
I'll,
send
you
the
link
to
the
draft
blog
post,
and
it
could
be
that
I
could
just
read
out
some
of
the
policy
stuff
until
that's
more
official,
and
I
could
just
focus
on-
what's
happened
already
yeah,
as
opposed
to
where
it's
going,
although
I'm
just
I'm
a
little
bit
nervous
that
once
we
start
to
publicize
this,
then
right
away
we're
going
to
get
questions
about
the
policy
moving
forward
and
if
we
don't
have
those
answered,
maybe
it's
better
to
you
know
to
not
make
a
big
deal
about
it
until
we
have
answered
those
questions.
A
Interesting,
okay,
well
I'll,
take
a
look
at
the
draft,
you
know
and
we
can
kind
of
work
from
there.
A
Okay.
Well,
we
are
past
the
top
of
the
hour,
so
we
normally
wrap
up
about
now.
So,
let's
you
know
say
adieu.
Thank
you,
everybody
for
being
here
this
week
and
we'll
get
together
again
next
week.
That
will
be
the
planning
meeting.
I
don't
think
that
we
reopen
the
survey
correct
tim,
okay,
so
that's
fine,
we'll
we'll
probably
just
kind
of
come
with
ideas
and
start
like
you
know.
Hopefully
we'll
get
one
or
two
volunteers.
A
You
know
to
advocate
for
particular
issues
so
scour
the
issue
queue
for
things
that
are
of
interest
to
yourself
or
things
that
you
think
are
just
priorities
and
we'll
kind
of
start
kicking
through
them
next
week.
Okay,
well
thanks
everybody
for
being
here
this
week
and
thanks
for
out
there
for
watching
catch.