►
From YouTube: Backdrop CMS weekly meeting 12/11
Description
Update on the progress of Backdrop CMS.
A
Alright,
we
are
on
air,
it
is
Thursday
December
11
and
we
are
getting
really
close
to
our
release
date,
which
is
super
exciting.
This
is
a
status
meeting
for
backdrop.
Cms
backdrop
is
a
content
management
system
that
is
specifically
geared
towards
the
nonprofit
small
to
medium-sized
business
and
companies
or
organizations
that
are
specifically
concerned
about
ongoing
costs
in
terms
of
maintaining
comprehensive
systems
like
content
management
systems.
So
we
have
a
couple
of
goals
and
working
on
backdrop.
A
A
We
know
the
triple
7
is
already
too
complicated,
so
we're
also
trying
to
decrease
the
complexity
for
in
backdrop
as
well
we're
going
to
be
fixing
bugs
so
folks
that
were
in
Drupal
7,
but
so
we're
interpolate
books
that
we've
introduced
on
our
own
when
really
fixing
all
those
along
the
way,
as
well
as
simplifying
existing
system.
So
because
you're
cool
sevens
too
hard,
we
want
to
remove
abstraction.
Where
we
can.
We
want
to
simplify
complexity.
A
So,
in
terms
of
future,
our
initial
release
is
coming
up
very
soon.
We're
going
to
do
a
backdrop
CMS
pre-release
on
December
eighteenth,
which
is
a
week
from
today
week
from
yeah
week
from
today.
So
at
that
point
we
will
stamp
the
code.
You
know
ready
to
ship
and
we're
hoping
that
we'll
get
a
bunch
of
people
to
come
and
test
it.
So
everyone
will
be
so
all
excited
about
going
on
winter
break
or
on
vacation
or
then
actually
have
any
work
to
do.
A
So
that
means
the
things
that
we're
working
on
now
are
all
non
release:
lockers,
but
their
stuff
that
we
really
like
to
get
into
the
first
release,
and
then
we
will
of
course
be
able
to
make
iterative
changes.
Going
forward
will
still
be
able
to
fix,
bub,
also
be
able
to
add
new
features,
but
we
won't
be
able
to
change
any
of
the
existing
apx.
So
we
do
have
a
change
that
is
going
to
be
required,
potentially
api's
work.
A
There's
got
to
be
backwards,
compatibility
in
there
so
that
everything
will
continue
to
work
from
this
point
forward
within
reason.
We
might
just
postpone
it.
So
in
terms
of
the
progress
of
the
project,
we
have
three
major
new
things
that
we
were
working
on
to
get
into
backdrop.
1
point
0
point
0:
those
are
configuration,
management,
getting
blocks
and
layouts
in
in
views
and
corp,
and
all
three
of
those
things
are
in
a
completed
non-release
blocker
state.
So
we
have
some
follow-up
issues
for
each
one.
None
of
those
are
released.
A
Lockers,
all
of
the
major
issues
are
completed,
and
therein
as
they
are,
which
is
fabulous
things
that
are
still
working
on.
We've
got
a
set
of
issues
that
we
would
like
to
do
for
camping
management
in
the
future,
but
those
are
probably
going
to
be
in
backdrop
to,
but
there
are
a
bunch
of
issues
that
Nate
opens
that
we
can
review,
try
and
figure
out.
You
know
they're
hard
problems
to
solve
Drupal
itself
in
one
way
we
want
to
solve
differently
in
backdrop.
A
We
can
examine
and
figure
out
the
right
way
to
deal
with
those
issues
for
vector
up
to
four
blocks
and
layouts.
The
underlying
api's
are
in
the
system
is
done,
everything
is
working,
the
interface
is
a
total
mess.
We
know
that,
but
it
works.
That's
the
most
important
thing
and
it's
actually
even
already
better
than
panels.
So,
even
though
it's
confusing
it's
better
than
panels
was
it
provides
the
same
functionality
the
panel's
provided,
and
we
have
the
ability
to
change
that
interface
later.
So
we
can
do
some
user
testing.
We
can
do
some
designing.
A
We
can
build
some
interfaces
that
work
even
better
and
we
can.
We
have
a
chance,
you
know,
to
examine
our
human
interface
guidelines,
make
sure
we're
using
the
right
tools
and
right
places
and
make
that
really
slick
in
the
coming
months.
But
as
it
is
now,
it
works
perfectly
well,
so
that's
in
it
it's
ready
and
then
the
last
thing
is
views.
We
have
views
the
underlying
system
and
for
we've
got
a
couple
of
little
tiny
changes
that
are
going
in.
A
We
have
a
couple
of
administrative
listings
and
content
listings
that
could
be
using
views
that
also
need
to
go
in.
These
are
also
things
that
are
not
API
breaks
and
we
can
introduce
them
later,
of
course,
will
be
nice
if
we
had
it
all
packaged
up
and
ready
to
go
and
released,
but
not
as
nice
as
having
a
release
product.
A
So
we're
gonna
go
ahead
and
release,
as
is
with
the
stuff
that
we
don't
get
done
in
the
next
month
and
a
half
here,
I
guess
month
in
a
few
days,
but
where
we
are
really
close
and
it's
looking
really
good.
So
we've
got
a
couple
of
issues
for
blocks
and
layouts.
A
couple
of
issues
for
views
depending
on
was
to
jump
in
on
those
and
help
us
make
it
a
little
shinier
on
the
outside.
We
could
definitely
use
some
hop
there.
A
B
A
B
Those
other
listings
are
looking
good,
but
them
have
upgrade
pads
yet
so
when
you
upgrade,
if
you
have
a
block
placed
for
example,
that
lists
like
recent
comments,
that
block
should
get
converted
to
a
view
for
you
as
part
of
the
upgrade
pack.
So
that's
a
little
bit
of
a
tricky
thing
to
accomplish
and
we're
looking
out.
You
know
making
sure
that
we
include
those
upgrade
paths
and
not
just
including
the
built-up
views
for
new
installations.
B
There's
also
a
lot
of
discussion
happening
right
now
around
performance,
because,
if
use
you
know
super
flexible
or
super
popular
as
it
is,
it's
just
not
as
performant
as
a
hard-coded
listing.
So
there's
some
discussion
happening
right
now
about
what
we
want
to
do
about
that
or
what
listings
are
considered.
You
know
acceptable
the
current
performance
on
them,
but
I
think
that
you
know
with
eighty
percent
of
Drupal
sites
out
there
using
vuze,
there's
not
really
an
option
to
not
use
vuze
or
even
shipping
backdrop.
B
Not
using
vuze
is
just
the
whole
ball
situation
would
be
well
yeah.
It
would
be
silly
exactly
so.
What
we're
looking
at
right
now
is
you're,
probably
going
to
accept
the
performance
regressions
at
least
as
far
as
like
administrative
listings
go
because
the
number
of
administrators
are
really
low.
Typically,
I
mean
the
overall
impact
is:
is
pretty
bad
like
on
the
language
of
like
75%
slower,
but
75%
slower
is
still
like.
B
You
know
in
half
a
second,
so
it's
not
like
it's
going
to
be
crippling
it's
just
going
to
be
slightly
slower
than
what
it
was
previously,
but
still
probably
below
a
perceptible.
You
know
time
difference
for
a
human,
so
what
we're
going
to
do
probably
is
is
move
forward
with
converting
those
listings
and,
at
the
same
time
start
going
through
and
trying
to
optimize
use
itself,
and
we
found
a
couple
of
issues
already
this
week
that
get
us
like.
B
One
of
them
is
like
a
ten
percent
faster,
and
one
of
them
is
like
an
eight
percent
faster,
so
we're
already
moving
views
into
making
it
more
efficient
and
I.
Think
that's
really
I
mean
that's
about.
Our
only
option
really
is
is
put
these
stunts.
Put
these
conversions
in
like
knowingly
look
at
the
performance
difference
between
them
and
then
work
towards
optimizing
it
at
least
for
the
out
of
box
views
so
and
it's
it's
all,
still
really
exciting.
The
conversions
are
totally
worth
it.
There's
some
new
functionality
that
gets
added
as
well
like.
B
B
It
there's
nothing
really
new
one
dose,
those
guys
like
blocks
and
layouts.
It's
been
in
a
shippable
state
for
a
a
month
or
two
now
see
em
I
see
em
I
the
big
news
like
two
weeks
ago.
We
finished
all
of
the
conversions
for
CM
I,
so
that
literally
everything
is
all
in
cm
I.
Oh,
we
deprecated
system
settings
form
this
past
week,
so
that
got
moved
into
Drupal
by
ink.
So
it
only
exists.
If
you
have
the
compatibility
mode
turned
on
there's
a
lot
of
discussion
going
on
right
now
around.
B
If
we
can
make
a
replacement
for
that
system,
settings
forum
was
used
is
like
the
shortcut
to
say:
I've
got
a
configuration
form
just
shove,
every
single
value,
exactly
as
it
is
in
the
form
into
the
variables
table,
but
there's
kind
of
I,
don't
know
it's,
it's
been
convenient,
but
it's
pretty
magical
and
what
we
did
in
backdrop
was
we
stopped
using
that
and
we
just
manually
coded,
submit
handlers
for
every
settings
form
in
backdrop.
That
has
some
disadvantages
that
it's
a
little
bit
more
code,
but
it
has
an
advantage.
B
Is
that
it's
more
clear
where
configuration
is
getting
saved,
it's
less
magic.
You
also
have
the
opportunity
to
like
clean
up
your
values
before
you
save
them
like.
If
you
want
to
cast
them
as
boolean
sore
integers
that
happens
now.
Instead
of
saving
everything
is
a
string
which
it
often
shouldn't
be
so
I,
don't
know,
there's
there's
a
lot
of
good
reasons.
Why
why
we
got
rid
of
it
and
didn't
make
a
replacement,
but
there's
some
consideration
around.
Should
we
make
a
replacement
for
system
settings
form
and
right
now
back.
A
A
B
Right
now
we
don't
have
a
shortcut
and
I
mean
we
could
add
a
shortcut
at
any
time,
so
I
think
I'm,
fine,
with
just
accepting
with
what
we've
got
right
now,
which
will
kind
of
you
know,
set
the
precedent
that
people
will
have
to
write
us
in
the
end
other
for
their
settings
forms
now.
But
if
it
turns
out
to
be
like
you
know,
we
get.
A
large
group
of
people
are
saying
they
really
want
that
convenience
than
maybe
we
can
add
it
later,
because
it's
not
it
would
be
an
API
edition.
B
We
should
leave
system
settings
forum
exactly
how
it
is
for
compatibility.
So
if
you've
got
a
drupal
module
and
you
poured
it
to
backdrop,
system
settings
won't
actually
continues
to
work
and
continues
to
save
in
two
variables.
It's
just
that
the
entire
system
is
deprecated
like
variable
set
where
it
will
get
is
deprecated
and
system
settings
forum
is
deprecated,
but
they
all
still
work
so
so
they
it
should
stay
as
it
is
and
continue
to
save
into
the
variables
table,
because
that's
that's
what
that
function.
Does
okay,.
A
All
right,
so
that
is
the
status
of
our
three
major
new
features:
config
management
blocks
and
layouts
infuse.
We
also
have
a
couple
of
other
things
that
we
need
to
work
on
before
we
can
really
spectrum
one
point:
0
point
0,
the
one
major
thing
that
I
think
is
actually
and
I
released.
Blacker
at
this
point
is
figuring
out
our
security
issues.
We
have
to
unresolved
security
issues
for
backdrop.
A
A
And
so
we
were
evaluating
other
solutions
that
might
also
solve
the
problem
that
wouldn't
break
in
trim.
In
that
way,
we
would
solve
the
not
a
big
deal
security
issue,
but
also
not
breaking
trib,
and
there
are
a
couple
of
ideas
in
there
that
I,
don't
think
anyone
is
really
decided
are
the
absolute
best
way
to
go.
So
if
we
have
anyone
who
specifically
interested
in
security,
understands
the
scope
of
the
problem
and
can
offer
some
insight
on
which
solutions
are
good.
A
How
big
of
an
issue
it
actually
is
all
of
that
kind
of
stuff
we
can.
We
can
try
and
figure
out
what
our
path
forward
should
be
for
that
last
security
issue
and
then
other
stuff
that
we're
working
on
that
are
not
necessarily
release
lockers,
but
I
think
are
important,
you're
getting
cross
sports
from
Drupal
7
33
in
to
backdrop,
so
this
is
just
mostly
bug
fixes
and
user
interface
improvements
and
documentation
updates
that
are
good
changes.
A
We
have
a
couple
of
lists
of
Drupal
8
backports.
These
are
at
this
point
not
very
crucial
for
us.
There's
like
a
handful
of
like
three
html5
issues.
I
think
one
of
them
has
a
poor
request.
It
just
needs
some
work,
one
of
them
and,
let's
take
a
look
at
which
ones
they
are.
One
of
them,
I
think,
is,
is
just
clean
up
on
how
we
add
attributes
to
the
one
of
the
template
files
and-
and
one
of
them
is
trying
to
get
multiple
files
into
file
upload
using
the
multiple
html5
ability.
So.
A
B
A
B
A
So
when
we
got
people
who
are
you
know
mucking
around
in
our
JavaScript,
it
would
be
easy
for
easier
for
them
to
work
on
it,
but
it's
definitely
not
mission-critical.
It's
not
a
true
point,
really
cursed.
It's
not
a
ton
as
important
to
us
as
it
was
for
plate.
So
I
think
we
should
just
close
the
JavaScript,
not
an
issue.
Yeah.
B
The
remainder
of
the
ones
that
are
in
the
javascript
is
sure
doing
things
like
you
know,
making
things
that
previously,
where
javascript
file
into
a
library
with
the
javascript
file
inside
of
it
and
using
pound
attached
in
a
bunch
of
places
and
getting
rid
of
drupal
ijs.
But
none
of
those
things
are
a
requirement
for
backdrop,
because
we
still
have
the
implied
dependency
on
jquery.
So
you
don't
need
to
register
the
library
and
we
also
kept
triple
a
DJ
s.
Add
CSS
at
library
around.
B
A
Ok
and
then
other
things
that
we're
working
on
these
are
also
not
release
blockers,
but
that
we
are
thinking
about
for
backdrop,
are
the
design
related
tasks,
including
a
little
clean
up
on
the
administration
theme
clean
up
on
the
install
blur
stuff
like
that.
That
I
think
is
again
not
a
really
slacker
a
lot
of
what
we
can
do
after
the
initial
release
of
that
job
team
system
cleanup.
A
A
lot
of
these
can
also
be
done
after
the
initial
release.
Things
like
adding
a
rich
text
editor
and
establishing
her
human
human
interface
guidelines.
Those
are
not
dependent
on
being
in
before
we're
established.
Before
one
point,
0
point
0
so
also
thanks
for
working
on,
but
not
super
urgent,
and
then
we
have
a
couple
of
issues
where,
if
we
have
someone
who's
an
expert
in
CSS
our
age,
we
could
use
just
an
overall
review.
A
Nate
and
I
have
obviously
been
looking
at
this
stuff
a
lot,
but
it
would
be
good
to
have
a
new
set
of
eyes
on
it.
To
say,
like
hey,
you
know,
is
this
the
mark-up
you
want
for
a
wheelie
layouts,
or
is
this
the
way
our
CSS
formatted?
Is
it
correct
and
be
good
to
just
kind
of
have
a
high
level
review
of
those
things?
If
that
someone
wants
to
jump
in
on
that?
A
Obviously,
if
we
don't
get
those
reviewed
before
released,
we're
going
to
release
any
way,
but
it
might
have
some
yuckiness
and
we've
got
too
many
dips
or
too
many
selectors
and
a
given
CSS
file
or
something
so
yeah.
It
would
be
good
to
have
a
review
if
people
are
interested.
In
that,
let's
see,
we
have
a
section
in
this
weekly
meeting
to
announce
updates
from
the
PMC.
We
don't
really
have
any
updates
this
week.
A
Last
week,
when
we
have
this
meeting,
we
announced
that
we
had
established
a
mission
statement
which
I
think
is
super
important
for
us,
which
is
good
we're
also
working
on
some
new
content,
for
our
our
primary
website
will
try
and
get
that
up
soon.
Also,
it
helps
kind
of
say
what
is
backdrop,
and
why
should
you
care
about
it,
which
I
think
is
useful,
other
things
I
think
are
really
important-
that
we
should
just
enter
it
again.
Pre-Release
is
coming
out
next
week,
December
eighteenth,
actual
release
of
backdrop.
Cms
is
coming
out
january.
A
Fifteenth
so
tell
your
friends.
Tell
your
family.
Let
your
dog
know
all
that
good
stuff.
It's
coming
soon,
other
things
that
we're
working
on
that
aren't
necessarily
backed
off
the
product
that
are
important
for
backdrop.
The
community
are
the
primary
website,
the
API
site,
the
github
service,
the
update
server.
We've
got
a
lot
of
stuff
going
on.
That
is
at
peripheral
to
the
actual
project
itself.
That
all
needs
a
bunch
of
work
and
it's
all
been
kind
of
postponed
because
we
want
to
get
the
product
out
so
I
think
as
soon
as
backdrop.
A
One
point
0
point:
0
is
released,
but
we
should
all
do,
is
kind
of
take
a
nice
deep
breath
and
then
refocus
on
some
of
the
stuff
around
the
product
itself,
because
if
people
are
going
to
be
using
backdrop,
they're
going
to
need
a
place
to
go
my
modules,
we
have
to
build
that
place.
You
have
to
build
those
modules
and
we've
got
to
kind
of
help,
establish
the
community
around
the
software
as
well.
So
things
we're
working
on
our
the
API
site.
We've
got
a
bunch
of
change
records
going
on
there.
A
We've
got
a
bunch
of
people
doing
review
of
the
chain
right
change
records
that
are
there
trying
to
make
sure
we've
got
code
samples
from
before
and
after
I
think
that's
a
really
great
place
to
start
and
we're
going
to
be
working
on
putting
a
nice
theme
on
it.
We're
going
to
work
on,
in
addition
to
the
API
side
itself,
we're
also
going
to
be
working
on
setting
up
an
update
server
so
that
your
backdrop
site
will
be
able
to
tell
you
if
it's
up
to
date
or
not
short
term.
A
It's
just
going
to
be
something
that
you
know
returns
a
message
and
it's
like
I'm
server.
You
know.
Oh,
it
won't
be
useful,
but
longer
term.
We
want
that
server
to
actually
house
some
really
useful
data
data.
For
us
we
know
with
Drupal
dark.
Not
only
does
your
site,
your
drupal
site,
painter
bowl
and
the
Drupal
updates
over
and
tell
you
if
your
site's
up
to
date,
but
the
Drupal
update
server
checked
some
statistics
on
what
your
site
is
actually
doing.
A
You'll
be
really
great
if
our
updates
over
contracts
and
statistics
too,
and
in
addition
to
the
stuff,
the
Drupal
trucks
will
also
want
to
check
things
like
which
modules
are
currently
being
used
on
your
site,
like
which
core
modules,
and
that
will
give
us
some
really
useful
information
for
in
the
future.
If
we
decide
to
remove
module
support.
Well,
no,
you
know
if
eighty
percent
of
people
are
using
that
module,
we
obviously
should
before
so.
A
So
we'll
regroup
a
little
bit
and
work
on
that
after
backdrops
out
and
then,
of
course,
getting
our
flagship
website
up
is
probably
the
most
important
thing.
We
need
to
tell
the
world
that
we
have
a
really
systems.
We
have
a
really.
We
need
to
tell
people
why
they
should
care
about
it,
why
they
should
use
it.
You
know
today,
you've
got
a
choice
of
choosing
Drupal
7
drupal
later
backdrop.
We've
got
a
fight,
a
good
fight
for
getting
people
to
use
backdrop.
A
Obviously
our
major
selling
point
over
Drupal
8
is
it's
here
today,
but
we've
got
some
really
good
selling
points
over
Drupal
7
too.
We
want
to
list
those
I
think
we've
got
a
pretty
good
pitch
going.
We've
just
sent
some
content
after
our
designer
we're
gonna
figure
out
how
to
get
it
all
laid
out
and
presented
in
a
way,
that's
pretty
as
well,
and
so
that
I
think
we
need
to
get
done.
We
need
to
build
the
pages
that
allow
people
to
find
the
modules
and
themes
that
are
on
github.
A
We
need
to
set
up
a
showcase
site,
so
people
who
have
built
backdrop
sites
can
post
them
on
our
website
and
you
know
maybe
write
a
little
a
story
about
how
backdrop
worked
for
them.
That
sort
of
thing
we
want
to
put
a
listing
of
people
who
are
building
sites
in
backdrop
on
site.
So
if
someone
comes
star
site
and
wants
a
backdrop
site,
they
can
find
someone
to
build
it
for
them.
I
think
that
would
be
super
useful
and
we've
got
a
whole
bunch
of
plans
for
other
stuff.
A
We
can
do
with
that
site
in
the
future,
based
on
things
that
have
worked
for
the
Drupal
community
or
things
I
haven't
worked
for
the
Drupal
community.
We
can
kind
of
learn
from
from
their
mistakes
as
well
as
their
successes
and
do
the
same
thing
in
fact.
So,
though,
a
lot
of
work
to
do
it's
not
backdrop
a
product,
and
we
should
get
started
on
that
here
in
the
next
month
or
so
as
backdrop
gets
done
and
today
after
this
meeting
will
be
working
virtually
together
on
github
on
IRC.
A
If
you
have
any
questions
you
can
tweet
at
us,
you
can
jump
in
IRC
channel
and
ask
us
directly
we're
usually
in
there.
If
you
need
to
get
neat
or
my
attention
so
that
I
do
type
our
name.
First,
we
go
sometimes
we're
heads
down
in
code
working
on
for
work
best,
whatever
might
not
notice
conversation
going
on,
but
we
usually
are
in
there,
and
hopefully
you
can
have
find
a
way
to
get
our
attention
and
then
at
some
point
in
the
future
will
establish
some
more
in
person
Sprint's.
A
A
And
then
I
know
Alberto
you're
here
to
I,
don't
know
if
you
have
any
questions
you'd
like
to
bring
out
for
us
or
not,
if
you
don't
have
voice
capability,
you're
welcome
to
type
them
into
the
chat
too.
If
you
want
to
add
them
there
or
if
anyone
else
is
watching
the
video
and
has
any
questions
for
so
you
can
tweet
at
us
at
backrub,
CMS
usually
gets
our
attention
and
it'll
notify
both
need
myself.
A
A
All
right,
well,
I,
can't
think
of
anything
else
that
we
should
talk
about
today
or
anything
else
that
we
should
add
to
the
agenda
for
every
week.
But
we
will
be
meeting
again
next
week
on
December
eighteenth,
which
is
a
very
exciting
date
for
us,
because
its
release
date
will
be
issuing
our
pre
release
next
weekend,
we'll
be
starting
to
build
sites
with
factor
which
is
really
creepy.