►
From YouTube: Backdrop Weekly May 10th
Description
Today’s development agenda: https://bit.ly/2wxVxhA
A
All
right
we
are
on
air,
just
Thursday,
May
10th.
This
is
a
meeting
to
check
in
on
active
development
tasks
for
backdrop
CMS.
Before
we
get
into
that,
though,
we
have
a
very
exciting
announcement
from
the
PNC
backdrop
was
officially
adopted
as
a
project
for
the
software
freedom
Conservancy
this
week,
I'd
like
to
say
thank
you
to
Matthew
Tift,
who
I
believe
Nate
Kirkman
I'm
around.
A
He
recommended
this
offer
freedom
Conservancy
to
us
maybe
three
years
ago,
helped
you
a
good
place
to
go
so
I'm
really
excited
that
we
were
finally
able
to
make
that
happen.
They
wrote
a
blog
post
this
week
about
it.
I
have
a
meeting
with
our
team
next
week
to
send
out
a
newsletter.
If
anybody
wants
to
write
a
blog
post
about
that
before,
then
that
would
be
fantastic.
A
It
should
probably
be
something
like
what
it
means
for
backtracked
to
be
part
of
the
Conservancy
and
for
somebody
to
write
that
post
it
might
require
doing
a
little
research
of
like
looking
at
all
the
awesome
things
the
Conservancy
can
provide
for
us,
so
it
could
take
some
time,
so
don't
volunteer
for
it.
Unless
you
are
willing
to
interested
and
willing
to
do
that,
research,
but
the
primary
things
are
people
who
make
donations
to
backdrop.
Those
are
now
text
adaptable,
which.
A
On
the
backdrop,
CMS
org
website
the
contribute
page
I've
already
swapped
out
the
donate
button.
That's
the
top
one
on
that
page
with
one
that
goes
to
Conservancy,
and
people
will
get
excellent
deductible
donations
for
that
one.
If
people
want
t-shirts
and
hoodies
that
form
that
we're
using
to
let
them
special
specify
what
size
and
style
they
want
is
still
our
form
so
I'm
working
with
the
Conservancy
to
get
a
custom-made
form
to
replace
the
one
that
we
have
now.
The
button
was
easy.
C
A
Anything
anywhere
you
think
we
should
include
it
I
think
that
would
be
valuable
in
that
broad
sections,
a
good
place.
We
also
mind,
if
want
to
add,
like
a
standalone
page
about
the
Conservancy.
If
we
have
enough
information
for
that,
so
I'm
definitely
open
that
and
in
general
we
have
a
lot
of
editors
on
the
backdrop,
so
you
must
at
work
site
that
have
good
ideas
about
where
content
should
go.
A
There's
issues
in
the
Q
about
like
pages
we
might
want
to
add
and
like
create
an
issue
recently
and
think
you
waited
on
us
about
wanting
to
put
a
security
page
I'm
totally
in
favor
of
doing
that.
We
just
need
someone
to
write
the
content.
So
if
anyone
who's
a
content,
editor
on
the
site
wants
to
make
a
page
in
write
the
content
anytime,
that's
really
fine!
If
you
want
to
review
first,
just
leave
it
unpublished
and
put
a
link
somewhere.
C
Maybe
Nate
can
you
just
start
a
place
just
with
filling
in
the
details
of
what
you're
always
because?
Oh
because
I
don't
know
what
what
what
work
is
involved,
how
things
are
coordinated
and
then,
if
you
are
this
really
laughs,
then
then
one
of
us
can
jump
in
and
then
fill
in
the
gaps.
It's
just
that
we
don't
know
the
internals
of
health.
Things
are
coordinated
or
with
details
can
go
public
on
it.
D
A
D
A
A
A
Support
it,
which
is
great
now
we're
gonna,
have
it
they've
been
running
it
in
production
for
a
while
and
it's
a
fun
well
so
they're
contributing
to
backdrop.
So
thanks
to
that
team
for
getting
that
done,
which
is
great
on
our
websites,
the
forum
site
is
about
to
get
some
updates.
We
discussed
them
in
more
detail
in
the
design
and
usability
meeting
we
just
had
over
the
last
hours.
So,
if
you're
interested
in
seeing
all
the
stuff
we
talked
about
there
to
encourage
you
to
watch
that
video,
we
probably
shouldn't
go
into
them
again
here.
D
D
D
This
issue
is
issue
2904,
where
we
have
a
workarounds
still,
but
we
need
to
expose
to
the
user
the
fact
that
there's
a
problem
that
they
need
to
fix,
I
posted
a
comment
to
the
issue
saying
how
I
think
we
could
go
about
that,
but
we
haven't
updated
the
implementation.
Yet
it
looks
like
John
Franklin.
It
does
a
lot
of
these
awesome.
Back-End
issues
gave
it
the
thumbs-up
at
least
conceptually.
So
it
looks
like
you
know.
It
seems
like
it's
a
good
idea
or
good
approach.
D
Let's
see,
there's
also
a
bunch
of
other
items
in
the
1.9
point.
6Q
we've
actually
been
knocking
a
lot
of
them
out,
as
we
do
a
lot
of
code
review,
so
we've
got
a
number
of
them
that
got
knocked
out.
Some
promises
table
select,
jQuery
form,
j/s
fix
some
problems
with
color
module
updates
for
PHP
7.20.
Thank
you
very
much
to
oppose,
if
or
Joseph
for
doing
that
issue.
D
That
makes
it
so
that
backdrop
is
now
fully
compatible
with
PHP
7.2,
which
previously
it
would
run,
but
through
some
exceptions
in
in
edge
cases
and
now
in
1.9
point
6.
It
should
be
fully
a
PHP
7.2
compatible.
So
thank
you
very
much
for
the
work
they're
importing
that,
let's
see
I'm
not
gonna,
go
through
all
of
the
other.
D
One
point:
nine
point:
six
issues:
we
do
have
27
open
issues
in
that
tag
of
just
things
that
they're
really
more
like
high-priority
bug
fixes,
but
none
of
them
particularly
critical
outside
of
that
2904
issue
for
database
credentials.
So
you
skin
abyss
directly
to
check
out
those
items
and,
of
course
anything
that
we
fix
in
1.9
point
6
will
also
be
in
the
one
point
10
release.
D
D
D
But
the
problem
is:
is
that
makes
it
hard
for
users
to
log
into
their
site
if
they,
if
it's
not
usable?
So
we
want
to
make
it
so
that
the
site
is
still
functional
if
users
update
to
one
point
ten,
so
that
they
can
log
into
it
and
then
visit
update
dot
PHP
so
that
asu
3100
is
basically
find
a
way
to
work
around
the
menu
updates,
not
the
menu
updates,
but
the
the
menu
queries
from
completely
breaking
the
site
and
then
once
update
dot
php'
is
run.
D
Then
it
just
starts
using
the
new
column
so
that
one
I
filed
is
a
bug.
I
mean
but
I,
don't
know
it's
it's
a
little
bit
fuzzy
as
to
if
it
would
actually
be
a
bug,
because
it's
the
behavior
of
backdrop,
but
it's
definitely
something
that
we
want
to
smooth
that
upgrade
process
and
I
feel
like
every
time
we
introduce
a
little
bump
like
this.
It's
ruining
people's
confidence
and
in
our
backwards-compatibility
policy
and
making
it
easy
to
update
and
upgrade
and
maintain.
D
Next
item
is
a
block
translation
issue
29:56
we
merged
this
on
code
freeze
day
and
there's
no
updates
there
that
one
still
looks
great,
of
course,
if
anybody
that
wants
to
please
install
the
1.10
or
the
one
dot
x.
Ladies
def
version
and
try
it
out.
Block
translation
is
new
and
it
does
have
test
coverage.
But
you
know
once
it
hits
actual
usage,
probably
finds
new
problems.
D
D
Let's
see
improvements
to
modules,
themes
and
layouts,
there's
been
some
other
issues
that
we
have
completed
in
here,
but
they've
been
removed
from
the
agenda
for
brevity.
That
one
issue
that
still
opened
here
is
issue
37,
which
is
making
it
so
that
modules
can
expose
tags.
In
addition
to
categories
the
status
of
this
one
is
that
it
still
needs
feedback.
There
still
isn't
we
don't
reach
total
consensus
there
as
to
the
usefulness
of
the
functionality
and
how
it
should
work
and
also
code
wise.
It
meets
some
iteration
there.
D
This
one's
as
far
as
features
are
concerned
is
probably
the
only
thing
that
is
still
like,
potentially
out
there.
For
one
point,
ten
might
happen
as
a
user
experience
feature
it's
exempt
from
the
feature
freeze
as
long
as
it's
limited
in
scope
and
low
impact,
as
far
as
likelihood
to
break
the
site.
So
it's
still
possible
to
get
that
in
for
one
point
ten,
but
we
need
to
get
things
figured
out
and
resolve
kind
of
our
differences
there
quickly.
For
that
one
to
happen.
D
Let's
see
other
features
for
one
point:
ten
going
through
the
ones
that
got
in
common
closer.
We
added
this
capability
in
issued
three
thousand
and
one
to
make
it
so
that
you
can
now
schedule
per
content.
Type
say
automatically
closed
comments
after
X
number
of
days
like
fourteen
days
and
then
after
content
is
existed
for
fourteen
days.
Comments
will
automatically
be
closed
on
that
issue.
D
To
prevent
spam
from
coming
in
on
legacy
content,
I
filed
a
follow-up
on
this
one
issued
3102,
which
is
making
it
so
that
the
check
box
that
we
have
on
the
the
node
forum
for
automatically
closed.
In
the
comments
you
can
per
node
allow
the
comment
closer
to
be
enabled
or
disabled,
and
the
UX
around
that
check
box
right
now
is
is
rather
poor
and
so
I
filed
a
suggestion.
There,
just
flipping
away
around
the
way
that
we
use
the
check
box
on
the
node
forum
to
enable
and
disable
the
overwriting
of
the
comment
closure.
D
So
please
take
a
look
at
that
one
that
one
needs
some
feedback,
at
least
on
the
suggestion
of
the
implementation
there
and
then,
if
we're
in
agreement,
we
can
move
forward
and
and
change
the
way
that
checkbox
works,
which
is
pretty
trivial
as
far
as
code.
But
it's
a
it's
a
mentality
flip
on
the
way
that
works.
D
There's
issue
3073
that
when
we
introduced
the
scheduler,
we
use
the
date
modules
date,
popup
field,
which
introduced
a
coupling
or
a
dependency
on
date.
Module
now
note,
module
effectively,
depends
on
date,
and
so
there's
a
couple
of
ways
that
we
can
fix
that
problem
or
we
could
just
make
it
so.
The
date
becomes
a
required
module
to
match
no
to
module,
but
there's
a
pull
request
in
that
issue
that
makes
as
the
if
date
module
is
available.
It
uses
the
date
field.
D
D
D
So
please
take
a
look
at
those
issues.
There's
only
one
poor
request
that
fixes
both
of
those
problems
and
one
of
them,
the
author
Don
feel
getting
fixed
would
be
nice.
That's
been
a
long-standing
issue
and
then
fixing
the
new
scheduled
date
would
also
in
many
ways
almost
imperative
that
we
figure
out
one
solution
or
the
other
for
when
1.10
is
released.
D
Okay
and
lastly,
in
the
world
of
features,
is
the
ability
to
upload
files
through
the
seek
editor
link.
Dialog,
that's
issued
2072,
no
updates
on
that
one
that
one
has
been
merged
and
is
complete
and
we'll
just
pull
out.
Another
request
for
additional
testing
like
please
try
out
the
1.10
dev
release,
which
is
actually
is
the
latest
of
release
and-
and
let
us
know
if
there's
any
problems
with
the
SI
Cavender
link
dialog
right
now
we
haven't
all
tested
manually.
D
D
D
Olaf
has
reviewed
it
and
I'm
tempted
with
his
review
and
my
own
to
go
ahead
and
merge
that
one
there's
an
ability
to
add
search
options
to
configuration
options
to
the
search
block,
a
change
to
the
way
comments
are
nerd
on
nodes
to
make
it
so
that
you
don't
end
up
with
empty
markup,
and
that's
it
so
yeah
well,
I
mean
we've
only
got
five
days
until
release
and
we've
got
about
seven
or
eight
open
issues
that
we'd
like
to
get
completed
before
that
date.
So
timeline
wise,
were
in
real
great
shape.
A
D
That's
it
for
1.10.
It's
really
exciting,
just
a
couple
days
away,
we're
in
really
great
shape,
I
think
for
1.10,
and
the
best
thing
that
we
can
ask
our
community
members
to
do
is
to
try
it
out
far
out
the
one
not
x-step
release,
and
let
us
know
if
you
encounter
any
problems
and
if
you
do
file
an
issue
in
the
the
kid
hub
issue,
queue
attack
it
for
1.10.
D
D
A
D
C
D
Looked
at
it,
I
read
it
over
their
press
release
and
the
functionality
and
everything
like
that
and
looked
neat
I
I.
Don't
I
didn't
do
an
evaluation
as
to
how
drastically
it
breaks
their
api's,
although
I'm
certain
that
it
does.
Hence
the
the
major
version
bump
so
I'm,
not
quite
sure
what
that
means.
For
us,
I
mean
I,
haven't
seen
I,
guess:
there's
imce
module,
but
I
haven't
seen
a
lot
of
controls
that
have
you
know,
built
out.
C
Yes,
I
mentioned
it,
because
I
was
kind
of
over
what
what
video
was
watching.
Maybe
was
a
presentation
from
Mossville
and
they
were
mentioning
it
and
it
brings
out
all
of
the
functionality
that
is
now
in
BH,
quick
edits.
We
carried
module,
I
think
come
on
I
think
they
have
a
quick
edit
module
sort
of
like
in-place
editing,
something
like
that
and
WordPress
is
also
working
on.
They
have
the
new
Guttenberg,
whatever
they
call
it
an
editor.
So
that's
why
I
mentioned
it.
Yeah.
D
One
thing
I
saw
in
it
that
looks
appealing
to
me:
they
have
a
functionality
that
mirrors
that
of
of
Dropbox
paper,
where
you
basically
use
more
down,
but
as
you're
typing
the
markdown,
it
automatically
converts
it
into
the
display
style
HTML.
So
you
can
do
like
you
know,
hash,
sign
and
then
space
and
then
start
typing
and
it'll
automatically
convert
that
to
an
h1
or
a
back
tick
box.
Check
back
to
can
automatically
turn
that
into
a
code
tag.
That's.
D
And
that's
the
funny
thing
is
that
another
thing
why
we
shouldn't
move
to
one
or
two
5.0
yet,
as
they
specifically
noted
that
their
paste
from
word
functionality
doesn't
work
in
five.
Yet
so
I
think
we'll
have
to
wait
on
that
before
before
we
even
consider
moving
to
five,
because
that
is
kind
of
a
key
thing
that
if
they're
paste
copy
paste
functionality,
it
doesn't
adequately
strip
stuff
out
like
coming
from
external
sources.
Then
that
would
be
a
big
grievance
for
for
many
users.
A
We
might
want
to
mention,
though,
is
that
right
now
the
version
we're
running
seek
editor
is
unsupported
and
so
probably
still,
and
they
had
a
security
release.
We've
had
to
patch
the
version
walk
around
you,
so
it
might
be
valuable.
Even
if
we
don't
move
to
five.
If
we
move
to
a
version,
that's
supported,
then
that
way
will
be
easier
to
apply,
unlike
security
fixes,
yeah.
D
We're
using
were
actually
using
seek
editors
image,
caption
support
functionality,
but
we
the
part
that
we
have
customized
this,
just
the
dialogue
for
configuring,
the
image,
but
when
it
comes
to
the
actual
display,
that's
that
CK
editor
image
to
plug-in
native.
So
we
actually
have
very
little
modification
on
that
area.
D
Yeah
I
saw
that
I'm
not
quite
sure
what
to
make
of
it
that
yes,
so
they
have
Google
Docs
like
functionality
or
Google
or
Dropbox
paper
functionality,
where
you
have
multiple
people
typing
at
the
same
time,
and
it
shows
you
where
the
cursors
are
and
highlights
who's
who's
typing.
What?
But,
obviously
that
requires
a
server
side
component
and
they
have
smartly
made
that
into
a
business
offering
where
you
can
just
pay
them
and
they
will
host
the
service
of
the
collaboration
capability.
D
But
considering
the
rest
of
the
content
form
wouldn't
have
that
same
functionality.
It
would
make
kind
of
an
awkward
fit
I
kind
of
feel
like
that's
something.
It
would
be
like
an
awesome
weekend
trip
solution
until
we
figure
out
if
it
makes
any
sense
at
all
being
in
court,
we're
considering
it
probably
have
a
dependency
on
their
servers
or
some
kind
of
specialized
server
configuration
on
the
hosting
side.
I'm
feeling
that
would
be
difficult
for
us
to
support
directly.
D
D
The
jQuery
update
is
still
actually
Mike
can't
think
you
brought
this
up
recently
as
well,
but
it's
not
enough
the
the
upgrade
that
there's
a
pull
request
for
it's
just
upgrading
to
the
latest
version
of
jQuery
UI,
not
the
latest
version
of
jQuery
itself.
So
we're
still
on
the
1.10
release,
which
is
the
last
release
of
the
one
point.
D
It's
a
difficult
transition
and
I'm
not
sure
how
we
can
handle
that
as
far
as
backwards
compatibility
is
concerned,
I
think
my
preferred
route
on
this,
for
the
time
being,
would
be
finding
a
vendor
that
has
continued
to
support
the
jQuery
one
dot,
X
version
for
security
fixes
and
start
using
their
a
fork
event
that
has
security
updates,
because
there
just
has
to
be
a
vendor
out
there.
That
is
providing
support
for
a
library
that
is
installed
on,
like
one
third
of
the
entire
Internet.
D
C
C
Not
doing
it
and
actually
people
are
using
jQuery
update,
it
breaks
a
lot
of
the
admin,
not
a
lot,
but
quite
a
few
of
the
admin
back
end
up
at
the
four
themes:
yeah
and
certain
modules,
not
working
that
you
have
some
weirdness.
That's
why
there's
even
options
to
select
which
the
cohesion,
its
theme,
or,
at
least
between
admin
and
sound
and.
D
Yeah,
it
actually
kind
of
brings
up
the
need
that,
like
it,
was
great
for
a
while
there
that
we're
running
the
latest
version
of
jQuery
without
really
any
problems.
But
now
because
of
the
compatibility
breaks,
we
may
find
ourselves
in
a
position
where
J
query
update
needs
to
exist
as
a
contributor
again,
so
that
we
can
have
backdrop
one
dot,
X
sites
that
can
run
jQuery
three
dot
X,
if
they,
if
they
want
to,
is.
C
D
E
E
E
D
You
know
all
of
the
event
named
ones,
but
it
used
to
be
in
an
earlier
version.
Jquery
that
introduced
bind
is
being
a
superior
way
of
doing
event
handling,
but
then
later
they
introduced
a
more
superior
way
of
doing
event,
handling
called
on
and
so
dot
on
is
still
there
and
the
most
recommended
approach
to
event
handling.
But
click,
which
is
the
simplest
way
to
event
handling,
is
still
there
but
bind
which
is
kind
of
the
middle
away
of
doing
event,
handling,
they've
removed
and
so
I
would
bet.
E
D
So
so
that's
the
thing
is
that
you
could.
There
is
a
library
that
adds
back
the
deprecated
functionality
for
jQuery
3.
But
then,
if
you
upgrade
to
the
next
version,
they
also
had
API
breaks,
apparently
in
between
jQuery
3
and
gosh.
I
need
to
know
what
the
current
version
is:
3.2,
even
matter
their
compatibility
library
yeah.
D
They
have
to
have
had
changes,
which
is
not
good
that
we're
supposed
to
stop
doing
that
when
they
suppose
the
derivative
following
semantic
versioning
right,
but
there's
differences
between
3
and
3.2,
and
that
requires
a
different
compatibility
library
and
you
can't
just
load
both
compatibility
libraries
and
go
from
1
to
3
point
to.
You
can
only
go
from
1
to
3,
use,
one
compatibility
library
and
then
once
you
get
up
to
grade
into
three,
then
you
can
go
from
3
and
3.2
with
another
compatibility
library,
but.
C
C
D
Yeah
yeah
just
doing
a
search
there
code
base.
We've
got
lots
of
occurrences
of
some
deprecated
functionality,
so
I
did
the
first
thing
we
should
do
before.
Anything
else
is:
go
through
our
code
base
and
update
all
of
it
to
not
use
any
of
the
deprecated
functionality.
According
to
the
latest
version
of
jQuery
yeah
they're,
all
the.
E
E
E
D
C
D
So
I
think
in
1
dot
X.
Our
path
here
is
restore
jQuery
update,
module
make
it
so
jQuery
update,
can
swap
out
to
jQuery
3x
and
then
make
sure
the
core
works
with
jQuery
3
dot
X.
So
we
can
use
jQuery
update
module
to
like
suss
out
any
problems
of
things,
but
I
mean
also
just
doing
a
finding,
replace
and
search
that
the
codebase
would.
Okay.
E
Here's
a
question
for
you:
would
we
perhaps
would
we
want
to
add
a
jQuery
update
into
core
as
like
a
jQuery
switcher
and
switched
core
and
ship
core
with
two
versions
of
jQuery
and
the
ability
to
switch?
So
when
people
upgrade
their
site,
it
stays
on
one
branch,
but
any
new
installations
go
to
the
three
branch.
C
I,
wasn't
thinking
exactly
that,
that's
something
like
that!
So
if
we
ship
CD,
always
the
issue
that
I
bring
up
with
experimental
modules
for
d8
the
thing
that
they're
using
it,
if
we
could
add
that
as
an
option,
we
could
allow
the
risky
guys
or
people
that
are
willing
to
help
like
such
as
myself.
You
know,
I'd
have
something
like
that:
I'd
just
flip
it
to
three
decks
and
try
to
see
if
there's
anything
broken
and
then
I
reported.