►
Description
Weekly check-in on Backdrop CMS. Today’s agenda: http://bit.ly/1QX8HqY
A
Alright,
we're
on
air
happy
december
10th
everyone.
We
are
right
in
the
middle
of
the
month
before
the
backdrop
release
or
almost
exactly
a
month
out
pretty
exciting
as
we're
going
to
do
a
little
check
in
on
everything,
starting
with
general
announcements.
We
do
have
dragon
t-shirts
and
hoodies
for
anyone
who
wants
to
make
a
donation
to
the
backdrop
foundation.
If
you
provide
$25
so
we'll
send
you
an
adorable
t-shirt,
and
if
you
want
to
make
a
donation
for
fifty
dollars,
we
can
send
you
a
nice.
A
Warm
stuffed
dragon
hoodie,
so
you
can
make
those
donations
on
the
website
at
backdrop.
Cms
org,
slash,
contribute
and
we'll
mail.
You,
your
document
document
your
clothing
document,
I,
don't
move
apparel
as
a
thank-you
gift.
We
also
have
free,
phpstorm
licenses
for
backdrop
kinship
developers.
So
if
you
are
a
member
of
the
backdrop,
contribute
and
would
like
to
try,
I
think
she
was
like
to
dr
ehab
storm.
You
can
go
ahead
and
send
an
email
to
info
backdrop,
CMS
org,
and
we
can
send
you
a
license.
A
The
license
case
that
we
have
right
now
are
set
to
expire
in
February,
which
is
pretty
soon
so
we're
going
to
reach
out
to
the
people
at
phpstorm
and
see
if
they
want
to
send
some
more
licenses
for
kindred
developers
starting
next
year
or
how
they
want
to
handle
that
going
forward
because
I
think
their
license.
Key
situation
might
be
changing
I
that
we
had
a
downer
list
last
week
too,
but
I
actually
haven't
reached
out
to
them.
Yet
I
think
maybe
I
better
met
actually
make
myself
up
item
to
do
it.
A
B
All
right
new,
ok,
let's
see
so
numbers
for
this
past
week,
so
we
have
178
total
Kim
to
be
contributed
projects
for
backdrop
that
are
in
the
github
group.
That's
one
new
project
since
last
week
on
backdrop,
CMS
org,
there
are
a
hundred
and
ten
official,
really
official
projects
that
have
releases.
It's
really
great
to
see
that
our
number
of
official
projects
is
equipped.
The
total
number
of
github
projects,
I
mean
I,
mean
more
than
half
of
them.
B
It's
pretty
solidly
the
majority
that
everybody
that
makes
any
module
on
the
github
repository
group
they're,
also
making
official
releases
that
gets
inked
over
to
backdrop
CMS
towards
so
that's
great
two
new
projects
and
had
official
releases
since
last
week,
which
is
fantastic
and
then
there's
a
hundred
and
forty-one
total
releases
of
all
projects
on
backdrop,
CMS
org.
That
means
that
there
are
not
only
new
modules
being
created,
but
the
existing
modules
are
getting
new
releases
and
getting
updated
all
the
time.
B
We
saw
42
total
backdrop,
contributed
authors,
there's
one
application
that
has
kind
of
been
waffling
back
and
forth,
but
we'd
really
love
to
have
more
authors,
working
to
port
modules
to
backdrop
four
or
more
themes.
Themes
would
be
actually
in
a
lot
of
ways
better
than
modules,
but
we
have
a
process
for
getting
into
the
backdrop
contribute
you
can
learn
more
about
it.
At
github
com,
/
backdrop,
gash,
ops,
/
can't
rig,
that's
where
we
talk
about
modules
that
are
being
ported
or
what
model
should
be
ported
as
well
as
like
the
entire
business
of.
B
Go
on,
let's
go
on
to
the
next
thing.
Next
item
on
the
agenda
is
infrastructure.
There's
been
a
lot
of
kind
of
exciting
things
happening
an
infrastructure
land
in
the
past
week,
actually
so
update
checking
for
backdrop.
This
has
been
working
for
ages.
It
just
makes
it
so
that
update
module
checks
into
backdrop,
CMS
org,
but
the
thing
that
hasn't
been
working
for
a
long
time
now
is
that
when
sites
do
the
check-in
job,
CMS
org
stores,
information
about
what
modules
are
current
or
projects
are
currently
installed
on
that
site
and
make
sense.
B
Last
week,
I
actually
did
look
at
the
data
that
is
stored
there
and
it
is.
It
is
a
random
hash
that
it
each
site
did
check
same
since
in
a
random
hash.
It
actually,
where
we
actually
record
the
IP
address
in
the
raw
data,
but
then
once
it
gets
processed
on
a
daily
basis,
then
IP
address
is
discarded
and
I'm,
not
quite
sure
why
it's
kept
there
for
that
short
while
in
the
raw
data.
But
my
guess
is
that
it's
just
I
don't
know,
help
detect
any
anomalies
like.
B
B
But,
oh
yes,
so
the
thing
that
they
hadn't
been
working
is
that
our
numbers
haven't
been
calculating
correctly
and
there's.
There's
been
a
long-standing
issue
to
fix
the
number
crunching
script
to
make
it
so
the
analytics
recurring
correctly
and
and
there's
been
some
work
on
that
in
the
last
week
and
I
think
that
will
have
a
PR
probably
later
today
that
should
fix
that
problem,
and
then
we
can
turn
back
on
the
number
crunching
script
on
back
job,
CMS,
org
and
then
we'll
actually
have
usage
statistics
on
all
of
the
modules
and
themes
and
dr.
B
itself.
It's
going
to
be
great
because
that
will
allow
us
to
do
sorting
by
most
popular
modules.
So
we'll
be
able
to
say
you
know,
show
me
all
modules
that
contain
another
word:
web
form
and
the
web
form
module
be
at
the
top
rather
than
the
latest
web
form
related
module
ending
up
on
the
top,
which
is
which
is
not
for
that.
B
Let's
see
after
we
get
that
all
done.
There
are
some
wish
list
items
issue.
99
in
the
backdrop
see
messed
up.
Org
Q
is
to
try
to
extend
a
project
module
I'm.
Sorry,
yeah
project
module
on
the
server
side
and
update
module
on
the
client
side
to
send
over
more
information
about
what
sites
are
running
like
what
options
are
configured
like
if
they
have
caching
turned
on
or
off
or
clean
urls
turned
on
and
off
things
like
that.
B
B
Let's
see
next
thing,
I
kind
of
mentioned
it
project,
browser
and
project
browser
server,
project
browser
right
now,
as
a
contributor
server
is
up
and
running
on
backdrop.
Cms
org
and
the
big
exciting
thing
since
last
week
is
that
project
browser
servers
have
been
kind
of
broken
on
backdrops
Davis
Organa
hasn't
been
able
to
return
all
of
the
items.
It
should
like
you'd
say,
give
me
30
items
and
it
will
give
you
like
16
back,
and
so
there
was
something
wrong
there
turns
out.
B
It
was
a
problem
in
the
sequel,
query
and
I
got
that
fixed
up
this
week.
So
so
now,
project
browser
server
is
working
correctly.
You
can
download
and
try
out
that
contribute
to
make
it
so
that
you
can
install
modules
through
browsing
interface.
Now,
there's
a
new
issue
for
merging
project
browser
in
decor.
It's
issued,
1499
I,
actually
haven't
even
tried
it
out
yet
so
I'm,
just
fine
everything
worked
on
the
server
I
haven't
actually
tried
out
the
interface
I
thought.
B
So
that's
issue
1399
to
actually
put
project
browser
into
court
now
that
the
server
is
up
and
running
and
working
correctly,
and
we
have
the
controversia
knits,
really
just
a
matter
of
getting
that
module
to
a
state
that
we
think
it
that
it
is
suitable
for
inclusion
in
court,
and
so
that
might
be
in
the
next
release.
It's
still
going
to
be
a
little
bit
crunch,
but
we'll
see
we'll
see
if
that
can
happen,.
B
A
B
For
now,
our
focus
is
really
just
I'm,
getting
dressed
working
for
backup,
because
the
tool
that
people
are
already
familiar
with
josh
is
really
flexible,
and
so
we
are
we've
already
gotten
it
to
the
point
that
you
can
use
the
newest
version,
josh
Josh,
eight.
You
can
download
an
extension
that,
right
now,
it's
just
in
the
same
in
my
personal
sandbox
quickest,
get
nervous,
I,
github.com,
/,
quick,
sketch
/
backdrop
brush,
and
you
can
find
a
virgin
address
extension
there.
B
That
will
make
it
so
the
fact
it
will
make
its
a
trash
can
identify
backdrop
and
certain
Josh
comments
will
work.
Then,
right
now,
it's
just
the
basics
to
see
all
drush
up,
DB,
really
basic
commands
things
like
brush,
DL
and
dress
up
are
much
much
more
complicated
and
so
getting
those
commands
working
on
on
dr.
projects
metric.
C
B
D
B
B
Yeah
right
now,
if
you
type
in
a
command
that
doesn't
work
either
a
Drupal,
7,
Drupal,
8
or
backdrop
it'll
just
say
this
command
is
not
supported.
Oh
it's
kind
of
annoying
because
it's
like,
like
oh
sweet.
I
can
totally
do
these
things
and
just
like
creek
yeah,
it's
like
it's
setting
you
up
to
fail.
B
Anyway,
so
that
that's
seeing
some
progress,
probably
once
that
gets
fast,
can
a
kind
of
prototype
phase.
We
can
move
that
into
the
contributory
and
then
from
there
we'll
kind
of
figure
out
what
we
want
to
do
with
it
from
there.
Whether
there
cuz
of
the
core
or
station
can
trip
hope
figure
that
out.
C
B
B
A
B
A
It's
supposed
to
identify
the
root
of
your
project
and
then
look
for
a
dress
directory,
but
it
won't
be
able
to
do
that.
Obviously,
if
you're
not
in
in
a
site
like
you,
can
use
dressed
to
download
Drupal
right,
but
it
wouldn't
be
able
to
run
commands
that
work
with
in
Drupal
from
you
there,
but
it
should
be
able
to
find
anywhere
within
sight
you're,
even
in
a
sub-site
directory.
So.
B
Yep
and
that's
that's
a
problem
that
I
think
may
not
be
solved
because
drush
doesn't
know
what
an
installation
route
looks
like
unless
it
has,
unless
it
already
has
found
its
base
class.
That
says
this
is
one
of
your
inspiration.
Rubbery
directory
looks
like
exactly
so
we're
in
this
chicken
egg
problem.
So
I
don't
know
that
that
will
actually
the
dress
extension
to
actually
identify
backdrop
will
work
if
it's
just
in
the
root
of
the
backdrop
installation
as
it
does
so.
It
sounds.
C
Like
it
can't
be
in
quorum
lesson,
though
thats,
because
otherwise
I
mean
it
wouldn't
live
there,
it
would
live
in
your
dress
links,
it
would
have
to
be
a.
It
might
not
be
a
contributor
module.
We
might
need
like
another
like
like
in
extensions
or
tools
repository
or
something
that
could
live
in
yeah.
B
Or
address
you
need
to
figure
out
a
way.
That's
like
it
goes
up
the
pairing
directories
until
it
finds
a
Drudge
directory
and
then,
if
it
finds
one,
then
it
says.
Oh,
this
must
be
a
root
or
I'm
going
to
load
the
extensions
in
it
or
something
like
that.
It
could
be
possible,
but
yeah,
there's,
there's
weirdness
going
on
for
sure.
B
B
A
So
this
is
something
we
talked
about
last
week
that
we
have
a
bunch
of
issues
in
the
queue
that
involve
working
directly
with
github
and
getting
our
issue
tracker
to
be
more
user
friendly,
and
somebody
mentioned
why
don't
we
have
into
agenda
if
they're
not
getting
attention
and
they
should
that's
like?
Oh,
that's,
smart.
So
there's
a
new
agenda
item
here
for
github
automation,
tasks
and
there's
a
tag
on
the
backdrop
CMS
or
q,
specifically
for
anything
relating
to
github
automation.
A
A
Fails
tests
automatically
marking
it
needs
work
in
an
art
also
automatically
marking
the
associate
as
horror
course
needs
work
in
things
like
that,
since
people
don't
often
have
control
over
the
tags
on
the
floor
request
queue,
we
need
to
get
those
automated
and
then
having
the
poor
across
the
sync
with
the
issues.
I
think
we'll
also
give
us
a
better
experience,
searching
through
HD
queues
and
we're
looking
for
things
like
for
requests
that
need
to
be
reviewed.
A
A
A
So
far,
we've
added
a
ton
of
fields
to
the
user
profile
on
backdrop
there
at
two
modules
that
need
to
be
ported
and
two
modules.
It
just
needed
to
be
added
to
our
code
base
in
order
to
get
the
complete
set
of
everything
we
talked
about,
but
most
of
it
is
already
there
so
I
think
it'll
be
pretty
easy
to
take
the
design
that
serious
gave
us
and
build
out
90,
so
percent
of
it,
which
I
think
is
enough
for
us
to
launch
on
january.
A
First,
my
launch
I
mean
allow
people
to
login,
so
I
think
that
would
be
great.
Let's
see
the
there's
one
thing
that
we
never
design
meeting
tip.
There's
one
thing:
I
just
want
to
kind
of
throw
out
to
you
guys
and
see
what
you
think
his
designs
look
fantastic
and
it
allowed
each
user
to
upload
a
banner
image.
Much
like
you
have
on
your
Twitter
page
or
on
your
facebook
account
or
whatever.
A
That
is
not
something
we
currently
support,
but
it
made
the
page
look
fantastic
I
also
think
it's
a
good
place
to
kind
of
let
people
show
a
little
bit
more
of
their
personality
by
choosing
an
image
for
that
I
want
to
throw
that
out
and
see
if
anyone
had
any
strong
feelings
for
against
not
only
an
icon
that
represents
you
that
I'll
appear
in
comments
and
stuff,
but
also
a
banner
image.
Just
for
your
homepage.
A
A
There's
a
good
one
in
in
the
design
mockup
that
we
might
use
for
now,
but
I
think
that
once
we
start
getting
consistent
branding
assets
for
backdrop,
it
might
be
good
to
take
the
one
that
we
use
on
Facebook
Twitter
whatever
and
put
that
one
up
there.
That
way,
I
don't
know
it'll
be
consistent.
I,
don't
know
what
to
see
what
it
looks
like,
but
it's
a
great
starting
point,
so
I'm
very
excited
about
that.
A
A
D
A
It
would
be
really
nice
if
we
knew
something
about
marketing
and
then
our
little
monkey
contributor
created
this
amazing
issue
in
the
issue
queue
about
all
the
stuff.
The
backdrop
should
be
doing
marketing
related.
That
would
really
help
us
and
I
went
through
and
created
a
whole
bunch
of
smaller,
like
some
issues
off
of
his
net
issues
like
we
need
to
do
all
of
these
things
and
here's
the
to
do
list
for
us
to
kind
of
work
through
and
get
them
done.
A
So
I
put
some
of
the
high
level
ones
on
this
agenda,
so
we
can
talk
about
them
and
one
is
optimize
our
website
or
searching
sort
of
someone's
searching
for
a
content,
management
system
or
CMS
or
a
website
framework,
whatever
they'll
find
dr.
up,
I
think
right
now,
if
you
search
for
backdrop,
we
find
us
right
away,
but
if
you
search
for
content
management
system,
that's
not
the
case,
so
I
think
it
would
be
good
to
get
our
website
optimized.
For
that,
another
thing
we
could
probably
do
is
pay
for
targeted
ads.
A
A
We
have
a
couple
of
suggestions
in
there
like
Google,
ads
or
Facebook
ads
that
might
specifically
target
people
who
say
their
Drupal
developers
might
be
a
good
first
start
or
yeah
I,
don't
know
anyone
who's
looking
for
a
CMS
could
be
great
for
for
Google
as
well,
and
then
creating
a
blog
and
writing
posts.
That's
definitely
something
that's
been
in
on
our
list
for
a
long
time,
having
a
place
to
say
thanks
to
the
community,
we
kind
of
have
a
content
type
on
our
website.
We
don't
actually
have
a
blog
page.
A
We
only
just
let
the
most
recent
item
on
the
homepage
and
then
it
kind
of
disappears
into
the
ether.
But
even
though
we
have
a
mechanism
for
creating
blog
posts,
we
don't
often
have
anyone
saying
anything.
So
if
we
have
anyone
who's
in
this
meeting
or
watching
this
video
now
or
later,
who
is
great
at
writing
words
that
maybe
feels
more
comfortable
writing
words
for
backdrop
than
writing
code
or
dividing
providing
designs
or
any
other
stuff
we
need.
We
definitely
need
help
with
that
too.
So,
just
some
kind
of
way.
D
A
A
A
We
also
want
to
update
the
titles
and
descriptions
for
all
of
the
videos
for
these
weekly
meetings.
Today,
I
did
remember
to
put
a
link
to
the
agenda
in
the
meeting
description,
so
that
should
be
exciting,
but
having
a
name
that
actually
describes
what
we're
talking
about
would
also
be
good
if
someone's
looking
for
something
like.
Oh
this
is
you
know
the
meeting
they
had
the
day
they
released,
1.2
or
whatever
it
is.
A
A
Also,
we
do
have
google
analytics
on
backrub
CMS
org,
but
we
haven't
paying
any
attention
to
it
to
like
who
our
people
are
where
they're
going
on
our
website,
where
they're
coming
from
and
I
think
doing
a
little
research
on
what
we're
doing
now.
That's
working
what
we're
doing
out
it's
not
working,
might
also
be
really
useful.
Just
to
try
and
figure
out.
You
know
what
we
could
be
doing
better
or
who
we
could
be
targeting
better
to
try
and
let
them
know
about
backdrop.
A
Alright,
that's
it
for
backdrop,
infrastructure
marketing,
other
various
tasks
associated
with
the
product
and
now
we're
going
to
talk
about
status
of
backdrop,
the
CMS
itself.
We
have
an
upcoming
bug-fix
release.
Number
one
point
two
point:
three:
there's
nothing
super
urgent
or
critical
in
it,
but
we
do
have
a
bunch
of
cross
ports
from
Drupal
7
that
we
could
get
in
and
make
that
release
at
any
time.
Nate
is
also
super
excited.
Last
week,
PHP
7
came
out,
and
so
we
started
on
an
issue
to
make
backdrop
work
on
PHP,
7
and
I.
B
It
should
be
both
exactly
we
should
get
out
both
of
those
things,
so
we
should
make
a
release
and
we
should
write
a
blog
post
on
on
PHP
seven
support,
so
I
think
that
would
be
great
I
know,
drupal,
7
and
PHP.
Seven
support
is
not
so
hot
because
there's
this
constant
like
needs
to
be
fixed
interplay
first
and
then
it
gets
stuck,
and
then
it
never
makes
it
back
to
seven
so
I
don't
know
I've
seen
posts
recently.
They
were
just
like
mentioning
that
Drupal
7
might
not
ever
support
the
HP
seven.
B
Just
because
of
this
funny
like
nobody's
really
working
on
Drupal,
7
anymore
mentality,
you're
really
sad
well
I
mean
then
there's
some
things
like
views
like
our
poor,
defuse
at
least
had
a
problem
where
it
was
spewing
errors
all
over
the
place,
and
so
even
if
core
supports
it,
contributes
to
have
some
issues
so
yeah
anyway.
So
we
should.
We
should
write
that
up.
It
would
be
great
I.
Also
love
to
do
the
benchmark.
Sonic
I
saw
Gore
posted
an
article
that
was
like
here's
being
a
wordpress.
B
A
Fantastic
and
it's
a
great
idea,
alright,
so
as
soon
as
we
want,
we
can
make
a
release
for
that.
Do
any
I
know
I,
don't
know
if
you
had
any
time
to
look
at
all
of
those
cross
boards
from
Drupal
7.
You
know
you
said
a
couple
weeks
ago.
You
were
interested
in
doing
it
but
busy,
and
that
might
be
something
that
maybe
we
could
work
on
today.
A
If
you
can't
recommend,
say,
I
can
probably
work
on
it
today,
just
to
get
a
whole
bunch
more
of
those
passports
in
and
then,
if
there's
anything
that
looks
sticky,
we
can
just
do
it
in
the
next
release.
But
that
way
we
can
get
the
point
release
out
with
more
of
that
similar
stuff
awesome,
probable,
with
Drupal
7
is
good.
Supporting
PHP
seven
is
better
okay,
so
next
major
release.
A
Sorry
next
minor
release,
one
point
three
point:
zero
scheduled
for
january
fifteenth-
that
is
one
month
and
five
days
from
today,
and
we
have
a
bunch
of
things
we
want
to
get
into
1.3,
there's
a
ton
of
tiny
issues
that
are
all
scheduled
for
1.3
and
github
I.
Don't
think
all
of
them
are
going
to
get
done.
A
lot
of
them
already
have
four
requests.
A
lot
of
them
need
reviews.
A
lot
of
them
need
a
little
bit
of
work.
A
A
lot
of
them
haven't
had
any
work
at
all,
but
I
think
that
if
we
can
just
get
some
of
these
little
details,
right
it'll
make
backdrop
the
product
just
that
much
more
appealing
to
new
users.
People
who
know
drew
more
familiar
with
these
problems
already,
so
it
might
be
kind
of
a
breath
of
fresh
air,
but
they
already
know
how
to
solve
it,
but
I
think
the
more
we're
trying
to
market
backdrop
to
people
who
aren't
in
Drupal
this
liquor.
A
It
needs
to
feel
as
a
standalone
product,
so
I
think
the
more
of
that
we
can
fix
the
better
if
anyone
has
a
nice
time.
A
lot
of
these
issues
are
also
not
super
complicated.
A
lot
of
them
are
novice
issues.
So
if
you
have
five
or
ten
minutes-
and
you
want
to
write
a
foreword
west,
it's
a
good
issue
to
grab
NORs.
Do
that.
So
let's
just
keep
that
in
mind.
If.
A
A
You
can
build
sites
with
it,
as
is,
as
has
been
proven,
it
works
great,
but
there
are
more
things
that
would
make
it
better
that
we
want
to
do
that
are
on
that
list
and
that's
a
shoe
345
same
thing
with
a
rich
text
editor
in
core
we
put
in
a
Minimum
Viable
Product.
We've
already
made
some
significant
updates
to
it.
We
know
there's
a
handful
more.
We
can
get
those
in
to
1.3
point.
Oh,
that
would
be
great
as
well
administration
views
in
court.
A
This
was
something
that
we
wanted
to
get
all
of
the
admin
listings
and
back
job
turned
into
views
for
backdrop
one,
but
we
missed
one
of
them.
It's
for
comments
listing.
We
can
get
that
one
completed.
We
can
knock
that
off
the
list.
That's
just
one
of
those
check
marks
that
your
blade
has
that
we
don't
love
to
get
that
check,
mark
done
for
us.
Well
then,
there's
just
some
usability
things.
A
We
use
the
word
edit
and
the
word
configure
all
over
core
interchangeably
a
lot
of
the
times
and
it's
a
little
confusing
when
you're
supposed
to
use
one
and
when
you're
supposed
to
use
the
other
I
think
we
have
a
really
good
dilemma
nation
in
backdrop
between
thinks
that
are
saved
in
configuration,
the
only
to
say,
configure
and
things
that
are
saved
in
the
database.
The
thing
should
say
it,
and
if,
in
the
future
we
make
a
change
like
we
want
to
move
a
menu
link
from
being
content
making
configuration.
A
We
can
change
that
link
from
edit
to
configure
in
the
future
and
that
what
people
will
understand
when
they're
doing
configuration
management
that
maps
to
every
link
they
clicked
it's
as
configured,
so
it
just
need
to
do
a
little
cleanup
on
those
and
I
think
for
the
most
part,
that's
pretty
straightforward.
There
are
a
couple
of
really
easy
tasks
associated
with
that.
There
are
also
a
couple
of
really
tricky
ones
that
we
might
not
be
able
to
get
to
like
changing
the
edit
links
on
views.
Every
piece
of
documentation
about
how
to
deal
with.
A
A
A
We
also
want
to
clean
up
field.
You
I.
This
is
a
big
hard
problem.
We've
made
a
bunch
of
progress
in
terms
of
making
some
designs
where
I
haven't
made
very
much
progress
towards
actually
figuring
out
how
to
implement
them.
I,
don't
think
this
is
going
to
make
1.3
based
on
the
amount
of
time
we
have
left,
but
field
UI
is
a
separate
module,
which
means
it
could
develop
and
control
could
turn
off
the
field
you
I.
We
have
been
poor
and
turn
on
busy
fields
or
whatever
it
is.
A
Oh,
if
we
don't
make
1.3,
we
could
still
get
a
new
fields
by
at
some
point
and
we
can
merge
it
when
it's
ready
and
then
I
also
just
moved
the
project
browser
into
core
issue.
I
reckon
the
agenda
here
could
be
great
to
get
in
1.3
I'm,
not
sure
how
close
it
is,
if
it's
ready
for
that,
but
I
think
that
would
be
a
big
win
for
usability
just
why
I
scheduled
it
for
this
road
so
we'll
see
we
also
have.
A
If
you
check
the
github
issue
tracker,
we
have
a
milestone
for
1.3
point
now,
where
you
can
see
a
whole
bunch
of
little
tiny
issues.
If
you
want
to
take
a
look
at
those
two
that
didn't
make
this
agenda,
but
are
still
on
high
road
map
for
getting
those
done
and
then,
since
1.3
is
not
a
feature
release,
it's
a
user
experience.
Polish
follow
up,
make
things
nice
release.
A
We've
also
started
thinking
about
what
might
feed
what
features
we
might
want
for
1.4
we've
talked
about
reference
references
module,
we've
talked
about
adding
some
kind
of
version
of
the
redirect
module.
We've
also
talked
about
adding
in
a
new
front
end
theme
that
people
could
actually
use
come
back
to
batted
box.
I.
Think
all
of
those
things
are
great,
I.
Think
anyone
who
wants
to
start
thinking
about
them
now
can-
and
we
will
definitely
start
talking
about
them
more
seriously
after
1.3-
is
art.
A
Our
official
road
map
is
listed
on
the
website
back
top
CMS
org
slash
roadmap.
A
lot
of
it
is
still
in
flux.
Obviously,
if
you
have
suggestions,
let
us
know,
but
we
definitely
are
still
up
mind
about
what
we're
doing
in
the
future
and
things
that
aren't
ends.
Don't
aren't
going
to
be
on
the
website
soon,
as
we
figure
things
out,
we'll
add
to
website
so
yeah
feel
free
to
weigh
in
there's
always
a
bunch
of
other
issues,
we're
working
on
for
backdrop
that
are
not
necessarily
mentioned
in
this
meeting.
A
These
are
experiences,
something
that's
going
to
be
really
important
for
backdrop
going
forward,
so
a
special
man
in
katy
perry
to
choose
my
little
square
brackets
and
then
beginning
of
the
issue
title
with
the
letters
ux
between
them
and
that
way
we
can
call
special
attention
to
issues
that
might
improve
these.
Your
experience
at
backdrop
same
thing
goes
for
developer
experience.
We
put
DX
in
square
back
into
the
beginning
of
the
issue.
A
Title
and
that'll
call
attention
to
issues
that
might
improve
what
it's
like
working,
refractor
up
as
developer,
that
tag
works
for
both
front-end
developers
and
back-end
developers.
So
if
you
find
something
funny
in
the
theme
system
and
all
stiff,
it's
a
DX
tag
so
definitely
use
that
jab
file
issues
technol.
Accordingly,
if
you
can,
we
do
try
and
keep
an
eye
on
stuff
that
comes
in
and
can
help
organize
them.
A
Alright,
every
Thursday
we
have
this
weekly
meeting,
which
is
at
one
p.m.
california
time
fortnightly
every
other
thursday.
We
have
a
design
focus
meeting,
sometimes
that
just
talks
about
things
we're
working
on.
Sometimes
it's
a
working
meeting
where
we
will
actually
try
and
solve
some
problems
depending
on
what's
needed.
We
have
a
little
sprint
after
these
meetings
on
thursdays,
where
we
hang
out
in
the
IRC
channel
back
trap
or
the
get
ur
da
IM
channel
backdrop
issues.
A
We
also
have
a
lot
of
activity
in
the
issue
queue
at
this
time,
which
is
on
github,
and
we
have
a
reddit
that
I,
don't
think,
is
super
active
these
days,
but
it's
reddit
com,
/
r,
/
backdrop.
We
will
eventually
figure
out
how
to
do
something
on
our
own
website
quite
there.
Yet
with
that,
if
you
want
to
subscribe
to
these
meetings
or
have
them
show
up
on
your
calendar,
we
do
also
have
an
ical
feed
available,
which
you
can
get
from.
Google
will
eventually
move
those
on
to
our
website
again
long
term
goals.
A
A
So
if
there
is
a
triple
event
that
you
would
like
to
speak
at
or
have
been
asked
by
organizers
to
talk
about
backdrop
or
if
you
are
an
organizer
and
you
want
the
world
to
know
that
you
can
come
to
that
event
to
talk
about
backdrop,
you
can
send
an
email
to
info
a
backrub
soonest
at
work
and
we'll
add
that
to
the
calendar
again
will
hopefully
get
that
on
our
websites,
and
you
can
find
your
own
events.
But
for
now
we've
just
got
a
couple
of
events
coming
up
on
that
calendar.
A
D
A
We
have
drupalcamp
Chicago,
which
is
at
the
end
March.
So
if
anyone
has
anything
else
coming
up,
they
want
to.
Let
us
know
about,
let
us
know
otherwise,
that's
what's
coming
up
2016,
let's
see
yeah.
So
under
publicity
we
have
the
first-ever
backdrop
CMS
book,
which
is
being
published,
I
just
followed
up
on
the
issue.
For
that
yesterday,
it's
supposed
to
hit
shelves
on
December
15.
So
if
you're
looking
for
a
Christmas
present
for
your
honey-
oh
maybe
the
fact
I've
CMS
book,
it's
a
good
choice.
A
It's
written
by
Todd
Tomlinson,
whose
guy
who
did
the
pro
dribble
development
book
for
Drupal
7,
it's
published
to
the
same
company,
which
I
think
is
a
press
and
so
I
have
high
expectations
about
it
being
very
accurate
and
well-written.
We're
super
excited
to
see
it
and
thanks
big
thanks
to
todd
for
putting
all
the
time,
work
energy
that
to
get
that
book
out.
So
I'm
I'm
really
looking
forward
to
getting
that
he's.
Also
doing
a
drew
bleep
look
too.
A
So
I
think
it
will
be
really
cool
to
get
his
perspective
on
the
two
systems
as
well.
I
mean
been
so
experienced
with
drupal
7
and
looking
at
both
Drupal
8
and
backdrop
and
seeing
you
I
feel
so
I'm
looking
forward
to
it's
going
to
be
all
right.
So
is
there
anything
else
we
should
talk
about
this
week
that
we
haven't
talked
about
or
that
you
guys
want
to
talk
about
while
we're
here
open,
Q&A,
I.
C
C
There
seems
to
be
several
different
sort
of
competing
issues
for
changing
how
blocks
work
with
layouts
and
how
to
add
custom
blocks
about.
You
know
whether
you're
switching
them
with
because
right
now
they're
in
configure,
but
they
are
treated
if
content
in
the
database,
and
so
it
looks
like
there's.
Two
different
issues
like
one
is
to
like
make
them
into
content
and
feel
double
entities
and
stuff
like
that.
There's
another
one
to
make
an
implementation
of
like
another
type
of
custom
block
within
the
layout
energy.
A
So
there's
two
different
solutions:
if
you
have
a
block
that
is
in
the
custom
blocks
table,
that
is
content
and
will
always
be
content
and
we're
manage
managing
thing
that
using
the
uuid
for
each
block
as
I
get
inserted
into
the
layout.
But
the
thing
that
you're
also
talking
about
is
that
going
to
be
called
a
custom
text
block
which
is
not
a
not
a
block
module
block
is
a
layout
module
block.
That's
just
a
box.
You
can
type
whatever
you
want
into
when
you
save
it.
A
The
content
of
that
box
gets
saved
with
a
layout.
So
it's
not
content.
It's
just
configuration
and
the
custom
text
box.
We
don't
have
yet
that's
an
hour
follow-up
issue
for
layouts,
so
hopefully
that'll
be
in
1.3,
but
the
block
content
we
do
already
have
the
custom
product
is
content
and
that's
what
you
see
on
the
blocks
list
now.
So
there
are
two
different
approaches
and
when
to
use
each
one
will
be
up
to
you
like.
If
you
need
your
content,
editor
is
constantly
editing
or
updating
or
adding
blocks.
A
A
A
C
But
I
mean
that
yeah
but
I
mean
you
could
theoretically
put
HTML,
you
could
like
put
a
movie
and
there
it's
not
just
text
and
I.
Think
it's
so
I
mean
whether
we
want
to
call
it
something
else
like
maybe
like
a
layout
block
or
something
like
that,
because
it's
just
if
we
call
the
layout
block
that
sort
of
clarifies
that
it's
just
usable
within
that
layout,
yeah.
A
C
I
mean
I
mean
the
one
suggest
the
current
custom
blocks
of
which
are
going
to
be
content.
Perhaps
we
could
call
those
content
blocks
and
that
will
sci-fi
that
their
content
and
appear
under
the
content
menu
and
that
their
field,
a
bowl
and
stuff
like
that,
and
we
call
those
content
blocks
and
then
the
ones
in
layouts
that
are
just
less
or
like
custom
blocks
or
something
like
that.
But
yeah.
A
A
A
And
the
words
are
confusing
that
I
think
if
we
can
figure
out
what
words
to
call
things,
then
your
reading
the
issues
I
forgot
less
confusing
too
but
yeah
we
are
gonna,
have
both
I
agree.
We
need
to
figure
out
what
to
name
them.
I
would
love
to
take
that
offline
or
it
may
be
just
into
a
different
conversation
and
just
try
and
figure
out
like
what
do
we
call
these
things
gonna
make
sense
to
people.
A
I
also
am
not
married
to
the
word
block
before
it
has
a
long
history
interval,
but
I
feel
like
there
might
be
a
better
word
to
use
than
that,
and
we
also
are
misusing
the
word
layouts
to
like.
Sometimes
a
layout
is
a
project,
and
sometimes
the
layout
is
a
page
and
sometimes
a
layout
is
a
configuration,
and
I
think
that
trying
to
figure
out
how
to
talk
about
these
things
in
and
waste
and
well
so
I'm
just
using
the
word
page.
Well,
it's
just
not
was
not
get
into
that.
A
We
need
to
figure
out
what
to
call
these
things,
particularly
the
custom
block
versus
text
block
problem.
So
yes,
I,
don't
know,
I
don't
mean
we
have
it.
Why
don't
we
work
on
the
name
for
a
text
block
in
the
fifth
follow
up
issue
for
layouts
panchal?
That
was
to
add
that
whatever
it
is
block
and
then,
if
we
need
to
change
the
word
of
custom
black,
we
can
I
think
it.
A
We
call
the
custom,
but
because
that's
what
you're
Blake
called
it
I
think
the
module
was
called
custom,
block,
module
and
Drupal
8
and
that's
where
they
got
the
name
from.
But
we
might
look
into
that
too
and
see
what
the
value
is
of
having
that
needs
to
be
the
same
as
Drupal
8
versus
having
to
be
clear
for
this
thing
by
itself.
I'd
love
to
just
see
it
make
sense.
But
okay.
B
I
one
point:
Jenna
I
recall
that
think,
there's
an
issue
for
this,
that
you
wanted
to
move
blocks
the
custom
blocks
into
the
content,
menu
and
out
structure,
because
they
really
are
they're,
basically
yeah
once
they
become
and
once
they
become
feel
double
entities
like
a
block
and
a
node
will
essentially
be
the
same
thing.
It's
just
that
blocks
or
notes
have
URLs
and
blocks
don't
and
that
other
than
that
they
basically
be
the
same
yeah
wait,
which
also
prompted
like
what
about
like
URL,
less
notes.
B
C
But
then,
when
you're
building
a
layout
with
blocks,
the
problem
is
you'd,
build
a
layout
on
your
dev
server
or
something
like
that,
and
then
it
would
be
in
configuration
and
you'd
move
it
to
the
live
site.
But
the
problem
is:
if
you're
using
content
blocks,
then
the
content
isn't
in
the
configuration,
and
you
end
up
with
a
layout
that
points
to
nothing.
So
it's
sort
of
like
you
have
this
weird
thing:
we
have
to
go
the
live
site,
create
the
blocks.
Think
to
your
dev
site,
then
add
the
block
rather
than
yes,
I
mean.
C
Maybe
if
we
have
the
two
different
solutions,
maybe
people
most
often
use
the
the
layout
blocks.
The
layout
custom
blocks
for
doing
that
sort
of
thing,
but
yes,
it's
yeah,
but
we
might
want
to
think
about
having
it
seems
like
there's.
A
lot
of
these
sort
of
discussions
like
maybe
have
some
sort
of
issue
tag
specifically
around
terminology
or
around
like
hey.
A
Big
things
it's
like
for
that:
it's
the
needs,
feedback
tag;
okay,
okay!
Yes,
so
if
you
ever
find
an
issue
that
is
specifically
like,
we
need
to
have
a
conversation
tag
it
with
needs
feedback
and
that
will
hopefully
get
the
attention
of
people
to
like
way
in
and
have
that
conversation
and
if
it's
something
specifically
around
terminology,
also
feel
free
to
add
the
UX
tag.
That's
definitely
something
that
always
seems
to
be
a
vex
user
experience.
So
that's.
C
A
C
A
A
A
I,
don't
talk
about
I
feel
like
sometimes
in
in
Drupal,
and
people
are
like
hesitant
to
make
any
change
adults
they're
like
what
do
we
get
it
wrong
and
I'm
with
all
the
stages
again
so
yeah
I
think
lets.
You
know
not
not
spend
too
much
time
worrying
about
it.
We'll
try
it
if
we
get
arrival,
just
change
it
again
later,
hopefully
sooner
brother
trying
thanks,
I'm,
good
okay,
anything
else
or
did
you
have
something
you
want?
A
D
D
A
So
it's
really
great
feedback.
We
usually
have
the
agenda
ready
a
week
before
and
I
just
joel
one
tweet,
which
is
like
half
an
hour
before
the
meeting
it'll
be
really
easy
to
schedule
one
a
day
before
and
that
way
people
can
weigh
in
on
the
agenda
and
what
happens
is
the
tweets
automatically
import
into
Facebook?
So
if
I
can
schedule
them
to
happen
a
day
before
and
then
half
an
hour
before?
That
will
get
people
to
give
feedback
on
the
agenda?
We
can
add
anything.
We
want
I,
think
that's
a
brilliant
idea.
D
That's
great
that's
awesome
and
because
it
will
be
available
one
day
before
I
can
repost
it
it
on
the
Russian
market
on
Drupal,
the
troll,
which
is
can
bring
a
potential
developers
who
kind
of
want
to
check
it
out
and
at
least
listen
and
maybe
give
you
some
feedback
about
process
a
note.
Another
question
I
have:
is
there
really
one
person
who
is
doing
marketing?
No,
is
there
any
plans
to
make
somebody
who
is
not
so
involved
in
development
process,
but
really
like
to
talk
to
people,
chair
staff
and
etc?
A
I
would
love
if
we
could
get
somebody
who
was
like
stamped
official
backdrop,
marketing
person,
I
was
kind
of
hoping.
Maybe
we
could
get
our
back
jobs
favorite
monkey
to
do
it
since
he's
a
marketing
expert,
but
I'm
not
sure
how
much
time
he
has
to
contribute
to
that.
So
I
would
just
say
anyone
who's
interested
in
it
if
anyone's
watching.
A
D
When
this
person
will
show
up,
I
already
have
a
proposition
what
to
do
actually
his
information.
So,
for
example,
I
was
posting
this
link
yesterday
and
worried
about
HP
7i
bello
post
in
the
chat
right
now,
and
we
need
somebody
who
is
kind
of
searching
through
internet
through
popular
blogs,
about
information
that
pop
out
about
new
features,
HP,
seven
or
Drupal
8,
or
something
like
this,
where
it's
applicable
to
share
information
about
backdropped,
ms
as
well
just
to
do
so.
D
So
if
somebody
like
so
we'll
just
go,
there
drop
messages
right
now,
maybe
to
bring
extra
attention
pass,
Google
will
index
it
and
it
will
get
linked
at
HP,
seven,
but
wrote
a
mess
and
eventually
we
will
show
up
somewhere,
which
is
good
idea,
and
why
add
this
topic,
for
example,
is
anybody
else?
Souls
in
city
hall.
D
Or
did
anybody
see
this
link
before
work
that
I
just
positive
about
this
backdrop
review,
and
it
has
zero
actually
right
now,
one
share
on
Facebook
that
I
did
so
we're
completely
missing
when
we
even
find
some
information
about
the
drops
image
online
here
is
nothing
happened
like
no.
Nothing
happened
really
doesn't
happen.
No
links
on
facebook,
no
anyway,
yeah.
A
D
A
D
A
D
Gator,
there
is
almost
no
way
information
about
it,
but
if,
like
people
who
really
interested
get
together-
and
it
could
be
a
public
chat-
that's
easy
to
find.
So
what
articles
for
exist
could
be
dropped
in
a
chat
and
people
can,
like
sure,
spread
it
around.
If
you,
if
you
don't
even
have
a
time
when
check
it
out,
just
open
fair
enough
click
to
share,
that's
it.
So
that's
my
proposition
at
this
point.
Okay,.
A
I
think
that's
great
I
will
go
ahead
and
start
posting
these
things
today,
just
so
that
we
can
get
them
out
there
already.
But
again,
if
anybody
is
interested
in
picking
up
some
or
all
of
these
marketing
tasks
or
even
better
managing
kind
of
the
role
of
backdrops
marketing
expert
would
be
great
to
have
that
I'll
also
send
out
a
tweet
and
a
facebook
post
about
needing
someone
to
do
our
marketing
stuff.
A
Maybe
we
can
even
send
a
new
newsletter
Nate
that
talks
about
backdrop
on
page
b7,
and
we
can
put
a
little
paragraph
in
there
about
looking
for
someone
up
with
marketing.
You
think
we
probably
have
somebody
in
our
community
already.
It
would
be
perfect
for
that
job,
who
maybe
even
have
some
time
to
do
it
and
I
think
just
making
a
little
bit
more
noise
about
it
will
help
and
then,
if
we
can
get
that
person,
then
we
can
make
a
bunch
of
noise
about
everything.
B
Liberties
of,
like
our
twitter
account
like
right
now.
It's
it's
jen
and
I
running
like
the
backdrop,
facebook
page
and
the
backdrop
twitter
accounts
and
the
youtube
fee
and
really
like
a
if
we
do
have
a
volunteer.
It's
interested
in
handling
the
social
aspects
of
things
like.
We
will
be
more
than
happy
to
share
that
responsibility
and
I
think
that's
a
great
idea
that
we
need.
B
But
conferences
are
so
bad
about
actually
publishing
the
videos,
that's
like
when
one
actually
shows
up
like
I've,
never
even
seen
a
video
of
our
presentations
before
so
there
is
one
now
I
guess
it
would
be
great
to
yet
market
that
to
other
people
as
well,
because
I
didn't
even
know
it
existed.
So
it's
really
unlikely
anybody
else
knew
it
existed
either.
A
Right,
what's
been
about
an
hour,
why
don't
we
go
ahead
and
wrap
up?
This
meeting
will
move
to
github
I?
Have
a
nice
look
to
to
list
of
things
to
get
going
today,
but
I
also
really
want
to
try
the
project
browser
yeah
I'll
get
to.
It
may
be
all
right.
First
things:
first
marketing
first
then
go
later,
but
okay!
A
Well,
thank
you,
everybody
for
coming
and
thank
everybody
for
watching
and
definitely
if
you
have
any
feedback,
you
can
send
a
tweet
to
a
factory
of
CMS
to
or
you
can
find
us
on
facebook
you
can
send
an
email
to
info
backdrops
and
mr.
org
or
most
easily
create
issues
on
github.
That's
usually
most
of
the
time
but
yeah.
Thank
you
all
for
coming,
and
we
will
see
you
next
week
all.