►
From YouTube: Backdrop Weekly Feb 8th
Description
Today’s development agenda: http://bit.ly/2E8mL0U
A
All
right
we're
on
air.
It
is
Thursday
February
8th.
This
is
a
meeting
to
check
in
on
active
development
tasks
or
a
backdrop
CMS.
On
top
of
our
meeting
here,
updates
to
the
community
software
Conservancy.
It's
excited
to
get
us
on
board
and
I
should
be
hearing
from
Karen
this
week
about
what
our
next
steps
will
be.
So
that's
really
great
I
expect
to
see
some
blog
posts
and
newsletters
about
what
that
means
for
everyone
backed
up
community
coming
soon.
A
In
the
past
week,
we've
had
a
couple
of
new
projects
for
backdrop,
Jeff
Town
breadcrumbs
this
one
I
mentioned
last
week,
which
is
super
crazy
and
complicated,
but
kind
of
cool.
You
want
to
give
it
a
try
and
Auto
menu
settings
something
someone
else
made
last
week.
We've
also
had
a
ton
of
new
releases
of
existing
projects
in
the
last
week,
including
file
filled
sources
back
up
in
my
grade
table
filled
rabbit,
hole
and
coder
review.
A
So
thank
you
to
all
of
our
maintainer
for
containing
to
a
great
job
on
making
updated
releases
of
existing
projects
working
on
backed
up
CMS
to
org.
We
currently
are
thinking
about
how
to
fix
our
modules,
themes
and
layouts
pages
to
make
searching
for
existing
projects
easier
and
more
straightforward,
and
also
possibly
to
reveal
more
information
about,
for
example,
projects
that
you
don't
need
to
use
on
backdrop
anymore,
so
we're
looking
at
how
we
can
improve
our
search.
A
We
are
also
trying
to
wrap
up
the
remaining
few
changes
that
go
along
with
our
new
homepage
design.
So
we've
got
a
try
new
backdrop,
page
and
Jeff
might
look
at
your
request.
Yesterday,
I
thought
it
looks
really
great
I
liked
the
silo
changes,
but
I
had
some
thoughts
about
how,
as
we
have
more
tools
that
will
allow
people
to
run
backdrop.
A
We
should
probably
build
that
page
as
a
layout
interview,
so
we
can
just
add
a
new
node
and
it'll
automatically
appear
there
so
before
I
wanted
to
merge
it
as
it
was
I
was
like
well,
let
me
think
about
it
see
if
we
can
come
up
with
a
kind
of
more
architected
solution
to
that
page.
That'll
still
match
the
designs,
which
is
the
hard
part.
So
I
want
to
take
a
look
at
that
today.
A
That
explains
what
add-ons
are,
but
I
wanted
to
ask.
If
you
guys
thought
we
should
add
a
section
for
installation
profiles
or
recipes,
so
installation
profiles
exist,
but
we
don't
have
any
for
backdrop
other
than
what's
in
core
and
recipes
don't
yet
exist,
but
we
want
them
to
you
think
we
just
leave
those
off
of
that
page
for
now
and
just
focus
on
module
states
and
layouts.
Or
do
you
think
we
should
mention
that
profiles
that
you
might
have
you
sent
Drupal
7
will
so
work
on
back
job.
B
Installation
profiles
are
actually
a
bit
of
work
because
at
least
the
way
that
work
on
drupal.org
is
that
you
included
rush,
make
file,
and
then
that
specifies
all
of
your
dependencies
and
then
the
packager
assembles
all
of
the
dependencies
and
your
profile
altogether
for
you.
So
that
would
require
some
effort
on
our
part,
to
probably
port
that
functionality
over
from
Drupal
8
org.
But.
A
A
A
B
A
In
theory,
so
what
I
want
to
and
what
I
want
on
the
landing
page
s?
Obviously,
we
should
mention
modules,
themes
and
layouts,
which
we
need
to
explain,
but
there
are
a
bunch
of
people
who
are
evaluating
backdrop
who
are
trying
to
figure
out
figure
out
like
can
I
move
my
existing
infrastructure
over
and,
if
they're,
using
an
install
profile.
A
I
want
to
explain
that,
like
backdrop
still
supports
install
profiles,
but
not
in
a
way,
that's
like
download
your
install
profiles
here,
because
we
don't
actually
have
that
functionality
on
backdrop,
CMS
network,
so
maybe
I'll
make
a
draft
of
that
page
and
put
a
link
up
for
people
to
review,
to
make
sure
that
what
I'm
saying
is
accurate
as
well
as
not
technically
overwhelming.
It
needs
to
be
kind
of
short
and
concise
and
says:
yes,
you
have
to
port
them.
You
can't
find
them
here.
B
B
A
If
we're
gonna
have
an
add-ons
page,
I
wanted
it
to
cover
all
of
the
things
people
might
be
trying
to
add
on
to
their
site,
and
then
we
compare
that
to
the
way
Drupal
works.
Installation
profiles
is
one
of
those
things.
That's
that's
gonna
be
one
of
the
things
people
are
gonna,
be
coming
to
that
page.
To
learn
about
so
I
thought
just
having
a
paragraph
at
the
bottom.
That
says
this
is
what
it
is,
would
be
good.
A
A
B
It
yeah
so
I
was
thinking
that
we
have
some
descriptions
about
what
topics
like
what
cons
sar
in
the
handbook
break.
Our
handbook
and
I
think
that
describing
installation
profiles,
because
that's
a
concept
impact
job
would
be
suitable
underneath
the
handbook
and
so
yeah.
You
write
them,
maybe
including
like
on
the
main
add-ons
page,
like
talk
about
the
different
kinds
of
add-ons,
but
we
wouldn't
actually
need
a
menu
item
underneath
the
add-ons
drop
down
for
profiles,
because
there
are
none
right,
yeah,
okay,
yeah
that
sounds
good.
Okay,
so.
A
What
about
recipes?
This
is
this
idea.
It
doesn't
exist
yet
of
making
something
kind
of
like
an
install
profile
and
kind
of
like
a
feature
that
can
be
both
enabled
and
disabled
on.
An
existing
site
should
I
link
to
like
a
github
issue
where
we're
talking
about
it
or
should
I
leave
it
off
that
page
entirely.
B
A
B
A
B
A
Maybe
this
is
just
features
module
for
backdrop
yeah,
but
I
was
thinking
that
it
wouldn't
necessarily
need
features
module
to
run
it
like
if
you
could
just
drop
one
in
like
here's,
a
bundle
of
config
or
like
I'm.
You
know
how
a
feature
is
a
module
and
you
can
turn
it
on
like
if
you
could
do
that
and
not
need
to
have
a
features.
Api
yeah.
A
B
B
But
I
liked
in
the
new
version
of
features
for
Drupal
8,
actually
does
the
same
thing
where
it
basically
throws
away
all
of
this
stuff.
It
didn't
need
and
it
still
exists,
but
its
focus
is
different
and
the
number
of
people
are
gonna
be
using
features
or
recipes
or
whatever
in
backdrop
is
going
to
be
a
subset.
You
know
it's
like
actual.
It's
on
its
I
can
be
the
de
facto
way
of
doing
config
deployment
anymore,
thank
goodness,
but
it
would
just
be
providing
the
package
we
just
be.
B
What
features
was
supposed
to
do
in
the
first
place,
exactly
yeah,
so
my
feeling
on
that
is,
like
you
know,
if
there's
enthusiasm
around
it
like,
let's
make
a
backdrop
version
of
features
that
is,
you
know,
built
her
backdrop
and
built
with
89
degrees,
firm
features.
No,
because
what
features
had
been
used
for
in
all
the
Drupal
7
cycle
on
pretty
much
every
site
that
used,
it
was
for
configuration
management
right
unless.
A
A
A
Somebody
spent
a
lot
of
time
making
Miami
doc
mama,
making
the
forum
site
code
look
really
good
using
Bartok,
which
I
think
what
it's
running
right
now
so
want
to
make
sure
that
the
code
still
looks
really
good
in
the
new
theme
and
then
that's
it
for
our
websites
before
we
take
too
much
more
time.
Let's
turn
it
up
to
talk
about
upcoming
or
upcoming
release.
One
point:
nine
point:
one.
B
Yeah
so
one
point
nine
point:
one
is
the
first
bug
fix
release
for
the
1.9
version.
1.9
came
out
last
month
on
January
15th,
and
so
one
point.
Nine
one
will
come
out
with
a
couple
of
fixes
that
we've
discovered
since
the
last
minor
release,
one
of
which
we
have
a
fix
for
its
issued
29:43,
which
is,
if
you
upgrade
to
1.9
and
you're.
B
Not
already
logged
in
visiting
the
login
page,
doesn't
work
and
tell
you
either
clear,
caches
or
run
update
whp,
but
those
things
can
be
difficult
if
you're
not
logged
in
so
we
have
a
fix
for
that.
The
fix
is
a
little
bit
strange,
but
it's
it's
marked
our
TBC.
It's
kind
of
an
unusual
exceptional
situation.
B
B
B
That
one
is
a
thorny
issue.
So
what
we
may
end
up
doing
is
pushing
at
1.91
pretty
much
right
away,
because
the
user,
login
page
fix,
seems
like
that's,
ready
to
go
and
the
database
credentials
one.
It
might
take
us
a
little
longer
to
figure
out
a
solution
there.
Any
ideas
as
to
how
to
solve
that
problem.
Please
post
your
thoughts
to
issue
2904
and
that's
the
database
credentials
one.
So
we've
got
a
little
bit
of
discussion
and
some
ideas
back
and
forth,
but
yeah
we
haven't
landed
on
anything
that
that
gracefully
solves
the
problem.
B
B
So
the
last
four
requests
from
that
issue
just
before
the
meeting,
which
means
for
the
first
time
in
quiet
a
long
time
backdrop
one
point:
nine
point:
one
will
be
entirely
up-to-date
with
the
latest
version
of
Drupal,
so
we'll
have
full
parity
between
everything
that
applies
to
Drupal
will
also
be
applied
to
backdrop,
so
that'll
be
great,
that'll,
be
a
1.9
one
and
the
date
for
doing
that-
probably
probably
really
soon.
Next
couple
of
days,
maybe
as
soon
as
tomorrow
and
always
late
is
Monday.
B
B
The
other
area
of
focus
for
one
point
10
is
internationalization
and
translation
improvements.
We
have
issue
225
that
makes
menu
items
translatable.
The
status
of
that
is
that
the
PO
request
is
confirmed
as
working
and
functional
and
actually
approved
in
all
ways,
except
that
there's
some
minor
terminology
updates,
so
that
one
seems
like
it's
really
really
close
and
just
needs
a
reroll
just
to
adjustment
terminology.
B
The
other
item
that
we're
looking
at
really
improving
and
translation
is
config
translation,
which
is
issues
issued
704
and
the
status
of
this
one
is
still
more
in
the
like.
We
have
the
conceptual
battle
plan
for
this
and
we
actually
have
a
kind
of
some
proof
of
concept,
pull
requests,
but
we
have
a
lot
of
work
to
do
there.
We
have
an
overall
plan,
but
we
need
to
back
that
up
with
some
implementation.
B
A
This
Shiva
self
has
been
around
for
a
while.
We
haven't
talked
about
it
for
a
while,
which
is
like
you
haven't
heard
about
it
recently,
but
it
is
something
that
I
think
based
on
our
recent
survey
and
realizing
that
people
are
struggling
with
module
since
and
layouts.
It
would
add
a
lot
of
value,
especially
in
the
penis
area,
but
also
two
modules
and
Lance.
Oh.
B
A
Make
sense
if
we
could
get
our
github
integration
working
so
that
we
can
control
access
so
that
project
maintainers
can
edit
the
notes
on
Vectra
semester
org,
but
we
don't
have
that
integration
yet
so
right
now,
the
only
tool
that
maintainer
x'
have
to
add
screenshots
is
to
put
them
and
they
get
have
repository.
So
I
have
no
preference,
whether
we
do
it
one
way
or
the
other.
We
just
need
to
figure
out
how
to
do
it.
Whichever
way
we
choose
to
do
it,
yeah.
B
We
could
make
it
because
edit
permissions
or
per
content
type
I
mean
yeah.
Maybe
github
integration
could
have.
Integration
would
definitely
be
better,
but
because
can't
rip
access
gives
you
actually
access
to
all
modules
right
now
all
contributes
like
if
you
had
that
level
of
access
in
the
contributory.
You
also
should
have
the
access
to
edit
all
different
projects
on
backdrops
núñez,
org
yeah,
but.
A
B
Well,
let's
move
on
from
that
one,
it's
still
in
concept.
You
know,
we
know
what
we
want
to
achieve.
We
just
don't
know
how
we
want
to
go
about
it
yet
so
this
issue
tags
for
modules,
is
issue
number
37,
one
of
our
oldest
issues
and
that's
just
a
way
of
recategorize
in
the
modules
page,
so
that
modules
are
to
a
single
category,
I
think.
A
A
So
we
can
keep
the
official
grouping
thing
that
we
have
now
and
just
add
an
additional
value
of
tag,
and
what
we
could
do
is
we
could
use
the
tags
list
to
determine
when
we
need
to
add
a
new
official
grouping
right,
because
if
everybody
starts
adding
something
called
the
social
networking
or
whatever
it
is.
You
know
that
was
hot
like
10
years
ago,
but
we
might
need
to
say.
Oh
hey.
A
B
A
B
A
Keep
being
unable
to
find
it,
but
if
I
can't
track
it
down
with
the
screen
another
one
but
yeah
it's
so
that,
like.
If
you
search
for
categories
in
your
instant
filter
on
the
modules
page,
you
don't
find
taxonomy.
In
spite
of
the
fact
that,
like
categorization
is
the
name
of
the
group.
So
if
you
type
the
name
of
the
group,
you
don't
get
any
results
where
I
think
that
it
should
search
the
project
name
as
well
as
the
module
name
in
the
sorry
at
the
package
name.
Well
as
the
module
name
in
the
description.
B
C
Larenz
been
doing
good
work
working
with
our
partner,
my
plays
better
in
Memphis,
and
we
met
Tuesday
with
hack
for
Western,
Mass
and
I
introduced
that
as
a
topic,
a
project
that
people
could
work
on
and
we
got
a
couple
punched
there.
So
we
have
some
motion
both
in
getting
specifications
in
some
code.
Moving.
B
And
still
again,
just
a
great
initiative
they're,
basically
simultaneously
giving
our
community
members
projects
to
rally
around
and
also
building
our
backdrop
websites
out
there
for
good
causes,
so
yeah
really
great
idea:
okay,
I
think
that's
it.
We've
got
some
general
discussion
open
Q&A.
If
you
guys
have
anything
that
you
guys
would
like
to
add
that
we
haven't
brought
up
on
air
anything
else.
You
guys.
A
So
I
haven't
told
everybody
about
this
yet
but
I
emailed
fastly
earlier
this
week,
because
I
was
looking
at
setting
up
a
CDN
for
a
ton
of
my
clients
and
the
guy
who
responded
sent
me
a
link
to
and
blog
post
they'd
written
fairly
recently
about
how
fastly
is
trying
to
support
more
open
source
projects
in
2018
and
so
I
emailed
community
at
fastly,
calm
and
said.
We're
an
open
source
project
and
we'd
love
your
support
and
they
wrote
back
and
said
as
long
as
you're,
not
monetizing
traffic
on
vector
of
CMS
org.
A
They
would
be
very
happy
to
help
us
and
so
I've
started
the
process
of
getting
backdrop
and
all
of
backdrops
properties.
So
the
API
side,
the
forum
site,
the
main
site
and
the
localized
site
using
the
fastly
CDN,
and
then
we're
gonna
write
about
blog
post
about
them
supporting
open
source
and
they
will
probably
write
a
blog
post
about
supporting
the
backdrop,
although
it
might
be
supporting
these
eight
projects,
depending
on
how
many
other
people
they've
adopted
at
the
same
time.
A
So
I
just
want
to
say
that
was
really
exciting,
because
fastly
is
also
providing
CDN
services
for
Drupal,
so
I
think
it's
something
that
the
Drupal
community
is
going
to
be
aware
of,
and
the
fact
that
they're
gonna
work
with
backdrop
as
well.
It's
also
super
exciting,
so
excited
there.
Oh
and
since
the
last
time
we
spoke,
D
dev
has
committed
native
backdrop,
support
into
their
local
development,
environment
and
that'll
go
out
with
a
next
release,
which
will
be
next
Tuesday.