►
From YouTube: Backdrop CMS weekly meeting 11/5
Description
Weekly check-in on development tasks for Backdrop CMS.
A
Just
keep
us
on
track
for
Nick
chiles
before
we
get
started.
I
want
to
have
a
couple
general
announcements.
First
and
most
exciting
is
dragon
related.
We
do
have
new
backdrop,
t-shirts
and
hoodies
available.
As
thank
you,
gifts
on
our
backdrop,
CM
esta
hora
contribute
page.
You
want
to
make
a
donation
for
$25,
you
get
this
adorable
dragon
t-shirt,
and
if
you
are
going
to
be
ready
backdrop,
then
you
get
a
t-shirt
anyway,
because
you've
already
earned
one.
A
So
we
sailed
off
a
bunch
just
this
morning,
actually
absolutely
and
getting
those
out,
but
you
will
have
them
in
the
next
three
to
five
days.
So
keep
an
eye
out
contributors
on
those
coming.
Your
way
we
handed
out
a
ton
of
fat
camp,
they
were
pretty
popular,
they're,
very
soft
and
comfortable
in
breathable
and
covered
with
dragons,
so
I'm
new
around.
We
also
will
hoodie
available.
It
says
backdrop
on
it
which
you
can
get
for
a
fifty-dollar
contribution.
That's
our
thank
you
gift
for
those
people.
A
So
if
you
are
worried
about
the
winter
approaching-
and
you
need
something
warm
who
do
you
want
to
keep
your
ears
comfortable,
they're,
very
soft
and
comfortable
and
also
will
keep
you
more
so
consider
making
a
contribution
in
and
we'll
mail
one
of
those
off
as
well,
and
the
cost
of
mailing
is
included
in
the
cost
of
your
contribution.
So
thank
you
in.
A
Interested
in
church
of
it's
all
right,
we
have
no
well
okay,
there's
a
couple
of
other
announcements.
A
drupalcamp
Utah,
which
is
march
forth
through
fifth,
is
looking
for
people
to
attend
to
speak
about
backdrop.
So
if
you're
interested
in
getting
some
skiing
done
early
next
year,
I
have
friends
or
families
in
salt
lake
city
and
want
to
go
participate
in
a
Drupal
event.
They're
looking
for
backdrop
speakers
there,
so
that
might
be
a
fun
thing
to
do.
A
B
So
I
kind
of
same
same
story
as
usual.
The
steady
march
of
progress
continues
forward,
make
sure
do
have
an
applicant's.
Oh,
this
is
actually
really
exciting.
Actually,
we
have
an
applicant
to
the
contribute.
They
may
be
ported
honeypot
module,
but
of
course
we
already
had
honeypot
module
for
did
so
so
he's
just
chilling
out
until
he
runs
across
another
situation
in
which
he
needs
to
port
Lodge
hole.
B
B
A
B
B
I
actually
said
the
same
thing
that
you
could
collaborate
with
the
existing
maintains,
who
I
think
that
the
existing
maintainers
might
be
Quackers
ate
me,
which
is
funny
because
they
both
have
been
operating
their
handles
I
got
another.
We
don't
take
that
I,
don't
know,
that's
her
herb
dual
&
herb's
been
pretty
active
on
and
on
I
think
these
he's
probably
reasonably
active,
but
yeah.
B
It
would
be
nice
if
they,
if
they
work
together
and
due
to
the
recent
github
changes,
he
actually
can
collaborate
on
a
project
without
being
granted
access
to
the
entire
contribute
group.
So
anybody
that
can
edit
the
individual
projects,
which
they
sure
that
they
are
in
the
their
group
I
think
they
can
now
invite
individuals
to
collaborate
on
a
project
without
going
through
the
application
process
which,
which
is
interesting,
an
alternative
instead
I.
A
B
B
B
B
Well,
anyway,
maybe
we'll
just
forget:
I
said
that
anyway,
so
since
last
week,
nurs
been
one
new
project
created
in
the
backdrop
kinship
group
and
language,
there's
been
one
new
release
or
one
new
project
added
to
the
official
list
of
projects
on
backdrop,
CMS
gorg,
bringing
us
up
to
167
total
projects
and
92
of
those
with
official
releases
that
are
on
backdrop,
CMS
Borg
great.
As
always.
B
B
Okay,
so
let's
go
on
to
infrastructure,
so
infrastructure
updates
devis
teching.
We
have
this
issue
where
our
numbers
aren't
occurring
correctly.
That
is
still
an
issue.
Last
week,
gore
and
I
were
chatting
in
IRC
that
he
has
been
working
on
or
trying
to
come
up
with
a
proof
of
concept
of
alternatives
or
collecting
number
scripts.
I'm,
not
sure
about
that.
Like
I.
B
Think
that
short-term
the
best
thing
to
do
and
just
be
able
to
fix
the
script,
I
mean
it's
just
a
hundred
line,
PHP
script-
that
if
we
get
it
fixed,
then
we
would
start
having
usage
statistics
that
were
accruing
historical
data,
but
that
is
currently
broken,
but
Gore's
looking
into
doing
some
kind
of
alternative
that
would
replace
the
current
PHP
script
anyway.
That's
issue
number
nine
in
the
project
module
so
backdrop,
contribs
/
project,
there's
issue
key
there
and
issue
number
nine.
Is
that
particular
problem?
B
B
Let's
see
the
project
browser
server,
so
we
are
hoping
to
make
it
so
that
you
can
install
or
not
just
install
but
find
modules
through
backdrop,
an
installation
of
backed
off
without
needing
to
leave
your
own
websites,
and
it
looks
like
since
last
week,
dr.
Elmont
posted
updates
to
that
issue,
which
is
issue
870
and.
B
B
Since
last
week,
I
took
a
look
at
Russia
and
what
people
had
encountered
so
far
and
then
basically
the
big
problem
is
that
we
can't
get
dressed
to
properly
identify
backdrop
without
trying
to
treat
it
like
drupal
7,
in
the
way
that
doesn't
work.
But
we
filed
a
pull
request
against
a
brush
eight
last
week
and
it
is
since
the
merged
that
solves
that
problem
of
not
being
able
to
it,
treats
its
so
much
like
drupal
7
that
it
has
to
match
the
directory
structure
of
triple
seven,
and
so
that
was
causing
an
issue.
B
B
I
have
actually
works
for
the
most
part,
but
there
are
some
things
that
are
like
a
little
bit
too
dangerous
at
this
point
like
if
you
did
a
rush
up,
for
example,
to
update
from
an
update
server,
it
would
so
connect
to
drupal,
org
or
drush
dl
would
download
like
a
Drupal
7
version
of
a
module
rather
than
a
backup
version
of
a
module.
So
we've
got
some
work
cut
out
for
us
to
make
those
things
work,
but
things
like
Josh,
CC,
all
or
just
equal
CLI.
B
B
Eight
so
yeah
is
it
in
dress.
72
I
actually
filed
the
pull
request
for
quote
seven
and
eight,
but
Greg
said
that
he
wasn't
going
to
implement
it.
Drush
seven,
so
I
tried
to
get
it
into
seven,
but
basically
there's
no
release
of
drush
gate,
which
is
the
really
unfortunate
thing.
It's
basically
just
the
master
branch
of
the
Drudge
project.
At
this
point
so
yeah,
so
me,
please
crush
ate
an
order
today
to
work.
What's
it,
you
know
what
the
difference
is.
A
B
A
B
That
that
is,
it's
weird,
there's
still
a
bunch
of
Drupal
6
code
in
drush
meat.
So
it's
a
little
bit
fuzzy
I
think.
Basically,
they
just
stopped
development
on
Drupal
around
rush
7
just
to
draw
a
line
in
the
sand,
and
just
say
this
is
for
Drupal
7
in
Drupal
6,
and
then
then
I
think
they
are
saying
that
Josh
8
is
for
triple
seven
and
Drupal
8,
but
not
triple
six,
but
it
still
has
all
the
Drupal
6
code
in
it.
B
It's
all
so
strange
that
drush
7
has
a
bunch
of
Drupal
8
code
in
it,
but
supposedly
is
not
going
to
officially
support
triple
eight,
so
I
think
that
they're
actually
the
same
code
base.
It's
just
that
they've
just
decided
to
stop
iterating
on
Triple
Eight
code
and
rush
7
and
stop
it
during
a
hunt,
ripple
6
code
and
rush
eight,
but
they
actually
still
have
all
of
the
code
from
both.
They
sell
dribble
a
code
and
rush
them
and
I
stopped
Drupal
6
code
and
rush
8.
But.
A
B
Us
then,
to
only
get
our
patches
integer
sheet.
Yeah
and
it'll
be
okay.
I
think
because
people
need
to
upgrade
in
the
near
term
anyway.
So,
okay
anyway,
so
that's
working
pretty
well
I'd
like
to
probably
it
do
some
more
research
or
maybe
we
need
to
file
for
work
West
against
rush
I'd
like
to
make
it
so
that
rush
right
now,
a
command
is
assumed
to
work
on
every
system.
That
drush
supports
so
like
if
there's
a
command
like
a
dress-up
DB,
for
example,
which
is
update.
Your
database
running
update
a
PHP.
B
If
that
command
doesn't
work
for
backdrop.
Currently
it
would
be
nice
of
that
command.
Weren't
even
displayed
in
the
list
of
commands,
but
right
now
brush,
doesn't
know
how
to
make
a
command
B
version
specific,
like
it
just
assumes
that
if
you
have
a
command,
it
works
on
every
system
that
it
supports,
but
I
think
that
it
would
behoove
them
to
make
it
so
that
you
could
have
a
command.
It
was
like
a
you
know:
Drupal
8
only
command
like
config
sink
right,
because
there
is
no
King
fake
in
Drupal
7
and
make
it
so.
B
B
It
would
be
nice
if
the
commander's
weren't
shown
at
all
if
they
weren't
supported
on
particular
platform,
and
so
if
we
can
get
that
working,
then
that
would
be
good
for
us
to
make
it
so
that
we
could
iterate
on
our
commands
to
make
it
so
that
only
the
commands
that
we
know
worked
would
be
shown
because,
right
now
all
the
commands
are
shown
and
some
of
them
work
and
some
of
them
don't
and
it's
a
big
big
mess.
So.
A
Now
we
wanted
to
compare
Drupal
8
against
backdrop,
and
if
we
can
give
them
a
place
to
sign
in
and
collect
some
information
well,
they
start
to
get
an
idea
who
it
is
that's
looking
at
backdrop.
We
also
want
to
look
and
do
other
things
once
they
log
in
so
there's
a
couple
of
easy
wins
like
letting
those
people
who
login
lips
themselves
as
either
a
backrub
service
provider.
A
If
they're
they
want
to
have
like
a
company
listing
or
an
individual
contractor
if
they
wanted
to
that,
so
that
people
who
are
looking
for
other
people
to
do
backdrop,
work
could
have
a
listing
where
they
can
find
them.
I
also
think
we'll
move
our
list
or
backdrop
supporters.
That's
currently
on
the
homepage
on
to
that
listing
page
initially,
because,
even
though
those
who
will
have
unlocked
it
in
creating
create
pages
and
specified
that
they
are
providing
backdrop
services,
you
can
still
click
through
to
their
website
from
there
and
contact
them
and
say:
hey.
A
Are
you
providing
backdrop,
services
which
might
be
useful
for
people
who
are
looking
for
people
providing
backdrop
services,
so
that's
kind
of
where
we're
thinking
about
starting
with
that
also
moving
the
events.
Calendar
/
would
be
much
better
than
relying
on
a
google.
I
trow
feed
that
you
have
to
email
info
backdrop
CMS
to
get
listed
on
so
I
think
creating
the
wafer
people
are
organizing
events.
People
were
attending
events
or
people
for
wanting
to
attend
events
to
log
in
and
add
an
event
and
say
you
know,
I'm
going
to
give
a
backdrop.
A
Let's
see,
we
also
want
to
add
things
like
job
listings
and
other
things
to
have
been
super
successful
on
drupal.org,
but
I.
Think
higher
priority
for
X
is
going
to
be
getting
a
showcase
up.
So
after
we
get
the
profile
page
done,
all
right,
stereo
focus
is
going
to
be
on
the
showcase,
and
that's
because,
when
you're
trying
to
sell
backdrop
to
someone
saying
it's
a
really
great
software
platform,
it
can
do
all
this
stuff.
A
It's
really
helpful
to
have
a
list
of
websites
built-in
backdrop
and
say
here
are
websites
that
have
been
built
in
this
platform
and
it
kind
of
proves
that
it
can
do
the
things
that
you're
saying
you
can
do.
I'd
also
be
nice
for
people
to
be
able
to
log
in
and
post
the
work
they've
done
right.
So
if
we're
going
to
give
people
a
log
into
the
website,
let's
let
them
show
off
the
work.
They've
done,
get
a
link
back
to
their
website.
I
get
a
little
SEO
juice.
That
way
too.
A
So
lots
of
work
to
do
I'm
say
we'll
get
there.
Okay,
more
exciting
things,
backdrop
itself,
our
next
release.
We
have
a
bug-fix
release
coming
out.
One
point
two
point:
three:
there's
nothing
super
urgent
for
that
release,
but
we
would
like
to
get
it
out.
Soonish.
There
have
been
a
couple
of
new
releases
of
Drupal
since
the
last
backdrop,
at
least
triple
seven
point.
Four
and
7.41
have
come
out.
7.41
contained
only
single
security
fix,
which
does
not
apply
to
back
up,
so
we're
basically
ignoring
that
one.
A
But
there
are
a
handful
of
feature,
is
added
to
bug,
fixes
patches
committed
to
Drupal
7.40
that
we
should
cross
for
four
back
job
for
our
next
minor
least
1.3.
This
is
a
user
experience
release.
We
have
a
ton
of
issues
that
are
tagged
if
you
check
out
the
milestone
and
get
help
with
1.3
point
out,
there's
a
ton
of
issues
that
are
user
experience
related
that
are
tagged
with
that
tag.
A
If
you
want
to
look
at
what
we'd
like
to
get
done,
a
lot
of
them
are
little
money
minor
fixes
that
we
can
get
done
in
merchant
anytime.
Some
of
them
are
bigger,
more
complicated
tasks
like,
for
example,
we
want
to
fix
the
field
you
I.
That
is
a
big
hard
task
in
will
likely
take
rewriting
a
bunch
of
stuff
in
order
to
get
in.
We
have
follow-up
issues
that
are
smaller
and
easier
to
get
done
like
fully.
A
Oats
module
has
a
bunch
of
new
features
we
want
to
include,
and
this
is
stuff
that
was
included
in
panels,
but
we
didn't
get
into
core
for
backdrop
yeah.
We
need
to
add
those
arms
to
make
the
experience
of
using
it
a
little
bit
richer
and
something
with
a
views.
You
I
there's
a
bunch
of
minor
follow
of
issues
that
we
want
to
get
into
backdrop
one.
A
It
also
looks
like
they're
people,
thinking
of
re
overhauling
the
views
you
I,
that's
not
something
I,
think
that's
on
the
road
map
for
backdrop,
one
but
I
think
it's
important
to
start
thinking
about
it,
because
that's
another
huge
task,
much
like
field
you
I.
We
know
you
see
eyes,
not
perfect,
and
it's
gonna
probably
take
a
lot
of
thinking
and
designing
and
mocking
up
in
order
to
get
that
right.
A
So
lots
of
work
on
that
as
well
and
then
there's
a
couple
of
little
issues
that
have
been
resolved
in
Drupal
8
that
have
not
yet
been
resolved.
In
fact,
I
think
would
be
good
to
reevaluate
things
like
cleaning
up
the
way
menus
work.
Getting
all
of
our
admin
listings
converted
to
views
just
a
bunch
of
little
tiny
tasks
that
we
should
get
done
just
to
get
them
off
our
to-do
list
and
to
be
feature
comparable
with
Triple
E.
A
A
It
would
also
be
good
to
make
sure
that
the
taxonomy
term
reference
it's
in
poor
matches
the
same
model
that
we
get
by,
adding
that
reference
in.
So
if
we
need
to
write
an
update
but
for
something
to
get
things
organized
in
the
same
way,
we
should
consider
that
carefully
as
well.
Another
thing
too,
it's
been
an
honor
list
for
a
while
now
is
getting
some
kind
of
redirect
ability
into
poor
and
I
think
that
there
are
some
easy
things
that
we
can
do
any
time.
A
A
more
complicated
interface
like
a
listing
of
all
of
the
redirects
in
poor
and
listings
on
any
given
node
of
redirects
to
perhaps
that
node
or
user
or
term
I
think
that
is
more
like
the
contributor
act,
module
functionality
we
have
now.
That
might
be
something
we
could
consider
putting
into
backdrop
1.4,
but
I'd
kind
of
like
to
see
redirect
module
develop
in
confers
before
we
just
go
ahead
and
shove
that
right
into
four.
So
it
would
have
to
follow
a
pattern.
A
Much
like
token
in
path
auto,
where
we
got
reported
first
and
then
we
go
to
the
ports
and
then
move
the
ports
in
the
core
with
whatever
necessary
changes.
I
think
will
be
great
if
we
did
that
same
thing
for
a
redirect.
So
if
we
can
get
I
know,
think,
there's
already
a
port
a
redirect
module
if
we
can
get
more
people
using
that
and
commenting
on
it,
it's
how
it
works.
What
you
like,
what
you
don't
use
your
experience,
feedback
stuff
like
that
on
the
task.
A
There
will
then
be
to
move
that
contribute
to
poor
and
if
we
can
get
the
global,
redirect
style
functionality
in
for
first
using
redirect
module
with
that
change
in
full
core.
I
think
would
also
be
good
to
to
make
sure
we
don't
end
up
in
the
infinite
redirect
loop
problem
that
we
have
all
the
time
with
Drupal,
sir
so
yeah
Hey
look.
It
looks
like
we're
using
redirect
module
on
backed
up,
so
you
must
at
work,
so
it
definitely
exists.
It
looks
like
Jeff.
A
Where
did
it
so
thanks
for
that
as
well,
but
that's
definitely
something
we're
thinking
about
for
our
future
roadmap.
So
far
we
have
some
of
these
thoughts
outlined
on
backdrop.
Cm
esta
hora
road
map
so
check
there
for
continuing
updates
as
we're
working
on
backdrop,
we're
always
interested
in
user
experience,
issues
and
developer
experience
issues.
A
So
if
you're
writing
a
theme
or
writing
a
module
or
writing
a
layout
or
just
building
a
website-
and
you
find
some
part
of
the
process
to
be
non
intuitive
or
overly
complicated,
open
an
issue
and
tag
it
with
a
DX
and
square
brackets
in
the
title,
because
that's
something
we're
going
to
need
to
solve.
Not
only
is
it
important
for
our
existing
people,
but
as
in
the
future
we're
trying
to
move
the
focus
of
backdrop,
its
target
market
is
going
to
expand
downstream
to
PHP
developers,
people
using
WordPress.
A
It's
got
to
be
more
intuitive
them
more
straightforward
for
everyone
to
use.
So
if
you
find
something,
that's
not
intuitive,
let
us
know
we
can
think
about
how
to
solve
it.
Some
of
those
shin
just
can't
be
done
in
the
12
x
release
cycle
because
they
might
require
api
changes,
but
it
is
good
to
know
about
them
and
start
thinking
about
how
we're
going
to
solve
that
in
the
future.
A
I
know,
Wes
and
I
have
kind
of
a
running
list
of
issues
that
come
up
when
deeming
sites
he
made
a
whole
bunch
a
long
time
ago,
which
is
fantastic.
I
just
started
working
on
my
first
backdrops
like
more
recently,
but
I've
also
been
developing
a
list
of
things
are
a
little
bit
a
little
bit
weird.
When
you're
building
themes
like
how
you
have
to
you
can't
really
target
of
use
block
adequately.
A
So
there's
that
I
think
we've
got
got
a
bunch
of
issues
if
I
clean
up
with
the
mark-up
to
as
well,
which
might
not
be
possible
in
the
one
actually
cycle,
because
we
don't
want
to
break
anyone's
existing
sites
so
trying
to
schedule
a
plan
for
the
future
of
hat
like
what
should
change
and
how
and
when
is
going
to
be
really
important.
So
definitely
on
them.
Let's
constantly
think
about
things
to
improve
and
we
can
get
some
kind
of
a
master
plan
going
for
backed
up
to
it,
mm-hmm
all
right.
A
So
every
Thursday
after
this
weekly
meeting,
we
usually
have
a
little
sprint
that
all
that
really
means
is
that
there's
more
people
in
IRC
our
IRC
channel
pound
backdrop,
there's
more
people
in
the
github
issue,
queue
if
there's
more
people
running
tests
and
working
on
problems
and
collaborating
things
on
Thursday
afternoons
than
on
other
days.
But
that
does
not
mean
that
Thursday's
are
the
only
day
that
sprinting
happens.
A
I
for
some
of
us
printing
happens
all
the
time,
so
I
would
say
if
you
can't
can't
get
time
on
Thursdays
to
work
on
factor,
but
you
want
to
work
some
other
time
log
into
IRC.
If
you
can
and
see
who's
there,
and
if
there
are
people
there
who
can
help
you
we're
going
to
help
you
no
matter
what
date
or
time
it
is
so
we'll
definitely
take
contribution
at
any
hour
of
any
day,
and
hopefully
we
can
be
around
to
help
with
that
process
as
well.
A
We
do
have
in
addition
to
being
active
on
github,
which
is
where
we
deal
with
all
of
our
issues
and
Oliver
code.
If
an
IRC
channel
pound
backdrop,
we
have
a
get
our
sorry,
a
sub
reddit
at
reddit
com,
/,
r,
/
backdrop
and
last
week
on
Mike
McAfee
also
asked
that
we
try
a
github
related
chat,
a
tool
called
get
ur,
so
I
created
one
of
those
for
backdrop
and
it
looks
like
anyone
I
created
it
specifically
for
the
backdrop
issues
project,
so
anyone
who's
killed,
committed
comment
and
even
on
any
issue.
A
In
the
backdrop,
history
has
access
to
that
chat,
room
I'm,
not
sure.
If
anyone
else
uses
get
er
but
I
figured,
we
could
create
one
and
see
if
it
caught
on,
because
it's
a
platform
that
people
were
I
get
already
familiar
with
using
that
might
be
a
better
place
for
us
in
the
future
than
IRC.
Just
because
IRC
seems
to
be
kind
of
a
subset
of
super
nerdy
people,
though
I
love
IRC.
There
are
also
some
issues
with
sometimes
connectivity,
so
it
runs
on
a
funny
port
and
I
thought.
A
That
might
be
a
good
thing
to
try
we'll
see
if
it
catches
on.
If
not,
we
don't
have
to
use
it.
If
so,
we
could
change
or
use
both
or
whatever.
So
that's
just
something
to
keep
in
mind
upcoming
events,
so
we
have
backed
up
meetings
every
Thursday.
It
stood
kind
of
a
checked
in
on
development
tasks.
We
have
active
design
meetings
every
other
stay.
We
have
a
couple
of
drupal
events
coming
up.
A
A
Mid
camp
Andy:
do
you
know
the
dates
for
that
one?
Does
anyone
know
it's?
Okay,
I
just
figured
your
closest
okay,
yeah
I'll
check
my
email
and
we'll
get
that
on
the
calendar.
To
put
your
boot
camp
chicago
known
as
mid
camp
is
also
coming,
if
I
believe
in
March
and
then
yeah
well,
we'll
try
and
get
the
website
up
and
running.
So
people
can
post
their
own
events
and
then
you
don't
have
to
rely
on
this
meeting
or
are
I
calfee
in
order
to
find
out
about
them.
A
A
That's
fry
it
all
right,
I'm,
going
to
post
the
link
to
get
er
in
in
the
issue
queue
or
in
the
in
the
chat
here.
It's
basically
get
ur
da
IM
/
and
then
whatever
the
name
of
your
project
is
so
including
the
project
in
the
repository.
So
in
this
case
it's
/
backdrop
/
backdrop
dash
issues
I'll
also
put
post
a
link
in
in
the
agenda,
but
yeah.
It
does
look
a
lot
like
slack,
which
I
must
admit.
I
really
like
slack.
A
B
Don't
think
so
Andy
asked
if
there
was
anything
new
in
layouts
land,
doc,
wawa
filed
for
request
a
while
back
to
add
one
field,
/
I
know
one
block
per
field
and
that
issue
is
actually
really
really
close.
I
think
that
functionality
wise
it's
looking
great
there's
couple
of
minor
things
like
the
modal
dialog,
always
says,
like
add
field
block.
When
really
should
say
you
know,
add
body
field,
but
that's
like
really
minor
UX
thing
and
it
needs
tests.