►
From YouTube: Backdrop weekly 1/8
Description
Backdrop CMS weekly meeting to check in on current priorities.
A
Right,
it
is
Thursday
Jan
right
eight,
so
this
is
our
second
weekly
status
meeting
of
2015
and
we
are
super
excited
the
kids
backdrop.
Cms
will
be
related
released
on
january
fifteenth,
which
is
a
week
from
today,
based
on
our
past
history
of
release,
dates
it'll,
probably
be
around
midnight
California
time
next
week
and
we've
got
a
handful
of
issues
that
we'd
like
to
get
done.
Nothing,
that's
a
really
splock
er.
Since
last
week
we've
made
a
bunch
of
progress,
so
we're
going
to
just
talk
about
that.
A
Today
we
have
a
section
at
the
top
of
this
meeting
for
updates
from
the
PMC.
This
is,
if
any
issues
run
into
problems
and
need
to
have
conflict
resolution
will
talk
about
it
as
the
PMC
and
then
we'll
make
an
announcement
in
this
part
of
the
meaning.
To
the
more
general
backdrop
public,
we
haven't
had
any
problems
like
that
recently.
We
also
done
a
very
big
pnc,
so
we're
working
on
trying
to
get
the
product
out
the
door
and
then
try
and
get
some
more
people
to
flush
out
our
community
here.
A
First
things:
first,
let's
work
talk
about
this
product
with
the
release
next
week,
we're
trying
to
figure
out
how
we're
going
to
deal
with
dealing
with
pull
requests,
two
different
versions.
So
what
we're
going
to
do
is
we're
going
to
create
backdrop,
1
point
0,
point
0
and
we're
going
to
create
two
other
branches
that
were
going
to
be
doing
develop
on
development.
A
One
point
0
point
X,
which
is
where
we're
putting
any
bug
fixes
that
need
to
come
out
right
away
and
then
we're
going
to
create
a
or
leave
the
1x
branches
where
any
of
the
new
features
are
going
to
go
so,
depending
on
what
it
is.
You're
working
on
you're
going
to
do
file
your
poll
request
against
a
different
branch,
we're
going
to
try
and
create
some
documentation.
A
That'll
make
it
a
little
bit
clearer,
which
branch
your
paw
request
should
be
against,
and
one
day
when
we
get
some
automation
set
up
for
github
will
probably
try
and
automatically
closed
for
requests
that
are
filed
against
the
wrong
branch.
With
a
friendly
message
thing,
you
need
to
file
a
pull
request
against
another
branch
and
maybe
some
instructions
on
how
to
quickly
move
the
chain
chief
made
from
one
branch
to
the
other.
The
again
so
we'll
see
we
know
right
now
it's
going
to
be
a
little
yucky.
A
Just
because
we're
about
to
start
this,
we
haven't
ended
yet,
but
we'll
get
that
process
cleaned
up
a
little
bit
in
the
future
about
extra
releases.
We
decided
last
week
on
our
release.
Schedule
we're
going
to
release
backdrop
1.1
on
May
fifteenth,
the
backdrop
1.2
on
September
15th
in
Bactra
1.3
on
january
fifteenth.
So
far
we
have
a
list
of
features
we
wanted
1.1,
but
1.2
and
1.3
are
still
kind
of
up
in
the
air.
Depending
on
how
fast
we
can
get
our
first
set
of
features
into
1.1.
A
So
we'll
have
a
official
announcement
from
what
comes
in
each
branch
when
we
start
working
on
it
and
that'll
be
kind
of
where
we're
directing
most
of
our
focus
for
the
next
release.
So
in
terms
of
longer
term
than
this
first
year
january,
fifteenth
2016
we're
going
to
reevaluate
the
release
schedule.
We
did
this
first
year
this
first
year
we're
going
to
do
one
released
every
four
months,
depending
on
our
momentum,
the
number
of
core
committers.
How
fast
things
are
going.
We
might
start
releasing
every
three
months
in
2016.
A
We
might
also
reevaluate
how
backdrop
one
has
done
and
see
if
we
want
to
release
a
backdrop
to
early
next
year,
I
to
see
if
we
have
any
major
problems
or
any
features
that
need
to
get
in
or
something
that
might
require
an
API
change.
So
we're
going
to
kind
of
take
a
look
at
how
the
project
is
progressing
as
well,
originally
anticipated
a
two-year
major
uli
cycle,
but
we'll
reevaluate
the
end
of
backdrop,
one
and
see
how
that's
going
based
on
all
the
activity.
A
A
They
implemented
a
fix
that
included
adding
a
particular
token
to
the
end
of
your
request
and
if
turbo
got
the
token
and
know
that
the
request
came
from
triple
and
was
valid,
generate
the
image,
and
we
didn't
like
that
solution,
because
it
ended
up
breaking
a
bunch
of
sites
that
had
inserted
images
into
content
and
had
those
requests
hard-coded
without
the
token
on
them.
So
in
backdrop,
what
we've
done
is
we've
implemented
a
different
solution.
A
We
go
it's
actually
issue
358
and
where
this
past
week,
Nate
went
and
read
through
all
of
the
previous
suggestions
that
were
made
on
drupal.org
issue
and
one
he
thought
he
liked,
and
we
adapted
that
for
backdrop.
So
we
have
a
solution
that
will
solve
the
problem
for
most
use
cases
and
hopefully
not
break
any
kinship
projects
or
sites
in
Drupal
7
that
have
their
images
inside
and
content.
A
A
Two
of
them
have
been
committed
since
last
week,
which
is
great,
so
we've
got
plenty
of
those
fixes
and
I've
got
two
of
them
that
need
work,
that
I'll
work
on
today
and
then
I
think
I
only
need
to
create
one
more
there's
like
12
remaining
patches
that
haven't
yet
been
applied,
and
our
Nana
for
requests.
I'll
get
that
done
today
and
this
I
think
as
soon
as
we
get
this
issue
in,
we
have
a
bunch
of
other
stuff.
A
So
we
have
been
thinking
about
it.
This
past
week,
we've
created
a
bunch
of
other
infrastructure
that
we
needed
to
support
our
security
classes.
In
fact,
up
we
have
set
of
a
new
page
on
the
back
to
our
primary
website
that
talks
about
how
security
issues
should
be
reported,
that
we've
got
a
security
email
address.
Now
that
you
can
email
us
reports
to,
and
we
have
an
RSS
feeds
hope
you
want
to
subscribe
to
security
issues
that
might
come
out
for
backdrop,
and
you
can
do
that
on
our
website
as
well.
A
Obviously,
right
now
there
aren't
any
yet
we
haven't
really
see
it,
but
we
didn't
want
to
make
sure
we
had
all
this
in
place
to
make
sure
that
everyone
would
stay
secure,
a
positional
release.
So
that's
some
kind
of
big
things
that
we
needed
to
take
care
of,
and
we
were
able
to
do.
In
the
last
week
we
had
some
great
feedback
from
suggestions
from
David
David
R
opportunity
planted
all
of
them
since
then
so
kudos
to
need
for
presenting
love
that
up.
A
B
A
All
require
obviously
significant
testing
to
make
sure
that
the
bugs
are
actually
fixed
and
that
they
aren't
causing
any
other
books
since
we're
so
close
to
release.
We
don't
risk
breaking
a
bunch
of
stuff,
but
we
are
pretty
close
on
that
as
well,
and
then
bug
fixes
can
also
go
into
point
releases.
So
if
we
don't
get
all
bug,
fixes
done,
I
mean
there's.
A
Obviously
thousands
of
bugs
in
Drupal
we've
inherited
most
of
those
bugs,
in
fact
up
we're
not
going
to
get
all
from
them,
but
we
will
try
and
get
them
done
iteratively,
so
they
don't
need
to
hold
up
the
release
the
world
really
summit.
As
soon
as
we
get
them
fixed.
We
have
a
handful
of
blocks
and
layouts
follow-up
issues.
This
is
kind
of
our
baby
killer
feature
the
one
thing
that
Drupal
doesn't
have
yet
we've
got
a
handful
of
follow-up
issues
from
that.
A
A
So
your
style
sheets,
in
your
louder
than
once,
that
handle
your
layout
target
your
layout
classes
and
then,
if
you
have
parts
of
your
layout
that
need
color
right,
those
will
go
in
your
theme,
and
so
I
think
that
it'll
kind
of
people
understand
that
separation
between
layout
and
style.
This
one
is
happening
in
kind
of
the
front
end
world
in
general.
There's
a
whole
philosophy
of
smacks.
It
like
separates
your
layouts
from
your
styles.
A
We're
doing
that
in
backdrop,
in
a
more
physical
way
where
the
templates
are
actually
not
part
of
your
feet
in
New,
Year's,
its
style,
shoesnike
controller.
So
having
those
classes
go
into,
layouts
I
think
is
going
to
be
super
humble
for
the
class
names
of
the
prefixes.
So
that's
also
done
since
last
week,
which
is
great.
A
Anyway,
we
talked
to
a
bunch
of
other
people
is
that
they
never
used
it
more.
Like
a
you
know,
what's
the
point
of
maintaining
this
piece
of
custom
code
when
you
have
using
core
people
could
build
of
you
if
they
wanted
to
who's
online
ur,
this
new
block,
so
we
removed
those
in
the
hopes
of
not
having
to
maintain
that
chunk
of
none
view.
A
Custom
code,
we
have
two
other
block
views
that
have
not
yet
been
converted
to
the
recent
content
view
and
the
recent
comments
view
those
both
have
views
in
backdrop,
but
they
don't
have
upgrade
paths
yet.
So
we're
going
to
leave
the
custom
code
in
core
until
we
get
the
upgrade
path
for
the
view,
and
we
can
swap
that
at
any
time
that's
not
an
API
blocker,
so
well,
we'll
just
whenever
we
get
those
ready,
we'll
remove
the
custom
code.
A
If
you
have
to
support
it
and
replace
it
with
a
view
in
terms
of
our
administration
page
is
we
have
both
replaced,
the
admin
people
page
and
the
admin
content
page
with
views
and
the
reason
those
are
really
important
is
because
those
have
an
integration
with
views
both
operations,
and
so
there
are
actions
that
are
like
published
this
note
or
get
this
user.
This
role
that
needed
to
be
created
so
that
we
could
remove
the
old
custom
actions
that
were
in
Drupal
7
and
roughly
with
a
beautiful
operations
equivalent
of
those
actions.
A
So
we
want
to
get
those
done
before
the
initial
release
and
those
are
both
done
and
in
so
we're
looking
good
on
that
front
and
then,
in
terms
of
the
rest
of
our
use,
conversions,
the
only
thing
left
is
the
pages
that
are
generated
by
a
fuse,
so
that
will
be
noted
taxonomy
term.
These
are
things
that
I
feel
pretty
strongly
about
in
terms
of
usability
like
we
want
people
to
not
have
to
override
those
pages
with
a
view.
A
We
want
people
to
just
edit
the
view,
but
there
also
we
can
put
in
those
changes
at
any
time.
We
can
replace
the
note
page
and
put
in
a
view
and
provide
an
upgrade
path,
so
not
a
release
blocker.
So
those
are
kind
of
the
next
things
on
my
list,
but
you
know
we
need
leaving
someone
to
work
on
them.
I
think
there's
pull
requests
for
both
of
them.
A
Both
of
them
have
actually
I'm,
not
sure
anyone's
worked
on
taxonomy
term
at
all,
so
that
one
might
not
even
have
a
poor
oppressed
before,
but
I
know
the
node
one
has
a
pull
request
and
needs
an
upgrade
path.
So
obviously
that's
the
the
sticky
part
there
is
getting
that
upgrade
path
in.
We
can't
just
copy
the
config
file,
which
is
going
to
be
the
easy
part.
A
Instead,
what
we
need
to
do
is
actually
just
write
it
out,
because
in
the
future
we're
going
to
have
additional
upgrades
that
change
the
config
file,
and
so,
if
it's
not
in
this
state,
we
intend
it
to
be
first.
If
it
copies
it
and
then
it
tries
to
change
it
and
that
changes
can't
be
made
because
the
file
copied
already
contained
it
is
gonna,
be
problematic.
So
and
there
are
some
struct
instructions
in
there
on
how
you
and
I
get
those
upgrades
done,
but
it's
much
harder
than
helping
confuse.
A
So,
let's
see,
where
are
we
in
this
agenda
fused,
so
yeah?
This
is
looking
good,
we're
ready
for
release
stuff
coming
lately,
config
management.
We
don't
have
any
release
blockers.
We
have
had
a
couple
of
people
testing
it
I
found
one
bug
related
to
config
management
that
was
from
July
or
something
and
I
haven't
been
able
to
recreate
it.
I'm
a
little
bit
nurse
we
haven't
been
getting
more
bug
reports
I
mean
that's
amazing.
A
That
seems
like
everything's
working
but
I
have
a
feeling
that
we're
going
to
be
getting
bug
reports
soon
and
we're
going
to
be
fixing
stuff
throughout
the
one
point,
0
point
0
or
one
point,
no
point
X
cycle
as
people
start
actually
using
it
and
seeing
what's
coming
up,
but
so
far
I
mean
the
kinds
of
things
they've
been
doing
with
it
and
perfectly
fine,
but
it
would
be
great
if
we
could
have
some.
You
know
more
hands-on
experience
with
it
to
actually
prove
that
it
is
as
worthy
as
we
think
it
is.
A
So
that's
great
another
thing
added
a
new
item
in
this
list
since
last
week
is
a
section
for
improving
backwards
compatibility.
Obviously,
the
our
biggest
selling
point
right
now
is
that
backdrop
is
really
close
to
triple
seven
and
we're
trying
to
make
it
as
easy
as
possible
support
flights
that
are
currently
on
Drupal
7
to
backdrop
and
as
part
of
that
process,
we've
had
a
couple.
A
People
write
blog
posts
about
what
it's
like
to
port
modules,
and
we
found
some
functions
that
were
changed
early
in
Drupal,
8
or
even
later
in
backdrop
that
don't
exist,
and
so,
when
you
put
in
a
module-
and
you
turn
it
on-
you
get
this
undefined
function
call.
So
we
have
a
triple
that
ink
backwards.
Compatibility
player
file
and
we've
been
putting
wrappers
for
all
of
these
change
functions
into
that
file.
A
Obviously,
at
the
end
of
1
point
0
point
0
and
see
we'll
try
and
get
some
statistics
on
whether
people
are
using
that
to
bed
early
or
not,
and
if
we
should
remove
it,
but
hopefully
the
modules
will
be
far
enough
along
by
then
it
can
be
written
for
backdrop
and
not
for
triple,
but
we'll
see
how
it
goes.
So.
We've
got
some
improvements
for
backwards.
A
Compatibility
since
last
meeting
to
I
added
a
section
into
this
agenda
for
things
that
we're
working
on
in
one
point:
0
point
X,
which
are
bugs
that
need
to
be
fixed
and
things
that
we're
working
on
in
one
point,
one
point
X,
so
these
are
new
features
that
we
want
to
roll
out.
Obviously
we're
not
working
on
any
of
these
things
right
now,
because
we're
working
getting.
B
A
First
release
out,
but
just
for
those
of
you
curious
of
what
we
have
planned
for
1.1
we've
got
a
built-in
rich
text.
Editor
we're
not
calling
it
a
WYSIWYG
editor,
because
in
Drupal
/
backdrop
land
and
you
aren't
gonna-
see
what
you
get
because
you're
looking
at
it
in
an
admin
theme
and
you're
building
it
out
in
a
box.
That's
not
necessarily
the
right
size.
We
think
WYSIWYG
wooden
quote
encompass
like
the
whole
page
and
that's
not
quite
what
we're
talking
about
we're.
A
Calling
it
a
rich
text
editor
we're
giving
you
people
to
put
HTML
or
rich
text
into
a
body
field,
and
so
we're
trying
to
kind
of
set
the
right
tone,
though
the
terminology,
but
we
want
to
get
that
in
it's
something
that
Nate
worked
really
hard
on
for
sure
boy,
it's
kind
of
silly.
The
backdrop
doesn't
have
that
so
we're
going
to
get
that
done
pretty
soon
and
other
things
we're
going
to
kind
of
go
through
the
top
10
modules
that
are
used
on
Drupal
and
make
sure
we
get
most
of
those
into
core.
A
So
the
first
two
we're
targeting
our
token
and
path,
auto
and
there's,
obviously
a
bunch
of
field
modules
and
stuff
that
we
also
want
to
get
in
there
pretty
soon.
So
we're
gonna
put
this
on
the
list
for
maybe
two
or
three.
So
that's
we're
looking
at
right
now
and
then
there's
a
bunch
of
other
stuff
that
we're
working
on
all
the
time.
The
biggest
thing
that
I've
been
focused
on
lately
is
trying
to
get
our
style
guide.
Change
is
done.
We
have
some
designs
for
them.
A
We
got
last
night
which
look
pretty
good
they're,
not
done.
We
have
Ronnie
Norwood,
also
working
on
it
for
us
and
we've
got
another
set
of
designs
coming
today
tonight,
we're
gonna,
see
demanding
on
how
crazy
the
style
guide
changes
are
how
much
of
those
are
safe
to
get
in.
For
one
point,
0
point
0:
it
could
be.
You
know
if
it's
drop
button
style.
A
We
can
put
that
in
that's
no
problem,
but
if
it's
something
like
a
drastic
change
to
our
admin
thing
we'll
have
to
wait
and
we
can
put
it
in
one
point,
one
or
one
point
a
point:
X
or
whatever
we
can
put
it
in
later
and
we
just
don't
want
to
run
the
risk
of
breaking
anything
by
making
two
large
sweeping
changes.
So
we'll
see
what
we
get
we'll
see,
how
fast
we
can
get
implemented
and
we'll
see
how
dangerous
it
is
and
then
we'll
decide
which
branch
a
goal.
A
We
also
have
a
ton
of
you
for
easier
experience.
Improvements.
We've
got
a
new
issue
tag
UX.
If
anyone
runs
into
user
experience,
problems
or
wants
to-
and
these
are
experienced
problems
you
can
either
tag
an
issue
or
social
issues
with
the
tag
and
it's
not
a
fishel
github
label
like
some
of
our
other
ones,
like
marking
an
issue
as
a
bug,
we're
just
using
square
brackets
and
then
the
letters
D
in
acts
in
there
to
indicate
or
you
an
X
indicate
these
are
experienced.
A
We
also
have
a
DX
tag
in
issue
title,
which
is
for
developer
experience
and
that's
what
will
marking
most
of
the
things
that
are
adding
backwards,
compatibility,
a
lot
of
layers
and
if
you
find
anything
that
you're
working
on
you
feel
is
stupid.
I.
Do
this
all
the
time
I'm
like?
Oh
that's
stupid.
Why
does
that
work
that
way,
I'll
go,
create
an
issue
and
tag
it
with
DX
and
be
like
developers
have
a
better
experience
of
way
to
this.
A
So
there's
a
bunch
of
those
issues
in
the
queue
to
let's
see
other
things,
we've
got
going
on
that
aren't
backed
up
the
project.
Our
number
one
update
server
for
backdrop
CMS
last
week
at
the
last
meeting
me
nuts,
that
we
have
an
update
server.
All
it
does
right
now
is
returned
a
what
is
it
a
405
or
whatever
it
is
that
is
not
implemented
and
so
backdrop
the
software
it
listens
for
that
enough,
not
implemented
error
and
won't
throw
an
ugly
error
in
your
website
just
because
there's
no
bad,
no
updates
average.
A
So
we
kind
of
just
bought
us
a
little
bit
more
time
to
create
the
update
server.
We're
obviously
going
to
need
to
do
that
here
in
the
very
near
future,
but
we
couldn't
release
the
software
with
it.
Chef
showing
a
big
red
error,
saying
that
you
know
Drupal
is
not
up
to
bake
some
checking
the
triple
servers,
so
we
we
fixed
that
bought
of
some
more
time
there
and
we're
going
to
go
ahead
and
work
on
the
update
server.
Next,
let's
see
we
are
also
working
on
the
API
website.
A
We've
got
change
wreckers
being
created
over
there.
We've
got
some
documentation
being
created
over
there.
I
have
a
to
do
to
port
the
module.
That's
on
or
sorry
the
theme
that's
on
backdrops
primary
website
over
to
the
API
site.
It
has
some
formatting,
that's
super
useful
for
documentation
pages,
but
it
has
some
formatting
for
the
main
navigation
that
doesn't
really
work
on
the
API
site.
So
we've
got
to
fix
that
that's
kind
of
a
to
do
on
my
plate
just
to
get
that
in
there.
We
also
have
a
change
records.
A
We've
been
making
some
more
changes
to
backdrop
in
the
last
few
days,
so
I.
Don't
that
a
bunch
of
people
who
created
a
bunch
of
change
records,
we
have
a
handful
of
new
ones
that
we
need
to
have
created.
Obviously
it's
not
super
urgent,
but
the
more
accurate
our
change
records
are
when
we
were
released
easier.
A
Okay,
so
something
else
that
we
need
is
a
fishel
github
service.
So
if
you
create
a
backup
module
or
you
create
a
backdrop-
a
theme-
we
want
you
to
be
able
to
edit
your
github
project
under
settings
and
it
says
like
what
kind
of
project
it
is,
and
it's
got
options
there
for
like
this
is
a
jquery
plugin
we
want
to
have
it
have
an
option
that
it.
A
This
is
a
backdrop
extension
whatever,
and
you
check
the
box
and
then
backdrop
CMS,
two
orbs
primary
website
can
then
index
all
of
those
projects
that
have
that
box
chart.
So
it
will
give
us
an
easy
way
for
people
to
search
for
modules
and
themes
that
are
made
on
a
backdrop
but
made
for
backdrop
but
hosted
on
github,
and
so
they
aren't
having
to
search
github
for
everything,
because
it's
really
hard
to
know
like
you
know,
which,
who
is
the
definitive
owner
of
this
project
like
is
this
one
I
should?
Is
it
actually
for
backdrop?
A
Was
it
for
Drupal
so
having
a
way
to
do
that
would
be
super
useful
and
then
we're
going
to
have
the
official
backdrop.
Projects
also
create
a
node
on
the
primary
backdrop
website,
where
you
can
put
things
like
links
to
the
issue,
queue
and
all
of
that
stuff.
So
if
you
check
the
box,
it's
an
equivalent
if
your
bowl
sandbox
project
and
if
you
create
the
node
on
a
backdrops
website
official
official
project
and
we'll
have
also
have
a
more
clear
documentation
about
how
that
works
too.
A
After
we
make
it
work
all
right,
so
other
things
primary
website
now
has
our
logo
and
fonts
on
it.
So
that
was
something
that
had
been
bothering
me
that
we've
had
a
logo
for
a
long
time,
but
hadn't
updated
our
actual
website
with
our
logo.
So
we
got
it
on
there.
I
think
the
first
round
of
design
updates
is
done.
We
have,
we
need
a
mobile
navigation
on
it
right
now.
A
It
just
kind
of
prints
them
when
you
out
at
the
bottom
of
the
page,
which
is
less
than
idea,
and
we
have
designed
swimmable
navigation,
but
everything
else
I
think
has
been
implemented
and
then
all
of
these
other
parts
of
our
flagship
site,
like
adding
a
showcase
aight,
find
modules
themes,
pages
a
service
directory
jocks
listing
those
will
wait
until
we
have
things
to
show.
So
is
that
it
we
have.
The
github
service
will
be
able
to
build
the
modules
and
themes
pages
as
soon
as
there
are
sites
running
back.
A
Jeff
will
build
a
showcase
as
soon
as
there
are
people
trying
to
hire
people
for
backed
up
or
we'll
build
a
job
site
so
we'll
get
to
those
as
needed,
but
we
have
plans
for
them.
I
just
aren't
there
yet,
okay,
so
every
Thursday.
After
this
meeting
we
usually
have
a
little
mini
sprint.
Moving
on
IRC,
we
can
talk
about
what
we're
working
on
what
you
need
help
with
what
you
have
questions
about.
You
can
also
tweet
at
us
at
factor
of
CMS.
You
can
send
us
an
email.
A
We
put
up
a
contact
form
on
our
website.
It's
when
it
has
any
questions.
I'm
getting
hold
of
us
is
pretty
easy,
but
we're
trying
to
do
a
bunch
of
work
together
on
Thursdays
just
so
that
we
can
make
some
progress
and
have
you
can
have
hands-on
assistance
with
whatever
it
is
you're
working
on
and
in
terms
of
upcoming
events.
A
Don't
think
we're
gonna
have
enough
time
to
write
enough
material
to
do
a
training
on
backdrop,
so
we're
probably
gonna
mix
that
one,
but
we
will
do
a
session,
maybe
even
a
two-hour
session
that
involves
a
bunch
of
demo
and
we're
going
to
start
porting
backdrop,
CMS
networks,
primary
website,
404
the
backdrop
and
I
think
that
would
be
a
really
cool
thing
to
show.
People
like
this
is
what's
involved
in
terms
of
moving
in
triple
seven
said
to
a
backdrop
site.
A
Here's
how
you
check
your
modules
to
see
how
much
works
would
be
involved
in
reporting
them.
This
is
what
you're
going
to
need
to
do
to
your
theme
and
kind
of
walk
through
that
process
and
I.
Think
after
we've
done
it,
we
might
be
able
to
do
an
abbreviated
version
of
it
in
an
hour.
So
maybe
we
can
do
like
our
standard.
Why
backdrop
like?
Why
should
you
care
talk
and
then
an
hour
of
like
okay?
A
If
you
do
care,
this
is
how
so
the
Y,
backed
up
in
the
house
backdrop
might
be
a
good
combo.
So
I
got
that
request
from
Susan
this
morning.
We
need
to
talk
to
nate
about
it
and
figure
out
our
schedule,
but
I
think
that
sounds
like
a
really
fun
thing
to
do
when
we
actually
have
something
to
show
people
than
talking
about
it.
A
I'm
just
should
so
I'm
pretty
excited
about
that
again,
we
don't
usually
go
to
drupal
camps
and
loss
were
specifically
invited
because
there
is
a
little
bit
of
tension
in
the
Drupal
community
around
factor
up,
and
we
don't
want
to
feel
like
we're
showing
up
and
telling
people
what
they
should
be
doing
instead,
but
if
a
community
says
hey,
we
want
to
know
about
backdrop,
come
talk
about
it,
we
will
come
and
talk
about
it.
So
if
you
want
us
to
talk
at
your
camp,
please
invite
us
cuz.
We
heart
can
offer
her.
A
Okay
but
yeah,
so
bye,
there's
also
some
people
watching
this
video
right
now.
So
thank
you
for
watching.
If
you
have
any
questions,
you
can
tweet
at
backdrop
CMS
or
send
us
an
email
or
find
us
on
IRC,
yeah
I
think
I'm
really
excited
about
backed
up
coming
out
soon.
I
really
want
to
use
it
so
every
day
I'm
like
I
want
to
use
it.
Oh
wait,
I
should
work
on
it.
First
I
want
to
use
it
now.
A
I
need
to
fix
this
thing
first
next
week
next
week,
I
can
use
it
this
week,
stay
in
the
code,
but
yeah
so
I'm
really
looking
forward
to
having
the
release
out
I.
Also
really
like
our
idea
of
you
know.
If
it's
not
in
it
next
version,
we're
still
releasing
anyway
I'm
really
looking
forward
to
the
virtually.
So
we
can
kind
of
start
proving
that
to
people
that's
kind
of
the
opposite
of
how
Drupal
works
so
and
that's
kind
of
a
big
piece
of
why
we
are
not
Drupal
anymore.
A
B
A
B
A
This
is
the
biggest
question
I.
Think
for
everyone
is,
you
know,
I
maintain
Drupal
modules.
I,
don't
want
to
maintain
two
separate
sets
of
code
like
one
for
Drupal
Mon
forgot
job
I
have
a
handful
of
Drupal
modules
fam
in
the
same
boat.
The
problem
is
not
really
between
Drupal
and
backdrop.
The
problem
is
really
between
triple
seven
and
Drupal
8.
A
It's
gotten
to
the
point
where
you
do
have
to
maintain
two
separate
pieces
of
code
for
your
Drupal
7
version
of
your
module
and
you're
deployed
version
of
your
module,
we're
trying
to
make
it
as
easy
as
possible
to
maintain
one
version
of
the
code
for
Drupal
7
and
backdrop.
However,
there
are
caveats
to
that.
Like
I
have
a
bunch
of
modules
that
do
one
thing
and
that's
like
provide
a
block
and
that
block
might
be
like
flex
nap
or
maybe
it's
social
media,
icons
or
whatever.
A
A
You
know
default
config
for
your
settings,
forms
for
that
module
or
whatever
that
dribble
will
ignore.
It
just
doesn't
know
what
to
do
with
the
Jason
files.
A
backdrop
can
read
them
in
and
find
them,
however,
so
where
you
keep,
that
code
is
up
to
you.
If
you
want
to
you
know
you
have
your
code
already
in
the
Drupal
repository.
If
you
want
to
keep
it
there,
because
it's
easier
for
you
to
maintain
it
there,
that
is
perfectly
fine.
What
we
don't
want
to
do
is
rely
on
Drupal's
infrastructure
to
support
backdrop
projects.
A
So
if
you
ever
feel
like
you're
not
going
to
support
the
Drupal
project
anymore,
we
want
it
off
of
their
infrastructure,
just
to
be
respectful
of
the
fact
that
they
have
to
pay
for
that
and
maintain
it
and
all
that
stuff,
and
so
there
are
projects
that
will
allow
you
to
keep
that
code
on
github,
which
is
free
and
usable
for
everyone
and
sink
it
between
github
and
Drupal
I.
Think
I.
A
A
I
have
to
talk
about
it,
but
there's
a
project
that
will
let
you
automatically
sync
your
github
repository
with
your
drupal.org
repository
using
kik,
which
is
good
now,
if,
if
you
have
a
module
that
is
more
complicated
than
just
providing
a
block
something
like
flag,
for
example,
it
has
its
own
database
table
as
its
own
settings.
It
has
a
ton
of
stuff
associated
with
it.
In
a
backdrop,
world
you're
going
to
want
that
module
to
use
config
and
in
a
Drupal
7
world
it
can't
its
stage
storing
all
that
stuff
in
the
duties.
A
So
you
can
make
that
Drupal
7
module
work
on
backdrop
exactly
the
same
way
as
it
works
on
Drupal
7.
This
is,
we
call
backdrop
compatible
module
where
it
still
source
all
that
stuff
in
the
database,
and
you
can
turn
it
on.
You
can
use
it
exactly
the
same,
a
wooden
triple
second,
but
you
aren't
going
to
be
able
to
deploy
those
configuration
changes
on
a
backdrop
site
like
you.
Would
your
content
types
or
other
things,
in
fact
rope
that
are
using
cmi.
A
A
And
you
don't
want
them
to
have
to
worry
about
the
stuff
that
you're
dealing
with
a
Drupal
7.
You
could
say:
okay,
you
do
triple
87
on
Drupal
thumbs
up
I.
Imagine
that
same
thing
will
happen
in
backdrop
where
you'll
have
some
people
who
don't
care
about
backdrop
and
aren't
interested
in
doing
whatever
it
is
that
we're
doing
over
here,
and
you
have
some
people
who
are.
A
You
know
the
same
way
about
what's
going
on
at
your
plate,
and
so
you'll
have
one
person
who
wants
to
maintain
a
fly
panchal
for
backdrop
and
one
person
who
wants
to
maintain
flag
module
for
drupal
and
probably
what
will
happen
is
the
code
will
fork
just
like
the
backdrop
project
is
fort
in
an
ideal
world,
the
module
maintains
will
still
talk
to
each
other,
so
you
have
some
security
issue
that
comes
out
on
triple
it.
You'll
also
be
adjusting
backdrop,
or
vice
versa.
I,
don't
know
how
that's
going
to
work
in
a
reality.
A
A
Maybe
someone
new
will
step
up
and
say:
I
want
a
support
vector
or
this
module
for
backdrop,
because
I
have
it
on
my
sites
and
I
used
a
lot.
So
we
don't
really
know
it's
going
to
be
we're
trying
to
make
this
initial
transition
as
easy
as
possible
for
people,
but
it'll,
be
up
to
the
community
and
maintain
us
to
decide
what
they
want
to
do
with
their
projects.
Longer
I'm.
B
A
Theory
and
we've
only
tested
as
the
handful
of
modules
so
far,
and
what
we're
trying
to
do
is
as
Lee
notice
like
functions
that
are
missing.
We
build
in
that
backwards,
compatibility
layer,
it's
not
going
to
be
complete,
there's,
definitely
like
porting.
A
module
is
not
going
to
be
as
simple
as
woman
in
your
info
file,
though
that
might
work
for
some
modules
there's
always
going
to
be
like.
A
Oh,
this
one
function
needs
to
be
changed
in
this
one,
but
our
goal
in
terms
of
doing
this
is
making
a
port
from
a
Drupal
7
module
to
a
backdrop,
module
be
like
an
hour
as
opposed
to
a
week
or
I.
Don't
know
rules
module
is
supposed
to
take
like
six
months
or
something
for
Drupal
8
right
that
we
want
to
make
it
as
easy
as
possible
to
get
ported.
So
we're
not
going
to
get
everything.
A
There's
a
lot
of
code,
interpolate
a
lot
of
code
and
can
trip
and
we're
going
to
try
and
adjust
as
many
of
these
issues
as
we
can
going
forward.
So
I
would
imagine
that
most
of
these
first
sites
that
are
built
using
backdrop
will
probably
port
modules
and
throw
them.
In
the
backdrop
contributory
and
say
this
is
just
how
I
did
it
and
whether
those
modules
end
up
being
maintained
there
or
just
like
for
use.
There
is
up
to
the
people
who
created
them
and
the
original
creator
to
the
module
and
Drupal
like.
A
If,
if
you
go
to
their
issue
humans,
there
even
our
sins
for
news
from
metro,
and
they
say
no,
then
that
module
is
going
to
need
a
new
maintainer
in
backdrop
land
and
it
might
live.
In
the
backdrop
repository
and
you
know,
become
something
completely
different,
so
yeah
it'll
be
up
to
the
communities
to
decide
how
they
want
to
handle
each
project.
B
A
A
I'll
just
do
the
same
thing
I'll
download
again
down
again,
ideally
we'll
be
able
to
do
that
with
josh
at
some
point
we'll
get
dressed
support.
We've
talked
to
the
judge
maintained
years
and
they
said
they're
fine,
if
Josh
supports
backdrop
as
long
as
they
don't
have
to
support
it.
So
we
can
get
a
maintainer
Ford
rush
to
do
that
for
us,
which
I
think
we
will
be
able
to
because
everybody
let's
trash,
will
be
able
to
do
that
with
Josh.
Eventually,
just
can't
do
it
today.
A
So
today,
I'm
back
to
like
old
school
like
download
the
tarball
on
target,
put
it
copy,
the
files
add
them,
but
that's
how
I'm
going
to
manage
I
think
if
people
wanted
to
have
that
entire
get
history,
they
could
I
just
feel
like
that's
too
much
information,
it's
not
really
relevant
to
any
given
project
and
working
on
so
I.
Don't
include
it
yeah
did
that
answer
the
question.
Why.
B
A
B
A
What
a
backdrop
the
update
server
will
do
is
we're
gonna,
try
and
figure
out
some.
You
know
how
Drupal
darkness
like
a
packaging
scripts,
and
it
adds
the
version
number
we're
gonna,
try
and
do
something
similar
with
with
a
backdrops
update
server,
where
it'll
be
able
to
pull
a
version
number
either
from
a
get
tagged.
We
have
an
issue
in
the
queue
about
how
we're
going
to
solve
this,
where
a
lot
of
the
stuff
is
still
kind
of
unresolved.
A
But
the
big
picture
is
that
all
of
the
update
information
will
come
from
github
it'll
either
be
from
package
automatically
by
github
or
tagged
in
the
short
term.
Tagged
manually
by
month
will
maintainer
like.
Maybe
you
have
to
add
that
version
string
when
you
create
a
version,
but
we
do
want
to
all
come
from
github
and
not
from
triple
that
works.
A
A
B
A
There's
not
retain
your
set
right
now
like
prefer
to
have
their
Drupal
code
on
github
just
because
they
use
getting
up
all
the
time
and
then
there
were
maintainer
to
prefer
to
have
their
code
on
drupal.org,
but
have
to
have
it
on
github
for
some
client
reason
or
business
or
whatever.
So
that's
why
this
two
tools
already
exist
so
we're
just
kind
of
hoping
to
leverage.
What's
already
out
there,
nice.
A
Well,
thanks
for
coming
and
asking
questions,
those
two
in
particular
ones
that
you
know
everyone
keeps
asking
over
and
over
against,
will
be
good
to
have
some
of
the
reporting,
but
yeah
I
mean
a
lot
of
it.
A
lot
of
it
is
still,
you
know,
we
don't
exist
yet
we
won't
exist
until
next
Wednesday
and
we'll
see
and
depending
on
what
happens
in
the
community.
We
can
change
our
minds
about
stuff
too
right.
It's
like,
oh,
we
think
it'll
happen
this
way,
but
then
we
watch
something
I'm
and
differently.