►
From YouTube: Backdrop Weekly June 14th
Description
Today’s development agenda: https://goo.gl/9S6dVr
A
B
B
Although
I
mean
it's
now
been
one
month
since
1.10
came
out
and
that
kind
of
means
that
I
think
people
knows,
we've
got
three
months
until
1.11
comes
out
and
there's
lots
of
excitement
about
potential
things
that
could
be
implemented
and
we're
seeing
a
lot
of
activity
which
actually
is
really
great
to
see
it
at
this
point
in
the
development
cycle,
and
some
of
these
items
are
new,
some
of
them
are
old.
We've
got
a
great
grab
bag
of
great
new
functionality.
It
looks
like
it's
coming
together
before
we
get
into
1.11.
B
Be
of
course,
b12
tended
to,
and
we
don't
have
any
real
critical
issues
for
that
long
outstanding
issue.
Now
it's
a
long
outstanding
issue,
it's
2904,
which
is
regarding
database
credentials
that
the
way
that
we
store
database
credentials,
the
encoding
on
them
changed,
and
so
there,
if
you
had
special
characters
or
specifically,
a
percent
symbol.
B
Your
database
credentials
set
up
previously
now
I'm
working,
and
so
we
have
a
a
PR
that
started
there.
That
kind
of
fixes
the
problem
that
needs
just
some
visibility
improvements
to
make
it
so
that
we
notify
the
user.
That's
that
a
fallback
is
is
being
used.
So
that's
the
only
item
that
we've
got
for
the
bug
fix
release.
There
are
a
number
of
looks
like
about
20
items
for
one
dot,
10.2
that
could
potentially
be
handled
that
all
have
pull
requests,
but
we
won't
go
over
all
of
those
here.
B
So
let's
talk
about
1.11
looks
like
the
agenda
is
getting
moved
around.
This
could
be
exciting
going
through
these.
The
first
time
that
we've
got
is
issue
37,
which
is
one
of
our
oldest
open
issues,
the
entire
queue,
and,
if
you
37,
is
the
ability
to
add
tagging
to
modules
and
this
one
just
barely
got
bumped
out
of
the
1.10
release
and
we
have
a
plan
for
moving
forward.
B
Oh
there
also
will
be
some
like
the
modules
will
say
what
tags
they
have
applied
to
it
in
the
extended
description.
That
also
opens
the
door
for
more
possibilities
regarding
better
search
when
doing
the
site
wide
excited
when
doing
the
project
browser
or
installer
through
through
the
backdrop
application,
as
well
as
on
backup
CMS
store
the
work
to
make
it
so
the
modules
can
kind
of
categorize
themselves
more.
B
More
probably,
let's
see
next
issue
is
704,
which
is
configuration.
Translation
we've
been
moving.
This
one
I
think
this
is
now
the
third
release
that
we've
moved
this
to
still
the
last
release,
we
had
a
focus
on
translation
capabilities
and
we
got
two
out
of
three
of
the
translation
features
implemented.
Many
translation
and
block
translation
were
completed,
but
this
like
improving
the
config
translation
issue.
B
B
Some
of
them
are
for
sure,
going
to
happen
and
are
nearing
completion.
Things
like
having
a
settings
forum
for
contact
module
to
make
it
so
there's
more
configuration
other
than
just
categories,
improving
the
way
that
recipients
are
set
up
on
the
categories
forum,
let's
see
making
it
so
it's
contact
categories
or
a
reorder
Bowl.
Actually
that
was
that
actually
did
get
into
one
tenth,
but
it's
part
of
his
larger
group
thanks,
adding
a
cycloid
contact
form
block
I
got
one
is
kind
of
a.
B
Why?
Don't
we
have
it?
So
you
can
place
the
contact,
module
or
contact
form
in
a
block
and
place
it
on
other
pages,
lots
of
lots
of
really
great
improvements.
He
also
has
some
suggestions
to
enable
it
by
default,
enable
contact
module
by
default,
but
there's
some
concern
about
spam,
like
not
just
some
but
like
a
large
amount
of
concern
about
spam,
that
turning
on
contact
mantra
by
default
could
potentially
end
up
being
a
heavy
source
of
a
good
spam
target,
which
of
course,
then
leads
us
into
well.
B
Let's
get
some
spam
protection
in
court,
but
that's
the
kind
of
thing
that
maybe
you
know
we
haven't
really
gone
down
that
road
quite
yet
so
anyway,
I
hope
you.
Thank
you.
So
much
for
doing
all
of
this
contact
module
improvements,
there's
a
boatload
of
code.
Almost
all
of
these
issues
are
in
a
state
that
needs
review.
So
if
you
guys
I'm
looking
for
something
to
to
review
which
I
know
is
kind
of
funny,
because
Opie
is
like
ours,
our
premier
reviewer.
So
now
that
he's
written
some
new
code,
you
can't
self
review.
B
B
Boy
there's
so
many
items.
Okay,
next
item
up
is
note.
Preview
node
bring
back
the
node
previous.
This
would
add
a
preview
button
to
to
the
node
form
again
prior
to
save,
and
this
is
completely
reworked
version
of
preview.
We
removed
preview
from
backdrop
way
back
in
1.0,
because
the
preview
on
the
node
form
was
so
incredibly
useless
and
actually
misleading
that
it
would
just
show
you
this
big
dump
of
data.
That
was
in
the
administrative
theme,
so
it
was
just
like
a
complete
complete
waste
of
space
and
just
confusing
user
interface.
B
B
But
the
concept
of
this
note
preview
is
really
pretty
impressive,
that
it's
puts
the
entire
node
into
the
temp
store,
so
it
doesn't
actually
save
it.
And
then
you
can
go
and
look
at
a
preview
that
pulls
this
node
out
of
the
temp
store
and
you
get
it
in
the
front-end
theme
at
the
same
path
or
close
to
the
same
path,
and
it
looks
like
well.
B
B
So
let's
start
with
this
one
issue,
3105,
which
is
just
simply
allowing
core
itself
to
be
updated
via
the
user
interface
right
now
we
have
a
user
interface
for
updating
modules,
so
that
modules,
when
an
update
comes
out,
you
can
click
a
button
and
it
will
download
and
install
the
new
module
update.
That's
been
in
Drupal
7
for
its
entire
history.
B
I
think-
and
it's
been
a
backdrop
for
its
entire
history
after
we
got
the
project
server
set
up,
so
we
already
have
the
ability
to
update
modules,
but
we
don't
have
the
ability
to
update
core
an
issue.
3105
has
a
pull
request
that
needs
review.
That
makes
it
so
the
core
itself
can
be
updated
and
much
to
everybody's
surprise.
It
was
a
rather
trivial
implementation,
the
danger
level
there
is
the
same
level
as
it
is
with
King
Chair
modules.
Honestly
that
if
something
catastrophic
were
to
happen,
you
know
the
site
would
become
non-functional.
B
But
it's
been
the
same
problem
that
we've
been
you
know,
I
mean
the
same.
Problem
has
existed
for
the
entire
existence
of
the
contribute
dates
with
limited
problems,
so
extending
that
car
is
completely
reasonable,
with
no
real
increase
in
in
danger,
but,
like
you
know,
a
substantial
improvement
for
people
who
aren't
used
to
or
are
uncomfortable
with,
with
manipulating
the
code
on
their
site.
B
That,
though,
is
that
the
profiles
directory,
which
includes
the
installation
profiles,
is
not
inside
of
the
core
directory,
and
so
that
makes
it
so
that
your
profiles
directory
rarely
if
ever
gets
updated.
If
you
follow
those
steps
or
if
you
use
this
new
updater
via
the
user
interface,
you
would
also
have
the
same
problem
and
would
only.
B
It
really
wouldn't
affect
sites
bit,
I
mean
cuz.
Once
you
do
the
install
like
you
never
install
again,
who
doesn't
know
the
profile?
Doesn't
really
it's
not
it's
not
a
terrible
problem
but
yeah.
If
you're
doing
installs
on
a
regular
basis
like
via
multi-site,
then,
yes,
it
would
be
a
problem
because
you
could
end
up
with
an
older,
install
profile
on
a
newer
version
of
backdrop
and
then
and
thanks
cuoco
bad,
but
I
mean
we
don't
even
change
the
profiles
that
frequently
so
again
a
pretty
small
problem
anyway.
B
D
B
That
is
right,
so
we're
actually
extending
the
ability
of
profiles
to
be
in
more
locations,
because
currently
it
can't
live
under
court
and
we're
making
it
so
that
it
can
stay
where
it
is.
If
you
want
to,
or
it
can
be
under
core
and
they're
like
wait,
look
allah.
B
E
C
One
not
in
core,
it
still
takes
effect.
So
anyone
doing
this
upgrade
it
wouldn't
help.
Anyone
who
already
has
this
doesn't
help
anyone
who
has
already
upgraded
where
I
already
has
a
site,
because
when
we
do
move
it
in
the
core,
they'll
still
have
the
profile
in
the
old
directory
and
it'll
always
stay
there.
B
Yeah,
that's
true
and
we
could
potentially
go
some
cars
to
like
make
a
hook
requirements
to
like
say
hey.
You
should
delete
that
out
of
your
root
directory,
but
it's
such
a
small
issue.
We
might
just
like
put
it
in
the
release,
notes
and
just
say
you
know,
you
should
remove
that
if
you
have
it
there,
this.
B
That
says
this
package
was
zipped
up
and
then
compiled
by
backdrop,
CMS
Torg
and
by
no
other
server
on
the
entire
internet.
And
then,
when
a
backdrop,
your
local
install
downloads,
the
update
it
uses
a
public
key.
That
is
included
with
backdrop
core
itself
and
says.
Is
this
signature
valid
and
it
can
then
check
to
make
sure
that
that
archive
came
from
nowhere
else
other
than
a
package
from
backdrop
CMS
tow
org?
B
B
Sorry
I
should
have
started
with
that
is
issued
in
1992,
and
this
involves
a
number
of
moving
pieces,
including
project
module,
backup,
CMS,
org
and
a
backdrop
core
itself.
So
there's
a
pull
request
that
is
posted
to
backdrop
CMS
org.
That
makes
the
changes
to
all
three
of
those
places,
because
by
drop
CMS
torque
has
both
has
all
a
project,
module,
Drupal,
core
or
backdrop
court
and
the
backdrop
semester
or
modifications
itself.
So
that
combines
all
three
of
those
projects
into
a
single
Pro
request
in
a
proof
of
concept.
C
B
Is
built-in
in
newer
versions
of
PHP
and
has
backwards
compatibility
shim
for
older
versions?
John
Franklin
is
suggesting
that
we
use
open
SSL.
There's
also
PGP
would
also
work
for
signing,
so
there's
lots
of
different
options
there,
but
I
like
how
we
actually
do
the
signing
is
actually
just
kind
of
like,
like
the
only
outstanding
question,
the
infrastructure
around
how
to
actually
deal
with
the
signing
and
have
a
backdrop
core
itself
verify
the
signature.
That
will
be
the
same.
B
Regardless
of
what
algorithm
we
use
to
do
textual
signatures,
so
so
we're
making
some
really
great
progress
in
that.
That
is
that
area
and
then,
finally,
with
those
three
issues
once
they
get
out
of
the
way,
then
we
start
worrying
about
automatic
updates
themselves.
I
I,
don't
really
know
if
that's
even
a
realistic
thing
for
us
to
even
attempt
for
1.11
I
think
just
getting
those
infrastructure
pieces
in
place
here,
111
be
a
really
most
excellent
start.
B
Yeah,
we
haven't
even
gotten
to
how
the
user
interface
should
look
like
for
turning
on
automatic
updates
or
the
frequency
of
them.
We've
had
some
brainstorming
sessions
around
how
to
deal
with
like
only
update
security
updates
or
bug
fix,
release
only
or
contribute
score
updates.
But
all
of
those
questions
are
all
all
up
in
the
air
like
if
you
kind
of
feedback
on
on
that
or
user
interface
suggestions
right
now,
post
directly,
an
issue
20:18
I
guess:
I'll
take
a
break
here,
we're
only
halfway
through
the
1.11
there's,
so
many
things.
B
An
issue
792
that
pull
request
is
our
TBC,
but
not
yet.
I
get
merged
other
things
in
color
module
that
I
know
are
underway.
This
isn't
directly
color
module,
but
Joseph
has
worked
to
colorized
basis
to
make
it
so.
The
basis
can
now
be
configured
via
color
module,
which
is
a
really
great
user
improvement
for
for
out
of
box
experience
to
make
it
so
that
not
all
backdrops
need
to
look
identical
and
basis
has
got
like
a
nice
kind
of
generic.
B
B
B
Let's
see
oh
yeah,
also
Thank
You
Jennifer,
building
out
more
of
these
colored
module
issues.
We
also
recently
merged
issue
3153,
which
was
removing
the
image
handling
from
color
module,
which
I
know
it
seems
a
little
bit
strange,
but
it's
some
cruft
that
has
existed
in
color
module
since
Drupal
6
days
it
actually
hasn't
even
been
in
use
since
Drupal
6
that
previously
the
garland
theme
would
generate
images
to
handle
gradients
and
rounded
corners,
both
of
which
are
obsolete
concepts.
B
F
B
But
I
mean-
and
this
is
kind
of
a
good
thing-
I
mean
like
this
functionality
for
image,
generating
the
gradient
generating
like
we
haven't,
used
it
in
over
a
decade
in
backdrop
or
Drupal,
and
so
it's
no
wonder
it's
not
tested
because
nothing
was
actually
calling
it
so
yeah,
very
nice
keen
eyes
pulling
out
that
Crofton
and
just
getting
rid
of
it
really
appreciate
that.
Okay,
okay,
let's
keep
going-
oh,
my
goodness,
all
right,
adding
saved
draft
to
Kors
issue
1383.
B
D
D
Maybe
we
wouldn't
implement
that
in
backdrop
as
drop
buttons,
but
as
separate
buttons,
but
still
would
need
something
that
would
expose
the
publishing
functionality
out
of
the
vertical
tabs
and
into
closure
there's
a
big
buttons,
and
they
have
been
some
back
and
forth
between
this
issue
and
another
issue.
But
but
now
this
is
focused
on
doing
exactly
that,
adding
a
an
extra
button
that
is
conditionally
shown
only
when
when
it
makes
sense
and
that
all
the
rest
of
the
buttons
also
their
labels
reflect
what
is
actually
being
done.
D
B
D
B
Okay,
so
issued
1383
basically
needs
feedback
as
to
like
what
we
should
what
we
should
do
there.
We
should
start
mentioning
that
one
and
the
design
/ux
meetings,
Jen
I,
think
that
would
be
good.
Maybe
we
should
even
remove
it
from
this
because
that's
like
it's
an
open
question
for
UX,
rather
than
a
developer,
oriented
task
at
this
point
now
that
Wes
is
Berkeley's
a
great.
D
B
Let's
see
well,
this
ties
right
into
the
next
issue,
which
is
better
workflow
handling,
which
is
1475.
Oh
yeah.
This
is
very
similar,
isn't
it
yeah
I,
actually
even
wonder
about
like?
Maybe
we
should
combine
these
two,
because
this
is
the
same
sort
of
question
that
is
asking
is
also
about
workflow
states
and
content.
Saving
options
also
include
screenshots
from
WordPress.
A
A
First
until
we
yet
I
like
end
result
of
what
we
want
and
then
once
we
know
what
we
want,
we
can
make
a
bunch
of
smaller
issues
if
that's
gonna
be
easier
to
get
them
in
that
way.
But
I
feel
like
right
now,
because
we're
also
in
sort
of
needs
review
needs
to
be
back,
needs,
user
experience,
guidance
or
whatever
it
might
be.
Good
just
have
one
issue
where
we
can
talk
about
it,
all
figure
it
out.
A
D
D
Just
as
a
top-level
thing
is
Drupal
8
has
the
concept,
or
at
least
the
API
as
far
as
I
know,
of
more
clothes
or
states
in
court,
at
least
the
API.
We
are
not
there
yet
and
one
of
my
questions
when
the
publishing
thing
was
getting
into
for
was.
You
know,
schedule
publishing
why
not
scheduled
on
publishing,
but,
as
I
said,
we
try
to
keep
it,
keep
it
minimal,
so
maybe
the
workflows
in
core
same
as
v8
has
maybe
it's
not
such
a
good
thing.
D
B
D
Yeah,
it's
getting
save
draft
into
court,
just
exposing
the
published
checkbox,
making
it
a
button
or
what
have
you,
along
with
other,
submit
buttons
and
then
making
sure
that
it's
time
that
a
user
either
adds
new
contador
at
its
existing
coded,
everything
is
taking
out
the
entire
consideration
and
the
labels
of
the
buttons
actually
and
the
amount
of
buttons
which
buttons
are
available
makes
sense.
That's
so
there's
not
what
the
facts
you
know,
I.
B
B
In
summary,
this
issue
we
just
want
to
start
collecting
more
information
about
how
people
have
configured
their
backdrop
websites,
so
that
we
can
make
better
product
decisions
about
what
functionality
is
commonly
used
and
what
functional
is
not
commonly
used.
There's
been
some
great
updates
here,
we're
still
for
the
most
part.
Everybody
agrees.
We
need
to
start
collecting
more
information
about
how
people
are
using
backdrop.
It's
also
been
you
know,
an
interesting
topic
only
because
of
gdpr
I
think
that's
the
right
acronym
for
the
new
European
law
regarding
privacy
controls,
so
that
I
mean
I.
B
D
D
One
of
my
all-time
favorites
from
Vito
toward
because
they
were
the
the
community
there
was
larger
and
especially
with
with
tickets,
that
would
affect
a
big
chunk
of
the
of
the
community
or
of
the
site's.
There
were
a
lot
of
conflicting
opinions
and
everybody
was,
you
know,
fighting
over.
What
is
the
80/20
the
same
thing?
If
we
have
raw
data
to
back
everything
up
and
we
would
avoid
so
many
parts,
shading
things
no.
B
A
Was
like
three
or
four
weeks
ago,
but
I
reread
the
issue
since
then,
and
it
I
forgot
how
complicated
it
was
in
terms
of
we
need
to
give
people
away
to
opt
out
and
like
clean
up
our
terminology
around
what
the
button
says
so
that
they
know
what
they're
asking
and
how
to
that's
separate
from
update
checking
to
think
we
do
already.
But
then
we
also
need
to
figure
out
what
data
we
want
to
collect.
A
We
need
to
figure
out
how
to
collect
it
on
the
back
drop
site,
size
and
figure
out
how
to
submit
it,
and
then
we
need
to
figure
out
how
to
measure
it
on
the
project
module
side
as
well,
so
there's
a
whole
bunch
of
moving
pieces
like
every
time.
You
add
a
new
thing
that
we
want
to
track.
We
must
have
to
track
it
on
the
sites
that
are
running,
and
then
we
have
to
record
it
on
the
server
that.
C
A
E
D
Maybe
not
only
other
is
it
in
the
installer
and
I'm
not
saying
that
it
should
be
because
we
should
it
should
be.
We
should
simplify
the
installer.
All
I'm
saying
is
maybe
a
message
like
the
new
informations,
the
thing
that
I've
added
that
says
we
are
collecting
data,
though
the
same
way
that
the
browser's
do
it
I,
don't
find
it
intrusive,
like
even
when
you
install
Chrome,
for
example,
it
says
that
we
are
collecting
our
name.
Is
data.
Please
see
what
that
is
being
collected.
D
Yeah
I,
don't
think
that
anybody
finds
this
intrusive
and
so
long
as
this
is
like,
if
we
could
have
been
implemented
on
our
dismissible
message
with
the
next
button
that
shows
up
there
and
says
hey,
we
are
collecting
data,
here's
what
we
are
collecting
click
here
and
if
the
people
know
about
it,
they
just
click
on
next
button
and
then
that
thing
never
shows
the
bottom
again.
That's
it
right.
B
So
during
the
installer
we
ask
two
questions
like
allow
the
site
to
send
me
email
when
there
are
updates
and
check
for
updates
automatically
yeah
I
think.
Actually,
what
we
should
do
is
this
possibly
opinionated
and
controversial.
We
should
remove
the
check
for
updates.
We
should
always
be
checking
for
updates,
but
we
renamed
that
change
changed
the
thing
to
send
anonymous
data,
and
so
we
should
decouple
checking
from
updates
for
sent
from
sending
data.
B
D
E
C
E
C
Haven't
really
even
gotten
this
or
an
e-commerce?
Yes,
I
can
only
have
a
commerce
module
and
stuff
like
that,
but
once
we
do
what
are
going
to
be
the
the
requirements
around
that
data,
whether
it
can
just
like
report
back
to
some
odd
certain
site,
yeah
I,
don't
know
I
I,
don't
know
the
legal
rules
are
made
with
the
PCI
compliance
rules.
I,
don't.
G
B
It
said
we're
not
going
to
record
even
just
the
update
you
exactly
like
checking
the
update
feeds
shouldn't
record
anything
that
should
separately
be
reported
as
anonymous
data
that
is
sent
in
a
separate
task,
and
then
it
actually
makes
it
so
that
we
can
cache
the
update
feeds,
because,
right
now,
when
you
check
for
updates,
it
has
to
record
information
the
fact
that
that
update
was
requested.
So
it
actually
would
be
a
double
win.
Okay,
increasing
the
cache
ability
to
update
feeds
and
sending
data
separately.
That.
C
A
C
E
D
B
D
A
B
Actually
would
be
a
good
thing
to
separate
entirely
from
this
retrieving
information,
because
it's
like
we
could
build
out
just
sending
the
anonymous
information
to
a
new
API
like
that,
doesn't
include
any
additional
data
collection,
like
separately
from
the
data
collection,
so
that
would
be
good.
Okay,.
B
A
B
So
anyway,
they're
still
updates
to
be
had
and
other
issues
for
1.11
that
are
not
mentioned
its
meaning
check
out
the
one
point
in
eleven
milestone:
okay,
I
think
with
the
Jeff
not
being
present.
Let's
go
to
general
discussion
and
Q&A
and
I
actually
only
got
a
couple
minutes
before
we
two
o'clock,
though
so
anything
you
guys
would
like
to
add
or
discuss.
B
Okay,
we
wore
ourselves
out
talking
about
statistics,
tracking,
okay,
all
right
well,
thank
you,
everybody
for
joining
the
meeting
today.
Thank
you
for
all
the
dogs
that
are
present
and
walking
around
in
people's
backgrounds,
and
thank
you
as
always
to
our
viewers
that
watch
these
means
to
keep
up
to
date
on
the
latest
impact
drop.
Thanks
again
and
we'll
talk
to
you
guys
next
week,.