►
From YouTube: Backdrop weekly 8/28
Description
Backdrop CMS
A
All
right
happy
thursday,
everyone.
It
is
backdraft
day
again
as
usual
backdrop.
Cms
is
a
full
featured
content
management
system
intended
primarily
for
non-profits
and
small
to
medium
businesses.
We
are
working
on
creating
a
product
that
has
comparable
features
with
triple
eight
on
an
architecture,
that's
more
similar
to
drupal
seven.
So
when
backdrop
one
is
released,
it
won't
have
all
of
the
same
features
as
triple
eight,
but
we
are
planning
on
doing
regular
releases
shortly
thereafter.
So
we
should
be
adding
all
those
features
in
the
coming
months.
A
We've
got
a
couple
of
major
release,
blockers
that
we're
going
to
talk
about,
and
then
after
1.0.0
comes
out,
we're
going
to
be
releasing
regular
versions
every
few
months
after
that,
so
for
major
new
things
that
we're
working
on
and
that
are
currently
blocking
the
release.
The
biggest
thing
is
the
new
blocks
and
layout
system.
This
is
something
that
drupal
8
doesn't
have.
A
Yet
it's
something
that's
been
in
the
in
the
plans
for
a
really
long
time,
but
they
aren't
actively
working
on
it
that
we
know
and
what
we're
going
to
be
able
to
do
is
separate
the
layout
of
content
from
the
theme
by
having
our
new
box
and
layout
system.
So
where
you
put
things
on,
the
page
will
be
managed
in
a
different
interface
than
you
know.
A
A
So
far,
we've
made
a
lot
of
progress
with
the
blocks
and
layout
system.
We've
got
nate
working
on
replacing
the
current
themes
block
system
with
the
layout
system,
and
I
started
on
some
conversions
from
plugins
in
in
panels.
We
don't
have
any
updates,
I
think
on
that
since
last
week,
but
we
are
kind
of
trudging,
along
with
with
moving
that
forward.
A
For
example,
we've
got
actions
that
need
to
be
turned
into
these
book
operations
tasks,
so
we've
got
kind
of
a
list
of
complicated
things
there
that
need
to
be
done
as
well
as
just
building
the
pages
of
you
and
the
other
thing
that
is
going
to
change
everybody's
life.
If
you're
a
drupal
7
developer.
A
Now
we've
got
config
management
cmi,
as
it's
known
in
in
drupal
8,
and
the
config
management
initiative
is
also
in
backdrop,
though
it's
done
slightly
differently
for
backdrop
and
though
the
the
core
system
is
in
and
views
is
saving
its
config
into
config
files
instead
of
into
the
database.
There
are
a
bunch
of
other
major
systems
in
core
that
have
not
been
converted
yet
primarily
content
types
and
fields
which,
without
having
content,
types
and
fields
and
config,
you
don't
really
have
config.
A
So
we
need
to
get
those
converted
and
those
are
going
to
be
kind
of
complicated,
hairy,
conversions
and
there's
some
other
systems
too.
That
need
to
be
converted
as
well,
that
aren't
quite
as
as
hard
but
do
need
some
attention,
and
so
those
are
the
three
major
things
that
we're
working
on
that
are
preventing
release.
Getting
boxing
outs
done
getting
views
converted
as
much
as
possible
and
I'm
not
sure
that's
an
entirely
release
blocker.
A
A
So
in
drupal
7
we've
got
three
security
issues
that
need
to
be
resolved
in
backdrop,
and
we
have
a
handful
of
commits
that
have
been
made
to
core
that
also
need
to
be
ported
over.
I'm
gonna
wrap
up
the
724
to
727
issue
today
after
this
call
and
get
those
closed
out,
I
think
there
might
be
a
pull
request
for
that
already,
but
I
don't
think
it's
passing
tests
and
then
the
728
to
31.
These
are
the
more
recent
versions
of
drupal.
7
have
a
handful
of
new
issues.
A
A
We've
made
a
bunch
of
progress
on
this
since
last
week
we
have
48
out
of
the
50
issues
that
we've
identified
as
being
important
completed,
which
is
great
and
then
in
javascript,
there's
just
a
bunch
of
tasks
of
running
js
hint
on
the
code
and
getting
everything
cleaned
up
and
reorganized
into
the
correct
positions
and
there's
a
handful
of
those
that
are
left
as
well.
These
are,
of
course,
not
release
blockers,
but
they
are
fairly
important
in
terms
of
making
our
code
easy
for
people
to
work
with
in
the
future.
A
So
we
have
so
far
updated
the
installer,
we're
working
on
rebranding,
the
administration
theme
and,
more
recently,
what
we've
started
doing
is
is
or
what
we
have
done
already
is
renamed
every
instance
of
drupal
and
core
with
backdrops.
So
it
doesn't
say
drupal
linear,
which
is
good,
and
what
we're
doing
right
now
is
trying
to
choose
a
new
mascot.
A
We
have
converged
on
the
idea
that
backdrop
should
have
a
dragon
as
a
mascot,
and
we
think
that
that'll
be
a
lot
of
fun
both
for
drupal
developers
to
kind
of
poke
fun
at
backdrop
and
be
like
oh
there'd,
be
dragons
right,
but
also
a
lot
of
fun.
For,
for
for
backdrop
to
just
kind
of
have
a
kind
of
a
icon,
an
identity
of
its
own.
It
seems
to
be
really
fitting.
A
We
want
to
name
our
dragon
drop,
so
he's
drag
and
drop,
which
is
kind
of
clever
if
you're
nerdy
and
I
don't
know,
nate
spent
a
lot
of
time-
writing
drag
and
drop,
so
there's
kind
of
a
back
history
there
too,
and
so
we
love
the
idea
of
dragon.
I
just
personally
love
dragons.
I
just
hadn't
thought
of
it
as
a
backdrop,
icon,
mascot
thing,
but
as
soon
as
somebody
mentioned
it
I
was
like.
Yes,
we
need
that.
A
A
Primarily,
we
have
been
going
through
and
removing
and
renaming
things
so
cleaning
up
like
the
names
of
the
menus
and
making
sure
that
things
are
kind
of
intuitive.
When
you
use
the
user
interface
like
making
sure
it
says
edit
when
you
want
to
edit
and
configure
when
you
want
to
configure
and
doesn't
get
those
backwards,
and
I
think
it's
kind
of
going
to
make
it
a
little
bit
more
intuitive
for
people
to
get
in
and
start
working
with
it.
So
I
know
that
last
week
I
created
like
10
or
15
issues.
A
A
Some
of
them
are
things
that
we
just
thought
up
for
backdrop.
We
were
like
how
are
we
going
to
solve
this
problem
like
oh?
If
we
just
remove
the
navigation
menu,
then
everything
will
be
fine,
because
there's
just
some
some
simple
cleanup
on
stuff,
like
that
going
on
too
another
thing
that
we're
gonna
work
on
is
adding
a
rich
text,
editor,
which
is
super
important,
but
again
if
it's
not
a
release
blocker,
so
it
might
not
be
done
before
we
release
backdrop,
but
we
will
eventually
get
a
rich
text
editor
in
core.
A
If
somebody
wants
to
help
us
with
that
sooner,
we
would
love
getting
it
in
sooner
but
again,
we've
got
other
things
that
are
currently
more
important
and
the
last
major
thing
that
we're
working
on
is
theme
system
cleanup.
I've
also
got
a
couple
of
full
requests
going
on
these,
where
we're
gonna
be
doing
things
like
removing
the
process,
layer
and
that's
kind
of
a
doozy.
It
requires
kind
of
rethinking
how
we
deal
with
our
template
files,
which
of
course
fits
in
with
our
new
blocks
and
layouts
theme
system.
A
So
there's
a
lot
of
kind
of
chicken
and
the
egg
stuff
going
on
there,
where
I'm
doing
some
cleanup
in
terms
of
moving
around
where
things
are
called,
but
we've
got
to
wait
until
we
get
our
new
page
rendering
engine
in
before
we
can
make
the
final
changes
there,
but
there
are
a
bunch
of
other
stuff
in
theme
system.
Cleanup
too,
that
we
have
been
working
on
like
consolidating
template
files
and
and
making
things
make
a
little
bit
more
sense.
A
But
then
the
major
overhaul
is
going
to
wait
until
after
blocks
and
notes
are
done.
It's
also
less
important.
Locksmiles
is
a
release
blocker
and
the
theme
system.
Cleanup
is
a
good
improvement,
but
it's
not
going
to
hold
up
our
release
either
so
lots
of
stuff
going
on
the
next
section
of
this
meeting
is
supposed
to
be
for
updates
from
the
pmc.
A
All
right
so
just
kind
of
business
as
usual,
and
then
we
are
working
on
a
couple
of
things
that
are
not
related
to
the
code
of
the
backdrop
project
itself.
We've
got
an
api
website
underway,
it's
actually
showing
our
apis,
which
is
good.
It
needs
a
little
theme
love.
So
I
was
going
to
see
if
I
could
just
drop
the
theme
from
our
public
facing
site
onto
the
api
site
today.
A
I
just
got
access
to
it
yesterday,
so
hopefully
we
can
do
that
and
then
I
know
lucas
is
currently
working
on
setting
up
change
records
there.
So
as
soon
as
we
get
that
content
type
built,
then
we're
going
to
need
a
bunch
of
hands-on
deck
to
help
create
the
change
records
so
that
people
who
are
reporting
modules
to
be
able
to
see
what
is
different
about
our
apis.
A
A
We
need
to
build
that
and
then,
of
course,
we've
got
our
own
website,
which
is
going
to
need
a
redesign
we're
going
to
try
and
get
that
done
kind
of
in
conjunction
with
the
release
of
the
product.
So
right
now
it's
obviously
less
of
a
priority
than
actually
getting
backdrop
out,
but
we
have
talked
to
a
couple
of
designers
about
helping
getting
designs
ready
so
that
at
least
when
we're
ready
to
implement
it,
we
have
something
to
run
with,
so
that
should
be
getting
underway
in
the
next
few
weeks.
A
Here
too
other
stuff,
let's
see
so
every
thursday
we
have
a
little
sprint
after
this
meeting.
So
today,
starting
in
10
minutes
or
so
nate
now
be
around
and
we'll
be
working
on
back
trip.
If
you
want
to
jump
in
and
help,
we
would
love
to
have
you
we're
also
going
to
be
doing
in-person
sprints
when
we
can
not
this
coming
weekend,
but
next
weekend
we're
going
to
a
camp
drooper
camp
la
in
southern
california
and
they
have
a
designated
like
meeting
area,
but
it's
not
necessarily
an
official
sprint.
A
A
So,
if
you
want
to
come
and
work
with
us,
then
it
is
still
to
be
determined
whether
we're
going
to
be
working
at
that
point
on
backdrop
1.0
or
1.1,
because
it
could
be
that
backdrop
has
been
released
by
november
and
what
we're
doing
is
working
on
adding
new
features
or
getting
in
you
know.
Little
tiny,
I
don't
know
like
ck
editor.
A
There
are
things
that
don't
require
api
change,
but
we
could
also
be
doing
like
bug
fixes
on
on
minor
versions
or
I
don't
know
what
our
plan
is
yet
for
that
far
in
the
future.
So
I
would
encourage,
if
you
want
to
do
some
sprinting,
do
it
with
us
on
thursdays
and
we'll
try
and
come
up
with
another
in
place
in
in-person
sprint
before
november
as
well.
We
are
probably
going
to
be
attending
the
pacific
northwest
drupal
summit
in
october.
A
I
don't
know
if
they
have
a
designated
sprint
day
or
not,
and
I
don't
know
if
we'd
be
able
to
sponsor
it
or
welcome
to
participate,
but
I
will
reach
out
to
them
and
see
what
the
plan
is
for
that
and
then
I
guess
we
could
organize
our
own
sprint
if
we
needed
to
that's
not
associated
with
a
drupal
event,
but
so
far
that
is
not
currently
on
the
agenda.
So
we're
just
gonna
do
as
much
as
we
can
from
here
for
now
and
we'll
see
where
we
end
up
nate.
A
I
know
you've
got
a
ton
of
full
requests
on
your
plate,
so
thank
you
for
reviewing
all
those
yeah.
One
thing
I
do
want
to
say
is
that
we
had
a
really
great
intern
all
summer,
a
kid
from
the
high
school
that
I
went
to
came
and
worked
for
us
for
like
a
month
as
an
internship
as
part
of
his
high
school
program,
and
then
he
stayed
on
and
he
worked
on
bachelor
first
all
summer.
A
I
was
a
hello,
mr
cat,
if
you
seen
him
in
in
irc,
and
he
was
absolutely
amazing
and
he
left
he's
leaving
this
week
to
go
to
college.
So
I
just
wanted
to
like
say
thank
you
so
much
for
all
of
paul's
help
and
we
hope
he
comes
back
at
winter
break
or
you
know.
If
he's
got
down
time,
that
would
be
amazing
but
yeah.
So
he
was.
A
He
was
definitely
a
force
in
our
pull
request
queue,
and
so
I'm
really
happy
to
have
had
him
and
said
that
he's
gone,
but
college
is
important.
It's
fun,
so
you
should
go,
have
fun
with
that
and
worry
about
backtracking
later,
okay.
Well,
I
guess
that's!
It's
kind
of
a
short
meeting
today,
just
because
we've
been
kind
of
heads
down
for
a
while,
but
we
will
make
an
announcement
about
the
dragon
when
we
have
one.