►
From YouTube: Backdrop Weekly Jan 18th
Description
Today’s development agenda: http://bit.ly/2mkHMKZ
A
Hoping
that'll
mean
that
later
this
month,
we'll
be
able
to
send
a
newsletter
out
to
our
people,
letting
them
know
about
the
Conservancy
as
their
fiscal
sponsor
and
also
requesting
donations,
which
is
something
we
haven't
done
for
a
long
time.
So
tax-deductible
donations
it'll
be
really
exciting
for
people.
This
week
we
have
a
new
community
member
Callum
ash
has
ported
the
file,
filled
paths
module.
So
thanks
for
all
your
work
there,
it's
looking
really
great
and
it
should
be
moved
into
contributory
later
today.
A
New
homepage
redesign
is
mostly
done
if
there
are
a
couple
of
little
CSS
glitches
that
I'm
going
to
clean
up
later
today.
But
if
anyone
sees
anything
weird
going
on
on
backups,
you
neste
org
related
to
the
new
homepage
stuff,
that's
up
file
an
issue
in
the
back
drops,
you
missed
our
cue
and
we
will
sort
it
out.
A
Also,
now
that
backdrop
1.9
is
out
I'm
hoping
to
take
the
borg
base
theme
and
apply
it
to
our
api
website,
so
we
can
get
some
consistent
branding
across
all
our
space,
so
that'll
need
to
be
done
a
little
bit
carefully
because
right
now
we
have
really
great
code
formatting
on
the
API
site
and
I
want
to
make
sure
that
we
don't
lose
any
of
that
in
replacing
a
theme
all
right.
Let's
turn
it
over
to
meet
for
backdrop.
B
One
point
nine
came
out
on
Monday
and
that
included
some
minor
new
functionality,
including
the
ability
to
edit
an
existing
file
in
place
separate
from
any
pieces
of
content
or
anything
like
that,
and
that
is
they
have
a
couple
other
minor
additions,
functionality,
wise
and
1.9
as
well,
but
that's
kind
of
the
main
one
that
you'll
see
from
a
end
user
standpoint,
there's
also
quite
a
few
bug
fixes
and
everything
that
are
in
1.9
and
we'll
cover
real
quickly.
What
those
things
are
in
the
1.8
point
to
update.
B
B
We
also
included
all
those
fixes,
of
course,
in
1.9
itself,
so
I
just
wanted
to
put
it
out
there
if
you're.
Looking
to
great
one
point,
eight
point
two
for
some
reason
like
you
just
want
the
bug
fixes,
you
don't
want
the
new
features
in
1.9,
then
that
versions
available,
but
really
because
of
the
minor
increment
nature
of
1.9.
We
even
put
in
the
release
notes.
We
really
just
recommend
everybody.
B
B
Regarding
the
creation
of
the
new
release,
we
have
a
checklist
that
we
follow
every
time
we
make
a
new
version
of
backdrop,
and
the
checklist
for
1.9
is
at
issue
29:41,
and
some
of
the
items
in
the
checklist
that
have
yet
to
be
completed
include
writing
up
a
more
comprehensive
blog
post.
They
never
dumb
did
it
are
you've
drafted
it
no.
B
A
A
B
A
B
And
a
lot
of
those
include
my
captain
roadmap
updating
the
docker
image,
push
meant
to
Pantheon
updating
Wikipedia,
so
we've
got
a
couple
of
things
that
need
to
become
there
that
will
kind
of
address
this
soon
as
possible,
but
one
point
9.0
itself
is
out
and
has
been
announced
via
Twitter.
At
least
it's
on
the
home
page.
Everybody
sites
are
probably
saying:
hey,
there's
a
new
version
available
now.
So
all
of
those
things
proceeded
as
expected,
with
no
no
special
surprises,
which
was
great.
B
There
is
one
issue
that
we
identified
pretty
quickly
after
the
release
came
out,
and
that
is
that
there's
a
set
of
circumstances
that
make
it
so
that
it
can
be
difficult
to
run,
update
dot,
php',
we're
sorry
difficult
to
login
after
upgrading
from
a
previous
version
to
1.9
point.
Oh,
if
you
already
logged
in
and
you
run
update,
whp
or
if
you
run,
update,
dot
PHP
be
at
rush
or
you
run
update
PHP
via
using
the
update
free
access
instead,
except
PHP.
B
All
of
those
things
work
fine,
but
if
you
are
not
logged
in
to
your
website
and
you
can't
access
up,
they
got
PHP.
Then
you
have
this
problem
that
you
can't
log
in.
So
it's
a
set
of
circumstances
that
itself
it's
actually
not
even
like.
If
you
follow
the
update
instructions,
you
won't
run
into
this
problem,
but
lots
of
people
do
that
like
update
the
code
first
and
then
realize
they're,
not
logged
in,
and
so
it's
possible
that
people
run
does
kind
of
frequently
when
updating
to
1.9.
B
We
don't
want
to
get
into
a
situation
where
people
are
not
blind
update
to
minor
versions
because
they
run
into
problems
when
updating.
So
we
have
a
patch
that
fixes
this
particular
problem.
It's
issued,
29:43
I,
think
who
knows
yeah
Gregory
just
said
we
should
get
on
1.9
point
one
as
soon
as
possible.
B
B
A
So
this
is
just
something
that
Olaf
mentioned
in
the
meeting
notes
here,
that
we
changed
the
way
database
passwords
were
handled
in
1/8
and
somebody
who
just
upgraded
from
the
previous
version.
One
each
to
1/9
is
having
a
password.
The
previously
works,
no
longer
works
and
I
think
that's
the
source
of
%
symbol
in
it.
So
we
need
to
figure
out
if
the
encoding
that
we
added
for
our
database
handling
doesn't
work
with
the
percent
symbol
and
trying
to
get
that
fixed.
All
I
was
wondering
if
that
was
critical
or
not
so
him.
A
If
we
have
a
fix
ready
for
1/9,
one
I
would
recommend
we
get
it
in
and
because
the
you
know
we're
gonna
be
having
a
bunch
of
people
wanting
to
upgrade
and
the
lease
the
less
we
can
affect
them.
The
better
I'm
not
sure
it's
critical,
because
I
don't
know
how
many
people
are
using
it,
but
it
seems
pretty
terrible.
You're
even
I
know.
B
It
sounds
it
sounds
critical
that
your
psyche
was
working
in
the
update
and
then
it's
not
working
anymore
because
it
can't
connect
to
the
database.
I
mean
that's
I
mean
it's,
not.
Data
lost
level
critical,
but
it's
you
know
your
site
gets
entire
broken
I'm,
pretty
critical,
I,
also
kind
of
I.
Imagine
that
it's
not
kind
of
tough
to
track
down.
Oh
I,
don't
know
how
to
look
at
the
airport.
A
B
B
B
B
Okay,
also
in
the
Crossroads
land,
there
was
one
issue
of
cross
ports.
The
latest
versions
of
Drupal
Drupal
7.56,
there's
a
number
of
cross
ports
that
haven't
been
completed
yet
and
we're
tracking
those
crosswords
at
issue.
27
76
and
those
are
kind
of,
as
always
kind
of
as
soon
as
possible
type
item
just
to
keep
us
on
par
with
what
people
are
saying
in
gerbil,
okay,
1.10
I.
B
B
For
this
a
couple
of
months,
they
were
probably
going
to
be
pulling
out
issues
related
to
translation
and
bringing
them
up
during
these
weekly
meetings
to
items
that
are
in
progress
include
making
menu
items,
translatable
issue
or
issue
2:25,
and
this
one
is
functionally
complete.
We've
had
a
consumer
Jeeves
on
that
Olaf
since
you're
here
on
the
meeting.
Thank
you
for
taking
a
look
at
that
and
reviewing
they're
eating
it
even
I
think
it
even
includes
tests,
but
now
that
I
think
about
I
can't
recall
if
it
does
or
not
anyway,
the
poor
request.
B
There
needs
a
little
bit
of
work
based
on
some
user
experience,
feedback
that
we've
gotten
but
functionally
it's
complete.
So
that's
a
really
prime
candidate
for
1.10
and
hopefully
we'll
be
able
to
get
that
finished
early
on
in
the
release
cycle.
A
more
comprehensive
set
of
changes
is
issue
704,
which
is
adding
the
concept
of
configured
translation.
B
There's
a
proof-of-concept
pull
request
there
and
some
discussion
about
how
we
think
the
thing
should
work
and
I
think
that
we
have
a
direction
there.
That
is
really
solid
and
people
would
agree
upon,
but
we
need
some
more
work.
First
on
the
implementation
concept
and
then
we
need
to
take
the
concept
and
then
apply
it
throughout
all
of
core.
So
those
two
things
can
be
done
separately.
B
A
So
this
is
based
on
the
results
of
our
survey,
so
for
those
of
you
haven't
noticed,
we
have
a
survey.
That's
currently
on
our
blog.
We
send
it
out
via
newsletter,
we've
been
tweeting
about
it.
Recently,
we've
gotten
an
overwhelming
number
of
responses.
I
can't
believe
how
many
people
have
taken
the
time
to
answer
the
survey
we've
had
so
far,
I
think
eighty
people
complete
this
everybody
haven't
checked
my
inbox
today
to
find
out,
if
they
many
more
but
I,
that's
fantastic.
A
We're
getting
some
really
great
statistics
on
with
the
makeup
of
the
people
who
are
on
our
mailing
list,
as
well
as
people
who
are
just
finding
that
post
through
Twitter
from
our
blog
and
it's
kind
of
what
we
expected.
But
one
of
the
things
we
asked
with
what
the
blockers
work
for
getting
adoption
in
our
number.
A
A
So
I
think
getting
that
sorted
out
to
have
give
people
a
better
searching
experience
both
on
bike
trips.
You
must
org
where
we
can
have
like
a
select
list
of
the
support
and
tags
in
it.
You
know
I'm
Otto,
complete
of
the
regular
tags
and
then
on
the
supper
itself,
or
you
can
they're
grouped
by
the
supported
categories
that
you
can
search
using
the
search
box
for
anything
with
a
specific
tag.
A
Then
you
don't
have
to
know
exactly
what
category
that
module
is
placed
and
you
can
search
for
other
things,
so
I
think
that'll
help
and
so
I
want
to
I
taste
that
and
see
you
know.
We've
got
a
couple
for
quest
in
the
QC.
What
state
they're
in
what
of
you
know
how
much
of
that
we
can
add
to
in
the
1/2
X
cycle
to
make
that
better
experience
and
then
adding
screenshots?
We
know
we
haven't
had
screenshots
for
themes,
since
we
want
launch
the
search
for
themes,
page
1
impacted
semester,
org.
A
We
have
some
ideas
about
how
to
support
multiple
screenshots.
We
need
to
figure
those
out
and
get
that
sorted
out,
and
these
changes
to
backup
itself
will
coincide
with
changes
to
backdrop
CMS
to
org
to
support
the
new
features
that
we're
adding
so
like
show
the
screenshots
once
we
good
then
supported
via
the
info
file.
So
we've
got
some
work
to
do
there,
but
I
think
based
on
the
feedback
of
our
survey.
It
should
be
a
higher
priority
item.
So
that's
why
I
have
tagged
some
of
these
things
for
one
time.
B
B
Semi
official
I
mean
it's
it's
almost
like
with
a
90
percent,
so
you
need
the
next
version
of
backdoor.
It
will
be
one
point
ten
not
going
to
2.0,
so
we
can
now
that
we've
kind
of
made
that
decision
that
kind
of
leaves
the
door
open
here
for
continuing
down
minor
releases
for
a
really
long
time,
because
we
can
just
keep
going
to
1
dot,
11,
12,
13
and
so
forth.
B
Up
until
we
get
to
a
an
inflection
point
where
we
need
to
make
a
decision
about
actually
releasing
2.0
or
they
think
universally
amongst
all
community
members
that
have
chimed
in
that
anywhere,
they
have
all
agreed
that
we're
not
ready
to
break
backwards-compatibility
yet
with
earlier
versions
of
backdrop
and
explicitly
the
Drupal
compatibility
layer.
So
continuing
the
one
dot.
X
branch
keeps
us
within
semantic
versioning
standards
and
also
saves
us
a
lot
of
effort
needing
to
modify
the
way,
update,
module
works
and
backdrops.
B
B
That's
it
for
the
product
updates.
This
week
it's
been
oh
man,
it's
been
quite
a
week,
so
I'm
really
excited.
Congratulations
again,
thank
you.
Everybody
for
your
hard
working,
kidding,
1.9
out
the
door
and
yeah
another
great
year
of
backdrop.
Work
we've
now
had
10
releases
of
backdrop,
including
like
1.0
up
to
1.9
yesterday
yesterday
was.
C
B
C
B
That's
just
the
gestation
period.
Exactly
so
backdrop
is,
has
turned
three
years
old,
which
yeah
I
mean
done,
and
itself
is
it's
a
pretty
tremendous
milestone.
I
know
we're
continuing
to
build
other
people's
confidence.
In
the
backdrop
platform
I
mean
the
new
features
and
functionality
that
we're
adding
or
speaking
volumes,
I
think,
but
for
those
people
that
have
never
used
backdrop,
I
think
we're
really
shocking
people
with
just
purely
with
the
longevity
and
the
continued
existence.