►
From YouTube: Backdrop Weekly - May 14th 2020
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
A
Before
we
get
started
on
the
agenda,
I
would
like
to
have
everybody
introduce
themselves
so
your
name
where
in
the
world
you
are
located
and
if
you
have
a
30-second
snippet,
you
would
like
us
to
know
about
that.
It
is
not
already
on
the
agenda,
feel
free
to
say
it
now
great
you're
in
my
top
left.
So
would
you
like
to
go
first
yeah.
C
D
Mccormick
I'm
in
San,
Ramon
California,
lots
of
noisy
things
happening
today,
so
I'll
be
on
mute
and
hidden
most
of
the
thing,
because
I'm
mostly
here
to
lurk
I'm
interested
in
sort
of
the
marketing
side.
Of
a
backdrop,
although
can't
do
that
competently
without
you
know,
keeping
up
on
the
technical
side
as
well
great.
E
A
All
right,
matthias
is
here,
but
it
says:
listen
only
mode
today,
so
hello
Matthias,
we
understand
you
can
introduce
yourself
but
I
believe
you're,
calling
in
from
Switzerland
all
right
name
is
John.
Lampton
I
am
also
from
Oakland
California
and
I.
I.
Don't
have
any
exciting
update
today,
but
I
have
a
dog
tada
she's
asleep,
so
there
we
go
all
right
first
thing
on
the
agenda
new
projects.
So
since
we
last
met
there's
a
new
contributed
module.
It
is
a
part
of
the
Drupal
invite
project.
C
Just
realized
I'm
looking
at
a
different
agenda
file
than
you
are
Jen,
so
I'm
gonna
be
using
my
agenda
file,
which,
if
you
could
merge
those
together,
would
be
great.
Ok,
ok,
so
backdrop,
115
is
the
current
release
and
115
2
will
be
coming
out
tomorrow,
along
with
the
116
release,
115
2,
it
will
contain
various
bug
fixes
and
we
have
2
issues
that
could
potentially
be
moved
into
one
15
2
as
well,
although,
with
the
scope
of
these
changes
they
might
get
merged
into
one
16.
C
Only
I
don't
know
it's
not
really
a
much
of
a
big
deal,
I,
don't
think
with
116
coming
out
tomorrow
as
well
anyway.
The
two
issues
that
we've
got
here,
our
PHP
7.4
support.
It's
issue
43082
review
this
week.
The
work
that
Joseph
has
done
to
make
backdrop
PHP,
7.4,
compatible
I
think
that
Joseph,
the
ball
could
be
in
your
court.
C
C
C
All
right,
let's
see
what
the
status
is
tomorrow,
if
it
doesn't
make
it
in
that's
fine,
yeah,
yeah,
I'm
a
little
nervous,
there's
a
couple
of
places
where
it's
not
quite
so
obvious
that
it's
just
a
syntax
change.
It's
like
some.
Some
things
are
possibly
having
like
a
difference
in
logic,
but
it's
it's
not
100%.
Clear
I
also
saw
it
in
several
places.
In
several
places
you
fix
bugs
that
have
been
there
forever.
I
saw
that
an
aggregator
module
I
think
it
was
that
there
was
like
we.
C
C
C
C
Another
issue
that
came
up
this
week,
Indigo's
Ella,
had
been
working
on
this
issue
that
strings
within
views
are
not
translatable
currently,
and
so
they
opened
up
an
issue
4382
and
cross
ported
the
localization
functionality
from
Drupal
7.
Back
into
your
backdrop,
I
was
a
little
bit
surprised
that
apparently
it
was
me.
Two
had
removed
localization
functionality
several
years
ago
with
the
intention
it
seems
to.
It
was
part
of
the
switch
from
storing
configuration
the
database
to
using
config
files.
C
I
think
the
intention
had
been
to
use
the
config
translation
system
once
it
was
available,
but
that
happened
only
much
more
recently
so
issue
4382.
The
current
approach
is
not
actually
using
config
translation,
but
just
reinstating
exactly
what
was
in
Drupal
7,
considering,
ultimately,
both
approaches
boiled
down
to
using
locale
module
and
the
T
function.
C
There's
really
not
that
much
difference
in
the
way
that
strings
are
stored
and
the
way
that
translators
would
actually
translate
the
content,
because
they're
both
locale
based
so
not
really
going
to
be
too
different
for
end-users
one
way
or
the
other,
so
the
status
on
that
is
that
code
has
been
our
TBC
herb.
Duel
has
taken
a
look
at
it.
Think
thanks
for
doing
that,
and
we're
basically
just
having
a
discussion
right
now
about
do.
We
need
to
do
any
further
reconciliation
between
the
two
translation
systems,
or
should
we
just
move
that
in
wholesale.
C
C
We
added
a
feature
that
there's
now
a
new
permission
for
preventing
access
to
the
layout
builder
to
edit
and
create
new,
flexible
layouts.
But
we
have
a
follow-up
issue
on
that
that
we
need
to
add
an
update
hook.
That
makes
it
so
that
it
on
a
site,
that's
upgrading,
if
you
are
not
user
number
1
and
you
previously
had
administer
layouts
that
you
maintain
the
permission
to
administer
flexible
layouts.
So
that's
this
one
Gregory
I
saw
that
you
already
filed
a
pull
request
for
that
yeah.
B
It's
just
five
lines:
yeah,
it's
just
easy,
so
I
filed
a
separate
issue,
a
follow
up
or
what
it
was
okay
yeah.
So
doctrine
would
notice
that
it
would
be
order
to
give
someone
the
flag
of
all
the
administer
flexible
templates
permission
and
not
have
access
to
the
new
state
layouts,
and
he
recommended
that
we
do
the
same
thing
that
we
do
for
administer
pages
in
the
administration.
But
when
you
take
it,
there's
a
JavaScript.
It
says
a
you
want
to
enable
that
as
well,
because
you
won't
see
anything
happen.
B
So
I
have
a
pull
request
on
my
local
for
that.
But
I
thought
that
it
would
be
better
to
be
a
follow-up,
maybe
for
116
1
as
a
task
for
something
so
I've
noticed
that
with
the
admin
bar,
what
happens?
It's
two-way
so
either
either
permission
you
tick
the
box,
for
it
asks
you
to
enable
the
other
one
I'm,
not
sure
that
we
want
to
do
the
same
with
layouts
in
flexible
templates.
I
think
it
should
be
one
way,
but
I
need
some
feedback
on
that.
B
B
And
the
other
thing
is
that,
while
I
was
working
on
that
code,
the
error
message
that
is
shown
assumes
that
anyways,
it
doesn't
make
sense
if
you
enable
the
other
permission
for
admin
bar.
So
we
need
to
fix
that.
It's
a
common
message
for
both
tick
boxes.
Both
permissions
as
you'd,
say
so
yeah,
maybe
I,
might
need
I
might
need
some
help,
we'll
see
how
it
goes
anyway.
It's
it's
a
follow
up,
so
not
to
sort
of
like
mr.
the
the
feature
that
is
going
into
116.
C
B
B
A
Might
want
other
places
like
administer
nodes
like
there's
a
bunch
of
places
where
I
think
when
we
have
that
relationship
between
like
you're
gonna
enable
this,
but
maybe
you're,
not
gonna,
give
you
what
you
think
you
want.
Maybe
you
also
on
whatever
that
could
be
a
handy
tool
we
could
use
if
we
had
it
so.
B
B
C
B
C
Yeah
at
this
point,
I
mean
I,
guess
we
could
still
have
it
completed,
but
the
follow-up
doesn't
even
have
any
code
behind
it.
Yet
your
follow-up
is
just
you
know,
display
things
like
changing
the
display
of
the
button
to
make
it
consistent
with
other
drop
buttons
throughout
backdrop
and
possibly
moving
the
enabled'
check-box
from
the
right
to
the
left.
There.
B
Was
there
was
another
thing,
I'm,
not
sure
if
it's
within
those
tweaks
or
find
those
a
separate
or
just
discussed
with?
Where
there's
some
awkwardness,
where
you
have
to
save
the
form?
You
know
that
to
see
the
importance
and
ckeditor
appear
or
disappear,
it's
not
much
of
an
issue,
but
it
might
be
a
little
bit
of
a
UX
WTF.
There
yeah
nothing,
but
you
know
be
followed
up.
C
Okay,
let's
see
another
one
deprecating
cache
clear:
all
is
the
shoot
21:58.
This
doesn't
have
anything
done
yet,
but
I
think
the
hope
is
because
it's
fairly
minimal
that
adding
the
deprecated
tag
is
something
that
could
still
be
done.
I
was
pointing
out
last
week,
though,
the
core
is
actually
still
using
cache
clear
all
in
a
couple
of
places,
and
so
it's
not
quite
just
to
add
the
deprecated
tag
and
be
done
with
it,
and
then
we
need
to
change
record
if
that
comes
to
pass
as
well.
C
C
Lastly,
entity
cache
almost
lastly
entity
cache
issue,
number
74
Joseph
for
the
change
record
for
the
entity,
cache
addition
to
core
and
the
way
that
contributes,
needs
to
implement
entity
cache
to
have
it
functioning
if
they
so
choose.
Thank
You
Joseph
for
writing
that
change
record
that
really
helped
quite
a
lot.
C
I
went
ahead
and
published
it
with
some
Changez
I
think
we
mentioned
a
couple
weeks
ago
that
there
were
three
things
they
need
to
be
done:
create
the
cash
table,
update
hook,
entity
info
and
then
possibly
change
your
storage
controller,
to
make
sure
that
you
include
the
parent
load
call,
and
so
that
third
item
was
missing,
even
though
I
hope
for
most
people.
They
won't
need
to
change
anything
because
you
should
be
doing
it
should
have
been
doing
that
anyway,
but
it's
a
pitfall
so
figured
its
best
to
mention.
F
C
C
A
A
C
Yeah
anyway,
I
think
that
if
we
give
them
a
little
extra
assistance,
we
might
build
it
turn
that
and
do
something
that
still
works,
though
it'd
also
be
good
for
posterity
for
anybody
else,
because
there
were
several
people
that
were
like
oh
yeah
I
could
use
this
kind
of
functionality
of
making
the
standard
profile
plus
one
other
things,
so
some
proof
of
concept
exhibiting.
If
that
truly
is
possible,
it's
still
be
useful.
Here
is.
B
C
B
With
the
change,
I
have
a
question
before
we
move
to
the
initiatives
with
the
change
of
moving
of
adding
the
separate
permission
for
flexible
ten
flights
earlier
on
in
that
ticket.
It
was
discussed
for
that
to
become
a
separate
module,
but
we
realized
that
we'll
be
far
easier
to
just
control
it
with
the
permission
and
then
what
we
were
discussing
about
the
JavaScript
being
used
to
enable
variable
required
permissions
is
a
side
effect
of
the
fact
that
in
the
menu
system,
the
flexible
templates
UI
is
within
the
layouts
menu.
B
So
that's
why
you
have
to
have
the
administer
layouts.
So
my
permission,
I
was
wondering
if
it
was
a
separate
module
and
people
just
decided
it
or
enabled
it.
Maybe
we
wouldn't
done
to
this
problems,
and
so
my
question
is
that
do
we
still
plan
to
move
it
to
a
separate
to
being
a
separate
module?
Is
that
what
we
want
to
do.
B
A
F
A
B
A
Mean
I'm
a
fan
of
having
lots
of
issues
but
I
know
there
are
people
who
aren't
I
think
having
something
they
look
sort
of
retains
the
conversation
we
had
there
about
like.
Maybe
this
should
be
a
separate
module
would
be
good,
but
if
we're
not
going
to
work
on
it,
we
could
do
it
at
the
point
that
we
do
work
on
it.
So
I
don't
know.
B
A
Just
gonna
make
an
announcement
because,
like
Greg's
here-
and
he
wasn't
here
so
we
just
so
people-
know
what
happened
in
Matias
this
year.
So
last
week
was
the
week
we
had
the
conversation
about
which
initiatives
we
were
going
to
propose
to
the
PNC
for
a
vote,
and
we
looked
at
what
was
in
the
forum
and
there
were
sort
of
of
the
people
on
the
call
everybody
there
and
decided
that
telemetry
was
important.
So
that
was
a
priority
we'd
like
to
put
that
one
up
to
the
PMC.
A
And
then
there
was
this
other
issue
that
our
proposals
that
Luke
had
originally
created
as
putting
more
themes
in
core
and
has
sort
of
been
refactored
to
be
something
larger
than
that
which
is
to
make
it
easier
for
people
who
don't
have
the
ability
to
write,
HTML
and
CSS
to
build
and
launch
a
backdrop
site
and
I.
Don't
know
if
that
what
the
current
status
of
the
issue
is
I
think
the
plan
was
to
update
it
or
the
forum
post
after
the
last
meeting.
A
B
Thing
sorry,
I
wasn't
I
missed
those
meetings.
One
thing
that
I
wanted
to
propose
and
it's
been
long-standing
is
there's
two
things.
One
of
them
is
the
mate,
the
other
one
is
sort
of
like
it
was
meant
to
be
a
helper
issue
for
the
other
is
about
finalizing
and
deciding
which
module
we're
going
to
use
for
references
and
add
it
to
the
poor.
I
know
that
Mike
a
couple
of
years
ago
did
a
lot
of
work
at
some
point.
He
hit
some
roadblocks.
A
B
B
A
B
A
We
have
pinned
projects
and
we
currently
have
save
as
draft
pinned
but
I
think
after
all
of
our
recent
discussions
about
future
revisions,
maybe
we
should
revisit
that
and
and
I
don't
know
whether
that's
still
a
candidate
fork
or
not,
or
if
it's
a
new
priority
for
a
candidate
for
core
or
if
it
needs
to
be
modified
based
on
all
of
our
conversations,
but
I
saw
that
there
and
I'm
like
is
this
so
pleasing,
so
just
food
for
thought.
No
answers
yet.
B
A
So
four
initiatives:
next
steps
are
creating
a
shape
for
the
PNC.
Let
them
discuss
for
two
weeks
and
vote
and
then
we'll
we
come
back
to
this
meeting
with
and
maybe
a
blog
post
would
be
nice
with
the
decided
on
initiatives.
Their
initiative
leads,
and
maybe
a
summary
of
what
we'd
like
this
to
be,
maybe
a
blog
post
from
each
initiative.
We
don't
each
one
I,
don't
know
we'll
see.
A
Alright
general
discussion
open
QA
period,
anything
on
the
agenda.
People
would
like
to
talk
about.
A
Okay,
well,
we
have
eight
minutes
left
I!
Guess
we
can
give
you
all
your
eight
minutes
back.
Thank
you
guys
for
coming
and
participating
in
the
meeting
good
to
see
you
Greg
I'm,
glad
to
see
everything
is
okay
and
that
your
children
are
still
running
around
distracting
you.
So
let's
go
George.