►
From YouTube: Backdrop Meetings - May 27, 2021
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).
B
Hey
folks,
it
is
may
27
2021,
and
this
is
the
weekly
backdrop
developer
meeting
we
get
together
every
week
and
talk
about
the
latest
pressing
needs
from
the
development
side
of
the
backdrop.
Cms
project
plus
also
touch
on
other
things
that
our
development
really
did.
B
We
will
go
ahead
and
start
with
some
introductions
of
those
present.
My
name
is
nate
lampton.
I
live
in
oakland
california.
I
am
quick
sketch
on
the.
B
And
yeah
we
have
some
exciting
well
some
some
developments
that
have
been
happening
this
past
week
that
we're
going
to
get
into
let's
go
to
robert.
Could
you
introduce
yourself.
D
E
B
A
I'm
tim
erickson,
st
paul
tim
on
the
internet,
I'm
in
deerwood
minnesota
and
I
have
been
mostly
lately
really
busy
with
work
and
a
lot
of
or
the
backdrop
time
is
mostly
spent
on
administrative
stuff,
organizing
stuff
and
getting
ready
now
we'll
be
getting
ready
for
backdrop
live
now.
Robert
did
you
you
already
introduced
yourself.
A
A
D
B
Net
says
from
greece:
sometimes
australia
knows
clonos
on
the
internet.
D
B
So,
let's
see
we
will
go
through
announcements
from
the
pmc.
I
don't
think
that
we
have
announcements
for
this
week.
New
contributed
modules,
it's
exciting
that
we
have
one
new
contrib
module
view
summarize
that
was
released
this
past
week.
Thank
you,
jason
flatt
for
porting
that
new
module
and
we
can
go
right
into
the
core
status
updates.
B
We've
been
discussing
a
little
bit
before
this
meeting
and
there's
been
some
discussions
in
the
pmcq
and
some
other
community
places
about
restructuring
what
we
do
with
these
meetings,
possibly
turning
them
into
more
of
a
working
session
where
people
can
bring
in
ideas
or
issues
that
it
is
that
they
want
to
discuss,
and
then
we
can
try
to
work
through
them
live
that
would
result
in
a
lot
less
a
lot
less
structure
and
a
lot
less
unpredictability
but
possible,
possibly
also
make
it
like
more
incentivizing
for
people
to
show
up
if
they
felt
that
they
could
get
help
or
opinions
on
issues
during
these
calls,
rather
than
the
majority
of
the
meeting
being
taken
up
by
things
like
the
progress
report,
where
we
go
through
the
same
issues
every
week.
B
B
While
we
kind
of
sort
out
what
that
new
format
might
potentially
look
like
so
kind
of
on
the
horizon.
Some
changes
might
be
coming
to
this
to
this
meeting.
The
way
that
we
organize
it
also
related
at
the
beginning
of
every
release
cycle.
We
usually
have
some
kind
of
planning
meeting
where
we
take
this
meeting
time
and
we
use
it
to
solicit
ideas
from
the
whole
community.
Saying
hey.
B
What
is
it
that
people
are
interested
in
working
on
kind
of
talk
about
what
we
think
is
feasible,
where
momentum
is
and
then
we
can't
really
force
any
issue
to
be
like
a
priority,
because
we
need
people
to
work
on
it,
but
what
we
can
do
is
kind
of
incentivize
and
encourage
people
to
work
on
particular
issues.
So
our
plan
is
that
that
meeting
for
discussing
like
priority
features
for
the
next
version,
which
would
be
1.20,
will
probably
be
during
next
week's
meeting
at
this
time
so
june
3rd.
B
At
this
time,
we'll
be
doing
kind
of
the
the
planning
meeting
for
1.20
as
prioritizations,
maybe
after
that,
we'll
also
move
towards
this
newer,
like
bring
your
ideas
format
to
the
meetings
as
well.
So
some
changes
on
the
horizon
next
week
will
definitely
be
different
and
then
the
one
after
that
we'll
see
like
if
we,
if
we
shake
up
the
whole
format
entirely,
we
might
have
a
new
agenda
template
that
we
work
from.
B
Instead,
I
think
I
summarized
that
tim
and
greg
you
two
have
also
been
privy
to
that
discussion,
about
changing
up
the
format
and
also
planning
meetings.
You
guys
are
familiar
with
how
they've
worked
in
the
past.
Do
you
guys
have
anything
you'd
like
to
add.
A
I
don't
think
so
I
mean
I,
I
think
you
you
may
basically
described
it
the
way.
I
understand
the
current
proposal
and
we
could
still
discuss
it
more.
Is
that
basically,
instead
of
listing
all
of
the
the
milestone
projects,
whether
or
not
there's
been
any
update
is
that
to
sort
of
get
on
the
agenda
either
a
core
committer
would
need
to
be.
A
You
know
someone
would
flag
them
with
an
issue
and
they
would
sort
of
be
ready
to
talk
about
it
at
the
meeting
or
anyone
else
could
show
up
at
the
meeting
and
be
able
to
talk
about
it,
but
that
we
avoid
talking
about
issues
where
there's
no
update
or
there's.
No,
you
know
nobody
there
with
any.
You
know
that's
prepared
to
talk
about
it,
so
that's
kind
of
how
I
understand
the
proposal,
if
I'm
misunderstanding
that
please
somebody
let
me
know.
F
That's
how
I
understand
it
as
well,
more
or
less
it's
trying,
at
least
with
the
the
next
milestone,
the
minor
milestone,
try
to
get
certain
things
done,
rather
than
you
know,
discuss
current
status
or
where
it's
blocked.
Actually,
if
there
is
a
blocker
try
to
see
if
we
can
sort
it
out
during
that
session,
it
sort
of
becomes
like
a
very
limited
mini
code
screen,
I
should
say,
or
some
code
review
streams.
B
One
one
concern
I
have
is
how
we
could
prepare
for
those
meetings
like
if,
if
people
are
coming
in
with
the
ideas-
and
they
haven't
told
anyone
about
it
prior
to
the
meeting-
then
it
it
might
not
be
very
productive
if
we
spend
the
whole
meeting
describing
what
the
problem
is
without
any
background,
because
sometimes
these
issues
take,
you
know
10
or
15
minutes
to
get
enough
background
to
actually
provide
any
valuable
input.
B
But
on
the
other
hand,
sometimes
issues
are
so
complicated
that
they
have
to
be
described
verbally.
So
it
could
see
a
benefit
there
as
well,
but
the
agendas
they're
a
little
bit
locked
down
and
I
think
a
lot
of
people
don't
know
where
they
live.
B
You
know
like
asking
people
to
add
stuff
to
the
agenda
document.
I
don't
think
has
been
super
successful.
I
think
we
might
need
a
different
way
to
flag
issues
for
these
weekly
discussions.
If
we're
going
to
start
changing
them
up
frequently-
and
I
don't
quite
know
what
that
would
be,
it
could
be
like
a
submission
system
where
it's
like
you,
you
fill
out
some
form
somewhere.
It
could
be
a
channel
in
zulip
that
also
could
be
a
little
bit
obscure
for
some
people.
It
could
be
a
tag
on
the
issues.
You
know
something.
F
Like
that,
we
already
have
a
tag
that
we
kind
of
use
for
the
design
meetings
and
it's
just
design,
but
that
applies
only
to
the
core
http,
I'm
not
sure
if
they
have
the
same
tag
and
how
we
can
aggregate
those
tags
across.
Okay.
F
But
having
said
that,
this
is
about
the
the
core
project,
so
it
would
most
likely
involve
core
and
maybe
the
main
side.
Another
thought
that
I
had
is
yes,
we
can
get
lengthy,
like
the
discussion
could
get
lengthy,
but
we
can
spend
five
or
ten
minutes
at
the
beginning
of
the
session
to
sort
of
like
list
the
issues
and
prioritize
them
and
say
we're
gonna
go
through
them.
F
B
Yeah
I
like
that
idea,
a
little
pre-meeting
prioritization.
B
In
the
issue
queue
if
we
would
like.
B
Wipe
out
the
tag
every
time
in
between
meetings,
so
it's
like
putting
the
tag
on
something
means
you're
going
to
show
up
to
the
meeting
to
discuss
it,
and
it's
like
and
after
every
week
we're
going
to
wipe
out
the
tag
and
it's
like.
If
you
want
to
discuss
it
next
meeting,
you
got
to
tag
it
again
and
that
way
that
would
give
us
a
really
fresh
cycle
of.
Like
you
know,
hey.
We
have
new
stuff
to
talk
about
every
week
and
we
also
have
some
kind
of
idea
of
you
know.
B
B
F
B
C
B
All
right
well
we'll
go
through
the
normal
updates,
then,
for
now
we
don't
actually
have
a
whole
lot
of
time
today
to
go
over
it,
so
this
could
actually
end
up
being
fairly
short,
so
but
yeah,
let's
do
the
normal
core
update
for
now.
So
119
is
the
bug
fix,
release
that
just
came
out
yesterday,
so
you
guys
haven't
been
paying
attention
fully
to
what's
happened
in
the
core
sphere.
B
Is
that
both
triple
seven
and
eight
and
nine
released
new
versions
of
core
yesterday?
That
included
just
an
updated
version
of
ck
editor
module
that
there
was
a
third
party
vulnerability
in
ck,
editor
module
and
then
all
of
the
projects,
including
us
that
depend
upon
ck,
editor
4
all
went
through
and
updated
to
the
newest
version.
C
F
Yeah
drop
seven,
the
respective
there's
a
an
issue
in
the
respective
contrib
module,
where
they're
discussing
allowing
support
because
they
were
having
issues
with
previous
versions
as
well
for
15,
I
think
or
414
and
now
they're
working
towards
allowing
allowing
the
new
one
sorry
for
16.1
to
run
smoothly.
So
ongoing
discussion
still
in
the
seventh
grade.
B
Yeah
for
us
that
did
bump
us
up
a
couple
of
versions.
I
think
that
we
were
a
few
versions
behind,
so
we
went
from
trying
to
remember
about
something
I
had
414,
I
think,
to
416
one,
and
so
that
did
jump
us
up
a
couple
of
numbers.
We
did
some
checking.
B
You
know
to
make
sure
that
we
didn't
think
that
there
was
any
issues,
but
the
security
update
yesterday
honestly
was
really
hectic,
because
there
was
a
lot
of
confusion
about
what
was
happening
because
seek
editor
didn't
actually
specify
that
it
was
a
security
update
and
said.
The
drupal
community
thought
that
it
like
believed
strongly
that
it
was
a
security
update.
B
Even
though
canada
didn't
say
it
was
a
security
update,
and
then
there
was
a
lot
of
like
fluffing
around
about
like
getting
a
cve
and
like
is
this
actually
gonna
come
out
today
or
not,
and
so
so.
The
whole
thing
was
a
little
bit
hectic
and
we
apologize
for
kind
of
getting
that
out
late
in
the
day
and
making
that
a
big
big
rush.
But
we
didn't
and
we
didn't
get
it.
We
didn't
really
see
it
coming
because
it
was
all
such
a
hectic
thing.
D
A
Comment
is
important
because
I
think
people
like
me
associate
backdrop:
security
updates
with
drupal
7
security
updates,
so
it
was
confusing
that
drupal
7
wasn't
being
updated,
but
backdrop
was-
and
my
understanding
is-
that
is
because,
like
drupal
8,
we
brought
a
ct
editor
into
core
where
drupal
7
doesn't
have
ck
editor
in
core.
So
if
anybody's
confused
about
why
drupal
7
was
updated,
that's
my
understanding
or
it
wasn't
updated
and
we
were.
F
Yeah
and
it's
the
same
situation
when
we,
when
there's
security,
updates
for
the
d7
version
of
contrib
modules
that
we
have
included
in
port
so
that
so
so
in
triple
land,
it
might
be
a
d7
contribution
security
update,
whereas
in
microplanet
it
might
be
a
poor
update.
My
so
so.
The
only
concern
that
I
have
is
that
the
because
we
work
closely
with
the
triple
security
team.
Are
they
aware
that
syndicated
is
part
of
that
was
my
my
consensus?
F
They
were
there,
they
considered
backdropping
d7,
so
they
didn't
include
lupus
team
to
the
whole
thing.
So
what
happened
was
usually
report
made
and
make
the
releases
about
the
same
time.
But
this
time
we
had
to
wait
for
that
release
to
come
out,
and
then
we
were
looked
into
we
weren't
looked
in.
Actually
we
we
discovered
that
it
also
affected
us.
F
I'm
not
sure
what
we
can
do
towards
that.
I'm
not
sure
how
the
drawful
security
team
operates
and
who
makes
the
decisions
to
lucasian,
but
I
would
say
that,
and
then
someone
else
mentioned
that
in
the
two
I
think
it
was
peter.
I
think
that
it's
better
if
they
loop
us
in
to
everything
and
they
would
say
we
make
the
decision
of
yeah.
This
doesn't
concerns
us
and
then
we
get
removed
from
the
two.
If
that's
a
possibility
or
an
option.
B
Yeah,
I
think
that
we've
been
working
towards
that
that
jen
is
officially
a
provisional
security
team
member.
B
I
am
a
as
needed
added
to
issues,
so
I'm
not
a
security
team
member,
but
I
get
added
to
issues
super
frequently
and
I
think
jen
being
moved
from
provisional
to
full
security
team
member
would
help
with
that,
because
then
that
would
make
it
so
she
just
has
access
to
everything
which
of
course,
there's
a
bigger
level
of
trust
there,
because
there
are
hundreds
of
security
issues
for
everything
you
know
contrib
projects
and-
and
everything
like
that,
but
she's
been
working
towards
that
for
over
a
year
now.
B
So
I
think
that
it's
probably
like,
if
we
were
to
re-request
that
I
think
that
she
probably
has
been
putting
in
the
effort
necessary
to
fulfill
that
requirement.
F
B
Yeah
exactly
yeah
that
this,
this
sort
of
thing
might
have
been
avoided,
or
at
least
the
fault
would
be
on
us:
yeah,
yeah,
okay,
yeah
anyway,
so
119.1
came
out
just
yesterday.
That
was
the
only
change
in
the
whole
release.
It
was
just
the
update
to
ck
editor.
There
is
a
big
regression
that
we're
trying
to
work
through
that
was
included
in
the
119
release
related
to
backup
and
migrate
module.
B
Some
of
the
work
that
we've
been
doing
for
php8
support
required
that
we
change
an
api
in
the
database,
abstraction
layer
and
backup
and
migrate.
Doing
a
lot
of
direct
sql
queries
used
an
underlying
api
that
is
now
no
longer
functioning,
and
so
that
issue
that
we're
tracking
in
core
is
50.
94.
B
tim.
You
had
said
that
there
was
something
about.
There
was
a
new
release
of
backup
and
migrate
that
halfway
solve
the
problem.
Can
you
recap
again
what
works
and
what
doesn't
in
backup
and
migrate?.
A
Sure
so
initially
what
people
noticed
when,
after
the
release
of
1.19,
was
that
when
they
tried
to
do
a
well
actually
it
just
kind
of
broke
the
site,
my
recollection,
is,
you
didn't
even
have
to
try
and
use
backup
and
migrate.
Other,
I
think
personally,
I
tried
to
install
a
module
and
the
whole
site
broke
so
backup
and
migrate
quickly,
fixed
that
so
now
it
doesn't
sort
of
break
your
whole
site.
But
if
you
do
a
backup
with
backup
and
migrate
and
then
you
try
to
restore
it,
it
doesn't
work.
A
You
get
a
database
error,
so
you
can
from
the
command
line
you
can
up.
You
can
use
your
back
the
backup
you
made
from
backup
and
migrate
and
install
it,
but
you
can't
do
a
restore
through
the
ui
at
least
that's
my
experience
and
we've
had
at
least
a
couple
of
other
users
report
that-
and
I
don't
know
as
far
as
I
know,
there
aren't
any
other
side
effects.
A
You
know
unless
you're
trying
to
restore
from
backup
and
migrate,
but
it-
and
you
know
the
other
thing
I'll
just
point
out
in
the
context
of
this
conversation-
is
that
backup
and
migrate
is
the
most
installed
backdrop,
contrib
module
so
and
it's
and
it's
really
not
very
functional
if
you
can
back
up
but
not
restore
it.
So.
B
Okay
yeah,
it
looks
like
last
we
heard
from
the
maintainer
backup
my
great
quackers
ate
me.
B
Was
about
a
week
ago
and
he
suggested
a
pass
through-
that
would
make
it
so
that
the
old
api
would
continue
to
work.
I'm
not
sure
that
we'll
want
to
do
that.
That's
interesting!
I
I
think
that
yeah,
it
does
appear
that
we
definitely
need
a
core
adjustment
here.
It
looks.
I
have.
B
Idea
of
what
it
is
that
we
need,
I
think
I
I
don't
think
that
the
drupal
7
approach
is
something
that
we
necessarily
want
to
do,
but
we
can
come
up
with
something
that
will
work,
but
it
will
require
a
new
release
of
back
migrate
as
well.
D
A
A
So
what
is,
will
you
will
you
describe
that
in
the
in
the
issue
or.
F
Okay,
in
the
context
of
that
discussion,
and
as
tim
mentioned,
it's
the
most
frequently
used
the
most
popular
module
in
blackboard
plans.
There's
also
a
four
queue
where
we
sort
of
like
considering
to
bring
certain,
if
not
all,
of
the
features
of
the
backup
module,
at
least
the
backups
portion
when
we
perform
updates.
So
I
was
wondering
if
moving
some
sort
of
functionality
from
backup
and
migrate
into
four
would
still
make
it
the
most
popular
module
where
people
are
basically
using
it
in
order
to
back
up
before
they
upgrade.
F
B
E
B
I
think
that's
that's
a
it's
such
a
like.
A
a
long-term
like
pie
and
sky
type
idea
that,
like
we've,
got
our
immediate
concern
in
front
of
us.
That
seems
like
we
need
to
get
that
that
solved.
F
A
So,
okay,
my
understanding
is
that
again
after
so
what
happened
was
if
you
updated
to
tobacco
backdrop
1.19,
and
you.
D
A
A
That
was
the
main
problem
which
which
was
really
breaking
everything
and
and
then
shortly
after
people
realized
okay.
Well,
it
isn't
breaking
my
whole
site,
but
we're
still
having
problems
with
this
restore
feature
so
that
in
in
the
you
know,
both
problems
were
related.
So
I
think
it
was
a
partial
fix
to
just
get
sites
working
because
I
you
know
I
literally
you
know.
I
had
a
site
that
I
had
upgraded
to
1.19
and
then
I
tried
to
enable
another
module
and
my
whole
site
was
broke.
It
was
down.
A
Well,
yeah,
I
don't
I
actually,
I
think
by
that
time
I
realized
that
there
was
an
update
about
available,
so
I
didn't
uninstall
it
I
just
updated
it,
but
but
yeah
it
was
completely
breaking
sites
at
first.
So
so
I'd
just
like
to
stress
that
anybody
listening
to
this
meeting
make
sure
people
understand
that
if
you
upgrade
to
1.19,
you
have
to
upgrade
back
up
and
migrate.
B
Yeah
and
all
of
this
stems
from
php8
support,
which
is
kind
of
a
non-optional
thing.
You
know
we.
D
B
Php
eight-
and
this
was
a
certainty-
that
the
way
that
the
database
obstruction
layer
had
been
written,
it
was
doing
something
that
is
no
longer
allowed
in
php
eight,
so
some
restructuring
was
absolutely
necessary.
We
have
an
issue
tracking
further
php
eight
support
in
issue
5076.
B
backdrop:
119
is
not
100
compatible
with
php
8,
but
it's
pretty
close.
We
expect
day-to-day
functionality
to
work
just
fine,
but
if
you
try
to
run
the
full
test
suite
against
php
8
right
now
we
have
a
dozen
or
so
test
failures
of
certain
situations
and
so
issue.
50
76
is
the
tracking
issue
for
continued
fixes
to
php
eight
support
and
yeah.
We
still
have
a
lot
of
work
there
to
go.
B
B
Do
you
know,
what
can
you
can
you
d
acronym
at
flock?
What
floc
means.
D
F
I'm
not
I'm
not
a
native
english
speaker
and
it's
the
first
time
that
I
had
that
word,
but
yeah
anyways
I
had
to
google
it
out,
I'm
not
sure
if
google
provided
the
right
information
because
of
that,
but
yeah
anyways.
So
this
was
brought
out
at
the
same
time
the
d9
and
d7
had
commits
that
was
actually
fixing
that
or
at
least
providing
the
the
header
to
block
that
and
at
the
same
time
there
was
a
question
on
the
forum.
So
this
is
what
actually
triggered
it.
F
I
saw
the
the
monthly
or
weekly
newsletter
from
drupal
and
at
the
same
time
I
saw
that
I
noticed
that
there
was
a
a
post
on
the
forum
about
passion,
asking
what
backdrop,
what
the
stance
of
black
drop
as
a
product
and
as
a
community.
What's
what
are
we
doing
with
regards
to
that
reading
through
the
issue?
I
discovered
that
the
this
thing
this
feature
as
as
google
calls
it
was
introduced
in
from
version
89,
which
was
released
back
in
march.
F
B
So
without
so
this,
the
fix
here
is
that
we
add
an
http
header
to
the
responses
that
come
out
of
backdrop
pages
and
my
understanding
is
that
it
makes
it
so
that,
if
you're
using
google,
chrome,
chrome
doesn't
silently
like
read
the
page
that
you're
looking
at
and
then
build
an
advertising
profile.
Based
on
the
page
that
you're
visiting,
which.
F
B
Which,
rather,
oddly,
is
on
the
onus
of
the
site
owners,
not
the
visitors,
to
establish
whether
or
not
you
should
be
included
or
excluded
from
this
tracking
ability.
F
B
Yep
yep
and
the
fix
looks
pretty
straightforward:
it's
overrideable,
via
settings.php
or
via
the
config
file,
it's
very
similar
to
some
other
headers
that
we
selectively
turn
on
and
off,
based
on
certain
properties.
So
I
think,
like
the
x
frame
options,
or
something
like
that
is,
is
very
similar
in
the
way
that
it
turns
on
and
off
so
that
issue
5103
currently
needs
review.
B
I
think
yeah
it
looks
like
it
needs
review
and
you
already
hopefully
wrote
up
a
change
record
for
that
gregory.
Thank
you.
F
So
the
cool
request
is
basically
mirroring
what
happened
in
d7,
so
it's
a
cross
port.
The
only
difference
is
the
update
hook
that
converts
the
variable
into
config
for
us
and
the
difference
that
we
have
in
the
test
that
we
have
to
specifically
add
the
block
with
the
information
in
the
test.info
file.
There
was
an
issue
that
I
discovered,
which
I
I
reported
back
to
the
d74
maintainer
and
he
followed
up
with
a
fix.
F
His
follow-up,
full
request
is
also
included
the
things
the
consolidated
best
thing
was
included
in
output
requests,
so
we
excluding
the
test.info
file
chains
and
the
book
and
whatever
is
drupal.
Something
is
not
embedded
in
backup
something.
The
pull
request
is
101
with
whatever
is
in
d7.
C
B
There's
that
issue
it's
very
near
completion
we
think
so
far,
there's
also
been
absolutely
no
opposition
to
putting
it
in
I'd,
be
curious
to
hear
if
there
is
any
good
reason
not
to
put
it
in
because
right
now
it
just
seems
obvious
and
rather
annoying
that
people
are
needing
to
do
this
in
the
first
place,
so
yeah
any
opposition.
I'd
be
really
curious
to
hear
a
good
reason
as
to
why
we
shouldn't
do
that.
F
Yeah
there
is
a
in
the
case
where
we
need
to
allow
site
owners
to
do
it,
a
non-technical
people
to
enable
it
or
disable
it
providing
an
option
in
the
user
interface.
But
we
have
a
dedicated
issue
for
that,
but
there's
a
an
issue
in
core:
where
we're
examining
a
dedicated
security
section
in
our
configuration
ui
and
maybe
eventually
in
the
future,
we
can
add
a
checkbox
for
it,
we'll
see
so
I've
added
an
item
in
that
meta
and
we
can
discuss
it
at
a
later
time.
B
Yeah
that'd
be
really
fascinating,
like
security
and
privacy,
section
yeah.
That
would
be
interesting
it
because
everything
we
we
try
to
make
everything
secure
and
private
out
of
the
box.
But
then,
if
that
page
was
like,
if
you
want
to
loosen
your
privacy
settings,
then
then
you
could
have
an
interface
for
that.
F
Yeah
we've
been
discussing
that
for
a
couple
of
years.
That
issue
is
things
like
the
hardening
of
passwords,
which
we
apparently
have
it
sort
of
like
cardboarded,
and
then
we
are
looking
to
introduce
telemetry.
So
we
want
to
provide
people
with
options
so
having
a
dedicated
security
or
privacy
section
makes
sense.
It
would
be
a
nice
feature,
but
it's
a
feature
request.
B
Okay,
yeah
so
also
sort
of
related
and
and
an
issue
that
is
getting
some
traction
in
the
119.2
issue.
Queue
is
drupal,
7
cross
ports.
We
have
one
more
issue
that
includes
triple
7.70
through
7.75
at
issue:
50
91,
that
is
accumulating,
pull
requests
there
to
to
finish
some
crossboards
from
the
latest
version
of
drupal
7.
B
All
right,
that's
all
I
have
for
the
119.2
milestone.
If
there
are
other
bug
fixes,
you
guys
would
like
to
discuss
for
now.
B
The
policies
that
you
added
to
the
agenda
in
the
future
we'll
decide
kind
of
you
know
how
we
can
accrue
other
issues
that
you
guys
would
like
to
discuss.
There
are
a
lot
of
issues
in
the
119
to
milestone,
however,
there's
77
of
them,
so
those
are
all
issues
that
are
of
note
or
a
priority
for
the
time
being.
B
That
can
use
mostly
review.
Quite
honestly,
that
seems
to
still
be
our
main
bottleneck
for
1.20
1.20
will
be
the
next
version
of
backdrop
that
will
be
coming
out
september,
15th
2021,
and
we
don't
have
a
lot
of
items
slated
for
1.20
at
this
point
in
time
we
have
the
items
that
just
carried
over
from
119
but
I'll
run
over
a
couple
of
those
real
quickly.
B
The
exposed
file
name
filter
for
the
media
library,
dialog
issue
3293
just
simply
wants
to
make
it
so
that
we
can
expose
a
views,
exposed
filter
to
the
media
library
dialog.
We
have
a
an
issue
there.
That's
the
nested
form
tags
causes
it
to
break
and
so
issue.
3293
still,
I
think,
needs
some
technical
expertise
as
to
how
we
can.
F
Well,
so
so
even
there's
a
zulip
actually
dedicated
to
where
lauren
has
posted
a
video,
so
he
sorted
out
most
of
the
things
and
how
this
works
now
is
when
you
start
typing
on
the
the
file
selection.
The
path
sort
of
like
provides
autocomplete
most
recent
files
added,
and
it
also
at
the
same
time
filters
the
view
so
there's
a
screencast
of
how
that
works.
Currently,
so
he
seems
to
have
sorted
out
two
issues.
F
F
Great,
it
seems
to
be
working
functionality
wise,
it
seems
to
be
working
so
the
filtering
and
the
autocomplete
providing
the
most
recent
files.
This
works
as
expected.
It
might
be
a
bit
odd
that
you
have
two
input
fields
for
the
same
or
similar
functionality,
side
by
side
that,
at
the
same
time,
sort
of
like
whole
work
together.
So
whatever
is
typed
in
one
field
is
automatically
typed
on
the
other
and
the
list
is
being
filtered.
F
B
Then
they
might
also
do
that,
and
I
want
I'm
curious
if
this
solves
all
of
our
problems
or
if
it
only
works
for
file
names,
because
we're
we're
building
in
special
treatment
for
file
names,
which
is
by
far
the
most
helpful
filter,
and
this
this
may
be
one
of
those
things
where
it's
like.
We
say,
oh,
that's
obvious,
like
80
situation,
and
so
maybe
we
should
go
with
this,
even
if
it's
not
comprehensive,
but
it
would.
B
I
don't
want
to
get
us
into
a
situation
where
it's
like
we're,
making
things
difficult
for
ourselves
later.
If
they
want
to
add,
you
know
other
filters
to
the
view.
F
B
Yeah,
but
this
is
really
interesting-
it
looks
like
lauren
was
the
one
that
it's
interesting,
that
he
made
a
new
issue
for
it.
It's
issue
5102,
and
I
think
that
perhaps
just
because
it
kind
of
goes
in
a
slightly
different
direction,
that
it
was
a
good
idea
for
him
to
to
split
it
off,
but
this
could
be
a
completely
different
way
of
solving
the
main
problem,
which
is
adding
that
filter
interesting,
okay.
Well,
I
will
try
to
take
a
look
at
that.
That's
very
exciting.
B
Okay,
let's
see
other
issues,
we
have
this
advanced
caching
functionality,
adding
cache
tags
issue
4127
that
is
currently
needing
review.
Joseph
was
in
this
meeting
earlier,
but
is
has
dropped
out.
He's
expressed
a
little
bit
of.
B
Frustration,
I
guess
on
on
getting
that
issue
finished,
not
necessarily
on
the
review
side,
but
just
that
it's
it's
a
complex
problem
like
that.
The
whole
problem
is
frustrating
so
unclear
if
he'll
continue
picking
that
up
for
or
continue
with
that
for
the
next
release.
But
it's
there,
let's
see,
I
think,
we'll
skip
down
to
robert
the
issue
that
you've
advocated
for
the
decoupling
node
preview
from
layout
module
issue.
B
5067..
Are
there
any
updates
this
week.
D
B
Okay,
thank
you
thanks
robert
for
that
really
appreciate
it.
B
Okay
and
I
guess
that's
that's
kind
of
it
for
1.20
at
this
point
in
time,
we
do
have,
as
I
said
earlier,
kind
of
the
planning
meeting
for
next
week.
That
usually
ends
up
with
creating
a
few
new
advocates
for
particular
issues.
B
There's
no
real
need
to
delay,
though,
if,
if
you're
interested
in
becoming
an
advocate
for
a
particular
issue,
add
milestone
candidate
minor
to
any
issue
and
then
add
your
own
name
as
an
advocate
up
to
the
top
of
the
issue
summary
and
then
we'll
start
talking
about
those
issues.
Well,
I
guess
maybe
we
won't
talk
about
it
every
week
after
this,
but
but
still
getting
into
the
1.20
milestone.
The
only
thing
that
really
is
necessary
is
that
we
have
an
advocate
for
the
issue,
someone
that
will
kind
of.
B
Okay
initiatives.
The
only
initiative
we
have
active
right
now
is
telemetry,
which
is
like
tracking
the
way
that
people
are
using
their
backdrop,
sites
and
kind
of
returning
that
data
back
to
backdrop
cms.org
tim's
shaking
his
head,
because
I
think
he's
feeling
guilty,
but
there's
no
need
for
that
tim.
B
I
think
that
we
should
still
just
mention
that
that
that
initiative
is
still
ongoing,
even
if
there
haven't
been
any
updates
recently.
F
B
Okay,
that's
it
for
the
discussion
items
today.
Do
you
guys
have
anything
else
you
would
like
to
discuss
in
the
next
couple
of
minutes
before
we
close.
F
F
F
Yeah
I'll
work
on
that
because
it
needs
more
work,
but
it's
99
close
to
finish
that
18,
which
is
basically
adding
a
report
page
that
lists
all
parts
where
files
are
being
uploaded
on
the
site.
It's
basically
just
adding
a
report
page.
B
It's
like
a
usage
page
like
where
files
are
used.
Is
that
what
it
is.
F
Yeah,
so
it
basically
lists
all
the
paths
that
have
been
configured
either
in
image
and
file
fields
for
respective
what
you
call
it
text
filters
text
formats
where
they
say
the
files.
So
you
have
an
overview
of
all
the
the
the
platforms
yeah.
So.
B
40
45
85
that
issue
that
yeah.
F
My
only
broker
at
the
moment,
not
blocker.
I
need
to
find
pretty
names
for
the
entity
types
because
I
don't
want
to
call
things
nodes
or
taxonomy
terms
when
they're.
So
I
need
to
predefine
that,
but
I
need
before
I
do
that
which
is
tweaking.
I
need
feedback
on
anything
major
like
anything
that
should
be
out
of
there.
B
Yeah,
it's
something
that
probably
I
haven't
looked
at
it
yet
so
forgive
me
if
it
already
is
it's
probably
something
that
needs
to
be
extensible,
because
contributed
modules
are
going
to
be
adding
their
own
paths
of
where
they
might
put
stuff.
So
it
probably
is
one
of
these
things
that
every
module
in
core
should
be
using
an
api
to
say,
hey
as
file
module.
I
use
these
locations
as
filter
module.
F
Yeah
and
basically
now
I'm
looking
through
image
files
and
file,
sorry
image
fields
and
file
fields
and
I'm
looking
at
their
configuration
to
see
which
wrapper
they're
using
and
if
they
have
a
custom
path
between
either
private
or
public
files,
and
that's
what
I'm
listening
here
and
the
way
that
it's
written,
I
think
if
there
was
another,
I
think
that
the
other
non-core
use
case
of
rappers
is
just
cdns
or
something
else
that
says
directly
to
something
something
external.
Is
that
right?
F
So
I
think
that
the
way
that
it's
written
it
should
support
that
as
well
and
listed
there.
My
only
the
only
thing
that
I
saw
when
comparing
this
to
drupal
8,
I
think
of
mine,
is
that
certain
modules.
So
sorry
we
can
add
tokens
in
the
path
of
files.
So
basically
I
know
that
in
gatsiness
automatically,
for
example,
in
order
not
to
accumulate
multiple
files,
the
paths
include
year
and
month,
so
they
save
monthly
so
that
they
split
the
volume
of
files
into
separate
directories.
F
But
I
haven't
seen
any
mention
for
image
or
file
fields
in
backup
to
say
that
they
support
tokens
so
far.
Maybe
it's
something
that
we
didn't
add.
B
F
Maybe
maybe
I
didn't
see
it
in
the
ui
see
how
if
a
field
supports
tokens,
we
say
this
field
supports
toppings,
it's
not
mentioned
in
any
of
the
files
related.
The
paths
are
related,
but
yeah.
That's
a
follow-up
anyway.
I
would
like
feedback
on
that.
Maybe
you
can
get
it
out
of
the
way
soon
and
then
focus
on
the
same
drafting.
B
Yeah,
let's
see
speaking
of
the
safe
draft
issue,
there's
also
an
issue,
that's
kind
of
related
to
that
that
changes
the
way
that.
B
We
put
the
description
text
beneath
each
action
like,
if
you
say,
publish
or
save
as
draft
or
schedule
for
later,
there's
a
pull
request
that
changes
the
way
that
works
slightly.
To
tie
you
that
up-
and
I
wish
that
I
had
it
right
here,
but.
F
I
saw
that
you
posted
so
in
because
I
had
a
concern
with
regards
to
the
sorry
field
set
that
we've
added
that's
find
it
quickly.
B
there
we
go
yeah
and
that
issue's
super
close
it
might
actually
affect
a
little
bit
the
way
that
any
save
as
draft
functionality
works
yeah,
but
okay,
it
looks
like
jen
actually
commented
on
that
today
that
the
pull
request
is
super
close,
but
it
restructures
the
form
slightly
for
where
the
promote
front
page
and
sticky
check
boxes
are,
and
so
there's
some
concern
about
changing
the
form
structure
could
impact
existing
sites.
B
So
it
looks
like
that
that
jen's,
okay
with
separating
out
that
change
for
the
time
being
and
then
we'll
just
kind
of
get
the
usability
improvement
of
having
the
description
text
be
next
to
the
radio
buttons
in
that
issue
yeah.
I
like
that
issue.
A
lot
3122
just
does
a
little
cleanup
on
the
way
that
the
options
for
publishing
are
displayed
and
configured.
So
that's
really
close.
B
Okay.
Well,
we've
got
a
wrap.
It's
the
top
of
the
hour.
Thank
you
folks
for
being
here
today
and
thank
you.
Those
out
there
who
listen
to
these
phone
calls
probably
like
I
said
next
week,
we'll
do
kind
of
the
planning
meeting
and
yeah.
We'll
start
accruing
or
bring
your
ideas
for
things
that
you
would
like
to
talk
about
for
1.20.