►
From YouTube: Backdrop weekly developer check-in
Description
Weekly check-in on Backdrop CMS community, development, and infrastructure tasks.
A
Alright,
we're
on
air,
it
is
thursday
november
nineteenth
nate
is
happily
at
the
nonprofit
developer
summit
in
downtown
oakland
today,
so
he's
not
here,
I'm
in
the
fort
alone.
Usually
that
means
I
just
talk
really
fast
in
the
meeting
goes
really
quickly,
so
that
you
can
see
how
those
kids
general
announcements
we
have
dragon
t-shirts
and
hoodies.
If
you
look
like
one,
you
could
go
to
backdrop
CMS
to
org,
slash,
contribute
and
if
you
make
a
donation
for
twenty-five
dollars,
will
mail
you
a
t-shirt.
A
If
you
make
a
donation
for
fifty
dollars
from
a
hoodie
as
a
thank-you
gift,
we
have
a
lot
of
them,
but
we
are
planning
on
distributing
them
all
year
at
camps
and
conferences
set,
and
they
do
tend
to
go
fast
and
there
are
a
lot
of
people
around.
So
if
you
want
yours
make
sure
you
get
early
and
we
can
send
it
off
to
you
plenty
right
now,
but
there
might
not
be
after
the
next
event,
just
fair
warning.
A
If
we,
if
you
want
to
use
phpstorm,
we
have
a
bunch
of
licenses
that
are
available
for
free
to
backdrop
CMS
developers.
So
if
you're,
a
member
of
the
backdrop,
contribute
you
can
send
an
email
to
info
effective
CMS
to
Oregon,
will
send
you
a
license
key
if
you're
not
a
member
of
the
contribute,
but
you
do
consider
yourself
a
backdrop
developer.
We
can
get
you
into
the
kinship
group
either
if
you're.
A
In
co,
maintaining
a
module
theme
or
layout
or
reporting
or
creating
one
of
your
own,
so
most
people
who
are
developers
usually
have
one
of
those
things
going
on
and
we
can
help
get
you
through
the
process
to
get
your
code
up
there
to
be
officially
part
of
the
community.
If
you
are
interested,
no
important
updates
from
the
project
management
committee
so
far
community
growth.
Since
last
week
we
have
161
total
projects
for
backdrop,
CMS
that's
on
github,
and
that's
only
one
new
one.
A
Since
last
week,
I
think
everybody
has
had
their
hands
full
with
the
coming
release
of
Drupal
8.
So
before
I
go
any
farther
I
just
want
to
say
congratulations
to
all
the
people
that
worked
so
hard
on
getting
Drupal,
8,
ready
and
getting
out
the
door
I'm
excited
to
see
it
in
the
wild
so
good
as
to
everyone
involved.
A
Also
on
our
community
growth,
we
have
100
into
projects
on
backdrop,
CMS
org,
which
means
those
are
projects
that
have
official
releases.
The
developer
or
maintainer
of
that
project
has
given
it
an
official
release.
Number,
which
means
it's
ready
for
use.
So
I
think
that's
a
pretty
good
stat
we've
been
around
for
under
a
year.
We
have
over
a
hundred
contributed
projects
which
is
pretty
good,
and
if
you
look
at
the
number
of
releases,
so
not
just
the
number
of
projects,
but
how
many
of
those
projects
have
had
11
release.
A
We
actually
a
128
releases,
which
means
that
28
of
our
projects
have
been
getting
continued
maintenance
since
the
first
release,
which
is
pretty
good
and
considering
most
of
the
projects
that
are
out
there.
B
A
New,
so
I
think
that's
a
really
good
sign
in
our
community
is
alive
and
maintaining
itself,
which
is
fantastic
right
now
we
have
42
people
who
are
a
part
of
the
backdrop,
contribute
on
github
and
I
know,
there's
a
whole
bunch
of
other
people
who
are
members
of
the
community,
but
having
contributed
modules,
teams
or
layouts
and
so
they're
not
on
there
just
cuz.
They
don't
have
code,
that's
totally
fine.
A
We
love
you
anyway,
you're
going
to
make
it
so
that
people
who
don't
contribute
code
can
join
the
backdrop
community
by
signing
up
to
the
backdrop
website
and
we'll
talk
about
that
a
little
bit
later
in
the
agenda
infrastructure
tasks,
we
have
been
working
on
update,
checking
because
people
keep
asking
like
how
many
slides
are
running
back
drop
right
now
we
are
collecting
a
bunch
of
data
from
the
status
reports.
Anyone
who
has
update
status
or
I
think
it's
called
update.
Manager,
module
enabled
is
reporting
back
to
the
backdrop.
A
We
just
aren't
properly,
counting
the
statistics
to
aggregate
them
per
module.
So
there
is
an
issue
in
the
queue
for
project
module.
It's
issue
number
nine
and
it
has
a
flaw
request.
Just
need
some
work
to
get
that
sorted
out.
Once
we
get
the
numbers
counting
appropriately,
then
we
will
start
publishing
them
on
our
websites.
Well,
in
addition
to
tracking
which
projects
are
in
use,
we
also
want
to
check
which
specific
sub
modules
are
in
use,
so,
like
who's
using
users
versus
views,
you
I
right
now.
A
That
number
is
just
a
single
number:
it
checks
by
project.
We
want
to
get
information
on
each
specific
sub
module
two,
so
that
in
the
future,
if
we
wanted
to
do
something
like
remove
the
date
repeat,
module
from
the
date,
module
will
actually
have
data
on
how
many
people
are
using
repeat,
so
we
can
figure
out
whether
we
should
do
that
or
not
that's.
Currently,
you
know.
A
We
also
need
to
have
infrastructure
set
up
on
the
backdrop
server
to
be
able
to
deliver
that
data
to
your
website
as
requested
I.
Think
as
we
stand
right
now,
we
have
the
server
up
and
running.
We
have
the
pull
request
against
backdrop.
The
projected
soft
lips
really
good
and
recently
I
added
the
1.3
tag
to
that
issue,
because
I
think
it
would
be
a
great
user
experience
improvement
to
get
into
the
next
minor
version
of
factor.
So
things
are
looking
good.
A
Josh
for
backdrop.
In
the
last
two
weeks,
we've
made
a
ton
of
progress
on
Josh,
mostly
neat
his
made
a
ton
of
Irish
Josh.
He
took
a
look
at
what
the
blockers
were
with
the
current
status
of
things
and
started
filing
for
requests
against
Josh,
which
he's
gotten
a
bunch
of
feedback
from
Josh
maintained,
errs
and
he's
got
changes
merged
into
the
latest
version,
which
is
Josh.
Eight
that
make
Josh
work
for
backdrop
and
right
now
he's
got
it
running
as
a
set
of
command
files.
A
So
if
you
were
running
backdrop-
and
you
want
to
include
Josh
support,
you
can
just
load
those
command
files
into
your
local,
josh
installation
and
it'll
work.
He's
also
noted
that
there
is
a
bunch
of
work
going
on
to
make
josh
less
painful
to
install,
which
makes
me
really
happy
the
last
time
I
had
to
work
on
Josh
I,
don't
know
how
old
the
version
of
dress
that
I
was
running
before
that
was,
but
it
was
really
easy
to
install
and
I
got
it
going
with
no
problem.
A
A
Well
what
the
new
version
of
justice
it
contains
its
own
packager
so
that
you
can
download
installed
Josh
just
like
you
would
download
and
install
any
other
app
or
a
thing
you
want
to
install
on
your
computer
and
it
is
not
a
command
line
tool.
So,
if
you're
a
composer
friendly
and
you
really
wanna
use
composer-
that's
fine!
You
can
do
it
that
way.
But
if
you
are
new-
and
you
just
want
to
install
a
thing
that
gives
you
you
know-
command
line
access
to
your
backdrop
site,
you
can
do
that
too.
A
So
I
think
there's
a
lot
of
really
good-looking
stuff
coming
in
Josh
eight,
so
it's
kind
of
makes
me
really
excited
to
be
working
on
the
next
version
and
italy.
I
was
a
little
bit
worried.
I
was
like
trusty,
that's
the
future.
We
want
to
work
in
the
present,
but
the
future
is
here.
Drupal
8
is
out.
Josh
eight
will
be
out
any
any
moment
and
so
I
think.
Having
backdrop
support
in
that
next
version
is
also
super
fantastic,
so
woohoo
one
caveat
for
Josh
for
backdrop.
A
A
If
you
do
a
josh
status
or
add
rush,
I
suppose
it'll
tell
you
which
commands
will
work
for
which
ones
won't,
which
is
new
in
Nate's,
also
working
on
making
that
a
little
slicker
for
a
josh
for
drupal
as
well,
so
that
if
you're
under
bleed,
you
can
get
commensal,
let
you
do
stuff
like
config
sink.
A
You
also
get
those
for
backdrop,
but
you
won't
get
those
on
Drupal
7,
obviously,
because
no
config
so
just
making
sure
that
the
commands
that
work
on
the
on
the
version
of
the
software
that
you're
running
are
the
only
ones
you
get
access
to
is
what
we're
working
on
now.
So
future
of
Jewish
looks
very
accepting.
A
A
It'll
make
him
feel
like
they're
joining
something
words
right
now
are
like
be
a
part
of
back
job,
but
don't
plug
into
our
website
or
create
a
user
account.
It's
a
little
bit
weird.
The
only
part
only
to
be
a
part
of
backdrop
is
to
join
on
github
and
github
is
very
developer.
A
focused
place
and
I
think
we
need
to
make
it
more
welcoming
to
the
gallant
developers
so
we're
great
news
our
profile.
A
For
what
the
user
profile
page
should
look
like,
so
we
might
be
collecting
a
lot
more
information
than
will
be
displaying
right
away,
but
at
least
we'll
have
an
idea
of
what
we'll
want
their
a
long
term
and
would
be
able
to
build
that
out
as
we
get
people
creating
accounts,
which
is
great
once
people
log
in
we
also
are
going
to
want
to
allow
them
to
do
something
with
their
account.
So
hopefully
we'll
be
turning
on
logins
around
january.
A
First
I
would
love
it
if
you
could
add
a
submit
a
site
for
our
gallery
at
that
same
time,
but
I'm
not
sure
we'll
get
that
done
right
away,
but
we
would
at
least
like
people
be
able
to
add,
like
companies
and
organizations,
to
give
them
credit
to
list
them
in
a
service
provider.
Page
stuff
like
that.
A
So
we'll
see
how
much
of
the
infrastructure
stuff
we
can
get
done,
we'll
see
how
much
of
the
design
stuff
we
can
get
done
and
we
want
to
actually
give
people
something
to
join
and
a
place
to
go
to
find
more
information
about
vector
community
as
a
whole.
So
a
lot
of
stuff
coming
soon
I've
heard
things
we'd
like
to
do
is
once
people
are
signing
into
the
website.
We'd
like
them
to
be
able
to
join
their
github
account
with
their
backdrop
account.
A
So
you
don't
necessarily
have
to
have
to
so
we'll
try
and
set
up
some
kind
of
single
sign-on
so
that
we
can
credit
module.
Maintainer
state
maintains
layout
maintainer
for
the
work
that
they're
doing
on
github
as
well,
we'd
like
to
be
able
to
open
up
access
to
edit
those
project
pages
directly
on
backdrop
CMS.
A
In
particular,
we
need
to
kind
of
reexamine
our
forum
problem,
which
I
think
we'll
probably
do
after
we
get
some
of
these
other
things
done.
Is
that
having
a
well-maintained
forum,
I
think,
has
been
one
something
that's
really
important
to
the
Drupal
community
and
when
the
forum
stops
being
well
maintained,
it
starts
to
be
a
little
bit
of
a
problem.
You
have
enough
people
there
it's
fine,
because
they
answer
each
other
and
point
each
other
in
the
right
direction,
but
this
early
in
the
game.
A
So
I
think
trying
to
figure
out
where
to
tell
people
to
go
to
find
the
people
we
do
have
is
going
to
be
really
important,
so
I
think
maybe
sometime
in
January,
we'll
revisit
the
forum
thing
and
see
if
we
can
come
up
with
a
solution
that
not
only
is
not
a
lot
of
work
for
us
to
implement
but
more
importantly,
easy
to
make
successful
for
people
who
are
using
it
so
good
for
thought
there
all
right.
Let's
talk
about
backdrop,
the
project
and
our
next
release.
One
point
two
point:
three:
is
a
bug-fix
release.
A
I've
been
working
on
a
client
site
for
backdrop
which
is
been
making
me
so
happy.
It
went
live
last
week
and
I
fixed
a
bunch
of
so
I
was
building
it
and
it's
the
kind
of
thing
where
you
know
client
will
send
me
say:
hey
this
thing
over
here
is
acting
funny
and
I'll,
be
like
you
found
another
pub.
So
I'm
really
excited
to
get
this
next
bug-fix
release
it
back.
A
Drop
out
because
there's
been
a
bunch
of
stuff
that
I
found
and
fixed
recently
and
I
think
the
more
people
that
start
using
it
well,
of
course,
keep
finding
more
bugs,
hopefully
also
keep
fixing
the
more
bugs
and
gonna
just
make
the
software
better
through
actually
using
it.
I,
don't
think,
there's
anything!
That's
super
urgent
in
that
bug-fix
release,
there's
a
bunch
of
really
weird
kind
of
edge,
Casey
things
where
it's
like.
A
Oh
I,
put
a
block
into
view
with
a
contextual
filter
that
had
a
default
value
that
substituted
the
node
title
and
then
the
HTML
entities
appeared.
It
was
looking
not
sure
how
many
people
are
actually
doing
that,
but
it
should
be
fixed
in
case
they
do
so
I'm.
Definitely
not
super
urgent,
but
bugs
that
are
fixed
nonetheless,
and
and
I
also
think
we
should
try
and
get
all
the
relevant
patches
from
Drupal
7
40
into
that
release
as
well,
not
sure
how
much
time
you
have
lately
or
if
you've
looked
at
that
at
all.
A
A
If
you
want
to
take
a
look
at
what
those
are
now,
all
of
them
need
to
wait
until
1.3
to
get
in.
Obviously,
as
we
get
user
experience
changes
in
especially
little
ones,
we
can
push
them
so
fix
it
put
it
in
fix
that
put
it
in
figs,
put
it,
and
hopefully,
by
the
time
1.3
comes
out.
All
of
those
issues
will
be
fixed.
Some
of
them
are
doozies.
A
We
have
some
issues
in
there
like
redo
the
field
ey,
which
I
know
is
going
to
be
a
lot
of
work
because
of
the
amount
of
work
that
is
I
also
don't
want
to
add.
On
top
of
that
fix
the
views
UI,
which
is
also
something
we've
been
talking
about,
but
I
would
love
to
see
improved
vias,
you
I
something
like
field
you,
I
abused.
You
I
are
already
separate
modules
and
backdrop.
A
So
it's
the
kind
of
thing
where,
if
we
develop
something
in
can't
rip,
it
would
be
pretty
easy
to
turn
off
the
one.
That's
important
on
the
one
that
can
trip
and
give
a
little
test
that
way
and
see
if
it
works
as
expected
or
better
than
expected,
as
we
hope.
So,
if
those
don't
get
into
1.3,
there
is
still
hope
of
getting
them
in
at
any
point
in
the
future.
1.4
pick
5
as
needed,
so
hopefully
we'll
get
them
in
on
time,
but
I'm.
B
A
Possible,
it's
not
all
right.
We
also
have,
let's
say
handful
of
other
issues.
We
think
are
going
to
be
great
for
1.3
lei.
Let's
follow
up
layout
is
a
new
module.
We
put
into
backdrop
one.
We
know
we
know
it's
not
really
perfect.
Yet
we
have
me
know
if
so
some
problems
with
it.
We
want
clean
them
up.
Rich
text,
editor,
that's
something
that
went
into
1.2
same
thing.
We
put
in
a
Minimum,
Viable
Product,
there's
a
bunch
of
follow-up
issues.
A
That'll
make
it
much
better
and
cleaning
up
our
admin
pages
so
that
they're
all
views
there's
only
one
left.
It's
the
comment
listing.
There
are
a
couple
of
these
bulk
operations.
We
need
to
get
added
before
we
can
convert
that
enjoy
view,
but
I
would
love
to
get
that
off.
Our
to-do
list,
I
would
be
better
experience.
People
can
change
that
using
vuze,
you
I,
just
like
all
the
other
listings
I'm
getting
our
terminology
correct,
or
at
least
consistent,
would
be
really
great.
A
Edit
and
configure
are
two
words
that
we
kind
of
use
entertain
change
ibly
all
over
the
UI.
The
plan
is
to
make
anything
that
is
content
say
edit
and
anything
that
is
configuration,
say
configure,
but
there
is
kind
of
a
weird
grey
line
between
what's
content
and
what's
configuration
so
there's
a
list
there
of
you
know.
Taxonomy
is
probably
content,
but
it's
websites
its
kind
of
configuration
we're
going
to
edit
it
because
it's
hay
from
the
database,
so
that's
kind
of
like
where
our
line
is.
A
A
If
we
end
up
deciding
like
menu
links
are
configuration
but
right
now,
they're
content
will
change
that
link,
so
the
people
who
are
administering
their
sites
in
backdrop
to
well
know
if
I
configure
it'll
match
to
a
config
file,
so
hopefully
we'll
get
that
cleaned
up,
I'm
adding
a
notification
icon.
So
this
is
something
like
when
you
run
status
report.
You
look
at
your
status
report.
Sometimes
there
will
be
something
there
like
your
version
of
jQuery.
A
Is
it
out
of
date
or
something
and
you'll
realize
that
that
notification
has
been
there
for
the
last
six
months
or
whenever
it
was
that
you
updated
the
module
that
needed
the
thing
and
you
didn't
know
because
he
didn't
come
to
the
stash,
of
course,
so
having
something
in
your
toolbar,
your
admin
bar
like
a
little
red
icon
or
a
little
yellow
on
it,
says:
hey,
there's
something
you
should
look
at
here
and
sit
there
until
you
either
dismissed
it
or
solved
problem
I
think
will
help
people
with
that
issue.
We
also
have
this
problem.
A
Where
sometimes
we
you
know
you
install
a
module
and
instantly
you'll
get
a
message
that
tells
you
to
configure
it,
but
as
soon
as
you
leave
that
page,
that
message
is
gone
and
you
can
forget
to
configure
it
so
using
the
status
report
a
little
bit
more,
like
a
notification
system,
I
think
is
going
to
be
great
for
user
experience
to
get
people
to
solve
the
issues
that
come
up
and
then
long
term
we
can
figure
out
like.
A
Maybe
we
should
make
notification
smarter
than
just
either
messages
that
have
print
on
the
screen
or
up
here
in
your
status
or
apart,
but
actually
have
like
some
kind
of
an
inbox
or
I.
Don't
have
something
else,
so
we've
got
two
issues
there.
One
of
them
is
like
just
put
a
indicator
in
the
admin
bar
and
that's
instantly
a
much
better
than
it
is
now
and
the
other
one
is
like
solve
the
notification
system
problem,
which
is
a
little
bigger,
and
maybe
we
can't
get
in
by
1.3,
but
we
can
try.
A
We
want
to
so
there's
an
issue
for
that.
That's
number
6,
39
cleanup,
feel
you
I.
We
talked
about
already,
it's
gonna,
be
really
hard.
There's
been
a
bunch
of
great
work
going
not
on
in
that
in
number
seven
seventy-nine,
but
yeah
we'll
try
and
get
that
in
by
1.3
all
right,
because
1.3
is
a
user
experience
release.
We
are
also
starting
to
think
about
the
kinds
of
new
features
that
they
wouldn't
want
to
add
into
1.4,
and
so
far
we
have
two
candidates
for
that.
A
One
of
them
is
some
kind
of
references
module
which
I
think
McCaffrey's
been
doing
a
ton
of
work
on,
which
is
great,
it'll,
be
hopefully
code.
That
looks
a
lot
like
the
current
references
module,
but
will
provide
a
field
that
works
more
like
entity
reference
where
you
can
choose
which
thing
you
want
to
reference,
whether
it's
a
notary
user
term
initially
and
then
configure
it
the
same
way
across
all
those
different
entity,
types
and
then
other
thing.
That's
on
the
list
for
getting
added
into
1.4
is
some
kind
of
redirect
module.
A
We
want
to
put
something
equivalent
to
global,
redirect
directly
in
core,
but
I.
Think
having
like
an
administrative
page
that
shows
you
all
of
your
redirects
unless
you
set
a
canonical
path
for
each
item
is
something
we're
also
really
going
to
want.
It's
a
minute,
I
think
provides
a
lot
of
clarity
and
how
the
system
actually
works
with
its
paths
and
that
sort
of
thing
and
I
think
will
be
really
useful.
To
get
into
core
is
something
I
use
on
every
website.
A
I'm
not
sure
everybody
who
builds
Drupal
sites
uses
redirect
module,
but
it
is
a
really
popular
module,
so
I
think
it's
definitely
a
candidate
for
Korin
collision
be
great
if
we
could
get
some
actual
data
on
that,
but
1.4
is
long
way
away
so
we'll
see
maybe
by
10
Lou
awesome
good
data
all
right
and,
as
you
guys
are
building
websites
with
backdrop
also
keep
in
mind
what
kind
of
things
you
find
that
you're
putting
on
all
of
your
websites.
A
A
If
not,
we
can
continue
to
Z
youth,
doing
user
experience
releases
or
we
can
start
thinking
about
what
are
things
that
we
need
to
change
that
we
can't
that
might
require
API
changes
and
start
getting
a
future
list
of
what's
going
to
happen.
In
fact,
up
to
there
are
a
couple
of
issues
that
come
up
in
the
queue
where
someone
asks
for
something,
and
we
just
think
about
the
scope
of
the
change
and
go
this.
It's
not
possible
and
schedule
it
for
2x
at
some
point.
A
If
we
decide
we're
happy
with
back
Jeff
one
as
it
is,
we'll
start
looking
at
that
list
and
say:
okay,
let's
look
at
the
stuff
we
scheduled
for
the
future.
How
important
is
that,
when
we
need
to
set
a
date
for
backdrop
to
but
I
think
right
now
we
still
have
a
bunch
of
stuff
we
want
to
fix
in
terms
of
user
experience.
We
also
have
much
features.
A
We
want
to
add
form
click
for
so
we're
most
likely
going
to
have
one
play
for
in
a
1.5
and
we'll
see
about
maybe
January
next
year
being
a
backdrop
to
time
period,
so
honey
dad
work
on
black
truffle,
keep
your
thinking.
Caps
on
add
new
features,
all
right
all
the
time
as
we're
working
on
backdrop.
We
will
be
looking
at
developer
experience
issues,
and
this
is
just
what
it
feels
like
to
write
code
for
backdrop,
whether
that
code
is
CSS,
HTML,
javascript
or
PHP
or
sequel
queries.
A
If
you
find
things
that
feel
hard,
weird,
not
intuitive
confusing
document
them
tag
that
issue
on
github
with
DX
and
we'll
take
a
look
at.
Why
that
wasn't
approachable
enough
and
try
and
figure
out
how
to
solve
it?
In
a
lot
of
cases,
we
can
simplify
things
with
better
documentation.
We
can
provide
brabar
functions.
Little
do
things
for
us,
but
sometimes
the
problems
are
just
so
crazy.
They
go
all
the
way
to
the
core
and
we
need
to
think
about
how
to
change
them
right
now.
Bactrim
is
really
similar
to
drupal
7.
A
We've
gotta
make
our
code
easier
than
what
Drupal
sevens
code
was
like
so
developer
experience,
something
we
are
going
to
have
to
seriously
consider
and
try
and
make
some
changes,
so
note
things
that
are
weird
and
we
will
try
and
fix
them.
One
issue
a
time,
maybe
two
three:
we
get
them
all
eventually,
maybe
probably
not
anyway.
A
We
usually
spend
a
bunch
of
day
working
on
back
job
on
Thursdays,
most
activity
happens
in
the
github
issue
queue,
but
we
also
hang
out
on
IRC
in
the
channel
pound
backdrop,
we've
started
using
git
er,
which
is
a
lot
like
slack,
but
uses
your
github
user
name.
So
you
don't
have
to
log
into
two
different
things
which
I
think
is
so
far
has
been
pretty
successful.
There's
a
little
confusing
trying
to
figure
out
like
which
channel
to
join
right.
Now
there
is
a
backdrop
dash
issues
channel.
A
We
basically
got
one
channel
for
every
repository
on
github
the
backdrop
issues
repository
is
a
public
repository
that
anyone
can
contribute
to,
and
so
the
vac
truck
issues
get
er
channel
as
something
that
anybody
can
join
and
so
I
think
that's
the
front
of
you,
one
we
should
use.
There
is
also
a
git
er
channel
for
backdrop,
there's
also
a
gator
channel
for
backdrop
contribs.
Those
are
those
both
of
those
are
like
closed
group.
So
it's
a
little
weird
calm
to
be
communicating
in
there.
A
So
I
think
we
should
try
and
use
backdrop
issues
as
much
as
possible.
I
spent
some
time
trying
to
figure
out
how
to
make
the
contribute
coupling,
but
it
looks
like
it's
tied
to
the
kinship
project,
which
is
not
public.
So
I
guess
you
know
chat.
Where
were
you
guys
feel
most
comfortable,
we'll
keep
test-driving
Gator
and
see
how
it
goes?
A
B
A
A
Of
like
how
is
it
felt
to
be
on
reddit?
How
is
it
felt
to
me
on
IRC?
Are
the
tools
we're
using
the
right
tools
for
our
community
and
do
a
little
evaluation
and
see
if
we
should
move
any
of
that
on
to
backdrops
and
West
at
work?
And
if
so,
how
much
work
is
often
doing
so
and
so
yeah
keep
in
mind
problems,
you
have
them.
A
You
can
discuss
upcoming
events,
it
is
the
end
of
the
year
and
so
we're
about
a
tempter
holiday
seasons
and
people
are
doing
a
bunch
of
traveling
and
not
doing
a
lot
of
back
dropping
this
week.
A
We
do
have
a
the
nonprofit
developer
conference
here
that
needs
tending
today
a
mountain
tomorrow
next
week
here
in
Oakland,
there
is
an
Oakland
two
point:
O
like
tech
night
meet
and
greet
we're
going
to
go
to
so
I
think
kind
of
getting
out
of
the
dribble
world
and
into
the
kind
of
larger
web
world
is
going
to
be
goods.
A
That's
what
we're
trying
to
do
while
there's
no
Drupal
events
happening,
but
starting
early
next
year,
sand
camp,
the
San,
Diego,
drupalcamp,
februari,
25th
or
27th
has
invited
us
to
come
and
do
a
training
so
we're
going
to
do
another
backdrop.
Training
it'll
probably
be
a
full
day
event
where
in
the
morning,
we'll
do
some
kind
of
very
intro
like
how
to
build
a
basic
site
stuff
and
then
afternoon
we'll
get
into
a
little
bit
of
theming.
So
that
should
be
really
fun.
I'm
excited
about
working
on
that
with
Darius.
A
He
did
one
last
year,
what's
half
day
this
year,
we're
going
to
add
on
to
it
naked
all
day,
that'll
be
great
and
then
drupalcamp
Utah,
which
is
march
forth
through
fifth.
If
you
don't
like
sand
and
prefer
snow,
you
can
head
to
Utah
they're
looking
for
speakers
to
talk
about
backdrop
in
particular,
and
they
also
have
some
perks
where,
if
your
company
sent
to
your
company
I'll
get
sponsorship,
recognition
on
the
website
and
yeah,
it's
game,
gonna
be
great.
Drupalcamp
Chicago
is
also
March
19th
through
22nd.
A
So
if
you
like
cold
but
don't
like
skiing,
there's
another
option,
we
go
to
Chicago
and
hang
out
with
those
kids
there
they're
a
really
great
group
of
people,
they've
been
really
open
to
hearing
about
and
working
with
back
Jeff.
In
addition
to
Drupal,
that's
a
good
place
to
go
as
well
and
that's
all
I
have
on
the
event
calendar
so
far.
Hopefully
we'll
get
all
these
put
on
backdrop:
CM
esta
org
soon,
but
there
is
a
google
ical
feed
which
you
can
find
on
the
backdrop
sumus
org
slash,
contribute
page.
A
A
Yeah
I,
don't
know
how
to
aggregate
an
FAQ
thing.
I
mean
I
feel
like
if
we
set
up
something.
So
this
is
how
to
solve
our
forum
problem
I
feel
like
we
set
up
something
that
was
kind
of
kind
of
like
a
forum,
but
maybe
we
changed
the
fields
to
be
more
like
it
is
on
Stack
Exchange.
So
it's
like
ask
a
question,
get
an
answer,
something
like
that.
That
might
be
a
good
way
to
do
it,
because
then
we
could
kind
of
curate.
A
Those
and
say
here
are
the
questions
that
were
frequently
asked
and
make
a
kind
of
a
list
of
the
top
questions
or
have
some
kind
of
thumbs
up
thing.
I,
don't
know
it's
a
it's
a
big
project
to
trying
to
figure
out
how
to
build
it
forum,
that's
going
to
work
for
this
community,
but
I
think
it
is
something
we
are
going
to
need
to
address.
Having
a
place
for
a
few
people
to
get
answers,
it's
going
to
be
important
whether
it
ends
up
being
IRC
er.
B
A
A
We
know,
you're
going
to
ask
these
questions
because
we've
already
for
them
a
bunch
of
times
but
yeah
I,
definitely
think
like
there
are
going
to
be
questions
coming
from
people
with
experiences
that
we
don't
know
and
making
sure
that
those
people
can
get
answers
as
well
yeah
how
to,
I
think,
is
going
to
be
really
so.
This
is
kind
of
training
right
like
this
is
beyond
just
questions
but
like
how
to
tutorial
stuff,
or
it's
like.
A
How
do
you
build
a
whatever
I
spend
most
of
my
days,
googling
for
those
things
for
Drupal
or
it's
like
oh
I'm,
trying
to
do
this
crazy
thing.
Whatever
the
custard
wills
been
around
for
15
years,
you
can
find
that
just
by
googling
it
it's
going
to
be
a
long
time
before
backdrops
in
that
same
position,
but
yeah
I
definitely
think
there
are
a
bunch
of
really
common
use
cases
that
we
can.
A
B
A
There's
lots
of
lots
of
ways
to
solve
this
problem
and
I.
Don't
know
what
the
right
one
is
that
I
do
think
these
are
good
suggestions
and
Ian.
We
should
keep
thinking
about
how
to
solve
that
problem.
A
A
Okay,
I
think
that's
a
good
idea.
I
would
love
to
see
some
kind
of
curated
like
here
are
how
two
things
I
just
don't
know
where
this
would
live.
I
mean
I
also,
don't
know
who
we're
gonna
get
to
create
them.
I
mean
anyone
could
make
like
everybody's
made
a
blog
but
they're
all
found
a
little
different,
so
kind
of
having
having
the
aggregator
approaches
like
right
at
your
self
leave.
Poland
is
good,
but
youtube
channel.
A
That's
a
great
idea,
so
many
good
ideas
not
enough
time.
Okay,
well,
I,
think
I.
Think
those
are
fantastic
ideas.
Can
we
write
them
down
somewhere?
That's
not
in
the
google
chat
so
forth
with
them.
We're
never
gonna
I'll
just
copy
and
paste
them
into
the
meeting
notes.
So
at
the
bottom.
Then
that
way
we
can
refer
back
to
the
leader.
I
just
have
to
remember:
we
talked
about
it
on
november
nineteenth.
A
A
Has
worked
itself,
you
guys
it's
the
day.
Yeah
I
mean
I,
interrupt
myself
earlier,
just
to
say,
and
it's
probably
good
to
do
it
again.
Congratulations
to
all
of
the
amazing
people
who
spent
time
working
on
producing
triple
eight.
It's
been
five
years
in
the
making.
It
is
a
massive
undertaking
and
I'm
really
glad
that
it
is
out
I.
Think
it'll
be
great
too.
A
You
know
for
all
people
who
have
been
feeling
a
little
burned
out
on
it,
not
coming
up
not
from
you
it's
out
now
that's
going
to
be
huge
relief
companies
who
were
worried
about
upgrading
or
now
going
to
be
able
to
start
like
looking
at
you
know,
can
I
upgrade
my
site.
There's
been
a
bunch
of
really
great
work
about
tools
that
let
you
see
if
all
of
your
modules
are
ready
yet
or
not?
A
Hopefully,
it'll
be
much
less
that
I
in
the
dark
kind
of
transition,
then
it
was
to
Drupal,
7
I
think
the
community
has
learned
a
lot
from
mistakes
of
the
past.
Just
great
I
am
excited
to
have
continued
collaboration
between
backdrop
and
triple
both
in
security
issues,
user
experience,
there's
so
much
stuff
that
we
can
do
together.
It'll
make
what
projects
better
so,
yes,
/
age-related
out
I'm
going
to
Drupal
8
release
party
tonight
in
San.
A
B
B
You
know,
for
the
same
reasons
that
the
backdrop
did
so,
and
you
know,
are
talking
about
sort
of
maintaining
it
on
going
and
not
holding
up
features
for
Big
Bang
I
was
listening
to
a
podcast
from
jeez.
You
know
this
morning
where
he
was
talking
about
like
that.
Big
bang,
you
know
only
only
add
features.
Every
five
years
is
not
really
that
sustainable
model,
which
you
know
is
close
to
to
all
of
our
hearts
and
the
other
thing
actually
came
from
trees
and
I'll.
B
This
is
the
last
one
that
was
going
to
throw
in
it
is,
is
I
heard
web
chick,
quoting
trees,
talk
about
the
decision
to
go
with
Drupal,
8
and
and
and
hearing
one
step
away.
You
know
coming
come
from
trees,
saying
like
well,
they
at
this
point
where
drupal
7
had
become
more
complicated
than
then
it
needed
to
be,
and
they
they
had
to
choose
like
one
of
the
other.
B
They
had
to
either
you
know,
embraces
extra
features
and
do
that
or
simplify
it
and
they
he
said
well,
so
we
took
the
you
know,
embrace
the
complicated
features
fork,
and
it
strikes
me
that
you
know
were
the
other
fork
that
trees
talked
about
like
it.
It
seems
to
validate
the
whole
concept.
So
that's
just
you
know
the
thoughts
drupal
8
that
jumped
out
at
me,
yeah.
A
I
think
that
all
those
things
are
right
I
mean,
I
feel
like
semantic
versioning
is
something
that
the
Drupal
community
had
been
talking
about.
Long
before
backdrop
was
an
idea
in
any
of
our
minds,
and
it's
definitely
something
that
I
think
Drupal
7
and
the
really
low
release
cycle
of
Drupal,
8,
really
oh
kind
of
pointed
as
being
something
that
needed
to
be
solved,
and
the
fact
that
your
blade
is
adopting
it
same
reasons.
A
We
want
in
that
release
and
then
the
bug-fix
release
is
just
like
anything
that
comes
in
between,
whereas
with
Drupal
8
like
they're,
not
scheduling
the
releases
in
the
same
way,
there
they're,
not
or
without
scheduling,
like
features
for
releases
their
schedule
and
releases,
but
it'll,
be
interesting
to
see
if
there's
anything
that
they're
doing
that
we
can
learn
from,
and
vice
versa,
in
terms
of
how
the
two
projects
embraced
the
semantic
versioning
philosophy
differently,
which
I
think
will
be
I,
think
will
be
fun
and
yeah
I
mean
I.
Definitely
feel
like
that.
A
You
know
there
are
a
whole
bunch
of
people
who
want
the
crazy
feature-rich
Drupal
8
system.
Most
of
my
clients
are
not
those
people,
and
so
I
am
really
happy
that
we
have
another
option,
for
you
know
the
small
companies
that
are
perfectly
happy
with
their
Drupal
7
site
or
who
were
perfectly
happy
with
their
triple
six
site
right
and
they
didn't
need
any
more
features
and
they
got
them
anyway.
Now
it's
like
look,
you
can
have
the
smaller,
lighter
weight
software
option.
That
is
still
you
can
still
upgrade
to
it.
A
You
can
still
have
all
the
stuff
you
had
a
triple
seven.
You
got
to
do
a
little
work
to
get
it
there,
but
less
than
you
would.
If
you
went
to
Tripoli
and
I.
Think
that's
kind
of
the
whole
point
is
letting
people
have
options,
letting
everybody
to
choose
the
tool.
That's
right
for
them.
I'm
letting
developers
choose
the
tool
they
want
to
work
on.
I
just
recently
got
to
this
point
where
one
of
my
clients
is
like.
We
want
to
do
blade
so
I'm
like
no.
Thank
you.
A
Never
like.
Oh
really,
I,
don't
think
that's
going
to
make
me
happy.
I'm,
just
gonna,
I'm
gonna
find
you
a
company
to
do
that.
I'm
gonna,
keep
doing
my
thing.
It
was
great
to
be
like
you
know,
as
a
developer,
I
can
choose
to
do
the
thing
that
makes
me
happy,
which
is
fantastic,
I
hope
everybody
else
gets
that
same.
A
You
know
it
has
that
same
kind
of
good
place
to
be
in
where
you
don't
have
to
do
what
you
don't
want
to
do,
because
you
can
choose
to
do
things
if
you
want
to
do
and
for
some
people
that
would
be
like.
Finally,
I
get
to
work
with.
You
know
object-oriented
code
and
Drupal
8
uses
all
this
stuff.
I've
wanted
to
learn
for
forever,
like
twig
or
whatever
it
is,
and
they
can
make
that
choice.
They
don't
have
to
be
stuck
doing
something
they
don't
want
to
do,
but
we'll
see
some
people
have
jobs.
A
A
Yeah
so
I
feel
like
in
terms
of
actress
success.
We
have
I
mean
starting
nowish,
people
are
going
to
start
comparing
things
and
people
are
gonna.
You
know,
I
think
the
momentum
will
start
nowish,
which
will
be
good
I
feel
like
for
the
last
year.
It's
been
like
trying
to
get
ourselves
ready
for
today,
and
now
it's
like
okay,
today's
here,
let's
see
what
happens
so,
okay,
let's
see
more
comments
from
India.
A
I
missed
before
I'm
interested
to
see
the
theming
environment
grow
as
backdrop
sites
will
use
back
drop,
teeming
with
drupal
8
will
probably
be
a
half
headless,
just
fun
to
watch
yeah.
I
actually
have
wondered
about
that
too,
like
there's
been
a
lot
of
headless,
drupal
stuff
happening
and
me
even
since
drupal
6,
I'm
just
using
vuze
right
to
generate
your
data
and
then
writing
your
own
stuff
on
top
of
it
for
the
front
end.
A
But
there
is
like
a
significant
cost
to
using
you
know:
you're,
basically,
building
two
websites,
you've
got
a
back
end
web
site.
You've
got
a
front
end
web
site,
that's
something
that
everyone
can
afford
to
do.
I
think
a
lot
of
the
people
who
are
in
the
position
of
using
Drupal
8
will
be
able
to
do
that
and
I
think
that
that
might
I
that
might
change
the
way
front
and
development
works
a
lot
interpolate,
but
also
things
like.
A
Hopefully,
all
of
the
work
that
we
did
twig
will
make
using
the
existing
front
end
more
attractive
to
people
so
that
there
won't
be
like
oh
I,
don't
want
to
use
that
I'm
gonna
write
my
own
fancy
clean
whatever
the
co
Felipa
will
be
like
oh
I'm,
excited
to
play
with
suede
and
I
want
to
actually
work
with.
What's
there
that
was
my
goal
for
Tripoli
I'll,
see
I
also
think
you're
completely
right
that
most
of
the
people
who
are
in
the
market
for
back
job
sites,
probably
either
won't
want
to
do
ahead.
A
The
situation
part
can't
afford
to,
or
have
a
never
heard
of
it.
Don't
care
in
addition
need
a
website
kind
of
thing.
That's
most
of
my
clients
feel
like
I.
Just
need
a
website.
I,
don't
really
care
how
you
do
it
just
you
know
make
me
a
website
and
I
think
that
that
will
change
the
way
people
work
with
backdrops
from
it
too,
and
that
we
need
to
make
it
easier
to
just
make
it
pretty.
When
I
know,
Wes,
you
and
I
have
a
google
doc.
A
We've
been
working
on
a
bunch
of
weird
things
that
came
up,
I've,
been
kind
of
creating
my
own
list
of
weird
things
that
happened
and
working
on
my
own
site
and
especially
around
like
CSS
identifiers
and
like
where
the
classes
get
added
two
things,
two
things
a
little
weird,
because
we've
got
this
hybrid
of
like
blocks
and
panels
going
on
like
the
CSS
identifiers,
come
out
in
funny
places,
and
you
can't
target
things
exactly
how
you
want,
but
I
think
there's.
Definitely
you
know.
A
Room
for
improvement
in
both
I
am
really
interested
to
see
where
people
take
it
like
having
people
who
don't
have
any
Drupal
experience
come
to
backdrop
and
say
this
is
what
I
find
weird,
I
think
is
going
to
be
super
rushing
to
us,
because
we
don't
really
know.
I
mean
we
kind
of
know
because
we
know
what
people
found
weird
about
drupal,
but
it's
a
difficult
to
be
a
different
thing.
So
yeah
I
can't
wait
to
see
what
can
trim
produces.
A
Anything
else:
no
okay,
with
a
nice
long
meeting
today,
guys
thanks
for
coming
I,
will
see
you
guys
in
the
github
q
I'm
going
to
spend
some
time
working
on
the
easier
profile
stuff.
So
if
any
of
you
have
users
account
user
accounts
on
backdrop
CMS
to
org,
if
you
want
to
log
in
a
later
date,
tomorrow,
I'll
with
something
in
IRC
in
git
er,
when
it's
ready,
oh
I,
would
love
to
get
some
alpha
users
on
their
your
app
for
that.