►
From YouTube: Backdrop Weekly 2/9/2017 (localize checkin!)
Description
Today’s development agenda: http://bit.ly/2k1nzqS
A
Alright,
we're
on
air
happy,
Thursday,
februari.
Ninth,
everybody
we're
going
to
do
a
quick
run-through
of
our
vector
of
CMS
development
task
list
here.
Just
so,
you
guys
know.
We
have
a
pending
issue
for
the
PMC
it's
requesting
vote,
but
we
haven't
gotten
a
quorum
yet
just
around
how
we
want
to
handle
vendors
that
might
want
to
have
contracts
with
us
in
exchange
for
things
and
in
turn,
in
terms
of
what
what
kinds
of
things
we
might
want
to
be,
giving
them
or
not,
giving
them
and.
A
Like
we're
kind
of
coming
down
on
policy
for
those
of
you
who
are
watching
this
or
here
who
are
on
the
PMC
I,
have
posted
a
revision
since
last
week.
It
will
be
great
to
get
your
feedback
as
to
which
of
the
two
policies
you'd
be
interested
in
most
so
still,
not
quite
lingered.
On
that
for
community
outreach,
we
have
a
newsletter,
that's
ready
to
go
as
soon
as
our
next
release
of
backdrop,
which
is
great.
We
ordered
new
hoodies
they're,
currently
on
a
truck
on
the
way
to
my
house.
A
A
Alright
backdrop
CM
esta
org.
We
have
a
lot
of
work
to
do.
We
have
a
new
homepage,
design.
I
think
that's
finally
been
close
enough
to
finalize
that
we
can
build
it
and
iterate
once
it's
built,
but
we've
got
some
a
lot
of
work
to
do
in
terms
of
actually
getting
from
the
website
we
have
now
to
the
website.
We
want
to
have
with
that
new
design,
and
so
what's
that
started
on
it
back
when
he
had
time
to
work
on
this
for
us
and
he's
running
out
of
time.
A
So
if
anyone
else
wants
to
try
and
get
us
over
the
finish
line,
that
would
great
we've
got
to
current
approaches
where
les
hits
head
started
by
creating
a
sub-theme
of
basis
to
implement
all
of
the
new
fancy
new
stuff
in
new
design.
But
a
lot
of
the
branding
from
the
base
same
ended
up
on
backdrops
Sam,
esto
org,
and
we
need
to
figure
out
how
to
copy
all
of
the
burning
that
we
currently
have
on
the
website
into
that
need
theme.
A
Just
so
that
backdrop
CMS
or
doesn't
look
like
basis
because
that'll
be
really
confusing
people.
So
there's
a
lot
of
work,
they're
involved
in
all
of
the
stuff.
That's
in
the
current
theme,
hoping
it
into
the
new
theme
and
I,
don't
know
exactly
how
West
fun
and
have
it
all
organized.
So
maybe
somebody
that's
a
little
more
familiar
with
front
end
stuff
can
help
figure
out
where
to
put
the
code
in
a
way,
that's
gonna
make
sense.
Oh
I'll.
A
Great
so
so
we
have
on
the
backdrop
seamless
toric
repository.
There
is
a
new
branch
that
Wes
has
been
working
on,
so
just
go
to
the
public
retail
and
give
it
a
pull.
I'm
also,
I
have
a
branch
I've
I'm
working
on.
That
is
a
different
approach.
That
I
think
is
going
to
be
a
lot
less
work,
but
I
don't
have
time
to
do
it
that
at
all.
A
So
the
big
problem
is
that
we're
replacing
all
of
the
layouts
on
backdrop
CMS
to
work
with
all
of
the
crazy
custom
ones
that
are
there
now
with
one
store
in
cork,
which
should
make
it
much
easier
to
maintain.
But
there
is
some
CSS
mixed
in
with
our
current
CSS
that
handles
that
layout
business.
So
we
just
have
to
figure
out
like
if
we
have
random
blocks
that
are
floated
or
something
to
unload
them
where
necessary.
Okay,
that's
fantastic!
Thank
you
look
for
volunteering!
For
that
definitely
ping
me
on
git
er.
C
A
Alright,
we
also
have
a
new
forum
which
we're
working
on
at
forum
that
backdrop
CMS
to
org,
and
we
have
I
think
there
are
two
blockers
there
right
now.
One
of
them
is
deciding
on
a
cot
which
content
type
to
use,
so
we
have
three
examples
up
there.
One
of
them
is
just
a
custom
content
I've
created
through
the
UI
by
clicking
it
together,
one
of
them
is
provided
by
the
forum
module
and
one
of
them
is
the
QA
forum
modules
content
types.
A
It
is
a
little
different
from
the
other
two,
and
so
what
we
need
to
do
is
figure
out.
Does
the
forum
module
provide
anything
that
we
want?
So
look
at
the
one
that's
provided
by
the
foreign
module
and
see
if
there's
anything
there,
that's
not
included
in
our
custom
one.
If
there
is,
we
need
to
figure
out
if
we
can
only
get
that
from
the
forearm
module,
in
which
case
we
need
to
keep
the
forum
module.
A
We
need
to
document
that
too,
because
we're
probably
not
going
to
use
that
module,
but
we
do
want
to
look
at
that
experience
and
see
if
there's
anything
that
experience,
we
want
to
add
to
the
experience
of
using
our
forum.
So
that
would
be
the
steps
that
are
making
that
decision
and
I
would
just
love
to
have
more
feedback
from
people
in
that
issue.
To
help
make
that
decision.
So
then,
the
next
blocker
is
getting
bakery
module.
Working
and
I
know.
A
A
A
Translation
server-
I,
must
admit,
I
have
not
looked
at
this
since
Nate
updated
the
DNS,
but
we
should
have
a
localized
backdrop.
Semester
org
set
up.
It
might
not
be
connected
to
its
database
yet,
but
that
should
be
ready
to
go
today.
Maybe
we
can
do
that
through
the
you.
Are
I
don't
know,
maybe
someone
else
already
set
it
up
since
I
looked
at
it
no
idea.
Well,.
B
B
A
Just
needs
to
be
restarted
is
that
how
you
yeah?
Well
interesting?
Okay,
you
work
okay,
so
where
we
are
on
that
it's
a
repository
of
Drupal
eights
localized,
which
sorry
drupal
7
localize,
which
we're
going
to
try
and
get
to
work
with
factor
up.
So
what
I
was
going
to
do
is
hook
it
up
to
the
database
and
turn
on
the
necessary
modules
and
kick
it
over
to
whoever
else
wants
to
play
with
it.
A
B
Okay,
so
let's
talk
about
the
backdrop,
so
the
thing
that's
foremost
on
our
agenda
here
is
really
soon
1.61.
It's
been
almost
a
month
since
we
released
1.6
and
we
haven't
yet
released
a
bugfix
follow-up
release
to
address
items
that
have
cropped
up
in
1.6.
So
that's
our
objective,
as
noted
in
the
agenda
here,
were
attempting
to
release
this
tomorrow,
which
will
also
unblock
the
sending
of
the
newsletter
announcing
the
1.6
release.
B
So
the
issues
that
we've
got
here
to
deal
with
these
are
all
the
ones
from
last
week
and
we're
making
some
pretty
good
progress
here,
issue
2
480.
That
is
an
upgrade
path
for
nad
view
mode.
That
poll
request
has
not
emerged.
A
header
block
is
not
saving
which
components
should
be
shown,
including
the
logo
and
the
slogan
and
the
site
title,
which
is
the
two
2473.
B
B
B
2478
there's
an
issue:
its
system
settings
form
we
reintroduced
that
function,
in
fact,
rope
1.6,
but
there's
a
couple
of
forms
that
are
saving
data
incorrectly
because
of
Miss
matching
between
the
foreign
keys
and
the
values
very
sort
of
config
files.
John
Franklin
has
got
a
poor
requests
there.
That
does
work
and
I've.
B
Given
a
review,
and
it
looks
pretty
good
I
think
that
we
might
need
an
upgrade
path
to
clean
up
some
data
there,
because
in
his
fixing
of
the
problem,
which
is
actually
really
pretty
straightforward,
he
also
discovered
that
we
have
some
inconsistencies,
like
basically
discovered
other
bugs
that
were
on
its
name
on
those
same
forms
and
so
solving
the
regression
is
already
done.
But
we
can
take
that
a
little
bit
further
and
clean
up
the
kind
of
collateral
bugs
that
we
also
encountered
while
fixing
that
problem
and,
lastly,
the
table
drag.
B
We
have
an
issue
where,
when
dragging
table
rows,
sometimes
the
row
gets
stuck
to
the
cursor.
That's
2482
and
we've
had
a
lot
of
different
attempts
at
fixing
this
particular
problem.
Jen
apparently
tried
three
or
four
different
patches
from
the
drupal
queue,
but
none
of
them
either
independently
or
when
combined
all
together
actually
seemed
to
solve
the
problem.
B
But
it's
very
inconsistent
between
different
users.
I
can't
produce
the
issue
at
all.
Several
other
people
only
on
certain
browsers
and
other
people
in
the
same
browsers
in
the
same
operating
system
seems
to
work
fine.
So
we're
going
to
work
together,
jenna
night
to
kind
of
use
her
computer
to
see
if
we
can
figure
out
what's
happening
there
and
get
that
problem
fixed
up,
but
I
think
with
all
these
other
ones,
and
especially
things
like
the
system
settings
form.
That's
not
saving,
for
example,
that
we'll
do
our
best
to
resolve
all
of
these.
B
Sorry
there's
a
number
of
things
that
are
hard-coded
in
the
template.
But
this
makes
it
so
that
you
can
move
them
around
as
though
they
were
blocks
and
if
you've
placed
the
block
than
the
original
location
of
the
menu
tabs
or
whatever
it
is
that
they
are.
It
doesn't
show
up
anymore
doc.
Lamont's,
who
has
been
working
on
that
just
filed
an
updated
pull
request
a
couple
days
ago
that
include
some
new
usability
improvements
on
top
of
the
existing
functionality.
B
That
makes
it
so
that
when
you
place
the
page
title
block,
it
appears
as
though
the
pseudo
region
will
disappear
or
reappear,
which
is
kind
of
cool.
So
it's
great
to
see:
that's
not
just
functioning
because
it
was
already
working
but
now
being
improved
upon
further.
Anybody
wants
to
give
that
a
spin.
You
can
use
the
the
poll
requests
and
boxes
to
give
that
a
review,
because
from
a
code
perspective
it
looks
really
good
but
I'd
love
to
get
some
feedback
on
how
well
it
works
from
the
users
perspective.
B
B
This
ability
of
lat
relationships
would
allow
you
to
take
a
starting
context,
such
as
a
node,
if
you're
on
node,
/,
10
or
whatever,
no
10,
is
your
existing
content
text
and
allows
you
to
form
a
relationship
over
to
other
items
that
are
referenced
within
that
note,
such
as
the
author,
and
that
would
make
it
something
you
could
place
fields
or
place
an
entire
rendered
version
of
the
author
of
a
node
as
a
block
when
you're
on
the
nodes
layout.
So
that
would
be
very,
very
cool.