►
From YouTube: Backdrop Weekly - April 22, 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
All
right
today
is
thursday
april
22nd,
and
this
is
our
weekly
development
agenda.
Before
we
get
into
items
on
the
agenda,
we
should
probably
go
through
and
do
some
quick
introductions.
I
will
start.
My
name
is
jen
lampton.
I
am
from
oakland
california,
and
I'm
very
excited
to
be
working
on
a
bunch
of
backdrop
upgrades
this
week
from
drupal
and
I'm
hoping
to
be
working
on
the
backdrop
upgrade
status
module
as
part
of
that.
B
So
hopefully
it'll
start
to
contain
not
only
a
recommendation
from
indigo
zealot
to
check
github
for
projects
that
have
been
ported
but
don't
have
official
releases.
I'm
also
hoping
to
add
a
bunch
of
additional
pages.
That'll
give
us
some
information
like
how
many
nodes
of
each
content
type
and
any
fields
that
might
have
problems
with
the
migration
based
on
their
field
type
and
stuff,
like
that.
That
can
help
inform
estimates
or
how
much
time
it
might
take
to
move
a
site.
A
Hello,
I'm
nate
lampton
court
committer
and
yeah.
We
had
some
exciting
activity
this
week
with
security
release.
So
I'm
excited
to
talk
about
that
today.
Let's
go
to
robert.
C
I'm
robert
lang,
a
bug
folder
on
zulup
and
github
and
relatively
new
to
backdrop,
but
I've
gotten
involved
in
fixing
various
little
odds
and
ends
that
seem
to
need
fixing
and
folks
have
been
very
friendly
and
inviting
about
that
so
I'll
I'll
keep
doing
more
over
to
tim.
D
Hi,
I'm
tim
erickson,
I'm
in
deerwood
minnesota
and
have
been
pretty
busy
lately,
so
not
too
involved
in
the
issue.
Queue
mainly
focused
on
some
pmc
issues
and
yeah,
and
I
think
that's
it
just
here
to
keep
up
with.
What's
going
on,
we
have
a
feature
freeze
coming
up
soon.
So
let's
go
to
joseph.
B
That's
great
new.
This
week
we
have
four
contributed
modules
with
their
first
releases
flag,
clear
leaflet,
custom
error
and
sticky
note.
So,
thanks
to
all
the
contributors,
who've
been
working
on
those
and
there's
also
been
a
bunch
of
work
happening
on
the
documentation
website.
I
think
last
week
we
didn't
know
where
that
stood.
I
checked
on
it
this
week
and
it
looks
like
all
of
the
content.
From
the
backdrop
main
site
has
been
moved
over
to
the
doc
site.
B
It
has
been
reorganized
to
match
an
outline
that
peter
had
come
up
with.
For
us,
it
looks
fantastic
and
we've
turned
off
the
importer
from
the
backdrop
site.
So
now,
the
primary
source
of
documentation
for
everything
should
be
the
docs.backup
cms.org
site
and
we're
starting
to
go
through
all
of
the
content
on
the
backdrop
site
and
disable
it
and
set
up
redirects
from
the
old
url
to
the
new
one
on
the
doc
site.
So
soon
we
should
be
entirely
dependent
on
the
documentation
site
for
all
the
documentation.
A
B
I
don't
think
there's
any
so
all
of
the
things
in
the
menu
that
point
to
documentation
now
point
to
the
doc
site
and
there's
a
couple
of
things
like
there's
something
in
the
footer.
Maybe
there's
a
couple
of
links
in
the
text
that
point
to
it,
but
for
the
most
part,
all
of
the
content
on
the
main
site
still
points
to
the
main
site.
If
you
can
find
the
nodes,
but
all
of
the
links
in
the
menu
take
you
to
the
other
site.
B
A
I
noticed
that
the
forum
has
a
little
external
link
icon
on
it,
but
the
user
guide
does
not.
Is
there.
B
A
B
B
B
I
think
that's
it
there's
a
bunch
of
other
general
stuff
going
on
conversations
in
the
forum,
people
working
on
various
things
and
issue
queues
and
stuff,
but
nothing
specifically
notable
about
our
sites.
Oh
there's,
a
bunch
of
translations
happening
on
the
translation
site.
Turkish
is
now
like
the
language
that
has
the
highest
translation
level,
which
is
really
exciting.
So
I
think
I
want
to
say
a
special
thank
you
to
all
the
people
that
are
working
on
translating
backdrop
strings
too.
A
Yeah,
that's
wonderful,
okay,
so
118.3
is
the
latest
version
of
backdrop
that
has
a
release
that
just
came
out
yesterday.
It
was
a
security
update
that
we
coordinated
with
the
drupal
team
and
yeah
get
your
sites
updated.
It's
it's
an
xss
attack
which
is
the
most
common
type
of
web
attack,
not
particularly
dangerous,
but
this
one
kind
of
had
some
it's
it's
pretty
wide
for
an
exorcist
attack.
A
So
I
recommend
you
get
your
sites
updated.
Let's
see,
there
was
also
one
other
bug
fix
that
went
out
in
that
118.3
that
had
to
do
with
running
an
update
from
triple
seven,
so
really
minor.
Other
change,
so
183
is
mostly
just
that
security
fix,
since
we
had
a
bug
fix
that
had
a
whole
slew
of
releases
just
a
couple
of
weeks
ago.
A
118
4,
therefore,
is
our
next
bug
fix,
release,
bug
fix
releases.
We
try
to
incorporate
as
many
fixes
as
we
can
and
then
we
we
release
them
just
sort
of,
as
is
warranted
once
we
accumulate
enough
fixes.
A
The
first
time
that
I've
got
promoted
here
is
a
118
for
issue.
That
we'd
like
to
move
forward
is
php
8
support.
This
year
is
47.72
and
joseph
did
a
bunch
of
work
on
this
quite
a
while
ago,
and
it's
been
sitting
in
needs
review
for
a
couple
of
months
several
several
months.
A
I
also
saw
that
recently,
drupal
7,
I
think,
is
also
moving
really
close
towards
drupal
or
sorry
towards
php
8
support,
so
another
opportunity
that
we
have
here
besides
reviewing
the
work
that
is
already
done,
is
comparing
it
with
the
work
that
has
been
happening
over
in
drupal
and
seeing
if
there's
any
things
that
we
missed
in
our
implementation.
A
Joseph
I
saw
you
on
muted.
Do
you
want
to
add
some
things.
E
Yeah
there
was
someone
reported
a
while
back
problem.
I
think
it
was
indigozola,
although
I
don't
remember-
and
I
haven't
been
able
to
fix
that
yet
so.
Actually,
I
think
that
should
be
needs.
Work
not
needs
review.
A
Okay,
thanks
for
the
heads
up
there,
okay
yeah,
it's
currently
sorry,
I
saw
the
yellow
and
I
thought
that
that
meant
needs
review,
but
it
actually
is
needs
testing
and
the
pull
request
currently
needs
work
is
the
status
in
github.
I
just
misread
that.
Okay,
but
thank
you
joseph.
A
Let's
see,
there's
this
issue
that
has
to
do
with
internationalization
that
if
you
have
the
same
menu
item
in
different
translations,
it
can
cause
an
issue
about
which
one
is
currently
active
in
the
breadcrumb
and
in
the
menu
navigation.
The
issue
number
is
47.98.
A
A
Because
this
has
been
open
for
quite
a
while,
let's
see,
and
we
have
some
new
issues
that
were
brought
up
by
joseph
and
robert
here
that
we'd
like
to
talk
about
today,
joseph
you
filed
a
new
poll
request
around
an
issue.
The
issue
number
is
50
28
optimize
field
sync
status.
E
Yeah,
so
that
function
is
part,
it
gets
run
any
time
you
clear
cache.
It
was
it's
clear,
caches,
run,
cron
or
enable
or
disable
a
module,
and
basically
what
it
does
is
it
checks
if
there
is
a
module
that
provides
the
field
type
and
if
there
is
a
module
that
provides
the
field,
storage
type.
E
And
in
there
what
it
was
doing
is
it
was
running
a
for
each
loop
through
it
was
got
your
list
of
modules
and
then
ran
a
for
each
loop
per
module
and
then
in
there
got
a
list
of
your
fields,
and
so
what
I
did
is
I
just
moved
that
out
of
the
the
for
each
loop,
because
anytime
anytime,
it
looks
up
the
list
of
fields.
It
does
a
directory
scan
on
your
config
directory,
and
if
you
have
a
slow
file
system,
then
that
can
cause
massive
problems.
E
So,
if
you're
running
into
like
a
virtualized
environment
or
if
you
have
a
remote
file
system
or
anything
like
that,
it'll
cause
massive
problems
to
do
that.
Many
directory
lookups.
A
So
do
you
have
any
idea
about
an
estimate
about
in
your
testing
like
let's
say
in
one
of
those
hypothetical
slow
environments
say,
like
I,
don't
know
a
docker
environment
on
mac,
so
one
of
the
most.
A
E
I
haven't
really
tested
it
for
cash
clear
all
I
did
do
so.
I
was
actually
working
on
this
because
our
server
is
using
it's
using
cluster
as
the
file
backend
for
the
files
directory
of
our
sites
and
without
the
patch
doing
a
site
install
took
about
a
minute
and
a
half
and
with
the
patch
doing
a
site
install
takes
about
20
seconds
wow,
that's
a
huge
difference.
A
Wow,
that's
pretty
cool
yep
wow!
This
is
cool
and
indigozella
has
already
reviewed
it
and
said
that
she
also
sees
that
cron
runs
are
substantially
faster
doing
this
wow
well.
This
is
very
cool
yeah
well
worth
prioritizing
as
a
as
a
performance,
enhancement,
wow.
That's
really
great.
Nice
find
joseph.
A
Yeah
and
this
kind
of
goes
back
to
the
way
that
we
store
config
files.
It
sounds
like
that
if
the
config
files
were
stored
in
the
database,
would
this
still
be
a
problem
in
the
same
way.
E
A
Well,
cool
very
neat,
yeah,
I'd
love
to
take
a
look
at
that
issue.
Number
is
5028
currently
needs
review.
A
Let's
see,
let's
move
on
to
next
issue.
Robert
pulled
this
one
up
for
discussion
today.
It's
50
18
is
the
issue
number
that
node
previews
use
the
wrong
layout
and
I
think
we
we
did
a
little
bit
of
discussion
before
the
meeting
how
this
pull
request
has
been
tested.
It's
pretty
simple
fix,
but
I
think
we
wanted
to
kind
of
open
a
discussion
about
a
long-term
strategy
for
solving
this
problem.
A
A
However,
it's
an
unfortunate
like
hard-coded
integration
point
between
layout
module
and
node
module
that
layout
module
makes
an
exception
when
loading
node
previous
and
this
pull
request
fixes
that
kind
of
by
leaving
the
current
implementation
in
place
and
just
correcting
it,
but
there's
a
bigger
discussion
here
about
how
can
we
fix
this
with
decoupling
that
that
integration
and
making
it
so
that
we
don't
have
this
weird
exception,
handling
in
layout
modules,
specifically
for
node
previews,
so
robert?
I
think
you've
got
a
better
handle
on
this
than
I
do
do.
A
Can
you
describe
kind
of
what
ideas
you
might
have
for
solving
that
issue?
C
So
in
so
in
the
kind
of
layout
module
flow,
there's
a
step
where
the
layout
module
gets
a
path
and
then
calls
some
routines
to
find
the
layouts
that
match
that
path
and
then
does
some
processing
to
set
the
contexts
for
those
layouts.
So
it
can
check
the
access
and
throw
away
the
ones
that
don't
pass.
The
access
check
and
what's
left,
is
the
layout
that
it
uses
and
so
to
accommodate
the
node
preview.
C
There's
two
things
that
that
need
to
happen
is
first,
it
needs
to
find
the
layout
that
matches,
for
example,
node
slash
percent,
even
though
the
path
is
a
different
path.
So
it
needs
to
find
it
alter
the
way
layout
matches
the
path,
and
then
it
also
needs
to
modify
the
context
setting
because
for
previews
the
parameter
that
shows
up
in
the
context
isn't
a
node
id
it's
the
id
of
the
temporary
nodes
stored
in
temp
store,
so
it
has
to
interpret
context
parameters
in
a
different
way.
C
C
There
had
been
some
pushback,
noting
that
any
if
we
put
a
hook
in
for
laying
out
that
opens
the
the
door
to
someone
implementing
that
hook
in
a
very
inefficient
way
and
therefore
slowing
down
the
whole
site,
and
I
had
made
the
argument.
I
I
guess
towards
the
end
of
that
comment,
stream,
that
that
possibility
already
exists,
because
the
layout
wild
card
module
does
pretty
much
that
it.
C
It
basically
replaces
the
entire
call
chain
of
layout
module
with
its
own
call
chain
that
duplicates
a
whole
bunch
of
that
code
and
that's
how
it
can
inject
what
it
wants
to
do.
So,
I'd
come
down
to
come
to
the
argument
that
we're
not
we.
We
can
warn
people
not
to
over
the
to
implement
that
hook
inefficiently,
but
we
really
can't
prevent
them
if
they're
dead,
set
on
doing
it
and
yeah.
A
Like
a
wild
card
was
apparently
making
a
fairly
aggressive
move
there.
I
think
that
there's
a
really
early
because
determining
what
menu
route
to
execute
is
like
almost
the
very
first
thing
that
backdrop
does,
after
it
initializes
the
database.
It
says
who's
responsible
for
the
current
route.
A
What's
the
menu
entry
and
layout
module,
we
built
a
a
really
early
system
into
backdrop
that,
before
rendering
the
page
there's
an
opportunity
for
one
module
to
say
hey,
I
want
to
be
responsible
for
the
rendering
of
this
request
and
layout
module
takes
that
role
and
says
I'm
responsible
for
rendering
html
pages
and
I'm
guessing
layout.
Wildcard
module
probably
says
now,
I'm
responsible
for
rendering
these
pages
and
then
and
then
replaces
the
process.
A
Yeah,
so
I
think
yeah,
I
think
some
additional
hooks
sounds
pretty
valid.
Was
I
thinking
about
this
and
then
we
would
be
able
to?
Oh,
I
remember
what
it
was
that
so
layout
module,
oh
no
node
module
would
then
implement
the
hook
right
and
say
say
hey
for
the
preview
path
I
need
or
the
hooks
plural.
I
need
to
make
some
modifications
when
looking
at
a
preview
path
and.
B
A
I
think
the
main
consideration
we
should
have
with
making
that
change
and
in
core
is.
We
should
just
make
sure
that
node
module
implementing
that
hook
or
any
module
implementing
that
hook
but
known
module
will
do
it
out
of
the
box,
doesn't
really
have
any
noticeable
impact
which
shouldn't
because
it
should
say
you
know
an
if
statement
right
at
the
top
of
it.
Does
this
path
match
no
return
and
that
sort
of
thing
happens.
A
Hundreds
of
times
every
request,
you
know
that
a
hook
is
is
called
and
then
nothing
happens
and
then
it
just
it
just
returns
back
so
yeah.
I
think
just
confirming
that
and
then
yeah.
It
sounds
like
a
pretty
good
approach.
Thank
you
but
yeah.
I
also
I
probably
I
may
have
even
been
the
person
that
was
like
worried
about
the
performance
impact,
but
yeah
I
mean
sometimes
at
the
time
that
something
was
designed
like
several
years
ago.
When
layout
module
was
written.
A
You
know
it
didn't
take
into
account
all
of
the
needs.
We
didn't
have
this
preview
system
at
the
time,
although
we
did
always
know
that
multiple
layouts
was
at
the
same
path
was
always
going
to
be
a
desirable
feature.
Hopefully
that'll
make
layout
wild
card.
You
know
like
it'll,
be
able
to
come
out
with
like
a
2.0
version
or
something
like
that.
That
is
a
little
bit
simplified
in
its
approach.
A
Does
wait
that
that
also
means,
then,
that,
if
you're
using
layout
wildcard,
where
the
hooks
don't
like,
because
it
replaces
the
whole
discovery
mechanism
up
front,
that
means
that
node
previews
still
won't
use
the
right
layout
if
you're
using
layout
wildcard
right
until
they
until
they
update
to
incorporate
the
fix
that
we're
using
right.
C
A
Oh
good
well
in
a
way,
then
that's
great
because
it's
like
collecting
usage,
you
know
it's
having
it's
having
active.
It's
actively
testing
the
the
the
patch
in
production
environments,
which
is
great
cool,
yeah.
A
A
All
right,
119
119,
is
the
next
minor
version
of
backdrop.
It'll
be
coming
up.
May
15
2021.,
like
tim
mentioned
at
the
beginning
of
the
call.
That
means
that
feature
freeze
is
right
around
the
corner.
A
Like
always,
we
at
this
point
in
the
res.
The
release
cycle
need
to
decide
when
feature
freeze
will
actually
be.
We
have
a
historical
precedent
of
when
feature
freeze
falls
on
a
weekend
or
on
a
holiday
that
the
actual
feature
freeze
is
at
the
end
of
said
holiday.
So
this
being
a
primarily
hobbyist
driven
project,
weekends
and
holidays
are
when
backdrop
tends
to
make
a
lot
of
progress.
A
So
it
turns
out
that
may
1st
lands
on
a
saturday
this
year,
which
means
that
feature
freeze,
won't
actually
be
on
saturday
it'll,
be
at
the
end
of
sunday
april,
2nd
so
jen.
Is
that
sound
correct
to
you
like?
As
far
as
my
calculation
of
timing
and
everything.
A
Okay,
may
3rd
is
not
a
holiday,
so
it
will
actually
be
may
2nd.
Sometimes
it
gets
pushed
to
like
a
whole
three
or
so
days,
which
can
be
nice
or
not.
Nice.
A
Let's
see
so
future
freeze
actually
is,
may
2nd
I'm
going
to
update
that
in
the
agenda
for
clarity
and
we've
got
a
number
of
issues
that
are
in
flight
right
now,
one
of
them
the
first
one
that
we
would
like
to
get
fixed.
That
would
be
a
big
usability
improvement
that
we've
been
working
through
for
a
while.
Now
is
adding
exposed
filter
to
the
media
library
dialog.
The
issue
number
is
3293..
A
There
is
a
poll
request
that
kind
of
gets
this
working,
but
has
some
complications
because
the
the
underlying
issue
is
that
the
way
that
the
page
renders
there's
a
the
views
exposed
form
for
the
file
name?
Filter
is
inside
of
another
form
for
selecting
the
active
image
and
those
nested
form
tags
cause
chaos
with
drupal's
ajax
system,
so
that
the
situation
is
a
little
bit.
A
Complex
solutions
might
include
reworking
the
dom
output
so
that
the
form
tags
are
not
nested
inside
of
each
other,
but
it
will
require
some
effort,
so
issue
3293
needs.
Some
help
is
current
status.
A
Next
up
is
advanced
caching,
adding
cash
tags
and
a
dynamic
cash
max
age.
Header
issue,
4127
joseph,
is
the
advocate
for
this
one.
I
don't
think
there
has
been
any
changes,
but
joseph
do
you
want
to
give
us
an
update
on
any
anything
happening
around
this
issue?.
E
There
has
not
been
any
updates.
I
think
the
current
status
is
that
I
need
to
write
testing
documentation
so
that
people
actually
know
how
to
test
it.
E
A
Yeah
especially
yeah
agree
that
would
be
a
big
help.
A
B
I
rebased
the
issue,
push
it
up
again
with
all
the
recent
chord
changes,
I'm
looking
at
doc,
belmont's
kendrip
module
that
does
the
same
thing
right
now
and
hope
to
have
more
updated
shortly.
A
Awesome
speaking
of
doc,
belmont
he's
the
advocate
for
the
next
issue.
Add
support
for
relationships
to
layout
contexts,
issue
2134.,
herb,
dual
took
a
look
at
this
pull
request
recently
and
also
reviewed
it
and
added
a
couple
comments,
but
yeah
herbado,
basically
is
saying
like
it
looks
pretty
good
and
my
comment
on
there
was
that
I've
already
reviewed
it
and
only
had
a
couple
of
minor
things
about
renaming
things
which
document
has
now
done.
A
So
I'm
hoping
that
next
time
we
look
at
this,
it
might
be
ready
to
go
so
I
guess
actual
status
on
that.
One
is
needs
review,
but
really
close.
A
Okay
and
lastly,
we
have
an
issue
to
merge
together
the
update
pages
right
now
we
have
separate
update
pages
for
modules,
themes
and
layouts
and
put
all
of
the
updates
for
all
things
in
the
system.
All
into
one
page
issue-
numbers
27,
14.,
gregory
or
clonos-
is
the
advocate
for
this
issue.
A
Last
I'd
seen
the
merging
of
all
the
pages
has
gone
really
well,
but
there
is
a
dashboard
block
related
to
updates
that
gregory
was
also
trying
to
revamp
at
the
same
time,
and
that's
the
sticking
point
and
to
complete
this
issue
on
for
this
next
release,
he
may
just
remove
the
dashboard
block
changes
just
do
the
changes
to
the
menu
system
instead
combining
them
all
onto
one
page,
and
then
that
would
make
it
so
that
this
would
be
ready
to
go
as
well.
A
So
that's
it
for
the
issues
that
are
still
in
flight.
There
have
been
a
couple
of
issues
that
have
been
merged
in
already
for
119
and
from
the
looks
of
things
you
know,
a
couple
of
these
are
are
in
good
shape,
others
a
little
bit
further
out
so
we'll
see
which
ones
we
can
get
wrapped
up
here
in
the
next.
A
What
is
it?
Nine,
no
11
days,
yeah,
okay,
that's
it
do
you
guys
have
any
any
other
core
issues
that
are
features
that
you
guys
would
like
to
talk
about
before
we
move
on
to
initiatives.
A
Okay,
well,
initiatives
are
long-running
features
or
objectives
that
might
span
multiple
releases,
jen
kind
of
gave
us
an
update
already
on
the
state
of
the
documentation
initiative
with
the
doc
site.
That's
the
the
primary
change
there
is
that
bw
panda
has
been
doing
some
work.
Consolidating
all
of
our
documentation
looks
like
there's
an
update
actually
in
the
agenda
here.
The
bw
panda
has
declared
this
done
for
the
time
being
that
the
issue
747
in
the
backdrop
cms.org
issue
queue,
has
been
completed.
A
He
closed
the
issue
and
that
that's
kind
of
his
as
far
as
he
was
interested
in
in
taking
this
this
project.
A
So
I
guess
this
might
be
the
last
time
that
we
talk
about
documentation
as
an
initiative
for
the
time
being
until
we
get
a
new
initiative
lead
or
someone
that
is
interested
in
picking
it
back
up
again.
Does
that
sound
right
tim?
I
see
you
nodding.
D
A
Yeah
thanks
tim
tim
you're.
Actually
the
next
thing
to
talk
next
topic
to
speak
on
is
telemetry.
Do
you
have
any
updates
on
the
telemetry
initiative.
D
No,
but
I
I
think
with
that,
I
really
wanted
to
get
something
into
this
next
release
right
now.
I
don't
see
myself
being
able
to
to
so
what
it.
In
my
view,
my
role
has
been
for
the
last
two
or
three
months.
My
goal
has
been
to
go
through
the
work
day
that
you've
done
sort
of
review.
D
It
figure
out
exactly
what
we
need
to
do
to
get
something
into
the
next
release,
but
then
rely
on
you
or
someone
else
to
help
implement
that,
and
I
just
I
haven't
gotten
to
that-
I
don't-
and
I
don't
know
if
I
will
in
the
next
10
days
or
what
do
we
have
two
yeah
we've
only.
D
So
I
don't
know
if
anybody
else
has
time
to
help
with
that
I
mean,
I
think
the
stage
is
just
to
figure
out
what
needs
to
there.
I
think
we
I,
I
think
we
need
to
make
a
couple
of
decisions,
and
then
there
is
some
code
work
right
that
has
to
happen.
Do
you
remember
anything.
A
Yeah,
I
I
think
you
know
we
could
put
in
well
the
the
simplest
way
to
proceed
like
and
actually
get
it
done
next
week.
B
A
The
telemetry
module
that
is
written
for
core
is
pretty
much
ready
as
far
as
like
reporting,
some
really
basic
information.
Php
version.
B
A
Sql
version
and
web
server
that
we
could
merge
in
the
telemetry
module,
as
is,
and
not
even
turn
it
on,
and
if
that
were
the
case,
then
telemetry
module
would
be
in
core.
It
wouldn't
actually
be
turned
on
and
we
wouldn't
need
to
do.
The
peripheral
work
of
like
revamping
the
installer,
for
example,
to
request
permission
to
turn
on
the
telemetry
module
or
possibly
doing
some
other
kind
of
data
collection
notice.
D
And
I
suppose
it
would
make
it
a
little
easier
to
test.
Maybe
I
don't
even
know
if
that
matters
we,
I
feel,
like
we
talked
about
this
last
time
and
came
up
with
a
reason
why
this
we
didn't
want
to
do
this.
Put
it
in,
but
have
it
disabled.
A
D
So
the
we
have
issues,
obviously
around
the
the
the
code.
That's
going
to
go
into
backdrop.org
to
store
the
data,
that's
different
from
the
code.
That's
going
to
go
into
core.
What
is
what
hasn't
district,
I'm
trying
to
remember
myself
and
what
isn't
done
that
has
to
go
into
core
right
is
the
what
you
just
talked
about
it's
the
stuff
about
how
to
turn
it
on
and
how
to
manage
it.
A
B
I
have
a
question:
did
we
already
implement
the
restriction
that
prevents
people
from
recording
data
unless
it's
specifically
whitelisted.
B
A
Can
implement
the
hook
yeah
and
that
will
start
sending
data
to
backdrop
cms.org,
but
because
it's
an
anonymous
api,
like
any
site,
is
allowed
to
send
this
information.
There's
really
nothing.
We
can
do
from
stopping
data
from
being
sent
to
the
server.
A
B
A
Yeah,
we
don't,
we
don't
have
there's
a
pull
request
that
would
put
it
into
backdropcms.org,
but
it's
not
there.
Yet.
Okay.
D
So
it
sounds
to
me
like
to
quickly
summarize
that
we
could
the
the
the
best
route
to
getting
something
into
this
next
release
would
be
to
decide
to
to
verify
that
that
the
current
code
to
do
that
with
it
being
disabled.
D
A
Yeah,
yeah
and
and
that's
kind
of
an
interesting
question
about,
could
we
do
that
mid
or
not?
I
don't
really
know
I
kind
of
feel
like
probably
not
sure,
because
it's
not
really
a
bug
fix.
You
can't
even
really
say
that
it's
a
usability
improvement.
A
D
Well,
that's
certainly
not
where
I
was
going,
I
mean
I
would
be
happy
if
we
were
able
to.
I
think
if
we
knew
that
the
code
was
in
backrub.org
and
that
people
had
the
option
of
turning
it
on
right.
That
would
give
us
some
incentive
to
work
on
the
backrub.org
part
in
the
sense
that,
like
we'd
at
least
be
able
to
see
data
coming
in
once
we
implemented
it,
even
if
it's
only
for
10
sites
right.
A
A
D
We
wouldn't
have
to
wait
until
the
next
release.
In
order
to
see
anything
happen,
we
could
at
least
see
like
wow.
Our
work
is
working,
even
though
it'll
take
until
the
next
release
before
it's
actually
effective
yeah.
So
I
I
feel
like
I
would
argue
that
there
is
some
value
in
getting
it
in
you
know
and
getting
that
in,
so
that
we
could
turn
it
on.
D
If,
if
nobody
has
any
reasons
not
to
do
that,
if,
if
that
helps
us,
you
know,
even
if
it
only
suddenly
helps
us
motivate
us
to
get
the
backdrop
dot
org
part.
D
So
I
you
know,
if
anybody
has
time
to
help
with
this,
please
do
I'd,
be
happy
to
to
talk
to
anybody
or
set
up
a
meeting
between
now
and
and
and
the
feature
freeze
if
that's
helpful,
but
I
on
my
own,
I'm
not
sure
that
I'm
to
be
able
to
do
much
in
the
next
10
days.
A
D
D
Okay,
I'll
shut
up.
Okay.
Well,
how
about
this
I'll
make
comments
on
the
next
one,
because
the
next
thing
on
the
agenda
is
luke's
thing
and
luke
was
just
I'll
just
mention
that
luke
was
on
the
last
call
and
asked
what
what
are
people
expecting
from
me
or
where
is
my
initiative
at,
and
we
talked
briefly
about
it,
he,
the
the
where,
where
it
currently
stands,
is
he
would
like
to
get
some
kind
of
final
report,
and
we've
talked
about
that
before.
D
I
asked
him
if
he
was
sure
that
that
was
necessary
and
he
still
thinks
it's
a
good
idea.
He'd
like
he
was
looking
for
some
sort
of
a
deadline
and
at
least
the
idea
of
of
using
the
next
backdrop
live
as
a
deadline
came
up.
D
I
don't
know
I
think
he'd
like
to
do
it
sooner
than
that,
but
I
would
I
would
say
our
target
right
now
is
to
just
get
a
final
report
before
the
next
backdrop
live,
but
and
that
that
is
another
initiative
which,
like
the
documentation,
one
which
he's
doing
a
final
report
on
what
he
originally
set
out
to
do.
But
if
anybody
is
looking
at
that
and
interested
in
taking
it
further,
please
step
up
and
let
us
know,
because
there's
definitely
more
work
to
do
on
that.
D
A
Thanks
tim
now,
I
appreciate
that
I'd
actually
removed
that
from
the
agenda,
because
I
didn't
think
there
was
going
to
be
any
other
noise
there,
but
great
all
right,
we're
closing
in
on
the
top
of
the
hour
where
the
meeting
has
to
end.
But
do
we
have
any
other
general
questions
or
discussion
that
you
guys
would
like
to
talk
about.
A
Okay,
well
maybe
we'll
call
it
a
meeting,
then
thank
you
all
for
being
present
and
thank
you
out
there
to
our
online
audience
that
watches
these
weekly
videos.
We
really
appreciate
all
the
work
that
we're
doing
that
you
are
doing
for
backdrop.
We
have
10
days
about
before
the
code
freeze,
so
let's
make
them
count
thanks.
So
much
and
we'll
see
you
guys
on
the
internet.