►
From YouTube: Backdrop CMS Weekly 10/16
Description
Today’s agenda: http://bit.ly/Zuod5r
A
So
these
are
bugs
that
exist
in
Drupal.
7
website
exists
in
Drupal
8
in
other
bugs
that
have
not
yet
been
identified,
perhaps
specific
to
backdrop
and
we'll
fix
those
as
we
find
them
also
and
hopefully,
while
we're
adding
these
new
features
and
fixing
bugs
will
be
able
to
simplify
some
of
the
systems
that
already
are
in
the
tool.
A
A
A
We
can
push
those
back
to
after
the
initial
release
just
so
they
can
get
the
first
version
out
and
start
working
on
building
sites
with
it,
seeing
how
it
works.
So
we're
super
excited
about
that
in
terms
of
what
we're
working
on
right
now
we
have
three
things
that
are
released
blockers.
The
first
one
is
our
blocks
and
layouts
tool,
which
is
really
really
close
to
being
done.
Nate.
Do
you
want
to
give
us
a
little
update
on
where
that
stands.
A
B
All
right
I'll,
just
keep
talking
so
blocks
and
limits
are
looking
really
good.
We're
planning
on
doing
some
final
testing.
My
hope
was
it.
We
will
be
able
to
merge
it
today,
BW
pandas
been
doing
an
excellent
job
of
providing
some
really
great
feedback.
He
pulled
up
a
couple
issues
that
we
need
to
get
resolved
today
and
we
need
to
merge
in
with
the
latest
one
dot
X,
because
a
couple
things
have
changed:
more
system
updates,
and
things
like
that.
B
B
It's
it
drastically,
improves
the
situation
that
we're
in
in
a
whole
bunch
of
areas.
Let's
this
place
blocks
multiple
times
lets
us
use
multiple
layouts.
Oh,
it's
this
override
past,
let's
create
new
pads,
introduces
contexts,
it's
all
kinds
of
really
great
stuff,
and
it's
I
think
that
we're
really
at
a
point
where
we
should
be
putting
it
in
there
because
right
now,
although
we've
been
getting
great
testing,
as
is
from
a
few
people
that
have
been
active
in
Gib
I
think
would
be
really
excellent.
B
If
we
could
get
the
broader
audience
using
back
jump
kind
of
familiar
with
it
and
actually
seeing
it,
we
need
a
broader
audience
basically
to
test
it
right
now
and
I
think
the
best
way
to
do
that
is
to
get
it
into
the
project
and
then
move
forward
from
there.
We've
got
a
follow-up
issue
see.
What
number
is
that
so
86
is
the
layout
issue.
If
you'd
like
to
look
directly
at
that
one,
but
then
we
started
a
follow-up
task
at
345.
B
That
will
be
kind
of
the
things
that
we
want
to
do
afterwards.
So
the
base
system
will
still
just
provide
the
current
blocks.
It
will
make
new
ones,
but
we've
got
this
follow-up
for
doing
important
things
like
adding
field
like
a
block,
/
field
and
adding
a
search
box
for
the
list
of
all
blocks,
and
things
like
that.
So
there's
still
a
lot
of
work
to
be
done,
but
the
base
system
is
is
really
good
and
with
any
luck
we
can
get
that
wrapped
up
today.
B
A
So
really
close
with
box
and
lads
I
also
want
to
try
that
today
and
when
we're
done
with
this
call,
I
want
to
give
it
a
pull
and
try
it
I'll
take
a
look
at
the
issues
that
bwp
underreported
first,
just
that
I
have
an
idea
of
what
those
are,
but
I'm
super
excited
to
give
a
spin
and
anything
that
you
need
to
help
get
that
move
forward.
I'll,
try
and
work
on
that
too.
A
So
we
can
use
it
right
now.
It's
good
I
know
that
we
have
most
of
our
variables
convergent,
there's
still
a
bunch
that
need
some
rethinking
and
Nate
started
working
on
some
of
the
subsystems.
You
start
working
on
content
types
this
week
and
consolidated
some
of
our
existing
system
wide
config.
So
do
you
want
to
give
us
a
quick
update
on
where
that
is
too
yeah.
B
You
pretty
much
summarized
it
right
there,
though,
we
used
to
have
like
seven
or
so
config
files
that
were
all
used
bike
or
things
like
a
the
system
like
site.
Information
like
the
name
of
the
site
was
one
thing,
but
then,
like
the
performance
page
was
another
config
file
and
the
date
and
time
setting
is
another
config
file
and
with
we
got
this
largely
because
we
were
imitating
Drupal
8
implementation,
where
every
single
form
had
its
own
dedicated
config
file.
B
So
I
mean
that
had
a
that
I
had
a
minor
performance
improvement.
It
was.
It
was
really
small.
It
was
like
12
percent,
but
I
mean
it's
a
performance
improvement
nonetheless,
and
it's
also
I
think
going
to
prevent
the
site
from
having
performance
regressions,
as
you
add,
more
and
more
functionality
to
the
site.
So
that
was
a
nice
little
cleanup
and
the
other
thing,
let's
see
subsystem
lies
I
started
working
on
node
types
this
week
and
they've
been
coming
along
really
fast.
I've
got
a
an
issue
for
that
one
already
in
a
pull
request.
B
That's
already
ready.
As
far
as
I
can
tell,
it
looks
fully
ready
to
go,
but
it
probably
will
need
a
little
bit
more
revealing
before
before
we
merge
it
in
it's
only
node
types,
so
it's
only
the
ability
to
create
a
new
content
type
in
the
UI
and
things
like
that.
It's
not
actually
fields
at
this
point
fields
are
a
separate
cmi
task
that
once
we
get
no
types,
taxonomy
vocabularies
and
user
roles,
those
are
the
three
different
types
of
annuities
that
we
have
in
court.
B
A
It
sounds
great
I.
What
kind
of
a
review
do
you
need
on
that
SI
mi
pasion
people
to
test
it
and
make
sure
it
actually
works
the
same
after
as
before
in
terms
of
creating
content
type,
or
do
we
review
the
file
that
is
created
and
try
and
deploy
it
to
a
different
site,
see
if
it'll
import
that
kind
of
stuff
no.
B
I,
don't
think
we
need
to
test
the
the
individual
file
any
more
than
what
I
mean
it
wouldn't
hurt,
but
I
don't
think
we
need
automated
testing
for
that,
because
we
already
have
testing
the
checks
to
make
sure
importing
and
exporting
generic
files
work
and
I.
Don't
think
we
need
to
rebuild
the
same
tests
for
every
file
that
we
add
okay,
but
it
would
be
good
just
to
yet
to
run
through
the
entire
operation
as
soon
as
this
pull
request
is
ready.
Okay,.
B
B
Yeah
layout
says:
layouts
is
what
and
these
these
two
things
like
step
all
over
each
other,
because
they
need
to
change
a
lot
of
the
same
things,
which
is
another
reason
why
I'd
like
to
get
layouts
out
of
the
way
and
and
intercourse.
Oh
that
that
way,
I
won't
need
to
keep
rerolling
both
of
them
for
a
long
period
of
time.
Okay,.
A
A
We've
got
a
couple
of
them
in
the
queue
that
need
review,
I,
think
and
then
we
have
a
couple
more
that
are
a
little
bit
more
complicated
to
move
over
like
they're,
going
to
need
useful
operations
integration
so
that
we
can
build
to
switch
over
our
admin
pages.
I
was
actually
wondering,
if
maybe
we
should
move
that
task
to
after
long,
so
that
we
just
get
our
friend
and
views
done
before
launch,
and
then
we
get
our
admin
stuff
done
after
launch,
or
is
it
like
cute
so
the
way
that
the
video
stuff
works?
A
B
Well,
we
need
to
look
at
the
overall
action
system
and
get
that
I
know
it's.
One
of
our
task
is
converting
the
action
system
to
cmi,
but
I'm
not
really
sure
how
involved
that
is.
I
know
that
the
way
Drupal
8
implemented
things
with
with
vbo
system,
especially
around
canceling
user
accounts.
It
didn't
actually
like
create
a
new
way
that
user
accounts
are
canceled,
it
just
kind
of
wrapped
the
existing
functionality
into
an
action.
B
A
B
A
B
A
We
have
11
live
site,
running
back
crap
that
I
know
of
so
I
would
like
to
get
that
security
fix
in
the
backdrop
so
that
we
can
update
that
live
site
just
so
that
we're
not
also
potentially
exposing
people
to
the
same
risks.
That
Drupal
was
now
that
that
issue
is
public,
so
that'll
be
great
and
I'm
gonna
work
around
that
today,
too,
so
I'll
first
want
to
test
layouts
and
then
I
want
to
work
on
these
security
issues.
A
That's
my
plan
forte
and
then
there's
other
things
too,
like
not
only
security
issues
that
we
need
to
move
over
that
have
been
solved
in
Drupal,
but
also
other
issues
that
have
been
soft
in
triple
seven.
So
there's
a
bunch
of
bug
fixes
they
get
moved
into
the
latest
version
of
Drupal
7.
We
have
an
issue,
that's
tracking
those.
A
We
have
three
html5
issues
left.
We
have
a
handful
of
JavaScript
cleanup
stuff
again,
not
mission-critical,
but
would
be
good
to
get
our
JavaScript
consistent
before
we
ship
and
and
then
we
have
a
bunch
of
little
minor
things
that
we're
working
on
it
as
well.
That
are
not
release
blockers
but
we'll
make
backdrop
better.
The
first
one
is
separating
our
identity
from
Drupal's
identity,
and
we've
already
done
this
by
rebranding,
the
Installer
page,
which
is
good,
and
we
have
Julia
working
on
a
style
guide
for
the
administration
theme.
A
We
got
an
email
from
her
earlier
this
week,
so
I
know
that
she's
working
on
it
just
asking
generally
about
how
she
should
be
working
with
the
style
guide,
git
repo.
So
that's
a
good
news.
So
if
we
can
get
that
done,
we
can
start
to
create
issues.
They're,
like
okay,
the
style
guide
says
how
didn't
should
look
like
this,
but
our
headings
look
different.
Let's
fix
you
know
CSS
for
all
headings
on
site
or
what
have
you?
A
We
can
add
all
the
changes
that
she
wants:
two
separate
issues
and
cranky
those
fairly
quickly
once
we
have
them,
which
will
be
great
and
other
so
we're
working
on
is
themed
system.
Cleanup
we've
got
a
bunch
of
issues
here
that
are
pretty
straightforward
and
a
bunch
are
that
are
a
little
bit
more
complicated.
A
Some
of
the
the
theme
system,
like
kind
of
conceptually
how
it
works,
is
going
to
be
significantly
different
after
we
get
layouts
and
like
our
page
templates,
won't
be
page
templates,
anymore,
they're
going
to
be
layouts
depending
on
which
type
of
page
you
want,
and
so
some
of
that
is
on
hold
until
we
get
the
layout
stuff
done,
but
they're
as
much
of
other
stuff
that
we
could
do.
That's
in
that
issue,
that's
ready
for
people
work
on
it.
We
have
people
who
want
to
work
on
it.
A
I've
got
a
couple
that
go
half
done.
That
I
should
create
poll
requests
for
just
that
people
can
see
what
I'm
doing,
but
we'll
see
when
I
can
get
to
that.
Other
things
we're
working
on
our
some
user
experience.
Improvements
like
changing
the
way
that
people
interact
with
the
software
we've
got
a
metaphor.
A
Terminology
updates,
I
think
that
one
thing
that
is
important
to
mention
too,
is
that
in
Drupal
there's
a
lot
of
emphasis
on
making
the
right
decision,
because
we
have
to
stick
with
that
decision
through
the
entire
Drupal
cycle,
but
I
think
in
fact
rock.
We
should
be
okay
about
trying
something
and
seeing
if
it
works
and
then
trying
something
off
as
if
it
doesn't
so.
A
We,
for
example,
change
the
name
of
the
link
in
the
main
navigation
that
used
to
say
modules
to
functionality
and
there's
looking
a
lot
of
pushback
about,
like
you
know,
Drupal
8
named
it
something
else,
and
other
people
wanted
to
say
plugins
and
it's
like
look,
let's
just
drive
on
tonality,
because
it's
in,
if
it
doesn't
work,
we
can
change
it.
We're
not
we're
not
married
to
this
label
for
forever,
so
I
think,
especially
in
this
early
version.
Like
backdrop
1
point
0
point:
0
is
going
to
have
very
few
users.
A
Where's
that
dropped
one
point.
1
point
0
will
probably
have
more.
So
if
we
make
a
mistake
now,
it's
super
easy
to
change
it
and
if
we
wait
until
backdrop
to
it'll
be
a
little
bit
harder
to
a
couple
of
years
of
documentation
to
worry
about
so
I
think
we
should
just
give
it
a
shot,
see
how
it
goes
and
then
we
can
change
it
afterwards
if
it
doesn't
work.
So
that's
kind
of
where
things
stand
on
that
and
definitely
keeping
things
open
for
discussion
is
important.
A
Doing
some
actual
testing
on
them
seem
more
important
and
we'll
figure
out
how
those
go
other
things
we
want
to
do
for
user
experience
include
and
adding
rich
text
editor.
This
has
been
sort
of
postponed
until
after
the
initial
launch,
because
we
think
we
can
do
it
without
breaking
api's,
which
is
good
but
I.
If
we
have
anyone
who's
super
passionate
about
backdrop,
one
point
0
point,
0
being
released
with
a
rich
text
editor.
There
is
an
issue
it
can
be
worked
on.
A
We
have
ideas,
we
just
don't
have
enough
fingers
to
do
all
the
typing
and
then
there's
a
couple
of
other
issues
that
we
just
need
to
review
before
we
can
release.
One
of
them
is
pretty
straightforward.
It's
just
reviewing
all
the
CSS.
We
moved
all
of
our
CSS
around
in
backdrop,
and
we
also
change
some
of
our
syntax,
though
the
way
that
we
address
things-
and
it
would
be
good
to
just
have
kind
of
a
holistic
review
of
you.
A
A
list
of
all
the
style
sheets
in
court
make
sure
they
all
adhere
to
these
floating
standards
and
live
in
the
correct
location
and
all
that
stuff.
So
I
created
a
meta
issue
for
that
that
lists
all
the
stock
sheets.
We
need
to
review.
There
are
some
style
sheets
that
we've
included
that
are
just
for
testing
purposes,
so
I've
removed
those
from
the
list.
A
So
if
we
have
someone
who
is
the
CSS
ninja
and
let's
take
a
look
at
those
out,
be
pretty
great
and
then
there's
also
the
layout
markup,
so
the
way
out
patch
gets
in
really
soon
we
can
have
someone
start
looking
at
this
in
core.
If
not,
we
can
have
it
reviewed
in
its
current
and
pull
request,
but
we
have
a
bunch
of
mark
out
where
markup
we're
adding
for
each
layout.
That
could
use
a
little
review
and
so
I
create
an
issue
for
that
today
too,
so
that
we
can
get
some
review
inmate.
A
If
I
could
have
you
look
at
that
issue
and
see
if
there
is
anything
else
in
particular,
you
want
to
have
reviewed
I
made
a
bolt
list
of
like
things.
We
should
check,
I
mean
just
see
if
there's
anything
else
in
there,
you
want
to
add.
That
would
be
great.
So
that's
the
stuff.
What
we're
trying
to
get
done
before
we
release
we
really
soon
so
there's
a
lot
of
stuff.
We
could
definitely
use
more
hands
on
deck.
We
have
anyone
who
has
any
time
wants
to
contribute.
A
We
need
help
with
those
things
and
yeah
so
who
getting
close.
There's
a
section
in
this
weekly
meeting
that
we
have.
It's
called
updates
from
the
PMC.
So
if
there
are
any
issues
that
come
up
in
the
queue
or
otherwise
that
we
need
to
discuss
and
solve,
and
as
in
you
know,
does
this
adhere
with
where
the
project
is
going,
the
PMC
will
sit
and
then
explain
to
people
through
this
part
of
this
meeting
what
we've
decided.
A
So
there's
a
bunch
of
stuff
that
we're
working
on
that
is
not
back
drop.
The
code
backdrop,
the
original
project-
there's
a
bunch
of
stuff-
that
we
need
to
support
our
community-
that
we're
also
working
on
of
those
the
API
website
is
pretty
important.
That's
the
thing
our
developers
are
going
to
be
referring
to
to
check
out
our
code.
I
Luke
thank
you
for
joining.
The
meeting
today
has
done
a
great
great
amount
of
work
on
getting
that
site
up
and
running,
so
it
already
works.
A
I
actually
use
it
when
I
need
to
see
like
what's
different
between
backdrop
and
Drupal
7
I'll,
pull
it
up
and
look
at
code.
So
that's
great
and
and
we've
also
got
a
change
record
content
type
on
there
and
on
github.
Maybe
we
should
even
make
make
a
list
of
these
two.
A
lot
of
our
issues
are
tags
with
needs.
A
change
record
just
like
on
drupal.org
their
issue.
Queue
has
a
needs,
change,
record
tag,
so
I
don't
know
how
to
generate
that
list.
A
Anyway,
what
we'll
do
we'll,
try
and
generate
that
list
and
post
it
in
this
agenda
too?
So
we
can
see
it
every
week
and
but
we
should
just
kind
of
post
that
and
say
these
are
the
issues
that
we
need
to
have
change
records
created
for
and
you
can
go
through
our
queue
and
say:
okay,
here's,
the
change
and
most
of
the
time
it's
been
tagging,
something
with
needs
change
record.
He
also
puts
a
little
description
of
what
the
change
is.
A
So
it
should
be
pretty
easy
to
start
from
that
and
put
that
into
the
change
record
content
type
on
the
API
site
or
in
to
change
a
good
piece
of
content.
But
in
some
cases
it
might
not
be
enough
information
you
like
what
is
he
talking
about
it?
Don't
don't
understand
what
you
know,
there's
not
enough
information
here
and
in
those
cases
you
might
need
to
ping
him
or
just
try
like
create
a
change
record
and
then
say.
A
A
Unfortunately,
a
lot
of
those
change
records
have
been
updated
since
then,
because
Drupal
is
so
different.
Your
weight
is
so
different.
So
if
we
found,
for
example,
I
could
change
to
the
entity
system
that
we
have
in
backdrop.
It's
been
changed
again
since
that
change
record,
so
we
might
not
be
able
to
use
the
finished
change
record,
that's
up
currently
on
drupal.org,
but
we
might
be
able
to
view
/
vision
of
it.
I'm,
not
sure
how
tight
their
revision.
A
History
is
on
the
API
to
triple
that
work,
but
if
we
could
see
the
initial
one
or
one
that
maps
to
roughly
the
time
we
forked
witches
februari
29th
2012,
that
might
be
a
better
starting
point
for
us
than
the
finished
point
of
the
change
records
on
Drupal,
I'm,
not
sure
Nate.
How
to
get
a
list
of
those
change
records.
Do
you
think
I
mean
it
seems
like
the
brute
force
method
would
be
to
look
at
all
of
the
commits
that
happened
in
back
drop
between
our
fork
date
and
Drupal.
A
B
If
they
weren't,
then
we
could
somehow
get
it
into
create
a
date
order
yeah,
because
we'll
probably
only
have
to
go
forward
and
tell
ya
what
was
that
februari
2012,
so
I
mean
I,
don't
think,
there's
actually
that
many
change
records.
Drupal
8
actually
stayed
remarkably
similar
to
Drupal
7
for
like
the
first
year
and
that's
pretty
much
all
that
we
have
in
the
backdrop
code
base
as
far
as
overlap
goes.
B
B
B
B
A
B
Don't
know
we
I'm
not
sure
how
much
we
need
to
document
things
like
API
changes
that
are
happening
in
Drupal
7
that
we
also
implemented
in
Drupal
or
I'm.
Sorry
I'm
backdrop,
because
by
the
time
people
upgrade
from
their
triple
seven
sites
to
backdrop
one
point:
oh,
they
will
have
already
had
those
API
changes
in
the
Drupal
7
site,
yeah.
A
B
A
A
Okay
other
things
we're
working
on
as
an
update
server.
So
this
is
so
that
when
your
back
drop
site
goes
to
check
with
the
mothership
to
see
if
it's
up
to
date,
we
need
to
build
that
mothership,
so
that
you're
saying
well
know
if
it's
up
to
date,
this
I
think
is
important
to
at
least
have
one
before
we
release,
so
that
if
people
are
installing
and
trying
to
run
a
backdrop
site,
we
at
least
have
some
service.
A
That's
like
we
don't
have
any
information
yet
so
we're
not
connecting
to
Drupal's
mothership,
but
I
think
we
do
need
to
get
that
built
shortly
after
backdrop
is
released
so
that
people
can
start
using
it.
Even
if
we
can't
get
it
done
before,
we
need
to
have
it
exists,
which
is
so
I
think
I
don't
know.
If
we
have
anyone
working
on
that.
B
We
have
people
thinking
about
it,
but
no
real,
solid
commitments
at
this
point
like
there's,
been
a
lot
of
ideas
around
whether
or
not
we
could
use
packages
tour
some
other
package
manager
solution
out
there
rather
than
migrating
drupal's
update
service.
But
right
now
it's
not
clear
as
to
which
approach
is
is
going
to
be
easiest.
B
I
honestly
think
just
porting
the
update
module
our
side
project
module
code,
look
from
Drupal
7
over
2
backdrop,
there's
going
to
be
the
easiest
and
fastest
way
forward,
but
I,
don't
know
how
that
I'll
pants
out
we'll
need
to
yeah.
Well
I
mean
we're
open
to
alternatives.
It's
really
just
about
finding
the
easiest
way
forward.
At
this
point,
okay.
A
I
thinks
we're
working
on
our
creating
an
official
github
service.
So
this
is
what
allows
people
who
create
modules
and
themes
to
identify
those
modules
and
themes
as
being
made
for
backdrop
and
then
the
backdrop
API
say
we'll
be
able
to
pull
those
in
and
create
a
listing
of
everything.
That's
available
and
I
know
that
we
have
people
thinking
about
this
as
well.
I,
don't
think
that
anyone
is
working
on
it.
A
So
if
we
have
someone
who
wants
to
do
some
fun
stuff
with
github,
that
is
an
option
we
need
help
with
that
too,
and
then,
of
course,
we
have
our
flagship
backdrop
CMS
website.
In
the
last
two
weeks,
we
added
a
tool
on
the
front
page
so
that
anyone
who
is
in
support
of
backdrop
can
go
there
and
add
their
logo.
That
was
something
that
was
requested
by
a
couple
of
Drupal
company
owners.
I
talked
to
your
like.
How
do
I,
how
do
I
show
that
we're
in
support
of
this
thing?
I
was
like?
A
A
That's
all
I'll
ping
him
again,
and
then
we
also
want
out
of
showcase
site,
but
we
need
sites
to
showcase
first.
So
that
will
come
a
little
later.
You
want
to
add
a
way
that
you
can
search
for
modules
and
themes,
but
first
we
need
modules
and
themes
that
was
a
little
bit
later
and
we're
thinking
about
adding
like
a
job,
a
job
listing
site
like
drupal
that
work
just
added
a
great
job
site,
which
I
think
is
brilliant.
A
Something
like
that
anyway.
So
we've
got
big
plans
for
the
backup
website,
but
obviously
we've
got
bigger
plans
for
backdrop:
Oh
first
things.
First,
we're
gonna
get
some
software
out
we're
going
to
port
the
backdrop
website
to
using
backdrop
and
then
we're
going
to
start
building
out
all
the
cool
stuff.
We
can
do
with
it.
So
yeah
there's
a
lot
to
do.
We
definitely
could
use
more
help.
I've
talked
to
a
lot
of
people
who
are
super
excited
about
it,
but
are
just
kind
of
waiting
to
see
what
happens.
A
But
the
problem
with
waiting
to
see
is
that
you
know
you
have
to
wait
a
little
longer
because
you're
not
doing
the
work,
we're
not
all
doing
to
work
together.
So
if
anyone
does
have
any
time
now
is
the
time
to
contribute,
which
would
be
great
if
not
waiting
and
seeing
is
fine,
but
you'll
see
less
than
you
would
see.
If
you
were
helping
so
yeah
we're
we're
getting
close,
I'm
pretty
excited
about
it,
yeah
good
stuff.
We've
got
a
couple
of
ways
that
we
can
all
work
together
on
getting
stuff
done.
A
Every
Thursday.
After
this
meeting
we
have
a
little
sprint.
Nate
and
I
are
usually
on
IRC.
Anyone
who
else
wants
to
jump
jump
in
that's
a
great
time
to
ping
us
and
ask
us
for
questions
are
usually
working
on
backdrop
stuff
and
but
if
you
want
sperm
with
us
in
real
life,
we're
going
to
do
one
at
bad
camp
this
year
on
Sunday,
which
is
the
last
day
of
the
camp
in
the
sprint
area,
which
is
the
mezzanine
level
of
the
main
hall
in
where
bad
camp
is
so.
A
So
our
talk
is
on
Monday
when
we
get
back
or
we
get
to
sell
backdrop
to
people
who
don't
know
what
ripple
is
necessarily
so
that'll
be
fun,
and
then
we
have
bad
camp
november.
Six
through
nine,
followed
by
Cymphonique
on
in
madrid,
where
I've
been
asked
to
be
a
keynote
speaker
there
and
talk
more
about
large,
open
source
communities
than
specifically
about
backdrop.
A
But
as
someone
who
was
became
frustrated
with
the
way
our
large
open
source
community
in
Drupal
worked
and
felt
like
the
project
wasn't
going
where
I
wanted
to
go
anymore,
they
asked
us
kind
of
talk
about
why
that
happens.
So
that'll
be
that'll,
be
fun
to
kind
of
talk
about
the
problems
that
appear
in
a
large
open
source
community,
as
well
as
the
things
that
Drupal
is
done
really
well,
and
you
know
having
to
start
all
over
again
and
try
and
fill
their
own
community
and
deal
with
our
tools.
A
A
You
know
the
things
that
Drupal
does
better
than
github,
because
that's
where
they
are
and
trying
to
kind
of
take
the
good
things
from
what
your
post
went
really
well
and
the
the
things
that
have
upset
us
so
that
we
can
say
you
know
this
is
what
your
project
needs
to
do,
to
prevent
this
kind
of
thing
from
happening,
and
I
think
there's
there's
a
good
lessons
that
any
project
can
learn
from
that.
So
I'm
super
excited
about
that
too
plus,
who
doesn't
to
go
spain
so
that'll,
be
great.
A
There's
also
a
couple
of
drupal
cons
coming
up
a
lot
of
triple
condo
picking
up
that
we
are
probably
going
to
attend.
We're
also,
probably
not
going
to
be
speaking
at
backdrop
at
them
just
so
that
we
don't
ruffle
too
many
others.
But
we'll
see,
we've
been
requested
by
three
drupalcon
organizers
to
talk
about
backdrop
at
drupalcon,
but
I
think
the
consensus
is
still.
They
don't
really
want
backdrop
at
your
book
on
so
we'll
do
whatever
they
want
us
to.
If
they
don't
want
to
talk
about
it,
we
won't.
A
It
will
probably
still
be
there
because
you
know
we
still
work
with
Drupal
too
and
yeah.
We
can
talk
to
people
about
it,
so
that
is
the
end
of
the
agenda,
but
it
didn't
want
to
open
it
up
and
see.
If
anyone
has
anything,
you
want
to
add
Luke.
Thank
you
for
joining.
If
you
have
any
questions
about
anything,
we
can
definitely
address
those
now
or
if
Nate
there's
anything,
you
want
to
add
I,
don't.
A
Well,
we
will
then
hop
on
IRC
and
start
working
on
job.
So
if
anyone
has
any
questions
later,
if
you're
watching
this
video
and
we've
said
something
that
sparked
your
interest,
so
you
can
tweet
at
us
we're
back
draft
CMS
on
twitter.
You
can
contact
us
through
our
website,
I
think
or
you
can
jump
on
IRC
they're,
usually
in
the
pound
backdrop
channel,
so
yeah
good
stuff
coming
along
Oh
or
you
can
go
check
our
github
q.
We've
definitely
got
a
lot
of
new
people
participating
conversations
there
and
not
super
exciting
too.