►
From YouTube: Backdrop Weekly - Aug 2nd
Description
Today’s development agenda: http://bit.ly/2LvwgLS
A
Maybe,
okay,
all
right.
We
are
on
air,
it
is
Thursday,
August
2nd,
and
this
is
a
check-in
meeting
for
backup,
CMOS
development
tasks.
According
to
our
agenda,
we
were
supposed
to
think
new
members
of
our
community.
You
guys
might
have
knows,
there's
been
a
lot
of
activity
in
both
the
chlorine
contribute.
Last
week
in
particular,
we
have
two
new
maintainer
applications
from
cases
and
having
cracks
and
they're
currently
working
on
porting,
a
bunch
of
modules
overcome
through
posts,
there's
also
a
bunch
of
new
intensive
support
and
port
status
issues.
A
If
you
think
it's
pretty
tight,
don't
thanks
guys
for
all
the
work
on
that
where
we
work
on
getting
noticed,
move
forward.
Also,
in
the
world
of
putrid,
there
has
been
busy
among
other
people.
We
have
new
modules
formats
redirect
select
their
other
structured
data
mail
log,
slash
mail
developer,
that
of
augmentin
last
week,
so
I
think
everybody
was
been
working
on.
It
does
not
lessen.
Thank
you
answer
a
bunch
of
intensive
works
in
the
country
as
well.
All
right,
I'm,
gonna
turn
over
nate
talk
about
project.
B
C
Alright,
so
we
always
go
over
the
current
release,
which
is
1.10
first,
and
we
still
have
one
outstanding
issue
that
needs
to
be
addressed
regarding
database
credentials
need
to
be
URL
encoded.
Now
that
still
fiddling
around
is
something
that
needs
needs
some
additional
work,
it's
not
a
bug
unless
it's
like
really
a
bug
on
your
site.
C
So
it's
like
it's
a
problem
that
has
started
since
1.9
if
you're
upgrading
from
reversion
a
backdoor
prior
to
that-
and
you
add-
percent
symbols
in
your
database
credentials,
your
site
might
not
update
correctly
until
you
update
those
that
setting
and
setting
some
PHP.
So
we
would
just
like
to
make
it
so
those
upgrading
and
new
installations,
where
people
3%
symbols
in
the
passwords
get
notified
of
the
particular
problem
of
why
their
credentials
might
be
wrong.
C
So
that's
still,
we
have
a
workaround
in
place,
but
we
need
to
expose
the
workaround
in
establish
rapport,
so
it
still
means
work
as
it
has
needed
for
quite
some
time.
There's
other
issues
that
are
tagged
for
1.10
as
well.
I,
don't
think
I
have
any
a
particular
call-out,
though
at
least
aren't
in
the
agenda.
Do
you
guys
have
any
that
you
run
across
for
1.10
bug
fixes
that
that
are
pending?
C
No
okay?
We
also
have
a
number
of
fixes
that
are
actually
already
in
1.10.
We
don't
have
any
little
timeline
for
one
by
10.22.
Usually
you
know
when
we
accrue
enough
blood
fix
issues.
Something
is
important
in
that
than
when
they
connects
release,
probably
after
we
get
that
darn
URL
and
coded
database
credentials
thanks.
C
Okay.
So
let's
talk
about
1.11
when
911
is
the
next
release
that
will
be
coming
out:
September,
15,
2008,
teen
and
there's
a
number
of
large
features
that
are
being
worked
on
for
for
the
1.11,
at
least
it's
putting
into
the
agenda
that
code
freezes
September
1st,
so,
oh,
so
you
can
which
it
is
now
August,
which
means
that
we
have
this
month
to
wrap
up
the
features
that
will
be
in
1.11
and
then
starting
September
1st,
that's
the
start
of
feature
freeze
where
we
no
longer
add
new
functionality.
B
C
Although
really
the
way
things
usually
work,
as
things
are
supposed
to
be
stable,
even
at
the
time
that
they
have
merged
them
in
the
first
place,
but
that
gives
us
two
weeks
to
basically
do
some
testing
and
get
any
problems
that
are
discovered
in
worked
out.
So,
let's
go
over
some
things:
contact
module
contact
module
has
been
spearheaded
by
Opie.
The
meta
issue
is
3023
and
there's
a
number
of
things
that
have
been
really
moved
forward
in
this
past
week.
C
Thanks
to
excellent
work
of
community
members,
we've
got
issue
2872
that
improves
the
recipients
field
in
the
contact
category
form
32:15
that
provides
better
messaging
on
the
contact
categories,
32:16
that
the
recipients
should
be
rendered
as
a
list
and
32:17
that
were
just
adding
a
cancel
link
to
the
configuration
form.
So
the
last
three
of
those
you
know
is
probably
sequentially
noted
sequentially
numbered
UX
issues
that
were
all
created
and
solved
all
of
us
last
week.
All
of
those
are
our
TVC
and
so
we'll
be
getting
through
those
shortly.
D
The
kind
of
issues
that
I
like
it's
like
those
tiny
changes
like
even
like
ten
lines
of
code
or
even
one
line
of
code
that
actually
fix
problems
that
you
know
it's
annoying
things,
so
that
meta
is
not
even
like.
We
least
here
four
issues,
but
it's
like
more
like
a
dozen
of
them
and
there's
a
lot
of
them.
That
I'd
like
to
see
I
think
we
have
this.
C
Yeah,
those
are
just
the
new
ones
this
week
there's
a
number
of
other
items
inside
of
that
meta,
some
of
which
have
been
fixed.
You
know
over
the
past
couple
of
months
and
some
that
are
in
progress
that
could
still
easily
be
done
in
the
next
month,
so
the
contact
module
really
getting
some
really
great
TLC.
For
this
release
we
connect
to
each
other
okay,
so
also
in
the
modules
that
are
going
to
you'll,
see.
E
C
C
C
We
have
a
follow-up
issue
in
that,
so
the
meta
is
1905
to
make
it
so
that
we
ship
with
some
out
of
box
color
schemes
as
well
for
basis,
because
even
though
it's
color
izybelle
end-users
left
to
their
own
devices
tend
to
make
really
pretty
horrific
color
schemes,
so
the
big
game
provides
them
to
the
defaults.
Yeah
I
mean
I've,
seen
a
fair
number
of
Drupal
sites.
In
my
day
that
are
just
like
Arctic,
the
purple
version
you.
A
C
D
A
C
Know
this
is
almost
become
an
ancient
backdrop
history
at
this
point,
but
we
actually
already
revamped
all
of
the
color
schemes
that
are
out
of
the
box.
We
did
that
two
years
ago
for
Bartok
subarctic,
s--
out
of
the
box.
Color
themes
are
totally
different
than
the
ones
for
Drupal,
because
the
purple
ones
were
dated
and
nothing.
C
C
C
C
C
B
C
C
A
D
We
do
that
yeah.
Can
we
file
a
follow-up
ticket
like
let
us
not
hold
back
that
ticket
and
then
file
a
follow-up
like?
Would
that
ticket
fly
without
the
addition
of
the
new
library
only
with
fantastic,
and
then
we
file
a
follow-up
ticket
of
whether
to
add
for
replies
fantastic
with
that
one,
so
we
don't
hold
it.
Ups.
Will.
E
E
C
B
A
C
E
C
C
D
Biggest
problem
with
that
is
not
the
styling
or
styling
we
can
fix.
Oh,
we
can
decide
later
on.
My
biggest
concern
is
that
modules
that
actually
complement
the
submit
button
section
like
the
save
draft
module
that
adds
buttons,
so
the
the
ribbon
that
we
add
when
we
are
previewing
if,
for
example,
saved
our
key
installed,
it's
it's
buttons
are
not
present
there
anymore.
So
we
have
a
separate
thing
that
is
going
on.
D
That
is
being
read
there,
just
with
the
submit
button
with
the
Save
Changes,
whatever
button,
but
if
now
we
have
this
use
case
of
save
draft
that
we
think
of
adding
Interpol,
but
there
might
be
other
modules
that
interact
with
that.
So
my
point
was:
if
we
can
make
it
so
that
this
is
not
a
separate,
the
ribbon
is
not
a
sacred
thing,
but
it's
actually
the
actual
submit
section
of
the
Edit
form.
C
C
A
A
C
Okay.
So
the
next
issue
is
automatic
updates
or
just
generally
core
updates,
which
is
issue
2018,
there's
a
bunch
of
subbatches
here,
some
most
of
which
actually
haven't
received
a
whole
lot
of
attention
recently,
the
one
that
is
personal,
it's
serious
issue
3105,
which
is
making
it
so
that
cork
and
update,
sell
the
adhesive
interface
and
it's
problem
currently,
is
that
it
doesn't
work
with
the
authorized
HP
file.
C
That,
if
backdrop
doesn't
have
permissions
to
write
to
the
file
system,
if
it
stops
right
in
the
middle
of
the
update
to
go
and
ask
for
permissions
like
it,
it's
in
this
bad
place,
where
it's
like
trying
to
write
the
files
but
authorize
that
PHP
gets
injected
into
the
process,
and
then
it
does.
It
does
March
right.
Quite
don't
really
sure
why.
C
But
the
question
that
we
have
that
we
raised
in
this
past
week
is
a
sub
issue
of
this
now
3208,
which
is
removing
authorized
PHP
entirely,
which
may
seem
you
know,
although
the
experience
that
were
like.
Oh,
this
thing
that
has
been
in
drupal
forever
suddenly
doesn't
work
for
one
of
our
things
so
we'll
just
remove
it
rather
than
fix
it.
But
the
thought
process
there
is
that
authorized
dot.
C
Php
is
kind
of
fundamentally
incompatible
with
the
idea
of
automatic
updates,
because
an
automatic
update
means
that
the
user
is
not
actually
involved
and
so
authorized
dot.
Php
concept
is
that
when
you
update
a
module,
you
enter
in
your
FTP
credentials,
your
username
and
password,
and
then
back
drop
temporarily
switches
to
that
users
credentials
to
write
the
files
to
disk
and
then
switches
back
afterwards
and
forgets
the
username
and
password,
and
so
it
makes
it
so
that
it
writes
the
files
as
that,
other
user
instead
of
as
the
web
user.
A
C
Those
credentials-
and
we
certainly
would
not
want
to
try
to
store
users
credentials.
So
the
idea
is
in
3208
that
I'm
soliciting
or
asking
for
feedback
if
people
have
never
used
authorized.
Thb
I
also
asked
on
Twitter.
Most
people
didn't
know
that
it
existed
or
what
the
heck
it
did
or
anything
like
the
idea.
Well,
most
people
didn't
update
via
the
user
interface
in
the
first
place,
because
they're
drupal
users,
but
even
those
that
did
didn't,
encounter
authorized
whp
because,
if
you're
on
the
shared
host
web
user.
C
C
Know
and
so
there's
some
questions
around
that,
oh
and
lastly,
we
don't
use
authorized
PHP
for
the
project
installer
right
now
either,
and
so
the
project
installer
also
doesn't
work
unless
the
web
user
and
the
FTP
is,
there
are
the
same
person.
So
basically,
it's
like
it's
between
it's
like
not
fully
implemented
right
now
and
it's
fundamentally
not
compatible
with
where
we're
going.
Should
we
just
remove
it
entirely,
so
you
could
not
being
used
even
in
the
manual
installation
thing
it's.
It
is
no,
it's
only
being!
Oh!
Yes,
yes,
yes,
sorry
URL.
C
D
Other
the
other
place
that
I
often
seem
that
dialogue
was
simply
testing
at
some
point.
I,
don't
think
it's.
It
has
gone
through
various
like
maintenance
places
and
at
some
point
you
couldn't
install
modules
via
the
URL
thing.
It
was
asking
you
for
a
specific
credentials,
and
that
was
only
for
the
d7
version,
but
for
the
VA
there's
a
bit
funny,
but
I
haven't
used
it
in
a
while
I
mean
I
used
since
it
test
me.
But
not.
C
So
anyway,
we
saw
same
feedback
there.
It
seems
like,
for
the
most
part,
people
are
in
the
like.
Let's
just
remove
it
camp,
it
is
going
to
be
a
little
bit
strange
because
this
will
basically
put
backdrop
100%
at
odds
against
the
recommended
permission
setup
for
Drupal,
which
I
was
reading
over
the
permissions
page
for
Drupal,
like
how
does
that
your
file
permissions
for
Drupal,
which
is
an
extraordinarily
long,
read
and
permissions.
F
C
F
F
C
C
D
C
A
C
C
Sorry
that
I
haven't
responded
yet
to
do
it
so
there's
that,
so
that
is
still
an
option
that
we
could.
When
we
do
our
signing
of
our
packages,
we
could
use
open
SSL
instead
of
sodium
I.
Don't
think
that
you've
really
made
any
further
progress,
I'm
deciding
which
way
to
go
since
Jon
close
to
that
comment,
I.
D
A
Important
for
automatic
updates
and
is
a
good
idea
for
all
of
that
dates.
We're
doing
now
as
well,
so
I
think
I,
don't
know
if
it's
a
blocker
for
getting
the
manual
Update
button,
but
it
would
be
a
block
of
for
automatic
there.
Enough
also
minute
we
should
think
about,
although
it
doesn't
necessarily
need
to
be
done
by
September,
1st
I
would
say
we
should
focus
on
the
manual
button,
see
if
we
can
get
that
in
by
September
person,
and
this
can
come
either
shortly
thereafter
or
before
they
get
automatic
updates
in
yeah.
C
Sorry
Mike
sure
looks
like
a
funny
thing
here.
Is
that
he's
been
doing
some
perfect
concept
code,
but
it's
not
complete
yet
so
he
expected
to
bid
on
a
thousand
lines
roughly
when
he
gets
it
all
implemented
and
I
will
see.
Okay,
okay,
let's
move
on
now
somewhat
yeah.
We've
got
some
other
areas
that
we're
moving
forward
on
then
automatic
updates
I
do
think
God
removing
authors,
dot.
C
C
D
C
C
C
Okay,
yeah
follow
up,
follow
up,
I,
think
that's
what
I
just
decided
this
guy
okay,
more
issues
that
are
on
the
hit
list
for
1.11
tags
for
modules.
This
is
an
improvement
to
the
modules
page
I'm,
not
going
to
recap
this
one,
because
between
going
on
for
a
while,
maybe
updates
on
it,
that's
issue
number
37.
C
C
Media
issue
is
31
34,
which
is
the
ability
to
upload
a
file
directly
into
a
rich
text
editor
and
the
status
of
that
one.
Wait.
That's
not!
Oh
sorry
that
one
sorry
I'm
confusing
these
issues.
We
already
have
the
ability
to
upload
a
file
directly
into
the
road
stuck
to
the
outside.
Again
one
does
have.
C
C
To
the
insert
image
dialog,
which
is
quite
a
bit
more
ambitious,
and
that
one
also
it
might
needs
work
right
now,
but
it
really
kind
of
more
needs
review.
I
think
the
only
complaint
that
we
have
right
now
is
around
aesthetics
again,
like
the
image
browser
doesn't
have
enough
room.
Is
that
right,
Gregory
sort.
D
Of
that
so
there's
two
buttons
that
toggle
the
library
on
and
off
and
then
when
you
use
that
the
dialog
just
jumps
to
the
left
of
the
right
of
the
screen
and
then
it's
just
minor
usability
issues,
I
think
that
adds
and
put
it
nicely
there
that
even
like
that,
it's
a
huge
improvement.
So
we
shouldn't
worry
about
that.
It
shouldn't
stop
us
from
amazing
and
if
we
decide
to
merge
at
some
point
like
say
two
three
which
before
release
and
then
again,
I
can
follow.
C
D
A
D
D
A
D
C
Even
though
I'm
the
culprit,
that's
responsible
for
kind
of
being
like
not
documenting
processes
enough
but
yeah
and
things
that
you
guys
need
the
best
thing
to
do
for
me
actually
is
to
just
throw
me
into
the
meeting
honestly
and
then
then
I
can
communicate
that
way.
I
know
that
that's
terrible
because
so
I
wrote
it
down.
Then
it
would
last
forever.
F
C
A
A
F
D
D
Synchronizing,
keeping
keeping
core
sorry
keep
it
contraband
core
modules
that
came
from
d7
contribute
in
sync,
so
we
have
lost
sing.
We
started
off
by
finding
out
that
that
DCU
backdrop
that
old
side,
but
then
another
solution
came
up
with
from
yep,
so
I
think
we
should
do
this
then
later,
because
the
more
we
wait,
the
more
updates
are
accumulating
yeah.
If
we
get
the
notifications
now
we
can
like
it's
time,
there's
a
new
thing
that
comes
out.
D
A
D
B
D
C
D
A
C
F
Course
so,
like
I
started
going
through
the
files
which
is
really
gonna,
improve
our
API
site
because
the
stuff
that's
forcing
us
to
update
is
like
dock
blocks
and
that's
that's
really
exciting.
But
there
are
a
couple
things
where
I've
I've
asked
for
needs
review
like
where
I'm
making
decisions
and
I'm
not
sure
that
they're
I'm
on
the
fence
about
whether
the
right
thing
to
do
or
not
like
views
module,
for
example,
most
of
its
classes
are
word
underscore.
F
Another
word
underscore
yeah,
that's
code
violation,
so
I've
been
been
saying,
you
know
peach
Peaks,
yes,
ignore
this
line,
and
then
tagging
with
to
do
2x
rename
these
classes
to
me.
So
if
that's
a,
if
that's
okay,
if
people
are
on
board
with
that
I'll
just
keep
trucking
along
in
the
files
and
I've
been
adding
like
okay,
I'm
I'm
in
databases
right
now,
and
then
I
got
my
name
next
to
it.
E
F
D
A
F
D
C
F
B
C
F
D
We're
actually
comparing
everything
like
our
agency,
there's
another
fellow
here,
a
senior
tech
that
is
actually
converting
all
the
Drupal
7
sites
to
automating
everything
and
using
composer
authorizing
them
or
whatever.
If
it
is
a
great
tool
so
long
as
we
use
it
for
our
infrastructure
and
we
don't
push
it
to
people
to
use
it,
it's
nothing.
It's
fine!
Absolutely.
F
C
E
C
C
C
F
C
D
It
would
be
cool
if
we
could
have
mentioned
that
before
I,
don't
know
what
the
capacity
like
was
capacity
or
something
we
didn't
mention
that
in
the
past
soon,
as
we
had
it
for
core,
it's
full
request
had
its
own
sandbox.
We
said
that's
so
cool.
We
should
have
it
the
computer,
but
what's
a
whole
yeah.
C
I
kind
of
highly
interesting
thing
here
is
that
this
orifice,
the
way
it
works,
is
it
doesn't
dumb
it's
not
actually
using
an
external
service
to
be
the
code.
Checking
the
code.
Checking
is
on
the
machine
that
is
running
the
tests,
and
so
you
can
run
it
like,
but
Jeff's
probably
been
doing,
is
running
this
locally
and
then
fixing
all
the
issues
locally,
and
so
that
means
that
any
testing
service
like
Travis
or
whatever,
that
just
needs
to
run
the
script
and
then
we'll
get
the
coding
standards
file.
B
A
C
C
E
C
F
C
E
F
Would
definitely
feel
the
pull
pull
request.
I
mean
that's
how
the
Travis
works
for
sure,
but
we
could
get
better
language
than
that.
Well,
like
say
you
know
the
the
code
standard
you
know
we'll
make
it
so
says
the
coast
Anders
aren't
up
to
snuff
or
whatever
make
some
nice
sentence
and
and
then
should
give
them
like
the
line
number
or
numbers
and
ideas
of
what
to
go,
fix,
yeah.
That.
D
F
C
F
C
Okay,
I
mean
yes,
I,
think
it's
so
a
good
idea,
okay,
and
and
even
if
we
don't
get
the
automated
part
done,
although
the
automation
was
definitely
them.
That
would
just
say
anything.
It
would
just
be
so
nice
to
not
have
to
nitpick
people's
code
style
every
single
time
they
wrote
a
foreword
question.
Amin.