►
From YouTube: Backdrop Weekly - Feb 24th 2022
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
february
24th
2022,
and
this
is
the
backdrop
weekly
developer
call.
We
get
together
every
week
to
talk
about
priorities
and
things
that
are
happening
in
the
world
of
backdrop
specifically
core,
but
also
some
peripheral
projects.
My
name
is
nate
lampton,
I'm
quick
sketch
on
the
internet
and
I
am
coming
from
oakland.
California
we'll
do
some
other
introductions
of
everyone
on
the
call
we'll
start
with
joseph
and
then
we'll
go
to
robert.
A
Robert
greg
and
then
savashri,
if
you're
available,
otherwise
we'll
go
to
jen.
A
Thanks
sebastian
we'll
go
to
jen
and
then
justin.
F
A
Well,
I
hope
to
tell
us
about
those
justin
and
then
finally,
john.
G
H
A
All
right
thanks,
john
and
thanks
everyone,
let's
see
so
I
was
not
here
last
week,
so
we'll
probably
be
doing
a
little
bit
of
a
rehash
of
some
of
the
topics.
Last
week
before
we
get
into
backdrop
core,
we
usually
do
a
little
update
on
the
world
of
the
contrib
community.
Jen
you've
compiled
the
list.
Could
you
run
through
them
for
us.
F
Sure
so
I
don't
know
how
I
missed
all
of
the
modules
that
came
out
last
week,
but
I
wanted
to
mention
them
today,
because
we've
had
a
huge
flurry
of
activity
which
is
very
exciting.
So
last
week
we
had
views,
photo
grid
pack
and
upload
title
length,
active
tags,
advanced
text,
formatter
and
ip
anonymize,
and
I
I
think
I
only
mentioned
ip
anonymize
in
the
meeting
and
I'm
not
sure
why
I
missed
all
of
the
other
modules
that
were
released
last
week.
That's
fantastic!
F
A
Yeah
excellent
I've
also
been
seeing
all
those
come
in
also
before
we
we
carry
on
too
much.
Can
you
talk
about
the
homepage
changes.
F
Sure
so
this
was
revealed
in
the
design
meeting
in
the
last
hour,
but
we
did
get
nicole
orber
to
do
minor,
update
to
the
design
for
the
homepage
for
factor
of
semester.
Org
and
those
should
be
rolling
out
before
backdrop
live.
A
Great
all
right,
let's
see
so
every
week
we
have
a
post
that
is
created
on
bac
or
forum
dot
backdrop
cms.org
for
soliciting
topics
for
us
to
cover.
During
these
weekly
meetings.
There
were
two
posts
this
week,
one
from
indigozella
and
one
from
doc.
A
Beaumont
documents
is
in
regard
to
development
of
backdropcms.org
and
just
the
way
that
we
handle
web
hooks
coming
from
github
and
then
the
way
that
we
respond
to
them
on
backdrop,
cms.org
and
he's
looking
for
advice
on
how
we
can
debug
the
web
hooks
that
come
into
backdrop
cms.org
and
process
them
in
a
way
that
people
can
develop
like
local,
copies
of
backdrop
cms.org
and
make
adjustments
to
the
code
there.
A
That
includes
things
like
the
packager
that,
when
a
new
release
is
created
in
contrib,
it
sends
a
webhook
request
over
to
cms.org
backdrop,
cms.org
runs,
the
packager
creates
a
zip
file
updates
the
info
file
and
then
publishes
the
or
uploads
the
release
back
to
github.
I
think
that's
the
primary
web
hook
that
we
have
in
place
and
there's
two
there's
two
suggestions
that
doc
walman
has
put
forward.
A
I'm
guessing
that
not
only
would
we
need
to
have
a
dev
site,
but
we
need
to
give
people
access
to
the
dev
site,
so
they
can
make
changes
to
the
dev
site
and
test
things
yeah.
A
I
think
as
far
as
development
is
concerned,
that
might
be
a
little
bit
tricky
because,
usually
when
doing
development,
you
have
to
make
a
lot
of
changes,
and
if
we
have
the
dev
site,
we
then
we
need
to
have
it
like
be
reserved
for
an
individual
to
like
literally
modify
files
directly
on
the
server
or
you'd
end
up
with
like
a
a
really
busy
get
log
of,
like
you
know,
fixed
the
thing
fix
the
thing
too
fix
the
thing
three,
you
know
we're
just
like
pushing
and
pulling
every
every
change
there.
F
Already
have
a
beta
site
thanks
to
justin.
It
went
up
last
week
or
the
week
before,
and
it's
currently
I'm
running
on
a
beta
branch,
and
I
think
we
could
give
people
access
to
merge
changes
into
the
beta
branch
and
deploy
them
there
more
freely
and
then
once
we're
happy
with
stuff,
we
could
just
do
a
pull
request
against
the
live
site
and
pull
it
in,
and
that
would
clean
up
some
of
that
noise.
D
So
the
the
trigger
for
this
was
trying
to
troubleshoot
some
some
issues
with
the
packager,
and
my
understanding
is
that
if
people
want
to
test
it
on
the
local,
they
would
need
to
have
a
triggering
point
as
in
can
we
can
we
instruct
the
packager
to
listen
to
our
own
repository?
So
I
mean
when
we
clone,
we
fork
contrib
modules.
We
create
releases
there,
so
we
don't
affect
the
actual
contrib
and
then
and
then
our
local
copy
listens
to
our
version
of
the
contrib
module.
D
And
then
we
well,
of
course,
we'll
have
to
test
the
actual
thing.
But
in
the
preliminary
stages
of
troubleshooting
are
these
hardcoded
or
can
we
specify
the
endpoint
or.
A
They
are
hardcoded
by
the
configuration
of
the
web
hook
in
github.
It
points
at
a
particular
url
and
we
have
that
set
up
to
point
it
back
to
fcms.org.
So
we
can
point
github
at
whatever
url
we
want,
but
right
now,
there's
only
one.
I
think
we
could
probably
set
up
a
second
one
if
we
so
wanted
to
but
yeah
in
order
to
receive
them
from
github.
There
needs
to
be
a
public
address
that
github
would
actually
send
them
to.
C
So
sorry
go
ahead
and
open
it
there's
another
alternative
that
the
document
suggested,
which
was
this
service
called
ingrock
in
which
basically
you
set
that
up
and
then
it
looks
like
there's
a
free,
low,
low
duty
cycle
version
of
it
where
github
would
ping
ngrok
and
then
ngrok
can
mirror
that
out
to
your
actually
your
local
dev
site.
C
So
so
one
or
more
individuals
could
receive
the
web
hook,
things
on
their
local
system
and
then
do
all
their
development
there
and
try
things
out
and-
and
so
that
was
another
alternative
and
it
sort
of
would
have
would
avoid
the
problem
of
or
the
issue
of,
when
doing
a
lot
of
development
doing
a
lot
of
pushes
to
the
beta
site,
which
is
presumably
also
people
doing.
C
Civic
crm
development
are
also
tinkering
with
that
site,
and
might
you
know,
might
not
appreciate
it
going
white
screen
because
yeah,
because
a
dpm
call
got
left
in
or
something
like
that.
So
I
just
wanted
to
raise
that
kind
of
channeling
my
inner
doc
roma
as
another
alternative.
A
Yeah
this
looks
like
an
interesting
service.
It's
n,
the
letter
n
is
in
nate
gronk
g-r-o-k
com,
and
it
looks
like
it's
some
kind
of
thing
where
they're
a
public
service.
So
we
would
point
at
this
like
backdrop
backdrop.ingrock.com,
for
example,
as
a
recipient
of
the
web
hook,
and
then
you
would
run
a
local
process
that
is
connected
to
the
online
service
and
then
it
would.
A
It
would
forward
the
requests
from
the
public
url
to
your
local
computer,
making
it
so
that
you
don't
need
to
have
your
ip
address,
or
domain
name
pointed
publicly.
Instead,
this
website
is
the
public
thing,
but
then
it
forwards
the
requests
to
you
yeah.
It's
a
pretty
clever,
looking
thing
that
might
be
useful.
In
any
case,
they
do
have
a
free
tier
that
I
don't
think
we
have
a
lot
of
developers
working
on
backdrop
at
any
given
time
or
backed
up
cms.org.
We
might
be
able
to
make
do
with
just
that.
A
The
lowest
level
tier
put
that
into
our
one
password
for
the
devops
group,
the
people
that
are
members
of
that
and
if
I'm
not
sure
if
doc
won.
One
is
a
member
of
that
group,
but
if
he
is
not,
then
we
can
get
him
added
to
that.
Then
we
could
work
that
way.
A
Yeah,
it's
a
good.
It's
a
good
option.
Personally
I'll
say
what
I've
done
in
the
past.
For
for
backdrop,
cms.org
packager
problems
is
github
itself.
Has
a
history
of
every
web
hook
request
that
it
sends
and
then
a
record
of
the
responses,
and
so
usually
what
I've
done
for
my
local
development
is
I
create
a
test
package
in
contrib
and
then
I
go
over
to
backdrop
or
go
over
to
github
web
hook
log,
and
then
I
just
take
the
json
from
the
web
hook.
A
Example
and
I
copy
it
into
a
clipboard,
and
then
I
curl
my
own
local
computer,
with
the
logged
version
of
the
json,
and
that
way
I
only
need
to
recreate
one
package,
and
then
I
just
execute
the
curl
command
repeatedly
to
hit
my
local
to
test,
creating
the
package
that
way,
I'm
not
creating
a
package
creating
a
package
creating
a
package
to
make
the
web
request
happen
every
time.
A
Instead,
I
just
use
the
log
to
recreate
the
web
request
and
that
has
its
own
advantages
in
a
way
that
you
don't
need
to
actually
manually
initiate
the
web
hook
in
order
to
receive
it.
I
mean
you
only.
You
have
to
do
it
once,
but
then,
after
that,
you're
just
like
simulating
the
web
hook
happening
on
your
computer.
A
So
that's
that's
something
that
we
can
do
right
now.
I
don't
think
that
the
webgrok
ngrok,
I
think,
that's
a
good
idea
anyway,
but
I
don't
think
it
needs
to
be
a
barrier
really
for
development.
I
think
we
probably
need
to
either
get
a
log
to
document.
If
he's
working
on
these
things
or
if,
if
it's
possible,
we
might
just
also
just
give
duckwellmont
that
level
of
permission
to
see
the
weblog
history
directory
directly.
A
A
D
I
have
two
questions
so
so
no
questions
the
one
is
a
request.
It
seems
nate
that
you
have
done
this
before.
So,
if
you
could
document
like
even
bullet
points
the
process,
then
maybe
we
could,
we
could
do
it
and
this
would
be
a
viable
resource,
and
the
other
thing
is
that
the
method
that
you
described
still
requires
you
to
create
a
package
in
our
our
actual
official
contrib
group
right.
A
Yeah
it
does,
I
mean
well
in
a
way,
creating
a
release
on
our
contrib
group
is
no
different
from
creating
a
release
on
any
github
project
anywhere.
It's
the
same
content
that
will
be
sent.
So
really
you
don't
even
need
to
make
a
backdrop
contrib
project
you
can
just
make
a
release
anywhere.
You
want
in
your
own
personal
repository,
and
it
will
be
the
same
thing
as
far
as
the
web
hook.
Contents
is
concerned.
D
A
Yeah,
but
you're
right,
greg
documentation
would
help
tremendously,
I
think,
with
with
debugging
this
yep.
F
E
A
Okay,
let's
see
we
have
more
topics
to
just
to
discuss
so
we'll
kind
of
move
on
from
that
indica
indigozala
raised
two
questions:
around
access
functions,
there's
issue
5480,
which
is
around
file
access
and
then
issue
5517,
which
is
around
just
general
entity
access
functions
across
all
entity
types.
So,
in
both
cases
we
have
these
functions
in
the
case
of
files.
A
There's
file
underscore
access
in
the
case
of
nodes,
there's
like
node,
underscore
access,
taxonomy
term
access,
etc
and
the
file
access
one
there's
a
pull
request
that
she's
been
working
on.
A
That
makes
it
so
that
file
access
behaves
more
like
the
other
types
of
entities
and,
in
particular,
starts
dealing
with
view
access.
I
believe-
and
let
me
take
a
look
view
and
download
access
and
I'm
I'm
sure
that
indigo
asl
is
looking
for
more
specific
feedback
than
me
just
mentioning
this
issue,
but,
as
I
haven't
reviewed
this
poll
request,
yet
I'm
not
sure
I
can
provide
a
lot
of
valuable
feedback.
A
Does
anyone
else
have
any
familiarity
with
this
topic
or
have
something
that
I
could
go
off
of
as
far
as
providing
feedback?
Yeah.
D
I
think
that
the
indiegogo
and
rd
piano
were
working
on
these,
but
the
level
the
the
depth
of
knowledge
into
entity
space
required
did
not
at
least
allow
me
personally
to
contribute
other
than
saying
that
I
would
make
sure
that
these
are
brought
up
in
the
dev
meetings.
I
think
that
both
indie
godzilla
and
urdu
kian
are
basically
waiting
for
core
committees
for
direction
and
feedback.
A
Okay,
yeah
and
then
the
other
issue.
5517
is
pretty
similar
in
that
regard
that
it's
deeply.
Actually,
this
one
isn't
isn't
quite
so
bad,
but
both
of
these
are
very
technical
questions
about
like
what
should
we
possibly
do
for
these
things?
I
do
think
that
indie
gazelle
is
asking
this
thing,
as
one
of
the
alternatives
would
be
to
create
new
methods
in
all
core
entity
classes
to
check
access,
which
would
make
a
lot
of
sense.
A
But
yeah
there's
a
lot
of
methods
and
I
think
generally
indigozella
is
raising
this
concern
around
like
a
the
entity
system
in
backdrop,
is
not
fully
fleshed
out
that
there's
a
lot
of
holes
in
its
functionality
and
that
we
should
work
to
build
out
the
capabilities
of
the
entity
system
to
be
more
comprehensive
and
in
particular
to
make
it
so
that
energy
plus
is
not
really
dependency
for
so
many
modules,
and
so
I
think
we're
already
working
towards
that.
A
I
mean
I
say
we're
working
towards
that
as
a
community
in
particular,
really
isn't
a
godzilla
and
archie
piano
like
really
pushing
forward
on
improving
the
entity
system
substantially
and
robert
you.
You
too,
I
think,
you've
been
in
there.
A
Just
a
little
bit
so
I
appreciate
all
the
efforts
there
and
I
think
it's
a
it's
totally.
It's
a
worthy
cause
and
I
I
think
that
yeah
I'll
continue
to
try
to
provide
the
support
that
I
can
but
yeah.
D
A
We
need
to
do
some
fixes
there,
because
the
file
system
has
a
lot
more
capabilities
in
backdrop
than
it
did
in
drupal
7,
and
so
we
need
to
start
taking
into
account
the
fact
that
files
are
now
entities
that
are
fieldable
that
have
pa
they
have
pages
now,
like
all
the
functionality
of
media
module
in
drupal
7.
A
We
effectively
have
incorporated
a
lot
of
that
into
into
backdrop
core,
and
some
of
the
things
like
file
access
functions
haven't
really
caught
up
with
that
yeah
all
right.
Let's
see
I
want
to
do
the
status
report
update.
We
have
one
more
topic
about
the
drupal
end
of
life
announcement
that
came
out
yesterday,
but
I
think
that'll
probably
fill
up
the
rest
remainder
of
the
meeting.
So
before
we
get
into
that
I'll.
Do
a
quick
update
on
releases.
A
We
came
out
with
backdrop
121.2.
A
On
february
9th
that
includes
22
closed
issues,
which
is
a
great
release
for
us.
It
was
also
a
security
release.
We
had
a
a
corresponding
drupal
issue
that
that
we
had
to
make
a
release
for
at
the
same
time,
but
it
was
really
fantastic
to
get
out.
All
of
those
fixes.
We've
been
really
active
as
far
as
like
cleaning
up
a
lot
of
small
issues
in
core.
In
regards
to
that
backdrop,
121.3
the
next
bug
fix
release.
A
There
are
currently
30
open
issues
in
that
milestone,
three
of
which
are
rtbc
and
almost
all
of
which
have
pull
requests,
and
most
of
them
are
in
a
state
of
needs
review,
so
we're
in
a
really
excellent
spot
here.
As
far
as
getting
some
more
fixes
into
the
next
bug
fix
release
of
backdrop,
I'm
really
happy
about
the
amount
of
activity
that
we've
been
having
to
continue
cleaning
things
up.
As
usual,
we
get
kind
of
stuck
on
the
review
process
on
these
things.
A
So
if
there's
any
reviewers
out
there
that
are
interested
in
taking
a
look,
the
121.3
milestone
has
a
lot
of
issues
that
could
use
some
eyeballs
on
it.
A
A
Finally,
so
yeah
yesterday
there
was
an
announcement
from
the
drupal
community
that
drupal
7
currently
runs
about
50
of
all
drupal
websites
out
there
still,
despite
drupal
8's,
having
been
out
for
how
long
has
it
been
seven
seven
years
triple,
eight
has
already
had
its
entire
run
of
its
life
and
is
now
no
longer
supported
and
drupal
nine
is
out,
but
even
then
these
triple
seven
sites
keep
chugging
along,
and
so
it
had
been
scheduled
that
drupal
would
have
its
end
of
life
later
this
year.
A
A
They
haven't
really
specified
when
drupal
7
will
officially
cease
being
supported,
but
for
the
foreseeable
future
it
will
maintain
the
status
quo
of
being
a
community
supported
projects
that
new
releases
will
come
out
on
drupal.org
and
security
updates
will
continue
to
be
covered
well
past
this
year.
2022.,
we
just
don't.
I
think
they're
waiting
to
actually
see
the
data
as
to
like
whether
or
not
these
large
number
of
drupal
sites
will
ever
drop
off
and
when
they'll
stop
supporting
drupal
7..
A
The
way
that
this
affects
us
is
that
we
had
set
our
end
of
life
dates
for
backdrop,
one
based
on
the
end
of
life
of
drupal7,
so
with
triple
seven
having
an
end
of
life
and
in
2022,
our
plan
had
been
to
have
backdrop.
One
run
its
course
and
come
out
sometime
and
or
backdrop.
Two
would
probably
come
out
like
in
2024..
A
D
A
25,
excuse
me,
but
now
that's
not
really
clear.
Like
you
know
now
there
is
no
end
of
life
of
drupal
7
and
how
long
we
should
be
pursuing
getting
like
be
continue
being
like
the
lifeboat
for
drupal
7
users.
You
know
like
it's
not
quite
as
urgent
as
it
might
have
been
before
yesterday,
because
now
all
of
the
drupal
7
users
might
feel
that
there's
not
really
a
need
to
move
on
for
the
time
being.
F
We
could
also
be
a
little
bit
smarter
about
our
upgrade
path
too.
Knowing
that
we're
in
this
scenario
where
like,
if
we
want
to
release
backdrop,
two,
we
could
have
a
backwards,
compil
compatibility
layer,
much
like
our
drupal
ink
file.
That
could
be
like
a
backdrop,
one
that
contain
all
of
the
update
functions,
that
we
would
normally
remove
from
backdrop
when
new
version
came
out
and
then
that
way,
people
could
opt
to
turn
that
on
if
they
wanted
to
come
from
drupal
7
to
go
through
backdrop
2..
So
we
could.
A
Yeah
yeah
and
we
never
clarified
that.
Even
if
backdrop
two
were
to
come
out,
you
know
just
three
years
from
now.
If
it
would
still
include
an
upgrade
path
from
triple
seven
or
not,
I
don't
think
we
ever
really
said
that
it
wouldn't
the
idea
of
backdrop.
Two
primarily
isn't
really
around
new
features.
A
It's
about
cleaning
up
the
cruft
that
we've
acquired,
removing
all
of
the
deprecated
functionality
and
we
have
a
lot
of
functionality
within
backdrop
itself
that,
like
we,
have
a
lot
of
deprecated
things
that
we
introduced
and
then
deprecated
ourselves.
So
we
can
actually
remove
a
fair
amount
of
deprecated
functionality
without
affecting
in
any
way
the
users
that
are
coming
from
drupal
7..
A
We
do
have
a
lot
of
deprecated
stuff
from
triple
7
that
we're
carrying
around
as
well,
but
if
we
left
those
things
in
place
to
ease
the
transition
from
drupal
7
backdrop,
2
could
provide
us
an
opportunity
to
clean
up
our
code
base
from
deprecated
functionality
within
our
own
code,
but
not
actually
affects
the
users
coming
from
triple
seven.
A
Yeah
interesting
because,
right
now
the
drupal
wrappers
are
all
in
a
drupal
dot
inc
file,
yeah.
A
And
we
could
start
introducing
multiple
of
these
kind
of
like
deprecated
functionality,
wrappers
yeah.
It
doesn't
work
for
everything
but
you're
right
that
that
that
would
be
one
approach
we
could
use
to
kind
of
whisk
people
off
of
these
things.
Also,
we
have
the
drupal
deprecation
file
being
included
by
default
in
backdrop
one.
It
might
also
be
reasonable
for
us
to
to
turn
it
off
in
backdrop.
Two
again,
it
doesn't
really
affect
users
coming
from
drupal
7.
A
It
affects
the
porting
of
modules
from
drupal
7
and
really
like
using
any
drupal
namespace
function
like
drupal
set
message
being
a
really
typical
one.
It's
now
backdrops
that
message.
Hopefully
most
of
those
changes
have
already
occurred
over
the
last.
You
know,
seven
or
eight
years
that
the
backdrop
has
already
been
out-
and
I
think
maybe
moving
and
those
aren't
really
the
most
challenging
changes
to
make.
In
the
backdrop
code
base
either
like
it's
a
simple
find
and
replace
is
all
that
that
include
file
is
really
providing
for
us.
D
One
thing
that
I
would
like
to
point
out
is
that
the
dates
that
have
been
specified
by
the
drupal
community
are,
with
regards
to
drupal
7
core
a
lot
of
triple
7.
Contrib
maintainers
stated
that
they
will.
They
will
set
their
seven
dot
x
branches
as
unsupported,
so
it
doesn't
mean
that
drupal
7
site
owners
are
off
the
hook.
D
It
wasn't
clarified
whether
they're
going
to
be
security,
fixes
for
these
branches
or
that
the
contrib
maintainers
will
care
for
those.
So
we
might
be
discussing
now
with
relate
with
with
with
triple
seven
core
in
mind
that
it
will
be,
it
will
keep
receiving
security
updates,
but
site
owners
might
be
forced
to
to
seek
a
solution
sooner
because
of
contribute
push.
A
Yeah
and
that's
a
really
there's
a
poignant
example
of
that
that
colorbox
module
and
several
other
very
popular
modules
were
marked
supported
a
couple
weeks
ago
in
the
drupal
7
space,
and
we,
as
the
backdrop
community,
have
ports
of
these
modules
that
are
supported.
A
But
I
know
jen
in
particular,
had
to
go
through
like
several
hoops
to
try
to
get
access
to
the
security
issues
that
were
reported
to
drupal
so
that
she
could
then
fix
them
for
the
backdrop
versions,
but
as
a
part
of
that,
she
actually
ended
up
becoming
maintainers
for
the
drupal
7
versions
of
these
modules,
but
yeah.
That's
a
really
great
example
of
like
the
same
code
that
is
available
for
drupal.
A
7
may
end
up
getting
marked
unsupported
kind
of
permanently
because
there's
no
effort
in
maintaining
it,
while
the
port
of
the
backdrop,
port
of
that
same
module,
will
continue
to
be
supported
and
maintained.
And
so
it's
a
really
good
example
of
like
why
it
would
be
a
good
idea
for
a
lot
of
owners
to
get
their
sites
off
of
drupal
7
and
into
backdrop
if
they're
looking
at
it.
If
they're
looking
for
an
easier
transition.
D
And
also
there's
the
the
point
of
people
have
been
holding
on
to
off
with
finding
a
solution
in
order
to
see
what's
going
to
happen
in
that
space,
but
all
drupal
7
owners
have
not
been
getting
any
value
out
of
their
sites,
whereas
if
you
move
to
backdrop,
you
get
new
features
every
four
months
and
so
on
and
better
support.
So
there's
this
business
case
for
that,
so
we
need
to
be
aware
of
that.
So,
in
other
words,
what
I'm
trying
to
say
is
that
yes,
the
announcement
yesterday
is
is
good
news.
D
A
Yeah
it,
it
does
give
us
an
opportunity
if
we
so
wanted
like
if
we
change
what
backdrop
two
is.
You
know
we
could
release
backdrop
two
sooner
than
we
had
previously
planned
if,
if
we
so
wanted
to
as
long
as
like,
because
it's
like,
if
backdrop
two
keeps
its
current
definition
of
being,
as
you
know,
including
everything
that
we
have
right
now,
carrying
all
this
baggage
to
make
coming
over
from
triple
seven
as
easy
as
possible.
A
But
we
continue
to
tie
it
to
drupal
seven
like
we
don't
really
know
when
backdrop
two
would
come
out,
it
could
end
up
being
like
20
30
or
something
crazy
like
that.
You
know,
and
for
that
reason
we
may
want
to
change
our
plan
around
what
backdrop
two
is
because
it's
not
just
tied
to
the
end
of
life
of
drupal
7
anymore.
A
That
doesn't
mean
that
we
necessarily
need
to
move
the
date,
but
it
does
mean
that
we
need
to
change
the
approach
that
we
have
for
what
backdrop
two
actually
means
yeah,
but
now
it's
not
really
tied
to
the
date
either,
because
there
is
no
there's
no
trigger
point.
For
you
know:
drupal
7
end
of
life,
so
is
our
date,
doesn't
need
to
be
tied
to
the
previous
date
that
doesn't
have
any
meaning
anymore.
H
Do
you
see
the
updates
in
ph
in
the
php
world
as
something
that
might
drive
your
backdrop,
2.0
release.
A
What
yeah
it's
a
good
question
too
this
again
it
kind
of
comes
down
to
like
you
know
how
serious
we
are
about
our
our
backwards
compatibility
commitment
right
now,
we're
we're
kind
of
extreme
about
it.
Honestly,
we
just
in
we
just
merged
these
changes
that,
like
actually
we
haven't
merged
them
yet,
but
we're
increasing
the
minimum
php
version
of
php
5.6
for
backdrop,
1
22.,
but
you
know
php
5.6-
is
not
supported
by
the
php
community
nora's.
A
A
Yeah,
they
still
have
the
same
issue,
though,
where
operating
system
vendors
continue
to
backport
stuff
from
the
newer
versions
of
php,
so
the
lifetime
is
actually
a
little
bit
longer
than
it
is
of
of
php's
official
support.
The
os
vendors
continue
to
make
the
life
of
that
a
little
bit
longer.
A
H
I've
seen
two
things:
one
is
when
I
move
to
new
hosting
that
the
platform
is
coming
with
php
7.4
and
uncertain.
Certainly
it's
going
to
be
8.0
pretty
soon,
and
that
is
requiring
me
to
update
a
lot
of
modules
to
deal
with
php
syntax
changes.
H
The
other
thing
is
someone
who
has
drupal
6
sites
that
I
still
need
to
upgrade.
I'm
expecting
to
upgrade
them
from
drupal
6
to
drupal
7
and
from
drupal
7
to
backdrop
1
and
if
there's
a
backdrop
2,
then
I
would
just
go
from
backdrop
1
to
backdrop
2..
I
don't
see
that
as
a
huge
burden
for
someone
who's
upgrading
a
pretty
old
drupal
site
that
they
might
have
to
make
an
intermediate
step
along
the
way
to
get
up
to
something
that
supports
modern
php
and
has
the
legacy
code
removed.
A
Yeah,
that's
kind
of
an
interesting
thought
that
the
constantly
shifting
demands
of
php
could
actually
push
people
into
backdrop,
because
backdrop
does
have
support
for
the
latest
versions
of
php.
But
we
have
a
surprisingly
large
amount
of
support
for
pretty
old
versions
of
php2,
which
is
a
good
way
to
ease
people's
transitions
into
backdrop.
A
They
don't
need
to
set
up
a
new
server
right
away
to
move
on
to
backdrop,
but
if
they
do
move
to
a
newer
one-
and
we
encourage
that,
then
it
supports
all
the
way
up
to
the
latest
versions
of
php,
but
we're
running
into
kind
of
some
limitations
there
that
our
php
8
support.
For
example.
There
are
some
things
that
php
has
done
that
make
supporting
php
9
when
that
comes
out
and
php
versions
prior
to
7,
almost
impossible.
A
D
A
Actually,
it's
it's
unclear
if
this
is
really
going
to
be
a
problem,
because
even
within
the
within
the
php
community,
like
I
looked
at
some
of
the
announcements
that
they
made
and
it
was
like
a
pretty
even
split
between
they
have
a
voting
procedure
kind
of
like
we
do
only
there's
a
much
larger
number
of
people
that
vote,
and
I
think
the
vote
was
somewhere
around
the
the
scope
of
like
65
4
and
like
45,
against
the
proposal
of
creating
the
these
deprecations.
That
would
not
be
backwards
compatible
in
the
future.
A
So
there
was
actually
a
fair
amount
of
opposition
to
even
the
proposal
that
made
it
so
that
there
would
be
backwards.
Compatibility
breaks
in
the
future,
and
so
but
the
current
thing
that
ended
up
happening
was
that
they
proposed
a
backwards
compatibility
break,
but
there
was
an
easy
way
to
circumvent
it,
and
so
even
that
proposal
met
some
opposition.
So
it's
possible
that
when
it
comes
to
actually
pulling
the
trigger
and
breaking
a
lot
of
existing
php
code
intentionally,
that
timeline
might
get
pushed
off
further
than
just
php9.
A
H
I
know,
we've
talked
about
it,
but
people
here,
drupal
7
is
extended
and
they
think
I
don't
have
to
do
anything
and
and
their
contributed
modules
that
they
use
in
their
site
are
going
to
be.
You
know
hitting
very
yeah
very
very
rapidly,
so
we
should
make
sure
our
messaging
is
clear
that
it's
only
drupal
core
that's
been
extended.
A
All
right:
well,
I
guess
it
didn't
spur
as
much
conversation
as
I
thought
so
we're
here
at
the
kind
of
the
end
of
the
hour.
Does
anyone
have
any
other
topics
or
anything
they'd
like
to
to
bring
up.
A
No
okay!
Well,
we
will
close,
then
another
weekly
meeting.
Thank
you
all
for
for
joining.
As
always,
let's
see
I
feel
like
we
sh
because
tim's
not
here,
we
should
still
probably
make
an
announcement
about
backdrop
live
jen.
Would
you
be
able
to
just
talk
about
that?
Real
briefly
sure.
F
So
our
next
backdrop
live
is
coming
up
on
march,
11th
and
12th.
If
you
want
to
register
now,
you
can
you
can
sign
up
on
the
website,
you
can
leave
a
recommended
donation
of
any
amount,
and
if
you
want
to
have
a
conversation
about
something
specific,
you
can
take
a
look
at
the
schedule
and
see
what's
already
on
there.
But
you're
also
welcome
to
propose
your
own
discussion.
F
A
Based
on
registrations
that
have
come
in,
it
looks
like
this
is
going
to
be
a
pretty
exciting
event,
and
that
starts
two
weeks
from
tomorrow.
A
Okay,
well,
thanks
again,
everybody
we'll
see
you
all
on
the
internet.
I'll
do
my
best
to
try
to
get
some
reviews
in
on
some
of
these
things
that
have
been
brought
up
for
indiegozella
and
others
and
yeah
we'll
continue
working
through
those
bug
fixes
so
that
we
can
get
out
another
release
in
the
near
future.
So
all
right
thanks,
everybody.