►
From YouTube: Backdrop Weekly Status Meeting 11/6
Description
Our weekly status meeting on Backdrop CMS! Agenda at http://bit.ly/1whpxpc.
A
Hello
greetings.
Everyone
welcome
to
the
weekly
backdrop.
Call
this
week.
It's
pretty
much.
It's
likely
just
going
to
be
me
here
in
the
hangouts,
because
jen
is
out
organizing
bad
camp
this
week,
and
so
it
starts
actually
starting
today,
a
whole
bunch
of
summits
and
activities.
Sir
doorway,
so
today
is
the
beginning
of
bad
camp,
which
means
I'm
going
to
be
running.
The
bank
call
so
welcome
to
the
call
the
backdrop
project.
What
we're
trying
to
do
is
we're
setting
out
to
make
a
Drupal
8
alternative.
A
Essentially,
the
idea
is
a
new
version
of
Drupal,
that
is
on
the
Drupal
7
architecture,
with
Drupal,
8,
flank
features
and
what
that
encompasses
basically
means
some
modernisation
up
with
html5
new
blocks
and
layouts
initiative
views
and
color
cmi.
That
kind
of
functionality
is
what
we're
targeting
to
include
in
backdrop
1.0
original
timeline
or
our
revised
timeline.
Excuse
me
is
for
release
this
fall,
which
pretty
much
means
in
the
next
six
weeks
is
the
plan
right
now.
Our
timeline
is
looking
a
little
bit
tight,
but
we're
still
going
to
try
for
that
date.
A
It's
not
impossible.
It's
not
outside
the
realm
of
possibility.
It's
just
we'll
probably
need
to
do
some,
some
more
trimming
of
our
scope
in
order
to
make
that
a
timeline
and
I'll
talk
about
some
of
those
things
as
I
go
through
the
weekly
status
report,
so
major
initiatives
that
we're
undertaking
there's
three
major
initiatives,
the
first
of
which
is
blog
layouts
blocks
and
layouts,
is
in
a
really
good
place.
We've
got
a
video
up
on
our
YouTube
channel
if
you
haven't
seen
it
yet.
A
The
block
blocks
and
layouts
new
structure
is
sort
of
founded
upon
the
layout
module.
The
layout
module
is
essentially
replacement
for
block
module
when
it
comes
to
structuring
and
laying
page.
It's
super
cool.
It's
built
on
the
same
foundation
as
has
panels
and
see
tools.
So
if
you're
familiar
with
panels
and
see
Jules,
it's
a
lot
like
that.
Only
it's
a
lot
easier.
We
simplified
it
down
a
huge
amount,
rewrote
the
UI
and
reuse
the
underlying
architecture
of
subsea
chosen
and
panels.
A
So
overall
has
the
same
capabilities,
although
it's
not
fully
fleshed
out
yet,
but
all
of
the
same
underlying
API,
but
a
lot
easier
to
use
UI.
So
we're
super
excited
about
blocks
and
layouts.
It's
pretty
much,
probably
where
we
want
to
be
for
release.
We
could
extend
it
out
a
lot
more
with
the
digital
blocks
and
tokens
supports
and
things
like
that,
but
likely.
A
What
we'll
see
is
the
initial
release
of
backdrop
will
include
just
all
of
the
blocks
that
triple
7
did,
but
it
has
all
the
underpinnings
for
expanding
that
in
future
releases,
so
blocks
and
layouts
there's
still
an
issue
for
a
bunch
of
follow-up
tasks.
If
you're
interested
in
participating
blocks
and
layouts
right
now,
we've
been
generating
a
bunch
of
a
feedback,
that's
been
coming
in
regarding
blocks
of
layouts.
Thank
you
very
much.
A
Let's
see
the
next
major
initiative
is
configuration
management
or
regularly
referred
to
as
cmi
for
configuration,
management
initiative
and
CM
is
looking
really
good.
It's
probably
the
one
major
hang
up.
We
have
in
making
release
for
backdrop
1
point
0.
Some
things
have
been
in
configuration
management
for
really
long
time.
A
Things
like
views
layouts
as
soon
as
they
were
created
that
were
written
directly
against
CM
I,
most
variables
have
been
converted
and
some
other
bae
systems
have
been
in
place
for
a
long
time,
but
we
stole
several
major
systems
that
aren't
converted
yet,
and
it's
probably
our
biggest
luck
for
release.
Like
I
said,
we've
got
about
six
weeks
left
before
our
anticipated
release
dates.
So
we've
got
a
little
bit
of
work
to
make
sure
that
these
things
get
converted
and
fully
tested
before
that
time.
So
recently
we
converted-
let's
see
in
the
past.
A
Let's
see
it
was
week
before
last.
We
converted
three
major
systems
roles,
node
types
of
vocabularies,
which
is
great-
those
are
all
of
the
major
entity
types
in
Drupal
7.
We
now
have
those
all
converted
to
cmi,
so
they're
all
saving
into
individual
configuration
files
new
this
week.
At
the
end
of
last
weekend,
during
last
week,
status
column
mentioned
that
we've
been
making
a
lot
of
progress
in
fields
and
fields
have
now
been
fully
converted
and
they're,
also
in
the
current
master,
10
decks
branch
of
backdrop.
A
So,
if
you
check
out
backed
up
today,
we've
got
a
lot
of
things,
starting
configuration
management
now
all
of
the
major
crucial
systems,
but
there's
still
a
couple
of
sort
of
peripheral
ones,
maybe
not
suffer
from
menus
languages,
text
formats
and
actions,
and
then
a
few
lingering
variables
here,
and
there
are
the
remaining
things
to
be
converted
to
cmi.
So
some
of
those
should
be
pretty
straightforward
text
formats,
especially
menus,
should
be
okay,
actions
shouldn't
be
too
hard.
A
Languages
could
be
a
bit
of
a
doozy,
but
after
converting,
so
many
things
recently,
like
fields
only
took
two
weeks.
I'm
still
really
optimistic
that
we
might
be
able
to
put
all
of
this
together
before
we
want
to
release
so
see,
am
I
looking
good,
but
definitely
the
most
important
thing
that
we
have
on
our
plates
in
order
to
make
it
so
that
we
can
release
the
software.
A
The
last
major
initiative
is
views
in
core
views
have
been
in
core
and
backdrop
for
six
or
eight
months
or
so
they've
been
there
for
a
long
time,
but
we
don't
have
everything
converted
to
actually
fully
utilize
them.
Yet
we
still
have
a
whole
bunch
of
administrative
listings
front
and
listings
blocks
all
kinds
of
things
that
could
potentially
be
used
or
it
could
be
converted
to
views.
A
But
we
don't
have
those
in
place
if
we
need
to
release
backdrop,
1
point
0
without
these
things
converted
to
views,
that's
acceptable,
but
it
would
really
be
preferable
if
we
could
get
these
things
converted
to
views
so
that
right
out
of
the
box,
people
can
come
in
and
immediately
customize
their
narrative
interfaces,
as
well
as
the
front
end
displays
without
needing
to
create
new
views.
It's
always
much
easier
to
to
edit
and
manipulate
than
it
is
to
create
something
new.
A
Ok,
that's
it
for
our
main
initiatives,
they're
all
coming
along,
pretty
well
blocks
and
layouts
config
and
views.
We
also
have
some
other
things
that
we
always
try
to
keep
tabs
on.
One
of
them
is
making
sure
that
we
keep
up
with
Drupal,
both
Drupal
7
and
Drupal.
8
will
possible
back
porting
across
supported
features,
says:
let's
see,
the
last
release
of
Drupal
7
was
7
dot
32.
The
main
thing
was
a
security
update
or
the
only
thing
commonly
referred
to
as
Drupal
gedan,
which
was
a
major
sequel
injection
attack.
A
We
imported
that
to
gerbil
I'm.
Sorry,
we
putted
that
to
backdrop
pretty
much
right
after
it
was
released.
A
new
version
of
Drupal
7
is
coming
out
today
in
theory,
733,
which
is
looks
like
it's
just
normal
maintenance
releases,
but
it
has
a
really
interesting
feature
in
it.
They
backported
the
theme
debug
mode,
which
basically
injects
a
whole
bunch
of
HTML
comments
into
your
templates.
A
To
tell
you
where
markup
is
coming
from
the
back
part
of
that
into
Drupal
7,
which
looks
like
a
really
interesting
feature
for
us
and
something
that
we
could
easily
pour
it
into
backdrop.
Considering
were
still
running
the
same
theming
engine
as
triple
seven.
We
should
be
able
to
move
over
that
functionality
really
pretty
easily,
so
that's
exciting
and
something
that
we
can.
We
can
pour
it
over
the
backdrop
here
in
the
near
future.
A
Let's
see
Drupal
8
backports.
We
used
to
have
a
list
of
all
Drupal
eight
backboards,
but
there
were
just
so
many
of
them,
like
literally
thousands,
that
we've
gone
down
from
like
having
an
actual
list
of
these
things,
to
just
sort
of
selecting
them
a
la
carte
and
the
two
areas
in
which
were
actively
back
porting
things
as
html5
items
as
well
as
JavaScript
updates.
A
All
of
this
stuff
is,
is
optional,
but
nice
to
have
in
the
html5
category,
especially
if
you
look
at
issue
200
and
get
hop,
github
issue
queue.
There's
one
of
the
items
is
near
and
dear
to
my
heart,
which
is
adding
the
support
for
multiple
file
uploads
to
the
managed
file
element.
That
would
be
really
great
into
backdrop
again.
It
doesn't
have
to
happen
for
the
initial
release,
but
it
would
just
be
great
to
have
the
ability
to
upload
multiple
files,
all
at
once
through
a
final
element
in
backdrop.
A
Okay,
we
also
have
a
number
of
minor
projects,
just
things
that
we're
just
trying
to
get
as
far
as
you
can
before
release.
One
of
them
is
separating
the
identity
from
Drupal.
We've
already
done
a
really
pretty
good
job
of
doing
this,
we've
got
a
girl
goes,
we've
got
our
own
styling.
We've
got
our
own
installing
now
we're
doing
a
lot
of
work
to
try
to
separate
ourselves
and
make
ourselves
a
separate
project
with
a
sec
printed.
A
Try,
simplify
theming
in
backdrop,
even
if
I'm
going
to
be
using
twig
user
interface
improvements,
there's
actually
been
some
good
progress
here.
In
the
past
week,
we've
got
some
ongoing
issues
like
we
wanted
a
rich
text.
Editor
decor,
probably
not
gonna
happen
in
the
initial
release,
but
can
be
there
for
later
terminology
updates
those
can
rolling
along
various
names
that
we're
changing
and
reorganization
issue
127.
A
If
you
want
to
look
at
that
entire
list
of
renaming
and
terminology
items,
but
in
the
past
week
we
started
a
weekly
weekly
design,
hang
out,
I,
guess
it's
bi-weekly.
Actually,
so
last
week
we
had
one
this
week
we
don't
next
week,
we'll
have
another
one
and
we
have
a
volunteer.
A
new
volunteer
that
joined
in
to
say
that
he
wanted
to
develop
some
human
interface
guidelines,
which
will
ultimately
kind
of
turn
into
kind
of
a
style
guide
for
backdrop
overall
as
project,
so
he
just
posted
his
initial
draft
of
things.
A
Let's
see
it's
a
issue
390
the
human
interface
guidelines
that
he's
put
together
and
there
it's
really
pretty
exciting,
like
it's
a
good
start,
there's
not
a
whole
lot
of
solid
development
there,
but
the
skeleton
development
is
now
all
in
place.
So
thank
you
very
much
good
time
for
putting
that
together.
We're
really
excited
to
see
where
that
goes
and
and
how
we
can
implement
it.
A
Let's
see
every
week
we
like
to
have
this
section
in
the
meeting
for
updates
from
the
project
management
committee.
The
project
management
committee
basically
is
a
conflict
resolution
group
that
when
any
issue
gets
escalator,
we
can't
make
a
decision
on
something
it
can
be
escalating
to
the
PMC
for
decisions,
but
so
far,
like
we've
got
some
few
people
putting
stuff
forward
they're
pretty
much
anything
that
comes
forward
well
immediately,
just
kind
of
most
of
the
time
go
in,
so
we
haven't
any
conflicts
of
any
kind
recently.
So
there's
no
updates
is
section.
A
A
So
we'll
probably
ship
backdrop
with
update
module,
but
it'll
connect
to
like
a
shim,
basically
until
we
can
manage
to
actually
build
out
the
update
server
on
backdrop,
CMS
org,
let's
see
also
related
to
updates
and
contributed
modules.
We
also
really
want
to
make
a
official
github
service
for
for
backdrop,
CMS.
The
idea
is
that
we
would
organize
can
triple
OTT
like
jQuery
plugins.
If
you
go
to
plugins
jQuery
com
is
essentially
an
aggregation
of
all
jQuery
plugins
that
have
officially
been
registered,
but
all
of
those
plugins
are
simply
registered
through
github
itself.
A
We're
planning
on
doing
something
similar,
although
with
a
little
bit
more
of
a
hybrid
model
where
projects
can
register
themselves
through
github,
just
by
enabling
the
service
or
later
after
they've
registered
it
through
github.
They
could
also
login
to
backdrop
CMS
dot
org
and
do
some
additional
like
additional
editing
if
they
want
to
say
something
specifically
on
the
project
page.
So
that's
the
idea.
We
have
a
way
to
go
to
implement
that,
but
for
the
time
being,
kyndra
basically
is
going
to
be
a
little
bit
ad
hoc.
A
It's
basically
going
to
be
various
projects
distributed
through
github
and
then
we'll
work
on
aggregating
those
all
together.
After
the
launcher
backdrop,
we're
also
doing
some
work
on
the
flagship
sites.
Backdrop
CMS
torg,
we're
still
working
towards
building
out
a
new
redesign
and
making
it
so
you
can
do
things
like
you,
can
search
modules
and
themes,
showcase,
so
I
provider
directory
like
work
on
building
out
the
overall
backdrop
CMS
or
website.
As
we
go
forward,
let's
see
sprints
every
Thursday,
we
have
sprints.
A
That's
today,
I'm
available
in
IRC
impound
backdrop:
jen
is
not
around
this
week
as
she's
running
bad
camp,
but
we'll
be
doing
sprints
as
usual.
Today,
after
after
this
call,
you
can
join
us
in
IRC
and
pound
backdrop
in
real
life.
Bad
camp
is
this
week
and
so
we're
going
to
be
at
bad
camp
we're
giving
a
session
actually
this
saturday
at
bad
camp.
If
you're
in
the
bay
area,
you
can
drop
by
and
watch
our
presentation.
Let's
see
it's
saturday
afternoon,
I
think,
and
I'm
not
really
sure
what
time
it
is.
A
It
is
230
in
the
rainbow
road
room
here
in
san
francisco
for
bed
camp.
You
can
check
us
out
there
and
we'll
also
be
doing
code
sprints
all
day
sunday.
So
if
you
go
to
the
code,
sprint
room
will
be
having
a
backdrop
table
that
you
can
come
and
join
us
at
we're.
Also
giving
a
talk
at
symphony
live
in
Madrid
later
this
month
november
27th
and
then
we've
got
plans
to
be
at,
but
we
probably
won't
be
speaking
at
the
next
couple
of
drupal
cons,
but
we'll
keep
you
posted
as
those
dates
draw
closer.