►
From YouTube: Backdrop Weekly Apr 5th
Description
Today’s development agenda: https://bit.ly/2Ifhi6Q
A
A
The
goal
is
to
make
easier
for
people
to
find
modules
that
they
need
to
use
on
their
backdrop
sites,
so
they
can
tell
if
the
modules
are
currently
sitting
on
their
Drupal
sites
are
supported
already
or
not,
but
we
also
want
to
make
it
easier
to
find
modules
that
you
don't
need
to
use
on
your
backdrop
site.
So,
if
you
type
in
something
like
redirect,
we
should
say
this
module
is
now
included.
In
course.
A
So
you
don't
think
that
that
module
is
not
ready
for
you
yet
on
backdrop,
and
we
do
have
a
content
type
on
the
site
called
a
project
placeholder.
That
is
intended
to
do
exactly
that,
but
there's
something
about
the
way
our
search
works
that
doesn't
actually
return
those
results
when
you're
looking
for
projects.
So
we
have
some
kind
of
usability
improvements.
We
need
to
add
to
those
pages,
as
well
as
some
new
designs
they're
coming
soon.
We
could
use
some
help
with
that.
If
anyone
is
interested
in
working
on
those
issues
there.
A
In
the
backdrop
CMS
Network
issue
queue,
all
of
our
code
is
in
github.
It
should
be
fairly
easy
for
people
to
grab
that
we
also
have
sanitized
backups
of
the
database
created
everyday.
If
you
want
to
grab
a
copy
of
that,
I
think
someone
get
her,
we
can
tell
you
how
to
grab
it,
we're
also
working
on
the
forum
site.
The
one
remaining
feature
we're
going
to
be
adding
there
and
then
near-term
is
a
search
box
search
functionalities
already
there,
but
the
search
results
need
a
little
styling.
So
who
wants
to
work
on
that?
A
Things
that
were
working
on
for
the
next
release
of
backdrop
CMS
itself,
so
we
have
items
for
a
backdrop.
One
point
nine
point,
four,
which
would
be
the
next
bug
fixed
release
of
backdrop,
and
we
have
two
items
that
we're
hoping
to
get
in
for
that
release.
One
of
them
is
to
fix
database
credentials
that
might
have
been
working
in
a
previous
version
of
backup
that
are
no
longer
working
now
if
they
can
attain
a
funny
character
like
a
hash
symbol.
So
we
have
a
fix
for
that.
A
A
quick
fix
for
that,
but
we
want
to
include
something
that
will
throw
a
message
on
your
status
report.
If
you
have
a
database
password
that
contains
a
funny
character
that
might
cause
problems
so
that
it
will
notify
you
need
to
change
your
database
password
possible.
That
would
be
great
to
get
in
for
that
fix
and
then
the
other
fix
we
have
is
for
automated
email
messages.
It
is
the
messages
that
go
out
when
you
build
a
new
site
or
you
set
up
your
first
user
account
or
you
do
a
password
reset.
A
The
website
will
email
you
messages
and
if
you
had
upgraded
your
website
from
Drupal
7,
the
line
breaks
and
those
messages
got
converted
incorrectly
to
the
actual
characters
front,
slash
n,
instead
of
an
actual
line
break.
So
we
have
a
fix
for
that.
That
will
just
adds
another
update
hook
so
any
site,
that's
updating
from
Drupal
7
will
get
their
emails
fixed
and
that
one
I
think
is
ready
to
go,
but
the
poor
across
those
marked
needs
review.
A
So
we'd
have
someone
test
it
up
grave
site
from
Drupal
7
and
then
send
an
email
and
make
sure
it
comes
correctly.
Formatted
and
those
are
both.
So
you
for
the
next
version,
the
next
bug-fix
version
and
backed
up
for
just
1.9
point
for
the
next
major
arc.
Sorry,
the
next
minor
version
of
bachata,
which
is
one
point
ten
point
which
is
currently
due
out
may
fifteenth
feature.
Phrase
will
be
made.
First,
has
two
major
sections
of
focus.
A
The
first
one
is
around
improving
translation
and
there
are
three
issues
that
we've
been
talking
about
for
a
while
that'll
improve
translating
one
of
them
is
translating
menu
items.
One
of
them
is
translating
blocks,
and
one
of
them
is
translating
configuration
and
it
looks
like
the
block.
Translation
issue
is
still
marked,
ready
to
be
committed
or
reviewed
and
tested
by
the
community,
but
both
menu
item
and
translation
and
complete
translation
issues
are
Marcus
needs
work,
I'm
not
up
to
date
with
what's
going
on
in
those
issues,
but
I
own,
encourage
anyone.
A
That's
interested
to
have
a
look
and
see
how
close
those
are.
I
have
a
feeling.
A
lot
of
them
are
pretty
close,
so
it'd
be
great
if
we
could
get
all
of
those
fixes
in
for
1:10,
but
that
doesn't
mean
these
would
have
to
be
in
probably
before
the
first,
because
these
are
fairly
substantial
changes,
but
I
would
check
those
issues
and
see
if
they're
marked
as
new
features
or
bug
fixes
to
see
when
we
can
get
those
in
another
set
of
things.
A
A
One
of
them
is
fixing
the
incident
filter
on
the
modules
page
so
that,
if
you
type
in
something
like
categories
you'll
be
able
to
find
taxonomy,
another
one
is
adding
tags
for
modules
so
that
if
you
have
a
module
that
would
fit
into
perhaps
more
than
one
category
or
maybe
a
category
that
is
not
available
on
the
as
a
project
on
the
modules
page
you'll
still
be
able
to
search
for
all
modules
that
might
be
in
that
group
and
there's
a
long
outstanding
issue.
That's
issue
number
37
irie
rolled
the
pull
request.
A
A
If
we
do
add
so
I'm
a
little
bit
worried
about
adding
that
functionality
without
actually
using
it
because
I
don't
want
to
add
it
incorrectly,
so
be
good
to
figure
out
exactly
what
we're
going
to
be
doing
on
the
backdrop
site.
What
github
will
be
doing
like
how
we
can
actually
handle
all
of
those
screenshots
to
show
people
better
examples
of
what
modules,
themes
and
layouts
are
doing,
and
there
might
be
some
more
changes
necessary
for
layouts
as
well?
A
If
you're
curious
to
look
at
all
of
the
issues
that
we're
working
on
there
Slater
for
110,
we
have
a
milestone.
You
can
check
in
a
github
issue
queue,
but
if
there's
something
else
that
starts
getting
a
bunch
of
attention
that
isn't
necessary,
illah
slated
for
1:10.
That
doesn't
mean
it
can't
get
in,
and
a
great
example
of
that
is
right.
Now
we
have
a
new
meta
just
got
created,
that
is
about
improving
the
contact
form
in
core,
and
that
issue
is
3023.
A
It's
something
that
there's
been
kind
of
a
lot
of
griping
about
the
contact
form
module
recently,
and
it
would
be
great
if
we
could
figure
out
all
the
issues
that
we
want
to
get
resolved
and
see
how
many
of
those
we
could
get
included.
I'm,
not
sure
any
of
them
are
gonna,
be
ready
for
110,
but
the
fact
that
that's
getting
a
lot
of
attention
means
that
it
might
be
something
that
would
be
on
the
list
for
111.
A
So
if
that's
something
you're
passionate
about
and
be
more
passionate
about,
then
configuration
translation
or
module
search,
page
improvements
and
that's
another
place
where
you
could
definitely
use
focus
if
you're
curious
about
what
backdrops
long-term
plans
are
you're.
Welcome
to
view
the
roadmap,
our
website
I'm
not
sure
we
necessarily
have
super
long
term
plans
just
because
we
tend
to
adapt
based
on
what
the
community
finds
most
pressing
on.
But
you
can
at
least
get
an
idea
of
what
we've
done
before
in
terms
of
the
kinds
of
changes
were
likely
to
implement
in
future
and
I.
A
Think
that's
it
for
pack
drop
the
prod
project
product
Nate
usually
does
this
part
of
the
meeting,
but
he
is
unavailable
today.
So
I
tried
to
do
the
best.
I
can
I'm
again
not
completely
up
to
date
on
where
all
of
those
issues
are
so
I'd
encourage
anyone
who's
interested
in
looking
up
to
take
a
look
at
their
issues
on
get
Jeff
is
also
not
here
today.
So
usually
he
would
give
us
a
quick
update
on
the
back
job
for
good
project
and
how
it's
coming
along.
A
A
No
thoughts,
everybody's
muted,
I,
don't
know
if
you
have
thoughts
and
you're
talking
into
your
music
microphone.
If
you
don't
have
thoughts,
that's
also
fine
I'm,
good.
Okay,
you
never
know
someone's
like
oh
I
was
talking
for
a
minute.
I
doubt
you're
thoughtless,
but
I
would
say
you
don't
have
to
have
anything
to
say.
If
you
don't
want
to
I,
just
think
if
we
give
you
an
option,
so
that's
all
we
have
for
today's
meeting.
I
guess
it's
short
and
sweet
I
am
actually
excited
about
that.
Cuz
I'm
gonna
go
make
some
progress.