►
From YouTube: Backdrop Weekly Mar 29
Description
Today’s development agenda: https://bit.ly/2IGN9yp
A
This
meeting
is
to
check
in
on
active
development
tasks
for
backdrop
CMS.
Before
we
get
into
active
development
tasks,
quick
announcement,
we
are
under
contract
with
the
software
freedom,
Conservancy
I,
don't
know.
If
that's
what
it's
called,
we
have
a.
We
have
an
agreement
with
them
and
next
steps
are
writing
up
a
blog
post,
that's
announcing
our
terms
of
engagement
and
so
I
told
Karen.
A
A
So
if
we
can
write
a
post,
it'll
get
posted
on
their
system
as
well
as
ours.
So
let
me
know
if
you
have
any
thoughts
about
that.
In
the
past
week
we
got
a
new
backdrop.
Contribute
of
flat
submitted
an
application
along
with
a
port
of
the
New
Relic
module,
which
he
maintains
for
Drupal,
which
looks
really
great.
So
the
thing
shows
up
for
doing
all
that
work.
A
We
also
have
a
new
contributed
module
this
week
back
webform
clear
is
in
the
contributor,
if
anyone's
curious,
about
that
on
effective
CMS,
org
we're
currently
working
on
improving
the
modules,
themes
and
layouts
listing
pages.
We
have
designs
for
those
I
demonstrated
not
in
today's
design
meeting
but
the
one
two
weeks
ago.
If
anyone
wants
to
take
a
look
at
that
video
and
on
our
forum
site,
we
have
a
request
at
a
search
box,
because
we
now
have
enough
stuff
going
on
there
that
people
are
finding.
A
C
C
You
guys
know
the
version
number
7.54
da
58
yeah.
Sorry,
it's
really
up
there
these
days,
and
so
we
released
backed
up
1.9.3
in
tandem
with
that
and
similar
to
Drupal
and
per
a
security
announcement
that
we
set
up
a
public
security
announcement
that
we
said
sent
out
about
a
week
prior
to
that
we
also
released
kind
of
out-of-band
updates
for
1.8
and
1.7.
C
The
likelihood
of
your
site
being
exploitable
is
very
high,
so
update
okay,
so
one
point
9.4
now
becomes
the
next
bug
fix,
release
and
the
items
that
we've
got.
One
point
nine
point:
four:
we've
got
a
couple
of
dozen
items
that
have
been
marked
kind
of
a
higher
priority
for
bug,
fixes,
all
of
which
nearly
all
of
which
have
some
pull
request,
is
in
a
state
that
is
in
progress.
C
There's
only
one
RT
PC,
one
point,
nine
point,
four
issue
that
I'm,
aware
of
which
looks
like
it's
just
a
really
minor,
like
the
link
isn't
working
correctly
so,
as
always
like
a
more
cross.
Reviewing
and
more
pure
updates
between
community
members
would
be
highly
appreciated,
although
when
I
have
time
available
go
through
the
the
needs
review
list,
of
which
there
are
many
more.
Let's
see,
there's
currently
six
items
in
a
needs
review
and
more
than
a
dozen
in
any
needs
work
state
so
anyway,
of
interest
in
particular.
C
For
one
point,
nine
point
four
issue:
twenty
nine,
seventy
one,
which
is
when
upgrading
from
Drupal
seven
the
account
email
messages,
don't
actually
maintain
their
newline
characters
to
actually
get
converted
into.
Actually
hard-coded
backslash
n
in
the
email
so
which
makes
for
some
pretty
unfriendly
like
welcome
emails
and
password
reset
emails.
C
Well,
yeah.
We've
got
some
issues
in
there
that
that
one
is
a
little
bit
hard
to
describe,
but
we
have
a
fix
in
there
that
actually
makes
it
so
that
the
password
for
database
credentials
is
read,
URL,
encoded
and
URL
unencoded,
but
we
need
to
present
a
message
to
users
saying
if
their
database
credentials
that
are
using
the
incorrect
format
notify
them
so
that
they
can
make
that
correction
settings
dot
PHP,
because
there's
not
much
that
we
can
do
without
user
intervention
there.
C
So
if
we
introduce
something
that
is
basically
a
workaround,
we
want
to
make
sure
that
the
user
is
notified,
that
workaround
is
being
utilized.
So
that's
issue
2904
and
that's
it
for
the
things
in
the
agenda.
There's,
of
course
the
milestone
tag.
One
point
9.4:
you
can
check
out
on
github.
So
one
point
ten
at
one
point:
ten
is
the
next
minor
release.
It
will
be
coming
out.
May
fifteenth
I'm
sure,
and
you
know
come
next
week
when
it
when
April
rolls
around.
C
It
will
really
feel
like
a
kick
in
the
pants
that
that
the
next
version
of
backdrop
will
be
coming
out.
So
soon
code
freeze
is
May
first,
which
means
we
basically
have
one
month.
So
I
feature
freezes
May.
First,
we
basically
have
one
month
to
implement
some
new
functionality
into
the
backdrop.
To
make
one
point:
ten
kick-ass:
we
have
a
number
of
items
that
improve
the
translation
system
within
backdrop,
two
of
which
are
in
really
good
shape.
Issue
225,
which
is
making
menu
items
translate,
although
it's
stated
it
as
needs
work
it.
C
C
It's
like
I'm,
afraid
I
might
act,
a
bunk
that
one
down,
but
I
have
stated
that
it's
on
my
plate
to
do
a
code
review
of
that
one
not
looking
so
hot
is
issue
704,
which
is
the
ability
to
make
it
so
that
config
is
translatable.
We
still
have
a
really
great
framework
and
a
battle
plan
there,
but
implementation
wise,
we're
still
just
a
like
proof
of
concept
stage,
so
that
one
both
needs
some
work
and
needs
a
lot
more
attention
in
order
to
move
it
forward.
C
We
don't
need
to
complete
config
translation
like
if
we
get
into
the
base
up
system,
we
can
go
through
and
start
incrementally
swapping
out
where
translation
strings
or
run
through
config,
but
yeah
I
think
that
we
still
have
the
capability
of
getting
into
base
system
into
one
point.
Ten,
let's
see,
we've
got
a
number
of
items
here
for
improving
the
way
that
modules,
themes
and
layouts
are
discovered
and
enabled,
but
I
don't
think
that
I'm
going
to
recap
these,
because
there
hasn't
been
any
updates
since
last
week,.
C
So
a
new
item
that
is
on
the
agenda
this
week,
thanks
to
some
efforts
from
herb,
dual
and
Lauren,
is
issued
3001,
which
is
an
automatic
comment,
closer
functionality
which
has
been
discussed
in
there
as
being
something
that
if
Cora
had
comment
closer,
then
we
would
all
use
it
all
the
time,
but
just
comment
closer.
Is
it
contribute
it's
like
well,
I,
don't
really
want
to
go
through
the
effort
of
you
know
downloading
installing
that
module
which
herb
do
we'll
also
posts
are
also
ported.
C
D
C
B
The
other
sums
of
it,
it
seems
to
me
that
it's
going
to
be
a
similar
matter
of
providing
an
option
for
content
types
if
this
will
be
available
at
the
end
user
on
a
pure
condom
base
and
what
would
be
the
default.
It's
similar
to
the
sticky
settings
that
we
have
as
in
allow
allow
this
contact
to
be
set
as
the
key
and
the
default
is
sticky.
B
C
So
it
looks
like
the
current
implementation
is
content
type
only
so
there
isn't
any
per
noted
settings
for
that,
and
actually
now
that
you
guys
mention
it
there's
some
obvious
problems
that
could
arise
here.
If
comments
were
scheduled
to
be
closed
and
then
they
closed,
but
then
the
author
was
like:
oh
there's
a
lot
of
things
going
on
there
I
want
to
reopen
it.
Then
it
could
get
closed.
Good.
C
Would
not
be
very
friendly,
I
post
comments
to
that
effect,
saying
that
you
know
that
we
have
a
little
bit
of
a
problem
there
I
think
not.
You
know
what
Gregory
is
saying
fixes
that
problem,
because
it
would
make
it
so
you
would
see
on
the
node
itself
when
it
was
scheduled
to
be
closed.
I
don't
know,
but
that
makes
things
more
complicated,
though
the
implementation
was
merely
a
hundred
lines,
but
if
it
doesn't
work
then
we
need
to
you
know
iterate
on
that,
a
little
bit
and.
D
B
Have
a
similar
thing
going
on
tackling
the
problem
with
path
order
where
I
thought
it
was
set
automatically
generated,
but
the
user
antique
that
then
bethalto
persist
would
remember
that
choice
and
not
switch
back
to
automatic
parts.
Maybe
something
similar
can
be
applied
in
this
case.
So
if
the
user
sort
of
like
manually
overrides
this,
then
we
don't
switch
back
to
automatically
inside
minutes.
Yeah.
C
A
We
should
look
at
what
WordPress
does
for
this
and
see
if
they
offer
of
overwrite
something
because
this
might
be
the
kind
of
thing
where
it's
like.
If
we
put
comic
closer
in
core
as
a
content,
type
wide
thing
it'll
be
pretty
easy
to
add
a
control
that
would
add
all
the
like
per
node
override
stuff.
A
So
we
should
see
like
how
important
that
pieces
to
it
being
a
core
feature
and
I
think
seeing
what
WordPress
is
doing
with
theirs
might
help
us
figure
out
how
complete
our
future
is
compared
to
how
complete
their
feature
is
and
try
and
make
sure
we
get
something
comparable.
We
don't
leave
anything
out.
So
maybe
we
don't
like
go
overboard
on
what's
important.
The.
B
Way
that
I
see
it
is,
we
have
two
use
cases
you
know
about.
That
is
people
that
would
want
to
create
a
content
type
that
would
automatically
allow
comments
for
only
a
specific
period
of
time,
and
then
people
that
would
allow
to
allow
this
option
for
the
nodes
and
allow
specific
blog
posts
to
be
valid,
for
only
us
certain
things
like
pause,
the
comments
after
Easter
or
after
Christmas,
but
it
would
be
specifically
for
its
individual
node.
You
have
to
get
use
cases
there.
Yeah.
B
C
C
D
B
E
D
D
D
A
D
While
we're
talking
about
this
there's
a
related
feature
that
comments
that
I
would
really
love
to
see,
and
that
is
a
simple
checkbox
to
turn
off
comments
on
the
content
type,
because
right
now
you
can
only
do
is
you
can
only
set
it
default
to
closed?
But
if
you
don't
want
ever
to
be
any
comments
on
the
content
type,
there's
no
way
just
to
turn
that
off.
D
A
D
D
A
C
C
E
C
Needs
to
be
explored
in
that
ticket,
okay.
Well
anyway,
let's
continue
discussing
that.
The
issue
number
for
coming
close
who's
issued
three
thousand
and
one,
and
there
are
more
things
that
we'd
like
to
get
into
one
point:
ten
as
well.
Mike
mentions
file
bundles
earlier
I,
can't
remember
that
was
on
air
or
not,
but
per
the
bundles
on
file
types
and
also
a
number
of
other
file
and
media
enhancements
that
did
not
get
into
1.9
are
also
good
candidates
for
one
point
10,
although
the
kind
of
champion
for
those
feature
improvements
has
been
absent.
C
A
C
C
A
I
want
to
say
thank
you
to
everybody
who
was
involved
in
getting
the
security
release
out
yesterday.
I
know,
there's
a
lot
of
working
folks
from
a
lot
of
people,
and
everything
got
done
like
the
issue
for
like
creative
securely.
The
things
we
need
to
do
was
like
open
and
closed
in,
like
a
matter
of
hours.
I
don't
think.
A
We've
ever
gotten
a
whole
release
completely
finished
like
that
quickly
before,
like
not
only
all
the
stuff
you
have
to
do
before
and
during
it,
but
also
all
the
stuff
after
so
thank
you
Gregory
from
mysteriously
appearing
till
it
closed
that
one
out.
That
was
great
and
thank
you
Jeff
for,
like
maintaining
all
of
the
up
streams.
We
have
in
all
the
various
locations
earlier
than
anticipated,
so
that
was
that
was
fantastic,
so
good
work,
everybody
and
getting
that
organized
have
done.
Yeah.
C
And
I
shout
out
to
the
Drupal
folks
that
also
helped
us.
We
had
a
lot
of
tremendous
help
from
Michael
Hess,
whose
security
team
I'm
not
sure,
if
he's
the
lead
on
the
security
team,
but
he
does
a
lot
of
coordination,
huge
thanks
to
Michael
for
reaching
out
and
letting
us
do
a
lot
of
testing
on
the
patches
prior
to
the
release.
Pr
orga,
who
actually
not
only
was
thinking
about
backdrop
but
actually
rolled
the
initial
backdrop
patch
on
in
the
security
issue,
cue
over
on
drupal.org
and
also
gaming,
mckenna,
who
made
the
suggestion
hey.
C
C
So
yeah
thank
you
as
always
to
the
triple
security
team
for
their
wonderful
openness
and
letting
backdrop
collaborate
on
fixes
together,
so
that
really
it
really
was
kind
of
a
feel-good
like
even
for
a
terrible
situation
like
Oh.
Anybody
can
take
over
any
Drupal
site
that
has
ever
been
created
in
the
last
decade,
like
that's
a
bad
situation,
but
it's
really
great
to
see
the
community
come
together
and
just
you
know
here.