►
From YouTube: Backdrop CMS Weekly call 9/18
Description
The comprehensive CMS for SMB and NP
A
A
A
This
fall
we're
kind
of
nearing
that
time
now
and
things
are
starting
to
come
together,
which
is
really
exciting,
so,
hopefully
we'll
we'll
have
a
demo
video
up
for
you
pretty
soon
and
then
we'll
just
kind
of
start
cleaning
up
right
before
release
after
we
release
1.0.0
we're
hoping
to
continue
a
regular
schedule
of
releases.
So
every
four
months
after
that
we'll
have
a
minor
version
come
out
so
that
we
can
add
new
features
and
change
bugs
and
all
that
stuff
as
well.
A
In
terms
of
what
we're
working
on
right
now,
we've
got
a
couple
of
things
that
we
consider
release
blockers
like
we
can't
release
1.0.0
without
them
of
those.
The
the
first
and
most
important
is
the
blocks
and
layout
system,
which
I
think
we're
getting
really
really
close
on.
Nate
has
been
doing
a
ton
of
work
on
that
for
the
past
few
weeks.
So
neat,
why
don't
you
give
us
an
update
on
where
we
are
now.
B
B
Since
last
week,
we've
made
some
headway
in
a
couple
areas
like
I'm,
not
sure.
If
we
had
the
upgrade
path
working
last
week
or
not,
but
the
upgrade
path
is
there,
we've
stripped
out
all
of
the
like
layout
type
functionality
out
of
block
module,
so
block
module
is
now
nothing
but
a
custom
block
module.
Basically,
if
you
want
to
create
a
reusable
block,
you
know
that
the
ability
for
block
module
to
create
a
custom
block-
that's
the
only
thing
that
is
left
in
in
block
module.
B
Let's
see,
we
also
stripped
out
all
last
references
to
page
manager,
c
tools
or
panels
and
stripped
down
kind
of
the
plugins
like
we
had
on
our
list
here.
That's
some
of
the
things
we
wanted
to
tackle
was
plugin
conversions.
Those
are
still
valid
and
we
need
to
convert
some
things
like
like.
We
don't
have
field
blocks
yet,
so
you
can
position
like
split
up
a
node
and
position
it
individually
and
we
don't
have
token
handling.
B
So
you
could
use
tokens
inside
of
your
custom
blocks,
but
we
we
can
do
all
of
those
things
architecturally
we're
set
up
for
it
already.
It's
just
that
we've
trimmed
down
what
the
initial
scope
of
the
the
pull
request
is
because
it's
already
massive
to
just
focus
on
replacing
with
plugins
the
functionality
that
is
in
triple
core
right
now
and
that
way,
we'll
we'll
be
able
to
trim
down
like
the
number
of
tests
and
just
gets
the
current
functionality
replaced
with
the
upgrade
pad.
B
So
we're
looking
really
good.
I'm
gonna
make
a
new
video.
I
know
I've
been
saying
that,
but
I'm
really
gonna
make
a
new
video
demonstrating
where
we
are
currently
because
at
this
point,
we're
functionally
complete
like
we're.
Really
we're
really
ready
for
this
thing
to
go
in,
but
we
need
to
make
sure
that
it's
fully
working
and
in
order
to
make
sure
it's
fully
working,
we
need
to
get
more
comprehensive
test
coverage
right
now.
B
So
that's
where
we
are
we're
really
really
really
close.
I
I'm
I'm
confident
we'll
be
done
with
layouts
or
not
done,
but
layouts
will
be
in
core
within
the
next
month
for
sure,
so
I'm
really
excited
about
where
we
are
with
layouts
and
and
from
there
yeah.
Then
we'll
put
our
focus
towards
these
other
remaining
critical
tasks.
A
That's
great,
so
the
next
most
important
thing
that
we're
working
on
is
config
management
and
we
have
a
subsystem
in
core
all
ready
for
saving
our
configuration
to
files
instead
of
the
database,
but
not
all
of
the
systems
and
core
have
been
updated
to
use
that,
and
without
getting
things
like
content
types
and
fields,
actually
storing
their
configuration
and
files.
We
don't
really
have
configuration
management
yet
so
that's
our
next
major
release.
Blocker
is
making
sure
that
we
get
all
of
the
data
storage
for
those
things
saving
to
files.
Instead
of
to
database.
A
We
have
some
systems
converted,
but
obviously
content
types
and
fields
are
really
big
and
really
important.
We
need
to
get
those
converted
over
another
thing:
that's
not
necessarily
a
release
blocker,
but
that
we
would
like
to
have
done
before
release
is
getting
all
of
the
views
in
core
are
also
converted
to
use
views.
We
have
views
the
system
in
core
and
we
have
a
bunch
of
pages
generating
views,
but
we
need
to
kind
of
convert
the
rest
of
it
in
order
for
it
to
be
clean
on
release.
A
So
this
would
include
the
front
page.
The
node
page
needs
to
be
converted.
The
taxonomy
term
listing
page
needs
to
be
converted
the
blocks
in
the
sidebar,
like
the
who's
online
block,
the
recent
content
block
all
of
that
stuff
can
be
converted
to
views
also-
and
it
looks
like
we
already
have
some
people
working
on
it
since
last
week,
which
is
great.
We've
got
a
new
full
request
to
convert
things
over.
We
need
more
of
that
too.
A
More
administration
pages,
that's
what
the
first
one
was
is
for
the
admin
people
page.
We
need
to
get
more.
We
need
the
the
admin
content
listing
all
of
that
stuff
as
well,
and
some
of
those
pages
are
going
to
be
a
little
bit
trickier
because
they
need
new
views.
Bulk
operation
tasks
added
as
well
so
getting
those
in
would
also
be
great.
A
Other
things
that
we're
working
on
that
are
not
release
blockers,
but
that
are
super
important
for
us
is
making
sure
that
we
keep
up
with
what
drupal's
doing,
and
that
includes
all
of
the
security
fixes
that
have
gone
into
drupal
7..
We
need
to
apply
those
same
fixes
to
backdrop,
so
we've
got
three
of
those
that
are
left
that
we
need
to
work
on
and
I
started
creating
in
the
issue
a
set
of
steps
on
how
to
do
that.
A
A
So
if
we
want
to
get
the
same
solutions,
we
need
to
follow
the
same
process
there,
and
then
we
also
have
a
bunch
of
changes
that
have
made
between
728
and
731
that
need
to
get
in
the
the
other
issue
that
we
talked
about
last
week.
We
closed
yes,
last
week
after
the
meeting
in
the
sprint,
which
was
great
so
there's
just
one
issue
left
with
it,
looks
like
a
handful,
maybe
10
or
11
patches
that
need
to
be
applied.
A
A
A
We
also
have
a
couple
of
other
minor
projects
that
we're
working
on
and
we
want
to
get
done
before
we
release
backdrop.
The
first
one
is
continuing
to
separate
backdrops
identity
from
drupals,
and
we've
already
got
a
couple
of
major
things
in
the
do
that,
like
we
removed
the
word
drupal
everywhere
from
backdrop,
we
changed
the
installer.
So
when
you're
installing
it
looks
like
you're
installing
something
different
at
least
a
little
bit
different,
not
completely
different.
But
the
next
big
thing
on
our
list
is
rebranding.
A
The
administration
theme
and
we've
been
working
with
julia
on
getting
kind
of
a
new
style
guide
for
admin
theme
down,
and
I
know
she's
done
a
bunch
of
work
on
that
and
then
she
got
pulled
away
on
other
tasks.
We
have
a
meeting
with
her
later
today
to
figure
out
where
she
is
on
that
and
if
we
can
kind
of
take
over
her
work
or
if
she
wants
to
continue
what
kind
of
time
she's
going
to
have
what
we
can
do
to
help
so
that
she
can
make
more
progress
and
not
have
to
worry
about.
A
Like
I,
I
moved
the
git
repository
out
from
underneath
her,
we
hope
to
kind
of
if
we
can
get
her
back
up
to
speed
on
that.
That
would
be
really
great
just
so
that
we
can
get
some
idea
of
what
our
admin
theme
is
supposed
to
look
like,
and
if
we
can
get
some
pointers
from
her
on
style.
We
can
then
start
writing
the
code
around
that
too.
A
A
Obviously,
drupal
8
is
going
to
be
very
attractive
to
people,
because
they're
going
to
be
excited
to
use
twig,
there's
a
lot
of
changes
that
went
into
drupal
8
that
don't
actually
have
anything
to
do
with
the
conversions
to
twig,
and
we
need
to
get
most
of
that
stuff
into
backdrop
as
well.
So
we've
started
on
that.
A
That's
not
something
like
if
your
logo
contains
the
name
of
your
site,
you
don't
need
both
your
site
name
and
your
logo.
If
you
change
your
theme,
that's
going
to
be
the
same
like,
regardless
of
which
theme
you're
using
your
your
logo
is
not
tied
to
your
theme.
Your
site
name
is
now
tied
to
your
theme.
It's
part
of
your
site,
and
so
what
we've
done
is
we've
moved
these
settings
into
the
site,
information
section
where
you
define
your
site
name.
You
can
also
upload
your
logo,
so
it's
just
kind
of
some
stuff
here.
A
A
We
already
have
settings
for
what
information
do
you
want
to
show
about
your
node
or
what
information
you
want
to
show
about
your
comment
and
they're
in
different
places,
so
we
redistributed
all
of
these
things
that
used
to
be
theme
settings
into
where
they
lived,
and
now
that
we
have
something
like
a
header
block
that
shows
your
site
name
and
your
logo.
We
move
those
settings
into
the
header
block
and
and
in
the
process
of
re-evaluating
each
one
of
these
theme
settings
we
realized
that
there's
really
nothing
left.
A
A
We
moved
to
where
it
should
be
like
where
it's
with
the
other
settings
that
it's
like,
and
I
think
this
is
going
to
be
a
huge
improvement
for
what
front
enders
have
to
worry
about
in
terms
of
how
much
logic
they
put
in
their
themes
like
you,
don't
have
to
account
for
these
random
settings.
That
drupal
says
are
variables
and
you
need
to
worry
about.
A
What's
the
difference
between
a
global
theme
setting
and
a
specific
theme
setting
for
new
users
was
a
little
yucky,
so
what
we've
done
is
we've
created
a
settings
page
for
each
individual
theme,
gotten
rid
of
the
global
one
and
moved
all
the
settings
to
their
new
homes,
which
I
think
is
going
to
make
a
lot
more
sense
to
people
coming
in
so
yeah
we've
got
an
issue.
I've
got
actually
two
full
requests
open
for
that
one.
A
I've
got
one,
that's
passing
test
the
one
that's
not,
but
I've
got
to
move
some
of
the
stuff
to
from
the
one.
That's
not
passing
tests
into
the
one
that
is
or
maybe
create
some
more
follow-up
pull
requests,
because
the
the
one
that's
working
is
not
complete,
as
it
is
now
so
we'll
get
that
figured
out
and
there's
also
some
some
stuff
in
that
issue
that
converts
those
theme
settings
to
cmi
and
that's
where
things
are
breaking.
A
So
I
might
split
that
out
into
another
issue
as
well,
so
we'll
figure
out
how
to
get
that
resolved
and
we'll
get
that
in
here.
Hopefully,
today,
okay,
so
other
things
we're
working
on
that
aren't
related
to
the
theme
system,
general
user
experience
improvements,
we've
made
a
handful
of
terminology
updates
or
changes
in
the
user
interface
to
make
things,
make
more
sense
to
people.
A
There's
also
some
issues
about
making
sure
that
we
say
edit
when
we
mean
edit
and
configure
when
we
mean
configure
just
little
things
like
that,
that
we
should
just
be
able
to
go
in
and
hammer
out
pretty
quickly
and
then
we
also
want
to
add
a
rich
text
editor
into
court.
But
that
is
not
a
release
blocker.
We
think
we
can
do
that
in
backdrop,
one
or
backdrop
two
or
1.1
or
1.2,
because
it
doesn't
require
an
api
change,
but
it
would
be
great
if
we
could
get
it
in
in
the
initial
release.
A
And
then
I
also
created
a
new
section
in
the
agenda
for
kind
of
final
review
issues
like
there's
going
to
be
a
bunch
of
systems
where
we're
like
yeah
we're
done,
but
just
because
we've
gone
through
all
of
the
issues
that
we
currently
have
in
eq
doesn't
mean
we're
actually
done,
and
we
should
probably
just
have
someone
like
take
a
step
back
and
take
a
high
look
at
everything
and
one
of
those
things
that
that
we
finished
all
of
our
sub
issues
on
cleaning
up
css.
Last
week
it
created
a
new
issue.
A
That's
like
let's
just
look
at
all
the
css
and
make
sure
the
files
are
all
in
the
correct
directories
and
that
there
aren't
any
you
know:
drupal
8
style
identifiers,
so
we're
using
backdrop,
style,
identifiers
and
everything
just
looks
kind
of
kosher.
If
there's
anything
weird
going
on
in
there,
we
could
just
kind
of
do
a
high
level
overview
to
see
if
anything
stands
out
now
that
should
be
pretty
straightforward.
I'm
assuming
there
won't
be
anything,
but
we
won't
know
until
we
look.
A
There's
also
a
section
in
this
weekly
meeting
for
updates
from
the
pmc
we
haven't
had
any
crazy,
like
mind-altering
decisions
that
we
needed
to
talk
about
in
the
last
week.
So
there
aren't
any
updates
here
today
for
this.
If
anyone
has
anything
that
they
think
is
important,
that
we
should
discuss
about
the
future
of
the
project,
you
can
create
an
issue
and
we
can
talk
about
it
and
then,
in
this
meeting,
we'll
give
you
an
update
as
to
what
we
decided
about
it.
A
So
use
the
issue
queue
and
we'll
figure
out
what
needs
to
be
done
about
it.
There's
a
bunch
of
other
stuff
that
we're
working
on
that
is
not
related
to
backdrops
internal
code
and
those
are
usually
websites
and
web
services
around
having
backdrop
as
the
cms.
The
first
one
is
our
api
website,
which
is
coming
along
really
well,
since
last
week
we
have
well,
we
have
the
api
website
up.
It
actually
pulls
from
our
api,
which
is
great.
It
needs
a
theme
which
we'll
work
on
we're.
A
Getting
a
new
theme
for
our
main
site
and
we'll
probably
use
some
spin
off
of
that
one
for
the
api
site.
We
added
change
records.
Luke
set
up
a
content
type
on
there
to
put
in
change
records,
which
is
great
and
then,
since
last
week,
we've
started
talking
to
ron
about
going
through
and
documenting
some
of
our
changes
and
there's
a
lot
of
stuff.
A
That's
happened
in
the
early
phase
of
your
blade
development
before
we
forked,
where
they
already
have
change
records,
and
we
just
need
to
port
those
change
records
over
into
backdrops
api
and
make
sure
that
they're
still
relevant,
like
that.
We
haven't
changed
those
things
since
the
change
record
went.
B
A
And
if
there
are
we'll
update,
the
change
record
and
ron
is
very
willing
to
help
test
the
system
that
luke
built,
which
is
great
by
entering
all
of
this
content
reading
over
the
issues
and
making
sure
that
our
documentation
there
is
up
to
great
up
to
date.
So
I
think
it's
going
to
be
really
great
to
have
that
start.
Coming
together
as
well.
A
A
Other
things
that
we're
working
on
include
creating
an
update
server.
So
this
is
so
that
your
backdrop
website
can
tell
you
of
its
modules
or
themes
or
core
is
out
of
date,
so
we
need
to
find
a
way
to
set
that
up
place
to
set
it
up
and
have
somebody
set
it
up,
which
would
be
great.
Obviously
our
priority
is
getting
the
software
out,
but
if
we
want
to
have
people
running
the
software,
we're
going
to
need
to
have
all
of
these
services
that
run
around
it
as
well.
A
So
after
we
get
1.0.0
out
we're
going
to
be
changing
gears
to
focus
on
some
of
this
other
stuff
too,
unless
we
can
get
anyone
to
start
working
on
this
sooner
for
us,
which
would
be
really
great,
another
thing
we're
going
to
need
is
an
official
github
service.
So
anyone
creating
a
modular
theme
for
backdrop
can
register
that
modular
theme
on
github
as
being
a
backdrop
project
and
then
cms.org.
The
primary
website
can
scrape
those
modules
and
themes
off
of
github
and
build
a
comprehensive
listing
of
what's
available.
A
I
know
we
talked
about
this
a
little
bit
in
terms
of
how
we're
going
to
do
it,
where
we're
going
to
put
it
what
language
it
needs
to
be
in
written
written
in,
but
I
don't
think
we
have
anyone
working
on
it
right
now.
So
if
we
we
wanted
someone
to
take
that
on,
we
can
try
and
figure
out
how
that
should
work
and
what
we
need
to
do
to
get
it
up.
A
Obviously,
getting
backdrop
core
out
has
to
happen
before
we
can
get
backdrop
can
trip
out,
but
we
do
have
a
couple
of
projects
that
we've
removed
from
core
that
we
could
already
use
to
test
that
system.
So
if
we
wanted
to
put
like
xml
or
pc
or
something
like
that
into
the
backdrop,
control
repository
and
hook
it
up
as
a
backdrop
project,
we
do
at
least
have
some
things.
We
can
figure
out
how
to
how
to
get
that
working
with.
A
So
that's
good
and
then
other
things
that
we're
working
on
primary
website.
I
mentioned
earlier
we're
getting
a
new
theme.
We
recently
got
a
new
mascot
which
is
drop,
the
dragon
dragon
drop
and
we're
working
on
getting
a
picture
of
a
dragon.
We've
hired
an
illustrator
to
make
a
couple
of
pictures
of
us
of
dragons.
We've
figured
out
what
we
like
what
we
don't
like,
and
I
think
we're
really
close
we're
on
our
third
round
of
dragon
revisions
and
we've
got
something
that's
pretty
cute.
A
I
think
we're
probably
gonna
do
one
more
round
and
then
we're
gonna
post
the
image
up
and
everyone
can
kind
of
take
a
look
at
it.
We're
hoping
to
somehow
integrate
our
awesome
dragon
and
our
new
designs
for
our
website.
So
dragon
first
and
we'll
get
like
stickers
and
stuff
t-shirts.
I
don't
know,
and
then
after
we
get
the
dragon
we'll
do
the
design
for
the
website
and
then
we're
going
to
try
and
coincide
or
retheme
with
the
primary
website.
A
The
same
time
as
we
launch
backdrop
1.0.0
and
then
we're
going
to
do
a
port
of
backdrop
cms.org
to
backdrop
and
shortly
thereafter,
including
what
it
was
like
to
port
any
modules.
Or
you
know
just
not
publicly
making
that
process
available
to
people
who
are
considering
about
porting
their
own
sites
from
seven
to
backdrop,
which
I
think
will
be
great,
let's
see
so
every
thursday
after
this
meeting
we
have
a
sprint.
Sometimes
it
gets
quiet
in
irc
because
we're
all
working
on
pull
requests
or
code.
A
So
if
anyone
is
watching
this
and
wants
to
join
in
the
sprint,
you
can
ping
nader,
I
directly
in
there.
If
you
want
our
attention,
if
you
just
kind
of
put
in
a
message
that
goes
hey,
are
you
guys
renting?
We
might
not
see
it
because
we
might
not
be
looking
at
irc.
So
I
know
that
happened
last
week.
We're
here
we're
sprinting
we're
working,
but
you
might
need
to
specifically
get
us
get
our
attention.
A
If
you
have
a
question
so
feel
free
to
join
in
there
if
you'd
like
and-
and
we
can
help
you
find
a
task
or
answer
questions
or
whatever
you
need
and
we're
hoping
to
do,
some
in
real
life
sprints
as
well
as
these
virtual
ones.
We
do
every
thursday.
So
far,
the
only
one
we
have
scheduled
is
for
bad
camp.
A
Bad
camp
is
november
6th
through
9th
and
there
is
a
four
day
core
development
sprint
for
drupal
8,
which
will
start
thursday
through
sunday
we're
going
to
try
and
steal
one
table
in
that
sprint
room
at
least
one
table,
but
starting
with
one
table
to
work
on
backdrop
stuff.
So
if
you
are
coming
to
bad
camp
and
you're
really
interested
in
backdrop-
and
you
want
to
talk
to
us
about
it,
you
want
to
work
on
it
with
us.
We
would
love
the
help
and
I
think
it
might
be
good,
also
to
kind
of
see.
A
What's
going
on
in
drupal
8,
like
you'll,
be
in
the
middle
of
everything
you
can
watch
sessions
on
both
of
them.
You
can
get
your
perspective
as
to
you
know
who
you
want
to
be
in
the
future.
What
you
want
to
work
with,
I
know
a
lot
of
people
are
going
to
be
interested
in
both.
So
I
think
that
would
be
good
to
you
know.
Let
people
get
their
hands
on
the
code
too
and
then
yeah
other
stuff.
A
We've
got
coming
up
the
html
developer
five
conference,
I
thought
was
september,
but
it
turns
out.
It's
actually
october
22nd
through
24th
and
the
pacific.
Northwest
drupal
summit
is
the
week
before
17th
through
19th
we've
submitted
sessions
at
pacific
west
north
northwest
google,
something
I'm
not
sure
if
it's
been
accepted
yet
or
if
it
will
be
accepted,
but
we'll
probably
go.
A
If
it
is,
we
might
go
even
if
it's
not
just
because
we've
been
asked
to
go
and
talk
about
backdrop
there,
even
if
it's
not
in
a
session
or
talk,
people
in
the
hallways
might
be
good
and
then
html5
developer
conference
is
the
first
chance
that
we
get
to
pitch
backdrop
to
people
who
aren't
dribble
people,
which
I
think
is
important.
So
we
can
get
kind
of
a
feel
from
the
general
general
population
on
you
know.
How
do
you
feel
about
another
php
open
source
cms?
Would
it
solve
your
needs?
A
So
if
someone
asks
us
to
talk
about
backdrop,
we
will
submit
a
session.
Otherwise
we
won't
out
of
respect
for
the
drupal
project
and
early
in
our
forking
process.
We
were
kind
of
challenged
not
to
so.
I
think
we're
trying
to
respect
that
decision
as
well.
Like
you
know,
there
aren't
a
lot
of
wordpress
sessions
at
drupal
cons,
so
in
the
same
vein
there
there
won't
be
backdrop
unless
the
drupal
community
specifically
requests
it.
So
that's
why
we
are
with
those
right
now
in
terms
of
our
upcoming
schedule.
A
I
think
the
most
important
thing
is
just
that
you
know
backdrop
is
right:
around
the
corner:
we've
gotta
figure
out
how
to
tie
up
all
of
our
loosens
and
get
this
thing
out.
I
think
it's
looking
really
amazing.
I'm
really
excited
about
blocks
and
layouts.
I'm
really
excited
about
being
able
to
use
cmi
like
soon
so
yeah.
We
would
love
any
help
if
anyone
has
any
time
or
availability
in
the
near
future
to
work
on
the
code.
A
That
would
be
great,
but
of
course
the
the
support
we're
getting
right
now
is
also
really
great,
too
we're
getting
a
whole
bunch
of
people
saying
they
want
it.
We're
getting
business
owners
talking
about.
You
know
how
to
sell
it
to
their
clients,
it's
starting
to
feel
like
it's
really
coming
together.
So
thank
you,
everyone
for
all
the
emails
and
and
hats
on
the
back
at
camps
and
conferences
and
stuff
too
so
good
deal.
Is
there
anyone
who
has
any
questions
or
comments?
A
B
We
actually
have
something
well,
okay,
so,
first
of
all,
no,
unfortunately
can't
make
it
so
that
pantheon
spins
up
an
individual
branch,
because
pantheon
they're,
what
they're
hoping
to
do
is
get
people
started
on
an
account
and
then
eventually
they'll
just
convert
that
to
an
actual
production
site.
I
don't
think
they
want
to
use
it
for
for
testing
purposes
where
people
would
end
up
with
a
whole
bunch
of
different
sandboxes.
B
B
B
C
B
A
Those
are
specifically
pulling
from
the
master
branch
right
now,
okay,
so
it
should
be
like
latest
head
and
once
we
have
a
release,
those
will
specifically
pull
from
the
latest
release.
But
if
you're
a
developer-
and
you
know
what
you're
doing
you
can
get
to
the
command
line,
you
can
obviously
change
branches
or
you
could
change
to
you
know.
B
A
C
Yes,
so
the
item
so
with
the
wordpress
support,
they
added
the
ability
to
spin
those
up,
even
though
it's
not
listed.
If
you
start
a
new
pantheon
instance
from
scratch,
you
weren't
seeing
the
wordpress
listed
in
the
list
of
options
with
open
atrium
and
the
city
starter
kit,
those
types
of
things,
but
if
you
knew
the
url
to
go
to,
you
could
go
there
as
any
type
of
user
and
request
that
specific
type
of
site.
So
that
is
an
option.
Once
the
layout
pull
request
is
merged
back
into
your
master.
A
A
Yeah
and
we
have
that
same
link
for
backdrop
right
now,
and
we
have
one
pull
request
in
our
queue
where
we
need
to
write
an
automated
test
in
order
to
get
that
pull
request
committed
and
once
we
get
that
in
then
what
pantheon
will
be
able
to
publish
that
page
that
they
gave
us
it's
exactly
the
same
thing.
It's
a
landing
page.
It's
like
try
backdrop.
A
It
works
exactly
like
wordpress
hdm
actually
has
one
of
those
pages
too,
even
though
they
are
now
also
in
the
installer
process,
and
it's
just
kind
of
a
an
easy
way
to
get
people
to
try
it
and
that's
the
link
that
we're
going
to
put
on
our
home
page.
This
is
try
a
demo
now,
so
we
can
get
that
one
test
written
which
I
think
matt
asked
like.
How
do
I
even
write
a
test
for
this,
and
then
he
answered
with
an
idea
of
how
to
do
it.
A
A
Probably
I
don't
know
how
luke
is
working
on
the
port,
he
might
be
doing
it
locally
until
he
gets
it
close
enough
that
it
gets
committed
and
pushed
up
to
github,
but
it
will
eventually
be
a
github
project
because
we
need
to
pull
it
in
in
project
module
or
yeah
either
that
it's
not
gonna
end
up
in
our
repository.
Is
it
neat?
Is
that
no.
B
There's
a
group
on
github
for
backdrop
dash
contrib,
but
nothing
is
in
it,
but
that's
where
examples
will
will
eventually
pop
up
and
we're
going
to
move
the
xml
rpc
port
into
there
as
well,
because
right
now,
it's
just
in
somebody's
personal
repository
and
we'd,
like
any
of
the
modules
that
we've
removed
from
from
backdrop
core
will
probably
end
up.
In
that
backdrop,
contrib
repository
at
some
point
in
time
like.
A
Retire,
retire
is
better.
I
would
like
to
see
open
id
retire
and
I
think
that
if
we
leave
those
kind
of
more
in
the
public
domain,
where
it's
like
hey,
if
you
want
open
id
here's
a
step
module
like
make
it
better
than
core
made
it,
I
think
that's
kind
of
the
what
we
want
to
encourage
right.
We
don't
want
to
say
this
is
owned
by
backdrop
whatever
and-
and
it
can't
move
that
fast
if
someone
wants
to
take
it
over
and
do
whatever
they
want
with
and
turn
into
something
much
better.
A
A
Okay,
okay
yeah.
We
should
check
in
with
gore
and
see
if
he
needs
anything
else
from
us
too.
Nate
so
gore
runs
a
hosting
company,
I
think
in
in
ukraine,
and
so
he
reached
out
to
us
and
was
like.
I
really
like
this
backdrop
stuff.
How
can
I
help
like
by
the
way
run
a
hosting
company?
I've
got
a
bunch
of
servers
and
we're
like
servers,
because
we
really
like
this
idea
of
getting
a
test
instance
for
every
pull
request
so
that
we
can.
A
You
know
let
people
test
pull
requests
before
they
get
committed
and
we
showed
him
a
a
working
model
of
how
that
works
from
was
that
on
github
to
that
thing,
when
he
we
sent
him
some
example
of
how
it's
been
done
before
and
he
was
like.
Yes,
I
can
totally
do
this
for
you.
So
that's
what
he's
building
for
us
and
as
of
the
last
check-
and
he
was
doing
really
well
with
it,
so
it
would
be
great
to
to
give
that
a
try
and
see
if
we
can
get
it
up
too.