►
From YouTube: Backdrop Weekly - Mar 21
Description
Today’s development agenda: http://bit.ly/2UQ7Yx4
A
A
So
this
week
in
the
community
we
have
a
new
contributor.
A
That's
I,
don't
know
how
you
say
that
someone
new
sent
a
maintainer
application
they're,
currently
working
on
the
import-export
model,
just.
A
Of
protocol
so
that'll
be
great
to
get
some
new
ones
in.
We
also
have
three
new
contributing
project
updates,
so
the
modules,
fair
content,
type
clone
image,
resize,
filter
and
he's
accordion
have
been
published
and
are
now
available,
backed
up
CMS
to
ordinator,
which
is
great
updates
for
back
to
the
CMS
org
the
website
itself.
We
know
we
have
an
issue
with
our
progress
on
the
home
page
demo
button.
A
D
B
That's
that's
very
exciting
and
that
that
hopefully
I
haven't
actually
tried
not
yet,
but
that
hopefully
will
also
resolve
the
demo
button
problem
because
there's
some
kind
of
PHP
command-line
problem.
That
is
only
happening
on
the
current
server,
which
is
running
the
old
version
of
PHP
PHP
5.4.
This.
A
Also
I'm
not
sure
if
we
talked
about
this
last
week
or
not,
but
we
have
a
new
security
release
policy
which
was
voted
on
adopted
by
the
PMC
and
so
I
updated
our
security
page
on
dr.
up
semester,
org
slash
security
to
include
our
core
update
process
under
the
security
releases
section
the
first
paragraph
there,
and
then
we
also
updated
the
contributed
section
based
on
discussions
last
week.
So
that's
just
kind
of
open
for
feedback.
A
B
A
B
Okay,
well,
yesterday,
any
observers
of
the
backdrop
world
probably
noticed
that
there
was
a
security
release
of
backdrop.
One
point:
twelve
point:
five
came
yesterday
to
coordinate
with
security
release
of
Drupal,
seven
and
Drupal
8,
so
it
was
affecting
file
uploads
in
a
way,
and
so
we
made
it
really
subordinate
with
that.
So
they're
also
a
couple
of
other
things:
small
things
that
got
put
into
one
twelve,
five
and.
A
B
Yeah,
so
things
that
we
have
been
talking
about
in
previous
weeks
have
now
been
bumped
over
to
one
twelve
six,
as
the
next
bug
fix
release.
There's
RTL
issues
are
continuing
to
move
forward.
The
ckeditor
icons
being
broken
in
RTO
now
works
from
a
youth
like
it
functionally
works
now,
but
it
still
has
some
minor
padding
and
margin
problems,
so
it
had
been
marked
our
TBC
earlier
today.
B
B
Let's
see
other
things
that
were
working
through
still
highly
relevant
that
we're
working
on
this
issue
to
make
it
so
that
multiple
different
minor
versions
of
backdrop
can
have
equivalent
security
status,
basically
saying
that
the
previous
release
can
be
fully
patched
and
be
secure,
even
though
there
are
newer
versions
of
back
jump
available
so
that
issue
35
24
is
titled
support,
multiple
equivalent
security
releases.
So
like
we
released
111,
seven
I
think
yesterday
or
111
8,
which
coordinated
with
112
5
and
both
of
those
are
equally
secure.
A
B
A
A
A
B
A
B
B
A
A
B
B
A
B
A
Became
a
term
reference
field,
they
didn't
include
the
same
for
matters
that
were
in
six,
so
it's
a
accidental
oversight,
but
then
there
was
a
module
for
seven,
so
the
urgency
just
decreased.
But
if
we
get
that
module
on
core,
then
it'll
make
it's
better
for
people
operating
from
six.
So.
B
B
B
Well,
in
any
case,
the
problem
that
we
have
with
that
one,
the
functionality
is
all
there,
but
it
needs
tests.
We
can't
add
some
new
API
to
core
and
have
it
be
completely
untested
because
we'd
have
no
idea
if
we
broke
it,
unless
we
have
some
kind
of
test
coverage,
so
test
coverage
for
something
that
isn't
doesn't
core
doesn't
use
directly
as
unfortunately
extra
tedious,
because
you
have
to
write
a
test,
only
module
that
uses
the
functionality.
That
core
is
exposing
and.
A
B
A
C
A
B
A
B
Thus
far,
we
haven't
actually
written
any
code,
it's
just
kind
of
concepts.
Things
I
mentioned
this
last
week
and
most
weeks
that,
although
this
will
involve
interaction
between
backups,
EMS,
org
and
backdrop,
installations
like
the
API
can
be
like
basically
fabricated,
and
then
you
can
work
on
either
side
independently.
As
long
as
the
API
is
established
like
what
information
is
being
sent
and
how,
like
a
probably
you
know,
via
JSON
information
like
being
consumed
on
the
way
up
or
and
then
like
post
data
being
sent
on
the
way
in
something
along
those
lines.
B
So
yeah
not
there's
no
progress
on
that
one
that
was
still
just
discussion.
Dashboard
dashboard
is
really
close.
I'd
say
that
we're
kind
of
in
the
final
hard
served
review
there,
there's
continuing
to
be
more
suggestions
that
are
coming
in
I.
Think
that
there's
some
satisfaction
with
people
saying
we're
at
a
pretty
good
point
that
it's
close
enough
to
get
that
in
and
then
and
then
iterate
on
top
of
it
from
there.
A
Know
just
I
think
I
agree
that
pull
request
against
mine
or
request
look
at
that
today,
but
other
than
that
I
think
it's
ready
for
like
a
more
technical
review.
So
the
feature
set
is
complete
enough
for
merge.
There's
a
listed
like
a
list
of
additional
things.
We
can
do
in
follow-up
issues
and
I've
started.
Creating
those
follow-up
issues
assuming
they
won't
be
included
so
I
think
we've
got
all
the
features
from
what
we
just
need
to
make
sure
the
code
is
good,
I'm,
not
sure
it
has
tests.
B
Yeah
that
issued
3455
herb
duel
ropes
over
a
month
back.
Actually
that
has
been
needing
review
for
quite
some
time
and
just
making
it
so
that
certain
about
pretty
much
all
config
files
in
core
will
need
to
list
their
translatable
strings
and
35
or
34.
55
is
the
first
pass
at
that
for
some
system
settings
like
site,
name
and
slogan
like
ik
emails
I'm,
like
the
welcome
emails,
so
still
need
your
view
on
that
is.
A
B
I
actually
think
that
that
is
the
meta
and
34:55
days
the
meta
and
then
there's
the
link
to
the
one
that
makes
the
battle
starts,
perfect,
yeah
so
and
lastly,
on
the
113
hit
list
is
package
signing
issue.
1992
John
Franklin
put
up
a
substantial
amount
of
new
code
a
couple
of
weeks
ago
in
progress,
but
needs
review
from
from
some
more
eyeballs.
There
I
think
he
we
supposed
to
like
a
massive
amount
of
stuff,
but
we
need
to
like
go
through
and
actually
process
what
that
means
and
how
we
would
actually
leverage
it
yeah.
A
A
Future
Englishmen
for
the
next
version
of
Thatcher
yeah.
Everything
else
is
looking
like
it's
coming
along
great
and
I
just
want
to
say
a
special
thanks
to
everybody.
Who's
been
pitching
in
with
all
of
the
security
releases
recently
they've
had
a
whole
bunch
of
community
collaboration.
New
people
joined
the
security
team.
Helping
us
get
all
the
issues
out
heard
really
stuff,
so
really
appreciate
all
the
involvement
everyone
now.
B
Yesterday,
Jen
and
I
were
teaching
a
class
actually
during
the
security
release,
and
we
had
Tim
in
the
back
of
the
class
and
saying
hey.
There's
this
community
that's
going
out
today,
oh
boy,
so
Jenna
took
the
lead
on
the
class,
so
he
sat
down
and
everything
had
been
put
in
place
by
community
members.
Gregory
took
a
strong
lead
in
getting
that
coordinated
up
to
the
point.
That's
like
with
somebody
actually
do
the
committing
of
and
tagging
up
their
releases,
but
then
that
took
less
than
an
hour
of
my
time,
actually
doing.
B
A
A
Okay,
so
that's
it
for
the
official
agenda.
Justin
I
know
you
joined
the
call.
We
did
mention
the
very
beginning,
the
meeting,
all
the
great
work
you're
doing
on
the
new
server.
It
looks
like
there's
a
little
issue
where
you
need
it
host
name.
Information
from
us.
Is
there
anything
else?
That's
locking
you
on
that.
No.