►
From YouTube: Backdrop Weekly meeting - Nov 12th, 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
Okay,
we're
live
today
is
thursday
november
12th,
and
this
is
our
weekly
development
check-in,
so
we're
gonna
go
around
and
do
introductions
popcorn
style
I'll
start.
My
name
is
jen
lampton
joining
from
oakland
california,
and
I'm
excited
to
hear
about
all
the
exciting
things
in
last
week's
release
tim.
Do
you
want
to
go
next.
B
Sure
my
name
is
tim
erickson,
saint
paul
tim
coming
to
you
from
deerwood
minnesota.
I
mentioned
last
week
that
deer
hunting
had
started
up
here
in
deerwood
and
I'm
still
doing.
Okay
so
and
the
deer
are
still
out
there
so
been
very
busy
lately.
So
I
haven't
been
had
as
much
time
to
work
on
backdrop
issues
the
last
couple
weeks.
My
big
things
right
now
are
trying
to
work
on
some
conference
distribution
stuff.
I
have
a
in
the
the
telemetry
initiative
and
that's
it
greg.
C
Yeah
sure
hi,
my
name
is
greg,
I'm
usually
in
australia,
but
now
joining
for
grace
interested
in
everything
around
backdrop,
especially
user
experience,
and
my
the
issue
that
I
was
advocating
for
was
recently
best.
So
I
am
now
free
if
I
wanted
to
work
on
another
issue,
so
I
think
I'm
probably
going
to
be
working
on
the
one
about
merging
the
update
page
olaf.
D
Yeah
phil.
E
Hey
I'm
phil
ward,
with
out
of
wichita
kansas
and
mainly
just
kind
of
here
to
be
a
flying
wall
today
kind
of
see
what
you
guys
have
to
talk
about,
and
you
know
if
there's
if
I
could
throw
out
any
ideas,
then
I'll
be
you
know
willing
to
do
that,
but
otherwise,
just
kind
of
here
to
see
how
the
meeting
goes
appreciate.
It.
F
Thanks
phil
and
that's
awesome
you're
from
kansas,
I'm
also
a
kansan
so
originally,
but
now
I'm
in
oakland,
california,
and
I'm
doing
yeah.
This
week
we
got
117
2
out
and
like,
like
others,
I'm
excited
to
report
the
progress
on
that
and
turn
towards
these
118
issues.
So
that's
it
for
me
think
that's
everyone
jen!
You
want
to
take
it
back
over.
A
Sure
so
I
wasn't
here
last
week,
but
I
did
notice
that
there
are
two
new
contributed
project
updates
this
week.
Ubercart
who
bought?
What
has
a
modular
release?
Cs4
csv
export
is
a
new
module
release.
A
So
assuming
you
guys
covered
all
of
last
week's
last
week,
but
there
are
a
handful
that
came
out
on
november
4th
as
well
all
right
nate.
You
want
to
jump
into
117
two.
F
Yeah
117
two:
as
we
talked
about
last
week,
we
did
the
release
process
on
sunday,
so
a
couple
of
us
got
together
to
do
the
117
ii
release,
which
was
very
well
managed.
We
had
all
kinds
of
great
things
happening:
big
thanks
to
bw
panda.
I
sat
down
on.
I
should
have
done
this
earlier,
but
I
sat
down
on
sunday
morning
to
look
through
the
rtbc
queue
and
it
was
empty
because
bw
panda
had
already
been
through
it.
F
So
that
was
a
really
pleasant,
excellent
surprise
and
some
of
the
issues
that
we
have
been
talking
about
for
several
weeks
have
been
merged
into
that,
including
transliteration
of
urls
doesn't
expect
the
site
default
language
issue
2637
that
got
fixed
and
merged
in
the
mysql8
support.
We
had
talked
about
wanting
to
get
that
out
into
the
next
bug,
fix
release
and
not
in
the
security
release
to
make
it
so
that
it's
available
for
everybody.
F
But
if
there
are
any
last
issues
with
it,
they
could
go
back
to
the
previous
version
without
having
a
security.
A
F
We,
it
was
in
the
one.x
branch
for
three
weeks
and
we
didn't
have
any
additional
updates
or
issues
from
anyone,
and
it
had
five
different
confirmations
that
it
was
working.
So.
F
With
all
of
that,
we're
just
like
okay,
you
know,
let's,
let's
get
it
in,
so
that's
great,
because
it
means
that
the
latest
release
of
backdrop.
The
current
stable
version
now
runs
out
of
the
box
on
like
centos
the
newest
versions
of
cenos
and
red
hat,
which
use
mysql8
so.
B
I
don't
know
if
this
is
the
right
time
to,
but
there
is,
and
it
did,
it
may
have
caused
an
issue,
although
I'm
not
sure
if
the
problem,
if
you
haven't
seen
it
yet
there's
an
issue
about
civic
crm,
it's
issue
4745,
so
it
broke,
it
broke
somebody's
cvcrm
integration
and
they
made
a
comment
that
the
problem
might
be
this
sort
of
hacky
solution
for
the
views,
integration
and
civic
crm,
but
the
only
reason
I'm
raising
it
is
because
it
might
be
related
to
this
mysqla
thing,
and
I
just
want
someone
like
yourself
to
be
aware
of
it
in
case
there
are
other
implications.
F
Very
interesting
yeah,
I
think
I
interesting
oh,
I
had
not
seen
this
so
I'll.
Take
I'll
take
a
look
at
it.
That
is
interesting.
I
saw
something
just
similar
to
this,
that
it
looks
like
they're,
the
quoting
that
we
have.
We
quote
around
everything
and
it
looks
like
it
might
be,
quoting
around
an
empty
string
making
it.
F
So
it's
an
empty
table
name-
and
I
saw
that
happen
in
one
of
the
implementations,
but
I
fixed
it
in
the
core
version,
but
I'm
not
sure-
maybe
maybe
it's
like
you
say
some
kind
of
hacky
thing
that
they're
doing
that
the
auto
table
escaping
is
now
causing
an
issue.
F
Let's
see,
and
also
this
isn't
exactly
something
new
that
is
in
117.2,
but
tugboat
qa
we're
now
using
them
for
pull
request.
Sandboxes
the
issue
is
43.51
and
it
does
appear
that
right
now
we
get
two
sandboxes
on
every
pull
request,
one
on
zen
ci
and
one
on
tugboat.
It's
totally
fine.
For
the
time
being,
I
think
we're
gonna
likely
slowly
move
away
from
the
zen
ci.
F
F
Yeah,
but
there
are
some
like
issues
with
the
testing
infrastructure
too,
that
we
need
to
get
on
newer
versions
of
php.
You
know
right
now
we're
still
running
php
7,
which
isn't
even
an
officially
supported
version.
F
We
need
to
get
that
updated
and
so
yeah.
I
I'd
like
to
pursue
looking
into
github
actions
for
that.
Just
because
it'll
have
us,
give
us
a
lot
more
control
over
it
and
it's
integrated
into
github.
Now.
F
F
Well,
I
think
we
need
to
figure
that
out
like
exactly
how
fast
the
speed
of
it
is
a
lot
of
the
reasons
why
backdrops
tests
are
so
much
faster
than
drupals
actually
have
to
do
with
optimizations.
That
gore
made
to
like
the
install
profiles,
for
example,.
A
That's
it,
I
think
it's
because
a
gorge
server
can
run
like
six
different
updates
at
the
same
time
or
six
different
tests.
At
the
same
time,
it's
like
split
across
multiple
threads,
and
I
don't
think
github
actions
can
do
that.
F
A
It
to
that-
and
I
have
a
feeling-
github
actions
is
probably
comparable,
yeah
comparable
to
travis,
but
we'll
see.
Maybe
they
have
like
a
paid
plan
or
something
that
we
could
get
as
a
open
source
project
where
we
can
get
access
to
multiple
threads
and.
F
That
was
really
why
we
moved
off
of
it,
although
having
the
tests
run
in
five
minutes
instead
of
an
hour
and
a
half
was
definitely
a
real
improvement
in
our
performance,
but
most
of
that
was
again
like
that
was
in
code
improvements
plus
faster
servers,
so
anyway
yeah.
So
we
have
those
polarquest,
sandboxes
jen
the
conversation
with
gore.
F
A
We
because
he's
been
giving
us
this,
like
amazing,
free
service
for
forever.
It's
something
that
it
would
be
really
nice
to
be
able
to
say
thank
you,
rather
than
just
like
kicking
him
out
the
door
and
having
him
notice
by
one
day
showing
up
and
looking
and
thinking
and
be
like.
Oh,
my
god.
Why
are
they
doing
this?
It.
F
F
Let's
see
text
update
for
admin
blocking
this
shouldn't
be
in
here.
This
is
on
this
one,
okay,
but
other
than
those
issues
that
we
talked
about
every
week.
There
were
31
total
fixes
in
this
release,
which
was
super
cool,
so
that
was
like
a
really
good
collection
of
fixes
that
went
out
in
117
too
anything
else
you
guys
want
to
mention
about
the
new
release:
okay,
well,
3,
17
3
is
the
next
bug
fix
release
and
we
still
have
lots
of
bugs
to
potentially
tackle
tim.
F
Well,
I
guess
we
just
did
I.
I
don't
think
that,
because
there's
do
you
wanna,
do
you
wanna
say
more
about
that?
I
don't
know.
Are
we
allowed.
A
F
So
it's
good
that
we
got
1172
out,
you
know
and
and
got
in
all
of
those
fixes
it
with
you
know
not
relating
to
a
security
release.
F
Let's
see
tim,
you
also
mentioned
before
the
meeting
started,
that
the
docker
image
we're
having
some
issues
with
it.
I
it
needs
to
be
updated,
for
the
latest
release
is
one
problem
that
we
have
it
as
one
of
the
tasks.
Every
time
we
make
a
new
release,
but
the
last
several
releases,
no
one
has
been
updating
the
docker
image,
because
no
one
is
no.
No
one
within
the
core
development
team
is
actively
using
it.
So
we
need
a
a
volunteer
or
someone
that
we
can
consistently
depend
upon
to
update
that
docker
image.
F
But
I
looked
in
the
issue
queue
and
I
couldn't
find
an
issue.
Is
it
47.
B
B
C
Yeah
he
raised,
he
opened
a
few
blog
posts,
one
or
two
as
well,
so
they
started
testing
recently.
B
But
yeah
my
concern,
it
seems
like
there's
I'd
like
to
quickly
understand,
what's
going
on
here,
because
that
our
repo
doesn't
actually
contain
backdrop
itself.
We
have
a.
We
actually
have
a
repo
for
a
doctor,
but
I
looked
at
that
and
there
doesn't
seem
to
be
backdrop
in
it.
Is
that
just
like
some
config
files,
or
so
that's.
C
What
we
changed
and
then
doctor
pulled
that
information.
G
A
In
the
issues
github
repository,
there's
a
procedures
document
for
how
to
update
the
docker
stuff.
I
did
it
for
a
while,
but
I
wasn't
sure
anyone
was
using
it
and
then
I
think
someone
else
offered
to
do
it
and
then
they
stopped
doing
it
and
I
stopped.
I
didn't
start
doing
it
again.
G
A
Process
for
updating
is
pretty
straightforward.
We
just
like
update
our
repository
and
then
notify
docker
that
the
version
number
has
changed
by
submitting
a
polar
course
and
then
someone
a
doctor
merges
it
into
their
master.
So
it's
a
couple
of
lines
change
every
time.
It's
just
you
know
another
to
do
item
when
a
core
release
comes
out.
C
Do
we
have
it
as
a
list
in
the
in
the
release
template
we
do.
B
So
that's
the
only
thing
we
have
to
do,
though,
is
update
this.
This
the
backdrop,
ops,
slash
backdrop
dash
docker.
C
F
A
F
A
F
Be
worth
mentioning
that,
if
you
want
to
use
backdrop
with
docker,
you
can
use
lando
or
ddev,
both
of
which
have
excellent
support
for
backdrop.
G
C
F
Yeah,
I
think
that
we
we
just
need
to
check
in
on
that
issue,
47
47,
since
this
is
the
first
that
some
of
us
have
heard
of
it
all
right.
Let's
see
next
up
is
a
set
of
issues.
I
don't
think
there's
many
updates
on
there's
some
terminology
updates
jen
that
you
were
working
on
for
the
administrative
label
and
description
on
blocks
within
layouts
issue.
F
4600
looks
like
we've
been
going
back
and
forth
on
string
terminology
there.
It's
currently
marked
needs
review.
F
Let's
see
site
is
stuck
in
maintenance
mode
when
updating
modules,
issue
39.56
also
another
issue
that
has
been
sitting
in
the
needs
review
state.
B
Well,
wait
a
second.
This
is
a
github
issue,
a
new
one
or
an
old
one.
It's
an
old
one,
oh
because
there's
some
somebody's
having
a
problem
in
on
the
forum
right
now
with
that
issue-
and
I
didn't
know
that
this
was
an
outstanding
or
at
least
I'd
forgotten.
I
probably
should
have
known
okay.
F
B
Okay,
well,
I
don't
so
yeah
somebody
just
on
wednesday,
so
just
yesterday.
Well,
this
is
the
same
mates
the
same
one
that
I
think
is
having
the
problems
with
the
civic
crm.
B
F
F
Bw
panda
looked
at
it
not
too
long
ago,
and
there
was
kind
of
an
interesting
question
there
about,
like
a
lot
of
people
have
never
actually
encountered
this
as
being
a
problem
until
until
they
do
and
then
then
it's
a
big
problem
and
I'll
ask
a
question
here,
just
to
solicit
some
live
feedback
that
the
main
area
that
this
problem
usually
occurs
is
on
the
permissions
page.
When
you
have
lots
of
permissions
and
links.
C
Paragraphs
as
well
paragraphs
yeah,
multiple
things
yeah,
so
this
is
this-
is
plaguing
plaguing
the
the
larger
sites
in
gov
cms
platform,
we've
had
multiple
people
complaining
about
that.
The
the
issue
with
the
the
menu
management
page
is
solved
by
the
big
menu
module,
which
sort
of
like
loads
partially
the
menus
and
then
add
in
an
adjective
way
loads,
the
rest
of
it
as
you
edit
it,
but
fixing
yeah
yeah.
But
the
permissions
thing
is
just
the
more
the
more
modules
people
enable
and
the
more
roles
they
have.
C
F
So
the
the
pull
request,
I
believe,
throws
a
warning
right
on
the
status
report,
so
it
won't
be
a
red
dot.
It'll,
be
the
yellow
dot.
F
The
maybe
the
question
that
I
was
I
was
going
to
throw
out
there
now
that
you
guys
have
filled
me
in
a
little
bit
more
in
the
number
of
situations
that
might
not
be
valid
was.
Maybe
we
should
throw
that
error
like
we
should
do
some
checking
to
see
if
your
site
is
likely
to
be
affected
by
this
problem
and
then
throw
the
status
report
error,
but
determining
whether
your
site
is
going
to
be
affected
sounds
like
there's
a
lot
more
circumstances
than
I
would
have
guessed
like.
F
A
Right
so
we
could
make
sure
that,
and
I
think
the
majority
of
our
users
are
probably
on
apache,
so
we
can
make
sure
that
this
annoyance,
with
a
like
yellow
message,
won't
show
up
if
you're
on
apache.
So
it
won't
bother
all
the
people
who,
like
you
know,
don't
care
about
it,
but
if
you're
not
on
apache,
that's
that's
when
it
like
is
going
to
be
your
responsibility
to
fix
the
issue,
and
so
I
think
that
that
would
be
a
really
easy
limit
to
put
around
that
notice.
F
F
F
Maybe
that's
like
maybe
we're
making
too
big
a
deal
about
this,
because
it's
like
for
most
people,
it's
not
going
to
be
a
problem,
although
every
every
backdrop
site
that's
out
there
when
they
update,
they
probably
won't
update
their
hd
access
file,
even
though
we'll
probably
say
it
that
you
should
update
the
hdx's
file.
It's
just
not
in
the
usual
pattern
and
doesn't
it's
not
handled
in
automatic
updates
those
sorts
of
things.
C
On
a
platform
with
400
sites,
only
five
are
affected,
so
it's
a
very
small
percentage,
but
when
it
happens,
it's
really
annoying
and
it's
usually
the
high
profile
sites
like
larger
sites,
customers,
which
are
more
important,
I
should
say
so
yeah
and
because
our
target
audience
are
smaller
sides.
I
guess
maybe
that's
why
it's
not.
We
don't
have
many
complaints,
but
yeah.
We
don't
want
to.
I.
A
Also
feel
like,
when
it
happens,
you
have
no
idea
why
your
form
isn't
submitting
and
so
for
the
smaller
sites.
It's
like
a
bigger
problem
because,
like
you,
you're
less
capable
of
understanding
that
there
is
an
issue
you'll
just
be
like.
A
Oh
well,
sometimes
when
I
submit
this
form,
then
my
menu
items,
don't
say,
but
you
just
move
on
with
your
life
or
like
understanding
like
that's
broken
on
this
page,
so
yeah,
I
don't
know,
I
have
what
like
maybe
15
or
20
backdrop
sites
and
I'd
say
I've
run
into
it,
25
of
the
time
and
they're
not
most
of
my
sites
are
not
super
complicated,
but
all
of
them
usually
have
one
thing
where
it's
either
like
a
lot
of
taxonomy
terms
or
a
really
big
menu,
or
one
page,
with
a
multi-value
field
on
it
or
there's
always
like
one
of
those
eight
things
they
happen
to
have
stumbled
across
and
I'm
like.
A
D
B
G
F
D
Maybe
because
I
might
I
mean
to
remember
that
there
was
a
message:
maybe
that
form
provides
it,
because
they
know
that
you
know
with
big
back
forms.
It
could
be
a
problem,
so
we
could
have
a
look
at
the
web
form
how
they
handled
it.
A
There's
like
a
special
tag
in
the
drupal
issue,
queue
for
all
of
the
issues
that
have
ever
been
created
that
are
a
result
of
this
problem.
There's
like
a
special
issue
tag,
and
I
think
that
there
are
a
couple
of
kinship
modules
that
have
come
out
with
their
own
worker.
Unfortunately,
would
not
surprise
me
if
web
form
was
one
of
them,
because
that's
a
likely
candidate
to
ran
into
this
problem.
E
Here's
another
question
so
this
the
issue,
so
I
haven't
dove
into
the
issue
itself,
but
it
looks
like
somebody
wants
to
increase
the
vars
in
the
hd
access.
Is
that
kind
of
what
this
issue
is.
E
A
A
They're,
a
handful
of
people
who
are
like
my
site
is
never
going
to
run
into
this
problem.
Why
do
I
have
a
warning
on
my
status
report
saying
that
one
day
I
might
hit
this
problem
so
we're
trying
to
figure
out
a
way
to
make
that
warning
only
show
up
for
people
that
like
when
they
hit
the
problem
or
are
likely
to
hit
the
problem.
E
Yes,
actually
coding
for
it,
yeah
coding,
for
it
would
be
a
pain
to
try
and
do
that
on
a
check
for
every
single
time.
F
Yeah,
we're
not
really
even
sure
if
we've
overblown
it
or
not
like
is
a
wording
that
bad.
You
know,
I
don't
it's
it's
hard
to
say:
okay,
anyways,
but
that
that
is
basically
sitting
there.
The
pull
request
does
exactly
what
you
described.
Phil
adds
a
warning
to
the
status
report
and
it
changes
the
htaccess
file.
F
That's
in
the
out
of
box
to
fix
the
max
input
vars
for
people
running
backdrop
on
apache,
but
existing
sites
probably
won't
get
that
change,
definitely
not
automatically
and
yeah,
but
new
sites
won't,
hopefully
won't
be
affected
in
any
way.
F
C
Okay,
yeah
and
the
message
is
like.
It
also
leads
to
the
api
page
where
it
explains
how
things
are,
because
it's
not
only
apache
people
with
nginx,
like
we
don't
do
anything
for
with
people
running
on
nginx,
because
it
doesn't
work
with
hd
access.
F
Well,
let's,
let's
move
on,
we've
only
got
a
little
bit
of
time
left
these
next
five
issues.
We
don't
have
any
updates
on
so
unless
someone
has
a
something
in
particular,
they
would
like
to
note
about
them.
G
F
F
F
Let's
move
on
to
118
118
is
the
next
minor
version
of
backdrop.
It
will
be
coming
out
january,
15th
with
feature
freeze.
On
january
1st,
we've
had
some
updates
this
week.
The
link
sub
token
for
user
tokens
issue
4584
a
real,
simple
edition
that
adds
a
new
token
to
user.
To
you,
the
user
account
entities
gregory.
You
were
the
advocate
for
that.
Can
can't
give
us
an
update.
C
Yeah,
so
that
one
was
merged,
as
it
said,
so
I
can
now
move
on
to
the
next.
Wasn't
it
yes,
so
I
can
move
on
to
the
next
feature
for
an
eating
that
was
a
pretty
trivial
addition
like.
It
was
a
few
lines
of
code.
We
just
needed.
We
had
a
few
terminology
or
lingo
usage.
I
think
it
was
the
fact
that
it
was
mentioned
instead
of
mentioning
username.
We
said
login
name
or
something
like
that,
so
we
fixed
we
agreed
on
on
that
we
fixed
it.
F
Yeah
and
you
haven't,
I
looked
at
the
118
milestone
you
haven't
put
in
your
new
advocating
issue
yet
which
is
consolidating
the
available
updates.
I
think
into
one
single
page.
C
So
so
my
attention
was
drawn
with
the
help
of
others
in
the
queue
in
some
smaller
tasks
for
bug
fix
releases
which
I've
left
there
for
like
a
few
months.
So
I
started
looking
at
those
and
then
I
no
way
they
were
left
there
because
I
got
into
the
same
rabbit
holes,
but
it's
good.
I
like
that
so
I'll
finish
with
that
wrap
it
up.
Maybe
this
or
next
week
and
then
I'll
move
on
to
that
issue.
C
I
hope
to
get
it
no
I'll
push
myself
to
get
it
in
for
118,
because
it's
one
of
the
long-standing
issues
I
want
to
see
it
fixed.
F
All
right
next
up
is
webp
support,
a
new
image
format.
It's
issue,
4509
indigo
zella-
is
the
advocate
for
that
phil
claims
here
here.
Thank
you
for
doing
the
user,
testing
and
marketing
works.
For
me,
indigozala
marked
it
as
still
needing
code
review,
however,
so
that
seems
to
be
the
the
remaining
test.
I
think
they
were
hoping
for,
in
particular,
herb
dual
or
let's
see
herb,
duel
or
gregory
to
take
a
look
at
that,
because
they'd
already
done
a
review
once
before.
E
I
think
the
long-term
goal
is
to
convert
be
able
to
convert,
for
example,
upload
a
jpeg
it'll
save
the
jpeg,
but
then
also
convert
over
to
webp.
I
think
that's
kind
of
what
you
know
was
saying
his
long-term
goal
is,
but
outside
of
that.
E
I
was
kind
of
thinking
about
it.
I
probably
need
to
go
ahead
and
blow
my
sandbox
away.
Bring
in
core
do
some
testing
on
it
again
and
then
add
in
the
patches
and
make
sure
that
my
testing
is
legit,
but
from
what
I
could
tell
I
didn't
get
any
errors
or
nothing.
It
just
works
the
way
I
would
expect
it
to
work.
So
I
don't
think
I
have
any
other
issues
on
that.
B
C
E
Yeah,
I
probably
need
to
get
with
him
on
that.
I
think
my
only
issue
with
trying
to
kind
of
do
the
automated
thing
is
just
the
us
install
the
image
action
and
deal
with
creating
an
image
style
that
handles
all
of
that.
I
don't
like
that
from
a
ux
workflow,
so
I
don't
know
if
I
just
need
to
get
with
him
and
try
and
figure
out
a
better,
more
automated
approach
to
doing
web
f.
Doing
the
webp
and
and
honestly
webp
is
kind
of,
I
guess
in
my
back
pocket
too.
E
It's
something
that
I
have
wished
for
a
very,
very
long
time
that
the
drupal
handled
and
it
just
never
really
went
anywhere.
Well,
the
fact
that
he's
trying
to
get
this
going,
it's
it's
kind
of
near
to
me
as
well,
so
I'll
do
what
I
can
to
help
him
out
and
try
and
get
this
figured
out
from
a
ux
of
how
I
would
want
it
to
work.
If
you
know
if
this
thing
still
worked
the
way
I
wanted
it
I'll
I'll
try
to,
I
guess
get
my
input
on
that.
So.
G
B
It's
sad
for
yeah,
okay,
that's
probably
all
I
think
it's
basically.
It
sounds
to
me
like
it's
still
mark
this
works
for
me
and
yeah.
I'm
sorry.
I
just
wanted
to
make
sure
we
noticed
noted
that,
but
I
think
phil
got
it
covered.
F
All
right
next
up
upgrade
ui
jen.
You
were
taking
a
look
at
this
issue
of
making
it
possible
to
move
from
a
drupal
7
site
to
a
backdrop
site
through
a
user
interface
of
some
kind
that
wasn't
just
update.php.
F
Has
there
been
any
updates
on
that
initiative?
Sorry
that
issue
okay,
this
year
is
43.45
yeah.
This
is
kind
of
like
a
hypothetical
we're,
not
even
sure
if
this
will
work
issue,
but
lauren
you're
here
with
us
today.
Thank
you
and.
G
F
G
Yeah,
I
don't
I
don't.
I
actually
didn't
listen
to
last
week's
meeting,
so
I
don't
know
how
deeply
it
got
discussed,
but
the
gist
of
it
is
in
a
nutshell.
It
works
on
file
fields,
but
it
doesn't
work
in
the
ck,
editor
pop-up
and,
as
far
as
I
can
tell,
this
is
just
speculation,
but
when
it,
when
it
pops
up
in
the
ck,
editor
modal,
it's
like
a
form
within
a
form.
G
So
the
exposed
form
is
actually
inside
of
the
submit
form
for
the
modal,
and
I
think
that
causes
problems
and
I'm
not
sure
how
to
go
about
fixing
that.
So
when
you
submit
the
the
file
name
filter,
it
submits
it
to
the
the
ck
editor
form.
Instead
of
to
the
views,
exposed,
filter,
form.
F
Interesting
yeah
that
that
sounds
problematic,
interesting
interesting.
I
wonder
yeah
what
we
should
do
there.
Okay!
Well,
thanks
for
diving
into
that
and
figuring
out
that
context
of
why
that
problem
is
occurring,
also
very
interesting
that
it
only
happens
in
seek
editor
and
not
in
file
and
image
fields.
So
very
interesting.
D
F
Yeah
good
suggestion
that
was
fixed,
I
can't
remember,
I
think
I
fixed
it,
but
I
can't
remember.
F
F
46.63
bw
panda
is
the
advocate
for
that
one
and
there's
been
several
reviews
very
recently,
as
as
activists
today,
jen
and
indigozella,
both
posted
some
reviews
and
bw
panda
posted
some
responses
and
updated.
The
poll
request.
F
I
think
that
there's
the
ongoing
discussion
of
is
the
change
backwards
compatible
and
safe
to
include
or
not
jen.
Do
you
want
to
say
anything
about
that
issue,
since
you
are
the
one
that
looked
at
it
most
recently
from
those
present.
A
I
haven't
looked
at
it
since
peter's
last
change,
but
the
version
I
looked
at
before
that
was
going
to
break
all
existing
sites
that
had
overridden
the
style
sheet
and
so
he's
figured
out
a
way
to
change
it.
It
had
like
a
fundamental
rewrite
of
how
a
style
sheet
was
added,
which
is
super
dangerous
to
do
in
the
release,
and
I
think
he's
found
a
way
to
rework
it
so
that
he's
going
to
be
less
likely
to
break
all
the
current
sites.
F
F
C
B
F
Okay,
thanks
tim
and
lastly,
we
in
the
118
milestone.
We
have
advanced
caching,
such
as
adding
support
for
cache
tags
and
a
dynamic
max
age.
Cache
header
issue,
4127.
F
joseph,
is
the
advocate
for
that
one
currently
needs
work.
I
don't
think
that
there's
been
any
updates
in
the
issue
itself,
that's
it
for
the
118
list.
Do
you
guys
have
anything
you'd
like
to
mention
in
for
118
before
we
move
on
to
initiatives.
F
Okay,
we've
got
two
active
initiatives:
issues
initiatives
are
long-term
goals
that
might
not
necessarily
be
in
one
single
release
and
there's
two
of
them
right
now:
the
ready-to-wear
initiative
to
make
it
so
that
you
can
deploy
themes
without
doing
any
custom
coding,
that's
luke,
mccormick's
issue
or
he's
the
initiative
lead
on
that,
but
he's
not
present
today.
F
The
other
issue
that
we
have
is
telemetry
telemetry.
Well,
I
don't
even
need
to
summarize
it,
but
tim.
I
think,
you've
taken
that
over
from
jeff.
Are
there
any
updates
on
telemetry
this
week.
B
Not
really
I'll
just
say
that
the
current
status
is
really
in
testing
stage.
So
if
anybody
is
able
to
help
to
get
in
and
look
at
that
and
test
it,
I
think
we
also
have
to,
or
we
talked
about
creating
some
sort
of
follow-up
or
separate
issues,
but
we're
we
need
to
really
test
what
we've
done
so
far
and
I'm
trying
to
get
a
good
development
site
set
up
for
that
and
yeah.
And
I
and
I've
gotta
pass
the
roadblocks.
It's
just
finishing
the
process.
Finding
the
time
yeah.
F
And
we
have
some
obvious
enhancements
that
are
needed
in
the
module
to
to
make
it
so
that
we
can
enable
and
disable
the
collection
of
data
on
a
per
project
basis,
because
initially
we
want
to
make
it
so
that
we're
only
collecting
data
for
core
and
any
data
that
gets
sent
to
backdrop
cms.org
from
any
other
purpose
or
anything.
That's
not
supposed
to
be
saved
that
we
don't
save
arbitrary
data.
We
only
save
the
data
that
we're
expecting
so.
E
That's
it
can
you
on
this
telemetry.
I
actually
have
a
question
on
that.
It
just
kind
of
popped
in
my
head
last
night.
Is
that
mainly
just
to
collect
arbitrary
information.
F
Right
right,
yeah,
it
can
collect
arbitrary
information,
and
the
current
implementation
creates
a
hook
that
the
telemetry
module
itself
implements
its
own
hook.
That
collects
the
basic
information
of
your
php
version,
you're
my
sql
version
and
I
think
your
web
server
something
like.
G
F
F
We
want
to
make
sure
that,
on
the
server
side,
that
we
only
store
the
stuff
that
we're
expecting
and
that
way,
if
it
can
trip
modular
to
implement
this
hook
right
now,
it
wouldn't
act.
It
would
be
sending
us
data,
but
we
wouldn't
be
storing
it,
because
we
want
to
have
some
kind
of
process
around
like
making
sure
that
the
data
that
they're
collecting
is
acceptable
from
like
privacy,
standpoint
and
all.
G
F
Things
but
there's
not
actually
nothing
stopping
any
contrib
module
from
doing
any
kind
of
like
telemetry
or
check-ins
to
any
arbitrary
server
right
now.
But
this
we
don't
want
that
arbitrary
data
become
a
problem
on
our
side
that
if
we
start
collecting
personal
information
that
we
didn't
know
about,
then
we
could
cause
a
you
know:
legal
problems.
You
know
compatibility
with
safe
harbor
laws
and
stuff
like
that.
E
Well,
the
the
question
that
I
kind
of
had
on
that.
Is
it
worth
it
to
try
and
collect
a
list
of,
for
example,
php
errors
start
out
with
core
and
then
maybe
extend
that
into
contribs,
but
it's
it
might
be
a
good
tool
for
you
guys
where
you
know
100
sites
out.
There
are
all
getting
the
same
error,
but
nobody's
actually
reporting
the
error
back
into
the
issue
queue
and
so
yeah,
it's
kind
of
like.
Why
are
we
getting
all
of
these
errors?
What
what
what
is
this?
E
Maybe
we
need
to
look
into
this
and
try
and
figure
out
why
this
error
keeps
popping
up
on
all
of
these
sites?
But
I
I
don't
know
if
that
kind
of
goes
back
into
like
you
were
talking
about
the
privacy
or,
if
that's
going
to
end
up
generating
so
much
data
that
you
know
your
guys's
hosting
can't
handle
it
right
now
type
of
thing,
but
I
think
it
might
be
worth
kind
of
possibly
looking
into
adding
that
type
of
a
deal
in
the
future.
C
Yeah
yeah
so
go
ahead.
The
whole
the
whole
telemetry
thing
even
this
was
an
alternative
of
mine
that
started
back
in
the
drupal
days
and
in
the
original
issue
was
in
drupal.org
because
there
were
arbitrarily
decisions
being
made
like
some
person
would
come
and
say
nobody's
using
that
picture,
let's
remove
it,
but
that
they
didn't
have
hard
data
to
support
that.
C
So
the
telemetry
thing
started
off
of
that
it.
It
would
serve
as
a
means
for
us
to
make
decisions
when
it
comes
to.
You
know,
difficult
decisions
that
might
upset
the
community
and
we
need
hard
data
to
combine
it.
But
that's
an
interesting
idea
because
I
think
there's
a
module
that
actually
does
that.
C
So,
if
there's
a
new
release
that
goes
out,
it
sort
of
like
collects
similar
error
messages,
and
then
it
triggers
like
if,
if
there's
above
a
certain
limit,
it
sort
of
like
triggers
alerts,
but
telemetry
wasn't
built
for
that
in
mind
without
in
mind,
I
should.
F
Say
yep
good
summary:
there
gregory
that's,
not
really
like
solving
problems
that
might
be
occurring.
It's
like
getting
us
more
data
so
that
we
can
make
decisions
yeah.
C
H
So
this
is
my
breakpoint
module
thing.
H
H
Yeah,
so
jen
did
some
testing
and
found
a
way
that
it
does
break
existing
sites
if
they
override
something.
So
she
gave
steps
to
reproduce
that
I
was
able
to
reproduce
it.
I
found
and
fixed
the
problem
and
then
updated
the
pull
request,
and
so
now
it's
back
to
needing
review
and
testing
just
to
make
sure
it's
all
good
again.
It
doesn't
need
any.
I
mean
it
doesn't
break
any
existing
sites
since
what
we're
trying
to
fix
at
the
moment
so
yep
just
review
and
testing
needed
for
that.
F
C
Just
to
mention
that
at
some
point
there
was
a
documentation,
initiative
or
sort
of
like
it's
not
an
official
initiative,
but
it
was
discussion
about
it
becoming
an
initiative
because
documentation
is
an
ongoing.
I
think
it's
not
officially
in
the
agenda,
but
we
said
at
some
point
when
more
people
have
more
time
and
resources,
then
we'll
start
working,
putting
some
more
effort
to
it.
B
I
think
joe
might
have
come
to
the
meeting
with
some
items
too.
We
just
want
to
mention
that
go
ahead,
jen
or
phil.
E
I
got
I've
got
kind
of
a
brain,
fart
question
for
you
guys,
I
don't
even
know.
I
think
it
would
be
possible
to
do
this.
I
don't
know
the
ramifications
of
doing
this
from
a
coding
standpoint,
though,
and
I
think
the
idea
actually
came
when
I
started
playing
around
with
drupal
8
in
the
early
days
and
the
idea
was
to
move
a
lot
of
the
hard-coded
fields
out
of
being
hard-coded
into
actual
fieldable
fields.
E
So,
for
example,
the
url
turn
the
url
to
to
be
a
fieldable
field,
so
that,
if
you
want
to
add
a
url
to
a
block
and
then
have
an
actual
url
point
specifically
to
that
block,
you
can
or
to
a
paragraph
or
two
really
any
entity
some
of
the
things
I
think,
maybe
the
author
field.
Maybe
that
could
stay
hard
coded
or
you
know
some
still
stay
hard-coded.
I
try
to
basically
remove
some
of
the
hard-coded
fields,
make
the
entire
platform
more
flexible
in
how
you
want
to
actually
set
things
up.
E
I
know
the
whole
node
and
content
type
that
was
kind
of
you
know.
Drupal,
the
original
foundation
of
drupal
and
and
blocks
were
kind
of
the
original
foundation.
Then
drupal
7
came
along
and
it
turned
into
entities,
and
I
don't
know
I
just
kind
of
felt
like
we
were
pigeonholed
with
the
way
all
the
content
was
was
driven
with
the
nodes
and
everything
else.
It's
like,
why
not
turn
a
block
into
a
actual
page,
or
you
know
something
with
an
actual
url.
E
So
you'd
still
have
the
separation
of
your
back-end
url
the
system
url,
but
then
you
could
also
convert
other
entities.
Things
of
that
nature.
You
know
comment
fields
would
be
another
example.
Maybe
I
want
to
add
a
comment
field
to
a
block
or
something
of
that
nature.
So
again,
I
know
there's
a
lot
of
back
end
stuff,
I'm
just
flat
out
not
aware
of
that,
may
not
make
that
idea
possible,
but
I
just
kind
of
want
to
throw
it
out
and
see
what
your
guys
thoughts
were.
A
Yeah,
so
we
looked
at
that
a
lot
really
early
in
the
backdrop
life
cycle-
and
we
decided
that
for
backdrop
rather
than
turning
every
other
entity
into
a
node,
we
were
just
going
to
use
a
node
for
that
purpose.
So
we
included
what
was
a
module
called
rabbit
hole
in
drupal
7
that
allows
you
to
take
nodes
and
remove
the
url
for
them
and
make
them
like
we
call
them
page
list
nodes
so
that
you
can
have
a
node
type
called
block.
If
you
wanted,
that
would
have
comments
and
all
the
other.
A
You
know
publishing
options
and
translation
everything
this
way
the
same
way
in
node,
so
you
can
use
node
for
all
that
stuff
and
I
think
one
of
the
main
reasons
we
decided
to
go
that
way
is
because
there's
so
much
support
in
kindred
for
nodes.
A
So
all
of
the
things
that
you
might
want
to
do
to
nodes
you
might
want
to
do
to
all
those
node
like
things
also
that
it
just
made
more
sense
to
use
all
the
things
that
we
knew
would
work
rather
than
trying
to
create
a
new
entity
for
a
block
that
maybe
doesn't
have
translation
or
doesn't
have.
You
know
all
of
the
stuff
that
already
works
on
nodes.
E
A
Just
like
complexity,
I
think
people
they'll
get
their.
A
Every
piece
of
content
is
a
node,
even
if
sometimes
the
content
is
placed
like
a
block,
or
sometimes
it
has
a
page
and
conceptually
it
just
made
more
sense.
But
yeah
I
mean
we're
sort
of
in
this
world
where
in
drupal,
6
node
was
content
and
then
dribble
8
entities,
content
and
we're
kind
of
in
the
middle,
where
we
have
like
entity,
content
in
node
content
and
blocks
aren't
entities,
but
other
things
are
fieldable.
A
So
yeah
I
mean
it's
a
little
bit
sort
of
up
to
the
site
architect
to
decide
how
to
solve
that.
It's
a
problem
on
any
site,
but
we
did
put
rabbit
hole
in
core
with
the
hopes
that
the
standard
would
be
that
nodes
would
be
content
and
anything
that
you
need
for
content
can
apply
to
any
node
type,
regardless
of
how
you
treat
it
like
it
could
be
a
slide
in
a
slideshow.
It
doesn't
have
a
page
on
its
own,
but
it's
got
fields
and
it's
got
translation.
It's
their
comments.
If
you
want
them.
C
Yeah
just
telling.
D
D
Yeah,
by
the
way,
I
often
thought
about
it
so
about
the
implementation
of
rabbitool
and
corn.
I
use
it
also
a
lot,
but
I
think
there
are
not
many
people
aware
of
it,
and
so
once
I
had
the
idea,
if
we
maybe
ship
backdrop
with
the
third
content
type,
a
block-like
one,
to
make
people
aware
of
these
really
huge
possibilities
of
that.
C
So
really
often
often
used
solution.
Sorry,
implementation
of
that
is
slides
and
slideshows.
So
people
want
to
create
slide
blocks,
I
would
say,
but
they
don't
want
people
to
necessarily
be
able
to
access
its
individual
slides.
A
C
It's
something
that
people
yeah
people
request
a
lot
so
yeah.
So
by
the
way,
there's
four
fields
benefit.
There's
a
forum
topic
that
was
started
by
me.
It
was
sort
of
like
a
rhetorical
question:
thingy
with
titled.
What
can
people
do
in
triple
eight
and
nine
with
buildable
blocks,
which
can
which
is
not
possible
in
backdrop,
and
then
everyone
jumped
and
said?
Oh
you
know
what
the
rabbit
hole
solution
is
so
much
easier
and
it's
like.
I
don't
know
what
triggered
that
question
that
I
had.
C
Maybe
I
was
watching
a
tutorial
on
something
like
really
old
and
simple,
bending
that-
and
I
said
why
aren't
we
doing
that
and
then
I
tried
playing
as
well,
and
I
figured
out
that
we
can
do
pretty
much
whatever
that
tutorial
was
doing
without
having
those
features
so
yeah
I'll
provide
a
link
to
that
blog
post,
because
there's
other
people
that
chimed
in
and
it's
like
useful.
So
for
your
benefit
phil.
I
just
put
it
put
a
thing
in
the
in
the
zoom
chat
here.
E
The
only
other
thing
I
was
going
to
bring
up
you
know
I
put
that
issue
out
there
for
brockley
at
this
point
in
time.
E
Yeah
that
sent
me
down
a
rabbit
hole
of
information
that
I
just
was
not
prepared
for
and
dealing
with
broccoli,
and
I
would
honestly
say
at
this
point
when
you've
got
time
to
mess
with
it
and
look
into
it
mess
with
it.
Then
you
know
I'm,
I
I
don't
think,
that's
anything
that
we
need
to
try
and
deal
with
right
now.
You
guys
have
enough
on
your
plate,
but
I
think
that
at
some
point
down
the
road,
I
think
it
would
be
worth
trying
to
look
into
using
that.
E
I
don't
know
if
you
guys
are
familiar
with
broadly
it's.
Basically,
the
the
new
format
for
gzip
google
came
out
with
it
2013
it
compresses
most
your
stuff
give
or
take
by
about
five
percent
more
than
what
gzip
does
so
there.
There
is
an
issue
we're
going
to
get
committed.
That
will
fix
a
problem
that,
if,
if
bradley,
is
enabled,
for
example,
mod
bradley
is
enabled
for
apache
that
it
causes
problems.
I
think
we'll
be
getting
that
put
in
pretty.
E
To
resolve
that
which
is
good,
but
as
far
as
doing
it
on
the
fly
doing
a
pre-compress,
I
I
mean
there's
going
to
be
a
lot
of
work
involved
to
try
and
pre-compress,
and
I
think
right
now
it's
it's
not
even
worth
looking
into
doing
pre-compress
on
using
broadly
so
maybe
down
the
road.
Somebody
can
come
up
with
an
easier
way,
but
right
now
I
think
it's
going
to
be
too
complicated,
even
trying
to
mess
with.
C
Yeah
I
saw
that
issue
and
then
backboarding
the
fix
that
that
that
prevents
that
error,
which
sounds
that
it
might
become
a
what
you
call
it
a
more
frequent
than
we
would
like
thing
situation.
I
think
that
we
should
do
that.
The
rest
of
it
sounds
like
a
little
bit
of
work
and.
G
C
E
There's
yeah,
if
you
do
some
google
searches
for
bradley
a
lot
of
big
key
players,
cloudflare
key
cdn,
there's
a
lot
of
big
companies
that
they're
touting
it
talking
about
the
benefits
I
mean
it
has
it's
been
around
for
quite
a
while
now
already,
but,
unfortunately,
the
ease
of
use.
E
You
know,
for
example,
I
use
cpanel
for
my
hosting
platform.
I
have
to
actually
try
to
go
download
a
php
extension
get
that
installed
in
cpanel.
You
know
so
it's
it's
not
for
the
faint
of
heart
to
actually
get
the
binaries
to
get
everything
on
the
server
in
order
to
do
the
pre-compress.
So
I
think
until
until
that
becomes
more
popular
or
there's
a
way
of
doing
that
without
needing
third-party
binaries
or
something
I
I
don't
even
think
it
could
be
done.
E
I
think
you've
got
to
have
either
a
php
extension
or
be
able
to
have
access
to
the
binaries
to
make
it
work
so
yeah
we
can
kind
of
put
that
issue
as
far
as
including
the
pre-compressed
side
of
the
broadly.
We
can
put
that
on
the
back
burner.
So
sorry,
for,
I
guess,
bringing
up
kind
of
a
weird
little
issue
there
I'll
try
to
refrain
from
that
in
the
in
the.
C
E
F
Cool
well
we're
past
time.
I
think
let's
maybe
wrap
it
up
for
this
week.
Thank
you
guys,
all
for
joining
it's
exciting
to
see
the
different
crews
coming
in
people
updating
on
their
initiatives
that
are
updating
on
their
advocate
advocated
issues.
It's
highly
appreciated
when
you
guys
are
present
for
the
meetings
and
thank
you
guys
all
right.