►
From YouTube: Backdrop weekly 10/1
Description
Weekly check in on development and infrastructure tasks for Backdrop CMS
A
All
right
we
are
on
air,
it
is
Thursday
October
first
whole
new
month
for
a
oh
we're
just
going
to
do
a
little
check
in
on
tasks
for
backdrop,
starting
with
announcements.
The
first
most
exciting
announcement
is
that
we
have
placed
the
order
for
our
dragon
t-shirts.
If
you
want
to
see
a
preview
of
what
those
look
like
there
is
a
an
image
posted
in
the
agenda.
There's
also
a
little
teeny-tiny
image
posted
on
the
backdrop.
Cms
torg
contribute
page.
If
you
click
on
the
image
will
blow
up
to
be
a
bigger
one.
A
So
if
you
want
to
see
what
the
t-shirts
will
look
like
they're
on
there,
we
used
our
normal
dragon
from
the
sticker
and
put
him
on
the
front
of
a
white
t-shirt.
We
did
make
the
the
word
backdrop
a
little
bit
smaller,
so
the
emphasis
is
on
the
dragon
and
not
on
the
word
back
job,
which
was
a
very
comfortable
fabric
of
t-shirt,
the
same
kind
of
fabric
that
we
had
on
the
previous
t-shirt.
A
If
you
had
that
one,
but
we
did
it
in
a
Heather
white,
because
we
like
we
like
the
white
background,
because
you
could
put
the
dragon
on
it
really
easily,
but
we
didn't
like
a
plain
white
t-shirts
which
has
kind
of
a
really
pretty
devil,
heathered
color
for
white
jennings,
going
to
look
fantastic.
They
are
also
ordering
hoodies.
A
We
don't
have
designs
ready
for
you
to
see
those
yet,
but
we
did
choose
like
this
heather
gray,
color,
that's
the
traditional
bad
cam
puddi
from
2013
and
same
comfortable
eco-friendly
fabric,
and
hopefully
it'll
be
the
same
eco
black
color
as
well,
but
it'll,
say
backdrop
on
the
front
and
I'll
have
the
dragon
on
back.
We
have
a
new
dragon
for
that
and
he's
adorable
and
we'll
get
images
of
that
posted
on
the
line
suit,
probably
today
or
tomorrow.
A
So
if
you
want
to
preorder
a
t-shirt
or
a
hoodie,
you
can
do
that
on
our
website
or
accepting
$25
donations
for
t-shirts
and
fifty
dollar
donations
for
hoodies.
And
if
you
can
come
too
bad
camp,
you
can
pick
it
up
in
person.
If
you
can't
come
to
bad
camp,
then
we
can
mail,
you
t-shirts
and
hoodies.
So
anyone
who's
watching
this
video
and
really
wants
a
bad
camp,
t-shirt
or
hoodie
or
backdrop
t-shape
and
honey
and
can't
come
to
that
camp
can
still
have
one
we're
making
a
fairly
large
order.
A
We
think
we're
going
to
be
buying
more
than
we
need
for
bad
camp
and
we'll
be
able
to
continue
to
send
them
out
over
time.
So
if
you
miss
bad
camp,
you
don't
find
out
about
this
until
later,
and
you
see
somebody
wearing
a
hoodie
and
you
need
one
order,
one.
We
can
also
reorder
if
we
don't
get
enough,
so
we
have
a
process
in
place
for
dealing
with
people
who
want
their
schwag.
So
that's
biggest
exciting
news.
I
think
we
have
the
suit
and
same
news
as
the
previous
week's
as
well.
A
We
want
speakers
for
the
backdrop
summit
at
that
camp.
We
have
nominated
West
to
do
a
talk
on
deeming
and
backdrop.
We
need
somebody
who's
going
to
be
there
to
do
a
talk
on
module
development
if
you're
interested
in
that,
let
us
know
or
porting
modules
from
Drupal
7.
If
you'd
prefer
to
do
that,
we
would
like
to
do
a
show
and
tell
in
differences
between
backdrop
in
Drupal
7,
so
anyone
who's
interested
in
doing
that
can
do
that
as
well.
A
We
also
want
to
have
a
I,
don't
know
anyone
who
has
anything
particularly
interesting.
They
want
to
talk
about
in
backdrop
and
wants
to
spend
20
minutes
on
stage.
It
can
be
demoing
a
live
web
site.
It
can
be
demoing
it
in
development
website
it
can
she
be
just
talking
about
what
it's
like
to
be
part
of
the
backdrop
community.
Anything
you
think
might
be
interesting
to
anyone
who's
at
the
summit.
We
would
love
to
get
a
bunch
of
people
on
stage.
A
So
if
you're
going
to
be
there
or
if
you're
thinking
about
coming
you're,
not
sure
and
giving
a
talk
would
help
you
decide
to
come.
That
would
be
good
too.
If
we
don't
find
enough.
Other
speakers
do
all
these
talks.
Nate
and
I
can
kind
of
fill
in
the
gaps,
but
it
would
be
great
if
we
could
get
people
who
weren't
Nate
and
I
to
do
the
talks
as
well.
Since
Nate
and
I
talk
a
lot
and
we're
getting
kind
of
tired
talking,
so
anyone
else
opposed
to
do
it
that
way.
A
Fantastic
and
Jeff
also
has
a
session.
He
hated
recently
on
hello
world
module
comparisons
between
Drupal,
8
and
backdrop.
If
Anna
wants
to
give
that
his
slides
are
available
and
if
anyone
else
has
slides
that
they
have
worked
on
for
previous
backdrop
sessions
that
they'd
also
like
to
contribute
for
other
people
to
present.
That
would
also
be
fantastic.
So
anyone
who
has
any
interest
in
participating
either
presenting
or
donating,
slides
or
anything
else,
let
us
know
that's
coming
up.
A
We've
got
like
two
weeks
three
weeks,
one
two
three
three
weeks
to
the
day
until
the
back
jump
something
a
little
farther
in
the
future.
We
also
need
speakers
for
drupalcamp
Utah,
the
organizers
of
that
came
that
reached
out
to
us
trying
to
get
somebody
to
come
to
speak
specifically
on
backdrop.
So
that
would
be
good.
If
anyone
wants
to
do
that
and
then
same
thing
as
last
time,
we
have
free
phpstorm
licenses
for
backdrop,
contributed
developers.
A
B
B
We
have
39
total
people
that
have
access
to
the
contribute.
If
you
are
interested
in
being
King
trim
author,
which
basically
can
be
creating
a
new
module
for
backdrop
or
reporting,
an
existing
module
to
backdrop
from
Drupal
or
a
theme
or
doing
layouts
if
you're
into
that
sort
of
thing
as
well,
you
can
apply
to
join
the
backdrop,
contribute
at
github
com,
/
backdrop
dash
up
/,
can't
rib
and
of
course
these
links
are
in
the
release,
notes,
I'm,
sorry
in
the
agenda
which
we
have
every
week.
B
So,
let's
see
that's
it
for
community
growth,
I,
usually
roll
right
into
infrastructure
tasks.
There's
been
some
slow
and
steady
progress
in
these
areas
as
well.
This
week,
let's
see
update,
checking
we're
still
not
occurring
the
correct
data
for
how
many
sites
are
running,
which
modules
we're
collecting
it
correctly.
But
then
our
number
crunching
script
is
not
is
not
crunching
the
numbers
correctly,
and
so
it's
zeroing
everything
out.
B
So
that
could
use
some
work
because
it
would
be
great
if
we
could
then
make
it
so
that
our
listings
of
modules,
themes
and
layouts
on
top
CMS
org
were
sorted
by
usage
because
we're
keeping
track
of
receiving
information
about
which
sites
are
running,
which
modules
but
we're
not
actually
crunching
numbers
correctly
to
make
it
so
much
I'm
actually
sort
on
that.
Let's
see
and
then
once
we
get
those
numbers,
crunching
correctly
we'll
add
some
charts,
and
we
also
want
to
make
it
so
that
people
can
actually
see
that
information.
B
So
people
can
tell
which
modules
are
the
most
popular
and
how
many
sites
out
there
and
all
of
that
stuff.
Let's
see
a
project
browser
we're
hoping
that
in
the
next
release,
it
is
entirely
possible
that
we
would
implement
project
browser
into
core
project.
Browser
would
allow
you
to
find
modules
or
without
leaving
your
own
website.
B
And
if
we
just
give
users
a
way
to
actually
find
those
modules
and
then
tie
that
all
up
so
they'll
need
a
copy
and
paste
the
URL,
then
we
would
give
people
the
ability
to
install
modules
from
within
the
UI,
which
would
be
a
huge
win
for
usability,
and
it
would
also
really
increase
the
liveliness
of
the
control
board.
We
think
so
that
that's
coming
along
it's
issue.
870.
B
We
already
have
the
actual
implementation
for
that
on
backdrop,
cos
org,
so
it's
serving
up
Jason
files
that
backdrop
sites
can
consume
and
you
can
install
the
project
browser
module.
That
is
currently
contribute
to
try
it
out.
So
that's
working
and
actually
pretty
adequate,
but
there's
some
areas
that
it
needs.
Some
improvement
on,
let's
see,
dress
for
backdrop,
is
issue
number
47
in
the
vector
q.
This
has
been
kind
of
a
long-running
thing
that
we've
really
did
really
really
be
great.
A
So
we
got
a
new
contributor
and
thank
you
uber
hacker,
his
Murphy
on
it,
which
has
been
fantastic,
he's,
also
got
it
working
by
tricking
backdrop
into
thinking.
It
was
Drupal
7
by
adding
the
the
constant
version
in
backdrop.
We
changed
the
constant
version
from
version
2
backdrop
version,
so
that
we
wouldn't
get
it
confused
with
Drupal
7,
and
then
we
had
that
defined
in
the
dribble
compatibility
layer.
A
But
there
there's
a
couple
of
other
little
snacks
like
now
got
it
actually
firing.
We
need
to
go
figure
out
which
parts
of
drush
may
need
to
be
adapted
in
order
to
make
it
work
better.
For
backdrop
like,
we
have
the
ability
to
alter
of
the
command
files
that
run,
but
we
may
need
to
do
some
additional
things
like
the
location
of
our
sites.
At
PHP
file
is
different
in
Bactra
plan.
A
If
we
need
to
change
something
there,
that
needs
to
be
abstracted
first
into
a
way
that
we
can
change
it
before
we
can
actually
get
those
changes
in
so
I
think
we're
pretty
close
in
that
it's
almost
working
in
that
you
know.
If
you
change
the
way
backdrop
works
to
make
it
work
like
drupal
it'll
work
that
at
least
points
to
the
places
where
you
know
we
need
to
make
some
changes
in
order
to
go
to
work.
A
A
Should
I
take
over
so
a
backdrop
next
on
the
list,
Josh
Rebecca
jobs
really
important.
We
also
want
to
make
backup
CMS
org
a
little
bit
more
feature-rich
in
the
near
future.
We
just
got
modules,
teams
and
layouts
automatically
pulling
in
from
github,
which
was
our
number
one
priority.
Next
up,
we
want
to
allow
people
the
ability
to
sign
in
to
that
website.
A
So
that
means
setting
up
some
new
roles,
making
sure
the
Commission's
are
correct
for
the
average
user
and
then
making
sure
those
people
if
they
wanted
to,
could
sign
in
using
your
github
account.
So
people
who
already
are
github
users
won't
need
to
create
a
backdrop
account
too,
but
people
who
aren't
github
users
should
still
be
able
to
create
a
backdrop
account
for
the
people
who
aren't
developers
and
aren't
using
those
kind
of
tools
in
our
communities.
A
So
if
we
want
to
get
designers
and
content
editors
and
business
people
and
all
these
people
who
don't
actually
touch
code
involved
in
our
community,
we
need
to
them
something
to
join
as
well,
so
we'll
get
that
set
up,
and
then
we
also
want
to
be
able
to
set
up
a
showcase.
So
people
who
build
sites
and
backdrop
can
show
them
off.
We
want
to
be
able
to
set
up
a
service
provider
listing.
A
So,
if
you're
looking
for
a
developer
or
web
hosts
that
will
take
care
of
your
back
talk
site,
we
can
match
those.
We
want
to
put
up
an
event
calendar.
So
anyone
who
wants
to
go
to
a
Drupal
event
where
they
can
talk
about
backdrop
or
a
backdrop
specific
event
will
be
able
to
find
those
on
our
website
and
post
them,
and
then
we
also
want
to
be
able
to
put
up
things
like
the
job
listing.
That's
worked
so
well
on.
Drupal.Org
would
like
to
do
the
same
thing
on
backdrop.
A
B
A
A
B
Thoughts
that
were
important
to
get
scheduled
next
release.
Yeah
we've
done
really
even
scheduled
bugs
for
the
next
release.
It's
just
whenever
they
get
fixed,
then
then
they
get
headed
to
the
milestone.
So
the
milestone
actually
is
almost
always
empty
for
a
bug-fix
release
and
it
only
gets
stuff
put
into
it.
As
things
are
fixed.
Okay,
nice.
A
A
Having
fix
is
going
to
Drupal
8
that
we
really
likes
that
we
would
like
to
also
get
backdrop,
and
so
we've
created
a
fairly
large
set
of
issues
in
the
one
point.
Three
point:
Oh
milestone,
I'm,
not
sure
all
of
those
will
end
up.
Staying
in
that
milestone,
I
think
what
will
happen
with
this
is
will
try
and
fix
as
many
as
we
can
and
when
it
comes
to
january.
A
First
we'll
kind
of
reprioritize,
or
we
might
do
it
several
times
between
now
and
then
to
try
and
say
you
know
this
would
be
nice
to
have
but
nobody's
working
on
it,
and
it's
not
super
important
to
get
down
4.3
and
we
can
remove
from
also
and
remove
it
to
a
future
one,
but
because
most
of
these
issues
are
not
too
terribly
complicated.
I
think
we
can
get
a
whole
ton
of
them
done
so
that's
kind
of
where
we're
at
with
those.
A
We
also
have
some
major
major
ones
like
cleaning
up
field,
you
I,
which
might
be
big
enough-
that
we
aren't
really
sure
that
I'll
get
in
yet
and
I'm
sure
we
have
a
clear
plan
forward
with
a
lot
of
really
good
ideas.
Again,
I
really
get
a
lot
of
good
people.
Thinking
about
it.
The
person
need
to
figure
out
a
self
problem.
Then
we
need
to
technically
like
write
the
code
to
stop
a
problem.
A
I
really
hope
we
can
get
some
improvements
in
like
1.3,
but
that's
a
it's
gonna
be
hard
problem
to
solve.
So
we
also
have
a
roadmap
posted
epic
trip,
seamless
to
org,
slash
roadmap
that
contains
the
major
features
working
on
for
1.3
and
then
anything
we
need
to
any
new
features.
We
need
to
add
for
1.4.
We
can
add
there
as
well
at
this
point,
I'm,
not
sure
we
really
know
what
we
want
in
1.4.
A
A
Is
it
something
we
need
to
schedule,
or
is
it
something
we
should
just
have
on
our
wish
list
and
we
can
figure
out
if
that
needs
to
be
added,
so
on
future
I
think
looks
really
great
for
1.3
going
to
be
much
better
product
after
that,
and
one
point
there
for
is
so
punt
returned,
so
things
were
always
trying
to
work
on.
In
spite
of
the
fact
that
1.3
is
a
user
experience,
release
user
experience
issues
in
general,
we
can
get
in
all
the
time.
A
So
if
there's
something
that
gets
done
really
soon,
we
could
put
that
into
one
point.
Two
point
three
or
one
point
two
point:
four.
So,
depending
on
the
scope
of
these
deer
experience,
change
those
those
are
continually
reviewed
and
merged,
something
like
field
you
I
rewrite,
might
be
big
enough.
That's
gotta
wait
til
1.3,
but
little
tiny
things
like
terminology
changes
or
you
know
other
things
we
could
probably
get
in
sooner
than
that
developer
experience
issues
are
also
really
important
to
us.
A
Let's
see
if
we
can
figure
out
a
way
to
make
it
seem
less
weird
new
developers
or
more
intuitive
just
to
try
and
help
decrease
that
learning
curve
a
little
bit,
and
these
are
things
that
you
might
not
even
think
about
as
a
drupal
developer,
because
you're
used
to
working
in
the
weirdness.
But
if
you
can
kind
of
put
on
your
non-experienced
hat
and
when
used
to
go
to
do
something
think
about
like.
Is
this
intuitive?
What
I
have
guests
to
do
this,
or
just
ask
yourself
like
why
am
I
doing
this?
A
Does
it
make
sense?
It
would
be
really
great
just
kind
of
have
that
intersection
when
you're
working
through
code
to
try
and
see
if
we
can
catch
some
things
and
make
the
experience
of
developing
on
backdrop
more
intuitive
for
everyone,
every
Thursday
we
have
Sprint's
after
this
weekly
meeting
we're
actually
usually
in
IRC
channel
most
of
the
time.
Not
thursdays
are
a
good
day
because
there's
a
lot
more
people
in
that
channel
working
on
backdrop,
the
channel
is
found
backdrop
on
irc.freenode.net.
A
Our
website
is
a
place
where
we
can
collaborate,
but
we
don't
quite
have
that
working.
Yet
we
have
a
set
of
upcoming
events
if
you're
interested
in
following,
along
with
those
on
an
ical
feed
that
you
can
find
on
the
backdrop
CMS
or
contribute
page,
it's
also
linked
in
our
weekly
meeting
agenda
and
not
a
list
upcoming,
Drupal
events
that
are
backdrop
friendly.
A
Let's
see,
we
also
have
an
ical
feed
for
this
weekly
meeting.
We
also
have
a
design
meeting
that
happens
once
every
two
weeks
and
we'll
have
project
management
committee
meetings
as
needed,
and
there's
ical
feeds
for
those
meetings
as
well
coming
up
coming
events,
the
backdrop
summit
is
or
actually
the
Pacific
Northwest
Drupal
summit
is
first,
that
will
be
october
10th
through
11th
in
gets
in
seattle
this
year
and
then
backdrop
summit
at
bad
camp
is
october.
Twenty
second,
which
is
thursday
that's
three
weeks
away
triple
camp
ohio.
Is
that
same
weekend.
A
A
B
There's
no
official
updates,
but
there's
some
kind
of
exciting
stuff
happening.
Let's
see
the
layouts
follow-up
issue
is
345
and
there's
a
bunch
of
sub
items
under
there
and
there's
a
working
poll
request
for
a
couple
of
those,
one
of
which
is
pretty
exciting.
The
ability
to
have
just
a
custom
text
block
and
just
plop
it
right
into
a
layout
without
needing
to
make
a
custom
block,
so
it
would
literally
be
a
configuration
saved
just
string
of
texts
which
is
pretty
exciting.
B
B
Also
that
would
allow
you
to
place
a
individual
field
off
of
a
node
or
other
type
of
feel
double
content,
separate
from
the
node
contin
seeing
place
in
the
node
content
in
the
middle
and
then
you
could
place
like
a
no
profile
picture
in
the
right-hand,
sidebar
and
I.
Don't
know
date,
field
in
the
right-hand
sidebar
or
wherever
else
in
the
layout
you
wanted.
So
that's
pretty
exciting.
That
I
mean
we've
had
the
ability
to
have
like
node,
specific
or
context
specific
blocks
for
a
long
time,
but
we
don't
have
any
actual
uses
of
them.
B
B
B
So
I'm
even
though
one
point
a
1.3
might
not
have
major
features,
although,
although
as
we
get
closer
to
release
like
we'll
see
how
exactly
how
not
major
the
features
are,
I
think
some
of
the
things
like
that
are
inside
are
going
to
be
really
exciting.
Yeah
just
I
mean
maybe
it's
not
new,
but
it's
going
to
be
better
and
that's
going
to
be
really
exciting.
Yeah
there's
also
really
fascinating,
I
mean
not
to
ok.
This
is
Tooting
my
own
horn,
so
there's
a
an
issue
or
a
couple
of
issues
about
performance.
B
There's
a
background
like
background
processing
issue
which
allows
us
to
do
things
like
a.
If
the
automated
kromm
is
run,
we
deliver
the
page
back
to
the
user,
and
then
we
close
the
connection
so
that
the
background
chron
can
run
without
holding
up
the
page
request
which
is
really
exciting,
and
then
once
we
figured
out
that
was
possible.
B
We
expanded
that
to
make
it
so
that
so
we're
clear.
What's
up?
Does
it
do
the
same
thing
again
cash
clear
now?
It
doesn't
do
it
on
cash,
clear,
because
cash
clear
you
actually
need
the
cash
to
be
cleared
by
the
next
page
load
right
like
if
you're
looking
at
a
page,
you
clear
the
cache
you
actually
want
it
all
to
be
cleared
by
the
time
you
deliver
that
to
the
user.
B
If
your
website
is
low
traffic-
and
you
only
get
one
hit
per
day
or
something
like
that,
then
backdrop
could
use
the
previously
cached
version
from
yesterday,
while
it
generates
a
new
cached
version
for
the
next
user,
which
would
eliminate
the
slow
first
end
problem
for
not
frequently
visited
sites,
and
it
would
also
make
it
so
that
it
would
eliminate
the
one
random
user.
Every
five
minutes
gets
a
slow
page
load
problem,
because
everybody
would
get
a
fast-paced
load.
B
It's
just
that
one
user
would
get
a
just
slightly
stale
copy
of
the
page
and
then,
in
the
background,
that
request
would
generate
the
new
page
for
future
anonymous
users.
So,
basically,
every
like,
assuming
you
got
hit
constantly
every
five
minutes
in
one.
Second,
somebody
would
generate
a
new
cache
entry,
but
they
would
get
served
a
cached
page.
That
was
five
minutes
in
one
second
old,
even
though
five
minutes
was
your
cache
lifetime,
so
they
catches
a
very,
very
slightly
stale
copy,
but
nobody
would
get
a
slow
page
load
which
is
really
awesome
and.
B
That
sucks
in
1.2
actually
there's
a
bunch
of
yeah
there's
a
bunch
of
performance
stuff.
That's
in
1.2
that
things
like.
If
you
have
a
node
modules
directory
and
your
theme
theme
directory,
then
it
doesn't
scan
that
for
template
files,
because
that's
where
Mike
nodejs
keeps
all
of
its
stuff
and
we
don't
need
to
be
traversing
in
there
and
yeah.
When
we
file
scan
the
entire
site
structure,
we
skip
a
whole
bunch
of
stuff.
B
Now,
like
we
skip
CSS
directories
and
jas
directories
and
libraries
and
directors
that
clearly
aren't
going
to
going
to
contain
another
module.
So
our
scanning
of
dot
info
files
is
faster
e,
yeah
yeah
and
that
kind
of
stuff
doesn't
need
to
wait.
The
background
fetch
thing
is
going
to
wait
because
it
actually
adds
a
new
feature.
B
It
actually
adds
a
check
box
to
the
performance
page
that
says
you
know
turn
it
on
or
off
and
we'd
probably
turn
it
on
by
default
out
of
the
box,
but
we
probably
wouldn't
turn
it
on,
as
is
our
policy
on
existing
sites.
So
if
you
upgrade,
we
don't
want
to
be
changing
settings
of
nominee
existing
sites
that
could
cause
some
change
in
behavior.
Even
if
it's
positive
change
in
behavior,
okay.