►
From YouTube: Backdrop Weekly - Oct 18
Description
Today’s development agenda: http://bit.ly/2EfWVt6
A
All
right,
we
are
on
air,
this
Thursday
October
18th,
and
this
is
a
check-in
meeting
for
active
development
tasks
on
that's
up
CMS
before
we
get
into
what
we
are
currently
looking
into
today.
I
do
want
to
make
a
quick
announcement
that
we
have
a
ton
of
new
things
for
projects
this
week
so
focal
point.
Something
I
use
a
lot
in
Drupal,
7,
she's
great,
to
have
to
like
she's
a
center
front
of
a
photo
to
crop
around
she's,
fantastic,
bonding
history,
layout
nodes
and
web
form.
Submissions
multiples.
A
For
back
job,
we
do
have
a
securities
coming
out
later
today,
so
keep
your
eyes
open
for
that.
That
will
be
a
virtual
number
111,
and
then
we
have
a
bunch
of
issues
slated
for
111
3,
including
a
couple
that
are
TDC.
I
would
imagine
these
are
TV.
6
issues
are
not
going
to
go
in
today's
race,
because
Nate
doesn't
usually
like
to
do
non
security
fixes
with
security
fixes.
So
those
next
issues
for
111
3
include
adding
some
predefined
color
schemes
to
basis.
We
have
an
issue.
3209
has
a
for
request.
A
It
needs
a
little
work.
Some
of
the
colors
that
are
provided
are
not
accessible,
so
I'd
love.
We
could
just
run
all
of
the
predefined
color
palettes
through
a
web
accessibility
checker
to
make
sure
that
we
are
providing
accessible
to
folks
to
people
and
I
think
once
we
get
those
slightly
adjusted
that
will
probably
be
ready
to
go
in.
A
The
next
issue
is
already
or
you
can
testify
the
community,
and
this
is
regression
really
info
status
message
where
we
had
an
info
class,
someone
else
in
court
and
it's
not
quite
specific
enough,
so
we're
changing
that
class
name
to
get
around
the
issue
and
what
also
I
think
changing
this
CSS
identifier,
so
that
if
anyone
had
a
class
thing
can
throw
in
there,
it
wouldn't
automatically
be
updated.
So
I
don't
know
what
you
got
for
effects
lately,
but
it's
marked
our
TCC
associate
33.
A
Okay
and
those
are
all
of
the
issues
that
we
have
marked
high
priority
for
the
next
month,
which
means
we
have
a
couple
of
more
issues
for
112
zero.
So
these
are
new
features
and
this
version
is
due
out
January
15
code
3
is
January
1st.
The
first
one
is
related
to
our
core
updates
meta
issue,
where
we
want
to
turn
on
these
our
inner
peace
before
update
so
right
now,
there's
user
interface
and
core,
but
it's
not
visible
in
the
next
release.
We
want
to
make
it
visible,
so
people
can
start
using
this.
A
A
So
I
don't
know
if
there's
a
purpose
for
that
yet,
but
once
we
have
anything
start
cussing.
The
next
issue
is
around
package
signing.
This
is
issue
1992,
and
this
is
something
that
need
to
get
done
before
we
turn
on
automatic
updates.
It
will
also
be
a
good
idea
to
get
done
before
we
enable
the
Update
button
I'm,
not
sure
it
will
get
done
in
front,
but
if
so
that
would
be
nice.
What
this
will
do
is
just
ensure
that
the
package,
the
backdrop
receives
when
it
doesn't
update,
is
the
package
it
intended
to
receive.
A
So
if
you
go
to
update
core,
you
want
to
make
sure
that
you're
updating
with
a
version
of
core,
that's
the
one,
the
fact
that
they
intended
you
to
have
not
something
that
anything
intercepted
and
other
TV
instead,
so
that
one
I
think
it's
a
fantastic
idea.
I
would
love
to
see
it
get
in
there.
You
know
15
thinking
right.
We
just
need
some
more
progress
made
on
the
issue.
A
A
B
A
Next
issue
is
number
one
thousand
five
and
that's
about
adding
options
element
in
core.
So
this
takes
the
allowed
values,
text
area
and
turns
into
a
more
usable
interface
that
has
a
key
field
and
a
value
field
and
lets
you
reorder
them.
I.
Think
it's
a
fantastic
improvement.
I
made
a
couple
of
usability
recommendation
philosophy
if
implemented,
I
think
straight
again,
but
we'd
love
some
more
feedback
online.
If
anyone
else
has
any
thoughts
about
making
that
interface
at
a
better
effect,
it's
already
complete
another
lesson
course.
A
So
I
can't
wait
that
for
and
the
next
one
it's
something
that
has
been
fairly
important
backdrop
community.
It's
been
on
the
issue:
the
agenda
for
the
next
choice
couple
of
times
before
is
field
of
both
file
types.
So
if
you
wanted
to
be
able
to
add
a
photo
credit
or
a
caption
to
an
image
or
publish
date
to
a
PDF,
you
can
put
fields
on
those
files
and
they'll
be
separated
by
type.
So
this
is
issue
number
26
32.
We
have
a
pull
request
there.
It
needs
a
little
bit.
A
More
testing
looks
like
it
needs
a
little
work,
but
we
want
to
walk
feedback
on
it
before
we
do
another
revisions
that
for
us
only
one
who's,
here's
their
plain
with
helical
file
type
screamed
at
that
length
right
and
then
we
have
a
new
one
here,
Gregory
this
was
mentioned
by
you.
Do
you
want
to
give
us
an
update
on
it?.
B
Well,
yeah,
basically
I
mentioned
that,
because
I've
found
the
back
when
I
was
working
on
it.
It's
just
the
recommendation
to
have
sort
of
like
more
consistency
across
the
admin
pages
and
sort
the
available
updates
paid
the
same
way
that
we
saw
the
status
plays
with
with
the
important
there
are
security
updates
and
the
update
bubbling
up
to
the
top
of
the
list
and
then
having
the
modules
and
things,
and
what
have
you
then
are
up
to
date
be
at
the
bottom.
B
We've
been
working
on
that
the
problem
that
I
found
was
that
it
wasn't
a
problem
with
core
itself.
It's
we
thought
processes
and
he
has
to
do
with
security
releases
of
contributors
that
have
we
are
failing
to
mark
them
as
security
releases
on
Bilodeau.
Then
we
need
to
figure
out
a
way
to
streamline
that.
A
All
right
so
I
just
added
that
into
our
agenda
under
general
discussion,
so
that
we
can
follow
up
on
it
in
the
next
meeting
as
well
to
make
sure
that
we
actually
have
some
solutions
in
place,
but
yeah
there's
a
couple
of
things.
We
need
to
do.
I
think
you
need
to
update
the
documentation
about
contributor
leases.
We
have
a
cage
for
that
on
the
API
site
under
the
contributing
section,
we
need
to
make
sure
there's
a
specific
thing
there
about
like
if
it's
a
security
release.
A
This
is
what
you
have
to
do
so
number
one
is
document,
what
the
steps
that
are
required
and
then
the
second
one
will
be.
How
do
we
make
that
process
easier?
So
right
now
the
fact
that
we
have
to
document
it
is
not
great
and
it
does
require
someone
who's
an
at
least
an
editor
level
on
backups
in
us
or
can
manually
update
that
project.
A
We
talked
about
better
solutions
like
if
we
have
single
sign
of
github
and
anyone
who
is
a
maintainer
for
the
finisher
project
could
get
automatically
get
at
access
to
that
node
and
then
they
will
be
able
to
make
that
update
themselves,
so
that
wouldn't
require
an
administrator
which
would
be
great
and
then
even
better.
If
there's
something
we
could
do
at
the
gate
level,
that
would
let
us
do.
A
A
If
anyone
lives
in
the
San
Francisco
Bay
Area
and
would
like
kitten,
we
have
an
extra
one
and
put
lunch
to
get
it
adopted
out.
So
I,
don't
don't
chop,
sometimes
a
second
yeah.
Definitely
we
need
to
document
the
current
practice
for
anything
concern
context
into
security
releases,
and
then
we
also
need
to
make
that
process
easier
than
others.
B
So
also
the
the
ticket
number
for
the
for
updating
the
you
at
the
UI
I
was
for
one
for
not
for
for
one
okay
related
to
this
one
and
the
three
one
three
to
the
one
with
sorting
the
modules.
Certain
ideas
that
for
apt-
and
maybe
that
popped
up
in
the
past
as
well,
is
now
that
we
have
core
updates.
These
core
updates
will
be
appearing
in
in
update
modules,
update
things
and
update
layouts.
B
B
So
perhaps,
besides
just
listing
the
updates,
we
should
allow
people
to
update
from
within
that
planes.
That's
a
good
idea!
Okay!
Yeah!
Do
you
have
an
issue
for
that
already
yeah
I've
mentioned
it
in
the
comments
for
for
one,
for
if
we
don't
end
up
in
too
many
items,
not
then
we
will
follow
it
up.
Okay,
that.
A
Sounds
good
yeah
I
remember
that
discussion
if
he
was
very
early
in
back
to
boiling
water
leaving
it
when
we
were
taking
about
putting
the
project
browser
in
like
oh
there's
so
many
pages
about
where
you
can
do
updates.
How
are
we
going
to
do
it?
Well,
let's
just
leave
it
alone
and
we'll
figure
it
out
later,
I
think
it's
later
so
yeah.
A
B
Was
another
issue
that
might
be
worth
mentioning
the
one
to
move
certain
files
under
core
like
eights,
the
axis,
the
rest
of
them
so
yeah?
We
need
some
feedback
on
that.
There's
a
few
ideas
that
have
been
thrown
around
some
security
concerns
and
then
some
workarounds
possible
workarounds
for
those,
so
any
feedback,
especially
from
night
unzip
or
anyone
who's,
more
technical,
I
think.
A
So
I
also
like
the
idea
of
provide
like
moving
more
things,
to
course,
that
our
instructions
only
hope,
but
the
backup
are
just
popular
for
directory
I.
Think
that's
fantastic,
especially
after
wanting
to
deal
with
some
of
the
craziness
of
updating
the
Drupal
site.
So
if
you
can't
be
the
corner,
if
you're
in
a
new
vendor,
dark
green,
oh
there's
all
these
other
files
and
I
as
much
as
we
can
decrease
that
kind
of
confusion
for
people
the
better.
A
But
we
do
harvest
some
files
that
are
like
super
useful
to
have
in
that
root
directory
and
so
I.
Really
like
the
idea
of
providing
a
starting
point
like
we
have.
The
settings
example
file
right
having
something
like
that
or
we
could
have
an
example.
You
jaxa
sell
an
example
getting
one
phone
and
all
of
those
are
in
poor,
but
as
working
under
an
issue,
I
also
love
to
have
on
initial
install
all
the
files.
Don't
need
to
be
copied
so
that
your
instructions
can
be
update
course.
A
But
then,
if
you've
made
any
changes
to
those
other
files
like
your
site,
will
still
run
so
be
secure
out
of
box.
But
it's
not
going
to
overwrite
as
those
unless
you
really
need
those
changes.
So
there
are
some
things
we
need
to
do
carefully
when
we
do
that,
but
I
love
the
direction
that
is
going
in
so
I
agree.
We
must
be
back
on
it
from
core
committers.
It.
B
A
B
A
A
See
I
think
that's
it
for
high
priority
different
issues
but
112,
but
if
there's
anything
else
that
people
are
interested
in,
we
do
have
my
own
stone
for
one
puff.
It
includes
a
lot
more
than
what
we
just
talked
about,
so
I
would
just
encouraging.
What's
in
that
milestone
to
see
if
there's
anything,
you're
really
passionate
about
that
housing
people.
If
you
talk
about
in
the
agenda,
they
just
added
a
couple
of
new
things
to
it
today
make
fun
of
expert
three
so
we'll
see
if
we
can
get
those
into
one
fall.
A
So
so
next
up
we
have
a
section
in
the
agenda
where
we
do
update
on
backed
up
for
good.
We
have
a
project
that
could
use
volunteers.
There
is
an
issue
key
opening
wants
to
grab
issue
and
work
on
it
under
it
backed
up
the
good
I
would
there's
a
link
in
the
agenda.
It's
also
I
get
hub
through
is
capital
feedback,
job
and
number
four
calculate
G
good.
You
can
check
out
the
fun
all
right
so
under
the
non
discussion.
I
added
the
confirm
security
updates
here,
but
that's
mostly
for
our
next
meeting.
A
So
you
can
follow
up
on
what
we
have
to
do
today
to
make
sure
that
that
gets
done
and
then
there's
another
item
here,
which
is
licensing
for
concerns
objects
last
week
and
I
can
think
before
we
talked
about
it,
you
have
an
open
issue
for
the
PMC
that
was
currently
under
discussion.
I'm
gonna
bump
that
this
week
to
needs
a
vote
so
hopefully,
next
week,
we'll
have
a
definitive
answer
and
they'll
be
able
to
start
updating
documentation
to
reflect
that.
A
So
I'm
gonna
leave
this
in
the
agenda,
so
you
can
get
there
again
and
that's
it
and
what's
on
the
agenda,
but
as
with
all
of
our
meetings,
we
always
have
an
open
Q&A.
The
Android
can
bring
up
anything
related
to
what's
on
the
agenda
or
not.
So
if
you
want
to
say
hello
or
a
document
it
or
whatever
it
is
now
do
that
is
anyone
have
anything
to
add.
A
B
Were
doubting
our
website?
Our
main
word
said
we
got
one
so
there
was.
It
was
mentioned
at
so
point
or
asked
that
on
our
roadmap-
tides
as
there's
a
list
of
the
things
that
we
are
planning
for
the
next
release
and
also
the
goals
for
a
2.0.
But
someone
also
decided
so
anything
that
is
API
grating.
We
have
pushed
the
2.0
and
released
it
anything
that
we
definitely
want
to
get
done
on
the
next
release.
The
immediately
next
release
is
also
listed,
but
sometimes
we
have
big
plans
that
are
pushed
in
future.
B
B
A
A
I
would
encourage
anyone
who
has
a
edit
access
to
go
ahead
and
make
a
change
to
that
page
and
if
they're
not
sure
if
it's
correct
freedom,
religion
and
we
can
get
someone
else
to
review
it,
but
yeah
I
think
in
general.
The
more
information
to
put
on
stage,
especially
now
that
we
know
that
you
can
make
a
bunch
of
improvement
for
the
longing
API
breaking.
If
we
have
things
that
are
specifically
scheduled
for
poor.
A
Getting
them
on
the
list
would
be
good
to
make
that
transparent
for
everyone.
So
I
know
that
we
talked
about,
like
our
automatic
updates.
No
longer
have
to
wait
to
TX,
so
it
just
means
that
she,
the
boss
for
one
that
I've
section
but
I,
think
there
were
other
things
see
that
we
mentioned
that
we
wanted
to
get
into
one
that
X
that
aren't
on
a
list.
Yet
yeah.
A
A
A
That's
great
so
then
I
think
this
is
also
a
good
place
where,
if
we
have,
if
we
have
something
that
we
scheduled
for
a
release-
and
it
doesn't
get
done
and
we
have
to
bump
it
if
we
can
then
move
that
into
this,
like
you
know
we're
going
to
do
this
in
1x
section
it
just
like,
maybe
not
the
release,
the
virus
or
an
extension
or
that
would
at
least
let
people
know
I'm
working
on
these
famous
we're
going
to
get
them,
even
if
they
don't
make
this
particularly
so.