►
From YouTube: Backdrop Weekly - 5/15
Description
Today's agenda: http://bit.ly/Qk3DzE #BackdropCMS
A
Alright,
we
are
on
air,
happy
Thursday
everybody
its
backup
day
this
week,
we're
working
on
a
whole
bunch
of
new
stuff
with
our
bactrim
interns,
just
really
exciting.
So
I'm
not
sure.
Are
you
guys
watching
the
live
feet?
Are
you
trying
to?
You
can
join
the
hangout
of
two?
If
you
can
figure
out
how
or
you
can
keep
working
on
your
patches?
That's
fine,
too
we're
all
here
in
spirit,
even
though
maybe
not
in
the
wife
Ganga.
A
So
we
are
here
today
to
talk
about
backdrop
CMS,
which
is
a
content
management
system.
That's
based
on
Drupal.
We
are
creating
a
new
CMS
that
has
Drupal
8
comparable
features
on
a
Drupal
7,
like
architecture
well
include
bug
fixes
both
from
Drupal
7
and
Drupal
8,
as
well
as
anything
else
that
we
find
long
way
and
we're
possible
we're
going
to
try
and
simplify
existing
systems
and
add
new
features
when
we
don't
need
to
do
too
much
API
change
to
do
so.
A
So
the
general
idea
is
that
there's
a
cost
that
comes
with
change
and
drew
blades
changing
too
much
drupal
7
is
very
successful
platform,
so
we
would
like
to
continue
moving
Drupal
7
forward,
which
is
not
an
option
with
the
actual
Drupal
7
product.
So
we've
created
a
new
product
called
back
drop
the
whole
hours
to
take
the
software
that
we
know
and
love
and
continue
to
make
improvements
and
changes
to
that
existing
software
for
a
timeline.
We're
going
to
be
releasing
backdrop
one
sometime
this
summer,
we're
thinking,
June
or
July.
A
We've
got
a
couple
of
critical
issues
that
are
blocking
our
release
that
we're
hoping
to
get
done
soon
and
then
we've
got
a
lot
of
nice
to
have,
but
we'll
be
trying
to
do
as
many
as
we
can
before.
We
can
release
the
software
in
terms
of
our
progress.
We
have
been
keeping
track
of
all
of
the
changes
that
are
happening
to
both
Drupal
7
Andrew
White
in
terms
of
Drupal
7.
We
have
to
meta
issues
left
where
we
need
to
take
the
changes
that
happen.
7
include
them
in
backdrop.
A
We
have
one
minor
security
problem
that
needs
effects
and
we
have
one
that
has
a
fixed
that
we're
still
debating
those
who
need
to
get
in
before
backdrop
is
released.
Also
in
terms
of
Drupal
8.
We
have
more
than
7,000
commits
that
have
happened
to
your
voice
since
the
time
that
we
forked
we're
currently
going
through
all
those
trying
to
figure
out
which
of
them.
A
We
actually
need
for
backdrop
when
we
have
that
established,
will
cut
the
ones
that
don't
matter
like
conversions
from
one
system
to
another
reorganizing
the
code,
refactoring
things
we
don't
need
those,
but
things
like
bug,
fixes
and
improvements.
We
would
like
to
include
those
so
we've
got
a
couple
of
sub
issues
that
we've
split
out
into
different
groups
like
improving
the
CSS
and
proving
the
JavaScript
making
things
html5
all
this
she's
related
to
cmi.
Those
are
all
separate
subtasks.
A
So
we
make
sure
that
we
cover
all
of
those,
whereas
there's
massive
amounts
of
other
changes
that
we're
not
using
and
those
live
in
Drupal
8,
meta
issues
that
will
also
be
working
on
as
time
frames
and
in
terms
of
the
major
things
that
we're
working
on
we've
got
three
huge
things
that
are
probably
most
important
for
us
to
get
done
before
release
the
first
one
is
the
blocks
and
layout
system.
We've
got
a
bunch
of
progress
on
a
user
interface
for
that
we
don't
actually
have
anything
cuts
that
make
it
go
just
yet.
A
We
have
views
in
core,
which
is
these
number
one
downloaded
and
installed
module
for
Drupal
it's
in
poor
for
Drupal
8
we're
going
to
have
it
in
corporate
backdrop
as
well.
It's
something
that
sets
backdrop
apart
from
the
competition
like
WordPress
and
expression
engine,
none
of
the
other
systems
have
a
tool
like
views,
so
it's
really
important
that
we
keep
that
make
it
easier
to
use
and
put
it
writing
for
which
is
great
and
then
the
other
new
feature
is
cmi.
A
The
config
management
initiative,
which
allows
you
to
take
your
configuration,
export
it
to
code
version
control
it
and
deploy
it
between
platforms,
so
you
can
build
a
site
locally.
You
can
deploy
your
code.
You
can
also
deploy
your
configuration
when
you
go
to
launch
and
then
long-term
maintenance.
If
you
want
to
make
changes
to
an
existing
site,
you'll
be
able
to
make
changes
to
a
configuration
deploy
this
the
same
way,
you
would
make
changes
to
coat
and
deploy
them.
A
A
A
It
appears
and
for
either
with
the
word
backdrop
or
by
removing
it
entirely
I'm,
not
sure
if
we
have
a
policy
on
whether
we're
going
to
be
always
doing
one
or
the
other
or
whether
we're
going
to
be
kind
of
deciding
case-by-case
how
that
should
be
done
and
we're
also
going
to
be
resetting
the
version
and
update
numbers.
So
right
now,
Drupal
is
running
version
7
and
is
about
to
be
running.
A
Fortunately,
drupal
8
comes
out
back
dog
was
going
to
be
running
version
one
when
it
comes
out,
so
all
of
the
modules
and
themes
and
stuff
that
goes
it
back
up
will
be
reset
back
to
one
point:
oh,
and
so
we've
got
a
patch
in
the
queue
I'm,
not
sure.
If
it's
been
committed.
Maybe
you
can
talk
to
that.
A
little
bit
that'll
help
reset
all
the
version
numbers
and
get
things
going
with
that
backwards,
compatibility
layer
for
backdrop,
yeah.
B
B
Past
backdrop,
1
point
0
and
really
set
itself
apart
in
terms
of
developing
identity.
So
to
further
that
we've
been
making
a
lot
of
progress
this
past
couple
of
weeks
to
to
really
separate
backdrop
from
Drupal
waves.
The
first
thing
we
did
that
was
really
pretty
trivial.
Is
we?
Finally,
reset
the
version
number
so
that
backdrop
identifies
itself
as
one
dot
X
instead
of
eight
X,
which
is
the
next
version
of
Drupal.
So
we
have
that
now
in
place
so
that
it's
a
backdrop.
At
least
you
can.
B
You
can
check
if
you're
running
a
back
job
site
really
easily.
Now
by
saying
you
know,
hey
is
there
a
backdrop
version
and
it's
clear
that
yes
you're
on
vector
at
one
point
X
the
thing
that
follows
right
after
that
is
all
of
our
update,
hooks
right
now
or
update
or
upgrade
path
from
Drupal
7
to
backdrop,
all
of
our
updates
were
numbered
in
the
eighth
thousands
per
Drupal
conventions.
B
The
code
itself
still
needs
work,
but
the
general
idea
of
how
we're
kind
of
rolling
back
those
numbers
could
use
some
extra
feedback.
If
anybody
is
interested
in
just
reviewing
how,
let's
all
put
together
and
then
finally,
we're
going
to
replace
the
word
Drupal.
Just
with
backdrop,
throughout
all
of
the
code
for
the
first
iteration
for
consistency
will
probably
just
do
a
blanket
replacements.
Everything
that
is
like
a
Drupal
add
function
and
like
you're
glad
CSS,
Drupal,
ijs
or
Drupal
is
front-page.
B
All
of
those
things
will
probably
just
be
replaced
with
backdrop
just
blanket
just
for
consistency
and
making
it
easy
to
move
from
one
to
the
other
and
there's
there's
some
plans
for
backwards.
Compatibility
there
as
well
like
a
drupal
compatibility,
rapper
layer,
basically
to
make
it
so
you
can
have
backdrop
compatible
modules,
so
a
modular
run
triple
7
and
backdrop,
but
that
compatibility
layer
is
optional.
If
you
have
all
native
backdrop,
functions
or
backdrop
modules
like
all
of
core
will
be,
you
can
disable
that
and
just
run
pure
backdrop
modules.
So
that's
the
plan.
B
It's
moving
along
really
nicely
and
I'm
really
excited
to
see
the
project
like
really
differentiate
itself
from
Drupal.
So
it
I
mean
it's
getting
some
differences
on
the
front
end,
which
is
great,
but
we
need
to
be
differentiating
ourselves
in
the
back
end
from
Drupal.
8
are
really
just
from
from
Drupal
s
as
a
project,
so
yeah
lots
of
progress,
their.
A
Job
and
ok,
so,
there's
bunch
of
other
stuff
we've
been
working
on
this
vague
to
primarily
in
the
user
experience
improvement
section,
which
is
something
that
we
also
really
care
about
and
backed
up
and
want
to
make
the
experience
of
using
back
job
as
good,
if
not
better
than
the
experience
of
using
Drupal
it'll,
definitely
be
better
than
using
triple
seven.
We
want
to
be
comparable
if
not
better
than
using
Drupal
8.
A
One
of
the
first
things
we
did
this
week
in
terms
of
progress
is
taking
one
of
the
top
10
modules
from
Drupal,
which
is
the
admin
menu
module
and
moving
into
core
for
backdrop.
So
that
is
a
drop-down
menu
that
is
now
responsive.
It
wasn't
responsive
in
in
the
Drupal
7
contributive.
Also
it
works
on
mobile
devices
and
got
some
fancy
new
features
like
a
search
box,
which
is
something
that
we
worked
on
in
the
Drupal
7
branch
on
Drupal
as
well.
I
think
it's
a
huge
improvement
over
the
toolbar
module.
A
I
think
it's
going
to
change
everybody's
when
they
interact
with
core
admin
stuff,
which
is
great,
but
it
needs
review
its.
If
there's
a
pull
request
sitting
there
that
I
tested
yesterday
some
other
people
tested
and
we
need
a,
we
need
a
couple
more
people
to
use
it
to
make
sure
that
works
on
mobile
devices
and
make
sure
it
lets
you
get
the
pages
you
want
to
get
to.
A
It
would
also
be
good
to
have
a
code
review
if
there's
anyone
who
wants
to
look
at
that
and
figure
out,
if
there's
anything
that
we
could
do
differently
or
better
and
how
that
it
was
a
did
from
the
Drupal
7
version.
So
I
think
that
is
huge
in
terms
of
making
backdrop
different
from
Drupal.
Also
in
terms
of
improving
way,
people
are
going
to
be
interacting
with
it
needing
to
install
fewer
modules
once
you
have
it
up,
so
I
think.
B
B
It
probably
still
could
use
some
review
in
terms
of
just
making
sure
that
that
everything
is
done
and
kind
of
like
a
core
compatible
way
like
right
now,
some
fun
there's
some
funny
business
like
admin
menu,
still
provides
all
of
the
hook,
implementations
for
like
node
module
and
user
module.
So
it's
a
little
bit
on
the
weird
side,
the
way
it's
constructed,
because
it's
still
kind
of
built
as
a
contributor
core
module,
but
yeah,
it's
it's
it's
in
there,
and
so
it's
yeah.
It's
a
huge
improvement.
It's
really
great!
B
A
And
other
things
we're
working
on
we're
going
to
be
starting
on
getting
a
rich
text
editor
in
core.
This
is
something
Drupal,
8
or
42
is
wysiwyg
in
court.
But
it's
not
quite
wysiwyg.
It's
really
just
rich
text,
so
we're
going
to
try
and
call
it
what
it
is,
and
we
want
to
get
that
moving
students
if
I
want
to
work
on
that
use.
Some
help
we're
also
working
on
rebranding.
A
The
admin
theme
at
drupa
Layton's
done
a
lot
of
really
great
stuff
to
improve
its
admin
theme,
and
we
want
to
make
sure
that
we
have
similar
improvements
to
our
admin
theme.
But
we
don't
want
to
just
take
everything,
Drupal
8,
it's
done
because
then
we'll
end
up
looking
and
feeling
like
you're
using
Drupal
8,
and
we
want
background
to
be
different.
So
last
week,
I
think
we
talked
a
lot
about
setting
up
a
style
guide
for
Julia
to
work
through
to
come
up
with
design
changes.
A
We're
going
to
start
looking
at
what
she's
coming
up
with
for
that
and
trying
to
implement
those
changes
soon
to
which
I
think
will
be
really
great.
So
that's
creating
a
style
guide
for
the
admin
theme
and
then
rebranding
it
to
kind
of
match.
More
of
a
backdrop
feel
and
then
also
other
things.
We're
interested
in
doing
is
changing
some
names
for
things.
There's
weird
things
in
Drupal,
like
the
user
accounts,
are
42
of
people
we'd
like
to
kind
of
clean
that
up
and
there's
a
kind
of
a
long
issue
there.
A
If
you
want
to
look
at
some
of
the
changes
for
thinking
about
for
changing
those
all
right,
so
other
things
we're
working
on
we're,
making
a
whole
bunch
of
progress
in
the
issue,
queue
that
on
issues
that
may
be
or
not
mentioned
in
this
meeting.
But
if
you're
interested
in
what's
going
on
and
feel
free
to
check
us
out
on
github,
we've
got
a
special
project
for
a
shoe.
A
Just
that
you
can
read
it
anytime,
see
how
that's
going
so
yeah
a
lot
of
good
stuff
going
on
the
next
section
of
this
meeting
is
for
updates
from
the
PMC.
We
don't
have
any
issues
that
have
been
escalated
to
the
pnc
recently,
so
we
don't
have
any
updates
for
you.
I
guess
the
only
thing
to
know
it
would
be
that
we
are
looking
thinking
about
and
looking
for
ways
to
expand
pmc
to
include
more
people.
A
So
if
you
want
to
get
involved
in
the
project,
well
we're
definitely
keeping
their
eyes
open
from
people
who
would
make
good
project
management
committee
members
next
up
other
stuff,
we're
working
on
that
doesn't
involve
the
backdrop
project
itself.
We
need
an
API
website,
but,
most
importantly
because
we
no
place
to
put
change
notices,
that's
something
that's
in
the
works.
A
We
should
have
out
hopefully
fairly
soon,
and
we
also
need
a
place
to
document
all
of
our
code
like
where
our
code
differs
from
Drupal
and
give
people
place
to
go
to
look
things
up,
which
would
be
good.
We
also
need
an
update
server.
This
is
something
that
will
allow
every
back
drop
site
out
there
to
identify
itself
as
a
back
drop
site
and
let
its
owners
know
if
it
needs
any
updates
either
too
poor
contributed
modules
to
lead
a
machine
that
can
handle
that
we
also
need
an
official
github
service.
A
A
We've
been
looking
at
how
jquery
does
that,
as
one
we've
also
been
thinking
about
some
potential
other
models,
so
when
we
get
started
on
that
will
need
to
kind
of
hash
out
like
how
our
website
will
interact
with
that
service
as
well,
and
we
also
recently
launched
the
backdrop
CMS
org
website,
but
we've
got
some
more
features
in
the
works.
We
want
to
add
a
showcase
of
sites
with
a
running
back
job,
as
well
as
the
modules
and
themes
pages
too.
A
Once
we
get
our
service
that
effing,
we
have,
of
course,
so
much
with
some
things
that
are
ready
for
prime
time
and
every
Thursday
so
today
and
every
Thursday
in
the
future,
as
well
as
many
in
the
past,
we
do
a
little
backdrop
sprint.
So
usually
an
afternoon
after
this
meeting,
we
all
meet
on
IRC
and
work
on
various
issues.
A
Together,
we
are
also
have
a
couple
of
upcoming
Spence
will
be
meeting
in
person
at
Drupal
corn
camp
this
summer
in
July,
and
also
a
Twin
Cities
camp
in
august
will
be
planning
on
meeting
in
friction.
So
if
anyone
wants
to
watch
in
this
video,
maybe
you're
not
local,
to
the
San
Francisco
Bay
Area,
you
want
to
come
meet
us
in
person
somewhere
else.
There's
just
two
places
that
you
can
join
us
for
sprinting,
which
should
be
fun,
and
then
we've
got
a
bunch
of
other
publicity
things
coming
up.
Other
Drupal
vencer
will
be.
A
Maybe
will
not
be
talking
about
backdrop
a
triple
event,
so
you
can
definitely
come
ask
us
about
it
figure
out.
Why
we're
putting
all
this
work
into
this
project?
Oh,
we
really
believe
in
it.
We
think
it's
going
to
help
change
the
world,
hopefully,
which
is
really
exciting,
so
yeah,
come
see
us
a
triple
events
or
meet
ups
or
get
some
conferences
anyway.
A
B
B
B
Crusts
are
the
first
40
issues
and
then
Andy
filed
another
poll
request
with
like
the
other
half,
so
it's
really
exciting
to
get
that
kind
of
all
cleaned
up
and
out
of
the
way
it's
really
like
the
completion
of
the
Drupal
7
like
cross
sports's
is
the
primary
driver
why
we
can
move
forward
with
the
renaming
the
project
now
that
we've
got
like
all
of
the
patches
that
apply
kind
of
out
of
the
way
we're
moving
forward
in
sort
of
diverging
a
little
bit.
So
that's
great,
really
empowering.
C
A
A
Another
thing
we
could
do
too
is
if
you
wanted
to
start
on
the
Drupal
8
backport
list,
I'm,
not
sure
if
meta
1234
is
the
best
place
to
start,
but
we
could
definitely
use
some
help
on
like
the
CSS
is
a
JavaScript
converging
or
the
cmi
stuff
I
mean
that's
a
little
a
little
heavier,
because
it's
done
really
differently
from
the
triple
the
organ
tissues
than
it
is
from
ours.
But
I
don't
know
Nate.
What
do
you
think's
must
support
triple
sigh
technically
I
think.
B
Yeah
I
think
we're
going
to
need
to
go
through
the
Drupal,
8
back
ports
and
start
pulling
out
the
ones
that
are
are
more
important
right
now
we
don't
have
a
dedicated
list
of
like
tasks
that
are
readily
available
that
and
we
don't
really
even
know
like
how
many
of
these
patches
apply,
but
most
of
them
don't.
We
expect
I
think.
A
D
C
A
C
B
A
Have
the
front
page
one
right:
that's
that's
going
to
be
that!
Well,
how
node
is
which
is
just
like
a
blog
feed
and
is
it
worth
creating
another
one?
That's
similar
like
I,
think
lammons
is
disabled
by
default.
We
might
even
end
up
making
it
enabled
by
default.
So
that
uses
you
instead
of
the
node
page,
and
then
we
wouldn't
even
need
the
node
like
listing
for
for
the
front
page,
I
would
kind
of
tend
to
say
if
we
can
get
that
done.
E
A
E
A
B
Jeff,
so
one
of
the
things
that
that
we're
really
hoping
to
provide
is
we're
trying
really
hard
to
have
basically
an
equivalent
of
panels
in
court
that
that's
called
layout.
So
there's
an
existing
like
it's,
not
a
pull
request
yet,
but
there's
a
branch
that
I've
been
working
on
that
provides
panels
like
functionality
to
replace
the
block
system
and
once
that
is
in
place,
we'll
be
able
to
do
things
like
provide
default.
Layouts
that
are
potentially
disabled.
B
Just
like
just
like
views,
you
can
ship
views
out
of
the
box,
but
they're
actually
disabled,
and
that
could
allow
doing
things
like
setting
up
an
entire
yeah
like
a
blog
layout.
That
already
included
whole
of
the
pieces
that
you
could
just
enable
that
included
that
view,
for
example,
but
yeah
that's
I
mean
we're
still
still
pushing
hard
on
that.
But
I
think
that
layouts
would
enable
a
lot
of
that
kind
of
functionality
to
be
included
or
click
together
really
easily
out
of
the
box.
B
A
We
could
create
an
issue
for
that.
That's
like
provide
a
default
blog
whatever
in
core,
and
then
it
could
be
a
combination
of
a
view
that
includes
all
fees
plays
I
on
a
panel
and
at
least
we
had
an
issue
for
it
and
we
could
have
like
as
soon
as
we
had
the
view
stuff
ready.
We
can
build
it,
so
this
would
add
the
layout
stuff
ready.
We
could
build
that
too,
but
yeah.
It's
a
good
idea.
E
D
E
E
B
Right,
yep,
I,
totally
agree.
Yeah
I
think
yeah
I'm
of
the
same
mind
that,
even
though
backdrop
is
capable
of
doing
doing
a
tremendous
amount
more
than
the
word
presses,
providing
some
use
case
out
of
the
box
that
people
don't
need
to
actually
modify
a
whole
bunch
of
stuff
to
actually
accomplish
I.
Think
is
a
good
idea
and
a
blog,
you
really
still
is
like
you
know.
Most
sites
have
blogs.
Even
if
that's
not
the
primary
functionality,
they
still
have
a
blog
of
some
sort
on
them.
Some
yep
I
agree.
B
Okay,
so
yeah
I
also
think
Jen's
right
that
maybe
we
should
start
a
discussion,
an
issue
around
making
the
out
of
box
functionality
like
defining
what
it
is
and
making
sure
that
we
provide
that
like
completely
built,
so
that
that
way
out
of
the
box
there's
something
you
can
actually
do
with
the
product.
It
sounds
great
yeah.