►
From YouTube: Backdrop CMS Weekly Meeting 7/3
Description
The weekly Backdrop CMS hangout. Come join us for a status update!
A
Hello,
internet
greetings,
happy
3rd
of
july
2014.
This
is
the
weekly
backdrop
meeting
where
we
get
together
and
talk
about
how
backdrop
is
proceeding
and
trying
to
aim
forward
towards
our
release.
A
So
for
those
of
you
who
aren't
familiar
with
backdrop,
backdrop
is
a
drupal
fork
and
we
have
forked
the
drupal
project,
because
we
believe
that
there
is
a
cost
that
comes
with
change
and
the
drupal
8
release
cycle
basically
changed
too
much
and
in
a
lot
of
directions
that
we
didn't
agree
with.
So
we've
got
some
different
philosophies
from
the
drupal
project
and
we're
taking
drupal
in
a
different
direction
and
that
new
direction
is
called
backdrop.
A
So
what
we're
aiming
to
do
with
the
initial
release
of
backdrop,
is
to
provide
drupal,
8,
comparable
features
or
comparable
features
like
same
similar
set
features
on
a
drupal
7
like
architecture.
A
We
also
want
to
include
all
of
the
bug
fixes
from
drupal
7
and
drupal
8
and
our
own
fixes,
and
we
want
to
simplify
existing
systems
as
much
as
possible.
We're
also
looking
at
adding
a
bunch
of
new
features
very
similar
to
what
drupal
8
has.
A
Although
given
our
timeline,
we're
de-scoping
a
whole
bunch
of
things
right
now
to
make
it
so
that
we
can
get
out
a
release
and
get
out
back
up
into
the
wild,
so
timeline
wise,
we're
still
shooting
to
aim
to
release
backdrop
1.0
sometime
this
summer,
which
means
that
we're
really
kind
of
running
out
of
time
and
in
order
to
meet
that
goal,
we're
working
on
de-scoping
things
as
much
as
possible,
as
well
as
finishing
up
all
the
conversions
that
we
have
in
place.
A
So
we
can
get
a
stable
release
out
there.
So,
but
even
if
we
release
backdrop
1.0
this
summer-
and
it
doesn't
have
a
bunch
of
the
features
that
we
hoped
it
would-
we
have
a
different
release
cycle
from
drupal
itself,
where
we
plan
on
having
regular
releases
on
like
a
three
to
four
month
basis.
Basically,
so
if
we
don't
get
in
all
the
features
we
we
want
right
away.
That's
okay!
We're
just
going
to
continue
iterating
on
minor
releases
as
we
go
forward.
A
So,
let's
see
then
we're
going
to
go
through
our
project.
Progress
reports
say
how
we're
proceeding
on
each
of
our
initiatives.
A
We've
got
three
major
projects
that
we're
working
on
in
backdrop,
blocks
and
layouts
views
and
core
and
configuration
management,
and
so
for
the
first
of
those
blocks
and
layouts
is
issue
86
in
the
backdrop
issue
queue
status,
update
on
that
is,
I
haven't
had
a
lot
of
progress
since
last
week,
but
we're
still
moving
forward
on
building
out
the
new
layout
module.
We've
got
the
module
integrated
with
the
dialog
system.
A
When
you
create
a
new
layout,
it
saves
to
the
configuration
system,
it
saves
the
layout
and
menu
item
and
we're
working
on
the
actual
interface
to
layout
blocks
in
layouts.
At
this
point,
so
things
are
coming
along
okay,
but
if
you
want
to
see
progress
on
that
and
where
the
code
currently
is,
it's
not
in
pull
request
form
because
it's
not
yet
functional,
but
the
issue
is
issue
86.
A
A
We
still
need
some
help
in
moving
those
conversions
forward.
If
anybody's
interested
in
converting
things
like
our
listings
and
administration
pages
and
views,
that's
been
a
long-standing
issue
that
hasn't
had
any
forward
momentum
in
quite
a
while.
A
Let's
see
configuration
management,
the
last
major
initiative,
we've
got
all
the
the
base
system
of
configuration
management
in
place,
including
the
user
interface
and
the
importing
exporting
tools,
saving
to
json
files
and
all
that
sort
of
thing
and
we've
got
a
couple
of
base
systems.
A
We
recently
had
one
of
our
high
school
drop
turns
paul
or
hello.
Mr
cat,
who
is
who
is
joining
us
he's
taking
on
converting
a
whole
bunch
of
the
variables
to
cmi
right
now,
which
is
issue
170..
A
Do
you
want
to
give
an
update
paul
on
how
that's
been
going
and
any
questions
or
problems?
You've
been
running
into.
B
A
Yeah,
let's
see
which,
which
ones
have
you
got
on
your
plate
coming
up
for
this
week,
like
how?
How
do
you
think
you're
feeling
about
the
number
that
you
could
do
at
a
time?
And
things
like
that?
I
know
you
just
got
started
so
maybe
it's
too
early
to
be
making
estimates.
B
Yeah,
I'm
not
really
sure
I
mean
I've
kind
of
just
been
going
through
them
one
at
a
time
for
now,
but
I
assume
that
I'll
get
more
efficient
at
doing
them
as
time
goes
on.
Yeah.
A
A
Great
to
see
those
those
moving
forward
thanks
a
lot
for
for
taking
those
okay,
so
those
are
the
major
initiatives
and
the
status
on
them.
We
also
have
a
bunch
of
well
we've
got
minor
projects,
and
we
also
have
this
section
for
keeping
up
with
drupal.
A
We've
got
all
of
the
security
fixes
in
every
version
of
triple
seven
ported
to
backdrop
and
included,
with
the
exception
of
of
one
that
is,
has
to
do
with
image
styles
and
we're
still
looking
at
possible
ways
that
we
could
solve
that
problem
without
using
the
same
solution
that
drupal
7
used,
which
broke
a
whole
bunch
of
sites.
So
still
looking
at
solutions.
There,
we've
only
got
one
of
the
original
meta
issues
left
issue.
132
is
the
list
of
all
drupal
7
back
ports.
A
We
had
three
original
issues,
each
one
that
contained
about
200
back
ports
and
we
finished
the
first
two
of
those
and
we're
about
looks
like
about.
A
A
We
made
another
issue
for
recently
for
backporting
all
of
7.24
to
7.27
and
we're
50
out
of
88
through
that
issue
as
well
issue
222
and
then
finally,
gore
who's
joining
us
on
this
hangout
today
made
a
new
mini
new
issue
just
yesterday
for
backboarding
all
of
7.28
fixes
and
so
far
that's
going
along
swimmingly
with
21
of
34
of
those
patches
already
into
a
pull
request.
So
thanks
a
lot
corp
for
making
that
issue
for
doing
those
back
ports,
it's
really
appreciated
yeah.
It's
issue
262.
A
yeah
and
some
of
those
issues
were
21
out
of
34,
but
a
lot
of
the
remaining
ones
have
actually
already
been
done
as
part
of
other
back
ports
or
as
part
of
other
things
that
we've
been
doing
in
backdrop
since
we've
been
back
porting
things
from
drupal
8,
as
well
as
from
drupal
7.
Sometimes
what
happens
is
we've
already
backported
it
from
one
branch
or
the
other?
So
when
we
go
through
these
lists,
we
find
out
that
we've
already
done
a
lot
of
the
work
which
is
always
nice.
A
So
that's
it
for
drupal
7,
cross
ports
which
we're
keeping
up
with
just
fantastic
and
then
in
the
drupal
8
land
back
ports.
We've
got
three
categories
in
the
agenda.
At
least
we
want
to
make
sure
we
get
all
of
these
at
least,
and
that's
mostly
front
end
back
ports.
Things
like
html5,
which
is
issue
200.
A
We've
got
pretty
much
all
of
the
html5
form
elements,
backported
things
like
number
and
color
and
range,
and
all
of
the
fields
that
are
in
html5.
Those
are
all
backboarded
and
we've
got
most
of
the
markup
changes
as
well.
Using
things
like
section
and
sidebar
and
article
and
all
of
those
html5
tags,
we've
got
an
issue
also
for
both
css
and
javascript,
both
of
which
are
three
quarters
of
the
way
done.
A
A
There's
a
bunch
of
other
things
that
we're
also
back
porting
from
drupal
8
kind
of
a
la
carte
anything
that
makes
sense
to
back
ports.
If
we
get
a
full
request
for
it,
then,
of
course
we'll
merge
it
in,
but
there's
just
a
huge
number
of
drupal
8
things
that
will
never
make
it
back
into
backdrop,
because
it's
some
of
the
differences
that
we
have
in
the
direction
of
the
project
so
doing
a
really
great
job
pulling
things
back.
A
But
our
main
focus
really
is
on
fulfilling
the
major
initiatives
and
making
it
so
that
we
can
get
our
initial
release
out
so
other
minor
projects
that
we're
working
on
to
do
as
much
as
we
can
before
release
we're
continuing
to
separate
the
identity
from
drupal
in
order
to
make
it
so
that
backdrop
has
its
own
identity,
separate
from
drupal
in
the
future
and
can
be
like
a
real
sustainable
project,
we're
working
on
making
it
so
that
backdrop
really
can
live
a
life
on
its
own.
A
So
some
of
the
ways
we're
doing
that
is
we're
working
on
a
new
style
guide
for
the
administration
theme,
which
is
issue
139
and
we've
got
some
progress.
There.
We've
got
a
start
and
a
designer
who
has
been
working
on
building
on
a
new
admin
style
style
guide,
but
so
far
I
don't
know.
Work
has
been
a
little
bit
slow
on
that.
We'll
have
to
see
if
that
style
guide
can
be
completed
and
then
implemented
before
we
get
release
and
then
once
we
have
the
style
guide.
A
Yeah
then
we'll
need
to
implement
it
as
a
separate
issue,
which
is
issue
201.
Let's
see
user
user
experience
improvements,
this
first
one
is
near
and
dear
to
my
heart,
which
is
a
rich
text.
Editor
in
core.
Our
plan
is
to
include
all
of
the
the
ck
editor
and
filter
module
enhancements
into
backdrop.
A
That
was
something
I
was
really
involved
in
in
the
drupal
8
cycle
and
we'd
really
like
to
include
that
in
the
initial
release
of
backdrop
as
well,
we've
already
got
some
of
the
underpinnings
in
place.
Things
like
the
dialogue.
Api
was
a
critical
piece
of
functionality
that
was
needed
in
order
to
implement
the
wysiwyg
and
core
and
we've
gotten
dialogue
system
in
core,
which
is
great
for
establishing
some
of
the
base
baseline
functionality
that
we
need
that's
issue
101.
A
If
anyone
is
interested
in
taking
a
look
at
back,
pointing
ck
editor
module
into
into
backdrop,
let's
see
other
things
in
user
experience,
land
we're
also
looking
at
terminology
updates.
Drupal
8
rearranged
some
things
in
terms
of
like
what
certain
things
were
called
and
and
where
they
are
located
and
we're
looking
at
trying
to
simplify
a
lot
of
those
things
as
well
in
issue
127..
A
Some
of
the
things
that
we're
doing
we're
doing
things
like
taking
the
permissions
and
moving
it
under
user
settings
instead
of
under
people,
because
right
now
like
it,
doesn't
really
make
any
sense
that
permissions
are
located
under
people
instead
of
under
account
settings,
which
is
what
permissions
actually
are
doing.
Things
like
potentially
renaming
the
modules
page.
A
I
don't
know,
there's
a
whole
lot
of
discussion
going
on
there
around
what
terminology
should
be
now
that
we've
got
admin
module
in
core
that
has
a
search
box
in
it.
We're
hoping
that
the
way
a
lot
of
people
navigate
around
in
backdrop
is
by
using
the
search
in
the
administration
bar
but
having
the
search.
Work
means
that
we
need
to
use
the
terminology
that
people
are
expecting.
A
A
I
don't
know
lots
of
things
going
on
in
there.
You
can
read
about
it
in
issue
127.,
let's
see
and
finally
theme
system,
cleanup,
jen,
lampton
isn't
with
us
this
week,
she's
competing
in
a
horse,
competition
in
canada,
but
she's
taking
a
lead
on
cleaning
up
the
theme
system
in
dribble
eight
land.
They
switched
the
entire
theme
layer
to
use
twig,
which
jen
was
the
initiative
lead
for
and
in
backdrop,
land
we're
not
pursuing
twig
because
of
our
commitment
to
compatibility
with
existing
drupal
sites.
A
The
scope
of
change
that
we
already
have
is
already
significant
enough
that
we
can't
rewrite
the
entire
theme
layer
and
have
that
fit
within
our
principles.
However,
we
can
clean
up
the
theme
layer
a
whole
bunch
by
reducing
the
number
of
templates.
Consolidating
theme
functions,
doing
that
sort
of
thing,
so
we're
applying
the
same
principles
that
were
applied
to
the
twig
initiative
to
backdrop,
but
we're
sticking
with
php-based
templates
all
right.
That's
it
for
minor
projects.
A
We
have
a
section
in
the
agenda
every
week
to
talk
about
anything
from
the
project
management
committee.
The
project
management
committee
currently
consists
of
just
jen
and
myself,
where
we
handle
any
conflict
resolution
or
any
decision
making
anything
that
gets
stuck
within
the
project
that
gets
escalated.
Then
we
can
discuss
it
and
release
decisions.
A
We
haven't
never
had
anything
in
this
section
yet
because
our
community
is
small
enough
when
we
haven't
had
any
real
disagreements,
but
in
the
future.
If
such
a
thing
were
to
be
escalated,
we
would
discuss
it
at
this
point.
A
Okay,
besides
the
project
itself,
we've
got
a
bunch
of
peripheral
projects
that
we're
also
working
on
things
like
websites
and
community
tools
and
and
all
of
the
pieces
that
we
need
around
the
software
itself.
A
We're
working
on
rolling
out
a
new
api
website
api.backdropcms.org,
which
is,
we
have
a
separate
issue,
queue
for
managing
everything
in
the
backdrop
cms.org
process.
So
we
have
a
separate
issue
for
that
issue.
15.
In
the
backdrop,
cms.org
issue
queue
to
set
up
this
api
website,
the
good
news
this
week
hooray,
we
have
a
new
site
that
is
in
progress.
Luke,
who
volunteered
to
do
it
ages
ago,
got
around
to
actually
building
out
the
new
api
website.
A
It's
hosted
at
a
temporary
url
right
now,
which
we
can
put
in
the
the
notes
of
this
meetup.
It's
also
in
the
agenda,
and
it's
looking
really
good.
He
just
built
it
out
from
a
dribble
seven
site
using
the
api
distribution
and
it's
looking
fantastic.
A
It
already
includes
all
of
the
api
documentation,
so
it's
identical,
basically
api.drupal.org
and
its
functionality,
but
we're
planning
on
using
the
api
website
for
more
than
just
more
than
just
function,
documentation
like
reading
the
code
and
then
turning
into
docs
we're
planning
on
combining
all
actual
code
documentation
into
this
website,
as
well
as
change
logs,
and
so
that
functionality
we're
still
working
on
building
out,
but
we'll
probably
be
moving
that
site
to
api.backdrop
cms.org
in
the
very
near
term.
A
A
It
currently
still
connects
to
drupal.org
and
will
unfortunately
tell
you
that
your
version
of
your
cms
is
out
of
date
because
backdrop
is
version
1.0
and
obviously
there's
a
lot
newer
versions
of
of
triple
1.0,
so
so
we're
working
on
making
it
so
that
all
of
those
updates
actually
get
reported
to
a
central
server,
which
means
that
we
need
to
somehow
build
a
similar
solution
to
drupal.org,
probably
using
the
same
code
that
drupal
uses
to
keep
track
of.
You
know
whether
or
not
modules
have
new
releases
or
not.
A
We
don't
have
any
progress
on
that
at
this
point,
if
anyone's
interested
in
volunteering.
For
that
we're
more
than
happy
to
help
you
bootstrap
and
get
started
on
that,
so
speaking
of
keeping
things
updated,
we
also
want
a
way
to
manage
our
contributed
modules
and
our
plan
is
to
host
contributed
modules
on
github,
but
then
connect
them
to
a
central
repository
via
a
github
service.
So,
under
the
github
preferences
for
any
project,
you
can
enable
service
that
basically
pings
some
central
server.
A
Whenever
something
happens,
whether
that's
like
you
know,
a
new
pull
request
comes
in
or
a
new
release
is
made
and
what
we're
hoping
to
do
is
use
github
for
package
management,
use
their
tools
for
creating
releases
and
issue
queues,
and
things
like
that.
But
then
synchronize
that
with
the
central
backdrop
cms.org
server
and
then
that's
how
we
will
report
updates
from
our
central
server
based
on
projects
that
are
hosted
in
github.
A
A
So
if
we
have
any
node.js
aficionados
out
there
that
are
interested
in
helping
build
out
this
service
we'd
be
more
than
happy
to
accept
your
help.
That's
in
the
backdrop,
cms.org
issue
queue
issue,
number
eight,
let's
see
and
finally
work
on
the
flagship
site
itself.
A
Backdrop
cms.org
we
are
wanting
to
pursue,
pursue
an
updated
redesign
right
now
or
our
site
is
basically
a
wireframe
based
site,
but
we'd
like
to
fill
that
out
with
a
full
redesign
right
now
our
logo
isn't
even
used
on
the
on
the
website,
so
at
the
very
least
we'd
like
to
get
it
incorporated
once
we
have
backdrop
released
we'll
also
roll
out
things
like
a
showcase
section
right
now,
there
isn't
anything
to
showcase,
because
there
aren't
any
sites
and,
of
course,
the
modules
and
themes
section
for
actually
building
out
or
for
browsing.
A
The
available
modules
and
themes
needs
to
be
built
out
on
the
site
as
well.
A
So
that's
it
for
our
updates.
In
terms
of
where
we
are
on
the
project,
we
always
like
to
remind
people
that
we
have
a
sprint
every
thursday
today
after
the
weekly
meeting,
so
I'm
going
to
be
in
the
queue
reviewing
things
and
posting
things,
and
if
you
have
any
questions
you
can
you
can
ping
me
on
irc,
quick,
sketch
and
I'd
be
happy
to
bootstrap
you
we're
always
in
irc
in
pound
backdrop
on
freenode.
A
Let's
see
and
we've
got
a
couple
of
events
that
we're
going
to
be
at
jenna
and
I
are
both
going
to
be
at
drupalcorn
in
des
moines
iowa
we're
going
to
be
a
keynote
speaker
keynote
speakers
and
you
can
catch
us
there
and
we're
also
going
to
be
speaking
at
twin
cities.
Drupal
camp
also
on
fact
drop.
So
if
you're
interested
in
meeting
with
us
in
person
and
you're
in
either
of
those
locations
in
the
midwest
we'd
love
to
see
you,
let's
see.
A
Finally,
some
other
events
and
things
in
publicity
that
we're
working
on.
We
will
be
at
drupalcon,
amsterdam,
we're
not
doing
any
official
talks,
but
we
might
have
a
birds
of
a
feather
talk
or
we'll
be
there
to
to
meet
up.
If
you
want
to
in
september
and
of
course,
we'll
be
at
bad
camp
john's
one
of
the
primary
organizers
for
bad
camp
in
november.
Here
in
the
bay
area
and
we'll
be
giving
another
talk,
then
let's
see,
we've
got
some
plans
to
speak
it
at
user
groups.
A
A
The
entire
magazine
is
the
drupal
8
edition,
but
after
you
go
through
the
60
pages
of
drupal
8
content,
there's
a
nice
full
length
article
on
backdrop.
It's
the
last
article
in
the
whole
magazine,
so
good
publicity
getting
getting
the
word
out
there
and
we
got
a
lot
of
really
great
feedback
from
that
article.
A
So
that's
it
for
the
publicity
section
at
the
end
of
our
at
the
end
of
our
meetings,
we
like
to
open
it
up
and
see
if
anybody
has
any
questions
or
any
general
chatter
they'd
like
to
talk
about,
we've
got
a
couple
of
attendees
here.
You
guys
have
anything
to
add
or
any
questions
or
anything
that
we
should
add
to
our
weekly
calls.