►
Description
Today’s development agenda: http://bit.ly/1SOgjbm
A
Ray
Brown
air,
a
happy
Thursday,
April
14th
everybody.
Thank
you
all
for
coming
in
attending
I.
Just
want
to
ask
really
quick.
Last
week,
Nate
and
I
were
on
a
plane
during
the
meeting,
and
so
I
tried
to
facilitate,
like
everybody
else,
having
a
meeting
without
us
and
I
wonder
if
it
actually
happened,
were
you
guys
able
to
figure
out
how
to
get
on
the
Hangout?
B
B
A
At
the
recommended
time
and
in
theory
that
should
work,
everything
should
work
as
normal,
except
for
the
live
broadcast
can't
be
turned
on
unless
somebody
is
logged
in
as
the
backdrop
cage,
and
so
if
we
have
somebody
that
wants
to
run
meetings
in
our
absence,
we
can
just
turn
over
access
to
the
page
to
whoever
that
person
is
on
google+
and
then
they
can
change
to
the
beat
the
page
and
push
the
button
to
start
the
broadcast.
But
in
theory
the
meeting
should
still
be
able
to
happen,
even
if
there
is
no
live
broadcast.
A
So
what
I'm
going
to
do
from
now
on
is
set
up
all
of
the
meetings
like
a
week
in
advance
or
two
weeks
advance
or
depending
on
if
it's
a
design
meeting
will
be
two
weeks
in
advance
or
a
regular
one
one
and
then
we'll
try
and
see.
If
we
can
figure
out
maybe
next
week,
we'll
have
somebody
else
sure
I
in
start
the
meeting
and
see
how
it
goes.
A
If
you
guys
are
up
to
that,
because
I
think
it
would
be
great
if
we
have
this
much
interest
to
continue
the
weekly
meetings,
even
if
I'm
not
here,
to
push
the
button
and
so
anyone
if
we
can
get
anyone
to
push
the
button
I
think
that
would
be
good
so
we'll
give
it
a
shot.
Okay,
so
next
week
we'll
have
less
try
and
do
it
so
you're
we
can
get
kinks
ironed
out
and
then
that
way.
Hopefully
this
will
continue
to
be
more
usable
for
everybody
in
the
future.
A
So
all
you
really
need
to
do
is
kind
of
roam
through
it
and
if
you
don't
want
to
talk
about,
things
are
on
the
agenda
and
you're
the
one
that
grabbed
that
up
for
grabs
meeting
you
can
take
it
off
or
you
can
add
new
things
you
can
do
whatever
you
want.
So
your
meeting,
but
we're
trying
to
kind
of
take
away
the
work
of
setting
up
the
agenda
ahead
of
time.
A
So
it's
a
good
starting
point
for
anyone
and
you
can
update
it
or
not,
depending
on
what
you
want
to
do
so,
hopefully,
that'll
be
easy.
Other
announcements,
we
do
love
donations.
If
you
would
like
to
make
a
donation
to
vector
of
CMS,
you
can
do
so
on
our
website.
At
backdrop,
CMS
org
slash
contribute
and
we
will
send
you
a
thank-you
gift
of
either
a
t-shirt
or
a
hoodie,
and
I
will
send
you
a
t-shirt
if
you
give
us
25
dollar
donation
or
a
hoodie,
send
us
a
fifty
dollar
donation.
A
If
you're
already
a
backdrop,
contributor,
you've
already
earned
your
t-shirt
and
you
don't
need
to
set
this
a
donation.
You
can
just
send
us
an
email
to
info
a
backdrop
CMS
or
chamomile.
You
t-shirt
so
definitely
make
sure
you
get
those.
And
then,
if
you
want
a
phpstorm
license,
you
need
to
be
a
member
of
the
backdrop
contribute,
and
we
can
definitely
help
get
you
through
that
process.
C
I
just
had
a
sudden
inspiration
that
maybe
we
could
start
implementing
when
people
finish
their
contributor,
address
or
email
address
and
then
send
them
a
t-shirt
when
they
join
the
contribute,
just
be
like
yay
welcome
and
have
it
be
like
we
push
it
on
them
rather
than
a.
You
know,
on
request.
Only
because
it's
a
little
bit
awkward
for
people
to
say,
yeah
I
publish
my
module
can
I
have
a
teacher.
Now
you
know
we.
A
Don't
you
don't
even
need
them
to
be
a
part
of
the
contribute
to
get
a
t-shirt
like
there's
a
whole
bunch
of
people
that
contribute
to
core
that
maybe
don't
have
a
module,
a
theme
or
a
layout,
but
I
think
it
might
be
good
for
people
who
do
become
members
of
the
kinship
group
to
ask
them.
Do
you
want
a
t-shirt?
A
If
so,
what's
your
address
and
do
you
want
a
phpstorm
license
key
and
if
so,
what's
your
email
address
and
have
them
then
like
as
a
like,
welcome
to
the
community,
we
have
stuff
for
you,
let
them
opt
in
or
out,
but
do
it
as
part
of
the
application
process
and
then
also
just
to
be
clear.
Anyone
who
has
contributed
anything
to
backdrop
at
all
whether
it's
contribute
at
can't
have
a
t-shirt.
So
if
you've
been
really
active
in
like
the
park,
you
being
like
I
tested
this
thing
and
it's
not
working.
That's
enough!
A
Like
we'll,
send
you
a
t-shirt,
you
don't
have
to
write
any
code.
You
can
be
a
tester
or
user
whatever
you
need.
So
yes,
great
idea:
mate
follow
up
a
control
application
with
an
offer
of
free
stuff,
be
a
tee
shirts
or
phpstorm
licenses.
So
push
the
things,
but
those
things
are
not
limited
to
contribute.
So
there
we
go.
Let's
send
clonise
t-shirt,
stat.
A
Alright,
speaking
of
clone,
owes
who
have
announcement
to
make.
We
have
my
new
member
on
the
project
management
committee.
We
had
a
unanimous
vote.
Everybody
agreed.
We
wanted
to
have
a
Gregory,
be
our
first
site
builder,
constituent
representative,
I'm
kind
of
a
non
coder,
although
he
has
started
making
four
requests
so
maybe
not
for
long,
but
we
get
to
have
the
perspective
of
somebody
who
uses
all
the
things
we
build
and
maybe
doesn't
understand
how
we
got
there
in
the
first
place
to
say
this
is
really
weird.
A
We
shouldn't
do
it
that
way
and
we'll
go
oh
yeah,
it's
really
weird
and
we
can
fix
it.
So
we're
really
happy
to
have
you.
As
a
member
of
the
project
management
committee,
you've
been
a
great
contributor
to
backdrop
for
two
years,
maybe
more
than
two
years
as
long
as
we've
had
a
website
as
well
as
long
as
we
had
to
get
a
hub
queue
and
something
that
makes
me
personally
really
happy
about
having
you
on
the
PMC
is
that
I
also
run
into
all
the
time
in
the
drupal
org
issue
queue.
A
A
Originally,
the
plan
was
to
have
a
small
group
of
pmc
members,
maybe
six
or
seven
and
a
much
larger
group
of
core
committer,
so
that
we
could
empower
more
people
to
make
more
change
more
often
and
only
when
we
run
into
a
problem
escalate
those
issues
to
the
pnc
yeah.
Okay,
let
me
stop
before
I
start
talking
about
core
committer,
saying:
okay,
Nate,
just
as
a
question
should
we
let
Gregory
say
anything:
yes,
we
should
Gregory.
Would
you
like
to
say
anything
about
being
part
of
that
Jeff's
p.m.
see
ya.
B
A
B
A
C
Yeah,
well,
it's
been
an
exciting
week.
Actually,
two
weeks
since,
since
we
didn't
have
a
meeting
last
week,
lots
of
things
happening
in
the
cork,
you
can
tribute
community,
wise
and
in
the
contribute,
we've
had
a
little
bit
of
a
lull
in
the
porting
of
new
projects,
but
we
have
had
an
uptick
actually
an
interest
in
applications.
C
We
also
have
three
new
applications
since
I
last
checked
and
Gregory's
been
doing
a
great
job,
communicating
with
those
people
there's
one
new
application.
That
came
in
five
days
ago
that
we
haven't
yet
gotten
to,
but
it's
great
to
see
new
contributors
applying,
there's
so
there's
three
new
ones
since
a
last
meeting,
but
there's
also
nine
open,
total
contribs,
and
I
think
that
those
applications
people
are
getting
stuck
with
the
process
a
little
bit.
You
know
the
like.
C
I
don't
know
how
to
well-
maybe
maybe
the
yeah,
I
don't
know
how
to
put
a
project
up
on
github
or
how
to
put
it
in
my
personal
repository
and
then
go
through
the
review
process.
So
there's
people
that
are
interested
but
are
getting
a
little
hung
up
and
would
be
great
to
move
them
through
that
process.
So
anyway,
I'm
excited
about
the
new
users
and
existing
ones.
If
we
can
get
them
motivated
to
actually
push
their
projects
through
the
process,
how
are
we
communicating
the
updates
out.
A
B
A
When
a
project
gets
another
release,
so,
for
example,
when
I
first
release
a
project,
it'll
leave
one
point,
0
point
0,
then,
when
I
do
a
bug
fixed
my
release
at
one
point
0
point:
1,
we're
tracking
the
fact
that
there's
more
than
one
release
of
that
project,
we
can
tell
when
one
point
no
point.
One
came
out,
so
we
can
tell
when
a
new
project
first
gets
released.
If
it's
one
point
0
point
0
and
it
hasn't
been
there
before
we'll
say:
hey,
there's
a
new
project
and
or
we
can
tell
when
it's
like.
A
Oh,
this
is
just
an
object
to
an
existing
project.
So
it's
kind
of
continued
maintenance
for
updates
versus
like
new
things
appearing.
Is
that
and
and
just
technically
how
that
happens
is
as
soon
as
you
push
a
tag
to
get
hub.
There's
a
post
update
hook
that
will
fire
and
update
backdrop
CMS
to
org
of
the
changes,
so
we're
pulling
the
numbers
from
a
trophy
and
list
at
work,
but
they
are
coming
from
github.
Initially.
Does
that
answer
that
question.
C
C
Okay,
all
right,
oh
yeah,
yeah,
oh
yeah,
that
and
what
a
new
releases
update
yet
via
update
module.
So
if
you've
got
update,
module
turned
on
then
you'll
be
notified,
that
there's
a
new
version
and
you
can
configure
your
backdrop
site
by
default
backdrop.
Actually,
your
your
site
itself
will
email
you
if
a
new
version
of
a
module
comes
out,
but
only
for
security
updates.
There's
a
setting
in
your
update
module
to
change
that
to
all
releases.
C
C
Okay-
and
we
also
have
on
backdrop
CMS
org.
There
are
a
hundred
and
fifty
one
total
user
accounts
that
have
been
created.
18
new
users
have
signed
up
since
last
meeting.
That's
great.
We
I
think
the
big
difference
is
that
we
put
a
link
to
sign
up
in
the
in
the
sidebar
now
so
at
least,
there's
a
way
yeah
for
people
to
find
out.
Oh
I
can
sign
into
the
site
the
previous.
C
C
Okay,
so
that's!
That's!
All
I've
got
for
community
growth,
it's
great
to
see
new
people
coming
in
and
maintenance
on
those
modules.
Next
item
on
the
agenda
is
infrastructure.
We've
got
a
bunch
of
items
that
are
around
backdrop,
CMS
that
don't
involve
the
software
itself.
The
first
item
on
this
agenda
we've
got
is
update,
usage
statistics
and
analytics
yeah,
it's
kind
of
working
I.
We
still
are
having
a
little
bit
of
an
issue
with
the
number-crunching
script.
C
We've
got
all
the
numbers
up
until
mid-march
going
back
for
about
nine
months
at
this
point,
so
it's
great
that
we've
got
some
historical
data,
but
in
the
last
four
weeks
it's
all
just
been
zeros
and
that's
just
because
we've
got
an
issue
with
the
script
that
crunches
the
numbers
that
right
now
for
some
reason,
I
have
to
run
it
manually,
I'm
sure
it's
like
a
trivial.
You
know
crontab
configuration
issue
or
something
like
that,
but
we
haven't
quite
gotten
that
worked
out.
C
D
For
the
kallah
box
people,
so
they
can
track
against
releases
edge
of
master
case.
Something
is
wrong.
It
looks
like
it
didn't,
go
on
backdrop
see
and
that's
because
drush
doesn't
have
a
dot
info
file
which
I
don't
know.
If
we
want
it
on
there
or
not,
I
could
see
ya.
I
could
see
it
another
way.
Yeah.
C
I
was
thinking
the
same
thing,
because
it's
not
a
module
theme
or
layout
right,
and
so,
but
they
did
the
same
thing
on
drupal.org,
it's
good
for
findability,
if
it's
just
listed
there,
even
if,
even
if
it's
not
available
for
download
there,
I
think
what
we
might
do
is
just
manually
create
a
node
on
backdrop,
CMS
org.
That
says
that
is
the
dress
project,
just
so
that
we
have
something
on
backdrop:
CMS
org,
that
points
over
to
github.
That
sounds
like
a
fine
idea
to
me
now.
C
Janet
right
actually
page
right
now
backdrop
CMS
org.
If
you
look
at
the
apparently
there's
a
piece
of
news
post
called
placeholder
right
now:
oh
that's
because
I'm
logged
in
okay,
thank
goodness
because
that
would
be
silly
anyway.
I
think
that
is
the
case.
Yeah,
okay,
yeah!
It's
on
the
homepage
right
now
dealing
with
rush.
C
You
can
also
just
view
it
if
it's
not
on
the
homepage.
By
the
time
see
it.
You
can
visit
backdrop.
Cms
start
work,
/
news
and
it
will
be
one
of
the
more
recent
posts.
Yeah.
That's
a
great
post.
Let's
see
back
on
the
agenda.
Speaking
of
cala
box,
which
you
mentioned,
there's
some
exciting
cala
box
integration,
stuff
happening.
Jen
you've
been
you
communicate
with
them
just
yesterday.
You
want
to
give
an
update
on
that
sure.
A
So
cal
box
came
out
with
a
new
version
yesterday,
which
is
super
exciting.
It
can't
it
contains
out-of-the-box
trash
image
so
that
if
you
want
to
start
up
for
drupal
backdrop,
something
noun
okay,
so
cala
box
contains
a
different
versions
of
triple.
You
can
install
Drupal
7,
you
can
adult
installed
triple
8
and
it
uses
dagger
if
you'll
do
like
a
little
container.
That
holds
all
of
this
stuff
that
each
project
needs.
So
we
set
it
up
so
that
it
comes
out
of
the
box
with
a
backdrop
container
now
that
didn't
have
before.
A
In
order
to
do
that,
we
had
to
create
a
backdrop,
a
official
composer
file
for
docker
to
use.
So
now,
if
you're,
using
docker
and
not
Kalibak,
so
you
can
also
get
a
backdrop
container
pretty
easily,
which
is
great.
It
contains
I,
think
HP
seven
and
it's
almost
all
the
same
things
as
Drupal
like
it
has
trash,
but
also
has
our
factor
of
josh
extension,
which
is
why
we
needed
the
special
release
for
it,
and
it
looks
like
it's
working
pretty
well.
I
got
to
see
it
in
action
yesterday
and
it
looks
fantastic.
A
A
Right
so
things
are
working
on
right
now,
I
were
a
little
bit
blocked
on
design
for
setting
up
our
showcase
there's.
Definitely
some
things
we
can
do
without
a
design
like
building
a
content
type
on
the
trying
to
figure
out
what
that
should
look
like
is
going
to
need
a
little
in
operation
from
somebody
who
understands
design.
So
we
definitely
could
do
some
help
with
that,
and
we
also
something
I
want
to
get
set
up
before
next
week.
Is
our
service
provider
listing?
A
So
this
is
just
a
way
for
anyone
to
enter
a
company
or
organization
in
a
listing
so
for
trying
to
find
hosting
provider
developer
to
build
you
a
site
with
backdrop.
You
can
do
that
and,
and
hopefully
we'll
be
able
to
get
that
at
least
kind
of
MVP
by
next
week,
because
oh
it's
that
later,
okay
other
things
we'd
like
to
get
is
a
single
sign-on
with
github.
A
So
people
who
are
using
their
backdrop,
CMS
org
accounts,
don't
necessarily
have
to
log
in
with
a
separate
user
account
on
back
trips
in
this
or
dark
as
they
do
on.
Github
will
just
give
them
a
button
and
it'll
copy
their
username
and
any
relevant
information,
and
if
we
can
get
those
two
things
linked
together
and
then
we'll
also
be
able
to
grant
people
additional
permissions
for
modules,
they
maintain
down
the
road.
A
A
Once
we
start
having
people
who
have
companies
who
need
backdrop,
specific
people
will
probably
post
a
job
forward
to
that's
something
that
worked
really
well
in
the
Drupal
community
and
I'd
love
to
see
that
mirrored
for
backdrop.
We
have
a
bunch
of
stuff
on
the
backdrops
and
less
org
site.
That
needs
a
little
improvement.
Most
important
things
right
now
are
the
find
modules,
themes
and
layouts
pages.
We've
got
some
developer
tasks
that
need
to
be
done
for
module
stuff
just
to
make
the
project.
A
We
could
do
like
a
hybrid
of
the
module
page
and
the
theme
page
or
we
could
just
expand.
What
we
have
on
the
module
page
to
account
for
a
couple
more
things.
It
will
be
good
to
have
something
kind
of
think
about
that
problem,
face
and
try
and
figure
out
what
the
best
solution
might
be
for
getting
people
layouts.
So
from
the
to
find
the
layout
page
on
Petrov
CMS
to
org,
and
then
we
have
a
bunch
of
things
that
we've
built
on
back
top
CMS
or
that
might
need
a
design
review.
A
So,
for
example,
our
blog
/
news
section
think
it's
still
called
news
in
the
menu
but
page
heading
now
says
it's
a
blog
I,
don't
really
care
what
we
call
it
if
we
want
to
change
the
link
in
the
menu.
We
can
do
that
too,
but
it
does
need
someone
to
kind
of
look
over
it
and
say
just
this
page
line
up
with
our
design.
Aesthetic
for
the
rest
of
the
site.
Same
thing
is
true
for
the
event
listings
page.
A
A
A
C
Well,
I
did
I
will
say
thanks
to
a
Jeff's
input
from
last
meeting,
that
I
did
set
up
VMs
and
got
benchmarks
actually
four
five:
five,
five
six
and
seven-
and
that's
that's
pretty
exciting.
Actually
so
so
we
do
actually
have
numbers
now,
but
now
I'm
thinking
I'm
like
well.
Maybe
we
should
wait
on
publishing
them
until
we
make
them
even
better
numbers.
E
A
C
Yep
yeah,
because,
right
now
the
situation
is
and
I'll
just
go
out,
come
and
say
it.
I
suppose,
is
that
with
like,
when
backdrop
first
came
out
one
point:
oh,
it
was
slightly
faster
than
Drupal
7,
but
we've
been
putting
in
all
these
new
features
that
now
it's
slightly
slower
than
Drupal
7
for
authenticated
users,
but
for
anonymous
users
it's
still
like
substantially
faster.
It's
like
thirty
percent
faster.
So
there's
there's
some
good
news
and
some
bad
news
there.
C
That's
like
it's
moderately
slower,
but
it's
also
moderately
faster
for
for
most
visitors,
because
they're
going
to
be
anonymous
and
with
stuff
like
background
fetch
and
there's
no
slope
Apes
loads.
Anyway,
you
know
it's
really
I
mean
there's
a
lot
of
really
good
things
to
talk
about
so
I
guess
you're
right
that
maybe
let's
just
put
it
up
there
and
then
once
we
hopefully,
once
we
managed
to
make
backdrop
authenticated
experience
even
faster
than
Drupal
7.
C
A
D
F
A
Oh
yeah,
we
should
add,
update.
Ok,
so
I'll
I'll
put
a
note
in
here
about
that.
Ok,
so
Nate
I,
don't
know
if
you're
gonna
have
that
post
ready
for
tomorrow,
it
sounds
like
we've
got
a
lot
of
good
ideas,
that's
going
to
take
some
time
to
actually
benchmark
and
right
up.
So
if
anybody
else
has
an
idea
of
a
blog
post,
they
want
to
write
tomorrow.
We
definitely
are
open
to
that.
A
If
nobody
has
an
idea,
it's
also
okay
for
us
to
skip
a
week
on,
but
it
would
be
great
to
get
something
out
if
you
have
an
idea,
so
you
like
to
write
something.
Let
us
know
there's
a
couple
of
ways:
you
can
be
that
you
can
send
an
email
to
info
a
factor
of
CMS
to
org.
You
can
post
a
comments
on
the
official
blog
schedule
issue
just
number
158
in
the
queue.
So
anyone
has
any
good
ideas.
A
Oh
yeah,
good
idea,
all
right,
okay,
so
speaking
of
good
ideas,
her
degree
just
mentioned
two
things
in
the
chat
in
the
sidebar.
First
of
all,
he
said:
hey,
don't
you
guys
have
anything
to
talk
about
from
the
drupalcamp
that
you
went
to
last
week
and
I
was
like
oh
yeah
I'll
put
something
in
the
agenda
and
talk
about
it,
a
couple
of
minutes,
but
then
I
was
like.
Does
anyone
have
anything
to
write
about
the
blog
post
he's
like
no
silly
write,
a
blog
okay,
which
is
brilliant?
Okay?
A
A
Jen
thought
was
pretty
cool.
We
don't
have
a
lot
of
things
to
put
on
her
on
backdrops
wall
yet,
but
we
got
a
little
certificate.
I'm
not
super
fluent
in
Spanish,
but
I
think
it
says:
I,
don't
know
what
it
says
we'll
have
to
translate
it,
but
it's
really
cool
it's
in
Spanish
in
its
place.
It's
like
a
little
thank
you
for
coming
to
present
on
back
jahvid
conference.
I.
Think
that's
exactly
what
it
says,
but
I
can't
can't
don't
know
for
sure.
A
So,
no,
no
it
just
but
anyway,
I
think
that's
a
good
it's.
So
that
was
really
exciting.
There
was
that
we
were
received
really
well
in
Mexico.
There
are
a
bunch
of
people
who
were
super
enthusiastic
about
backdraft.
There
were
a
bunch
of
people
who
hadn't
heard
of
it
yet,
but
when
we
told
them
about
it,
they're
like
oh,
that
seems
great
and
there
were
a
bunch
of
people
who
kind
of
I'm,
not
sure.
A
B
A
So
we
did
some
work
on
our
slides
and
an
idea
that
we
had
that
we
thought
would
have
been
really
great
is
to
translate
our
contribs
set
into
Spanish,
so
that
anyone
who
wanted
to
give
the
talk
in
Spanish
could
do
that.
We
also
thought
it
would
be
good
for
us
to
give
the
talk
in
English,
but
have
slides
that
were
in
Spanish,
so
that
people
who
didn't
necessarily
understand
that
what
what
we
were
saying
could
read
the
slides
and
we
tried
to
get
that
together.
A
But
the
person
that
I
approached
about
translating
them
had
a
really
hard
time
without
the
context
of
what
we
were
saying
and
maybe
not
understanding
thanks.
We
were
talking
about
anyway,
just
because
they
weren't
as
familiar
with
backdrop.
So
if
we
get
some
help,
translating
those
slides,
I
think
that
would
be
really
good
too
and
then
our
friends
in
Mexico,
who
want
to
give
the
talk
and
could
could
take
from
the
slides
what
they
wanted.
So
right
now,
there's
an
English
in
a
Spanish
version
of
the
slides
in
the
high
github
repository
they're.
A
Spent
a
bunch
of
time
with
hey
Zeus,
I
I,
don't
remember
specifically
talking
about
I,
mean
I,
guess
there
were
there's
a
bunch
of
excitement
about
like
josh
and
drupal
console
working
together
now,
which
is
kind
of
cool,
but
it
was
actually
one
of
the
first
questions
we
got
at
the
end
of
our
session.
Was
somebody
raised
their
hand
and
they
were
like?
Do
you
have
a
command-line
solution
for
backdrop
and
then
hey
Zeus
walked
in
the
room
like
right.
Then
we
were
like
oh
hi
you're
here.
A
C
Hey
Zeus
is
expressed
enthusiasm
for
a
backdrop
console
tool,
but
that's
I
mean
he's
basically
like
yeah
I
totally.
We
could
totally
make
another
one
I
think
that's
his
his
perspective
is
he
thinks
it
would
make
a
lot
more
sense
to
make
a
separate
tool.
Obviously
that's
what
he
did
for
for
Drupal,
8
and
I
think
his
plan
for
Drupal,
like
right
now,
drupal
console
obviously
only
works
on
Drupal,
8
and
I.
C
Think
his
plan
moving
forward
is
that
he'll
just
make
a
separate
version
for
every
version
of
Drupal,
and
so
if
we
were
to
make
a
backdrop
console,
for
example,
it
would
just
be
oh
yeah.
You
can
totally
just
take
this
and
I'll
just
you
know,
change
it
into
being
all
backdrop
stuff.
Instead,
it
would
be
a
little
bit
weird,
though,
because
it's
definitely
architected
in
a
way
that
meshes
better
with
Drupal
8,
like
all
the
templates
for
code
generation,
all
twig
templates,
for
example.
D
My
name
is:
live
at
this
island
rush,
9
that
they're
making
a
big
move
to
Symphony
components.
So
I,
don't
know
how
you
feel
in
general
about
I,
don't
know.
I
waver
on
this
all
the
time
doing
something
native
for
backdrop
or
sticking
with
rush
dress
has
a
good
community.
We
get
good
support
from
them.
They're
very
nice
people,
I,
don't
know
no
I,
don't
know
what
the
right
architecture
decision
is.
Yeah.
C
I
think
for
the
short
term,
our
plan
has
always
been
a
good
one
that
getting
dressed
support,
even
if
it's
only
liked
rush
aight
support,
because
that
the
new
version
of
josh
probably
also
won't
work
with
triple
seven
in
the
near
future
and
having
drush
support
makes
it
so
that
we
can
get
things
like
pantheon
functioning
and
people
that
are
using
deployment
scripts
and
getting
at
least
getting
them
something
and
getting
that
working
for
for
the
the
most
basic
usage
and
then
yeah.
Where
we
go
long
term,
we
you
know
were
all
open
to
options.
G
C
So
we
ran
out
of
time
to
do
a
real,
in-depth
questions.
Jenny
talk
to
the
bunch
of
people.
Afterwards,
though
I
know
I
didn't
manage
to
rope.
Anybody
into
contributing
like
a
lot
of
people
were
really
interested
in
the
existence
of
the
project
and
using
it,
but
actually
being
like.
Oh
I,
really
want
to
help.
We
might
not
have
pushed
that
angle
enough.
We.
A
But
I
think
that
the
my
big
takeaway
from
this
was
just
kind
of
to
try
and
insight
more
more
interest
like
the
very
beginning
of
that
process.
But
there
are
definitely
people
are
like.
How
can
I
help?
What
can
they
do
it?
It's
like,
oh
well,
so
much
stuff,
they're
like
I,
don't
know
anything
yet
and
it's
like
that's
fine,
just
use
it
first
and
see
what
you
think
and
then
tell
people
what
you
thinking
they're
like
oh
I,
could
do
that
so
I
thought
it
went
pretty
well.
A
All
right,
let's
see
so
yeah
I'll,
write
up
a
quick
blog
post
about
that
excellent
idea
and
then
yeah.
Two
weeks
from
now,
the
folks
at
Cal
emunah
are
going
to
write
a
blog
post
about
the
cowl
box
version.
Just
came
out
in
fact
drop
support,
which
I
think
will
be
great.
It's
called
actually
give
it
a
try,
it
might
have
some
screenshots
and
it
showing
you
how
the
backdrop
stuff
works
or
link
to
the
docker
image
for
backdrop,
all
of
that
good
stuff.
So
we'll
keep
our
eyes
out
for
that.
A
If
anyone
has
anything
they
want,
but
on
the
blog
between
now
in
the
28th
definitely
have
room
for
that
or
if
they
want
to
go
and
scheduled
for
later
more
time
to
write
whatever
do
that
as
well.
It
needs
post
and
there
when
it's
ready,
we
are
trying
to
get
a
little
bit
better
about
sending
newsletters.
We
missed
one
month,
but
we
are
going
to
try
and
send
a
newsletter
every
month
this
year,
from
now
on
out
and
I
figured.
A
Here's
the
use
cases
and
examples
of
success
stories
and
also
like
share
what
you've
done
and
it'll
get
people
to
kind
of
give
back
and
start
using
that
that
section
of
the
site
too,
all
right,
let's
see
if
anyone
else
is
help
interested
in
helping
us
with
marketing
for
backdrop,
we
do
have
a
whole
tag.
In
the
backdrop,
CMS
torque
you
with
issues
that
might
help
us
get
the
word
out,
and
there
are
a
couple
of
new
things
that
I
just
thought
of
this
week.
A
Somebody
mentioned
that
you
can
set
up
if
you're
using
phpstorm,
you
can
set
a
backdrop
project
as
a
Drupal,
7
or
triple
eight
project.
It
will
be
great
if
we
had
a
backdrop
project
for
phpstorm
too,
since
they've
been
so
supportive
of
us.
It
would
be
great
if
we
could
get
kind
of
a
setup
that
works
for
backdrop.
A
That
does
the
you
know
core
code
in
the
core
directory,
but
also
the
function
lookups
like
all
the
stuff
that
you
want
for
a
Drupal
project
would
work
the
same
way
for
a
backdrop
project
but
kind
of
halfway
between
seven
and
eight.
So,
if
anyone's
interested
in
doing
that,
that
could
be
kind
of
a
fun
side
project,
there's
also
a
bunch
of
stuff
like
getting
backdrop
CMS
on
Wikipedia.
A
If
anybody
loves
tinkering
with
Wikipedia
pages,
just
to
kind
of
help
us
put
ourselves
on
the
map,
there
are
things
that
are
not
related
to
the
website
or
the
newsletter
or
the
code
itself
that
we
could
use
some
hot
boys.
So
those
issues
are
all
on
the
doctor,
I've
seen
as
to
org
q
under
the
tag
audience
dash
marketing
all
right,
let's
go
back
to
back
drop
CMS
the
project
itself.
Nate.
Do
you
want
to
give
us
an
update
on
a
latest
release
or
upcoming
release.
C
Right
sorry,
next
bug-fix
release
is
one
point
three
point:
five
there's
been
a
couple
of
minor
fixes
that
have
gone
in
but
and
I'll
probably
find
some
more
and
merge
the
men
in
the
next
week.
It's
really
likely
that
we'll
have
a
release.
Next
Wednesday
there's
the
security
window
at
that
time,
and
so
there
may
be
release
coming
out
that
day,
yeah
likely
to
see
a
release
next
Wednesday
for
the
next
bug
fixing
release.
C
So
if
there's
any
minor
niggly
issues
that
you'd
like
to
get
fixed
be
a
great
time
to
review
other
people's
work
or
get
somebody
else
to
review
your
own
work
and
we
love
to
get
those
fixes
in
and
those
just
as
needed.
Many
bug
fixes
that
you
encounter
just
file
them
and
we
will
fix
them
as
soon
as
possible.
C
The
first
item
on
this
list
here
we've
got
references,
module,
I,
mean
references,
module
is
issue
1301
and
honestly,
it's
like,
unfortunately
like
the
biggest
item
and
probably
the
most
important
item,
and
probably
the
one
that
is
also
not
very
far
along,
and
so,
if
there's
any
motivated
developers
out
there,
that's
the
one
that
really
could
use
the
most
help
right
now.
I
think
that
it's
unfortunately
it's
like
not
even
not
like
a
testable
state,
it's
just
in
like
a
starting
prototype
state.
So
we
could
use
some
additional
effort
there.
It's
issued
1301.
C
We
might
also
reach
out
to
Mike,
because
I
know
he
was
really
excited
about
taking
this
on.
But
then
he
moved
up
to
Portland
and
got
a
new
job,
and
so
life
is
derailed.
That
feature,
but
it's
still
really
important
to
us.
It
doesn't
make
it
into
one
point,
for
that
doesn't
mean
we'll.
Never
have
it
just
means
that
it'll
be
an
additional
four
months
away,
so
what
things
could
be
worse,
but
it
would
be
great
to
get
that
pushed
forward.
C
C
It's
really
good
I
think
that
it's
it's
ready
for
marriage.
This
next
week,
I
filed
a
pull
request
about
two
weeks
ago
that
built
on
top
of
Jeff's
work
that
just
did
some
UI
consistencies
things
like
made
it.
So
we
use
drop
buttons
started
using
the
responsive
columns
that
we
have
in
core
tightly
integrated
it
a
little
bit
better
in
between
path
Otto
and
redirect
so
that
they
cross
reference
each
other
correctly
because
they're,
both
in
cornell,
and
I
think
that
that's
really
pretty
much
ready
to
go,
oh
and
fix
the
tests.
C
So
unless
there's
any
other
big
issues
there
I'd
love
to
get
some
more
testing
on
it.
If
you
guys
would
like
to
provide
feedback,
but
I'll
probably
give
that
one
more
read
through
and
then
merge
that
in
the
next
week,
which
is
exciting
because
that's
huge,
let's
see
redirect
modules
issue
9
05,
if
you
would
like
to
take
a
look
at
it,
I
just
actually
I
just
updated
the
issue,
but
if
you
find
the
poor
is
down
there
at
the
bottom
of
the
issue,
you
can
try
out
the
demo
and
make
sure
it
works.
C
C
We
had
a
design
meeting
just
before
this
one
and
Wes
gave
us
an
update
on
the
new
front.
End
theme
I
think
that
one
of
the
takeaways
from
that
that
meeting
that
we
thought
was
a
pretty
good
idea-
is
that
what
we're
thinking
about
doing
is
shipping
a
new
front,
end
theme
with
backdrop
potentially
not
making
it
the
default
one.
C
So
that
way,
it'll
be
there
and
you
can
try
it
out
and
it'll
give
people
an
alternative
when
they
first
install
backdrop,
but
we
can
generate
more
feedback
from
it
being
in
court
and
getting
it
in
front
of
more
eyes,
but
not
necessarily
putting
all
of
our
eggs
into
that
basket
as
being
our
default
theme,
so
that
might
be
happening
as
well.
That
will
put
it
in
and
then,
rather
than
making
a
follow
up
to
make
it
the
default.
Well,
maybe
we
will
make
a
follow-up,
but
it
won't
be
for
1.4.
C
Yeah,
but
that's
that's
a
great
issue
as
well,
if
you're
looking
at,
if
you're
looking
for
something
to
contribute
to
issue,
1361
wes
is
looking
for
additional
feedback
on
the
theme,
it's
looking
great,
mostly
requiring
feedback
at
this
point
issue
698
is
adding
new
core
layouts
22
backdrop
core,
so
that
there's
more
things
other
than
the
four
layouts
that
we
ship
with
I
posted
an
issue
to
that
or
a
comment
to
that
issue.
I
think
that
we
should
officially
table
that
one
there
hasn't
been
any
progress
on
it
and
priority
wise.
C
We
need
to
figure
out
exactly
what
we're
doing
there
like.
We
would
still
like
it's
ambiguous
because,
like
how
cores
and
layouts
interact
with
each
other
hasn't
been
totally
solidified
yet
and
I.
Think
having
you
know,
our
new
core
theme
will
be
a
great
start
to
us
resolving
those
issues
of
like,
what's
in
theme
and
what's
in
the
layout,
and
then
we
can
work
on
adding
the
new
layouts
in
the
next
release
and.
A
But
it
would
be
good
to
just
kind
of
figure
out
like
what
how
layouts
and
themes
should
work
together,
and
we
shouldn't
put
the
layout
in
without
at
least
you
know,
resolving
some
of
these
questions.
Even
if
we
don't
actually
have
code
that
can
go
into
the
next
release
for
layouts,
just
to
make
sure
that
we're
not
putting
encoding
theme
that'll
make
it
so
that
we
can't
put
in
the
layouts
of
what
we
want
to
do
it
in
the
future.
So
I
agree
that
will
probably
won't
get
it
done,
but
I
think
maybe
we
should.
C
Well,
so,
in
the
last
item
that
we
have
on
here
of
the
items
that
were
scheduled
for
1.4
is
improving
the
rich
text
editor,
which
is
you
1087
and
that's
meta
issue.
One
item
we
definitely
need
to
make
sure
we
get
done
is
upgrading
ckeditor
to
the
latest
version.
There's
been
a
couple
of
minor
releases
since
backdrop
was
released
and
I
know
gee
fad,
whose
real
name
I
don't
know,
but
his
screen
name
is.
C
So
I
think,
if
we
can
start
just
by
upgrading
ckeditor,
that
might
kind
of
unblock
the
way
for
him
to
start
iterating
on
little
pieces
one
at
a
time,
so
that
we
can
get
everything
in
that
makes
sense,
rather
than
putting
in
a
whole
bunch
of
stuff
all
at
once.
That
might
not
necessarily
mesh
real
well
together.
C
Okay,
the
other
things
that
we've
got
user
interviews,
ER
experience
improvements,
we've
got
two
items
in
here,
one
of
which
is
almost
certainly
going
to
happen
and
that's
a
project
browsers
issue.
1399
doc.
Belmont
has
been
totally
rocking
this
and
he
was
here
earlier
in
the
meeting
and
he
dropped
out
so
I'll.
Give
an
update
on
that
that
this
is
super
really
close,
I've
been
trying
it
out
and
you
can
do
so
in
the
live
sand
boxes
and
I've,
given
it
to
thorough
code
reviews
and
it's
looking
great
like
it's
really
exciting,
it's
very
cool.
C
It
also
separates
update
module
from
the
ability
to
install
modules,
because
right
now,
if
you
have
update
module
turned
on,
it,
also
allows
you
to
install
modules,
which
is
very
strange
that
those
two
things
are
tied
together,
and
this
makes
it
so
that
the
new
installer
module
will
be
respond
before
installing
modules,
as
well
as
the
project
browser.
An
update
module
just
be
responsible
for
telling
you,
if
updates,
are
available,
so
very
cool.
C
That's
issue
1399,
there's
a
couple
of
new
bugs
and
I
guess
that
some
tests
are
failing
and
we
also
need
to
expand
them
slightly.
But
I'd
say
that's
the
major
hold
up
for
project
browser
we're
also
mentioned
during
the
design
cullet.
We
would
like
to
get
design
feedback
on
the
way
that
project
browser
looks,
but
that
can
be
done
as
a
follow-up,
really
like
it's
great
that
we,
the
functionality,
is
there
and
it's
working,
and
it's
so
much
better
than
what
we
have
now.
C
C
That
generally
wraps
up
our
meeting
every
thursday
is
backdrop
day
we
have
sprints.
Before
and
after
these
meetings
we
usually
meet
up
in
the
github
issue:
queue
github
com,
/
backdrop
and
then
there's
a
sub-project
backdrop.
Issues
is
where
l
or
issue
queues
happen.
We
also
interact
in
real
time
on
Gator
Gator
dot,
IM
/
backdrop
/
backdrop
issues.
We
have
an
IRC
channel,
although
we're
starting
to
abandon
it
kind
of
in
mass
for
get
er,
it's
in
pound
backdrop
on
freenode
and
we
have
a
reddit
channel
reddit
com,
/
r
/
backdrop.
C
Again,
though,
really
getter
and
github
are
the
primary
means
of
communication.
If
you're
looking
for
us
look
there,
we
also
have
an
ical
feed
of
upcoming
backdrop.
Events
as
well
as
events
listed
on
backdrop,
CMS,
org,
backdrops,
even
stored,
/
events
books.
This
is
also
kind
of
exciting
migrating
from
Drupal.
The
backdrop
was
the
first
ever
backdrop
book
it's
available
on
from
a
press
or
on
amazon
com.
Just
look
for
migrating
from
Drupal
to
backdrop
CMS,
and
it's
also
really
exciting.
C
Beginning
backdrop:
CMS
hits
shelves
quarter,
2,
2016
or
more
accurately,
it's
actually
shipping
or
going
to
press
his
next
week,
which
is
really
exciting.
I
wrote
a
foreword
or
the
book
and
sent
that
out.
Eric
I
know
you're
also
deeply
involved
in
in
that.
So
maybe
I
should
have
let
you
say
something
about
it,
but
its
ability.
It's
really
exciting
that
that's
that's
happening
in
the
near
near
future
and
that's
all
I've
got
all
we've
got.
G
Yeah
I
kind
of
I
think
I
emailed
you
all
about
it,
but
I'm
eager
to
hear
so
I'm
gonna
ask
here
what
the
progress
is
on
civis
erm
for
backdrop.
I
have
a
few
clients
who
have
one
who's,
definitely
using
a
backdrop
and
one
who
got
so
burnt
by
some
stuff
in
Drupal
8
that
they
want
to
use
backdrop.
So
I
was
curious
where
that's
wrong.
A
Just
going
to
say,
I
haven't
actually
done
any
work
on
it
recently,
but
I
know
that
somebody
else
showed
up
an
issue
queue
and
started
using
it
and
fixing
stuff,
which
is
fantastic.
So
I'll
take
a
look
at
that
today
and
see
where
it
stands.
I
know
it
is
approaching,
may
and
we're
supposed
to
be
giving
a
talk
on
it
see
end
of
may
so
we
doing.
E
C
A
I
gotta
get
it
ready
by
then.
I
would
expect
that
the
most
of
the
work
that's
left
is
pretty
straightforward,
I'll,
take
a
look
at
what
hasn't
been
covered
yet
and
see
if
we
can
at
least
get
a
bullet
list
of
like
these
are
the
things
that
we
know
don't
work
and
then
that
way,
it'll
help
you
inform
like
what
do
they
need?
What
do
they
don't
need
if
we
need
to
work
on
those
things
for
your
projects
or
not
yeah,.
C
B
C
Profiles
and
sevilla
integration
with
user
accounts
updated
the
install
files,
so
that's
working
now,
apparently
hook
install,
wasn't
quite
functioning
correctly.
So
now
that
works
correctly,
but
he's
got
four
other
issues
that
he's
opened.
That
are
things
that
are
clearly
not
working
like
integration
between
the
toolbar
and
savee
member
rolls
and
group
roles
he
says,
are
all
not
quite
functioning
so
but
yeah,
it's
all
been
pretty
straightforward,
porting
jobs,
but
we
have
been
saying
some
great
movement
there,
thanks
to
herb.
G
G
I
think
that,
but
they
might
also
try
to
commit,
we
have
a
client
who's
interested
in
maybe
funding
half
of
it
but
I
like
them.
I
try
to
commit
to
porting
web
forms
to
the
CRM
the
backdrop
as
soon
as
saveas
ready
enough
for
it,
which
it
might
be.
We
might
start
within
that
so
I
think
that's
probably
gonna
be
a
go.