►
From YouTube: Backdrop Weekly - Aug 30th
Description
Today’s development agenda: http://bit.ly/2Nbv3WY
A
A
A
Just
this
calendar
Sunday,
my
meteorite,
the
third
yeah
I-
need
to
learn
better
reading.
Calendar
writing.
Okay,
so
really
quickly.
Before
we
get
to
backdrop,
CMS
issues,
I
wanted
to
highlight
that
we
have
two
new
modules
this
week,
use
term
by
path
and
you've
filled,
so
we've
got
a
bunch
of
new
used
stuff
and
before
the
meeting
started,
Tim
and
I
are
also
talking
about
potentially
working
on
use
field
view.
So
it's
a
very
view.
B
So
before
we
get
into
1.11,
which
I
know
is
the
exciting
order
of
the
day.
Quick
recap
on
1.10,
which
is
the
next
bug,
fix,
release
no
pressing
issues
for
one
dot
Timbo,
but
we've
accumulated
a
good
number
of
issues,
probably
20
some
issues
that
have
been
fixed
in
1.10.
Before
we
get
into
the
code
freeze,
it
might
be
good
for
us
to
cut
another
1.10
release
just
to
make
it
so
we've
got
a
little
buffer
before
we
make
one
10.3,
which
would
be
the
last
release
when
one
double
oven
comes
out.
B
So
I
said
this
last
week
that
it's
likely
that
a
1.10
releases
eminent-
and
it
didn't
happen
this
past
week,
but
I
think
it
could
happen
assumes
today
or
tomorrow,
so
keep
your
eyes
peeled
for
one,
not
10.2.
That
includes
just
a
you
know.
The
collection
of
bug
fixes
that
can
accumulate
over
time.
So
take
a
look
at
the
one
that
tended
to
issue
tractor.
B
Okay,
so
1.11
is
a
next
minor
release.
It
will
be
coming
out,
September,
15th
and
Jen.
Maybe
we
should
clarify
the
September
3rd
code
freeze,
so
we're
saying
that
we're
extending
the
code
freeze
through
the
weekend
and
because
it's
a
holiday
in
the
United,
States
and
I
think
in
Britain
too
we're
including
Monday,
as
also
part
of
the
thought,
is
that
right,
so
the
freeze
will
be
the
end
of
day
Monday.
Okay,
all
right!
That's
now
official.
B
Okay,
so
we've
got
less
than
a
week
to
pull
in
the
last
features
for
1.11
and
we
have
a
lot
of
outstanding
work
outstanding
and
both
means
both
both
meanings
of
the
word
that
that
we
still
have
the
potential
to
complete.
So,
let's
run
through
the
list
of
things
that
we've
been
doing
all
1.11
release
and
see
how
we
stand
so
contact
module
improvements,
a
big
meta
issue
that
OB
has
been
taking
the
lead
on
issue
3023.
B
There
are
lots
of
contact,
module
improvements
that
have
been
merged
and
there's
two
more
that
are
in
the
RVT
sea
state
and
one
that
needs
the
ux
review.
So
it's
likely
that
those
two
that
are
rgbc
will
get
merged
in
promptly,
and
that
may
be
the
completion
of
contact
module
improvements
for
1.11,
we'll
see
how
that
proceeds.
This
next
week,
color
module
improvements
which
Joseph
or
hose
F
has
taken.
The
lead
on
in
1905
is
another
issue.
B
The
main
issues
that
we
were
aiming
to
complete
for
1.11
are
complete
and
merged,
including
a
a
new
user
interface
for
for
adding
colors
to
themes.
That
includes
a
live
preview
that
is
automatic
and
shows
the
actual
real
site
with
the
preview
applied
to
it,
as
well
as
the
colorization
of
basis
module.
B
B
Also,
this
one
that
hasn't
been
completed
yet,
but
I
would
really
love
to
see
completed,
is
adding
some
predefined
color
schemes
to
the
basis
theme
right
now.
It's
colorized
well,
but
it
doesn't
have
any
predefined
schemes
and
there's
been
some
suggestions
made
there,
but
we
have
yet
to
turn
that
into
a
pull
request
or
reach
any
kind
of
conclusion.
There
yeah
take
a
look
at
that
issue,
which
is.
B
3209
to
add
predefined
color
schemes
to
faces
okay,
next
up
bringing
back
the
node
preview
issued
3062.
It's
currently
needs
work.
It's
just
bounced
back
from
our
TBC
a
couple
of
times
in
the
past
few
days.
So
that's
really
exciting.
Thanks
doc,
Belmont
Olaf
and
herb
for
all
of
your
work
on
making
node
preview
come
back
from
the
dead.
It
looks
like
I
mean
it's
been
re
TBC
a
couple
of
times,
they're,
just
working
out
a
few
remaining
issues,
so
I'm,
hoping
that
that
should
reach
completion
here
within
the
next
couple
of
days.
B
30
105,
which
is
allowing
backdropped
core
to
update
itself
via
the
user
interface,
still
needs
review
on
that
one
I
think
that
there's
been
some
requests
that
the
current
pro
would
price
has
gotten
some
cruft
in
it.
That
doesn't
need
to
be
there
cruft,
like
literally
like
files
that
are
just
added
to
the
pork,
but
for
no
reason
and
so
I
think
there's
been
some
requests
to
clean
that
up,
but
still
need
needs.
B
Don't
think
it
would
be
the
worst
thing
for
us
to
to
merge
it
in
for
1.11
and
then
we'd
have
it
actually
in
the
release
to
actually
you
know,
do
the
testing
and
since
it's
such
new
functionality,
I,
don't
think
it's
likely
that
people
would
run
into
it
right
away,
but
yeah
I'm
kind
of
on
the
fence
about
how
we
should
handle
that
one,
because
it's
really
looking
like
this,
but
our
efforts
to
review
it
like
it's
really.
It
almost
needs
to
be
in
place
in
order
for
us
to
test
it
effectively.
B
B
B
Thank
you.
Let's
see,
we
also
have
this
issue
to
remove
authorized
debt,
PHP
you're,
probably
more
accurately,
to
deprecate.
It
lets
issue
3208
and
that
hasn't
been
any
substantial
progress
on
that.
One
we'll
see,
I,
don't
think
that
there's
much
work
involved
in
that
one,
mostly
just
removing
places
where
we're
calling
author
I
start
PHP
and
then
adding
dock
blocks
all
over
the
place
saying
that
it's
deprecated,
but
there
hasn't
been
any
any
code
implementation
of
that
yet
so
that
also
may
not
happen
for
1.11.
B
Okay,
let's
see
also
in
the
category
of
things,
hopefully
won't
make
it
more
window
to
living
issue
37
tax
for
modules.
No
progress
in
this
past
couple
of
weeks,
actually
on
that
one.
So
I
won't
recap
that
one
all
over
again,
let's
see
and
that,
let's
see
sorry,
there's
lots
of
things
going
on
in
the
agenda.
Okay,
something
that
was
brought
up
in
get
ur
right
before
the
meeting
is
issue
number
100.
B
The
system
for
page
list
nodes
was
resurrected
this
past
week
again
by
herb
dual,
who
took
the
question
of
like
all
of
these
complicated
solutions
that
we're
talking
about
and
really
distilled
it
down
to
the
main
functionality
and
made
a
pull
request
that
has
essentially
rabbit-hole
type
functionality
in
a
single
checkbox.
Just
saying
whether
or
not
the
content
type
that
you're
creating
has
a
page
or
not,
and
so
it's
definitely
the
MVP
Minimum
Viable
Product
for
rabbit-hole
type
functionality
in
cork,
but
it
looks
like
of
the
people
participating
that
issue
the
result.
B
The
the
comments
have
been
really
really
positive.
So
it
is
a
almost
trivial
implementation,
so
there's
not
much
maintenance
or
code
required
in
order
to
get
that
functionality.
The
way
that
it's
implemented
currently
so
I
think
it's.
It's
got
a
good
chance
at
it,
even
though
it's
only
a
couple
of
days
left
here-
and
this
hasn't
been
a
heavily
focused
item
for
1.11-
and
you
know
it
looks
like
this
particular
approach
could
make
it
in
for
1.11.
So
please
take
a
look
at
page
lists
now.
C
Do
you
know
what
that
does
to
rabbit
hole
itself
would
like
rabbit
hole,
be
like
an
extension
by
all
the
module
that
extends
the
functionality
or
deprecated
rabbit
hole?
Creature
per
so.
B
It
might
make
grab
a
whole
two
things
that
rabbit
hole
is
not
describing
because
written
like
basically
either
one
of
them
will
be
able
to
block
access
to
the
node
view
page
with
disability.
So
if
you
use
either
of
them
either
them
will
take
either
than
will
disable
the
view,
basically
or
if
you
wanted,
to
keep
using
rabbit
hole
for
the
time
being.
You'd
probably
just
have
to
ignore
the
page
list,
nodes
option
and
then
rabbit
hole
would
continue
functioning
as
rabbit
hole
does
so
for
existing
sites.
We.
B
B
What's
the
other
one,
it
can
show
say
many
not
found
I
can
do
a
redirect
or
or
it
can
do
access
denied
I
think
it
might
be
able
to
do
one
more
thing
as
well,
but
Rama
has
different
behaviors
for
what
to
do.
He
won't
have
access
to
the
node
and
the
core
version
only
returns
page
not
found
okay
yeah.
So
it's
it's
the
it's.
The
bare
minimum
I
think.
B
C
B
B
B
Our
longest-running
issues
so
yeah
and
if
you're
gonna,
if
you're
gonna,
come
in
with
it
a
bright
new
idea,
make
sure
that
you've
read
the
whole
issue
because
it
really
we're
just
like
all
over
the
place.
We've
talked
ourselves
into
circles
on
this
one
over
and
over
again
so
yeah.
It
can
take
a
little
bit
of
effort
to
review
the
options
that
are
out
there.
B
Okay,
next
up,
we've
got
a
series
of
items
that
are
related
to
image
and
file
handling,
use,
exif
data
to
rotate
images
when
they're
uploaded
is
issued.
28
87,
this
one
is
our
TBC
I've
already.
Given
this
one
look
a
couple
of
times
now,
I
think
that
one
is
ready.
Her
bill
has
seconded
on
that
one.
Thank
you
very
much
and
and
grant
72,
of
course,
for
doing
all
the
implementation
work
and
all
the
rebuilds
on
that
one,
so
that
one
is
in
real
good
shape.
B
We'll
probably
see
that
one
in
the
next
day
or
two
issue,
31
34,
for
the
ability
to
upload
or
select
an
image
through
a
browser
image
browser.
It's
actually
that
issue
this
one
it
it
looks
pretty
good,
but
it
needs
some
work.
There's
a
bug
that
is
a
major
blocker
that
the
Ajax
behaviors
within
the
embedded
view
of
the
image
browser
dialog,
don't
work,
which
means
that
you
can't
have
more
than
one
page
of
images
in
your
image
browser
and
have
it
work.
B
So
that
is
kind
of
a
major
issue
that
is
blocking
the
completion
of
that
other
than
that,
though,
the
functionality
looks
really
pretty
good,
so
31:34
is
specta,
meets
work
with
a
critical
problem
blocking
further
progress,
so
any
JavaScript
pros
out
there.
We
could
use
some
help
figuring
out.
What's
going
on
there,
it's
extra
tricky,
because
there's
no
problems
than
the
JavaScript
console
is
just
like,
silently
like
it's
just
not
working
the
way.
You
would
expect
so
a
little
bit
of
an
issue
there
and,
lastly,
feel
to
both
file
bundles
issue.
B
26
32
has
also
been
bumping
in
and
out
of
our
DBC
state
for
the
past
couple
of
weeks,
and
so
that's
really
exciting.
The
currents
for
request
status
is
that
document
says
that
it's
fully
passing,
but
recent
merges
into
one
decks
have
made.
It
have
a
merge
conflict,
so
merge
conflict
aside,
supposedly
that's
also
in
really
good
shape,
so
more
feedback
and
help
on
26:32
would
also
be
highly
appreciated.
So
that's
very
exciting.
That's
it
for
the
the
list
of
things
that
are
slated
for
one
double
Evan.
B
We
still
have
a
lot
of
things
to
to
ramp
up
and
only
a
couple
of
days
before
code
freeze,
hits
us
or
feature
freeze
hits
us
and
so
yeah
we've
got
a
work
cut
out
for
us
there's
so
many
things
like
there's
something
like
pretty
huge
features
in
here
that
it
would
be
totally
epic.
If
you
know
we
get
even
even
two
of
these
in
here,
then
two
additional
ones
and
it'll
be
really
fantastic.
B
C
C
A
A
Scot
bowler
have
his
blog
post
here.
I
will
post
this
in
together,
where
his
message
is
essentially
that
Gutenberg
is
going
to
end
up
costing
the
WordPress
community
too
much
because
of
upgrading
from
previous
searches
to
the
latest
version.
So
it's
sort
of
the
same
messages
that
got
was
so
yeah
kind
of
interesting.
It
only
happened
yesterday,
at
least
according
to
his
github
issues,
and
there
doesn't
seem
to
be
a
whole
bunch
of
noise
in
this
issue.
Queue
yet,
but
there's
really
a
whole
bunch
of
noise
on
the
internet
in
general.
A
About
this,
so
I'm
not
sure
he's
like
totally
ready,
for
you
know,
creating
an
entire
community
beer
and
alternate
piece
of
software.
If
he's
just
one
guy
who's
like
I'm
gonna,
do
it
my
way
and
then
he
won't
be
part
of
the
movement,
but
so
I
find
it
interesting
that
he's
got
sort
of
the
same
message
as
we
do
about
how
making
drastic
changes
to
the
software
can
affect.
The
whole
community
is
using
it.