►
Description
Today’s development agenda: http://bit.ly/1ODbH9Z
A
Alright,
we
are
on
air
happy
january
fourteenth.
It
is
one
day
before
the
big
release
of
backdrop.
One
point
three
point:
oh
we're
all
very
excited
about
it.
So,
thanks
for
joining
in
the
meeting
a
couple
of
general
announcements
as
usual,
you
can
get
your
dragon
t-shirts
and
hoodies
from
backdrop.
Cms
org,
slash,
contribute
you
make
a
donation
will
mail,
you
a
short
for
a
hoodie.
If
you
live
in
the
United
States,
if
you're
a
backdrop
contributed
a
developer
backdrop,
contributor
be
a
designer
or
a
marketing
writer
or
whatever
you've
already
earned
your
t-shirt.
A
Almost
anyone
for
free
so
just
send
an
email
to
info
about
drive
CMS
to
org
and
if
you're
not
yet
a
contributor,
you
can
always
contribute
dollars
and
your
thank-you
gift
is
going
to
be
a
t-shirt
or
a
buddy
depending
on
your
donation
amount.
So
definitely
on
get
your
shirts
and
hoodies
before
they're
gone.
We
are
going
to
be
attending
sand
camp
at
the
end
of
the
month
and
you
can
pick
them
up
in
person
there.
If
you
would
rather
test
drive
sizes
and
softness
ahead
of
time.
A
We
also
have
free
phpstorm
licenses
for
backdrop,
contributed
developers.
So
in
this
case
you
need
to
be
a
member
of
the
backdrop
contribute
on
github.
That's
how
phpstorm
checks
that
we're
not
giving
licenses.
People
were
not
supposed
to
be
giving
licenses
to.
So
if
you
have
ported
a
module
themer
layout
or
you
want
to
maintain
a
module
femur
layout,
we
can
get
you
included
in
the
contribute
and
send
you
off
a
license.
Key
and
we've
had
a
couple.
People
who
have
applied
recently,
which
is
fantastic
in
as
soon
as
we
get
you
through.
A
The
application
process
will
send
you
that
license
key
for
phpstorm.
So
thanks
a
lot
and
keys
are
on
the
way.
Anyone
who
needs
help
with
that
process
can
also
send
an
email
to
info
@
factor.
Fcms
org
I,
sometimes
is
a
little
confusing
as
to
what
is
required
to
in
order
to
do
that.
Will
help
walk
you
through
it.
We
don't
have
any
updates
from
the
project
management
committee
at
this
time,
so
I'm
going
to
turn
the
meeting
over
to
meet.
To
give
us
a
quick
update
on
community
growth.
B
Yeah
well
another
exciting
week
over
in
contribs
and
growth
planned.
Actually,
we
have
190
total
projects
for
backdrop,
CMS
there's
some
new
modules
and
some
new
layouts.
Actually
that
were
added
this
past
week,
we've
had
three
new
contribute
to
the
contribs
its
last
week
we
have
116
total
projects
with
official
releases
on
backdrop,
CMS
org,
156,
total
releases
of
those
projects.
There's
been
three
updates
to
existing
modules
since
last
meeting,
and
we
have
two
new
contributors,
bringing
our
total
to
45.
B
In
the
backdrop,
contribute
welcome
Dan,
Boulais
and
earth
day
47,
whose
first
name
is
also
Wes,
so
we're
about
to
have
to
wes's,
but
we're
really
excited
to
have
new
contributors.
Dan
worked
on
unsubscribed
module
and
earth
day
has
been
working
on
location
as
well
as
a
volunteered
to
pick
up
the
set
of
geo
modules
that
another
contributor
had
already
ported,
but
so
that
they
wouldn't
have
time
to
actually
maintain.
So
that's
really
exciting.
Earth
Day
has
also
been
involved
in
the
the
Drupal
controlled
for
a
long
time.
B
So
it's
really
great
to
have
that
experience
brought
to
backdrop
man
backdrop:
CMS
org
doubled
its
numbers
of
registered
users
since
last
week
we
had
way
now
a
68
total
user
accounts
on
backdrop,
CMS
org
and
that's
36
new
users
since
last
week,
which
is
pretty
bananas,
it
kind
of
made
I
mean
there's
not
a
whole
lot
that
you
can
do
on
backdrops
a
mess
dork,
but
I
think
people
are
mostly
just
coming
in
to
claim
their
low
user
numbers.
B
Contributing
the
data
read
me
checking
that
there's
a
license
file
and
project
history
is
longer
than
like
a
week.
You
know
make
sure
that
it
actually
matches
those
things
and
if
we're
going
to
automate
those
processes
and
make
it
so
that
people
can
get
through
them
faster,
like
the
feedback
loop
right
now
is
about
24
hours,
which
is
great,
but
not
nearly
as
good
as
if
it
were.
B
You
know
24
seconds,
and
I
think
that,
like
the
user
accounts
on
backdrops
a
mess
or
get
shows
us
that
if
we
had
more
automated
processes
where
people
could
help
themselves,
then
we
can
grow
our
community
a
lot
faster.
So
I
know
that's
that's
wish
list
stuff.
I'd
really
love
that
if
we
could
start
automating
some
of
these
things
more
because
quite
a
feedback
is
really
key.
It
seems
so
anyway,
lots
of
great
growth
this
past
week
and
we're
really
excited
to
see
see
our
momentum
building
up
even
further.
B
Let's
see
the
next
item
on
the
agenda
is
infrastructure
infrastructure.
All
the
things
around
the
backdrop,
software
that
isn't
the
software
itself.
One
thing
we
have
on
here,
we've
been
talking
about
every
week
is
the
update,
checking
and
the
ability
for
back
top
CMS
org
to
calculate
usage
statistics.
B
We
have
been
collecting
these
usage
statistics
for
months
now,
but
we're
not
actually
aggregating
them.
Yet,
due
to
what
had
been
a
bug
in
the
aggregation
script,
that's
the
bug
has
been
fixed,
or
at
least
is
ready
to
be
fixed,
but
we
still
haven't
actually
deployed.
It.
I
think
the
primary
concern
that
I
have
there
in
that
issue.
Those
listed
from
the
agenda
is
we're
currently
counting
Travis
CI
installations.
B
A
B
Well,
the
trouble
is
is
that
when
you
run
an
automated
test,
we
installed
drew
orcs
out
so
triple.
We
installed
backdrop
like
2,000
times,
like
at
least
I
mean
probably
it's
more
like
8,000
installs
when
you
run
the
full
set
of
tests
and
every
single
one
of
those
is
checking
in
to
22
backdrop,
semester
and
work,
saying:
hey
I'm,
a
new
site,
hey
when
you
say
hey,
what
do
you
say?
We.
B
B
Exactly
yeah,
we
need
to
end,
and
if
it's
in
a
test,
then
it
should
just
bail
out
or
something,
but
we
could
actually
speed
up
our
tests
quite
a
bit.
If
we
did
that
because
then
they
wouldn't
be,
you
know,
hitting
they
wouldn't
be
doing
an
HTTP
request
as
part
of
the
install
process,
which
would
be
good,
but.
C
A
A
There
could
also
I
mean
I
don't
know
how
much
we
want
to
check
this.
What
there
could
also
be
people
who
install
backdrop
and
then
turn
off
that
module
I,
don't
know
if
we
want
to
count
that
or
not
or
if
that's
like
a
respect,
their
wishes.
If
they
said
they
didn't
want
to
be
checked
undo
the
track,
they
accidentally
did
first
kind
of
yeah.
B
B
Let's
see
after
we
have
that
those
numbers
coming
in
not
only
coming
in,
but
also
getting
crunched,
we
also
want
to
start
collecting
usage
of
individual
features
and
Jen
added
some
new
ones.
This
past
week,
things
like
you
know
which
individual
core
modules
are
enabled
is
cleaning
or
elles
enabled
which
court
layouts
are
actually
being
used
on
the
site.
Maybe
how
many
layouts
are
being
used
like
how
many
layouts
are
on
on
a
typical
site?
Let's
see
which
core
field
types
are
in
use
which
contribs
like
the
individual
modules?
B
Not
the
projects
are
in
use
amongst
those
modules,
color
module
which
color
palettes
people
are
using
or
if
they're,
using
any
at
all
those
sorts
of
things.
If
we
can
start
accruing
that
data,
it
will
give
us
better
information
on
which
to
inform
our
decisions
about
what
features
we
should
be,
including
or
what
things
we
even
potentially
should
remove
in
future
versions
of
backdrop,
it.
A
Also
help
with
our
updates
to
like
we
ran.
We
committed
this
issue
this
week
about
changing
Bart,
X
color
from
blue
to
black,
but
then
we
had
to
like
write
this
update.
That
was
like
for
the
people
that
were
using
blue,
like
how
are
we
going
to
not
accidentally
change
the
color
of
their
site
and
we
went
through
several
iterations,
very
complicated
updates
and
then
just
decided
to
do
like
a
simple
fall
back
where
we
added
a
stylesheet
much
easier,
but
just
that
kind
of
stuff
where
it's
like.
A
How
do
we
know
who
is
using
color
module
and
who
is
using
this
palette?
And
wouldn't
it
be
nice
if
we
had
statistics
on
that,
because
if
we
looked
at
it
and
we're
like
oh
there's,
one
person
we
wouldn't
have
spent
like
five
days,
trying
to
figure
out
a
really
complicated
of
the
updated
path
for
that
we're
just
been
like.
A
Oh,
we
should
remove
this
from
court,
but
that
wasn't
you
know,
since
we
don't
have
those
statistics
we
still
have
to
handle
that
case
really
gracefully
right
now,
sister
starting
to
track
stuff
like
that
I
think
will
be
helpful,
especially
with
layouts
and
a
new
front.
End
theme
going
in
in
1.4
we're
going
to
need
to
deal
with
the
same
thing
again
where
it's
like
we
kind
of
have
to
write,
update
scripts
for
all
these
people,
who
are
currently
running
the
default
theme
to
change
to
a
new
or
not.
A
B
All
right
next
item
on
the
list,
drush
for
backdrop
just
for
backdrop,
is
issue
number
47
in
the
issue:
queue
on
the
longest
running
open
issue.
I
do
believe
we
have
an
open
prototype
of
drush
working
for
backdrop.
It's
ad
rush
extension,
so
you
can
drop
it
in
your
dot.
Drush
directory
in
your
home
profile
or
directly
in
your
project
or
in
to
the
dress
installation
itself
and
rush
will
find
those
extensions
and
then
it
will
magically
just
start
seeing
that
is
an
actual
backdrop
website
and
can
identify
how
to
how
to
work
with
it.
B
The
downside
of
that
is
that
we
have
to
rewrite
basically
all
the
commands,
because
of
the
way
drush
is
written
that
basically
command
just
maps
directly
to
a
chunk
of
code,
there's
no
abstraction
that
it
says
this.
You
know
under
these
different
situations,
call
these
different
callbacks
within
your
extensions.
It's
just
a
callback
execute
code
and
if
drupal
6
do
this,
if
Drupal
someone
do
that,
Nick
Drupal
8
do
this
so
making
it
work
for
backdrop.
We
need
some
special
code,
which
means
we
basically
need
to
add
in
a
different
command.
B
In
addition
to
the
Drupal
ones,
but
there's
the
prototype
is
currently
hanging
out
in
my
sandbox
I
wish
I
could
commit
to
moving
that
right
away,
but
with
the
release
tomorrow,
I'm
really
just
have
been
swamped
and
preoccupied
with
getting
everything
reviewed
it
and
pushed
in
there.
But
as
soon
as
possible,
I
know,
Saren
deputy
Jeff
you've
been
working
a
lot
on
on
making
drush
work
in
certain
situations,
and
you
ran
into
some
issues
as
well
as
filed
some
poll
request
to
add
new
features.
B
That's
all
awesome
as
soon
as
we
get
this
moved
into
the
contribute.
What
I
want
to
do
as
soon
as
possible?
I'd
like
to
just
add
you
as
as
a
maintainer,
and
then
you
can
just
kind
of
go
to
town
on
it,
because
if
you've
been
working
on
it
more
than
I
have
and
I
think
that
would
be
fantastic
just
to
have
you
empowered
to
just
iterate
as
quickly
as
possible
on
that
there's
not
a
whole
lot
to
lose.
At
this
point,
it's
just
a
you
know.
It's
it's
super
Beta
at
this
point.
B
Let's
see
so
there's
a
lot
of
issues
that
have
been
filed.
Currently,
under
that
sandbox,
it's
under
github.com,
/,
quick,
sketch,
/
backdrop
cached
rush
and
some
of
those
things
are
great
like
brush
up
DB.
Apparently
it's
broken,
but
there's
pull
request
to
fix
it.
There's
some
call
requests
to
add
new
features
so
that
it's
great
to
see
that
moving
along,
even
if
the
changes
haven't
been
merged.
Yet,
let's
see
github
automation,
I
think
Jen.
You
did
you
just
add
this
to
the
agenda
here
that
the
approval
of
github
are.
B
Yeah,
there's
there's
a
lot
of
interesting
stuff
in
here.
Actually,
what
I
won't
get
into
that
there's?
There's
a
tag:
github
dash
automation.
In
the
backdrop,
CMS
org
issue
queue
if
we
have
any
wizards
out
there
that
are
interested
in
working
with
the
github
API,
which
actually
is
a
real
joy
to
work
with.
Then
take
a
look
at
that
list
of
tags
that
listed
issues.
I
asked.
D
A
A
I
was
looking
at
that
too,
and
I'm
not
sure
there
is
a
good
triple
project
to
start
with.
It
has
a
ton
of
experience
on
single
sign-on,
stuff
and
neat
correct
me
if
I'm
wrong,
but
your
general
impression
is
that,
like
just
start
from
scratch,
well.
B
The
OAuth
project
is
great,
really,
I
mean
its
effects,
a
really
pretty
good
implementation,
but
it's
also
fairly
abstract.
It's
useful
if
you
actually
have
multiple
a
lot
authentications
or
if
you
also
are
dealing
with
you
know,
you
need
to
provide
your
own
server
and
you've
got
your
own
little
satellite
of
sites
that
single
sign-on
onto
your
parent
site.
Then
it
makes
a
good
solution
for
that
too,
but
for
a
single
sign
on
the
github
I
would
be
tempted.
I'm
not
sure
this
is
the
best
approach,
but
it
might
be
worth
looking
at.
B
Take
a
look
at
the
facebook,
a
walk
module
of
FB
0
op
module,
which
is
not
dependent
upon
the
OAuth
parent
project.
It's
just
a
an
OAuth
implementation
signing
in
to
facebook
and
if
we,
because
it's
all
0
off
facebook
and
and
github
both
you
probably
could
basically
just
take
everything-
that's
in
facebook
and
replace
it
all
with
github,
and
it
would
pretty
much
almost
work,
so
that
might
be
an
interesting
way
just
to
make
a
direct
implementation
against
github
based
off
of
the
direct
implementation
of
Facebook.
B
A
So
back
type
see
I
messed
up
bargain.
The
last
few
weeks
have
had
a
bunch
of
changes.
You
can
we
put
up
the
user
profile
pages,
which
is
really
exciting,
so
we
obviously
have
a
bunch
of
people
signing
up
now,
just
great.
We
also
since
I
think
our
last
meeting
kind
of
blog
post
that
come
out
in
this
week.
Maybe
it
was
last
Friday-
think
my
first
blog
post
went
up.
We've
had
a
bunch
of
great
tweets
and
noise
about
it.
People
read
it.
A
People
are
creating
accounts,
which
I
think
is
fantastic,
and
we
have
kind
of
made
a
commitment
to
keep
writing
blog
posts,
which
I
think
is
important.
Nate
is
going
to
write
the
next
one,
which
is
going
to
be
about
the
1.3
release,
which
is
tomorrow,
so
I
don't
know
if
that
blog,
but
should
look
tomorrow.
I
think
maybe
you
should
give
ourselves
a
couple
of
days
and
it'll
go
up
on
on
monday,
or
maybe
even
next
friday,
depending
on
what
we
find
in
that
next
release.
A
If
we
need
to
fix
anything
right
away,
we
can
put
the
blog
post
up
with
three
one
point
three
point:
one
a
good
plan,
and
then
we
also
are
interested
in
having
anyone
else,
write
blog
posts
too.
So,
if
you
have
anything
you
want
to
share
with
the
community,
our
official
schedule
is
to
do
official
scheduled
release
every
other
week
and
then
that
way,
if
anyone
has
anything,
that's
super
timely
that
needs
to
come
out
sooner.
A
We
can
squeeze
them
in
between
so
I
would
say,
like
the
more
voices
in
the
blog
the
better.
So
if
anyone
has
anything,
you
want
to
share
like
a
little
trick.
A
little
thing
you
want
to
show
off
of
a
website.
You
want
to
showcase
whatever
it
is
just
so
you
know
something
you
think
is
cool
about
backdrop
or
whatever.
It
is
just
add
a
comment
to
the
issue.
A
We
have
an
issue
for
our
blog
schedule,
which
is
number
158
and
we'll
try
and
get
you
on
there
and
we've
got
double
months,
working
on
a
bunch
of
stuff
right
now
and
I
think
suit
events
forgot
so
I'm
coming
as
well.
So
hooray,
everyone
wants
to
talk
about
back
Jeff,
totally
welcome
to
on
the
blog
we
also
I
haven't
turned
on
comments
for
the
bugs
yet,
but
we
should
maybe
think
about
whether
we
want
to
do
that.
A
If
we
need
responses
that
might
be
a
good
way
to
handle
it
so
I
just
say
kind
of
anyone
not
necessary
clonus
open
calls
anyone
who's
willing
to
kind
of
keep
an
eye
on
the
blog,
and
you
know
watch
watch
new
comments
as
they
come
in
and
make
sure
that
people
get
their
feedback
addressed.
I
think
we
could.
We
could
think
about.
Turning
on
comments
in
the
blog
and
I
think
maybe
move
should
also
figure
out
which
kinds
of
blog
posts
we
want
to
solicit
feedback
on
I.
A
Think
things
like
there's
a
new
release
might
not
be
something
that
would
start
a
conversation,
but
there
could
be
plenty
of
blog
posts
where
you
want
to
have
a
conversation,
and
so
we
can
also
use
that,
like
comment
off
on
setting
the
Thompson
backdrop
to
figure
out
when
it's
a
good
idea
to
turn
on
comments
and
whatnot,
so
that's
also
something
up
for
review
better
for
discretion.
If
anyone
wants
to
have
a
blog
question,
I'm
a
conversation
we
can
turn
them
on,
then
we
also
have
we're
working
on
integration
with
Sevilla
CRM.
A
One
of
our
plans
is
to
do
some
cross
blogging
between
one
well
as
many
other
websites,
as
we
can
in
our
own,
and
so
we've
been
talking
with
the
folks
at
Sevilla
to
try
and
figure
out
how
to
do
a
shared
marketing
around
sydney
and
backdrop
working
together,
I
think
will
be
great
if
we
could
get
one
or
several
of
them
to
blog
on
backdrops
website,
we've
offered
to
blog
on
their
web.
So
far,
they
seem
on
board
with
that.
A
We
don't
actually
have
a
schedule
up
yet,
but
it
seems
like
a
great,
a
great
way
to
kind
of
reach.
Each
other's
audiences
as
well
and
I
have
reached
out
to
a
whole
bunch
of
the
people
we've
done
podcasts
with
before
about
doing
back,
drop.
Podcast
about
you
know
backdrop:
one
year
later,
1.3
release.
What's
happened
to
our
community.
A
What's
going
on
with
can't
read
like
all
the
questions
that
were
kind
of
a
up
a
near
year
ago
we
did
our
last
blog
posts,
now
kind
of
happy
answer
to
fast
forward,
and
so
far
we've
gotten
a
really
good
on
response
from
all
of
the
podcast
people
pretty
much.
Everyone
has
said
yes,
they're
interested
in
doing
it
and
we're
just
trying
to
figure
out
when
so
I
think
that
that
sounds
really
good.
I
would
like
to
say
that
it
would
be
gratefully
to
get
more
people
involved
in
those
podcasts
too.
A
Some
of
the
podcast
I
think
are
going
to
be
like
a
backdrop
for
sister
blade
kind
of
compare
contrast,
which
is
also
kind
of
fascinating
to
me,
because
I
don't
really
know
what's
going
up,
but
what's
been
going
on
in
enjoyed
so
much
since
its
come
out
like
I,
don't
know
how
they're
handling
their
new
release
schedule
and
I'm
really
curious
to
see
people
who've
been
using
Drupal
8,
like
what
their
perspective
is
so
I
think
that
would
be
kind
of
a
fun
like
I'll
show
you
your
so
you
show
me
mine,
kinda
podcast
situation,
where
we
can.
A
We
can
do
a
little
like.
Oh
yeah,
well
I've
got
lots
of
tabs
a
pouch.
Let's
test
soooo
McKinley,
you
know
see
how
it
works,
so
fun
things
afoot
in
terms
of
marketing,
which
I
think
will
be
really
great.
Let's
see
we
have
oh
yeah,
so
we've
also
been
talking
to
Todd
Tomlinson,
who
wrote
the
first
ad.
B
A
Backdrop
or
upgrading
from
backdrop
up
getting
from
triple
the
backdrop
book
which
came
out
in
December
he's
working
on
a
intro
to
backdrop
book
as
well,
and
so
he
sent
us
an
email
on
earlier
this
week
with
an
outline
saying
like
Hazel's
I'm
planning
doing,
is
there
anything
I've
missed
like
I'd
love
to
have
your
eyes
on
it,
and
it
looks
fantastic,
so
I'm
really
excited
to
see
that
coming
out.
It
should
be
out
q2.
So
keep
your
eyes
open
for
new
backdrop
book
coming.
So
that's
super
exciting.
A
All
right.
Let's
see,
shall
we
talk
about
a
backdrop
itself
so
exciting
so
backed
up
one
two
three
came
out
and
that
included
a
whole
bunch
of
kind
of
cute
issues
that
we've
been
waiting
on.
None
were
super
urgent,
but
it
had
a
whole
bunch
of
cross
ports
from
triple
seven
I.
Think
in
it,
as
well
as
a
bunch
of
lower
priority
bug
fixes
so
mate.
You
did
that
I.
Think
two
weeks
ago
was
the
last
two
weeks
ago,
which
is
great,
and
so
now
we've
got
another
another
set
another.
A
What
is
that
called
bug-fix
release,
124,
which
will
come
out?
The
same
time
as
130,
that's
what
we're
guessing
and
so
all
of
the
the
fixes
for
both
of
those
will
be
together,
and
we
have
130
coming
out
tomorrow,
which
is
super
exciting.
We've
made
a
ton
of
progress
on
a
whole
bunch
of
stuff
that
was
in
our
queue
for
130
native,
been
doing
all
the
merging
on
the
city.
When
we
turn
this
back
over
to
you
to
talk
about,
especially
the
super,
exciting
blocks
and
layouts
progress,
yeah.
B
Sure
boy
there's
been
so
much
stuff,
actually
I,
don't
even
think
it's
on
this
list,
I
think
it
must
have
gotten
removed,
but
transliteration
I
guess
look.
Did
we
put
them
before
this
last
week
by
any
way,
transliteration
is
in
core.
It's
really
exciting,
including
integration
with
machine
names.
That'll
make
internationalized
or
non
English
actually
doesn't
need
to
be
international.
B
Of
course,
if
you're
in
a
place
that
has
a
node
in
which
you
can
display
those
fields
in
the
first
place,
so
those
fields
are
not
or
those
blocks
are
not
shown
on
the
default
layout.
You
need
to
actually
make
a
layout
at
node,
/,
node
ID,
and
then
it
will
make
those
blocks
available,
which
is
really
cool.
B
Building
on
some
of
the
functionality
that
we
added
a
couple
weeks
ago,
where
blocks
were
moved
from
being
contents
into
being
configuration
thanks
to
Mike
persistence.
There
we
expanded
that
made
it
so
that
now
from
the
layout
cui,
you
can
add
a
custom
text
block
directly
from
the
UI.
So
you
don't
need
to
go
and
add
a
custom
block
first
and
then
and
then
add
it
to
the
layouts
you
I
like
hopping
around.
You
know
the
classic
kind
of
like
pogo
sticking
behavior
that
you
get
in
Drupal
all
the
time.
B
You
can
now
add
a
custom
text
block
directly
from
within
the
layouts
UI,
which
is
awesome.
However,
the
weird
thing
right
now
is
that
those
text
blocks
are
currently
stored
in
the
layout
config
and
not
in
the
custom
block
config.
Basically,
they're
not
reusable,
but
we
have
an
issue
to
make
it
so
they
toggle
in
between
them
at
issue,
15
15,
which
basically
makes
it
so
that
you
can
take
a
text
block
check.
B
Little
boxes
just
make
it
reusable,
and
then
it
becomes
stored
in
its
own
config
file
and
can
be
reused
multiple
times
between
different
layouts.
Anyway,
it
sounds
complicated,
but
it's
in
practice.
It's
really
simple
and
straightforward.
It's
just
like
I
want
to
add
a
custom
block.
Bam,
add
a
custom.
Add
the
custom
block.
Oh
I
want
to
make
it
reusable
check
the
box.
It's
awesome,
I'm
really
excited
about
it.
B
Okay,
let's
see
so
that's
some
really
exciting
things
over
in
layout
lands
text
editor
follow-ups.
We
did
actually
merge
an
issue
issue
this
past
week,
just
to
clean
up
filter
tips
a
little
bit.
It's
not
as
elaborate
as
some
of
our
plans
for
filter
tips,
but
those
other
issues
would
probably
just
get
kicked
to
14,
which
is
fine.
B
Let's
see
we're
trying
to
work
on
this
issue
for
a
notification
icon
over
in
639
and
we've
had
three
different
approaches
to
it.
Actually,
more
than
that,
if
you
count
the
ones
that
we
didn't
write
code
for,
we've
had
several
approaches
to
making
it
so
that
we
don't
need
to
display
a
giant
red
error
at
the
top
of
every
other
page
in
the
admin
section.
B
When
there's
a
site
status
problem,
like
you
know,
there's
a
security
update
or
your
files
directory
isn't
writable,
rather
than
spewing
giant
red
errors,
all
over
the
place,
we're
going
to
put
a
little
a
little
red
dot
in
the
admin
bar.
Basically
saying:
hey,
there's
prom
with
you
site.
If
you
click
it,
it
takes
you
to
the
to
the
status
report.
B
That
issue
keeps
getting
reduced
and
reduced
in
scope
to
the
point
that
now
we
actually
have
something
that
we
can
implement
or
we
have
already
implemented,
but
it
just
needs
to
be
updated
for
the
latest
code
for
the
latest
feedback.
I
should
say
so
that
that
issue
just
needs
to
re-roll
to
address
some
minor
feedback,
and
then
we'll
probably
see
that
in
later
today
or
tomorrow,
before
the
release,
which
is
exciting
project
browser
today,
I
moved
that
into
the
one
dot
for
milestone.
B
So
I
moved
it
out
of
being
something
that's
tomorrow
into
something
that
is
probably
four
months
from
now.
The
project
browser
implementation
actually
works.
Pretty
awesome,
like
you,
can
find
a
project
you
can
just
quick
it
and
then
it
installs
it.
It
actually
really
is
a
pretty
slick
process
and
overall,
like
a
major
improvement.
B
B
A
B
A
little
bit
weird
that
you
would
need
to
have
something
that
was
telling
you
new
versions
of
modules
are
always
available
in
order
to
install
modules
a
little
bit
weird,
so
it's
possible
to
separate
those
two
that
might
be
great
to
do.
Anyway.
That's
issued
1399,
that's
been,
kicked
the
one
dot
for
so
hopefully
we'll
see
that
in
the
next
release
it
is
really
awesome
and
there's
been
a
lot
of
great
work
on
it
and
we're
hoping
to
see
it
in
the
next
release.
B
B
It's
pretty
unlikely
that
we'll
get
fixed
before
tomorrow,
but
it's
not
difficult.
It
just
is
it's
like
all
of
our
other
conversions.
It
just
takes
a
little
bit
of
effort
and
some
planning
because
you
have
to
read
an
upgrade
pad,
but
it's
not
not
particularly
difficult.
Maybe
I
don't
we'll
see
it
before
tomorrow,
but
one
can
always
hope.
C
B
Just
for
comparison,
I
found
this
interesting.
I
was
reading.
This
is
probably
I.
Don't
know.
Nine
months
ago,
I
was
reading
up
on.
Word,
presses,
really
cycle
documentation
about
how
they
manage
their.
You
know
their
new
versions
when
they
come
out
and
it's
pretty
awesome
how
straightforward
they
are
even
today
about
you
know
the
the
releases
come
out
like
clockwork,
that's
for
certain,
and
then
they
say
we
usually
make
a
bug-fix
release
two
or
three
days
after
the
last
release
to
fix
all
the
stuff
we
broke.
B
C
Bro
these
were
at
least
or
at
least
come
up
with,
like
the
types
of
bugs.
We
definitely
shouldn't
do
in
like
any
sort
of
upgrade
path.
It's
like
modifying
data
and
stuff,
like
that.
We
should
definitely
have
more
time
and
effort
to
check
just
because
some,
some
bugs
we
may
can't
be
fixed
after
the
fact.
Yes,.
B
That
is
true:
yeah
data
manipulation
right
before
not
the
greatest
idea,
yeah
other
things
like
yes,
CSS
fixing
like
wes
is
talking
about.
We
can
actually
fix
those
in
like
there's
no
rush
to
make
to
fix
a
CSS
bug
or
something
I
thought
that
we've
had
lingering,
because
we
can
always
fix
it.
You
meet
like
anytime,
you
know
it
doesn't
need
to
get
into
the
next
minor
release
it
can
be
fixed
in
and
in
any
bug
fix,
release
that
happens
periodically.
B
We
haven't
been
very
diligent
about
removing
the
things
from
the
1.3
list
that
aren't
going
to
make
it
yet,
there's
still,
it
looks
like
a
about
10
items
or
maybe
a
dozen
that
that
are
slated
for
13
that
are
in
either
and
needs
work
or
need
to
review
status
or
sometimes
not
even
sometimes,
work
hasn't
even
begun
on
them.
What
we
usually
do,
after
after
minor
release
happens,
is
we
allow
stuff
to
be
kicked
to
the
next
minor
release
once
so?
B
If
it
was
slated
for
13
and
didn't
make
it,
it
gets
moved
to
one
dot
for,
but
if
one
that
for
comes
around
and
the
feature
still
hasn't
been
implemented,
we
don't
move
it
to
1
dot
5.
We
actually
just
say
this.
The
future
of
this
thing
is
not
certain
enough
that
it
is
slated
for
the
next
release
that
we
just
move
it
back
into
the
general
one
dot
X
pool
until
enough
momentum.
This
built
up
around
it
that
we
can
feel
confident
about
its
release.
Date.
B
B
Anything
else,
I'm
123,
now,
ok,
one
dot
for
the
next
minor
release
is
going
to
be
May,
15
2016
four
months
from
now
and
our
primary
goals
for
that
release.
Our
references,
module
we'd
like
to
solve
once
and
for
all
our
references
problem.
Right
now
we
have
a
contributor
reference
module
and
then
in
core
of
course,
we
have
the
term
reference
module.
That
is
part
of
just
the
times.
B
Not
me
module
and
we'd
like
to
consolidate
all
of
those
different
ways
of
referencing
content
into
a
single
references,
module
that
lives
in
core,
so
that
people
won't
need
to
kind
of
have
this
divided
between
which
references
module
do
I
youth
days
and
any
reference
do
I
use.
No
reference
do
I,
use
some
other
kind
of
reference
module
and
so
we're
hoping
that
we
can
include
in
one
dot
for
a
core
references,
module
and
I.
B
Think,
as
part
of
that
will
also
need
to
figure
out
some
battle
plans
for
upgrade
pads,
whether
that
is
a
contributing
writer
that
can
do
those
upgrade
paths
or
whether
the
data
schema
is
identical
to
entity
reference
that
it
can
potentially
just
build
off
of
those
existing
tables.
There's
a
lot
of
things
to
consider
there
that's
issue.
1301
we'd,
also
like
to
figure
out
something
that.
C
B
B
C
B
Also,
that
would
be
fantastic
to
have
have
your
hand
in
that
Mike
yeah,
with
our
new
nadh
guidance
in
core
the
references
macho
entity.
Reference
in
Drupal
7
is
dependent
on
entity
module,
but
that
really
probably
is
not
necessary
in
our
situation,
because
all
of
the
abstractions
that
are
necessary
are
already
in
core
like
a
way
of
getting
the
URL
for
each
type
of
reference
or
the
type
or
the
bundle.
B
All
of
that
stuff
is
all
in
eric
lee
accessible
across
the
board
impact
drop,
which
is
nice
because
it
wasn't
in
Drupal
7,
but
also
other
features
redirect
module.
Something
like
redirect,
we'd
like
to
have
core,
primarily
because
we
have
Pat,
auto
and
core
and
right
now,
when
you
create
a
new
path,
I
can
be
changed,
the
title
of
something
it
also
updates.
It's
pat,
alias,
but
right
now
the
only
options
for
what
to
do
with
the
old,
alias
are
really
poor.
B
So
that's
poor
behaves
reasonably
out
of
the
box,
rather
than
this
bizarre,
like
it'll
delete
your
old,
alias
when
you
create
a
new
one,
which
is
just
silly,
let's
say
which
lists.
Maybe
I
shouldn't
call
a
wish
list,
but
we'd
love
to
have
a
new
front.
End
theme
in
backdrop
as
soon
as
possible,
and
so
we
have
it
slated
for
one
dot
for
its
issued
1361
and
our
hope
there
is
that
someone
can
write
up
a
really
badass
can
tripping
and
then
everyone
will
love
it
and
then
we'll
move
it
into
core.
B
B
There
was
a
lot
of
talk
about
using
the
radix
layouts
at
one
point:
let's
see
this
is
this
link
isn't
correct,
but
exactly
if
we
use
the
radix
layouts
or
some
other
layouts,
just
having
more
flexibility
in
core
to
position
to
position
your
blocks
is
something
that
we're
interested
in
and
so
there's
a
lot
of
banter
going
back
and
forth
about
what
that
looks
like
whether
it's
radix
or
whether
it's
something
else
in
the
issue
queue
right
now.
B
B
Let's
see
and
that's
it,
we
have
as
always,
continual
you
x,
+
DX
improvements,
user
experience
and
developer
experience,
improvements
that
are
just
tagged
with
square
brackets
and
the
issue
and
the
issue
title
and
those
we
liked
to
try
to
pay
particular
attention
to,
because
really
I
mean
like
this
last
really
showed.
There's
so
many
areas
that
we
can
just
improve
on
what
we
have
that
improving
on
what
we
had
have
is
just
like
such
a
priority
force
/,
adding
in
like
yet
another
module
adding
in
yet
another
module.
B
Sprints
sprints
today
is
the
last
day
before
the
release
of
backdrop,
1.3
point
0
and
so
all
day
today
we're
going
to
be
working
as
hard
as
possible,
reviewing
the
things
that
are
nearly
done
getting
the
last
things
merged
in
there
polishing
the
things
that
we
have
for
the
release
tomorrow.
If
history
is
any
indicator,
the
release
tomorrow,
probably
will
be
later
in
the
day.
Just
I.
B
So
hang
out
with
us
today
will
be
an
IRC
impound
backdrop
on
freenode.
We
also
started
using
git
er.
If
you
visit
get
on
IM
/
backdrop,
you
can
join
in
to
our
get
er
channel
and
that
can
be
useful
because
you
can
get
pinged
any
time
like
when
you're
offline
to
continue
an
email,
a
handy
alternative,
if
you're
not
into
IRC.
B
Let's
see-
and
we
have
a
reddit
channel,
the
reddit
channel
really
is
just
for
a
general
discussion
forum.
If
you
want
to
chat
about
dr.
up
in
general
or
discussions
that
are
happening
on
the
web
about
backdrop
or
not
backdrop,
the
other
things
that
we
could
derive
inspiration
from
or
something
like
that
share
a
link
on
Reddit
and
then
we
can
discuss
it
there,
let's
see
Jem.
Can
you
pick
up
the
remaining
the
upcoming
events?
All.
A
Right,
so
we
have
obviously
this
meeting
every
thursday
at
1pm
california
time
we
have
a
design
call
or
you
talk
about
the
design
lated
thanks
for
working
on
a
perfect
job,
every
other
Thursday
in
our
earlier
at
noon.
California,
time
pacific
time
and
both
of
those
calendars
are
available.
If
you
want
to
get
the
ital
feet
from
backdrop,
CMS
org,
slash,
contribute
upcoming
backdrop,
camps
and
conferences.
A
We
currently
are
still
doing
backdraft
talks
at
drupal
events
when
drupal
organizers
asked
us
to
come,
speak
to
their
audiences
about
backed
up
now
in
the
calendar
we
have
a
Santa
camp
which
is
at
the
end
of
februari,
where
we're
also
going
to
be
doing
our
first
full
day
back
draft
training.
We
have
a
drupalcamp
Utah,
which
is
the
beginning
of
March.
They
have
specifically
asked
for
someone
to
come
and
speak
about
backdrop
and
I've
called
it
on
the
list
here:
drupalcamp
chicago
but
I
think
you're
right.
A
It's
mid
camp
west,
it's
in
Chicago,
but
it's
not
actually
drupalcamp
Chicago.
It's
mid
camp
Midwest
drupalcamp,
which
is
March
19
to
20
second
and
webb,
says
he's
submitted,
there's
a
to
talks,
mid
camp
just.
A
So
that's
coming
up
as
well,
and
so
we
are
exiting
crazy
holiday
travel
season
and
entering
crazy
I
camp
travel
season,
so
I
would
expect
to
see
that
was
starting
to
grow.
There's
a
bunch
of
other
things
that
are
be
going
to
be
going
on
this
year.
I
know
we
have
also
volunteered
to
attend
silicon,
which
is
going
to
be
in
Denver
in
the
end
of
May
or
early
June.
I'm,
not
sure
they
have
a
date
yet
for
that.
A
But
we
have
the
nest
to
attend
that
so
we'll
definitely
be
there
because
and
then
I
think
we're
going
to
be
attending
on
drupalcon,
North
America,
but
I.
A
Don't
think
we're
going
to
be
doing
any
talking
about
backdrop
there
at
least
not
officially
giving
a
session
and
but
it's
always
good
to
go
there
and
talk
to
people
while
what's
going
on
in
the
world
of
drupal
anyway,
so
we'll
be
around,
even
though
not
officially
presenting
we'll
have
dragon
t-shirts,
though,
for
anyone
who
wants
one
so
we'll
just
leave
that
out
there
and
then
yes
also
the
book.
A
If
you
want
a
book
on
how
to
upgrade
from
purple
to
backdrop
Todd
Tomlinson's
luck
is
available
on
a
press,
I
think
Amazon,
Web
site
is
still
broken.
That
thinks
it's
coming
out
next
year,
I
reported
it
to
Amazon
on
twitter,
but
I'm
not
sure
the
amazon
twitter
account
has
anything
to
do
with
the
actual
working.
So
it's
the
episode.
D
A
So
close
eee
that
actually
fixes
it
and
then
another
backdrop
book
is
coming
out,
q2
and
so
I
guess
that's
sometime
between
march
and
june
and
that
I'll
just
be
beginning
think
it's
called
beginning
backdrop
or
beginning
backdrop:
CMS,
that's
exciting
too
alright!
Well,
that's
the
end
of
our
official
agenda.
C
B
B
C
And
we
probably
want
to
do
that
as
the
conversion.
We
probably
want
to
do
that
as
like
copy.
This
reusable
block
for
like
customized
that
were
over
I'd
adore
like
flown
it
or
something
like
that,
rather
than
rather
than
convert
it
from
the
custom
block
to
the
layout
black
Leslie
tested,
it's
not
using
any
other
anyway.
Yeah.
B
C
B
I
did
make
them
more
consistent
with
each
other,
like
I
said:
I
named
them
titles
in
both
places
and
things
like
that.
But
sometimes
it's
a
little
bit
weird,
because
the
block
implementation
is
consistent
with
a
hook
block
info
right
like
it.
The
admin
label
is
actually
just
as
the
machine
key
info
right,
because
that
corresponds
with
hook,
block
info
and
I.
Think
from
a
compatibility
standpoint,
that's
required.
B
B
I'd
actually
say
the
one
thing
that
oh
gosh
I
went
back
and
forth
on
this
right
now
the
body
of
a
block
is
in
the
config
file,
its
extra
stored
as
two
separate
keys,
its
body
and
then
to
subkeys,
underneath
that
value
and
then
format,
because
it's
a
it's
a
right,
filtered
HTML
element
and
I
couldn't
decide
if
I
wanted
to
make
those
into
like
flatten
it
in
the
config
file
or
not
like
it
seems
like
flattening.
It
would
be.
You
know
a
reasonable
thing
to
do
so
that
it
doesn't
have
this
odd.
A
C
So
so,
I
actually
actually
unflattering,
flattened
but
I
unflattering
the
form
to
when
you,
when
you
post
the
form
the
field
body
comes
back
with
the
two
sub
things
of
value
in
the
format
so
sort
of
making
the
config
match
the
form
architecture
of
the
forum
configuration
and
how
it
is
elsewhere
seemed
like
a
good
idea.
I
also.
A
Think
that's
good,
because
that
way,
if
somebody
changes
their
text
format,
you
get
the
correct
output
if
you're
running
that
conversion
through
format
text
every
time,
whereas
if
you
flattened
it
when
it
was
saved
and
then
they
change
their
text
format
and
you
just
retrieve
the
string
of
text,
you
might
be
revealing
tags.
This
should
be
stripped.
Oh.
B
B
We
would
we
would
store
them
next
to
each
other
in
the
root
of
the
config
file
and
the
the
inconsistency
there
while
I'm
bringing
this
up
is
because
the
text
block
patch
flattened
it,
but
the
custom
block
one
did
not
so
in
the
layout
files,
its
flattens,
but
when
it
gets
moved
to
a
custom
block,
it's
not
fun,
and
so
it's
like.
Maybe
we
should
update
text
blocks,
I.
Think
it's
within
our
ability
to
do
that.
Still
yeah,
I'm
going.
C
To
make,
I
was
going
to
switch
text
box
to
match
the
things
that
actually
have
some
like
change.
The
code
change
the
pull
request,
but
I
didn't
get
a
chance
to
do.
Any
tests
would
and
actually
posted
so
yeah.
The
other
thing
is
we're
we're
exactly
bhosle.
Where
does
the
conversion
that
you
may
live
from
layout
blocks
to
custom
blocks
which
which
module
that
the.
B
C
B
Yeah,
so
one
of
the
reasons
that
it's
only
one
way
right
now
is
because
custom
blocks
are
still
using
the
old
hook
block
system,
with
hook,
block,
configure
and
stuff
like
that.
In
order
to
do
the
conversion,
we
need
a
submit
handler
on
the
block
form
and
so
text
blocks
the
new
ones
that
are
added
in
layout
module.
They
can
be
made
without
custom
block
module,
turned
on
at
all
they're,
just
a
new
right.
B
You
know,
stored
in
layout
module
configuration
thing
and
so
they're
using
the
new
class
based
approach
which
lets
you
do
not
only
the
form
but
also
validate
and
submit
handler
and
what
what
they
do.
It
were.
What
it
does
is
in
the
submit
handler.
It
changes
the
block
property
for
a
plug-in
and
so
a
plug-in
identifies
what
module
is
currently
responsible
for
providing
that
block
and
then
and
then
layout
module
now
just
identifies.
B
If
the
plug-in
has
changed,
then
it's
clones,
the
block
and
then
makes
a
new
instance
of
the
block
that
is
the
different
type
that
matches
the
new
plug-in.
So
in
the
submit
handler,
it's
really
the
block.
The
text
block
basically
just
says
my
plugin
has
changed
and
then
layout
module,
and
it
sees
that
in
its
own,
submit
handler
says:
oh
I
need
to
actually
delete
this
block,
create
a
new
block
of
a
different
type
and
then
put
it
in
the
same
place.
B
C
I'll,
take
a
look
at
that
also.
This
is
sort
of
the
most.
The
one
thing
that
I
wanted
to
change.
I
didn't
get
a
chance
to
is
with
custom
blocks,
and
maybe
some
helpers
notice
this
to
custom
blocks,
as
they
are
right
now,
when
you
edit
them
in
the
layout,
you
can
edit
the
body
obviously
and
that
affect
everywhere.
C
The
block
is
used
and
you
can
change
the
and
you
can
change
the
admin
title
of
the
block
and
that
gets
changed
everywhere,
but
you
can't
actually
change
the
default
display
title
all
you
can
do
is
override
it.
So
the
only
way
if
you
have
like
a
optus
labeled
contact,
the
only
way
to
change
that
to
contact
us
is
to
go
into
the
block
interface,
because
the
default
title
isn't
listed
in
the
pop-up
layout
block
editor.
So
even.
C
Can
edit
two
of
the
three
things
like
sort
of
like
system-wide,
one
of
them
just
isn't
available
in
that
interface
and
I
was
going
to
add
it.
But
then
this
sort
of
there
was
some
interactions
with
the
the
the
layout
module.
Also
calling
its
overridden
title
just
title
so
I
mean
it
seems
like
if
you
should
be
able
to
change
the
content
and
change
the
label
of
a
custom
block
any
where
you
shop,
stable
change
the
default
title.
So
that's
that's
need
to
probably
be
done,
I'm,
not
sure.
C
B
B
If
you
select,
you
know
when
you
edit,
the
block,
the
second
then
be
the
display
title
is
at
the
top.
The
ayman
label
stays
actually
down
at
the
bottom
when
you're
in
the
layout
dialog,
because
it's
unlikely
you're
going
to
change
the
admin
label
from
within
the
layout
you
life,
but
it
is
possible.
Well,
my.
A
Recommendation
was
also
to
move
that
admin
label
always
to
the
bottom,
because
it's
the
least
important
element
on
the
page
like
when
you're,
adding
a
block
you
care
about
what
its
title
is
you
care
about?
What
people
see
you
don't
really
care
about
in
labels
and
have
that
element
very
top
is
like
completely
counterproductive,
because
people
always
get
confused
about
what
an
admin
label
is
anyway,
when
they're
thinking
I'm
going
to
add
a
block.
I
know
people
as
they
type
that
in
first
and
so
that
shouldn't
be
the
I'm
in
label
field
anyway.
A
B
It's
actually
in
the
issue
you're
going
to
have
to
be
pretty
quick
about
it,
because
there's
no
pause
button
on
animated
gifts,
but
there's
an
animated
gif
and
the
issue,
its
issue,
15
15,
and
it
runs
through
the
entire
process
of
making
a
custom
text
block,
checking
the
reusable
checkbox,
adding
in
an
admin
label
going
to
the
admin
configuration
for
the
list
of
all
custom
blocks
and
then
editing
it
and
then
seeing
it
on
the
funny
that
runs
through
the
whole
thing.
But
yeah
right
now,
I
left
the
the
custom
block.
B
Admin
form
the
standalone
form
for
editing
a
block
is
unchanged.
It's
exactly
the
same
as
it
was
before.
But
if
you're
within
a
dialogue,
it
moves
the
label
to
the
bottom
to
be
consistent
with
how
the
text
block
works,
because
the
text
block
the
checkbox
are
make
reusable
and
the
admin
level
at
the
bottom,
and
so
it
makes
it
so
that
when
you
switch
between
one
type
and
the
other
type,
it
looks
like
it's
still
the
same
thing.
B
I
am
so
excited
about
them.
I
think,
once
we
add
relationships
which
is
the
last
kind
of
silver
bullet,
actually
the
relationships
and
the
ability
to
embed
an
arbitrary
entity
which
blurs
the
line
a
little
bit
between
your
structure
and
our
content,
but
but
those
two
things
like
really
just
turn:
it
turns
it
into
something
like
truly
amazingly
powerful
right
now,
it's
just
it's
just
better
and
it's
more
convenient
and
it's
easier
and
it's
slightly
more
powerful.
But
it's
not
like
OMG.
You
know
limitless
it's
not
quite
panels,
but
we're
getting
there.
B
For
I
would
say
for
a
call
to
action
for
tomorrow,
if
anybody's
got
time
on
their
hands
today
and
tomorrow,
don't
just
look
at
the
one
dot
3
list,
because
the
one
dot
3
list
is
a
little
bit
weird.
But
look
at
the
wound
on
3
lists
and
the
in
combination
with
the
needs
of
work
tag.
The
pr
needs
work
tag,
because
those
are
the
things
that
are
most
likely
to
still
make
it
before
the
release
tomorrow,
because
they're
all
really
pretty
close.
A
I've
been
handling,
it
is
a
make
a
new
poll
request
and
then
close,
therefore
request
but
make
sure
everything
is
linked
together
and
that
you
know
you
guys.
Aren't
it's
really
hard
to
not
work
on
same
thing
at
the
same
time,
but
if
you're,
like
I'm
I,
want
to
try
this
to
get
like,
add
a
comment.
It's
like
I'm
gonna
make
a
new
PR
and
then,
when
you
make
a
new
pair
close
there's,
then
that
way
they
can
come
see
what
you're
doing
and
you
can
kind
of
trade.
A
C
B
B
But
anyway,
if
your
pull
request
has
been
closed,
don't
fret
about
it
just
file
a
new
one
like
it.
You
really
just
go
to
your
gear,
individual
repository
and
create
pull
request
a
second
time
and
just
make
a
new
one.
Once
your
pull
request
has
been
closed
force
pushing
to
it
apparently
will
not
reopen
it.
So
you
actually
need
to
make
a
new
poll
request,
but
we
like
to
treat
forward
to
us
in
the
same
way
as
patches.
That's
like
if
your
poll
request
just
becomes
out-of-date
or
closed
just
make
a
new
one.
B
It's
the
equivalent
gun
triple
that
org
of
just
saying
I
made
a
new
patch
right
so
for
requests
make
liberally
if
needed:
okay,
yeah,
usually
what
we
end
up
doing
is
we
take
the
last
pull
request
and
then
we
copy
it
down
and
then
we
modify
it
and
then
we
file
it
as
a
new
poll
request,
so
yeah
maintaining
attribution
in
that
is
a
little.
That
process
is
also
a
little
bit
messy
I.
B
Okay,
oh
I,
wanted
to
add
in
I,
threw
it
into
the
chat,
but
that
backdrop
CMS
migrating
from
Drupal.
The
backdrop
book
is
actually
now
fixed
on
amazon
com,
so
you
can
finally
buy
it
on
Amazon,
which
is
nice,
so
it's
available
immediately.
Apparently,
you
can
even
buy
used
versions
of
it
already,
I'm
not
sure
where
those
came
up,
but
apparently
people
have
already
finished
migrating
their
sites
and
are
ready
to
ready
to
be
ready
to
resell
their
book.