►
From YouTube: Why fork Drupal? The philosophy behind Backdrop CMS
Description
jenlampton / quicksketch
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.
https://2018.badcamp.org/session/why-fork-drupal-philosophy-behind-backdrop-cms-0
A
Okay,
so
thank
you
for
skipping
the
party
again
natan
I'm
here
today
to
talk
to
you
about
the
philosophy
behind
backdrop
CMS.
So
this
just
answers
the
question
why
we
decided
to
fork
Drupal,
it's
a
crazy
harebrained
idea,
but
we
didn't
do
it
lightly.
We
have
another
session
the
end
of
the
day
today,
we'll
do
a
live
demo
of
the
software.
So
if
you
haven't
seen
it
recently,
there's
a
lot
of
fantastic
movie.
Church
they'd
like
to
show
off
so
hopefully
by
the
end
of
this
session,
you'll
be
so
convinced.
A
So
we
have
a
very
specific
stated
target
market,
which
is
something
that
we
wanted
to
start
off
with
a
very
beginning,
when
we
first
started
working
on
backdrop,
backdrop
is
a
fork
of
Drupal.
Does
everybody
here
know
what
a
fork
is
already
yeah,
so
we
basically
took
your
bowl
stole.
It
changed
its
name
and
released
it
as
something
else.
It's
not.
B
A
A
Interval
we
do
that
Drupal
and
gerbil
became
sort
of
the
hammer
and
every
meeting
I
wanted
to
became
a
nail,
and
that
made
sense
back
then,
because
there
weren't
a
lot
of
other
tools
out
there.
That
was
before
we
had
WordPress.
It
was
before
we
had
Squarespace
and
once
you're
over
the
drupal
learning
curve,
especially
if
you
really
love
drupal.
You
like
working
that
way.
So
back
then,
ten
years
or
so
ago,
every
time
a
friend
came
to
me
and
said
minion
the
website
I
wanted
to
build
the
metropolis
today.
A
I
would
not
recommend
that
approach
even
with
backdrop,
do
not
give
all
your
pens
back
our
website.
A
lot
of
my
friends
come
to
me
and
they
say
native
website
and
I'm
like
hey,
have
you
heard
of
Squarespace
there's
this
thing
that
you
can
use
yourself
to
build
your
own
site
or
if
they
need
something
a
little
more
functionality.
You
can
say:
oh,
you
can
get
a
free
site
on
wordpress.com
and
if
you
need
to
host
your
own,
so
you
can
try.
A
You
know
to
take
your
own
hosted,
WordPress
version
and
only
when
they
start
to
need
something.
A
little
bit
more
customized
or
a
little
bit
more
complicated,
do
I
talk
to
them
more
about
whether
something
like
dr.
Richard
hole
would
be
a
good
fit
for
them
and
we're
hoping
that
backdrop
will
just
be
another
tool
in
the
toolbox
of
today's
web
developer,
where
you
can
evaluate
every
project
and
see
what
might
be
the
best
solution.
B
B
We've
got
a
long
history
with
with
Drupal
between
a
large
number
of
sites,
some
of
the
sites
that
we
built
out
do
it
was
thank
you,
okay
and,
and
we've
done
a
ton
of
training
that
I
was
originally
one
of
the
wall
about
trainers
that
did
in-person
trainings
back
when
we
were
the
only
in-person
training
company
that
did
Drupal
and
we
traveled
around
the
world
doing
training.
We
wrote
a
book.
Let's
see,
Jen
was
was.
B
So
we
also
have
a
pretty
good
history
in
Drupal,
core
I
wrote
the
original
Ajax
framework
I
still
liked
one
of
the
mechanics
or
file
and
image
modules
and
triple
core
for
triple
seven
and
I
wrote
the
dialogue
system.
That's
in
Drupal
8
today,
as
well
as
the
ckeditor
module,
that's
the
primary
proponent
for
putting
into
Drupal
8
and.
A
A
little
bit
newer
to
core
development,
I
didn't
get
involved
until
after
triple
7
came
out
and
I
thought
that
it
was
a
yeah,
less
usable
product
in
Drupal
6,
so
I
got
involved
in
the
usability
team.
I
started
working
on
seeing
the
kinds
of
problems
both
sighted
and
unsighted
people
experienced
with
Drupal
7,
created
a
magician's
to
work
on
that
and
then
based
mostly
on
my
experience
in
training.
I
realized
that
the
theme
layer
was
too
hard
for
new
people
to
learn
and
most
people
come
into.
A
Troopa
were
coming
with
an
experience
of
HTML
and
CSS
is
sort
of
the
lowest
common
denominator.
We
used
to
make
that
better,
so
I
accidentally
became
the
unofficial,
twig
initiative.
Leaper
Drupal,
8
and
I
did
that
for
a
couple
of
years,
wrangling
a
bunch
of
core
developers
to
get
Twigg
as
the
new
front-end.
So
we
have
a
lot
of
experience
not
only
in
building
websites
and
seeing
with
any
talking
to
people
and
saying
what
they
needed,
but
also
seeing
how
decisions
are
made
and
changes
are
made
in
the
software
itself
and
then
I
think.
A
Most
importantly,
Nate
and
I
are
huge.
Advocates
of
the
Drupal
community
long
before
I
ever
gave
a
talk
or
wrote.
A
line
of
code
for
Drupal
I
was
here
at
camp
running
a
registration
desk
and
getting
to
talk
to
people
at
camps
and
conferences
everywhere,
as
I
think.
The
most
exciting
part
for
us
I
mean
Tribble,
is
the
kind
of
thing
we
met
at
a
triple
camp.
We're
not
married
it's
the
kind
of
thing
that
changes
your
life.
If
you
have
passionate
about
it,
you
believe
in
what
it
does.
B
B
So
how
are
we
gonna
run
this
thing?
It
was
not
a
year
and
a
half
into
the
existence
of
backdrop
that
we
started
forming
some
ideas
about
how
we
were
going
to
run
the
project,
and
we
adopted
this
model
called
the
project
management
committee
model
or
the
PMC
module,
which
is
proven
successful
by
the
Apache
community
and
they
actually
enforce
it
for
every
single
one
of
the
Apache
projects
under
the
umbrella
of
the
Apache
namespace.
Not
just
the
web
server,
but
also
Cordova
Cassandra,
we've
seen
OpenOffice
all
of
the
projects
under
the
Apache
umbrella.
B
All
have
this
model
of
leadership
called
the
PMC
and
the
PMC
is
made
up
of
a
collection
of
people,
essentially
the
make
decisions
democratically
anything
that
needs
a
decision.
Then
we
put
it
to
a
vote
and
then
we
make
up
the
PMC
out
of
what
it
should
be:
a
diverse
collection
of
people
to
bring
different
perspectives
to
all
of
the
decisions
that
need
to
be
made.
So.
A
Right
now
we
have
a
bunch
of
the
people.
There's
a
lot
of
these
phases.
You'll
see
here
today.
Everyone
except
our
thuggery
who's
in
Australia,
it's
a
bit
of
a
hard
flight
and
everybody
is
supposed
to
be
representing
a
particular
constituent
of
backdrop.
Users.
So
nate
is
a
cork
emitter.
Mike
McCaffrey
works,
mostly
with
I,
contributed
modules
and
api's.
Jocko
Ponte
is
working
on
selling
backdrop
to
our
intended
market
so
that,
if
we
make
any
changes
that
we
make
backed
up
hard
to
sell,
we
better
check
on
that
I'm
particularly
focused
on
the
user
experience.
A
So
anything
I
think
will
improve
the
product
type
feel
of
backdrop,
as
opposed
to
a
framework
I'm
going
to
be
pushing
West
River
cobbler
move
acaba
rootball
cob
off
I
get.
It
eventually
is
a
friend
under
heated,
a
training
hearing
a
couple
days.
If
any
of
you
attended
that,
and
he
is
there
to
make
sure
that
we're
not
doing
anything
too
crazy
to
the
front
end
in
Gregory,
Dean
Estes
is
a
site
builder,
he's
a
architect
who
built
a
ton
of
sites
without
writing
any
code.
A
So
we
want
to
make
sure
he
has
all
the
tools
that
he
needs
to
in
order
to
date
do
his
job
at
the
end
of
the
day.
So
these
people
are
all
representing
right
now,
constituents
of
what
they
do
with
fact
drop,
but
we
also
want
to
make
sure
they
represent
other
constituents
like
race,
gender,
geographic
region,
languages
spoken
anything
we
think
we
want
to
have
represented
in
our
community.
We
want
to
see
represented
in
our
management.
So
if
we
get
a
huge
number
of
people
are
adopting
backdrop
in
Ukraine
or
Latin
America.
A
We
want
to
make
sure
there's
spaces
for
that
on
the
PNC
to
make
sure
that
the
needs
of
those
communities
are
met
as
well.
So
we're
gonna
try
and
make
sure
that
the
decisions
driven
four-vector
aren't
coming
from
a
single
person
or
a
single
type
of
people
that
are
active
accurately
representing
the
community
as
a
whole.
B
A
That's
really
important,
because
if
we
get
to
a
point
where
we
have
a
decision
that
needs
to
be
made-
and
everybody
agrees
like
quickly-
we
need
to
do
this
thing
to
backtrack
and
we
look
at
the
philosophy
anyway.
Well,
it
doesn't
line
up
with
the
philosophy.
If
the
project
management
committee
agrees,
it
needs
to
be
done,
then
that
means
the
philosophy
needs
to
be
modified.
So
what
we
would
do
is
first
change
the
philosophies.
A
So
the
pmc
is
supposed
to
take
their
own
experience
and
their
own
perspective
and
try
and
look
at
any
given
issue
and
decide
what
is
best
for
the
project,
not
what
is
best
for
them.
So
it's
a
little
bit
different
than
how
it
works,
where
everybody
thinks
their
own
experience,
their
own
desires
and
says
I
want
to
ask-
and
nobody
ever
says,
is
this:
what's
best
for
Drupal
we're
in
backdrop,
it's
the
other
way
around
where
it
doesn't
matter
what
you
want
you're
supposed
to
say.
A
Do
you
think
this
is
what's
best
for
backdrop,
and
so
that
should
be
based
on
your
experience
and
representing
your
constituent
as
a
whole.
So
again
you
have
to
take
what
are
the
options
available?
Look
at
the
project
philosophy
and
say:
do
you
think
this
lines
up
and
we're
hoping
that
the
different
people
and
the
different
experiences
will
have
different
perspectives
on
that,
so
we'll
be
able
to
have
a
conversation.
But
again
it's
about
looking
at
the
options
proposed
and
saying.
Is
this
what's
right
for
backdrop
yeah.
B
How
does
this
align
with
our
project
philosophy
in
Drupal,
because
that's
not
the
way
Drupal
works
Drupal
is
everybody
gets
to
bring
their
own
idea
of
what
they
want
and
then,
if
they
work
hard
enough
and
put
enough
fun,
then
it
can
get
in
the
Duan
Chrissie
kind
of
model
of
development,
but
by
defining
the
philosophy
it
makes
it
so
that
we
can
make
decisions
that
are
cohesive
ones
that
are
like
we're
bringing
our
experiences
together.
But
then
we're
saying
how
can
we
do
what's
best
for
the
project?
B
A
First,
one
is
easier
updates
and
this
obviously
came
from
the
experience
of
people
trying
to
get
from
Drupal
7
to
Drupal.
8
I
also
personally
experienced
a
lot
of
pain,
getting
a
lot
of
my
clients
from
6
to
7.
It
was
a
bumpy
transition
for
a
lot
of
them
where
it
was
pushing
their
budgets
and
they
didn't
necessarily
see
a
benefit
to
doing
it.
That's
the
kind
of
thing
we
want
a
mitigating
factor
up.
We
want
to
make
it
so
that
everybody
can
stay
up
to
date
without
a
huge
burden
on
developers
or
site
owners.
A
The
next
one
is
simplicity.
This
is
rather
than
following,
like
the
latest
and
greatest
exciting
design
patterns.
We
want
to
write
code
that
will
apply
to
the
majority
of
people,
and
this
is
not
necessarily
developers,
but
just
people
are
going
to
be
opening
this
offer.
For
the
first
time,
we
want
more
people
to
be
able
to
contribute
in
order
to
do
that.
The
code
has
to
be
easier
to
understand.
It's
simpler.
To
follow.
A
Focus
is
to
make
sure
that
the
features
that
are
in
core
are
going
to
benefit
the
majority
of
people
using
it.
So
if
we
look
at
what's
in
core-
currently
we
can
say:
ok,
there's
some
stuff
in
here-
that
it
benefits
less
than
1%
of
the
community
and
it's
making
it
really
hard
for
the
rest
of
the
community
to
write
sequel
queries
or
translate
things
or
whatever
it
happens.
To
be
and
we'll
pull.
C
A
And
so
that
that's
that
should
be
a
concern.
Well,
that's
something!
It
doesn't
belong
in
quark,
and
then
we
look
at
a
list
of
things
that
are
are
slated
for
core
who
say:
is
this
going
to
benefit
most
people
or
is
only
in
a
benefit
that
1%
of
people
and
if
it
doesn't
benefit
most
people
that
it's
going
to
stay
in
control?
A
It's
not
gonna,
go
in
Corso
it'll
help
us
keep
our
focus
really
narrow
on
the
things
we
think
are
most
important
to
most
people
and
that
we'll
be
able
to
we'll
be
able
to
iterate
and
improve
faster
with
less
code.
More
important
code.
Extensibility
is
also
super.
Important
Drupal
is
great,
but
it
wouldn't
be
as
powerful
as
it
is
today,
without
the
massive
number
of
contributed
modules
and
themes
and
other
things
that
you
can
plug
into
it.
A
A
This
also
came
from
Drupal
when
it
was
triple
sec,
so
you
could
put
it
on
shared
hosting
and
get
a
get
way
way
with
that
in
Drupal
7,
you
start
people
seeing
reaching
the
limits
of
what
their
hosting
providers
could
deliver
her
a
Drupal
site,
and
you
saw
the
emergence
of
triple
specific
hosting
providers
like
Pantheon
aqua,
Lea
platform,
black
mesh.
All
of
these
companies
emerged
specifically
to
meet
this
need.
Me
was
a
performance
engineer
for
Lullaby
and
he
used
to
hate
the
fact
that
that
job
was
even
necessary.
A
He's
like
why
don't
we
write
code
that
requires
this
special
specialized
knowledge
to
make
it
go
fast
enough?
So
that's
a
personal
issue
for
him.
It's
personal,
too,
you
can
make,
as
most
of
my
clients
were
those
that
were
on
shared
hosting,
so
we're
gonna
try
to
make
sure
that
backdrop
requires
less.
A
Less
memory
it
forms
faster
without
assuming
a
complicated
infrastructure
behind
it
and
releasing
on
time
is
also
something
that
is
super
important.
It's
really
hard
for
companies
to
figure
out
when
they
have
to
budget
time
for
an
upgrade.
If
there's
no
date
when
that
needs
to
happen,
it's
hard
to
for
developers
to
figure
out
when
they
need
to
set
aside
time
to
work
on
updating
those
projects
or,
if
you're,
a
core
developer
contributing
to
core.
A
Unless
you
don't
win
happen,
and
so,
if
we
can
have
on-time
releases
that
are
planned
and
scheduled,
and
everything
continues
to
roll
at
clockwork,
it
could
be
much
easier
for
the
whole
community
to
keep
up
with
the
project
and
last
one
is
freedom,
obviously
we're
here,
because
we
were
able
to
pork
Drupal
having
open
source
software.
That
is
amazing
and
gives
you
the
ability
to
take
it
and
do
what
you
want
with
it.
It
is
super
important
to
us,
so
we're
gonna
retain
that
free,
open
source
mentality,
going
forward.
A
B
Like
down
here
at
the
bottom,
we
go
there.
It
goes
into
all
of
this
and
even
more
depth
than
what
what
Jen
is
just
covered.
So
so,
if
we
take
all
these
principles
and
distill
them
together,
then
we
arrive
at
the
backdrop
mission
statement,
which
is
backdrops.
Ems
enables
people
to
build
highly
customized
websites
affordably
through
collaboration
and
open
source
software,
and
although
it's
a
loyalty
is
to
go
through
all
of
these
words,
they
have
meaning
people.
B
Our
audience
is
not
necessarily
developers
we're,
not
a
framework,
we're
actually
trying
to
be
more
product,
centered,
and
so
people
were
aiming
for
a
broad
audience
of
users
that
can
potentially
benefit
from
backdrop
highly
customized,
because
we're
not
Squarespace
and
we're
not
WordPress
we're
more
customized
than
those
products.
We.
B
A
B
That
we
are
about
websites
like
we're,
not
I
mean
web
systems
and
API
is
and
decoupled
front-ends.
All
of
these
things
are
all
options
with
backdrop
very
much
so
as
as
they
were
with
Drupal
7,
but
our
focus
is
really
on
delivering
a
website.
All
of
those
things
around.
It
are
peripheral
and
so
and
doing
so
affordably-
and
this
is
one
of
our
key
things
about
like
how
can
we
make
it
so
that
we
are
saving
people,
time
and
money?
B
Because
if
your
system
isn't
saving
you
those
things,
then
you
shouldn't
be
using
the
system
in
the
first
place.
It's
the
entire
purpose
of
any
content
management
system
is
to
save
people
time
and
then
collaboration
and
open-source
software
doing
things
we're
better
together
and
we
do
it
with
free
software.
So
let's
look
at
this
affordable
word
and
say:
how
can
we
make
web
development
more
affordable?
B
We
can
increase
the
out
of
box
functionality
more
if
the
software
does
what
you
need
right
out
of
the
box,
then
you're
shortening
the
time,
the
ramp
up
time,
and
also
just
the
general
mentality
of
download
Drupal,
now
download
these
same
15
modules
on
every
single
website
like
it.
It
doesn't
make
a
lot
of
sense,
so
take
those
ones
that
are
standardized
and
include
them
out
of
the
box,
improve
the
user.
Experience
make
it
so
that
people
can
use
the
software
more
easily
with
that
with
maybe
less
need
for
documentation
any
common
WTFs.
B
Is
some
of
our
desire
to
maintain
doctors
compatibility
as
well
that
things
should
be
as
straightforward
as
possible
using
familiar
patterns
as
much
as
possible
and
also
actually
being
consistent
about
it
over
time?
So
if
you
learned
something,
you
know
that
knowledge
should
apply
for
as
long
as
possible.
B
This
one's
kind
of
obvious
decrease
server
resources
that
if
your
software
is
less
expensive
to
host,
that
translates
directly
into
costs.
If
you
need
fewer
web
servers
to
power,
the
same
website,
making
maintenance
faster
and
easier,
whether
that
is
like
applying
or
you
get
a
delay
of
updates
is
several
yeah
okay,
so
you
make
your
kind
of
the
same
thing
so
making
updates
faster
and
easier
or
automatic,
we're
already
working
on
pushing
towards
automatic
updates.
A
Pushing
a
button
just
giving
someone
who's,
maybe
not
great,
at
maintaining
their
site
the
ability
to
push
the
button
when
a
security
update
comes
out,
I
think
is
gonna,
be
huge
for
making
them
say
and
more
I
mean
obviously
we're
coming
from
Drupal
there's
already
a
pain
point
around
the
cost
of
how
much
it
takes
to
have
a
Drupal
website
over
the
long
term,
and
with
this
being
one
of
our
primary
objectives,
it's
making
112
more
affordable.
Every
time
we
come
up
with
a
version
of
backdrop,
we're
gonna
be
like
okay.
A
B
B
B
B
You
which
ones
running
forward
which
ones
you're
not
the
dumpers
lines,
we've
got
30
of
the
top
72
modules
in
court,
30
of
them
that
are
in
contributed
for
them
they're
under
way
and
four
that
are
not
started
and
the
ones
that
are
not
started
are
ones
that
usually
cost
people
some
consternation.
But
it's
a
includes
use
PHP
that
lets
you
put
PHP
code
into
your
view.
Configuration
that's
so
there's
a
reason
why
it's
not
ported
but
I,
don't
even
know
why
that's
one
of
the
top
72
Drupal,
but.
B
A
Collection,
but
we
do
have
paragraphs
and
multi-field,
so
we've
got
two
alternate
solutions
to
that
and
we're
working
on
upgrade
path
from
field
collection
in
Drupal
7
to
paragraphs
in
dr.
and
there's
another
one
media
YouTube
we
don't
have.
We
do
have
YouTube
module
as
an
alternative,
so
there's
not
great
past
remediate
YouTube
to
YouTube.
This
is
stuff
like
that,
where
in
most
cases
we
have
a
comparable
alternative
and
that's
why
this
one
isn't
there.
Yet,
let's.
A
C
A
The
ones
on
the
left
hand
side
were
blue
because
they
were
in
core,
so
you
could
see
like
the
highest
from
most
used
month
of
The
Wiltern
pork.
And
this
way
it
became
more
and
more
green,
because
these
are
the
ones
that
are
in
contribute
or
to
see
our
like
put
more
out-of-the-box
effort
going
into
taking
the
things
that
are
most
important,
making
sure
those
are
available
to
everybody.
B
So
the
ones
that
are
included
in
core
are
listed
here,
some
of
them
with
asterisks
inside
a
direct
port.
But
there's
like
a
corollary
that
is
available
things
like
panels.
We've
got
the
layout
system
that
is
included
ever
since
backdrop
on
point.
No
media
is
not
the
full
media,
but
we're
pulling
in
parts
one
at
a
time.
Superfish
menus.
We
have
something:
that's
better
than
superfish
menus,
I
would
say
called
Smart
menus
that
is
included
out
of
box
yeah,
but
lots
of
modules
that
are
literally
direct
reports
from
the
Drupal
7
versions.
C
A
These
have
enough
food.
So
in
backdrop,
if
you
go
to
our
contribute
on
github,
you
can
see
that
there's
501
projects
in
there
that's
module
themes
and
layouts.
If
you
go
to
the
backdrop
CMS
org
website,
you'll
see,
there's
only
400
and
part
of
that
is
because
we
require
that
there
be
an
official
release
for
a
module
before
it
appears
on
the
website,
and
that
is
also
because
you
can
install
modules
directly
from
within
your
backdrop
site.
A
You
don't
need
to
go
to
backdrop
CMS
at
work,
and
we
wanted
to
make
sure
that
anyone
who
is
pushing
a
button
to
install
a
module
is
going
to
get
something
that's
stable
and
not
going
to
blow
up
their
site.
So
these
numbers
are
a
little
low
compared
to
Drupal
triple-n's,
like
7,000
plus
modules
for
Drupal
7,
but
in
terms
of
the
functionality
that
you're
gonna
get
from
backdrop.
There's
a
lot
there
and
even
better
there's
a
hundred
and
one
that
are
in
the
works.
So
there's
400
they're
out
now,
there's
101
probably
coming
soon.
A
Maybe
all
of
them
are
some
of
them
might
be
abandoned
or
started
and
not
finished.
But
there's
a
ton
of
activity
going
on.
We
get
a
couple
of
new
releases.
Every
week
we
have
weekly
meeting
where
we
talk
about
all
the
new
stuff
that
comes
up
so
we're
seeing
updates
to
existing
projects
and
new
projects
coming
along
for
backdrops,
which
is
really
exciting.
B
A
B
C
B
B
Two
two
releases
that
were
back
dropped
only
security
releases
that
were
separate
from
those
Interpol
and
we've
had
actually
two
drupal
security
releases
that
didn't
require
back
drop
updates.
So
it's
not
always
one
to
one,
but
it's
it's
usually
pretty
close.
Considering
the
amount
of
code
overlap
between
Drupal,
7
and
backdrop
is,
is
substantial,
so
our
own
system,
yeah.
C
B
A
private
security
queue
on
github
and
then
releases
the
mod
on
Wednesdays,
very
similar
to
to
that
of
Drupal
ornated
with
Drupal,
but
in
the
world
at
the
Trib,
so
contribute
is
a
little
more
fluid
because
we
don't
watch
every
security
issue
for
every
possible
contributor.
When
security
announcements
come
out,
Jeff.
B
But
what
we
do
we
work
slightly
differently
from
Drupal
and
that
the
the
backdrop
contribute
is
a
place
where
ownership
is
a
little
less
specified
than
it
is
on
the
yeah
less
rigid
than
it
is
in
the
Drupal
community,
where
there's
a
single
group
on
github,
where
all
contributes
and
as
part
of
the
encrypt
Agreement,
you
say
that
you
will
work
with
the
security
team
or,
if
necessary,
the
security
team
has
the
permission
essentially
to
update
your
module
on
your
behalf
and
then
push
out
a
new
release
to
address
any
security
issues.
There.
A
Are
a
couple
of
issues,
especially
with
Drupal
7,
lately,
a
lot
more
kitchen
products
are
getting
less
and
less
attention,
and
so
it's
becoming
hung
unsupported
and
there's
one
issue
recently
where
they
were
in
64,000
sites
running
a
contributor
release.
They
couldn't
get
in
touch
with
the
maintainer
and
the
project
became
unsupported.
So
now,
there's
a
security
rule
like
notice
out
there
telling
you
your
modules,
unsecured,
but
the
modules
don't
supported,
and
it's
not
going
to
get
one
enough.
Sixty-Four
thousand
sites
are
vulnerable
without
any
path
forward.
A
We
wanted
to
prevent
something
like
that
from
happening
in
backdrop,
because
we
don't
want
to
rely
on
that
one
person
to
be
able
to
make
a
change
to
that
project
to
fix
it
out.
So
in
impact
you
just
say
you
know
you
have.
The
security
team
has
commit
access
to
all
projects
and
that
way,
if
we
have
that
situation,
where
there's
a
lot
of
people
who
are
depending
on
a
particular
project,
we
can
fix
it,
we're
going
to
push
out
a
fix
and
keep
our
community
protected.
A
C
A
Continue
working
on
it
or
whatever
their
story
is.
We
also
have
a
pretty
good
process
for
handing
projects
over
from
one
maintain
her
to
another.
So
if
someone
was
using
it
for
six
months
and
then
they
stopped
and
someone
else
starts
using
it,
it's
two
weeks
of
inactivity
and
that
can
get
transferred
over
so
we've
had
a
ton
of
pincher
projects
get
started
and
then
handed
off
pretty
quickly
from
one
person
to
another.
So
it's
been
a
lot
more
collaborative
than
I
found
interval.
Just
because
setting
up
at
the
beginning
saying
you.
A
All
right,
so,
let's
talk
a
little
bit
about
the
backdrop.
Community
here
are
a
couple
numbers.
These
are
updated.
Recently
we
have
a
little
over
10,000
downloads
of
backdrop.
We
have
a
little
bit
more
than
1,600
members
on
backed
web
CMS
org,
so
those
are
generally
people
who
are
showing
some
sort
of
interest
lypa
backdrop
sites
just
over
650.
We
have
about
86
people
who
have
contributed
a
backdrop
core.
A
We
have
77
people
who
are
currently
maintaining
in
trim
projects,
so
what
I
think
is
really
interesting
about
that
is
that
we
have
more
core
contributors
than
we
have
contribute,
a
neurs
which
is
the
opposite
of
what
you
see
in
Drupal
and
I.
Think
part
of
that
is
just
because
number
one
factor
is
on
github,
which
is
something
that
a
lot
of
people
are
already
familiar
with
and
number
two.
A
C
A
A
A
A
But
that
a
lot
of
them
are
big
Drupal
shops
and
they've.
Looked
it
back
up
and
said
our
team
already
has
the
skill
toured
in
order
to
take
on
backdrop,
work
so
they're
listing
ourselves
as
seeking
with
those
projects
which
is
pretty
exciting
all
right.
If
you
would
like
to
find
some
members
of
the
backup
community?
Obviously
we
have
our
github
group,
where
we
do
most
of
our
code
and
issues,
which
is
backdrop
slash
backdrop.
We
have
a
git
er
live
chat
channel.
A
A
So
if
you
do
not
have
a
github
account
and
still
want
to
ask
questions,
there's
a
safe
place
for
you
to
do
that,
and
they
have
a
bunch
of
members
of
our
community
who
love
answering
questions
in
the
forum,
so
they
watch
all
the
time
and
they
try
and
be
as
helpful
and
friendly
as
possible,
which
is
great.
We
have
our
website
backed
up
CMS
org,
which
is
full
of
documentation
and
resources.
A
There's
things
like
you
can
find
books
on
backdrop
listed
there
that
sort
of
thing
we
have
our
Twitter
account
back
at
backdrop,
CMS,
where
we
post
sometimes
useful,
sometimes
not
so
useful
information,
but
it
could
be
fun
to
follow
and
we
have
meetings
once
a
week,
every
Thursday
at
1
p.m.
we
have
a
check-in
to
talk
about
what
we're
working
on
for
the
next
version
of
FAQ
Drive.
We
also
have
some
other
meetings
that
happen
right
before
that
one.
We
have
a
design
focused
meeting.
A
So
if
you're
particularly
interested
in
designer
usability,
we
have
a
focus
on
those
issues
and
then
the
following
week
we
have
a
meeting
on
community
outreach,
trying
to
figure
out
how
we're
going
to
spread
the
word
about
backdrop
at
the
end
of
every
meeting,
there's
an
open
Q&A.
So
if
you
don't
care
about
what
working
on
core
design,
usability
or
outreach,
you
just
have
a
question.
You're
also
welcome
to
join
in
and
say,
hey
guys,
my
dog
colonias
dinner,
and
we
should
talk
about
things.
We've.
A
Question
is,
you
may
have
preferably
focused
on
doctor
your
dog's
name,
backdrop,
maybe
that
counts,
so
that's
that
also
exciting
new
things
going
on
in
backdrop.
Obviously
you
guys
are
here.
This
is
a
Drupal
event,
so
you
can
find
back
up
a
Drupal
camps.
Bad
camp
in
particular,
has
sort
of
been
the
place
where
we've
been
most
active
as
our
own
sort
of
thing.
A
We
usually
have
a
summit
and
a
training
in
addition
to
sessions
like
this
one,
but
we
are
also
giving
talks
and
presentations
at
other
various
open
source,
nonprofit
tech
conferences
around
the
country
and
hopefully
in
Mexico
next
year
we
will
see
how
that
goes,
and
we
are
also
going
to
start
having
some
sort
of
casual
get-together
where
people
can
chat
about
backdrop.
The
first
one
is
scheduled
for
January
15th,
which
is
backdrops
birthday
and
so
happens
to
be
Julis
birthday.
A
So
we
are
going
to
celebrate
both
backdrop
and
Drupal's
birthday
on
January,
15th,
location,
TBD,
but
check
the
website
and
there's
gonna
be
a
bunch
of
parties.
At
the
same
time,
in
various
places
around
the
world,
we're
gonna
have
one
in
Las
Vegas
and
one
in
twin
cities
and
one
here
in
the
Bay
Area.
So
if
you
just
want
to
get
together
and
there
will
probably
be
live
demos
of
stuff
going
on
about
trapping
people,
you
know
having
birthday
cake,
her
vegan
birthday,
cake,
I,
don't
know
whatever
it
is.
A
C
A
C
A
B
C
C
B
I
come
to
this
same
room
here
at
2:30
today,
and
we're
going
to
be
spending
the
whole
session
going
through
a
hands-on
presentation
of
using
the
backdrop
and
putting
in
action
we're
really
in
a
hurry,
though
you
can
go
to
backdrop,
CMS
org
and
click.
The
try
demo
button
and
they'll
spend
up
a
Pantheon
instance.
Actually.
C
B
C
C
A
The
thing
for
me
is
easier
updates.
That
was
something
that
I
ran
into
as
a
the
person
who's
responsible
for
maintaining
my
client
sites
and
when
I
ran
into
that
issue
on
drupal.org,
where
the
module
was
just
marked
as
unsupported
and
then
I
went
to
the
issue
queue
and
was
like
I'd
be
willing
to
take
over
the
maintenance
in
lobs
just
for
the
18
sites
that
I
have
to
maintain
than
or
running
it,
and
I
saw
that
there
was
another
person
other.
A
He
would
also
offer
to
maintain
the
module
and
Drupal
security
staff
was
like
no,
it's
fine,
they
are
gonna,
do
different
module
and
Tripoli
anyway,
and
I
was
like
whoa
doesn't
help
me
today.
I
want
I
want.
There
needs
to
be
some
process.
That's
gonna
make
it
easier
for
people
to
maintain
sites
going
forward
like,
even
if
there's
a
security
issue
there,
either
than.
A
Great
pass
something
because
a
lot
of
times,
people
you
know,
invest
all
their
money
in
building
their
website
and
they
might
have
a
little
bit
of
budget
for
maintenance,
but
they're
not
planning
on
like
migrating
from
one
contribs
solution
to
another
at
some
random
point
in
time,
when
a
security
issue
may
or
may
not
come
out.
So
for
me,
it
was
really
under
the
making
it
easier
to
update
your
cycling
forward,
making
sure
there's
always
a
path
forward
for
everyone.
A
We've
also
started
to
include
that
in
all
of
the
Kindred
projects
we
put
into
core
we've
made
sure
there's
an
upgrade
path
from
the
contribs
solution
to
the
core
path,
which
is
different
in
Drupal,
7,
CC,
k1
and
but
they
couldn't
upgrade,
have
remained
in
come
true.
We
sort
of
flip
that
around
and
said
no
it's
court
burden
to
make
sure
there's
an
upgrade
path
there.
A
A
A
Community
vision,
mostly
about
code
and
product,
it
might
be
good
to
think
about
anyone
specifically
focused
on
community
two,
because
the
way
our
community
focuses
feels
a
little
bit
different
than
how
it
did
interval
just
because
it
tends
to
be
more
welcoming
to
a
beginner
level
developer
and
it's
secure
having
a
security
team
that
has
ability
to
go
in
and
fix.
Stuff
is
also
helpful
there,
because,
if
you
have
something
was
like,
oh
I'm,
not
sure
I
can
maintain
a
project.
Knowing
that
there's
help
like
we're.
Gonna
have
a
security
issue.