►
From YouTube: Backdrop CMS Weekly 2/6
Description
Weekly status meeting for Backdrop CMS. Today's agenda: http://bit.ly/1bayNB4
A
Thank
you
all
right,
we're
on
air.
Okay.
So,
let's
see
backdrop
weekly,
thank
you
everybody
for
joining
the
call.
So
far
it's
andy
Nate
myself,
we're
hoping
victor
will
be
able
to
join
us,
and
we
I
know
there's
two
sneaky
viewers.
I
expect
one
of
them
is
Luke.
Hi,
Luke
I
think
that
one
is
we're
watching
it
work
and
not
able
to
participate.
We
appreciate
your
watching
and
we
look
forward
to
getting
your
emails
and
everything
else
later
as
usual.
A
Yes,
definitely
we're
going
to
talk
about
a
bunch
of
stuff
today
that
we
need
help
with.
So,
if
any
of
you
see
or
hear
anything
that
you
are
interested
in
working
on,
let
us
know-
and
we
will
plug
you
n,
where
we
should
the
goals
for
backdrop
are
to
create
an
affordable
version
of
a
open
source
CMS.
That
will
continue
to
make
everybody
really
happy
for
a
long
time
to
come.
A
We
realized
there's
a
cost
that
comes
with
change
and
we
want
to
create
a
Drupal
8,
a
comparable
tool
on
a
architecture
of
more
like
drupal
7
has
everybody
knows
and
loves
triple
sevens.
We
want
to
keep
going
in
that
vein
and
add.
New
features
are
visually
excited
about
that
they
would
get
from
Drupal
8.
So
that
will
include
backdrop
will
include
all
of
the
bug
fixes
that
have
currently
gone
into
Drupal
7.
A
All
the
bug
fixes
that
are
currently
going
into
Drupal,
8
and
new
bug
fixes
that
we
might
find
along
the
way,
as
well
as
a
bunch
of
features
that
we'd
like
to
get
in
like
views
and
cmi,
and
if
there
won't
be
changing
too
much
of
api's
we'd,
also
like
to
simplify
existing
system,
so
where
we
think
current
architecture
of
Drupal
7
could
use
a
little
work.
We'd
like
to
clean
that
up.
A
But
if
it
requires
too
much
API
change,
then
we
won't
be
able
to
do
so
and
we'd
also
like
to
add
some
new
features.
Again.
This
will
mean
not
requiring
too
much
of
existing
api's,
but
adding
new
AP
ice
is
allowed.
So
if
we
can
get
something
like
a
box
and
layout
system
in
place,
that
would
be
super
killer
and
we'd
love
to
do
that
before
backdrop
releases.
A
A
So:
yes,
as
soon
as
the
blow
issues
are
resolved,
so
the
following:
keeping
up
with
Drupal
so
making
sure
we
get
back
parts
of
all
those
bug
fixes
in
both
from
triple
seven
in
Drupal
8.
We
need
to
get
those
done.
We
also
need
to
get
cmi
fully
converted
the
core
is
in,
but
we
need
to
get
it
done.
We
need
to
get
view
fully
converted.
A
We've
got
the
core
of
that
in
as
well,
but
we
need
to
get
all
those
conversions
done
and
as
soon
as
those
three
things
are
done,
we
could
in
fact
ship
backdrop.
One
we'd
also
like
to
get
a
blocks
and
layout
system
in
but
of
course,
will
depend
on
how
much
of
our
effort
is
spent
doing
other
stuff
and
how
much
time
we
have
for
meeting
so
a
little
update
on
those
major
projects,
config
management,
I'm,
not
sure
much-
has
changed
since
last
week.
A
I
know
we
are
waiting
for
Victor
to
come
back
so
that
we
can
find
out
not
only
how
things
went
in
South
America,
but
also
if
he
was
interested
in
taking
over
the
cmi
kind
of
meta
idea
of
what's
left
and
help
us
create
lists
of
easy
me
easily
manageable
tasks
that
people
can
take
on
and
I.
Don't
know
if
there's
anything
else
going
on
with
DMI
yeah.
B
There's
not
really
any
significant,
significant
updates
since
last
week,
but
for
anybody
that
that
hasn't
heard
able
to
see
my
base
system
in
and
we
have
a
new
state
system
and
for
converting
environment
specific
variables.
That's
ready
to
go.
That
is
we've
already
converted
some
variables,
but
we
still
have
a
lot
of
a
lot
of
variables
level.
A
lot
of
variable
gets
and
a
lot
of
variables
sets
to
convert
to
state
set
state
get
or
config
gettin
can
fix
it.
So
a
bunch
of
variables
that
need
to
be
converted
and
we
have
the
basics.
B
We
have
image
styles
and
views
currently
that
are
using
the
config
system,
but
that
obviously
leaves
a
lot
left
to
convert.
Most,
notably,
you
know,
content
types,
vocabularies
fields,
all
of
those
things
so
between
the
variables
and
the
type
conversions
we've
got
a
lot
of
work
to
do,
but
yeah
well,
we'll
see,
if
Victor's
interested
in
doing
that.
Otherwise
we
might
need
to
swim
back
around
and
start
picking
some
that
stuff
up
yeah.
A
I
think
if
he
doesn't
join
in
today's
meeting,
I
will
go
ahead
and
start
on
that
meta
issue
and
then,
if
he
gets
in
touch
with
us
sometime
between
eight
today
next
week's
meeting,
we
can
just
hand
that
off
to
him,
but
I
think
we'll
be
good.
Just
to
have
that
list
done
because
that'll
give
us
an
idea
of
what's
ahead
of
us
here.
Yeah.
A
A
B
Yep
so
and
in
the
views
and
core
area
views,
bulk
operations
has
been
pulled
in
and
committed
that
vbr,
the
views
and
core
business
got
down
a
little
bit
of
a
rabbit
hole
because
vbo
depended
on
nada,
p,
I
and
Drupal
7.
So
we
had
to
update
entity
our
energy
system
in
backdrop.
So
now
all
of
our
entities
are
actual
objects.
So,
let's
nodes
in
terms
and
comments
and
users
and
things
like
that
but
other
but
other
than
the
fact
that
they're
real
objects
like
the
API
is
essentially
unchanged.
B
So
all
of
those
functions
still
exist,
but
you
can
also,
in
addition
to
saying
node,
underscore
save
the
node
object.
You
also
can
say
no
to
object,
arrow,
save
and
so
basically
just
makes
it
so
you
can
interact
with
it
in
a
procedural
way
or
in
an
object-oriented
way,
but
yeah.
It's
basically,
basically
an
API
expansion
so
that
you
can
act
on
entities
equally
proof.
So.
A
B
Deprecated,
the
node
underscore
saves
for
backdrop
to
I
I,
think
that's
probably
long-term
goal,
but
considering
our
entire
purpose
is
trying
to
make
it
so
that
people
can
port
easily
from
Drupal,
7
or,
let's
say
poor
easily
from
the
previous
version,
and
for
now
and
all
time,
yeah
we'll
see-
and
you
know
a
year
from
that
stage-
yeah
so
so
anyway.
So
VPO
is
looking
really
good.
B
We're
ready
to
extra
start
doing
conversions
like
getting
the
admin
listings,
converted
like
the
user
listing
abusers
in
the
listing
and
nodes,
and
some
of
those
issues
still
have
a
little
bit
of
effort
that
are
that
is
required
because
things
like
users
have
the
special
thing
for
canceling
user
accounts
that
that
needs
to
be
handled
so
so
we'll
need
to
expand
the
existing
vbo
integration.
But
the
basics
are
oral
in
place
and
you
can
set
up
a
vp
of
you
to
do
bulk
things
now
so
yeah
it
doesn't.
B
Oh
ok,
that's
blocks
and
Lance
ok
anyway.
So
using
course
still
coming
really
nicely
I
think.
Once
this
video
stuff
wraps
up
I
mean
that'll,
be
that
would
be
the
primary
areas
for
all
of
these,
and
core
abuses
is
much
more
converted
than
everything
else
is
like.
We
don't
have
any
variables
and
views
we
don't
have
any
like.
All
of
the
tests
have
already
been
converted.
It's
using
config
management,
so
views
is
actually
like
of
all
things
like
sitting
in
the
best
place
right
now
so
yeah
it
will
keep
chugging
along
on
that
great.
A
So
it
also
looks
like
we
need
someone
to
kind
of
take
over
the
management
of
the
meta
issue.
Abuse
too
so
I
don't
know
if
matt
is
a
nurse
in
doing
that
or
if
we
want
to
flag
down
someone
else,
but
it
will
be
good
just
to
kind
of
have
someone
keep
an
eye
on
the
little
tasks
that
remain
based
on
reviews,
stuff
I
get
our
like.
You
know
admin,
page,
conversions
and
stuff
like
that,
all
in
a
row
yeah.
C
A
At
least
a
manageable
amount,
okay,
so
blocks
and
layouts
is
next
on
our
list
here.
This
is
something
that
again,
we
could
ship
backdrop
without
it,
but
I
think
that,
in
terms
of
differentiating
ourselves
from
Drupal,
it
would
be
nice
to
get
some
features
that
are
distinctly
different
blocks.
Lance
is
something
that
Drupal
8
tried
to
work
on
and
never
actually
got
done.
So
if
we
could
find
a
way
to
get
this
done,
I
think
it
would
be
good
differentiator
between
us
and
them,
and
we
have
some
really
great
ideas.
A
The
things
that
Nate
and
I
talked
about
in
terms
of
making
kind
of
a
panels.
Light
type
interface
seem
to
really
jive,
with
the
same
interface
that
boullion
had
been
working
on
for
Drupal
8
back
before
that
project
got
sidelined
and
so
I
think
that
we're
in
a
really
good
place
in
terms
of
having
a
Polian.
We
just
need
to
figure
out
all
of
the
bits
that
go
along
with
that,
make
sure
that
we
can
get
it
done
and
not
change
too
much
about
how
things
work
currently.
A
So
I
don't
think,
there's
been
very
much
work
on
this
lately
yeah,
but
but
if
anyone
is
super,
passionate
about
blocks
and
layouts
or
perhaps
panels
or
maybe
passionate
against
panels,
probably
good
to
have
you
on
fox
and
layouts
team,
so
we
can
figure
out
how
to
not
make
the
same
mistakes
that
were
made
before
or
how
to
make
significant
improvements
in
flux.
Anyone
yeah,
who
has
any
strong
feelings
about
it,
should
feel
free
to
get
involved.
Now
it's
a
good
time
to
help
us
kind
of
shoot
the
future
there.
A
So
we've
got
a
couple
of
minor
projects
that
I
think
are
also
really
important
for
backdrop.
User
experience
is
something
that
I
am
particularly
passionate
about.
There's
a
lot
of
kind
of
silly
things
that
drupal
does
that.
We
know
that
we've
been
fighting
for
a
really
long
time,
based
on
usability
studies
and
just
you
know,
giving
Drupal
sites
to
clients
and
listening
to
them
complain
about
it
and
I.
Think
that
that
especially
considering
our
market
is
going
to
be
more
of
the
do-it-yourselfers,
we
need
to
make
sure
that
Drupal
is
or
excuse
me.
A
They
should
make
sure
that
backdrop
is
really
easy
to
use.
So
there's
a
bunch
smaller
issues
that
we're
working
on
that
you
know
can
be
addressed
one
at
a
time,
but
there's
also
some
bigger
issues
that
we
should
focus
on
I'm.
Getting
a
WYSIWYG
in
core
is
going
to
be
huge,
that's
something
that
you
know.
Drupal
hasn't
done
for
a
really
long
time
and
it's
finally
doing
interpolate
and
if
we
don't
have
backdrop
with
always
waiting
for
everyone's
going
to
laugh
at
us,
that's
definitely
something
we
need
to
work
on.
A
We
want
to
work
on
an
improved
dialogue
system.
These
are
a
little
modal's
that
we
can
use
for
views
and
WYSIWYG
and
there's
a
bunch
of
progress.
That's
happened
on
that
in
Drupal
8,
so
hopefully
we
can
steal
some
of
the
improvements
there
and
and
make
sure
that
we
get
the
same
kind
of
improvements
in
backdrop.
We
need
a
better
tool
bar
the
Drupal
AIT's,
responsive,
toolbar
is
really
awesome
and
I
know.
A
A
lot
of
great
work
has
gone
into
that
it
would
be
like
it
would
be
nice
to
get
some
of
those
same
improvements
into
backdrop
for
for
us
and
and
there's
also
been
a
bunch
of
work
on
the
node,
add
edit
form.
So
the
page
we
go
to
create
or
edit
existing
pieces
of
content
they've
got
two
column
layout.
A
There's
been
a
lot
of
thought
gone
into
how
you
actually
want
that
that
layout,
to
respond
when
you're
working
on
it,
how
a
workflow
integrase
with
all
of
that-
and
it
would
be
good
to
kind
of
evaluate
all
those
changes
and
make
sure
we
get
the
ones
that
we
want
in
impact
drop
as
well
and
then
there's
a
kind
of
a
bigger
task
here
about
redesigning
the
administration
theme.
Originally,
we
all
decided,
we
loved
the
seven
theme.
It's
a
great
administration
theme
for
Drupal
7.
A
Everyone
really
likes
it,
so
we're
like
don't
touch
it
it's
great.
But
after
talking
to
some
people
about
our
strategy
for
this
product
and
our
branding,
it's
become
really
important
that
we
need
to
set
ourselves
apart
from
Drupal
NF
somebody
install
Drupal,
8
and
installs
backdrop,
and
it
looks
exactly
the
same.
That's
not
going
to
do
us
any
favors.
We
want
to
kind
of
set
ourselves
apart,
make
it
feel
different,
make
it
look
different,
and
that
means
that
we're
going
to
need
a
different
administrative
theme
as
well.
A
They're
bigger
things
to
that.
We
can
talk
about
later,
like
reorganizing
menus
and
stuff,
but
I
think
getting
the
most
important
things
done
first,
is
is
going
to
be
crucial
on
that,
so
that's
the
user
experience
task
and
also
needs
someone
to
kind
of
keep
an
eye
on
all
of
these
moving
pieces
and
make
sure
that
we
get
them
done
before
we
need
to
release.
A
So
if
there's
somebody
who
has
a
particular
passion
for
user
experience
and
wants
to
head
this
up,
let
us
know
on
that,
and
then
the
next
issue
is
something
else
near
and
dear
to
my
heart:
cleaning
up
the
theme
system.
This
is
something
that
people
struggle
with
a
front-end
developers,
in
particular
struggle
with
all
of
the
drupal
isms
that
have
made
it
into
drupal
7,
and
I
want
to
work
to
make
the
team
system
make
more
sense
to
people.
A
So
I
would
like
to
start
working
on
that
as
soon
as
we
got
all
of
our
Drupal
7
crafts,
ports
in
and
I've
got
my
own
spreadsheet
of
things
that
I
want
to
change,
but
I
don't
want
to
start
doing
it
if
we're
going
to
be
breaking
patches
to
do
so
so
that
is
currently
on
hold
until
after
the
crafts
ports
will
be
done
so
also
fun
stuff.
If
anyone
wants
to
work
on
cleaning
with
the
theme
system.
A
Oh
definitely,
let
me
know
about
that,
and
so
in
terms
of
other
stuff
we're
working
on,
we
are
underway.
On
the
backdrop,
a
CMS
primary
website.
We've
we've
been
working
on
content
strategy,
we're
trying
to
figure
out
what
to
say
and
how
to
say
it.
We've
a
couple
of
primary
pages
outlined
that
are
going
to
be
really
important
for
our
initial
launch
and
then
we've
got
kind
of
a
phase
2
and
phase
3,
where
we
can
add
modules
and
themes,
but
no
sense
of
worrying
about
that
until
we
have
modules
and
themes.
A
So
we've
got
it
all
organized
in
terms
of
what
our
priorities
are:
we're
trying
to
figure
out
what
needs
to
be
set
on
each
page,
how
it
needs
to
be
said
who
our
target
audiences
all
of
that
stuff,
that
developers
are
really
bad
at
oh
we've
got,
we've
got
some
people
helping
us
figure
out
how
to
say
those
things
which
will
be
great
and
then
we've
got
a
team
of
people
lined
up
to
actually
help
us
get
it
done
as
well.
We've
got
Michael
was
gonna
help
us
write
the
content.
A
So,
in
addition
to
our
own
website,
which
looks
like
it's
in
pretty
good
hands
right
now?
What
we're
also
going
to
need
an
update
server,
we're
going
to
need
to
create
an
official
github
service
so
that
people
who
create
modules
and
themes
on
github
will
be
able
to
register
them
as
backdrop
modules
and
themes
and
then
they'll
be
able
to
automatically
appear
on
the
backdrop
website
and
we're
going
to
need
an
API
site
and
I.
A
Think
of
these
things,
the
one
that's
most
urgent
is
the
API
site,
because
we
are
making
changes
to
triple
sevens
api's
and
we're
going
to
need
a
place
to
post
change
records
so
that
people
who
are
interested
in
making
the
upgrade
from
Drupal
7
to
backdrop
can
see
what's
involved
in
and
changes
to
the
api's.
So
it
might
be
good
to
just
kind
of
throw
up
a
Drupal
site
and
just
create
a
place
for
supposed
to
change
notices,
even
if
the
API,
parsing
and
listing
isn't
quite
ready.
A
A
And
we
usually
commit
Thursday's
to
being
back
to
update
at
least
Nate
and
I
do
so.
We
spend
our
thursdays
either
working
on
the
website
are
working
on
the
project
and
so
we're
happy
to
have
little
Sprint's
every
Thursday.
So
if
you
have
some
time
on
a
Thursday
and
you
want
to
get
involved
in
something
you
can
meet
us
in
IRC
we're
usually
working
on
issue
cuse,
then
so
that's
a
good
time
for
us
to
get
together.
There
are
going
to
be
some
camps
that
we're
going
to
be
attending
this
spring
and
summer.
A
C
A
Drupal
corn
in
iowa
we
could
probably
organized
little
backdrop
sprint
there,
so
that'll
be
fun
and
then
I'm
also
going
to
be
attending
a
Florida
drupalcamp
in
mid-march
I.
Don't
think,
there's
actually
going
to
be
any
time
for
sprint,
because
they're
going
to
be
doing
a
coding
for
good
project.
But
if
anyone
wants
to
work
on
anything
and
wants
to
ask
me
about
it,
one
there
I'm
definitely
happy
to
help
you
and
breaks
between
sessions
or
at
the
after
party
printing
needs
to
happen.
B
Andy
I
wanted
to
say
something
about
your
current
pull
request,
the
one
that
you
made
yesterday
or
today,
I,
don't
know
it
looks
really
good
there's
about
like
15
issues
in
there,
which
is
fantastic,
but
the
the
tests
aren't
set
up.
It
looks
like
the
the
tests
dot
info
file
is
missing.
Did
you
do
you
move
it
to
a
test
stud
info
file,
but
not
include
that
in
the
pull
request,
I.
B
B
It
looks
like
it's
got
a
couple
failures,
but
I
think
what
I
would
say
is
don't
worry
about
it
and
I'll
work
on
unresolved,
attest
failure
and
then
just
keep
chugging
along
like
I
think
the
most
valuable
thing
to
do
is
just
keep
applying
the
patches
and
finding
which
ones
are
hard
in
which
ones
are
easy
and
then
just
keep
keep
up
the
steady
stream,
because
it's
it's
so
helpful,
I'd
much
rather
resolve
merge
conflicts
then
then
be
sorting
through
all
of
those
issues.
So
I
really
appreciate
all
the
work
you
put
them
in
there.
B
C
A
C
There
was
some
issues
with
multiple
patches
in
which
you
know
pitch
number
one
wasn't
135
and
then
you'll
come
across
the
same
issue
when
134,
and
so,
if
you
are,
you
know
if,
if
you're,
you
know
doing
it
rapidly
up
multiple
e,
you
can
kind
of
you'll
remember
which,
which
ones
you
picked
up
uh-huh
and
refer
back
to
them.
I
guess
well,.