►
Description
Today’s development agenda: http://bit.ly/1mmCqxp
A
B
A
It
is
january
7th,
welcome
to
the
backdrop
weekly
hangout
we're
going
to
do
a
quick
rundown
through
our
agenda
this
week
we
have
so
many
fantastic
things
that
have
been
happening
recently
that
I'll
try
to
not
linger
on
the
things
that
are
less
important,
so
just
to
start
off
with
general
announcements.
If
you
want
a
backdrop,
t-shirt
or
hoodie,
if
you
make
a
donation
to
the
backdrop
foundation
on
our
website
at
backdrop,
cms.org
contribute
we'll
mail
them
off
to
you.
We've
had
two
orders
recently
and
both
of
them
were
sent
out
last
week.
A
So
thank
you
guys
for
supporting
backdrop,
and
I
hope
you
enjoy
your
warm
adorable
clothing.
We
don't
have
any
announce.
Oh
wait,
php
storm
licenses.
We
have
new
licenses
from
the
php
storm
books
that
should
last
an
entire
year.
If
you're
interested
in
having
one
you
need
to
be
a
member
of
the
backdrop
contributed
developer
community,
which
means
you
have
to
join
the
backdrop
contrib
group
on
github
there's
an
application
for
process
for
that.
A
Just
to
make
sure
you
guys
understand
how
code
is
managed
at
backdrop
being
slightly
different
than
how
it
was
managed
at
drupal.
That's
where
you're
coming
from,
if
you
aren't
creating
code
but
still
want
to
join
the
community
and
want
to
contribute
and
want
to
volunteer
to
maintain
modules,
themes
or
layouts,
that's
a
good
way
to
get
involved.
I
know
I've
got
a
couple
a
couple
too
many
projects
that
I'm
currently
maintainer
on
I'd
love
to
have
coal
maintainers.
A
So
if
you're
interested
in
stepping
up
and
helping
with
that
issue,
queue
review
process,
that's
a
great
way
to
get
involved
without
having
to
create
any
code
yourself.
So
you
can
send
us
an
email
info
backdrop
cms.org.
If
you're
interested
in
one
of
those
licenses,
we
can
help
get
you
through
the
github
contributor
approval
process,
it's
pretty
straightforward
and
and
get
you
that
copy
of
phpstorm.
B
B
That's
two
new
projects
since
last
meeting
116
projects
with
official
releases
on
backdrop,
cms.org,
that's
one
new
since
last
meeting,
153
total
releases,
so
two
new
releases
since
last
meeting
and
43
total
members
of
the
backdrop
contrib
group,
we
don't
have
any
new
contrib
authors
since
last
week,
but
we
have
three
applications
that
are
all
going
to
be
done
pretty
much
immediately.
I
think
so.
There's
giffad,
who
did
an
amazing
job
on
a
bunch
of
modules.
B
He
did
four
or
five
or
six
geo-related
modules,
geofield
geocoder
geo
everything,
and
so
that
would
be
really
exciting
to
see
those
come
over
in
the
near
future.
Dan
boulay,
who
supported
the
unsubscribe
module,
he's
also
been
really
active
in
the
core
queue
doing
lots
of
amazing
stuff
there
and
dire.
Who
is
also
in
this
meeting
evangelist.
Hey,
welcome,
glad
to
see
you
and
welcome
to
our
meetings,
and
so
we're
really
excited
to
have
those
new
contrib
authors.
B
If
you're
interested
in
joining
the
contrib
group,
you
can
do
so
at
github.com
backdrop
dash,
ops,
slash
contrib
and
that's
where
we
go
through
the
process
of
taking
a
look
at
any
modules
that
you've
written
or
reported
for
backdrop
cms.
B
We
review
them
and
then,
if
they
meet
basic
criteria,
then
we
grant
you
access
to
the
contrib
group
and
then
you
can
import
and
add
and
contribute
to
modules.
All
that
you
like,
within
that
group
and
being
in
the
group,
has
some
advantages.
B
Like
jen
mentioned,
we
can
get
you
a
license
to
php
store
if
you're
in
the
group,
but
it's
also
the
only
way
right
now
for
modules
to
end
up
on
backdrop,
cms.org
that
when
you
publish
a
module
within
the
backdropkinstrip
group,
it
automatically
synchronizes
over
to
backdropcms.org,
once
you've
made
an
official
release
of
that
project
on
github,
so
really
exciting
lots
of
great
progress
moving
along
in
the
contrib
world,
as
well
as
the
core
space,
and
we're
really
excited
to
welcome
our
new
contributors
and
to
see
more
in
the
future.
B
Let's
see
jen
added
a
new
item
in
here
last
week
we
yeah
last
week.
Six
days
ago.
We
enabled
the
ability
to
register
and
sign
up
for
accounts
on
backdrop.
Cms.Org
there's
not
a
whole
lot.
You
can
do
yet.
You
can
just
sign
in
and
update
your
profile
basically,
but
we're
hoping
to
expand
that
to
more
functionality,
integrating
it
with
github
and
making
it
so
that
people
can
actually
manage
things
like
our
news
posts,
the
projects
that
they
manage.
B
All
of
those
sorts
of
things,
so
we'll
be
looking
into
expanding
that
functionality
on
backdrop
cms.org,
but
for
now
you
can
go
and
register
an
account
and
there
have
been
24
registrations
since
that
was
opened
on
the
1st
of
january
and
that's
really
exciting
to
see
new
members
coming
in.
It's
also
interesting
to
see
that
it's
not
a
one-to-one
overlap
between
art
and
trib
and
core
developers.
You've
got
a
bunch
of
kind
of
lurkers.
B
I
guess
that
they've
clearly
been
around,
but
they
haven't
been
participating
in
development
directly,
but
we're
really
excited
to
see
excited
to
see
them.
B
Okay,
let's
go
right
into
infrastructure
infrastructure.
We
talk
about
the
things
that
are
around
the
software
that
support
the
project,
mostly
backdrop
cms.org
and
related
things
around
it.
B
Let's
see,
let's
glaze
over
this
this
week,
update
checking
that's
the
thing
that
lets
it
so
that
when
a
new
version
of
a
module
comes
out
or
a
new
version
of
backdrop,
cms
itself
comes
out,
update
module
tells
you
that
the
new
version
is
available.
That's
all
been
working.
We
have
a
pull
request
to
fix
the
analytics
on
backdropcms.org
that
will
make
it
so
that
we
can
accurately
count
how
many
backdrop
websites
are
out
there.
B
At
least
they
have
update
module
turned
on
as
well
as
which
modules
are
running
on
each
site.
That's
pull
requests
number
nine
in
project
module,
it's
actually
a
bug
in
project
macho
right
now,
but
we're
really
close
to
having
that
fixed.
B
Let's
see
after
we
have
that
fixed,
we
would
like
to
make
charts
of
usage
data
on
backdrop
cms.org
and
start
expanding
that
data
that
we
collect
to
be
more
than
just
the
modules
that
are
enabled,
but
also
include
things
like
which
features
are
being
used.
Maybe
things
like
you
know
how
many
layouts
people
have
on
the
site
or
which
layout
templates
they're,
using
whether
or
not
their
site
supports
clean
urls?
B
That
sort
of
thing
that
will
help
us
make
better
decisions
in
the
future
about
which
features
to
keep
and
which
ones
to
scrap
josh.
For
backdrop,
we've
had
a
working
prototype
of
brush.
It's
a
drush
extension
that
you
can
plop
into
your
drush
8
installation,
and
it
will
make
it
so
that
josh
can
identify
backdrop
and
use
some
basic
commands
like
just
cc
all
and
rush
updb,
and
things
like
that,
and
there
is
currently
a
pull
request.
B
Serendipity
jeff
thanks
for
taking
a
look
at
dress
this
past
week,
he's
got
josh
dl
working
for
for
backdrop
and
he's
filed
a
pull
request
against
that
to
the
sandbox
drush
extension.
The
sandbox
right
now
is
currently
just
located
at
github.com,
quick
sketch,
slash
backdrop
dash
drush
and
that's
for
now,
where
we're
holding
on
to
things.
Although
really
we
should
probably
move
that
into
the
contrib
group
in
the
near
future.
B
It
looks
like
okay
yeah,
that's
it!
So
that's
exciting!
Jeff!
Thanks
for
taking
a
look
into
that,
that's
that's
great
to
see
that
those
commands
expanded
and
more
drush
support.
Coming
into
backdrop.
B
Let's
see,
github
automation,
we've
got
some
ideas
about
how
we
can
better
integrate
backdrop,
cms.org
and
github,
or
even
just
between
github
repositories,
and
we
have
a
tag
for
that
on
on
github.
That
is
called
github
automation
and
it's
in
the
backdrop,
cms.org
issue
queue
jen.
We
we
attach
these
meeting
notes
to
every
video.
Now,
don't
we.
A
B
C
B
Just
some
of
these
urls
get
pretty
verbose,
okay!
Well,
anyway,
you
can
find
out
more
about
that.
On
the
github
backdrop,
cms.org
issue
queue,
let's
see
and
there's
a
bunch
of
new
stuff
with
the
website,
including
the
login,
but
there's
also
new
functionality.
Jen,
do
you
want
to
talk
about
that.
A
Sure
so
we
have
a
news
page,
which
is
currently
at
backup
cms.org
news,
which
is
new
since
last
meeting,
there's
been
a
bunch
of
flurry.
In
the
backdrop,
cms.org
issue
queue
about
how
to
build
the
news
page,
but
since
we
don't
have
any
news
yet
I
didn't
want
to
go
too
crazy,
with
dividing
all
of
our
content
up
into
different
types
of
content
and
organizing
it,
as
we
don't
have
anything
to
organize.
A
So
what
I
did
is
I
created
just
a
standard
blog
page,
which
will
put
all
of
our
blog
posts
on
the
left
hand,
side,
and
then
I
set
up
what
are
they
called
playlists
in
youtube
that
group
all
of
our
videos
together,
so
those
are
automatically
coming
in
from
youtube
instead
of
us
having
to
create
a
post
on
background
cms.org
after
every
meeting
to
get
the
meeting
videos
up.
So
I
divided
them
into
the
development
meetings,
which
is
this
meeting
that
happens
every
week
and
the
design
meetings
which
are
every
other
week.
A
So
there's
a
feed
of
both
of
those
and
then
I
also
just
dropped
in
a
little
twitter
feed,
because
that
right
now
is
where
we're
doing
all
of
our
announcements.
So
then
we
don't
have
to
have
an
announcement
content
type,
that's
different
than
the
blog
post,
and
if
we
have
a
really
big
announcement,
it'll
be
both
on
twitter
and
in
the
blog.
So
I
think
that
that'll
do
for
now
and
as
we
start,
creating
blog
posts
and
start
getting
more
content,
that's
divisible
by
category.
A
We
can
start
to
break
that
up
in
the
future
if
we
need
more
ways
to
organize
content,
so
we
do
have
one
blog
post,
written
and
ready
and
it
will
be
published
tomorrow,
and
I
did
a
little
bit
of
research
to
figure
out
like
what
day
of
the
week
is
best
to
publish
a
blog
post.
I
think
I
wrote
it
on
tuesday
and
I
was
like
I
should
publish
it
now,
but
apparently
people
who
are
are
really
busy
at
work
on
tuesdays.
A
So
you
shouldn't
publish
blog
posts
on
tuesdays,
but
if
you
publish
a
blog
near
the
weekend,
people
will
spend
time
over
the
weekend.
Reading
it
because
they
feel
less
cramped
with
work,
so
I
thought
we
would
do
is
publish
it
on
friday
and
if
we
publish
it
on
friday
in
california,
then
people
who
are
tired
of
working
all
week
and
want
to
go
home
early,
might
read
it
on
friday,
and
people
will
start
tweeting
about
it
and
talking
about
it
over
the
weekend.
A
So
it
seemed
that
seemed
to
be
a
good
recipe
for
engagement
on
the
blog
and
then,
if
we
need
to
send
a
newsletter,
those
are
usually
in
conjunction
with
blog
posts.
Those
are
better
earlier
in
the
week
because
people
are
in
their
email
as
opposed
to
on
the
weekend
when
they're,
not
so
I
figured
we
could
do
the
blog
post
first
and
then
follow
it
up
with
a
newsletter,
as
kind
of
our
regular
routine,
for
getting
people
to
know
all
the
things
that
we're
trying
to
tell
them.
D
A
A
We
I've
got,
I
created
an
issue
specifically
for
content
on
the
website,
and
I've
got
a
bunch
of
stuff
up
through
march
4th
that
goes
every
other
week.
I
left
some
holes
in
there
so
that
if
anyone
has
any
content
that
they
want
to
post
on
our
blog
stories,
they
want
to
tell
showcases
examples
whatever
it
is,
we
can
stick
them
in
those
off
weeks,
and
so
that
way
we
can
have
you
know
kind
of
an
official
feed
of
stuff
on
the
schedule
and
then
oh,
this
is
really
cool.
A
We
should
talk
about
this
and
just
stick
it
in
wherever
we
need
to
so
hopefully
that
will
keep
a
lot
of
activity
of
momentum
going
with
upcoming
blog
posts.
So
if
anyone
has
an
idea
about
things
you
want
to
put
on
our
blog,
you
can
add
a
comment
to
that
issue.
I'm
not
sure
how
long
we'll
be
able
to
deal
with
one
issue
for
the
entire
blog
schedule,
but
we'll
do
it
as
long
as
it's
manageable,
add
a
comment.
A
If
you
have
something
you
want
to
add
and
we'll
get
you
into
the
rotation
on
the
schedule,
let's
see
user
account
creation.
This
I
was
also
thinking
I
was
like
well
now
that
people
can
log
in.
Maybe
we
should
let
them
comment
on
the
blog,
but
then
I
got
worried
about
like
having
to
have
people
watch
the
comments
and
make
sure
there's
any
spam
and
then
answer
the
comments.
If
there's
questions-
and
it
just
seems
like-
maybe
we're
not
quite
ready
for
that.
Yet
we
just
started
the
blog.
A
Maybe
we
shouldn't
over
over
extend
ourselves,
especially
with
a
backdrop
coming
out
next
week.
I
don't
want
to
be
one
thing
at
a
time.
We'll
do
the
new
release
of
backdrop.
First,
we'll
see
how
the
blog
is
going
and
we
can
turn
on
comments
later.
We
can
make
a
bunch
of
noise
about
it,
write
a
blog
post
about
how
we
want
comments,
whatever
what
we're
gonna
have
in
the
future,
so
the
user
accounts
again,
you
could
just
sign
up
and
create
a
profile
page.
A
We
did
do
some
cool
stuff
with
the
profile
page,
where
you
can
add
your
own
banner
image
on
it,
which
I
think
will
be
fun,
lets
everyone
get
a
little
bit
of
their
own
personality
on
there.
So
if
you
don't
have
a
page
yet
go
ahead
and
edit
it,
we
did
a
little
cleanup
of
the
the
the
front
end
theme
so
that
you
can
see
tabs.
A
We
first
launched
it
and
I
had
removed
all
of
the
tabs
because
they
were
ugly
and
then
I
realized
that
nobody
could
edit
their
user
pages.
I
was
like.
Oh,
we
need
those.
I
just
need
to
make
them
not
ugly,
so
I
put
them
back
just
to
help
them,
and
now
I'm
gonna
edit
their
pages.
So
that's
good,
and
then
we
also
had
a
little
snafu
with
emails
that
people
were
getting
to
log
into
the
site
getting
caught
in
spam
filters.
So
I
did
like
a
crash
course:
oh
thank
goodness
andy,
mostly
ported.
A
This
smtp
module
I'll
just
shut
that
on
the
website
and
get
it
going.
So.
Thank
you
andy
for
getting
all
that
done,
and
the
thing
I
want
to
point
out
with
the
modules
page
is
that
the
smtp
module
appeared
there.
So
that
is
thanks
mostly
to
andy
and
then
also
to
backdrop
trying
to
get
people
to
log
in
so
that
was
great,
all
right,
so
coming
up
in
the
future
for
our
website
we're
gonna,
try
and
get
single
sign-on
working.
A
So
those
of
us
who
do
have
accounts
on
github
and
we're
using
github
for
taking
care
of
projects
we'll
be
able
to
link
your
github
account
and
your
backdrop
cms
account,
and
that
will
let
us
do
things
like
you.
Can
edit
your
own
project
pages
on
on
the
backdrop
cms.org
website
also
it'll
prevent
people
who
already
have
githubs
for
accounts
from
having
to
create
a
separate
account
when
they
can
just
say.
Oh,
I
want
to
sign
in
with
github
and
we'll
pull
over
whatever
information
we
can,
which
isn't
much
from
github.
A
D
A
Sites
are
using
it
now
and
you're
like
well.
Let's
see,
there's
my
wedding
website
and
my
friend
has
a
blog
and
it's
just
not
really
very
compelling,
but
if
we
had
a
list
of
all
the
websites
that
people
are
currently
working
on
now
or
have
recently
launched,
then
we
could
say
here's
a
list
of
all
the
sites
you
can
go
and
check
them
out.
It's
worked
really
well
for
drupal
they've
got
a
showcase
site
and
I
would
love
to
get
the
the
same
thing
going
for
backdrop.
A
So
what
we'll
probably
do
is
set
that
up?
It's
gonna
be
a
little
design
process
to
make
sure
we
get
the
whole
slideshow
thing
working
smoothly,
but
that's
next
on
our
horizon,
for
what
what
you
can
do
with
your
backdrop,
user
account
longer
term.
We
also
want
to
add
service
provider
listings
or
contractors.
Anyone
who's
working
on
backdrop
or
around
backdraft
should
be
able
to
list
themselves
or
their
company
so
that
they
can
be
found.
A
We
want
to
add
an
event
calendar,
so
anyone
who's
doing
a
backdrop
friendly
event
can
post
their
own
events
in
the
calendar
instead
of
having
to
email
us
and
say:
please
add
this
to
your
google
calendar
and
we
want
to
add
jobs.
That's
something
that's
been
really
handy
for
drupal
of
recent
is
just
to
be
able
to
post
a
job
or
post
that
you're
looking
for
a
job
to
connect
employers
with
employees.
A
We've
also
got
a
bunch
of
features
that
we
have
launched
on
the
site
recently,
that
need
follow-ups,
launches
themes
and
layouts
are
getting
a
little
better.
Thank
you
for
jeff
for
fixing
this
search
on
the
modules
page.
It
used
to
only
search
one
word
at
a
time
which
is
a
little
frustrating
and
I
think
it
only
searched.
A
I
don't
know
if
only
search
title
or
something,
but
you
fix
that
so
now,
when
you
run
a
search,
it'll
search,
title
and
body
for
as
many
words
as
you
put
in
there,
and
it
feels
better
already
so
that's
great
and
also
jim
burch
added
some
google
seo
stuff
on
there,
which
I
launched
instantly,
and
then
I
realized
that
it
broke
some
stuff.
A
So
I
took
it
off,
but
I
didn't
want
to
thank
him
for
his
effort
for
getting
that
on
there
and
we'll
revisit
that
and
try
and
get
tracking
on
there
and
that'll
give
us
a
hint
as
to
what
people
are
searching
for.
We
were
trying
to
track
their
search
terms,
which
I
thought
would
have
been
really
handy
to
try
and
figure
out.
Oh,
you
know
everybody
wants
rules,
let's
get
rules
on
there,
whatever
it
is,
so
that'll
be
fantastic
once
we
can
get
that
done.
A
Let's
see,
I
already
talked
about
the
blog
schedule
in
announcing
that
we
had
a
blog
upcoming
other
news
and
announcements.
We
want
to
try
and
help
get
the
word
about
backdrop
out
in
places
that
are
not
to
our
normal
community.
So
we
are
going
to
try
and
work
with
the
civic
crm
team
about
doing
some
kind
of
joint
announcements
about
backdrop
and
civil
working
together
having
them
do
some
blog
on
our
site,
maybe
I'll
see
one
on
their
site
or
announcements
to
our
newsletter
mailing
lists
together,
or
something
like
that.
A
So
we've
got
some
irons
and
fire
about
trying
to
figure
out
a
good
way
to
consolidate
marketing
around
that,
which
will
be
great.
We
also.
I
was
also
thinking
a
year
ago
we
did
a
bunch
of
podcast
stuff
that
was
like
you
know.
We,
we
did
a
bunch
of
podcasts
when
we
announced
that
we
were
working
backed
up
and
then
nobody
believed
that
it
would
happen,
and
then
we
launched
it
and
everybody's
like
wait
what
that
worked,
and
then
we
did
a
whole
bunch
of
follow-up.
A
Podcasts
we're
like
back,
drops
out
it's
ready
and
everyone
was
so
excited
and
I
don't
know
surprised,
but
it
made
it.
I
think
it'd
be
great
to
do
a
one
year
later
and
talk
about
all
the
fantastic
things
that
we
accomplished
in
the
first
year
and
what
it
looks
like
for
us
in
the
future
to
just
kind
of
be
like
hey.
You
know
you
guys
didn't
think
we
made
it.
We
made
it,
but
in
fact
we've
more
than
made
it.
It's
awesome.
We've
got
this
great
contributor
community.
A
We've
got
these
people
doing
these
fantastic
things.
We've
got
sites
running
it.
We've
got
success
stories,
we've
got.
You
know
a
whole
bunch
of
great
things
in
in
the
works
for
2016
as
well.
So
I
think
it
would
be
great
to
do
that
again,
just
to
kind
of
get
back
to
all
of
those
people.
A
We've
talked
to
before
and
see
if
they're
interested
in
finding
out,
what's
going
on
so
I'll
reach
out
to
those
people,
maybe
by
email
and
see
if
we
want
to
set
anything
up,
and
I
would
love
to
get
people
in
the
podcast
who
aren't
just
nate
and
myself
as
well.
So
if
any
of
you
are
interested
in
joining
in
and
answering
questions
about
what
it's
like
working
on
backdrop,
let
me
know,
because
I
think
that
would
be
fun.
A
Let's
see,
we
also
have
a
tag
in
the
issue
cube
for
backdrop,
cms.org
for
all
tasks
that
are
related
to
marketing.
I
took
a
bunch
of
them
off
of
today's
agenda
because
we
have
a
bunch
of
other
stuff
to
talk
about,
but
if
you're
interested
in
helping
us
with
marketing,
we
definitely
need
that.
There's
been
a
ton
of
flurry
of
activity
around
that
lately.
So
thank
you.
Everybody
who's
already
gotten
involved,
but
we
definitely
still
have
a
lot
of
work
to
do
so.
A
All
right
so
backtrack,
cms
the
project
itself
has
had
a
ton
of
fantastic
stuff
going
on
in
the
last
few
weeks.
I
don't
know
nate
if
you
want
me
to
turn
this
back
over
to
you.
B
Okay,
yeah,
it's
exciting.
Okay,
so
first
item
of
note
is
that
backdrop
1.2.3
came
out
yesterday,
which
is
really
exciting
backdrop.
One
two
three
and
the
exciting
thing
about
factor
1.23,
is
that
it
has
full
php
7
support.
B
So
we
fixed
a
couple
of
issues
there,
particularly
in
views
that
it
was
using
some
deprecated
apis
and
now
backdrop
is
fully
working
and
passing
all
tests
on
php7,
and
so,
if
you're
interested
in
giving
php
7
a
shot,
you
can
do
so
with
the
latest
version
of
backdrop
that
came
out
yesterday,
we
have
some
small
issues
for
the
next
bug:
fix
release.
That's
backdrop:
1.2.4.
B
What
we'll
do
is
we'll
cut
the
last
release
of
the
previous
miner
version
the
same
day,
so
1.2.4
will
come
out
next
friday,
with
whatever
bug
fixes
we
complete
before
then
in
particular,
there's
some
back
ports
from
drupal
7.40
that
haven't
been
ported
over,
but
we've
had
some
progress
starting
on
those.
B
B
So,
let's
see,
let's
talk
about
one
1.3,
which
is
coming
out
january
15th,
it's
supposedly
the
ux
release,
which
means
that
we've
been
doing
a
whole
bunch
of
work
on
user
experience.
I
shouldn't
say
supposedly:
we've
got
a
lot
of
great
stuff
in
here.
Probably
oh
man
there's
just
so
many
things:
okay,
so
layout
follow-ups,
we've
been
trying
to
make
it
so
that
layout
module
has
more
kind
of
smooth
and
tightly
integrated
pieces
with
the
rest
of
backdrop.
B
One
thing
that
happened
this
past
week
was
that,
thanks
to
mike
mccaffrey,
we
moved
blocks
into
configuration,
so
the
block
custom
table
has
now
been
moved
into
block
configuration
files
and
we
didn't.
We
went
back
and
forth
on
that
issue
a
couple
of
times,
but
it
turns
out.
B
We
saw
the
light
and
saw
exactly
what
kind
of
benefit
that
was
going
to
be
providing
us
that
we
have
other
follow-up
issues
that
make
it
so
you
can
create
a
custom
text
block
from
within
the
layouts
ui
directly
and
combined
with
this
change
makes
it
so
that
we
can
add
a
little
checkbox
for
reusable
configuration,
a
reusable
block,
and
then
it
will
just
leverage
the
existing
blocks
ui
to
display
and
manage
those
reusable
blocks
all
very
exciting,
there's
a
whole
list
of
issues
that
are
similar
and
related
to
this
in
issue
345.
B
It's
the
layout
follow-ups,
meta
issue
and
I'm
really
excited
to
see
that
happen.
One
the
things
that
are
almost
certainly
going
to
happen
before
1.3
the
custom
text
block
functionality
just
talked
about
making
it
so
there's
a
checkbox
for
reusable
that
will
integrate
backwards
and
forwards
with
these
new
config
stored
blocks,
actually
not
new
they're,
just
the
old
blocks
to
store
different
names
differently
now
and
the
one
field
per
block
one
block
per
field
patch.
That
will
make
it.
B
So
you
can
do
things
like
you
can
place
the
image
of
a
node
in
the
sidebar
or
in
the
header
in
the
footer
or
wherever
you
want.
On
your
node
pages
or
same
thing
like
on
your
user
pages,
you
could
set
up
layout
an
entire
profile
where
all
of
the
fields
are
all
over
the
page,
instead
of
just
being
confined
to
the
main
content
area.
So
those
are
exciting.
B
Rich
text,
editor
follow-ups
is
issue.
1087.,
there's
some
things
that
we
want
to
do
to
make
it
so
that
we
integrate
a
little
bit
better
with
filter
system.
B
We
have
a
couple
of
bugs
honestly
relating
to
existing
content
and
paper
and
paragraph
tags,
some
other
issues
with
images
when
they're
placed
in
blocks
garbage
collection
picks
them
up
a
whole
bunch
of
small
issues
there
that
we'd
love
to
see.
I
think
at
this
point
you
know,
there's
probably
only
a
couple
of
those
rich
text
editor
follow-ups
that
will
make
it
in
that
haven't
been
completed
yet,
but
we'd
love
some
additional
effort
there.
B
Let's
see
ux
change,
use
edit
and
configure
consistently
and
correctly.
We
had
a
bunch
of
pull
requests
that
had
been
queued
up
and
had
gotten
stale,
but
jen
rerolled
them
all
this
past
week,
and
almost
all
of
them
are
merged
in
in
issue
771.
The
only
one
that's
left
is
it.
Views
still
has
the
word
edit
view
instead
of
configure
view.
B
So
that's
the
only
remaining
usage
where
edit
does
not
refer
to
content
and
configure
does
not
refer
to
configuration.
B
So
that's
nice,
a
nice
little
win
there
for
terminology
consistency
that
we're
always
editing
things
that
are
editorial
related
and
configuring
things
that
are
stored
in
configuration,
rather
than
just
using
the
two
words
willy-nilly
all
over
the
place.
B
This
issue,
639,
would
be
nice
if
we
could
get
it
done.
It's
add
a
notification
icon
decor
that
will
make
it
so
that
when
there's
a
notification,
for
example
in
the
status
report,
instead
of
putting
giant
red
errors
all
over
your
site,
it
would
put
a
little
icon
in
your
admin
bar
indicating
hey.
You
should
go
and
look
at
this
item.
A
That
issue
wasn't
tagged
with
one
three.
So
when
I
went
through
the
one
three
q
last
week,
I
missed
it.
So
I
changed
the
tag
today
and
I'll
go.
Take
a
look
at
it
and
see
what
needs
to
be
done.
B
Okay,
let's
see
project
browser,
oh
boy,
I
haven't
taken
a
look
at
this
real
recently,
but
I'm
a
little
bit
worried
about
this
one,
since
we
only
have
eight
days
left,
but
project
browser
makes
it
so
that
you
can
find
modules
from
within
backdrop
and
install
them
through
a
browsing
interface.
B
That's
issue
13.99,
if
anyone's
interested
in
reviewing
that,
we
definitely
could
use
some
some
help
and
assistance
testing
checking
to
make
sure
it's
okay
like
deciding
if
it's
complete
enough
and
functionality
works
well
enough
to
be
moved
into
core
in
the
next
week.
But
that's
a
big
chunk
of
functionality.
B
A
I
really
want
to
look
at
that
one,
because
I
think
that
would
be
really
huge
for
usability
win.
So
if
we
can
get
that
in
this
release,
I
think
that
would
be
ideal,
but
I
haven't
played
with
it
for
a
while.
So
I
don't
know
how
close
it
is.
B
Yep,
okay,
other
items:
we've
got
a
couple
of
listings
in
core
that
still
aren't
views
in
particular
comments
or
not
yet
listings
and
we'd
like
to
get
those
converted.
I
there
are
pull
requests
for
those.
I
guess.
B
Okay,
maybe
I'll
mark
it
needs
work,
then,
okay,
so
a
couple
of
those
would
be
great.
If
we
get
those
converted,
I
mean
we're
not
really
losing
anything,
but
it
would
be
great
if
we
could
make
it
so
that
we
just
had
the
consistency
of
using
views
everywhere.
We
could.
B
I
had
a
couple
of
items
for
1.3.0
that
look
like
they're
going
to
get
in
just
because
they're
ready
they
weren't
necessarily
on
the
target
for
1.3
but
they're.
All
pretty
much
complete
one
of
them
is
transliteration
in
core
is
really
really
close.
It's
actually
fully
functional,
it's
just
a
matter
of
actually
reducing
some
of
the
functionality
and
making
it
make
a
little
bit
more
sense
in
core,
rather
than
being
a
contrib
module.
That's
issue
904
and
it's
it's
looking
really
good.
B
Prevents
slow
page
loads
if
your
website
hasn't
been
loaded
in
the
last
couple
of
hours
like
the
first
time
page
load,
instead
of
generating
the
page
and
then
running
chron
and
then
waiting
for
all
of
those
things
to
complete.
It
just
uses
the
last
good
copy
of
the
page
and
then
does
all
of
those
things
in
the
background
and
then
the
next
page
load
it
uses
the
fresh
copy
of
that
page.
B
So
that's
I
mean
that's
a
really
great
performance
improvement
for
sites
that
don't
get
a
lot
of
traffic
or
pages
that
don't
frequently
get
visited,
that
they
will
continuously
be
fast
and
and
be
returned
right
away,
as
well
as
cron,
not
holding
up
the
page
load
when
it
runs
in
the
background.
So
that's
issue
1214,
it's
completely
done,
but
it
needs
some
tests
before
it
can
be
merged.
B
Let's
see
and
oh
also,
really
exciting,
responsive
tabs.
We
have
new
tabs
for
the
seven
theme
in
issue.
671
wes
did
just
an
amazing
job
with
that,
and
I
think
it's
going
to
be
a
really
great
improvement
that
when
you
move
down
to
mobile
or
a
smaller
screen
that
the
tabs
now
collapse
and
we've
got
a
special
mode
when
just
one
or
two
tabs
can't
fit
it'll
turn
into
little
dots
and
a
little
drop
down
for
those
tabs
that
don't
fit
and
when
only
one
tab
will
fit.
B
It
drops
into
a
fully
mobile
mode,
which
looks
really
great
and
awesome.
You
can
take
a
look
at
that
issue.
There's
lots
of
animated
gifs
of
it
in
action
there
and
then
there's
a
bunch
of
other
issues
for
the
1.3.0
release
that
are
just
tagged
for
that
release
may
or
may
not
get
in.
It
really
just
depends
on.
You
know,
what's
what's
done
by
next
week.
Basically,
if
you'd
like
to
see
more
stuff
get
into
1.3.0
the
most
useful
thing
at
this
point.
B
Well,
besides
completing
some
of
these
ones
that
aren't
finished
yet
is
it
would
also
be
tremendously
beneficial
if
we
had
some
cross
author
reviewing
of
these
pull
requests
and
there's
a
tag
for
or
sorry
label
on,
github.
For
prd.
B
Back
back
to
the
authors,
the
sooner
they
can
fix
the
remaining
issues
and
then
the
sooner
we
can
get
those
things
in
ask.
E
Question
about
that
yeah
how
many
to
get
like
reviewed
and
tested
by
the
community
like
if
one
person
reviews
somebody
else's?
Is
that
sufficient
or
do
we
have
policy
about
that
or.
B
I
think
as
long
as
well,
if,
if
any
person
individually
feels
honestly
that
something
is
ready
to
go
in,
they
can
mark
that
ready,
reviewed
and
tested
by
the
community
yeah.
We
don't
need,
like
a
large
amount
of
consensus,
because
right
now
the
activity
in
a
lot
of
these
issues.
You
know
there's
usually
only
one
or
two
people
looking
at
things,
and
so
if
we
waited
for
like
three
or
four
people
to
say
something,
it
might
not
ever
happen.
B
So
yeah
go
ahead
and
be
bold
with
it
and
that
that
will
kind
of
bump
it
up
to
the
visibility
like
the
top
of
the
visibility
list.
For
me
to
look
at
for
merging
and
then
I'll
give
it
another
review
and
then
probably
like
make
somebody
depressed,
but
but
yes,
freely,
mark
rtbc.
If,
if
you
feel
that
something
is
ready,.
B
B
Besides
the
things
that
they
don't
make
it
in
this
next
release,
the
big
ticket
items
are,
we
would
like
to
have
ports
of
references
module
or
something
like
references
module,
a
generic
like
reference
from
any
entity
type
to
any
other
entity
type
solution,
there's
ticket
for
that
1301.
B
B
B
C
C
B
Thank
you,
okay.
Okay,
sorry,
thanks
mike
okay,
let's
see.
B
That's
pretty
much
it
for
summary,
where
we
are
sprints,
we
have
sprints
every
thursday.
That's
today,
after
the
weekly
meeting,
you
can
hang
out
with
us
in
irc
and
pound
backdrop
or
the
primary
place
where
we
do.
Most
of
our
communication
is,
in
the
backdrop
issue
queue
on
github.
B
We
also
have
a
reddit.
If
you
would
like
to
confer
us
there
and
we've
been
hanging
out
besides
irc,
we
also
have
a
getter.im
account
that
is
associated
with
the
backdrop
issues
queue.
If
you
want
to
visit
getter.im
backdrop,
you
can
do
that
to
join
the
online
chat
there.
A
Sure
am
I
muted,
no
okay
yeah.
So,
let's
see
we
have
sand
camp
which
is
coming
up
at
the
end
of
february.
That's
a
drupal
camp
in
san
diego,
where
it'll
be
hopefully
sunny
and
warm
february
25th
to
27th.
We
are
gonna,
have
our
first
full
day
backdrop
training,
so
anyone
who's
interested
in
getting
training
in
backdrop
and
wants
to
visit
some
sun
in
the
middle
of
the
winter.
That
could
be
a
good
opportunity
triple
camp
utah,
which
is
the
beginning
of
march.
A
So,
if
you're
not
so
much
into
the
sun
but
would
like
to
go
skiing
instead
triple
camp
utah
is
having
an
event
they've
reached
out
to
us
specifically
asking
for
speakers
on
backdrop,
I'm
not
sure
if
it's
too
late
to
still
get
in
there,
not
probably
not.
If
you
want
to
go
to
utah-
and
you
want
to
talk
about
backdrop,
they
would
love
to
hear
from
you
and
triple
camp
chicago,
which
is
at
the
end
of
march.
A
I'm
not
sure
how
open
they
are
to
having
backdrop
talks
in
their
agenda,
but
they
are
very
friendly
to
backdrop,
people
and
they
would
love
to
have
us
there
and
talking
to
everyone
about
all
of
that.
So
if
anyone
is
interested
in
attending
any
of
those
events,
they
are
posted
on
our
ical
feed,
which
you
can
grab
from
backdraftsms
or
contribute,
I
think
or
resources.
A
I
think,
but
if
you
have
other
events
that
are
you're
hosting
or
you're
attending
or
you're
speaking
at
and
you
want
them
to
be
added
to
our
calendar,
you
can
send
an
email
to
info
backdropstms.org
and
we'll
get
that
added
to
that
list
as
well.
A
We
have
a
presentation
for
anyone
who
wants
to
talk
on
backdrop
that
we've
kind
of
open
sourced
a
couple
of
slides,
it's
and
the
backdrop
ops
group
in
a
contributory
called
slides.
Similarly,
if
anyone's
giving
a
talk
on
backdrop,
we
would
love
to
have
your
slides
as
well
added
to
that
so
go
ahead
and
submit
a
pull
request
and
we'll
take
a
look
at
those
and
get
them
merged
again,
just
an
announcement
that
we
have
the
first
ever
backdrop.
A
Cms
book
is
available
from
a
press,
it's
called
migrating
from
dribble
to
backdrop,
and
it
came
out,
I
think,
on
december
20th
written
by
todd
tomlinson.
I
can't
wait
to
have
a
copy
on
my
shelf.
It's
very
exciting
and
he's
also
working.
I
think,
on
another
full
backdrop
book
as
well
as
books
on
dribble,
eight,
so
that'll
be
interesting
to
see
kind
of,
compare
and
contrast
between
the
future
of
practice
all
right.
Well,
is
there
anything
else
anyone
wanted
to
talk
about
open
q,
a.
B
B
Yeah,
it's
not
a
module
or
a
theme
exactly,
and
so
it
doesn't
really
work,
but
you
can
I
mean
we
can
make
a
a
project
page
for
it
on
on
backdrop,
cms.org
anyway,
as
a
module,
the
same
thing
drupal.org
did
and
I'm
not.
B
I
I
think
that
as
long
I
mean
as
long
as
we
tag
it
the
same
way
as
though
or
a
module
it'll
still
show
up
as
a
package
on
backdrop,
cms.org
wait
that
might
not
be
true
because
the
dot
info
files
well
anyway,
it
is
going
to
be
a
little
bit
weird,
but
we
could
manually
at
least
make
a
project
for
it
just
to
make
just
to
give
it
some
visibility.
B
B
A
A
All
right
well,
keep
your
eyes
open
for
the
blog
post.
That's
going
to
go
up
tomorrow!
Help
us
retweet,
share
facebook,
google,
plus
whatever
people,
do
to
get
the
word
out
and
yeah
happy
foraging
ahead
for
backdrop.
One
three.
B
D
Okay,
I
do
actually
have.
I
do
actually
have
one
question.
Okay,
so
I
got
the
obviously
the
config
block
save.
But
how
close
are
we
on
the
layout
block
component
of
that?
Because
I
haven't
had
a
chance
to
review
that
code.
B
That
I
I
think
I've
looked
at
it
and
it's
really
good.
We
have.
We
have
have
an
ongoing
issue
in
a
lot
of
places
where
tests
haven't
been
written
for
new
functionality,
and
I
think
that's
the
largest
hold
up
there,
but
the
ability
to
add
a
text
block
from
the
ui
is
there
and
to
have
them
stored
in
the
layout.
Is
there
but
the
reusable
checkbox?
You
know,
obviously,
that
block
config
just
got
in
yesterday
that
functionality
isn't
isn't
there
yet.