►
From YouTube: Backdrop Weekly 10/13
Description
Today’s development agenda: http://bit.ly/2dPNTGt
A
All
right
we
are
on
air,
it
is
Thursday
octobre,
13,
1013,
chris
carter's
birthday,
and
it
wins.
Big
exercise
fan
we're
not
anyway
bunch
of
other
stuff
on
1013
team.
It
was
okay.
A
This
week
we
are
one
week
out
from
back
in
all
of
that
rocks.
Thank
you.
So,
okay,
Andy
feedback
on
that
as
well,
led
in
with
a
update,
know.
If
anyone
else
here
has
any
updates
nothing's
to
burgeon
going
on
at
the
moment,
okay
infrastructure
tasks.
A
So
hopefully
we'll
get
a
little
movement
going
on
that
this
week.
I
don't
know
if
anything's
happened
in
the
issue
queue,
but
there
has
been
emails
going
around
so
I,
don't
know
if
we
go
down
by
next
week,
it'll
be
nice.
A
Alright,
the
next
release.
Anybody
should
kick
this
over
to
Nate
151.
B
Yeah,
okay,
so
the
next
release
is
151,
which
I'd
hope
to
release
this
past
week
for
that
that
didn't
come
to
pass
so
we'll
definitely
get
it
out
before
bad
camp.
So
that
me
this
week,
1.51
we've
made
some
really
important
fixes.
That's
they've
already
been
merged
in
all
of
the
most
important
ones,
including
loaded
up.
B
Let's
see
we
fixed
the
upload,
we
50
fix
the
Installer
module
so
that
it
works
for
manual
module
installations,
which
is
great.
Let's
see
we
fixed
some
ill,
some
issues,
the
hero
block.
Oh,
this
is
important.
We
fixed
the
homepage
layout
by
default
so
that
it
uses
a
drop-down
menu.
So
basically
I
mean
there's,
there's
nothing
like
super
critical
in
151,
but
there
are
some
pretty
serious
like
confusion,
issues
that
could
potentially
be
caused
by
the
bugs
that
are
in
there
right
now,
but
they've.
All
those
have
all
been
fixed.
B
There's
a
new
batch
of
issues
that
I
need
to
review
as
usual,
which
is
awesome
that
that
looks
like
they
could
all
potentially
go
in
as
well.
So
I'm
probably
getting
five
or
six
more
of
these
minor
issues
and
then
we'll
make
15
151
outs
there's
an
issue
at
267.
That
is
the
once.
151
is
outs
for
actually
in
the
preparation
for
151.
Go
through
that
checklist
after
151
is
outs,
we
plan
on
making
it
so
that
pantheon
gets
updated.
B
Historically,
that's
what
we've
been
doing,
although
in
the
future
we're
hoping
like,
but
starting
with
1.6
in
the
new
feature,
freecycle
we're
hoping
that
160
we
can
push
out
to
Pantheon
directly
rather
than
waiting
for
the
first
bug-fix
release
like
this.
So
anyway,
that's
it
for
151.
It
should
be
out
in
the
next
couple
of
days.
B
This
is
a
little
odd
that
that's
an
infrastructure
tasks,
I
guess
well
anyway.
That's
what's
in
the
agenda!
Next
item
is
a
backdrop
CMS
org
Jen.
You
want
to
take
it
to
take
it
back.
Tour
I,
also
great
little.
A
Weird,
that's
in
that
part
of
the
agenda,
but
that's
where
it
was
so
sorry
about
that
anyway.
What
actually
is
infrastructure
is
our
website
and
we've
got
three
things
that
are
kind
of
on
the
most
important
to
do
list.
One
of
them
is
getting
case.
Studies
up
and
I
would
love
to
be
able
to
get
at
least
two
case
studies
up
on
the
site
by
bad
camp,
and
those
are
the
two
that
we're
going
to
have
case
study
presentations
on
at
the
backdrop
summit
and
back
here.
A
That's
wishful
thinking
because
we
have
designs,
but
we
do
not
have
any
implementation
of
GSA's
on
the
site
as
of
today,
but
we'll
see
I
just
thought
it
would
kind
of
fair
nicely
if
we
could
let
people
kind
of
go
home
and
show
off
what
they
learned
at
the
summit
and
so
we'll
see.
The
next
item
is
documentation
which
I
think
is
coming
along
really
well,
I,
don't
know
Tom
if
you
have
an
update
for
us,
but
I
would
love
to
know
when
that
is
ready
to
link
up
in
the
mid.
C
Sure
in
the
air
me
yep,
okay,
mom
I've
gone
through
and
corrected
all
punctuation
usage
of
spelling.
One
time
I
appears
go
into.
Screenshots
is
wherever
they're
needed
and
I
think
I
had
posted
something
about
the
possibility
of
getting
those
to
expand
on
hand
of
the
borough's
quad
box,
I
think,
is
what
you
had.
So
we
can
get
back
killing
them.
I
don't
know
if
I
should
do
that
before
or
after
so.
A
I
would
say
the
screenshots
are
not
a
blocker
for
putting
the
documentation
into
the
menu,
I
think
is
as
long
as
you're
comfortable
with
the
language
that
can
go
in
anytime.
We
can
add
the
screenshots
as
we
have
them.
I
don't
want,
because
there's
a
lot
of
places
where
we
could
probably
have
screenshots
and
we
can
put
them
in
whenever
adding
color
box
module
to
the
site
is
also
pretty
straightforward
and
I
think
you
know
the
next
time
anyone's
in
there.
I
think
I
said
I
would
look
at
that
today.
A
That
can
just
be
added
think
it
should
be
a
blocker
for
anything.
A
loop
it'll
be
okay
without
them
is
better
with,
but
I
don't
think
it
should
prevent
the
link
here.
A
Nope
great
and
then
the
third
item
for
the
website
would,
which
is
long
overdue,
is
getting
the
forum
figured
out.
It
just
hasn't
been
a
priority,
because
we've
had
so
much
other
stuff
going
on
and
not
enough
people
working
on
it.
I
no
talk
once
done
a
great
job.
Porting,
the
flora
module
is
hosting.
It
he's
even
got
like
a
PR
opening
its
core,
so
we
could
have
any
users
try
it
out.
A
That
is
next
on
list
as
soon
as
we
get
documentation
linked
up,
which
I
think
should
be
any
day
now
and
when
we
get
the
showcases
done,
which
should
also
be
any
week
now
so,
hopefully
we'll
be
able
to
return
to
the
forums
and
make
sure
people
have
a
place
to
talk
about
back
job
shortly
next
item
under
infrastructure:
oh
there's,
some
more
infrastructure!
The
next
item
is
for
backdrop.
Cms
project
report.
D
A
Already
talked
about
the
bug-fix
release
151,
should
we
talk
about
any
of
the
important
bug.
E
B
A
B
We
have
an
issue
for
that
making
the
hero,
beep,
Oh,
bleep
life
left
to
right
across
the
entire
width
of
the
browser
window,
but
yeah
that
we
haven't
gotten
any
real
great
solutions
to
that
problem.
Yet
so
maybe
some
more
discussion
might
be
necessary
there.
That
might
not
be
possible
in
15.
It's
definitely.
B
D
A
A
I,
don't
know,
there's,
definitely
lots
of
solutions,
I,
don't
know
what,
where
our
line
is
for
what
we
want
in
core
like
I,
feel
like
we
need
to
figure
out
how
big
an
issue
this
is
for
people,
because,
right
now,
it's
like
we
have.
We
have
a.
We
have
a
hero,
it's
just
not
a
full
screen
here.
Oh
it's,
an
old
school
like
my
website,
fits
inside
this
box
kind
of
hero
and,
if
we're
okay
with
that,
then
maybe
we're
fine
with
leaving
for
really
pristine.
A
To
sacrifice
our
morals
a
little
bit
for
the
quality
of
the
code
that
goes
into
core,
so
I
don't
know
how
to
make
that
decision,
because
I'm
not
I'm
not
particularly
picky
about
how
pleasing
the
code
is.
I'm
also
not
particularly
aware
of
like
how
pretty
the
free
feature
is
so
be
great
to
get
more
people
to
eyes
on
that
and
say
like
how
important
is
this
feature
to
we
really?
Is
it
important
up
that
we're
really
willing
to
put
some.
B
A
That
people
will
likely
copy
this
and
do
it
for
themselves
like
is
it?
Is
it
a
tool,
we're
giving
them
to
be
like
hey,
look
at
this
cool
hack
you
can
use,
or
is
it
like
we're
teaching
them
to
do
bad
things,
I
don't
know,
but
yeah.
Anyone
was
watching
this
and
wants
to
weigh
in
on
that.
I
would
love
more.
In
fact,
ya.
B
Know
an
idea
we
haven't
suggested
yet
and
I'm
hesitant
to
do
it
now,
but
here
we
go
is
that
we
could
make
a
whole
nother
round
of
layouts
again
like
we
could
deprecated
all
the
current
ones
make
all
new
rounds.
That
is,
that
has
the
dips
that
we
need
that
would
allow
for
the
selects
ability,
because
we
almost
had
these
at
one
point
right,
but
then
we
we
back
down
from
it
more
like
no,
no,
if
your
dibs
and
now
we've,
we
created
the
situation,
we're
now
in.
B
A
E
E
E
A
B
A
A
B
Let's
see.
Okay,
the
next
issue
that
we
have
this
is
in
the
important
bugfix
category
is
issue.
19
20,
which
is
the
manual
module
upload,
doesn't
work
in
the
Installer
montreux.
But,
as
I
mentioned
earlier,
that
bug
has
been
fixed
yay,
so
we
can
take
that
one
off
the
agenda
for
next
week,
because
151
will
be
out
and
that
book
will
be
fixed.
Alright.
B
Alright,
the
next
item
on
the
agenda
is
the
1.6
minor
release
which
is
coming
up
in
january.
Fifteenth
2017,
we're
now
doing
a
feature
freeze
which
will
take
place
january
first
2017,
so
we
have
until
then
to
make
improvements
to
the
1dx
branch
to
make
the
new
1.6
version
release
the
items
that
we've
got
slated
of
being
of
importance
include
issue
1087,
which
is
the
improve
the
rich
text
editor.
B
B
Added
it
yeah,
because
it
really
wasn't
in
one
point:
oh
of
course,
so
anyway,
there's
a
bunch
of
items
in
there,
that's
a
meta
issue.
Most
of
them
are
up
for
grabs.
If
you're
interested
in
doing
integration
into
ckeditor,
we
still
need
people
that
have
the
time
and
interests
to
to
take
a
look
at
any
of
those
and
any
improvement
we
can
make.
We
can
merge
in
all
a
cart
as
those
improvements
are
made.
B
I
wait:
yeah
I
think
it
might
have
been
bumped
to
place
so
anyway.
So
now,
here
we
are
version
1.6
and
it
looks
like
this
time.
We've
got
a
real,
strong
motivation
behind
completing
the
reference
module,
which
is
akin
Eric
node
user
term,
any
other
kind
of
entity
reference
field
as
an
option
in
core.
B
So
he's
de-escalating
from
that
a
rather
challenging
feature
and
just
focusing
on
the
deeper
field
that
is
added,
which
is
great,
that
definitely
simplifies
things
and
I.
Think
that
it's
you
know
the
right
level
of
complexity
for
for
corn
the
first
place
he
is
looking
for
additional
help.
Let's
see
he
suggested.
B
He
needs
help
building
out
the
tests,
so
they
needs
to
be
tests
written
for
the
reference
module
and
views
and
creation
needs
to
be
rounded
out
so
he's
looking
for
helping
us
to
particular
spots.
If
you
give
reference
module
by
shots,
it's
in
the
contributory
and
then
file
pull
requests
against
that
module
and
eventually
that
will
be
moved
the
whole
thing
into
court
as
a
project.
So,
let's
see
next
issue
is
issue.
B
1448,
which
is
add
a
media,
/
file,
entity,
solution
and
I
think
this
one
can
really
get
very
large
in
scope,
but
the
first
step
is
to
make
files
into
it.
They're
kind
of
like
a
top
level
entity
like
we
treat
nodes
and
users
and
terms
that
we
should
make
a
listing
with
views
under
the
under
the
content,
section
so
add
mint
content
and
then
files
and
then
make
it
so
that
you
can
manage
files
directly,
such
as
deleting
them
or
replacing
them
a
separate
from
them.
B
The
pieces
of
content
that
they're
actually
attached
to
so
that's
step,
one
and
then
step
two
is
potentially
making
them
feel
the
bowl
step.
Three
is
then
integrating
into
the
ckeditor
or
the
rich
text
editor
dialog
for
inserting
images.
So
that's
a
lot
of
that
could
go
on
for
a
long
time,
but
step
one
is
really
pretty
straightforward.
You
know
make
of
you
make
it
so
that
we
can
edit
files
directly
and
delete
them
and
that
that
should
be
a
pretty
self-contained
project
and
if
we
get
that
done
for
1.6,
that's
a
good
start.
B
They're
both
dealing
with
managing
a
large
number
of
layouts
or
I-
guess,
maybe
not
a
large
number
but
managing
the
same
or
similar
blocks
across
multiple
layouts,
like
the
header
menu,
for
example,
or
the
primary
navigation
menu
like.
If
you
want
to
change
the
way
that
that
is
displayed,
you
want
to
change
the
way
it's
displayed
across
all
of
your
layouts,
not
just
one
of
them
and
right
now.
There's
a
lot
of
work
to
go
through
every
individual
layout
and
update
every
instance
of
that
block.
B
So
we
have
a
couple
of
different
solutions
that
have
been
suggested
to
handle
that
one
of
them
is
making
it
so
that
you
can
configure
a
block.
And
then,
if
you
update
one
place,
it
kind
of
dates
in
all
of
them
and
the
other
one
is
that
if
you
could
modify
like
a
collection
of
blocks
or
an
entire
region
and
have
that
collection
or
region,
be
the
settings
for
the
entire
region
or
collection
of
blocks
be
applied
across
all
layouts
as
well.
So
the
first
approach
is
2245.
B
The
second
approach
is
1886
and
we're
still
trying
to
figure
out
what
the
best
solution
is.
Is
there,
but
I
do
think
that
thinking
on
those
two
problems,
there
is
great,
because
that
would
be
great
UX
improvement.
If
users
or
able
site
builders
were
able
to
more
quickly
modify
their
entire
cycle
at
once,
and
not
so
much
busy
work.
B
B
We
have
a
like
a
it's
it's
great
from
our
perspective
that
we
can
now
use.
We
can
put
a
block
into
a
layout
and
have
that
be
exported
as
part
of
the
configuration
and
move
across
firemans.
But
it's
not
so
hot
and
that's.
You
could
very
easily
have
like
thousands
of
custom
blocks,
for
example,
as
you
would
probably
end
up
having.
If
you
had
a
carousel
that
had
like
regularly
rotating
content,
you'd
probably
put
thousands
of
those
pieces
of
content
over
a
long
enough
period
of
time,
so
that
issue
is
still
ongoing.
B
It
looks
like
we're
still
kind
of
working
out
what
would
be
the
best
solution
there.
So
more
thinking
on
that
would
be
great
or
somebody
wants
to
take
a
stab
at
just
seeing
how
one
approach
or
the
other
would
work.
That
might
be
a
good
option
too,
because
we're
kind
of
stuck
at
a
stalemate
where
we're
talking
ourselves
in
circles.
On
that
issue,
let's
see
John
I
think
you
may
have
added
this
one
right
menus
and
breadcrumbs
clean
up.
A
You
can,
if
I
can
unmute
myself
yeah.
That
was
something
that
I
Gregory
mentioned
last
week,
where
ever
since
the
new
menu
system
went
in,
I
think
it
was
in
drupal.
A
7
breadcrumbs
have
been
sort
of
screwed
up
interval
where
there's
some
weirdness
about
how
to
get
the
breadcrumbs
to
actually
match
I,
either
the
menu
trail
or
if
you
have
pages
that
aren't
in
the
menus,
like
you
have
to
build
like
a
fake
trail
for
them
to
work
and
I
was
I
was
just
looking
through
the
queue
to
see
if
I
can
find
a
single
issue
on
fixing
when
using
breadcrumbs.
A
But
it
looks
like
there's
about
30
menu
and
breadcrumb
related
issues
that
I
think
that
the
root
cause
us
might
be
something
that
we
could
clean
up
for
all
those
things.
But
I
don't
have
an
issue
for
it.
Yet.
So
it's
just
trying
to
make
breadcrumbs
make
sense
to
people
like
it
did
in
back
in
back
in
the
good
old
days,
but
yeah
breadcrumbs,
worship,
/,
mystery.
B
Okay,
that's
pretty
much
it
for
the
1.6
released
at
least
the
features
that
were
focused
on
it
says
more
to
be
determined
here
in
the
agenda,
but
I
think
that
expanding
the
scope
beyond
that
is
getting
overly
aggressive,
I
think
that's
Leo.
B
Yeah,
those
are
just
the
areas
that
we'd
like
to
get
accomplished
for
1.6
there's.
That
is
not
actually
guarantee
that
these
things
worship
and
if
some
other
feature
that
is
well
suited
to
1.6,
comes
along
and
is
ready
for
production.
Then
that's
another
option,
that's
that
we
may
make
it
into
1.6
as
well.
B
There's
also
an
issue
tracker,
of
course,
that
there's
a
tag
for
1.6.
That
includes
other
issues.
Besides
those
mentioned
here
and
you
can
find
those
on
github,
let's
see
Oh
Gregory.
Are
you
in
a
situation
where
you
can
do
the
community
update?
B
B
Jenna
you
I'm
dating
one
okay.
B
B
B
Well,
anyway,
we're
really
excited.
We've
got
a
really
good
set
of
things
to
be
speaking
about.
If
you're
new
to
backdrop,
then
you
can
attend
the
training
board.
You
know,
I
just
want
to
drop
in.
You
can
attend
training
as
well,
and
then
the
summit
is
for
everybody,
that's
interested
in
working
on
backdrop
and
improving
it.
B
You
don't
need
to
be
familiar
with
that
drop
and
if
you
attend
the
training
you're
more
than
qualified
to
also
attend
in
this
limits,
and
we
can
work
together
to
make
drop
better
and
do
it
all
in
person
which
might
accelerate
some
of
these
sticky
issues
in
which
we've
been
talking
in
circles
for
a
little
while,
so
the
summit
is
on
Thursday
I
got
it
backwards.
It
looks
like
the
summit
is
on
Thursday
and
then
the
training.
D
A
Way
the
summit
is
set
up
right
now,
and
I
can
definitely
use
some
feedback
on
this.
For
anyone
who's
there
is
the
first
half
of
the
morning
is
a
very
kind
of
high-level
like
what
is
backdrop
kind
of
thing,
so
anyone
that's
new
and
never
heard
of
drug
before
but
interested
come
and
learn
what
backdrop
is
and
on
the
very
end
of
the
day,
it
is
reserved
for
discussion
on
what
we
should
do
and
backed
up
to
since
there's
going
to
be
a
whole
bunch
of
people
there
who.
D
A
A
Jack
is
going
to
do
a
talk
about
why
it's
important
to
believe
in
something
like
backdrop
Wes,
if
you
want
to
add
something,
I've
got
a
hole
in
the
schedule.
I,
don't
really
know
what
to
do
with
you
and
yeah
it.
A
We've
got
people
from
Kalibak
Cynthia
Theon
talking
about
back
trip,
integrates
at
other
things,
so
we're
watching
this
marking
out
at
actual
timeline,
but
there
won't
there
it'll
be
it's
hard
because
there's
going
to
be
a
bunch
of
hardcore
backdrop,
people
and
a
bunch
of
I've
never
heard
of
vector
of
people
so
trying
to
squeeze
it
up
at
all.
In
one
day,
the
interesting
really
fun.
A
All
right,
we
also
are
doing
our
normal
backdrop,
talk
on
Sunday,
so
anyone
who
is
in
our
student
participating
in
that
I
think
would
be
great
to
get
as
many
vector
people
as
possible
kind
of
up
on
stage
in
front
of
the
room
with
Drupal
people,
Oh
getstring,
the
summit
I'm,
not
sure
the
internet
is
going
to
be
very
good
and
that
location,
but
it
we
could
try
it.
A
F
A
B
This
is
in
that
same
category
as
bad
camp,
but
I
think
it
would
be
good
if
we
could
get
together
in
schedule.
A
separate
meeting
for
everybody,
that's
planning
on
presenting
just
so
that
we
all
kind
of
can
get
on
the
same
page
and
feel
like
we're,
prepared
and
know
what
resources
we
have
and
everything
for
for
the
summit.
A
E
A
E
E
A
A
E
A
D
B
Okay,
well,
not
that's
great,
it's
a
meeting
hooray
as
always
we're
going
to
be
working
today.
Sprinting
working
the
issue
queue.
Hopefully,
I'll
get
some
more
things
merged
in
for
the
151
release
today,
and
you
can
check
us
out,
we
have
a
git
er
channel.
You
can
find
from
the
resources
page
on
backup
seamless
toward
the
primary
place
where
we
do
most
of
our
communication
of
courses
and
get
up
issue
queue.
So
we
will
see
you
guys
online.