►
From YouTube: 2021/12/30 Backdrop Weekly Dev
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
december
30th
2021,
the
last
meeting
of
the
year
and
the
last
meeting
before
the
1.21
backdrop
code,
freeze,
we'll
go
ahead
and
get
started
with
some
introductions:
I'm
nate
lampton,
I'm
quick
sketch
on
the
internet,
I'm
core
committer
and
I'm
coming
from
oakland.
California.
B
Hi,
my
name
is
jim,
I'm
in
no
I'm
not
in
st
paul.
My
name
is
saint
paul
tim,
I'm
in
deerwood,
minnesota
and
yeah.
That's
that's
it
for
today.
A
Thanks
tim
robert
and
then
joseph
I'm
robert
lang,
bud
folder
on
the
internet,
coming
to
you
from
a
very
rainy,
altadena.
California,
awesome.
Thank
you,
robert
joseph
and
then
greg.
A
Thank
you
greg
and
then
wilbur.
D
I
am
greg
I'm
joining
from
greece.
Thank
you
to
help.
E
My
name's
will
brance
I'm
coming
from
the
twin
cities
of
the
usa.
I
go
by
wilbur
w-y-l-b-u-r.
H
And
john
lampton
from
oakland
california,
hello,
everyone.
A
A
E
A
Everyone
not
professional
of
my
part
but
okay.
C
A
It
is
the
last
meeting
before
code
freeze,
I
think,
last
time
I
was
in
a
meeting
I
incorrectly
stated
when
code
freeze
was
going
to
happen
because
we
have
code
freeze
on
january
1st.
That's
the
official
normal
date
for
a
code.
Freeze
is
the
first
of
the
month
before
the
code
for
before
the
release,
but
that
is
on
a
saturday
and
we
normally
extend
code
freeze
up
until
the
last
non-holiday
day
before
I'm
sorry
after
the
code
free
state.
A
So
that
means
that
code
phrase
is
actually
going
to
be
january,
2nd,
which
is
a
sunday.
So
we
have
just
one
two
three
more
days
before
code
freeze
and
we
have
also.
A
Not
according
freeze
or
feature
freeze,
sorry
feature.
Freeze,
yes,
feature,
freeze
means
that
unfinished
features
that
didn't
get
in
before
january,
2nd
will
be
pushed
to
the
next
minor
release.
1.22
that
still
allows
us
to
get
in
user
interface
fixes,
as
well
as
bug,
fixes
and
follow-ups
to
the
ones
that
we
did
get
in
during
the
two-week
period
in
between
january,
2nd
and
january
15th.
A
So,
let's
see
before
we
get
into
that
jen.
Do
you
have
the
contrib
update,
ready.
H
Yup,
there's
only
two
modules
since
last
week
we
have
text
resize
new
release
and
read
time.
A
Awesome,
thank
you
to
our
contributors
that
are
putting
creating
new
modules
or
porting
those
modules
from
their
drupal
equivalents.
A
So,
let's
see
today,
we
normally
have
an
agenda
that
we
run
through.
There
wasn't
any
suggested
items
to
discuss
today,
other
than
a
topic
that
was
covered
during
the
previous
meeting.
A
A
A
So
oops
my
screen
keeps
reloading
we'll
start
at
the
beginning,
so
drop
support
for
php
lower
than
5.6
or
establish
a
best
effort
policy.
So
this
is.
This
decision.
Has
been
made
that
we're
going
to
drop
support
for
older
versions
of
php
before
5.6,
but
we're
not
actually
going
to
do
it
in
the
1.21
release.
We
just
haven't
opened
the
1.22
milestone
yet
which
perhaps
we
should
move.
A
We
should
create
that
and
move
this
into
that,
because
the
idea
is
that
we'll
merge
this
post
1.21
release
and
then
we'll
have
the
the
dropping
of
support
for
5.6
as
a
notice
of
some
kind
through
the
1.21
milestone,
which
means
now
I'm
thinking
about
it.
We
do
need
a
pull
request
that
surfaces
that
to
the
status
report,
so
perhaps
this
actually
should
not
be
fixed
but
need
a
pull
request
to
put
that
into
1.21.
A
Next,
up,
telemetry
module
on
new
installs
hold
this
one
up
just
before
the
meeting
and
saw
that
doc
belmont
has
filed
a
pull
request
on
this
issue
that
does
not
affect
the
installer
turns
on
telemetry
module
by
default,
and
then
it
also
adds
a
block
to
the
dashboard
to
surface
telemetry
information
to
the
dashboard.
A
I
haven't
actually
tested
it
in
the
sandbox.
I've
just
read
over
the
code,
so
this
is
something
that
we
could
use
some
eyeballs
on.
I
think
that
his
note
here
is
correct
that
we're
still
waiting
on
a
pmc
decision
on
this
one.
B
I
can
just
jump
in
and
say
that
I
think
we
have
a.
I
think
we
can
have
a
policy
decision
from
the
pmc
by
to
allow
for
opt-in,
which
is
dropped
out,
but
there
is
still
some
debate
or
discussion
going
on
about
how
to
add
new
telemetry
features,
but
I'm
not
I'm
not
sure
if
that
would
be,
that
decision
would
be
required
for
this
pr.
A
Yeah,
it's
a
good
question.
I
I
I
view
that
as
being
a
generally
separate
problem,
but
yeah,
that's
it's
just
it's
still
something
that
should
be
discussed.
B
And
just
to
make
to
clarify
ideally
the
sooner
the
better,
but
could
we
go
ahead
and
merge
if,
if
the
assumption
is
that
the
the
policy
is
going
to
pass
and
the
pr
is
ready,
could
we
go
ahead
and
merge
it,
and
then,
if
there
were
some
policy
decision
in
the
next
two
weeks,
sort
of
pull
it
back
or
where
would
you
not
want
to
merge
it
until
you
had
a
firm
policy
decision,
I
would
prefer.
A
Be
fine
but
for
sure
one
thing
about
the
approach
the
document
has
taken
here
so
far
is
that
this
definitely
needs
additional
review,
because
it's
not
just
turning
on
the
module,
it's
actually
making
a
new
block
on
the
dashboard.
D
A
D
B
D
A
Yeah,
okay!
Well,
this
could
use
some
testing
to
verify
that
the
approach
that
document
has
taken
with
the
block
all
looks
acceptable.
A
It
seems
like
this
is
this
is
like
a
you
know,
you
know
putting
on
your
belt
after
you've
already
got
suspenders
on
type
thing.
You
know
that
it's
already
on
the
status
report,
and
this
like
duplicates
that
same
like
information,
hey,
there's
something
being
reported
in
another
location.
A
Okay,
next
up
allow
settings
for
book
navigation.
This
is
a
pretty
simple
pull
request
that
herbdual
has
put
forward.
D
Whether
we
should
make
it
content,
type
or
global,
and
some
say
that
it
should
the
the
perk
on
the
type
thing
should
be
left
for
contrib,
and
it
should
be
a
global
thing
for
core.
Well,
I
yeah
anyways.
B
Yeah
jen,
open
jen
opened
this
issue
and
jen.
If
you
haven't
had
a
chance
to
look
at
it,
you
should
because
I
don't
think
it
does
what
you
asked
for
in
the
original
request,
because
it's
a
global,
because
it's
a
global
setting,
which
my
interpretation
of
what
you
wanted,
was
the
ability
to
have
the
navigation
on
book
pages,
but
not
on
other
pages
yeah.
This
pr.
This
pr
lets
you
turn
off
the
navigation
globally,
not
distinguish
between
one
intent
and
type
or
another.
A
Okay,
so
this
one
yeah
definitely
still
needs
review
yeah.
We
could
potentially
proceed
with
the
option
that
we
have
now,
which
is
global
and
then
convert
it
to
per
content
type
later,
that's
not
too
difficult
of
an
upgrade
path,
but
yeah.
If
it's
not
providing
the
feature
that
we
want,
or
especially
at
the
requester
originally
requested,
then
yeah.
We
can
reconsider
that.
A
Okay,
this
next
one
is
provide
a
new
hidden
path,
content
type
in
core.
This
one
is
continuing
to
see
a
lot
of
activity
and
discussion.
I'm
hoping
tim,
you
might
be
able
to
give
us
a
summary
of
where
we're
standing
right
on
it.
Right
now,.
B
So
we
started
to
talk
about
this
in
the
last
meeting.
The
status
of
this
is
as
of
the
last
meeting.
B
We
had
tentatively
decided
to
postpone
this
actually
to
1.22
and
they
that
might
be
news
to
you
beca,
partly
because
it's
going
to
affect
all
contribute
themes
and
we
wanted
to
be
able
to
give
contrib
teams
time
to
fix
it.
Now
some
of
our
contrib
authors
said
that
they
thought
two
weeks
would
be
enough.
B
I
had
hoped
to
have
a
more
comprehensive
list
of
which
themes
would
be
affected
by
this
meeting
so
that
we
could
decide
if
we
really
wanted
to
postpone
it,
but
another
issue
came
up,
which
is
whether
or
not
we're
currently
using
a
view,
and
I
I
do
have
a
the
the
site
open.
If
anybody
wants
to
look
at
it,
I
can
share
my
screen,
but
we're
currently
using
a
view
for
the
three
card
blocks
and
we
had
a
minor
issue,
and
this
issue
is
not
a
blocker.
B
It
wasn't
sorting
properly,
presumably
because
all
of
the
nodes
were
created
at
the
same
time,
and
so
then
we
were
discussing
should
we
add
another
short
order
field
or
some
or
should
we
use
some
other
means
of
sorting
it
when
doc
wilmont
pointed
out
that
any
of
those
solutions
are
a
little
bit
hacky
and
that
really
three
different
existing
content
blocks
in
different
regions
would
be
the
most
logical
choice
for
this,
and
I
think
some
of
us
agreed.
B
B
I
think
we
would
have
to
have
a
new
layout
and
unless
we
had
three
existing
content
blocks
and
just
styled
them
like
three
regions
that
that
there's
a
bunch
of
options
out
there
and
right
now,
we
just
don't
have
a
firm
decision
on
what
is
the
best
option,
and
I
think
that
if
we
did
move
towards
anything
other
than
a
view
that
we'd
probably
need
more
time
to
make
sure
everything
works.
B
So
I
don't
know
I'm
kind
of
feeling
like
and
unless
we
reverted
and
decided
to
just
stick
with
the
view
and
go
ahead
and
try
to
push
this
forward.
That
probably
we
are
going
to
need
to
delay
this
to
1.22
and
try
to
get
it
in
very
early
in
the
release
cycle.
You
know:
have
this
be
the
first
commit
because
we're
very
close,
we
could
get
this
done
in.
A
Okay,
yeah,
okay,
one
nice
thing
about
this-
at
least
I
I
feel
this
way
is
that
this
is
not
a
feature
that
benefits
existing
sites.
It's
about
the
new
site.
Experience
right,
so
I
feel,
like
a
lot
of
people,
are
probably
willing
to
like
let
this
one
slide,
because
it
doesn't
impact
their
desire
for
increased
functionality
on
their
current
sites
right
so
yeah.
I
can
see
that
being
a
good
justification
for
like.
What's
not,
let's
not
rush
this
okay.
B
A
B
A
Yep
agree:
okay,
okay!
Next
up,
we
have
trim
summary
on
word
boundary.
I
believe
this
is
basically
moving
a
contrib
module
into
core
here's.
The
settings
that.
A
Looks
like
it
trims
based
on
like
it
can
cut
off
mid-sentence
rather
than
making
summaries
cut
off
at
a
paragraph.
So
this
is
the
benefit
of
having
a
more
predictable
length
of
character
trimming
than
the
out-of-box
functionality
on
the
the
body
field.
D
I
can
timing
in
that.
So
basically,
basically,
we've
hit
a
problem
where
the
word
boundary
works,
but
then
things
are
being
cut
off
and
html
breaks,
because
the
html
tags
are
being
counted
within
the
word
or
the
count.
The
character
count
boundaries.
D
So
if
you
look
at
the
very
bottom
of
the
last
message
posted
by
peter,
he
said
that
he's
starting
to
work
on
the
previous,
the
309
issue.
If
you
hover
over
it
you'll
see
that
it's
basically
the
actual
issue,
which
is
how
to
figure
out
a
way
to
not
count
html
characters
like
html
tag,
characters
in
as
part
of
the
the
lane,
and
if
you
go
to
that
issue,
then
what
we?
D
What
was
used
for
the
current
solution
was
from
cake,
like
I
think,
a
borrowed
function
from
cake,
be
its
pain
which
does
more
things
than
we
wanted
to.
So
peter
is
actually
working
or
looking
for
help.
A
B
At
one
point
peter
said:
maybe
we
should
you
know
that
that
was
a
pre-existing
issue
right
that
the
other
issue
is
really
separate
from
the
the
word
split.
So
he
was
like.
Maybe
we
can
make
that
a
follow-up
issue,
but
in
this
last
comment
he
seems
to
have
backtracked
and
said.
I
think
that
he's
having
he's
having
second
thoughts
and
might
want
to
do
something
different.
D
Okay,
but
here
either
ck80
or
the
default
browser
behavior
is
to.
If
you
have
open
tags,
html
tags
it
automatically
tries
to
close
them
best
as
it
can.
But
then
you
end
up
with
breakages
in
both
situations,
both
character
account
and
word
count.
So
we're
trying
to
sort
of
like
tackle
that
issue
before
we
could
we
get
into
the
specifics
of
those.
A
Yeah,
I
know
I
know
in
particular,
things
like
a
table
can
cause
major
problems
on
automatic
trimming
because
it
can
trim
in
the
middle
of
the
table
and
just
like
close
the
current
cell
and
the
current
row
and
then
the
current
table.
You
end
up
with
like
a
row
that
just
like
stops
in
the
middle
of
the
row
and
like
the
rest
of
the
table
is
just
gone.
H
B
Yeah
but
but
that's
all
true,
but
that
is
a
different
issue
than
the
one
that
was
trying
to
be
solved
here
and
so
yeah
he
had.
He
had
a
working
solution.
You
know
that
was
better
than
what
we
had
it
just
didn't
solve
the
other
thing
you
know.
I
think
that
an
argument
could
be
made
that
this
this
pr
makes
things
better
without
making
anything
worse.
A
Yep
I
yeah
yeah.
I
don't
feel
like
that.
This
needs
to
be
done
in
a
particular
order,
like
I
think
he
he's
saying
that
both
word
trimming
and
paragraph
trimming
would
have
similar
fixes,
but
this
could
go
in
first
and
then
the
fixes
could
apply
to
both
of
them
or
vice
versa.
We
could
fix
the
current
trimming
and
then
reuse
that
on
this.
H
So
I
missed
the
first
beginning
of
this,
but
did
you
guys
talk
about
this?
How
the
smart
trim
module
does
this.
H
So
that's
the
current
solution.
If
you
have
a
drupal
or
a
backdrop
site
that
is
unable
to
trim
properly
without
breaking
your
formatting,
the
current
solution
is
to
install
the
smart
trim
module
because,
however
it
does
it's
trimming
seems
to
be
much
smarter.
I
haven't
looked
at
the
code
in
that
module.
I
don't
know
what
its
quality
would
be
like
for
core
inclusion,
but
it
might
be
worth
reviewing
at
least
the
approach
they
took
to
fix
the
problem.
H
I
don't
know
if
it
also
fixes
the
problem
bwa
pian
does
after
here,
but
it
it
might.
Maybe
it's
too
late
to
think
about
that
now,
I'm
also
in
favor
of
making
things
better.
Even
if
it's
not
perfect,
so
I
just
want
to
throw
that
out.
There.
B
Okay,
here
it
is
interesting.
Oh
I
will
say
we
we
had
somebody
in
the
forum
in
the
last
couple
of
weeks,
who
reported
their
drupal
7
site
to
backdrop
and
teasers
that
had
like
several
sentences
were
cut
down
to
just
three
words,
because
the
the
additional
sentences
were
all
in
the
second
paragraph.
So
if
you've
got
a
excuse
me,
a
600
word
limit,
but
your
first
sentence
is
only
two
words:
it
will
cut
off
after
the
first
sentence,
the
first
two
words
which
seemed
really
counter
so
this
this
already
fixes
that
problem.
B
So
it
does
solve
a
problem
yeah,
even
though
it
doesn't
solve
the
bigger
problem
or
the
other.
I
want
to
say
bigger
the
other
problems.
C
Yeah,
so
I
don't
know
if
this
would,
I
don't
know
if
this
would
help
or
make
it
more
complicated
or
whatever,
but
php
has
a
built-in
set
of
objects
that
allow
you
to
represent
a
html
structure
and
navigate
traverse
it
similar
to
the
way
you
would
in
javascript,
and
so
we
could
use
something
like
that
to
traverse
arbitrary
things
like
tables
or
lists
or
whatever,
to
trim
at
particular
spots.
A
Yeah,
I
don't
quite
know
where
that's
gonna
sit
as
far
as
like
difficulty
and
side
effects,
it
looks
like
the
smart
trim.
Module
is
not
actually
very
fancy.
I
mean
this
is
like
you
know,
regular
expressions
for
the
most
part
it
looks
like
in
the
end.
It
actually
uses
the
core
text
summary
for
paragraphs.
So
this
this
module
looks
like
it
mostly
deals
with
similar
functionality
like
trimming
based
on
word
length.
A
Yeah
then
it
does
a
bunch
more
work
afterwards,
yeah
interesting,
okay.
Yes,
this
definitely
needs
some
thinking
here,
even
about
the
approach
which
doesn't
put
us
in
a
good
good
position
on
this
issue,
but.
H
I
mean
how
would
you
feel
as
a
core
committer
about
like
if
we
have
something
in
the
already
state
that
fixes
the
original
problem
stated
getting
that
in?
For
I
mean
if
it's
a
bug
fix,
I
don't
know
how
big
the
change
is,
but
getting
that
in
like
shortly
and
then
following
up
with
another
issue,
that
would
be
to
sort
of
like
rethink
the
whole
problem
space.
Or
would
you
not
want
to
commit
a
partial
change,
knowing
that
something
else
is
coming.
A
A
It's
at
the
bottom,
this
one
that
this
one
is
like
this
one's
like
a
bug
so
yeah.
I
think
these
two
things
could
totally
be
handled
separately.
Like
tim,
okay,
like
this
is
a
feature.
F
A
A
This
needs
work
according
to
the
tag
gregory
you're,
the
advocate
for
this
one.
Can
you
give
us
a
summary.
D
Yeah,
so
if
you
scroll
at
the
very
bottom
there's
a
comment
by
doc,
wilmer,
which
I
need
to
respond
to
so
basically
it
started
with
issue
1040
and
when
I
announced
that
I
was
going
to
be
advocating
for
that
you,
I
recall
you
saying:
oh
that's
a
very
hard
one.
I
was
wondering
what
are
you
talking
about
and
now
I
know
what
you
were
talking
about
because.
D
While
I
started
working
on
inline
form
messages,
there's
other
things
that
we
need
to
fix,
or
some
of
them
are
either
d7
or
d8
things
that
got
committed
and
improved
the
situation
that
we
need
to
backport
or
cross
board.
Some
of
them
are
like
the
the
issue
that
is
linked
there.
53
46
is
a
regression
that
was
caused
by
the
solution
that
was
used
for
d8.
D
So
basically
they
switched
to
natively
supporting
html5
validation
errors,
but
now
they
can't
customize
the
the
error
messages
that
they're
throwing,
which
is
what
this
issue
is
about.
So
basically,
this
issue
is
introducing
a
new
parameter
which
is
bear
with
me.
D
Yes,
that's
that's
the
one
yes,
so
this
basically
allows
you
to
customize
those
hard
coded
browser
validation
errors.
So
we
need
to
get
that
one
messed
in
and
then
I
guess
we
need
to
merge
the
other,
the
html
native
validation
and
then
we
can
move
forward
with
1040,
but
there
may
be
other
issues
as
well.
D
So
as
I'm
digging
deeper
into
the
form
api,
I
I
come
across
various
small
issues
that
need
to
be
solved,
and
I
I
did
at
some
point
started
mentioning
that
I
might
not
be
able
to
get
this
like
1040,
initially
initially
for
120
1.21,
but
I
would
like
to
get
it
as
close
as
possible
like
eliminate
as
many
blockers
as
possible
so
that
it
can
eventually
get
in.
I
realized
that
this
is
breaking
some
functionality
with
the
search
form,
so
I
need
to
tweak
it
I'm
hoping
to
work
on
it
over
the
weekend.
A
Okay,
so
so
I
definitely
I
see
what
you're
saying
that,
so
this
affects
these
other
two
issues.
But
yes,
let
me
say
this
again
in
a
different
way:
you're
hoping
to
get
this
one
done
first.
Is
that
right,
yes
and
then
work
my.
D
A
Yeah
yeah,
so
that's
really
these
yeah-
that
this
functionality
would
be
heavily
affected
by
this
new
issue.
The
required
attribute,
because
you
need
to
use
the
custom
messages
that
are
created
yeah.
I
see
so
it's
not
really
a
blocker
for
this
issue,
but
this
issue
would
be
heavily
affected
if
it
is
actually
a
blocker.
D
A
Right
yeah:
oh,
I
see
kind
of
what
you're
saying
that.
Oh
that's
really
interesting
greg.
I
see
what.
A
So
you
need
to
know
what
the
message
is
without
firing
the
validate
handlers
in
order
for
this
all
to
work.
Interesting,
so
that
so
it
has
to
be
separated
from
the
validate
handlers
and
put
someplace
accessible
by
itself.
In
order
for
us
to
use
html5
validation
messages,
it
has
to
be
available
outside
of
the
validate
handler
and
be
available.
Discreetly,
that
make
sense.
A
A
Okay,
well
cool
yeah.
I
I
hadn't
quite
realized
how
this
issue
is
so
important
to
the
other
one
like
yeah,
interesting,
okay,
yeah.
Thank
you
for
the
summary
on
that
one
we'll
keep
keep
going
along,
because
we
still
have
a
lot
more
to
go
through.
Okay,
this
next
one
entity,
view
and
decor.
A
I've
been
checking
in
on
this
one,
I
think
of
the
people
here.
I'm
I'm
best
suited
to
to
check
in
on
this
one.
So,
oh
well,
oh
you
were
here
in
here
too,
but
herb
jewel's
been
doing
all
of
the
work
here,
fixing
up
stuff
for
making
this
happen.
Herbal
is
also
reworking
a
lot
of
the
entity
reference
module.
A
So
his
objective
is
that
he
thinks
that
entity
reference
module
as
it
exists
in
contrib
is
the
best
solution
forward,
which
is
different
from
our
previous
direction
of
trying
to
use
the
new
reference
module,
but
it
doesn't
really
matter
because
for
this
issue,
both
approaches
benefit
from
the
work
that
is
being
done
here.
This.
This
is
a
problem,
regardless
of
which
entity
reference
module
we
use,
and
so
this
is
preliminary
work
that
we
need
to
get
done
either
way.
A
A
A
So
overall,
this
this
all
looks
really
good.
I
think
that
this
one's
completely
feasible
for
us
to
get
in
looks
like
it's
back
to
rtbc
and
I've
reviewed
it,
and
I
think
I
think
it
looks
good
there's
some
follow-up
work
here
that
one
that
I'd
like
to
get
done,
but
it's
not
a
blocker
on
this
overall
issue
if
I
were
to
get
into
it
just
a
little
bit.
A
What
I
don't
like
about
this
issue
is
the
fact
that
finding
how
content
is
viewed
becomes
more
difficult
to
figure
out
because
there's
more
layers
of
nesting,
but
that's
the
same
problem
we
already
have
for
stuff
like
the
load
operation
on
a
node.
It
used
to
just
be
node
load,
you'd,
look
in
node
load
and
you
could
see
a
query
in
the
database.
A
Now
you
have
to
go
to
the
node
storage
controller,
to
find
out
where
stuff
is
loaded
from,
and
this
kind
of
adds
that
same
abstraction
to
the
viewing
operations
that
we
already
have
for
the
loading
operations.
A
The
thing
I
like
about
this,
though,
is
that
we
are
coming
to
an
agreement
that
we
currently
have
these
classes,
that
do
storage,
and
then
we
have
these
classes
that
do
non-storage
operations
and
based
on
the
backdrop,
focus
on
certain
like
making
decisions
around
way
things
work.
We
really
only
support
mysql
and
we
don't
support
alternative
field
storages
that
we
should
merge
together.
A
So
this,
while
it
adds
abstraction
in
one
place,
a
follow-up
issue
would
be
to
remove
some
of
the
abstraction
to
flatten
the
structure
a
little
bit.
So
I
think
it'll
be
a
net
like
this
is
a
good
thing.
By
doing
this,
plus,
of
course,
we
get
the
functionality
we
need
for
entity
reference
module,
so
big
win
on
that
front.
A
A
Okay,
fantastic,
okay:
next
up
is
optimize
menu.
Navigation
links
rebuild
joseph
is
the
advocate
for
this
one.
It's
already
marked
rtbc,
which
is
fantastic.
Let's
see
who
is
our
doc?
Belmont
was
our
reviewer
here.
I
also
reviewed
it
last
week.
It
looks
really
good.
I
don't
have
any
complaints
about
the
approach
so
far,
but
I
want
to
give
it
one
more
look
over
before
we
put
this
in
joseph.
Do
you
want
to
say
anything
about
this
issue.
C
I
I
well,
I
did
make
a
change
to
it,
but
I
think
that
was
before
you
reviewed
it.
So
I
don't
think,
there's
anything
really
to
discuss
about
that.
Who
was
it?
I
think
jen
was
commenting
on
the
pull
request
that
she
was
uneasy
about
the
removing
I
had
to
remove
part
of
a
test
in
order
to
make
the
tests
pass,
and
she
wanted
us
to
ask
a
core
committer
about
that.
H
Yeah
just
a
second
opinion.
It
made
me
a
little
nervous
because
I
was
like:
are
we
supposed
to
support
that?
But
if,
if
we
don't
need
it,
it's
fine.
C
So
we
have,
we
have
some
tests
that
check
that.
So
this
is
in
the
menu
link,
re-parenting
tests,
and
we
have
some
tests
that
check
that
menu
link.
Re-Parenting
works
in.
C
If
you
use
what
is
that
menu
link
delete,
I
think
so
you
you
load
the
link,
you
get
the
id,
you
pass
it
in
a
menu
link,
delete
everything
works
fine
in
those
tests
in
these
tests
it
just
does
a
db
delete,
but
because
I'm
using
a
static
cache
internally.
This
doesn't
get
updated
in
the
in
the
static
cache
until
the
next
page
load,
and
so
the
menu
re-parenting
doesn't
happen
until
the
next
page
load.
Yeah.
C
F
A
Yeah,
it's
an
interest,
an
interesting
concern.
I
I
think
it
would
be
nice
to
be
able
to
maintain
the
tests.
So
I
I
would
say,
let's
try
to
get
the
tests
working.
Okay,
but.
A
I'll
take
a
look
at
that
when
I
next
review
it
all
right
and
see,
we've
got
10
minutes
left
better
default
position
for
breadcrumbs
on
the
installation
of
new
sites.
I
haven't
checked
on
this
one.
In
a
long
time,
tim
you're,
probably
the
best
suited
to
talk
about
this.
B
B
A
B
A
Okay,
breadcrumb
add
empty
option
to
theme
item
list.
I
haven't
even
seen
this
one
before,
but
I
like
the
sound
of
it
already
so,
if
you're
using
an
item
list-
oh
I
like
it
up
until
I
when
I
saw
this
syntax.
A
Okay,
I,
like
I
like
this
more
okay,
so
robert
came
in
here
and
said
this
can
be
a
string
or
a
render
array,
so
pound
empty
actually
could
just
be
a
translated
string,
which
would
be
a
common
use
case.
I
would
think
okay
well,
this
is
interesting.
I
I
see
what
this
is.
So
this
pound
markup
actually.
A
A
C
I
think
a
single
level
markup
that
just
has
a
t
function
as
its
value
is
just
the
same
as
having
a
t
function.
H
H
A
D
And
basically,
I've
just
backboarded
what's
already
in
drupal,
so
it's
more
like
a
feature
parity.
So
if
people
are
trying
to
backboard
code
it
would
work
the
same,
but
I'm
fine.
If
we
don't
want
to
have
certain
things
work
that
way
and
I've
created
a
change
where
I
could
address
trains
record
as
I
say
there,
so
you
can
have
a
look
at
that.
D
A
Great
I'll
express
my
concerns
in
the
comments:
okay,
cool,
okay,
separate
health
help
text
for
publishing
options.
I've
not
seen
this
one
also.
A
Okay,
great
marked
our
tvc
already
that's
fantastic.
F
H
So
it
used
to
be
that
if
you
had
like
a
three
column
layout
that
were
all
33,
you
couldn't
target
any
one
of
those
individual
regions
by
itself,
because
the
only
classes
that
were
on
there
were
the
bootstrap
classes
that
made
them
all
the
same
size.
And
so
this
allows
you
well,
it
will
take
whatever
you've
provided
as
the
region
name
and
if
you
haven't
provided
anything
it'll,
take
the
region
region
number
and
create
a
unique
class
for
each
region.
H
I
would
like
a
sanity
check
on
the
syntax
for
the
class,
because
there
was
a
little
bit
of
back
and
forth
about
that,
and
the
latest
version
was
my
recommendation,
but
I'm
not
sure
anyone
other
than
her
has
had
a
chance
to
see
it.
So
we
could
get
some
other
eyes
on
that.
H
My
thoughts
were
that
it
should
start
with
l,
because
it's
related
to
layouts
and
all
of
our
other
layout
classes
start
with
l,
but
it
would,
but
there
was
also
some
feedback
in
the
issue
that
it
should
contain
the
word
region,
so
that
people
knew
that
it
was
in
case
your
region.
Name
was
something
like.
H
I
don't
know
puppy
or
something
you
would
know,
is
region
puppy
and
not
something
else
puppy,
so
I
ended
up
doing
l
region
and
then
a
double
hyphen
and
the
region
name,
and
I
know
we
usually
use
the
double
hyphen
to
indicate
that
it
is
a
a
permutation
of
the
parent
template
theme
hook
suggestion,
and
so
I
wanted
us
to
sanity
check
on
that
or
if
we
wanted
to
convert
that
to
a
single
hyphen.
H
I
just
thought
for
legibility.
It
was
easier
that
way,
but
I
didn't
want
them,
meaning
to
be
problematic.
H
H
H
If
you
look
at
the
top
post,
I
put
the
example
syntax
in
the
original
post
at
the
top,
where
it
says
markup
for
region
before
markup
for
region.
After.
A
Yeah,
if
it
hasn't
been
raised
already
that
I
have
a
concern
here,
that
translation
always
doesn't
doesn't
always
do
a
good
job.
If
you
this,
like
region
name,
the
label
were
like
in
japanese,
for
example,
the
machine
name
would
probably
need
fixing
okay.
H
So
is
that
also
true
for
the
machine
names
in
the
layouts
that
we're
using
now,
because
that's
the
field
we're.
A
Using
so
I
think
it's
fine
that
machine
names
use
transliteration
to
try
to
make
a
reasonable
machine
name
at
the
time
that
a
label
is
created,
but
I
think
it's
important
that
they
be
able
to
be
customized
right
away
because
a
lot
of
times
in
these
non-latin
character
languages,
a
person
that
knows
english
will
use
japanese
or
chinese
as
the
label.
But
then
they'll
immediately
use
english
for
the
machine
name
and
they
don't
have
transliteration.
They
actually
use
an
english
word
for
the
machine
version
of
things.
Okay,
so.
H
A
B
H
Yeah
interesting,
okay,
I'll
write
that
comment
in
there
and
say
it's
from
you,
because
that
was
a
good
idea.
A
Okay,
yeah:
I
thought
that
that's
what
this
was
indicating,
but
that
might
have
changed
so,
okay,
we
are
out
of
time,
but
let's
see
if
we
can
get
through
the
last
four
of
them
here:
okay,
negative
visibility,
condition
for
roles.
This
looks
like
it's
probably
adding
a
like
a
yes
type
option.
D
Yep
at
some
point,
the
suggestion
was
made
that
the
negation
was
added
generally
in
every
visibility
rule,
but
we
left
that
for
a
follow-up,
so
this
is
only
for
the
specific
for
four
roles.
That's
it:
okay,
okay!
Well,
I'm.
A
Not
really
quite
sure
about
the
looks
like
this
is
the
option:
okay,
yeah
yeah,
this
this
looks
fine.
Is
it
oh
wait.
D
A
Okay,
well,
I
I,
I
trust
you
guys
on
syntax
and
terminology
generally
you're,
really
good
at
that
sort
of
thing.
So
I'll
take
a
look
at
it.
A
D
That's
the
other
part,
half
of
the
part
of
the
issue
that
you
were
discussing
before.
Oh.
A
A
A
Yeah,
I
think,
we'll
get
a
benefit
to
the
machine
name
thing
separate
from
just
the
css
stuff,
because
it's
possible
that,
like
we
might
start
making
the
machine
name
available
like
in
the
templates
or
start
using
the
machine
name
yeah.
I
see
a
lot
of
benefits
to
having
a
machine
name
for
regions,
then
not
just
the
css.
So
I
I
don't
think
that
this
this
wouldn't
replace
the
name
from
machine
names.
H
A
B
I
D
A
Looking
good,
it's
marked
works
for
me,
but
needs
code
review
one
more
layout
issue:
boy,
lots
of
layout
issues,
add
help
text
to
explain
how
ordering
group
grouping
and
that
page
works.
I'm
not
quite
sure
what
that
page
is,
but.
A
This
was
mentioned
a
year
ago.
A
So
it
would
be
very
fitting
to
get
it
corrected
to
get
it
corrected
now.
So
yes,
this.
D
D
H
So
I
just
added
the
milestone
for
this
because
I'd
love
to
see
it
get
in
I'm
doing
some
testing
on
the
sandbox
right
now,
but
it
will
be
good
to
have
core
committer
feedback
on
whether
this
is
suitable
for
inclusion
in
121.
H
A
A
A
Got
the
bump
but
yeah
there's
a
lot
of
rtbc's
I've
been
going
through
this
week.
I
merged
a
couple
of
these
and
I'm
hoping
to
to
get
through
a
lot
more
of
them.
Oh.
H
Yeah,
I
have
a
question
I
forgot
on
the
css
automatic
css
class.
If
all
we're
doing
is
adding
a
css
class,
I
was
wondering
if
that
would
be
suitable
for
120
instead
of
121..
H
A
Right,
yeah
and-
and
I
I
would
not
want
us
to
do
the
automatic
machine
name
because
then
we
would
need
to
support
that
somehow
moving
forward
like
that,
that
makes
that
makes
it
so
it
gets
more
complicated
to
add
machine
name
later.
If
you
needed
to
remove
the
automatic
one
and
put
in
the
manual
one,
then
you
need
to
do
some
work.
There.
A
If
we
made
an
automatic
machine
name
right
now
and
by
machine
name,
you
mean
css
class,
yeah,
sorry
yeah
an
automatic
css
class.
Now
then,
when
we
support
the
manual
machine
name
later,
we
would
still
have
to
support
the
automatic
class
we've
made
before
yeah
exactly
so.
It
would
definitely
be
preferable
to
just
jump
right
to
the
customizable
rather
than
using
the
automatic.
A
Okay,
all
right,
we
are
out
of
time,
but
I'll.
Let
anybody
if
they
have
any
questions
or
other
things.
I'd
like
to
look
at
before
we
close
the
the
issue.
D
D
I'm
gonna
try
and
be
available
on
sunday,
yeah
saying
here
or
throughout
the
weekend:
yeah,
it's
actually
a
public
holiday
on
monday
and
tuesday
for
australia.
So
I'm
not
working
so
I'll
be
around
to
help
with
the
feature
freeze
and
moving
things
around.
If
we
do
that
really.
A
What
what
what
holidays
are
you
guys
having
on
those
days,
I
think.
D
Yeah
they've
moved
because
it
falls
on
a
on
a
weekend.
They
moved
it,
so
they
it's.
What's
the
bed
that
they're
using
but
observing
the
holiday
for
for
new
year's
new
year's
day
yeah
on
the
second.
D
It
was
the
same
with
christmas
and
boxing
day,
but
we
had
monday
and
tuesday
off
last
week.
A
Yeah
in
the
united
states
they're
observing
new
year's
day
on
friday
for
some
reason.
Next
friday,
this
this
friday,
like
tomorrow,
oh
okay,
which
is
kind
of
weird
I
I
would
have
thought
that
that
would
have
been
global
actually
and
now
that
I'm
hearing
that
it's
not
global,
trending
tomorrow
then
yeah
yeah.
A
D
A
I
don't
have
enough
information
to
say
that
right
now,
I
don't
think,
but
but
let's
let's,
let's
keep
people
posted,
we'll
look
into
that,
we'll
announce
it
via
twitter
and
discuss
it
in
zoolope
and
maybe
we'll
even
make
an
issue
about
what
what
date
code
freeze
should
be,
because
I
didn't
think
that
that
was
different
across
countries,
but
it
is
so.
We
need
to
figure
that
out.
A
Okay,
but
let's,
let's
still
plan
on,
I
like
the
code
sprint
on
sunday
idea,
I'm
I'm
widely
available
through
the
end
of
the
year
through
the
next
couple
of
days.
So
I'm
really
hoping
I'll
be
able
to
knock
out
all
of
these
rtbc
ones.
That
just
need
need
committed
feedback.
So
I
think
we're
in
good
shape.
I'm
very
excited
about
the
list
of
features
here.
We
may
not
have
gotten
entity
reference
in
again.
A
But
I
feel
like
there's
there's
a
serious
momentum
and
that
always
gets
me
excited
so
yeah
yeah
big
thanks
to
all
of
our
contributors
and
yeah,
we'll
have
a
busy
next
couple
of
days:
cool.