►
From YouTube: Backdrop Weekly June 1st
Description
Today’s development agenda: http://bit.ly/2ql4seJhttp://bit.ly/2ql4seJ
A
A
Stuff
Wes
was
there
and
gave
us
an
update,
he's
got
a
fresh
database
dump
and
he's
going
to
be
working
on
some
of
the
missing
pieces
of
content
for
the
home
page,
because
we
have
content
in
the
new
database
which
somehow
views
set
up
for
it.
So
I
think
we're
in
a
pretty
good
position
on
that
so
and
he's
made
a
bunch
of
progress
over
the
weekend.
He'll
probably
do
some
more
progress
this
weekend,
so
looking
forward
to
that
you'll
be
great.
That
is
it
for
a
backrub
CMS,
org
updates.
B
All
right,
let's
see
here
so
backdrop,
1.7.1,
is
our
next
bug
fix
release
of
backdrop.
A
week
ago,
when
we
had
this
meeting,
I
had
discussed
possibly
making
that
release,
which
would
have
been
Tuesday
this
week
on
May
30th,
but
really
looking
at
the
items
that
we
had
slated
for.
1.70
I
couldn't
really
bring
myself
to
make
the
release
because
didn't
seem
to
be
necessary,
so
we
did
not
make
1.7.1
release.
B
So
so
it's
been
delayed
for
a
little
while,
while
we
rack
up
issues
that
actually
need
to
be
fixed
and
get
merged
in
so
no
major
items
still
for
1.7.1
that
I'm
aware
of
and
so
we've
just
got
the
issue
tracker,
you
can
find
a
milestone
within
k-dubb
1.7.1,
there's
still
only
one
RT
bc
issue,
I
believe
for
that
version,
but
there's
lots
of
items
that
have
been
marked
needs
review.
We
could
definitely
use
some
peer
reviews.
B
So
let's
talk
about
1.8
1.8
is
the
next
minor
version
that
will
be
coming
out:
May,
15,
2017,
and
so
far
we
have
a
small
number
of
items
that
we've
started.
However,
each
of
the
items
are
kind
of
major,
so
the
first
time
that
we
have
is
layout
relationships,
issue
2130
for
this
one
we've
brought
up
for
pretty
much
all
of
the
1.7
cycle
as
well.
Its
status
is
still
the
same
as
before.
B
That
would
be
an
awesome
feature
to
continue
working
on
the
media,
library,
media
libraries
issue
14:48,
and
there
has
been
work
on
this
very
recently
and
on
I
haven't
looked
at
the
individual
issues,
but
that
issue
is
a
meta
that
has
a
number
of
sub
items
for
improving
the
media
support
within
backdrop.
Let's
see.
A
B
A
B
Anyway,
I
think
that
that's
a
really
worthy
goal
for
us
to
pursue.
It's
also
like
the
ideas
that
we
have
here
are
definitely
divergent
from
those
that
we're
seeing
shape
up
the
next
version
of
Drupal
8.
We've
also
been
working
on
media
support,
but
taking
it
in
an
entirely
different
tack,
I
think
than
we
are,
as
usual,
drupal's
and
being
really
ambitious
with
its
scope
and
flexibility.
B
So
another
item
that
I've
got
slightly
here:
41.8
config
translation
I
posted
an
update
just
recently
about
how
I
think
that
we
might
be
able
to
tackle
config
translation
in
issue
704,
it's
kind
of
a
hole
in
our
functionality.
At
this
point,
right
now
for
translation,
we
basically
handle
translation
the
same
way
as
it
had
been
done
in
Drupal,
7
or
a
few
have
things
like
content
tightening.
B
We
just
run
that
content
type
name
through
the
T
function,
and
we
do
that
kind
of
manually
right
now.
So
it's
it's
no
different,
whereas
in
Drupal
7
had
been
like
you
pull
values
out
of
the
variable
table
or
the
note
type
table
or
any
other
type
of
thing,
like
a
view
or
any
other
configuration,
and
then
you
just
ran
through
T,
which
was
never
really.
B
We
just
continue
doing
what
we're
doing
right
now,
but
we
sanctioned
and
just
being
an
okay
approach
and
we
make
it
okay
by
making
those
strings
discoverable,
that's
the
basic
idea.
It
also
won't
required
a
tremendous
amount
of
work.
I,
don't
think
so.
I
lots
of
benefits
to
that
backwards.
Compatibility
backwards,
compatible,
doesn't
require
a
whole
heck
of
a
lot
of
work,
and
you
end
up
with
no
new
interfaces
for
people
to
learn
like
to
just
continue
using
the
locale
module
to
translate
stuff.
B
That
is
both
in
code
and
in
config,
rather
than
having
a
third
interface
from
content
or
content,
translation,
config,
translation
and
code
translation,
there's
still
only
two
there's
content
and
then
there's
everything
else.
So
it's
an
idea,
and
we
can
talk
more
about
it
in
that
issue.
There's
no
code.
Yet
it's
just
ideas.
B
C
Originators
started
thinking
about
it
as
to
point
X
saying,
but
there's
certainly
no
API
change
and
my
main
reason
for
thinking
to
point
X
is
I
thought
it
would
take
me
a
while
to
do
it,
but
the
basic
import/export
forward
is
not
WordPress
a
backdrop.
Content
is
a
is
there
and
then
it
just
needs
to
be
extended
to
accept
WordPress
and
possibly
Drupal
files.
C
Know
I
can
I
can
look
at
it
as
a
contribute,
hadn't
thought
of
it
that
way.
It's
just
the
way
it
came
up
was
through
to
point
X
conversations
and
people
getting
content
from
WordPress
specifically
to
backdrop
and
it's
in
WordPress
core,
so
my
thinking
had
always
been
core,
but
I
can
look
at
a-
contributing
right.
Now
I
integrated
to
the
system
module.
I
would.
A
Love
to
see
that
in
corpse,
I
think
it
would
be
a
big
like
selling
point
for,
like
are
you
limited
by
what
wordpress
can
do,
choose
a
more
comprehensive
content
management
system
and
then
because
wordpress
has
a
built-in
export
having
something
in
backdrop
that
has
a
built
in
import?
I
think,
would
be
really
great
for
people
to
just
try
it
like
take
their
WordPress
content,
throw
it
into
a
backrub
site
and
see
what
they
get,
but
I
think
that
might
really
help
adoption.
A
If
people
can
just
feel
like
okay,
I
plugged
it
in
I
get
it
I
can
see
my
website.
It
looks
good
or
looks
at
least
like
my
content.
It
would
give
people
a
real
good
idea
of
what
they
could
do
with
backdrop.
So
I
think
it's
a
good
like
marketing
perspective
tool.
I
think
it's
also
kind
of
helping
our
target
market
right
or
people
who
might
already
be
using
WordPress
and
so
giving
them
a
clear.
B
C
A
C
A
That's
right
so
I
gave
them
access
to
project,
installer
and
updater,
and
all
that,
but
then
I
wanted
to
give
them
a
way
to
be
able
to
easily
make
backups
of
everything
before
they
did
any
of
those
kind
of
updates,
and
so
I
set
up,
backup
and
migrate
and
I
thought
that,
having
like
those
that
pair
of
combination
of
tools
would
be
super
powerful,
because
then
people
wouldn't
need
to
hire
developers
to
do
all
that
for
them.
Unless
there
was
a
problem
right,
they
could
be
like
Ron,
the
updater
Olaf.
A
All
my
stuff
is,
you
know,
out-of-date
make
a
backup,
ok.
Well
now,
I've
made
a
backup,
I'm
gonna
run
the
update,
and
then,
if
everything's
fine,
then
they
can
just
carry
on
with
their
day-to-day
work
and
having
something
like
this
that
can
generate
a
backup
of
your
content,
might
tie
in
nicely
with
that
or
it's
like
here's
all
of
the
stuff
from
your
database
that
you're
going
to
need.
So
if
you
need
to
restore-
or
after
maybe
a
bad
upgrade,
that
might
be
a
good
way
to
do
it.
A
So
there's
kind
of
a
tie-in
between
like
a
tool
that
lets
you
import
other
content
and
export
your
own
sites.
Content
versus
something
lets
you
do
backups
like
I
mean
I
could
see
a
JSON
file
being
an
excellent
way
to
backup
all
of
your
existing
content.
It's
not
the
same
as
like
a
my
sequel
dump.
Obviously,
but
it
might
still
be.
C
B
C
Yeah,
we
have
to
think
about
a
do.
We
just
explain
to
people
that
they
should
move
their.
You
know
if
they're
exporting
it
to
a
different
site,
they
shouldn't
their
files
directory
yeah
it
song.
We
need
to
think
about
yeah
plus
there's
other
kinds
of
content
like
taxonomy
terms
and
all
kinds
of
things,
they're
just
going
to
need
their
own
kind
of
little
handling
and
a
case
of
WordPress
I.
Think.
A
A
Doesn't
it
was
mentioning
like
those
IDs
need
to
stay
unique
across
all
instances
and
if
a
ref
like,
if
it
ID
changes
from
one
side
to
another,
that's
going
to
be
a
problem
like
all
your
tags
will
be
wrong,
but
I
think
that,
like
there
are
solutions
to
this
in
Drupal
already,
you
know,
migrated
ran
into
a
bunch
of
them
with
like
set
you
IDs
for
as
much
things
as
possible
and
I
think.
Maybe
one
path
forward
for
this
might
be.
If
you
can
refactor
this
into
a
control.
A
Six
and
like
we
have
these
taxonomy
terms
and
the
IDS
didn't
work,
so
I
use
the
UUID
solution
or
whatever
it
is,
and
that
will
kind
of
give
us
a
clear
path
to
how
we
want
to
handle
this
in
core
in
future.
And
then
we
could
also,
you
know,
I,
don't
know
what
to
X
is
coming
out,
but
it
would
give
us
an
idea
of
whether
it'll
be
ready
by
then
or
not
yeah.
B
B
That
are
some
wishlist
items,
some
things
that
are
in
progress
already,
many
of
which
are
you,
are
have
a
needs
review
some
yeah
between
those
two
tags
for
milestones
and,
of
course,
any
issues
that
our
contributors
have
been
working
on,
that
have
open
forward
quests
I'm,
looking
forward
to
taking
a
look
through
those
and
yeah,
but
that
will
be
where
we're
heading
for
one.
It's
eight,
that's
it
for
the
backdrop
product
I
kind
of
jumped
ahead
into
the
Q&A
stuff,
because
that
was
the
only
thing
we
had
was
talking
about
import
expert
from
chef.
B
B
A
Anything
else
we
stuck
but
this
week
or
anything
we
specifically
want
to
talk
about
next
week.
No
okay,
well
I,
would
say:
let's
go
back
to
the
issue,
queue
and
get
back
to
work.
If
anyone
has
any
ideas,
Twitter
the
issue
queue
is
a
great
place
to
put
them
or
talk
to
us
in
getter,
and
we
can
figure
it
out.