►
Description
Development agenda: http://bit.ly/1QqORPb
Hangout: http://bit.ly/1UjTQZ5
B
We
are
live
a
happy
Thursday,
April,
twenty-eighth,
everybody
we're
gonna,
do
a
little
run
through
our
weekly
development
task
agenda,
starting
with
general
announcements.
There's
a
new
announcement
this
week
that
backdrop
was
contacted
by
the
organizers
of
drupalcamp
czechoslovakia,
which
is
interesting
because
there
isn't
a
checklist
Lakhia
anymore,
there's
like
a
Czech,
Republic
and
Slovakia,
but
apparently
it's
still
called
dribble
camp
Czechoslovakia.
So
that's
a
thing
it's
happening
and
they
want
to
know
more
about
backdraft.
So
if
anyone
is
near
Czechoslovakia
or
interested
in
traveling
to
/,
take
the
city
in
particular
is.
B
Bratislava
they're
having
a
camp
and
they
want
speakers
so
andy
says
it's
in
Slovakia.
I,
don't
know
where
that
is.
But
if
anyone
is
interested
in
going
to
Slovakia
and
talking
on
backdrop
I,
definitely
let
us
know
we
have
slides
you
can
present
from
or
if
you
want
to
give
your
own
talk,
that's
fine.
We
have
resources,
we
could
share
with
you,
but
they're
definitely
eager
to
hear
more
about
back
Jeff.
So
anyone
who
is
located
over
there
or
wants
to
travel
there.
Let
us
know
next
up.
B
We
also
have
free
Calla
box,
alpha
access
for
backdrop
developers.
So
the
way
Calla
box
works
right
now
is
it's
in
alpha
and
you
are
required
to
have
a
code
to
download
it
and
that's
just
because
it's
an
alpha
as
soon
as
it
goes
to
beta.
That
code
will
not
be
required,
but
you
want
to
try
early.
We
have
a
sign
up
link
in
the
Google
hangout
or
Google
agenda
the
google
doc.
B
But
if
anyone
wants
it,
you
can
and
you're
watching
this
later
and
you
don't
have
access
to
the
google
doc
or
the
cat
in
the
sidebar.
You
can
go
ahead
and
send
us
an
email
to
info
from
CMS.
Organ
will
definitely
send
that
off
deal
socal
a
box
for
those
of
you
who
don't
know
is
a
local
development
environment
that
uses
dapper,
and
it
will
give
you
a
set
up
of
backdrop
running
locally.
B
If
you
want
to
try
give
that
a
shot,
that's
pretty
cool
tool,
then,
as
usual,
we
do
have
create
phpstorm
licenses
for
backdrop
developers
to
so.
If
you
want
to
give
phpstorm
a
try
in
your
a
backdrop
contributor,
you
can
send
us
an
email
to
info
backup,
CMS
torque,
and
we
can
send
you
a
link
to
get
a
copy
of
phpstorm
if
you
are
a
contributor,
but
are
not
a
member
of
the
contribute.
Let
us
know
about
that
too.
B
We
can
help,
get
you
through
that
process
and
get
you
have
to
be
on
that
list
in
order
for
phpstorm
to
authorize
use
of
their
product,
but
there's
if
you're
willing
to
be
a
co
maintainer
on
a
project.
We
can
help
you
with
that
as
well.
All
right,
also,
if
you're
interested
in
a
dragon
t-shirt
or
hoodie,
we
are
giving
away.
As
thank
you,
gifts
in
exchange
for.
B
Donations
to
backdrop
CMS,
so
you
can
donate
on
the
contribute
page
backdrop
see:
my
storage
/
contribute
if
you
are
already
a
contributor,
either
code
or
passion
we
take
that
loosely.
You
have
earned
a
dragon
t-shirt,
and
so
we
will
definitely
send
them
out
and
I
did
get
your
email
clone
us
and
we
will
definitely
let
you
have
t-shirts.
If
that's
what
you
want
anyone
else,
I
think
I
sent
a
couple
off
last
week,
I
sent
an
email
to
info
backdrop
CMS
to
org.
B
If
you
would
like
a
t-shirt
sub
to
you,
we
can
have
those
go
out
to
updates
from
the
PMC.
We
currently
have
a
couple
of
votes
going
for
new
core
committers.
I
was
hoping
to
be
able
to
announce
when
today,
but
we're
still
missing
a
couple
people,
and
we
have
a
couple
of
the
PMC
members-
are
out
of
town
this
week
as
well.
So
coming
soon
as
usual,
we
should
be
able
to
have
an
update
for
that
for
you
next
week
and
I
want
to
turn
it
over
to
Nate
for
community
growth.
B
C
Let's
see
it's
been
an
exciting
week
in
the
in
contribs,
we're
seeing
some
modest
growth
but
I
think
most
of
our
focus
with
our
small
communities
encore
these
these
past
couple
weeks
so
but
we're
still
seeing
some
activity.
Let's
see,
we
have
238
total
projects
for
backdrop
listed
on
github.
That's
two
new
projects
since
last
week,
I
haven't
actually
checked,
which
ones
they
are
but
so
exciting
to
see
new
modules
coming
in
or
layouts
as
they
may
be.
C
Let's
see,
there's
159
total
projects
with
official
releases
on
backdrop,
semester,
org,
no
new
modules
listed
on
backdrop,
CMS
org
since
last
week,
but
as
those
new
projects
show
up
on
github
as
soon
as
they
make
their
first
official
release
on
github,
they
start
showing
up
on
backdrop,
CMS
org
as
well
so
probably
be
seeing
more
of
those
coming
up
real
soon.
There's
224
releases
of
those
projects
on
backdrop,
CMS
org,
one
new
release
since
last
week,
and
most
exciting
in
my
opinion,
is
that
there's.
C
Oh,
hang
on
that
numbers
not
obeyed
53,
total
backdrop
contributors,
we
have
a
new
contributor
David,
also
known
as
d
Kenyan
are
decaying
from
drupal
org,
which
is
pretty
exciting.
Bringing
15
years
of
Drupal
experience.
He's
got
a
three
digit
user
ID,
that's
pretty
exciting.
Coming
over
to
the
world
of
backdrop,
he's
poured
in
seven
modules
so
far,
but
he
hasn't
transferred
them
into
the
backdrop
contribute.
He
also
wrote
a
pretty
sweet
shell
script.
That
actually
does
the
porting
of
modules
for
him,
which
is
pretty
cool.
C
Just
does
all
of
the
you
know
the
the
legwork,
the
find/replace,
the
make
hook
config
info
the
update
the
settings
forum
update
the
info
file,
those
sorts
of
things
which
is
pretty
sweet.
You
can
find
his
application
in
the
closed
backdrop
contribs
and
that's
where
he
posted
that
that
gist
I
suggested
that
he
put.
Maybe
we
push
that
into
the
brush
key
or
something
like
that.
You
know
somewhere
would
somewhat
a
little
more
permanent
but
yeah
we'll
figure
that
out
anyway
welcome
David.
We're
really
excited
to
have
you.
C
We
have
two
hundred
and
eight
total
user
accounts
on
backdrop
CMS
dork.
Last
week
we
had
160,
so
that's
48,
new
signups
since
last
week,
which
probably
had
something
to
do
with
the
newsletter
that
we
sent
out
that
tell
people
hey,
you
can
create
a
user
account,
and
so
a
lot
of
people
did
so
that's
really
exciting.
Yay
marketing
it
works
yeah.
C
So
that's
exciting.
We're
really
glad
to
see
that
those
new
years
is
coming
on
to
backdrop
CMS
org
as
well:
ok,
infrastructure,
things
that
are
around
backdrop.
The
project
that
aren't
the
project
itself,
mostly
drush,
get
hub
integration
and
our
flagship
website.
The
first
item
on
the
agenda
here
is
usage.
Statistics
are
usage.
Statistics
has
been
kind
of
working
for
months
now,
I
actually
took
a
look
at
it
this
weekend
and
reran
the
number-crunching
script
several
times
to
work
out
some
kinks
with
it.
C
C
So
we
have
all
the
usage
numbers
on
everything
for
almost
half
a
year
now,
but
for
some
reason
it's
not
crunching
new
weeks
now
so
I'm
going
to
take
yet
another
look
at
that,
if
anyone's
interested
in
helping
that
it's
just
project
module
that
has
the
bug
in
it
and
we're
trying
to
work
that
out
after
we
get
doesn't
have
to
be
afterwards.
But
once
we
get
usage
statistics
working
consistently,
we
also
would
like
to
add
charts
to
the
usage
pages.
C
That's
issue
98
in
the
backdrop
CMS
or
queue,
and
also
start
tracking,
not
just
modules
that
are
enabled
but
specific
features
within
those
modules
which
is
issue
99.
In
the
backdrop,
CMS
or
guess
uq
it.
So
those
project
we'll
take
a
little
bit
of
work,
collaborating
between
core
which
needs
to
report
that
an
update
module,
contribute
module
and
backdrop
CMS
or
get
self.
So
those
sorts
of
tasks
take
a
little
bit
of
collaboration,
but
what
it
all
ties
together.
D
D
Josh
dl
wasn't
working
because
they
didn't
have
w
get
in
the
container,
but
I
filed
an
issue
1284,
and
these
says
that
he'll
be
pretty
easy
to
fix.
That's
good
and
in
cala
box
uses
PHP
7,
which
is
kind
of
fun.
I
play
around
with
it
too
much,
but
backdrop
was
working
on
it
nicely
PHP
7
it
was
my
sequel
57,
which
gives
us
some
more
confidence
in
one
of
those
issues.
We
had
a
while
back
mm.
C
D
And
the
rest
of
it
is
the
same
old,
give
Josh
a
spin,
make
sure
on
the
ax
branch
and
if
you
have
a
favorite
brush
feature
with
some
issues
in
the
dresser
shook
you
like
the
one
named
mention
that
would
be
pretty
cool.
I.
Think
you
have
that
automated
module
Porter
do
some
legwork.
That
would
be
pretty
cool,
pretty
neat
and
that's
what's
going
on
with
josh.
From
my
perspective,
awesome.
C
Eventually,
we
talked
about
it
for
weeks,
I'll,
publish
my
findings
on
performance
from
a
backdrop
on
55,
56
and
PHP
7,
which
it's
faster
of
course,
but
we
also
run
automated
tests
on
PHP
7
all
the
time
on
Travis.
So
we
know
with
a
high
degree
of
certainty
that
the
backdrop
already
runs
on
on
PHP
7.
It
actually
was
doing
some
research
on
drought
are
on
Drupal
7
and
PHP.
C
7
I
thought
that
they
were
working,
but
they
still
have
some
like
pretty
serious
issues
like
you
can
load
a
backdrop,
a
website
on
page
b7,
but
there's
like
session
handling
problems
which
can
be
pretty
bad.
So
it's
just
one
of
those
things
I
guess
it's
still
relevant
that
Drupal,
7
and
PHP
7
really
not
working
together.
Quite
yet,
but
we've
had
our
our
page
37
support
working
since
pretty
much
the
week,
Paige
v7
came
out
so
anyway
exciting.
B
Sure,
I'm
not
sure,
there's
much
new
since
last
week
we
are
currently
working
on
a
showcase
section
and
I
know
Eric
you
volunteer
to
help
do
some
of
the
site.
Building
on
that.
So
thank
you
in
advance
for
all
of
your
hard
work.
We
are
still
waiting
on
designs
for
that,
so
that
isn't
going
to
be
ready
on
any
time,
particularly
soon,
but
I
think
getting
a
place
for
people
to
add
stuff
is
a
great
first
step.
B
Other
things
we
want
to
include
on
the
website
is
a
single
sign-on
feature
with
github,
so
anyone
who
has
a
github
account
doesn't
have
to
also
create
a
separate
account,
my
back
to
obscene
Lestat
org.
They
can
just
click
a
button
and
how
username
I
think
would
also
be
great
for
all
who
are
already
on
our
site
to
be
able
to
link
their
current
account
with
github.
So
there's
a
lot
of
single
Atlanta
and
solutions
for
Drupal.
It
is
already.
We
can
definitely
look
at
that.
B
I
think
we
looked
to
see
if
there
was
already
a
single
sign-on
with
github
module
for
Drupal
and
there's
not
there's
a
couple
of
ones
that
are
a
little
bit
similar
that
we
might
be
able
to
pull
from,
but
I,
don't
think,
there's
anybody
working
on
single
sign-on
for
backdrop
CMS,
yet
so
that
item
our
issue
is
currently
signed
to
need
volunteers.
So
apparently
Andy
created
a
module.
It's
a
single
sign-on
printer.
B
Well,
second
meeting
me
I
know:
you've
got
a
lot
on
your
plate
right
now,
maybe
next
month
or
the
month
after
that
way,
we
can
get
your
expertise
on
the
single
sign-on
issue.
For
for
backdrop,
as
well
things
that
we
recently
added
is
the
surface
provider
listing
which
is
under
in
the
cyber
I've
got
a
link
called
support,
long-term
we're
going
to
be
adding
other
stuff
in
there,
like
the
documentation
section
that
dr.
B
Bowman
has
been
doing
a
bunch
of
work
on,
there's
also
been
a
bunch
of
conversations
about
putting
forums
back
on
the
agenda
for
things
we
can
do
for
vector
of
CMS
network.
So
I
think
it
might
be
good,
temporary
and
said
that
I
checked
out
word
to
press
this
site
and
they
have
both
forums
and
documentation
under
support
section,
as
well
as
their
service
providers.
So
I
thought
we
might
kind
of
model
that
once
we
get
all
those
features
done
right
now.
B
All
we
have
on
that
section
is
service
providers
and
that
would
be
open
to
changing
the
link
title
from
a
support
if
it's
not
anything
else
related
to
support.
Yet
so
that's
a
follow
up.
We've
got
on
that
issue.
We
are
waiting
for
a
design
review
for
the
service
provider
listing,
as
well
as
the
event
listing,
as
well
as
the
news
section.
So
anybody
who
wants
to
do
kind
of
a
design
pass
on
site
make
sure
we're
up
to
snuff
with
the
rest
of
our
kind
of
aesthetic
on
site.
B
That's
definitely
I'm
going
to
be
appreciated.
We
also
have
a
bunch
of
all
issues
related
to
the
find
module
teams
and
layouts
pages.
Some
of
those
are
technical.
Where
we
just
don't
have
the
data
we
need
to
display
need
to
figure
out
how
to
get
it.
Some
of
them
are
designed
implementations,
but
in
general,
there's
a
lot
of
improvement
that
could
happen.
There
I
think
the
more
people
start
using
backdrop.
The
more
important
is
we
get.
B
B
Okay,
so
that's
all
we've
got
on
the
backdrop
website.
I
think
the
forums
topic
is
going
to
be
the
biggest
can
of
worms.
So
we'll
maybe
talk
about
that
a
little
more
detail
next
week.
Next
up
on
the
agenda
is
news
and
announcements.
I
am
very
excited
to
announce
that
we
have
a
blog
post
ready
to
go
up
today.
There's
no
more
of
this.
Does
anyone
have
anything
they
want
to
share?
B
We
got
one
this
week,
which
is
really
exciting.
Alec
from
Callan
Luna
wrote
a
great
post
on
cala
box
and
backdrop
support,
so
we'll
get
that
up
either
later
today
or
first
thing
tomorrow
morning,
and
hopefully
people
will
love
it.
Next
newsletter
is
scheduled
to
go
out
after
the
next
version
of
backdrop
comes
out,
so
backdrops
scheduled
for
May
fifteenth.
The
newsletter
is
currently
slated
for
me.
20Th,
so
I'll
give
us
a
couple
of
days
to
work
out
any
kinks
as
needed
and
push
another
release
if
needed
before
waste
on
the
newsletter.
B
If
you
are
particularly
passionate
about
marketing,
there
is
a
tag
in
the
backdrop
CM
esta
hora
q,
just
for
you,
its
audience
marketing's
go
ahead
and
take
a
look
there,
there's
a
bunch
of
stuff,
the
developers
or
not
so
good
at,
and
we
would
love
to
get
some
help
from
people
who
have
insight
into
marketing
and
there's
definitely
much
a
stuff
there.
That
is
not
a
huge
time
commitment.
If
you
only
have
about
an
hour
so
to
contribute
to
backdrop,
we
could
use
your
help.
Oh
right.
B
C
So
the
next
bug-fix
release
is
136,
that's
on
it
as
is
needed
basis.
We've
got
five
issues
currently
that
are
tagged
for
that
release,
some
of
which
look
like
they
are
RTB
seed.
So
that's
great,
we'll
probably
be
seeing
that
in
the
next
couple
of
weeks,
probably
prior
to
1
dot,
4
or
if
not,
we
also
have
a
history
of
doing
one
dot
for
are
doing
a
minor
release
and
the
last
bug-fix
release
for
the
previous
version.
C
At
the
same
time,
so
at
the
very
latest,
it'll
be
May,
fifteenth,
yeah
speaking
of
May
fifteenth,
that's
when
the
next
version
comes
out,
which
is
really
exciting.
There's
all
kinds
of
things
that
we've
been
working
on
hard
for
the
past
three
months
about
three
and
a
half
months
and
works
I
did
so
mid.
15Th
is
one
dot
for
dot.
Oh
and
we
have
a
bunch
of
major
items
here
that
we're
rushing
to
try
to
get
those
things
completed.
C
The
first
item
on
one
dot
40
is
redirect
module,
read
our
modules
issue,
9
05
that
was
merged
this
week,
yay
yay
one
major
feature
down
very
exciting:
that's
really
exciting.
We
did
a
whole
bunch
of
work,
making
redirect
module
core
friendly.
We
more
tightly
integrated
it
with
with
path
module
and
made
it
so
that
they
work
better
together
than
the
contribution
had
previously.
C
It
also
makes
it
so
that
things
make
sense
again
in
a
lot
of
ways,
because
in
the
the
port
that
we
had
from
Drupal
7,
it
was
entity
so
he's
using
entity
storages,
but
it
also
was
still
I
did
the
database,
so
you
couldn't
really
use
it
as
an
alternate
like
it
as
an
indie
anyway.
So
yeah
there
was
some
weirdness.
Now,
it's
just
all
just
classic.
You
know.
C
C
We
are
running
out
of
time,
of
course,
so
we'll
see
what
comes
out
of
Mike's
magical
sandbox
here
in
the
next
couple
of
days,
because
we
really
need
to
get
it
at
the
point
that
it
needs
to
be
getting
integrated
into
core
at
this
point
and
we
need,
like
things
like
an
upgrade
path
or
figuring
out
how
we're
going
to
deal
with
an
upgrade
path
because
there's
several
controversia
of
alternatives
and
how
are
we
going
to
move
those
into
into
using
the
core
version
of
references
anyway?
That's
issue
1301.
C
C
A
Sure
yeah
my
I
broke,
my
webcam
did
I
get
a
new
one
soon,
anyway,
yeah
so
I
got
some
great
feedback
from
Graham
and
there's
some
issues
of
the
way.
I'm
positioning,
the
header,
it's
starting
to
feel
betta
ready.
But
there's
definitely
some
important
like
fall
backs
and
features
that
I
want
to
get
in
before
1.4,
and
we
just
talked
about
how
we
will
start
getting
the
layouts
and
bassist
kind
of
in
the
same
repo.
So
we
can
test
them
together
because
they're
they're
going
to
be.
A
A
C
Super
air,
and
then
the
next
issue
on
here
is
core
layouts,
which
is
a
lot
of
ways
related
to
the
new
core
theme.
But
it's
still
a
separate
issue
which
is
698,
we're
doing
a
whole
bunch
of
work,
trying
to
figure
out
how
to
add
new
layouts
to
core
for
the
next
release.
It
looks
like
it's
almost
certainly
going
to
be
bootstrap
based,
and
you
can
read
more
about
it
in
that
issue.
C
It's
getting
to
be
quite
a
long
thread,
but
we
also
just
talked
about
it
for
a
good
half
an
hour
in
the
design
call
earlier
today,
and
so
there's
a
link
in
the
agenda
to
the
YouTube
video.
If
you'd
like
to
watch
the
discussion
there
about
how
to
deal
with
the
new
chord
layouts
yeah
I,
oh
I,
promised
in
the
issue
that
I
would
let
somebody
else
talk
about
court
layouts,
because
I
have
not
been
the
most
involved
person
on
this
topic,
so
it
isn't
jen
jen.
Why
don't
you
give
an
update
so.
B
We
have
I
think
was
sometime
in
the
last
two
weeks
were
like
we're,
not
sure
this
is
going
to
happen,
and
then
there
was
this
huge
push
back.
Remember
he's
like
no.
We
really
wanted
to
happen,
so
we
tried
to
figure
out
how
to
kind
of
control
the
scope
and
get
it
going
and
I
think
we
came
to
a
really
good
conclusion.
B
We
kind
of
talked
around
in
circles
a
little
bit
in
the
issue,
and
now
we
have
a
to
do
list
of
items
that
we
need
to
resolve
in
order
to
get
them
in
so
I
think
it
looks
manageable
to
get
done
in
the
next
few
weeks.
We
better
if
we
get
it
done
like
now
and
I'm
going
to
have
a
week
to
review
it,
and
so
I
know
Andy's
working
on
it.
I'm
gonna
work
on
it.
B
Wes
is
going
to
jump
in
we're
all
going
to
try
and
create
a
little
magic
in
in
these
magical
sandbox
and
hopefully
we'll
figure
out
how
to
get
our
new
chord
layouts
working
with
the
new
poor
theme
and
we'll
do
some
testing
on
fire
ticket
will
do
some
testing
on
some
other
contribs
and
make
sure
everything
is
going
according
to
plan.
But
if
you
guys
are
interested
in
what
is
left
to
be
done,
you
can
check
out
the
issue
queue
for
that.
It
is
a
number.
C
Great
alright
other
items
for
one
dot
fork.
We
have
improving
the
rich
text
editor
in
here
that's
issued
1087,
which
is
a
meta
issue
of
a
bunch
of
sub
issues.
The
only
really
critical
item
we
have
from
that
issue.
I
mean
there's
a
lot
of
things
we
can
improve
about
the
rich
text.
Editor!
There's
no
doubt
about
that.
But
many
of
those
things
in
that
meta
are
bugs
and
bugs.
We
can
really
fix
it
anytime
as
long
as
they're,
not
API
breaking.
C
Let's
see
other
items,
we
have
these
in
a
separate
category.
In
the
agenda,
because
they
want
on
the
original
outline
for
one
dot
for,
but
it
looks
really
likely
that
it
will
happen
and
that's
a
we've
got
user
experience
improvements,
but
in
particular
we
are
talking
about
project
browser
project.
Browser
issue
is
issue.
1399,
we've
done
a
ton
of
reviews
and
a
ton
of
work
on
this
dock
beaumont
has
come
back
and
pushed
update.
After
update
after
update
to
project
browser,
I
think
that
it's
getting
really
really
close.
C
It's
my
agenda
for
this
week
is
to
review
and
push
that
forward.
So
I
think
we'll
probably
be
seeing
the
merger
project
browser
this
next
week,
which
would
be
really
exciting
to
have
another
major
feature
down
for
on
dot
4
20.
Let's
issued
1399,
it's
really
fun
to
go
and
try
it
out.
You
can
use
one
of
the
live
sand
boxes
or
you
can
pull
it
down
locally.
It
basically
just
exposes
the
ability
to
find
and
install
modules
themes
and
layouts
within
the
UI.
C
It's
just
that
you
had
to
copy
and
paste
a
URL
into
a
field
which
is
very
awkward,
and
so
this
adds
that
ability
in
a
much
more
usable
and
findable
way
that
you
can
just
click,
install
new
module
from
the
top
of
the
modules
page
or
find
new
modules
from
the
top
of
the
modules
page
and
then
find
the
module
you
want
or
bulk
find
modules
you
want
and
install
them
all
at
once.
It's
actually
really
really
cool
yeah,
there's
also
a
bunch
of
other
issues,
tagged
with
you
x,
in
square
brackets
on
github.
C
If
you
would
like
to
find
other
issues
that
improve
the
usability
of
backdrop,
there
are
a
slew
of
them,
they're,
also
DX
issues
for
developer
experience
again
square
brackets
DX
both
of
those
categories
we're
trying
to
continuously
improve
all
the
time.
If
you
could,
if
you
feel
passionate
about
those
things,
filing
pull
requests
or
working
on
those
issues
is
always
appreciated.
C
That's
all
we've
got
as
far
as
the
main
weekly
agenda
goes.
We
have
sprints
every
Thursday
like
that's
today,
we'll
be
hanging
out
in
get
er
chatting
together.
We
will
also
be
in
the
github
issue,
queue
probably
a
lot
of
action
around
layouts
and
themes,
because
there's
been
a
lot
of
activity
on
those
areas
in
the
past
couple
of
days,
I'm
also
going
to
take
a
look
project
browser.
So
if
you
are
interested
in
participating
now
is
a
great
day
to
be
doing
so.
C
The
github
issue
queue,
of
course,
is
github.com
/
backdrop
/
backdrop
dash
issues
and
that's
where
all
of
our
primary
work
for
backdrop
core
happens,
get
er
is
get
ur
da
IM
/
backdrop
/
backdrop
dash
issues
as
well,
and
you
can
meet
up
with
all
of
us
in
real
time
there.
We
also
have
an
IRC
channel,
although
it's
kind
of
fading
away,
not
a
whole
lot
of
activity
happening
there
as
well
as
reddit
channel.
Again,
not
all
I
like
to
be
happening
there
either,
but
they
are
there.
C
We
will
be
there
talking
about
a
using
backdrop
and
civvy
crm
together,
which
is
coming
along
very
nicely:
Twin
Cities,
drupalcamp,
Drupal,
corn,
Bay,
Area,
jerk,
amp
lots
of
exciting
things,
we'll
see
about
drupalcamp
check,
Czechoslovakia,
that's
so
weird,
that's
called
Czechoslovakia
anyway,
the
Czech
drupalcamp.
We
would
love
it
if
somebody
is
available
in
the
area
that
is
going
to
be
going
to
that
camp.
They
want
to
hear
about
backdrop.
We
have
slides
that
you
can
use
to
talk
about
backdrop.
C
So
if
you're
going
to
go
to
that
event,
please
let
us
know,
and
we
can
help
coordinate,
making
a
backdrop
presentation
happen,
books,
beginning
backdrop
CMS
or
backdrop
co-star
dog
beginning
backdrop:
CMS
will
be
out
june
twenty
seconds,
the
first
full-length
backdrop
book:
we're
really
excited
it's
by
Todd,
Thomason,
the
same
author
as
Pro
Drupal
development,
and
it
will
be
out
on
a
press.
He
also
has
a
book
migrating
from
Drupal
to
backdrop
that
is
out
already.
C
A
C
D
We
is
it
easy
to
put
the
agenda
link
in
the
description
of
the
YouTube
video
so
that
we
could
watch
it.
They
could
click
on
the
agenda
and
fall
I.
C
B
I
think
it's
supposed
to
be:
there
usually
want
to
create
the
hangout.
They
put
the
a
gently
agenda
link
in
the
Hangout
description
and
they
hang
out.
Description
is
automatically
supposed
to
become
the
YouTube
description,
so
I'll
look
into
that.
It
could
be
that
we
either
forgot
or
that
it's
not
populating
automatically,
but
it's
suppose
to
we'll
find
out.
B
E
B
Are
so
there
is
going
to
be
a
backdrop
release
coming
immediately
after
drupalcon,
and
so
we
are
definitely
going
to
be
doing
a
lot
of
a
backdrop
coding
while
at
drupalcon,
but
we
don't
know
like
where
or
when
or
any
of
that,
but
we'll
figure
it
out,
there's
probably
going
to
be
like
a
coder
lunch
at
the
hotel
or
something
that
might
be
a
good
place.
B
C
I
know
less
in
LA
we
did
to
dinner,
which
I
think
was
fun
and
we
might
do
something
similar
again,
but
yeah
like
Jen,
says
once
we
get,
the
lay
of
the
land
will
be
more
capable
of
deciding.
If
that's
a
good
idea,
but
I
mean
last
time
it
turned
out
to
be
a
great
idea.
We
had
like
40
people
show
up
to
our
dinner,
which
was
really
exciting.
Yeah.
There
won't
be
any
official
things,
but
Jen
and
I
are
going
to
be
there,
as
are
a
lot
of
other
backdrop,
people.
F
I
yea
sorry,
I'm
I
had
a
few
things.
I,
don't
know
if
you
guys
didn't
receive
the
email
that
I
send
you
there's
a
cute.
Pointment
I
have
a
couple
of
questions
or
there's
a
few
things
that
I
thought
that
maybe
I
kiss
the
PMC
should
be
aware
of,
and
it
is
kind
of
related
to
things
that
you
mentioned.
B
So
that's
a
that's
a
good
question
in
general
like
how
should
a
backdrop
people
be
in
the
Drupal
community
and
what
we
found
is
that
it
is
only
a
triple
con
where
we've
actually
been
discouraged
from
talking
about
backdrop,
that's
where
the
drupal
association
has
asked
us
not
to
present,
and
so
we
go
to
drupalcon
because
we
left
your
pecan
and
we
love
all
of
our
triple
people.
But
we
don't
about
backdrop
there.
B
If
you
want
to
give
a
talk
on
something
else,
and
then
you
know,
while
you're
there
talk
about
backdrop
in
hallways
or
parties
or
whatever
that's
fine,
but
they
don't
want
you
to
give
any
talks
on
backdraft.
So
we
have
found
the
opposite
experience
at
camps
and
meetups,
we're
usually
organizers
of
the
camps,
approached
us
and
asked
us
to
come
to
their
camp
and
talk
about
backdrop
and
I
feel
like
anywhere
or
even
if
it's
not
an
organizer.
B
If
it's
someone
in
the
area
that
says
hey,
you
know
we're
going
to
be
doing
X
thing
in
Portland.
Please
come
to
portland
and
I
want
to
hear
about
whatever
then
it's
coming
from
the
community,
and
so
it
feels
like
that's
a
much
more
comfortable
place
for
us
to
give
the
talk,
and
so
in
general.
If
anyone
asks
please
talk
about
backdrop,
whether
it's
coming
from
a
camp
organizer
or
a
local
person,
then
we
feel
like
it's
valid
for
us
to
go
and
talk
about
backdrop.
B
If
you
want
to
attend
event
and
want
to
talk
about
backdrop,
I
would
definitely
say
you
know
submit
a
session
if
they
don't
want
you
to
talk
about
backdrop
there
they
won't
accept
it.
Most
camps
have
a
usual
process
for
that
and
we're
just
kind
of
trying
to
abide
by
what
people
want.
If
you
feel
like
there
is
more
animosity
at
one
camp
in
another,
you
might
want
to
approach
the
organizers
ahead
of
time
and
say:
hey.
B
Would
you
guys
be
open
to
me
submitting
a
session
about
back
job
and
just
kind
of
make
sure
that
you're
not
upsetting
their
sponsors
or
whatever
they've
got
going
on
that
in
general
people?
You
know
we're
we're
all
dripping
people
to
we.
We
like
people,
they
like
us
for
the
most
part,
it
hasn't
been
an
issue.
I
would
just
say,
act
act
as
you
would
normally
act
in.
It
should
be
fine.
B
We
have
been
to
a
lot
of
drupal
camps
and
handed
out
back
up
shirts
and
then
been
surprised
and
honored
that
everybody
like
instantly
puts
on
the
backdrop
shirt.
So
it's
definitely
cool
to
wear
a
backdrop
shirt
at
a
drupal
event.
It's
also
cool
to
hand
out
backdrop
shirts
at
triple
ovens
in
general,
but
we
have
been
trying
to
avoid
anything
that
looks
like
advertising,
so
we
don't
generally
have
a
booth
format.
Backdrop
at
a
drupal
event.
We
try
not
to
have
ads
on
websites
for
triple
events,
because
we
don't
want
to
feel
like
we're.
B
You
know
stealing
drupal
people
we
want
feel
like
they
want
us
there,
and
so
that's
kind
of
the
the
line.
We're
trying
to
walk
is
like
you
know
where
we're
all
friends
and
we're
all
doing
similar
software,
and
we
do
it
because
we
love
it
and
we're
trying
not
to
make
any
money
angry
so
use
your
best
judgment.
I
would
say.
F
Yeah,
this
is
pretty
much
covered
everything
I
wanted,
because
that
was
a
subsequent
question
to
whether
if
we
got
the
sense
events,
we
are
where
we
are
not
welcome
to
talk
whether
we
should
be
wearing
a
backdrop.
He
needs
it
or
if
people
find
that
even
a
hostile,
so
so
yeah
yeah.
You
pretty
much
answered
that
question
then
the
third.
The
third
point
that
I
have
here
jon
is
like
I'm
in
Australia,
correctly
and
and
I
would
like
to
contact
other
people
that
are
interested
in
were
registered.
F
B
So
we
did
only
last
week,
I
think,
add
location
for
user
profiles
on
factor
of
CMS
org.
We
do
not
currently
have
any
way
to
search
anyone
by
location,
but
I
think
that's
a
good
point.
I
know
on
drupal.org.
It
lists
specifically
where
you're
located
on
your
profile
page.
We
haven't
even
included
that
yeah
I,
don't
think
so
be
good
to
do
that
and
then
maybe
also
figure
out
some
way
to
let
people
find
other
people
close
to
them.
I
think
it's
a
good
idea.
I
think
you're
right
that
you
know.
F
So
sorry,
so
I
was
thinking
because
I
don't
know
if
they
should
be
like
a
tech
books
on
their
profile
to
say,
allow
people
near
my
area
to
contact
me
or
something
like
that.
I
will
figure
it
out,
but
but
so
long
as
this
is
a
subject
that
everyone
is
a
winner
of
its
cool
and
then
the
fourth
point
that
I
had
on
my
nose.
F
I've
been
conducted
by
a
Greek
person
he's
actually
the
I
think
the
lead
on
the
soul,
translator
of
WordPress
a
bit
community
or
something
like
that,
and
he
contacted
me
via
email,
past
februari.
Unfortunately,
his
email
slipped
off
my
radar
and
he
was
asking
whether
I
was
keen
on
on
starting
a
support
forum
with
him
for
backdrop,
I
have
replied
to
him
that
I,
don't
think
it's
a
good
idea.
F
If
the
person
that
is
registered
to
the
impact
with
CMS
can
sort
of
like
create
an
issue
no,
and
that
would
automatically
create
an
issue
indeed
have
and
then
sort
of
like
we
have
this
thing
synchronized
these
people
find
it
especially
Drupal
people
find
it
more
familiar
to
sort
of
like
go
to
the
CMS
website
official
website
and
then
find
their
support
link.
And
then
there
should
be
at
like
initiative,
and
then
they
file
requests
through
there
so
yeah.
That
was
his
point
as
well.
F
B
B
Unfortunately,
I
think
I'm,
not
a
fan
of
having
two
issues
like
one
on
the
issue:
queue
and
one
on
github,
just
because
I
think
that's
going
to
become
kind
of
a
nightmare
in
terms
of
maintaining
them.
I
also
think
that's
bad
for
SEO.
B
We
have
like
a
generic
backdrop
user
that
adds
comments
and
how
do
they
find
also
searching
on
github
is
not
not
good,
but
how
do
we
like
help?
People
find
the
particular
issue,
or
do
we
just
automatically
create
new
ones
and
then
do
we
have
people
like
watching
the
issue
queue
to
try
and
figure
out
whether
these
are
duplicates
or
not?
It
just
seems
like
a
big
problem.
I
think
it
might
be
better,
and
this
is
kind
of
what
I
was
thinking
about
anyway.
B
If
we
can
set
up
some
kind
of
a
curated
forum
that
would
then
point
to
relevant
issues
in
github,
so
that
people
can
say
like.
Oh,
you
know
I'm
having
problems
installing
and
it
can
be
more
actual
support
in
on
backdrop,
CMS
org
and
then
it's
like.
Oh,
we
found
a
bug
and
then
we'll
have
an
issue,
an
issue
queue
for
developers
that
explain
the
bug
in
the
progress,
and
so
the
forum
would
just
say
like
keep
an
eye
on
the
issue,
but
then
it
isn't
necessarily
necessary
for
those
people
to
engage
in
the
issue.
B
B
People
who
are
comfortable
in
the
forum
will
learn
how
to
use
github,
but
maybe
we
can
kind
of
help
get
them
over
that
initial
intimidation
by
having
people
help
I,
don't
know
it's
definitely
a
hard
problem
like
what
we're
using
github,
because
it's
github
not
because
it's
the
best
tool,
that's
out
there,
but
I
think
for
a
developer
engagement.
B
It's
important
that
it's
github
I,
don't
know
how
to
make
that
easier
for
non
developers,
but
I
think
having
some
tool
for
non
developers
to
use
is
important,
which
is
why
I
think
revisiting
the
we
need.
Our
own
forum
issue
is
a
good
place
to
start
and
then,
if
we
can
figure
out
how
to
kind
of
have
a
conversation
in
one
place
and
bugs
in
another
place,
there
might
be
a
better
way
to
kind
of
bridge
that
gap.
B
I
don't
know
if
anyone
else
has
any
other
strong
feelings
on
how
to
help
people
who
aren't
github
friendly,
get
the
help
they
need
with
backdrop
yeah.
C
But
then,
when
you
click
on
them,
it's
going
to
go
to
github
and
that
way
people
that
come
to
backdrop
see
my
start
org
like
wanting
to
report
a
problem
or
something
that
they
can
find.
Oh
here's
the
issue
list
and
have
it
searched.
Although
you
know
that
would
only
be
for
core.
Like
there's
other,
you
know,
we'd
have
to
figure
out
to
deal
with
can't
ribbons
like
that,
because
otherwise
yeah
they
I
mean
there's
lots
and
lots
of
issues.
B
So
I
also
like
the
idea
of
integrating
like
if
we
could
build
a
like
a
form
that
would
post
to
github
in
a
search
tool
that
would
search
github.
We
can
definitely
help
people
get
to
where
they
need
to
be
I.
Just
am
a
little
bit
worried
about
core
versus
contribute
up,
and
that's
going
to
be
hard
for
new
people
to
understand
like
why.
Why
can't
I
find
the
problem
with
my
kinship
module?
The
same
way
I
can
with
my
core
module,
but
there
might
be
a
way
we
can
bridge
that
gap
too.
F
B
D
I
think
if
we
can
have
the
forum
on
backdrop,
CMS
be
discussion
about
the
issues
and
how
people
want
it
to
be,
and
then
we
could
have
a
you
know,
a
taxonomy
term
or
something
that
says
ready
for
dev
and
then
that's
what
it
goes
to
github
one
of
the
frustrations
as
a
developer
I
had
in
drupal
and
and
backdrop
is
when
I'm,
when
I
have
two
hours
to
get
dedicates.
Something
I
want
to
contribute
back
to
open
source.
You
don't
know
what's
pick
and
then
you
pick
one
and
it's
really
not
right
for
dev.
D
It's
not
flesh
now
how
the
functionality
wants
to
be
yet.
So
if
we
have
those
things
that
are
ready
for
dev
and
then
they
go
together
when
they're
ready
for
dev
I,
don't
think
we
can
completely
eliminate
that
problem.
But
I
think
that
would
be
a
good,
better
developer
experience,
especially
for
people
who
are
looking
to
get
into
contributing,
but
it
would
be
hard
would
be
a
lot
of
curating.
You
need
eyes
on
the
content
stuff
like
that.
Yeah.
B
I
think,
starting
with
building
a
forum
is
a
good
first
place,
and
then
we
can
figure
out
how
we
need
to
help
get
people
to
issue
cues
or
not,
or
if
we
need
to
have
more
integration
with
search
like
well,
we'll
figure
out
what
all
of
our
problems
are
and
hopefully
and
using
the
tools
will
somehow
figure
out
potential
solutions
and
get
them
going,
but
I
do
like
integrating
with
github
and
not
duplicating
as
much
as
possible.
B
I
I
don't
know
that
we
can
do
a
better
job
than
github
at
user
experience,
but
I
think
that
we
will
have.
We
have
a
very
different
audience
in
a
lot
of
ways.
We've
got
a
bunch
of
people
who
aren't
to
be
developers
and
github
is
primarily
for
our
developers
so
trying
to
figure
out
how
to
tailor
what
we
do
to
account
for
our
entire
audience
is
also
going
to
be
something.
Github
is
not
thinking
about
so
better,
maybe
not
but
encompass
more
people,
possibly
so
yeah.
B
F
Last
last
thing,
since
you
sort
of
like
to
mention
it,
it's
related
to
that
I
think
that
we
should
continue
at
least
or
or
have
at
least
a
a
summary
of
the
barriers
boy
implementing
something
like
that.
I
don't
have
much
time
today,
but
later
tonight,
I
will
file
an
issue,
so
we
have
a
place
where
we
talk
about
it
or
at
least
have
a
list
of
ideas
or
things
that
we
need
to
tackle,
at
least
at
all
right.
That's
it
great.