►
From YouTube: Backdrop CMS 6/26 Weekly Hangout
Description
Weekly status meeting! Agenda is at http://bit.ly/1iz6N0g.
A
As
always,
we
start
these
meetings
with
an
overview
of
backdrops
goals
and
purposes
which
are
that
we're
aiming
to
make
a
continuous
version
of
Drupal,
basically,
the
next
version
of
Drupal
that
will
still
be
largely
compatible
with
Drupal
7,
making
it
so
that
all
of
the
existing
sites
out
there.
All
of
the
people
who
have
done
a
large
amount
of
investment
in
Drupal
7
have
a
platform
that
they
can
move
to
without
needing
to
rewrite
their
entire
site.
So
backdrop
aims
to
provide
Drupal,
8,
comparable
features
on
a
Drupal
7,
like
architecture.
A
A
Just
one
second:
okay:
here
we
go
so
let's
see
we're
trying
to
simplify
some
existing
systems
more
time
to
reduce
the
number
of
drupal
isms
and
make
it
so
that
people
can
onboard
much
more
easily
and
we're
adding
new
features
things
that
users
will
expect
in
this
day
and
age
out
of
a
CMS,
so
timeline
wise,
we're
planning
to
release
backdrop
1
point
0
sometime
this
summer,
which
is
a
tight
timeline.
We're
going
to
see
how
well
that
all
pans
out
the
biggest
hold
up
so
we'll
get
to
further
on
in
the
progress
report.
A
The
major
projects
projects
we've
got
going
on
right
now,
the
biggest
of
which
is
probably
blocks
and
layouts
so
blocks
and
layouts
is
something
that
we're
trying
to
do
in
backdrop
to
really
differentiate
ourselves
from
from
Drupal
8,
we're
working
on
rewriting
the
block
system
and
making
so
that
blocks
have
contexts
and
can
be
used
multiple
times
per
page
and
can
be
placed
in
different
regions
per
page
and
each
page
can
have
its
own
different
region.
Essentially,
essentially,
it's
like
panels.
It's
basically
a
panels
like
system,
but
with
a
simplified
UI.
A
So
it's
not
it's
not
so
complicated
and
difficult
to
wrap
your
head
around
like
panels
itself
is
things
with
blocks
and
layouts.
That's
been
my
primary
goal
over
the
past
couple
of
weeks
and
it's
moving
along
pretty
well
recently
in
issue
86,
you
can
see
progress
as
that's
moving
along.
We
got
integrated
with
the
new
dialogue
system
that
we
added
a
couple
of
months
ago.
Layouts
to
menu
items
can
be
created
and
saved
into
the
configuration
system
and
we're
just
now,
starting
on
actually
arranging
laying
out
the
blocks
on
the
page
so
moving
along
there.
A
It's
still
still
going
to
be
tight
to
try
to
get
that
all
all
done
before
before
the
end
of
the
summer,
but
we're
going
to
keep
pushing
forward
on
it.
The
next
major
item
views
in
core
views
and
Cory's
been
in
backdrop
for
last
four
or
five
months,
and
it's
it's
looking
really
good.
It's
it's
largely
compatible.
A
We've
converted
it
to
use
the
new
dialogue
system
as
well,
but
there's
just
a
couple
of
places
where
we
need
fuse
to
be
converted
in
core
itself
and
if
anybody
is
interested
in
helping
with
that
issue,
it's
issue
151
in
our
github
issue,
queue
and
we're
moving
along.
We
really
just
need
to
convert
a
couple
of
things
like
the
administrative
listings
and
the
front
page
to
finish
up
the
views
and
core
initiative.
A
So
the
next
item
is
configuration
management.
We've
had
the
base
system
in
place
for
configuration
management
probably
longer
than
anything
else
in
terms
of
really
big
changes.
So
we've
got
a
lot
of
things
converted
to
it
already
views
image.
Styles
contact
module
a
good
number
of
variables,
but
we
still
have
a
bunch
more
of
these
to
go
and
of
all
the
things
that
we're
working
on
in
backdrop.
A
For
one
point:
no
configuration
management
getting
everything
converted,
including
like
fields
and
content
types,
is
really
our
biggest
hold
up
for
release,
and
so,
if
anything
needs
attention,
it's
converting
things
to
configuration
management.
I
know.
Jen,
says
that
she's
going
to
take
the
lead
on
that
since
she's
completed
the
Drupal,
7,
backports
or
cross
supports,
so
we're
pretty
much
wrapped
up
with
those
so
she's
going
to
turn
our
attention
to
configuration
management.
A
So
if
anyone
is
out
there
and
helping
are
interested
in
helping
with
issue
1
69
get
in
contact
with
Jen
Lampton
she's,
usually
in
IRC,
but
she's
out
today
likes
next
week.
It
probably
could
be
a
good
time
to
reach
out
to
her
or
just
post
a
comment
on
it.
She
169
and
we
would
be
more
than
happy
to
help
anybody
on
board
on
the
backdrop
to
get
them
working
on
configuration
management.
A
So
those
are
three
main
issues
that
were
hoping
to
complete
for
Rebecca
up.
One
point
of
blocks
and
layouts
using
core
and
configuration
management
we've
been
doing
a
bunch
of
minor
work
as
well,
trying
to
just
make
sure
that,
when
backed
up
one
point
out
comes
out,
it
has
all
of
the
functionality
that
you
would
expect.
A
Probably
most
important,
but
not
particularly
very
difficult,
is
keeping
up
with
Drupal
7,
so
Drupal
7
has
a
bunch
of
stuff
and
they're
still
improving
documentation
on
Drupal
7
fixing
security
issues
on
Drupal
7,
even
though
the
dribble
release
cycle
doesn't
really
add
allowing
new
features
to
be
added
within
a
single
release
cycle
in
Drupal
7.
We're
still
making
sure
that
we
keep
up
with
everything
that
happens
in
Drupal
7,
so
that,
when
backdrop
1
point,
0
is
released
it
as
all
of
the
same
security
fixes
and
bug
fixes
and
everything
else.
A
So
we've
already
ported
a
lot
like
800
some
issues
from
Drupal
7
over
to
backdrop
to
make
sure
that
we're
keeping
up
with
everything
that
triple
7
is
doing.
We've
just
now
added
a
new
security
update,
so
that
will
be
up
to
date
with
the
latest
version
of
Drupal,
7
27
and
we've
got.
It
looks
like
about
looks
like
about
80
issues
left
to
backport
or
to
cross
port
over
to
22
backdrop,
but
most
of
those
are
really
minor
things.
Fixing
tests,
documentation
things
and
things
like
that,
so
drupal,
8
backports.
A
This
is
things
that
we've
been
doing
to
make
it
so
that
the
functionality
that
is
in
Drupal
8
is
also
in
backdrop
and
there's
a
lot
of
these
like
thousands
of
issues
that
could
potentially
be
backported.
However,
a
huge
number
of
those
won't
ever
be
back
ported
to
backdrop,
because
we're
not
including
a
lot
of
the
conversions
that
make
dribble
a
difficult
to
move
to.
A
So
some
of
the
areas
that
were
specifically
focused
on
right
now
is
making
sure
that
all
of
the
html5
enhancements
all
gets
moved
back
into
backdrop
and
more
about
three
quarters
of
the
way
through
those
we're
also
making
sure
that
the
CSS
free
architecting,
the
simplification
of
classes
and
things
like
that
is
also
happening,
and
what
four-fifths
of
the
way
through
those
and
we're
making
it
so
that
all
of
our
JavaScript
gets
updated
so
that
it's
passing
jslint
tests
and
updated
it
properly.
Enclosed
uses
the
latest
version
of
jQuery
those
sorts
of
things.
A
So,
let's
see
some
other
minor
projects
that
we're
also
working
on
so
the
first
one
that
we've
got
here
is
separating
our
identity
from
Drupal,
because
Drupal
owns
the
name
and
and
trademark
of
the
word.
Drupal
Drupal
in
the
future
will
come
to
mean
something
very
different
than
than
what
Drupal
means
today,
as
the
as
the
architecture
completely
changes
underneath
it
Drupal
will
become
something
else
in
the
future.
A
With
with
the
Drupal
8
release,
and
so
in
order
to
establish
ourselves
and
make
it
so
that
we
can
document
and
have
our
own
identity,
we've
started,
making
sure
that
everything
throughout
all
the
backdrop
is,
is
branded
as
backdrop
instead
of
Drupal.
So
there's
a
couple
of
areas
that
we've
making
real
progress
on
this
we've
updated
all
of
the
source
code
to
replace
the
word
Drupal
with
backdrop,
and
that
includes
class
names
and
functions
and
variables
pretty
much
everything
and
added
a
compatibility
layer
in
there
that
is
turned
on
by
default.
A
That
makes
it
so
that
everywhere
that
you
used
to
reference
triple.
You
now
say
backdrop,
but
if
you
still
reference
Drupal,
that's
fine!
Everything
will
continue
to
work.
All
of
the
functions
are
wrapped
making
it
so
that
people
moving
from
triple
the
backdrop
have
an
easy
time,
getting
their
modules
initially
converted
and
up
and
running
in
a
really
short
amount
of
time.
But
we've
gone
through.
A
We've
got
a
really
awesome
logo
that
Darius
has
put
together
for
us
that
you've
probably
seen
around
the
interweb,
and
it
looks
great-
we've
got
it
on
all
of
our
branding
pages.
We've
got
it
on
our
site
now
and
we've
got
it
into
backdrop
itself,
so
there's
no
more
drupalcon
and
in
fact,
drop
which
is
kind
of
sad
but
but
necessary.
Really,
we
don't
really
have
any
choice
to
continue
using
Drupal
branding
as
Drupal
itself
changes
into
something
else.
A
Let's
see
that's
just
about
it
for
separating
the
identity.
The
next
things
we've
got
here
is:
we've
got
a
number
of
user
experience,
improvements,
we're
working
on
moving
ckeditor
module
into
core,
which
I
did
a
lot
of
work
on
in
the
Drupal
8
psycho
already,
so
we've
already
made
some
progress
on
that
kind
of
indirectly.
A
Things
like
the
dialogue
system
and
some
JavaScript
updates
we're
necessary
in
order
to
put
ck
editor
into
core
and
Drupal
8,
and
we've
already
got
those
underpinnings
in
place
for
for
backdrop,
but
we
haven't
yet
to
actually
started
moving
forward
on
converting
ckeditor
module
into
a
backdrop
module.
So
that's
an
issue
that
is
a
big
one,
that
we'd
love
to
have
out
before
the
one
point:
0
release
and
that's
issue.
101
in
the
backdrop
issue
queue
terminology
updates.
A
This
is
a
just
a
number
of
minor
improvements,
since
we've
moved
admin
menu
in
decor,
the
way
our
terminology
works
and
lists,
we
could
make
some
changes
to
make
it
so
that
things
could
be
easier
to
find.
Drupal
8
did
a
couple
of
these
things
as
well,
like
changing
the
modules
page
to
extend,
for
example,
and
that's
just
the
way
it's
listed
in
the
new
system
with
backdrop,
because
we
have
hierarchical
menu
system
that
has
dropdowns
kind
of
actually
unlike
Drupal
8,
which
as
a
toolbar,
but
it's
not
actually
a
very
hierarchical
menu.
A
We're
likely
to
do
things
like
change.
The
top-level
item
of
modules
to
extend
just
like
drupal
8
did
but
then
leave
the
modules
page
as
modules,
so
in
the
drop-down
you
would
select,
extend
and
then
modules
as
the
first
item
making
it.
So
that's
kind
of
both
the
terms
are
still
there
and
it
increases
the
searchability,
because
we've
got
a
search
in
the
admin
toolbar
as
well.
We
want
people
to
be
able
to
search
for
either
word
and
make
sure
they
can
land
on
the
right
page.
A
Let's
see
the
last
minor
issue.
We
have
is
theme
system
cleanup.
As
many
people
know,
jen
Lampton
was
headed
up
heading
up
the
twig
initiative
and
Drupal
8,
we're
not
including
twig
in
in
backdrop
for
compatibility
reasons
making
it
so
that
people
can
continue
to
use
their
existing
code
and
also
for
performance
reasons
and
simplicity,
but
theme
system
cleanup.
We
can
still
do
a
lot
to
make
the
overall
theme
system
a
lot
simpler
doing
things
like
we're,
trying
to
remove
the
process
layer,
not
the
preprocessed.
A
I
put
the
process
layer
and
remove
one
of
those
layers
of
complexity
and
minimizing
the
number
of
templates
that
we
have
doing
a
lot
more
template
sharing
minimizing
our
class
usage,
making
it
consistent
all
of
those
sorts
of
things
we're
still
working
on
incorporating
into
backdrop
itself,
and
that
issue
is
issue
125.
If
anyone
out
there
is
interested
in
helping
work
on
it,
we
also
have
some
sections
in
our
weekly
meetings.
Every
week
we
talked
about.
If
we
have
any
updates
from
the
project
management
committee.
A
The
project
management
committee
currently
consists
of
simply
Jen
and
myself,
and
we
don't
have
any
outstanding
items
this
week
on.
Regarding
my
conflict
resolution
or
decision
making
more
or
anything
like
that,
we
are
always
looking
for
additional
members
to
help
run
the
project
most
of
both
as
committers
and
as
members
of
the
PMC.
So
if
anyone
is
out
there
that
is
interested
in
in
working
on
backdrop,
then
just
get
involved
in
the
issue
queue
or
contact,
generai
and
we'd
love
to
talk
to
you.
A
As
changes
happen
in
the
code
itself,
when
backdrop
one
point
L
is
released,
we
need
an
update
server
to
make
it
so
that
the
installations,
a
backdrop
out
there
can
connect
to
the
updates
over
to
see
if
new
versions
of
modules
are
available
and
a
new
version
of
backdrop
itself,
and
so
we're
working
on
setting
that
up
as
part
of
our
our
main
infrastructure
site
and
speaking
of
updates.
We
need
a
way
to
actually
collect
and
list
all
of
the
available
modules
for
backdrop
in
a
central
location.
Our
current
plan,
for
that
is
leveraging
github.
A
Essentially
a
github
would
be
where
the
code
is
hosted
and
where
issue
hughes
would
live,
but
then
having
github
register
through
a
github
service.
With
backdrop,
CMS
org
itself
to
build
a
list
of
all
officially
officially
supported
modules
on
backdrop,
CMS
or
gets
self,
so
so
basically
still
have
a
module
browsing
and
downloading
capability
like
triple
that
work
does,
but
all
of
the
code
itself
is
hosted
on
github.
A
Let's
see
and
the
last
thing
is
continuing
to
work
on
our
flagship
site,
backup,
CMS
org
right
now-
we've
got
kind
of
intentionally
a
wireframe
kind
of
driven
website,
but
we've
got
some
plans
to
get
like
a
full
redesign
and
some
some
more
branding
going
on
on
the
domain
flagship
site.
So
we've
got
some
some
designers
working
on
that,
but
we
we've
got
a
lot
of
other
things
to
do
before.
We
decide
to
spend
too
much
time
on
on
the
flagship
site
itself,
all
of
those
of
their
peripheral
sites.
A
Right
now,
the
the
backup
CMS
torg
does
what
it
needs
to
do
in
terms
of
information,
but
we
need
to
start
working
on
building
out
so
that
it
sports
things
like
the
update,
server
and
contribute
listings,
and
things
like
that.
So
we
have
Sprint's
every
Thursday,
that's
today
after
the
weekly
meeting,
so
I'm
going
to
be
in
the
queue
working
way
continue
to
do
some
back
ports
as
well
as
blocks
and
layouts.
A
But
if
anybody
is
interested
in
helping
with
backdrop
I'll
be
in
IRC
today
and
I'd
be
more
than
happy
to
point
you
guys
in
in
the
right
direction.
Let's
see
we're
always
in
IRC
on
freenode
in
pound
backdrop,
and
later
this,
let's
see
next
month,
we're
also
going
to
be
at
drupal
coin
in
Des,
Moines,
Iowa,
Jen
and
I
are
both
going
to
be
there
we're
going
to
be
doing
a
keynote
stock
and
we're
both
also
going
to
be
at
the
Twin
Cities
drupalcamp
in
august
august,
seven
through
10th.
A
So
if
you're
interested
in
meeting
up
with
some
of
the
people
from
backdrop,
we're
going
to
be
it
a
couple
of
drupal
events
here
in
the
near
future,
let's
see
we've
got
a
couple
other
things
for
publicity.
We
recently
included
it
in
an
article
and
drupal
watchdog,
if
you
flip,
through
all
of
you,
flip
through
all
of
the
50
pages
of
Drupal
8
articles.
A
At
the
very
end
of
the
magazine,
there
is
an
article
on
backdrop,
just
kind
of
as
a
as
a
contrast
to
talk
about
what
backdrops
goals
are
and
what
we're
interested
in
doing.
If
you've
been
joining
these
meetings,
you
probably
already
know
most
of
it,
but
if
you
haven't
pick
up
a
copy
of
triple
watchdog
and
check
out
our
article
in
there.
A
Well,
since
this
is
pretty
much
a
solo
meeting
here,
we
don't
really
have
any
need
for
questions,
so
thank
you.
Everyone
for
for
joining
for
watching
I
see
that
we've
got
a
couple
online
viewers
already
thanks,
hi
guys
and
we'll
be
meeting
again
next
Thursday,
hopefully
with
the
large
team.
So
thanks
everyone
for
watching
and
I'll
see
you
next
week,
bye.