►
From YouTube: February 3, 2022 - Backdrop Weekly
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
All
right
we
are
live
today
is
thursday
february
3rd,
and
this
is
our
weekly
developer
check-in
meeting
before
we
get
started
with
items
in
the
agenda,
we
should
go
around
and
have
everybody
introduce
themselves
if
you
could
share
your
name
and
where
you're
from
and
anything
fun
you
want
to
share
with
the
group.
That's
not
currently
on
the
agenda.
That'd
be
great
I'll,
be
happy
to
go
first
and
after
me,
it'll
be
nate
and
then
he'll
take
over
assigning.
A
Who
comes
next,
so
my
name
is
jen
lampton,
I'm
joining
from
oakland
california,
and
I
am
very
excited
about
all
the
activity.
That's
happening
in
the
backdrop
right
now,
turning
it
over
to
nate.
B
Thanks
jen,
my
name
is
nate
lampton,
I'm
in
oakland
california,
and
I'm
a
core
committer
yeah.
Today
we're
going
to
be
doing
some
122
planning
excited
to
get
started
on
that
and,
let's
see
I'll
continue
the
introductions
we'll
go
to
martin,
followed
by
joseph.
C
I'm
martin
I'm
in
the
uk
and
I've.
I
have
my
first
first
taste
of
doing
a
pull
request
on
car
and
I'm
just
looking
to
find
out
how
I
can
get
more
involved.
B
Awesome
thanks
martin
joseph,
if
you're
available
to
speak
and
then
robert.
D
B
We'll
come
back
robert
and
then
greg.
E
I'm
robert
lang
bug
folder
on
the
internet,
coming
to
you
from
el
dorado
california,
I've
gone
various
odds
and
ends
lately
since
modules
and
documentation.
B
Thanks
robert
greg
and
then
wilbur.
D
I
am
greg
I'm
joining
from
greece
generally
interested
in
helping
out
wherever
I
can
no
news
that
come
to
mind
now.
Thanks.
B
It's
craig
wilbur
and
then
joseph.
F
Can
you
hear
me,
go
ahead,
hey
it
works.
Okay,
I'm
joseph
I'm,
a
backend
developer
from
las
vegas
nevada
and
I
am
having
technical
problems
with
my
microphone.
B
All
right
thanks
joseph
and
thanks
everybody
for
for
joining
today's
meeting,
like
I
mentioned
today,
we're
hoping
to
turn
an
eye
towards
122.
Today,
that'll
be
the
next
release
of
backdrop
that
comes
out
may
15th.
B
B
I
think
that
may
be
the
bulk
of
what
we
discussed
today,
but
we're
definitely
also
open
to
hearing
ideas
about
things
that
should
be
in
122
things
that
you're
excited
about
working
on
or
things
that
we've
been
trying
to
get
done
for
a
long
time
that
maybe
this
time
will
be
the
release
and
yeah
that's
kind
of
going
to
be
the
topic
for
today
before
we
get
into
that
jen.
Do
you
have
any
updates
from
the
contrib
side
of
things,
you're,
muted,.
A
B
Fantastic
and
from
the
forum
post
over
on
forum.backdropcms.org,
we
have
an
event
posted
every
week
to
collect
topics
for
these
weekly
meetings.
Asynchronously
and
doc.
Wilmot
left
a
post
in
there
pointing
at
issue
4582
that
there
is
a
bug
in
the
relationships
handling
of
layout
module,
in
particular
layout
relationship
author
from
node.
B
So
this
is
a
new
feature.
I
believe
that
we
added
the
ability
to
pull
the
author
from
so
starting
with
the
node
context.
You
can
then
add
in
a
user
context,
pulling
from
the
author's
the
author
node,
the
node's
author.
There
we
go,
but
it
looks
like
in
the
case
of
if
you
do
this,
for
a
node
that
comes
from
the
path
like
node
slash,
10.
B
It
doesn't
necessarily
get
you
the
author
of
node
10,
like
it
like.
You
would
expect
so
he's
asking
for
some
eyeballs
on
that.
One
looks
like
he
just
opened
this
four
days
ago,
and
we
have
some
things
to
discuss
in
here.
I
I'll
say
right
now
that
the
way
that
contexts
are
added
to
the
layout
object,
I'm
not
super
thrilled
with,
in
the
first
place
that
we
do
this
loose
mapping
system.
B
Where
inside
of
the
context
array,
the
key
really
matters
a
lot
that
if
it's
a
numeric
key
and
the
key,
is
one
for
example,
that
means
that
the
context
is
associated
or
coming
from
the
first
path
in
the
menu
position,
which
is
a
little
bit
confusing.
So
one
would
be
the
node
context,
for
example,
as
opposed
to
zero.
B
But
if
you
were
at
a
path
that
had
the
note
multiple
context,
it
might
be
one
for
the
object
coming
from
the
second
part
of
the
path
and
then
three
for
the
object
coming
from
the
fourth
part
of
the
path,
because
it's
zero
indexed
and
that's
and
then
there's
also
keys
that
are
just
things
like
logged
in
user
that
have
strings
in
them.
B
So
it's
like
this
mess
of
like
numeric
keys
that
are
menu
path,
locations
and
then
strings
that
are
just
kind
of
arbitrary,
and
I
don't
really
like
the
way
that
that
works,
but
I'm
not
sure
that
we'll
be
able
to
change
it
anytime
soon,
because
those
things
have
meaning.
But
it
might
be
nice
if
we
could
not
be
so
dependent
upon
the
keys
and
come
up
with
some.
B
Some
other
way
that
more
clearly
identified
where
these
contexts
were
coming
from,
I'm
not
sure
if
that
will
actually
factor
into
this
particular
issue,
but
it's
also
possible
that,
because
the
context
system,
the
way
things
are
keyed,
is
so
confusing
that
that's
the
root
of
this
problem
that
either
we
overwrote
a
key
and
introduced
a
bug.
Because
of
the
funny
way
the
contacts
are
listed
or
there's
a
misunderstanding
in
attempting
to
get
the
right
context,
and
maybe
it
is
correct.
B
After
all,
it's
definitely
something
that's
pretty
easy
to
get
mixed
up,
so
I
don't
really
have
anything
else
to
say
really
on
5482,
because
it'll
take
some
diving
in
to
get
more
information
on
that
one
robert,
I
think
you've
done
a
fair
amount
of
layout
work
as
well.
No
I'm.
E
Done
a
little
on
layouts,
but
this
this
is
new
to
me.
B
Well,
I
hope
I'm
hoping
I
could
recruit
you
to
help
triage
on
this
as
well.
Maybe
maybe
we
can
figure
it
out
together,
I'll.
B
Okay:
well,
that's
the
item
that
we've
got
from
the
forum
post
today
and
then
we'll
take
a
look
at
122..
B
The
first
item
that
we've
got
that
I
think
needs
to
be
completed
as
soon
as
possible
is
issue.
39.92,
dropping
support
for
php
earlier
than
5.6
earlier
less
than
so
we're
gonna
issue.
39.92
is
where
we
established
the
policy
on
this
we've
already
put
into
121
the
current
release,
big
red
errors.
B
That
say,
if
you're
running
an
older
version
of
php
prior
to
5.6,
it's
now
throwing
errors
on
the
status
report,
saying
that
you
got
to
get
off
of
5.6
or
get
off
of
5.3,
5.4
or
5.5
as
soon
as
possible,
because
the
next
release
coming
out
may
15th
will
not
support
it.
B
So
in
issue
93
92,
we
I
filed
a
pull
request
to
go
ahead
and
increase
that
minimum
php
version
there's
a
constant
in
bootstrap.inc
that
lists
the
minimum
version.
There's
a
couple
of
kill
switches
where
backdrop
just
absolutely
refuses
to
run
on
anything
lower
or
anything
below
the
minimum.
Php
version
that
we
specify
which
got
moved
up
to
5.6
in
that
pull
request
and
then
there's
a
large
number
of
workarounds
for
older
versions
of
php.
B
So
there's
all
those
three
changes
and
I
think
all
three
of
those
things
have
been
taken
into
account
in
that
pull
request.
But
we
have
a
mysterious
problem
with
the
test.
Runner
that,
for
whatever
reason
I
it
looks,
kind
of
like
a
php
doesn't
have
right
access
to
the
file
system,
possibly,
but
it
seems
to
be
specific
to
github
actions
and
possibly
the
setup
php.
B
B
It's
kind
of
a
frustrating
little
problem,
so
I
think
the
next
step
there
is
to
what
what
I'll
I'll
try.
But
I'm
saying
this
out
loud.
So
if
anybody
else
wants
to
try
as
well,
install
the
github
command
line,
tool,
github
cli
and
then
the
github
actions
cli
as
well.
So
that
way
you
can
run
github
actions
locally
through
docker,
rather
than
needing
to
run
the
workflows
as
pull
requests
and
then
once
running
those
locally
it'll
be
easier
to
debug.
B
Exactly
why
this
isn't
working
correctly
rather
than
pushing
a
thousand
changes
up
to
github
and
having
github
run
the
actions
so
we're
a
little
bit
stuck
on
that
particular
point.
We
could
bump
the
php
version,
but
not
increment
the
tests
that
are
running,
but
I
like,
we
really
kind
of
need
to
get
that
figured
out,
because
our
test
should
be
running
on
the
minimum
php
version,
and
so
we
we
can't
go
running
5.5
seems
a
little
bit
weird
and
then,
if
you
go
upwards
to
php
7,
it's
like
completely
different.
D
B
I
did
not
see
that
oh
this
is
so
great.
I
didn't
see
since
she
just
posted
this
last
night.
It
looks
like
there's
a
general
problem
with
their
tests.
Okay,
I
filed
a
separate
pr
issue
for
this.
D
Yeah,
so
this
is
the
one
that
I
was
referring
to,
but
the
the
pr
for
the
one
that
you're
saying
39.92
from
what
I'm
looking
at
the
pr
that
andy
gozell
has
put
together.
There's
an
inline
comment
that
says
any
files
for
five
six
are
in
it.
It
is
php,
whereas
in
private
versions
it
used
to
be
in
user
local
php,
so
it
used
to
be
different
locations
of
the
p,
php
and
e.
So
I'm
not
sure
if
that's
the
issue
but
yeah.
B
Okay,
well,
this
is
good,
should
I
include
the
fix
okay.
Well,
let's
at
least
start
with
the
other
pull
request
that
she
filed.
That's
issue,
40,
sorry,
54.90,
that
she
fixes
some
paths
but
yeah.
I
don't
think
that
this
will
solve
our
underlying
problem,
but
she
seems
to
have
kind
of
a
better
idea
than
I
do
about
what's
happening
here.
B
D
D
B
D
B
B
Yeah,
it's
like
it's
probably
like
if
the
php
can,
if
the
configuration
file
isn't
found,
something
like
the
the
path
rewriting
might
not
work
like
htaccess
might
not
be
picked
up,
or
something
funny
like
that,
so
it
might
be
like
the
tests
that
are
using
clean
urls
are
all
failing.
That's
a
pretty
common
consequence
of
the
web
server
being
misconfigured.
B
That
would
explain
why
some
tests
pass,
but
most
of
them
don't
that
would
do
it.
Okay!
Well
awesome.
While
I
was
going
to
ask
for
more
help
but
looks
like
help
has
already
helped
has
already
arrived:
that's
fantastic,
okay,
great!
Well!
That
puts
us
in
a
really
good
spot.
Then
I'll.
Take
another
look
at
that.
That's
issue
39.92!
B
Let's
see,
let's
go
to
the
next
okay!
So
now
we'll
run
through
the
other
issues
that
got
bumped
from
121.
and
the
first
up
I'm
going
to
go
to
yours.
Greg
custom
required
validation,
messages,
issue
5348..
D
That's
yeah,
that's
that
was
like
98.99
there.
I
just
last
minute
discovered
something
that
was
not
working
as
expected
in
the
in
the
search
form
as
it
wasn't
retaining
the
search
them
properly
after
the
form
was
submitted.
D
I'll
I'll
put
some
details
because
I
failed
to
go
back
and
document
what
the
problem
is,
what
what
what
was
holding
it
up,
but
I'm
trying
to
figure
out
the
last
details.
It
was
a
bit
tricky.
I
gave
it
a
couple
of
tries
but
I'll
make
sure
that
I
post
what
the
problem
is
there
because
others
might
help.
B
Okay,
great
all
right,
I
see
peter
has
joined
us
peter.
Are
you
able
to
speak
right
now?
We
were
going
through
the
issues
that
were
bumped
from
121,
one
of
which
is
599,
the
trim
on
word
boundary
for
which
you're
an
advocate
and
I'm
not
sure.
If
you're,
I
mean
we're
kind
of
springing
this
on
you,
since
you
just
showed
up,
but
if.
A
B
Able
to
give
us
any
kind
of
update
or
we
can-
we
can
loop
back
around
if
you
would
prefer.
G
I
can
well
I
can
try.
I
mean
I
haven't
looked
at
it
much
lately,
since
I
think
we
bumped
it,
but
the
situation
was
that
there's
trimming
on
word
boundaries
so
maybe
making
it.
So
it's
not
trimming
on
like
paragraph
or
sentence
but
closer
to
the
actual
character
limit
that
you
want
by
doing
the
actual
word
and
there's
a
separate
issue,
which
is
trimming
like
counting
the
number
of
trimming
characters
without
the
html.
G
That's
in
one
of
the
drupal
modules
that
they
pulled
from
cake
php,
and
that
does
this
whole
big
function.
That
does
all
the
trimming
and
the
counting
lots
of
stuff,
and
that
seems
to
be
the
most
robust
option
that
I've
seen.
But
it
does
everything
in
one
go
and
I
don't
know
how
to
sort
of
like
cut
it
down
to
make
it
do
just
one
thing
for
one
issue
and
one
thing
for
another
issue.
I
think
it's
best
to
just
combine
both
issues
put
that
function
in
there
and
then
just
do
everything
at
once.
B
Okay,
the
thing
about
any
robust,
complicated
functionality.
If
we
don't,
if
we
don't
trim
it
down
and
it
uses
more
capabilities
than
we
actually
use,
then
we
probably
need
to
have
test
coverage
for
the
functionality
that
doesn't
have
displays
in
it,
because
if
we
don't
have
any
test
coverage
and
there's
some
hidden
functionality
in
core
and
some
module
starts
using
it.
B
So
I
don't
I'm
not
immediately
opposed
to
the
like.
Let's
just
put
this
giant
thing
in
from
cake
php,
but
let's
just
make
sure
that
if
we
do
put
it
in
that
we
have
adequate
coverage.
B
B
Okay,
let's
see
okay
and
the
last
one
we
have
that
got
bumped
from
121
is
the
hidden
path,
content
type
issue:
4903
olaf
and
tim
seem
to
be
the
people
best
connected
on
this
issue
and
either
of
them
are
here
today,
although
it
does
look
like
they've,
olaf
posted
something
as
recently
as
this
week,
it
does
kind
of
look
like.
B
I
think
that
we're
trying
to
move
towards
using
the
approach
that
is
already
completed,
that
there's
already
a
pull
request
that
is
out
there.
That
is
pretty
good,
although
there's
a
lot
of
hope
that
maybe
we
could
do
it
better,
but
that
would
involve
more
work
either
using
a
flexible
layout
or
creating
a
new
layout
specifically
for
the
home
page
new
custom
layout,
specifically
for
the
home
page,
and
I
think
that
our
general
approach
is.
B
We
already
have
enough
something
that's
working
right
now
that
makes
a
new
home
page
as
well
as
this
new
content
type.
We
can
proceed
with
that
and
then
try
to
iterate
on
it.
It
does
only
affect
new
installations
of
backdrop,
so
we
have.
The
opportunity
to
you
know
do
as
best
as
we
can
for
new
one
cells
now
and
then
improve
upon
it
later
to
again
make
them
them
better
yet
and
since
it
doesn't
impact
any
existing
sites,
we
have
a
lot
of
flexibility.
There.
B
Okay,
all
right,
well
that
those
are
all
of
the
issues
that
we
have
that
were
bumped
from
121.
I
think
we've
got
a
good
chance
of
getting
all
of
them
completed
that
php
5.6.
We
can
get
done
really
pretty
quickly.
B
I
think
I'd
like
to
open
the
floor
a
little
bit
here
and
just
see
if
anybody
has
informal
suggestions
for
122
features,
we're
kind
of
going
to
try
to
get
a
better
formalized
system
by
soliciting
like
suggestions
on
twitter
and
collecting
ideas
from
zulip
and
the
forum
and
assembling
all
those
together
and
then
voting
on
them,
but
I
don't
think
it
would
hurt
to
go
ahead
and
start
like
brainstorming.
Some
ideas
now
to
just
start
like
puts
them
on
the
table.
B
D
There
was
some
recent
discussion
about
how
inconvenient
it
is
for
layouts
that
have
sidebars
when
there's
no
content
in
the
sidebar,
and
these
are
sort
of
like
kept
there
like
as
a
blank
space,
and
my
last
comment
at
all
I
didn't
follow
up
on
that
issue
was
that
at
some
point,
when
we
decided
to
put
radix
into
core
what
we
did
is
we
moved
the
existing
things
into
a
legacy
folder
and
we
added
hidden.
Is
it
equals
true
to
them?
So
we
didn't
break
existing
sites.
D
So
the
decision
to
to
have
this
behavior,
where,
where
empty
regions
are
retaining
the
space
that
they
would,
they
would
normally
take
up
if
they
were
blocks
in
them,
was
back
in
2015
2016
and
most
people
seem
to
agree
that
it's
not
appropriate
anymore
or
yeah.
That's.
A
That's
the
other
way
around.
Actually,
the
expanding
collapse
in
columns
was
something
that
was
popular
in
drupal.
So
it's
a
really
old
pattern
and
we
adopted
a
modern
one
by
keeping
this
space.
That's
like
a
usability
improvement,
because
you
can't
have
your
text
read
more
than
like
80
characters
in
line
or
people
can't
read
it,
but
I
think
that
what
we're
seeing
now
is
all
of
these
people
who
are
coming
from
drupal,
who
are
accustomed
to
the
old
design
patterns
that
aren't
up
to
modern
standards
want
those
back.
A
And
so
I
think
what
we
need
to
do
is
add
a
set
of
old
style
design
patterns
that
people
from
drupal
can
have
that
functionality.
So
like
a
contrib
layout
that
makes
all
of
backdrops
cores
like
behave
like
drupal
7s,
and
then
that
way,
anyone
who
had
that
functionality
in
drupal
would
be
able
to
get
the
same
functionality
when
they
move
to
backdrop
without
like
breaking
their
theme
or
their
current
patterns.
A
A
It
I
think
it
could
be
if
we
created
a
new
like
in
a
new
layout,
template
or
layout
project.
A
As
long
as
we
accounted
for
it
in
the
markup,
we
could
do
that,
but
I
don't
think
we
can
change
existing
core
markup
to
account
for
that,
like
the
way
that
the
the
there's
no
variables
in
there
now,
and
so
if
we
had
to
like
rewrite
the
templates
to
put
in
variables
for
that
it
would
be
hard,
but
I
think
in
in
new
templates
we
could
we
could
do
something
smarter
with
class
handling.
That
would
allow
that
to
happen
exactly
yeah.
It.
H
B
When
it's
rendered
on
the
admin
side,
it
could
ignore
the
setting
and
because
they
also
have
settings
already
like
regions,
have
settings
in
the
flexible
layout
builder,
like
the
classes
and
things
like
that,
it
could
be
an
option
in
there
and
then,
when
it's
rendered
on
the
front
end,
it
could
respect
the
setting
and
show
or
hide
any
columns
that
are
empty.
But
during
the
admin
interface,
of
course,
it
would
need
to
show
the
empty
rows
so
that
they're
the
empty
empty.
C
B
So
I
wonder
if
that
might
serve
the
need.
B
A
B
A
So
that's
a
good,
a
good
point,
nate
that
all
of
the
flexible
layouts
already
are
built
with
variables.
So
that's
a
good
solution,
but
another
thought
greg.
This
is
just
that
remind
me.
Is
you
had
a
suggestion
before
that
had
a
button
on
a
core
layout
that
was
like
convert
this
to
flexible?
That
would
also
solve
that
problem.
A
D
Of
course,
I
think
that
I
have
two
issues,
which
is
basically
two
entry
points
to
the
same
thing.
So
it's
one
to
have
a
button
in
its
layout
that
says,
make
this
a
flexible
one
or
which
basically
doesn't
make
it
one.
It
creates
one
off
of
that.
It
still
keeps
it
and
then
the
other
one
is
when
you,
when
you
click
the
add
flexible
layout
button.
The
first
page
that
you
see
gives
you
an
option.
D
Would
you
like
to
use
one
of
the
existing
layouts
as
a
template,
and
then
it
generates
one
of
those?
So
it
would
be
the
same
feature
basically
but
two
different
edging
points.
B
Yeah,
fortunately,
we
got
most
of
those
terminology,
things
sorted
out
finally
yeah,
but
now
we're
to
choose
another
one:
oh
no,
okay,
yeah
yeah,
so
there's
a
layout
configuration
and
a
layout
template
and
we
try
to
use
those
words
and
then
there's
also,
I
mean
there's
also
a
layout
instance
yeah
and.
H
A
B
E
D
If
only
we
knew
all
these
things
when
we
started
naming
things
like
where
it
was
yeah,
and
we
also
have
the
something
that
cannot
be
changed
easily.
The
fact
that
a
project
type
is
layout
when
it
shouldn't
be
like
the
machine
name
is
layout
and
it
should
be
layout
template
as
in
we
say,
type
equals
layout.
It's
not.
A
B
Yep:
okay!
Well,
thanks
greg.
A
But
that
also
exciting
things
for
1
22,
though
that
convert
this
layout
to
be
flexible,
could
be
a
fun
feature.
Just
that's.
G
I
yes,
a
less
fun
possible
feature
for
the
next
version.
I
just
made
a
pull
request
the
other
day
for
issue
4013,
which
is
about
being
able
to
fully
delete
text
formats.
Apparently
we
can
only
disable
them
and
now
we
can
re-enable
them,
but
this
is
a
follow-up
to
be
able
to
fully
delete
them
now.
So
there's
a
poor
request
that
is
avoiding
review
and.
B
Testing
cool
yeah
looking
forward
to
that,
as
you
know,
there's
lots
of
concerns
around
deleting
text
formats,
but
done
correctly
done
carefully,
it
should
be
possible.
Do
we.
A
B
B
B
We
couldn't
still
have
the
ability
and
come
up
with
a
fallback
behavior
of
some
kind.
It's
a
little
bit
less
dangerous
than
it
used
to
be.
I
think
the
primary
concern
previously
was,
if
you
use
the
php
text
format,
and
then
you
fell
back
to
plain
text.
You
could
reveal
sensitive
php
code
to
the
front
end,
but
nobody
is
doing
php
code
they're
in
their
text
formats
anymore.
G
Yeah
and
in
the
quick
testing
that
I
did,
it
seemed
like
before
I
worked
on
this
full
request.
I
tested
the
current
functionality
in
backdrop
now,
which
is
where
you
can
delete
a
text
format,
so
I
had
a
text.
Format
enabled
use
some
content
disabled
it
and
then
I
went
back
to
edit
it
and,
after
a
refresh
of
that
page
of
the
case
refresh,
it
would
come
up
saying
like
there
was
no
text
format
selected
and
you
had
to
sort
of
select
one.
G
So
we
have
this
ability
and
call
already
that
handles
disabling
a
text,
format,
meaning
it's.
It's
not
got
a
text
format.
You
have
to
save
one
with
a
new
one
or
whatever.
So
to
me,
deleting
one
is
systematic,
deleting
the
config
file
and
then
using
the
existing
functionality
to
select
a
new
one.
If
you
try
to
edit
all
that
content.
A
B
Yeah
that'd
be
that'd,
be
interesting.
My
impression
of
what
should
happen
is
that
if
it's
disabled
but
in
use
somewhere,
it
actually
still
works
on
view,
but
I
might
be
wrong
about
that
and
if
they're
already
hiding
it,
then
there's
it's
no
worse
deleting
it.
G
G
D
B
Well
anyway,
yeah
sounds
great
peter.
It's
issue,
40
13.
B
A
D
I
have
a
question
this
has
come
up
recently.
I
can't
remember
if
it
was
an
initial
queue
forum
or
zulip,
but
it's
my
understanding
that
that
the
layouts
in
backdrop
were
built
based
upon
a
an
early
version
of
bootstrap.
Four
and
people
now
seem
to
be
keen
on
using
booster
five
and
I'm
not
like.
D
I
only
recently
started
working
on
themes
and
trying
to
port
things,
but
is
there
any
way
that
we
can
without
breaking
existing
sites,
with
like
backwards,
compatible
way
of
of
upgrading
to
bootstrap
5
and
still
keeping
butcher
for
compatibility.
A
Differences
are
yeah.
I
would
imagine
that
just
swapping
out
a
library
for
another
version
would
cause
a
bunch
of
problems,
because
it
expects
the
markup
to
be
a
specific
way
and
all
of
our
core
markup
assumes
bootstrap
four.
But
there
could
be
a
way
that
we
add
a
backwards
compatibility
layer
in
there
so
that
all
of
the
four
stuff
is
still
supported.
But
I
don't
know
how
complicated
that
would
be.
B
D
D
And
I
have
I
have
talking
about
teams,
I'm
not
sure
I
will
be
able
to
work
on
that
because
I
don't
know
what's
involved,
but
there's
there's
a
long-standing
issue
about
treating
themes
as
modules
and
allow
them
to
be
installed
and
uninstalled
properly
and
include
install
files.
So
update
hooks
and
things
like
that.
B
Okay,
so
I
was
doing
doing
a
look
up
on
things.
I'm
I'm
curious
if
bootstrap
is
a
dependency
of
our
layouts
or
if
it's
added
someplace
else,
because
if
depend
if
bootstrap
is
a
dependency
of
the
layouts
in
theory,
that
would
mean
that
certain
layouts
are
tied
to
certain
grid
systems,
and
that
would
make
it
so
that
we
could.
It
would
be
tedious,
but
we
could
make
a
bootstrap
five
version
of
all
of
our
layouts
and
then
do
the
same
thing
again,
where
we.
B
From
four
to
five
in
this
case,
because
it
would
be
a
really
apples
to
apples
transition,
it's
possible
that
we
could
provide
some
kind
of
tool
to
say
like
convert
all
of
my
thanks
from
four
to
five
and
just
like
flip
them
and
then
hide
all
of
the
old
layouts,
again
deprecate
them,
and
then
they
would
go
away
and
backtrack
too.
D
Yeah
and
and
the
other
thing
I
was
saying-
I
I
recently
started
trying
to
to
port
themes,
and
I
come
there's
a
need,
sometimes
to
just
as
part
of
the
theme
move
blocks
around,
so
the
default
blocks
in
the
admin
layout
and
it
could
in
theory,
be
done
easily
if
there
was
an
install
called
an
update
hook,
that
that
could
run
with
the
things.
But
it's
not
possible
as
it
is,
and
my
only
workaround
was
like.
A
Like
you
couldn't
have
an
update
hook
and
a
theme
that
wouldn't
use
any
region
name
because
the
regions
are
dependent
on
which
layouts
you're
using
and
so
there's
no
correlation
there
in
drupal,
it
was
really
common
that
you'd
have
to
move
blocks
around,
but
in
backdrop
you
wouldn't
want
to
do
that
in
your
theme.
That
update
hook
would
need
to
be
in
like
a
custom
module.
Something
was
very
specific
to
that
site.
It
couldn't
match
a
theme
yeah.
D
A
A
D
Yeah,
the
other
thing
would
be
to
just
have
a
note
and
or
instructions
and
read
me
on
how
to
achieve
that
like,
as
in
you
need
to
move
the
breadcrumb
thing
there
in
another
region
or
whatever
yep.
B
Okay,
we're
almost
out
of
time
here,
but
so
there's
one
more
issue
that
I
want
to
raise.
Just
as
a
maybe
this
time
issue
issue
1301,
which
is
add
a
reference.
Add
reference
module
to
core.
This
has
been
changing
directions
a
lot
most
recently.
B
The
issue
or
the
the
direction
has
changed
that
we're
looking
at
pursuing
entity
reference,
putting
nd
reference
in
core.
After
all,
our
primary
concerns
in
the
past
have
been
that
entity.
Reference
was
a
little
bit
of
a
mess.
It
depended
on
nd
plus
module
which
we're
not
ready
to
just
put
that
wholesale
into
core
herbduel
has
been
taking
those
complaints
and
putting
some
action
behind
it,
and
he
has
already
removed
the
dependency.
B
My
understanding
is
removed
the
dependency
on
entity
plus
so
that
now,
in
the
reference
module,
the
contrib
version
works
without
it.
So
it
does
not
have
any
external
dependencies
anymore
and
he's
working
on
cleaning
up
the
code
base
to
make
it
so
that
it's
less
of
a
of
a
mess,
and
so
those
are
the
primary
concerns
that
we
had
about
using
entity
reference.
The
contrib
module
and
herbal
has
been
working
to
mitigate
those
problems.
B
So
if
those
problems
have
been
resolved,
then
that
makes
it
a
lot
better
candidate,
there's
other
good
arguments
for
using
entity
reference
like
it's
the
most
flexible
solution.
It's
already
the
most
widely
used
solution,
I
think
both
for
backdrop
and
for
and
for
drupal
7.,
and
it
also
has
a
pretty
good
suite
of
modules
that
depend
on
it.
And
if
we
were
to
leverage
it
directly,
we
could
use
our
standard
approach
to
like
merging
a
module
into
core
and
just
saying
hey,
this
contrib
module
by
the
same
name.
B
So
that
also
changes
our
approach
to
what
needs
to
be
done
here
that
primarily
where
we
need
to
be
focusing.
Our
efforts
is
in
the
contrib
module
space
working
on
entity,
reference
module
directly,
any
other
problems
that
we
have
with
md
reference
or
any
other
preparation
that
we
need
to
do.
We
should
be
doing
that
in
the
contrib
queue.
B
I'm
not
totally
sure
that
we
are
100
like
this.
Is
the
direction
we're
going
now.
It's
just
that
herb
has
removed
all
of
the
big
complaints
about
entity
reference
that
that
now
makes
it
a
much
stronger
contender
than
it
was
previously.
So
we
need
to
start
and
reconsider
our
options
again
and
decide
which
one
is
is
the
best
way
forward.
B
It
is
kind
of
the
case
that
entity
reference
has
some
advantages,
that
other
modules
will
not
be
able
to
meet
like
being
the
most
popular
and
having
the
most
dependencies
because,
like
us,
working
on
the
other
modules
doesn't
really
get
over
that
barrier
and
entity
reference
already
starts
with
it.
B
So
in
a
way
this
is
now
like
the
path
of
least
resistance
has
probably
changed
here,
and
so
we
need
to
go
back
and
look
at
the
options
again,
which
is
great.
This
is
a
good
problem
to
have
that
something
that
had
been
eliminated.
It's
not
actually
so
and
again,
big
shout
out
and
appreciation
herb
dual
for
taking
that
on
and
and
taking
this
very
seriously
the
the
feedback
that
we
have
and
then
addressing
it.
So
really
great,
oh,
go
ahead!
Peter.
G
What's
going
to
happen
if
entity
reference
ends
up
making
into
call
like
the
one
we
choose
to
put
into
call
what
happens
with,
I
think
was
reference
whatever
the
one
that
we
were
building
for
backdrop
specifically,
what
happens
to
that
like,
I
imagine
we're
not
going
to
make
it
a
contrib
module,
because
I
mean
there's
a
point.
So
is
that
code
just
then
gone
or.
A
I
would
like
to
work
on
an
upgrade
path
from
reference
to
entity
reference,
and
then
we
can
mark
the
kindred
module
as
deprecated
and
recommend
people
switch
to
entity
reference.
B
Yeah
but
it
will
still
exist
in
contrib,
just
like
references
module,
the
one
that
contains
node
reference
and
user
reference.
It'll
continue
to
just
kind
of
hang
out
and
contrib,
probably
for
a
long
time
to
come.
A
B
Yeah,
the
the
really
tricky
thing
with
those
reference
modules
is
that,
because
they're
structural,
their
configuration
ends
up
in
things
like
views
and
in
layouts
and
all
over
the
place.
It's
it's
not
just
a
problem
of
the
data
being
changed
from
the
database
schema
and
updating
content,
which
is
already
a
challenge
enough,
then
updating
the
field
configuration
which
that's
fairly
straightforward,
but
then
all
of
the
places
those
things
are
used
is
really
where
just
it
just
gets
really
challenging.
B
Yeah.
Okay!
Well
we're
at
the
top
of
the
hour.
We
got
a
little
bit
of
a
late
start
today,
but
I
think
we
we
need
to
wrap
up.
Does
anyone
have
any
things
that
they
would
like
to
add
before
we
close.
D
Just
pointing
out
that
dr
martin
zulu
is
asking
for
attention
on
54
82,
I
I
mentioned
that
the
relationship,
the
layout
relationship
thing
and
he
needs
feedback
on
whether
the
the
fix
is
reasonable.
The
the
fix
that
he
he's
proposing.
B
B
Okay,
that's
it
for
today,
then,
thank
you
all
for
for
joining
the
meeting,
hoping
that
we'll
continue
to
talk
about
122
for
the
next
couple
of
weeks,
and
it
does
look
like
with
indigozales
helpful.
We
might
be
able
to
get
that
5.61
knocked
out
right
away,
so
that
would
be
great
well.
Thank
you
all.
I
hope
you
all
have
a
great
week.