►
From YouTube: Backdrop Weekly May 25th, 2017
Description
Today’s development agenda: http://bit.ly/2pYZrIw
A
All
right
we're
on
air,
it
is
May
25th,
and
this
is
a
check-in
meeting
for
development
tasks
for
dr.
at
CMS
on
the
agenda
for
today.
First
item
is
updates
from
the
PMC
we're
still
working
with
the
software
freedom,
Conservancy
x'
lawyer,
to
get
our
agreement
ironed
out.
He
did
send
an
email
last
week
to
everyone
on
the
PMC
via
our
shared
email,
address
and
I.
Don't
think
anyone
else
has
written
back,
except
for
myself.
So
if
you've
got
that
email,
please
reply
to
it
just
so
he
knows
you're
alive.
B
Freedom
Conservancy
rules
around
PMC
members
being
in
the
same
company.
What
do
you
mean
at
it?
Where
just
mention
it
that
the
thought
that
software
freedom,
Conservancy
current
rules
regarding
fiscal
sponsorship
include
that
if
a
project
is
PMC
managed
like
ours
is
that
they
don't
allow
multiple
people
from
the
same
company
to
have
multiple
seats
on
the
PMC
and
so
right
now
we
actually
have
an
issue
in
that
Wes
and
I
both
work
for
law,
labott
and
so
according
to
their
standard
rules.
That
would
not
be
allowed.
B
B
But
really
just
prompt
them
to
finally
happen
just
so
that
there's
kind
of
like
multiple
conflicts
going
on
there,
but
nothing
to
worry
about
and
as
as
the
details
of
that,
fully
get
published
and
as
I
write
of
the
next
planation.
Everything
like
that
yeah
it'll
be
fully
explained,
but
it's
really
not
done
anything
to
be
concerned
about,
but
something
that's
gap
will
be
moving
towards
the
next
couple
of
weeks.
D
B
Yeah,
for
the
same,
for
the
same
reasons,
basically
just
like
like
overpowering
the
board
or
stacking
the
sorry
stacking,
the
PMC,
with
a
kind
of
like
already
aligned
interests
as
yeah.
It
can
make
it
so
that
you
can
overpower
the
PMC
one
way
or
the
other,
and
it's
the
same
idea
in
mind,
basically
that
they
want
to
prevent
that
from
happening.
Awesome.
A
So
yeah
we're
working
on
that
we'll
get
it
figured
out
in
the
next
few
weeks
and
then
keep
your
eyes
open
for
a
post
I.
Think
it's
going
to
be
in
the
github
issue:
queue
where
the
lawyer
and
the
books
from
supper
Conservancy
will
be
trying
to
reach
out
to
the
larger
development
community.
For
backdrop
to
make
sure
everybody
knows
we're
working
on
this
and
everybody's
in
agreement.
This
is
that
they
want
so
it'll,
probably
be
in
our
primary
github
issue.
A
A
Okay,
so
other
things
we've
been
working
on.
We
had
a
design
meeting
about
an
hour
ago
that
Wes
joined
in,
and
he
showed
us
some
of
the
work
he's
been
doing
on
for
doing
on
the
new
homepage
for
backup
CMS
to
org.
He
hasn't
had
a
lot
of
time
recently,
but
he's
going
to
be
working
on
that
in
the
next
week
and
hopefully
we'll
have
an
update
for
us
by
next
weekly
meeting,
which
should
be
exciting
backdrop,
CMS,
neat
and
turn
it
over
to
you.
Yeah.
C
Well,
we
do
that
before
we
go,
there
can
I
just
say
something:
Jaya
I
wanted
to
do
that
when
the
video
stream
started
buzz,
yeah,
here's
the
chance
last
week
when
we
had
the
release
it
went
so
many
people
like
on
the
on
the
course
I
wanted.
A
BPA
1:5
was
released,
yay
3.77,
yes,
sorry
but
yeah!
Well,
that's
just
that
I
said.
Oh.
E
B
Ya,
so
1.7
came
out
and
actually
related
that
marketing-wise
well
and
everything.
So
the
way
we
normally
handle
releases
is
that,
after
two
weeks
we
release
a
bug-fix
update,
so
1.71
and
the
status
of
1.71
is
at
least
according
to.
What's
in
our
issue,
tracker
I
mean
there
are
good
I,
don't
know
like
20
issues
or
so
in
there,
but
none
of
them
are
like
really
substantially
like
critical
and.
B
They
were
all
pre-existing
issues
that
that
we're
just
hoping
to
get
handled
as
soon
as
possible,
and
so
nonetheless,
that
would
probably
make
1.71
anyway,
just
because
this
is
what
we've
done
every
release
prior
is
after
two
weeks
we
make
a
bug-fix
release
and
at
the
same
time,
we
update
Pantheon
the
Pantheon
upstream
that
are
using
a
backdrop
on
papian
as
well
as
we
send
out
the
newsletter
announcing
the
official
version.
So
I,
don't.
A
Think
we've
ever
done
that
before,
but
I
think
that
we
should
get
in
a
habit
of
doing
that.
Every
time
regard
on
which
part
we
like
it
was
months
before
we
came
out
with
the
first
release
after
1/6
the
bug-fix
release
really
yeah,
and
that's
why
we
have
a
two-week
milestone
for
171
because
we're
like
we
don't
want
that
to
happen
again
because
it
was
like
we
need
to
send
a
newsletter.
But
now
it's
old
news
so
well
it'd
be
good
to
do
it.
My.
A
B
B
B
Okay,
so
1.71
issues
there's
no
items
that
actually
want
to
call
out.
Although
we
can
take
a
look
at
the
issue,
tracker
there's
only
one
issue
in
the
RGB
CQ,
if
there's
many
more
in
the
needs,
review
queue.
So
as
always,
if
we
have
the
capacity
to
do
some
peer
reviewing
and
get
things
moved
from
needs
review
status
into
our
TBC.
That
will
help
speed
things
along
I
guess.
B
B
B
I
would
say,
let's
target
for
the
30th,
but
29th
is
Memorial
Day
in
the
United
States,
it's
a
holiday,
so
it
will
give
us
ample
time
to
do
some
prep
work,
but
a
good.
We
should
do
the
release
actually
on
a
weekday,
so
we
can
follow
that
on
Tuesday
and
then
the
newsletter
will
come
up
the
next
step
to
that.
So,
let's
let's
shoot
for
that
and
then
go
ahead
and
type
that
in
here.
B
Okay,
1.8
do
have
any
other
questions
on
1.7
actually
before
I
move
on
okay,
1.8
1.8
is
the
next
minor
release
of
backup
that
will
be
coming
out.
September
15
2017,
so
we've
got
a
good
four
months
from
now
before
our
next
release.
As
always,
the
code
freeze
will
be
on
future.
Priests
will
be
on
September
1st,
so
we
have
a
nice
glorious
summer
to
make
some
progress
in
the
next
version
of
backdrop
or
well
or.
C
B
You're,
absolutely
right,
ok,
so
items
for
1.8
that
we're
thinking
about
some
items
from
1.7
that
we
had
hoped
to
complete,
but
I
hadn't
include
layout
relationships
which
issue
2130
for
the
status
of
this
is
that
it's
kind
of
in
a
proof
of
concept
state,
but
the
concept
is,
is
solid.
The
architectural
underpinnings
are
there
and
we
really
just
need
to
figure
out
like
if
the
implementation
is
acceptable
and
that
the
user
interfaces
is
adequate.
So
that
would
be
awesome.
B
Media
library
issue
1448
on
there's
been
a
lot
of
excitement
around
this
recently
we've
had
some
new
contributors
come
in
and
kind
of
roll
together,
like
a
large
amount
of
changes
all
at
the
same
time,
and
now
we're
kind
of
working
backwards
and
splitting
those
out
into
more
granular
issues
so
that
we
can
make
a
iterative
progress.
One
issue
at
a
time
so
I
think
at
least
some
of
the
that
functionality
is
almost
an
ever
well
that
will
be
completed.
B
B
B
B
We
could
teach
it
tricks
on
how
to
read
config
files
and
pull
out
strings
that
need
to
be
translated
out
of
them,
which
that's
the
primary
reason
why
you're
not
supposed
to
run
T
like
T
on
a
variable
is
because
the
PRT
extractor
doesn't
know
what
the
value
of
that
variable
is.
But
if
we
make
an
official
mechanism
for
translating
values
and
config,
then
a
PRT
extractor
can
find
those
strings
and
things
will
be
run
through
locale
and
right
now.
What
we're
doing
is
every
time
we
have
like
content
type
ylabel
or
something
like
that.
C
B
B
B
B
B
We've
started
adding
to
these
weekly
agendas
backdrop
to
Don
X
discussions
because
we're
moving
towards
that
version,
number
I,
think
that's
we
just
like
to
discuss
kind
of
what
we're
thinking
about
for
backup,
which
would
be
out
like
a
year
from
now.
Yeah
very
is
when
it's
scheduled.
Little
sooner,
you
have
been.
B
A
I
just
want
to
preface
it
a
little
bit
by
saying
like
if
we
do
want
to
release
a
backdrop
to
in
January.
We
need
to
figure
out
what
it
means
to
be
the
next
version
of
backdrop,
in
particular
like
whether
work
and
a
break
ap
is
or
not
because
the
way
dribble
works,
every
major
version
breaks
api's.
But
now
in
backdrop,
we've
been
on
backdrop
one
for
three
years.
We
have
a
really
good
track
record
of
like
adding
new
features
without
breaking
api's.
A
So
then
that's
kind
of
one
question
and
then
the
other
question
is
like
what
do
you
get
for
upgrading
the
backdrop
to,
and
that
I
think
is
the
discussion
that
just
added
a
bunch
of
stuff
into
the
agenda
here
about,
like
you
know,
be
great.
If
we
had
a
killer
feature,
it
would
be
great
if
we
had
something
that
would
benefit
existing
sites.
The
like.
What
is
that
going
to
be
so
Jeff
I
want
to
turn
it
over
to
you.
So
you
can
talk
a
little
bit
about
your
ideas
here.
F
Yeah,
the
basic
idea
is
I,
think
it
was
phrases
upgrade
to
WordPress
I,
think
that
might
be
a
little
strong,
but
a
way
to
get
content
from
WordPress
sites
to
backdrop
sites.
So
my
main
concept
of
it
was
to
kind
of
replicate
the
ease
of
getting
content
in
and
out
of
WordPress
in
backdrop,
and
then
once
we
have
that
we
can
build
on
top
of
that
to
get
content
from
other
sources.
That
art
backdrop
like
WordPress
and
or
Drupal.
B
Yeah
I
wonder
for
most
of
these
ideas,
which
that
are
in
the
food
ethics
checklist.
Most
of
them
have
to
do
with
features.
You
know
things
that
we
could
add
that
aren't
necessarily
blocked
on
to
not
X.
It's
just
a
matter
of
you
know
if
we
want
to
bundle
them
to
dot
X
or
you
know
kind
of
marketing
purposes,
or
something
like
that,
because
there's
nothing
preventing
us
from
implementing
most
of
these
things
in
in
the
1x
cycle.
B
Yeah,
we
don't
want
your
item
slated
for
a
me
in
the
to
not
X
milestone,
because,
as
we
encounter
things
that
require
API
changes,
basically
like
we
put
them
into
the
2x
milestone,
but
almost
all
of
these
things
are
not
really
so
much
feature.
So
much
is
there
just
like
cropped,
basically
that
we
could
remove.
A
Well,
some
some
some
things
to
like
we
initially
Singh
on
start
saying:
oh,
that's
really
hard.
That
should
be
like
a
2
to
X
feature,
and
then
we
talked
about
it
for
a
while,
and
we
come
up
with
significant
changes
that
we
can
do
without
breaking
api's.
And
then
we
have
a
follow-up
issue.
That's
like!
Oh,
we
might
need
to
break
you
guys
to
do
that
and
something
like
menu.
Translation
might
be
something
we
can
fix
without
breaking
api's,
especially
if
we
get
some
significant
improvements
to
translation
in
general.
B
B
Very,
very
simply,
you
know
with
just
the
few
updates
to
the
dot
info
file,
but
that's
not
really.
You
know
how
you
should
be
leaving
your
modules
takes
quite
a
bit
more
work
to
get
them
to
be
totally
backed
up,
compatible
and
so
I
think
it's
time
for
us
to
evaluate.
If
that
ease
of
transition.
Is
you.
C
A
Would
say,
probably
not
based
on
the
number
like
I'm
still
moving
Drupal
6
sites
to
back
job
I
would
say:
there's
probably
a
ton
of
Drupal
7
sites
that
are
still
ready
or
haven't
been
moved
yet
and
still
would.
But
what
might
be
a
good
halfway
step
is
like
in
backdrop
to
rather
than
having
it
set
to
enabled
by
default.
We
set
it
to
disabled
by
default
and
then
in
backdrop
three.
We
could
remove
it.
B
D
I
was
gonna.
Chime
in
this
is
Jack
and
say:
I
agree
about
retaining
backwards,
compatibility
for
a
little
bit
longer.
Just
there
are
so
many
folks,
I
think
right
about
now,
realizing
like
there's
a
new
wave
of
folks,
realizing
that
Drupal
8
is
not
so
ready
for
many
sites.
You
know
and
I
think
there's
going
to
be
continued
waves
of
interest
in
all
good
alternatives,
so
I
feel
like
continuing
and
have
the
Drupal
6
in
Drupal
7.
Easy
pathway
is
pretty
important
for
a
while
yeah.
C
I
think
I
think
that
it
was
well
maybe
when
we
reach
Virgin
Trains
I
think
I
think
that
the
way
that
Drupal
8
is
sampled.
That
is
the
way
to
go
they
more
or
less.
They
said
that
double
9
is
not
going
to
be
a
major
breaking
version,
so
it
will
be
easier
to
move
from
Drupal
8
to
Dougal
9
and
then
then
will
be
the
API
breaking
one
I
think
that
we
should
follow
the
same
path
more
or
less.
B
C
C
A
It
having
a
PMC
consensus
on
whether
this
is
a
good
idea
or
not,
is
good,
but
then
we
also
need
to
have
like
a
technical
follow-up
to
be
like.
Is
it
possible
and
I
think
that
if
what
we're
looking
for
is
removing
deprecated
functions
and
changing
the
way
the
module
system
works
to
support
two
major
versions
that
might
be
possible?
But
if
we're
also
looking
at
removing
database
abstraction
layer
or
something
crazy
that
might
not
be
possible.
A
A
Okay,
now
out
on
another
alternative,
or
if
we
need
to
say
like
we're
going
to
do
it
and
we
look
at
it
and
go
back
and
say:
oh
no,
we
can't
do
it
we'll
do
something
else,
but
I
also
think
it's
good
to
have
these
conversations
with
people
outside
the
PMC
too.
Just
so
that
we
get
an
idea
of
like
you
know,
anyone
who's
watching
this
video
might
have
some
really
valuable
feedback
on
like
oh
I've
got
20
back
job
sites.
Please
don't
break
my
API
or
you
know
whatever.
A
B
D
And
I
really
appreciate
that
folks
are
talking
about
this,
like
kind
of
not
being
beholden
to
the
calendar
for
it.
You
know
like
for
the
technical
reasons
and
also
for
reasons
that
go
towards
our
mission
more.
You
know.
You
know
that
these
kind
of
concerns
about
staying,
ready
for
all
the
people
still
getting
off
of
Drupal
6
and
realizing
that
their
options
are
not
what
they
thought.
They
would
be
that
that's
really
part
of
our
mission,
so
it
makes
sense.
C
But
then
another
score
of
zero
underscore
button
gets
appended
to
the
final
and
there
is
a
module
yeah.
There
is
a
module
that
handles
that
case
for
Java
7,
but
it's
not
ready
for
to
play
anyways.
This
problem
just
keeps
coming
up
and
I'm,
not
sure.
If
this
would
be
handling
these
cases
would
be
an
API
breaking
change
or
we
can
make
it
an
option
like
in
the
file
system
and
say
how
you
wanna
be
handling
new
uploads.
Should
they
be
renamed
or
whatever
I
don't
know,
maybe.
A
Yeah
I
also
run
into
that
issue,
really
commonly
it's
not
related
to
government
sites.
Anyone
like
from
a
end-user
experience
when
you
were
plates
a
file
and
you
upload
a
file
with
the
name.
You
expect
the
new
file
to
have
the
name
that
you
gave
it.
There's
a
great
Drupal,
7
module
I
think
that
we
could
implement
parts
of
that
in
core
without
an
API
break.
I
also
think
we
could
do
it
anytime.
We
could
do
it
in
seven
one.
If
you're
upset
about
enough
I'm
pretty
upset
about
it,
we
go
run
it
together.
C
Looks
like
you,
the
subject
is
being
brought
up
like
very
often,
and
it's
like
I
guess
what
people
expect,
but
on
one
hand,
people
that
are
happy
with
how
joopa
works.
Now
they
will,
if
we
change
it
and
don't
make
that
optional
will
be
disappointed.
But,
on
the
other
hand,
there's
a
lot
of
people.
I
guess
like
50/50
thing
that
expect
Drupal
to
be
behaving
like
a
file
manager.
So
when
I
upload
something
I
just
wanted
to
have
that
name
yeah.
So
I,
don't
change
that
I!
A
Mean
I
think
I
think
what
we
do
is
we
have
a
setting,
just
like
you
recommended
and
for
all
old
sites.
We
set
the
setting
to
remain
the
way
it
is
now
and
then
for
new
sites.
We
said
that
the
way
people
expect
it
to
be,
and
then,
if
people
want
to
change
their
own
sites,
they
go
change
the
setting,
but
yeah
I,
don't
think
that
that's
a
it
wouldn't
require
API
breaks.
A
Okay,
well,
let's
keep
talking
about
it,
I'm
curious
to
see
what's
required
in
core
in
backdrop
core
to
support
two
major
versions
of
controls:
I'm
happy
to
look
into
that.
I
do
not
know
what's
required
on
our
infrastructure
side
in
terms
of
project
module
or
back
from
CMS
org,
to
support
two
major
versions
of
kinship
projects
at
one
time,
but
we'll
have
to
look
into
that
too.
A
A
D
So
that's
kind
of
like
a
general
city,
con
thing
and
I
think
some
folks,
some
new
folks
are
excited
about
getting
evolved
to
the
community
there
around
that
stuff
and
I
know
that
my
co-workers
and
maybe
folks
from
another
shop
open
flows,
also
talked
a
backdrop.
While
they
were
there
and
I.
Think
that's
what
helps
push
the
backdrop.
Official
release
of
civis
erm,
so
super
CRM
stable,
is
out
it's
on
the
download
page.
D
It's
you
know.
It's
ready
for
Showtime
I've
been
testing
it
quite
a
bit
on
the
site
that
we're
about
to
make
live
the
backdrop
site.
That's
going,
live
I!
Think,
finally,
in
June
that
we're
using-
and
it's
going
great
so
I
think
folks
were
pretty
excited
about
that.
It
was
a
sharp
contrast
to
what
I
heard
about
the
presentation
on
Drupal
8,
where
it
was
demonstrated
that
civis
erm
can
be
turned
on,
but
once
you
do
that
you
can't
enable
any
other
modules
in
Drupal
8.
So
so
we're
a
lot
further
ahead.
D
Not
that
it's
all
about
that,
but
it
was
just.
It
was
news
to
a
lot
of
people
at
City
Khan
and
that's
specifically,
a
big
nonprofit
audience
and
folks
working
in
education
and
stuff,
like
that.
So
I
think
it
put
a
backdrop
a
little
bit
more
on
folks
radar
after
that,
and
that's
why
that
flurry
came
up
because
the
interest
is
there.
I
definitely
saw
a
number
of
nonprofits
come
back
from
that,
because
a
city
con
is
something
that
users
actually
go
to,
which
is
interesting.
D
Like
a
lot
of
users
go
there's
a
user
summit,
there's
trainings
and
stuff
like
that,
so
many
of
my
montes
clients
were
actually
there,
and
so
they
get
directly
this
news
about.
What's
going
on
in
Drupal
and
in
in
WordPress
and
in
a
backdrop
now
too
so
yeah
I
guess
for
those
reasons,
I
would
definitely
encourage
folks
to
try
to
make
it
out
or
for
us
to
do
some
more
recruitment.
D
Maybe
a
folks
were
doing
the
city
and
backdrop
thing
like
you
know:
herb
has
been
doing
a
lot
of
stuff,
herb
dull
I
believe
and
did
a
lot
of
work
to
get
the
city
release
for
back
dropouts
so
might
be
worthwhile
to
get
in
touch
with
folks
about
I,
don't
know
more
backdrop:
resin
representation
in
that
community,
so
yep
great
cool
I'd
be
down
to
reach
out
to
her
at
some
point.
After
I,
catch
up
on
I
have
to
get
webform,
civis
erm
fully
released,
and
then
I
can
ask
other
people
to
other
work.
A
E
Sure
I
did
put
something
in
about
it
was
on
the
metaphor
too,
and
I
don't
know
if
we
want
to
hold
off
till
2:00
or
if
it's
something
that
you're
even
interested
in,
but
it
had
to
do
with
pre-populating
a
site
when
people
download
with
content,
it
seemed
like
a
few
people.
There
said
yeah
it'd
be
a
good
idea,
because
I
guess
for
some
novices
coming
in
downloading
backdrop.
E
For
the
first
time
they
might
not
see
the
potential
with
a
vanilla
site,
even
though
there
are
posts-
and
there
are
pages-
and
there
are
some
samples
in
the
download
I-
don't
know
if
others
have
an
interest
in
that.
But
I
know
when
I
downloaded
other
CMS's
when
I
was
first
looking
a
long
time
ago
and
then
I
revisited,
there
seemed
to
be
some
content
creators
that
just
fill
in
with
samples
so
that
people
could
see,
if
that's
a
discussion
where
it's
having
here.
If
we
want
to
keep
it
in
the
the
issue,
queue
yeah.
A
I
mean
it's,
this
is
a
long-standing
problem
with
Drupal
2
is
that
when
you
first
install
a
Drupal
site,
you
get
a
blank
slate
and
it's
really
hard
for
people
to
visualize
like
how
this
slate
relates
to
their
finished
product
website,
and
we,
in
the
version
of
backdrop,
have
now
included
one
page
in
one
post,
which
is
better
than
nothing,
but
it
still
doesn't
communicate
like
a
power
of
a
content.
Management
system.
A
I
think
we're
a
little
torn
between
the
amount
of
work
somebody
would
have
to
do
to
actually
build
their
own
site
with,
like
deleting
all
the
stuff.
They
don't
want
versus
the
amount
of
benefit
it
does
to
have
all
of
that
content
there
for
new
people.
So
I
don't
know
like
where,
like
where
that
option
might
be.
It
looks
like
everybody
in
the
chat
is
talking
about
to
Belle
generate.
A
We
already
have
a
tool
in
a
developer,
module,
develop
content,
but
that's
kind
of
the
opposite
of
what
we
run
right
like
we
want
de
velde
leet
all
of
your
content,
and
we
want
backdrop
to
ship
all
of
your
contents.
The
developers
have
the
work
to
do
and
not
the
end
users,
so
I
guess
we
would
just
I
think
Tom.
It's
a
great
idea.
We
need
to
have
more
of
a
conversation
about
how
to
get
the
content
in
what
the
content
should
be
like.
A
If
you
install
a
module,
should
it
automatically
provides
like
a
content
type,
should
it
automatically
create
content
of
that
type?
Is
there
going
to
be
like
an
easy
off
button?
So,
if
you're
a
developer-
and
you
do
want
to
start
with
a
blank
slate,
you
can
you
know
disable
auto
content
and
then
turn
on
module,
and
then
there
won't
be
any
content.
I
think
just
like
a
little
with
a
little
thought
about
how
it'll
work
I
think
it's
a
good
idea.
Well,.
E
Thanks
so
the
one
I
saw
was
almost
in
the
opposite
fashion.
That
I
thought
would
work
that
I
liked,
and
that
was
where
the
the
default
was
just
the
vanilla
download.
This
is
what
you
get,
but
if
you
downloaded
it
and
then
wanted
to
see
more
than
there
was
a
populate
content
button
that
brought
in
a
bunch
of
sample
content.
E
So
it
was
not
an
afterthought,
but
if
there
wasn't
enough
there
for
you
to
begin
with
and
you're
just
perusing
CMS's,
there
was
a
possibility
to
do
that,
but
it
didn't
come
in
with
the
default
installed.
It
was
something
that
a
novice
could
then
add
to,
and
it
populates
a
bunch
of
crap,
so
you
really
had
more
there
than
what
you
would
want.
E
A
A
Maybe
good
idea
to
put
something
like
backup
in
migrating
core,
so
that
people
just
have
that
ability
to
like
do
automated
backups.
And
if
we
had
something
like
that
in
court,
we
could
give
them
a
button
that
would
essentially
like
restore
a
database
that
might
have
a
ton
of
content
in
it
and
then
we'll
also
have
the
ability
to
revert
back
to
the
clean
slate
version.
A
So
that
might
be
like
two
features
that
would
go
in
hand-in-hand
is
like
one
give
you
this
back
up
in
my
great
tool,
but
to
also
build
in
a
feature
that
we
could
like
ship,
backup
and
migrate
with
some
empty.
You
know
empty
database
versus
a
or
just
just
a
database
with
content
in
it,
and
then,
when
you
go
push
the
button
that
says,
show
me
simple
content.
A
It
would
make
a
backup
of
your
empty
database
install
the
other
one
and
then,
when
you're
like
okay,
see
what
I
want
give
me
back
my
empty
site,
you
can
hit
revert
and
it
would
switch
it
back.
One
thing
back
up
in
migrate
doesn't
handle
right
now
is
config,
so
we
would
need
to
figure
out
how
to
backup
your
config
in
addition
to
your
database,
but
I
think
that's
fairly
trivial
in
terms
of
like
the
utility
that
would
provide
and
it
might
solve
both
those
problems.
So
I
love
this
idea.
A
C
Mean
I
read
both
net
posts
for
the
2.0
version
and
Tom's
suggestion
for
that
and
I
wanted
to
chime
in,
but
I
didn't
have
the
time.
Just
just
a
few
thoughts
feeds
module
how
it
works
is
it
allows
you
to
input
from
say
a
CSV
file
and
then,
if
you
do
not
like
the
input
from
the
importer
page,
it
allows
you
to
delete
imported
content
just
that
imported
color.
C
So
it
keeps
track
of
what
he
tells
imported
and
it
allows
you
to
remove
it
not
to
reflect
to
delete,
because
if
you
have
said
it
to
overwrite
things,
he
would
still
delete
them
and
I,
which
might
be
considered
a
loss
so
that
there
was
one
thought
and
then
what
you
are
talking
about.
Tom
just
brought
back
the
memories
of
the
I.
Think
that
there's
an
issue
in
the
queue
about
permitting
profiles
to
run
even
after
installation
yeah.
C
We
should
take
another
focus,
because
what
you
suggest
there
is
like
we
can't
have
a
single
sort
of
like
type
of
bulk
content.
That
will
please
everybody
so
I
think
the
solution.
There
is
a
variety
of
of
like
sites
that
would
be
profiles
and
then
allowing
people
to
browse
from
the
project
browser
and
install
like
a
blog
site,
a
demo
blog
site,
because
the
belgian
rate
is
good,
but
it
just
generates
lorem
ipsum
things.
It
doesn't
like
it's
not
an
actual,
pretty
thing.
It's
just
the
development
Oh.
E
Karim
yes
well,
and
this
is
going
to
be
a
conversation.
It
goes.
I
just
want
to
get
a
feeling
to
see
if
there
had
anybody
was
opposed
to
it
or
if
it
was
something
that
we
would
feel
like
from
a
marketing
standpoint.
It
really
would
help
novices
I
remember
for
the
first
couple
years,
I
was
playing
Drupal
and
going
to
Drupal
cons,
and
they
would
show
all
the
wonderful
things
could
do
on
a
vanilla,
blue
background
and
I.
E
Look
at
my
partner
go
what
having
it
took
several
years
and
we
I
mean
we
were
invested
in
it
at
that
point
and
I
didn't
see
the
magic
so
now
I
can
yeah.
This
is
seven
years
later.
But
if
we're
trying
to
pick
up
people
with
that,
first
impression
the
one
CMS
that
I
downloaded
I
was
like.
Well,
there
it
is
yeah
I
can
see
it.
C
Yeah
so,
as
Jen
said,
we've
done
baby
steps
on
improving
the
situation
and
I.
Think
it's
a
good
thing
that
we
now
have
a
this.
Is
your
first
page
just
edit
it,
but
that's
a
really
cool
thing
and
we
have
a
couple
of
menus
there.
I
would
love
it
if
there
were
more
menus
to
showcase
that
drop
down
out
of
the
box,
for
example,
but
with
just
two
pages
just
feed
seems
redundant
but
yeah
this.
This
needs
a
lot
of
conversation
and
and
I.
C
Think
that
see
how
we
have
them
as
projects
modules,
themes
and
layouts
I
think
that
there
should
be
another
level
for
profiles
and
allow
them
to
be
executed,
post
installation
and
then
people
can
start
creating
their
blog
profile
over
there.
I
don't
know,
yellow
pages
profile
and
built
on
top
of
that.
Fist.
I
bet
that
no
one's
going
to
be
happy
with
what
little
pudding
core
and
it's
like
I
guess,
that's
saying
all
the
things
to
these
or
be
that,
so
it
will
be
a
lot
of
bike
shading.
That
was
my
main
point.
What's.