►
From YouTube: Backdrop Weekly 3/16
Description
Today’s development agenda: http://bit.ly/2mMguPI
A
All
right,
we
are
on
air
happy
Thursday,
it
is
March
16th
we're
just
gonna.
Do
a
quick
check
in
on
development
things
that
we
are
working
on
as
far
as
I'm
aware,
there's
nothing
super
exciting
going
on
for
the
PMC,
unless
anyone
here
has
any
updates.
Okay,
most
exciting
progress
happening
recently
has
been
on
backdrop.
A
Cms
org
and
it's
subsites
mike
has
done
a
ton
of
work
on
the
new
homepage
redesigned,
starting
with
the
layouts
and
I,
think
we're
going
to
try
and
launch
that
tomorrow,
at
5pm
and,
lastly,
find
anything
significantly
problematic
with
what's
there
now.
But
that
means
that
we
need
help.
Q,
laying
so
I
put
a
link
in
the
agenda
to
back
job
CM,
esta
micro
Caffrey,
not
net.
If
anyone
has
any
time
today,
you
can
help
click
through
pages
and
just
make
sure
everything
looks
sort
of
fine.
A
B
A
C
D
Have
a
suggestion,
/
question:
maybe
we
can
discuss
this
I
think
it's
awesome
that
Mike
set
up
the
sandbox
site
on
his
personal
website.
That's
going
the
extra
mile
there
to
get
us
so
that
we
can
QA
this
I
remember
a
couple
weeks
ago.
We
asked
likewise
and
this
just
on
pantheon,
and
the
answer
to
that
is
that
bike.
Jeff
CMS
has
a
lot
of
specialized
integrations
that
require
a
dedicated
server.
D
Essentially,
however,
that
got
me
thinking
that
perhaps
like
there's,
no
reason
why
we
can't
use
pantheon
for
demonstration
and
QA
purposes
like
potentially,
we
could
use
like
multi
dev
and
multiple
sand
boxes,
and
things
like
that
on
Pantheon
and
just
have
a
mirror
of
backdrop.
Cms
org
that
we
can
all
can
collaborate
on,
even
if
we're,
even
if
the
production
website
isn't
actually
launch
day.
So.
D
Right
yeah,
I
understand
that
we
have
a
deficit
but
we'll
run
into
you,
know
access
problems
and
deployment
problems
in
the
same
way
that
we
wouldn't
pretty
much
well
on
tightropes
ems
torg
itself
right
and
I
think
it's
fine,
the
pack
job
CMS
torgus
lockdown.
Well,
I
don't
know
it
was
just
an
idea
that
may
be
potentially
it
didn't.
Don't.
D
Okay
noted
its
possibility
in
the
future
food
not
happening
for
now
sounds
good,
but
yeah.
Okay,
I
just
think
it'd
be
nice.
If
you
know
we
had
the
ability
to
deploy
changes
to
dev
without
requesting
access
from
other
people,
but
I
think
the
answer
to
that
is:
we
just
need
to
get
more
people
access
to
the
dev
server
and
sorry
have.
A
A
dev
server
if
we
could
set
it
up,
we
could
give
anyone
who
wants
to
develop
access
to
dev
server
without
any
risk
to
live
server,
and
we
might
even
be
able
to
set
it
up
so
that
our
automated
sanitized
backups
get
copied
their
automatically
to.
But
we
can't
do
anything
until
it
has
donated
domain
name.
Linda.
A
A
Okay,
for
now,
I
would
just
encourage
anyone
who
wants
to
work
on
backdrop
to
do
whatever
is
listening
in
to
them
forum
the
forum
site,
good
news.
I
got
bakery
set
up
on
it
last
week.
I
set
it
up
on
the
forum
site.
I
set
up
on
the
api
site
and
both
of
those
I
should
be
talking
to
backdrop.
Semesta
org
I
would
love
it
if
we
could
get
some
people
testing
that
sign
on
process.
I
know
these
are.
A
A
I've
had
limited
success
with
it
like
it
as
long
as
I'm,
not
logged
in
to
a
different
user
account
in
the
same
browser,
it
seems
to
work
for
me,
but
I
would
love
to
get
some
actual
people
triangle
to
log
into
the
forum
and
seeing
if
it
copies
over
your
user
credentials
in
that
you
get
logged
in
correctly,
I
hit
a
couple
snags
on
API
said
yesterday
and
had
turned
off
in
order
to
get
logged
in.
So
worried
it
might
not
be
working
correctly,
but
testing
w's
testing,
but
that's
good.
A
If
we,
if
we
can
make
sure
that
login
user
experience
is
good,
I
think
we
can
start
telling
people
to
use
the
form
which
will
be
good
and
I,
don't
know
if
we
should
maybe
seed
the
forum
with
a
couple
of
issues
from
the
github
q
that
we
think
would
be
better
suited
to
a
forum
discussion
than
an
issue
queue
discussion
just
to
get
people
using
it.
Even
if
it's
just
us
like
okay,
here's
an
issue,
four
of
us
are
talking
about.
A
A
D
Since
no
one
else
is
a
meeting,
circor
is
just
making
the
suggestion
that
that
we
could
enhance
the
automation
on
github
to
make
it
so
that
we
had
/
pull
requests
and
boxes
in
the
same
way.
We
have
for
backdrop
core
itself,
which
would
be
awesome,
but
yeah
that's
going
to
take
some
efforts,
but
yeah
I
think
this
is
a
core
feeling,
the
waters
kind
of
thing,
but
I'm
not
sure
if
he's
gone
so
far
as
to
actually
volunteered
taking
on
that
effort.
B
Well,
we
can
make
it
possible
it's
fiction.
Is
there
is
low
to
lush
work
up?
There
is
a
one
piece
that
we
require:
attention
is
sanitizing
database
down
on
everything
else.
Have
you
already
have
on
that,
but
drop
by
drop?
Basically,
every
time
when
branch
created
sin
ti
will
cry.
Take
your
a
website
to
deploy
code
from
our
repository
on
I'm
dumb.
I
scale
database,
and
here
we
go.
We
have
a
QA
website,
typically
for
this
branch,
and
every
time
when
there
is
Luca
meet
God
has
been
organized
it.
B
Small
things
that
require
attention
is
what
these
database
update,
so
user
is
any
codes
require
update
database
structure,
its
need
to
be
properly
region
in
this
town.
We're
like
a
hook,
update
feature
and
from
from
this
point,
is
quite,
is
seriously
not
too
much
work
and
we're
doing
it
for
all
my
projects,
so
I
have
to
just
copy
paste
and
in
little
organized
this
process
where
and
how
and
on
which
further
atyminius.
A
B
Actually,
awesome
idea,
so
if
we
have
a
static
URL
that
we
can
always
request
using
sound
password,
then
we'll
get
access
to
specific
file,
it
will
be
automatically
on
each
deploy.
It
will
be
automatically
downloaded
and
put
in
a
sandbox.
The
difference
is
if
we
already
created
sandbox
database
of
SQL
update
away
from
a
fresh
one.
It's
like
a
questions
that
will
be
discussed,
but
it's
like
a
small
things
to
start
top.
It's
like
I,
don't
know
with
my
current
schedule,
like
a
few
days
to
make
it
possible.
B
D
B
D
A
D
A
Next
item
on
the
agenda
is
the
translation,
server.
I,
don't
think,
there's
been
any
update
on
this
since
last
week
it
looks
like
we
have
a:
what
does
it
localized
I've
active
semester
or
a
site
up
that
can
translate
things.
We
just
need
to
figure
out
how
to
get
people
translating
them.
If
we
can
get
bakery
working,
we
can
also
put
bakery
on
to
the
translation
server.
The
triple
seven
version
should
work
there
too,
in
order
to
test
bakery.
A
Just
because
I
saw
a
note
here
in
the
dock,
you
just
try
and
log
in
to
the
forum
website.
If
you
have
a
account
there
already,
it
should
copy
your
credentials
from
factor
of
CMS
org
over
to
the
forum
site.
If
you
don't
have
an
account
already,
it
will
create
an
account
for
you
copying
your
credentials
phone
factor
of
CMS
network
over
to
the
form,
so
it
should
work
for
both
of
those
scenarios
and
if
it
works
for
one
and
not
for
the
other,
we
should
fix
that.
C
A
So
if
you
try
and
log
in
with
your
password
from
the
forum
website,
it
should
throw
a
message
saying
that
your
account
needs
to
be
repaired,
with
a
link
for
you
to
repair
it
and
when
you
click
the
repair
link,
it'll
synchronize
those
credentials
once
and
then
from
then
on.
It'll
require
that
you
use
your
password
from
backdrop
CMS
network
instead
of
the
forum.
So
it
has
like
a
little
kind
of
a
synchronized
feature
which
worked
for
me
when
I
tested
it,
but
I
want
to
make
sure
it
works
for
everyone.
D
D
A
Hopefully
it's
a
weird
experience
than
sugar.
Ok,
so
I
don't
really
know
where
we
are
for
next
steps
of
translation
so
ever
other
than
installing
bakery,
but
I.
A
A
So
we'll
just
wait
and
see
if
anyone
else
wants
to
try
using
it,
I
would
recommend
playing
with
it
same
one
scene
where
we're
at
let
us
know,
and
that's
all
I
have
for
websites
related
to
backdrop
seeing
this
so
or
goodnight.
Do
you
want
to
take
it
over
and
talk
about
our
trip
itself,
yeah.
D
So
this
week
was
eventful
as
far
as
backdrop
releases
go
as
some
people
in
this
meeting
and
I'm
watching
this
video
probably
notice
that
we
had
two
releases
of
backdrop.
Yesterday,
1.62
and
1.63,
so
1.62
included
two
security
fixes,
both
of
which
were
accessed
by
past
problems
that
have
been
corrected.
You
can
read
the
full
details
of
that
from
the
security
announcement
or
by
visiting
backdrop,
see
my
storage,
/
security
and
so
162
corrected
those
problems.
D
Of
course,
if
you're
updating
new
sites,
you
should
be
using
163,
they
both
contain
the
security
fix,
of
course,
and
so
sites
that
are
updating
will
probably
just
skip
162
and
go
right
to
163.
The
versions
have
been
pushed
out
to
all
pantheons,
the
Pantheon
upstream,
as
well
as
all
of
our
normal
process
for
deploying
I.
Don't
think
that
we've
yet
gotten
the
docker
image
updated,
but
that's
just
played
I
think
to
start
the
process
for
getting
through
that
deployment,
which
I
understand
takes
a
day
or
two
anyway.
So.
D
And
that's
it:
that's
our
status
for
the
162
and
163
being
pushed
out
this
past
week.
164
is
now
the
next
bug-fix
release
and,
as
always
items
that
haven't
been
completed
in
the
previous
releases
have
been
bumped
into
one
sec.
For
you
can
find
the
issue
tracker.
It's
got
a
good
boatload
of
issues
that
we
would
like
to
get
fixed
or
that
are
nearly
fixed
and
are
slated
for
the
next
bug-fix
release.
D
1.7,
oh,
is
our
next
minor
release,
which
is
coming
up.
May
fifteenth
2017
of
these
of
these
items
that
we
have
slated
on
the
road
map.
You
can
see
them
on
the
agenda
here.
We've
got
page
element
blocks,
which
is
issue
1704
layout
relationships,
which
is
issue
21
34
and
reference
module,
which
has
its
own
contribute
record.
D
All
of
these
items
are
any
needs
review
state,
but
I,
don't
think
any
of
them
have
any
updates
since
last
week,
so
I'm
not
going
to
run
over
them
again.
All
of
them
need
assistance
in
reviewing,
though,
so,
if
anybody's
interested
in
contributing
some
other
time
for
review.
All
of
those
items
appreciates
code
reviews.
The
page
element
blocks
one
if
you're
looking
for
one
that
might
give
you
the
most
immediate
satisfaction,
the
page
element
block
blocks.
One
is
the
one
that
is
closest
to
completion.
D
They
will
probably
need
the
minimal
amount
of
work
so
1704
if
you're
looking
to
push
something
to
completion.
There's
also
much
for
other
features
that
we
would
like
to
include
in
1.7,
oh
and
many
items
that
have
some
items
that
have
been
completed
for
1.7.
Oh,
you
can
find
those
all
in
the
github
issue
tracker
under
the
1.7
Oh
milestone
tada,
that's
it
for
the
update
on
back
drops
a
messed
up,
a
respecter
of
CMS
the
product
we
move
on
to
general
discussion.
C
D
Well,
no
worries
you've
still
been
churning
out
poor
requests
like
a
machine
sup
of
nobody
would
complain
about
the
level
of
contribution
that
anyone
here
is
provided.
So
thanks
again,
as
always
to
all
of
our
contributors
and
thanks
everybody
for
joining
this
meeting
and
for
watching
and
we'll
catch
you
guys
again
next
week.
Thank
you
very
much
bye.
Everybody.