►
From YouTube: Backdrop weekly 10/2
Description
Backdrop CMS! Today’s agenda: http://bit.ly/1vjmzi6
A
All
right
we
are
on
air,
it
is
thursday,
which
makes
it
backdrop
day
happy
backdrop
day.
Everyone
today
is
october.
It's
a
new
month.
It's
very
exciting,
we're
here
to
do
a
little
status,
update
on
backdrop,
cms
backdrop:
cms
is
a
content
management
system,
specifically
geared
towards
nonprofits
and
small
to
medium-sized
businesses,
and
anyone
who
has
concerns
about
building
a
really
comprehensive
website
on
a
smallish
budget.
A
What
we're
trying
to
do
is
create
a
system
that
has
features
that
are
comparable
to
that
of
triple
eight,
but
on
an
architecture
that
is
more
comparable
to
that
of
triple
seven.
In
fact,
we
think
drupal
7
is
already
too
hard
and
too
slow
and
too
complicated,
and
so
we're
going
to
try
and
make
it
even
easier,
faster
and
less
complicated
in
the
future.
A
Our
timeline
for
backdrop.
We
are
hoping
to
release
backtrack
1.0.0.
This
fall,
which
gives
us
a
few
months
at
the
most
in
order
to
get
everything
done.
But
once
we
get
the
1.0.0
release
out,
we
will
continue
with
more
releases
in
short
iterations,
so
every
quarter
will
come
out
with
a
new
release
that
will
contain
new
features
and
again
we
won't
be
breaking
apis
in
that,
so
hopefully
we'll
be
able
to
get
initial
release
out
and
then
add
a
bunch
of
new
stuff
iteratively
going
forward.
A
So
even
though
1.0
is
out,
that's
not
going
to
be
the
end
of
what's
in
1.0,
we
will
continue
to
improve,
as
time
goes
on
in
terms
of
what
we're
working
on
now.
We
have
a
couple
of
things
which
are
release
blockers,
that
we
need
to
get
done
before
we
can
release,
and
then
we
have
a
couple
of
things
that
are
important,
but
maybe
won't
prevent
the
original
release.
A
So
we're
going
to
start
with
this
list
of
release
blockers
and
some
of
them
are
huge
things
like
the
first
one
here
are
blocks
and
layouts
solution,
drupal
7
for
a
long
time
has
drupal.
All
versions
has
had
a
really
hard
time
figuring
out
how
to
handle
its
layout.
The
drupal
8
had
an
initiative
for
creating
blocks
and
layouts.
That
was
never
realized.
What
we
want
to
do
is
solve
that
problem
once
and
for
all
and
backed
up
and
nate.
B
Yeah
yeah
things
are
continuing
to
roll
along
and
just
a
really
excellent
way
with
blocks
and
layouts
we've
had
the
base
system
kind
of
functioning
correctly.
It's
not
it's
not
part
of
the
project,
yet
it
still
lives
independently
its
own
separate
little
branch
over
in
issue
86.
B
B
I
did
benchmarks
for
the
first
time
this
past
week
and
initially
layouts
were
quite
a
bit
slower
than
the
old
block
system,
but
I
hadn't
done
any
optimization
at
all.
I
went
back
through
and
and
introduced
a
new
cache
table
and
then
made
it
so
that
layouts
were
utilizing
caching
properly
and
now
we're
seeing
like
pretty
significant
performance
improvements
on
the
front
end
like
somewhere
upwards
around
like
15
percent,
or
something
like
that
for
for
the
front
end
yeah,
it's
it's
it's
great.
B
It
seems
like
the
more
blocks
you
have
on
the
page,
the
better
the
the
performance
improvement
is,
which
is
just
it's
just
tremendous,
and
I
think
most
of
that
comes
down
to
there's
like
90
fewer
calls
to
drupal
render
on
the
page,
and
that's
probably
because,
like
we
got
rid
of
the
page
renderable
and
the
blocks
themselves
like
just,
are
rendered
into
text
a
lot
sooner.
So
the
overall
amount
of
rendering
that
has
to
do
all
at
once
seems
to
be
dramatically
reduced.
B
So
yeah,
it's
really
exciting
and
we
haven't
even
added
back
in
block
caching,
yet
block.
Caching,
right
now
is
removed
just
kind
of
as
a
as
a
by-product.
It
needs
to
be
re-implemented,
so
there's
still
room
for
for
more
improvement,
but
right
now,
yeah
we're
looking
just
fantastic
like
the
new
system
is
just
awesome
like
the
functionality
ads
is
incredible.
B
You
know
contexts
they're,
responsive
layouts.
You
can
have
multiple
layouts,
just
all
kinds
of
greatness,
yeah
I'll
stop.
Now
it's
it's
looking
really
amazing.
We
do
need
a
lot
of
more
people
to
test
out
the
new
software,
though
so,
if
anybody
out
there
has
an
opportunity
to
do
so,
please
go
and
see
issue
86.
In
the
backdrop,
github
issue
queue,
find
the
branch
copy
the
branch
locally
and
then
give
it
a
try,
we're
probably
still
a
couple
weeks
away
from
merging.
B
But
I've
been
saying
this,
like,
I
think,
we'll
get
it.
You
know
really
soon.
Here
I
was,
I
said
in
the
last
couple
of
weeks
in
the
next
month,
so
probably
in
the
next
two
weeks
or
so
we'll
see
the
initial
merge
into
the
project.
A
So
we've
solved
the
blocks
and
layouts
problem
and
we've
introduced
a
performance
improvement
which
is
fantastic,
so
other
things
that
we're
working
on
that
are
release
blockers
but
are
underway,
is
we're
working
on
introducing
a
system
for
configuration
management.
So
this
solves
the
problem
of
you
have
a
website
itself.
It's
been
up
for
a
while
and
you've
had
a
new
feature.
A
That
new
feature
requires
some
content
types
and
some
views
and
a
lot
of
things
that
you
do
in
drupal
by
clicking
things
together.
So
what
you
want
to
do
is
click
it
together
on
a
local
site
or
on
a
development
site
somewhere,
and
when
you
have
exactly
what
you
want,
you
want
to
then
deploy
that
to
your
live
site,
and
it's
really
hard
to
do
that
in
drupal,
because
the
things
that
you
click
together
aren't
meant
to
be
deployed.
A
They
live
in
the
database
and
they
stay
in
the
database
and
they
there
are
some
tools,
like
the
features
module
that
lets.
You
manage
this,
but
it
doesn't
work
very
well
just
because
your
wasn't
intended
to
be
used
that
way,
and
so
both
tripoli
and
backdrop
have
decided
to
create
a
distinction
in
the
way
that
the
information
is
sourced
saved.
A
So
if
you
have
configuration
it
gets
saved
into
files
and
if
you
have
data
it
gets
saved
in
the
database
and
as
soon
as
those
things
are
separate,
you
can
then
deploy
your
configurations
from
one
site
to
another.
We've
done
the
same
thing
in
backdrop:
where
we've
got
a
system
that
saves
to
configuration
files,
we
can
deploy
those
configuration
files
from
one
development
to
an
environment
to
another
and
we're
working
on
finalizing
all
of
the
conversions
of
all
of
the
systems
in
core
that
need
to
save
their
configuration.
A
So
where
we
are
right
now
is
that
we
have
several
of
the
subsystems
converted.
We
need
help
with
a
couple
more
most
notably
fields
and
content
types,
because
we
don't
have
content
types
and
fields
converted
to
cmi.
We
don't
really
have
configuration
management,
but
we
have
already
converted
views,
which
was
the
other
big
one,
because
that
was
something
new
that
we
were
adding
into
core.
We
were
able
to
just
write
that
integration
directly
when
views
went
in,
which
is
great,
so
we
still
need
some
help
with
config
management.
A
If
anybody
else
wants
to
jump
in
and
help
work
on
some
of
those
subsystems.
That
would
be
great.
I
know
we
do
have
a
bunch
more
activity
in
the
issue
lately.
So
if
anyone
who's
working
already
feels
motivated
to
work
on
cmi
stuff,
we
would
love
that,
but
we
do
still
need
to
work
on
getting
that
in
before
we
release
this.
Is
that
our
last
huge
remaining
release
blocker
is
getting
these
converted.
A
The
other
thing
that
we
have
here
is
a
view,
as
I
mentioned,
that
views
already
saves
to
cmi,
because
it
was
recently
added
to
core.
We
have
the
entire
view
subsystem
in
core.
What
we
also
have
in
core,
though,
are
a
whole
bunch
of
pages
that
views
could
override
but
doesn't,
and
so
we
need
people
to
build
us
some
views,
and
so
that's
a
a
less
heady
task
in
a
lot
of
cases.
Building
these
views
listings
are
pretty
straightforward.
You
know
some
people
have
started
on
a
few
of
them.
A
We'd
get
those
wrapped
up
and
to
get
all
the
rest
of
them
converted
and
I
think
for
release.
What
we
should
shoot
for
is
getting
all
of
the
front.
End
views
converted
before
we
release
so
getting
stuff
like
the
front
page
and
the
taxonomy
term
listing
and
some
of
the
blocks
converted
into
views
and
getting
our
administrative
listings
converted
to
like
views
plus
views.
A
But
I
think
it's
it's
nice
to
have
not
necessarily
required,
and
that
does
also
require
converting
some
of
the
actions
to
be
able
to
work
from
a
views
interface,
so
there's
a
easy
stuff
which
is
build
some
views
and
then
there's
more
complicated
stuff,
which
is
build
views
and
build
actions
that
work
with
those
views,
and
I
think
for
release.
All
we
need
to
do
is
get
those
views
built.
A
So
anyone
who
knows
how
to
build
views
in
drupal
7
will
know
how
to
build
views
and
backdrop,
and
we
could
definitely
use
your
help
in
getting
those
built
and
added
in
so
other
things
that
we're
working
on
that
are
not
necessarily
release
blockers,
but
that
are
super
important
for
us
are
getting
all
of
the
changes
that
have
been
into
drupal
7
also
merged
into
backdrop.
So
that
includes
anything,
that's
been
committed
and
included
in
731
or
732.
If
it's
out
before
we
release
those
need
to
be
merged
into
backdrop.
A
Just
so
that
we're
not
behind
the
curve
on
what
problems
the
dribble
is
solved,
and
then
we
also
with
something
that
is
super
important.
You
need
to
get
all
of
the
security
releases
that
are
in
drupal
7,
also
in
backdrop,
so
problems
that
have
been
solved
for
drupal
need
to
be
solved
in
backdrop
in
the
same
or
similar
ways.
A
I
know
that
there's
one
of
them
that
we're
still
kind
of
evaluating,
as
was
the
solution,
the
right
solution
for
backdrop,
even
though
it
was
the
right
solution
for
drupal,
but
there
are
a
couple
of
other
ones.
I
know
we've
got
some
traction
on
those
too.
I
think
we've
got
some
pull
requests
so
be
good
to
get
those
cleaned
up
as
well,
and
then
we've
also
got
a
bunch
of
back
ports.
A
Things
that
have
been
problems
have
been
solved
in
drupal,
8
or
solutions
that
have
been
introduced,
that
we
care
a
lot
about
and
we'd
like
to
see
those
in
backdrop
as
well.
These
are
just
kind
of
some
cleanup
tasks,
making
sure
that
we
get
all
of
our
html5
elements
in
so
that
we
have
a
nice
mobile-friendly
base
for
people
to
start
from
and
then
doing
some
cleanup
on
stuff
for
front-end
folks,
like
css
and
javascript,
and
just
making
sure
that
things
are
consistent
from
place
to
place.
A
Those
again
are
not
release
blockers,
but
it
would
be
super
nice
if
we
could
clean
up
our
act.
A
little
bit
on
the
front
end
drew
blade,
is
gonna
have
twig,
which
is
gonna,
be
a
huge
draw.
We
can
do
a
lot
of
the
stuff
that
was
done
in
the
twig
initiative
to
backdrop,
without
actually
changing
to
twig
all
of
the
cleanup
in
css
files.
Javascript
files
template
files,
syntax,
you
know,
consolidation
of
things
can
all
be
done
in
backdrop
as
well.
A
We
just
need
to
make
sure
that
we
focus
on
on
getting
the
most
important
things
done
first,
so
we've
got
a
couple
of
back
port
issues
from
driplet
stuff.
That
would
be
pretty
good
for
new
people
to
come
in.
If
you
want
to
just
help
us
clean
up
some
javascript
files,
they're
little,
they
don't
take
very
much
time
and
you
can
knock
them
out.
A
You
know
one
at
a
time
as
you
have
the
urge
and
we've
got
some
other
stuff
we're
working
on
too,
which
is
less
critical,
but
still,
we
think
really
important
for
backdrop.
The
the
biggest
one
on
here
is
separating
our
identity
from
drupal's
identity.
We
did
fork
this
from
the
drupal
project,
which
means
that
initially,
it
started
off
as
exactly
the
same
thing.
A
We've
made
a
bunch
of
changes
and
we
need
to
make
sure
that
our
identity
reflects
the
fact
that
we
are
a
different
software
platform
now
and
we've
made
some
a
bunch
of
changes
to
the
installer.
So
when
you're
installing
backdrop,
it
doesn't
say
installing
drupal
show
drupal
icon.
It
actually
looks
and
feels
like
backdrop
but
we'd
like
to
take
that
one
step
further
and
make
the
entire
administration
experience
feel
different
as
well.
Drupal
introduced
a
really
great
administrative
theme
in
triple
seven
called
seven.
A
I
think
we
should
probably
also
change
the
name,
because,
having
a
name
called
seven
doesn't
make
any
sense
in
a
software
platform
that
doesn't
even
have
a
version
seven
in
its
history,
but
before
we
do
that,
we
wanna
make
sure
we
know
where
we're
going
in
terms
of
what
it
should
look
like
what
it
should
feel
like,
and
we
do
have
julia
working
on
a
style
guide
for
us
so
that
we'll
have
some
you
know
guides
as
to
what
colors
we
should
use
and
what
fonts
and
where
they
should
go
and
how
things
should
look
as
soon
as
she's
done
with
a
style
guide.
A
Then
we'll
start
writing
some
patches
against
our
administration
theme
and
make
sure
that
it
starts
to
feel
a
little
bit
different
than
drupal
as
well
other
things
we're
working
on.
Obviously,
I
talked
about
how
there's
a
lot
we
can
do
on
our
front
end
and
our
theme
system
to
clean
up.
So
that's
an
issue
here
again,
not
a
release
blocker,
but
we
can
do
some
consolidation
of
things.
We
can
do
some
making
things
make
more
sense.
A
We
can
do
some
stuff
that
will
give
us
some
performance
improvements,
so
we've
got
a
metal
list
here
of
stuff
that
is
nice
to
have,
but
won't
prevent
the
release
of
the
software
and
then
same
thing
goes
for
user
experience.
Improvements
too.
We
want
to
make
the
experience
for
people
who
are
creating
content
on
the
site.
Better.
A
We've
already
made
a
couple
of
significant
improvements:
we've
cleaned
up
the
modules
page,
we've
added
a
drop
down
menu
for
our
administration
bar,
and
I
think
that
we've
already
gotten
leaps
and
bounds
over
drupal
7,
but
there's
a
bunch
of
stuff
that's
going
on
in
drupal
8.
That
is
also
really
good,
that
we
should
take
a
look
at
and
include
the
things
we
want.
A
But
if
we
had
someone
who
was
willing
to
work
on
that
now,
it
would
be
fantastic
if
we
could
release
1.0.0
with
the
rich
text
editor.
So
if
that's
something
that
you're
particularly
passionate
about
pop
up
in
irc
and
talk
to
us
about
it,
we
have
a
bunch
of
ideas.
Look
at
the
github
issue,
queue
there's
an
issue
there
for
it
already
and
yeah,
so
we
could
definitely
use
some
help
there
or
any
of
the
other
user
experience
tasks.
A
Most
of
them
are
fairly
easy
in
terms
of
technical
implementation,
though
difficult
in
terms
of
decisions
that
need
to
be
made
as
to
what
would
actually
make
things
better,
so
feel
free
to
weigh
in
in
those
conversations
too.
Even
if
you
aren't
interested
in
writing
the
code
and
then
we
have
a
new
section
of
tasks
here,
where
I'm
just
kind
of
throwing
in
stuff.
That
needs
a
final
review
before
release
and
it
looks
like
so
far.
We've
got
all
of
our
css
cleanup
as
a
task
in
there.
A
We
also
are
I'm
pretty
soon
going
to
be
able
to
include
the
blocks
and
layouts
review,
which
would
be
great
and
some
of
these
other
things
like
html5,
or
you
know
two
issues
from
away
from
being
done.
So
we'll
get
all
those
into
this
final
review
section.
Then
we
get
definitely
some
people,
you
know
new
eyes
on
the
code
or
anyways
on
that
face
help
us
with
the
final
review
before
release
there.
So
that
would
be
great.
A
The
project
management
committee
has
no
updates
for
the
larger
audience
this
week,
but
if
any
issues
get
escalated
through
our
issue
queue
and
need
to
be
discussed,
the
answers
will
be
discussed
in
this
part
of
the
meeting
in
the
future.
So
nothing
to
report
today,
but
we
will
reserve
this
spot
for
reports
in
the
future
are
a
bunch
of
other
things
that
we're
working
on
too.
A
That
don't
include
the
backdrop
cms
project
code
itself
and
those
include
all
of
the
peripherals
that
we
need
for
supporting
the
community
around
backdrop
cms
one
of
the
things
that
we've
been
working
on
a
lot
lately
lately
is
the
api
website.
We've
got
it
pulling
from
our
code.
We've
got
change
records
created
up
there,
we're
getting
some
help
from
people
just
writing
up
documentation
on
these
change
records.
A
Porting
over
change
records
that
exist
for
dribbling,
making
sure
that
they're
accurate
for
what
we're
doing
in
backdrop,
as
opposed
to
what's
going
on
in
drupal
8
and
then
adding
a
bunch
of
new
ones
for
things
that
we've
changed,
that
drupal
8
hasn't
so
we're
going
to
need
some
help
there.
Someone
with
some
technical
understanding
what's
going
on,
would
be
beneficial,
but
also
someone
with
some
writing
skills.
A
Even
if
you
don't
understand
the
technical
details,
having
someone
you
know,
draft
things
up
initially
would
be
great.
For
someone
who
does
have
technical
skills
to
review
would
be
beneficial,
so
we
could
definitely
use
help
there
from
anyone
who
feels
so
inclined.
A
We
also
have
a
need
for
an
update
server.
So
this
is
when
your
backdrop
website
goes
to
check
to
see
if
it's
up
to
date
right
now,
the
code
pings
drupal,
I
think,
which
is
not
gonna
work
long
term.
We're
gonna
need
to
build
our
own
update
server.
So
that
backdrop
can
ping
backdrops,
update
server
and
find
out
if
it's
up-
and
we
have
some
ideas
about
things
that
we
would
like
to
track-
something.
A
For
example,
it
was
really
hard
to
remove
things
from
core
and
drupal,
because
we
didn't
have
any
statistics
on
which
core
modules
were
actually
being
used.
So
it'd
be
good
when
we
built
backdrop
server
to
include
that,
so
we
get
some
statistics
on
you
know
are
people
actually
using
our
new
admin
bar
module
or
not,
and
that
way
it
will
help
us
gauge
going
forward
how
valuable
the
things
that
we've
done
are
and
what
you
know
holes
need
to
be
met.
A
A
Other
thing
we
need
is
a
github
service,
so
since
all
of
our
contrib
code
is
going
to
be
hosted
on
github,
we're
going
to
need
a
nice
easy
way
for
people
to
search
and
find
things,
and
we
want
to
do
that
from
the
backdrop
cms.org
primary
website.
In
order
to
do
that,
it's
going
to
need
a
way
to
find
backdrop
specific
projects
on
github,
and
you
do
that
by
providing
a
service
on
github
that
allow
people
to
register
modules
and
themes
and
layouts.
A
As
specifically
for
backdrop,
and
so
we
have
some
ideas
about
how
to
do
that
as
well,
and
I
know
that
we've
had
a
couple
people
who
are
interested
in
working
on
it.
If
you're
still
interested
in
working
on
it,
give
us
ping,
we
can
figure
out
how
to
help
get
that
going
forward
too
and
then
obviously
the
backdrop
cms.org
primary
website.
It's
going
to
get
a
design
rebrand
before
we
release,
hopefully
before
release,
maybe
shortly
after,
depending
on
how
busy
we
are
and
we'd,
also
like
to
add
a
couple
of
new
sections.
A
Obviously,
we're
going
to
need
to
build
the
pages
that
allow
people
to
search
for
modules
and
themes,
we're
also
we
want
to
add
a
showcase
section.
We
talked
about
adding
you
know
a
job
section,
all
of
the
stuff
that
the
drupal
community
has
as
part
of
its
stuff.
We
want
to
try
and
recreate
for
backdrop,
but,
of
course,
we'll
try
and
engage
the
priorities
there
if
there
aren't
any
backdrop
jobs,
yet
it's
silly
on
a
backdrop,
job
site,
but
long
term.
A
We
do
have
plans
for
how
to
do
some
of
these
things.
So,
if
you're
interested
in
working
on
that
either
the
retheme
we're
getting
designs
done
already,
that
would
be
great
or
adding
some
of
these
new
features.
We
could
use
help
with
that
as
well.
A
So,
in
terms
of
when
all
of
this
work
is
getting
done,
we
do
sprint
every
thursday
afternoon
after
this
meeting.
So
if
you
want
to
meet
us
in
irc,
there's
things
we
can
help
you
with
ping
us
by
name,
if
you're
trying
to
get
us
our
attention,
because
sometimes
we've
got
our
noses
in
the
code
and
don't
notice
just
general
chatter.
A
In
there
and
yeah
we
can
help
give
you
things
to
do
or
help
you
with
things
you're
working
on
answer,
questions
about
the
project,
anything
like
that
and
then
we
do
have
one
in
real
life
sprint
coming
up
at
bad
camp.
We're
gonna,
do
it
on
sunday
november,
9th
in
the
coder
lounge
area.
So
if
you'd
like
to
meet
us
in
person,
ask
us
some
hard
questions
face
to
face
we're.
A
Definitely
up
for
that
and
we'll
be
trying
to
get
some
work
done
on
getting
the
project
out
the
door,
probably
by
that
point.
So
that
would
be
really
fun
in
terms
of
what's
coming
up
nate
and
I
will
be
attending
the
pacific
northwest
drupal
summit
to
talk
to
that
crowd
about
what
backdrop
is
why
it
exists
and
hopefully
have
a
little
demo
that'll
go
over
amazingly
we're
hoping
which
will
be
fun
and
then
the
following
week.
A
We're
going
to
be
speaking
at
the
html5
developer
conference,
which
is
here
in
san
francisco,
it'll,
be
our
first
chance
to
demo
the
software
to
a
group
of
people
who
don't
necessarily
know
what
drupal
is,
which
I
think
is
going
to
be
great.
We're
going
to
be
kind
of
sticking
our
toe
in
the
larger
world
of
html
people
and
showing
them
what
we
have
and
then
we've
got
bad
camp,
which
is
november
6th
through
9th,
which
of
course,
we'll
we'll
be
there.
A
Although
I'll
be
pretty
busy
and
it'll
be
probably
sprinting,
we'll
definitely
be
around
we'll
try
and
give
a
talk,
all
that
good
stuff,
and
then
we're
going
to
be
going
to
symphonycon
in
madrid,
which
is
november
27th,
which
is
super
exciting
to
go
talk
to
another
open
source
community
that
is
tightly
tied
to
drupal
for
a
bunch
of
other
reasons
and
talk
to
them
about.
Basically,
the
message
being
better
code
isn't
necessarily
better
for
the
community,
and
this
is
a
community
that
also
loves
better
code.
A
So
it'll
be
interesting
to
see
how
our
message
is
received
there
if
they're
getting
the
same
kind
of
business
pressures
in
the
real
world
that
we're
getting
that
spark
to
the
creation
of
bacteria.
So
I'm
super
excited
about
that.
I'm
super
excited
talking
people
at
html,
developer,
5,
conference
kind
of
branching
out
from
our
typical
group
of
drupal
people
and
speaking
to
the
larger
world
about
backdrop
which
I
think
will
be
great
and
there's
a
whole
bunch
of
drupal
events
coming
up
as
well.
A
There's
a
drupalcon
in
latin
america
in
february,
there's
one
in
los
angeles
in
may,
there's
one
in
india
shortly
thereafter
and
I
was
specifically
asked
by
one
of
the
drupalcon
latin
america
organizers
to
submit
a
session
on
backdrop.
So
I
did.
But
then
it
got
escalated
to
the
larger
group
to
see
how
they
felt
about
that
and
they
decided
that
it
was
not
appropriate
as
a
session.
But
then
the
guy
begged
me
to
come
and
do
it
as
a
boss.
He's
like
you've
got
to
come.
A
You've
got
to
talk
about
it
and
I
am
kind
of
conflicted
about
doing
that.
Just
because
when
we
first
forked,
we
had
some
heavy
conversations
with
people
about
how
that
would
go
down,
but
I
think
it
would
be
good
if
we
could
get
there
anyway
and
just
chat
with
people
about
backdrop
and
how
it's
going
and
what
it
means,
especially
in
a
part
of
the
world
where
they
seem
to
be
really
hungry
for
it.
So
that
is
definitely
on
our
agenda
and
we'll
try
and
find
a
way
to
make
that
work
too.
A
So
we've
also
been
asked
to
speak
at
drupalcon,
india.
I
was
contacted
by
one
of
their
organizers
and
they
requested
that
we
do
a
featured
session
on
backdrop
and
I'm
not
sure
how
that's
going
to
go
down
either.
A
But
we
will,
we
will
see
you
know.
Maybe
maybe
the
environment
at
in
the
in
the
drupal
community
will
have
calmed
down
a
little
bit
by
the
time
the
india
conference
rolls
around.
I
know
it's
still
a
little
tense
there
for
the
latin
america
ones
as
being
the
next
con.
A
Again,
we
don't
really
want
to
go
anywhere,
we're
not
wanted,
but
it
seems
like
we're
getting
a
huge
push
from
the
larger
community
to
come
and
speak
about
backdrop,
even
if
they
aren't
necessarily
behind
us.
They
want
to
hear
we
have
to
say,
which
is
a
good
first
step.
I
think
so
it's
pretty
exciting
in
terms
of
what's
coming
up,
and
I
would
say
if
there
are
any
other
camps
or
conferences
that
want
to
hear
about
what
we're
talking
about,
even
if
they
don't
want
us
to.
A
You
know,
come
and
talk
to
their
people,
but
they
want
to
talk
to
us
personally,
I'm
definitely
open
to.
Having
that
conversation,
I've
had
a
couple
of
really
great
phone
conversations
with
you
know
four
random
business
owners
on
the
phone
that
have
a
bunch
of
hard
questions
for
us.
That's
fine,
too
we're
happy
to
talk
about
what
we're
doing
and
why,
obviously
we
feel
very
strongly
about
it.
So
yeah,
I
think
it's
great
nate.
Do
you
want
to
add
anything
to
the
meeting
today.
A
You
know:
we've
been
kind
of
rambling
on
for
a
while
there's
a
lot
of
great
stuff
going
on.
B
Yeah,
I
guess
I
owe
pull
request
reviews
to
a
lot
of
people.
There
are
a
number
of
pull
requests
that
are
outstanding
and
and
I'm
going
to
get
to
them
as
soon
as
possible.
Okay,.
B
Yeah,
that
would
be
handy
because
some
of
the
things
like
we've
got
a
volunteer.
Who's
actually
started
porting
views,
but
I
think
that
it's
lacking
like
an
upgrade
path
and
things
like
that.
So
it's
it's
not
ready
yet,
but
just
addressing
the
feedback-
and
you
know
trying
it
out
would
be
helpful
because
right
now
it
needs
it
needs
more
work,
but
he
needs
to
be
told
that
it
needs
more
work.
A
Too
busy
to
tell
you
what
to
do,
but
you
should
go.
Do
it
okay,
I'll
see?
If
I
can
do
some
of
those
today,
I
think
that
might
be
really
good
use
of
my
time.
I
don't
have
a
lot
of
time
today,
so
I
think
if
I
can
do
pull
request
reviews
and
rather
than
writing
code,
that
would
be
useful
for
you
and
also
easy
for
me
to
manage
so.
B
A
Sounds
great
all
right!
Well,
we
will
see
everyone
on
the
internet
and
same
bad
time
standby
channel
next
thursday.