►
Description
Check-in on development + infrastructure tasks for Backdrop CMS.
Today’s agenda: http://bit.ly/1NeNZiq
A
Alright,
we
are
on
air,
happy
Thursday,
December,
17th,
everybody,
we're
gonna,
do
a
quick
meeting,
maybe
not
so
quick,
a
matter
of
CMS
development
tests,
moment
and
infrastructure,
we'll
start
with
general
announcements.
As
usual.
We
have
dragon
t-shirts
and
hoodies
available
on
our
website.
If
you
go
to
backdrop,
CMS
org
slash
contribute,
you
can
make
a
donation
of
twenty-five
dollars
to
get
an
adorable
t-shirt.
A
Nate
is
sporting
one
right
now,
which
is
nice
white,
ish,
very
comfortable,
soft
fabric,
adorable
dragon
on
it,
and
if
you're
already
backed
up
CMS
developer
and
our
contributor-
and
you
want
one-
you
have
already
earned
it.
So
you
can
send
an
email
info
backdrop
CMS
or
with
your
address
and
preferred
size
and
will
sell
out.
If
you
want
a
hoodie,
you
can
make
a
donation
for
fifty
dollars
and
we
can
mail
one
anywhere
in
the
United
States.
If
you
live
outside
the
United
States,
you
want
a
hoodie.
A
We
can
negotiate
on
additional
costs,
will
look
it
up
and
see
how
much
it
costs
and
we
get
someone
up
to
you
for
a
reasonable
surcharge.
Just
that
we're
not
hurting
ourselves
in
the
process,
but
yeah
they're
available
we're
going
to
be
bringing
them
with
us
to
camps
and
conferences
and
meetups
and
whatever
around
the
country
or
world
or
wherever
it
is
that
we
are.
A
A
We
have,
since
the
last
meeting
reached
out
to
the
people
at
phpstorm
and
gotten
new,
updated
licenses
for
all
of
our
contributors,
and
they
have
a
new
fancy,
sophisticated
way
of
dealing
with
license
keys
where
last
year
we
kind
of
gave
everybody
the
same
license
key
and
that
license
key
was
good
for
a
certain
number
of
uses.
This
year
everybody
has
their
own
license
key
and
we
have
them
available
for
backdrop
kinship
developers.
So
that
means,
if
you
are
a
member
of
the
backdrop,
dash
contribute
on
github,
send
an
email
to
info
a
backdrop.
A
Cms
org
and
we
will
distribute,
said,
license
key
and
we've
got
a
bunch
for
this
coming
year
and
I
think
they're
all
good
for
a
year
from
there
start
date
now,
which
is
also
a
little
fancier
where
it
is
a
couple
months
ago
or
like
will
give
you
one,
but
only
works
for
a
little
while
this
is
actually
legitimately
going
to
be
good
for
you
for
a
year.
So
definitely,
if
you're
interesting,
that,
let
us
know
if
you
are
a
bat-trap
contributor,
but
you
are
not
yet
a
member
of
the
kinship
group.
A
We
can
also
help
get
you
in
there,
so
shoot
us
an
email
or
tweet
or
use
the
contact
form
on
website.
Whatever
we
can
hook,
you
up
alright
big,
exciting
news.
This
Tuesday
Nate
and
I
did
a
sprint
with
Tim
otten
from
the
civvy
CRM
team,
and
we
spent
an
entire
day
trying
to
see
if
we
could
get
civvy
to
work
with
back
job
and
by
the
end
of
the
day
we
actually
had
civvy,
mostly
working
with
backdrop,
so
took
one
day
to
do
a
port
of
the
drupal
module
that
was
in
there.
A
Nate
did
some
work
on
some
of
the
integration
with
Sevilla
CRM
in
civvy,
serum
core
I
did
a
bunch
of
work
on
the
drupal
module
and
we
got
by
the
end
of
day.
You
could
actually
see,
in
your
backdrop,
website
you're
savvy
serum
data,
which
I
thought
was
fantastic,
there's,
obviously
a
bunch
more
work
to
do
to
get
it
to
be
to
the
point
where
it's
comparable
with
what
it
does
on
Drupal,
there's
a
bunch
of
supporting
modules
that
haven't
been
ported
yet,
but
I
think
that
it's
looking
really
good.
A
The
fact
that
we
could
get
up
and
running
within
one
day
with
a
little
help
from
the
core
team
linked
in
our
agenda.
We
can
post
these
in
the
meeting
to
is
right.
Now
we
have
nightly
dove
builds
that
are
including
the
backdrop
integration.
So,
if
you
want
to
help
us
work
on
it,
you
can
grab
one
of
those
and
it
pulls
from
all
of
the
Associated
repositories
where
we're
committing
the
backdrop
work
in
bundles
them
together.
A
It's
currently
labeled
unstable
because
is
not
ready
for
production
use
yet,
but
it
is
great
if
you
want
to
just
give
it
a
test
and
see
how
it
was
going.
It's
a
great
place
to
do
that.
We
now
have
a
civvie
cerium
dash
backdrop,
a
repository
which
includes
all
of
the
modules
for
backdrop
that
provide
the
civvy
crm
integration.
A
So
the
way
that
it
works,
the
civvy
serum,
is
that
you
drop
the
entire
city
CRM
project
into
your
modules
directory,
but
then,
within
that
huge
project,
there's
a
subset
of
directories
that
contain
the
modules
that
actually
handle
the
integration.
So
if
you're
wanting
to
put
this
together
yourself,
you
got
CB
CRM,
you've
got
the
backdrop.
Integration
means,
though,
the
whole
thing
into
your
modules
directory
and
you
get
everything
you
need.
A
So
it's
a
separate
project
so
that
you
can
either
drop
in
the
Drupal
configuration
of
the
back
job
are
the
WordPress,
the
Joomla
or
whatever,
and
we've
got
one
of
those
up
and
running
right
now.
So
that's
very
exciting.
Nate
also
posted
a
link
to
the
civvy
serum
JIRA
issue,
which
is
where
we're
documenting
all
the
progress
we're
making
on
getting
to
be
working
with
vector.
So
this
is
super
exciting
because
we
recently
went
to
a
bunch
of
of
us
that
were
not
gerbil
events.
A
They
were
just
tech,
people,
nonprofit
events,
and
we
found
that
there
was
this
huge
demand
for
backdrop,
but
also
backdrop
with
City,
and
so
we
decided
that
we
should
make
it
a
priority
to
get
backdrop
working
with
sippy,
because
that
right
there
is
our
market
and
if
we
can
meet
their
needs,
then
that's
great
going
forward.
Yes,
backdrop
is
going
to
be
easiest
to
use,
for
people
have
already
using
triple,
but
going
forward.
A
Dribble
events
are
going
to
be
more
and
more
for
people
who
are
interested
in
triple
eight,
and
we
need
to
kind
of
focus
on
our
market
which
are
going
to
be
people
who
maybe
won't
be
a
triple
events,
because
they
have
other
things
going
on
that
are
more
relevant,
they'll,
be
at
tech,
conferences
or
there'll,
be
a
non-profit,
focused
events,
and
if
we
can
make
sure
that
we
meet
their
needs
to
I,
think
that's
going
to
be
overwhelming,
more
and
more
important.
A
So
great
progress
on
that
front
and
super
excited
that
we
were
able
to
make
as
much
progress
as
we
were
in
the
first
day
later
today,
we
have
another
meeting
with
the
folks
at
sbisa
route
to
figure
out
how
we're
going
to
handle
ongoing
updates
responsibilities,
issue
queue,
management,
poor
request
processes,
all
of
that
stuff,
just
to
make
sure
that
we
can
figure
out
how
to
get
everything
we
need
done
and
in
an
orderly
fashion,
with
collaboration
so
very,
very
excited
that
these
open
source
projects
are
are
going
to
be
working
together
in
future.
A
Okay,
that's
the
most
exciting
announcement.
We
don't
have
anything
new
from
the
BFC,
but
I
do
want
to
turn
it
over
to
meet
or
update.
B
Hey
sorry,
I
thought
I
was
me
too.
I
cuffed,
but
it's
not
okay,
so
community
growth.
So
we
like
to
take
a
little
bit
of
time
to
talk
about
all
the
projects
that
we
have
ported
or
created
for
backup
CMS.
We
currently
a
179
total
projects
for
backdrop.
Cms
in
the
github
contribute
that's
github.com
/
backdrop
dash
can't
rip.
One
new
project
has
been
created
since
last
week.
It's
exciting
to
see.
B
We
currently
have
42
total
members
of
the
backdrop
contribute
like
jazz
mentioned
earlier.
If
you
join
the
group,
you
can
also
get
a
phpstorm
license
for
your
backdrop,
development,
but
you
have
to
join
the
group
door
to
do
that
and
if
you
would
like
to
apply
to
be
a
part
of
the
group,
you
can
visit
github
com
/
backdrop
dash
ops,
/,
contribute
a
where
we
process
anybody
who's
interested
in
enjoying
the
group
and
porting
modules
over
to
fax
drop.
B
One
issue
is
we're
currently
working
on
making
it
so
that
data
that
is
sent
to
our
servers
back
to
ms
org
from
individual
back
job
sites
starts.
Recording
the
projects
of
those
modules
have
our
that
those
those
sites
have
installed.
We've
been
collecting
that
data,
but
we
haven't
been
able
to
process
it
correctly.
B
Last
week
we
had
some
progress
there
that
we
think
that
we
have
the
number-crunching
script
finally
fixed,
so
that
we
can
take
all
this
data
we've
been
accruing
over
the
past
several
months
and
crunch
it
into
historical
usage
data.
Sorry
I've
got
cat
problems,
let's
see
after
we
get
that
put
together.
We
want
to
add
in
some
additional
powers
to
that
update,
checking
like
recording,
which
features
are
enabled
within
individual
sites
like
one
that
you
have
clean,
urls
turned
on
or
off
or
all
kinds
of
other
things.
B
B
Once
we
actually
have
this
thing
working
yeah
Jen,
just
added
like
do.
We
have
a
meta
issue
to
add
more
drush
commands
I
think
what
we
probably
could
do
for
the
time
being
is
just
use
that
sandbox
and
add
individual
issues
like
saying
you
know:
port
this
command
and
port
that
command,
rather
than
filling
up
the
cork.
You
with
you,
know,
meta
and
sub
subsequent
commands,
maybe
just
start
populating
issues
in
that
individual
repository.
B
Cool,
let's
see.
The
next
item
we
have
here
is
github
automation.
We
have
a
long-standing
issue
over
in
backdrop:
CMS
orgs
issue
queue,
issue,
number
72
kind
of
synchronize
the
tags
between
issues,
because
all
of
our
our
members
of
the
backdrop
issues
group
can
label
and
tag
individual
issues,
but
they
can't
actually
label
and
tag
pull
requests,
and
so
we
want
to
make
it
so
that
pull
requests
are
synchronized.
B
The
tags
have
their
tech
synchronized
with
issues,
because
right
now
it
does
have
a
big
list
of
pull
requests
and
none
of
them
have
any
tags
or
any
labels
or
anything
to
separate
them,
because
only
the
people
that
can
commit
to
the
core
depository
can
add
those
labels
and
that's
not
where
all
of
our
work
is
happening.
All
over
work
is
happening
over
issues
queue
and
the
issues
kids,
where
other
labels
come
from,
so
we'd
like
to
make
it
synchronized
speech
between
those
two
repositories.
B
Here's
the
big
issue
for
infrastructure
is
that,
as
of
yesterday,
we
haven't
fixed
this
yet,
but,
as
of
yesterday,
Travis
CI
basically
is
totally
broken.
What
happened
is
this
current?
They
switched
their
entire
infrastructure
from
using
their
previous
hosting
provider,
which
is
bucks
over
to
Google
compute
engine
and
basically
Google
compute
engine
is
like
way
way
slower
like
on
the
order
of
like
six
times
slower,
and
so
what
is
happening
right
now
is
that
all
of
our
pull
requests
are
failing
tests
because
they're
all
maxing
out
the
time.
B
B
So
I'm
hoping
what
we'll
do
is
well
we'll
switch
back
to
the
old
servers
until
things
kind
of
settled
down,
because
even
lots
of
other
people
are
having
issues
on
the
new
service
as
well,
and
I
think,
for
the
time
being,
we
can
just
kind
of
hop
back
over
to
the
old
servers.
Let
them
work
out
their
issues
and
then
we
can
switch
over
to
the
new
servers,
hopefully,
which
will
have
increased
performance
by
the
time
that
we
go
back
over
there.
B
A
So
I
think
maybe,
since
our
last
meeting
went
ahead
and
implemented
most
of
Darius's
design
for
the
new
user
profile,
page
and
I
filled
out
my
profile
and
I
felt
their
half
of
Nate's
profile
and
I.
Think
West
filled
out
his
profile.
So
there's
three
pages
you
can
actually
see
it
on,
but
if
anybody
else
wants
to
help
us
test
this
thing
send
me
an
email
or
tweet
or
let
us
know
and
chat
or
whatever,
and
we
can
create
accounts
for
all
of
you.
A
You
can
go,
fill
your
profile
page
and
take
a
look
at
what
it
looks
like
the
blocker
on
releasing
that
to
the
general
public
is
that
the
edit
form
for
your
profile
is
kind
of
a
mess
so
well
yeah.
Maybe
we
should
we
should
check
the
permissions
and
make
sure
users
can
view
other
users
profile
pages
to
that
might
not
be
set
up
yet
so,
what's
an
access
to
nine
messages
being
delivered
on
this
page
I,
don't
know
why
mine
would
work
in
years
1.
A
Then
we
can
figure
that
out
something
we
are
going
there
anyway.
We
have
him
wooded
areas.
His
designs,
my
favorite
part,
is
the
big
fancy
banner
image
that
was
not
in
any
of
our
minds
when
we
asked
him
to
do
it.
He's
like
you
know,
it
look
good,
any
posted
that
what
we're
gonna,
try
and
do
is
get
some
branding
assets
for
backdrop
that
we
can
use
consistently
across
all
platforms
for,
like
a
banner
image
on
our
Twitter
account.
A
A
We
want
to
be
able
to
let
people
do
single
sign-on
with
github,
so
that
if
you
have
a
github
account,
you
don't
need
to
create
a
new
account
for
backdrop.
You
can
just
click,
link,
sign
and
get
heaven
all
your
github
info
be
pulled
over
and
we
want
to
do
a
little
bit
more
work
on
the
modulus
themes
and
layouts
pages
as
well.
A
I
just
noticed
yesterday
that
we
have
a
lot
of
modules
on
website
and
the
original
designs,
where
the
modules
page
had
filters
that
you
could
find
exactly
what
you
were
looking
for
in
that
modules
list,
and
we
just
didn't
have
any
of
that
built
out
yet
we're
like.
We
only
have
20
modules,
it's
not
important.
Well
now
we
have
hundreds
of
modules
or
more
than
a
hundred
module,
so
I
think
it's
getting
more
and
more
important
for
people
to
actually
be
able
to
use
those
filters.
A
So
I
think
my
next
focus
is
going
to
be
in
getting
those
filters
done
west's
volunteered
to
work
on
the
edit
form,
I
think
we're
totally
and
in
good
shape
in
terms
of
our
allowing
users
to
join
our
community
by
January,
first,
so
very
exciting.
A
Other
things
we
want
to
do
on
our
primary
website
include
a
service
provider
or
contractor
listing
an
event
calendar
a
job
board
and
a
blog.
What
yeah
blog?
Really
we
have
this
new
section
and
our
meeting
here
for
marketing
tasks
that
we
need
to
start
thinking
about
for
backdrop
as
developers,
Nate
and
I
are
not
super
great
at
marketing.
So
last
week
we
put
out
a
call
for
anyone,
and
this
continues
this
week.
A
If
you
are
interested
in
helping
us
with
marketing-
and
we
create
a
bunch
of
issues
in
the
backdrop
CMS
network
q4
things
that
we
need
to
do
related
to
marketing.
We've
gotten
a
bunch
of
progress
already
since
last
week,
yesterday
or
the
day
before
we
went
and
set
up
our
google
in
it
analytics
account,
which
apparently,
we
had
set
up
a
year
ago,
but
never
actually
properly
implemented.
So
now
we
have
google
analytics
both
on
backdrop,
CMS
org
and
API
that
backdrop
CMS
to
org.
A
So
we
can
see
what
people
are
doing
on
our
website,
which
is
useful
to
help
us
try
and
figure
out
what
we
want
them
to
do
on
our
website
and
then
try
and
get
them
to
the
places
we
want
them
to
be
more
easily.
So
that'll
be
really
great
in
order
to
draw
traffic
to
our
website,
we
also
have
plants
to
do
things
like
write
blog
posts
now,
building
a
blog
is
something
I'm
very
good
at,
but
writing
words
that
go
into
a
blog,
not
very
motivated
to
do
so.
A
We
definitely
need
somebody
who's.
A
good
word
sniff
to
help
us
write
some
of
this
content.
We
have
a
bunch
of
good
ideas
about
things
that
maybe
should
end
up
on
the
blog,
but
just
aren't
actually
doing
it.
We
actually
already
have
a
content
type
that
we
use
for.
One
blog
post
will
go
right
to
the
homepage
like
the
most
recent
one,
but
we
don't
have
a
blog
page.
We
don't
have
an
RSS
feed.
I
was
looking
at
some
of
the
page,
not
found
airs
on
our
website.
A
People
are
currently
trying
to
find
the
RSS
feed
of
our
website
or
robots.
Are
it
does
exist,
so
we
should
make
one
so
people
can
use
it,
which
would
be
great
this
should
we
should
tell
people
what
we're
doing
that'll
be
good
too,
and
just
having
a
little
more
activity
there.
To
show
that
you
know
we
are
a
community,
we
are
doing
things.
Progress
is
happening.
Talking
about
these
meetings
would
be
good.
Talking
about.
A
Other
big
news
would
be
good,
PHP
sevens
for
a
civvie
crm
integration,
there's
a
bunch
of
good
stuff
going
on
that.
We
need
to
do
a
better
job
of
telling
people
about
so
I.
Just
think,
like
you
know,
I
once
a
week
little.
This
is
what's
going
on
in
backdrop.
Maybe
once
every
two
weeks
would
be
great,
we
could
get
somebody
to
write
those
for
us.
That
would
be
even
better.
A
Oh
definitely,
if
your
inner
snubbing
us
marketing,
webster
backdrop
CMS
itself
the
product
and
has
a
bunch
of
stuff
up
coming
soon,
we
are
going
to
issue
a
one
point,
two
point:
three
release
fairly
soon
that
will
contain
and
back
boards
from
Drupal
7.40
whenever
we
get
around
to
the
source,
nothing
super
urgent
in
there
that
is
demanding
that
we
do
it
right
away,
but
I
think
that
once
we
get
this,
and
that
would
be
a
good
kind
of
milestone
for
getting
that
next
release
out
and
not
release.
I
think
correct
me.
A
If
I'm
wrong,
mate
will
also
contain
the
PHP
seven
support,
so
that
would
also
merit
a
newsletter
going
out
to
people
saying
they
can
use
backup
on
Fifi
seven,
which
will
make
it
fast
faster
sweep
your
sevens
really
fast.
Let's
joining
one
point
three
point:
o
is
the
next
minor
release,
it's
scheduled
for
january
fifteenth,
and
it's
supposed
to
be
a
user
experience
release
where
we're
taking
some
time
to
go
back
to
the
stuff
that
we've
put
in
earlier
and
kind
of
put
some
polish
on
it.
A
A
If
we
only
have
10
15
minutes-
and
you
want
to
make
some
significant
difference
in
the
improvement
of
backdrop,
there's
a
bunch
of
low-hanging
fruit
there,
which
could
be
really
great,
there's,
also
a
lot
of
issues
there
with
pull
requests,
and
we
could
definitely
use
help
reviewing
for
requests.
A
So
if
you
want
to
spend
15
minutes
helping
backdrop,
but
don't
want
to
write
any
code,
you
could
grab
a
patch
apply
it
and
give
it
a
test
and
see
if
the
thing
that
we
were
complaining
about
in
the
issue
has
been
resolved
satisfactorily
or
not,
we
can
have
someone
else
review
code.
You
can
review
the
change
that
was
made.
That
would
be
really
beneficial
for
us
as
well.
A
Some
of
these
things
that
we're
trying
to
work
on
are
improving
the
layout
module
you
I,
the
way
you
drag
and
drop
blocks
into
places
has
some
some
issues
that
need
to
be
resolved
and
adding
new
things.
You
can
add
to
your
layouts,
like
the
one
field
for
one
block
per
field
issue:
adding
contexts,
there's
a
bunch
of
kind
of
heavier
more
complicated,
follow
up
issues
that
aren't
necessarily
user
interface
related,
but
our
user
experience
related
I
would
like
to
get
done
for
that
and
all
of
those
layouts
follow.
A
Ups
are
in
issue
3
45
on
github.
We
also
have
a
handful
of
rich
text.
Editor
follow
ups,
which
is
at
issue
1087
same
general
story
with
rich
text
editor.
We
put
it
in
at
a
minimum,
viable
product.
We
know
it's
a
little
clunky
and
there's
a
couple
of
tiny
things
we
could
fix.
It
would
make
a
big
improvement
and
they
are
noted
in
that
issue,
and
there
is
one
remaining
administration
view
that
we
didn't
get
into
core
initially
and
that's
the
comments
listing.
A
If
we
could
get
that
converted
into
of
you,
then
we
could
put
a
little
check
mark
on
that.
All
administration
pages
are
now
views
which
is
uninjured
late.
Has
we
haven't
gotten
it
done?
Because
there
is
a
few
spoke
operation
for
managing
comments
that
has
not
had
been
created.
So
the
view
is
pretty
easy
to
build.
The
bulk
operation
is
slightly
less
so
we
could
definitely
use
that
area.
A
We
want
to
change
at
some
terminology
and
our
menu
systems
that
we
say
edit
when
you're
editing,
content
and
configure
when
you're
going
to
be
saving
the
results
of
that
form
into
a
configuration
files
post
database,
and
we
think
if
we
can
use
those
words
consistently
it'll
start
to
make
more
sense
to
people
which
things
are
which
right
now,
it's
all
kind
of
a
big
hodgepodge.
Alors.
The
place
so
getting
those
cleaned
up,
I
think
will
help
people
a
lot.
A
We
want
to
add
a
notification
icon
decor,
so
this
is
0,
for
example
your
websites
out
of
date.
If
you
visit
an
administration
page,
you
get
a
big
ugly,
red
air
and
every
single
page,
and
if
you
visit
the
front
end
of
the
site,
you'll
never
know,
there's
nothing
wrong.
Well,
we
were
thinking
about.
Doing
is
just
putting
a
little
icon
in
the
admin
bar
that
would
say
hip.
A
We
have
the
project
browser.
This
is
issue
1399,
I'm
set,
so
that
the
goal
is
so
that
you
can
go
to
your
modules
page
and
you
can
browse
available
modules
for
backdrop
from
the
modules
page
or
breast
themes
in
the
future.
For
us
lay
out
some
layouts
page
browse
things
that
are
not
already
on
your
website,
and
so
we
have
this
browser.
We
have
a
server
setup,
we're
trying
to
get
it
integrated
I'll
be
fantastic.
If
we
could
get
that
in
by
1.3,
that
would
make
a
huge
difference.
A
User
experience
I'm
not
sure
it's
close
enough
to
do
that,
but
I
think
that
we
could
try.
It
would
be
fantastic
if
we
got
that
and
that's
definitely
something
that
would
make
a
really
big
difference
to
new
users
of
backdrop
not
needing
to
go
to
our
website
to
find
what
they
want.
A
A
One
I
don't
think
it's
looking
very
likely
for
backdrop
1.3,
but
I
would
like
to
keep
it
on
everybody's
minds
because
getting
an
easier
way
to
build
content
types
and
is
something
it's
definitely
going
to
be
important
for
the
success
of
backdrop,
I
mean
what
makes
us
different
from
something
like
WordPress,
where
most
pages
are
just
a
title,
embodies
the
ability
to
add
fields,
and
if
we
can
make
it
easier
for
people
to
add
fields,
then
that
feature
would
become
more
powerful,
more
people
who
use
it.
A
We
will
complain
less,
we
like
complaining,
but
we
should
complaint
lists.
A
So
if
you
want
to
take
a
look
at
all
the
issues
we
have
marked
for
1.3,
you
can
check
in
searching
the
issue
queue
to
check
on
milestone.
One
point
three
point:
oh
so
a
lot
of
little
ones
in
there.
The
big
ones
are
ones
that
I
just
mentioned,
but
since
1.3
is
not
a
release
for
we're,
focusing
on
new
features,
we're
also
starting
to
think
about
the
kinds
of
things
that
we
want
in
1.4
and
so
far.
Oh
sorry
field,
you
I
issue,
number
Luke
is
number
seven
seventy-nine.
A
But
for
backdrop,
1.4
we're
starting
to
think
that
we
will
rewrite
and
include
some
version
of
references
module.
We
also
are
thinking
that
we
might
need
some
version
of
redirect
module
and
perhaps
also
new
front
end
theme,
which
I
think
might
be
becoming
our
most
pressing
issue
in
order
to
get
people
who
are
interested
in
using
backdrop
actually
using
backdrop
giving
them
a
usable
front.
A
End
theme
out
of
the
box
what
is
going
to
be
more
and
more
important,
so
that
issue
is
1361
and
if
you
want
to
take
a
look
at
our
official
roadmap,
it's
a
backdrop
CMS
to
org
slash
road
map.
A
Again,
we've
only
added
stuff
there
that
we
have
definitely
decided
we
are
doing
for
certain
release,
so
we
don't
have
anything
listed
yet
for
1.4,
but
I
think
we're
kind
of
zoning
in
on
references
redirect,
but
well,
we'll
post
that
once
we
get
closer
1.3
things
we're
always
working
on
backup
core
is
improving
user
experience,
though
we
do
have
a
special
release
scheduled
in
January
for
that,
if
you
find
anything,
related
user
experience
tagged
with
that
release
or
not,
and
you
can
get
it
fixed
now,
it'll
go
in
next
release,
so
the
better
we
can
make
the
user
experience
the
better
the
whole
product,
and
also
things
that
are
of
particular
to
us,
is
developer.
A
Experience.
Drupal
gets
a
bad
rap
for
being
hard
to
learn
hard
to
use
hard
to
code
for
we
started
with
Drupal.
We've
got
all
the
same
problems,
Drupal
has,
and
so
as
you're
working
with
software
coding,
either
front
end
or
back
end,
and
you
find
something.
That's
really
weird
write
it
down
in
the
issue
queue.
Let
us
know
it's
really
weird
and
put
a
tag,
the
beginning
of
the
issue,
title
DX
and
square
brackets,
and
that's
something
that
we've
got
to
improve
to
make
people
like
working
with
vector,
there's.
A
Definitely
a
ton
of
stuff
we've
already
improved,
but
there's
a
whole
lot
more.
We
can
make
it
a
lot
better
and
I
think
we
just
need
to
kind
of
keep
a
holistic
view
of
what
is
it
that's
going
to
make
working
with
this
offer
more
enjoyable
for
12-person
future,
all
right,
every
Thursday.
After
this
meeting,
we
spend
some
time
together
in
IRC
on
get
er
in
the
github
issue
cute
when
we
try
and
work
through
some
of
these
issues.
Sometimes
what
we
worked
you
through
is
codes
and
that's
what
we
work
through
is
marketing.
A
Sometimes
what
we
work
through
is
design
whatever
it
is.
We
try
to
get
together
on
Thursdays.
If
you
don't
have
time
on
thursday
or
you
can't
get
time
off
work
during
the
work
week
or
anything
you
can
get
any
other
time
is
definitely
appreciated.
They're,
almost
always
people
in
IRC
and
in
the
issue
queue
in.
If
you
need
help
from
someone
you
know,
get
er
now
sends
emails
to
people,
so
there's
lots
of
ways
that
you
can
get
in
touch
with
the
community,
even
if
you
can't
be
available
on
thursday
afternoons.
A
This
afternoon's
are
a
good
time
because
there
are
a
lot
of
people
around.
If
I
want
to
get
involved,
then
we
also
have
a
reddit
I
should
have
mentioned
in
addition
to
an
IRC
channel,
which
is
found
backdrop,
a
github
issue
queue
and
get
er
IM,
which
I
think
is
a
backdrop
shoes
for
the
public
one
hour.
Reddit
is
I
reddit
accomplished.
A
Aren't
that
back
r,
/
extra
and
I,
don't
think
there's
that
many
people
in
it
already,
but
it's
the
only
forum
like
place
we
have
at
the
moment
we
are
evaluating
other
options,
we're
going
to
try
and
figure
out
what
we
can
do
with
a
forum
where
we
can
let
people
talk
to
each
other
in
with
it's
a
little
more
conducive
to
community
building,
but
that's
what
we
have
for
now.
A
Upcoming
events
meetings
like
this
one
happen
every
thursday
at
one
p.m.
pacific
time.
We
have
a
design
meeting
very
similar
to
this
one
that
happens
at
twelve
noon,
every
other
Thursday,
so
fortnightly.
There
was
one
today,
there'll
be
another
one
on
31st
and
we
have
a
bunch
of
upcoming
drupal
events
that
are
backed
up
friendly,
that
we
will
be
attending
so
far.
There
is
sand
camp
in
February,
drupalcamp
utah
in
march
in
chicago
at
the
end
of
march.
A
It
is
so
it
was
written
by
Todd,
Tomlinson
I.
Think
who
wrote
the
proud
little
development
book
is
about
as
well
as
a
bunch
of
other
books
on
a
press.
This
a
great
couple
sure
it
all
I'm
so
excited
to
see
this
book.
I
really
want.
I
want
to
buy
it
right
now,
but
wait
till
then
at
the
meeting
so
respect
off
book,
it's
written
by
somebody
who
knows
the
landscape
really
well.
He
was
an
issue.
You
asking
some
good
questions,
not
an
amazon
unit,
yeah,
okay!
Well,
Nate
will
tweet
about
it.
A
When
it
appears
on
amazon,
but
it
does
look
like
you
can
buy
it
directly
from
a
press
now,
if
you
want
and
eric
says
that
Todd
is
also
working
on
a
pure
backdrop
book
that
will
come
out
in
April,
that's
exciting,
so
yeah
I
can't
wait.
This
would
be
great
a
backdrop,
a
community.
Thank
you,
everybody
who
put
in
time
and
effort
in
that
I
know.
A
A
All
right:
well,
if
you
guys
don't
have
anything
to
add
I
guess
we
can
wrap
the
meeting
go
back
while.
A
C
That
can
be
used
on
more
than
one
layout,
so
I
mean
just
there's
like
three
different
ways
that
people
are
proposing
to
do.
Custom
blocks
and
it'd
be
good
to
talk
about
which
we
are
actually
want
to
pursue
and
what
people
are
thinking
for.
The
because
I
haven't
heard
much
I
can't
think
of
why
we
need
to
feel
blocks.
I.
A
Can
give
you
a
couple
good
use
cases
for
that,
but,
okay,
I,
just
back
up
a
step.
I
am
in
favor
of
all
of
these
methods.
Basically,
what
we're
talking
about
is
panels
which
I,
love
and
panels
has
this
concept
of
a
reusable
content,
pane
right,
which
it's
something
that
is
stored
in
configuration,
but
that
also
has
a
record
that
you
can.
It
is
an
entity
you
can
pull.
You
can
bet
as
many
times
as
you
want
whatever.
A
So,
yes,
I
think
we
should
have
a
piece
of
content
that
is
stored
in
the
database.
That
is
filled
the
bowl
as
a
block
type
I.
Don't
care
what
we
call
it,
we
want
to
change
its
name
to
be
content
block,
or
so
whatever
we
can
call
whatever.
But
the
use
case
for
that
is
that,
right
now
what
people
have
been
doing
in
Drupal
for
a
really
long
time
is
creating
nodes
that
don't
have
pages
things
for
like
a
home
page
slide
right.
A
If
you
have
a
slide
show,
and
you
need
to
have
a
view
of
eight
of
them
and
you
don't
ever
want
anyone
to
go
to
a
page
for
anyway.
These
things
we
want
them
to
rotate
and
they
have
a
title
and
they
have
an
image
and
they
have
a
link
and
some
of
those
links
are
off
site.
Maybe
some
of
them
are
on
site
whatever,
like
there's,
you
now
have
three
fields
you
need
on
this
thing.
That
is
a
field
of
all
thing,
but
it
doesn't
shouldn't
have
a
page.
A
So
it
doesn't,
it
shouldn't
have
meta
tags.
It
shouldn't
have
a
path.
It
shouldn't
have
any
of
this
stuff
that
is
associated
with
a
node.
Usually
so
there's
this
module
in
Drupal
it
I
use
all
the
time
called
rabbit
hole
that
lets
you
block
acts
us
to
the
pages
for
those
notes,
but
you
actually
wanted
was
a
field
of
a
block,
so
the
slideshow
is.
It
is
a
perfect
use
case
for
something
like
that,
but
there's
a
whole
bunch
of
other
things
too.
That
sometimes
come
up
like
maybe
file
entities
or
I.
A
Don't
know
you
might
have
a
listing
of
people
right
and
these
people
are
like
administrators,
and
so
you
have
a
content,
type
called
administrator,
but
nobody
ever
goes
to
an
individual
administrator
page.
You
only
ever
look
at
them
in
that
in
a
list
of
other
ones,
but
instead
of
having
like,
maybe
you
have
like
a
list
of
one
class
of
administrator
on
one
page
and
another
one
so
now
they're
like
categories
with
taxonomy,
you
can
have
like
very
complicated
use
case
for
things
that
need
to
be
organized
like
content,
but
don't
have
pages
like
notes.
A
So
that
is
the
use
case
for
a
feel
double
block.
So
that's
def.
C
A
Well,
the
checkbox
is
a
simple
solution
that
architectural,
a
building
that
thing
is
not
because
part
of
node
module
is
/
node
and
the
way
to
get
that
thing
is
like
/,
no
/
and
ID,
but
we
already
have
this
in
blocks.
All
we
need
to
do
is
say
block
is
an
object
that
extends
entity
and
it
you
know,
entities
are
already
page
lists
nodes,
so
both
solutions
are
valid
right.
The
question
is
like:
which
way?
Do
we
go
on
I?
A
Think
that
doing
a
filled,
the
bowl
block
is
what
seems
the
most
natural
I'm,
not
sure
that's
I,
don't
know
I,
think
anyone's
opinion
could
go
any
way
and
I'm
not
sure
that's
right
or
wrong
answer
yeah
and.
C
I
think
we're
facing
sort
of
an
over
complexity
of
just
how
Drupal
did
things
like
it's
sort
of
like
abstracted,
abstracted,
different
page
types
into
content
like
in
two
different
content
types
and
then
we're
having
entities,
and
it's
almost
like
a
double
abstraction
and
yeah.
It's
very
it's
very
we're
sort
of
stuck
with
a
lot
of
legacy
stuff.
It
almost
seems
like
I
wish.
Instead
of
doing
entity,
everything
became
a
note,
but
you
know
so
yeah
yep.
A
That's
definitely
one
one
way
of
doing
it,
but
that's
that's
we're
going
with
that.
Let's
talk
about
configuration
blocks
or
whatever
we're
going
to
call
these
other
things
too,
because
this
is
the
piece
that's
missing
right
now
from
back
job
is
and
there's
an
issue
to
build
them,
which
is
we
want
to
put
a
thing
in
a
panel
which
is
just
some
text
right.
It
can
have
HTML
in
it
or
not,
but
it's
just
text
doesn't
need
to
have
a
database
entry.
It's
not
going
to
be
published
or
unpublished.
A
It's
not
going
to
be
edited
by
editors
that
are
separate
from
those
who
are
managing
layouts.
It's
just
a
thing
you
want
in
your
sidebar
I.
Definitely
think
we
need
to
have
that.
That's
something
that
is
a
hard
to
do
right
now.
Without
that
feature,
you
have
to
kind
of
build
something
and
put
it
in
the
sidebar,
which
is
kind
of
frustrating
I.
Also
like
the
idea
of
those
things
being
reusable
right.
This
is
something
that
panels
came
up
with
is
an
afterthought
as
well
or
they
were
like.
A
You
don't
want
to
reuse
these
things,
let's
build
in
a
checkbox
and
store
it
in
a
way
that
we
can
access
them
later.
I
think
that
I
mean
I,
don't
know
maybe
I'm
technically.
How
does
how
to
solve
that
problem
like
we
might
have
to
have
a
separate
config
file
for
each?
A
What
are
we
fun,
config
block
or
whatever
it
is,
and
then
your
your
layout
configuration
have
to
reference
the
block
config
file
to
pull
in
the
content,
but
then
that
way
that
block
content
is
stored
as
config,
rather
than
a
record
in
your
database
right.
A
A
C
Means
something
they're
basically
asked
where
you
drop
into
the
things.
I
mean
it's.
You
know,
use
pain
instead,
but
thinks
I
think
there's
like
different
use
cases
between
the
custom
content
blocks
that
were
feel
beable
and
be
listed,
probably
in
the
content
area,
or
something
like
that
and
then
just
the
ones
that
are
placed
individually
in
the
in
the
in
the
like.
It
sounds
like
the
custom
custom
content
blocks
will
almost
probably
be
used
more
with
views
to
create
lists
of
them
or
something
yeah.
A
A
A
C
C
A
C
A
B
C
B
Know
yeah
it's
hard
to
say
it
does
seem
like
they're,
pretty
close,
like
I
know
that
one
that
I
mean
kind
of
related
layout
issue
that
one
field
for
one
block
per
field
issue
that
one's
ready
to
go
other
than
it
doesn't
have
any
tests.
B
A
B
C
B
No
we're
actually
expanding
the
way
blocks,
work
that
we're
completing
some
functionality
from
panels
that
that
we
didn't
get
in
the
initial
version
of
backdrop.
That
makes
it
so
that
a
single
block
can
have
like
have
children.
Basically,
so
there's
only
one
block
for
a
field
and
it
happens
to
provide
you
know
one
instance
of
itself
for
every
possible
field,
so
there's
actual
only
11
injury
of
bluk
info,
but
under
the
right
context
it
creates
a
bunch
of
sub
locks.
B
Yeah
they
said,
there's
a
bunch
of
things
and
I
like
your
idea,
Mike
on
phone,
basically
treating
all
blocks
as
though
they
could
be
read
them
all
config
blocks
as
if
they
called
la
music
on
the
future
yeah,
because
you're
right
that
it,
I
think
in
panels
it
like
once
you
make
the
decision
that
something
is
reusable
or
not.
Well,
you
can't
switch
it
later,
I,
don't
think
actually.
A
B
Thought
well,
if
it
did
change
it,
because
I'm
pretty
sure
it
does
save
it
directly
in
the
panel's
configuration.
And
then,
if
you
check
the
box,
then
it
it
makes
a
different
database
item
for
that
reusable
block.
But
it's
funny
because
I
don't
think
are
those
reusable
blocks
actually
exportable.
The
only
use,
uuid
yeah,
so
they're
kind
of
their
kind
of
not
really
explore
anything
in
so.
A
B
As
I
wonder
what
I
mean
we're
really
doing
people
some
new
opportunities
here,
I'm,
not
sure
people
would
start
just
creating
their
entire
site
out
of
config
blocks.
It
is
possible,
I,
suppose
I
know,
yeah
I
know
but
yeah.
Well,
why
not?
It
would
be.
You
know
if
you
end
up
with,
like
thousands
of
config
blocks,
you're
going
to
have
some
they're
going
to
be
repercussions
from
doing
that.
B
C
B
Well,
that's
what
I'm
worried
about
is
it
if
we
all
I
save
one
config
block,
you
know
make
it
a
separate
config
file,
regardless
of
whether
or
not
it's
quote
reusable
or
not.
You
still
could
end
up
with
some
issues
if
you
literally
had
thousands
of
them
that,
like
when
the
config
system
gets
the
directory
listing
of
all
of
the
config
files,
it's
going
to
loop
through,
you
know
an
extra
thousand
individual
config
blocks
to
get
to
you
know
something.
That's
completely
unrelated,
like
the
list
of
views
or
something
like
that.
B
B
B
B
But
if
you
create
a
new
view,
then
the
web
user
owns
those
files
and
I
thought
I
fixed
it
initially
by
making
our
user
so
on
backdrop,
seamless
downward
the
user
is
back
dropped
and
the
group
is
as
www
and
so
I
added
backdrop
to
the
WWE
group
so
that
all
the
files
it
made
would
be
owned
by
www.
That
was
like
okay,
that
looks
like
that's
all
good.
Now,
the
web
server
can
write
two
files
them
imaging
and
kick.
Unfortunately,
we
found
the
converse
was
not
true.
B
When
the
web
server
may
defile
the
backdrop
user
couldn't
write
to
them,
because
by
default
the
web
server
will
make
things
right
able
by
its
user,
but
not
writable
by
its
group
and
backdrop
whistle
named
group,
not
actually
the
owner.
So
we
fixed
that
on
our
own
server
using
a
I'm,
not
really
sure
this
is
a
great
fix,
but
we
change
the
there's
a
you
mask
option
that
PHP
runs
as
and
we
change
it
to
the
PHP
when
it
writes
files
will
make
them
group,
writable
and
owner
writable
and
that
solved
the
problem.
B
C
If
CM
I
didn't
necessarily
make
things
less
complicated
and
using
features,
it
just
created
different
problems
which
yeah
that's,
which
kind
of
emblems
of
all
the
initiatives
of
Drupal
8
seem
to
have
done.
That
yeah.
B
Unfortunately,
for
our
introductory
users,
there
probably
are
going
to
beach
vide
config
in
a
similar
way.
It's
their
database
will
just
export
and
import,
and
so
this
only
becomes
a
problem
with
you're
trying
to
manage
version
using
version
control,
which
of
course,
is
like
the
big
reason
we
make
it
yeah
that.
B
Candace
it's
hard,
though
I
will
admit
all
right,
I,
think
Jenna.
We
have
another
meeting
at
two
with
the
city,
folks
and
so
I
think
we've
gotta
wrap
this
up
and
yeah.
We
just
have
to
continue
discussing
the
virtues
and
downsides
of
the
block
configuration
problem,
because
I
can't
really
decide
which
one
we
should
do
either
Jen's
Jen's
in
favor,
basically
doing
all
of
them.
I
think.
A
B
B
The
jumper
dealers
yeah
but
I'm
sure
dr.
Elmont,
will
have
some
things
to
say
like
I,
if
you
posta
issued
properly
TV
so
on
the
run
differential
oil
patch
and
he
probably
would
would
be
more
than
happy
to
have
some
additional
collaboration
there.
Even
if
it's
in
a
different
approach,
like
I'm
sure
I'd
love
to
discuss
it.