►
Description
Today’s development agenda: http://bit.ly/26yra3f
A
Alright
happy
Thursday
april
fifth,
everybody
we're
gonna,
do
a
quick
check
in
on
development
tasks
for
backdrop
CMS,
but
before
we
do,
we've
got
a
couple
of
announcements
and
we
are.
We
have
been
contacted
by
the
organizers
of
check,
pocket,
chuckle
camp
trip
optical,
so
lucky
they
have
asked
for
speakers
specifically
on
backtrack.
So
if
anybody
is
nearby
or
interested
in
traveling
to
Czechoslovakia,
it
would
be
great
to
get
back
Jack
spoken
about
there.
We
have
slides
if
anyone
wants
to
pull
from
our
resources
in
order
to
give
a
talk.
A
So
that
is
so
on
the
agenda.
It
looks
like
it
is
May,
28
and
29.
So
coming
up
here
pretty
soon
anybody
who
wants
to
use
Calla
box,
which
is
a
local
development
environment.
It's
currently
an
alpha
and
usually
I'm
using
an
alpha
version
requires
a
special
code,
but
they
gave
us
a
code
for
any
backdrop
developers
who
want
to
try
it
and
start
using
with
backdrop.
So
if
you
have
a
link
to
the
meeting
agenda,
we
put
the
link
for
downloading
a
kallah
box
in
there.
A
But
basically,
when
you
try
to
download
a
copy
of
alpha,
it
will
ask
you
for
a
key
code
and
we
have
a
key
code
specifically
for
backdrop
users.
So
if
you
want
that,
let
us
know
or
check
that
agenda
and
you
can
grab
it.
There
might
also
be
a
link
in
the
latest
blog
posts,
which
is
about
cowell
box
as
well.
Although
a
double
check
today
and
see
if
it's
up
there,
we
also
have
free
phpstorm
licenses
for
anyone
who
is
using
backdrop.
A
So
if
you
are
a
contributed
group
member,
so
the
backdrop
CMS
contribute
on
github,
we
can
send
you
like
to
download
a
copy
of
that
software.
I
think,
is
good
for
a
year,
but
if
you
are
not
yet
in
the
contribute
and
want
to
be
in
want
to
try
phpstorm,
we
can
help
you
with
that
as
well,
and
as
always,
if
you
would
like
to
support
backdrop,
you
can
go
to
our
contribute
page
I'm
back
from
CMS
to
org.
A
If
you
make
a
donation
for
$25
will
send
you
a
thank-you
gift
of
an
adorable
dragon
t-shirt
you
make
a
donation
for
fifty
dollars,
will
send
you
an
adorable,
warm
comfortable
dragon
hoodie.
We
will
have
t-shirts
and
hoodies
at
triple
con
this
week.
So
if
you
want
to
try
yours
on
in
person,
come
track
us
down.
I'll,
probably
have
a
suitcase
you're.
Just
like
me
down,
looks
like
I'm
going
or
going
or
coming
to
the
airport,
but
it's
actually
full
of
Dragon
schwag.
So
that's
a
if
you're
going
to
be
there.
A
It's
a
good
way
to
get
one
all
right.
Big
news
from
the
project
management
committee
we
have
elected,
are
a
new
core
committer
and
that's
Jeff,
so
Jeff
I,
don't
know
if
you
want
to
say
a
few
words,
but
we've
been.
This
has
been
a
long
time
coming
or
like.
We
need
more
core
quitters.
We
have
a
core
committer.
We
need
to
figure
out
a
process
for
setting
for
bears.
A
A
Hey
okay,
so
next
we
should
turn
over
to
meet
to
give
us
an
update
on
community
growth.
I
know.
Last
week
we
had
some
kind
of
sad
announcements
for
nothing
had
happened,
but
this
week
it
looks
like
everything
is
exploded.
So
me,
security,
yeah,.
C
I
also
want
to
add
that
so
Jeff
and
I
went
through
the
process
of
committing
stuff
early
last
week
and
he's
already
merged
like
lots
of
stuff,
and
it's
so
awesome.
It's
like
such
a
relief
that
it's
like,
oh
yay,
twice
the
reviewing
twice
the
committing
power.
This
is
this
is
huge
it
actually
it
actually
so
huge
you
probably
when
we
get
to
the
marketing
section,
we
should
write
up
a
blog
post
because
we
actually
Jeff
isn't
our
second
committees.
Actually,
our
third
doc
well,
monts
also
commit
her,
but
only
in
the
documentation
areas.
C
So
Jeff
is
our
first
full-fledged
core
committer,
but
the
third
overall,
very
exciting,
yeah
community
growth,
lots
of
great
and
very
exciting
things
happening
in
the
contribute.
Two
hundred
and
fifty
two
total
projects
for
backdrop
listed
on
the
github
trib
group.
That's
14
new
modules
since
last
week,
which
is
pretty
incredible,
mostly
I,
think
we
we
owe
our
thanks
to
David
or
D
KN
for
his
exceptional
efforts
there.
He
basically
as
a
whole
bunch
of
utility
modules,
they've
been
working
on
porting
and
he
put
them
all
into
github
this
past
week,
which
was
very
exciting.
C
There
are
234
total
releases
for
all
projects,
10
new
since
last
week,
which
is
basically
the
nine
new
projects
plus
one
existing
module,
had
a
new
release,
which
is
great
there
53
total
backdrop
can't
rib
authors
one
new
since
last
week,
and
that
new
person
is
Philip,
welcome,
Philip
or
on
github
white
pH,
and
we're
really
excited
to
have
you
fill
up
Ben.
Thank
you
so
much
for
your
work,
porting
five
star
and
voting
API
this
this
past
well
past
a
couple
of
weeks.
C
I
know
it's
been
a
little
while
coming,
but
it's
really
excited
to
seeing
those.
In
the
official
repository
this
past
week
we
have
221
user
accounts
on
backup,
CMS
torg
13
new
users
signed
up
for
accounts
since
last
week,
so
yeah
a
great
week,
just
all
kinds
of
great
new
projects.
Great
new
releases
people
signing
up
all
over
the
place,
plus
a
tremendous
amount
of
activity
in
the
core
issue:
queue
as
well
with
the
release
coming
up
in
just
10
days.
That's
not
surprising,
I
suppose
so.
We'll
go
right
into
infrastructure.
C
The
big
item
this
week
in
infrastructure.
We
have
a
new,
a
new
thing
that
cropped
up
that
kind
of
completely
derailed
our
core
review
process
this
past
week,
and
that's
that
travesty
I
totally
fell
on
its
face
last
week,
which
was
really
frustrating
and
unexpected
that
they
moved
us
from
their
old
infrastructure,
which
was
on
like
physical
iron,
basically
to
Google
compute
engine
and
our
load
or
our
testing
times
stretched
like
six
times
what
they
previously
were.
C
We
went
from
15
minutes
to
almost
two
hours
in
some
cases,
for
our
tests
to
finish,
but
Travis
cuts
you
off
after
50
minutes
of
processing,
so
all
of
our
tests
started
failing
everywhere,
so
I
did
oh.
There
should
be
a
link
in
the
agenda
for
that,
but
I
did
a
ridiculous
amount
of
reviewing
looking
for
alternatives,
but
ultimately
what
weird
we've
done
for
the
time
being,
because
we
really
just
need
to
get
to
release
or
we
need
to
be
unhindered
and
focus
until
release.
C
We
just
increased
the
parallel
ISM
that
we're
using
on
Travis.
So
instead
of
two
builds
for
one
for
php5
and
one
for
PHP
7,
we
now
do
6
builds,
so
we
have
three
parallel
tests
on
each
version.
Basically,
and
it's
still
not
as
fast
as
before.
Like
previous,
it
was
like
15
minutes
now,
it's
like
half
an
hour.
So
it's
a
little
bit
of
a
bummer
that
Travis
had
this
like
catastrophic
change,
basically
work:
I!
C
Guess
everybody
just
got
a
lot
slower
they've
been
slower
for
a
while,
because
we've
opted
into
the
the
iron
architecture
for
a
long
time.
Well,
in
any
case,
it's
fixed
for
the
time
being,
but
we're
looking
at
all
kinds
of
alternatives,
self-hosting
or
own
testing
boxes,
those
sorts
of
things,
but
for
the
time
being
we're
going
to
stick
with
Travis,
at
least
until
they
release.
So
there's
an
issue
with
the
summary
I'll
put
up
with
the
link
in
the
agenda.
C
So
next
item
usage
statistics,
usage
statistics
and
analytics
finally
fixed
for
real
yay.
We've
got
two
whole
weeks
without
any
problems
which
is
really
exciting,
and
so
now
that
we've
got
all
of
our
requirements
met.
There's
no
testing
numbers
skewing
things
in
our
in
our
usage
statistics
anymore
and
they've,
been
crunching
successfully
for
two
weeks
now
and
so
I've
made
the
usage
statistics
public
now.
C
In
the
backdrop,
CMS
org
is
your
queue
and
we'd
also
like
to
pretty
up
that
usage
page.
So
it's
not
just
a
big
table
of
information
which
probably
means
adding
a
chart
of
some
kind
and
that's
issue
98.
If
you're
interested
in
putting
up
that
page
a
little
bit,
then
look
over
there,
that
would
be
great
to
get
that
information
a
little
bit
more
digestible
format.
B
Kalibak
sigh
they
added
w,
get
to
the
dress
container,
so
dress
do
work.
Some
cow
box
now.
B
I
haven't
tested
that
but
I
believe
in
goodbyes,
but
I
will
test
it.
New
commands,
Calla
box
folks
want
brush
SI.
That
would
help
with
some
of
their
spin
ups
in
backdrop
land.
B
So
that
sounds
like
kind
of
a
hard
one,
but
I'll
definitely
take
a
look
at
that
and
there's
a
new
proposed
command
proposed
by
me
to
spin
up
boilerplate
module
code,
which
I
think
is
useful
in
its
current
state
I
guess
we
have
one
thumbs
up:
I,
don't
see
much
farming
lugging,
although
I
saw
you
have
a
comment
nique
about
probably
a
better
way
to
respond
to
the
arguments.
I
think
what
I
haven't
looked
at
that
since,
but
I
think
it
will
be
a
useful
thing.
Anyone
strongly
objects,
I,
won't
murder,
but
I.
A
B
C
C
Rush
extension
yeah,
it
was
a
module
that
provided
drush
commands,
which
is
a
little
bit
weird
because
you
had
to
like
turn
on
the
module
hahahaha
in
order
for
the
dress
command
to
be
there,
which
I
can
see
why
people
probably
wouldn't
do
that
on
most
sites.
I
think
it
probably
makes
more
sense
as
a
dress,
command
first
and
then
a
module
seconds
as
opposed
to
the
other
way
around.
A
I,
don't
actually
have
any
updates,
I
haven't
done
anything
to
the
site
in
the
last
week,
but
I
know
gore
volunteered
to
take
online.
The
single
sign-on
task
between
backdrop,
semester,
org
and
github
and
I
didn't
know
if
you
had
any
updates
for
on
that
or
if
you
had
any
questions.
I
haven't
looked
at
that
issue
recently.
I
could
do
that.
I
can.
D
Now
when
I
done
exist
are
not
a
single,
it
will
be
clear
what
need
to
be
done?
I,
don't
move
to
sing
going
to
login
with
the
cart
and
then
next.
Our
task
is
an
integration
project.
Integration
physically
complicated
issues.
It's
about
wishes
to
show
at
least
at
least
show
with
the
fishes
clear
country
project
on
the
dirtiness
itself.
Don't
secrete
a
bit
about
all
starts
the
things
that
I
want
to
finish
with
test
environment
and
then
I
don't
move
to
integration
for
logging
and
then
and
your
move.
Your
project
that.
A
Sounds
great
and
the
only
question
I
have
is,
if
I,
like
other
people
like,
for
example,
if
we
have
a
backdrop
camps,
and
they
also
want
to
provide
single
sign-on
with
github,
they
probably
aren't
going
to
be
using
and
github
API
module.
So
we
should
figure
out
if,
if
there's
a
way
for
those
things
too
like
so
that
we
can
contribute
back
a
github
single
sign-on
solution,
I,
don't
know
how
complicated
that's
going
to
be
well.
D
The
tablet,
the
I
module
fear,
is
only
for
integration
at
my
job
website
with
guitar
man,
it
just
collect
all
in
PR
requests
or
whatever
required
to
a
request.
So
if
the
camp
is
going
to
use
that
drop
for
single
login
as
any
to
you
need
to
pick
up
the
underside,
please
become
urban
cell
phone,
better
mobility,
the
whole
thing,
so
it's
kind
of
required
part
in
a
sense
of
not
cutting,
is
the
same
code
from
github
API
to
and
separated
module
to
make
that
you're
able
toward
me
with
the
top
axis.
D
A
A
Fantastic
and
then
only
other
things
are
going
on
on
the
backdrop
CMS
to
Oracle
site
right
now
is
that
we
have
Eric
Goldman
Texas
building
out
our
content.
Type
first
showcase
I
know
hopefully
have
that
set
up,
and
then
I
also
want
to
take
another
hard
look
at
the
build
our
own
forums
own
issue.
I
noticed
that
WordPress
has
a
couple
of
forums
and
they
somehow
manage
to
keep
them
under
control.
A
So
I
kind
of
wanted
you
to
kind
of
study
how
they
image
to
do
that
and
see
how
their
moderation
works
and
how
their
cattle
ization
of
different
foreign
types
work
and
see.
If
it's
something
that
we
want
to
set
up
on
backdrop
CMS
for
people
who
need
to
top
questions
about
installation
whatever
it
is
so
doing
kind
of
another
investigation
into
that,
and
then
probably
in
our
next
meeting,
will
have
an
update
with
a
proposal
on
how
to
do
form.
A
Sun
backdrops,
you
must
organ
see
if
anyone
else
thinks
that
sounds
like
a
good
idea
or
a
terrible
idea,
whatever
feedback
we're
getting
it.
So,
let's
see,
there's
a
whole
bunch
of
stuff
on
the
site
that
can
always
use
improvement,
our
find
modules,
themes
and
layouts
pages.
In
particular,
now
that
we
have
update
data
like
usage
statistics
data,
it
would
be
great
to
get
that
integrated
into
those
pages
in
entire
views.
So
we
can
do
things
like
search
by
most
popular.
A
So
if
anyone
wants
to
lend
a
hand
at
getting
that
going,
I
think
that
would
be
probably
our
next
most
important
item
and
then
we've
got
a
bunch
of
fall
of
issues
on
just
design
and
aesthetics
around
the
blog
news.
Section
events
service
providers,
all
that
stuff
just
could
use
a
little
kind
of
aesthetic
touch-up.
In
the
news
announcements
we
have
I've
added
that
our
next
blog
posts
should
be
an
announcement
about
jeff
as
our
new
core
committer.
I
don't
know
who
should
write
that
nate.
C
A
I
think
that
sounds
great
and
we'll
plan
on
doing
that
by
next
Thursday
or
Friday.
Next
week
is
drupalcon
and
a
lot
of
us
are
going
to
be
there.
A
So
I'm
not
sure
what
our
meeting
situation
is
gonna
be
like
I
guess
it
will
depend
on
the
internet
access
out
of
there,
which
it
probably
will
be
good,
but
you
never
know
with
references
so
we'll
plan
on
having
a
meeting
next
week,
but
if,
for
some
reason
that
has
to
get
canceled
or
postponed
or
run
by
somebody
who's,
not
at
Triple
con,
and
we
can
send
out
a
tweet
asking
for
help
and
then
our
newsletter
next
tues
letter
is
supposed
to
be
coming
out.
A
May
twentieth,
which
will
be
right
after
backdrop.
1.4
is
out
so
we'll
be
able
to
kind
of
get
workout
some
of
the
kinks
in
the
latest
release
and
then
announced
to
our
followers
that
it
is
ready
for
testing
we're
ready
for
ready
for
use.
C
For
the
time
being
so,
there
will
be
a
last
release
for
people
that
aren't
ready
to
make
the
jump
to
one
dot
for
when
it
comes
out.
Although
the
way
things
are
looking,
it's
really
going
to
be
mostly
an
extension
of
functionality
and
pretty
unlikely
to
affect
anybody
site
on
upgrades.
But
the
option
is
there
for
the
more
cautious
of
the
backdrop
users
out
there.
C
So
one
point
for
point:
0
is
the
next
minor
release
and
that's
coming
up
in
10
days,
which
is
really
exciting
and
also
really
scary,
because
we
have
a
lot
of
things
that
are
really
close
or
getting
really
close,
but
not
a
whole
lot
of
things
that
are
actually
merged
into
the
mainline
branch.
What
we've
got
so
far
is
references,
module
is
in
pretty
much
its
final
form,
well
tested,
well
integrated
and
heavily
reviewed,
and
so
that's
great
that
redirect
is,
is
all
in
place
and
ready
to
go.
C
F
Can
you
guys
hear
me
now
so,
let's
try
and
talk
before,
but
then,
if
I
have
not
gotten
any
work
near
complete
with
this
I
had
a
bit
of
things
happening
here.
You
know,
I,
you
know
took
a
job
three
months
ago,
partly
under
the
hoping
that
you
know
the
agency
would
help
sponsor
some
open
source
contributing,
but
apparently
they
only
sprint
three
hours
a
month
on
open
source
stuff,
and
they
tell
you
what
you
need
to
be
sprinting
on
anyway.
F
They
did
not
support
any
backdrop
stuff
and
over
the
past,
like
month,
I've
been
trying
really
hard
to
make
it
work
with
them,
but
it
did
not
work
with
them.
So
so,
unfortunately,
I
have
not
had
any
time
to
work
on
it,
and
so
I'm
not
sure
how
I'm
going
to
have
time
to
do
it
over
the
next
10
days.
Consider
your
all
watch.
You
walk
on
so
unfortunately
I'm
a
big
failure,
work.
C
That's
well,
let's
not
say
it
that
way:
I
mean
we
still
have
things
that
we
can
work
on.
But
let's
see
10
days
yeah.
If,
if,
if
it's
in
this
date
that
you
say
it
is
I
think
it
would
be
foolhardy
of
us
for
it
to
to
try
and
rush
it.
At
this
point,
yeah,
which.
C
I
think
that's
much
safer
option
anyway.
But
what
we'll
do
I,
like
this
idea
of
a
contribute,
have
been
a
contributing
factor
standard,
which
is
why
we
wanted
it
in
court.
But
that
will
give
us
some
opportunities
to
optimize
it
and
and
to
provide
like
upgrade
pads,
which
are
going
to
be
hard
to
test,
but
are
really
important,
because
nobody
is
going
to
be
using
this
new
module
that
we've
written
they're
all
going
to
be
using
node
reference,
user
reference
or
entity
reference
and
so
figuring
out
how
we're
going
to
help
those
people
move.
C
F
I
mean,
I
think,
that
sort
of
a
short
coming
in
you
know
has
been
a
short
coming
in
drupal
that
once
you
create
a
field,
it's
sort
of
lost
in
place
and
you
can't
switch
it
to
another
field
type
or
something
like
that.
You
can
switch
like
a
like
a
text
field
to
a
number
field,
even
of
all
the
values
in
the
text
field.
Two
numbers
so
I've
been
thinking
like
some
sort
of
like
field
operations
or
feels,
like
you
know,
editing
module
that
actually
lets.
F
You
convert
one
type
of
field
into
another
type
of
field
and
essentially
goes
through
and
creates
a
new
table
and
copies
over
all
values
and
tells
you
if
all
they
all
made
it
properly
might
be
an
interesting
solution.
And
then
you
could
do
something
like
change
the
field
from
a
node
reference
into
just
a
reference
module
field
and
it'll.
Tell
you
like.
Oh
there's
this
many
records,
you
know
putting
the
values
from
one
to
the
other.
It
looks
like
all
them
like
have
the
exact
same
value,
there's
no
type,
mismatches
or
anything,
and
then
yeah.
F
Well,
let's
put
it
this
way,
yeah!
This
is
sort
of
a
good
opportunity
to
try
that.
So,
if
we
just
try
this
little
thing
with
having
a
way
to
convert
the
the
individual
reference
fields
to
the
common
reference
thing,
that
might
be
a
good
test
case
for
how
we
might
do
it
on
a
larger
thing,
so
yep.
So
we
can
maybe
call
it
a
little
testing
for
this
and
then
maybe
expand
it
into
something
larger
cool.
C
Yeah
I
think
it
I
think
it's
a
good
plan
and
really
our
capability
to
do.
That
is
pretty
it's
well
within
possibility
and
and
not
very
difficult
as
far
as
like,
because
in
our
world
we're
only
dealing
with
dealing
with
my
sequel
tables,
because
users
can't
use
alternative
backends,
and
so
it's
really
and
we
know
what
columns
the
old
tables
are
in
and
what
the
new
tables
are
in
and
then
we
can.
C
F
C
C
C
Cool
all
right,
let's
see,
let's
go
on
to
the
theme,
Wes
issue,
1361
yeah,.
G
So
I
want
to
do
that
and
then
there's
some
tickets
in
the
contribute
bow
which
I'm
still
using
as
like
to
keep
track
of
what
I
need
to
do,
and
yes,
I'm
some
bugs
and
questions
whatever,
and
there
are
a
few
that
are
marked-
need
help
for
stuff
that
people
other
people
could
jump
in
on.
Some
of
them
are
more
back
ND.
A
G
C
A
C
A
We
got
a
subset
of
layouts
from
radix
ready
to
go
in
core
Andy
has
been
doing
a
bunch
of
work
on
it.
West
did
a
little
bit
of
work
on
all
of
the
bootstrap
stuff
and
his
theme
as
well.
So
last
week
I
tried
to
kind
of
marry.
The
two
together
I
took
all
of
the
layouts
that
we
had
I.
Think
original
poor
request
from
Doc
Wilma.
A
Them
with
more
layouts
as
we
got
feedback
from
the
community
I
took
Andy's
style
sheet
and
put
that
on
there
and
then
I
tried
to
grab
Wesson
style.
A
You've
got
some
debug
code
in
there,
so
we
can
see
there's
like
background
color,
so
you
can
see
if
things
are
in
the
right
regions
or
not,
and
so
I
think
we
just
need
to
do
a
little
bit
more
testing
on
that
and
see
what
we
need
to
do
to
figure
out
how
to
get
it
ready.
So
I
know
you
guys
are
working
on
that
already.
I
would
like
to
get
some
feedback
neat
from
you
on
our
solution
for
how
to
include
the
bootstrap
grid
system
style
sheets.
A
We
could
use
that
javascript
file
to
do
the
browser
detection
to
figure
out
whether
flexbox
was
necessary
or
not,
and
then
switch
out
the
style
sheet
with
the
I
float
fall
back,
so
the
library
contains
both
of
those
elements
and
then
we
can
attach
the
library
to
any
layout
in
the
info
file
by
adding
a
library
square
bracket
in
the
name
of
the
library.
But
there
is
a
little
hiccup
in
that,
because
right
now,
defining
libraries
requires
both
the
module
name
as
well
as
the
library
name
and
our
info
file.
A
Syntax
doesn't
really
support
that.
So
I
had
a
couple
of
different
ideas
about
how
we
could
do
that
like
if
you
did.
The
key
in
the
array.
Syntax
is
like
the
module
name
or
something,
but
it
seems
just
kind
of
messy
anyway.
I
could
think
about
doing
it.
So
I'd
love
some
feedback
on
that
and
then
also
like
we're
where
we
want
all
this
code
to
live.
A
Is
the
layout
module
the
right
place
to
define
that
library,
or
should
it
be
in
system
so
just
kind
of
getting
a
little
code
review
in
terms
of
where
should
we
put
all
the
code
that
brings
this
stuff
together?
I
think
would
be
super
beneficial
and
if
I
think
I'm
West
and
you
can
figure
out,
CSS
stuff
I
can
work
on
the
library
stuff
and
we
can
figure
out
how
to
get
it
all
done.
It
looks
like
we
kind
of
had
a
consensus
on
which
layouts
we
chose
from
radix.
A
We
took
layouts
that
all
have
not
only
a
header
and
footer
region,
but
also
a
top
and
bottom
region,
and
we
tried
to
do
some
standardizing
on
the
names
of
those
regions.
So
it's
always
top
and
bottom.
We
standardize
on
the
names
of
sidebars
that
when
they
get
ones
and
twos
added
so
that
if
you
try
and
change
from
one
region
to
another
you're,
not
going
from
like
a
sidebar
column
to
an
inner
column,
so
hopefully
that'll
kind
of
makes
sense
to
people.
A
When
you
start
to
see
how
everything
fits
together
but
yeah,
it's
it's.
You
know
starting
from
radix
and
then
trying
to
do
a
bunch
of
cleanup.
There's.
Also
some
questions
about
and
I,
don't
know
Wes.
If
you
have
thoughts
on
this
but
which
dude
strap
classes,
we
should
be
including
in
the
layout
markup
by
default.
I.
A
Think
right
now
we
have
one
layout
class,
it'll
say
like
l
dash
sidebar,
and
then
we
have
one
bootstrap
class,
which
is
the
number
of
columns,
but
there's
also
like
pushing
pole
classes
and
a
whole
bunch
of
other
stuff.
When
I
couldn't
it
seemed
kind
of
arbitrary
as
to
where
which
ones
were
included
in
not
in
the
radix
stuff.
So
we
could
maybe
use
another
set
of
eyes
on
that.
Maybe
we
should
compare
Wes
your
templates
to
the
ones
that
are
in
there
and
see
what
we
think
about
that
and
I
know
Andy.
A
You
had
some
feelings
on
on
that
too,
and
then
Andy
also
had
some
pretty
good
feedback
about
what
we
should
do
with
the
info
files.
So
right
now
in
layouts
in
core
all
the
info
files
included
the
like
default
region
for
content,
even
though
they
had
a
region
named
content
and
then
when
I
took
those
out,
I
realized
that
that
line
that
we
had
indicated
wasn't
necessary
was
necessary
because
all
of
our
core
layouts
were
using
it.
We'd
never
tested
a
layout
without
including
that
line
so
I
fixed
that.
But
Andy
said
why?
A
So
maybe
we
should
just
leave
everything
in
a
layout
in
profile,
commented
out
with
some
documentation
about
how
it's
used
like
we
did
in
the
current
core
layouts
with
the
default
region
and
then
that
make
it
easier
on
theme
developers
to
be
able
to
copy
those.
So
that's
not
in
the
pull
request
right
now,
but
India
I
just
want
to
say
I
think
that's
an
excellent
idea.
I
went
through
and
removed
at
all
and
then
Andy's
like
wait.
We
need
that
and
I
was
like.
A
Oh
yeah,
that's
smart,
so
we
should
probably
put
that
back
in
as
well,
and
I
can
work
on
that
too.
So
I
think
like
it
feels
like
we're
close
with
layouts
as
long
as
we're
on
the
right
track.
But
if
we
look
at
like
someone's
as
a
code
review,
if
this
and
goes
oh,
my
gosh,
this
is
totally
not
the
right
way.
We
need
to
rethink
it,
then
we're
not
close,
and
we
should
figure
out
if
that's
gonna
be
an
issue
for
a
release
or
not
I
feel
like
where
we
are
right.
A
C
C
Well,
that's
those
are
main
items.
We've
got
a
issued
1087,
which
is
improving
the
rich
text,
editor,
which
is
a
meta
issue
with
a
bunch
of
sub
issues,
most
of
which
are
actually
bugs
not
features,
but
the
one
item
on
there
that
I
really
want
to
make
sure
we
get
done
before
the
release
is
the
upgrade
of
ck
editor,
which,
from
other
people
that
have
tested
this.
It's
mostly
just
plop
it
in,
but
there's
some
great
features
in
the
new
version
of
seek
editor.
C
That
week
also
can
utilize
like
drag
and
drop
uploads
or
something
that
sort
which
would
be
cool
but
probably
well.
Unless
someone
else
has
the
time
to
start
taking
a
look
at
it,
probably
not
something
that
will
happen
before
1.4,
but
for
starters,
let's
just
get
it
updated
so
that
it's
there
and
so
that
we
get
all
the
bug
fixes
from
ck
editor,
and
then
we
can
work
to
expand
it
in
next
release,
if
necessary,
which
will
be
so
it's
always
necessary
to
keep
improving
the
rich
text
editor.
C
Let's
see
other
items
that
we've
got
that
weren't
on
the
agenda,
for
one
dot
for
but
are
going
to
happen
or
just
one
item
actua
that
is
really
important,
is
project
browser
project
browsers
issued
1399,
oh
jen,
you
gave
this
another
look
this
week
I
have.
I
was
derailed
by
the
testing
framework.
Could
you
give
the
update
on
project
browser
sure.
A
So
project
browser
looks
fantastic.
I
went
through
kind
of
a
super
nit
picky
detailed
review
of
like
this
word
should
be
this
other
word.
These
are
in
their
face,
but
it
works
really.
Well,
it
lets
you
it
lets.
You
browse
the
modules,
themes
and
layouts.
You
can
add
as
many
our
sous.
You
want
to
a
queue
you
can
install
them.
It'll
go
through
and
install
them
one
at
a
time
then
it'll
ask
if
you
want
them
turn
on
or
not
and
maple
they're,
not
you
can
enable
them
and
then
it'll.
A
Take
you
back
leave
and
turn
on.
Like
your
theme,
gets
you
bunch
and
turn
on
your
theme.
It's
super
slick,
I,
think
it's
totally
ready
and
what
I
did
is
I
created
a
follow-up
issue
that
was
specifically
a
design
review
because
I
think
what
we
should
do
is
put
it
in
when
it's
functionally
ready
and
we
can
clean
up
the
aesthetic
of
it
at
any
time.
There
are
a
couple
of
little
things
that
I
thought
were
usability.
A
Issues
like
I
couldn't
find
the
search
box
because
it
was
in
the
sidebar
and
on
all
of
the
other.
You
eyes
and
backdrop
like
on
the
modules
page.
The
search
box
is
right
at
the
top,
so
I
just
had
recommendation
to
move
it
so
edit
a
comment
and
then
document
went
and
moved
it
like
instantly
so,
like
I,
think
I
think
that
one's
looking
really
great
I
think
it
might
need
another
code.
Review
I
did
a
lot
of
interface
review
and
then
I
consulted
the
code
where
the
thing
was
added.
A
C
C
But
if
you
didn't
have
those
modules
and
you
had
installer
module
turned
on,
it
could
actually
install
those
modules
on
the
remote
site
to
which
would
make
for
a
badass
demo
of
setting
up
an
entire
site
on
your
localhost,
installing
modules,
configuring
them
and
then
doing
an
import
of
config
and
having
that
also
download
the
modules
all
at
once.
It
would
be
pretty
sweet.
C
It's
thursday,
every
thursday
is
backdrop
day.
We
hang
out
in
the
github
issue,
queue
github.com,
/
backdrop,
/
backdrop
issues
and
in
git
er,
which
is
a
chat
channel
that
you
can
use
to
your
web
browser,
get
er
IM,
/
backdrop,
/
backdrop
dash
issues
and
that's
where
we
are
going
to
be
for
a
little
while
Jedi
are
packing
up
and
heading
out
this
evening,
so
we
will
be
having
a
short
day,
but
we
will
be
doing
backdrop
until
until
we
head
to
the
airport,
we
have
an
IRC
channel,
we're
still
there.
C
Some
of
the
time
but
get
er
is
really
that
the
way
to
go
these
days
and
reddit
channel
if
you're
interested
in
talking
about
things
that
are
just
poor
referral
to
to
backdrop
that
don't
actually
involve
the
improvement
of
the
software
reddit
com,
such
r
/
backdrop
upcoming
events,
you
can
get
a
list
of
them
at
backdrop,
CMS
org,
slash
events,
there's
also
an
ical
Phoebe.
You
can
get
from
this
agenda
here,
I'm
guessing
Jen,
you
want
to
say
something
about
OS
bridge
yeah,.
A
So
I
think
my
viewed
mentioned
something
about
trying
to
do
some
kind
of
a
backdrop
thing
at
open-source
bridge.
It's
in
Portland
in
June.
C
A
Think
I
don't
know
if,
if
you're
planning
on
going
to
that
or
not,
but
it
might
be
good
for
somebody
to
give
a
talk
on
backed
up
there
if
they
are
going
yeah.
F
A
A
A
Let's
see
beginning
doc,
Japanese
on
Oh.
F
A
We
have
a
thought
about
it,
so
neat
and
I
will
be
a
triple
con.
We
do
not
actually
we're
not
planning
on
attending
sessions,
but
we're
gonna
be
nearby
and
probably
sprinting
on
backdrop,
because
we're
so
is.
A
F
A
F
A
That
sounds
good.
What
I
put
it
on
Twitter,
yeah
I'm
will
say
something
in
like
then
get
our
log
or
whatever
we'll
try
and
make
as
much
noise
as
we
can
once
we
figure
it
out,
but
we
don't
have
anything
official
scheduled
as
of
yet
just
cuz.
We
don't
know
where
we're
going
to
be
doing
it.
We
want
to
buy
something,
that'll
be
convenient
for
everyone,
that's
there,
but
also.
A
Delicate
how
we
go
about
it
so
yeah,
that's
the
plan
and
I
think
it'll
be
good
to
do
some
kind
of
a
backdrop
party
thing.
Last
year,
drupalcon
we
had
everybody
meet
up
at
a
bar
that
was
nearby
just
kind
of
hung
out
and
chatted
and
people
eat
food
and
people
drank
drinks,
and
we
always
had
kind
of
a
little
backdrop.
A
Celebration
I
think
would
be
great
to
do
something
like
that
again,
but
again,
last
year
we
got
there
and
figured
out
where
it
would
be
a
good
place
to
have
Larry
mint,
and
then
we
announced
it
on
Twitter
and
then
whoever
came
came
so
we'll
probably
plan
on
doing
the
same
thing
again.
This
year,
too,.
A
A
Yeah,
maybe
a
Wes
and
Andy
and
I
should
stay
on
and
talk
about
layouts.
That
would
be
good
wicked.
We
could
do
a
separate,
hang
our.
We
can
just
keep
talking
review,
guys,
mine,
all
right,
one
I
think
that's.
It
won't
figure
out
our
layout
plan
and
we'll
see
all
of
you
guys
next
week.
Unless
we
can't
have
a
meeting.