►
From YouTube: Backdrop CMS weekly meeting 9/11
Description
Backdrop CMS - core status, updates, and more!
A
A
That's
coming
with
your
blade,
we're
here
to
create
a
system
that
has
triple
eight
comparable
features
on
an
architecture,
that's
more
similar
to
that
of
Drupal
7
as
we're
making
that
system,
we
also
can
be
fixing
bugs
so
bugs
that
existed
in
Drupal,
7
and
bugs
that
were
introduced
into
plate
and
any
other
bugs
that
we
find
along
the
way,
where
possible,
we're
going
to
be
trying
to
simplify
existing
systems
and
that'll,
be
while
minimizing
API
change
and
adding
new
features.
Also,
one
not
very
much
api
changes
required.
A
So
new
features
of
new
api's
are
okay.
New
feature
syrup
are
changing.
Api's
need
to
be
carefully
measured
against
our
principles.
Our
timeline
for
releasing
backdrop,
one
point,
0
point
0,
is
that
we'd
like
to
have
it
out
this
fall.
This
false
starts
I
think
in
two
weeks,
so
we
need
to
be
wrapping
up.
A
All
the
things
that
we're
working
on
trying
to
get
everything
ready
and
hopefully
we'll
be
done
before
the
end
ADEA-
will
be
out
in
and
start
working
on
a
trip
after
we
really
stocked
up
one
point:
0
point:
0,
we're
gonna
issue,
regular
releases,
so
every
four
months
or
so
will
gather
a
list
of
things
that
we
want
to
be
in
the
next
release
and
work
towards
getting
those
done
and
released.
It
will
happen
on
time.
A
So
if
we
don't
get
the
feature,
then
that's
fine,
we'll
just
release
about
wherever
we
are
and
the
feature
will
get
pushed
till
the
next
release.
So
we
looking
count
on
releases
on
a
regular
schedule.
Even
if
features
don't
make
individual
releases,
the
release
doesn't
get
pushed
in
terms
of
what
we're
working
on
right.
Now,
we've
got
three
major
projects
that
are
released
blockers.
The
first
one
is
the
blocks
and
layouts
initiative.
A
This
is
a
replacement
for
Drupal's,
page
layout
problem
that
it's
had
for
forever
and
we're
trying
to
put
in
a
really
fancy,
drag
and
drop
panels,
like
version
with
a
new
user
interface,
so
that
it's
easy
to
use
and
makes
for
people.
I
know
you've
been
doing
a
ton
of
work
on
this
to
any
of
us,
an
update
on
blocks
and
layouts
yeah.
B
Sure
so,
thanks
for
coming
along
really
really
nicely
actually
I
gave
a
demo
at
La
drupalcamp
last
weekend,
which
went
moderately,
ok,
but
I
think
that
we
need
to
put
out
a
new
video
demonstrating
where
we
are
currently.
As
always,
you
can
get
the
code
of
where
we
currently
are
by
going
to
issue
86
in
the
backdrop
issue
queue
and
you
can
follow
along
with
the
status
there.
B
But
even
though
there
haven't
been
a
whole
lot
of
updates
to
the
issue
itself,
like
I've
been
doing
code
pushes
pretty
regularly,
and
so,
if
you
want
to
do
a
poll
from
the
branch
that
is
linked
to
an
issue
86,
you
can
see
where
we
are
currently.
That
status
is
basically
that.
Well
since
last
week,
we
now
have
menu
access
level
control
working,
so
you
can
restrict
access
to
all
layouts
of
a
particular
path,
similar
to
like
page
managers,
access
control
system.
B
Many
links
you
can
now
add
and
save
in
to
save
into
the
menu
system,
like
you
would,
with
Paige
manager,
I
stripped
out
all
kind
of
remaining
references
to
see
tools
or
page
manager
or
any
Drupal
6
code.
With
the
exception
of
things
that
that
we
still
need
to
port,
so
there's
a
number
of
plugins
that
suddenly
to
be
ported,
things
like
you
can
place.
B
Let's
see
I
know
you
can
use
things
like.
You
can
use
conditions
to
say,
like
only
showed
this
thing
on
certain
node
types
or
certain
common
types,
but
you
can't
yet
do
something
like
display
fields
like
break
out
a
field
and
display
anywhere
you
want,
but
that's
a
that
actually
isn't
that
difficult
to
implement.
It
just
needs
to
be
ported.
So
the
only
things
left
from
Drupal
7
C
tools,
/
panel
/
page
manager,
is
just
a
little
bit
of
porting.
It's
only
to
be
on
just
a
couple
of
plugins
and
I.
B
B
It's
already
and
I
mentioned
this
past
couple
weeks,
but
we
have
it
fully
replacing
regions
and
layouts
and
all
of
the
theme
capabilities
at
this
point.
So
it
is
effectively
like
panels
everywhere
on
every
page
of
your
site,
which
is
really
really
awesome
so
keep
following
along
with
that
issue,
I'll
post,
another
YouTube
video,
hopefully
before
the
end
of
the
week,
showing
where
we
are
currently
because
it's
it's
something
that
is
much
easier
to
see
than
it
is
to
hear
about.
A
Okay,
it's
great
and
I
think
that
we're
working
on
is
getting
the
views
module
in
core.
We
currently
have
views
in
coram.
We
have
a
bunch
of
the
pages
that
are
generated
by
views.
In
course,
though,
things
like
the
front
page
and
taxonomy
term
listings
and
things
that
we
need
help
with
are
getting
actions
converted
into
our
video
system
so
that
we
can
get
our
administrative
listings
converted
to
be
used
to.
That
is
not
a
release
blocker,
but
it
is
something
that
I
think
will
be
really
great
to
happen.
A
The
first
release,
so
it's
lower
and
I
priority
list,
but
something
that
we
still
want
to
get
done.
So
if
we
have
an
immense
work
on
that
with
love
help
with
that
other
things
that
our
release
blockers
is
getting
our
configuration
management
tools
fully
converted.
So
we
currently
have
the
config
management
subsystem
in
court
and
we
have
a
bunch
of
sub
other
systems
converted
to
use
cmi,
but
we
don't
have
all
of
them
the
big
ones
that
would
prevent
a
release,
in
particular
our
content,
types
and
fields.
A
A
Last
week,
I
was
doing
a
bunch
of
work
on
theme,
system,
stuff
and
I
moved
most
of
the
theme
system
variables
that
we're
keeping
into
config
so
we're
getting
closer,
and
but
there
there
are
a
few
variables
left
and
then
the
rest
that
are
just
sub
systems
that
need
also
to
be
converted
in
terms
of
other
things
we're
working
on.
We
have
a
couple
of
issues
that
are
helping
us
keep
up
with.
A
What's
going
on
in
Drupal
to
match
with
what's
going
on
in
Drupal
7,
we
have
one
issue
that
includes
all
of
our
security
fixes
that
we
need
and
another
one
that
just
includes
all
the
other
commits
that
were
made
to
Drupal
7.
Then
we
want
to
make
sure
that
we
also
have
in
backdrop
so
that
we're
not
behind
where
drupal
7
was
one.
We
need
to
release
and
we're
pretty
close
on
the
Drupal
7
issues.
A
It
looks
like
we
have
11
of
those
left,
which
is
probably
what
needs
to
go
into
731
or
all
the
stuff
that
happened
in.
In
most
recent
version,
we
haven't
gotten
those
in
yet
and
then
there's
three
security
issues
that
are
also
left
so
offending
on
myself
with
those
with
yourself
with
that
and
then
in
terms
of
Drupal
8
backports.
We
originally
thought
we
were
going
to
review
all
you
know.
A
Eight
thousand
plus
issues
that
have
happened
commits
between
when
we
forked
backdrop
and
when
at
war
drew
blade
is
now,
but
since
then
we've
decided
that
that's
just
way
too
much
change
to
look
at,
especially
because
we
aren't
going
to
be
doing
most
things
they're
doing
so.
Instead,
we
chose
several
important
subsets
of
things
that
we
wanted
to
to
also
work
on,
so
we've
got
html5
issues.
We've
got
almost
all
of
those
wrapped
up.
We
have
CSS
issues.
A
A
You
to
make
sure
that
na
de
stuff,
that
we've
moved
in
from
contribs,
like
four
views
or
admin
menu,
is
also
matching
our
new
coding
standards,
as
well
as
the
stuff
that
we
have
in
core.
That
has
been
changed.
We
want
to
make
sure
it
hasn't
been
changed
to
look
like
your
blade,
but
it's
instead
been
changed
to
look
like.
So
that's
really
great.
We
also
have
a
collection
of
JavaScript
issues.
A
These
all
have
had
j/s
hint
run
on
them
with
our
new
coding
standards
to
make
sure
that
they
look
nice
and
we've
gone
most
of
those
changes
in
there's
a
handful
of
those
are
left.
So
if
anyone
is
a
JavaScript
expert
and
wants
to
help
us
clean
up
our
JavaScript
code,
there's
a
couple
of
those
that
are
left.
A
This
also
isn't
going
to
block
release
sloppy
code,
isn't
a
big
enough
thing
to
prevent
release
happening,
but
obviously
it
would
be
better
for
code
wasn't
sloppy,
so
we
could
use
some
help
on
those
also,
if
you
want
to
help
there
and
other
things
that
we're
working
on
that,
we
would
like
to
get
done
before
we
release
our
separating
backdrops
identity
from
Drupal,
obviously
being
a
fork
from
Drupal.
We
start
off
with
something
that
looks
a
lot
like
drupal,
and
we
have
a
couple
of
places
that
we're
trying
to
make
ourselves
look
different.
A
We've
already
included
our
new
installer
branding,
which
looks
great,
but
we
want
the
rest
of
the
administration
theme
to
take
on
a
backdrop,
look
and
I.
Think
probably
also
renaming
the
administration
theme,
so
it's
not
called
seven,
which
would
be
confusing,
and
it's
already
confusing
it's
confusing.
If
there's
not
a
virgin
Stefan
for
it
to
match
would
also
be
really
good.
So
we'll
probably
do
that
in
the
same
kind
of
rebrand.
A
The
administration
theme
issue
and
some
other
things
that
we're
working
on
our
cleaning
up
the
theme
system
to
make
it
easier
for
people
to
work
with
there's
a
lot
of
stuff
that
I
did
in
the
twig
initiative
that
involved
just
kind
of
making
things
work
in
a
way
that
made
more
sense
that
we
can
also
do
in
backdrop.
A
lot
of
the
changes
didn't
actually
have
anything
to
do
with
twig.
A
They
are
just
kind
of
sensible
improvements
and
we've
got
a
list
of
those
that
needs
some
attention
to
I
made
a
little
bit
of
progress
on
that
last
week.
I've
got
a
couple
for
requests,
I
think
one
of
them
is
even
passing
tests,
which
is
pretty
great,
oh,
and
what
we'll
keep
working
on,
making
those
better
too
and
then
other
things
that
are
really
important
are
improvements
to
user
experience.
A
Experience
is
pretty
great,
so
there's
a
couple
of
things
that
we
need
to
just
kind
of
take,
get
and
backed
up
and
make
sure
that
we're
getting
right
and
there's
a
bunch
of
stuff
that
we
know
is
wrong
that
existed
from
Drupal
that
we
can
just
kind
of
clean
up,
there's
already
existing
Drupal
issues
in
most
cases
there's
existing
triple
patches.
So
that's
really
great.
We
can
just
kind
of
knock
those
out
a
bunch
of
great
stuff.
A
That's
been
done
into
your
blade
and
we
need
that
too,
but
there's
also
about
a
bunch
of
other
stuff
that
we're
introducing
the
Cussler
backdrop
that
we
also
need
to
make
sure
that
we
get
right
like
terminology
in
the
layouts
interface
and
stuff,
like
that.
So
we'll
do
a
kind
of
a
holistic
review
of
that
once
we
get
closer
to
release
too,
but
there
is
a
meta
issue,
127
that
includes
some
terminology
team
changes
that
we
should
consider
doing
and
a
bunch
of
other
stuff
kind
of
along
those
lines.
A
We
also
would
like
to
add
our
rich
text
editor
into
core.
This
is
not
something
that
sort
of
release
blocker,
because
we
think
we
can
add
it
after
the
initial
release
without
breaking
api's,
but
obviously
it
would
be
great
if
we
could
get
that
in
for
backdrop,
one
point
no
point
now
so
there's
a
section
in
this
meeting
for
weekly
updates
from
the
PMC,
where
we
can
notify
you
of
any
issues
that
have
become
heated
in
the
issue,
queue
that
have
needed
further
discussion
and
a
decision
to
be
made.
A
Other
things
that
we're
working
on
in
backdrop
world
that
aren't
the
project
itself
include
the
infrastructure
around
having
an
open
source
project.
You
have
an
API
website
which
Luke
thought
I'll
set
up
for
us,
which
is
great.
It
actually
checks
our
our
code
base,
not
real
time.
I.
Think
we're
going
to
set
it
up
so
that
it'll
do
a
check
out
of
our
code
base
every
hour
so
but
I
think
that's
fair,
considering
the
rate
of
commits
we're
working
on
right
now,
I,
that's.
A
A
A
New
content
type
on
the
API
site
for
change
notices,
and
so
we
can
start
getting
to
people
to
start
populate
those
if
we
wanted
to
especially
the
ones
that
are
sort
of
exact
copies
of
change,
notices
that
are
on
Drupal
site,
so
backdrop
for
tamara
lee,
drupal
8,
so
they're
already
changed
records
from
a
lot
of
those
changes
that
went
into
drupal
8
on
Drupal's
website,
they're,
probably
very
different
now
than
they
were
at
that
point
in
time
when
we
forked.
So
we
might
need
to
do
a
little
kind
of
reworking
rewording
on
those.
A
But
it
might
be
a
great
starting
point
for
us.
So
if
we
have
anyone
who
wants
to
help
back
job
but
isn't
competent
and
working
in
code,
we
could
definitely
use
some
triage
on
the
the
change
notice
list.
So
if
you
wanted
to
look
at
our
issue,
queue
and
search
for
things
that
need
change,
notices,
that'll
be
a
great
place
to
start
and
then
I'm
not
sure
how
we
would
get
a
master
list
of
all
of
the
change
wreckers
that
existed
on
drupal.org
at
the
time
that
we
forked.
A
But
if
we
could
figure
that
out,
that
would
probably
be
a
great
place
to
start
there
too,
just
to
make
sure
that
we
have
all
the
stuff.
We
need
other
stuff
we're
working
on
update
server.
So
when
your
backdrop
website
needs
to
talk
to
the
mothership
and
find
out
if
it
is
up
to
date
or
not,
we
need
to
make
sure
we
have
a
mothership
for
it
to
talk
to
so
I
know,
we've
got
a
discussion
about
how
we're
going
to
handle
that
in
I
issue
queue.
A
We
also
need
someone
to
actually
build
the
tool
that
will
handle
it.
So,
if
someone's
interested
in
setting
that
up,
we
would
love
some
help
there
and
we
also
need
to
get
hub
service.
So
this
is
so
that
people
who
create
contribs
can
register
their
projects
as
being
part
of
backdrop,
and
then
backdrops
main
website
will
search
the
github
queue
for
a
list
of
those
modules
in
pullman,
so
that
we
can
get
a
single
place
to
search
for
modules
and
themes
that
are
for
backdrop.
A
A
Gonna
get
a
little
revamp
in
time
with
our
release,
so
we
have
a
contacted
designer
and
we're
working
on
getting
some
designs
done
for
a
new
version
of
the
site
and
then
that
hopefully,
if
we
can,
we
can
get
someone
who
wants
to
actually
build
it
for
us.
That
would
also
be
really
helpful
between
now
and
the
end
of
all.
So
we
don't
have
designs
yet,
so
it's
not
urgent,
but
that
is
coming
up.
So
if
you
want
to
help
us
with
that,
I
know
John
offered
to
help
us
with
that
before.
A
Maybe
we
should
reach
out
to
him,
see
if
he's
still
interested
and
then,
let's
see
so,
we've
got
a
couple
of
Sprint's
coming
up,
obviously
every
day
on
Thursday.
If
you
want
to
join
us
in
IRC,
we
have
a
little
sprint
here
last
weekend.
No
Luke
was
an
IRC
he's.
Like
my
in
the
right
place.
He
was
in
the
right
place.
A
It
just
happened
to
be
that
we
were
working
so
I
didn't
respond
him
quickly
enough,
but
we're
in
there
if
you
paying
us
by
name
like
if
you
have
a
specific
question,
you
type
one
of
our
names
at
all,
make
our
machines
beep
and
will
notice
it.
So
if
you're
in
there
and
you're
hanging
out-
and
you
want
our
attention-
just
hyper
name-
will
notice
more
quickly,
but
we
are
usually
they're
all
day
on
Thursdays
in
real
life.
We're
also
going
to
have
a
sprint
at
bad
camp,
which
is
november
six
through
nine.
A
There
is
going
to
be
a
core
developer
summit
that
will
happen
for
all
days
at
the
camp
and
we'll
try
and
commandeer
one
table
in
that
space
for
backdrop,
work.
If
we
got
enough
people
we
might
be
able
to
take
over
to,
but
we'll
see,
we'll
see
who
we
get
but
yeah,
so
there's
a
sprint
for
everything.
Drupal
related
at
that
kick,
which
will
be
great
other
things
that
we
have
coming
up.
A
We
are
going
to
be
giving
our
first
backdrop
talk
to
a
non
Drupal
audience
I'm
coming
up
here
in
two
weeks
at
the
html5
developer
conference,
so
that'll
be
fun.
We
just
got
to
go.
Talk
to
people
are
working
in
the
web
world
and
show
off
what
we've
built
last
time.
I
did
a
talk
for
them.
They
were
super
impressed
by
views
and
panels,
so
I
think
showing
them
backdrop
with
these
and
panels
in
core
will
be
pretty
cool
demo.
A
A
If
they're
going
to
be
interested
in
hearing
about
backdrop
at
drupalcon,
but
we
will
put
it
on
the
Senate
of
agenda
and
see
if
someone
asks
we
talk,
that's
usually
how
it
goes
if
we
get
invited
to
a
specific
event,
because
people
there
want
to
hear
what
we
have
to
say
then
we'll
say
it,
but
we
don't
usually
submit
backdrop
sessions
to
Drupal
events
unless
we
have
been
specifically
asked
to
so
we'll
see
what
the
community
wants
in.
If
they
want
to
hear
what
we
have
to
say,
them
will
say
it.
It's.
A
A
Don't
know
anyway,
well
we'll
figure
it
out.
We
don't
have
anything
on
schedule
for
next
year.
Yet,
okay,
I
know
I
I've
got
a
lot
of
stuff
to
work
on
today.
Meet
you
probably
have
a
bunch
of
stuff
too
so
I
think.
Maybe
we
should
wrap
this
meeting
since
there's
no
one
else
here
for
any
questions,
but
yeah
will
be
an
IRC
if
you
miss
the
meeting,
for
whatever
reason
didn't
have
questions
for
later,
don't
know
how
to
find
us.