►
Description
Today’s development agenda: http://bit.ly/1ORVBts
A
All
right,
happy
Thursday,
January,
21st
everybody.
It
is
a
monumentous
occasion
for
backup.
Actually
it
was
last
week,
but
this
is
our
first
meeting
since
we've
gotten
to
talk
and
celebrate
all
the
amazing
things
that
happened
so
I'm
happy
one
point
three
point:
X
everybody
we're
now
in
the
future:
hey,
let's
see
general
announcements,
obviously
backed
up
one
point.
Three
point:
O
was
released
last
Friday
with
much
fanfare
and
a
celebratory
chip
to
our
local
curry.
Restaurant
know
what
you
guys
did
to
celebrate,
but
we
have
a
good
time
we
were
here.
A
I
just
wanted
to
say.
Like
I
know,
there
was
a
little
wall
on
development.
At
the
end
of
the
years,
everybody
was
trying
to
get
ready
all
of
their
normal
work
and
stuff,
but
come
holiday
season
was
like
nobody
had
anything
to
do
but
work
on
backdrop,
and
we
got
so
much
amazing
things
done.
It
was
just
like
four
solid
weeks
of
backdrop,
progress
and
we
ended
up
getting
so
much
done
for
the
1.3
release
and
then
in
the
final
hours
there
it
was
fantastic
to
have.
You
know.
A
I
was
just
like,
isn't
an
interesting
idea.
I'm
just
gonna
assign
it
to
jeff,
and
then
it's
likely
I
emerged
that
and
I'm
like
what
like
I,
didn't,
even
see
it
between
when
I
was
like
idea
to
like
finish
so
there's
just
so
much
tougher,
everybody
was
contributing
and
revealing
things,
and
we
got
a
bunch
of
feedback
in
1.3
is
a
fantastically.
A
So
thank
you
to
everybody
who
pitched
in
and
did
a
ton
of
work
right
there
at
the
very
end,
helped
us
kind
of
make
it
as
fantastic
as
it
was
for
those
of
you
who
haven't
seen
it
Nate
published
the
blogpost.
Yesterday,
it's
a
factor
of
CMS
to
org,
slash
news,
our
new
news
section
on
the
top
closer
Scott,
really
cool
animated
gifts
and
stuff
with
their
demonstrating.
Some
of
the
great
new
features
that
we
have
I
am
so
excited
to
start
using
it.
A
I
can't
wait
to
to
build
new,
sights
on
it
and
upgrade
my
old
sites
and
get
everybody
running
the
latest
and
greatest
so
cray
other
general
announcement.
Obviously
we
have
t-shirts
and
hoodies.
If
you
want
to
celebrate
your
dragon,
pred
put
them
on.
If
you
don't
have
one
yet
you
can
order.
One
factor
of
CMS
org,
slash,
contribute
you
make
a
donation,
will
send
you
things,
glass,
I,
hope
you
got
your
things.
A
Yes,
okay,
good.
We
sent
a
bunch
out
in
the
last
few
weeks,
I
I
forgot
to
follow
up,
but
that's
good
and
we
also
have
new
phpstorm
licenses
for
backdrop
contribs.
So,
unfortunately,
if
you're
a
core
developer,
you
don't
get
one,
but
if
you're
a
consumer
we
can
give
you
I
backdrop
a
license
for
phpstorm.
So
if
you
are
a
member,
a
backdrop
contribute
and
send
an
email
to
info
backdrop,
CMS
network.
If
you
have
a
pending
application,
we
have
a
pending
license
key
for
you
and
we'll
help
get
you
over.
A
Whatever
hurdles
are
necessary
in
order
to
get
your
license
key
to
get
you
involved
in
and
all
that
stuff.
So
that's
that
no
significant
updates
from
the
project
management
committee.
So,
let's
turn
it
over
to
Nate
for
community
growths
yeah.
C
B
Talk
about
all
of
our
releases
when
I
get
done
to
that
schedule,
but
to
that
part
of
the
schedule,
but
a
community
growth
we've
had
five
new
projects
published
in
the
backdrop,
contribute
that's
awesome
since
last
week,
bringing
our
total
to
195
total
projects
for
backdrop.
There
are
118
projects
with
official
releases
that
have
been
published
on
backdrop,
CMS
org,
that's
two
more
since
last
meeting
and
there's
been
four
new
releases
of
said
projects
since
last
week,
bringing
the
total
260
we've
had
45
or
we
have
45
total
contributors.
B
There's
a
couple
more
in
the
application
process.
Right
now,
one
has
actually
already
been
approved,
but
we're
waiting
for
him
to
accept
the
conservative
Riemann,
which
is
great,
and
there
are
80
total
user
accounts
on
backdrop,
CMS
org,
12,
new
signups
since
last
meeting,
so
really
great,
really
excellent
growth.
That's
great
to
see
I
love,
seeing
those
new
contributor
belapur
is
coming
in
I.
Think
that's
what
gets
me
most
excited
when
I
go
over
this
every
week.
B
If
you're
interested
in
joining
the
backdrop
contribute,
you
can
do
so
by
visiting,
get
calm,
/
backdrop
dash
off
/
can't
rib
and
that's
our
issue
queue
where
we
handle
all
contribs.
That
URL
is
also
at
the
top
of
the
contribute,
which
is
github.com
/
backdrop
dash,
can't
rib
yeah.
That's
all
I've
got
to
say
about
that.
Let's
see,
let's
roll
right
into
infrastructure
infrastructure
is
our
things
around
the
the
backdrop
project.
Like
backdrop,
CMS
org,
github
integration,
drush
things
like
that
update
checking
for
back
to
fcms
org
gosh.
B
We
really
need
to
get
this
one
just
removed
from
our
list
because
it's
been
updating
has
been
working
for
ages,
but
our
analytics
script
isn't
running.
The
thing
that
we're
holding
off
on
is
that
Travis
CI
right
now
is
currently
reporting
its
usages
into
our
our
totals,
and
so
it's
screwing
up
all
the
analytics
because
the
more
pull
requests
we
have
like
the
past
couple
of
weeks
before
the
release
of
1.3.
We
have
spikes
and
usages,
and
then
it
goes
back
down
afterwards,
because
Java
Sea
is
reporting
itself
as
being
an
installation.
B
So
we
need
to
get
that
fix
or
we'd
like
to
get
it
fixed
before
we
crunch
all
of
our
numbers
to
generate
our
historical
usage
data
after
we
get
that
in
place.
We
would
also
like
to
start
tracking
individual
features
that
are
used
within
backdrop.
Things
like
you
know
what
color
schemes
people
are
using.
B
What
core
modules
they've
turned
on
what
controls
inside
of
contribs
they've
turned
on
certain
settings
like
why
they
don't
have
clean
urls
we'd
like
to
get
all
of
those
things
being
tracked,
and
then
that
way
we
would
be
able
to
see
like
which
features
are
being
used
and
which
ones
aren't
or
which
core
modules
never
get
turned
on
those
sorts
of
things,
although
that
actually
doesn't
need
to
wait
at
all.
It
can
happen
at
any
time,
and
that's
in
a
lot
of
these
issues
are,
in
the
backdrop,
CMS
org
q
and
that's
issue
99.
B
Where
we're
trying
to
talk
about
what
kind
of
features
we
would
like
to
collect
specifically
from
individual
sites
and
that
that
will
take
a
little
bit
of
coordination,
because
we'll
need
to
build
out
functionality
in
core
an
update
module
and
we'll
need
to
build
out
the
functionality
on
backdrop,
see
messed
up
org
to
actually
calculate
and
accrue
that
data.
So
that's
definitely
going
to
take
a
bit
of
work
in
a
bit
of
time
to
actually
bring
that
to
fruition.
B
Dress
for
backdrop,
Josh
for
backdrop
is
issued.
Number
47
in
the
backdrop,
is
your
cue:
we've
had
a
working
prototype
for
a
couple
of
weeks
and
I've
just
been
working
on
improving
it
and
fixing
some
issues
in
there.
It's
really
on
my
plate
and
I
I
swear
god
it'll
happen
this
week
to
move
that
into
the
contribute,
and
once
it's
in
the
control
group,
I'm
going
to
give
jeff
communiqués
this.
Actually
I
don't
need
to
give
him
command
axes
because
he'll
already
have
it
but
I'll.
B
Let
him
miss
him
maintainer
in
the
readme
file
to
make
it
so
that
he
can
actually
start
working
on
fixing
those
issues
directly,
because
I
know
these
already
fixed
a
couple
of
them
and
it'll
be
great
to
get
them
into
the
official
project
and
give
the
official
project
into
the
contribute.
So
the
more
people
can
work
on
it.
Besides,
just
my
my
little
sandbox,
let's
see.
B
B
So
what
we've
been
doing
is
we've
used
to
separate
repositories,
14
issues
and
one
for
the
code
itself
and
we'd
like
to
make
it
so
that
when
you
make
an
issue
and
you
label
it
as
having
like
a
pull
request
and
that
it
needs
review,
it
would
also
update
the
corresponding
pull
request
to
keep
those
tags
and
sync
to
make
it
so
that
we
can
see
which
pull
requests
need
work
brushes,
which
pull
requests
are
just.
You
know,
just
like
proof
of
concepts
and.
A
B
But
that
brings
us
to
the
next
item
on
the
list,
which
is
backdrop
CMS
org,
one
of
the
primary
things
we'd
like
to
do
on
backdrop
CMS
or
has
had
some
kind
of
single
sign-on
that
uses
your
github
credentials
and
that
single
sign-on
actually
is
what
empowers
to
do
a
lot
more
than
just
log
into
the
website.
It
really
would
be.
B
Releases,
the
oid
one
on
by
KFC
mr.
Dargis
prop
so
drop
drop,
owns
all
releases
it
it's
fine,
so
anyway,
single
sign-on
with
github
we'd
love
to
get
integrated
into
backdrop,
CMS
org,
and
it
will
encourage
to
do
all
kinds
of
other
integrations
between
our
website
and
get
have
once
we
have
that
information.
A
Little
differently,
I
really
like
the
way
drupal.org
has
like
that
reference
field
that
you
can
use
on
a
person
to
say,
I'm,
part
of
a
company.
You
can
do
it
on
a
comment
to
to
attribute
whatever
I
think
it'll
be
great
if
we
could
kind
of
figure
out
the
same
sort
of
architecture
model
where
you
can
say,
I
work
for
a
company.
A
The
company
provides
these
services
and
then
you
know
if
a
company
was
involved
in
this
case
study
just
so,
you
can
get
all
those
kind
of
references
every
way
and
I
think
our
current
supporter
field
might
not
be,
or
a
current
supporter
list
might
not
be
adequate
for
that.
So
we
might
just
create
something
new
and
then
we
can
change
it
around
without
worrying
about
getting
rid
of
anyone's
data
accidentally.
A
B
Okay,
so
yeah,
we
would
like
to
have
it
an
event.
Calendar
of
some
kind
is
also
on
the
docket
for
backdrop
CMS
org
have
we
had
any
ideas
about
how
we
would
like
to
that.
We
thinking
like
nodes
with
date
module
or
we
thinking,
google
number
or
what
sort
of
solutions
everything
now.
B
B
We
also
have
some
issues
to
improve
the
interfaces
for
finding
modules,
themes
and
layouts.
There's
meta
issue
over.
In
the
backdrop,
sea-mester
org
issue,
issue
95
that
covers
some
design
elements
that
weren't
quite
completely
implemented,
as
well
as
some
abilities
like
sorting
on
usage
information
right
now.
B
Gotcha,
why
don't
you
go
into
news
and
announcements
Josh
or
so.
A
News
this
week,
obviously
one
point
three
point:
0
is
our
most
exciting
thing
on
the
blog
post
is
up
at
the
at
the
news
section.
If
you
want
to
look
at
that
now,
our
next
vlog
on
the
schedule
is
currently
for
februari
sadness.
Sorry
februari
everywhere,
a
fifth
I
think
I
got
that
date
round
and
it's
going
to
write
up
yeah
it's
on
your
voice.
A
That's
only
I,
don't
think
Drupal
7
has
PHP
seven
support
yet,
so
it
also
be
a
good
differentiator
between
trying
to
figure
out
whether
you
want
to
build
the
new
backdrop
cider
in
a
Drupal
7
site.
If
we
could
do
speed
test,
compare
since
that
might
be
kind
of
fun,
so
that's
coming
soon
and
we've
also
been
getting
a
whole
bunch
of
great
ideas
from
the
larger
community
about
things
we
should
put
on
our
blog
I
received
a
great
blog
post
from
Graham
first
draft
this
morning
about
theme,
development
for
backdrop
and
I.
A
Think
that
would
be
good
because
we
don't
have
a
lot
of
voices
about
theming
elsewhere,
using
the
blog
to
kind
of
showcase.
How
people
have
done
things
like
tips
and
tricks.
I
think
might
be
a
great
place
to
do
that.
I
also
open
a
new
issue
in
the
queue
this
morning
about
a
community
spotlight,
type
blog
post
thing,
which
name
would
be
great,
where
we
can
kind
of
get
feedback
from
various
people
in
the
community
and
maybe
get
some
good
questions
going
about.
What?
A
What
do
you
want
to
know
about
people
in
the
community
and
kind
of
set
up,
maybe
an
interview
format,
so
we've
got
some
ideas
about
other
things
put
on
our
blog
coming
up
soon
as
well.
So
I
was
thinking.
We
could
sprinkle
these
other
posts
kind
of
between
all
of
beneficial,
especially
officially
scheduled
lead
posts
as
I
get
ready.
A
We
can
just
kind
of
post
them
an
art,
so
anyone
else
has
any
ideas
about
anything
we
should
blog
about,
even
if
it's
like
a
case
study
of
a
site
on
back
draft
and
them
like
that,
we
could
definitely
squeeze
that
into
so
I
had
a
comment
to
the
issue:
issues
number
158:
if
you
have
something
you
wanted
a
blog
and
we
can
get
it
scheduled
and
we
also
have
a
bunch
of
other
stuff
coming
up
since
1.3
just
came
out,
we
have
gotten
on
the
blog
or
on
the
podcast
rotation
for
a
bunch
of
different
groups,
starting
this
Friday
we've
got
a
drupal
easy
podcast.
A
A
Know
what's
going
on
in
Drupal,
8
anymore,
but
I
know
what's
going
on
in
backdrop
and
they're
like
dr.
up
with
a
lot
of
backtrack,
so
that
was
really
exciting
that
they
were
so
thrilled
about
wanting
to
get
backed
up
on
their
schedule.
New
life
like
tabula,
backed
up
now,
actually
our
next
our
next
spot.
A
We
need
that
to
be
back
okay,
so
we're
gonna,
try
and
come
up
with
a
webinar
content
which
will
be
fun
and
that's
currently
scheduled
for
you,
weary
24th,
which
was
their
next
webinar,
so
that'll
be
fun,
and
then,
of
course,
as
we
get
more
things
on
the
schedule
Wolfram
in
here
and
talk
about
them
to
cool
stuff,
let's
see
next
on
the
list
is
backdrop
itself
Nate.
Do
you
want
to
talk
about
all
the
little
releases
yeah.
B
So
we
had
a
weird
a
strange
week
of
releases
so,
as
everybody
knows,
dr.
up
one
point:
three
point
o
came
out
on
january
fifteenth,
which
was
friday,
and
it
was
great
that
it
came
out.
We're
all
excited
a
bunch
of
people
that
are
on
this
call,
actually
all
updated
their
websites
and
then
reported
feedback.
Saying
yay
work.
Cia
is
so
exciting.
The
upgrade
went
so
well,
which
is
fantastic,
that
it
went
well
for
most
people.
B
Although
I
found
out,
we
found
out
that
there
were
a
couple
of
issues
that
they
cropped
up,
and
so
we
had
one
issue
with
background
fetch
that
it
was
causing
a
PHP
notice
on
every
cached
page
serve,
but
it
wasn't
very
visible
because
the
notice
was
happening
after
the
page
had
been
delivered.
So
it
was
basically
just
filling
up
people's
logs,
which
is
kind
of
a
largest
largest
large
ish
ish
issue,
and
so
so
we
made
one
dot
3
dot,
one
to
fix
that
problem.
B
Just
yesterday
that
got
pushed
out,
but
then
in
the
process
of
pushing
out
the
updates
to
pantheon.
We
also
noticed
that,
when
you're
upgrading
from
an
older
backdrop,
sites
to
13
that
your
color
scheme
goes
from
blue
to
black,
which
was
not
supposed
to
happen,
we
did
a
bunch
of
work
making
it
so
that
people's
color
schemes
specifically
would
stay
exactly
as
they
were
in
fact,
and
so
that
caused
another
issue.
That
was
was
a
pretty
jarring
for
people
upgrading,
and
so
we
made
one
dot-to-dot
or
132.
B
So
it
was
quite
a
week
when
three
releases,
but
just
this
past
week,
which
I
guess
is
kind
of
to
be
expected
when
we
make
a
new
minor
release
that
once
it
gets
into
a
broader
testing
sphere,
that
it
became
a
you
know,
obviously,
a
lot
more
people
start
using
it,
and
so
the
problems
become
more
obvious.
So
our
current
version
is
132,
which
is
exciting.
It's
currently
the
version
that
is
available
for
download
on
backdrop,
CMS
org.
It's
also
pushed
up
to
pantheon.
C
B
Another
bug,
that's
right,
so
the
next
release
bug
fixing
release
will
be
133.
We
don't
have
anything
immediately
scheduled
for
that
bug.
Fixing
release
it'll
be
as
needed
if
any
other
critical
issues
come
up
or
after
we
have
accrued
enough
minor
problems
to
make
it
worthwhile
to
make
a
new
minor
regard
to
make
any
bug-fix
release,
then
we'll
put
out
that
version
just
as
needed.
B
Let's
see
one
dot
for
dot.
0
is
the
next
minor
release
which
will
be
coming
up,
May
15
2016,
and
there
are
a
bunch
of
items
that
didn't
make
it
into
one
dot:
three
that
would
be
lovely
to
get
them
into
one
dot.
For
specifically
like
a
bunch
of
the
UX
work
that
we
started
on,
we
didn't
actually
bring
it
quite
to
completion,
and
so
it's
not
in
one
dot
for
one
two:
three,
it's
not
here
in
the
agenda,
but
some
things
that
were
getting
close,
or
at
least
we
have
been
some
nice
effort
as.
B
Project
browser
in
particular
got
really
close.
It
actually
I
mean
ahead,
pull
requests,
we've
got
project
browser
server
up
on
backup,
CMS
org,
all
the
capabilities
are
there
and
actually
works,
but
it
needs
basically
like
a
usability
review
and
some
tighter
integration,
because
the
way
it's
implemented
right
now,
it's
a
little
bit
redundant
with
some
of
the
other
bits
and
pieces
in
in
project
module
right
now
or
in
the
update
module.
B
It
also
would
be,
since
we've
got
a
little
bit
more
time,
nice
to
separate
project
browser
so
that
you
could
do
the
thing
you
could
install
modules
without
needing
to
turn
on
update
module.
You
know
it's
a
little
bit
weird
that
they're
that
they're
bound
together,
but,
on
the
other
hand,
update
module
is
a
lot
less
annoying
than
it
was
in
one
dot
too,
because
of
our
new
notification
icon
moving
it
into
like
the
admin
bar
instead
of
spewing
giant
red
errors
all
over
the
place.
B
Let's
see
Weston's
work
on
it
just
got
out,
but
West's
work
on
on-field,
dy
I
also
would
love
to
see
implemented
just
kind
of
finishing,
remember,
not
finishing
field.
You
I,
like
we've,
got
a
bunch
of
different
ideas,
but
not
a
whole
lot
of
implementation.
Yet
but
finishing
up
some
of
those
UX
improvements
that
we
started
13
but
didn't
quite
bring
the
completion.
B
It
would
be
great
to
see
this
in
the
future,
so
our
schedule
data
into
one
dot
for
the
biggest
item
we've
got
here
is
we
want
to
have
references,
module
or
a
solution
like
references
module
in
core,
so
something
Universal
that
would
replace
node
reference
user
reference
term
reference.
Maybe
we'll
see
I'm
not
quite
sure
how
that
would
work
getting
rid
of
our
existing
term
references
because
they're
a
little
bit
special
they're
different
than
than
other
types
of
references.
So
we'll
see
what
kind
of
work
is
involved
in
that
issue
1301.
B
Our
plan
right
now
is
to
basically
take
a
look
at
the
capabilities
of
references
module
in
Drupal,
7
contribs,
but
we'd
like
to
largely
give
it
a
rewrite
for
consistency
with
the
way
backdrop
core,
writes
things
and
also
using
backdrop
cores
entity
integration
instead
of
entity
API,
so
that
in
in
the
references
module
d7
can't
rip,
there
is
a
lot
of
kind
of
unusual
coding
for
for
drupal,
7
and
especially
for
backdrop
like
it's
just
not.
This
is
not
very
standardized
compared
to
the
rest
of
our
core.
B
We'd,
also
like
to
add
a
redirect
module
some
kind
of
solution
like
redirect
module
in
decor.
That's
issue,
9
05.
The
primary
reason
for
this
is
because
we've
got
path
auto
and
core
and
path
auto
when
you
automatically,
when
you
change
a
title,
and
you
automatically
generate
a
new
URL
right
now,
the
behavior
for
for
those
old
patterns
old
pads
is
very
unfriendly
that
it
basically
you
can.
You
can
leave
both
of
them
there
or
you
can
delete
the
old
one,
but
the
ideal
solution
would
be
after
new
path
is
generated.
B
B
What's
yours
is
and
silently
yeah
it
I
wonder
design-wise
like
we're
going
to
need
some
assistance
on
that
I
would.
I
would
expect
andy,
says
I
thought
everyone
was
going
to
vote.
I.
Think
that's
awesome,
I
mean
sure
like
it.
If
we
have
multiple
options,
we
would
love
to
have
a
vote.
40404
who's
gonna.
Do
it
well,
I,
guess,
there's
nothing
ways!
I
could
take
that.
D
B
A
D
Person
I
was
thinking
about
working
on
an
actual
good
bootstrap
clean
implementation
for
us,
but
I'm
not
sure
if
that
was
something
we
wanted,
but
as
our
core
theme,
because
we
come
along
with
a
lot
of
extra
stuff
that
we
probably
don't
need,
but
I
imagine
most
people
start
their
site
designs
of
the
strategies.
Days,
though,
might
be
good
half
yep.
B
C
B
B
B
We'd
also
we're
also
discussing
besides
a
new
core
theme,
we're
also
talking
about
new
core
layouts.
Initially
I
guess
this
title
is
actually
still
labeled.
Add
radix
layouts
to
court.
Radix
is
a
set
of
layouts
that
are
all
Twitter
bootstrap
based
using
bootstraps,
grin
system,
we're
not
sure
about
that.
There's
been
some
back
and
forth
on
whether
or
not
that's
a
good
idea.
It's
it's!
B
It
is
interesting
that
there
are
I
mean
it
really
widens
the
options
for
how
you
can
lay
out
your
page
ads,
quite
a
few
different
layouts
that
you
can
use,
but
we're
also
concerned
about
the
the
strain
that
that
might
put
on
the
developers
that
they
would
have
to
deal
with
that.
Many
different
that
many
more
variations
of
ways
that
a
page
could
possibly
be
laid
out.
So
there's
some
back
and
forth
on
that
and
we'd
love
to
discuss
more
an
issue
698
about
core
layouts
and
which
correlates
we
should
potentially
include
in
court.
Also.
A
B
B
But
our
focus
for
one
point
for
point:
O
are
the
things
that
are
that
that
we
just
talked
about
1.3
point
0,
for
example,
transliteration
was
not
on
our
overall
schedule;
it
wasn't
on
her
focus,
but
it
was
done
and
it
was
completed,
and
so
it
was
moved
into
core
four
for
that
release.
So
you
have
other
ideas.
We
won't
stop
you
from
implementing
any
of
them
and
if
they,
if
they
get
done
in,
if
they're
complete,
then
they'll
be
moved
into
this
next.
That.
B
Okay,
Prince
every
Thursday,
that's
today.
Of
course,
we
get
together
and
we
hammer
out
back
job
stuff,
I
swear
to
god.
Jeff
I'm
I
will
transfer
like
the
rush,
I'll
transfer
the
dress
repository
today.
That
would
be
my
absolute
for
certain
task.
Good
I,
complete
during
sprint
time,
but
we
hang
out
in
pounds
back
drop
in
IRC
on
freenode.
B
We've
also
really
been
using
git
er,
quite
a
bit
frequently,
which,
if
you
visit,
get
er
IM
/
backdrop,
then
you
can
join
in
the
backdrop
issue
get
er
channel
and
we've
been
conversing
there
as
well.
But
the
primary
place
of
all
communication
is
the
backdrop
issue
queue
on
github,
github.com,
/
backdrop,
/
backdrop
dash
issues
and
that's
where
all
of
our
communication
happens.
Our
primary
communication
happens
in
record
of
what
it
is
that
we're
actually
working
on.
So,
if
you're
interested
in
working
today,
we
hope
to
see
you
there.
C
A
Can
we
just
thank
Jim
for
a
minute
because
I
have
to
say,
like
that?
I
am
so
impressed
by
all
of
the
things
that
backdrop
has
been
tweeting
and
we've
been
getting
a
ton
of
activity
like
people
are
favoriting
and
responding
and
I
think
it's
exactly.
What
we
wanted
is
to
kind
of
make
a
little
more
noise
and
how
people
not
forget.
We
existed
and
he's
been
doing
such
a
great
job
with
the
right
talent
and
the
right.
The
right
reactions
from
everyone.
So
thank
you,
Jim
for
being
awesome
on
Twitter
and
everywhere
else.
A
B
Also,
of
course,
brings
up
a
point
that
you
can
follow
backdrop
on
Twitter.
We
are
twitter
com,
/
backdrop
CMS
in
our
facebook,
very
similar
facebook.com,
slash
backdrop
CMS
and
we're
posting
things
really
regularly
there
now,
primarily
with
Jim's
help,
so
we
want
to
give
you
a
finger
on
the
pulse
backdrop.
Those
are
two
great
resources
to
do
so.
B
Let's
see,
we
also
have
an
ical
feed
of
upcoming,
a
backdrop,
events
and
meetings.
It
looks
like
we've
got
two
of
them:
the
ical
feed
for
backdrop,
meetings
such
as
this
one,
as
well
as
the
design
meeting
that
happens
every
other
week.
The
link
for
that
you
can
get
from
the
agenda
which
is
attached
to
these
video
recordings.
It's
else
go
on
back
to
see
my
starred
/
contribute
or
national
resources
all
right.
B
Well,
that's
even
better,
so
you
can
find
a
list
of
all
upcoming
vectra
meetings
and
events
that
are
backdrop
friendly
or
we'll
head
back
to
our
presentations
at
them.
A
couple
of
those
that
are
coming
up.
St.
camp
is
februari
25th
through
27th,
and
there
will
be
a
full
day.
Backdrop
training
workshop
there,
Jen
and
I
will
both
be
down
there
in
San
Diego's
doing
some
Drupal
trainer
tactical
training
backdrop
training
if
you're
interested
in
learning
about
backdrop,
it's
great
opportunities.
B
Drupalcamp
Utah
is
march
forth
through
fifth
they've
been
looking
for
backdrop
presenters,
but
they
haven't
actually
found
one.
Yet
so
grinch
isn't
talking
about
backdrop
in
any
capacity
whatsoever,
you
can
be
brand
new
to
it.
You
can
have
just
installed
it
once
or
twice
and
use
have
some
thoughts
about
it.
They
would
love
to
have
some
information
about
backdrop
at
their
camp.
B
B
B
And
then
civic
on
for
civ
ecrm
is
coming
up
in
May
or
June
I.
Guess
they
don't
have
the
exact
dates
yet
in
Denver
and
we
hope
to
be
there
as
well,
because
of
our
recent
work
to
integrate
backdrop
CMS
with
Sylvie
CRM,
we're
hoping
that
we
can
attend
that
conference
and
let
people
know
about
some
alternatives.
They
have.
They
have
an
existing
civvy
installation,
a
couple
with
Drupal
7
that
we
have
some
options
for
them
moving
forward
with
their
websites.
B
C
B
Wait
but
now
you
can
find
it
on
amazon
if
usage
for
backdrop
CMS
the
first-ever
backdrops
in
this
book,
it's
a
little,
it's
pretty
short.
It's
actually
I
think
it's
only
like
a
hundred
some
pages
or
less
89
pages.
So
it's
a
pretty
short
introduction,
just
basically
a
dipping,
your
toe
in
the
water
introduction
to
backup
CMS
but
Todd
tomlinson
is
also
working.
E
A
E
A
No,
in
general,
what
happens
is
before
we
do
any
work
on
the
back
roads,
CMS
to
org
website
I'll
commit
everything.
That's
in
the
live,
I
can
fake
directory
and
then
pull
it
down
or
tell
whoever's
working
on
it
to
full
so
that
they
get
the
latest
set
of
configurations
in
the
live
directory,
and
then
they
should
run
the
importer
script
which
that
way
or
if
they,
if
I
fresh
database
copy.
A
That
would
also
work
to
you,
can
just
manually
copy
the
files
over
so
that
they're
in
the
dev
directory
and
then,
when
they're
done,
they'll
submit
a
poor
quest
that
contains
all
of
the
configuration
changes
that
they
made
in
the
development
directory
and
then,
when
I,
pull
to
the
production
site
will
run
the
update
script
on
production.
That
will
then
copy
those
files
from
the
development
directory
to
the
production
directory
and
run
any
updates
that
are
necessary
for
those
as
well.
B
Yeah
and
that
way
you
get
all
of
your
oddities
and
all
of
the
resolving
conflicts
and
anything
like
that
all
happens
on
your
local.
So
before
you
start
committing
any
changes
into
configuration,
the
first
thing
you
should
do
is
go
to
my
own
learning
that
production
production
changes
are
committed
in
in
version
control.
Before
you
start
trying
to
get
those
before
you
before
you
commit
any
configuration
changes
from
your
local
yeah.
D
That's
that's
really
important
and
one
of
the
things
that
I've
found
is
that
it
really
gets
messed
up.
When
you
have
some
changes
on
your
dad's
and
some
changes
on
live
you
push
because
right
now
we
have
no
way
to
individually,
like
mark
without
copying
the
files
that
you
can't
do
on
campeon
stuff
like
that,
but
I
mean
there's
no
way
to
individual
the
that's.
Why
or
not
apply
the
configuration
changes.
So
then
it
requires
some
very
complicated.
D
A
D
A
A
B
D
D
A
Could
get
some
we
could
get
some
old
from
the
folks
at
Pantheon
too,
if
we
were
like
look,
this
is
the
problem
with
the
current
setup.
We've
used
it
for
a
year
like
we
know
now
that
this
is
going
to
continue
to
be
a
problem.
Let's
get
a
tool
we
can
probably
especially
for
a
willing
to
work
something
into
trash
like
add
rush,
sinker,
Josh,
unsink
or
whatever
it
is
we
come
up
with.
There
might
be
some
way
that
we
can
get
get
a
tool.
Won't.
A
A
D
E
B
Hampel
right
now
is
so
odd
how
they
may
require
that
you're
an
installation,
a
backdrop
be
in
the
roots
or
installation
of
Drupal
be
in
the
route
and
its
really
kind
of
obnoxious,
because
there's
a
lot
of
other
stuff,
you
frequently
want
to
put
in
your
site,
that's
affiliated
with
it
that
shouldn't
be
in
the
web
roots.
You
know
like
configuration
files.
Well,
that's.
D
A
little
bit
less
important
now
that
we
have
the
core
directory,
because
now
we
do
have
like
all
the
other
directories,
other
than
core
or
sort
of
site-specific
already
so
adding
like
I,
add
a
patches
directory
in
there
and
add
a
config
staging
directory
and
it
sort
of
goes
along
since
everything
other
than
coors.
Just
you
know,
sites
accessible,
so
it's
a
bit
better.
Now.
B
Yeah,
okay!
Well,
let's
call
it
a
call.
Thank
you,
everybody
for
joining,
think
you're
ready
for
watching
and
we
will
meet
up
again
next
week
next
week
will
be
both
the
design
meeting
earlier
in
the
day
now
earlier,
and
then
this
regular
weekly
developer
call
as
always.
So
thanks
everybody
for
joining
and
we'll
see
you
next
week.
Oh
and
in
our
see
you.