►
From YouTube: Backdrop Weekly - July 5th
Description
Today’s development agenda: http://bit.ly/2Kg5W7T
A
Right
we're
on
air.
It
is
a
Thursday
July,
fit
happy.
Fourth
of
July
everybody.
This
meeting
is
a
check-in
on
active
development
tasks
for
backup
CMS.
Before
we
get
into
active
tasks,
I
did
want
to
announce.
There
are
two
new
contributed
projects
for
backdrop.
The
first
is
the
L,
a
kiss
matched
module,
which
is
the
spam
prevention
tool
for
WordPress.
It's
a
subscription
service.
It's
you
know
anyone
can
use
it.
So
there's
been
a
Drupal
module
for
a
while
another
to
backtrack
model.
A
So
if
you
have
been
experiencing
an
increase
in
spam
on
your
site
and
you're
looking
for
another
solution,
this
is
another
good
product.
That's
out
there
and
then
another
module
that
was
created
is
one
called
env
metadata
wrapper.
So
if
you
really
miss
the
end
of
the
metadata
wrappers
2007
and
want
to
use
them
as
backdrop
there's
now,
I
can
dream
a
goal
that
can
give
you
your
layers
of
abstraction
back.
B
B
A
I
don't
know
I
I
hate
energy,
maybe
the
wrapper
so
I
probably
won't
be
using
I
think
of
myself,
but
if
you
need
it,
okay,
if
you
run
in
that
problem,
need
to
file
or
replace
yeah.
C
B
A
So
yeah
it
sounds
like
there's.
Definitely
a
developer
experience
improvement
necessary
for
vector
core
so
that
we
can
give
that
same
feature
to
developers
to
be
able
to
get
access
to
their
only
did
whatever
I
don't
know
what
that's
gonna
look
like
in
background
and
wonderful,
something
it
was
yeah
and
it
even
be.
The
wrappers
definitely
went
to
improvement
there.
C
Sure,
okay,
okay,
so
what
we've
got
going
on
here?
Let's
see
we
usually
talk
about.
Oh
hang
on
I'm
on
the
wrong
agenda.
We
usually
talk
about
the
latest
bug
fix
release
first,
and
that
is
the
next
version
is
one
but
10.2.
We
did
have
a
couple
of
more
issues
that
were
merged
that's
past
week,
which
is
great,
so
we're
seeing
some
kind
of
some
continuous
improvements.
C
If,
if
we're
using
a
workaround
to
connect
to
the
database,
that
we
expose
that
to
the
user
is
a
big
problem
in
their
status
report,
there's
a
bunch
of
other
issues
that
are
flagged
for
one,
that
10.2
I
check
the
issue.
Tracker
usually
they're,
flagged
as
being
in
the
next
bug
fix
release
because
they're
close
to
completion,
and
so,
if
you're,
looking
for
issues
to
review
that
are
likely
to
be
completed
on
a
very
short
timeline.
Checking
out
the
issue.
Tracker
for
1.10
up
to
milestone
is
a
great
way
to
find
issues
that
need
reviewing.
C
C
At
this
point,
we've
merged
in
three
or
so
of
those
contact
module
improvements,
but
just
take
a
look
at
issue,
30
23,
to
take
a
look
at
those
other
issues
that
are
still
in
progress,
things
like
adding
a
contact,
module
block
or
enabling
contact
module
in
default
profile
or
what
was
the
other
one
Oh,
adding
a
menu
item
for
contact
module,
Winn
contacts
or
when
the
module
is
turned
on
things
of
that
nature?
So
please
take
a
look
at
the
meta
in
post
feedback
on
each
one
of
those
issues
that
is
not
yet
been
completed.
C
Next
up
is
color
module
improvements.
There's
another
metaphor.
This
one
at
1905
and
Joseph
has
been
doing
a
lot
of
work
on
color
module
improvements,
most
notably
issued
31
86,
which
is
improvements
to
the
way
that
the
color
Pickers
work.
When
you
are
configuring
a
theme,
this
was
separated
out
into
a
dedicated
issue
just
this
past
week,
which
is
very
helpful.
It
has
a
pull
request
that
currently
needs
needs
review
functionally.
It
looks
like
it's
fairly
complete,
but
there
hasn't
been.
There
hasn't
been
a
lot
of
feedback
posted
other
than
wow.
C
D
C
C
Yeah
I
think
Wes
had
a
suggestion
in
there
at
one
point
about
somehow
in
the
iframe.
You
can
somehow
scale
the
entire
you
port
and
the
iframe.
Is
that
still
possible
with
us,
or
is
that
just
like
a
crazy
idea
that
didn't
actually
work?
No
I've
done
it
before
it
works.
It
is
a
little
crazy.
Oh
yeah,
I.
D
B
C
Interesting
I
wonder:
I
might
not
be
the
only
person
to
speak
on
this
particular
behavior,
but
I
wonder
if
it
might
be
preferable
to
have
the
preview
be
a
fixed
size
so
that
the
UI
is
predictable,
but
then
have
like
a
pop-out
button
that
opens
it
in
a
new
window
so
that
you
can
see
the
entire
site
in
the
new
theme
like
as
a
full
window.
Instead
of
as
part
of
the
page.
D
C
D
C
Anyway,
this
is
exactly
why
we
need
a
code
review,
but
that
looks
that
mean
it
looks
like
it
looks
like
it
works.
Oh
yeah.
E
D
C
B
E
It's
interesting
that
was
looking
like
up
last
couple
of
weeks:
visual
regression
tests
how
they
have
a
slider,
but
you
you
know
they
have.
You
have
two
versions
of
a
same
screenshot
of
our
side
and
then
you
have
a
slider
that
makes
you
see
that
overlay
of
that,
whatever
regression
was
there
and
then
I
started
looking
at
similar
patterns
for
UI,
where
you
could
sort
of
like
have
the
preview.
Sorry,
the
controls
that
change
the
colors
I'll
do
whatever
you
want
with
the
theme
preview,
and
then
you
have
the
preview
at
the
background.
E
Somehow,
as
a
like
second
layer
and
the
courses
that
I
could
find
was
a
hell.
Wordpress
works
the
thing
customization,
so
I'll
post
a
link
in
Gator
as
well
with
the
lip,
the
video,
the
demo
that
I
was
taking
WordPress
Oh
course.
If
maybe
you
wanna
take
a
look
at
that
for
ideas.
C
E
Sure
so,
first
of
all,
I'm
doing
that
on
behalf
of
Doc
Wilma,
who
has
done
an
amazing
job
and
various
iterations
on
it,
fixing
small
things
that
I
was
pointing
out
and
all
these
as
well.
So
the
first
iteration
of
this
included
a
new
ribbon
that
was
introduced
at
the
top
of
the
basis
thing
which
had
controls
for
switching
display
modes
and
saving
the
preview
without
having
to
return
back
to
the
edit
mode.
To
do
that.
E
The
main
concern
there
was
that
this
ribbon
was
at
the
top
of
the
page,
was
being
run
at
the
top
of
the
page.
So
if
one
ended
into
preview
mode
and
then
scrawled
at
the
bottom
of
the
page,
if
the
page
was
long
enough,
then
they
would
have
to
scroll
back
up
in
order
to
save
so
the
suggestion
there
was
that
we
should
put
this
ribbon
at
the
bottom
of
their
height
and
perhaps
make
it
sticky,
and
this
was
a
pattern
that
was
suggested
in
other
issues.
E
E
So
if
there
are
contributors
that
are
in
and
hansung
or
changing
the
forms
in
the
admin
UI,
this
is
not
reflected
when
you're
doing
the
preview.
So,
for
example,
save
as
draft
adds
a
new
button,
and
this
is
on
the
form
on
the
normal
admin
interface.
But
when
you
click
preview,
this
button,
the
say
first
draft
gets
lost,
so
you
only
keep
the
default
save
or
return
back
to
edit
mode.
E
There
was
a
discussion
in
the
previous
meeting.
The
design
meeting
that,
because
we
are
styling
this
ribbon,
to
look
to
resemble
the
admin
UI
just
to
differentiate
of
what.
What
part
is
the
actual
preview
of
the
side
and
what
part
of
controls
for
saving
and
changes,
and
we
have
styled
it
as
I
said,
as
look
as
the
admin
in,
but
this
is
now
part
of
the
whole
page.
E
So
this
is
different
CSS
and
the
concern
there
is
that
its
theme
would
need
to
implement
or
add
the
CSS,
and
it
won't
look
as
good,
so
Wes
suggested
that
perhaps
the
the
preview
bit
of
the
actual
front-end
thing
should
be
on
its
own
iframe
sort
of
sort
of
like
isolated
or
sandbox.
It
I
think
that
if
we
did
do
that,
we
might
be
able
to
also
use
the
the
submit
buttons
as
they
are
from
the
actual.
C
Okay,
yeah
good
ideas
that
makes
it
almost
like
a
it's
like.
The
reverse
problem
of
CK,
editor
or
CK.
Editor
has
to
load
a
stylesheet
from
the
front
end
team
in
the
admin
team,
and
this
is
like
the
opposite
problem,
where
we
need
an
admin
stylesheet
on
the
front
end
essentially
and
yeah.
Ck
editor
has
the
advantage
of
using
an
iframe.
So
it's
a
good
nobody
there,
okay
yeah
great.
So
it
sounds
like
like
we're
stuck
on
almost
like
design
and
UX
issues,
which
isn't
surprising.
B
C
Okay,
next
up
is
automatic
updates,
which
is
a
you
know,
an
issue
that
is
taking
up
a
lot
of
mental
space
in
the
Drupal
world
and
in
the
backdrop
world
at
the
moment-
and
we
have
a
big
meta
issue
for
that
at
2018,
and
we've
got
a
couple
of
sub
issues
for
tackling
these.
These
problems.
Sorry
Mike!
Is
there
something
you
want
to
add?
C
Okay,
sorry,
okay.
So
some
of
these
sub
issues
that
are
in
progress
include
issue
3105,
which
is
allowing
cor
to
you
updates
via
the
user
interface.
The
status
on
this
one
is
still
needs
review.
It's
a
little
bit
of
a
tricky
one
to
actually
do
testing
on,
because
it's
difficult
to
actually
do
the
testing
of
something
that
doesn't
actually
have
new
updates
available.
Yet
I
think
there's
still
the
outstanding
problem
regarding
authorized.
Dot.
Php
doesn't
work
with
the
combination
of
doing
a
core
update,
and
so
this
probably
actually
needs
to
be
bumped.
C
C
Next
up
that
we've
got
is
issue
1992,
which
is
an
issue
to
improve
the
security
of
downloaded
packages.
A
issue
is
a
meta
or
as
a
as
a
feature
request
that
works
to
add
package
signing
as
well
as
md5
hash
validation
needs
work
on
that
one.
We've
got
some
progress,
moving
forward
on
project
module,
backup,
CMS,
org
and
backdrop
core
itself,
all
three
of
which
need
to
be
updated
in
order
to
make
that
happen
and
there's
some
prototype
work
that
is
pushing
that
forward.
C
C
And
lastly,
and
the
core
updates
issues
is
issue
2555,
which
is
an
issue
regarding
the
profiles
directory
that
the
profiles
director
should
be
moved
under
the
core
directory,
like
all
other
core
files,
so
that
when
core
is
automatically
updated
or
updated
via
the
user
interface,
the
profiles
directory
also
gets
updated
status
or
that
one
still
needs
review.
I.
Think
that
we're
all
on
the
same
page
regarding
implementation
there.
So
if
anyone
gets
chance
to
do
a
little
bit
of
further
testing
on
that
one,
that
would
be
appreciated.
C
C
Let's
see,
we've
got
issue
20
or
285,
which
is
better
statistics,
tracking,
better
statistics
tracking.
We
separated
out
into
a
new
issue
at
31
68
for
initial
work.
We
can
go
ahead
and
start
solving
this
technical
problem,
which
is
merely
that
we
want
to
separate
out
the
sending
of
anonymous
statistics
to
backdrop
CMS
dorg
from
the
checking
of
updates,
so
your
site
can
continue
getting
information
about
updates
and
downloading
updates
without
sending
information
to
backup,
CMS
org
about
what
versions
and
modules
you're
running.
C
So
that
issue
is
a
technical
one,
that
we
can
start
on
right
away
and
that's
3168,
and
then
the
parent
issue
of
all
of
this
is
285,
which
is
the
issue
in
which
we're
trying
to
determine
what
information
we
should
actually
be
collecting
like
what
anonymous
information
we
should
actually
collect
from
the
sites
that
send
this
anonymous
in
from
to
us.
So,
okay,.
B
E
C
It's
a
great
a
great
idea:
I
didn't
realize!
That's
why
you
added
that
new
tag,
but
that
makes
a
lot
of
sense.
So
that
way
we
know
we
can
do
a
combination
where
we
can
put
a
big
long
list
of
things
that
we
think
need
to
be
collected
into
285,
but
all
our
cart
as
we
encounter
issues
that
also
should
be
sending
information
to
backup
CMS
tart,
or
we
can
just
add
that
tag.
So
we
can
kind
of
in-depth
reference
for
the
why
we
need
particular
data
collection.
It.
E
Could
be
closed
tickets
as
well?
So
if
there's
any
anyone
that
believes
that
we
have
defaulted
a
certain
setting
into
something
that
should
not
be
the
default
just
go
to
that
closed
ticket
and
target
with
needs,
use
its
message
matrix
so
that
maybe
in
the
future
we
can
change
the
defaults,
if
maybe
maybe
we're
being
wrong,
and
most
people
not
use
that
yeah.
C
Mr.
Tuesday,
at
the
minor
version
of
Joomla,
the
PHP
version
and
the
operating
system
that
they're
running,
which
you
know
that
would
be
huge
like
if
we
knew
what
version
of
PHP
people
were
running.
That
would
let
us
make
a
lot
of
decisions,
so
yeah
really
great
information.
Any
comments
there
like
we're.
Still,
you
know
we
haven't
made
any
traction
on
technical,
fomentation,
they're
kind
of
looking
for
a
champion
to
to
take
that
on.
So
if
anyone
is
interested
in
I'm,
you
know
it's
a
little
bit
exciting.
C
Let's
see
two
other
issues
that
I'll
just
throw
out
there,
but
not
recap,
because
we
just
talked
about
them
during
the
design
meeting
an
hour
ago
include
issue
28
87.
That
is
automatically
rotating
images
when
they're
uploaded,
based
on
the
EXIF
data
and
issue
37,
which
is
an
improvement
to
the
modules
listing
page
to
allow
for
tagging
of
modules,
in
addition,
or
possibly
instead
of
categories,
so
both
of
those
who
are
discussed
during
the
design
meeting.
So
we
won't
recap
them
again
here
or
you
can
just
take
a
look
at
those
individual
issues
on
github.
E
About
37
I
think
that
dock
will
would
was
actually
because
he's
not
present
he's
looking
at
the
videos
after
the
fact,
so
he
is
actually
looking
for
direction
and
input.
If
we
could
at
least
know
if
we
can
come
come
up
with
a
consensus,
it
doesn't
have
to
be
this
meeting,
but
in
in
a
meeting
then
he
he
will
know
what
to
work
on
or.
A
C
E
Not
so
much
features
I
would
like
to
bring
up
an
old
ticket
that
sort
of
came
up
and
that
one
is
27
89.
It's
a
meta
issue
and
it
says,
stay
on
top
of
contributor
updates,
so
yeah
recently
there
was
some
discussions
about
features
that
exist
in
the
file
entity,
module
that
people
would
expect
to
be
in
core,
because
that's
what
we
are
listing
in
one
of
our
slides
as
well.
E
But
there's
things
like
I
think
that
from
what
I've
heard,
the
same
thing
happened
with
c2,
so
so
part
of
arizim
core,
but
not
so
I've
thought
of
a
way
that
we
could
keep
up
with
these
updates.
It
will
take
some
manual
work
from
some
people,
I
volunteered
to
dedicate
some
time
for
that.
But
we
need
to
be
aware
of
module
updates,
so
my
thought
was
to
set
up
a
Drupal
installation
instance.
E
C
And
Gregory
another-
you
just
reminded
me
of
another
issue,
and
that
is
I.
Don't
have
the
number
for
it,
but
we
mentioned
it
last
week
and
that
is
the
the
file
browser
allowing
the
file
to
be
reused.
When
you
insert
an
image
into
the
rich
text,
editor
and
I
wish
that
I
had
that
issue,
because
there's
still
continuous
progress
happening
in
that
issue.
C
Right
so
I
don't
have
the
number
on
hand,
but
let's
add
it
to
the
agenda
for
next
week.
I
know
that
we
keep
having
it
all
occurred,
but
keep
forgetting
to
put
it
in
the
template.
So
I
apologize
to
those
that
are
working
on
that
issue
still
doing
a
great
job,
and
there
is
an
issue,
the
image
that
that
work
is
happening
and
it's
coming
on
really
strong
light.
But
I
don't
have
the
number
you're
for
reference.
E
C
Anything
else,
folks,
okay,
we've
got
a
lot
of
really
exciting
things
happening.
I
know
we
were
worried.
Just
did
you
know
made
to
release
cycle
2
moments
and
it
feels
like
we've.
All
I
got
tons
of
time,
because
it's
the
summer
sort
of
feels
like
for
me
made
me
not
those
of
you
that
are
in
Australia,
but.