►
From YouTube: Backdrop Weekly 12/29
Description
Today’s development agenda: http://bit.ly/2hhtSt4
A
Hello,
everybody,
it's
December,
29
2
2016,
and
this
is
the
weekly
backdrop
def
meaning
so
every
week
we
get
together
and
we
talked
about
the
tasks
that
are
facing
a
backdrop
and
this
particular
meeting.
We
have
a
really
shortened
agenda
because
we're
focused
on
the
next
release
of
backdrop,
1.6
that
comes
out
in
a
couple
of
weeks
january,
fifteenth
also
per
our
new
policy.
We
are
doing
code
freeze
on
january
first,
so
we
have
some
items
that
need
to
be
finished
up
in
order
for
us
to
meet
that
deadline.
A
A
B
I,
don't
see
how
that's
going
to
happen
for
this
release
I'm
slowly
working
my
way
through
adding
tests
but
I'm
having
some
issues
that
and
no
one
else's
pitched
in
anything.
Along
with
that,
we
have
a
few
outstanding
issues
in
the
issue:
queue
for
the
module
that
shouldn't
be
that
hard
to
address.
We
have
a
few
remaining
features
which
shouldn't
be
that
hard
address,
but
I
don't
think
we
can
do
it
all
by.
However
many
days
two
days
three
days
and
then
I
definitely
can't
do
the
stuff.
B
A
I've
volunteered,
but
I'm
not
been
fulfilling
my
obligation
here
on
on
helping
with
tests,
so
I
still
plan
on
chipping
in
there
as
soon
as
possible,
which
basically
means
today
and
tomorrow
and
the
weekend
but
yeah
you're
right
that
it's
gonna
be
tough,
we'll
see,
yeah
I
think
at
this
point,
like
I,
can
help
with
testing
and
I'll
see
how
far
we
get
on
that.
It
might
also.
A
It's
been
proposed
that
we
leave
in
like
term
reference
by
yourself
and
others
that
you
know
cuz
doing
the
upgrade
path
is
challenging,
and
so
that
might
be
on
the
table
and
it
might
not
be
I
think
want
me
to
see
how
John
feels
about
this.
After
you
know,
she
was
unable
to
work
on
the
upgrade
path
so
that
my
yeah.
B
Chaley
tips
and
we
can
always
do
an
automatic
upgrade
later
and
I
mean
we
can
there's
like
I,
said:
there's,
basically
nothing
in
the
data
structure
of
one
of
these
references
other
than
just
like
the
entity
type
and
I
e.
That
is
referencing
yeah
and
is
in
the
same
thing
the
same
for
turn
for
for
the
same
things,
the
same
for
taxonomy
reference.
Probably
the
only
thing
it
has
special
as
the
widget
for
creating
that
and
stuff
like
that.
A
Something
so
I
mean
yeah,
I'm
also
not
keen
on
it
that
we
could
do
like
one
thing,
like
the
reference
module
first
and
then
do
the
upgrade
path.
Later
I
mean
what
it
is
worth,
acknowledging
the
fact
that
we
do
actually
have
two
additional
weeks
before
the
release
itself
comes
out
and
1.6
is
right
now
very,
very
limited
in
its
changes.
There's
hardly
been.
You
know
anything
at
all,
actually,
so
then
number
of
bugs
that
we
have
to
squash
in
that
two-week
period
or
almost
non-existent,
because
everything
is
pretty
pretty
much
the
same.
B
C
B
C
B
A
And
I
like
that
idea,
actually
quite
a
bit,
we
could
even
feature
it
like
in
the
newsletter
that
goes
out
talking
about
1.6,
let
it
like
to
that.
It's
made
to
work
together
or
something
like
that
yep
and
that
and
that
could
get
some
momentum
behind
making
trip
version
which
could
be
made
part
of
Cory
as
we
go
forward.
Yep.
A
A
D
Gregory,
or
are
you
going
to
say
yes,
so
a
couple
of
things?
First
of
all
that
the
idea
that
you
said
that
you
were
talking
about
reminds
me
a
lot
of
the
way
Triple
H
has
these
experimental
modules
that
get
into
core
I
think
we
might
have
touched
on
that
issue
a
couple
of
times
what
we
said.
It's
not
a
good
idea
but
might
seem
like
this
is
a
perfect
chance.
D
Bag
I'm
just
saying,
and
the
other
thing
is,
although
it
saddens
me
and
watch
it
not
enough
to
help,
we
we've
been
through
that
with
the
WYSIWYG
module
I,
don't
mind
if
we
even
like
I
hate,
I
hate
have
been
to
stress
ourselves
and
members
of
our
community
just
to
get
features
in.
So
if
this
gets
pushed
Stephen,
217
I'm,
not
saying
don't,
try
to
get
it
in
there,
but
even
if
it
gets
pushed
to
the
next
three
days
I.
D
A
B
A
B
A
Ok,
well,
let's
it's
very
least
just
continue
developing
the
criminal.
It
is
accessible
under
Jacob,
calm,
/
backdrop
dash
contribs
and
that's
where
developments
happening
and
I
really
like
the
idea,
at
least
of
making
an
official
release
if
it
doesn't
get
in
then
at
least
having
a
module
that
people
can
actually
use.
That
is
yeah
searchable
and
installable,
and
everything
like
that.
A
A
A
It's
I
think
it's
a
question
of
what
our
priority
is
here,
whether
or
not
disabled
view
modes
are
going
to
be
used
frequently
enough
that
we
should
show
them
on
that
page
or
whether
or
not
adding
a
view
mode
or
showing
a
disabled
via
mode
is
not
important
enough
to
show
on
the
same
page
and
should
be
stashed
away
under
the
add
or
customized
you
mowed
link,
there's
mock-ups
I
know
it's
a
little
bit.
Ron
and
I
share
my
screen.
Here
we
go.
A
I'm
second:
here
we
go
okay,
so
here's
what
we're
looking
at
this
is
a
one
version
where
we
only
show
the
view
modes
that
are
that
are
activated
and
then,
if
you
want
to
add
or
customized
one
of
the
disabled
view
modes,
you
have
to
click
this
link,
which
then
shows
you
a
drop-down
select
list
of
all
of
the
possible
few
modes
and
an
option
to
add
another
one.
I,
don't
think.
B
B
Either
the
first
time
I've
actually
finally
take
a
look
at
it.
The
customized
terminology
is
a
bit
weird
like
it's
a
gothic
and
second
to
realize
what
it
was
I
mean.
It
makes
sense
once
I
realize
it,
but
like
an
able
sort
of
seems
better
or
something
word
yeah,
but
you
know
customize
make
sense,
I'm,
absolutely
cool.
B
A
B
A
Lets
that
that's
the
weird
thing
about
it
is
that
you
can,
you
can
configure
views
or
reference
or
whatever
it
is
you
used
like
the
full
content
view
mode,
even
if
the
full
content
view
mode
isn't
actually
any
difference
or
enabled
or
whatever
you
want
to
call
it.
It'll
just
fall
back
to
the
default,
so
it's
confusing
about
it
is
that
they're
always
enabled
so
yes,
I
was
highly
customized.
Argue.
B
Against
hiding
them
with
it
because
they
are
in
play,
even
if
they're
not
customized,
and
there
should
be
like
a
list
of
them.
So
yes,
I
think
this.
This
is
better
than
the
other
one.
That
was
hiding
it,
because
you
need
to
know
that
these
exist,
because
then,
when
you
go
to
select
them
somewhere
else,
they
show
up
in
the
list.
Yep.
A
And
so
that's
exactly
the
two
sides
of
the
coin
that
that
we
have
have
this
problem
I
would
as
strong
here
I.
Actually,
I
favored
the
other
approach
that
I
prefer
to
hide
them
for
the
reasons
that
I've
stayed
here
and
your
point
is
totally
valid
as
well.
I'm,
not
really
sure
how
to
resolve
this.
We're
at
a
point
where,
like
other
people
like
dr.
Wilmont,
are
also
saying
that
is
as
well
so
I
know
what
to
do.
It's
not
not
that
either
approach
is
really
bad.
A
It's
really
just
deciding
which
one
is
better
because
both
are
better
than
what's
then
what
we
have
currently
and
what's
an
interval
aight,
I
feel
so
it's
really
yeah,
I'm
not
quite
sure
how
to
resolve
it.
What's
in
the
PR
0
PR
right
now
is
the
one
where
they're
hidden
where
they're
in
a
select
list,
yeah.
A
A
Some
of
them
can
yeah
first,
okay,
so
this
is
oh
I'm.
Sorry
manage
displays.
Is
that
I
always
thought
that
was
okay.
So
here's
what
it
looks
like
right
now
and
the
the
reason
why
I'm
a
fan
of
this
is
that
really
in
most
situations
you
don't
actually
need
more
additional
view.
Modes
like
few
modes
are
not
a
kind
of
an
advanced
topic
and
it
really
puts
the
focus
on
what
your
extra
are
interested
in
the
default
view
mode
and
the
teaser.
A
And
then,
if
you
want
to
add
an
additional
view
mode,
you
choose
which
one
it
is
or
if
you
want
to
add
a
customized
one.
So
these
ones
are
the
hard
code,
big
ones
like
for
content,
and
so
now
that
one
is
now
added.
But
if
you
want
to
add
a
new
view
mode
entirely,
you
know
like
slideshow
or
something
like
that.
You
give
it
a
label
in
a
machine
name,
and
then
this
one
actually
can
be
deleted,
but.
D
I'm
generously,
something
that
of
course
not
see
how
you've
added
the
full
content
least
they're
right
what
what
was
the
purpose
of
hiding
it
you've
added
it
there.
Now
it's
there,
you
haven't
customized
it.
Yes,
yet
so,
what's
the
point
of
having
it
there
except
say,
somebody
adds
it
like
what
you've
just
done,
but
you
haven't
customized
it.
So
what's
the
difference
between
this
one,
as
it
is
now
non
customized
than
the
other
ones
that
are
hidden.
A
For
one
difference
now
is
that
if
I
were
to
change
the
default
view
mode
at
this
point,
it
would
not
affect
for
content.
All
content
is
now
a
copy
of
what
default
used
to
be,
and
so,
if
I
change
default,
like
you're,
like
a
managed
display
here,
is
like
okay,
well,
I
think
I
may
have
a
bug
here,
because
this,
because
there's
nothing
actually
copy
anything,
it
just
says
everything
all
hit,
but
so
I
guess.
Actually.
This
is
something
different
in
that
the
view
mode
when
I
turned
it
on
it
shouldn't
do
this.
A
B
B
Okay,
that's
an
ottoman
and
non
discoverable,
like
you,
don't
know,
what's
like
if
you
just
want.
If
you
just
want
the
list
of
all
the
possible
view
modes
for
selection,
you
don't
really
have
like
one
list.
It's
like
you
have
to
sort
of
add
up
all
the
ones
that
are
enabled
and
then
go
look
at
the
ones
that
are
there
to
see.
B
D
F
Think
there's
another
factor
in
the
view
modes
can
be
a
tricky
enough
concept
to
wrap
your
head
around
that
unless
you
know
what
they
are
you're
looking
for
as
much
contact
session
to
figure
out
what
they
are
right.
So
if,
if
most
of
them
are
hidden
that
that's
removing
information
from
you
comers
to
figure
out,
you
know
what
what
it
is.
They're
messing
with
ya.
A
So
one
thing
that
I've
concerned
around
first
of
all
noted
everyone's
opinions,
so
we
might
could
might
end
up
going
that
way.
But
an
additional
concern
I
have
is
that
one
change
that
we
introduced
here
is
that
previously,
when
you
into
this
page
manage
displays,
you
would
immediately
see
this
page
that
the
default
view
mode
with
a
collapsed
field
set
down
at
the
bottom,
and
so
that
made
it.
A
So
I
don't
know,
I've
got
a
concern
around
you
know.
Taking
the
page,
that's
you
know
is
the
most
commonly
visited
page
and
putting
it
a
level
deeper,
but
that's
a
problem
with
either
approach,
but
I
think
that
there's
more
going
on
this
version
that
a
new
user
might
be
might
not
get
to
the
page
that
they
want,
which
is
the
default
display,
and
so
why
did
we
get
rid
of
the
cab?
A
The
tabs
I
think
it's.
D
What
can
I
say
something
there
I
had
a
design
there
that
with
vertical
tabs
I
know
that
it's
wrong
from
my
a
from
the
design
standards
point
I
know
it
was
wrong,
but
it
was
so
fitting,
like
all
nations,
with
discussing
male
hiding
the
the
fields
for
the
default
one
having
to
do
a
lot
of
clicks
and
everything.
The
vertical
tabs
just
sorted.
D
A
A
B
A
A
B
We
could
always
remove
them
later
hi,
so
maybe
we
could
take
it
one
step
at
a
time
here.
The
only
thing
is
with
the
operations
then
we'd
end
up
with
a
situation
like
with
the
views
you
I,
where
we
have
the
secondary
tabs
for
the
different
view
modes
and
then
like
an
Operations
button
over
to
the
right
or
something
like
that
when
you're
actually
looking
at
the
view
mode,
right
and
I,
think.
A
G
C
E
B
D
D
A
Let's
see
so
seems
like
we're,
kind
of
I
mean
actually.
Actually
there
is
some
agreement
here
amongst
the
people,
at
least
that
are
on
this,
call
that
that
we
don't
like
putting
them
under
the
add
new
thing,
yeah,
so
I
think
it
would
be
most
valuable
if
everyone
that
has
an
opinion
could
post
their
opinion
as
so
or
as
it
is
to
the
issue
queue
so
that
we
get
it
more
than
just
on
this.
A
A
Okay,
you
guys
have
more
feedback
there
more
discussion
that
we
should
have
about
this
I
sort.
B
D
B
A
B
B
B
B
E
A
Okay,
yeah
yeah.
We
can
do
exactly
that,
although
we
just
talked
about
this
particular
issue
so,
but
that
is
the
idea
of
the
the
follow-ups
that
we
could
in
theory,
you
know
schedule
some
action
for
to
like
discuss
further
after
the
meeting,
so
it
is
possibility
if
we
need
to
that
on
this
topic
or
another
one
at
the
end
of
the
call.
A
D
I,
don't
remember
the
review.
Sorry
I,
don't
remember
if
I
did
a
thorough
code
review,
because
usually
what
I
do
is
I
look
at
that
you're
talking
about
the
file,
adding
the
file
view
right.
Yes,
that's
right!
Yeah,
all
I
did
was
just
not
really
just
run
through
and
I'm,
not
sure
if
I
would
be
just.
Let
me
quickly
jump
to
that
issue.
I
mean.
Maybe
the
review
is
just
going
through
it
quickly
and
just
looking
at
the
user
interface
and
the
text
mainly
and
let's
see
yeah,
let's
fly
gum.
F
A
D
A
D
A
D
Yes
and
the
other
thing
was
that
I
tried
deleting
an
image
file
created
an
article
and
then
I
went
to
be
this
view.
The
file
view
and
I
deleted
damage.
So
I
went
to
view
the
article
again
or
actually
edited
and
then
I
uploaded
the
same
file.
So
I
got
to
I
got
an
error
at
the
website
in
Canada
and
unexpected
error.
A
D
Well,
yeah
and
then
in
it
some
simple
stuff,
like
the
actual
name
of
the
dacian
file
being
file
admin
I'm
trying
to
get
consistency
with
the
other
places
that
we
are
converting
to
admin
views
to
be
managed
XYZ.
So
it
should
be
managed
files
as
a
title
and
imitation
file
just
just
so
that
people
can
locate
the
views
easily
if
they
go
to
their
active
config
folder.
D
And
yes,
so
just
just
a
few
things.
A
few
corrections
in
the
view
here
and
there
also
the
tights
title
of
the
queue.
If
you
have
it
as
manage
files,
or
if
this
makes
sense,
I
have
a
screenshot
there.
But
if
you
open
the
can
I
do
that.
Can
I
share
my
screen
if
I
open
d,
the
sandbox,
the
call
request,
just
let
me
see
if
I
can
demonstrate
what
I'm
talking
in
that
real
quick.
D
A
D
To
be
Malik's
content
as
well
and
now
lemons
file
class
yeah,
so
this
is
all
under
content,
so
it
should
be
content
manager
is
instead
of
manage
files
manage
files,
because
I
have
other
pull
requests
that
are
replacing
this
with
the
view
and
it's
again
manage
content
comments,
so
in
content,
planets
comments
and
then
also
these
changes
to
content
manage
content.
So
everything
is
under
a
title
that
says
content
and
then
it's
manage
content
manage
comments,
manage
files
yeah.
How.
D
Is
a
wonderful
request
for
it
that
recur
ex
it?
So
it's
another
issue:
it's
one
of
the
small
issues
that
I'm
fixing
all
the
the
views.
Small
issues
like
that
egg,
fine
to
change
the
just
the
content
and
this
becomes
manage
content,
and
this
becomes
manage
comments
and
all
these
are
views.
Excellent,
okay,.
A
You
could,
but
I
don't
owe
you
could,
but
that's
it's
not
a
very
safe
thing
to
do,
because
what
happens
is
if
you
just
copied
an
existing
config
file
like
the
one
that
ships
with
the
module
and
just
copied
it
all
in
it.
That
makes
it
inconsistent
in
the
future.
If
we
were
to
change
that
config
file
in
the
future
and
also
have
an
update
hook
that
changed
it,
you
would
end
up
with
like
an
old
site
that
updated
would
copy
a
newer
config
file
than
the
previous
then
like
gosh.
A
This
is
confusing
to
explain
it's
the
same
reason
why
you
can't
copy
you,
while
you
can't
use
hope,
schema
to
update
a
database
table
because
hug
scheme
of
my
change
or
the
config
file
might
change,
and
so
the
future
version
that
gets
changed.
The
update
hook
will
be
expecting
the
old
version
and
then
subsequent
update
hooks
will
build
upon
the
old
version.
That
might
not
be
the
one
that
got
copied
in
anymore
if
that
makes
some
sense.
So
when
it
comes
to,
if.
G
A
D
An
easy
question
about
this
by
the
way
and
the
way
we
have
two
ways
of
doing
it.
There
were
two
full
requests
that
actually
did.
This
whole
thing
copied
the
entire
JSON
file
as
a
enough
in
a
format
of
an
array,
and
there
were
another-
took
two
bull
request,
but
what
they
did
is
they
read
the
JSON
file.
They
config
that
could
befall
config
Stuart
building
a
data
object
outside,
and
then
they
did
Jason
d'accord
on
that
I
have
an
issue.
D
A
Yeah,
but
it's
similar
to
any
other
config
file.
That's
whenever
we
created
a
config
file
like
all
of
the
stuff
that
was
copied
out
of
variables
in
Drupal,
7
and
then
put
into
config
and
in
fact
drop
or
or
with
we
created
a
new
module
or
create
a
new
config
file.
We
never
copy
the
file
out
of
the
config
directory
and
just
load
it
into
the
active
config
directory
for
the
same
reason.
A
So
whenever
it
would
create
a
config
file,
you
actually
need
to
code
it
exactly
the
way
the
default
config
file
needs
to
be
in
the
update
hook
and
then
just
like
config
save,
and
that
makes
it
so
that
the
starting
point
is
always
consistent.
So
subsequent
update
hooks
that
build
on
that
the
build
on
modifying
that
config
file
will
all
get
the
same
expected
output,
while
new
sites
will
use
the
default
config
file
that
that's
in.
G
D
D
A
Yep,
but
either
way
both
you
guys
are
definitely
right
that
we
need
an
update
hook.
That
actually
creates
this
view
for
existing
sites.
There
are
I
mean
we
do
a
fair
amount
of
you
know
if
you
update
your
site
from
an
old
version
of
backdrop
to
a
new
version
of
backdrop
that
the
new
functionality
is
there,
but
it's
not
turned
on,
but
this
is
a
situation
that's
I
feel
like.
A
D
Also
another
thing
that
I
wanted
to
ask
the
chick
what
happens
but
seeing
we
are
replacing
those
those
legacy
triple
seven
pages
with
views,
but
but
we
allow
these
views
to
be
disabled.
So
if
it
is
stable,
if
you
disable
the
manage
content
or
admin
content
view,
then
people
lose
the
entire
menu
of
find
content.
That
is.
B
D
A
Yep,
that
is,
that
is
the
case
and
I
agree,
but
let's,
let's
make
a
new
issue
of
probably
for
that
for
the
discussion,
yeah,
okay,
that's
it!
Those
are
the
three
main
items
for
1.6.
It's
funny.
I
was
feeling
really
good
about
the
lab
latter
two
entity
view
modes
and
file
view,
but
now,
after
talking
about
them,
I'm
feeling
a
little
less
confident
even
about
them,
but
we
have.
A
We
have
a
couple
of
days
to
get
them
into
a
committable
state
and
then
a
couple
of
weeks
to
actually
do
follow-ups
to
fix
any
bugs
that
that
we've
accidentally
introduced.
So
we've
got
some
work
to
do.
We've
only
got
today,
let's
say
three
days
to
actually
polish
these
things
up
and
any
other
issues
that
are
tagged
for
the
1.6
release.
So
I'd
say
we
should
put
our
focus
on
any
few
modes
in
the
file
view
which
seemed
like
they
both
have
small
bugs
and
upgrading
issues
and
testing
issues.
A
A
Okay,
anything
that
we
should
talk
about
next
week
that
that
we
would
like
to
add
to
the
agenda
yeah,
not
really
I,
think
I.
Think
sticking
with
our
focused
agendas
up
until
the
releases.
That
is
a
good
idea.
So,
okay,
that's
it!
Thank
you!
Everybody
for
watching,
think
you
are
ready
for
joining,
we'll,
see
you
guys
and
get
her
in
an
issue
queue
and,
let's,
let's
keep
cracking
all
right,
bye.
Everybody.