►
From YouTube: Backdrop Weekly May 31st
Description
Today’s development agenda: https://bit.ly/2IJuy4k
A
A
Let's
see
so
we
also
became
the
last
meeting,
we're
going
to
be
working
and
improving,
obviously
themes
and
layouts
election
pages
on
back
Pepsi,
mascot
org.
That
hasn't
hasn't
been
any
practice
yet,
but
now
that
one
and
one
is
out,
we
should
be
able
to
focus
on
that.
The
forum
site
duck
home
and
some
changes
to
that
are
not
going
to
forget.
So
that's
my
welcome
face.
B
C
C
We
still
had
the
meeting,
even
though
it
wasn't
recorded
and
discussed
particular
potential
functionality
and
features
that
we
should
include
in
the
1.11
release,
which
would
be
the
next
release,
looks
like
that's
not
right,
so
I
may
15th
it'll
be
September
15th
2018,
but
before
we
go
into
that,
let's
talk
about
the
maintenance
releases
for
1.10,
which
is
the
currents,
might
a
release
of
backdrop,
and
it's
the
one
that
if
you
go
to
backup,
see
my
stonework
it's
what
you
would
download
today
is
the
current
stable
release.
Just
yesterday
we
released
one
dot,
10.1.
C
110
and
we
fixed
a
boatload
of
issues,
kind
of
an
in
that
in
that
release,
only
a
few
of
which
were
actual
regressions
introduced
in
one,
and
we
did
some
tidying
up
around
the
way
the
messages
are
displayed.
When
you
schedule
content
for
publishing,
we
fix
some
issues
with
the
menu
translation
we
improved
version
checking
it
looked
like.
We
had
some
thoughts
that
maybe
the
1.10
released,
because
it
you
know,
went
over
them.
C
The
singular
number
9
that
some
of
our
version
comparisons
might
be
causing
problems
that
string
comparison
of
like
10
versus
9
I
might
end
up
being
higher
than
10,
which
of
course,
did
not
correct,
but
it
actually
turned
out.
All
of
our
urgent
checking
was
completely
fine,
but
there
was
just
some
unrelated
version,
checking
issues
that
have
been
in
Drupal
and
in
backdrop
since
forever,
regarding
dev
versions,
beta
versions,
alpha
versions,
etc,
and
so
we
fixed
all
those
problems
which
is
great
like
we
thought
that
it
was
the
number
10
related,
but
just
turned
out.
C
It
was
an
unrelated
problem
that
that
we
handle
at
the
same
time.
So
that's
been
great
and
so
one
the
10.1
is
now
out,
and
we
also
pushed
that
to
all
of
the
up
streams.
So
if
you
run
Pantheon
site
I,
think
platform
got
updated
as
well
or
use
the
darker
image.
All
of
them
are
now
on
the
1.10
release.
So
you
can
update
all
of
your
sites
to
one
to
ten
with
confidence
for
the
next
bug.
Fix
release
looks
like
we've
got
two
issues
in
the
agenda
here.
C
This
issue
2904
database
credentials
used
to
not
be
URL
encoded,
and
now
they
are
URL
encode.
It
really
only
applies
to
people
that
have
used
special
characters
in
their
database
password
and
we
we.
This
has
been
an
issue
since
the
release
of
1.9.
So
unfortunately
it's
been
plaguing
us
for
last
4
months.
C
We
have
a
fix
in
the
issue
there
that
will
remedy
that
problem
temporarily
and
we
haven't
planned
for
making
it.
So
that's
actually
merge
Bowl
the
thing
that's
holding
it
up
is.
We
need
a
status
report
indication
if
the
password
is
being
attempted
to
be
fixed
automatically.
We
need
to
throw
a
status
report
error
there,
but
it
would
continue
to
work.
We
would
just
throw
a
warning
to
the
user,
saying:
hey:
you
need
to
update
your
settings
about
PHP
file,
so
that
still
needs
a
little
bit
of
work,
but
it's
coming
along.
C
It's
kind
of
dropped
off
in
importance
like
it
was
really
important
when
1.9
first
came
out,
because
there
were
a
couple
of
sites
out
there
that
actually
broke
when
updating,
but
now
it
spent
4
months.
So
updating
users
is
the
the
biggest
problem
and
those
users,
if
probably
updated
by
this
point
or
where
they
manage
to
update
their
files
by
now
so
I'm,
a
lesser
important
thing.
C
C
Well,
not
at
the
last
minute,
but
I
was
basically
being
stubborn
in
that
issue,
and
so,
if
we
didn't
reach
a
consensus
on
on
implementation
there,
but
now
we've
kind
of
desculpe
that
issues
lightly
to
make
it
so
that
the
implementation
is
a
lot
lower
impact
than
the
previous
iterations
of
it.
And
so
the
idea
here
is
simply
that
we
make
it
so
that
modules
have
the
ability
to
have
tags
and
got
info
files.
But
the
user
interface
stays
exactly
the
same.
C
A
C
B
D
D
A
A
C
A
D
D
Mean
I
would
I
would
be
fine,
adding
the
ability
to
put
these
in
the
the
other
thing
we
could
do
is
yeah
I,
don't
know
either
way
yeah.
It's
kind
of
a
little
change.
I
think
the
bigger
thing
that
we're
gonna
brag
about
is
like
when
it's
actually
searchable
on
the
website,
yeah
dependable
release.
When
we
actually
get
a
search,
agon
pedo,
then
that's
when
we
can
sort
of
announce
it
yeah.
C
C
C
Most
of
those
have
pull.
Requests
looks
like
all
of
them
have
been
reviewed
and
all
of
them
meets
work
at
the
moment.
So
if
you're
looking
for
bugs
to
fix,
high-priority
items
are
in
the
1.10
that
milestone,
but
none
of
them
are
like
high
enough
that
we're
gonna
pull
them
out
and
mention
them,
and
this
meeting
so
yeah
the
state
of
backdrop,
is
stable.
C
Ok,
let's
talk
about
1.11
on
911
is
the
next
minor
release.
That
is
the
next
release
that
includes
features
and
that
will
be
September
15th
2018,
like
I,
said
we
have
a
little
meeting
discussing
what
areas
of
focus
we
have
for
the
next
release,
though
these
things
are
not
set
in
stone.
We
have
a
couple
of
ideas
here
that
we're
looking
to
get
implemented.
C
Looks
hard
yeah
I'm
going
to
start
with
this
one,
which
is
a
little
bit
easier,
so
the
first
one
I'll
talk
about
is
issued
3105,
which
is
a
poor
quest
that
makes
it
so
that
we
can
make
it
so
the
backdrop
core
can
update
itself
through
the
user
interface,
and
this
is
not
as
ambitious
as
it
might
sound.
It
uses
the
same.
The
existing
update
mechanism
that
we
currently
use
for
updating
modules,
it
just
reapplies
that
exact
same
approach
to
updating
core
itself,
so
the
pull
request
is
is
up
there
already.
C
It
is
M,
it
needs
review
state
and
it
actually
seems
like
it
already
work
so
they're
testing.
It
is
somewhat
difficult
because
you
have
to
mock
up.
You
know
pretending
to
be
a
previous
release,
then
updating
to
a
newer
release
and
then
once
you've
updated,
the
self
updating
ability
disappears
because
the
self
updating
ability
isn't
in
the
new
release.
C
It's
actually
been
an
open
issue
for
quite
a
while,
but
this
is
kind
of
the
first
step,
which
is
just
allowing
court
updates
at
all
allowing
backdrop
to
update
itself,
and
so
it
looks
really
good
more
eyes
that
we
can
get
on
that
the
better
and
then
I
think
that
we
should
probably
barring
any
large
issues,
get
that
merged
into
the
1.1
dot.
X
branch
for
one,
not
eleven
kind
of
as
soon
as
possible.
C
C
So
the
profiles
directory
where
install
profiles
live
is
still
in
the
root
of
the
backdrop
installation,
instead
of
being
under
the
core
directory,
as
the
core
self
updater
only
replaces
the
core
directory
and
actually
most
of
our
instructions
regarding
updating
bactrim,
actually
also
only
say
that
you
need
to
update
the
core
directory
moving
the
profiles
directory
underneath
core.
We
simplify
the
update
process
and
make
it
so
that
profiles
are
included
in
the
automatic
updates
eventually.
So
that's
another
issue
that
is
kind
of
an
infrastructure
task
that
would
be
good
to
handle.
C
A
C
And
the
current
point
cost
what
it
does
is
it
updates
the
readme
file,
that
is
in
the
core
profiles
directory
to
say
something
different.
It
says
like
if
you
want
to
run
your
own
profiles,
create
a
directory
called
profiles
in
the
roots
and
then
look
at
your
profiles
there.
So
it
does
have
some
documentation
updates,
but,
unlike
the
modules
and
themes
directory
which
are
there
but
empty,
it
doesn't
create
one
out
of
the
box
because
it's
kind
of
unlikely
for
a
normal
user
to
create
their
own.
The
install
Pro
40
yep.
D
C
Okay,
now,
let's
get
into
some
of
the
more
complicated
things
so
also
related
to
all
of
our
abilities.
To
do
updates
and
auto
updates
is
this
issue,
which
has
to
do
with
collecting
better
statistics
about
what
users
are
doing
with
their
backs
on
websites
and
that's
issue.
Issue
285,
as
you
285
recently
got.
An
excellent
updates,
looks
like
by
BW
panda,
actually
not
super
recent
last
month
regarding
how
joomla
accomplishes
this
and
the
company.
A
We
say
it's
just
gonna
be
like
two
or
two
or
three
different
parts:
we're
number
one.
We
need
to
figure
out
what
information
we
want
to
track.
Number
two
we're
gonna
have
to
set
a
project
module
to
be
able
to
support
this
kind
of
information
and
then
number
three
we're
going
to
have
to
set
up
backup
itself
to
be
able
to
submit
the
information
to
the
project,
module,
yep.
C
Exactly
all
of
those
things-
and
we
haven't-
you
know-
started
any
implementation
here,
so
the
door
is
kind
of
wide
open
as
to
how
we
approach
it.
It
seems
kind
of
obvious
that
backdrop
already
backed
up
installs,
already
communicate
with
backdrop
CMS
org
updates
and
that
we
can
piggyback,
on
top
of
that
same
request
when
a
backdrop
site
checks
for
updates
that
we
can
also
record
information
not
just
about
what
versions
of
modules
they
have
installed,
but
also
about
how
those
modules
are
being
installed
or
how
those
modules
are
being
used.
A
Doesn't
currently
report
which
modules
it
only
reflects
which
projects?
Yes,
so
things
like
the
first
step
would
be:
let's
see
if
we
can
add
module
data
in
addition
to
project
data,
because
I
think
that'll
be
pretty
easy
and
then
we've
got
to
figure
out
I
think
we
need
to
track
specific
variable
values
and
then
how
do
we
communicate
to
people
are
running
this
sites
what's
being
transmitted
and
give
them
an
option
to
opt
out?
D
A
But
I
think
they'll
be
really
great
if
we
could
like
itemize,
but
this
is
the
data
we're
collecting
from
you.
It's
which
modules,
which
versions
over
there
enabled
or
not,
and
then,
if
we
want
any
other
information
like
which
languages
do
good
software
translation
or
whatever,
we
specifically
put
that
into
a
list
and
say
this
is
what
we're
trying
to
figure
out
and
then
we
already
have
a
paragraph
about
why
we
want
this
information
internally,
making
decisions
about
each
other
product.
A
D
D
Setting
that
says,
like
you
know,
send
anonymous
usage
statistics
to
you
know,
but,
like
you
know,
if
we
enumerate
all
the
things
that
we're
collecting
and
then
we
add
another
thing,
then
it's
kind
of
invalidating
their
decision
when
they
clicked
on
the
checkbox
begin
with.
So
it's
like
either.
We
should
keep
it
sort
of
general
about
the
information
we're
collecting.
So
we're
not
you
know
being
too
specific
and
then
changing
it
or
we
need
to
figure
out
some
way
to.
Let
them
know
that,
what's
being
changed,
yeah
I
think
what
I
would
like
to.
C
See
is
the
concept
of
having
the
central
server
backed
up.
Cms
org,
determined
was
collected,
is
too
dangerous,
I
that
the
decisions
about
what
are
the
capabilities
about
what
information
is
sent
should
be
in
the
software
itself,
which
means
that,
in
order
to
collect
new
information,
they
would
have
to
update
to
a
newer
version
of
backdrop,
and
at
that
time
we
could
give
them
a
status
report,
update,
saying
the
information
we
collect
has
changed
and
then
you
would
like
go
to
a
button.
C
Then
click
like
ok
or
some
air
go
to
a
page,
and
then
click.
Ok.
So
basically
like
say
it's
fine
week
now
I'm
avoiding
this
yeah
exactly
so
every
one.
Every
time.
Every
time
you
make
a
change
to
what
we're
collecting
that
requires,
the
software
change
and
I
think
that
would
be
the
safest
way
to
go
about
it.
C
C
C
Actually,
I
was
thinking
about
this
as
being
like.
You
know,
it
would
probably
be
separated
by
module,
but
every
individual
thing
that
we
track
would
just
have
some
kind
of
identifier.
Like
let's
say,
system
module
collected
PHP
version,
so
it'd
be
like
system
:,
PHP
version,
and
that
would
be
like
the
unique
key
for
that
particular
piece
of
data
that
we
collect
and
then
each
module
could,
in
theory,
provide
options
of
data
to
collect
I.
C
A
So
I
think
I
haven't
looked
at
it
recently,
but
I
think
where
we
left
it
is
document
was
able
to
take
the
note.
We
go
work
from
simple
eats
in
by
its
backdrop,
and
it
accounted
for
everything
except
for
layouts,
which
strictly
doesn't
happen.
The
same
way
that
we
do
and
so
I
thought
it
looked
fantastic
and
said.
If
we
can
get
this
work
really
outside
totally
B,
we
should
include
it.
A
You
continue
editing
button
where
I
don't
know
if
we
have
this
already,
but
we
talked
about
when
we
put
sequencing
in
core
using
the
tump
store
where
drats
so
something
like
that
could
work
for
that.
Well,
we
could
just
say
it's
like
a
unpublished
for
vision,
because
by
doing
that
we
talked
about
the
creating
a
fake
node
object
and
trying
to
somehow
shove
it
in
as
a
context,
perfect
subject
that
wasn't
a
true
node,
but
last
I
read
Babylon
said
he
was
gonna,
try
a
couple
things
and
see
what
he
thought
was
just
interesting.
C
Yeah
I'm,
looking
at
the
request
now,
Ivan
I
haven't
tried
it
out.
We
do,
we
do
have
temp
store
functionality
in
core,
it's
used
by
views
and
layouts,
and
it's
this
sort
of
thing
is
exactly
what
it's
intended
to
be,
or
it
looks
like
what
happens?
Is
you
click
the
preview
button
and
it
basically
saves
the
node,
but
it
saves
it
into
temp
store
instead
of
instead
of
into
it
like
a
to
the
node
tables.
So
it's
kind
of
that's
really.
B
A
C
To
take
write
it
to
the
table,
but
this
is
not
not
saving
it
anywhere.
It's
literally
well
I
mean
it's
in
temp
store,
but
temp
store
is
per.
It's
named
temporary.
It
has
a
an
expiration
date
where
it's
like.
If
you
were
not
to
edit
your
content
for
like
a
day
or
three
days,
the
montreux
gets
to
determine
how
long
LS,
then
it
gets,
dropped
from
the
database
got
cleaned
up.
A
C
Yeah
it's
currently
and
it
needs
work
states,
but
the
implementation
just
browsing
over
a
free
food
and
it
looks
pretty
good
no
tests
yet
that,
of
course,
would
need
to
be
added,
but
yeah.
That's
that's
pretty
exciting.
The
reason
why
we
were
moved
note
preview,
of
course,
is
because
the
preview
was
really
terrible,
and
so
we
got
rid
of
that
concept
from
Drupal
seven
because
it
was
not
actually
very
useful
yeah,
it's
so
confusing
like
does
it?
C
Was
it
something
that,
like
they
engage
in
the
wrong
theme,
yeah
boy
that
was
the
worst
so
anyway,
that
looks
that
looks
really
promising
issue.
30
62
great
meets
need
some
work
and
somewhere
feedback
as
well,
more
I'm
also
on
that
would
definitely
be
appreciated,
so
Jen,
there's
the
next
issue
in
the
agenda
is
adding
save
draft
decor
and
just
as
question
marks
here.
Is
there
an
issue
for
that
so.
A
I
think
for
every
said,
you
create
an
issue
for
it,
but
I
looked
at
a
few
couldn't
find
it
that
doesn't
mean
it's
not
there.
Sometimes
the
mark
on
finding
things
on
github
but
yeah,
there's
a
there's,
a
module
called
safest
routes
for
simple
seven
that
I
thought
might
fit
really
nicely
with
the
VP
feature.
A
So
if
we
wanted
to
serve
editorial,
include
news,
monitor,
might
work
well
and
then
we'd
also
been
talking
about
workflow
states
in
the
last
release,
because
we're
looking
at
the
scheduling
feature
we
just
added,
and
so
we,
if
we
wanted
to
figure
out
how
to
solve
our
workflow
problems,
save
the
straps
might
be
part
of
that
as
well.
So
the
next
one
is
also
I've
better
workflow
and
only
it
is
really
good
to
save
this
jacket
too
and
I'm.
Pretty
sure.
A
Gregory
has
some
issues
on
all
of
these
things,
but
I
couldn't
find
them
so
I
don't
know
if
we
need
to
create
new
issues
or
dig
up,
there's,
probably
a
meta
somewhere
about
workflow
or
several
metas
about
workflow
me
just
a
figure
out
which
one
of
those
we
should
be
looking
at
there.
We
go
click
on
it.
C
C
Interesting,
this
is
actually
less.
This
is
actually
more
like
a
user
interface
switch
around
rather
than
adding
real
substantial
functionality.
It
looks
like,
although
really
the
suggestion-
and
this
one
is
to
use
the
to
use
the
drop
button
capabilities
like
to
change
the
Save
button,
and
my
most
recent
comment
on
this
was
about
a
month
ago
saying
that
Drupal
8
actually
removed
that
feature
from
Drupal
8,
because
people
couldn't
figure
out
how
to
publish
an
unpublished
content.
So
I,
don't
know
I
feel
like
this
particular
issue
we
might
consider
like.
C
C
But
anyway,
you're
right
that
there's,
maybe
I,
should
say
gregory's
right
that
you
know
there's
potential
for
doing
a
lot
of
work
in
the
workflow
area,
especially
now
that
we
have
scheduling,
figuring
out
how
scheduling
and
publishing
and
saving
as
drafts
or
previews.
All
of
these
things
are
they're
interconnected.
So
there
are
opportunities
here
to
to
improve
our
implementations.
C
C
Or
market
unpublished
or
publish
like
when
you
check
those
options
for
scheduling
or
for
publishing,
it
changes
the
label
of
the
button
on
the
page
to
make
it
clear
what
the
action
is
that
you're
actually
doing
that's
an
interesting
concept
where
instead
like
it
right
now,
we
just
have
a
button
just
as
safe,
but
this
would
change
the
button
label.
It
looks
like
to
match
the
action.
So
if
you
scheduled
it,
it
would
say
schedule
publication
that
looks
like
if
you
had
it
unpublished,
it
would
be
save
as
draft
and
I.
C
C
Yeah
I
would
be
happy
with
a
hijacking
of
that
issue
1383
to
take
on
that
purpose.
Instead,
instead
of
like,
let's
use
the
drop
button
like
triple-eight
instead
be
the
issue.
There's
like,
let's
use
this
control
or
this
functionality
from
this
control
module
into
into
court
judge
just
close
out
you
reopen
it.
Okay,
making
a
new
issue
might
be
even
better,
though
I
mean
that
one
that
one's
already
good
just
got
some
noise.
Okay,
all.
C
C
You
know
we
had
three
items
that
we
were
angling
for:
one
of
10
menu,
translation
improvements,
block
translation
and
config
translation.
At
least
we
got
menus
and
blocks
completed
and
in
court,
which
is
great
issue.
704
would
take
us
kind
of
the
next
level
that
it
would
allow
us
to
track
translatable
strings
that
are
sorting
configuration
files.
It
actually
doesn't
add
new
functionality
so
much
because
you
can
already
fully
translate
back
drop,
including
the
strings
that
are
in
configuration
files.
C
It's
just
the
backdrop
can't
accurately
identify
which
strings
need
to
be
translated
in
those
configuration
files,
so
it
makes
it
so
that
sites
like
or
tools
like
our
localization
website,
don't
include
all
of
the
streams
that
need
to
be
translated,
because
it
can't
extract
from
the
codebase
which
strings
are
actually
required
to
be
translated,
so
issue.
704
would
fix
that
limitation
in
our
translation
extraction
capabilities
and
make
it
so
that
backdrop
could
be
fully
translated
or
we
could
pull
out
all
of
the
strings
that
need
to
be
translated
more
effectively.
C
And,
lastly,
you
know
there's
always
the
1.11
issue.
Tracker
milestone,
which
looks
like
currently
contains
about
ten
more
items
that
that
have
mentioned
Oh
I'll,
throw
it
here
are
some
things
that
also
look
like
they're
likely
to
be
improved
in
the
very
near
future.
Opie
has
been
doing
an
enormous
amount
of
work
on
contact
module,
so
contact
module
has
been
getting
new
settings
or
has
been
meritorious
working
towards
having
a
settings
form
right
now.
C
There
isn't
really
any
settings
for
contact
module
other
than
the
categories
and
where
emails
are
sent
to,
but
he's
looking
at
adding
things
like
controlling
the
threshold
of
like
how
frequently
people
can
send,
because
there
is
that,
like
a
flood
control
impact
drop,
but
it's
not
exposed
through
the
user
interface
also
making
it.
So
you
can
disable
the
send
yourself.
A
check
button
send
yourself
an
email,
send
yourself
a
copy
checkbox,
so
increasing
the
configurability
of
the
contact
module.
Those
are
coming
along
quickly
and
we'll
probably
see
those
in
1.11
and
Abdul
has
been
doing.
C
Work
regarding
user
registration
and
user
login,
similar,
adding
options
for
flood
control
or
exposing
the
options
for
flood
control
to
the
user
interface,
and
also
it
looks
like
we'll,
probably
have
the
have
the
login
settings
separated
from
the
rest
of
these.
Your
account
settings
which
I
feel
like
probably
it
would
be
a
good
thing
because,
like
as
we
get
more
options
controlling
how
a
user
logs
in
and
how
they
create
an
account
like
that
user
account
settings
page
is
already
overwhelmingly
long,
including
all
the
registration
emails
and
everything
like
that.
A
If
you
wanted,
to
like,
add
a
new
section,
just
a
whole
bunch
of
questions
and
how
the
things
like,
if
it
is
something
like
a
collection
of
modules
and
the
collection
of
configurations
how
to
get
bundled
and
distributed
in
the
Drupal
distribution
who's
using
fresh
make
files
is
sort
of
a
very
special
case
solution
that
we've
had
to
come
up
with
a
Drupal,
because
there
wasn't
anything
else,
but
now
that
we
live
in
this
time,
the
composer
we
could
just
have
some
kind
of
it.
Those
are
file
that
would
list
the
dependencies.
D
Have
we
have
the
we
have?
We
have
cor
able
to
download
projects
now
so
I
mean
if
we
had
so
so.
My
the
thing
that
I'm
advocating
for
is
that
we
make
install
profiles
just
install
right
now
they
sort
of
install
and
then
hang
around
doing
stuff,
and
you
can
have
modules
in
them
and
themes
included
in
them
and
stuff
like
that,
and
it's
sort
of
like
this
whole
other
thing.
I'm
thinking
that
we
switch
installed
profiles
to
just
install
it
has
an
info
file.
D
It
has
a
bunch
of
dependencies
that
either
the
can
download
independently
like
or
you
can
use
the
auto,
auto
download
to
download
all
them
or
say
you
need
to
install
these.
People
are
running
the
profile
and
then
it
just
installs
a
bunch
of
it
does
or
it's
a
bunch
of
configuration
and
runs
any
like
an
install
function
then
just
makes
any
changes
that
need
to
happen,
and
then
once
it's
done,
it
goes
away
because
it's
already
done
everything
it
needs
to
do.
That's.
D
C
That
idea
I
was
thinking
along
the
same
lines,
but
something
like
right
now
when
you
do
a
config
import,
config
and
ports
aren't
smart
enough
right
now
to
be
able
to
enable
modules,
let
alone
download
them.
But
it's
pretty
easy
to
identify
what
modules
provide,
what
config
files,
because
they're
all
namespaced
we
couldn't
potentially
make
it
so
that
importing
a
config.
A
C
D
I
think
it
probably
already
supports
those
like
I,
think
I
think
if
we
have
profiles-
and
they
have
an
info
file,
I
think
already
has
dependencies
in
it,
but
just
making
sure
that's
there
and
like
I,
just
think
this
might
not
even
be
really
a
technical
thing.
It
might
just
be
more
about
let's.
This
is
direction,
we're
going
from
now
on,
don't
put
modules
and
themes
into
your
install
profile.
Instead,
you
know
them
in
control
and
have
it
pull
it
in
yeah.
C
That's
always
been
a
mess
as
long
as
profiles
have
existed
anyway,
that
the
copy
that's
in
your
profiles,
module
directory
versus
the
one,
that's
in
the
normal
modules
directory.
It's
a
it's.
A
big
mess
like
so
I
would
yeah
absolutely
be
in
favor
of
deprecating
that
concept
of
a
profile
also
containing
modules
yeah.
D
So
it's
like
you
know
and
yeah.
So
it's
all
profiles
install
a
bunch
of
stuff
and
that's
it.
You
can
even
have
it.
You
know,
so
you
could
just
run
an
install
profile
on
an
already.
You
know
installed
site
and
it
can
just
set
up
some
more
stuff.
Oh
like
that,
where
it
doesn't,
you
can
do
it
like.
You
know,
after
the
fact
like
if
you
want
to
like
a
so
like
adds,
features
to
your
site.
I
know.
Last
time
I
talked
to
Jen.
She
was
worried
about
being
able
to
roll
back
that
stuff.
D
A
Those
are
they
problem
will
help,
because
the
reason
that
right
now
people
get
stuff
without
being
able
to
get
out
of
there
houses,
because
that
code
is
still
there
and
still
running.
But
if
maladies
is
a
script
that
it
runs
and
deletes
itself
like
a
config
does
on
the
config
sing,
then
you
don't
have
a
remaining
dependency
and
you
can
remove
that.
D
A
D
That's
what
I'm
sort
of
imagining
like
you
know,
I
I,
forget
what
I
posted
about
this,
because
I've
posted
I
think
in
several
different
places,
but
I
think
we
sort
of
need
a
na.
We
need
to
sort
of
agree
on
a
direction
to
go
with
it
and
I.
Think
I
have
like
some
principles
that
I'd
like
to
propose
along
these
lines
about
aliens
still
install
profiles
would
just
be
for
installing
yeah.
D
A
C
Does
look
like
profiles
do
support
config
import
like
they
have
a
config
directory,
just
like
modules.
Do
because
internally
modules
and
install
install
profiles
are
actually
considered
the
same
thing,
which
is
a
little
bit
weird,
but
that's
like
a
may
have
died
in
profiles
that
specify
dependencies
and
they
have
install
files
that
do
hook
install
and
they
have
config
files
that
get
imported
automatically
when
they're
turned
on
for
the
first
time.
It's.
D
C
D
D
Install
profiles
are
just
for
installing
I
think
we
still
need
to
figure
out
a
bunch
of
other
stuff
like
what,
if
you
want
to
feature
that
then
gets
updated
or
runs
on
an
ongoing
basis
or
distribution
like
this,
wouldn't
necessarily
handle
all
those
cases,
but
they
can
be
handled
some
other
way.
I
say
install
profiles
just
for
installing
your
recipe
on
your
site,
yeah.
C
You
know
I'm
not
saying
blocker
employing
this
as
a
king
trip
module.
At
least
you
know
to
beta
test
it.
Like
I
mean
it
could
be
like
a
standalone
module.
That
basically
just
reads
what
profiles
you
have
and
lets
you
execute
any
profile
arbitrarily.
You
know
like
I,
just
want
to
run
this
profile
and.
C
D
C
D
Core,
like
the
other,
the
other
thing
I
was
saying.
Is
that
there's
another
ticket,
whereas
basically
saying
that
our
default
installed,
install
profile
that
you
know
sets
up
posts
and
pages
and
stuff
like
that?
Is
it's
not
really
anyone's
use
case
like
I?
Don't
think
anyone
opens
a
backdrop
place
to
inside
and
says
well
what
has
all
the
pieces
I
need?
I'm
just
gonna
start
using
it
like
the
install
profile.
We
have
does
some
stuff,
but
it's
not
really
for
anyone.
D
So
if
we
were
to
come
up
with
a
couple
of
install
profiles
for
core,
like
you
know,
a
blog
or
a
calendar,
or
something
like
that
and
then
so
when
people
are
installing
backdrop
with
a
few
different
choices
of
install
cohorts
are
actually
geared
towards
things,
a
lot
one
being
most
important,
because
if
we
want
to
do
any
sort
of
wordpress
import,
if
we
had
an
install
profile
that
mimics
WordPress,
then
you
can
sort
of
install
a
wordpress
version
of
backdrop
on
install
and
then
just
import.
The
data
I
would.
A
Love
it
if
we
can
make
our
default
profile
the
wordpress
blog
profile.
So
I
and
I
think
that
I'd
like
where
you
on
that
mike
but
I'd
like
to
see
the
other
profiles
existing
country
first
and
then
we
move
them
in
the
for
later,
but
if
we
can
work
on
making
our
default
profile
that
one
here
talking
about,
I
think
that
would
get
us
a
long
way.
Yeah.
C
The
concept
that
we
have
is
that
the
default
install
profile
should
be
the
blog,
because
that's
about
the
only
like
common
thing,
or
we
can
kind
of
assume
that
most
sites
are
going
to
have
they'll,
probably
extend
on
top
of
that
quite
a
bit,
but
the
default
install
situation
is
supposed
to
be
the
blog.
Maybe
another.
D
One
that
could
be
yes,
I
think,
if
we
continue
to
refine
our
current
install
profile,
maybe
just
to
make
it
as
wordpress
e
as
possible
blocks
and
everything
just
so,
we
can
have
a
data
import
that
just
sets
up
everything.
That's
already
in
a
wordpress
blog
yeah.
That's
something
I
think
the
other
core
install
profile
we
could
have
is
a
portfolio
site
and
sort
of
compete
with
sort
of
the
square
spaces.
C
Yeah
so
to
dampen
this
too
much,
but
I
like
to
I'm
nervous
about
adding
more
options
to
the
installer
I'm,
always
like
the
time
zone
related
thing
like
I'm,
trying
to
remove
things
from
the
Installer
as
much
as
possible,
just
because
it
speeds
the
like
initial.
First
impression,
you
know
it's
like.
Oh,
this
thing
is
really
simple,
because
I,
don't
I
just
clicked
a
button
and
it
was
installed.
It's
like
that's.
C
C
It
doesn't
present
me
with
functionality,
questions
it
just
installs
and
then,
when
I,
like,
oh
I,
want
to
portfolio
I,
go
to
the
install
modules,
page
and
type
in
portfolio
and
then
I
click
a
button
and
then
my
portfolio
is
set
up.
You
know
like
that's
like
what
you're
saying
like
functionality.
Wise
it's
like
might
be
an
install
profile
that
runs
later,
but
it
would
be
done
like
then.
D
D
D
A
A
I
mean
I
think,
let's,
let's
not
worry
too
much
about
in
software
files
right
now,
because
nobody
knows
how
to
use
them.
I
think
like
in
terms
of
that,
like
let's
make
a
decision
before
we
install
the
software,
it's
just
not
really
a
thing.
I
think
that
we
can
focus
on
make
like
doing
what
he
said
about
making
default
backdrop
be
as
much
like.
Wordpress,
that's
going
be
a
big
win
and
people
don't
have
a
problem
with
WordPress
being
like
to
feature-rich
like.
A
If
you
want
to
make
that
portfolio
the
WordPress
site,
you
start
with
WordPress
and
you
add
stuff
to
it
and
I
think
that's
kind
of
the
same
model.
We
should
use
and
backdrop.
Let's
start
there
adds
up
to
it
and
if,
if
the
things
we
end
up
adding
to
it,
those
are
install.
Profiles
are
whatever
they
end
up
being
end
up
like
overriding
your
home
page
layout
with
the
different
layout.
That's
fine!
So
it's
a
decision.
A
Somebody
means
like
I,
want
a
portfolio
say,
click
the
button
and
now
your
portfolio
site
and
as
long
as
there's
a
way
for
them
to
say
I
want
my
blog
site
back,
go
and
install
whatever
overwrite
again
like
we
can
overrides
many
times
as
we
want
for
sure
any
customizations
are
gonna,
be
lost,
but
that's
kind
of
you
know
that's.
That
would
be
true
if
you
want
install
the
module
or,
if
you
you
know,
it's
that's
just
kind
of
the
way
it
works.
D
Okay
I
mean
this
is
just
a
discussion
on
things.
I
mean
it
sounds
like
yeah
I,
just
I,
just
think
that
we
should
sort
of
codify
what
we're
looking
for,
because
if
people
do
start
building
distributions
or
features
and
stuff
like
that,
and
they
try
to
use
install
profiles,
older
they've
traditionally
been
used,
then
it
could
be
problematic
down
the
line.
So
it's
sort
of
like
I,
think
we
should
come
up
with
guidelines
for
how
install
profiles
are
supposed
to
work
and
then
maybe
discuss
how
features
or
distributions
are
supposed
to
work
in
the
future.
D
A
I,
like
what
you're
about
the
way
to
install
profiles,
could
work
I,
think
that
sounds
way
saner
than
anything
we're
doing
now,
anything
that
we
want
to
set
up
like
best
practices
for
install
profiles
and
then
even
rework.
The
way
course
easy
needs
profiles
to
try
and
follow
those
best
practices.
That's
awesome
thing
we
can
do
in
one
that
X
cycle
and
if
we
have
to
interpret
or
also
you
can
use
like
yeah
well,.
D
That's
the
other
thing,
then
yeah,
that's
the
other
thing,
then
is.
We
would
have
more
profiles
on
backdrop.
That
Orcas
is
something
that
can
be
downloaded
just
like
you
know,
just
like
modules
and
features
like
you
know,
we
can
have
like
you
know
your
portfolio
install
profile
and
other
things
that
we
we
just
need
to
figure
out.
We
just
need
to
figure
out
a
way
to
make
it
easy
for
people
who
want
to
have
a
portfolio
site
to
install
backdrop
and
get
it
and
not
have
to
actually
drag
things
to
their
port.
D
C
Yeah
and
right
now
we
don't
have
the
capability,
even
in
the
installer,
to
handle
dependencies
like
if
a
dependency
is
specified
it
it
downloads
at
first
minute,
says:
oh,
you
also
need
to
install
these
things,
which
is
a
little
bit
cumbersome
like
it
would
be
awesome.
It
could
figure
out
like
I,
want
to
install
I.
C
C
Sometimes
you
know
a
module
might
per
any
integration
with
four
other
modules
like
a
module
might
have
like
like
rules,
integration.
That
is
a
separate
module.
That
depends
on
rules
module,
but
you
don't
necessarily
need
to
turn
that
module
on
you
don't
need
rules
so
about
this
already
or
not.
Now,
I,
don't
think
so
this
right
now
it's
it's
just
a
known
thing
that
when
you
download
modules
it
doesn't
download
the
dependencies,
but
when
you
go
to
turn
them
on
it'll,
say:
hey!
You
need
these
two
extra
modules
before
you
can
proceed.
I
have.
D
C
And
and
also
I
totally
think,
we
should
proceed
with
deprecated
the
functionality
for
modules
to
be
in
profiles.
Yeah
I
think
that
we
can
like
just
discuss
how
to
deprecated
it
and
then
make
that
be
a
thing
like
without
any
blocking
whatsoever,
because
I
think
just
about
everybody.
It's
gonna
be
on
the
same
page.
There
that
holding
your
modules
in
the
modules
directory
isn't
much
saner
thing
to
do
then
put
it
in
the
profiles
directory
yeah.