►
From YouTube: Backdrop Weekly 1/26 (Localization!)
Description
Today’s development agenda: http://bit.ly/2iYKbKT
A
A
Agenda
start
hey
next
week:
I'll
do
that
before
I
start
the
podcast
all
right,
so
we
don't
have
any
updates
for
the
PMC
this
week,
but
we
do
have
one
item
that
need
to
vote
or
we
should
have
an
update
next
week
and
also
not
an
email
to
everyone
on
the
pnc
after
this
meeting
to
remind
everyone,
but
it's
around
policies
for
pro
bono
work.
So
people
want
to
donate
work
to
backdrop.
If
we're
going
to
have
any
policies
about
that
backdrop,
outreach
meeting
we
just
had.
A
A
That's
not
super
exciting.
We
do
have.
Let's
see
if
I
am
a
link
to
that
I
can
just
throw
in
here
now
I,
don't
have
an
open
anymore.
If
you
have
opening,
you
can
add
to
the
agenda,
but
we
did
a
little
cleanup
and
I
think
it's
pretty
much
ready
to
go
so
that's
exciting.
As
soon
as
we
push
161
will
be
able
to
push
the
newsletter
to
backrub
CM,
esta
org.
We
have
a
new
homepage.
A
We
got
our
design
finally
finalized,
so
we've
got
stuck
because
the
version
that
West
had
been
working
on
had
a
couple
of
blockers
where
we
needed
a
home
page
hero,
and
we
finally
got
this
from
a
designer
and
so
I
think
we're
ready.
Now
we
just
need
to
have
implemented.
So
if
we
have
anyone
who
is
interested
in
updating
our
current
theme
or
working
on
wes's
new
branch,
we
would
love
volunteers
there,
a
forum,
module
I,
think
we
made
a
lot
of
progress
last
week,
which
is
great.
A
We
took
the
disc
an
offline
after
weekly
backdrop,
meeting
and
I
think
we
have
clearly
outlined
some
next
steps.
Since
that
meeting,
I
created
a
backdrop
forum
repository
under
the
backdrop,
ops
group
and
their
most
importantly,
there's
an
issue
queue
there.
So
we
can
continue
to
work
on
items
that
need
to
happen
for
the
forum
in
that
queue
and
take
them
out
of
the
factor
of
C,
Mista
or
q.
A
Next
steps,
we
have
to
decide
on
technical
implementation,
details
and
anyone
who
wants
to
help
weigh
in
on
comparisons
of
using
the
forum,
module
or
just
using
parts
of
backdrop
core.
We
could
use
helpfully
on
it:
translation
server.
This
is
new.
We
haven't
talked
about
it.
Yet
in
this
meeting,
my
dog
wants
to
talk
about
translation
server.
Apparently,
originally
we
decided
we
would
just
use
drupal.org
translation
sugar
because
are
stirring,
so
we
originally
respect
backdrop.
A
One
point:
oh
we're
very
similar
to
this-
that
ruined
Drupal
7,
we've
added
a
bunch
of
stuff,
in
particular
views
module
that
makes
that
not
really
viable
and
so
we're
now
at
the
point
where
we
need
our
own
translations
over.
We
can
include
backdrop
specific
translations
and
today,
after
this
meeting,
I
would
like
to
take
that
discussion
into
more
detail.
A
So
if
you
can
stick
around
at
the
conclusion
of
running
through
this
agenda,
will
stop
the
live
broadcast
in
kind
of
get
deeper
into
how
to
do
that,
where
to
do
that,
who's
going
to
do
that
kind
of
just
next
steps
on
on
getting
that
going,
Olaf
because
you're
here
today,
I
don't
know
if
you
want
to
weigh
in
on
that
at
all
now
or
if
you
just
want
to
wait
and
participate
in
the
discussion
leader.
But
you
were
the
one
that
brought
to
our
attention.
A
B
We
have
a
number
of
issues
that
have
been
discovered
that
we're
working
on
correcting
there's
two
issues
related
to
the
new
system.
Settings
form
function
that
we've
reinstated
and
started.
Abusing
those
two
issues
are
2473
and
2478.
I
can't
quite
recall
which
forms
are
which
let's
say
one
is
the
site.
Information
check
boxes
are
not
saved
after
hitting
the
update
block
button
that
doesn't
sound
like
thats
related
well
anyway,
that's
a
layout
sishu.
It
looks
like
not
a
system
settings
form
and.
B
B
So
2473
is
an
issue
with
saving
blocks
and
2478
is
an
issue
with
timezone
settings
not
getting
saved
correctly,
both
of
which
have
pull
requests,
which
is
great
but
both
are
in
a
needs,
work
state.
So
it's
great
that
we
have
some
initial
stabs
at
fixing
each
of
those
problem,
but
they
need
some
work
yet.
B
The
next
item
is
we
have
a
ten
dvo
mode
module
or
basically,
we
added
its
capabilities,
but
did
a
rewrite
of
that:
the
user,
interface,
VIN
and
EV
mode.
But
ultimately
the
concept
is
the
same,
and
so
is
the
configuration,
and
so
we
have
an
issue
at
2480
to
provide
an
upgrade
path
from
entity
view
modes.
The
contribute
I
think
that
we
missed
that,
because
many
of
us
didn't
even
realize
there
was
an
entity
view
mode
for
backdrop
as
of
yet
so.
B
Nice
thing
is
that
that
issue
not
only
solves
the
problem
for
the
contribute
of
entity,
view
mode
for
backdrop,
but
also
adds
the
upgrade
path
from
triple
sevens
and
Annie
View
mode,
so
people
taking
the
Drupal
7
site
and
running
it
through
update
on
PHP
to
get
to
a
backdrop
website.
It
now
also
includes
an
upgrade
path
for
an
interview
mode,
which
is
great
when
Jack
confirm
that
that
a
pull
request
to
fix
the
problem,
plus
my
own
manual
testing,
so
that
one
has
been
marked
our
TBC
and
we'll
get
that
end
shortly.
B
Let's
see
another
item,
apparently
not
a
1.6
issue,
just
a
coincidence,
basically,
that
newer
versions
of
Firefox
and
Chrome
have
this
problem
with
table,
drag
that
the
cursor
gets
kind
of
or
the
row
gets
stuck
to
the
cursor,
and
that
issue
is
2482
and
we
have
a
pull
request.
That
is
a
back
port
from
Drupal
7,
dot,
53
I
think
so
they
have.
The
same
problem
happened
in
the
Drupal
world,
because
this
wasn't
actually
a
problem
that
we
introduced,
but
rather
browsers
changed
and
then
introduced
this
problem.
B
So,
but
it
looks
very
likely
to
that
fix
which
is
currently
in
needs.
Review
stage
should
solve
the
problem,
as
it's
already
been
corrected:
r,
interpol
and
Islam,
and
then
finally
related
to
the
new
update
to
normalize
that
CSS
multi
select
items
currently
have
a
fixed
height.
Instead
of
being,
you
know
able
to
select
multiple
items.
There's
only
one
row
of
items
now
which
it
looks
like
jen
is
volunteered
to
take
on,
but
it
doesn't
look
like
there's
an
issue
tracked
for
it.
Yet
that's
it.
Those
are
the
items
that
are
slated
for
1.61.
B
That's
it
for
the
1.6
release
and
the
current
things
that
I
have
out
there.
Of
course,
as
always,
there
are
many
many
issues
that
could
be
fixed
at
any
time:
posted
user
experience
land
as
well
as
bugs
and
as
soon
as
those
items
are
already,
we
can
merge
them
at
any
time
and
it'll
be
in
the
next
bug-fix
release.
B
B
But
we
have
some
serious
challenges
around
moving
into
core,
one
of
which
is
that
we
have
an
upgrade
path
to
deal
with
from
the
term
reference.
That's
built
into
taxonomy
module
not
to
mention
upgrade
ads
from
contribs
of
other
reference
modules.
So
that
could
be
quite
a
challenge
and
we
still
have
yet
to
actually
make
any
headway
in
the
upgrade
path
process.
B
B
Let's
see
what
else
title
tabs
oh
and
messages
things
like
that
things
that
currently
are
hard-coded
in
the
layout
templates
it.
This
issue
makes
us
that
you
can
place
all
those
elements
as
blocks
instead
kind
of
allowing
for
a
full
page
flexibility.
That
issue
is
1704
and
right
now
is
in
a
needs
review
states.
B
2134
I
personally
haven't
had
a
lot
of
time
to
look
into
this,
but
it's
also
in
a
state
that
needs
review
and
let
relationships
would
allow
us
to
do
incredibly
powerful
things
like
starting
with
a
node
page
joint
over
to
the
author
entity
and
pull
out
fields
from
the
author,
and
then
you
could
go
from
the
author
on
to
other
things
and
so
forth.
That
would
be
really
cool
in
combination
with
reference
module
again,
like
these
things
kind
of
become
exponentially
more
powerful
as
you
combine
them
together.