►
From YouTube: Backdrop Weekly Oct 5th
Description
Today’s development agenda: http://bit.ly/2hmjMV3
A
Check-In
meeting
for
backup
CMS
can
see,
updates
there
aren't
any
PMC
members
here
that
haven't
sent
in
their
agreements
for
the
software
freedom
Conservancy,
but
I
have
a
feeling
that
there
are
PMC
members
among
us
that
haven't
done
that
I
emailed
the
lawyer
last
week
to
find
out
how
many
copies
he'd
gotten
and
if
we
were
still
short
I,
have
a
feeling,
we're
probably
still
short,
I'll,
follow
up
with
them
again
this
week,
but
we
need
to
get
moving
on
that
community.
This
week
we
had
a
new
maintainer
application.
A
Opie
who's
been
working
really
hard
in
core
lately,
helping
us
in
particular
with
backdrop
1.8
ported,
his
first
module,
the
geolocation
module,
and
so
that's
fantastic.
Thank
you
for
starting
to
work
on
contribs,
nuke
and
rip
projects
this
week,
smooth
roll
and
text
formatter
both
have
new
releases
or
a
backdrop
which
is
great
and
me
when
I
talk
about.
B
Releases
yeah,
so
it's
been
2
weeks
since
we
had
a
good
meeting.
Sorry
last
week,
Jenna
and
I
were
out
of
the
country,
and
so
we
didn't
have
a
meeting
last
week,
but
I
think
it's
worth
noting.
This
is
our
first
meeting
since
1.8
was
released.
I
think
we
should
yeah
yeah
we're
at
least
one
point,
a
new
minor
version
of
backdrop.
B
It's
very
very
exciting,
and
you
know
every
time
we
get
a
new
release
out
its
continuing
in
the
evolution
of
backdrop,
CMS
and
so
I
think
we
should
all
be
really
pleased
with
having
put
out
another
release
regarding
1.8.
Almost
everything
is
done.
A
newsletter
went
out
just
this
morning.
Talking
about
backdrop
1.8,
the
blog
post
is
written.
Obviously
the
release
is
out
there
and
everything
it
came
out
as
expected
on
September
15th.
B
B
B
B
Yeah
a
little
well
two
weeks
is
that
right,
yeah
it's
been
over
two
weeks,
but
we
normally
wait
until
we
release
one.
The
next
bug
fix
release,
although
we
haven't
really
had
any
items
arises,
really
requiring
a
bug
fix
release.
So
I
think
that
we're
probably
good
at
this
point
to
say:
let's
go
ahead
and
put
the
upstream
for
Pantheon
21.8,
as
well
as
the
docker
image
and
just
get
everything
all
officially
recommending
the
latest
version.
B
Like
I
just
said,
we
don't
have
any
key
items
that
need
to
be
completed
in
this
bug,
fix
release,
or
at
least
nothing
that
would
prompt
us
to
cut
a
new
release.
However,
before
1.8
came
out,
we
put
a
bunch
of
effort
into
finishing
up
a
bunch
of
cross
ports
from
Drupal
7
up
50
up
to
7.56
and
there's
a
bucketload
of
issues
that
track
all
of
these
cross
ports.
B
2013
is
7.50
in
previous
and
I
think
that
there's
only
one
or
two
remaining
cross
ports.
There
I'll
actually
looks
like
there's
one
or
two
pull
requests
that
out
there,
but
they're
still
probably
could
dozen
cross
ports
there
and
then
back
to
our
side.
Ripple
7.51
through
7.56
are
covered
by
backdrop,
issues
2774
twenty
seven,
seventy
five
and
twenty
seven.
Seventy
six
and
all
of
those
also
have
pull
requests
and
all
of
them
are
more
than
half
merged.
B
At
this
point,
so
it's
great
to
see
those
cross
sports
getting
completed
and
all
of
them
I
expect
will
probably
be
done
by
the
time.
One
point
eight
point:
one
comes
out,
so
we
don't
have
any
timeline
and
we're
around
11.81
might
come
out,
but
there
will
be
a
lot.
A
lot
of
cross
ports
in
that
bug,
fix
release,
there's
also
other
items
that
we
have
scheduled
for
1.81.
There's
about,
looks
like
about
35
or
so
issues
that
we
would
like
to
have
done
as
soon
as
possible
that
it
tagged
for
the
one
point.
B
Eight
one
milestone
most
of
those
have
no
requests,
although
almost
all
of
them
are
in
the
status,
it
needs
work
in
the
current
pull
request,
queue,
there's
nothing
our
TBC
and
only
six
items
that
are
in
needs
review
so
where
our
review
log
is,
is
really
short
right
now,
so
it's
a
great
opportunity
to
move
for
requests
into
needs
review
and
because
the
key
was
completely
empty
right.
Now,
there's
a
really
good
chance
that
the
item
will
get
reviewed.
B
B
B
B
So
it's
open
season
on
crazy
ideas.
Right
now,
I
think
the
only
item
that
we
really
really
have
slated
for
1.9
at
this
point
is
there
was
a
lot
of
functionality
regarding,
but
a
media
handling
and
better
image
handling
in
particular
that
we
had
hoped
to
move
into
1.8,
including
the
ability
to
upload
a
file
independently
of
any
content,
as
well
as
edit
files,
independent
of
the
content
and
all
of
and
a
bunch
of
other
items.
B
B
Concentrating
on
one
item
at
the
very
least,
really
increases
our
probability
of
delivering
that
functionality.
So
at
this
point,
that's
the
only
item
that
we're
really
that
we
really
have
state
goes
as
a
high
desirability
thing.
There's
other
things
that
we
brainstormed
in
1.8.
That
didn't
happen.
Some
things
like
adding
more
official
translation
support
to
configuration
management,
for
example,
relationships
to
layouts.
B
B
B
A
Also
this
this
is
edit
existing
files.
This
has
a
really
strange
user
experience
where,
when
you
edit
a
file,
people
are
expecting
something
different
than
what
actually
happens.
We
just
copied
what
file
entity
does
which
gives
you
a
fields
to
rename
the
file,
but
it
doesn't
actually
rename
the
file
a
train
into
a
current
record
in
the
database,
which
is
funny
and
then
there's
also.
A
Like
it
does
something
weird
with
the
temporary
files,
it's
really
confusing
to
people
so
I
think
it
needs
a
user
experience
task
as
well
as
a
like
I
mean.
Obviously
it
must
mean
an
upgrade
path,
but
there's
there's
some
weird
stuff
going
on
there
that
this
is
just
completely
not
intuitive
and
so
I
think
we
can
figure
out
how
to
smooth
out
those
non-intuitive
edges.
We
need
to
do
that
before
we
can
get
it
in
yeah.
B
You're
right,
the
file
name
thing
is
still
really
bizarro.
However,
we
had
a
reroll
before
one-point-eight
came
out
that
pushed
forward
a
lot
of
those
issues,
especially
the
temporary
file
management,
seems
to
I
think
largely
be
resolved
yeah.
You
can
take
another
look
at
that
and
see
if
there's
still
issues
to
meet
working
out,
the
upgrade
path
is
actually
a
lot
simpler
than
it
might
sound.
It
really
just
needs
an
upgrade
path
to
update
the
view,
so
the
view
needs
the
ability
to
have
the
Edit
link.
B
A
Some
time
trying
to
figure
out
how
to
make
that
form
field
that
changes
what's
in
the
database
also
rename
the
file
and
I
had
a
couple
problems
with
that,
because
you
have
to
like
rename
the
temporary
copy
and
then
there's
like
a
later
thing
and
it
renames
the
real
thing,
and
so
it
looked
hard.
Yeah
I'm.
A
B
Exactly
and
so
we
might,
we
can
also
circumvent
this
slightly.
Perhaps
by
doing
things
like
you
know,
perhaps
just
removing
that
field
you
know
make
it
so
the
ER
or
displaying
it
as
a
none
editable
field
or
displaying
it
as
just
a
label
and
a
value
without
you
know
just
as
text
and
make
it
not
a
field
at
all,
and
then
that
could
potentially
open
the
door
to.
B
Contribute
a
be
Ott's
that
it
could
break
stuff
or
Tim
trim
might
be
able
to
handle
the
complexity
of
you
know,
going
through
all
of
the
nodes
and
running
regular
expressions
on
the
bodies
to
update
the
file
names
yeah
so
yeah
anyway,
that
that
needs
some
work
clearly.
But
it
is
definitely
moving
along
after
that
one
issue:
26:33,
which
is
the
ability
to
upload
file
manually,
and
this
one,
like
you
say,
judge,
and
we
took
the
functionality
out
of
file
in
any
module,
but
it
still
needs
yeah.
B
A
Now
it's
a
multi-step
form,
so
first
you
upload
the
file
and
then
based
on
the
file
type.
It
gives
you
a
secondary
field
that
lets
you
secondary
form
that
lets
you
fill
in
any
fields
they
might
even
attach
to
that
file.
But
I
think
that
what
we
could
do
is
we
could
do
this
all
in
a
single
file
with
Ajax
so
like
after
you
upload
it.
Then
it
can
detect
the
type
and
then
load
in
the
rest
of
the
form
fields
as
necessary.
A
So
it
could
just
be
one
fancy
form,
rather
than
being
like
a
bunch
of
separate
unrelated
forms
that
you
page
through
but
yeah
again
it
that's
gonna.
Take
some
reworking
and
I
also
wondered
how
much
of
that
we
should
do
separately
from
the
next
issue:
26
32,
which
is
field
of
both
file
entity,
bundles,
because
the
two
of
them
kind
of
go
hand-in-hand
and
originally
I
thought.
B
Yep-
and
that
is
the
next
issue-
it's
going
to
bring
up
26
32,
which
is
adding
the
ability
to
have
files
that
are
filled
a
book,
and
this
also
encompasses
having
multiple
file
types.
Because
right
now
we
don't
have
file
types,
it
just
files,
our
entities,
but
they
don't
have
separate
like
types
like
content
type,
does
or
vocabulary
dozen
vocabulary:
alright,
taxonomy
module,
so
those
three
items:
kind
of
form,
the
core
of
functionality.
B
B
That's
all
I
was
going
to
mention
for
1.9
at
this
point,
we're
a
long
ways
away
and
we
have
a
lot
of
time
DeForest,
but
yeah.
We
do
tend
to
get
in
the
pattern
of
rushing
everything
at
the
end.
So
with
these
items
that
have
substantial
code
behind
them,
I'm
hoping
that
we
can
make
some
progress
earlier
in
the
release
cycle
and
really
put
some
kickass
functionality
into
backdrops
sooner
rather
than
than
later
for
1.9.
B
A
So,
a
couple
of
weeks
ago,
before
1.8
came
out,
we
had
a
bunch
of
really
great
conversations
going
on
around
the
translation
and
internationalization
and
I
thought
it
might
be
something
that
would
be
good
to
designate
a
particular
focus
for
a
particular
release.
So
if
we're
slating
1.9
to
be
a
release,
that's
focused
on
files
of
media.
Maybe
we
should
focus
1.10
on
translation
and
internationalization.
I
think
we
would
need
to
identify
a
bunch
of
specific
issues
related
to
translation.
A
Internationalization
is
that
we
want
to
have
fixed
whether
those
are
like
big
picture
issues
or
small
little
bug,
fix
sort
of
things
and
I'm
not
sure
we
have
a
concrete
list
of
those
yet.
But
if
we
had
scheduled
translation
internationalization
for
a
backdrop
10
that
might
be
something
really
right
now
people
would
start
trying
to
gather
together
their
thoughts
and
figure
out
what
kinds
of
things
we
do
want
scheduled
for
that
release.
A
So
another
thought
was
Jeff,
I'm,
not
sure.
If
you
were
around
for
this
meeting,
if
we
could
pick
a
site
for
backdrop
for
good
that
required
translation,
that
might
be
a
place
where
we
could
help
identify
pain
points
or
areas
that
needed
focus
where
we
could
be
benefiting
the
whole
backdrop
community.
In
addition
to
that
individual
site.
A
A
So
yeah
I'm
not
sure
where
we
are
on
that
I'm,
not
sure
we
need
to
make
a
call
on
dr.
up
ten
yet
but
I
know
Nate
there.
If
that
one
issue
that
we've
been
working
on
in
bactrim
I
think
was
one
seven
about
trying
to
figure
out
how
to
handle
translations
in
can
fake.
That
might
be
something
to
put
on
the
list
for
110
and
and
if
anything
else
comes
up
to
something
like
in
the
language
contexts,
maybe
for
layouts
or
something
getting
the
lay
up
relationship
thing
on.
B
B
No,
but
also
one
point
ten
point:
no
and
actually
start
tagging
issues
more
than
one
release
into
the
future,
indicating
that
you
know
we
could
be
working
on
stuff
expecting
it
to
not
be
in
the
next
release
and
I'm
not
actually
sure
like
what
the
benefits
of
doing
that
would
really
be,
but
it's
a
possibility
that
we
could.
You
know
use
at
least
for
planning
at
this
point,
even
if
we
don't
use
it
for
development
purposes.
B
A
One
of
them
would
be
on
the
direct
update
that
huge
key
like
screen
when
someone
starts
an
upgrade,
if
we
notice
that
there
are
no
controls
present,
that's
a
good
time
to
send
a
message
to
me
like
hey,
you
might
be
doing
things
wrong
if
you're
upgrading
for
without
a
job
but
not
be
a
blocking
thing
like
we
didn't
want
that
to
be
your
requirements
check
the
kiss
and
those
people
do
like
to
have
great
things
in
pieces
first
before
they
upgrade
it
properly
later.
So
we
wouldn't
want
to
break
that
process.
A
Even
if
we
wanted
to
use
that
moment
to
let
people
know
that
upgrading
court
without
kinship
might
not
work,
and
then
there
was
another
idea
about
if
an
upgrade
failed,
because
it's
not
able
to
meet
in
individual
modules
update
dependencies,
we
could
do
a
better
job
of
letting
people
know
which
upgrade
failed
and
which
dependency
wasn't
matt
or
right.
Now
it
just
skips
it
entirely,
and
so
nobody
would
even
know
if
that
upgrade
failed
or
not
until
it
was
too
late,
like
their
site's
finished
and
they
think
they're
done.
A
A
Legacy
data
mappings
table
which
it
sounds
like
the
current
status
status
on
that
is
no,
but
I
want
to
leave
that
issue
open
see
if
there
are
other
people
who
are
doing
kinship
courts
that
felt
differently
about
it.
So
this
is
for
things
like
texana
me
vocabulary,
IDs
and
user
role,
IDs,
which
are
deleted.
In
the
backdrop
triple
the
backdrop
upgrade
the
taxonomy
vocabulary.
Ids
are
renamed
to
vocabulary
under
silk,
underscore
whatever
the
ideas
and
the
user
roles
are
exactly
the
same.
A
It's
the
same
role
idea
in
both
places,
but
some
people
might
want
a
mapping
for
whatever
reason
to
order
to
get
from
one
to
the
other.
So
if
there
was
something
else
that
like
in
I,
don't
have
any
good
examples,
but
if
there's
something
else
that
needed
to
be
mapped,
we
could
save
that
data
in
a
database
table
so
that
it
would
be
available
for
other
country
projects
to
use
during
the
upgrade
process
if
they
didn't
want
to
depend
on
the
particular
order
of
operations.
A
B
You
know
this
brings
up
something.
That's
bothered
me
for
a
while
and
that
updating
their
backdrop
cite
an
existing
backdrop
cite
from
like
1.7
to
1.8,
for
example,
looks
exactly
the
same
as
upgrading
from
Drupal
7,
to
like
backdrop
like
the
major
major
upgrades
and
I,
think
that
we
could
definitely
improve
it
to
make
it
so
that
it
would
be
clear
if
you're
doing
like
a
major
version,
upgrade
that
things
look
different
and
function
different
than
if
you're
just
doing
a
day-to-day.
B
You
know
minor,
update
things
like
identify
if
modules
are
missing
and
let
people
like
let
people
know
that
we're
going
to
disable
that
module,
if,
if
they
don't
have
it
and
like
show
them
a
list
of
like
these,
are
all
the
modules
I
expect
to
find
and
tell
them
like
which
modules
actually
we're
found
and
which
ones
are
missing
and
say.
If
you
don't
include
them
right
now,
they
might
not
upgrade
and
they
definitely
will
be
disabled.
B
They
give
people
like
a
better
process
for
upgrading
from
from
Drupal
or,
ultimately
like
backdrop
on
the
backdrop
to
you
know,
because
right
now
it
like
even
our
our
update
page
is
updated
on
PHP
tells
you
to
do
stuff
that
doesn't
make
any
sense
right
now
for
a
major
upgrade
like
backup.
Your
config
directory
config
directory
doesn't
even
exist
yet,
but
it's
like
there's
no
need
to
back
it
up.
B
It's
not
even
there
yeah,
so
yeah
that'll
probably
be
an
inevitable
consequence
of
of
this
endeavor
to
to
make
it
so
that
we
give
people
better
messaging.
If
they're,
upgrading
from
Drupal
we'll
probably
end
up
rewriting
that
entire
page,
because
it
doesn't
make
any
sense,
the
latest
now
I
think
we're
just
kind
of
stuck
and
we're
just
so
used
to
word.
B
A
C
B
In
system
module,
okay,
we
also
could
even
get
smart
about
things
and
actually
tell
people
like
when
they're
running
an
upgrade.
Hey
you're
upgrading
from
this
version
to
this
version,
and
it
would
be
a
little
bit
weird
to
doing
the
backwards
compatible
manner
or
like
in
a
straightforward
manner.
But
we
can
map
system,
schema
versions
to
backdrop,
version
numbers,
for
example,
and
say
like
you're,
going
from
this
version
to
this
version,
but
that
would
require
every
version
of
backdrop.
Papa.
C
B
B
I
think
that's
it
for
this
meeting,
let's
wrap
it
up
and
yeah.
Thank
you,
everybody
for
watching
our
regular
weekly
dub
meeting.
If
you're
out
there
watching
feel
free
to
join
I
happen,
it
happens.
Every
single
Thursday
at
1:00
p.m.
Pacific
time
and
we'd
love
having
people
join.
You
can
keep
track
of
this
meeting
and
when
it
occurs
by
joining
our
Gitter
channel
or
by
following
us
on
Twitter,
and
so
that's
it
for
this
meeting.
Think
you're
ready
for
joining
and
thank
you
guys
for
watching
as
well.