►
From YouTube: Backdrop Weekly - Nov 1st
Description
Today’s development agenda: http://bit.ly/2pZ1qhy
A
All
right
we're
on
air,
it
is
Thursday
November
first,
and
this
meaning
is
to
check
in
on
active
development
tasks
for
backdrop
CMS
before
we
get
into
the
product
itself.
A
quick
update
from
the
project
management
committee
Kevin
a
couple
weeks
ago
asked
us
to
evaluate
our
King
tread
licensing
situation
so
that
we
could
specifically
support
GPL
3
in
contribute.
We
needed
to.
We
raised
that
to
a
vote
for
the
PMC.
A
What
we
need
to
do
in
order
to
make
that
clear
to
people
about
what's
going
on,
is
to
update
the
documentation,
for
example,
to
read
me
in
the
contribute,
so
that
everybody
knows
that
they're
allowed
to
use
GPO
3
and
make
it
clear
that
our
preference
is
silver
GDL
2,
so
that
if
a
project
gets
slated
for
core,
we
can't
include
it.
A
GPL
3
project
cannot
be
included
in
that
report.
A
A
A
If
you're
interested
in,
what's
going
on
in
backdrop
semester
org,
we
did
talk
a
little
bit
about
content
in
the
last
meeting
for
last
hour
on
community
outreach,
but
I
did
want
to
mention
that
the
module
since
and
layouts
pages
are
searched.
There's
not
currently
working
and
I
have
a
task
myself
today
to
get
the
search
so
that
the
results
to
come
back
in
the
right
order,
but
there's
a
bunch
of
other
changes
that
we
want
to
get
worked
on
there
too,
and
those
could
take
volunteer
time
if
possible.
A
C
C
So
it's
on
through
the
agenda
here,
which
is
probably
going
to
be
similar
to
our
giri's
update
last
week
anyway,
but
most
of
the
activity
looks
like
it's
happened
about
10
or
11
days
ago.
So
we'll
recap
so,
let's
see
actually
is
this.
Is
this
right,
I
think
we're
currently
actually
on?
We
have
one
dot
11.3,
exactly
one
dot.
11.2
came
out
a
couple
of
weeks
ago.
C
1.11
is
the
current
release
of
backdrop,
and
one
11.3
is
the
next
bug
fix
release
that
will
be
coming
out
once
we
have
some
issues
corrected,
so
we've
got
a
couple
of
regressions
or
things
that
could
be
tidied
up
since
1.11
was
released.
One
of
the
new
features
in
1.11
was
enhancements
to
the
color
module
and
to
the
basis
thing
to
make
it
colorize
a
bowl,
and
so
we
have
two
issues
related
to
that
3209,
which
is
adding
predefined
color
schemes
for
basis
this
one
there
hasn't
been.
C
It
would
be
worthwhile
if
we
could
reach
out
to
Wes
again
to
have
him
take
a
look
at
the
color
scheme.
So,
as
the
original
author
of
the
basis
thing
to
get
his
input
there,
let's
see,
we
also
have
an
issue
with
the
color
preview.
It
doesn't
work
correctly
in
Safari
and
that
issue
is
3295.
We
don't
have
any
current
updates
on
that
I.
C
Don't
think,
there's
even
been
any
efforts
to
correct
it
thus
far,
but
anyone
looking
for
a
moderately
important
issue
to
fix
a
bug
that
would
be
appreciated
to
have
a
dev
take
the
lead
on
that
one.
Let's
see.
Lastly,
a
regression.
The
new
info
status
message
affects
the
available
updates
page
in
a
negative.
C
B
B
C
Super
yeah,
this
looks
like
it's
been
available
for
Earth
have
been
open
for
a
while
already
I
love
it.
When
we
can
figure
things
out,
that's
it
really
interesting.
You
know.
Actually
it's
really
interesting.
We
added
similar
problems
that
you
know
recently.
We
made
it
so
that
we're
supposed
to
be
trying
both
local
host
and
127.0.0.1
and
using
the
one
that
works,
but
it
looks
like
maybe
we're
not
checking
for
the
failure
condition
quite
correctly
there.
Okay,
that's
that!
Yes,
things
like
this
that
make
it
so
the
Installer
throws
fewer
errors
that
are
really
valuable.
C
C
All
right,
let's
say
next
up-
is
1.12
1.12,
be
the
next
minor
release
that
will
come
out.
January
15th
2019,
although
it
seems
like
that's
still
a
little
ways
away.
We
are
heading
right
into
crazy
holiday
time
and
if
last
year
was
any
indication
that
frequently
means
that
kind
of
wants,
Thanksgiving
hits
things
become
a
little
nebulous.
Sometimes
we
have
like
mad
rushes
of
development
work
because
people
have
lots
of
holiday
and
sometimes
people
actually
use
their
holiday
like
they're
supposed
to-
and
it's
a
nice
quiet
time
in
the
world
of
backdrop.
C
But
we
have
a
number
of
things
that
have
actually
been
in
really
there
already
a
really
strong
position,
because
there
were
things
that
were
nearly
completed
in
the
last
release
and
of
those
we
will
go
over
all
of
them.
This
one
not
super
solid,
but
still
has
a
lot
of
progress
and
that's
automatic
updates
automatic
updates.
We've
got
a
meta
issue
at
2018,
a
creator
again
that
backdrop
1.11.
C
The
current
version
has
the
ability
to
update
itself,
but
we
disabled
that
ability
in
the
user
interface
and
now
it's
been
confirmed
by
myself
and
preggers
I
know
you
try
it
out
as
well.
Jeff,
probably
also
like
everybody's,
tried
updating
their
locals
using
the
core
self
updater
mechanism
with
success,
which
is
great,
but
the
next
step
that
we
have
is
to
expose
that
ability
to
update
and
potentially
automate
it,
and
that
issue
is
414
and
Gregory.
You
were
the
last
one
to
take
a
look
at
it.
Could
you
give
us
an
update
on
your
findings?
C
B
Yeah
sure
so
there's
a
related
issue,
which
is
to
remove
the
authorized
PHP
entirely
during
my
testing,
and
it
depends
on
what
you're,
using
for
local
development,
I
guess.
I
was
using
a
bit
book
so
I
guess
it
was
a
permission
issue.
I
just
got
the
that
page.
That's
for
the
FTP
passwords.
If
we're
it
for
authorized,
be
it's
been
not
to
be
there
I'm,
not
sure
what
would
have
been
like
the
arrows
thrown.
So
that's
one
thing
that
we
need
to
test
further
and
then
I
found
it
to
be
relatively
smooth
other
than
that.
B
Just
a
few
suggestions
that
are
made
with
regards
to
simplifying
the
the
options
for
the
user
interface,
for
it,
just
converting
certain
things
to
check
boxes
or
sorry,
radio
buttons
and
then
hiding
things
by
States,
so
to
make
the
the
formless
shorter
I
guess
so
that
people
hope
scroll
less
and
then
also
we
had
a
big
description
text
a
little
rather
long,
one
explaining
what
its
level
of
security
release
sorry
of
its
release
does
explaining
what
what
releases?
What
minor
releases
are?
B
C
Right,
yeah,
I'm
still
so
excited
I,
can't
I'm
stoic
just
Flores
that
that
that
functionality
is
already
in
court
and
that
how
close
we
are
to
making
it
totally
possible
Jeff.
Do
you
want
it
read
any
extra
info
on
that
since
that
you're,
the
one
that's
been
doing
all
the
development
work
on
automatic
updates,
no.
D
D
C
Okay,
let's
see
other
issues
related
to
automatic
updates,
yet
Gregory
you,
you
noted,
remove
authorized
PHP.
That
issue
is
not
in
the
agenda,
but
last
I
looked
at
it.
We
had
a
pull
request
that
kind
of
removed
it
from
everywhere
and
I
was
tempted
to
take
it
further,
because
there's
also
this
entire
set
of
classes
for
moving
files
around.
That
is
also
used
exclusively
by
authorized
dot
PHP.
So
that's
another
subsystem
that
would
basically
not
be
used
anywhere
and
we
could
potentially
deprecated
that
entire
system
as
well
but
I,
don't
know
it
got
a
little.
C
C
Okay,
let's
go.
Let's
carry
on
to
other
issues.
Let's
see
these
other
three
issues
that
we
have
are
all
moving
along
nicely
issue
number
thirty-seven
text,
four
modules:
this
has
been
reviewed
by
Gregory
and
they
kicked
back
to
needs,
work,
Jenna,
I,
think
you're,
the
one
that's
is
taking
the
lead
on
doing
tags
from
on
trolls,
so
that
one
back
to
needs
work,
option,
1005
options
element
in
court.
This
one
is
ready
for
review.
Again,
it's
been
rear,
old
and
updated.
C
Everybody
seems
to
express
their
extreme
happiness
with
that
particular
poll
request
and
that
particular
feature.
It's
ready
for
review
I,
don't
think
there
are
any
outstanding
issues
with
it.
It's
already
gone
through
a
couple
of
iterations
and
now
is
back
looking
for
more
eyeballs
and
lastly,
field
of
both
file
types
issue:
26
32.
C
There
aren't
any
large
updates
on
this
issue.
This
makes
it
so
that
files
become
more
like
normal
entities
that
there's
different
types
of
them
like
video
and
photo
can
be
separated,
and
then
files
also
become
field
goal.
No
recent
updates
on
on
this
one
and
it
I
think
just
generally
needs
more
reviewing.
There's
nothing
explicitly
wrong
with
it
that
we
know
of
it's
been
reviewed
a
couple
of
times
it's
a
massive
amount
of
code,
but
it
looks
really
good.
There
are
some
questions
about
like
how
it
should
be
represented
core
outside
of
concern
about.
C
C
C
B
Yeah
I
have
a
recommendation,
so
I
was
looking
at
the
certain
libraries
that
we
are
sleeping
with
core
and
like
jQuery,
mostly
in
the
ckeditor.
We
are
a
few
visions
behind
and
I
did
file,
maybe
four
or
five
issues
with
with
regards
the
ckeditor.
Some
of
them
might
be
for
the
113
released,
but
one
step
forward
would
be
to
update
to
the
latest
version,
which
offers
certain
new
features,
and
my
my
overall
question
or
thing
that
I
would
like
to
discuss
is
maybe
say
one
month
before
it's
made
minor
release.
B
But
if
we
let
a
lot
of
releases
like
every
four
months
and
update
like
libraries,
which
are
critical
to
help
back
drop
in
the
UI
operates,
then
we
risk
having
way
too
many
features
or
changes
happening
in
these
between
these
versions.
So
I
think
that
we
should
update
more
frequently
like
we
should
make
sure
that,
with
each
minor
release
we
update
to
the
latest.
B
If
things
don't
break,
and
so
one
thing
that
I
wanted
to
point
out,
I'm
not
sure
if
we
can
make
for
the
1.12
but
ckeditor
now
introduced,
is
sort
of
like
a
balloon
tooltip,
which
is
the
equivalent
of
see
how
in
google
docs,
for
example,
when
you
click
on
link,
there's
a
balloon
with
a
link
that
allows
you
to
edit
it
in
place.
They're
like
yeah.
B
I
thought
it
was
a
d8
thing.
So
I
would
like
us
to
discuss
that
and
for
parity
reasons.
Maybe
we
could
offer
it
as
an
option
and
it's
not
actually
a
screenshot.
It's
like
if
you
go
in
city,
editor,
calm
a
for
version
of
it.
It
has
a
live
demo
day
on
the
front
page
where
you
can
switch
it
and
just
play
with
it.
C
Yeah,
so
the
just
tearing
that
thought
through
so
inline
editing
like
the
current
version
of
CK,
that
we
have
supports
inline
editing,
but
it
typically
doesn't
actually
work
that
great
because
of
input
formats
like
input,
filtering
and
even
in
Drupal
8.
It's
the
case
that
pretty
much
no
inline
editing
actually
edits
directly
inline
it.
C
Actually,
when
you
click
in
it,
Ajax
requests,
it
gets
the
raw
HTML,
because
the
front-end
version
usually
has
been
transformed
by
input
filters
before
it
gets
to
the
front
end
and
then,
when
you're
editing,
that
you
need
the
raw
HTML
that
is
stored
in
the
database
before
it's
transformed
and
so
inline
editing
doesn't
work
real
great,
even
in
Drupal
8,
because
it
always
has
to
go
and
get
and
a
back-end
version
of
the
content.
So
you
can't
just
click
to
edit.
C
B
C
B
C
B
C
B
C
It's
handy
well,
anyway.
What
we've
also
done
in
previous
versions
is
sometimes
we
update
to
the
new
version
of
ckeditor,
but
we
don't
actually
use
the
new
features
in
it.
Yet
so
we
update
to
the
new
version
to
make
sure
that
we
don't
break
things
and
then,
in
the
next
minor
release
we
usually
actually
use
the
enhancements
that
were
added.
C
That
happened
with
upload
progress,
for
example,
and
inline
like
copy
and
paste
like
we
added
the
versions
of
seek
editor
that
supported
those
features,
but
we
didn't
actually
integrate
them
until
the
next
the
subsequent
release
so
yeah.
That
is
a
good
point.
We
we
always
have
that
issue
of
make
sure
our
libraries
are
up
to
date
and,
like
you
point
out
great,
sometimes
we
don't
do
them
until
like
almost
immediately
before,
and
it
would
be
better
in
many
cases
if
we
updated
them
more
incrementally
throughout
the
minor
release
cycle.
So.
B
There's
there's
a
lot
of
people
just
testing
various
pull
requests
in
the
sand
boxes,
which
makes
it
a
good
chance
if
it
if
things
are
most
say
a
month
before,
if
there's
good
chances
that,
if
there
are
breakages,
they
will
be
discovered
or
more
of
them
will
be
discovered.
That's
why
I
was
mentioning
it
and
the
other
thing
is
that
I
was
thinking
that
in
the
descriptions
of
this
ongoing
thing.
Maybe
we
should
add,
because
these
this
is
JavaScript
and
we
don't
have
tests
for
it.
B
So
I
would
like
us
to
add
steps
in
the
issue
summary
that
test
that
need
to
be
repeated
every
time
that
we
update
the
library
to
make
things
that
think
make
sure
that
things
that
have
been
broken
haven't
been
broken.
So
yeah
I
would
like
some
help
with
that
compiling
the
list
of
what
needs
to
be
tested
for
jQuery
and
for
ckeditor
I.
Think
Nate.
B
You
mentioned
in
the
past
that
there
is
a
list
somewhere
like
I'm,
not
sure
if
you
have
it
written
down
somewhere,
but
at
some
point
you
pointed
out
one
during
one
of
the
jQuery
updates
that
sort
of
like
a
list
of
five
or
ten
items
that
needed
to
be
tested.
That
would
be
really
handy
and
then
one
final
question
related
degrees.
I
was
checking
the
change
log,
because
I
did
file
a
pool
full
request
to
update
it.
B
So
it
seems
that
we
are
not
using
the
native.
What
is
it
called
URL,
the
the
plugin
that
converts
urls
to
things
like
actual
we're
using
our
own
implementation,
and
there
was
a
point
in
the
change
log
that
said
that
this
plug-in
now
supports
liquefying
emails
as
well.
I'm,
not
sure
if
that
was
the
reason
why
we're
not
using
the
native
one
just
mentioning
it.
C
Yeah
I
don't
think
we
have
I'm
not
quite
sure
why
we're
not
using
it
I
think
it's
just
because
we
have
the
we
still
have
automatic
creating
of
links
happening
at
the
filter
level
instead
of
at
the
text.
Editor
level.
Honestly
I
think
it
would
be
better
if
the
text
editor
level
like
that
I
give
automatic
linking
stuff
is.
You
know,
based
upon
an
era
where
we
didn't
have
a
rich
text,
editor
at
all
and
I
was
like
convenient,
so
I
think
you'd
be
better
at
the
text
writer
who
did
it
for
you,
yeah.
C
B
C
C
D
D
C
I
think
it
does
actually
I
think
that
that's
it's
got
a
lot
of
stuff
that
isn't
related
to
authorized
dot
PHP
in
there,
but
it's
the
one
that
is
responsible
for
actually
moving
the
files
around
I
think
that's.
It's
definitely
used
in
the
up
in
the
updates
to
the
UI
yeah
yeah.
That's
that
file
is
heavily
used
by
the
Installer
module,
but
it
doesn't
actually
make
extensive
use
of
authorized
PHP,
which
is
weird
okay.
Thank
you.
C
Let's
see,
there's
question
here
in
the
agenda
about
contribs
acuity
updates,
probably
relevant,
because
there
were
some
security
updates
just
yesterday.
That's
it's
confusing
to
deal
with
security
updates
for
control
a
four
core
actually
to
the
way
that
we
currently
manage
security
updates
is
that
we
cut
the
security
release.
C
You
know
we
publish
the
security
announcement
on
backdrop,
CMS
org,
but
then
there's
one
special
trick
that
a
lot
of
people
miss
when
doing
security
releases,
and
that
is
after
the
security
release
is
created
on
github
a
project
release
node
is
created
on
backdrop
CMS
org,
and
they
have
to
edit
that
node
and
check
the
box.
For
is
this
a
security
update
and
that
turns
on
the
flag
in
update
module.
That
makes
it
so
that
it
says
you
know,
there's
a
critical
security
update
for
your
site
on
the
status
report
page.
C
So
two
questions
here,
two
comments:
how
do
we
document
that
like?
How
can
we
make
that
easier
for
people
to
find
how
to
do
that
process?
And,
secondly,
like
could
we
make
that
entire
process
easier
to
make
it
so
that
maybe
the
documentation
wouldn't
be
so
necessary
or
it'd?
Be
more
intuitive
to
do
that,
I'm!
Guessing
Jen!
You
may
have
added
these
things.
Do
you
want
to
elaborate
any
further
on
these
questions.
C
B
Can
say
a
few
things,
so
the
reason
why
this
was
added
in
the
previous
to
the
previous
dev
meeting
was
that
I
discovered
that
two
modules
that
actually
were
supposed
to
be
security
releases
have
not
been
marked
as
such,
mm-hmm
and
I.
Think
one
of
them
was
web
form
or
something.
So
the
main
issue
with
that
is
that
people
that
are
ignoring
regular
updates
and
only
do
the
security
updates
would
not
have
picked
up
that
there
is
actually
a
security
update
and
I
think
that
we
yeah.
B
We
can
document
that
somewhere
in
the
that
contribute
me
MD
file.
That
says
how
you
can
move
things
around,
but
it
can
easily
be
forgotten,
so
I
thought
that
maybe
see
how
we
have
templates
for
github
issues.
When
you
create
a
new
issue,
there's
a
template
being
created.
I
would
like
to
see
if
there's
an
option,
to
add
a
template
when
you
are
actually
creating
a
release
that
says
hey.
B
If
this
is
a
security
release,
don't
forget
log
in
or
have
someone
log
in
in
B,
dot,
org
and
market
as
a
securities
I
did
some
research
I
couldn't
find
anything
related.
But
my
point
is
that
documentation
is
good
and
I'm
sure
that
people
will
read
it
and
some
of
them
will
keep
it
in
mind,
but
some
will
forget
some
I'm
trying
to
figure
out
a
way
to
sort
of
like
with
each
release.
Say:
hey
is
this
security
list
in
case?
If
that's
the
case,
you
need
to
do
an
extra
step
and.
C
Great
question
that
would
be
really
helpful
if
you
did
that
indicate
up
level.
I
haven't
heard
of
something
like
that
before,
but
I
hadn't
really
seen
issued
templates
use
the
way
that
we
use
them
now
either,
so
it
might
be
possible
which
either
way
I
really
like
our
issue
templates.
That
comment
section
is
down
at
the
bottom.
That
says
you
know
like
if
this
is
a
security
issue,
that's
like
magic,
sometimes.
B
I'm
complicating
things
in
my
head
because
I
don't
know
how
these
things
work,
but
the
other
idea
was
that
it's
if
we
have
the
maintainer
of
a
specific
module
as
a
an
actual
field
or
in
billet
org,
with
each
creation
of
our
release,
we
can
send
an
email.
I
know
they
could
be
annoying
and
saying
hey
by
the
way.
Was
that
a
security
release
that
would
be
another
way
but
yeah.
A
A
Yeah
I
still
think
we
need
to
get
the
github
single
sign-on
working
before
we
can
do
that.
So
we
can
tie
a
username
on
backdrop,
semester,
artim
username
on
github,
but
we
need
that
anyway
and
I
think
I.
Think
Kevin
did
some
work
on
that
too,
so
or
at
least
the
synchronization
between
github
and
backdrop
site.
So
we
should
take
a
look
at
that
and
see
if
we
can
use
that
on
back
continue
starboard.
Yet
what
are
blockers
are.
C
Yeah:
okay,
let's,
let's
call
it
feel
it
good
I've
been
doing
backed
up
means
for
two
solid
hours.
Now,
almost
so.
Thank
you.
Everybody
for
joining
these
meetings,
as
always
see
you
guys
again
on
the
internet
and
just
keep
on
back
drop
in
so
bye,
guys.