►
From YouTube: Backdrop Weekly Aug 31st
Description
Today’s development agenda: http://bit.ly/2iwk2oz
A
Hey
there
we
go,
it
is
Thursday
August
31st.
Thank
you
guys
for
joining
in
on
our
last
backup
developer
meeting
before
code
freeze.
So
that's
exciting.
We
have
a
a
agreement
that
we're
working
out
with
a
lawyer
from
the
software
freedom
Conservancy
with
that
a
question
for
him
and
he
hasn't
followed
up
yet
so
I've
been
like
sending
annoying
emails.
Hopefully
look
at
the
response
soon
and
they'll
be
able
to
move
forward
on
that
this
week.
A
There
are
a
ton
of
new,
contributed
projects
for
backdrop,
including
a
port
of
uber,
carte
blanche
which
is
pretty
exciting,
so
anyone
who
needs
it
were
cut
on
their
Drupal
7
site
now
can
update
that
site
to
backdrop
and
I
think
we
should
move
directly
into
talking
about
a
backdrop.
Progress
since
we're
coming
up
on
the
1.8
release
and
people
are
probably
curious
to
know
about
what
they
should
help
with
between
now
and
then
so
neat.
Why
don't
you
take
it
over
and
talk
about
some
of
these
issues.
B
All
righty,
okay,
let's
start
with
1.73,
which
will
be
the
last
bug,
fix
release
on
the
1.7
minor
version.
We
have
a
regression
that
we
discovered
in
1/72
that
affects
drop
buttons.
The
drop
buttons
are
positioned
strangely,
in
some
cases,
especially
in
the
future.
Lies
is
especially
noticeable
right
now
and
that
issue
is
2806.
B
That's
a
pull
request
that
fixes
the
views
you
live,
but
there's
still
some
minor
overflow
issues
and
other
places
where
drop
buttons
are
used,
and
so
that
issue
right
now
we're
pondering
if
we
should
just
revert
what
was
in
1/72
entirely
or
stay
the
course
and
try
to
finish
fixing
the
issues
that
have
been
discovered
figure.
Your
feedback
on
that
might
actually
be
kind
of
useful
I.
Think
here
so
state
that
suggested
that
we
flip
it
in
the
first
place
which
yeah
it's
mixed
bag.
B
A
So
it's
specifically
on
the
layout
you
I
drop
buttons,
don't
work
very
well
on
mobile
I.
Think
it's
been
like
a
long-standing
bug
that
just
never
had
an
issue.
We've
all
been
reporting.
It's
been
an
issue
for
a
while,
so
it's
not
related
to
the
fix
that
we
just
put
in,
but
since
now
people
are
noticing
try
out
buttons,
that's
how
it
came
up
recently.
So
if
we
I
don't
know
what
we're
gonna
do
for
a
fix
for
our
drop
buttons
globally,
but
if
we
find
something
that
also
fixes
this,
that
would
be
awesome.
Okay,.
B
Okay,
other
thanks,
173
included
a
bucket
of
cross
ports.
We've
got
four
issues
regarding
cross
ports,
2013,
which
is
a
bunch
of
old
cross
ports
from
triple
7.50
and
previous
versions,
and
then
it's
27,
74,
75
and
76,
which
are
three
other
issues
for
doing
cross
ports
I.
Think
right
now.
Our
intention
is
that
we're
putting
most
of
our
focus
into
one
point,
eight
related
issues
and
then
we'll
continue
doing
the
cross
ports
after
code
freeze,
which
is
coming
up
here
on
Monday.
B
So
let's
get
to
one
point:
eight,
which
is
the
next
minor
release
that
is
coming
out:
September
15th,
so
just
a
little
bit
over
two
weeks
from
today,
which
is
kind
of
exciting,
and
we've
got
a
lot
of
items
that
are
outstanding.
That
we'd
still
like
to
get
wrapped
up
and
to
be
clear.
Our
way
to
paying
these
things
is
going
to
be
August
4th
Monday,
which
is
Labor
Day
in
the
United
States.
B
German
ality
that
will
go
into
1.8
and
then
we'll
spend
the
remaining
the
remainder
of
the
two
weeks
to
fix
up
any
bugs
that
we
may
have
introduced
during
that
time.
So
the
first
time
we've
gone
on
the
hit
list
here
is
improving
media
supports,
which
is
a
meta
issue
at
14
48,
oh
sorry,
did
I,
say
August
4th
I
meant
September
4th.
Yes,
thank
you.
All
September
4th
is
good
freeze,
so
the
meta
issue
is
1448
for
improving
media
support,
and
primarily
it
looks
like
for
1.8.
B
What
that
really
means
is
adding
and
editing
files
independently
of
any
kind
of
content,
and
so
first
one
that
looks
like
it'll
probably
be
complete
is
the
ability
to
edit
an
existing
file
which
is
27,
ninety
six,
which
is
functionally
complete,
but
need
some
more
tests
to
ensure
that
it
behaves
the
way
that
we
expect
it
to
do.
We
have
some
questions
around
what's
been
implemented
there
like
we
might
need
to
make
some
changes
in
the
in
the
way
that
it
functions.
B
B
B
That
issue
needs
a
little
bit
of
work.
It
starts
in
PHP
notices,
tasks,
there's
a
couple
of
items
relating
to
CSS,
styling,
2804
and
2803.
Both
affect
the
way
that
the
installer
looks
when
you're
running
through
installing
backdrop
for
the
first
time
28
go.
3
is
a
revamp
of
the
progress
bar
styling
and
that
one
has
been
merged
since
last
week.
So
that's
great,
we'll
probably
pop
our
bucket
list,
but
if,
for
those
that
haven't
had
a
chance
to
take
a
look
at
it,
2803
introduces
a
new
styling
for
the
progress
bar
which
affects
everywhere.
B
The
progress
bars
are
shown,
including
the
Installer
before
Reis
tiles
task
lists
tasks,
lists
are
kind
of
uncommon,
but
you
see
them
in
two
particular
places
during
the
installer
and
when
using
the
project,
installer
module
to
install
new
modules,
and
so
that
has
a
pull
request
that
introduces
some
new
styling
to
make
it
look
more
like
the
rest
of
the
7
theme,
but
there's
some
suggestions
on
their
own
implementation.
That
will
probably
end
up
kind
of
taking
a
different
approach
on
that
one:
to
implement
some
design
recommendations.
B
Let's
see
other
items
41.8
a
minor
feature
is
fixing
the
way
to
pack
Auto
handles
curly
quotes
and
hyphens,
which
is
2765
a
little
bit
on
the
fence
about
whether
or
not
that's
a
new
feature
or
or
a
bug
fix,
but
it
makes
it
so
that
path
auto
can
handle
more
types
of
quotes
and
more
types
of
hyphens.
That
issue
needs
review,
probably
our
TBC,
but
we
can
do
some
sign-off
from
someone
else
on
that
issue
to
make
sure
that
it's
all
ready
to
go.
B
Lastly,
jQuery
UI
I
should
say
all
like
a
birthday,
so
would
like
to
make
sure
that
all
libraries
are
updated
when
we
release
a
new.
My
hair
release
of
backdrop
and
I
know
that
we've
already
updated
ckeditor
I
think
that
there
was
an
issue
for
updating
jQuery
once
but
I
can't
remember
if
that's
been,
if
that's
been
merged
yet
or
not,
I,
don't
I.
Think
I.
Don't
think
so.
B
I
think
that
it's
it
needs
work
actually,
but
it's
not
in
the
agenda
here,
but
that's
another
item
that
we'll
probably
need
to
take
a
look
at
jQuery
itself
has
already
updated
to
the
latest
version.
But
there's
a
minor
version
of
jQuery
UI
that
would
get
updates
and
so
I'll
keep
track
of
that
in
24,
93,
updating,
jQuery,
UI
whoo
all
right.
Well,
that's
the
hit
list
of
things
that
were
likely
to
knock
off
41.8,
there's
actually
some
other
items
yet
that
are
slated
for
1.8
that
are
perhaps
less
notice
notable.
B
A
Added
a
couple
things
that
aren't
related
to
1.8
to
the
agenda.
One
of
them
is
one
of
our
new
kinship
maintainer
she's,
having
a
problem,
giving
the
module
to
package
properly
and
I.
Remember
we
had
this
issue
recently,
mm-hmm
and
I.
Couldn't
member
what
the
fix
was
for
it.
I
checked
the
tag
and
it
does
have
release
notes.
There's
no
packaging
error,
it's
just
not
going
to
catch
at
all.
Does
the
tied
name
need
to
be
in
a
specific
format?
I,
don't
know
anyway,
I
put
an
issue
in
the
agenda.
A
A
And
then
the
next
item
is
a
conversation
that
we
had
in
Kidder
yesterday
or
the
day
before
about
plan
for
better
internationalization
for
backdrop
and
whether
that
was
going
to
be
something
that
we
could
do
in
the
1x
cycle
or
something
that
might
be
a
good
selling
feature
for
getting
people
to
upgrade.
To
backdrop
too,
and
so
I
thought
we
should
talk
about
that
today
as
well.
A
Okay,
so
what
do
you
guys
think?
Do
you
want
to
talk
about
translation,
stuff
kind
of
quiet,
I,
don't
know
if
that
means.
Yes,
no.
A
I
think
the
reason
this
came
up
is
because
Olaf
was
it
you
that
have
a
project
that
you
have
like
a
one-year
timeline
on
yeah,
that's
gonna
need
some
translation,
stuff
and
so
trying
to
figure
out
like
now
whether
one
year
from
now
is
like
a
realistic
timeline
to
get
like
everything
we
need
translated
done
was
the
original
question
and
my
answer
was
yes,
because
we
can
already
do
all
of
that
stuff
in
Drupal,
7
and
so
just
trying
to
figure
out
what,
if
that
needs
to
get
moved
over
to
backdrop
seem
like
a
year.
A
We
want
to
improve
on
that
and
trying
to
figure
out
what
our
path
forward
should
be
would
be
good.
So
right
now
it's
kind
of
indeterminate
like
which
way
we're
going
to
go.
There's
been
a
lot
of
improvements
to
the
translation
system
and
Drupal
8,
and
then
a
lot
of
increased
complexity
as
well
and
so
I
think
we'll
need
to
kind
of
look
at
what
we
really
like
about
translation
intercalate.
What
we
really
like
about
translation
in
Drupal
7
I
have
a
lot
of
experience
with
translation
going
back
as
far
as
Drupal
5.
A
There
are
some
parts
of
that
it
really
likes
to,
but
just
kind
of
pick
the
best
of
all
worlds
and
see
what
we
think
might
be
the
best
fit
for
backdrop.
C
C
But
maybe
let
me
mention
shortly
what's
also
interesting
for
me,
it's
not
only
this
particular
point
internationalization,
but
also
how
we
manage
the
development
process,
because
at
this
point,
I
actually
really
need
yes
to
evaluate
if
I
can
use
it
in
one
year.
And
that
brings
me
to
the
point
that,
because
we
all
do
it
not
paid
so
voluntary,
we
can
so
we
can't
say
so
to
some
people.
C
C
C
A
This
1.8
release
is
kind
of
leading
towards,
like
continued
file,
hand
stuff,
but
would
have
been
better
had
we
had
a
lot
of
fun
handling
stuff.
Now
it's
gonna,
be
you
know
a
couple
file
handling
things
a
couple.
Other
things,
but
it
is
very
dependent
on
what
people
have
time
to
handle
I
think
like
for
me
personally.
If
I
have
a
project
has
specific
requirement.
A
That
project
helps
drive
the
development
in
a
particular
angle,
I'm,
not
sure
if
this
will
be
for
you
too,
or
if
you're
gonna
have
a
project,
that's
kinda
require
translation
and
that
project
has
funding.
Now
you
can
hire
developers
to
work
on
it
and
that'll
help
move
that
forward
too.
So
it
just
depends
on.
You
know
like
you
have
to
make
it
happen,
but
you
also
have
to
like
get
other
people
to
make
it
happen
to
like.
A
You
can't
do
everything
by
yourself,
obviously,
and
I
think
that
this
is
something
that
we've
identified
as
an
area
that
needs
focus
like
we
need
to
work
on
translation,
internationalization,
I,
don't
have
a
project
right
now,
I'm
working
on
that
has
it
I
know.
Larrin
said
he
had
projects
that
was
gonna
need
it
in
the
future.
You
have
problems
our
community.
We
could
find
you
know
a
handful
of
people
that
have
the
skills
to
work
on
these
issues
and
get
them
done.
I
think
scheduling.
A
A
Together,
it
definitely
goes
faster
when
there's
more
than
one
person
working
on
it,
but
yeah
I.
Think
that
is
a
great
topic.
We
should
talk
about
it,
maybe
I'll
add
it
into
the
weekly
agenda.
It'll
show
up
every
week,
so
we
can
think
about
it.
Obviously,
we're
gonna
be
busy
for
the
next
two
weeks.
Working
on
the
one
point
really
said:
I
want
us
to
forget
about
it.
A
B
Yeah,
it
is
awesome
right,
noting
the
tongue
we've
been
a
lot
more
fragmented
as
of
late,
because
we
haven't
put
any
well.
We
haven't
had
any
real
consensus
actually
on
things
that
we
should
focus
on
in
the
recent
point
releases
like
even
on
the
roadmap
hunts,
the
reason
I
haven't
mentioned
roadmap
and
any
recent
meanings.
B
We
don't
even
have
item
slated
out
for
1.8
in
the
roadmap,
despite
the
fact
that
it's
coming
up
two
weeks
and
1.9
is
the
same
thing
where
it's
like.
It's
all
unfocused
right
now
and
I
think
that
you
know
stating
those
things
officially
in
a
place
like
the
road
map
and
mentioning
it
kind
of
creates
a
focus
just
by
stating
it
being
the
goal
and
we
haven't
in
the
night
thing.
B
The
reason
why
we've
slipped
on
this
in
1.8
and
probably
1.9,
is
because
we
had
a
number
of
items
that
we
were
repeatedly
trying
to
get
done.
Reference
module
is
a
really
great
example
of
it,
trying
to
be
in
like
three
subsequent
releases
that
never
happens
and
I
think
that
was
a
little
bit
discouraging
for
us
to
keep
putting
the
same
item
in
every
next
point.
Really
it's.
B
C
Yeah
I
think
sort
of
not
officially
focus
of
the
list
of
the
current
upcoming
release
was
media
and
files,
but
yeah,
maybe
bit
because
it
was
never
stated
officially.
It
was
not
so
clear.
For
example,
also
you
gen
very
interested
to
get
a
lot
of
things
in
oh
I.
Wasn't
holiday
ii
couldn't
hope
for
a
long
time,
but
yeah
I
think
May.
That
could
be
the
next
focus
or
the
1.9
release
or
one
of
the
focuses
and
then
internationalization,
maybe
for
the
1.10
I
suppose.
B
C
B
As
a
great
proposal
actually
because
we
didn't
have
a
focus
on
me
and
1.8
until
people
started
doing
it
and
basically
finishing
that
work
in
1.9
would
be
a
great
vector
for
us
to
continue
on
and
then
plan
out.
Internationalization
is
a
1.10
item,
but
that
doesn't
mean
that
we
can't
start
working
on
it
right
away.
It
just
means
that
we
won't
actually
put
a
focus
on
it
until
1.10
or
see.
Now,
where
I've
already
saying
one
point
tendon.
So
it's
going
to
exist,
but.
B
A
Just
say
the
next
one
I
also
think
like
scheduling
it
too
releases
out
could
be
really
good,
because
that
would
give
us
a
whole
release
ahead
of
him
to
kind
of
put
our
ducks
in
a
row
in
terms
of
like
what
are
the
actual
issues.
We're
gonna
work
on
like
trying
to
figure
out
some
kind
of
plan,
give
us
a
whole
release
to
be
like.
Oh,
this
is
related
to
that.
A
C
C
What
we
give
a
statement
about,
there
may
be
upcoming
commitment,
so,
but
one
question
I
can
evaluate
very
good
because
internationalization
with
all
the
sub
modules,
it
looks
like
a
monster
in
Drupal,
7
and-
and
there
are
also
some
other
modules
which
is
not
part
of
internationalization
and
which,
but
which
you
need,
because
and
yeah
omit
source,
so
I'm
also
asking
how
we
are
listed.
Is
it.
C
A
In
general,
I
like
to
say
better
than
we've
done,
and
first
we
can
get
done.
You
can
make
it
better
later,
but
I
think
like
in
the
process
of
your
particular
project.
You'll
come
up
with
some
priorities
or
it'll
be
like
okay.
I
definitely
need
to
translate
menus
and
taxonomy
and
layouts
or
something,
and
then
those
will
be
the
things
that
we
drive
forward,
because
those
ones
that
we've
got
feedback
on
right
away
and
then,
as
we
go
forward,
it's
like
oh
well,
you
know.
A
Maybe
now
we
also
need
translate
books
or
some
other
things
that
are
supported
in
core,
that
weren't
necessary
for
your
project.
This
will
come
along
later
and
the
sub
modules
will
be
reported
as
needed
and
as
we're
going
to
keep
that
process.
You'll
identify
like
oh,
really
quickly.
There's
this
problem
with
translating
menus,
I
also
need
to
have
whatever
and
then
we'll
figure
out,
whether
that's
something
that
can
be
fixed
in
and
can
trim
panel
solution
or
something
that
needs
to
have
something
changed
in
core
and
I.
A
Think
that
longer-term,
having
like
it's
hard
for
us
to
make
these
decisions
about
what
to
work
on
without
an
actual
use
case
without
a
project,
that's
using
it
and
running
into
it
issues,
and
then,
when
we
have
a
use
case,
we
can
also
recommend
fixes
that
you
can
try
and
be
like.
Yes,
it
solve
the
problem,
we're
just
kind
of
doing
that
in
a
vacuum
or
it's
like
I
think
this
will
help,
but
no
one's
actually
using
it.
A
D
Just
yeah
just
wanted
to
say
real
quick
that
I
was
looking
at
the
well
I
kind
of
remember
the
gadigal
now
about
the
v8,
and
one
of
the
selling
points
was
what
used
to
be
like
used
to
required.
12
latest
modules
in
d7
is
now
hothead
out
of
the
box,
and
they
were
preparing
to
being
able.
You
know,
having
poor
the
core
of
CMS
being
multilingual
on
like
a
blue
box.
A
That
could
be
something
we
could
work
on
so
I,
don't
know
what
changes
were
necessary
in
Tripoli
to
make
all
of
the
chance
ation
happen
internally,
but
we
should
review
that
as
well
and
see
if
there
I'm
sure
there
are
things
that
should
be
changed
in
core.
But
if
we
could
get
like
a
list
of
what
those
are
that
make
it
not
necessary
to
need
those
controls,
then
we
can
have
that
same
feature.
A
We
just
need
to
figure
out
what
what
the
end
goal
is.
So
I
think
the
end
goal
is
gonna
be
different,
but
that
doesn't
mean
the
ball
list.
Item
for
a
sales
point
has
to
be
different.
We
just
need
to
get
a
comparable
solution
that
meets
the
needs
for
our
audience
in
the
same
way
that
triple-eight
solution
met
the
needs
for
their
audience.
D
D
I
can
do
it
off
of
that
branch
instead
of
the
the
actual
developed
friends
and
I
have
found
that
this
is
a
good
way
of
you
know
catching
errors
or-
or
you
know,
problems
really
early
on,
and
we
can
start
very
simple
like
having
us
small
goal
to
get
content
translation
working
to
first
and
then
we
can
move
to,
because
this
is
the
basic
thing
and
then
moving
onto
menus
and
then
fix
something.
The
basic
would
be
getting
a
condom.
D
A
D
What
was
stopping
him
from
trying
it
more
now
was
the
fact
that
it?
What
if
it
wasn't
multilingual
so
my
point
is
how
would
we
get
more
people
that
are
actually
interested
in
multilingual
to
be
involved?
That's
that's!
Where
is
getting
it,
because
if
we
get
more
people
involved
things
we
get
done
even
if
it's
just
testing
more
bug,
reporting
or
more
suggestions
not
be
healthy.
So.
D
A
A
Okay,
will
you
let
me
just
actually
write
that
down
to
do
that
today,
I'll,
look
into
that
and
see
I
know,
I.
Think
I've
mentioned
that
there's
like
on
backup
semester
or
we
can
add
a
check
for
actually
easily,
but
we
need
to
figure
out
how
that
affects
the
sort
order
for
project
browser
results
and
for
module
like
on
the
modules
page
and
stuff.
It
could
just
be
that
those
are
all
views
and
then
we
would
just
need
add
some
styling,
but
yeah
that
should
be
pretty
straightforward.
I.
C
C
And
then
the
idea
came
up
to
translate
back
drops
in
as
walk
directly
I
know
that
WordPress
has
also
its
website
and
different
versions
or
different
languages,
and
that
would
also
help
to
spread
backdrop
in
other
countries.
Then
only
english-speaking
but
I
think
it's
yeah.
That's
that
could
also
lead
to
that.
More
people
are
interested
to
contribute
because
then
yeah,
maybe
Robert
Quarles
makes
it
for
Catalano
even
Spanish,
and
then
he
sees
the
problems
and
what
needs
to
be
done,
and
it's
also
guaranteed
that
all
people
who
work
for
backdrop.
C
A
A
Is
a
good
news
case,
I'm
concerned
about
like
the
amount
of
resources
we
hope
to
work
on
dr.
Epstein
mr.
Orrick
are
already
quite
limited
and
I
would
rather
have
people
working
on
like
the
localization,
so
I,
then
try
and
figure
out
how
to
make
backdrops,
CMS,
org,
visible
and
other
languages.
I
agree.
I
really
want
other
people
speaking
other
languages
to
get
all
the
content.
A
So
we
can't
provide
that
service
is
kind
of
a
weird
decision-making
factor.
I
mean
that's
a
reality,
but
it's
tough
I,
wonder
if
there's
something
we
could
do
as
like
a
halfway
like
until
we
do
get
to
the
point
where
we
have
enough
people
to
maintain
all
different
versions
of
backdrop
and
translation,
whether
it's
developers
or
people
are
just
maintaining
the
translations.
A
We
can
find
another
way
to
make
our
content
available
to
people
who
speak
other
languages
already
like
using
some
kind
of
translate
plug-in
that
might
like,
like
a
Google,
Translate
language
selection
list
or
something
that
might
be
like.
We
know
that
crop
can
do
translation,
but
we
don't
have
the
resources
to
maintain
that,
but
we
could
put
a
widget
on
the
site
and
that
might
at
least
be
something
that
will
let
people
read
our
news
pages
in
the
short
term.
A
A
Think
if
we
could
get
a
non-profit
that
we're
working
on
anyway
to
be
one
that,
is
it
a
solid
use
case
for
a
translation
that
would,
you
know,
take
those
ten
hours
a
month
that
were
devoting
to
that
project,
and
it
would
also
find
a
fit
backdrop.
So
it
benefit
the
organization
that
needs
it,
as
well
as
the
software
itself,
which
is
great
and
that
might
be
like
Jeff
once
we
start
getting
a
lot
of
people
applying
for
help.
A
A
Gonna
have
to
jump
off
doorbell
it's
about
to
rain
here
any
minute,
but
I'm
gonna
copy
some
of
the
ideas
into
our
weekly
agenda
so
that
we
can
keep
remembering
to
talk
about
them
after
1.88,
because
I
think
these
are
great
points,
then
we
should
keep
moving
forward.