►
From YouTube: Backdrop CMS weekly meeting 4/17
Description
Backdrop CMS
A
Are
on
air
happy
Thursday
everybody!
It
is
a
wonderful
beautiful
backdrop
day!
I
have
to
apologize
in
advance.
My
voice
is
not
doing
so
well.
I
seem
to
have
come
down
with
a
terrible
cold.
So
if
I
have
to
blow
my
nose,
I
might
like
mute
myself
if
I
remember
just
how
apologizing,
if
it's
for
that
anyway,.
A
So
today
is
we
are
here
in
mid-april:
we've
got
a
new
website.
We're
really
happy
about.
We've
got
a
lot
of
new
features,
we're
working
on
in
back
shop,
which
we're
pretty
excited
about.
We
are
working
on
backdrop
CMS,
which
is
a
content
management
system
for
the
nonprofits
and
the
small
to
medium
sized
businesses.
A
It's
kind
of
a
step
down
stream,
where
drupal
8
is
taking
a
step
towards
the
enterprise,
we're
kind
of
trying
to
build
the
tool
for
the
little
guys,
and
it
will
be
a
famous
that
has
features
that
are
comparable
to
Drupal
8,
but
will
be
on
a
code
architecture
more
like
that
of
Drupal
7.
So
anyone
who's
done
more
fun
triple
seven
should
be
able
to
work
on
backdrop
instantly
without
a
huge
learning
curve.
It's
just
kind
of
more
of
the
same
we're
going
to
be
adding
new
features.
A
We've
got
cmi
and
views
and
for
already
we're
going
to
be
working
on
a
block,
some
layout
system,
which
will
hopefully
solve
some
of
the
biggest
pain
points
that
have
been
around
in
Drupal
for
a
while
and
we're
going
to
try
and
fix
a
bunch
of
bugs
while
we're
at
it.
We've
got
already
got
a
bunch
of
bug,
fixes
that
have
gone
into
Drupal,
7
already
merged
into
backdrop.
We're
going
to
be
looking
at
all
of
the
future
bug
fixes
for
Drupal
7
as
well
as
many
of
the
things
have
been
fixed
in
Drupal.
A
8
will
also
be
fixed
and
backdrop,
but
maybe
not
fixed
in
exactly
the
same
way,
because
we're
going
to
be
doing
things
a
little
differently
with
our
code
and
we're
also
going
to
try
to
simplify
existing
systems
and
add
even
more
new
features
as
long
as
that
doesn't
require
too
much
API
change.
So
Drupal
8
is
adding
a
ton
of
new
stuff,
which
is
great.
We
want
to
add
ton
of
new
stuff
too,
but
we're
not
going
to
rewrite
a
entire
system.
A
So,
in
order
to
do
that,
so
we're
going
to
kind
of
look
at
the
features
we
want
find
out.
You
know:
can
we
just
merge
in
existing
Drupal
7
modules,
because
those
seem
to
be
a
fairly
popular
and
make
it
just
easier
for
people
who
any
no
Drupal
to
continue
working
on
a
system
that
has
great
new
toys?
It'll
be
great.
The
big
thing
is
just
we
just
don't
want
to
change
the
underlying
system
too
much
our
timeline
we're
looking
to
have
our
first
release
of
back
job,
which
will
be
back
drop.
A
One
point
0
point
0
coming
out
this
summer,
which
will
be
we're
thinking,
June
or
July,
where
we've
got
a
bunch
of
conversions
that
we
need
to
get
done
before
then
in
terms
of
converting
subsystems
to
see
AMI
and
converting
listings
to
views.
Those
are.
A
There
are
two
major
blockers,
the
rest
of
the
stuff
that
we
want
to
get
in
is
nice
to
have,
but
we
can
probably
add,
after
that
initial
release,
so
we're
going
to
set
a
deep
pretty
soon
here
and
then,
after
that,
if
we
don't
get
to
end
by
that
date,
then
it's
not
getting
in
until
the
next
version
of
actor.
So
that's
what
we're
looking
at
we've
got
a
bunch
of
stuff
that
we're
working
on
in
terms
of
backports
from
Drupal
8.
A
There
are
more
than
7,000
issues
or
7000
commits
that
have
made
to
drop
weight
between
the
date
when
we
forked
it,
which
was
at
January,
29th
or
februari,
29,
2012
and
now,
or
at
least
last
week,
drop
a
bunch
more
between.
Lastly,
this
week
we're
not
going
to
worry
about
all
of
those
commits
right,
because
there's
a
lot
of
those
commits
that
are
converting
from
one
system
to
another
they're
making
the
codebase
align
with
principles
that
don't
apply
to
backdrop.
A
But
there
are
a
lot
of
really
good
things
and
those
commits
to
everything's
like
making
the
site
use
html5
elements.
There
are
things
like
making
all
of
our
themes
response.
If
there
are
things
like
cleaning
up
documentation,
there's
a
bunch
of
stuff
in
there
we
do
want
so
we're
just
going
to
kind
of
do
a
pass
on
all
of
these
commits
and
say
you
know
of
the
stuff.
That's
happened
to
Drupal
8.
What
do
we
want
for
backdrop
to
and
what
is
the
stuff
that
we're
happy
to
ignore?
A
So
we've
got
a
bunch
of
meta
issues.
There
are
eight
of
them.
Well,
there
are
four
of
them
that
are
currently
up
on
github.
Each
one
has
about
250
issues
that
have
already
been
pruned.
These
are
issues
that
we
kind
of
hand-picked
out
of
out
of
the
list,
starting
from
oldest
to
newest
and
said.
We
definitely
want
to
do
these
things,
and
then
we've
got
a
couple
of
other
issues
that
are
related.
A
We've
pulled
out
all
of
the
CSS
changes
and
moved
them
into
one
meta
issue.
We
pulled
out
all
the
JavaScript
issue,
some
of
those
into
another,
it
meta
issue
and
their
reason.
We
did
this
because
those
things
need
to
kind
of
be
looked
at
holistically
right,
there's
a
whole
bunch
of
CSS
and
JavaScript
clean
up
that
happened
in
Drupal
8
that
we
may
or
may
not
want
in
back
trap.
And
if
we
want
to
do
things
like
change
all
of
our
class
names,
then
we
can
apply
those
patches.
A
How
do
you
convert
something
to
cmi,
but
we're
not
going
to
be
able
to
use
that
patch?
So
those
are
all
separated
too
and
then
there's
a
bunch
of
like
Stan.
My
follow-up
issues
that
we
may
or
may
not
need
to
consider
like
you
know,
maybe
we
forgot
the
same
thing
they
forgot,
but
maybe
we
didn't,
maybe
it's
included
in
our
so
there's
just
kind
of
a
list
of
things
that
we
should
review
and
if
we
need
to
think
about
those
problems
and
solve
them
also
we'll
deal
with
those.
A
A
A
If
Drupal
that
came
out,
we
should
look
at
that
security
fix
that
went
into
seven,
make
sure
that
we
have
something
comparable
and
impact
drop
as
well,
and
then
I
I
think
we're
really
close
in
terms
of
making
sure
that
we're
comparable
to
where
drupal
7
is
in
terms
of
all
its
big
bug
fixes.
So
that
should
be
done
probably
this
week,
which
will
be
really
great
and
as
soon
as
we
get
the
drupal
7
crafts
ports
done.
A
That
means
that
we
can
change
backtracks
name
so
right
now
hit
in
the
code,
not
changing
backdrop
saying
the
changing
drupal
backdrop
in
the
code
right
now,
there's
a
whole
bunch
of
functions
that
start
with
Drupal.
There's,
like
you
know,
Drupal,
add
CSS
through
Pelagius.
When
you
run
the
Installer,
it
says
you
know
installing
drupal
right.
A
There's
a
med
issue,
I
think
to
talk
about
changing
all
the
function
names.
We
should
decide
whether
we
want
to
call
them.
You
know
backdrop
at
j/s
or
just
at
jas.
I
think
there's
kind
of
a
lot
of
momentum
about
leaving
out
the
name
of
the
software
number
one.
If
anyone
ever
decides
to
fork
backdrop
in
the
future,
it'll
be
much
easier.
If
you
don't
have
the
name
of
the
software
and
the
function
calls.
So
we
know
that
going
forward
and
also
like,
is
it
really
necessary
like?
A
Are
we
going
to
be
battling
a
PHP
function,
it's
the
same
like?
Is
there
a
PHP
at
jas
function?
If
there's
not,
then
what
are
we
worried
about
in
terms
of
namespace
conflicts?
Is
our
module
called
a
DJ
s
or
a
theme
called
a
DJ?
S,
like
you
know,
is.
Are
there
considerations
that
we
need
to
think
about
when
we're
renaming
these
functions?
If
not,
maybe
it's
just
more
concise
to
call
them
what
they
are
and
leave
out
the
name
in
Drupal
right
now,
there's
kind
of
a
handful
of
both
right,
like
sometimes
their
functions.
A
That
start
with
your
bowl,
and
sometimes
there
aren't.
You
know,
there's
L
functions
and
key
functions
that
are
nice
and
short
because
they're
convenient
and
then
we
have
like
drupal,
add
CSS
in
triple-a,
jss
that
are
really
for
both
some
long
and
so
it's
like.
Maybe
we
can
just
kind
of
do
a
clean
up
if
we're
changing
the
names
anyway,
maybe
we
can
make
them
better.
A
I,
don't
know
so,
there's
an
issue
where
we're
talking
about
that
and
if
anyone
has
any
strong
feelings,
one
way
or
the
other
about
whether
we
should
leave
backdrop
in
the
name
of
that
function
or
not
way
in
in
that
issue,
I
think
we're
leaning
towards
just
removing
it
unless
we
have
a
good
reason
not
to
and
I,
don't
think,
we've
come
across
any
use
cases
or
any
particular
functions
that
have
that
good
reason.
Not
to
that
doesn't
mean
we
won't.
A
If
we
start
making
the
conversions,
we
might
write
it
to
one
and
we'll
have
to
talk
about
how
to
solve
that
when
we
get
to
it
might
just
be
a
change
to
name
of
the
function
still
wouldn't
have
backdrop.
It
be
called
something
else,
so
I'm
like
really
looking
forward
to
changing
the
name,
changing
the
brand
I'm
starting
to
set
ourselves
apart
a
little
bit
more.
So
that's
super
exciting.
A
Okay,
in
terms
of
the
major
things
that
we're
working
on
in
backdrop,
we
have
blocks
and
layouts.
This
is
the
problem
of
you
know.
Right
now,
layouts
are
determined
by
your
theme,
yet
your
site's
configuration
is
married
to
wear
those
regions
are
so.
If
you
change
your
theme,
your
site
gets
broken.
It's
been
a
long
time
problem
in
Drupal.
The
whole,
like
you,
can
only
have
one
block
in
one
region.
Thing
has
been
a
long
time
problem
and
Drupal
and
there's
a
bunch
of
different
solutions
of
how
you
promised
solve
that
problem.
A
Right
we've
got
context,
module,
we've
got
Delta,
we've
got
panels
and
page
manager.
We've
got
themes
that
have
regions
out
the
wazoo
I'll
trying
to
solve
this
problem
in
creating
an
imperfect
user
experience.
I'd
say
the
least,
and
it's
kind
of
frustrating
how
that
fits
together.
So
we're
going
to
solve
that
in
in
fact
drop
by
creating
a
layout
system
that
is
part
of
core
and
is
separate
from
themes.
So
layouts
in
core
will
come
with
a
handful
of
layout
sort
of
like
panels
comes
with
a
handful
glance.
A
Now
more
themes
can
come
with
handfuls
of
layouts
and
I.
Contribs
Eve
will
just
need
to
deal
with
the
layouts
that
are
in
core.
They
can
add
additional
ones
that
they
want
to,
but
we
haven't
figured
out
exactly
how
that
works
yet
and
I
theme
will
become
more
like
a
skin
and
that
it
will.
Your
layout
is
actually
your
configurations.
It's
part
of
your
site
and
when
you
change
the
theme
it'll
just
skin
it
right
more
like
how
you
would
expect
a
theme
to
work.
A
A
It's
a
it's
a
killer
feature
that
Drupal
8
wanted
to
deliver
and
because
they're
doing
so
much
other
stuff
in
your
plate,
they
haven't
been
able
to
do
it
so
I
think
if
we
can
do
blocks
and
layouts
and
give
people
that
kind
of
better
site
building
experience,
it
will
start
to
say
backdrop
with
something
different
from
Drupal:
that's
different
from
Drupal
7.
It's
are
from
for
Drupal
8.
So
how
do
we
build
this
crazy
new
system
without
changing
what
people
already
know?
A
The
answer
is
to
base
it
off
of
what
people
already
dunno
and
so
we're
basically
taking
panels
module
importing
it
into
backdrop
with
an
entirely
new
user
interface.
So
we
know
that
panels
is
overwhelming,
there's
a
lot
of
buttons
and
it's
a
very
complicated
system,
but
it's
very
powerful
and
it
solves
almost
all
of
the
needs
that
we
need
to
have
solved.
So
we
figure.
If
there's
a
way,
we
can
write
a
new
user
interface
for
something
like
panels
and
make
it
integrate
with
a
rest
of
Drupal.
A
We
can
make
that
work
a
lot
better,
so
Nate
has
been
diligently
working
on
writing
the
new
user
interface
I'm,
trying
to
find
a
way
to
bring
complicated
concepts
like
contexts
down
into
things
that
people
can
either
understand
or
ignore
if
they
don't
need
to
and
take
things
like
blocks
and
add
them
to
the
page
in
a
way
that
makes
sense.
Bo
yaad
did
a
really
great
design
back
when
we
were
doing
black
box
and
layouts
for
Drupal
8.
A
He
built
an
interactive
tool
where
you
could
demonstrate
how
work
and
we've
been
also
basing
our
interfaces
off
of
all
the
work
that
he's
been
doing
too.
So
I
think
that
we've
we've
made
a
lot
of
progress,
which
is
really
great.
We've
got
most
of
the
user
interface
done
that
user
interface
saves
to
cmi,
but
we
don't
have
the
layouts
piece
done
yet
so
I
think
it'll
be
good.
So
we
can't
rebuild
the
pages
because
we
don't
have
the
layouts,
but
I
think
it
would
be
good
Nate.
A
C
C
We
can
decide
that
any
time
in
the
meantime
right
now,
I'm
just
using
the
layouts
that
come
with
panels
just
because
all
then
I'm
concerned
about
is
making
so
you
can
put
blocks
on
the
page
and
all
of
the
things
that
panels
does
but
yeah
deciding
the
actual
layouts
themselves
yeah.
We
can
make
that
a
separate
issue
and
start
start
tackling
that
I
have
a
feeling.
You
know
if
we're.
If
it's
a
it's
a
visual
task,
you
know,
and
so
I
have
a
feeling.
C
A
There's
no
6040
layout
right
there
30-17
layout,
it's
only
a
50
and
so
there's
definitely
places
in
there
that
we
need
to
fill
in
those
holes.
If
this
is
going
to
be
something
that
looks
in
course,
so
that
everyone
who
built
the
theme
isn't
trying
to
figure
out
how
to
make
it
not
5050
layout.
A
So
it
would
be
good
to
have
how
some
of
those
options
so
I
mean
I.
Think
we
can
figure
out
a
markup
sure
go
to
the
HTML
people
and
ask
for
that.
We
can
come
up
a
list
of
like
these
are
layouts.
We
want
this
is
the
way
our
markup
should
be
going
down
and
then,
let's
see
what
they
produce
I
agree
it'll
be
hard
to
do
that
without
a
sight
right.
A
Oh
that's,
right,
yeah,
but
I
think
there
are
enough
people
have
enough
experience
with
panels
or
layouts
in
general
and
Drupal
that
they
might
know
where
to
start
from
which
would
be
good.
Okay.
So
that's
great
any
other
updates
on
on
the
blocks
and
layout
system
that
we
need
to
worry
about.
Yet
no.
C
It's
it's
just
chugging
along
I
did
some
more
work
on
it
this
week
to
get
it
irie,
reformatted
the
cmi
files,
so
they're
structured
more
like
muses
cmi
files,
so
trying
to
get
some
consistency
between
the
way
that
views
works
in
the
way
that
layout
module
works
but
yeah
other
than
that
just
kind
of
continuing
to
chug.
Along
still
you
it's
yeah.
It's
still
got
a
long
ways
to
go.
You
still
can't
configure
individual
things.
You
can.
C
A
And
other
things
we're
working
on,
we
also
have
these
in
core,
so
he
is
obviously
number
one
downloaded
contributes
something
that
sets
you
apart
from
other
continent,
other
simpler
content
management
systems
like
WordPress,
it's
a
query
builder.
It's
super
powerful,
also
kind
of
confusing,
but
I
think
it
is
like
one
of
one
of
the
things
that
makes
gerbil
gerbil.
A
I
think
that,
if
we're
going
to
create
something,
that's
comparable,
the
drupal,
we
can't
do
it
without
views,
so
I'm
really
excited
that
we
got
views
in
core
for
backdrop,
just
those
visas
and
forever
to
wait,
and
we've
got
some
conversions
that
need
to
be
done.
So
there
are
listing
pages
in
in
core
right,
like
a
taxonomy
term,
listing
like
the
front
page
listing
that
need
to
be
converted.
Those
are
fairly
easy,
there's
some
harder
ones
like
administrative
pages,
for
example
like
the
list
of
all
your
users.
A
That
also
should
be
computed
converted,
and
we
also
have
a
usable
cooperations
equivalent
in
court,
but
not
all
of
the
operations
are
done
yet.
So
when
you
get
to
something
like
building
a
user
page,
you
also
need
to
go
build
the
operations
that,
with
a
lot
of
you
to
do
things
like
a
site
or
remove
roles,
that's
something
that
you
can
do
in
core.
If
we're
going
to
replace
that
listing
with
a
view,
we
need
to
make
sure
that
we
have
the
same
and
a
functionality
in
there.
A
So
there
are
some
easy
tasks
and
the
worst
abuse,
conversions
and
some
harder
once
we
could
definitely
some
help
on
those,
but
the
hard
stuff
is
done:
users
already
saving
to
cmi.
So
if
you're
a
nurse
in
seeing
how
cmi
stuff
works,
this
might
be
a
good
place
for
you
to
jump
in
on
that
get
get
your
teeth
on
the
sea
of
my
conversions
and
then
are
on
the
views.
A
Conversion
see
how
cmi
works
and
then
maybe
decency,
my
conversions
to
so
that's
a
fun
stuff
to
do
in
terms
of
of
those
two
things
and
then
see
my
we
talked
about
a
little
bit
earlier.
We've
got
a
bunch
of
a
metal
list
of
all
the
stuff
that
happened
in
interpolate.
That's
just
kind
of
a
reference.
A
We
also
have
our
own
internal
lists
of
all
of
the
things
that
we
need
to
convert
a
backdrop,
there's
obviously
some
things
that
we
have
in
backdrop
that
are
some
things
that
are
Drupal
8:
the
ironing
backdrop
that
we
don't
have
to
convert
okay,
but
there's
still
a
lot
of
subsystems
that
we
do
need
to
move
over.
So
we
could
use
some
help
with
that
as
well
and
then
there's
a
bunch
of
minor
things
that
are
not
released
lockers.
A
A
There's
been
a
bunch
of
work
going
on
in
Tripoli
that
have
improved
a
lot
of
them
and
we
need
to
make
sure
that
we
get
most
of
those
improvements
into
backdrop,
but
there's
also
some
other
things
that
we
can
do
as
well
and
to
make
a
process
more
sense
to
new
people
as
well
as
existing
and
drupal
users.
So
there's
some
meta
issues
on
tasks
that
we
want
to
do
like
getting
a
WYSIWYG
editor
in
that's
a
no
brainer,
but
we
need
to
actually
do
it.
So
we've
got
some
tests
like
that.
A
There's
some
some
other
minor
things
like
changing
terminology
that
creates
a
bike
sheds,
but
you
know,
is
a
very
minor
task
when
you
actually
get
down
to
doing
it,
and
so
there's
an
issue
up
with
a
bunch
of
ideas
I
have
about
those
there's.
People
will
feel
very
strongly
on
both
ways.
At
some
point.
Probably
what
we'll
do
is
take
these
terminal,
patient
terminology,
terminology
changes
and
escalate
them
to
the
PMC
for
discussion,
I'm,
hoping
that
we'll
have
a
larger
PMC
before
we
can
do
that.
A
So
we've
got
a
couple
of
people
who
are
looking
to
tap
and
see
if
they
want
to
get
involved
with
managing
a
direction
for
backdrop,
but
because
we
haven't
had
that
much
activity.
Yet
it's
kind
of
weird
to
be
like
well,
you
know,
there's
a
bunch
of
people
and
we're
just
gonna
pick
this
one
and
so
we'll
see
we'll
see
if
they're
interested
number
one
and
number
two.
A
If
they've
got
the
time
and
resources
to
put
into
that
right
now,
there's
not
a
lot
of
decisions
that
need
to
be
made,
but
who
knows
going
forward
what
we're
going
to
be
kissing
and
so
a
bunch
of
little
changes
and
the
other
thing
in
terms
of
making
it
easier
to
learn.
We've
already
got
some
ideas
about
like
developer
experiences.
Changing
things
like
module
load
include
to
be
a
little
bit
less
silly
in
the
order
of
arguments
and
and
making
it
work
for
maybe
any
file,
rather
than
just
modules
and
just
kind
of
developer.
A
Experience
clean
of
tests
like
that
and
then
also
there's
a
whole
bunch
of
these
some
cleanup
stuff.
That
I
worked
on
very
vigorously
in
Drupal
8
trying
to
make
things
consistent,
and
we
can
do
those
same
kind
of
changes
in
fact
drop
things
like
we're.
Moving
the
process
layer.
We
don't
need
that
anymore.
A
Things
like
separating
out
the
book
suggestions
from
pre-processing
so
that
your
only
pre-processing
the
template
file
you're
actually
using
rather
than
trying
to
change
it
at
the
same
time,
which
creates
some
problems
and
things
like
that,
make
a
lot
of
sense
and
then
there's
just
some
general
cleanup.
Like
we've
got
duplicate
functions.
We
don't
eat
those,
let's
just
standardize
on
one
and
make
everything
that
produces
a
list.
Call
an
item
list
or
you
know,
can
combining
menu
tree
and
menu
item.
You
know
making
it
so
that
we
don't
have
a
few
functions.
A
A
If
we'll
have
a
feedback
period,
maybe
we
should
announce
it
one
week
and
then
announce
a
decision
the
next
week,
so
that
if
anyone
wants
to
weigh
in
who's
not
on
the
PMC,
they
have
a
chance
to
do
that,
and
I
think
that
the
standard
process
will
be
there
only
an
issue
in
the
public
github
q
that
anyone
can
weigh
in
on
any
time
and
if
it
starts
to
feel
like
that
issue
becomes
a
bike
shed.
That's
when
I
gets
escalated.
A
Pmc
at
that
point,
we'll
probably
announce
the
fact
that
we're
discussing
it
open
it
up,
for
you
know
any
last
comments
and
then
we'll
close
it
and
say:
okay,
it's
going
to
the
PMC
for
decision
and
that
point
no
more
comments
can
be
ad
in
the
public
issue.
We're
just
going
to
talk
about
it,
make
a
decision
and
then
that
decision
comes
back
down
to
the
public
issue.
It
says
this
is
what's
happening
and
the
idea
there
is
to
prevent
bike
sheds
from
going
on
for
300
plus
comments.
A
We
want
to
make
more
decisions
in
and
not
necessarily
final
decisions
like
this
is
addition
for
now
we're
going
to
try
it
we're
going
to
do
what
we're
going
to
see
what
happens
and
it
doesn't
work.
We
can
change
our
minds
later.
You
know
the
ability
that
will
have
to
push
changes
out.
A
So
now
we're
announcing,
we
don't
have
anything
to
discuss
yet,
but
next
week,
if
we
end
up
deciding
to
push
things
to,
the
pnc
will
announce
that
they're
being
pushed
to
the
PMC.
Well
give
you
notifications
in
the
future
and
so
other
stuff.
We're
working
on
that
doesn't
involve
a
backdrop:
the
product,
our
other
websites,
that
we're
working
on
right
now
we're
working
on
the
API
website,
which
I
should
have
up
by
the
end
of
the
day.
Today,
Luke
McCormick
has
offered
to
help
us
do
do
some
site.
A
A
So
this
is
again
a
task
that
doesn't
require
that
you
be
a
coder
which
I
think
could
be
really
useful
to
some
of
our
new
people
who
want
to
get
involved
by
AP
eyesight
will
eventually
also
need
to
scan
our
code
and
be
an
API
site
that
we
also
need
someone
to
take
that
on
so
Luke's
going
to
start
us
off
with
building
that
the
change
noticed
piece
that
we're
going
to
need
sooner
rather
than
later,
and
then
the
API
site.
A
We're
obviously
gonna
need
that
before
we
launch
before
people
start
trying
to
write
modules
against
the
sort
of
pork
modules
from
triple
the
backdrop
or
drop
up,
drupal
module
and
a
backdrop
site
see
if
it
works,
and
so
that's
kind
of
a
priority
there.
So
we
do
have
kind
of
a
timeline
on
that
as
well.
So
the
student
is
better.
We
can
use
some
help
with
that
we're
getting
the
update
server,
so
people
are
actually
running
backdrop.
Websites
can
tell
if
they're
modules
or
themes
or
core
needs
to
be
updated.
A
Drupal
has
this
it's
super
handy.
We
just
need
to
kind
of
recreate
the
same
thing
in
back
Trapland.
So
if
any
a
nice
work
on
that,
we
could
use
help
with
that,
and
then
we
do
I
think
have
some
work
going
on
for
creating
an
official
github
service.
So
this
is,
if
you
create
a
modular
theme
for
backdrop,
you
want
to
be
able
to
tell
github
hey.
A
This
is
a
backdrop
project
and
then
the
backdrop
CMS
org
website
will
scrape
that
list
of
projects
that
exist
for
backdrop
and
pull
them
in,
so
that
you
can
go
to
backdrop
CMS
at
work
to
search
for
a
modular
theme
and
I'll
say:
hey.
You
know
if
your
module
circuits
that
exist
on
github,
so
you
still
get
a
central
place
to
look
for
it.
You
don't
have
to
look
on
github
for
modules
and
themes,
but
anyone
who
creates
one
can
register
it.
A
So
it'll
kind
of
tie
tie
that
stuff
together
JD
public,
and
then
we
have
a
backdrop.
Cms
org,
a
primary
website
got
a
little
facelift
and
some
initial
content,
which
is
great.
We
have
some
plans
for
other
things,
we'd
like
to
do
to
it.
It's
obviously
going
to
list
our
modules
and
themes
when
we
have
those
it's
going
to
have
a
showcase.
A
If
we
have
websites
that
are
running
back
drop,
it's
gonna
probably
have
a
list
of
where
you
can
find
service
providers
and
all
the
stuff
that
Drupal
that
work
well,
some
of
the
stuff
drupal.org
provides
the
backdrop
website
will
provide.
Also,
the
major
differences
are
being
that
the
issue
he's
are
going
to
be
in
github
and
the
code
itself
will
not
be
managed
on
the
backdrop
website.
A
It'll
all
be
managed
through
can
so
there
are
some
differences
there,
but
there
are
still
lot
of
great
things
that
we
need
to
provide
for
our
community
through
that
website
school.
So
we
could
use
some
help
on
that
too.
If
anyone
wants,
it
is
obviously
lower
priority.
Now
that
we
finally
have
an
actual
website
and
we
are
still
working
on
some
kind
of
branding
like
the
website,
we
have
now
doesn't
have
a
logo
or
any,
and
you
know
anything
particularly
fun.
A
If
there's
an
opportunity
for
sprinting
will
be
spending
on
backdrop,
I'm
not
sure
that's
going
to
happen
yet
I
do
they
have
really
full
schedule
so
we'll
see
how
that
goes,
and
then
we've
got
an
official
sprint
at
Drupal
corn
camp
in
Iowa.
We
are
actually
sponsoring
the
entire
sprint
day,
so
I
don't
who
wants
to
work
on
your
blade?
He
wants
to
work
on
back.
Job
wants
to
work
on
you
know
whatever
it
is.
A
They
want
to
work
on
we're
going
to
give
you
coffee
and
lunch
and
and
try
and
spread
a
little
goodwill
around
sprinting
in
general,
which
I
think
is
gonna,
be
really
good
and
we're
also
going
to
be
doing
some
sprinting
hit
the
Twin
Cities
drupalcamp
later
this
summer.
In
August
so
I'm
not
sure
they
they
need
sponsorship
yet,
but
we
have
offered
so
we'll
see
and
anywhere
else
that
we
are
that
involves
sprinting.
We
can
help
with
that
too.
Also
this
weekend,
there's
a
whole
bunch
of
nerdy
stuff
going
on
in
the
bay
area.
A
There
is
a
triple
camp
down
at
Stanford,
which
I
think
Nate
and
I
will
probably
be
going
to
lunch
Saturday
pending
a
health
and
other
things,
and
then
there's
also
a
like
a
SAS
camp
in
San
Francisco
that
I
know
a
bunch
of
people
are
going
to
which
we
probably
won't
be
played
to
Ed's
on
Saturdays.
Well,
shall
add
a
fun
text
stuff
going
on
here
in
the
near
future.
So
yeah
you
camp
season,
starting
I'll,
try
to
be
over
the
illness.
Before
I
see
anyone,
don't
any
other
people
sick?
A
What's
D,
ok,
sprinting
remotely
he's
totally
safe.
You
can't
get
a
cold
via
IRC,
so
there's
a
whole
bunch
of
camps.
We
have
on
our
agenda
that
we
are
either
planning
on
attending
I
know.
Nyc
camp
was
last
week
so
taking
that
off,
but
there's
a
whole
bunch
of
other
stuff.
Coming
up
that
we're
hopefully
going
to
be
involved
in
one
way
or
another
and
there's
a
bunch
of
user
group
meetings
we
have
coming
up
there's
one
in
we're:
gonna
do
one
in
Oakland
and
one
in
Reno
Nevada.
A
We
have
an
article,
that's
going
to
come
out
and
Drupal
watch
Doug
this
summer.
So
keep
your
eyes
open
for
that
and
yeah.
Anyone
who
wants
to
talk
to
us
about
backdrop
we're
totally
trying
to
do
this
in
the
open
in
the
clear
any
questions
why
we're
doing
it?
Does
we
left
your
pool?
We're
happy
to
answer
so
feel
free
to
reach
out
to
touch
plus
I
need
that?
Okay?
So
that's
the
end
of
the
official
agenda
I'd
like
to
open
the
meeting
up
for
any
questions
or
comments
from
anyone
else.
C
D
C
Sol
SI
mi
is
it's
if
it's
a
yeah,
it's
bad
acronym
for
us,
because
it's
short
for
configuration
management
initiative,
which
is
the
Drupal
8
initiative
that
basically
makes
it
so
that
you
can
move
configuration
from
one
server
to
another.
So
if
you
set
up
a
content
type
on
your
development
Earl
on
your
localhost,
you
can
move
it
to
your
production
site
just
by
exporting
the
configuration
and
then
importing
it
on
the
production
server
or
you
can
store
your
configuration
in
source
control
now.
So
you
wait
as
you're,
making
like
content
type.
C
It's
writing
to
files
that
are
in
in
backdrop
there
JSON
files,
so
you
store
those
JSON
files
in
get,
and
then
you
commit
your
changes
and
you've
literally
like
created
and
stored
a
content
type
in
get,
and
then
you
go
over
to
your
production
server.
We
need
to
say,
get
pull
and
that
pulls
in
the
content
type
that
you
created
on
your
development
server.
It's.
A
C
A
C
A
Me,
yes,
it's
been
a
pain
point
for
like
database
turbulence
for
a
really
long
time
and
in
Drupal
7
land.
We
had
this
awesome
solution
called
features
right
where
it
took
all
of
the
stuff
and
exported
to
cone
everyone's
like
wow.
This
is
so
amazing,
but
it's
not
quite
right
right,
because
none
of
that
stuff,
most
of
them
sup,
wasn't
meant
to
be
stored
in
code.
So
it's
a
little
janky,
it's
like
well,
how
do
you
revert
and
how
do
you
undo
and
how
do
you
like?
Can
you
delete
a
content?
A
Type
was
created
with
a
feature
like
there's
some
kind
of
weird
clunkiness
around
it,
and
it
was
just
like
well
the
reason
that
it's
clunky
is
because
you
know
Drupal
wasn't
meant
to
do
that,
and
so
it's
like
well,
what
have
we
made
a
version
of
Drupal?
It
was
meant
to
do
that
and
that's
what
cmi
in
Drupal
8
is
all
about.
It
was
like
reinventing
the
system
to
say
you
know
to
be
built.
A
This
way
right,
run
off
of
code
import
from
code
like
make
it
work
the
way
ever
and
always
wanted
it
to,
and
we
want
that
too.
We
want
that
for
triple
seven
right.
We
want
that
same
feature
in
Drupal
7
like
world,
and
so
we
kind
of
looked
at
this
problem
again
and
said:
okay.
Well,
how
can
we
take
triple
seven
and
move
it
towards
that
same
goal?
How
changing
quite
as
much
as
as
you're
Boyd
did,
and
so
we
but
they're
all
the
decisions
that
see
him.
A
I
went
through
in
terms
of
like
what
format
to
use
and
how
to
integrate
it.
We
basically
ended
up
taking
the
most
recent
version
of
cmi
that
Drupal
landed
on
and
moving
it
into
backdrop
with
some
significant
changes,
for
example,
the
format
of
our
files
for
using
JSON
files
and
they're
using
EML
files
and
there's
some
other
differences
too.
But
for
the
most
part
it's
it
solves
this
problem
that
everybody
has
been
you
know
running
into
not
just
in
Drupal
but
in
any
database
chauvin
system,
where
it's
like
you
built
a
site
in
one
place.
A
How
do
you
like
had
it?
Where
is
the
separation
of
configuration
and
data
right
them
to
figure
configuration
and
content,
because
the
content
depends
on
the
configuration,
so
you
want
those
to
be
together,
but
then
you
need
to
like
make
changes
to
the
configuration.
How
do
you
get
it
out?
How
do
you
yeah
so
the
problem
is
solved.
Theory
I'll.
C
D
C
Yeah,
it
would
be
I
mean
it'll
it'll,
be
fully
integrated
in
to
all
look
pretty
much
any
listing.
There
is
like
all
of
the
administrative
listings
like
right
now.
The
content
listing
the
front
page
I
mean
the
content,
administrative
listing,
the
editing
of
comments
or
the
comment
administration.
All
of
those
things
are
all
lists
that
could
be
managed
with
views
and
actually,
if
you
install
a
module
like
Jen's,
total
control
or
admin
menu
comes
with
one
called
admin
views.
C
A
People
like
using
views
are
gonna,
be
out
of
luck,
pretty
much
everybody
who
does
like
using
views
or
they're
gonna
be
in
luck,
because,
where
there's
gonna
be
examples
thereof,
how
to
do
everything
right
like?
Oh,
you
know,
here's
how
you
do
you
front
page
listing
here's,
how
you
do
exelon
of
me
listing
here's,
how
you
do
it
had
been
listing
I'm
in
at
all
I'll,
just
be
views
yeah.
D
C
Okay,
all
right!
Well,
let's
call
it
a
meeting.
Then
thanks
Richard
for
joining
we're
here
every
thursday.
At
the
same
time,
so
doing.
A
Well,
unless
I
don't
know,
if
Richard
you
want
to
write
a
meeting
Andy
or
someone
wanted
to
run
it
I
mean
we
basically
create
an
agenda
that
has
the
status
of
like
where
we
are
in
various
different
issues.
Next
week
be
exciting,
things
will
probably
be
that
like
issue,
135
is
done,
but
yeah
I
mean.
If
anyone
else
wants
to
run
the
meeting,
we
could
try
and
run
it
from
Mexico
I.
A
A
Did
it
anyway,
depending
on
internet
quality,
at
the
venue,
and
it
could
go
really
badly
yeah?
We
could
do
that,
but
yeah
so
and
I
know
we're
giving
a
talk.
Next
Thursday.
Our
talk
is
scheduled
for
thursday
on
factor
of
CMS,
and
so
we
probably
won't
have
a
meeting,
but
maybe
what
we
should
do
is
just
record
the
top
and
I'm
recording
it.
A
Even
if
we
aren't
going
to
do
live
stream
and
then
we
could
put
it
up
on
on
the
YouTube
channel
around
you
know
or
say
anything
or
whatever
and
send
out
a
noticing.
You
know
you're
interested
in
seeing
this
talk
here.
It
is
yeah
that
sounds
good,
all
right,
so
we'll
plan
on
no
official
meeting
next
week,
but
thanks
for
the
recommendation,
Richard
will
put
the
top
cop
instead.