►
From YouTube: Backdrop weekly 1/1
Description
Happy New Year! Let's check in on Backdrop CMS progress, and prepare for our release of 1.0.0!
A
Alright,
we
are
live,
it
is
2015
Happy,
New,
Year
everybody,
it
is
January
first,
this
is
our
first
backdrop:
CMS
weekly
progress,
meeting
up
2015
and
we
are
imminently
close
to
release
of
backdrop.
One
point
0
point
0,
which
makes
everything
super
exciting.
So
today
we're
just
going
to
go
over
our
weekly
agenda,
just
a
little
status
report,
where
we
are
what
we're
working
on
what
needs
the
most
attention
and
other
potential
issues
we
may
need
to
discuss
for
the
project
going
forward.
So
first
thing
on
our
list.
A
A
They
encounter
things
they
like
things
they
don't
like
and
depending
on
how
big
changes
are
based
on
their
feedback,
we
might
even
be
able
to
incorporate
some
of
those
changes
before
the
one
point
0
release,
and
we
also
have
a
bunch
of
minor
task,
clear
working
on
between
now
and
release
date
and,
of
course,
the
once
they
get
done
before.
Then.
A
We'll
probably
get
in
a
depending
on
how
solid
they
are,
and
once
the
don't
will
not
so
that's
kind
of
what
we're
looking
at
right
now
and
one
thing
that
we
should
talk
about
in
this
meeting
is
our
potential
timeline
for
what
comes
after
we
release
one
point,
0
point
0
and
we've
talked
about
how
one
of
the
things
that's
going
to
differentiate.
Eight
the
way
backdrop
verse
from
the
way
Drupal
work
just
that
we
want
to
have
measured
and
scheduled
releases.
A
So
that
means
we
need
to
decide
what
comes
in
weight,
which
release
and
when
that
release
will
happen
and
unlike
Drupal
work
in
a
stick
to
releasing
something
on
that
date.
Even
if
that's
something
doesn't
include
the
features
we
originally
intended
to
include
so
one
point,
0
point
0
will
come
out
and
then
we
need
to
decide
what
is
going
to
be.
A
In
one
point,
one
point:
oh,
and
when
that
will
come
out
and
that'll
be
our
next
release,
so
we
need
to
figure
out
what
our
release
schedule
is
going
to
look
like
and
what
will
be
included
in
each
further
release.
So
we
have
a
couple
of
things
on
the
agenda
here.
The
first
one
is
a
potential
three-month
release
cycle.
The
second
one
is
what
I'd
like
to
propose,
which
is
a
four-month
really
cycle,
so
this
is
woody,
be
either
four
releases
per
year
or
three
releases
per
year.
A
Originally
I,
really
like
the
idea
of
having
one
release
for
quarter
that
sounded
nice
and
organized
to
me.
But
when
I
started
taking
a
look
at
the
dates,
those
releases
would
fall
on,
it
seemed
like
they
were
pretty
close
together
and
if
we're
going
to
be
adding
significant
new
features
like
WYSIWYG
incor
half
ago
and
token,
it
seemed
like
we
might
need
more
time
between
each
of
those
releases
in
order
to
get
those
done.
A
So
for
those
of
you
who
are
watching
the
video
and
not
looking
at
the
agenda,
the
three-month
release
cycle
would
have
the
1.1
release
on
April
fifteenth
1.2
on
July
fifteenth
1.3
on
October,
fifteenth
and
1.4
on
january,
fifteenth
next
year
and
Nate.
What
is
your
initial
reaction
to
that?
Does
the
those
also
seem
too
close
together
for
you.
B
A
B
Well
doing
those
three
in
three
months
would
be
one
heck
of
an
accomplishment,
so
I
don't
think
that
that
aligns
with
what
we've
slated
for
1.1,
but
we
can.
We
can
think
about
this,
and
you
know
approaches
from
a
different,
a
different
tack,
but
symphony
does.
Since
jen
I
went
to
the
symphony
conference
a
couple
months
ago
we
talked
with
them
about
how
they
handle
releases,
and
it's
kind.
C
B
An
interesting
approach
where
they
follow
a
policy
of
not
feature
based
releases,
they
don't
even
plan
what
features
are
going
to
be
in
each
upcoming
release.
Instead,
they
just
keep
working
on
a
feature
for
potentially
you
know.
Maybe
it's
two
weeks,
maybe
it's
two
years
until
it's
finished
and
then
when
they
merge
it
in
they
say:
okay
now
this
is
going
to
be
in
the
next
money
release,
and
so
they
don't
actually
schedule
any
of
their
functionality,
but
they
require
all
functionality,
be
absolutely
completely
finished
by
the
tenants
merged,
and
then
they
don't,
like.
B
B
Yep
or
if
there's
like
you
know,
20
features
and
at
all
at
once,
just
because
all
the
work
I've
done
all
at
once,
then
that's
just
another
mining
release,
and
so
it's
an
interesting
approach
where
they
basically
forcibly
make
new
minor
releases
every
quarter.
I
think
it
is
regardless
of
what's
in
there
or
what
is
not
in
there.
So.
A
What
I
would
like
us
to
do
is
to
stick
to
our
principles
in
terms
of
actually
planning,
what's
going
to
be
in
a
release,
rather
than
just
saying
whatever
gets
done
gets
done,
but
I
would
like
to
stick
to
the
symphony
model
of
issuing
or
release
on
the
date,
regardless
of
what
gets
in
it.
So
that
way
like
we
can
say,
you
know,
1.1,
we'll
plan
on
having
WYSIWYG
token
path
auto.
But
if
1.1
comes
down
and
all
we
have
is
a
rich
text
editor
in
core,
we
still
ship,
yeah,
yeah.
B
A
We're
sticking
to
our
idea
of
like
we
release
whenever
we
say,
but
we
we
have
a
focus,
whereas
the
problem
with
Drupal
is
that
they
never
had
a
focus.
Now
she
said:
oh
well,
just
release
wolf
or
whatever's
in
it,
and
then
there
was
no.
Nobody
had
any
idea.
What
was
coming
and
I
think
that's.
What
we're
trying
to
avoid
by
having
planned
and
measure
releases
is
that
people
do
know.
What's
coming
and
that'll
give
a
place.
You
know,
I
want
to
work
on
something
okay.
A
A
Don't
actually,
we
don't
actually
know
what
you
look
like.
We
say
we're
competing
Junior,
15th,
we're
gonna
release
on
junior
15th
and
if
that
doesn't
include
whatever
it
is,
we're
working
on.
That's
fine
it
ships
anyway,
and
even
even
if
the
tag
includes
nothing
they're,
still
a
tag
on
that
date.
That's
the
same,
as
you
know,
all
of
the
bug,
fixed
versions
or
whatever,
and
it
goes
out
like
that
yeah.
B
A
Or
talk
remotely
use
a
date
and
stick
to
it
is
because
that's
what
the
business
world
wants
to
know
is
like.
I
need
to
allocate
money
for
my
website
for
next
quarter
am
I,
gonna
have
to
update
it
or
not,
and
the
business
world
around
dribble
has
been
struggling
this
for
a
long
time
or
like
do
I,
try
and
request
extra
funds
to
upgrade
the
website
or
not.
A
It's
always
kind
of
a
gamble
like
oh
well,
we
don't
know
if
there's
going
to
be
an
update
next
next
month
or
not
it
might
be
next
year
might
be
five
years
from
now
and
I
think
that
if
we
can
start
to
build
an
ecosystem
that
the
the
companies
that
run
the
software
that
the
business
world
needs
to
adjust
to
in
a
way,
that's
more
predictable,
that'll
be
better
for
backdrop,
or
we
can
say
we're
going
to
have
a
release
three
times
a
year.
A
A
C
C
And
from
a
marketing
perspective,
you
know
not
just
you
know,
reactive
in
terms
of
maintenance
costs,
but
but
looking
forward
into
project
planning
things
having
having
a
published
roadmap
with.
You
know
on
this
particular
day
we're
hoping
to
have
this
set
of
features
and-
and
then
you
know,
if
I'm
putting
together
development
came,
you
know
hell
if
I'm
raising
money
for
development
team
again
looked
at
that
move.
Okay,
you
know
this.
This
will
either
be
in
there
or
close
to
being.
C
You
know
we
could
go
to
dead
version
where
you
know
what
things
to
to
develop
internally,
you
know,
if
you
don't
see
in
the
roadmap,
you
know
okay,
well
we're
going
to
write
that
thing
ourselves.
You
know
like
just
having
that
kind
of
predictability.
I
think
can
help
the
future
path,
because
you
can,
you
can
set
all
the
other
pizzas
in
motion.
Knowing
you
know
what
the
technology
is
is
likely,
hopefully
trying
to
do.
That's.
A
B
Well,
I'm
actually
kind
of
fine
with
either
of
these
either
of
these
like
quarterly
or
or
three
times
a
year,
because
it
really
just
depends
on
I
mean
it'll,
just
adjust
the
size
of
what
it
gets
included
like
I.
Don't
think
that
we
could
do
a
thought,
oh
token,
and
WYSIWYG
by
April
fifteenth,
for
example.
We
might,
but
it
probably
end
up
just
being
path,
auto
and
token,
and
then
yes,
you
wait
would
just
have
to
wait
till
july,
but
I
mean
right
now
which
they
were
just
gonna
have
to
wait
until
May
anyway.
C
And
I
mean
the
the
dates
could
be
adjusted,
but
just
the
way
doing
the
four
verses
3
and
a
quarter
versus
trimester
thing
which
out
here
this
the
every
four
months
schedule
has
summer
like
nicely
as
one
big
thing,
whereas
the
quarterly
thing
we're
splitting
summer
in
half
and
I,
you
know
I,
don't
know
whether,
whether
that
matters,
whether
people
would
you
know
working
backdrop
for
the
summer,
just
having
it
having
it
switch
in
mid-july,
I'm,
not
that
matters
or
not,
but
that
just
jumped
out
at
me.
Yeah.
B
Actually,
when
I'm
really
feeling
is
them,
is
it
given?
I
mean
it
takes
a
lot
of
resources
to
do
a
release
like
we
have
to
write
up.
You
know,
release
notes
and
we
have
to
coordinate
with
people
and
in
all
kinds
of
things,
I'm
feeling
that
maybe
just
fewer
releases,
just
from
reducing
the
overhead
perspective
for
the
time
being,
would
be
a
wiser
moved
for
us,
because
it
really
does
take
a
lot
of
effort
to
make
a
to
make
a
release.
A
A
And
see
how
it
goes,
the
less
work
initial
initially,
if
we
have
like
a
more
committers,
more
people
who
are
able
to
do
things
like
you
know,
take
some
of
the
work
off
your
plate
for
reviewing
pull,
requests
and
stuff
by
next
year,
and
it
might
be
a
good
thing
to
say:
okay.
Well,
we
want
to
move
faster.
Maybe
we
have
a
whole
bunch
of
stuff
for
our
roadmap
that
are
smaller
projects
as
we're
moving
smaller
and
smaller
modules
and
decor,
rather
than
giant
ones
like
rich
text.
B
A
A
Maybe
it
releasing
backdrop
to
rather
soon
so
in
one
year,
two
years
rather
than
three
years
or
four
years,
so
I
think
it
would
be
good
to
reevaluate
next
fall,
whether
we
want
to
do
a
1.3
release
or
two
point
O
release
on
January
next
year,
just
depending
on
the
amount
of
feedback
we've
gotten.
A
If
we
need
to
change
any
api's,
just
taking
a
look
at
how
far
we've
come
in
and
what
the
community
thinks
of
the
product
would
be
good
to
kind
of
reevaluate
everyone's
happy
with
the
status
quo,
and
we
want
to
continue
week
and
then,
instead
of
looking
at
major
release,
look
at
adjusting
our
schedule
for
minorly
assist.
You
so
I
think
it'll
be
good
to
just
kind
of
work
through
the
first
year
and
see
where
we're
at
and
we
can
reevaluate
everything
next
year.
A
Alright.
So
now
that
we
have
a
time
line
set
up,
let's
talk
about
our
progress,
so
we've
got
a
couple
of
things
that
we're
working
on
between
now
and
the
release
and
the
I
think
most
important
thing
at
this
point
when
we
to
decide
how
we
want
to
solve
the
security,
the
one
remaining
security
release
that
we
have,
that
was
soft
and
Drupal
7.
A
That's
not
yet
been
softened
backdrop,
and
that
was
the
problem
that
happened
about
halfway
through
the
Drupal
7,
really
cycle,
with
image
Styles
being
generated
in
a
way
that
you
can
take
on
a
server
and
the
solution
that
went
into
Drupal.
7
broke
a
whole
bunch
of
contribs
dealing
with
image
styles
that
were
in
line
or
otherwise
created
on
servers.
A
And
so
we
wanted
to
look
at
that
solution
and
say:
is
there
a
solution
we
can
implement
that
isn't
going
to
affect
contribu
in
the
same
way
and
it
does
it
mitigate
the
risk
in
the
same
way
that
the
solution
that
was
implemented
in
Drupal,
7
jets
and
I,
think
you
know
it's
got.
It's
been
to
a
point
now,
where
most
of
contribs
has
found
some
way
to
work
around
this
problem.
A
Another
thing
to
consider
here
is
how
big
the
actual
risk
was
and
that
they
assessed
in
salt
in
Drupal.
7
I
have
a
feeling
it's
not
a
super
huge
risk,
and
so,
if
we
can
solve
it
in
a
way
that
is
better
than
nothing
but
less
than
what's
been
done
in
Drupal
7.
That
might
also
be
satisfactory.
So
I
think
we
should
maybe
take
another
look
at
that
issue.
This
issue
is
to
have
its
own
issue.
Yeah.
B
It
does
it's
pretty
poor,
yeah.
A
Issue
number
34:
it's
nice
early,
one
for
us,
take
a
look
at
the
comments,
the
different
approaches
that
we
recommended
in
there
and
see
if
we
can
come
to
a
decision
about
which
solution
that
we
want
to
use
for
that
job.
Other
things
we
are
working
on
our
there's
one
remaining
issue
of
Drupal
7
cross
Forks.
This
is
issue
4,
20
I
was
working
on
that
this
morning.
A
This
is
ready
just
take
all
of
the
other
improvements
that
are
included
in
Drupal
7
bug,
fixes
and
similar
user
experience,
improvements
and
documentation,
updates
and
merge
those
in
with
backdraft.
So
we're
not
behind
where
drupal
7
is
when
backdrop
is
released,
I'll
try
and
get
that
done
today,
and
then
we
have
a
that's
it
in
terms
of
keeping
up
with
Drupal
or
pretty
close,
which
is
good,
and
we
have
a
couple
of
things
that
we
have
been
working
on
for
our
major
tasks.
A
The
three
major
features
that
we
have
that
are
different:
cheating
us
from
Drupal
7
right
now
are
blocks
and
layouts,
which
is
our
kind
of
panels
everywhere,
equivalent
views
and
core
and
config
management.
We've
got
a
couple
of
things:
we're
working
on
an
improving
box
and
layouts.
We've
got
bullion
working
on
new
user
interface
for
us,
and
once
we
get
those
design
files
will
be
able
to
do
a
little
revamp
of
the
interface
we
have
now.
A
We've
got
CSS
and
markup
changes
going
in
thanks
to
a
front-end
review
that
we
got,
which
made
a
whole
bunch
of
sense
and
it's
going
to
require
punch
changes
for
layouts,
but
I
think
the
front
end
early
going
get
after
that
and
I
don't
know.
Nate
you've
been
doing
a
lot
of
work
on
this.
You
want
to
give
us
an
update
on
CSS
or
markup
stuff
for
layouts
yeah.
B
That's
been,
it's
been
a
really
interesting
issue
and
we
had
a
Trish
go
through
and
do
an
amazing
review
of
of
all
of
the
markup.
And
previously
what
we've
done
is:
we've
taken
the
drupal,
7,
markup
and
just
kind
of
converted
it
into
layouts,
mostly
from
the
Bartok
theme
and
then
I
kind
of
set
the
pattern
for
all
the
the
other
layout.
B
B
Basically,
all
regions
had
IDs
and
then
inside
of
them
we
had
a
div
that
had
class
of
section,
and
that
was
just
kind
of
the
way
regions
worked,
kind
of
Interpol
7
I
mean
we
got
some
Drupal
8
updates
in
there
as
well,
but
we
had
each
region
had
an
ID
and
inside
of
it
had
a
rapper
and
then
and
then
the
actual
region
content
inside
of
it
and
after
a
really
good
discussion
in
there,
we
came
to
a
lot
of
conclusions.
Things
like
the
inner
and
outer
wrappers
for
regions
is
entirely
unnecessary.
B
These
days
from
a
let
out
perspective.
Previously,
it
was
needed
because
for
IE
or
old
browser
reasons
you
couldn't
put
padding
on
the
the
outer
wrapper
itself,
but
now
you
can
just
use
content
box
and
that's
important
in
IE
a
eight
and
up.
So
that's
all
that
we're
concerned
about.
So
we
can
eliminate
the
inner
and
outer
wrappers.
B
And
so
so
we
eliminate
all
the
classes
are
sorry
so
eliminate
all
the
IDS
and
instead
settled
on
prefixing
classes,
with
l
/
layout
if
they
are
a
layout,
specific
class,
and
that
has
some
other
great
benefits
that
it
makes
distinguishing
between
a
layout
based
selector
and
a
like
a
theme
provided
or
a
component-based
selector
a
lot
easier.
So
if
it
starts
with
L,
that
means
that
that
is
something
provided
by
the
layouts
and
if
you
switch
layouts,
you
may
or
may
not
actually
have
that
selector
available
to
you.
B
Based
on
you
know
the
regions
that
are
there
like
you're,
not
going
to
have
a
l
dash
cryptic
example
in
the
two
column
layout.
But
you
know
that
that's
provided
by
the
layout,
because
it's
prefixed
with
out
so
lots
of
great
things:
reduction
of
classes,
reduction
of
rappers
identification
of
layout
based
classes,
but
the
downside
is
is
that
we
need
update
and
markup
there's
a
pull
request
for
that.
But
the
tests
aren't
passing
yet
we'll
probably
see
that
in
the
next
couple
of
days
some
revised
markup
for
layouts.
Ok,.
A
Also,
a
personal,
exciting
bit
for
means
when
you
first
install
backdrop
if
it's
using
the
bar
to
king,
which
it
is
out
of
Buck,
the
the
footer
is
like
halfway
to
the
page,
which
is
really
frustrating
see
how
many
content
to
push
it
down
and
in
the
layout
changes
that
Nate's
doing.
He
found
a
way
to
stick
the
footer
on
the
bottom
of
the
page,
which
means
that
you're
gonna,
if,
when
you
install
backed
up
it'll,
look
much
better
just
your
first
impression
isn't
like.
A
Why
is
there
blue
stripe
at
the
tap
and
a
gray
stripe
in
the
middle
and
all
this
extra
white
space?
The
bottom
so
I
think
that's
going
to
really
help.
The
first
impression
too,
which
is
gonna,
be
great.
A
Alright,
so
we've
got
views
is
another
thing
that
we've
been
working
on
and
we
have
a
bunch
of
people
working
on
converting
views,
so
things
that
are
in
court
now,
they're,
not
views
into
things
that
our
videos,
Nate
I,
know,
has
been
doing
a
bunch
of
the
more
complicated
conversions,
the
stuff
for
our
admin
listings,
because
they
also
require
actions
being
created
at
the
same
time
and
I
think
we
have
some
other
people
who
are
working
on
some
of
the
views
of
people
will
actually
be
overriding
so
things
that
are
useful
like
the
front
page
and
the
taxonomy
term.
A
In
the
recent
comments
and
stuff
like
that,
there's
a
whole
bunch
of
four
requests
in
the
works.
I
think
bunch
of
them
are
probably
still
missing,
updates
need.
You
want
to
give
us
an
update
on
the
more
complicated
stuff,
the
user
listing
and
content
listing
that
you
worked
on
yeah.
B
I
can't
remember
it's
been
two
weeks
since
our
last
meeting
hang
on.
Let's
see
so
I
can't
remember
when
this
actually
happens,
but
we
converted
the
node
administration
finally
to
a
few.
So
when
you
visit
admin,
/
content,
that's
now,
let's
NAB
with
you,
which
is
great
and
that's
her
purse
to
administrative
listing
that
we've
got
converted.
We
also
have
a
pending
pull
request
for
converting
the
user
listing.
B
The
whole
list
of
all
of
these
conversions
is
issue
151.
If
you
want
to
take
a
look
at
the
views
that
need
to
be
converted
at
some
point,
none
of
these
are
considered
hold.
Ups
for
one
point:
0
point:
0
release
they're,
all
just
really
nice
really
really
nice
to
have,
but
you
actually
could
even
do
these
conversions
after
the
fact,
because
for
the
most
part
there's
there's
no
real
AP
is
that
are
associated
with
them,
although
that's
not
for
users
and
and
nodes
there
actually
is
some
API
is
associated.
B
So
that's
why
we're
focused
on
them
first,
but
anyway,
the
node
listing
is
air
that
note
administration
has
been
converted
with
all
of
the
functionality
that
had
before
plus
some
new
ones
like
like
there's
a
search
box.
That's
that's
handy,
considering
that
I
think
that
administrative
menu
links
is
find
content.
I,
think
it
says
this
even
in
Drupal
7,
but
there's
no
search
box
like
the
only
thing
you
can
do
is
filter
by
node
type,
which
is
just
really
silly.
B
So
the
user
administration
is
converted
to
as
one
test
failure
that
is
proving
tricky
to
figure
out,
but
it'll
probably
get
resolved
here
and
then
streak.
Let's
see
that
those
two
were
probably
the
most
important
ones,
which
is
why
they've
been
getting
focus
but
bwp
and
has
also
been
working
on
doing
a
lot
of
the
block
conversions
and
some
of
these
we
could
probably
kill
entirely
the
recent
content
block.
B
B
It
was
intended
to
be
as
for
administrative
purposes,
but
it
doesn't
make
any
sense
as
a
running
walk
so,
but
we're
also
looking
at
removing
the
who
is
new
and
who
is
online
blocks
which
can
be
converted
to
views.
But
the
theory
is:
is
that
those
who's
online
who's
online
in
whose
new
blocks
are
so
infrequently
used?
B
And,
of
course
you
don't
have
statistics
on
this,
because
we
don't
collect
that
kind
of
information
in
Drupal
or
in
fact
dropped,
but
the
kinds
of
sight,
the
sights
that
would
be
most
likely
to
use
those
blocks
or
forums,
but
we've
removed
forum
module.
So
so
it's
kind
of
like,
even
even
on
the
few
sites
that
needed
it
previously.
B
B
B
B
B
What
we
could
do
after
release,
though,
if
we
don't
get
those
done
I
think
we
will
I
mean
they're
already
ready
and
we
just
need
to
merge
it.
But
if
we,
if
we
need
to
do
this
in
the
future,
we
don't
I,
don't
think
we
should
have
the
option.
If
just
wholesale
removing
stuff,
we
would
have
to
provide
an
upgrade
path
to
in
an
update
hook.
We
add
those
blocks
as
views,
which
is
a
valid
approach,
but
then
on
new
installs
there,
those
bloxorz
wouldn't
exist
anymore.
A
B
A
B
C
We
really
care
specifically
I.
You
know
perk
me
if
anything
is
wrong.
I
about
what
people
in
drew
are
doing,
we're
we're
at
our
address
full
audience.
If
so,
we're
worried
about
people
to
come
to
backdrop
that
want
these
features.
So
so
maybe
it's
a
documentation
thing.
Maybe
we
pull
stuff
out
of
that
and
have
within
the
support
stuff
say
you
know:
does
anybody
want
this
like
check
this
box
to
vote
here?
C
A
Also,
that's
also
true,
like
it's
really
easy
to
generate
this
config
file.
For
this
view,
we
could
just
have
a
documentation
page
or
like
a
blog
post
somewhere.
That's
not
even
backdrop.
That's
like
if
you
want
this
view,
here's
your
config
file
and
then
tell
them
where
to
put
it,
and
that
would
solve
the
problem
for
the
people
that
do
have
it.
A
We
don't
have
to
have
anything
in
core,
but
in
terms
of
our
audience
like
like,
we
are
expecting
that
the
majority
of
our
audience,
at
least
for
one
point:
O,
are
going
to
people
who
are
moving
from
Drupal
7
to
backdrop
and
so
be
nice
to
not
break
their
sites,
but
if
we
can
not
break
their
sites
by
here's,
what's
in
core
and
here's
a
file,
that's
a
config
file.
You
should
throw
in
your
site
to
get
your
view
back.
C
Useful
as
sort
of
a
product
roadmap,
product
management,
side
of
things
to
to
I
mean
not
just
for
this,
but
just
in
general
to
be
constantly,
you
know,
taking
the
pulse
of
not
only
your
users
but,
like
you
know
your
most
important
audience,
your
your
rejecters
people
that
evaluate
you
and
decide
not
to
use
you
like
you
know.
Finding
out,
why
is
is
tough
and-
and
this
seems
like
a
pretty
good
sort
of
example
like
like
solve
this
for
that
case
and
like
other
stuff,
will
also
flow
in
yes,.
A
That's
a
good
point
like
having
some
way
to
survey
people
and
about
what
features
they
want,
which
features
they
don't
want
would
be
useful.
I
think
the
the
most
value
will
get
is
if
we
can
find
some
way
to
put
this
into
the
update
status
module
so
that
we
can
figure
out
like
what
core
views
are
being
used.
So
we
don't
accidentally
remove
something
in
the
future.
That
people
are
using
would
be
great
because
that
doesn't
require
any
active
feedback
from
people.
It
would
just
automatically
get
the
statistics
on
sites
that
are
running
back
drop.
A
Unfortunately,
we
don't
have
any
sites
running
back
drop
right
now
we
don't
have
a
Joe
Lobeck,
Alexa's
information,
yet,
but
I
think
that,
having
that
automatic
thing
go
plus
some
kind
of
manual
thing
where
like
if
people
do
want
to
tell
us
these
are
the
features
I
wanted
that
I
didn't
find
on
backdrop.
It
would
be
good
to
have
some
way
for
those
people
to
get
us
that
information
right
now
we
don't
have
that
Avenue
built.
We
have.
A
You
know
people
can
tweet
at
us
every
now
and
we
read
tweets
and
we
respond
to
them
that
way.
People
can
projects
and
IRC
and
those
who
find
our
email,
I,
just
email
us,
but
that's
kind
of
it.
It
might
be
good
to
have
some
kind
of
more
official
way
to
contact
us
like.
Maybe
throwing
a
contact
form
on
the
fact
website
would
be
a
good
starting
point,
make
it
a
little
easier
for
people
to
get
us
information
and
then,
if
we
want
to
set
up
official
surveys
that
actually
ask
these
questions.
A
That
would
be
good,
too
I'm,
not
sure
going
to
have
time
to
do
that.
To
me
now
and
one
point:
oh,
but
having
some
kind
of
Avenue
like
that-
or
at
least
a
policy
for
been
happening
like
that,
would
be
good.
C
B
A
Okay,
so
configuration
management
we
have
no
current
release.
Blockers
I
mentioned
earlier.
I
was
really
excited
that
no
one
is
reporting
any
problems.
It
could
be
that
nobody's
just
testing
it
because
it
just
kind
of
works.
The
way
I
think
drupal
works,
and
so
they
don't
know
that
there's
a
config
system
there
that
needs
additional
testing.
A
So,
if
anyone's
watching
this
video
wants
to
give
back
drop
preview,
a
try
I,
give
it
a
try
and
then
play
with
config
management,
see
if
you
can
export
and
import
things
and
if
it
dips
the
way
you
want,
and
if
it
generally
solves
the
problem,
the
features
was
being
used
to
solve
in
Drupal
7
see
if
you
can
make
any
bugs
up
here.
We
we
haven't
found
any
recently.
It's
got
some
good
testing
in
there
and
we
haven't
gotten
any
feedback
at
all
about
anything
being
wrong,
which
makes
me
feel
a
little
nervous.
A
Know
so
that
would
be
a
great
thing
that
we
could
get
some
some
feedback
on.
We've
got
a
list
of
major
bugs
and
it
looks
like
me:
you
wanna,
give
us
an
update
on
cashing,
since
that
was
the
beginning
of
your
existence.
For
a
few
days,
yeah
yeah.
B
So
I
put
this
into
the
to-do
items
for
one
point:
0
point
0
just
because
if
we
do
have
any
bugs
sweet
and
they
really
look
that
it
is
possible
that
we
would
get
a
bug
that
is
so
bad
that
we
would
have
to
fix
it
immediately,
and
one
of
them
came
up
the
other
week
that
the
page
cache
basically
wasn't
working.
That
would
be
that
would
qualify
as
so
bad.
We
couldn't
possibly
do
this
release,
but
we
fixed
that
yay,
because
that
the
page
cache
had
been
doing
this
funny
thing
where.
B
It
would
clear
all
the
time
when
crown
was
run
or
it
would
never
clear
it
at
all
and
less
cron
was
run,
so
that
was
kind
of
a
big,
a
big
problem.
Now
you
hit
the
page
cache
lifetime
25
minutes
and
it
actually
lasts
for
five
minutes.
There's
some
really
really
really
strange,
behavior
in
the
way
the
triple
seven
handles
the
page
cache
and
now,
since
we
removed
that
minimum
cash
lifetime
option.
That's
what
caused
the
problem!
B
We
didn't
realize
that
clearing
the
page
cache
was
dependent
upon
the
minimum
cash
lifetime,
but
anyway
that
that's
all
been
fixed
now
in
the
future.
If
we
have
any
more
major
bugs
that
are
going
to
hold
up
release,
we
can
put
them
here,
but
we've
been
hitting
the
1
point,
0
point:
0
tag
really
heavily
and
the
ones
that
are
bugs
have
been
getting
some
priority
and
for
the
most
part,
I'm
I
think
we
might
have
two
bugs
that
are
in
the
one
point,
0
point
0
tag,
but
neither
of
them
are
actually
critical.
A
B
No
actual
reason
for
removing
them
include
food
in
Drupal
8
they
removed
cash
set
and
cash,
get
the
procedural
functions
and
in
a
crop.
What
we
currently
been
doing
is
you
just
create
a
new
cache
object
by
using
the
cache
function,
and
then
that
returns
an
object,
and
then
you
say
cash
arrow
set
and
cash
arrow
get,
and
even
in
Drupal
7
there
was
an
internal
cache
object,
but
you
couldn't
get
at
it.
In
in
backdrop,
you
can
now
access
the
cache
object
directly,
and
so
they
removed
the
procedural
wrappers.
B
While
we
are
all
about
maintaining
compatibility.
So,
instead
of
removing
access
to
or
removing
the
procedural
wrappers,
you
can
now
access
the
cache
object
directly
and
use
the
object-oriented
approach,
or
you
can
use
the
procedural
method
of
cash
underscore
cider
cash
under
strokes.
Do
cash
underscore
goodness
get
so
anyway.
That's
one
huge
API
compatibility
improvement,
because
that
was
something
that
was
running
into
frequently
in
my
porting
tasks.
The
second
one
that
we
did
in
the
past
week
was
we
restored
the
name
of
the
global
for
language
in
Drupal
8.
C
B
Had
to
rename
it-
and
I
think
my
finding
replace
in
Drupal
core
was
there
were
about
700
references
to
this
when
I
put
it
back.
So
that's
an
idea
of
how
many,
how
frequently
this
this
gets
used
and
how
many
times
you'd
have
to
change
it
if
you're
reporting
from
Drupal
7,
so
so
things
like
that
are
really
great
enhancements
that
make
it
so
that
moving
from
triple
7
is,
is
easier
and
we're
hoping
that
we
can
continue
to
make
it
easier
easier.
Yet
yeah
and
Jen
just
had
this
issue.
B
A
B
A
Okay
and
let's
see
so
I
added
model
native
stocking
and
a
section
here
for
a
kind
of
a
list
of
bug,
so
after
1
point
0
point
0
comes
out,
we're
gonna
have
two
lists:
we're
paying
attention
do.
One
of
them
is
a
list
of
bucks
that
are
in
one
point,
0
point
0
and
those
folks
will
need
to
be
fixed
in
minor
from
fix
versions
and
so
I'm
added
a
list
here
where
we
can
track
bugs
that
come
up
one
more
point,
0
point
0
that
need
to
be
fixed.
A
Currently
on
this
list
are
rich
text,
editor
token
module
and
half
auto
I
think
maybe
we
should
readjust
our
priorities
on
this
I
don't
know
if
we
need
to
think
about
it
now
or
if
we
can
think
about
it
after
one
point,
oh,
but
maybe
we
should
just
remove
rich
text
editor
if
you
want
that
to
be
in
1.2.
A
Let's
not
think
about
it
now
now,
let's
think
about
one
point:
0
first,
because
it
what
comes
after
1
point
0
point
0,
once
we
get
1
point
0
bueno
done
but
yeah.
We
have
a
list
here
what's
currently
on
our
plate
for
1.1,
and
we
can
update
this
in
the
future
as
we
start
to
to
look
at
that
more
closely
as
a
bunch
of
other
stuff
we're
working
on
to
that's
not
currently
tied
to
a
specific
release.
We've
got
some
style
guide,
changes
that
are
going
on.
A
We
have
to
do
it
have
Darius
our
designer
doing
design
review
of
the
current
style
guide.
Now
we'll
see
what
he
gets
back
to
us
in
terms
of
how
much
change
we
will
have
time
to
make
before
1
point
0
point
0
comes
out.
There
find
out
me
very
much
time,
civ
down
to
15
days
now,
but
we
do
have
a
designer
people
happening
of
that.
A
Finally,
I
just
good
and
we've
got
some
other
things
going
on
too
there's,
obviously
a
bunch
of
issues
on
github,
around
user
experience,
I've
started,
pre
fixing
all
of
those
issued
titles
with
square
bracket.
You
x
square
bracket,
since
we
have
a
limited
number
of
tags.
We
can
use.
I
didn't
want
to
start
creating
tags
for
everything,
so
it'll
make
our
tag
list
impossible
to
manage
so
I
created
a
square
brackets.
We
were
using
meta
to
indicate
meta
issues.
A
We
now
have
DX
for
developer
experience
and
UX
for
user
experience,
as
we
come
up
with
other
things
that
are
more
tag
like
and
less
label
like
we
can
continue
to
create
more
of
those
two.
As
we
start
noticing
patterns
develop
so
things
that
are
ongoing.
It
will
be
able
to
include
at
any
time
our
user
experience,
exchanges
things
that
we
might
need
to
be
more
careful
about,
including
our
developer
experience
changes,
because
if
any
of
those
require
an
API
change,
they'll
have
to
wait.
A
Things
like
I
think
adding
a
backwards
compatibility
wrapper
around
things.
I,
don't
know
Nate.
How
do
you
feel
that
if
that's
API
change
or
not,
but
there
might
be
some
small
things
that
are
not
API
changes
that
we
could
get
in
in
minor
bug
fix
releases
too?
So
those
are
the
issues
there.
A
If
people
want
a
good
place
to
jump
in
some
of
those
are
novice
issues
and
our
good
first
issues,
and
you
want
to
work
on
backdrop
or
if
you
just
really
care
about
user
experience
and
want
to
create
us
designs
for
things
or
some
issues
that
could
use
some
design
work
too.
Okay,
so
that
is
backdrop
CMS
the
product
and
we've
got
a
bunch
of
other
stuff
that
we're
working
on
for
our
community
as
well.
One
of
the
things
that
was
a
release
block
earth
was
not
actually
backdrop
CMS.
A
The
product
last
week
was
trying
to
get
an
update
server
doing
something
so
that
our
core
backdrop
does
not
throw
errors
when
it
tries
to
check
with
an
update
server
to
find
out
if
it's
up
to
date
and
you've
done
a
bunch
of
work
on
that.
Do
you
want
to?
Let
us
know
what
the
and
solution
is
it
being
yeah.
B
Yeah,
it's
not
a
solution,
a
good
temporary
shim,
but
what
we've
done
is
a
long-term.
What
we
want!
What
we
need
to
do
is
we
need
to
make
it
so.
The
update
module
receives
update
information
like
a
dozen
Drupal
7
and
says
when
a
module
or
core
itself
needs
to
be
updated,
but
the
trouble
with
that
is
that
we
don't
have
the
infrastructure
yet
in
place
to
report
when
a
new
version
of
a
module
comes
out,
because
we
don't
even
have
a
repository
of
all
modules
and
their
versions.
B
Yet
so
we've
got
a
lot
of
infrastructure
setup
to
be
done
to
make
it
so
that's
even
possible
to
have
update
module
return
information.
So
what
we've
done
for
the
time
being
is
we've
taken
the
update
server
where
it
will
ultimately
live,
which
I
think
is
like
updates
backdrop,
CMS
org
and
we've
just
set
up
the
entire
domain
to
return
on
the
HTTP
response.
B
It
doesn't
report
an
error,
it
just
reports
a
notice
saying
that
no
updates
or
that
the
update
server
does
not
currently
work
yet,
and
then
it
links
to
the
related
github
issue
to
say
you
know
when
the
update
server
will
actually
be
done
or
or
show
progress
on
how
the
update
server
is
coming
along.
So
that
makes
it
so
that
when
you
leave
update
module
on
in
theory,
what
will
happen
is
it
will
not
give
you
nasty?
B
Will
you
know
errors
all
over
your
site
and
instead
it
will
just
give
you
a
notice
saying
that
you
know
the
updates.
Basically
don't
work
yet,
but
as
soon
as
the
update
server
is
put
in
place,
all
of
the
sites
that
we
have
out,
there
will
immediately
start
reporting
themselves.
As
you
know,
this
is
the
version
of
the
software
they're
running
and
we
can
keep
it
an
it
basically
from
day.
One
of
all
of
the
backdrop,
one
point
0
point
0
sites
that
are
out
there
I.
A
Think
that's
great!
It's
a
perfect
temporary
solution
in
it
will
give
us
enough
time
to
figure
out
what
our
long-term
solution
will
be.
So
that's
good,
okay,
so
other
things
we're
working
on
include
the
backdrop
API
site
and
I.
Think.
A
Yeah
I
think
we're
pretty
good,
so
the
API
site
is
currently
set
to
pull
the
latest
version
of
the
backdrop
code
and
show
all
the
functions.
So
if
you
want
to
search
functions
for
a
backdrop,
you
can
definitely
do
that.
We
also
have
a
growing
changed
records
section
and
I
at
last,
examine
I,
think
all
of
the
chain.
All
of
the
issues
from
github
that
were
tagged,
needs
change,
record,
have
a
change
record
and
I
know.
A
We've
got
a
couple
people
working
on
reviewing
the
issues
that
are
there
and
making
sure
that
they
have
good
code
examples
and
all
that
stuff,
so
I
think
we're
getting
pretty
close.
We
also
have
someone
reviewing
all
of
the
issues
from
early
triple
8
and
their
change
records,
which
the
change
records
on
your
board
or
we're
likely
to
be
different
than
what
we
need
on
backdrop.
But
there's
still
a
great
starting
point:
I
think
we're
pretty
close
on
those
as
well,
so
I.
Every
time
I
go
check.
C
A
So
thank
you
Luke
and
thank
you.
Everyone,
who's
done
any
work
on
the
change
records
because
they're
coming
along
really
well
so
I
think
Nate.
Maybe
you
want
you
and
I
can
look
over
those
after
one
point,
Oh
point
0
comes
out
and
see
if
there's
anything
that
wasn't
tagged,
that
we
missed
I
know
that
there's
going
to
be
some
theme
stuff
that
we've
get
your
on,
that
I'm
not
sure
got
tagged
with
needs
change
notice,
so
I'll
go
through
that
and
see
if
we
can
get
that
cleaned
up
to
so
yeah.
A
Okay,
great
progress
on
that
I'm
really
excited
about
it.
Other
stuff
that
we
also
need
to
think
about
working
it
on
is
all
of
our
magic,
github
integration.
So
there's
a
couple
of
different
pieces
associated
that
the
first
ones
one
we've
been
talking
about
every
week,
creating
a
github
service
that
anyone
who
creates
a
module
theme
or
layout
for
backdrop
will
be
able
to
register
it
as
such.
A
On
gab
and
I
will
allow
our
site
to
set
up
the
central
repository
of
all
of
the
modules,
themes
and
Lance
that
exist
for
backup
their
statuses
that
are
up
to
snuff
out
just
module
work
and
also
give
people
a
nice
convenient
way
to
search
for
modules,
things
and
layouts
for
backtrack
from
our
website.
So
a
single
place
to
go
to
find
everything.
It's
also
going
to
be
really
handy
and
then
there's
some
other
integration
we
need
with
github
too.
A
In
particular,
we
want
to
make
things
happen
more
automatically
on
the
github
side,
so
things
about
issue
management
so
that
when
for
poor
quests
are
filed,
related
issues
get
the
tags
applied
correctly.
So
whether
that
pull
request
needs
a
review
or
as
our
TV
see,
the
issue
should
get
a
matching
tag
and
as
soon
as
the
poor
quest
exists
issue
get
it
should
get
a
tag,
meets
pull
request
when
an
issue
is
closed.
A
Any
poor
requests
associated
with
that
issue
should
also
be
closed.
Just
a
bunch
of
kind
of
cleanup
tasks
that
we
need
to
do
to
make
managing
our
issue
queue
easier
in
the
long
term
and
also
if
we
have
someone
playing
with
github
magic
behind
the
scenes.
It
would
be
great
if
we
could
get
our
projects
like
the
tags
associated
in
correct
places
and
things
synchronized.
A
A
You
know
the
issue
queue
in
the
pull
request
queue
as
well
as
things
we
would
like
to
have
happen
behind
the
scenes.
I
think
those
are
all.
In
the
backdrop
ops
group
on
backdrop,
CMS
dorks
issue
queue
as
opposed
to
backdrop,
issues
issue
queue,
but
yeah
I
think
I
picked
a
pink
to
Jared
last
week
to
see
if
he
are
two
weeks
ago
or
so
to
see
who
be
a
nurse
working,
I've
gotten,
no
response,
so
it
assume
holidays
are
happening
and
I
expecting
a
fast
response
from
anyone.
A
But
I'd
also
assume
that
he's
not
chomping
at
the
bit
to
do
that.
So
if
we
have
anyone
else
who
wants
to
work
on
github
internal
stuff,
which
I
personally
think
would
be
really
fun
and
I
kind
of
want
to
learn,
but
I
have
other
stuff
that
I
already
know,
and
so
I
keep
working
on
that
instead,
if
anyone
else
has
time
and
interest
in
working
on
it,
we
could
definitely
some
help
on
that.
Get
out
front
there
too.
Okay,
other
things
we're
working
on
our
the
flagship
backdrop
CMS
org
website.
A
We
have
gotten
designs
for
a
new
version
of
our
site.
That
includes
a
logo.
We've
got
half
of
the
designs
implemented
today
on
that
truck
tonight
we
have
our
new
fonts.
We
put
a
logo
on
the
site.
We
don't
have
the
backdrop
word
mark
on
the
site,
yet
I
still
need
to
add
that
and
we've
started
implementing
some
of
the
new
responsive
design
stuff
too,
on
everything,
except
for
a
nice
solution
to
a
menu
which
we
don't
have
on
there.
A
Yet
so
we're
like
halfway
through,
but
it's
slightly
better
than
it
was
last
time
we
had
this
meeting
notices
about
progress,
not
that
completion
but
we're
getting
there,
and
then
we
also
in
the
future
will
add
a
whole
bunch
of
stuff
to
our
primary
site
as
well,
including
browse
pages
for
finding
module,
seats
and
layouts
a
showcase
for
sites
built
with
backdrop,
a
service
provider
directory.
A
A
Kept
falling
out
of
the
inbox
onto
keyboard
anyway
yeah,
so
we've
got
like
his
stuff
going
on
for
the
primary
website
that
is
coming
down
the
pipeline,
but
or
not
actually
implementing
it.
Currently,
in
terms
of
our
communication,
this
meeting
is
held
every
Thursday,
a
video.
You
can
watch
it
now.
You
can
watch
it
later.
You
can
join
in
if
you
aren't
on
hangouts.
We
also
hang
out
in
IRC
every
day,
every
Thursday.
After
this
meeting,
we
are
usually
working
in
IRC
on
backdrop.
A
So,
if
you
use
IRC,
you
can
ask
us
questions
directly,
we're
on
Twitter
all
the
time
at
backdrop.
Cms.
If
you
have
any
questions
about
us
or
want
to
share
anything
with
us
or-
and
you
know
just
tweet
about
us
in
general-
we're
watching
that
in
I
really
appreciate
up
to
all
of
the
communications
we've
gotten
there
and
I,
thanks
to
a
wonderful
suggestion
from
look
today,
I'll
try
and
set
up
a
contact
form
on
our
website.
A
So
if
anyone
needs
to
get
ahold
of
us,
we
can
try
that
for
a
while,
I
think
right
now.
That
makes
sense,
because
there's
we
have
enough
bandwidth
studio
de
menthe,
the
amount
of
email
that
will
get
through
that
form
longer
term
I.
Think
that
might
not
be
a
great
solution
because
we're
going
to
end
up
getting
a
lot
more
emails
in
there,
people
with
time
to
answer
them,
but
short
time,
I
think
that's
perfectly
fine.
A
So
we'll
come
up
with
a
longer-term
avenue
for
communication
between
our
users
and
us
that
might
make
a
little
bit
more
sense,
but
for
now
I
think
that's
probably
about.
As
goes
we
can
do
and
then
yeah
generally
I,
don't
think
we
have
anything
on
our
horizon
here.
In
terms
of
publicity,
we
should
probably
plan
on
making
a
bunch
of
noise
around
january
fifteenth
to
a
lot
of
lino.
A
This
out,
I,
don't
have
any
specific
plans
for
how
we're
gonna
do
that
I
am
planning
on
writing
another
article
for
the
backdrop
magazine.
It
will
be
out
in
March,
so
hopefully
we'll
have
a
better
idea
of
what
the
own
landscape
looks
like
by
then,
which
will
be
good.
Is
it
may
I,
don't
remember
sometime
this
year,
I
know
my
article
student
februari,
but
I'm
not
sure
when
the
Maggie
actually
comes
out,
I
think
it's
good
we
later
than
that,
but
yeah
we
should.
A
We
should
try
and
plan
some
stuff
I
think
maybe
Doug
van
is
collecting
some
media
outlets
where
we
would
be
able
to
let
them
know
the
backdrop
is
out
that
might
be
something
to
schedule
around
january
fifteenth
and
tell
everyone.
You
know
if
you're
watching
this
podcasts
would
be
good,
we
can
probably
try
and
schedule
some
of
those
just
get-get
people
trying
it
and
seeing
what
they
think.
A
A
A
All
right:
well,
that's
all
I
had
I
think
we
should
break
be
on
IRC.
If
anyone
wants
to
add
anything
or
ask
us
anything
or
need,
I
could
stuff.