►
From YouTube: 2022/01/20 - 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
out
there,
it's
january
20th,
2022
a
fun
date,
and
this
is
the
weekly
backdrop
developer
meeting.
We
get
together
every
week
to
talk
about
priorities
and
objectives
for
backdrop
core
and
beyond.
A
B
So
before
we
get
into
the
agenda,
we
should
probably
go
and
do
some
introductions.
Oh
wait,
nate's
back.
C
A
Meeting
notification
popped
up
and
I
tried
to
dismiss
it
and
I
left
so:
hi
yeah,
okay
introductions,
I'm
nate
lampton
from
oakland,
california,
I'm
quick
sketch
on
the
internet
and
a
core
committer,
let's
go
to
jen
and
then
to
robert.
C
I'm
robert
line
bug
folder
on
the
internet,
coming
to
you
from
el
sadina
california,
working
lately
on
contributions.
A
Okay
thanks
robert
greg
and
then
joseph.
D
Hi,
I'm
greg
I'm
joining
from
greece
interested
to
help
with
anything
related
to
backdrop.
Yeah.
A
Thanks
greg
joseph
and
then
justin.
E
A
Yeah
we'll
talk
about
that
later
on
in
the
meeting
thanks
joseph
justin
and
then
olaf.
A
All
right
thanks
joseph
or
justin
olaf
and
then
wilbur.
A
Thanks
wilbur,
can
you
give
us
a
quick
intro
and
then.
G
My
name
is:
will
burns
I'm
in
minneapolis
minnesota
and
I
host
backdrop
office
hours,
which
happens
19
to
2100
utc
time,
which
is
in
your
time
zone
as
well
somewhere.
So
come.
A
A
Thanks
wilbur
finally,
tim.
H
My
name
is
tim
erickson,
I'm
st
paul
tim,
I'm
in
deerwood
minnesota
and
I
enjoy
going
to
office
hours
with
wilbur
and
I'm
excited
to
start
ramping
up
and
getting
ready
for
backdrop
live
which
will
be
on
march
11th
and
by
the
way
wilbur
you
mentioned
the
times,
but
not
the
date
for
office
hours.
It's
wednesdays,
wednesdays.
At
the
time
wilbur
mentioned.
A
All
right
thanks
everybody
before
we
go
into
things
into
the
main
part
of
the
meeting,
we
usually
do
contrib
update
jen.
Can
you
give
us
an
update
on
contrib
world.
B
C
B
B
So
just
in
time
for
australia
day,
everybody
should
install
the
aussie
slang
module
and
get
a
little
fun
out
of
their
websites.
C
A
All
right
yeah
big
news
this
past
week,
so
this
is
the
first
meeting
since
our
121
release,
so
yeah
jen
our
backdrop,
121
came
out
january,
15th,
2022
very
exciting.
Also,
our
seventh
birthday,
I
believe,
tammy,
did
an
excellent
job
with
twitter.
A
I
was
very
surprised
to
see
you
took
all
of
the
suggestions
for
what
we
could
do
for
birthday
and
did
all
of
them,
which
made
made
quite
a
lot
of
fun
noise
on
on
twitter,
and
that
was
that
was
really
excellent,
so
happy
seventh
birthday
to
backdrop
and
happy
22nd
release.
If
you
count
21,
I
think
that
that's
right
yeah
well
happy
release.
Nonetheless,
it
was
a
good
release,
lots
of
new
features
that
got
in
there.
A
We
didn't
bump
very
many
things,
but
we
did
didn't
quite
get
to
absolutely
everything,
also
kind
of
exciting
or
or
very
helpful.
We
some
of
the
the
people
on
the
security
team
were
aware
of
this
before
121
was
released,
but
we
knew
that
there
was
going
to
be
a
related
security
release
to
jquery
ui
promptly
after
the
release
of
121
and
so
indogozella's
work
to
bump
121
up
to
the
latest
version
of
jquery
was
very
advantageous
for
us
to
coincide
that
with
a
minor
release,
some
people
may
have
noticed
yesterday.
A
There
was
a
security
release
for
drupal
that
was
related
to
jquery
ui,
and
we
didn't
have
to
apply
that
same
update
because
we
included
it
in
121.
and
sorry.
I
told
jen
that
she
was
going
to
talk
about
that
and
I
just
ran
right
into
it.
So
jen
is
there
more
details
that
you
would
like
to
say
about
that
particular.
B
Updating
to
the
latest
version
of
the
library
meant
that
we
didn't
run
into
the
same
problems
with
the
regression.
There
were
also
three
additional
issues:
security
issues
that
affected
drupal
7
did
not
affect
backdrop,
because
they
were
problems
with
jquery
110
and
for
the
entire
lifetime
of
jquery.
We've
only
had
111
and
later
so.
Those
issues
also
not
apply
to
backdrop.
So
it's
only
the
most
recent
ones
for
issues
with
112
that
were
now
fixed
by
us.
Moving
to
113.
A
Yeah
hooray
preventative
measures
for
the
win,
that's
fantastic,
so
we
did
release
a
public
security
announcement.
I
think
that's
what
it
was
psa
yesterday,
just
saying
that
no,
there
is
no
security
for
backdrop
and,
yes,
that
is
intentional,
so
great
to
get
ahead
of
things
all
right,
so
121,
not
all
sunshine
and
roses,
though
we
had,
we
have
a
couple
of
issues
that
are
causing
trouble,
one
of
which
is
issue
5460.
A
Well,
we
put
in
some
optimizations
into
the
way
menu
links
are
saved
in
121,
and,
although
that
that
change
had
been
in
the
one.x
branch
for
several
weeks,
we
didn't
catch
the
issue
that
a
lot
of
people
ran
into
pretty
quickly
after
updating
and
that
it
surfaces
in
your
site,
creating
lots
of
duplicate
links
in
particular
user
slash
login
seems
to
get
duplicated
frequently,
as
does
well.
I
guess
that's
the
only
one
that
seems
to
happen
frequently
because
out
of
the
box,
it's
the
only
menu
link
that
exists
in
two
places.
A
If
you
have
one
menu
link
in
two
places,
then
it
starts
making
lots
and
lots
of
that
particular
menu
link.
I
haven't
actually
seen
that
this
I
haven't.
I
haven't
experienced
this
behavior
myself
because
I'm
going
to
elaborate,
if
that
actually
shows
itself
in
the
front
end
interface
as
well
like
do
you
literally
see
your
menu
tree
flooded
with
user
login
links.
E
So
what
essentially,
what
happens
is
when,
in
hook
menu
when
you
create
a
menu
entry
with
a
certain
certain
like
type
certain
many
many
router
types
will
cause
it
to
automatically
create
menu
links?
E
And
so,
if
you
have
something
like
that,
which
user
login
is
one
of
those
so
that
it
automatically
gets
put
into
certain
menus,
then
you
create
a
customized
menu
link
with
the
same
router
path
afterwards,
that
one
will
overwrite
the
original
one
created
by
the
system
module,
and
so
every
time
caches
are
cleared,
it
will
try
to
create
a
new
system
version
of
that
link
every
single
time,
and
it's
essentially
because
I'm
using
the
the
link
path
as
the
array
key
in
our
cache
array,
and
so
anytime,
you
have
two
two
or
more
items
with
the
same
link
path.
A
Okay,
so
what
we're?
What
we're
planning
on
doing
to
solve
this
problem?
First
of
all,
is
that
we're
going
to
revert
the
optimization
that
we
put
into
121
that
will
stop
the
menu
links
from
being
created,
but
we
need
to
do
more
than
that.
We
need
to
actually
clean
up
the
mess
that
we've
made
on
anybody's
sites
that
have
made
duplicate
links.
B
A
Indigozales
started
on
a
pull
request
that
does
the
revert
and
fixes
the
user
login
link,
specifically
because
that's
the
situation
that
we've
seen
do
you
think
it's
possible
joseph
for
us
to
write
a
better
update
hook
that
cleans
up
all
of
the
menu
links
that
might
be
duplicated
or
I'm
kind
of
wondering
which
way
we
should
take
this.
A
E
H
D
A
Yeah
couldn't
this
also
then
occur
joseph
if
you're
saying
if
something
adds
something
through
hook
menu,
and
you
also
have
a
manual
link.
This
could
also
happen
with
things
like
a
view
or
even
a
layout.
I
think
where
those
those
things
are
creating
menu
entries
it
through
hook
menu
and
then,
if
you
also
put
a
custom
menu
link,
then
you
could
get
duplicates
that
way
too
yeah
so
view
views
and
layouts
would
be
very
common
things
to
have
menu
system,
driven
tabs
and
menu
entries,
and
things
like
that.
Well,
it's
very
useful.
A
Knowing
that
we
can.
I
think
that
we
can
now
reproduce
it
with
that
level
of
information,
but
that
also
sounds
like
yeah.
We
need
to
have
a
comprehensive
fix
and
I
don't
want
to
have
two
releases.
I
don't
have
121.1
that
reverts
it
and
then
121.2
that
fixes
the
the
mess
so
yeah
fixing
this
as
soon
as
possible.
A
B
A
Looking
at
this
right
now
as
soon
as
we
get
something,
that's
ready,
we'll
make
the
new
release
whenever
that
is,
is.
H
H
E
I'm
not
100
sure
I
so
we
have.
We
have
like
a
plan
for
how
to
fix
this,
but
I
don't
know
at
this
time
how
long
that's
going
to
take
to
actually
implement.
A
So
yeah,
let's,
let's
let's
put
a
let's
put
a
deadline
on
it,
then,
and
if
we
don't
get
it
done
very
quickly,
then
we'll
publish
it
and
let's,
let's
be
aggressive
with
that
and
say:
if
we
don't
get
it
fixed
before
the
end
of
tomorrow.
If
it's
not
fixed
on
saturday,
then
then
post
post,
the
warning
so
that
that
puts
our
objective
of
fixing
this
on
today
or
tomorrow,
and
then
also
making
the
release
yeah.
Robert
sorry
did.
D
I've
recently
seen,
I
think,
lando
or
I
can't
remember,
which
releases
I
was
monitoring,
which
they
did
actually,
that
they
discovered
that
there
was
a
bug
and
then
what
they
did
is
they
removed
the
assets
from
the
github
release,
and
maybe
we
can
unpublish
the
node.
So
if
we
know
that
it
is
problematic,
maybe
we
should
prevent
people
from
installing
it.
Once
we
have
an
alternative
version
out.
A
Yeah
I
mean
we
could
unpublish
the
node
on
backdropcms.org
that
would
stop
update
module
from
notifying
people.
It
would
have
the
effect
of
making
the
other
release
that
we
made.
The
bug
fix,
release
have
that
be
the
notification
that
they
get
saying.
You
should
update
to
120.4.
A
It
does
not
yeah
yeah,
so
yeah,
it's
clearly
best.
If
we
get
this
solved
as
quickly
as
possible
yeah.
I
I.
B
A
F
A
So,
thank
you,
rg
for
our
alejandro
for
your
feedback.
Yeah
there's,
there's
a
lot
of
truth
to
that
and
we
do
have
an
update
hook
right
now.
That
fixes
the
kind
of
like
the
most
common
situation
of
user,
slash,
login
and
it's
also
pretty
safe,
but
I'm
a
little
bit
worried
that
121.2
might
not
come
out
for
with
the
same
urgency
and
wait.
It
might
be
a
couple
of
weeks
before
we
make
a
second
release.
I.
B
H
What,
if
there's
broken
sites
out
there
right
now
that
they
don't
people,
don't
know
how
to
fix
them?
Yeah,
like
I,
the
sky
on,
I
forget
his
name,
but
the
guy
in
the
forum
who
originally
reported
this,
I
think,
he's
still
working
on
a
dev
site.
So
I
I
I
think
his
live
site
is
still
clean.
I'm
not
sure
about
that,
but
I'm
just
worried
about.
There's
somebody
like
him.
A
Well,
these
are
our
options.
Maybe
maybe
we
should
proceed
with
the
plan.
That's
like
we
should
try
to
fix
this
before
tomorrow
and
if
we
don't
have
it
fixed
before
tomorrow
we
go
with
the
pull
request
we
currently
have
and
we
do
a
release
either
way.
So
121.1
comes
out
tomorrow,
no
matter
what
and
it's
just
a
matter
of
whether
or
not
we
have
a
great
fix
or
an
like
a
most,
mostly
fix,
but
we
can
stop
the
proliferation
of
duplicate
links
immediately.
A
Okay,
and
then
we
don't
need
to
prepare
the
notification,
because
we
know
121.1
is
going
to
come
out,
we
might
want.
Well,
I
don't
know
we
might
want
to
prepare
a
121.1
post
of
like
what
it
fixes.
You
know,
and
let
people
know
that
that's
available
rather
than
people
needing
to
find
the
bug
report
and
then
finding
the
issue
that
way,
because
it's
possible
that
people
may
have
upgraded
to
120
one
and
not
noticed
that
they've
got
duplicate
links,
and
so
it
might
be
good
to
be
proactive
and
tell
people.
A
Okay,
that's
a
plan.
A
Okay,
all
right
next
issue
that
we've
got
here
also
a
121
problem
that
has
a
written
arisen,
something
that
we
kind
of
foresaw
that
there
might
be
some
problems
with,
but
we
thought
that
we
mitigated
it
fully
but
didn't
quite
get
at
all
and
that's
we
introduced
some
new
methods
into
the
entity
classes.
A
They
now
have
view
and
build
content
methods,
and
when
we
were
testing
this
pull
request,
we
did
a
lot
of
prep
work,
checking
for
entity
plus
to
make
sure
that
it
wasn't
going
to
be
negatively
affected
as
well
as
some
other
modules.
I
think
robert
you
mentioned
ubercart
and.
C
A
Rules,
so
all
all
three
of
those
modules
have
had
fixes
or
tests
applied
against
them
or
new
releases
to
make
it
so
that
they
all
work
with
121
and
they
all
came
out
before
121
was
released,
but
we
missed
one
at
least
so
far
in
registration
module
that
it
also
created
a
custom
entity
had
a
view
method
on
that
custom
entity
and
that
view
method
wasn't
compatible
with
the
definition
set
forth
by
backdrop
121..
A
So
registration
module
has
seen
a
pull
request
applied
to
it.
I
think
joseph
was
the
one
that
did
the
work
there,
I'm
not
sure
if
there's
a
new
release
of
registration
yet,
but
this
is
kind
of
it-
was
a
little
bit
of
an
iffy
thing.
We
saw
that
there
was
going
to
be
some
potential
problems
with
contrib.
A
By
adding
these
new
methods,
we
tried
to
mitigate
it
as
best
we
could,
and
it
turns
out
there
wasn't
quite
enough,
and
it
also
brings
up
the
concern
that
there
could
have
been
like
custom
code
out
there,
that
we
weren't
seeing
that
could
have
also
been
affected
in
this
case.
Well,
joseph
yeah,
why
don't
you
if
you
have
anything
to
say
why
don't
you
go
ahead.
E
A
Yeah,
so
so
we
we
have
the
contrib
problems.
As
far
as
we
know
of
in
hand
this
situation,
we
don't
really
have
a
way
to
do
any
further
mitigation.
I
don't
think
at
least
as
far
as
contrib
or
sorry
custom
code
is
concerned.
A
A
I'm
not
quite
sure
what
this
really
means,
as
far
as
like
adding
methods
to
classes
is
kind
of
a
common
thing
that
we
need
to
be
able
to
do,
and
I'm
not
quite
sure
what
to
do
about
classes
that
extend
our
current
classes
and
add
their
own
methods
with
common
names
that
could
potentially
conflict
with
other
the
parent
classes,
new
methods
that
we
had
in
the
future
yeah
just
a
little
struggling
a
little
bit
to
find
a
good
way
to
manage
that.
I
A
So
anyway,
I
think
all
that
we're
doing
with
this
is
bringing
it
to
people's
attention
that
it's
a
potential
concern,
and
I
think
that
you
know
we
don't
really
have
much
to
do
to
resolve
that
problem.
A
E
A
Yeah,
oh
that's
kind
of
an
interesting
point
there
that
if
you're
running
an
older
version
of
php,
it
actually
doesn't
cause
problems
right,
yeah,
yeah,
well,
yeah,
we're
not
living
in
that
world
anymore,
though
so.
But
let's
move
on
to
the
next
topic,
because
it's
highly
relevant
and
that
is
dropping
support
for
old
versions
of
php.
A
A
I
don't
know
where
that
issue
went
in
my
browser,
but
we
discussed
and
made
that
decision
during
the
121
release
cycle
and
we
decided
we're
going
to
bump
it
to
122
and
we're
going
to
merge
in
that
change
as
soon
as
possible,
so
that
issue
to
bump
the
minimum
php
version
to
5.6.
It
already
has
a
pull
request.
A
A
So
so
that's
coming
down
the
pipe.
There
is
a
notice
in
backup
121,
however,
that
if
you're
running
an
old
version,
it
throws
an
error
on
the
status
report
telling
you
that
your
version
of
php
is
completely
unsupported
and
backdrop
will
not
support
it.
Moving
forward,
starting.
A
Okay,
so
that's
one
of
the
things
that
we
can
move
forward,
121
and
higher.
I'm
sorry,
starting
with
122.
other
122
issues
that
got
bumped
from
121
include
the
hidden
path
content
type,
which
I
think
we're
also
planning
on
moving
forward
as
soon
as
possible.
But
I
think
that
we
got
stuck
on
some
more.
A
H
All
right
suppose,
although
feel
free
to
help
me
out
where
this
issue
got
stalled,
was
that
we
are
currently
well
quickly.
The
the
main
focus
of
the
issue
is
to
add
a
hidden
path,
content
type,
and
we
wanted
to
display
that
in
the
default
the
install
profile,
so
we,
the
original
poll,
request,
had
a
view
on
the
front
page
that
showed
three
hidden
path:
nodes
that
had
information
about
a
backdrop.
H
Some
people
suggested
that
a
view
isn't
really.
I
mean
part
of
our
reason
for
doing
all
of
this
is
to
educate
people
and
to
give
them
an
example
of
how
to
use
this,
and
some
people
pointed
out
that
a
much
more
logical
way
of
doing
this
would
be
with
a
layout,
not
a
view,
and
I
think
there
was
a
lot
of
sympathy
that
that
was
true,
that
it
would
a
layout
is
a
better
route
to
go.
H
So
we
said,
let's,
let's
hold
off
and
work
on
that,
but
as
soon
as
we
started
to
think
about
that,
we
realized
that
that
introduces
some
new
problems
that
we
can't
use.
We
can't
do
it
exclusively
with
a
layout
in
existing
path
nodes
using
the
existing
front
page
layout,
unless
we
basically
because
we
have
just
horizontal
rows
like
if
you're
going
to
use
a
layout
to
place
three
side-by-side
blocks.
H
Ideally,
I
would
create
a
flexible
layout
and
I
would
create
a
row
with
three
regions
in
it
and
I
would
put
a
block
in
each
one.
We
could
use
css
to
to
put
three
existing
content
blocks
next
to
each
other,
but
in
my
view
that
isn't
really
much
better
than
doing
a
view.
H
So
we
have
that
option.
We
have
the
exists
or
create.
We
could
replace
the
front
page
layout
with
a
flexible
layout
in
core.
What
are
our
other
options?
All
of
is:
are
there
any
existing
layouts
in
core
that
would
work
for
this.
F
F
F
The
title
is
not
arrangeable,
there
there's
an
issue
for
it,
and
I
would
welcome
it
very
much
if
we
could
add
this
future,
but
that
this
is
the
kind
of
feedback.
I
think
we
need,
because
every
approach
has
its
difficulties,
and
now
we
have
to
decide
which
difficulty
to
solve
and
also
which
yeah
which
at
which
place
backdrop
will
win.
For
example,
if
we
would,
by
this
opportunity,
would
make
title
as
a
pseudo
field
and
make
it
rearrangeable,
it
would
be
a
very
nice
thing.
B
I
H
A
hidden
path,
node
is
a
node
that
doesn't
have
its
own
page
and,
and
you
can
use
an
existing
content
block.
We
have
existing
content
blocks
in
core
and
in
an
existing
content
block
you
just
put
a
node
number
in
it
and
that
that
node
populates
the
block
and
one
of
the
main
use
cases
for
existing
content
blocks
is
to
make
it
easier
for
site
editors
to
to
edit
blocks
because
oftentimes,
we
don't
give
site
editors
access
to
edit
blocks,
but
we
do
give
them
access
to
edit
nodes.
H
So
if
you,
if
you
use
existing
content
blocks,
your
site
editor
can
edit
the
content
of
blocks.
So
that's
the
that's.
The
feature
that
we're
trying
to
introduce
is
to
add
this
content
type
to
core,
but
we
we
feel
like
we
need
to
demonstrate
how
it's
used
in
the
install
profile
and
that's
where
the
problem
is
right
now
is
how
do
we?
I
I
H
Certainly
for
those
of
us
who
started
this
issue,
we
feel
like
this
is
a
it's
an
important
or
it's
a
very
useful
tool.
These
these.
H
A
useful
tool
for
users,
but
it's
exactly
the
fact
that
people
don't
understand
them,
which
is
partly
why
we
wanted
to
put
them
in
core
and
demonstrate
how
to
use
them
to
make
them
more
understandable,
yeah.
But
your
your
response
is
very
common,
a
lot
of
people
when
they
first
look
at
the
issue
are
kind
of
like
I
don't
quite
get.
Why
you're
doing
this.
H
G
What
if
we
would
add
a
a
recipe
that
would
provide
us
with
another
page
on
the
website,
not
necessarily
the
homepage,
but
it
would
just
create
a
recipe
or
a
block
demonstration
page
right.
We
could
add
a
block
demonstration
template,
then
that
would
be
able
to
handle
that,
but
maybe
that's
a
way
to
package
it,
and
it
would
be
an
extra
page
on
the
website
rather
than
the
front
page.
H
So
you
know
my
quick
response
is
that
a
lot
of
the
excitement
around
around
this
pr
is
that
it
does
also
update
the
front
page,
but
that
here
we're
sort
of
blending
different
purposes,
and
I
don't
know
if
we
should
be
so
we
have
so
you
know
olaf
and
I
have
identified
like
two
possible
solutions,
and
the
question
is:
is
there
opposition
to
those
before
we?
D
I
I'm
in
favor
of
not
specifically
the
home
page
but
in
general,
providing
one
of
the
default
layouts
having
a
flexible
layout
out
of
the
box
because
of
the
benefits
that
flexible
layouts
provide.
If,
if
the
home
page
provides
an
opportunity
to
do
that,
yeah
so
long
as
we
don't
break
existing
sites.
A
A
You
are,
if
that's
a
preferred
approach
or
not,
but
I
could
see
that
being
a
very
good
argument
for
let's
definitely
not
make
a
new
layout
a
theme
to
layout
just
for
the
home
page
if
we're
making
it
just
for
this
one
page,
because
now
we've
just
created
yet
another
layout
that
you
know
that
maybe
it
it
would.
I
would
prefer
the
flexible
approach
over
making
a
new
template,
and
so,
if
those
are
our
only
two
options,
then
I
would
take
the
flexible
approach.
A
D
The
flexible
layouts
provide
a
two
things
that
that
that
exist
in
drupal
land.
The
way
that
I
see
it
is
the
new,
so
some
of
the
not
all
of
the
functionality
but
comparable
features
right.
One
is
the
layout
builder
for
drupal.
So
it's
something
comparable
to
that,
and-
and
second
is
something
that
you
were
able
to
do.
D
Yeah
so
and
there's
a
very
old
issue,
I'll
try
to
find
it
where
we
were
before
even
layout
builder
existed,
where
people
suggested
that
hey
they
saw
this
like
in
wix
or
some
other
product,
where
you
could
sort
of
like
drag
and
drop
and
create
squares,
which
would
be
your
regions
and
they
would
say.
Yes,
we
want
this
a
visual
layout
builder,
which
is
basically
what
flexible
layouts
are
so
yeah.
D
That's
why
I
said
I
would
be
in
favor
of
one
of
our
default
layouts,
even
if
it
was
one
that
was
disabled
and
you
could
enable
was
using
a
flexible
layout.
I
see
the
benefits
of
that.
B
I
don't
I'm
also
on
your
team
here
nate.
I
also
feel
like
the
inflexible
layouts
are
currently
limited
by
permissions,
so
you
could
have
people
who
are
allowed
to
adjust
layouts
but
can't
get
to
flexible
layouts
and
in
the
future
we
also
talked
about
setting
them
up
as
a
separate
module
that
can
be
disabled.
I
Let
me
ask
what
is
flexible
layout
apologize
for
interrupting
it's
very.
This
topic
is
very
dear
to
my
heart.
I
That
is
a
very
big
problem,
and
I
know
that
there
are
other
templates
that
eliminate
this
very
simple.
This
is
a
very
minor
but
very
important
topic.
So
maybe
I
misunderstand:
what
is
flexible
layout.
D
I
H
I'll
just
one
argument
for
I'm
not
advocating
for
this,
but
one
argument
for
a
new
layout
template
might
be
one
to
address
the
problem
that
jen
just
raised,
but
two
because
I
don't
think
any
of
our
current
layout
templates
work
good
for
like
from
the
common
front
page
designs
in
terms
of
like
the
placement
of
the
container
block
and
region.
So
I
think
there
an
argument
could
be
made
that
adding
a
layout
to
core
that
kind
of
addresses
some
of
the
common
needs.
H
B
I
think
that
would
be
much
easier,
because
it
would
be
something
that,
if
nobody
like
on
any
existing
site,
if
they'd,
never
used
it,
it
could
even
be
disabled.
If
we
wanted
to,
we
have
ability
to
enable
enable
disable,
the
enable
and
disable
specific
layouts,
but
we
could
also
just
leave
it
enabled
and
then
the
next
time
they
go
to
create
a
layout
they'll,
have
a
new
option
and
then
for
new
installs.
They
could
use
the
new
layout.
B
I
also
would
be
in
favor
of
you
know
if
we
are
finding
a
limitation
with
the
layouts
that
are
in
core.
Adding
a
new
layout
gives
people
more.
Flexibility
also
solves
that
problem
for
them
down
the
road
where
maybe
they
don't
need
to
make
a
flexible
layout
in
order
to
get
what
they
need,
and
I
think
that
that
you
know
if
we
could
get
some
use
cases
of
what
do
you
do
on
a
homepage?
F
Yeah,
I
think
this
sounds
good
in
theory,
but
this
way
the
issue
becomes
even
much
bigger
and
so
I'm,
I
fear
that
we
don't
get
it
in
for
the
next
release
this
way
because
yeah
it
sounds
good,
but
who
does
the
work
and
the
decisions
for
the
layout?
And
maybe
we
can't
decide
in
time
and
so
on.
So
I'm
not
sure
if
I
agree
and
then
there's
even
the
feel
the
title
field
issue,
which
is
another
problem
and
it's
it's
not
easy
for
the
people
fields.
C
C
They
they'd
know
it,
but
also,
if
they're
coming
from
drupal,
they
understand
how
to
play
with
views.
Whereas
layouts
are
this
new
thing
and-
and
I
agree
that
we
we
want
to
introduce
people
to
the
power
of
layouts,
but
this
might
not
as
as
complicated
as
it's
starting
to
get.
This
might
not
be
the
right
tool
to
use
to
do
that.
Introduction
so
maybe
revisit
whether
just
going
with
a
view
would
work
yeah.
B
I
think
the
view
was
sort
of
a
work
around
for
this
problem.
Originally,
when
I'm
like.
Oh,
I
want
the
thing
that
greg
showed
us.
How
do
we
do
that
with
what
we
have
and
fuse
was
the
answer
to
that?
It
might
also
be
good,
though,
and
have
a
follow-up
issue.
That's
like
let's
talk
about
how
we
could
do
this
with
the
layout,
and
maybe
we
get
this
issue
done
with
the
current
approach
and
we
not
worry
about
layouts.
B
F
F
D
H
I'm
just
going
to
endorse
this,
given
the
direction
everything's
went,
which
is
that
we
go
with
the
views
option,
but
that
we
open
an
issue
and
we
maybe
look
at
this
idea
of
a
new
template
which
addresses
some
of
the
front
page
issues
and
then
once
we've
got
that,
then
we
could
reorganize
the
front
page
using
that,
if
we
decide,
my
only
fear
was
that
people
won't
want
to
change
the
way.
But
maybe
that's
not
an
issue
like
if
we
start
with
views
for
this
and
then
we
do
have
a
template.
H
B
D
Just
just
the
same
this
black
that
that
I
have
an
issue
somewhere
lying
there,
that
to
introduce
a
button
that
says,
use
this
fixed
layout
template
to
create
a
flexible
template
so
that
people
say
I
like
this,
but
it's
not
100
what
I
need.
So
then
you
start
off
with
that
and
then
you
sort
of
like
mix
and
match
them
by
the
way.
D
I'll
find
it
I'll
I'll,
send
it
yeah
so
so
alice
alejandro
has
joined
us.
Maybe
we
want
to
give
him
an
opportunity,
hello
to
to
say
something.
I'm
not
sure
if
you
joined
to
say
something
specifically
or.
A
A
Well,
we
are
at
the
top
of
the
hour
and
kind
of
out
of
time
for
this
normal
discussion.
The
big
takeaways
from
today
is
that
we're
going
to
release
121.1
tomorrow,
one
way
or
the
other
we're
gonna
try
to
write
a
better
update
hook
and
if
we
can't
write
a
better
update
hook
and
test
it
before
then
we'll
go
with
the
poll
request
that
we
have
currently
that
reverts
that
problem
and
cleans
up
the
user
login
link
yeah.
A
It
sounds
like
yeah,
we'll
bump
to
php
5.6
kind
of
whenever
we
get
around
to
it.
That'll
probably
be
in
the
next
week
and
the
hidden
path.
Node
type
sounds
like
we
kind
of
have,
at
least
amongst
those
present
reached
a
general
agreement.
That's
proceeding
with
what
we
have
right
now
is
the
most
clear
way
forward,
but
not
necessarily
the
final
product
that
we
might
follow
up
again
later.
A
B
A
So
so
I
like
this
idea
of
going
with
what
we
have.
I
think
that
that'll
at
least
make
the
number
of
problems
that
we're
trying
to
solve
like
fewer
or
split
up
into
more
separate
issues,
so
wow
lots
of
things
that
have
all
been
happening.
So
thank
you,
everybody
for
for
joining
us
meeting.
It
was
a
really
great
one
and
we're
gonna
leave
this
room
open
after
the
recording,
but
I
think
we'll
go
ahead
and
end
the
broadcast
and
say
thank
you
all
for
joining.