►
From YouTube: Why fork Drupal? The philosophy behind Backdrop CMS
Description
Backdrop CMS is the Drupal fork. It is a faster and less-complex version of Drupal 7 with more features you want, and fewer you don't.
This session will highlight the Backdrop Mission, it's intended audience, and it's guiding principles.
We'll explain the decision making process, introduce the Project Management Committee, and expand on how the project's direction is set by the needs of the whole community.
We'll cover topics like how we handle Security and Stability, and talk about how we're trying to decrease the cost of long-term website ownership.
A
B
A
D
So,
of
course,
backdrop
is
a
fork
of
Drupal
like
I.
Think
most
most
people
know
that
for
all
intents
and
purposes
we
can
say
it's
a
fork
with
Drupal
7.
It's
actually
early
Drupal
8,
but
you
can
say
like
if
you're
on,
Drupal
7
moving
to
backdrop
is
kind
of
the
ideal
transition
we're
starting
a
new
site
from
scratch.
So
as
the
functionality
you
kind
of
expect
from
Drupal
7,
but
also
a
lot
of
features
and
things
that
were
added
into
Drupal
8,
but
on
Drupal
7
architecture.
D
A
D
A
World
people
are
starting
to
think
outside
the
box.
We
really
need
to
build
your
friend
simple
website.
Maybe
we
do
a
static
standard.
We
can
do
something
and
get
to
your.
What
have
you
to
fill
in
a
bit
different
needs,
and
so
that's
kind
of
our
data
idea.
Backdrop
is
that
like,
if
you
have
a
really
simple
site,
there
are
tools
like
Squarespace
out
there,
where
you
can
say
just
go,
make
this
workspace,
so
you
have
something
up
today,
just
for
fire,
a
lot
of
effort,
it's
being
a
little
bit
more
complicated.
A
Oh
you
customize
it.
You
can
use
something
more
like
WordPress
and
then
there's
big
fancy
enterprise
system
where
it's
like.
Okay,
you
have
a
really
complicated
need
here.
Is
this
great
tool
to
like
do
that
and
bactrim
is
supposed
to
sit
between
what
WordPress
can
do
and
what
you
really
can
do?
Sort
of
like
the
next?
The
next
version
of
Drupal
7.
D
So
Jen
and
I,
we
are
the
the
founders
of
backdrop
on
quick
sketch
on
drupal.org
and
Jenna's
Jim,
Lambton
I
think
we
have
some
things
about
this.
Yes,
so
between
the
two
of
us,
we
have
a
lot
of
experiences
dupa
website
builders,
we've
built
a
lot
of
projects
for
what
organizations
large
and
small,
mostly
large
ones
here
listed.
D
We
also
individually
have
a
lot
of
experience
during
Drupal
education
is
all
about,
was
and
like
the
original
triple
training
company
and
we're
flying
all
around
the
country,
training
people
about
Drupal
and
triple
five.
When
we
made
the
original
training
videos
for
Drupal
that
were
distributed
on
DVDs,
pretty
awesome
and
yeah
also
up
first
O'reilly
book
on
Drupal
I'm.
A
Started
doing
triple
painting
under
six
but
actually
started
it
here
we
were
asked
to
teach
a
whole
bunch
of
people
on
Stanford
how
to
use
this
new
infrastructure
to
build
your
cool
sites.
So
that's
how
I
got
started
doing
training
and
we
realize,
like
oh,
it's
gonna
be
valuable
to
everybody,
and
so
we
developed
a
class
we
started
doing.
Insurance
is
going
around
the
u.s.
teaching
body
is
your
goal.
Mitchell
Simon
came
out
and
I.
D
A
It
needs
to
be
more
intuitive
from
the
code
side
to
like
be
able
to
get
in
there
and
do
what
they
need
to
do,
and
so
all
of
these
experience
of
teaching
people
how
to
code
or
people
just
maybe
there
are
coders
but
they've.
Never
how
do
you
get
over
the
triple
isms
and
into
it
getting
stuff
done
quickly,
and
so
our
decision
on
backdrop
is
coming
from
an
experience
and
please
make
this
easier
for
people
to
work
with.
D
We
also
have
some
extensive
history
and
Drupal
core
development
and
and
just
confirmed
well
a
lot
of
experience
in
Drupal.
Double
six
I
wrote
the
Ajax
framework
that
we
still
basically
use
today
in
Drupal.
8
I
still
am
a
file
image
system
maintainer
for
Drupal
7,
never
at
the
dialog
system
in
Drupal
8
as
well
as
was
the
primary
advocate
for
you,
since
you
can
either
interpolate.
A
A
C
A
Then
the
fight
for
trying
to
make
things
easier
hilarious.
What
drove
me
to
be
the
unofficial
tweak
initiative
lead
for
two
years
in
the
triple-eight
site
books
I
wanted
to
make
the
theme
system
easier
for
people
to
understand
as
well
and
so
bringing
our
experience
in
like
understanding
how
decisions
were
made
in
Drupal,
our
experience
in
working
with
core
and
our
motivations
for
moving
Drupal
to
moving
back
up
insane
all.
A
Also
love
the
community.
We
can
spend
a
lot
of
time
at
your
boot
camps
and
conferences
for
ten
years.
I
was
the
leader
very
perfectly.
I
was
wanted
to
leave
organized
some
triple
constan
Francisco
in
2010,
and
long
before,
I
ever
contributed
a
line
of
code
did
you're
qualified,
was
running
a
registration
desk
at
an
event
and
I
felt
that
one
of
the
things
that
you
roomie
to
the
software
was
the
fact
that
it
can
help.
A
A
D
A
D
D
A
D
A
A
A
D
Yeah,
and
so
the
friended
management
committee
is
effectively
as
play,
a
more
democratic
way
of
running
a
project
where
it's
sort
of
having
a
single
BB
FL
is
the
open
source
term
for
a
benevolent
dictator
for
life,
that
that
is
the
supreme
authority
within
the
software
project.
The
Apache
model
is
the
project
management
committee,
where
they
form
a
committee
or
board.
Essentially
that
makes
all
primary
decisions
and
installment
via
votes
and
then
there's
process
for
a
introducting
new
injuries,
new
people
into
the
committee
like.
D
What's
it's
basically
just
like
a
committee
board,
but
it's
it's
the
model
that
all
Apache
projects
use
and
now
that
we're
a
part
of
this
conglomeration
of
software
freedom
Conservancy,
which
is
a
basically
a
wrapper
around
other
GPL
projects
for
being
a
physical
and
legal
sponsor.
So
you
can
donate
to
the
software
freedom
Conservancy
and
it
passes
through
money
to
other
software
projects,
including
backdrops.
They
actually
require
a
project
management
committee
model
on
top
of
also
requiring
not
requiring
but
strongly
preferring
GPL,
and
so
we
happen
to
be
like
fitting
right
within
this.
A
A
Is
a
back-end
developers
he's
looking
at
how
the
API
is
work?
I'm
gonna
work,
the
way
you
want
to
make
credit
for
it
against
them
west
through
the
coupla
is
our
front
end,
guys
to
make
sure
we're
doing
stuff
on
the
and
it's
gonna
be
easier
for
people.
Understand
people
like
to
use
Chaco
Ponte
is
there
to
represent
the
business
focus.
So
if
we
want
to
build
a
fantastic
feature
in
they'll,
be
like
no,
no
I
can't
sell
that.
It's
just
something.
That's
important
and
Gregory.
A
D
A
D
A
In
terms
of
handling
conflict
resolution,
that
means,
if
you
have
two
people
in
an
issue,
queue
who
are
arguing
with
each
other
a
lot
of
times
you
just
kind
of
let
the
fire
burn
out
and
whichever
ember
is
still
burning
and
is
the
one
that
wins.
We
don't
want
to
have
that
kind
of
conflict
in
our
community.
So
if
it
looks
like
to
feel
ordinary,
which
happens
actually
to
our
MC
members
myself
to
be
one
of
them,
someone.
A
Have
a
vote
and
it
comes
back
down
and
it
says:
okay
guys,
this
is
what
they
decided
it.
So
it'll
help
make
Constantine
or
community
members
stronger,
or
at
least
less
hostile,
we're
hoping
so
in
the
overall
direction.
The
project
is
choosing
like
okay,
what
is
going
to
be
in
fact
route
114
or
is
you
know
the
internet
will
change
vastly
ten
years
ago
we
didn't
know
we
would
be
interacting
with
phones.
So.
A
A
What
we
want
for
backdrop
or
are
we
putting
in
something
because
somebody's
driven
it
forward,
but
it
doesn't
really
align
with
what
we
want
from
our
software
and
then
also
if
you
have
something
that
comes
in
that
you're
like
everybody
on
the
team.
So
you
agree,
we
need
this,
but
it
doesn't
align
with
our
philosophy
and
that
makes
our
philosophy
needs
to
be
updated
first,
so
we
can
publicly
say
this
is
what
we're
for
and
then
you
see
that
change,
and
then
you
see
the
change
money.
D
D
This
is
what
is
a
is
that,
in
order
for
the
entire
PMC
model
to
work
like
you
bring
in
all
of
these
different
people
from
all
of
these
different
backgrounds,
they're
all
going
to
have
different
experiences.
Now
we're
gonna
have
different
biases
they're,
all
going
to
want
different
things,
and
that
is
okay,
but
what
you
you
need
is
the
the
product
philosophy
to
be
defined
so
that
people
are
winning
the
decisions
against.
What
does
the
project
need
and
my
experiences
help
shape.
D
A
I
have
this
needed,
so
this
is
really
important
and
without
something
to
say,
like
gee,
is
this
security?
What
is
everyone's
need
or
is
hearing
the
same
thing?
That's
like
what
the
project
is
a
battle.
It's
really
hard
to
decide
whether
that's
an
important
feature,
and
so
you
have
a
list.
That's
like
okay.
D
So
what
are
they
like?
What
is
the
philosophy?
That's
super
important
in
our
world,
the
first
one
is
summarizes,
easier
updates,
but
primarily
backwards.
Compatibility
is
important
and
we
came
up
with
this
philosophy.
Five
years
ago,
when
we
first
started
the
project
when
backwards,
compatibility
have
been
totally
thrown
out
the
window
in
the
world
of
Drupal,
and
this
was
kind
of
guided
like
this
being
one
of
the
most
important
factors
is
that
we
were
looking
at
this
thing.
We
need
this
like
changing.
A
Like
everyone
dedicated
before
it's
removed
and
we're
like
Drupal,
particularly
seven,
are
starting
with
it's
such
a
beast
like
how
are
we
ever
gonna
match,
either
of
those
so,
rather
than
specifically,
sitting
probably
backwards
compatible?
We
stated
that
compatibility
is
important
and
that
leaves
us
a
little
wiggle
room.
A
We
need
to
make
a
change
we
can,
but
we
need
to
find
a
way
to
support
our
developers
in
making
that
change
and,
as
we've
been
learning
through
backdrop,
it's
become
more
and
more
clear
that
we
were
really
worried
about
it,
because
people
never
did
the
backwards
compatibility
but
as
I
started,
adding
some
like.
Oh,
this
isn't
so
hard
in
most
cases
we're
finding
ways
to
do
a
smoother
transition
for
our
adopters.
D
A
There's
simplicity,
and
so
this
is
where
drupal
8
decided
to
make
all
of
the
code
object-oriented
and
based
on
symfony
models.
That
requires
a
level
of
understanding
that
we
didn't
want
to
be
a
requirement
for
working
on
backdrop
and
so
we're
sitting.
Rather
than
trying
to
choose
the
latest
and
greatest
design
patterns.
A
We
want
to
choose
code
that
most
people
can
understand
so,
whether
you're
a
developer
or
not,
we
want
you
to
be
able
to
open
a
file
Ritu
top
to
bottom
I,
get
a
general
idea
of
what,
and
so
that
means
the
way
the
car
code
is
written,
is
going
to
be
slightly
different
than
the
Whydah.
It
relates
go
to
Canada.
D
A
A
D
D
So
backed
up
performance
is
extremely
important
for
us,
because
we're
targeting
like
lower
budget
sites
like
that
means
lower
infrastructure
costs,
are
also
really
important
to
us.
We
do
have
every
time
we
make
some
decisions
around
performance
where
we're
trying
to
use
shared
hosting
actually
as
a
benchmark
like
is
this
acceptable
on
shared
hosting
and
that
some
of
our
optimizations
in
fact
are
targeted
specifically
towards
shared
hosting
saying,
like
you
shouldn't,
we
shouldn't
be
working
with
the
expectation.
A
D
Releasing
on
time
so
again
like
heavily
dependent
or
based
upon
the
history
of
Drupal,
at
the
time
where
Drupal
8
was
in
development
for
almost
a
decade
like
I
mean
it
was
a
a
long
time
like
almost
half
of
em
is
a
decade
exaggeration
but
like
it
was
like
seven
or
eight
years,
like
literally
half
the
existence
of
the
entire
project,
to
spend
up
one
release.
So
Drupal
7
had
this
like
giant
long
lifetime
compared
to
all
of
the
previous
versions
of
Drupal,
and
nobody
had
any
idea.
D
When
triple-a
was
going
to
come
out,
it's
like
the
constant
refrain
was
like
when
his
dude
come
out
yeah
when
it's
ready,
and
so
nobody
really
knew,
and
that
was
always
the
policy
for
drupal's
up
until
until
until
the
present
and
so
playing
and
scheduling
the
releases
was
really
important
to
us
to
say
you
know,
people
need
predictability.
They
need
to
schedule
things.
We
need
to
make
that
available.
D
Unless
laid
freedom
we're
in
both
free
and
open-source.
Like
some
of
these
things,
we
definitely
share
the
heritage
of
Drupal.
That
purple
is
GPL
software
and
we
inherited
that
with
pride,
saying
we
really
love
and
support
the
open-source
community,
and
we
really
want
to
make
sure
that
what
we
have
created
is
accessible
and
free
and
open
to
everyone.
Weirdly.
D
We
actually
there
actually
is
a
backdrop
for
it,
but
it's
like
the
press
flow
of
backdrop.
It's
called
silkscreen,
and
so
it's
like
the
high
performance
high-end,
scalability,
scalable
version
of
backdrop
similar
to
press
flow.
So
all
of
this
we
still
into
the
backdrop
mission,
which
is
bankruptcy.
Mess
enables
people
to
build
highly
customized
websites
affordably
through
collaboration
and
open
source
software.
Is
there
another
now
say
times,
but
so
some
keywords
just
to
really
go
through
I
know
it's
it's
a
little
cliche,
but
missions
are
really
important.
Philosophy
is
really
important.
D
D
We
want
to
be
able
to
take
to
anybody
that
is
just
out
there
any
person
today
we
want
to
enable
them
to
build
something
and
what
we're
having
the
bill
is
highly
customized,
so
flexible,
like
not
wordpress,
it's
more
structured,
more
flexible
than
that
and
websites
like
we
are
really
focused
on
web
sites.
Not
systems
or
API
is
classification,
those
applications
or
anything.
These
things
we're
really
focused
on
websites
having
all
those
things
are
all
like.
You
know
frosting
on
the
cake,
but
what
backdrop
does
is
it
builds
the
website?
D
It
doesn't
build
a
mobile
application
or
authentication
system,
and
you
can
do
all
of
these
things.
That's
all
peripheral.
What
we're
doing
is
building
websites
affordably,
lowering
the
cost
like
if
you're
using
the
system,
that's
not
saving
you
time
and
saving
you
money.
You
should
be
used
again,
so
affordability
is
one
of
the
most
important
things
in
our
entire
process,
in
collaboration,
the
way
that
we
build
and
construct
the
software
together
and
then
open
source.
A
So
the
first
thing
here
is
to
increase
the
box
functionality.
More.
You
can
do
without
needing
to
install
modules
with
your
custom.
Mark
is
better.
The
second
one
is
making
it
more
intuitive
and
usable.
The
last
time
you
spend
searching
documentation
and
reading
and
poking
in
the
wrong
place
to
find
something.
The
last
time
years,
I'm
working
on
projects
experience
better.
A
D
D
A
C
D
C
A
D
The
paradigm
that
we
have
is
that
you
know
the
head
branch
or
the
one
other
experience
or
back
dog
should
always
be
shippable,
and
so
every
like
there's,
never
there's
sometimes
there's
some
things
that
we
like
commit
and
then
iterate
and
that's
considered
completely
acceptable.
But
at
any
time,
if
the
next
version
of
backdrop
had
to
come
on
tomorrow,
it
could,
and
so
there's
never
the
like
we'll
have
this
stuff
be
broken
for
a
little
while
and
then
fix
it
before
they.
C
A
C
A
There's
a
green
check
box.
That
means
we
have
an
impact
drop,
can
trip,
there's
two
other
things,
there's
that
little
cog
village
make
sure
you're
working
on
it.
So
those
are
also
red
and
green
to
say,
like
freedom
working
on
a
country
from
working
on
in
court
and
then
there's
two
x's
the
flat
one
means
you
don't
need
this
anymore
in
backdrop,
usually
because
they
have
something
in
court
and
they
just
haven't
started
working
on
it.
A
A
B
A
D
So
security
is
always
a
concern
that
we
have
every
single
time.
We
have
one
of
these
presentations
and
we
want
to
make
you
guys
feel
a
little
bit
more
scare
that,
on
the
backdrop,
community
has
representatives
on
the
Drupal
security
team
all
the
time,
so
we're
tightly
coordinated
with
them.
When
a
security
release
comes
out
for
Drupal,
we
know
about
it
beforehand.
Hopefully,.
A
A
B
A
A
A
D
D
A
A
And
pertwee
user
groups
our
first
Tuesday
of
every
month.
So
do
you
wanna
talk
about
something
specific,
that's
a
good
place
to
do
it,
and
then
we
are
also
starting
local
meetups
in
Bay,
Area
and
there's
some
other
places.
Twin
Cities
stuff
is
happening
so
we're
starting
to
get
enough
people
in
individual
locations
than
needing
outcome.
Persons
making
sense
so.
D
C
D
So,
every
every
two
weeks
autumn
or
alternating
meetings,
outreach,
I'll
sound
like
so.
We
have
design
on
where
the
noon
meeting
the
one
o'clock
meetings
always
death,
but
the
new
meeting
alternates
between
designing
UX
and
outreach
and
the
outreach
meeting
fortunately
still
mostly
does
and
we're
just
like.
How
do
we
do
this?
D
And
so
so
we
various
things
that
come
up
like
you
know,
attending
different
conferences
with
more
varieties.
You
know
going
at
to
general
web
conferences
instead
of
Drupal
once
basically
getting
listed
and
other
you
know
other
systems
that
are
outside
the
Drupal
sphere,
especially
like
this
really,
where
heavy
phone
cases
Benetton
on
Drupal,
community
and
developers.
A
C
Right,
that's
not
the
learning
curve
that
you
see
yeah
the
direction
that
they
were
taking.
It's
not
migrating
for
going
to
solve
for
the
dependent
out
there,
but
at
the
same
time,
I
also
hear
from
the
community
that
is
hard
to
find
driven
dollars.
So,
in
fact,
drop
is
to
police
yeah.
It's
certified
to
technological
developers
and
the
rest
of
the
community
is
now
learning.
D
D
A
A
A
D
You're
right
that
we
absolutely
need
new
blood
in
development
and
in
the
Drupal
world
sure
you
may
be
notice
over
the
last
decade.
We're
getting
older,
and
the
number
of
new
people
that
were
getting
in
Drupal
is
not
really
growing,
like
as
I
think.
The
people
that
we
get
are
usually
the
ones
that
have
to
learn
as
I.
Don't
assess
you
for
their
job
right
and
we're
hoping
that
we
can
become
again
a
platform
that
a
hobbyist
would
pick
up
as
like.
Oh
I
could
look
at
it
right
away
and
go
I
can
do
this.
D
A
I
think
that
started
like
slightly
too
abstract
for
people
I
thought
when,
when
I
was
doing
training
in
Drupal
6,
there
was
more
like
show
me
how
to
do
it
and
then
oh
I
can
do
it
for
a
drupal,
sometimes
like
there's
so
much
stuff,
I,
don't
understand,
and
so
we're
trying
to.
Hopefully
get
back
to
that
experience
of
like
we'll
show
you
the
once
and
hopefully
you'll
be
like
I
can
do
anything
and
that
will
also
appeal
to
people.
B
A
D
Write
my
sequel,
specific
queries
and
that's
totally
fine
DB
query
is
completely
okay
again,
like
using
the
abstraction
layer
is
optional
like
if
you,
if
you're
more
comfortable
with
it,
but
but
that's
like
one
less
drupal
ism
that
you
need
to
definitively
learn
in
order
to
in
order
to
write
a
module.
But
the
biggest
one
I've
had
is
standardized
tooling,
that
using
github
as
our
community.
Oh
like
just
lowered
the
threshold
of
the
people
that
can
contribute
dramatically
yeah
because
they
don't
even
need
a
backdrop.
D
D
A
A
B
C
D
A
A
C
D
D
And
so
they
can
also
because
the
the
capacity
and
the
number
of
contributors
is
easy
normos,
and
what
we
found
is
that
by
focusing
we
can
do
a
lot
more,
at
least
in
one
direction
with
less,
but
we
probably
will
never
have
the
same
breath
as
Drupal
development
capacity,
but
it
by
doing
focus.
We
can
go
further
in
one
direction.
D
A
D
Small
small
teams,
but
still
have
a
need
for
structured
content
that
seems
to
be
about
our
sweet
spot
where
site,
building
tools
and
WordPress
are
highly
unstructured.
Big
blog
posts
and
backup
akin
to
Drupal.
Like
its
primary
thing
is
you
can
really
structure
things
you
can
make
complex
relationships
and
backup
excels
at
that
as
well,
but
then
meeting
that
more
complexity
requirements,
but
with
a
solid
team
manage
it.
That's
where
we
are.