►
From YouTube: Backdrop Weekly 12/1
Description
Today’s development agenda: http://bit.ly/2gqZqLq
A
Hey
we're
on
a
happy
december,
everybody,
it's
December.
First
we're
about
to
do
a
development
task
check
in
meeting
for
backdrop,
CMS
to
start
off
the
meeting.
I
just
wanted
to
make
an
announcement
that
I
have
requested
from
the
phpstorm
folks
are
set
of
licenses
that
we
hand
out
to
contribute
I
rear.
So
I
have
submitted
a
new
application
to
get
either
those
much
like
the
license
rollover
date
to
be
pushed
out
another
year.
I
guess
I'm,
not
sure
exactly
how
that
works,
but
they
wanted
me
to
resubmit
the
ablution
I.
A
Did
it
we'll
see
where
it
leads
infrastructure,
stuff
we're
making
a
bunch
of
changes
to
dr.
of
CMS
org?
Most
importantly,
we're
first
on
the
list,
maybe
not
most
importantly,
we
have
built
a
new
content
type
for
showcases
we're
trying
to
set
up
a
view
where
people
can
actually
see
them
may
have
designed
to
be
able
to
do
which
built
a
view.
A
If
it's
not
be
view,
it
still
needs
some
work
and
I
also
think
we
should
do
some
work
on
the
content
type
as
well
to
make
sure
we're
asking
people
all
the
right
questions
to
get
the
right
kind
of
contents
that
we
get
some
compelling
stories
about.
Why
you
chose
backdrop?
What
is
this
site
actually
doing
for
you,
rather
than
just
hit
a
pretty
picture
of
my
website,
which
is
good,
but
it
would
be
good
if
we
could
actually
get
those
stories
in
there
too.
A
So
right
before
this
call,
I
was
looking
at
the
Blue
Drop
Awards,
which
is
a
website
that
was
made
specifically
to
generate
content
for
drupal
showcase
section
to
see
how
they
phrase
the
questions
to
try
and
get
a
compelling
answers
from
people
telling
content
for
people
who
are
submitting
sites
for
the
contest.
So
hopefully
I'll
get
some
insights
from
there
and
we'll
be
able
to
figure
out
how
to
get
some
better
content.
But
for
now
we
need
to
see
the
view.
The
documentation
on
backed
up
CMS
org
is
also
something
we've
been
working
on.
A
A
Just
to
get
this
item
off
of
our
list,
we
would
create
a
new
top-level
link
called
documentation,
and
then
we
are
working
on
a
redesign
of
backdrop
CMS
to
org
that
will
include
a
menu
that'll,
be
our
fancy
drop-down
menu,
that's
in
court,
and
then
we
can
reorganize
them
in
you
to
put
all
the
links
where
they're
supposed
to
be
when
that
redesign
happens.
So
you
know
we
already
have
too
many
links
in
our
top
menu
right
now,
but
I
think
it
would
be
better
to
have
a
link
to
documentation
than
no
link
to
documentation.
A
Knowing
that
we're
going
to
fix
that
problem
in
the
near
future.
Does
anyone
have
any
objections
to
just
putting
that
link
in
the
top
level
for
now?
Okay,
I'll?
Do
that
after
this
meeting
or
whoever
can
do
it
whenever
but
yeah
I
would
love
to
just
get
that
get
that
off
the
to-do
list,
since
it's
mostly
done
and
then
other
things
we
are
working
on,
the
homepage
redesign
you
guys
might
have
seen
at
wes's
designs
as
of
late
I
know
last
week.
A
So
that's
the
week
before
wats
you
did
a
walkthrough
of
what
your
design
look
like,
not
sure
if
anyone's
got
to
see
that
design,
yet
I
think
it
looks
fantastic,
it's
a
it
going
to
be
a
huge
improvement
on.
What
we
have
now
is
just
something
people
have
been
clamoring
for
for
a
while.
My
started
implementation
this
week,
so
I'm
not
sure
when
that
I'll
be
done,
I
think
in
a
perfect
world,
if
we
can
have
that
done
by
january
fifteenth,
and
so
we
kind
of
coincide
with
the
release
of
16.
B
A
And
then
next
on
the
list
is
the
forum
module
so
as
soon
as
we
get
these
showcase
and
homepage
rebranding
done,
those
were
kind
of
marketing
efforts.
Documentation
done
that's
for
existing
users.
The
forum,
I
think,
is
also
something
that
existing
ages
you're
going
to
benefit
a
lot
from
having
a
nice
safe
place
to
talk
to
each
other
about
backdrop.
A
It
was
something
to
which
really
useful
in
the
early
days
of
drupal
and
something
people
have
been
clamoring
for
so
I
would
love
to
see
that
get
done
too
I
know:
we've
got
a
port
of
the
forum
module
and
a
bunch
of
interesting
work
going
on
there.
So
I'd
like
to
take
a
look
at
issue
again
soon
and
that's
it
for
backup,
CMS
org.
Does
anyone
have
anything
they
want
to
add
No?
Ok,
let's
move
on
to
backdrop
the
project,
because
we
are
needing
to
work
on
it.
Ok,
quick
sketch!
B
There
are
a
couple
of
issues
that
we
would
like
to
focus
on
and
if
we
can
complete
them,
then
we
will
make
153
and
then
push
all
the
existing
issues
to
154,
one
of
which
has
been
an
issue
since
1.5
came
out
and
that
is
the
full
bleed
hero
in
basis.
I
think
we've
reached
agreement
as
to
how
we
will
go
about
that,
but
I
don't
think
yeah.
B
Anyway,
so
no
reelect,
a
video
on
that
one.
That's
issued
2194
fixing
the
the
hero
image
in
basis.
The
recommended
solution.
There
is
that
we
will
override
the
homepage
single-column
layout.
So
really
that
means
read
the
single
column
layouts
only
and
not
any
of
the
other
layouts,
so
that
actually
would
apply
to
more
than
just
the
home
page,
but
the
home
page
by
default
would
be
using
it
an
issue
that
has
come
up
recently
to
begin
of
the
month.
We
found
out
that
backdrop.
B
The
Installer
seems
to
be
broken
when
installing
in
other
languages,
it's
unclear
when
this
originally
broke.
It's
issued,
2329
I
know
that
we've
had
backdrop
install
and
other
languages
previously
I'm,
guessing
that
it
may
have
been
a
1.5
issue
that
that
may
have
introduced
it
and
my
complaint
in
that
issue.
We
actually
already
have
a
working
solution,
I
believe,
but
my
complain.
B
That
issue
is
that
we
should
have
more
testing
on
that,
but
I
realized
as
I
think
others
have,
that
we
are
unable
to
test
the
Installer
currently
because
simple
test
skips
the
installation
or
it
doesn't
use
the
normal
installer,
especially
not
install
that
PHP
to
do
the
installation.
So
that's
an
area
where
we
should
live
in
the
meantime.
B
We
may
just
need
local
local
individual
testing
on
that's
just
with
people
justing
it
out
and
making
sure
that
it
works
and
again
because
even
our
live
sandboxes
skip
the
installation
that
requires
actual
manual
testing
on
on
people,
actually
downloading
the
poor
request
in
trying
it
out
not
ideal,
but
I.
Think
for
the
sake
of
fixing
this
vibe
like
testing.
The
installer
is
a
much
larger
problem
than
fixing
this
particular
issue.
B
Let's
issue
23
29:
ok,
that's
it
for
1.5
and
the
minor
things
that
we're
fixing
here
and
there
for
1.6.
The
next
minor
release
will
be
coming
out
january,
fifteenth
2017,
that's
a
month
and
a
half
away,
and
we
have
a
feature
freeze
coming
up
January
first,
so
we
have
one
month
to
push
for
it
forward
as
much
as
we
can
on
all
of
these
issues
that
we
have
slated
for
1.6,
the
first
of
which
is
reference
module.
Marfan's
module
has
been
making
some
progress.
B
We
also
still
have
the
the
question
of
upgrade
paths
and,
in
particular,
an
upgrade
path
from
term
reference,
module
the
upgrade
paths
from
the
contribs.
If
these
modules
may
continue
to
live
in
contribute
initially,
but
depending
on
what
we
decide
to
do
with
term
reference,
because
that
is
a
core
module
currently
making
that
an
upgrade
path
to
the
supporting
core
would
be
preferable.
I
did.
A
A
There's
any
reason
that
a
term
reference
field
couldn't
be
an
entity
reference
field
as
long
as
that
had
the
existing
widget,
the
existing
configurations
all
still
in
place
so
I
want
to
go
through
and
look
at
exactly
what
those
differences
are
because
I
haven't
gotten
super
intimate
with
a
new
reference
solution
and
see
what
it
looks
like
to
get
from
one
to
the
other,
and
if
we
can
still
get
the
same
exact
thing
after
that
great
path.
Yeah.
A
A
B
No
I'm,
saying
like
like
in
the
node,
object
the
properties
that
say
these.
The
terms
that
structure
will
change
with
reference
module,
and
thus
it
will
break
all
modules
that
are
currently
using
taxonomy
terms,
because
they're
looking
in
the
node
object
in
a
particular
location
for
the
term
information.
If
that
moves,
just
fields.
A
A
A
B
A
B
Okay,
next
issue
is
issued
3
15,
which
is
adding
entity
view
modes
to
core
making
it.
So
you
can
add
your
own
view.
Modes
Allah
display
sweet
without
needing
to
install
any
other
modules.
It
looks
like
this
has
a
pull
request,
which
I
haven't
had
a
chance
to
take
a
look
at.
Oh,
it's
duck
Beaumont
port
bust,
which
is
always
encouraging.
C
B
B
B
B
B
My
god
had
been
that
we
would
make
a
like
a
reusable
block.
That
would
be
like
a
section
that
was
like
these
are
blocks
that
are
being
reused,
but
this
approach
thus
far
is
more
direct
and
that
it
just
allows
you
to
copy
in
one
layout
the
configuration
of
a
block
from
any
other
layout,
and
so
there's
not
like
a
master
copy
of
the
block
somewhere.
It's
just
literally
another.
B
Any
arbitrary
layout
can
borrow
any
other
arbitrary
layouts
block
settings,
which
I
think
actually
is
more
direct
and
would
probably
be
easier
for
people
understand,
but
it
might
also
be
maybe
a
little
bit
sloppier
from
a
site
structure
and
site-building
standpoint,
but
that's
not
necessarily
a
bad
thing.
You
know,
sometimes
things
that
are
looser
and
easier
can
be
better
than
things
that
are
harder
and
more
structured,
so
some
trade-off
there.
That
I
think
would
be
valuable
for
us
to
discuss
as
to
what
approach
is
preferable
there.
B
B
B
A
B
A
At
that
this
morning,
it's
actually
kind
of
interesting
what
it
does.
It
also
adds
a
new
block
class
and
the
block
class
lets
you
choose
any
region
in
any
other
layout.
Just
like
the
block
one
lets
you
have
any
block
in
any
or
any
other
layout,
but
then,
when
it
renders
it,
it
renders
a
block
with
a
region
with
all
the
blocks.
A
So
you
end
up
with
like
a
vastly
different
output,
then
I
think
what
people
would
expect,
which
is
just
all
the
rocks,
all
the
blocks
in
the
array
junt
and
they
defined
so
I
added
a
comment
on
the
pull
request
that
was
like.
Can
we
find
a
way
rather
than
having
this
block
print
a
block?
Have
this
block
changed
the
way
the
layout
renders
so
that
it
will
retrieve
like
data
from
another
layout
and
render
the
blocks
the
same
way?
The
other
layout
rendered
them,
which.
A
Yet
in
the
the
big
problem
there
I
think
is
that
we
want
to
make
sure
that
when
somebody
adds
another
block
to
a
region
in
the
parent
area,
that
block
appears
on
the
way
out
that
they
copied
the
region
from.
And
so
we
can't
just
copy
the
blocks.
We
have
to
actually
retrieve
the
data
from
the
parent
layout
and
render
them
and.
A
A
B
Yeah
yeah,
I'm
I'm
concerned
about
both
of
these
issues.
In
that,
like
we
may
be
able
to
get
some.
You
know
useful
functionality
by
doing
the
easiest
to
implement
approach,
but
we
may
be
working
ourselves
into
a
corner
of
like
a
not
very
good,
long-term
approach
that
when
we
have
more
time
or
potentially
in
contribs
Lucien,
they
come
along.
That
would,
you
know,
be
a
kind
of
situation
where
it's
like.
Oh
you
shouldn't
use
what's
in
court
because
that
one
sucks,
you
should
use
the
one
that's
in
contributor,
okay,.
B
Yeah
you
let
me
you
get
back
to
me
after
you
write
the
taxonomy
term
up
how
easy
that
actually
turned
out
to
be
I.
Think
it's
more
likely
that
we'll
do
things
like
deprecated
functionality,
you're
right
that
we
would
still
need
an
upgrade
path,
but
we
could
deprecated
functionality
and
then
remove
it
in
the
next
and
like
backdrop
to
but
yeah
anyway,
I'm
yeah,
I'm,
even
more
worried
about
the
region
copy
that
I
am
the
black
coffee,
because
it's
more
even
more
kind
of
honor
of
potential
mess.
B
B
A
An
editing
black
that
renders
all
the
stuff
that
we
want
to
move
around
in
Lance,
but
can't
currently
and
then
change
the
way
the
outs
work
to
say
if
that
block
has
been
rendered,
don't
print
the
thing
and
I
think
that
we
need
to
do
this.
I
think
we
need
to
add
one
walk
that
prints
all
the
things
together
and
then
we
need
to
add
one
block
for
each
one
individually
and
then
in
Kent,
rib
or
anyone
who's
running
a
site.
A
If
they
want
to
move
the
page
title,
they
place
the
package
title
block,
they
want
to
remove
moves
all
the
things
and
they
place
all
the
things.
And
that
way
we
don't
have
to
worry
about
removing
anything.
That's
in
the
core
layouts,
because
they'll
be
smart
enough
to
not
print
themselves
twice.
So
in
theory
that
is
possible
to
get
done
in
time
probably
need
to
have
someone
start
working
on
it
soon
or
we
won't
have
time
just
because
the
weight
affects
the
way
out.
Layouts
need
to
determine
if
walks
with
it.
B
B
B
Not
not
a
lot
of
activity
on
this
one,
but
the
the
first
item
in
that
we
would
like
to
accomplish
this
is
simply
an
interface
for
listing
and
managing
uploaded
files.
So,
basically
a
view
post
them
in
you
call
back
for
managing
an
individual
football
I
think
even
that
would
be
a
really
good
start.
Yeah
with
bulk
operations.
You
know
bulk
operations
use,
so
that
would
be
a
really
great
start
for
this
issue,
and
that
alone
would
be.
B
B
A
Recently,
Jeff
said
that
it
would,
it
might
not
be
that
much
code
to
make
a
page
lists
node
as
opposed
to
entity
type
without
a
path,
and
so
I
think
where
we
were
stuck
on.
This
is
let's
look
at
the
code
as
long
as
we
don't
think.
It's
going
to
be
so
much
time
to
write
the
code
that
you
know,
we
would
feel
sad
and
we
wrote
it
and
didn't
get
in
so
I
think
all
we
are
for
this
one
I
don't
know
having
a
month
left.
It
seems
like.
A
Maybe
it's
not
really
possible,
but
if
it
were
possible
to
do
I
like
a
what's
that
called
rabbit,
hole,
style
solution
where
we
just
did
like
an
access
denied
and
then
remove
the
UI
or
something
that
could
happen
theoretically,
unless
it
turns
up
and
feel
a
lot
more.
Where
can
we
think
it
is
so
that's
still
kind
of
a
maybe.
A
We
know
that's
the
thing
we
don't
really
know
what's
going
on
there
either.
We
know
that
menus
and
breadcrumbs
are
have
been
kind
of
a
pain
point
in
Drupal,
since
Drupal
6
and
he's
just
got
reworked,
and
it
would
be
good
if
we
could
find
a
way
to
tie
them
together
and
make
them
less
confusing
and
easier
for
people
to
follow.
A
I
think
this
issue
is
gonna
end
up
being
a
meta
of
some
really
simple
things
that
we
can
do
right
away,
that
will
improve
user
experience
and
some
really
crazy,
complicated
things
that
are
probably
going
to
be
API
changes.
So
I
think
we
need
to
figure
out
like
if
moving
blocks
on
the
page
is
a
solution.
B
A
I,
let's
check
with
Gregory,
because
I
know
he
still
had
some
strong
feelings
about
and
using
breadcrumbs
being
confusing
for
people,
but
if
all
of
the
sub,
like
all
the
action
items
we've
currently
ended,
but
it
might
be
that
we
can
close
that
issue.
My
understanding
at
recently
was
that
there
were
still
some
outliers
like
I,
figured
out
what
needed
to
be
done
about
it,
which
is
why
there
aren't
any
sub
issues
for.
B
B
B
Okay,
all
right
next
item
configuration
storage
in
the
database
is
issue
2277.
This
one
actually
from
a
technical
standpoint,
looks
really
pretty
solid.
Sentai
digital
did
some
work
on
this
back
in
october,
and
we
had
a
lot
of
back
and
forth
back
then,
but
it's
been
stalled
mostly
on
reviews.
Since
then,.
A
B
B
A
B
B
A
If
that
is
not
the
target
audience,
we
care
about
I
think
we
need
to
evaluate
whether
this
change
is
actually
any
good
for
backdrop
or
if
this
is
one
of
those
like
1%
scenarios
like
I,
think
and
I.
Don't
haven't
left
the
code.
I
don't
know
how
is
configured,
but
if,
if
it's
like,
adding
it's
like
setting
that
can
be
set
in
settings
done
PHP
and
doesn't
affect
anyone,
then
that's
not
an
issue.
A
B
B
But
as
for
the
complexity
issue,
I
think
that's
the
one
area,
that's
which
take
a
look
at
and
see
you
know
if
the
in
some
places,
we've
added
that
or
the
pull
request
adds
like
a
new
function
to
consistently
get
what
the
backend
storage
is.
Instead
of
using
the
file
paste,
one
directly,
for
example,
and
so
I
think
taking
a
look
at
that
and
saying
you
know,
is
this
making
the
code
more
difficult
to
understand
in
a
way
that
has
a
you
know,
substantial
cost?
For
backdrop
developers
then
that's
a
question
that
is
valid
all.
A
Right,
I
haven't
looked
at
the
code,
so
I
don't
know
it
just
seemed
like
a
request
that
was
against
the
best
interests
of
things.
But
if
the
code
is
minimal
and
like
the
cost
of
change
is
minimal,
maybe
it's
okay,
but
I
think
it's
something
we
shouldn't
rush
into
like
I
don't
necessarily
see
a
reason
to
put
it
into
16,
especially
if
it's
something
where
it's
like.
Maybe
there
are
other
use
cases
that
could
benefit,
but
we
don't
have
any.
It
seems
a
little
strange
to
put
it
in
now.
Oh.
B
Here's
one
more
use
case.
He
actually
put
it
right
into
some
way.
I
should
have
mentioned
this
as
well
that
his
statement
is
that
it
makes
it
easier
to
capture
the
entire
state
of
an
environment
which
I
think
is
probably
also
true,
that
it
rather
than
needing
to
capture
two
things:
the
file,
the
config
files
and
the
database.
It's
just
one
thing,
and
so
that
also
brings
it
more
in
line
with
software
like
wordpress,
where
it's
like.
B
A
A
B
And
you're
not
really
supposed
to
be
modifying
your
active
config
files
directly
anyway.
They
don't
that
what
files
gets
us
is.
It
really
gets
us
version,
control
management
of
our
config
in
an
easy
to
acquire
fashion.
Basically,
but
it
doesn't
even
eliminate
entirely.
You
can
still
export
your
config
and
then
put
that
into
version
control
and
how
the
active
directory
is
stored.
You
know,
isn't
relevant
in
a
lot
of
situations.
A
C
B
B
B
B
B
If
there
are
any
of
these
sub
issues,
there's
there's
about
20
issues
listed
and
10
of
them
have
been
fixed,
since
this
issue
was
originally
opened,
I'm,
not
sure
that
that
any
of
these
have
seen
progress
doesn't
look
like
it
so
again,
I
guess
a
call
out
is
always
anyone
that
is
interested
in
being
champion
of
the
ckeditor.
Improving
the
rich
text
editor
experience
issue.
1087
is
great
place
to
start,
because
it
has
a
whole
bunch
of
ideas
that
are
pending
of
things.
We
would
like
to
improve
about
the
rich
text.
B
B
A
A
Xml
sitemap
XML
sitemap
module
like
a
year
ago,
and
that
was
something
I
needed
on
one
of
my
site
this
week
and
so
I
started
support.
It
and
I
was
like
wait.
A
minute.
There's
one.
That's
already
here,
like
I,
found
an
issue
in
the
key
one
drupal.org
it
was
like
I
just
boarded
this
module
and
I'm
like
what
and
so
I
went
and
found
out.
A
A
In
Panama
in
the
Pacific,
Northwest,
Drupal
summits,
and
then
I
actually
had
a
question.
If
anyone
has
anything,
they
want
to
share
backdrop
related.
We
need
a
blog
post,
so
I
don't
know
if
there's
anything
cool,
you're,
working
on
or
fun
things
you've
been
wanting
to
share
with
people,
don't
know,
but
it's
been
a
while
since
we've
happen,
I
think
the
last
blog
post
was
about
bad
camp.
So
getting
something
else
on
the
blog
would
be
great.
Anyone
has
any
ideas,
let
us
know.
Maybe
we
could
get
yeah.