►
From YouTube: Backdrop CMS weekly meeting 3/27
Description
Backdrop CMS strategy meeting and progress report!
A
All
right,
happy,
Thursday,
happy
back
job
everyone
back
draft
day.
We
are
here
because
we
believe
that
there's
a
cost
that
comes
with
change
and
we're
trying
to
create
a
new
CMS
out
of
what
we
loved
of
Drupal
7
and
on
the
same
kind
of
architecture,
but
including
a
whole
bunch
of
features
that
are
comparable
to
those
in
Drupal
8.
A
Through
that
process,
we're
going
to
be
fixing
all
the
bugs
we
can
sow
bugs
that
exist
in
Drupal
7,
bugs
that
have
been
fixed
in
Drupal
7
bugs
have
been
faced
in
Drupal
8
and
any
other
bucks
that
we
find
along
the
way
we
will
try
and
also
fix
and
where
possible,
we'd
like
to
simplify
existing
system.
So
are
things
in
Drupal
7
were
too
complicated.
We
want
to
streamline
them
as
long
as
it
doesn't
involve
too
much
API
change
and
we
also
want
to
add
new
features.
A
A
So
we
have
a
huge
medallist,
a
lot
of
that
stuff
we
can
just
cross
off
because
we
don't
want
to
convert
from
one
system
to
another,
but
there's
a
bunch
of
really
good
jumps
in
there
that
we
might
want
to
include
as
well
I'm,
not
sure
we
only
get
all
of
those
changes
done
before
we
release,
but
we'll
be
able
to
at
least
evaluate
them
and
put
them
into
a
timeline
for
whether
we
want
to
add
those
things
in
the
future.
Again,
if
we
don't
get
it
in
before.
A
One
point
know
we'll
have
to
make
sure
we're
not
breaking
I
api's
to
add
it
in
the
future.
We
also
have
a
bunch
of
security
issues.
These
are
things
that
don't
have
issues
and
don't
have
issues
public
issues
on
drupal.org
don't
have
patches,
we
can
directly
apply.
There
are
currently
seven
security
issues
for
Drupal
7.
We
fix
six
of
them
in
backdrop
since
our
pork
date,
the
last
one.
We
have
a
couple
of
solutions
for
that
are
all
non
ideal
solutions,
so
we're
letting
that
one
sit
in
the
issue
queue
to
see.
A
If
anyone
else
has
any
ideas
about
how
we
can
solve
that
particular
problem
with
breaking
less
of
contribs,
we've
got
a
couple
of
major
projects
that
we're
working
on
the
first
and
most
exciting.
One
in
this
list
is
blocks
and
layouts,
which
is
something
that
is
near
and
dear
to
my
heart,
because
I
left
panels
and
I
think
that
the
layout
system
in
drupal
7
theme
was
kind
of
done
all
wrong.
It's
been
that
way
for
a
really
long
time
and
people
had
a
really
hard
time
changing
it.
We're
gonna
fix
that
problem.
A
B
Sure
so
so
things
are
coming
along.
I've
been
working
on
basically
porting
panels
to
backdrop
with
some
slight
differences
in
architecture
involves
pretty
significant
differences
in
architecture,
but
close
enough
that
we
should
be
able
to
be
porting
things
between
the
existing
integrations
for
panels.
We
should
be
able
to
port
those
to
this
layout
module
and
hopefully
keep
most
of
the
critical
like
Lynch
pin
code
from
panels
in
a
way
that
we
won't
need
to
rewrite
it
all
from
scratch.
B
Right
now,
progress
wise
we've
been
making
some
some
movement
towards
the
sort
of
increasing
the
similarity
between
layout
module
and
panels.
Like
originally
I
thought.
Oh,
we
can
simplify
this
all
the
way
down
to
make
it
so
much
easier
than
panels,
but
architectural
II,
the
more
I
go
along
the
more
similar.
B
It
becomes
two
panels
itself,
which
I
guess
shouldn't
be
that
surprising
that
architectural
II
all
of
these
issues
have
been
worked
out
already,
so
we're
ending
up
with
something
architectural
II
like
conceptually
in
terms
of
like
arguments
that
come
in
and
a
selection
criteria
and
contexts.
All
of
those
concepts
are
moving
over
pretty
much
directly
into
this
layout
module.
B
The
one
thing
that's
definitely
changing.
A
lot,
though,
is
the
user
interface
for
all
this
stuff
is
being
rewritten,
so
we're
not
needing
to
go
through.
So
many
like
wizards
and
like
steps
in
order
to
get
things
going.
So
the
UI
is
significantly
simplified
as
much
as
we
can,
while
keeping
all
the
same
concepts.
Basically
I
think
it's.
Actually
it's
got
a
lot
of
the
same
things
going
on,
but
the
workflow
is
a
lot.
It's
it's
much
more
streamlined,
so,
unfortunately,
I
haven't
even
pushed
that
up
anywhere.
B
A
We
also
want
to
make
sure
those
are
responsive.
There
are
a
bunch
of
changes
that
happened
in
bar
taken
and
maybe
not
in
panels,
but
in
in
sort
of
future
of
what
the
code
that
we're
working
with
now
that
we
should
also
take
into
account
and
I
know
that
I
gotten
a
bunch
of
people
friend
Enders
and
the
last
few
weeks
asking
how
they
could
get
involved
in
backdrop
and
I
feel
like
I'm.
Helping
us
create
these
layouts
might
be
good
place
for
that
so
Nate.
A
If
you
want
to
talk
to
me
after
this
meeting
about
with
which
things
you
want
to
start
with
and
where
you
want
to
hand
off
like
creation
of
layouts
other
people
we
can
maybe
creates,
and
that
issues
and
task
those
out
to
people
to
some
might
be
good
in
our
near
future
way
to
leverage
some
more
people
great
and
other
things
that
we've
done
are
getting
the
views
module
into
core.
We
have
the
core
of
views
into
the
core
of
back
jab,
but
we
still
have
a
bunch
of
conversions
that
need
to
happen.
A
So,
if
I
an
wants
to
build
some
views
and
see
how
cmi
works
for
backdrop,
we
could
definitely
some
help
there.
We
also
have
a
CM
I
config
management
system
that
needs
some
more
systems
converted
to
use
it.
So
we
could
use
some
help
there
as
well
minor
projects
that
we're
working
on,
and
this
is
where
I
start
getting
really
excited.
We
have
a
bunch
of
user
experience
of
improvements
that
we
want
to
get
into
backdrop.
1
point
0
point
0,
but
they're
not
as
big
a
priority
some
of
these
major
systems.
A
A
Some
of
them
can
probably
get
done
after
the
release,
especially
if
they're
just
things
like
terminology
changes
in
these
are
interface,
but
if
it's
something
bigger,
like
you
know,
putting
in
a
rich
text
editor,
that's
something
that
is
really
hard
to
add
after
release,
without
changing
it
guys.
So
that's
something
I'm
really
passionate
about,
and
we
definitely
need
help
on
those
issues
as
well,
and
we
also
want
to
start
on
theme
system
cleanup.
A
So
this
is
the
same
kind
of
changes
that
wanted
to
Drupal
8
minus
the
conversions
to
twig,
so
I
know.
After
talking
to
friends
last
week,
I
went
created
a
whole
bunch
of
issues
specifically
around
what
we
should
be
changing
like
what
the
scope
of
our
changes
would
be
for
backdrop.
A
lot
of
the
issues
are
linked
to
their
equivalent
issues
on
drupal.org,
so
you
can
see
how
those
changes
happened
before
so,
if
I
don't
wants
to
jump
in
there,
there's
a
lot
of
low-hanging
fruit
on
that
as
well.
A
Most
of
those
changes
probably
need
to
wait
until
after
our
Drupal
7
patches
get
in,
but
there
are
a
couple
of
them
that
would
be
completely
unaffected.
So
if
you
want
to
look
at
the
list
and
see
you
know
like
removing
theme
functions
that
can
happen
before
after
it
doesn't
matter
so
stuff
like
that
that
it
definitely
is,
it
feels
good
feels
good
remove
stuff,
and
we
could.
We
can
use
some
help
on
those
too.
A
So
that's
in
our
inner
near
future,
here
just
great
and
for
the
exciting
part
we
have
a
bunch
of
other
stuff
we're
working
on.
That
is
not
backdrop.
The
software
including
backdrop
CMS
org,
our
primary
website
and
we've
been
through
a
content
strategy
phase
we've
been
through
a
design
phase
and
within
three
development
phase,
and
our
website
is
nearing
launch,
so
I'm
thinking
we'll
probably
be
able
to
launch
it.
A
Tomorrow
we
have
a
designer
of
you
meeting
scheduled
tonight
with
our
designer
to
make
sure
that
we
got
all
the
little
bells
and
whistles
you
wanted
on
there.
Our
initial
launch
tomorrow
is
just
a
super
simple
website.
That's
got
a
home
page,
does
what
we
are
and
then
our
handbook
that
talks
about
like
our
philosophy,
so
people
can
kind
of
see
number
one
more
for
real.
We
have
a
real
website,
but
number
two
like
they
want
to
know
more
about
us
all.
A
The
information
is
going
to
be
there,
and
this
and
we've
already
gone
through
kind
of
the
content
that
we
want
to
have
in
the
long
term
we've
been
through.
You
know
what
do
we
want
on
the
modules
page?
How
do
you
want
when
you
want
the
download
page
to
work
like,
and
we
have
plans
for
all
that
stuff?
A
It
just
seemed
unnecessary
to
put
all
of
those
pages
up
now,
while
most
of
them
are
empty,
so
we're
going
to
launch
our
first
website
soon
tomorrow,
hopefully,
and
with
all
of
the
information
that
people
need
to
know
about
our
project
and
as
we
have
other
things
becoming
available,
we'll
add
other
pages
to
the
site.
We've
already
got
all
the
work
done
fro,
so
it
should
be
pretty
easy
to
maintain
this
thing.
Look
forward
as
of
today.
Our
new
website
is
running
Drupal
7.
A
But
before
we
launch
backdrop,
one
point
0
point
0:
we
will
probably
port
this
site
to
back
job.
We
just
felt
like
between
now
and
then
it
wasn't
quite
stable
enough
to
launch
yet
I
mean
the
things
we're
doing
with
the
website
today
are
not
very
complicated,
in
fact,
drop
of
them
perfectly
capable
of
doing
it.
But
if
we
want
to
do
something
in
a
month,
the
backdrops
not
quite
ready
for
she
should
just
not
limit
the
things
the
website
could
do
by
the
software.
But
by
the
time
1
point
0
point
0
is
out.
A
We
need
to
be
on
backdrop,
so
it'll
be
our
first
test
case
of
my
greeting,
a
Drupal
7
sent
to
a
backdrop
site
which
I
think
will
make
a
really
exciting
blog
post
and
be
able
to
use
a
bunch
of
publicity
on
that
as
well.
So
I
think
I
think
we're
in
a
good
position
with
our
website,
which
is
great.
We've
got
a
bunch
of
really
great
quotes
from
people,
both
people
from
the
Drupal
community
and
people
outside
the
Drupal
community.
A
Just
talking
about
why
they're
interested
in
backdrop,
we
obviously
don't
have
a
product
for
them
to
review
and
talk
about
yet,
but
I
think
that
quite
sort
of
helps
set
the
stage
like.
Why
is
this
necessary?
Why
are
people
interested
in
it
and
get
those
quotes
up
there,
and
then
we
have
a
download
button.
Of
course,
it
says,
like
you
know,
we're
still
in
development,
so
we
will
know
they're
downloading
the
master
branch
and
it's
not
anything
official
and
we
also
have
a
demo
on
Pantheon
button
which
won't
be
up
tomorrow.
A
You
know
this
is
for
real.
It's
happening.
We've
got
a
bunch
of
progress,
they've
got
something
for
you
to
see
and
I
think
that'll
be
huge
for
us
too.
So
I'm
super
excited
about
that.
So
yeah,
that's
like
watching
tomorrow,
ish
originally
we
anticipated
in
April
first
launch
and
then
we
were
like
maybe
April,
Fool's
Day
is
not
the
best
day
to
launch
but
say
so
we're
going
to
try
and
push
it
up
and
do
it
earlier,
which
I
think
is
great.
A
Let's
see
also
we
have
an
API
site
under
way.
I
know.
Nate
gave
me
access
to
a
server
last
week
that
I
haven't
looked
at
I
promise,
Luke
you're,
probably
watching
I
promise
you
be
on
the
server
all
set
of
today.
Make
sure
you
get
have
access
to
that,
just
to
kind
of
do
some
basic
site
building
and
set
us
up
a
place
where
we
can
put
in
change
notices.
A
Obviously,
to
hook
up
the
API
portion
of
that,
that
is
less
urgent,
because
our
AP
eyes
are
still
changing,
but
it
would
be
good
for
people
to
kind
of
look
at
Drupal's,
API,
backdrops
API,
compare
them
one
to
another,
so
I
think,
like
you
know,
we
don't
necessarily
need
it
today,
but
the
sooner
we
get
it
done
the
better.
So
if
we
have
anyone
who
wants
to
work
on
getting
that
functionality
going,
that
would
be
really
great.
A
We
also
need
an
update
server,
so
this
is
the
machine
that
tells
you
whether
your
backdrop
website
is
up
to
date
or
not.
This
is
something
that
you
know
we're
gonna
need
before
we
launch.
We
don't
necessarily
need
right
away,
but
it
could
be
kind
of
tricky
to
figure
out.
So
if
anyone
wants
to
work
on
that,
that
could
be
kind
of
a
fun
project
and
we're
also
going
to
need
an
official
github
service.
A
I
know
I've
had
a
couple
of
conversations
about
people
who
are
interested
in
working
on
that,
so
we'll
try
and
get
moving
on
that
as
well.
Let's
see
sprint's
so
today,
after
this
meeting
we're
going
to
have
our
usual
Thursday
backdrops
front,
where
I'll
be
in
IRC,
creating
issues
creating
pull
requests,
merging
patches,
all
that
fun
stuff,
removing
things
from
the
theme
layer
may
be
cozy.
So
that
would
be
really
great
and
we
also
have
a
couple
of
upcoming
in
persons.
A
There's
a
bunch
of
drupal
events
that
you
know
a
bunch
of
people
in
our
community
are
going
to
anyway,
so
be
good
to
at
least
have
conversations
about
backdrop
and
lindy
and
chicago's
mid
campus
this
weekend.
I
think
it's
this
weekend
might
be
next
weekend
next
weekend.
This
is
still
March
still
March
it's
soon
anyway.
So
if
anyone
wants
to
just
talk
about
backdrop
at
these
events,
just
I
know
there's
a
lot
of
rumors
about
what
we're
doing
that
aren't
necessarily
true,
just
kind
of
have
the
conversation
with
people
and
be
like.
A
No,
no,
that's
not
what
it's
about.
You
know
we're
trying
to
make
a
better
product
for
the
people
who
can't
afford
a
tens
of
thousands
of
dollars
project
we're
trying
to
you
know,
move
it
downstream,
we're
going
to
make
it
faster
for
hosting
we're
going
to
make
it
easier
to
understand
it's
going
to
be.
You
know
less
enterprise-e,
so
you've
got
the
enterprise
solution
interplay
and
you
have
the
nonprofit
solution
in
backdrop.
A
I
think
both
of
those
two
products
can
coexist
happily
and
I
think
that
we
should
kind
of
work
on
building
that
positive
relationship
and
make
sure
that
you
know
we
can
kind
of
stop
people
from
being
so
mad
at
us
or
possible
by
setting
the
record
straight.
So
there's
a
list
of
all
of
the
upcoming
events
in
in
the
google
doc.
A
I
feel
like
it's
probably
getting
too
long
for
us
to
talk
about
every
week,
but
I
did
just
want
to
say
the
one
new
thing
that's
been
added
for
sure
this
week
is
a
Twin
Cities
drupalcamp
in
August
they
just
announced
their
dates
is
august,
seven
through
10th.
We
obviously
have
a
lot
of
friends
in
that
area.
This
is
the
conference
for
last
year
we
first
started
a
beta
testing.
Our
idea
of
doing
a
fork,
so
they're
all
very
familiar
with
backdrop,
and
they
have
asked
us
to
come
and
talk
about
it.
A
I
think
Nate,
first
Sugar's
going
I'm
a.
Maybe
I've
got
a
horse
competition
that
same
weekend
that
I'd
really
like
to
go
to
so
I've
got
to
figure
out
where
my
priorities
lie.
We're
software
I,
don't
know
all
figured
out,
and
then
we've
got
a
bunch
of
user
group
meetings
coming
up
to
one
here
in
the
Sonoma
County
next
tuesday,
and
then
shortly
after
that,
the
east
bay
drupal
meetup
we're
just
going
to
kind
of
go
and
show
them
backdrop.
A
We
can
do
a
presentation,
we
can
do
a
show
and
tell
obviously
the
closer
we
get
to
release
date.
People
can
actually
want
to
see
the
thing.
So
if
we
will
start
working
on
that,
which
should
be
really
fun,
I
also
have
a
list
of
podcasts
on
here.
I'm,
not
sure
we're
actually
going
to
be
doing
any
of
them.
We
don't
have
any
dates
scheduled,
but
it's
something
that
I
thought
might
be
good
to
kind
of
talk
about
it.
A
Now
that
all
the
stress
has
died
down
just
kind
of
say
hey,
this
is
what
we're
at
is
what
we're
doing.
This
is
where
you
can
go
to
try
it
and
do
kind
of
a
calmer,
a
podcast
about
it
with
one
of
these
people,
if
not
more
than
one,
and
we
also
have
my
article
coming
out
and
drupal
watchdog
and
it's
really
hard
to
write
words.
A
I
find
I
one
much
easier
time
writing
code,
but
when
you
have
to
like
explain
yourself
in
a
way
that
when
you
present
this
written
thing
to
somebody
else
who
doesn't
know
what
you're
talking
about
it
to
understand,
it's
really
hard
but
I've
gotten
a
lot
of
really
great
feedback
from
the
watchdog
editors
and
we're
going
to
try
and
do
it
in
a
way.
That's
you
know
we're
not
comparing
to
Drupal
8,
very
much
just
Cheyenne's.
A
You
know
tell
the
story
of
why
we're
here
without
upsetting
anyone,
I'm
trying
to
paint
a
fair
picture,
but
we'll
see
we'll
see
how
that
goes.
I
think
it
I
think
it'll
be
really
good,
but
it's
hard
and
then,
let's
see,
we've
got
ten
minutes
to
talk
about
other
stuff.
That
makes
everybody
really
excited
questions.
Anyone
has
or
excitement
about
the
website.
A
A
Oh,
oh,
wait
wait
one
more
exciting
thing
so
also
on
that
list.
Last
week
I
wrote
a
bad
camp
on
there
and
then
for
the
dates.
I
wrote
like
oh
tentative,
because
that
wasn't
public
yet
but
its
public.
Now
we
just
announced
bad
camp
safety
october.
Twenty
thirty
six
shameless
plug.
It's
gonna
be
different.
This
year
we're
gonna,
try
and
move
into
San
Francisco
such
it'd
be
really
fun.
We've
got
a
giant
like
hangar,
we're
gonna
fill
with
Drupal
people.
Hopefully
we
can
work
that
out.
It's
gonna
be
cool,
so.