►
From YouTube: Backdrop CMS weekly meeting
Description
Progress report on Backdrop CMS. Today's agenda: http://bit.ly/1l5YDg3
A
Okay,
we
are
alive,
happy
Thursday,
everybody
happy
backup
day
every
Thursday
Specter
update
here.
A
Let's
see
it
is
the
end
of
June
nearing
the
end
of
June
here,
so
what
we
were
doing,
we're
working
on
backdrop
CMS,
which
is
an
open
source
content
management
system
that
will
be
intended
specifically
for
nonprofits
and
small
medium-sized
businesses,
people
who
want
a
full
featured
content
management
system
for
without
to
to
high
cost
a
costume
in
terms
of
maintenance
and
hosting
and
all
the
other
stuff
that
goes
along
the
hidden
costs
of
the
website,
we're
trying
to
create
a
set
of
features
that
is
comparable
to
that
that's
interpolate,
and
maybe
we
won't
get
there
right
out
of
the
gate,
but
that's
our
long-term
goal,
but
we're
trying
to
keep
the
architecture
more
similar
to
that
of
Drupal
7.
A
So
any
existing
drupal
developer
should
be
able
to
work
on
factor
up
very
easily
without
needing
to
make
it
a
huge
time.
Investment
in
learning
anything
new
modules
should
be
able
to
port
deported
from
Drupal
the
backdrop
really
easily
and
hopefully,
that
I'll
make
it
really
easy
for
a
community
to
grow
up
around
back
shop
really
quickly.
We
are
trying
to
fix
those
that
exist
in
current
versions
in
Drupal,
so
both
Drupal,
7,
android
and,
of
course,
any
bugs
that
we
found
on
our
own
we'll
fix
those
as
well.
A
We're
also
going
to
be
simplifying
existing
systems
when
possible.
So
if
there
are
things
that
were
too
complicated
in
Drupal
7,
we
want
to
clean
those
up
to
make
them
easier
to
use
and
understand
in
backdrop,
we'll
try
and
do
that
and
we're
going
to
add
new
features.
As
long
as
all
of
these
things
don't
require
changing.
The
API
is
very
much
so
in
order
to
stick
to
our
goal
of
making
it
really
easy
to
get
to
backdrop
from
Drupal
7
we're
going
to
keep
changed
to
a
minimum.
A
Our
back
our
timeline
for
backdrop,
we're
going
to
be
hoping
to
release
back
up
one
point:
0
point
0
this
summer.
So
right
now
it's
kind
of
the
middle
nearing
the
end
of
june
or
thinking
this
will
probably
be
released
in
July
and
I.
Think
we
should
probably
choose
a
date
and
put
that
down
sometime
soon,
so
maybe
I'm
Nate.
When
we
get
closer
to
the
end
of
this
blocks
and
layouts
thing
will
hat
will
know
when
that
date
would
be,
and
then
we'll
try
and
figure
out
what
needs
to
get
in
before
the
date.
B
A
So
maybe
I
know
we're
really
close
on
the
Drupal
7
conversion
stuff.
If
I
can
get
those
done,
I
can
start
working
and
see.
My
conversions
I
think
would
also
be
good
to
try
and
get
more
hands
on
it.
I
know:
we've
got
contact
module
converted
to
cmi,
and
maybe
we
can
get
some
other
people
working
on
some
other
stuff
too.
Well,
we'll
see,
I
don't
know
you
think
we
can
get
Andy
doing
some
of
that.
A
Well,
we'll
figure
it
out
we'll
try
and
try
and
redistribute
work
a
little
bit
now
that
work
I'm
ending.
So
no,
oh,
we
also
have
one
of
the
backdrop.
Interns
who
worked
for
us
in
May
is
going
to
be
coming
back
starting
july
first,
he
might
be
a
good
one
to
put
on
some
of
those
too.
If
we
can
find
some
some
easy
once
in
beginning
and
walk
him
through
those
he'd
be
good
to
kind
of
take
over
the
rest
of
them.
Maybe
don't
give
him
fields
first,
but
yeah.
B
Anyway,
for
anyone
interested
in
working
on
the
issue,
the
meta
issue
is
number
170
and
that
lists
all
of
the
oh
wait.
These
are
all
with
all
of
the
variables
and
others
there's
another
meta.
That's
above
that
one
969
there
we
go
okay,
so
issue.
1
69
is
the
like,
overall,
all
of
the
things
that
need
to
be
converted
to
cmi
and
we've
stuck
that
quite
a
few
of
those
to
tackle.
Okay.
A
But
then,
after
we
kind
of
getting
a
grasp
on
that,
we
should
maybe
set
a
release
date,
and
this
is
obviously
these
conversions
are
released
blocker,
but
it
would
be
good
to
to
figure
out
when
that
could
be
like
if
we
need
to
start
saying
obvious
instead
of
July,
that
would
be
good,
that's
still
summer,
all
right
and
then
after
we
get
the
1
point,
0
point
0
release
out.
A
We
are
going
to
keep
releasing
frequently,
so
the
reason
that
we're
not
pushing
to
add
a
whole
ton
of
new
features
right
now
is
because
things
like
adding
link
module
decor
can
happen
after
we
released,
we
can
add
features
as
Long's
doesn't
require
changing
any
face.
We
can
do
that
much
later.
Api
auditions
are
fine,
just
not
changing
existing
ApS,
so
right
now
we're
just
working
on
trying
to
get
the
biggest
things
in
like
cmi
conversions
and
then
we'll
be
able
to
add
new
stuff
after
the
fact.
A
So,
in
terms
of
a
progress
report,
you
just
heard
a
little
bit
about
our
config
management
status,
which
is
probably
the
most
important
thing,
and
but
we
have
some
major
news
from
last
week-
is
that
we
have
mostly
resolved
backdrops
identity
crisis.
So
the
problem
we've
been
having
for
the
last
nine
months
where
you've
installed
backdrop
and
it
says,
install
like
drupal,
has
now
finally
been
replaced.
We
took
our
beautiful
new
logos
from
darius
and
put
those
in
so
when
you're
running
the
installer,
you
don't
see
the
drupal
drop
anymore.
A
You
know,
see
the
backdrop
square
and
all
of
the
code
well
most
of
the
code
that
said
drupal
in
function.
Names,
for
example,
has
now
been
converted
to
say
backdrop
and
neat.
You
committed
that
patch
earlier
this
week.
Do
you
want
to
say
anything
about
how
happy
you
are
that
that's
done.
B
B
So
it's
it's
pretty
well
backdrop
everywhere.
There
are
a
couple
places
where
we
still
have
your,
both
mostly
in
links
to
drupal
org.
Let's
let
the
only
thing
that
is
is
remaining,
but
most
of
those
even
are
just
in
like
doc
blocks,
and
then
you
know,
code
comments
so
front
facing
lies,
there's
very,
very,
very
little
left
that
says
Drupal,
which
is
a
good,
a
good
improvement.
We've
still
got
some
some
pieces
that
are
missing.
Of
course
we
don't
have
like
a
locale
server
and
we
don't
have
an
update
server.
B
A
B
And-
and
it's
also
nice,
that
writing
new
code,
you
can
use
all
the
function
names
like
it
previously.
It
was
really
crazy.
How
we
had
new
functions
were
named
it
backdrop
underscore,
but
old
functions
were
still
drupal
underscore
now.
Everything's
just
backdrop
underscored
for
for
everything.
Well,
sided
I
mean
the
compatibility
layer
took
on
a
much
bigger
role.
When
we
did
that
conversion,
you
can
still
call
all
of
the
dribble
functions,
all
the
triple
class
names,
all
the
methods
that
had
the
name
Drupal
in
them.
B
As
long
as
the
compatibility
layers
turned
on
which
it
is
by
default
in
settings
PHP,
so
everything
still
works
like
even
even
the
JavaScript
still
works.
If
you
use
the
word
drupal
instead
of
backdrop
again,
that's
to
help
facilitate
for
the
easy
migration
from
from
Drupal
7.
To
backdrop
like
converting
something
is
really
pretty
trivial,
but
you
know
that,
as
we
move
forward
to
like
backdrop
to
you
know
the
compatibility
layer
will
get
taken
out,
but
for
now
you
can
still
use
Drupal
everywhere,
but
you
shouldn't,
if
it'll
just
be
backed
up
everywhere
for
consistent.
A
Alright,
well
that's
great.
That
was
a
major
release,
blocker
that
we've
knocked
out,
so
that
makes
me
feel
much
better
about.
What's
left
to
be
done
before
we
could
release,
which
is
good.
Other
things
we
talked
about
briefly
blocks
and
layouts
name
is
back
on
the
trail
of
blocks
and
Leah.
So
do
you
want
to
give
us
an
update
on
how
that's
going
yeah.
B
It's
it's
coming
along,
so
I've
pushed
up
my
branches
branch
changes.
So
if
you're
following
along
issue,
86
for
blocks
and
layouts
and
branch
currently
is,
has
been
updated
with
the
latest
code
that
has
layouts
you
can
horses
layout
module,
you
can
add
a
new
layout,
it
automatically
creates
menu
item.
B
You
can
configure
that
layout
and
add
context
smell
or
yes,
yes,
you
can
add
context
and
you
can
add
conditions
which
is
like
selection
criteria
and
panels
land,
and
it's
it's
working
really
pretty
well,
it
actually
does
make
pages
right
now,
so
you
can
actually
create
a
new
layout
page
and
it
will
show
up
in
the
mini
system.
But
the
actual
configuration
of
the
layout
like
placing
blocks
is
not
actually
there's
no
interface
for
that.
Yet.
A
B
So
it's
I
mean
it's
a
start,
but
we
still
got
a
long
ways
to
go
like
the
entire
interface
for
for
placing
blocks
also
involves
like
setting
all
of
the
lino
selection
criteria
on
each
individual
block
or
whatever
the
panel's
terminates.
For
you
know,
X
access
rules
or
whatever
it
is
for
showing
the
blocker
hiding
the
block.
There's
a
lot
to
do,
but
it's
coming
on
timeline
wise,
yeah
I'm
still
really
nervous
about
getting
this
done.
B
You
know
before
the
end
of
next
month,
so
we'll
see
how
everything
else,
how
everything
else
is
coming
along
and
whether
or
not
we
can
trim
down
functionality,
because
it
would
be
better,
in
my
mind,
to
get
a
layout
module
that
has
at
least
the
capabilities
of
blocks
which
isn't
very
much
and
get
blocks
replaced
with
like
a
bare-bones
layout
module.
So
we
can
improve
and
iterate
it
on
it
after
release,
as
opposed
to
needing
to
be
stuck
with
blocks
and
regions.
For
you
know
the
entire
1
point
0
cycle
yeah.
A
I
think
that's
definitely
realistic.
I
mean
there's
a
lot
of
stuff
and
in
like
panels
in
the
layout
configuration
that
is
completely
not
unnecessary
for
the
eighty
percent
right,
like
selection,
can't
area
configurations
for
individual
blocks
can
come
somewhere
else.
They
don't
have
to
come
in
that
configuration
and
things
like
adding
styles,
and
all
of
that.
It's
it's
nice
to
have
that.
A
But
it's
completely
unnecessary
and
I
think
like
just
a
layout
where
you
put
choose
a
layout
and
put
blocks
into
the
layout
is
all
we
really
need
and
as
long
as
leaking
it
that
much
done
I
think
we
can
ship
and
we
can
add
any
of
that
other
stuff
later
too,
especially
if
it's
just
involves
like
altering
forms
and
and
adding
a
new
config
files.
A
So
I
think
that
sounds
like
a
good
plan
and
other
stuff
we're
working
on
we've
gotta
release
blocker
in
here,
which
is
used
in
court,
and
we
actually
have
the
core
abused
in
court.
There
are
a
bunch
of
use
themselves
that
are
not
yet
in
for
their
they're.
Currently,
the
listings
that
Drupal
7
had
and
those
need
to
be
converted-
and
there
are
some
administration
listings
that
need
and
matching
actions
created
for
the
equivalent
of
VB,
oh
so
I,
don't
necessarily
think
all
of
that
needs
to
be
released.
A
Locker
I
think
we
should
kind
of
prioritize
and
say
you
know
these
10
or
release
blockers,
and
these
four
are
fine.
If
we
don't
get
to
the
and
then
we
can
figure
out
where
you
know
where
our
priorities
should
be.
So
that's
that's
also
something
that's
on
our
list
that
we
want
to
get
done
before
we
release,
but
not
not.
All
of
it
is
preventing
look
at
their
release
and
we
definitely
need
help
with
those
conversions.
A
So
if
anyone
wants
to
jump
in
on
converting
views
and
that's
a
good
place
to
start
the
issue
number,
there
is
number
151
and
in
config
management
I
think
we've
already
talked
about
probably
enough,
but
we
have
a
version
of
cmi
in
backdrop
and
it
needs
more
conversions
in
that
issue.
One
more
time
is
169.
Another
thing
that
we're
working
on
is
trying
to
keep
up
with
all
of
the
progress.
A
That's
going
on
in
Drupal
and
particularly
in
Drupal
7,
so
any
commits
that
have
been
made
to
Drupal
7
we
need
to
include
as
well,
and
we
currently
have
to
meta
is
open,
but
we
are
closing
in
on
getting
both
of
those
done.
We've
had
a
bunch
of
progress
since
last
week
on
both
of
those
and
then
we
have
the
security
issues
that
are
currently
open
against
drupal
7
and
we've
got
two
of
those
remaining
one
of
them.
We
have
a
solution
for
the
other.
A
One
I
think
I'm,
not
sure
that
most
recent
one
we've
actually
looked
at
it
yet,
but
two
there's
only
two
left
before
we
need
to
release
I
think
that's
fine,
and
then
we've
got
a
bunch
of
backports
of
stuff.
That's
going
on
in
Drupal
8
that
we
also
want
to
do
in
backdrop.
So
I
get
all
the
conversions
to
html5.
A
Most
of
those
are
in
and
we're
more
than
halfway
through
the
list
of
all
of
the
conversions
I'm,
not
sure
we
need
all
the
conversions
there's,
some
of
them,
that
after
they
introduced
interpolate,
caused
a
bunch
of
problems,
so
we're
kind
of
unfold.
Those
and
but
all
that
all
the
important
ones
and
easy
ones
are
in
which
is
great,
and
then
we've
just
got
the
rest
of
the
normal
tracking.
So
those
aren't
release
blockers
is
just
kind
of
progress.
We're
making
towards
improving
backdrop,
there's
also
a
bunch
of
CSS
cleanup.
A
That's
been
done
in
Drupal
8,
like
standardizing
on
file
names
standardizing
on
and
the
way
that
you
identify
right
to
left
with
a
set
a
selector
rather
than
a
separate
stylesheet.
That
gets
added
just
some
cleanup
stuff
like
that.
That
was
generally
really
good
idea
done.
Interpolated.
We
want
to
do
the
same
thing
in
backdrop.
We
went
through
most
of
those
issues
and
it
looks
like
more
than
half
of
those
are
in
which
is
really
good
and
then
for
JavaScript.
A
Similarly,
we
went
and
ruined
ge'ez
hint
on
all
the
JavaScript
files
and
core,
and
most
of
those
have
been
cleaned
up
as
well.
So
we
are
kind
of
nearing
the
end
of
improvements.
There
there's
a
couple
left
that
are
probably
pretty
easy
to
just
go
ahead
and
do
if
anyone
wants
you
know,
has
five
minutes:
free
nice
to
them
as
a
poor
request.
But
again
we're
now
point
where
none
of
those
or
release
blockers
I
think
we're
in
pretty
good
shape
in
terms
of
CSS
and
JavaScript
clean
up
in
html5
elements.
A
So
you
know
easy
low
picking,
but
nothing
there.
That's
going
to
prevent
us
from
releasing,
which
is
awesome
and
we've
got
some
other
small
projects
we're
working
on
too.
So
in
continuing
the
main
of
trying
to
I
separate
our
identity
from
Drupal
we're
trying
to
make
the
administrative
theme
look
a
little
bit
different.
A
We
have
a
style
guide
for
our
website
and
we're
going
to
try
and
create
a
style
guide
for
the
admin
theme
to
that
can
if
it
wants
to
use
some
of
those
same
elements
so
fonts
and
colors
and
stuff
can
be
recycled.
If
we
want
to
do
that
and
I
know,
Julia
spent
some
time
working
on
a
first
Jack.
Do
that
I
looked
a
little
bit
at
her
version
of
the
code,
but
I
couldn't
actually
see
the
changes,
I,
don't
think
cuz.
A
They
were
on
a
different
branch
and
I
wasn't
sure
how
to
make
the
code
she'd
written
actually
apply
to
the
style
guide
so
check
in
with
her
and
see.
If
she
can
tell
me
how
to
do
that,
but
but
there
is
a
whole
bunch
of
progress
under
that
in
terms
of
our
rebranding
as
well,
and
we're
probably
also
going
to
need
that
same
kind
of
rebirthing
on
the
Installer
page
too.
But
it
already
looks
you
know
one
hundred
percent
better
with
just
the
different
logo
on
it.
A
We've
got
some
user
experience,
improvements
underway
as
well,
so
we'd
like
to
add
a
rich
text
editor
in
core.
We
have
an
idea
on
a
plan
on
how
to
do
that.
The
issue
for
that
is
101
and
we
just
need
someone
to
actually
do
it.
So
if
anyone
is
particularly
interested
in
making
sure
the
backdrop
gets
rich
text,
that
would
be
the
place
to
go,
and
we've
got
some
more
terminology
updates
to
kind
of
help.
People
navigate
a
little
bit.
A
A
We
did
some
cleanup
on
how
the
people
config
section
works
too,
so
hopefully
they'll
be
a
little
bit
more
intuitive
for
people
and
rather
than
just
kind
of
sticking
that
stuff
like
out
in
the
middle
of
the
people
section
where
you're
managing
people,
which
I
think
will
be
good
and
we've
got
theme
system,
cleanup
underway
as
well.
We've
got
a
whole
bunch
of
consolidation
in
proper
use
of
theme
of
suggestions
that
I
has
already
done.
A
Moved
in
we've
got
a
bunch
more
there's
a
couple
of
major
things
that
need
to
happen
for
the
team
system,
like
the
addition
of
the
new
hook
that
went
Hatton,
use
time
before
release
and
then
removal
process
layer
that
are
both
going
to
be
a
little
tricky.
But
everything
else
I
think
is
just
you
know,
improvements
that
we
could
ship
without.
We
had
to
there's
already
a
lot
of
progress,
that's
making
it
better.
A
So
we
can
just
it's
a
good
place
to
jump
in
if
you
wanna
jump
in,
but
it's
not
as
important
to
see
of
my
conversions
and
then,
let's
see
so
I
think
that's
it
in
terms
of
our
minor
projects
that
we're
working
on,
there's,
obviously
a
whole
bunch
of
other
issues
in
the
queue
that
we
don't
talk
about
in
this
meetings,
they're
less
important
than
these
ones.
But
if
there's
anything
that
you
know,
you
really
want
to
see
happen
in
backdrop.
A
Just
create
an
issue
and
we
can
figure
out
if
it's
super
important
and
needs
to
be
part
of
a
meta
or
coming
to
this
issue
or
whatever.
But
we
kind
of
have
our
priorities
that
a
lot
of
work
ahead
of
us
so
Laurie
on
right
now,
and
we
have
a
section
in
this
weekly
meeting
to
have
a
updates
from
the
PMC.
We
don't
have
any
updates,
it's
just
kind
of
business
as
usual
right
as
much
good
as
you
can
run
a
bunch
of
tests.
A
That
kind
of
thing
I
think
we
are
looking
to
expand
the
PMC.
So
I
say
this
every
week
to
if
you're
involved,
in
fact,
job
and
active
an
issue
queue
or
active
in
this
meeting,
you're,
not
an
issue
queue
type
person.
We
do
our
art
/
eyes
open
for
new
people
who
might
be
good
potential
candidates
for
that
in
terms
of
things
that
we're
working
on
it
is
not
directly
related
to
the
code
of
the
project.
We
need
an
API
website.
A
To
know
you
know
how
do
I
poured
a
module
in
order
to
have
porta
modular,
getting
a
PA,
so
I
will
change
notices
on
it
and
they're
going
to
need
to
know
what
modules
have
already
been
ported.
A
We've
got
some
start
underway
and
a
couple
of
these
things,
but
we
don't
have
anything
done
yet.
So
if
anyone
wants
help
with
those,
we
use
that
as
well,
and
we
obviously
have
some
more
plans
for
our
primary
website.
We're
gonna
convert
it
to
backdrop.
We're
also
going
to
add
some
pages
for
showcase,
which
we
have
some
other
websites
running
back,
Jeff
we're
going
to
set
up
much
of
Cynthia's
pages
and
maybe
a
way
for
people
to
register
themselves.
A
As
you
know,
backdrop,
businesses
or
people
who
will
bid
build
websites
on
backdrop
if
clients
are
interested
in
that,
so
that
some
long-term
plans
to
the
website,
but
those
are
obviously
lower
priority
than
getting
the
product
done.
Oh
that's
kind
of
where
we
are
with
those,
and
then
we
have
Sprint's
every
Thursday
after
this
weekly
meeting
last
week
and
I
had
to
run
off
on
Thursday
and
run
an
errand.
So
we
did
backdrop
day
on
Saturday
instead
which
actually
isn't
working
out
really
well.
A
There
was
no
phone
calls
or
emails
to
disrupt
us,
so
we
just
went
ahead
and
crank
through
a
whole
bunch
of
pull
requests
and
he
committed
everything
which
is
amazing.
So
we
got
a
bunch
done
that
way,
so
I'm
hoping
that
we
can
get
equally
as
much
done
today
and
we'll
see
how
that
goes,
and
then
next
week
actually
I'm
going
to
out
of
town
I'm
going
to
be
in
canada.
A
The
out
of
the
country
in
there
farrah
northern
neighbor
but
nate,
do
you
want
to
try
and
run
this
meeting
next
week,
yep.
A
Neat
needle
be
in
charge
into
the
meeting
I'll
set
up
the
agenda
and
everything
to
try
and
make
it
as
easy
as
possible
on
you,
but
that'd
be
great.
If
you
could
do
that
and
then
we've
got
two
camps
coming
up:
we're
we're
doing.
Backstrap
keynotes
drupal
corn
in
iowa
in
20
days,
drupalcamp
in
minneapolis,
so
I
think
that'll
be
really
fun.
A
We
can
kind
of
you
know
it's
been
a
while,
since
we've
been
in
out
in
the
Drupal
community,
since
we
missed
triple
bond
Austin
that'll
be
going
to
go
talk
to
people
and
show
everyone
you
know.
What's
going
on
now,
like
it's
been
a
while,
since
a
lot
of
people
have
seen
backdrop
and
have
its
new
logo,
it's
your
name
and
add
menu
Accord
a
whole
bunch
of
other
neat
stuff,
I
think
it'll
be
fun
to
be
like.
A
Look
it's
better
than
Drupal
7,
tall
and
kind
of
start
to
show
like
a
little
more
of
the
future,
rather
than
what
they've
already
been
see.
So
that's
super
exciting.
Is
there
anything
else
that
we
should
add
to
this
weekly
agenda
or
anything
else
that
anyone
wants
to
bring
up
or
talk
about?
What
we're
here.
A
Okay,
all
right!
Well,
it
looks
like
we've
got
six
viewers
today,
that's
a
great
number,
so
hi
people
thank
you
for
watching
we're,
gonna
go
ahead
and
hang
out
in
IRC,
I
guess
for
the
stuff
in
the
noon.
So,
if
anyone
who
is
watching
the
video
has
questions
for
us,
you
can
also
happen
over
there
and
ask
otherwise.
We
will
do
this
again
next
week.