►
From YouTube: Backdrop Weekly 05/04
Description
Today’s development agenda: http://bit.ly/2pmSfX8
A
Hey
Ronnie
err,
happy
metaphors.
Everybody
feel
free
to
make
your
own
internal
Star
Wars
jokes.
We
don't
have
any
updates
from
the
project
management
committee
this
week.
Last
week
we
mention
that
we
are
working
with
the
software
freedom
Conservancy.
We're
still
doing
that.
We
just
haven't
made
any
significant
progress.
Who
will
post
updates
on
that?
As
it
happens,
working
on
backdrops,
a
mesta
org
wes
is
hankering
out
how
to
how
to
get
our
new
home
page
designs,
reorganized
and
put
together,
I
think
in
a
new
theme.
A
So
he's
not
here
to
give
us
an
update
on
that,
but
I
did
see
that
he
tweeted
that
he
was
working
on
it
recently.
So
that's
good
Olaf.
Would
you
like
to
give
us
an
update
on
translation,
stuff.
B
You
hear
me
wait
a
minute:
yep,
yeah,
okay,
okay,
not
really,
actually,
because
I
didn't
make
it
to
work
at
the
translation
staff
yeah
because
of
other
important
important
things,
and
there
was
one
back
with
the
extraction
module
and
which
not
considered
JavaScript
fires
with
translation
strings
in
it
or
language
streams
in
it
and
Jeff
wanted
to
have
a
look
at
it,
but
I
think
he
didn't
have
a
chance
because
of
the
upcoming
1.7
release.
So
we
actually,
we
didn't
work
on
it.
B
A
C
A
Probably
was
another
did
all
right.
Well,
let's
switch
over
to
talking
about
backdrop
CMS
with
its
upcoming
release
and
all
the
amazing
stuff
that
salmon
in
the
last
week.
So
neat
you
want
to
take
away
sure.
C
So
yeah
it's
been
one
heck
of
a
week
has
now
May.
First
was
the
code
freeze
for
the
one
point,
seven
release,
and
so
we
hustled
and
bustled
dand
tried
to
get
everything
done,
that
we
could
point
seven
an
awesome
at
least
and
I
think
that
we've
got
some
really
kick-ass
stuff
done.
But
before
we
get
to
that,
we'll
talk
about
one
point:
six
branch,
the
last
version
that
will
cut
them
out
would
be
version.
C
One
point
six
point:
four
I
think
that
that
will
come
out
May
fifteenth
the
same
time
as
one
point,
seven
does
and
we've
solved
lots
of
bugs,
like
dozens
of
bugs
and
in
a
one
point,
six
x
branch
that
will
be
included
in
that
version.
The
only
ones
that
are
of
note
a
transliteration
issue
that
when
you
use
path
auto
the
transliteration,
doesn't
actually
match
the
language
of
the
content.
In
terms
of
this
is
slightly
deeper
than
just
a
bug.
C
It's
actually
like
a
behavioral
thing
like
what
language
content
should
be
saved,
as
if,
if
you
don't
have
the
content,
translation
module
turned
on,
but
you
still
have
a
a
non-english
language
website
and
so
we're
talking
about
basically
how
to
deal
with
this
situation
of
single
language
websites
that
are
not
English
and
how
content
should
be
saved
and
treated
in
that
issue.
So
that,
like
with
a
larger
than
just
being
a
transliteration
issue.
But
it's
developing
into
some
interesting
conversation,
they're.
C
C
E
C
Of
things
happening,
err,
lots
of
discussion
happening
that
issue
to
try
to
figure
out
how
to
deal
with
that
situation.
Let's
say
an
autocomplete
style
bug
issued
2517
that
one
was
fixed
this
past
week
or
actually
my
accurately
backported
in
1.6
this
past
week.
So
we
now
have
autocomplete
styled
and
prettied
up
in
the
1.6
release
as
well,
or
we
will
all
in
1.64
and
there's
a
bucket
of
other
issues,
better
tagged
for
the
1.64
release,
basically,
these
being
other
bugs
that
are
of
substantial
note,
that
is
in
the
very
near
future.
C
Okay
items
for
1.70:
this
has
gotten
a
little
interesting
because,
because
now
that
we're
after
feature
freeze,
we
can't
actually
implement
new
functionality.
It's
really
about
bug,
fixing
things
we're
still
letting
in
UX
improvements.
So
they
have,
if
you
have
minor
changes
that
are
going
to
be
non
breaking
they're
we're
still
letting
in
changes
that
fix
bugs
and
improve
the
UX,
but
we
don't
have
any
actual
items
singled
out
as
being
an
area
of
focus.
At
this
point
on
May
1st,
we
released
a
preview
release
for
the
first
time
ever,
which
is
very
exciting.
C
C
E
Sorry,
maybe
if
we
make
this
a
habit,
which
is
a
good
thing
we
should
making
creepy
releases,
then
we
should
apply
to
recommendation
that
has
the
tasks
that
we
do,
but
we
should
add
a
task.
The
preview
release
as
well
see
how
we
have
the
tasks
that
people
get
to
do
things
you
mean
like
I'm,
a
milestone
and
github
yeah.
We
open
an
issue
and
it's
like
no.
Besides
just
tagging
the
release,
is
there
anything
else
to
do
I.
C
Understand
so,
like
a
release
issue
that
we
make
a
checklist
of
what
to
do
in
order
to
make
the
release.
Yes,
that's
a
great
idea,
because
I
just
cut
the
release
tag,
but
then
I
still
like
started,
make
release
notes,
for
example,
and
I.
Don't
think
that
we
about
it
or
did
anything
else
in
that
probably
would
have
happened.
If
had
we
follow
the
checklist
so
agree,
that's
a
great.
E
C
Okay,
let's
see
so,
let's
talk
about
what
got
done
last
week.
So
every
week
we've
been
pulling
up
this
list
of
like
features
that
have
focus
and
other
than
the
ones
that
we
took
off
a
couple
of
ones
in
the
past
few
weeks,
including
things
like
relationships
and
layouts,
but
the
one
on
our
list,
all
of
them
have
been
completed.
That
includes
them
redesigned
the
status
report
and
the
available
updates
page.
That
issue
has
been
merged
clean
up
CSS
for
the
views,
UI
issue
930
that
one
looks
really
pretty
amazing
two
views.
C
C
This
functionality
makes
it
so
that
we
can
move
around
the
messages,
tabs
page
title
and
action
links
within
layouts,
and
that
is
all
complete
and
very,
very
cool.
A
copy
paste
upload.
This
one
was
marked
our
CBC
last
week
and
has
now
been
merged
in
port
views.
Pane
displays
this
issue
24
33,
and
that
allows
us
to
base
blocks
from
views
and
then
override
the
settings
of
views
on
a
per
block
instance.
C
So
you
could
place
the
same
view
twice
for
example,
and
then
make
one
display
five
items
in
the
other
one
display,
10
or
overwrite
any
of
the
options
that
we
expose
to
you
on
a
per
block
basis
that
one's
really
cool
it
also
unblocks
Gregory,
pointed
out
also
unblocks
the
ability
for
us
to
convert.
The
recent
comment
blocks
I'm.
C
Sorry,
the
recent
comments
to
a
view,
because
that
what
previously
had
like
how
many
comments
do
you
want
to
display
and
now
that
we
can
expose
the
pager
count
via
views
to
block
that
makes
it
so
that
we
can
have
a
feature
equivalent
functionality
between
the
Drupal
7
approach
and
the
backdrop
approach.
I.
E
C
C
There
some
other
issues
that
are
slated
for
1.70
that
are
tagged
is
such
there's
only
about
a
I,
don't
know
eight
or
so
of
them,
and
you
can
find
them
in
a
github
issue
tracker
under
the
1.70
milestone
time
for
the
next
couple
of
weeks
before
1.7
comes
out
to
find
things
to
fix
or
actually
in
the
1.6
milestone.
The
164
milestone,
basically
the
bugs
that
we
think
are
fixable
in
the
very
near
term
and
by
fixing
them
in
164
they'll
also
be
fixed
in
the
1
dot,
X
version.
C
So
if
you're
looking
for
something
to
do
you
prior
to
our
release,
checking
out
the
bugs
and
specifically
the
bugs
that
are
tagged,
4,
1,
6,
4
or
1
7
out
those
are
the
the
best
bugs
take
a
look
at
and,
of
course,
there's
always
one
point,
eight,
which
will
come
out
four
months
from
now.
So,
if
you're
interested
in
looking
forward
to
the
future,
it's
never
too
early
to
start
thinking
about
the
next
minor
version
of
backdrop.
A
Sure
so
I
just
added
a
section
here,
because
last
week
was
DrupalCon
and
I
know
a
lot
of
us
were
there.
There
is
a
fantastic
blog
post
by
Tom
on
our
website
right
now,
if
you
want
to
give
that
a
read
about
a
Drupal
con
in
particular,
and
then
Jeff
also
is
recommending
this
post
on
open
source
and
human
time
management.
I.
Just
looked
over,
looks
kind
of
interesting,
so
I'll
give
that
a
read
later
today
too.
A
If
anyone
else
heard
of
anything
at
Drupal
con
or
wants
to
share
anything
or
post
blog
posts,
that
think
are
relevant.
Definitely
let
us
know
I
know
Wes
was
there
and
a
bunch
of
people
had
a
bunch
of
good
conversations
about
backdrop
on
Twitter,
which
is
pretty
exciting,
but
I
would
love
to
hear
more
about
the
event
to.
A
Next
week,
I
think
is
civic
on
I
know
Jax
going
to
be
there,
I
don't
know
if
anyone
else
is
planning
on
attending
and
it'll
be
great
to
get
a
recap
of
that
event
afterwards
too.
So,
if
you
are
planning
on
going
and
you
want
to,
let
us
know
how
it
is
people
to
get
updated
on
that
when
it's
over.
Does
anyone
have
anything
else,
they'd
like
to
add
to
this
week's
meeting
related
to
events
or
the
release
or
anything
else,
we
should
talk
about
one.
C
More
thing
related
to
civvy
CRM,
just
the
latest
version
of
savvy
CRM
finally
includes
out-of-the-box
backdrop
support.
How
awesome
is
that
yeah
yeah,
and
so
so
we
had
backed
up
support
in
civvy
for
a
while
now,
but
it
wasn't
actually
included
as
like
one
of
the
the
integration
to
now.
It's
it's
right
out
there
just
with
Drupal
and
WordPress.
So
it's
a
good
chance.
A
Would
be
I
would
love
to
see
a
blog
post
about
that
with
some
screenshots
I.
Don't
know
who
I
know
Jack's
not
gonna
have
time
to
write
one
good.
Maybe
if
anyone
else
is
using
it,
I
would
love
to
see
how
that's
going.
A
Okay,
well,
let's
get
back
to
the
issue
queue
and
get
some
of
those
bugs
fixed
for
one
seven:
oh,
hey.
D
C
A
An
issue
somewhere
that
aligned
all
this
stuff
that
we
want
to
add
and
I
think
it's
against
project
module,
but
yeah.
It
would
be
great
to
make
some
more
progress
on
that
and
try
and
figure
out
how
to
include
the
information
we
need
I.
Just.
D
A
D
E
E
D
We
need
to
be
done
on
a
more
informed
way,
so
it's
like
yeah,
we
can
just
spend
all
of
our
time,
like
you
know,
doing
feature,
requests
and
patching
bugs
and
things
like
that,
but
unless
we
actually
have
some
information
on
which
are
actually
important,
like
you
know
how
many
users
are
encountering
this,
because
how
many
people
have
this
module
turned
on.
It
seems
kind
of
vital
for
us
to
actually
do
like
to
actually
see
what
work
needs
to
be
done.
So
so
I
would
say.
I
would
say
this
is
sort
of
a
higher
priority.
A
Yeah
I
mean
I,
agree,
it's
important,
I,
don't
know
what
kind
of
changes
are
going
to
be
required
in
order
to
collect
the
information
we
need.
If
it's
additions,
is
there
a
chance?
We
could
get
any
of
that
into
one
708.
So
no
there's
a
code
freeze
code
right,
I
like
to
move
to
your
freeze,
its
feature:
freeze,
not
code,
freeze,
okay,.
A
D
A
D
So
I
mean
have
been
great.
If
I
can?
Okay,
that's
a
fairly
innocuous
setting
to
have
been
tracking
that
all
along,
but
don't
promise
is
like
I'm.
Not
trip
is
any
way
that
we
could
blanket
capture
a
bunch
of
config
well
and
make
sure
that
we,
we
should
probably
look
through
every
core
configuration
and
see
which
ones
have
sensitive
information
and
which
ones
don't
and
track
any
ones
that
don't
that's
what
I'm
thinking
my.
E
Thought
was
because
some
some
of
the
settings
might
have
sensitive
or
private
information
that
should
not
be
communicated
my
off
of
the
top
of
my
head.
What
I
could
think
was
that
the
things
that
we
require
are
all
the
things
that
have
a
checkbox
or
a
radio.
We
don't
necessarily
need
to
know
what
option
people
use
as
a,
for
example,
a
text
box
that
says,
what's
your
site,
many
more!
What's
your
email,
but
if
there
is
that,
if
there
are
things
that
I
have
options,
we
need
to
know
which
checkbox
is
checked.
E
So
we
need
to
go
through
every
complete
when
it
comes
to
poor.
But
then
there
was
also
an
issue.
It's
going
to
be,
if
we're
going
to
implement
that
before
will
be
very
useful,
to
also
do
it
for
the
trip.
So
we
should
go
through
every
complete
file
and
see
all
the
settings
that
have
values
like
true/false
or
0,
1
or
B
options,
I,
guess
and
then
report
that
I
feel
like
I
feel
like.
A
That's
a
good
like
I
think
we
should
try
and
roll
this
out
in
phases
and
saying
like
we
want
to
track
modules
versus
projects
as
good
for
phase
one,
but
trying
to
guess
like
what
from
kindred
we
need
is
gonna,
be
hard
I
like
your
idea.
Mica
flooding
projects
specify
but
I
also
think
that
that's
not
necessarily
crucial
for
the
problem.
We're
trying
to
solve,
which
is
helping
us
make
informed
decisions
about
core
I.
Think.
D
A
D
A
C
If
this
is
actually
got
a
oh
yeah,
I
mean
we
need
to
store
it
on
the
server
side.
You
need
to
define
on
the
client
side
information
across
the
wire,
because
I
mean
this
is
like
right
now
we're
only
conveying
their
minimal
amount
of
information.
It's
a
side
effect
of
update
modules.
So
like
it,
you
have
to
compile
it.
What
versions
you're
running?
C
Basically
in
order
for
it
to
say
like
these
are
the
things
that
you
care
about,
not
true,
but
it
is
more
just
like
a
side
effect,
rather
than
a
functionality
of
like
sites
reported
back
a
bunch
of
information,
because
we
start
sending
over
lots
of
information.
You
know
like
doing
it
could
be
like
a
megabyte
of
data
that
we're
sending
over
I
could
have
some
serious
impacts
as
well.