►
From YouTube: Backdrop Weekly 12/8
Description
Today’s development agenda: http://bit.ly/2gET7Sl
A
Phpstorm
licenses,
those
have
been
renewed
and
I
think
the
way
that
works
is
that
she
took
all
of
the
ones
that
we
had
and
handed
out
yet
and
converted
them
into
a
different
kind
of
license.
So
now
it
covers
more
than
just
phpstorm
there's
some
other
products
that
you
can
get
with
it.
So
I
would
say
anyone
who
currently
has
a
license
probably
isn't
going
to
have
access
to
that,
but
we
have
a
handful
more
to
get
up.
A
So
if
you
need
a
phpstorm
license,
you
want
to
try
all
the
cool
new
stuff
that
they're
giving
away.
Let
me
know,
send
an
info,
an
email
to
input
backdrop
see
Miss
toward
the
new
ones
should
be
good
for
a
year
from
now.
So
that's
it
I,
don't
know.
If
anyone
else
has
any
other
updates
can
see
wise.
We
haven't
been
doing
much
lately,
but
moving
on
infrastructure
tasks.
We
are
working
on
backdrop,
CMS
org.
A
A
Section
and
wes
is
working
on
a
redesign
and
reef
aim
of
backdrops
esto
org.
The
theme
is
mostly
the
same
with
the
a
separate
lyric
and
have
a
left
sidebar
anymore.
So
all
of
our
layouts
that
have
the
drawer
are
being
replaced
with
the
new,
probably
core,
layouts
that
we're
using
that
use.
This
and
he'll
that'll
make
some
of
our
theming
a
little
less
crazy,
so
the
reteam
isn't
going
to
actually
be
a
rebrand
in
any
way
other
than
the
homepage
being
significantly
invert.
A
So
we're
hoping
to
have
that
done
by
the
launch
of
backdrop
16.
So
hopefully
we'll
have
a
new
homepage
on
january
fifteenth.
But
if
we
end
up
having
a
bunch
of
stuff
that
West
needs
to
work
on
between
now
and
then
on,
vac
top
16
itself,
the
new
homepage
will
go
out
after
the
new
product.
We're
also
excited
to
start
working
on
our
forum,
which
is
that
something
that
we
have
needed
for
a
long
time.
A
It's
been
requested
for
a
long
time
in,
and
we
have
a
bunch
of
code,
that's
kind
of
ready
for
a
review.
It's
going
to
need
to
design
kind
of
review
to
make
sure
that
the
new
stuff
looks
like
it
looks
good
on
our
current
site
looks
good
on
the
new
site
after
the
new
launch
to,
and
then
we're
probably
going
to
need
some
user
experience.
Just
to
say
like
is
this:
what
people
want?
What
are
features
that
you
want?
The
aren't
there
are
they
possible
for
us
to
add
quickly
and
easily.
A
A
B
A
B
B
B
Sure,
okay,
so
1.6
comes
out
january
fifteenth.
We
have
creature,
feature
freeze
january
first,
which
means
we
have
one
two
three
yeah
three
weeks,
basically
plus
tomorrow,
to
kind
of
wrap
up
what
we're
going
to
be
doing
for
1.6,
which
wrap
up
might
not
be
that's
right.
They're
very
word:
we've
got
a
lot
of
work
to
do.
I
think
the
one
point
x
branch
is
still
not
a
whole
lot
different
than
the
1.5
x
branch
at
this
point,
but
there
is
a
lot
of
a
lot
of
work.
B
That's
currently
in
progress,
first
of
which
is
the
reference
module
and
the
reference
module
didn't
make
it
into
the
last
release
and
we're
hoping
to
thank
you
21.6.
Its
main
issue
is
1301,
but
the
primary
place
for
development
is
happening
is
in
github
com,
/
backdrop
dash
contribs,
/
reference
a
contribute
in
stead.
B
There
has
been
some
work.
Jeff
has
done
to
make
some
initial
testing
things
for
reference
module,
which
is
fantastic.
Thank
you,
Jeff.
It's
not
yet
merged
into
the
project,
but
couldn
t
need
some
review
Jeff.
Are
you
hoping
I
imagined
for
review
for
me
on
that
tour?
Mike?
Maybe
you
could
take
a
look
at
it
as
well:
yeah
yeah,
yeah.
B
C
A
C
A
Be
little
scowl,
it's
part
of
taxonomy
module.
We
can't
keep
it
separate
that
way
and
the
I
think
like
this
is
another
thing
about
backdrops
principal
saying
that
pushing
this
burden
on
ticking
trib
is
against
what
we
believe
in
like
saying
sorry,
you're
going
to
have
to
write,
support
for
both
term
reference
and
only
produce
reputation
feature.
A
So
we
just
need
to
like
actually
something
to
measure
in
terms
of
what
we're
adding
versus
what
we're
doing
to
the
rest
of
people
using
backdrop,
and
so
I
think
like
I,
want
to
spend
some
time
looking
at
what
that
actually
feels
like
to
write
that
upgrade
path,
because
I
think
it's
going
to
be
significantly
better
for
users.
If
we
can
do
it
and
I'm
worried
that
if
we
can't
do
it
when
reference
goes
in,
we
won't
be
able
to
do
it
at
all.
Okay,.
B
C
C
A
B
Yeah,
okay!
Well,
it's
good
to
see
that
moving
along
nonetheless,
so
yeah
good
to
see
prior
Saturday
entity
view
modes
is
issued
315.
This
allows
you
to
add
custom
view
modes
like
out
of
the
box,
there's
like
a
teaser
view
mode
and
a
search
result,
view
mode
and
things
like
that,
and
this
allows
you
to
create
customized
view
modes
for
each
type
of
entity
when
managing
the
view
modes
for
a
teaser
and
like
managing
how
the
fields
are
displayed
for
each
one
of
those
few
modes,
this
one
that
actually
is
looking
really
pretty
good.
B
It
functionally
works,
but
I
think
there's
been
a
lot
of
back
and
forth
around
the
UX
of
how
these
pages
are
displayed.
How
we
deal
with
where
the
link
goes
for,
at
a
new
view,
mode
terminology
around
view
mode
versus
display
mode,
lots
of
copper
or
lots
of
conversations
happening
there
and
that's
a
315
issue.
B
I'd
like
to
get
my
own
personal
review
on
this
as
well.
I've
been
looking
at
it
and
even
though
it
works,
you
know
we
have
to
figure
out
some
consistency
issues.
There
there's
also
been
a
lot
of
suggestions
around
ways.
We
can
handle
this
better,
but
those
better
ways
are
introducing
new
UX
patterns
that
we
don't
use
real.
B
Frequently,
or
possibly
at
all
in
some
places,
so
anyways
lots
of
great
discussion
there,
yeah
I
think
it
would
be
best
if
we
can
you'd
be
consistent
with
parents.
We
have
right
now,
because
that
is
also
being
consistent
is
also
the
easiest
thing
to
do,
because
if
we're
not
introducing
anything
new,
then
we
already
have
all
the
tools
in
place
to
to
use
the
existing
patterns.
B
A
A
That
is
ended
a
table
with
draw
buttons
like
the
rest
of
our
you
guys,
rather
than
lichfield
sets
with
edit
links,
which
is
what
it
was
and
can
trim
and
I
also
wrote.
I
made
some
changes
to
the
form.
I
think
it
was
based
on
my
suggestion,
where
we
should
be
able
to
select
the
entity
type
and
then
it
does
look
at
ajax
reload
and
show
do
the
bundle
type
selection.
So
you
don't
have
to
have
a
specific
ad
path
for
each
entity.
A
So
it's
a
little
different
I
think
it's
better,
but
I
would
love
to
get
more
people's
opinion
on
whether
it's
actually
better.
It's
just
a
friend
and
yeah
I.
Think
it's
looking
great
in
terms
of
the
functionality
it
works.
It
does
what
it's
supposed
to.
We
just
need
to
find
a
way
to
meet
the
user
interface
makes
sense
to
people.
A
B
From
an
implementation
perspective,
the
block
copy
one
is
a
lot
simpler
and
works
in
a
way
that
I
think
people
would
more
likely
expect.
That's
issue
20
to
45,
but
there's
also
region
copy
block.
That's
in
eighteen.
Eighty
six,
both
of
these
pull
requests,
although
they
work
really
to
kind
of
bring
up
some
concerns.
For
me,
that's
where
we
basically
are
creating
interdependencies
from
one
layout
to
another
layouts
and
actually
finding
like
which
layout
provides
like
the
master
block,
can
be
a
little
bit
tricky.
There's
also
a
little.
B
I
posted
some
feedback
in
about
the
way
that
the
drop
down
for
the
list
of
blocks
has
created
it's
a
little
bit
overwhelming,
showing
every
layout
every
block
in
every
way
out
all
in
one
giant,
drop-down
select
list.
So
there's
some
good
ideas
in
here.
The
implementation
is
really
pretty
simple
for
both
of
them,
but
I'm
worried
about
the
long-term
repercussions
of
what
we
could
be
getting
ourselves
into
making
these
dependencies
in
between
layouts
just
from
a
actual
site
management
perspective.
B
It's
simply,
could
you
be
convenient,
but
also
really
difficult
to
keep
organized
if
we're
just
referencing
blocks
in
between
arbitrary
layouts
could
make
for
a
site
management
headache.
In
my
opinion,
some
more
feedback
would
be
appreciated
on
those
I'm,
I'm
not
sure
if
the
current
approaches
are.
What's
that
we
want
to
stick
with,
but
that's
why
we
need
additional
feedback
on
those,
because
I'd
love
it
if
other
people
had
other
people
wait
in
as
to
whether
or
not
they
felt
even
the
current
approach
would
be
something
that
they
would
use
on
a
regular
basis.
B
It
looks
like
okay
this
this
is
this
issue
that
I
just
mentioned.
2375
is
not
the
entire
meta
issue,
which
is
at
1448.
It's
a
sub
issue
that
looks
like
Jenna's
been
working
on.
That
is
really
just
about
providing
a
listing
of
files
and
an
interface
to
a
bulk
manage
them
so
that
you
could
find
a
file
in
your
entire
system
and
then
delete
it
or
replace
it
with
a
different
file,
or
something
like
that.
B
B
E
A
C
D
C
A
Looked
into
a
little
bit
so
just
for
you
guys
that
aren't
where
I
wanted
to
put
the
file
usage
count
on
there,
you
can
see
like
a
quantifier
was
referenced
in
law
school
places
that
it
was
used
in
multiple
places.
But
as
soon
as
you
added
join
to
file
usage
from
file
managed
all
of
the
rows
duplicate,
so
I
think
it
might
just
be
a
problem
with
the
views
in
agreement.
A
I
tried
the
reduced,
duplicates
checkbox
and
then
there's
like
a
seriously
reduced,
duplicates
check
box
as
well.
It
didn't
seem
to
do
anything
I'll,
try
again
after
I,
guess
drinking
put
the
view
bag
and
see
how
our
plans
will
get
0
drupal
sevens,
fused
integration
worked
and
make
sure
that
we
have
it
the
same
I
think
there
might
have
been
changes
to
that
since
our
family,
a
niche
thing
went
in
so
yeah.
B
Once
that
gets
back
up,
I'd
like
to
take
a
look
at
that
as
well,
I
think
God,
if
you
haven't,
tried
it.
The
turning
on
the
aggregate
aggregate
rows
option
made
all
standard
query.
Options
is
probably
also
what
we
want,
because
that
enables
doing
stuff
like
count,
queries
and
some
queries,
and
things
like
that
and
I
think
that's
what
we
need,
because
the
same
file
can
be
used
in
multiple
different
places
and
multiple
times
within
those
places.
A
B
I'm
actually
saying
that
the
data
structure
itself
does
cause
duplicates
because
that's
the
way
it's
stored
in
the
database,
but
actually
doing
a
query.
If
you
were
to
write
this
out
when
I
join
and
then
it
requires
doing
a
some
query
in
order
to
together
is
the
multiple
rows
to
give
it
to
actually
determine
the
total
number
usages
anyway.
Work
I
think
both
yeah.
F
C
B
B
A
Just
say,
I
think
it
was
here
and
we
were
talking
about
you
know.
Last
week
we
were
talking
about
we're
moving
things
from
the
list
that
weren't
possible.
They
had
done
by
1.6,
and
so
that's
why
this
one
says
it's
possible
because
it's
gonna
be
really
hard
to
get
it
to
work.
But
it's
not
actually,
but
it's
not
impossible.
So
I
would
say.
B
C
C
So
basically,
it
should
be
backwards,
compatible
perfectly
fun.
Until
you
add
a
page
title
block,
it
still
displays
the
page
title
where
it
is
so
we're
not
breaking
the
API
or
the
functionality
we
might.
We
might
want
to
remove
that
conditional
statement
then
and,
like
you
know,
to
exit
backdrop,
because
then
you
can
just
assume
that
people
use
the
block,
but
for
the
time
being
it
should
be
fun
right.
A
A
Think
I
were,
there
are
a
lot
of
intricacies
that
we
have
to
look
into
when
we're
working
on
it,
because
it
is
intended
to
work
the
way
it
works
now
and
not
the
way
we
want
it
to
work
but
I
think
like
at
the
very
least
we
can
in
theory
we
can
add
the
blocks,
I'm,
not
sure
the
ramifications
of
what
will
happen
after
that.
So
that's
why
it's
like.
A
B
A
B
A
B
B
A
We
want,
we
want
to
be
able
to
create
content
that
does
not
have
a
path.
Things
like
slideshow,
slides
or
items
will
only
appear
in
any
kind
of
you
like
the
list
of
commissioners
or
whatever,
there's
lots
of
different
ways
that
Drupal
solve
this
problem.
It
would
be
fantastic
if
we
could
make
a
decision
about
which
one
we
want
to
pursue
for
backdrop
and
move
towards
putting
it
in,
for
we
haven't
been
able
to
make
the
decision
we
have
sort
of
an
idea
of
which
pack
that's
easiest,
but
we're
not
entirely
sure
it's
easiest.
A
C
B
C
Then
there
was
the
other
issue
that
I
think
that
the
entity
API
makes
the
assumption
that
all
entities
have
paths
so
so
I
think
that
was
the
thing
that
we
had
to
look
at
next
was
like
hey.
Can
we
even
create
an
entity
that
doesn't
have
a
pass
because
all
I
think
the
system
actually
that's
going
to
baked
into
the
entity
API,
which
we
can't
really
change.
B
C
Mean
we
could
definitely
we
can
definitely
remove
the
Hat
aliases
for
for
them,
but
I
think
they
still
need
paths
to
actually
view
and
whether
I
mean
theoretically,
we
could
see
if
we
can
change,
make
a
change
to
the
entity
API
that
so
it
doesn't
need
a
view
thing
or
automatically
redirects
to
the
edit
or
something
like
that,
but
I'm
not
sure.
Hopefully,
if
we
can
do
that
without
making
things
complicated
yeah,
I
would
say
I
would
say
bump
this
just
because
I
think
we
have
enough
on
our
plates
other
stuff.
C
B
B
B
Ok,
next
time,
Oh
X
item
on
the
list
is
bread,
crumbs
and
menus
clean
up.
This
is
actually
a
different
issue
than
was
in
agenda
last
week.
It's
2156
is
the
issue,
and
this
is
a
suggestion
by
Gregory
to
correct
the
way
that
we
handle
breadcrumbs
menu
title
or
the
title
in
the
header
of
the
page,
as
well
as
the
the
title
and
the
h1
tag.
So
the
HTML
head
title,
the
page
title
the
breadcrumb
and
the
tabs
basically
reworking
the
way
the
menu
system
displays
those
things
to
be
consistent
across
the
board.
B
Right
now,
we've
been
solving
this
issue,
primarily
by
using
like
backdrops
that
title
in
various
places
to
make
the
menu
make
sense
or
make
sense
in
a
way
that
we
think
is
better
than
what
was
there
by
default.
I
mean
potentially,
this
would
change
the
way
the
menu
system
itself
functions
to
to
be
to
provide
like
a
consistent
structure
all
the
time
for
us.
B
C
B
E
Probably
have
some
time
I
mean
I'm
in
theory,
in
theory,
I
mean
I'm
a
whole
day.
I
might
have
some
time,
I
just
give
it
a
couple
of
weeks
and
if
not,
then
we're
pushes
maybe
maybe
a
week
so
yeah
I'll
see
you
put
something
with
a
simple
stuff,
at
least
that
don't
mess
way
too
much
with
the
menu
routing
system.
E
B
E
B
Okay
and
finally,
the
last
issue
that
we
have
in
this
listing
is
improving
the
rich
text,
editor
and
ongoing
meta
issue
at
issue.
1087
yeah,
the
items
that
can
be
implemented
in
there
is
basically
pick
and
choose
any
individual
one
ivan.
I
saw
a
gem
looking
at
spell
checker
again
today,
but
I
haven't
actually
tracked
with
which,
if
any
of
these
has
been
making
progress
for
1.6,
it.
A
Don't
think
any
progress
on
any
of
them,
but
I
just
had
an
issue
today
on
one
of
my
drupal
7
sites.
With
the
spell
check,
and
so
I
was
checking
to
see
what
we
did
in
backdrop,
I
thought
we
had
an
issue
to
enable
browsers
built
in
spell
check,
but
they
couldn't
find.
That
anywhere
is
that?
Did
that
get
committed
with
the
update
to
seek
editor
that
when
in
was
it
in.
B
B
B
A
A
It's
totally
fine
it
does.
It
spell
checks
correctly,
the
prep,
the
reason
that
you
might
want
the
spellcheck
plugins
as
I'm
running
to
own
the
other
site
is
that,
depending
on
people's
operating
systems
and
browser
settings,
they
might
have
turned
off
spell
check
and
don't
know
how
to
turn
it
back
on
or
as
if
you
have
a
button
and
editor.
You
can
push
the
editor
and
I'll
always
spell
check
the
code
in
the
editor.
So
particularly
like
there's
some
really
crazy
issues
with
chrome
on
mac
about
built
in
spell
checking.
A
So
it's
just
a
lot
easier
for
people
to
push
the
button
and
figure
out
how
to
use
their
own
software.
So
that's
the
the
reason
people
might
want
the
spellcheck
plugin,
but
I
think
that
disabling
the
built
in
spell
check
is
weird
and
we
should
turn
it
on
and
then
for
people
who
want
the
spellcheck
plug-in
and
there
could
be
a
contribute,
have
the
problems
that
exist
in
the
world
for
and.
C
B
B
B
Yeah
aren't
really
like
really
exciting
features,
but
just
like
some
of
them
like
a
really
big
one
like
replace
color
module,
for
example,
Wes
isn't
here,
but
that's
that
Advent
I
think
for
him
all
working
out
basis,
but
I
think
that
that
is
slips
in.
You
know
priority
from
other
stuff,
which
is
fine.
That's.
It
is
a
reason
why
we
try
to
focus
our
focus.
Our
efforts
and
those
other
items
are
all
just
kind
of
you
know
great
to
have,
but
you
know
not
at
all
expected.
B
Okay,
that's
it
for
the
1.6
release.
We've
got
a
lot
of
work
to
do
in
three
weeks
to
do
it
it.
It
is
great
to
see
that
there's
been
a
lot
of
progress
on
a
lot
of
issues
and
there's
more
progress
in
issues
that
have
been
mentioned
directly
in
this
meeting
that
are
also
rather
exciting.
So
that's
it
for
the
1.6
update
and
where
we
are.
We've
only
got
10
minutes
before
the
end
of
the
meeting,
but
that's
more
than
enough
time
to
do
the
community
current
section.
Take
it
away,
Gregory
things.
E
So
we
have
7651
downloads,
that's
plus
431
one,
since
since
last
time
we
did
the
community
stats.
We
have
342
total
projects
on
patch
obscene
44
batch
of
CMS,
that's
plus
12.
You
have
387
user
accounts
or
backdrop
CMS,
though
that's
plus
16
since
last
time
and
then
51
total
backdrop
country
office,
which
is
plus
1
and
welcome
big
welcome
to
Alex
kingdom.
So
that's
it.
G
G
B
Yeah
findingking
trip
I
think
it
may
be
possible
to
put
it
in
our
existing
drush
extension
because
I
existing
drush
extension.
It
does
include
a
bootstrap
class.
Yes,
but
right
now,
it's
it
basically
doesn't
do
any
like
command
rewriting
unless
the
bootstrap
class
is
used,
but
it
actually
contains
commands
itself,
I,
believe.
Ok,
we
can't
override
the
brush
dl.
B
G
B
A
B
B
Let's
see
upcoming
events,
we
have
a
calendar
at
backdrop,
CMS
/
events,
there's
also
an
ical
feet.
You
can
pull
out
of
the
agenda
and
I
think
it's
also
there
on
that.
/
events,
page
I,
don't
think
that
we
have
any
that
are
being
calling
this
meeting
currently,
so
that's
it!
Now
we
go
into
a
general
discussion,
QA
anything
else
that
we
would
like
to
bring
up
to
talk
about
right
now
or
something
that
we
talked
about
next
weekend.
We
could
put
it
on
the
agenda.
We
need.
C
Well,
ok,
I
wanted
to
I
added
a
message
to
the
Phillippe
MC
actually
take
a
look
at
the
the
drupal
issue
for
the
configuration
storage
thing,
and
this
is
definitely
not
something.
I
think
that
we
should
tackle
this
release,
but
we
might
well
consider
looking
at
for
next
release
and
beyond
and
unless
sure,
if
you've
seen
the
latest
nate.
I
made
a
comment
earlier
in
the
thread
and
you
did
a
lot
of
work
and
looking
at
the
pull
request
for
for
doing
the
configuration
management
database,
the
the
thread
is
included.
C
A
lot
of
discussion
like
oh.
This
is
an
edge
case
and
stuff
like
that.
But
I
was
actually
thinking
that,
like
you
know,
after
using
both
backdrop
and
d8,
it
makes
a
lot
more
sense
to
keep
the
active
configuration
in
the
database,
and
so
I
was
actually
suggesting
that
we
take
a
look
at
maybe
actually
changing.
The
default
database
store
the
data.
This
default
configuration
storage
to
use
the
database
instead
of
the
files.
B
Yeah
I
go
about
twice
on
that
one
I
do
think
it
might
be
a
good
idea
for
us
to
do
one
thing
at
a
time,
possibly
and
add
it
as
an
option
yeah
and
then,
because
I
think
we
actually
could
at
it
as
an
option.
This
release,
because
the
code
is
quite
functional
at
this
point
and
then
decide
on
on
switching
it
to
fall
at
some
at
some
point,
I
something
more.
A
C
I
I,
don't
think
we're
going
at
the
ridge
I'm
not
saying
this
is
something
that's
only
useful
for
things
I'm
saying
that
the
vast
majority
of
sites
would
be
better
served
by
storing
the
configuration
the
database
I'm
not
really
worried
about
the
edge
cases
and
people
who
wanted
to
do
it.
One.
The
other
I'm
saying
by
default,
having
the
configuration
database
is
a
fuckload
easier
than
having
a
separate
configuration
location
I
mean
I.
A
A
The
issue
several
times,
if
you
want
to
read
it
but
having
a
place
that
people
can
see
like
when
I
save
this
file.
This
is
the
value
like
there's
an
understanding
of
life.
This
configuration
gets
saved
into
this
file.
It's
like
very
transparent
and
easy
for
people
to
understand
where
it's
like
saving
it
and
putting
in
the
database.
It
doesn't
look
any
different
from
the
outside
quadruple,
save
stuff
and
put
in
database
I
purple.
C
A
B
I
think
that
there's
a
good
situation
here,
where
it's
like
okay
for
a
beginner
developer.
It's
really
easy
to
see
the
files
changes
in
the
file
system,
like
that's
great,
for
beginning
developer.
But
if
you
go
one
tier
lower
than
that
which
is
potential
users
or
site
builders
that
don't
even
understand
anything
about
the
architecture
or
where
anything
is
stored,
that
having
it
be
seamlessly
part
of
the
database
in
an
invisible
location,
could
actually
be
considered
easier.
B
Yet
and
that's
that's
the
way,
a
system
like
WordPress
functions
and
that
there's
the
database
and
that's
it,
and
so
when
it
comes
to
moving
your
site
around,
you
move
the
database
and
that's
a
much
easier
thing
to
deal
with
then
making
sure
that
your
database
near
config
directory
are
always
tied
together
because
they
are
very
much
dependent
on
each
other.
But.
B
But
even
the
actual
concept,
downloading
your
configuration
only
or
any
kind
of
configuration
management
at
all
is
actually
a
higher
concept
than
many
end.
Users
would
even
understand
in
the
first
place
like
for
an
end
user.
The
problem
of
configuration
and
content
being
separated
from
each
other
being
important,
probably
doesn't
even
register
as
a
problem
in
their.
D
B
A
That's
true,
but
I
also
think
that
making
the
concept
of
configuration
management
harder
for
those
people
to
understand
is
a
big
deal
and
like
saying
okay,
this
is
something
you're.
Never
going
to
need
to
understand
is
fine,
but
then,
when
you
say,
oh
actually
there's
this
tool
we
built
for
you
and
you
mark
and
understand
it.
It's
different
than
saying
there's
this
tool
we
built
for
you
in
here.
It's
really
straightforward.
You
can
see
how
it
works.
I,
don't
know,
I
feel
both
ways
on
this
issue.
A
I
feel
like
I,
I,
I
looked
at
the
code.
It
looks
clean.
It
looks
good
I
wish.
We
didn't
have
to
force
this
on
all
of
our
users,
especially
existing
sites.
So
if
we
can
figure
out
a
way
to
like
introduce
it
as
a
setting
first
and
then
being
backed
up
to,
we
have
like
a
way
to
get
into
it,
but
I
wouldn't
want
to
like
make
all
the
sites
that
people
already
understand
think
they
understand
change
the
way
they
work.
Oh
no.
B
A
C
And
I
am
suggesting
to
make
it
the
new
default
I'm
not
suggesting
to
like
go
back
and
change
how
people's
current
sites
work,
but
that
we
have
it
as
a
new
default
way
is
the
store
in
the
database.
The
other
thing
that
I
would
look
at
is
hosting
I
would
say
we
should
really
see.
We
should
really
define
like.
We
should
see
how
our
users
are
currently
hosting
their
sites
and
how
we'd
like
to
see
them
hosting
their
sites.
C
I
think
that
having
configuration
files
where
people
can
ftp
up
to
their
site
and
look
around
is
one
thing,
but
if
there
and
that
sort
of
makes
things
like
easier
and
you
could
show
them,
but
if
they're
using
something
like
Pantheon
like
they,
don't
really
have
access
to
see
the
configuration
files
anyway
directly
on
the
live
site
or
see,
changes
happen,
or
else
like
that
and
there's
no
way
for
them
to
you
know,
use
version
control
without
importing
and
stuff.
So
I
mean
it's.
It's
like
I
feel
like
I,.
A
Like
if
our
target
audience
our
WordPress
users
and
WordPress
users,
don't
use,
get
then
providing
a
tool
that
allows
them
to
manage
their
configuration,
changes
and
get
is
sort
of
silly.
So
thinking
about
that
like
what?
What
are
people
actually
doing
with
backtrack
in
the
wilds?
With
you
get
to
measure
yeah.
C
A
C
I
think
I
think
we
should
just
like
I'm
not
suggesting
we
do
anything
for
this
release.
Like
you
know,
even
though
the
codes
mostly
there,
we
can
just
keep
it
as
a
patch
or
something
like
that
for
now
and
but
I
just
like
to
look
at
the
issue
and
I'd
kind
of
like
to
not
have
like.
Oh
my
god,
it's
violating
our
principal
discussions
and
because
well.
A
I
think
that's
the
only
discussion
we
need
to
have
like
the
patch.
The
patent
deploy,
dress,
looks
good,
it's
like
ready
to
go
and
the
reason
I
pushed
it
away
from
six
is
because
it's
like
we
need
to
look
at
an
edge
case,
feature
request
and
figure
out
what
makes
us
decide
either.
This
is
not
an
edge
case
or
we
don't
care.
We
need
to
do
it
anyway,
and
those
are
the
things
that
we
are
going
to
use
in
the
future
to
make
similar
decisions.
A
C
A
C
A
C
G
E
Tonight,
giant
my
my
is
not
enough
fun
opinion
the
work
haven't
decide.
Man
decided
on
that
as
well,
but
as
I
spied
builder
in
a
beginner,
coder
can
I
add
my
thoughts
there.
Yes
I'm.
So
heaven
d
in
mine
was
added.
What
was
changed
from
d7
was
added
to
backdrop,
because
we
didn't
want
to
stay
behind
for
what
the
aid
was
offering.
As
a
single
side.
Fielders
see
my
helps.
People
track
changes
via
jeans.
It
doesn't
help
a
simple
builder,
but
that
begs
the
question:
why
did
we
add
it?
In
the
first
place?
E
It's
sort
of
like
implies
that
it
was
a
wrong
move.
On
the
other
hand,
as
a
beginner
quarter.
It
greatly
helps
me
like,
as
Jen
said,
to
understand
what
James
has
happened
when
I
can't
it's
hard
for
me
to
go
into
the
database
to
see
it.
So
it's
helpful
but
I'm
not
sure
whether
it's
emi
was
intended
for
our
target
audience
in
the
first
place
as
a
jit
developer
thing.
E
Thing
and
having
in
mind
that
our
policy
from
the
party
Sierra,
we
favor
the
simple
user
rather
than
the
developer
right
yeah.
So
that's
what
I'm
thinking
I
was.
I
was
leaning
towards
not
on
touch
it,
we've
added
it
there,
but
then
the
more
I
think
about
it.
I'm
thinking
that
yes,
tits
are
useful
to
but
Juve
07,
which
is
what
we
say
we
branched
off
and
what
we
say.
C
Yeah
and
it
sort
of
we've
sort
of
landed
on
a
solution,
that's
different
than
both
drupal
7
and
drupal
8.
So
we
sort
of
have
a
third
way
of
doing
it.
So
that's
not
as
sort
of
one
of
the
things
I
suggesting
is
like
triple
a
configuration.
Management
actually
seems
to
work
as
far
as
the
workflow.
So
if
we
like
sort
of
copy
that
solution
that
might
make
things
a
lot
easier,
so
you
don't
have
to
explain
how
our
power
cmi
implementation
is
different
than
that
one.
C
This
is
sort
of
a
long,
long
term,
Aloha
yeah,
but
one
and
we
might
want
to
I
like
I,
feel
like
we
need
a
better
way
to
have.
This
discussion,
like
I,
feel
like
we're
sort
of
lacking
the
tools
and
that
having
this
one
big
issue
is
sort
of
creating
like
it
just
more
and
more
things,
just
pile
onto
it.
So
I'm
not
sure
whether
we
should
create
like
a
document
with
like
pros
and
cons
for
the
different
things
on.
A
Too,
putting
pros
and
cons
in
the
in
the
very
bottom
of
the
first
issue,
but
the
Rome
is
like
I
went
through
the
entire
issues
thread
to
do
that.
But
every
time
someone
has
a
comment,
there's
going
to
be
another
one,
but
I
would
encourage
like
if
you
have
another
like
anyone,
who's,
adding
a
comment
if
they
have
another
pro
work
on
the
throw.
E
A
A
Have
a
they
have
a
issue
coming
up
the
specifically
focused
on
security
and
I
thought
it
would
be
nice
to
write
up
like
our
commitment
to
release
patches
for
every
security
release,
as
opposed
to
just
tar
balls
and
how
and
like
all
the
stuff
we
discussed
earlier
this
summer
about
trying
to
make
security
fixes
easier
on
existing
maintainers,
but
I
don't
have
time
to
do
it
this
month.
This
looks
probably
no
one
is
dying
this
month,
but
I'd.