►
From YouTube: Backdrop CMS weekly 7/2
Description
Weekly check in on development and infrastructure tasks for Backdrop CMS
A
Alright,
we
are
on
air,
it
is
thursday
july.
Second,
so
happy
july,
everybody
big
summer,
beautiful
weather,
well
good
stuff,
we're
going
to
do
a
quick
check
in
on
development
and
in
for
infrastructure
tests
for
backdrop
CMS
and
at
the
end,
we'll
have
a
section
for
questions,
comments
and
anything
that
we
haven't
gotten
and
covered
in
our
agenda.
So
to
start,
we
general
announcement
same
as
always.
We
have
phpstorm
licenses
for
anyone
who
is
a
backdrop
developer.
A
So,
if
you
remember
the
backdrop
contribute
you
can
send
the
email
to
info
@
backdrop,
CMS
organic,
its
annual
license
key
if
you
are
a
backed-up
developer,
but
not
part
of
the
contribute.
Yet
the
requirements
getting
the
license
is
just
being
a
member
of
that
group,
which
means
you
need
to
have
ported
or
created
a
module,
femur
layout
to
a
backdrop
and
released
it
into
that
group.
But
you
haven't
created
ones
that
you're
a
nurse
and
maintaining
one.
A
B
Yes,
of
course,
okay,
so
every
week
we
go
over
the
number
of
projects
and
everything
that
we
have
in
github
and
we
have
38
total
contributed,
are
38
total
backdrop,
contribs
we're
looking
for
more
control
authors,
if
you're
interested
in
porting
the
module
or
running
a
brand
new
module
for
backdrop,
you
can
join
the
backdrop,
contribute
under
github.com
/
backdrop,
ops,
/,
contribs,
a
shoe
queue
for
going
over
project
applications
and
our
application
process
is
really
pretty
streamlined.
It's
just
file
an
issue.
B
B
B
That
is
working
and
we're
collecting
project
usage
data,
but
we're
not
just
playing
that
anywhere
yet
and
we're
just
kind
of
moving
along
there.
It's
we've
gotten
a
little
bit
hung
up
on
designs,
but
we've
got
some
news
on
that
later
for
project
listing
pages.
Let's
see
you
want
to
talk
about
dressed,
Jen
sure.
A
A
What
was
necessary
in
order
to
make
that
happen
is
to
kind
of
abstract
this
rule
out
of
josh,
which
is
something
Josh
maintainer
wanted
to
do
anyway,
because
a
Drupal
7
in
Drupal
8
are
different
enough
that
they
needed
to
have
different
controllers
for
the
way.
Those
two
things
worked,
I
figured
if
they
could
kind
of
abstract
that
out.
We
could
use
that
abstraction
for
best
rap
as
well.
A
He'll
help
us
fix
them,
which
is
great,
but
we
need
to
kind
of
create
a
use
case
where
we
can
run
into
in
those
problems
so
that
they
can
be
fixed.
So
it
looks
like
yeah
it's
been
about
a
month
since
anyone's
worked
on
that
it
looks
like
Jeff.
You
were
probably
the
last
one
to
work
on
it.
So
you
probably
know
more
than
I
do,
but
was
that
kind
of
a
of
a
plan
to
go
forward?
Just
get
some
sticking
point
to
none
sticking
at
those
result
to
get
that
sorted
out.
A
So
coming
it's
not
here
yet,
but
it's
it's
close.
Anyone
who's
super
interested
in
working
on
Direction
wants
to
jump
in
on
that
issue.
It
would
be
great
to
have
some
new
eyes
on
the
problem
and
help
kind
of
move
that
forward,
but
we
will
get
it
sorted
out.
The
next
thing
on
our
list
in
terms
of
getting
work
done
for
a
backdrop.
A
It
is
getting
our
primary
website
backdrop
CMS
org,
ready
for
prime
time,
and
what
we've
been
doing
for
the
last
few
months
as
Nate
mentioned,
is
aggregating
all
the
information
from
github
in
our
kinship
group
about
module,
stains
and
layouts
aggregating
that
information
over
onto
our
primary
websites
that
we
can
build
a
page
that
will
allow
you
to
search
for
consciousness
and
layouts
for
backdrop.
So
obviously
github
is
really
hard
to
find
anything
on
dribbble.
That
work
is
also
kind
of
hard
to
find
things
on.
A
So
we're
looking
at
other
projects
around
the
web,
how
they
guide
people
to
their
extensions
or
plugins
or
whatever
they're
called
in
trying
to
steal
what
we
like
from
everything
and
create
the
best
possible
way
for
people
to
be
able
to
find
suffer
backdrop.
We
currently
have
designs
now
for
the
modules
page
in
themes
page
and
we
have
a
working
design
for
much
like
a
project
page
like
once.
You've
actually
got
that
age,
so
we're
ready
to
start
building
those
I
know.
A
I
suspect
some
supporters
list
of
themselves.
In
a
backdrop,
services
directory
cuz
I've
already
had
people
coming
up
and
saying
well
how
to
have
been
developer.
It's
been
working
on
backdrop
and
sig.
Well,
we'll
build
that
for
you
later,
but
first
we
need
to
build
backdrop.
Well,
you've
got
some
good
long-term
plans,
for
you
know
the
stuff.
Those
worked
really
well
for
the
Drupal
community.
A
We
want
to
kind
of
have
the
same
resources
for
ease
of
active
community
as
well,
and
we
will
actually
get
there,
but
that's
kind
of
the
end
of
our
infrastructure
to
do
list
and
we're
going
to
do
a
little
checking
on
backdrop.
The
project
now
as
well,
so
it
looks
like
we
are
currently
working
on
our
next
minor
release,
is
going
to
be
back
drop.
One
point
one
point
three,
and
what
we're
trying
to
do
is
get
all
of
our
cross
ports
from
Drupal
7,
so
anything
that's
been
fixed
in
Drupal.
A
7
should
also
be
fixed.
In
backdrop,
looks
like
we
have
one
remaining
cross
port,
just
checking
to
see
if
this
one
hasn't
been
merged
to
looks
like
it's
still
open,
which
is
pretty
good
and
and
then
we
also
have
a
bunch
of
work
going
on
to
improve
the
layout
cui.
So
this
is
layouts
is
something
that's
new
to
backdrop.
A
We
rewrote
the
UI
for
panels
and
we
know
that
when
we
put
it
in,
it
was
kind
of
a
Minimum
Viable
Product
and
there
was
lots
of
improvement
and
now
we're
getting
a
bunch
of
really
great
feedback
from
everybody.
Who's
been
using
it
what's
confusing
what
makes
sense
you
know
bugs
that
need
to
be
sorted
out
or
clean
up
on
on
various
different
things,
so
we
think
it
would
make
it
easier
and
more
intuitive
people
to
use.
So,
thank
you,
everybody
for
using
it.
Thanks
for
writing
feedback
Thank
You
everybody's
working
on
it.
A
I
am
really
looking
forward
to
getting
some
of
those
fixes
in
and
it
looks
like
we
have.
You
know,
11,
really
long,
major
issue,
which
I
think
is
number
90
93,
it's
not
linked
on
here,
but
then
we
have
a
whole
bunch
of
little
tea
or
no
here
it
is
this.
Is
it
345,
but
a
whole
bunch
of
little
teeny-tiny
follow-up
issues
to
that
people
are
tagging
in
the
queue
with
layouts,
UI
and
square
brackets?
A
So
if
you're,
a
particularly
passionate
about
cleaning
up
the
layout
COI,
there's
plenty
of
well
hanging
for
that
it
can
be
worked
on
as
well,
which
is
great.
We
also
have
a
couple
of
responsiveness,
responsiveness,
issues
with
best
dress
and
backdrop
is
responsive
out
of
the
box,
which
is
something
that
Drupal
wasn't,
but
we've
inherited
a
bunch
of
Drupal
code.
Like
the
use
UI,
which
is
not
responsive,
so
we
have
a
little
cleanup.
We
need
to
do
in
order
to
make
sure
the
front-end
responsive
and
the
backends
responsive.
A
Just
so
we
can
kind
of
stick
to
our
guns
about
backed
up
being
responsive
a
box.
So
there's
a
couple
of
minor
issues
working
on
those
two
and
as
any
of
these
things
get
done.
That
might
be
a
good
time
for
us
to
release
another
minor
version
of
backdrop.
We
don't
have
any
security
issues
right
now,
but
should
a
security
issue
come
out
that
we
need
to
issue
a
new
release
for
we'll
go
ahead
and
cut
that
with
the
commits
already
in
there
now?
A
Many
of
this
other
stuff
gets
done
like
a
cross
board
or
layout
UI
improvements
or
responsiveness.
Bob
successful
get
those
in
there
too.
So
with
nothing
super
junt
right
now,
but
we
as
things
come
up,
we
will
reevaluate
terms
of
putting
a
release
date
on
point
one
point
rates:
it
looks
like
we
have
a
bunch.
We
have
a
milestone
in
the
issue.
Queue
for
one
point,
one
point:
three:
we
haven't
tagged
anything
specifically
for
that
release,
but
we
can
do
that
in
future
if
it
becomes
necessary.
A
Okay
backed
up
one
point
to
this:
is
our
minor
release
a
little
bit
more
exciting
we're
planning
on
rolling
out
new
features
for
backdrop
every
four
months
so
bat-rope
one
came
out
in
January
backdrop,
1.1
came
out
in
May,
backed
up
1.2,
welcome
at
September
15th
on
our
agenda
for
backdrop.
1.2
first
and
foremost
is
rich
text.
A
Editing,
so
neat
I'm,
not
sure
if
there's
any
significant
update
since
last
week,
but
I'm
super
excited
about
having
her
text
editing
for
I've
been
spending
the
last
probably
month,
working
on
setting
up
rich
text,
editing
in
Drupal,
7
and
I
am
completely
embarrassed
by
how
horrible
it
is
to
get
a
good
experience
and
I'm
really
looking
forward
to
switching
everyone
over
to
backdrop.
Come
September
16th,
where
everything
will
be
perfect.
So
maybe
honey
gives
enough
to
know
where
that
did
yeah.
B
There's
there's
not
too
much
since
last
week,
although
we
did
get
some
more
testing.
Thank
you.
Everybody
that's
been
trying
out
that
issue
with
issue
101
in
issue
queue.
There's
that
there's
not
actually
a
pull
request,
but
there's
an
entire
branch
of
work,
1
dot
x,
dash
WYSIWYG
is
the
branch
that
you
can
clone
right.
Out
of
the
backdrop
repository
to
check
out
the
latest
work
there
and
the
latest
status
is
that
everything
is
working
really
pretty
well.
B
It's
a
little
bit
rough
because
we
don't
have
JavaScript
based
testing,
but
we
should,
at
the
very
least,
add
some
tests
to
make
sure
that
the
binding
of
editors
to
text
formats
and
the
configuration
forms
and
things
like
that
safe
and
then
once
those
new
tests
are
done.
I
think
that
we're
ready
to
merge
our
initial
pull
requests
into
the
project,
which
is
very
exciting
to.
A
B
A
Great
well,
that's
fantastic
I'm,
so
looking
forward
to
getting
that
in
aa.
The
next
thing
that
we
want
to
include
in
core
is
the
date
module.
This
is
a
module
that
provides
a
date
field
date,
modules
already
forded
the
backdrop
which
is
great,
which
need
to
figure
out
how
to
get
it
in
core
and
of
the
date
module.
There
are
a
whole
bunch
of
moving
pieces
that
we
may
or
may
not
want
to
include.
One
of
the
things
that
is
particularly
hard
to
deal
with
in
general
is
repeating
Bates.
A
I.
Also
think
that
the
date
modulus
is
now
comes
with
a
whole
bunch
of
different
database
types
like
what
do
you
want
a
date
time
field
or
just
date,
field
or
a
date
like
it
is
a
timestamp
instead
and
that's
the
kind
of
question
where,
when
somebody's
setting
with
a
content,
type
you're
asking
and
end-user
what
their
architecture
should
be
and
I'm
not
really
sure,
that's
the
best
user
experience
for
people.
A
I
think
it
would
be
good
for
us
to
kind
of
examine
why
these
three
different
formats
exist
and
outline
the
three
you
use
cases
for
them
and
see
if
all
of
them
are
actually
necessary.
If
we're
still
only
supporting
one
database
in
court.
I
have
a
feeling.
Some
of
these
things
are
here,
because
when
you
needed
an
on
my
sequel
database,
you
can
rely
on
a
nice
equal
date
column,
and
so
you
need
to
use
the
unix
timestamp
unix
time
since
have
problems,
because
you
can't
deal
with
time
zones
correctly.
A
So
I
think
it
will
be
good,
just
kind
of
evaluate
the
landscape
and
say
like.
Maybe
we
really
only
need
a
my
sequel
date,
and
why
do
you
need
a
my
sequel
day
and
in
my
sequel
daytime
like
shouldn't
that
just
be
like
you
know,
can
we
label
that
differently
for
people?
So
if
anyone
I
know,
there's
a
lunch
of
people
are
doing
work
on
dates,
which
is
great.
If
anyone
has
any
feedback,
if
you
could
weigh
in
in
those
issues
and
say
like
yes,
you
know,
remove
recurring
dates,
make
that
contribute
whatever.
A
I
think,
it'll
help
us
with
our
path.
Decor
and
there's
definitely
some
things
in
the
date:
module
that
need
to
be
part
of
core
and
some
things
that
need
to
eat
the
date
field,
module
and
helping
us
kind
of
draw.
Those
lines
is
so
like
what,
in
you
know,
if
we
did
move
recurring
dates
and
to
contribute
need
to
have
in
core
and
what
would
be
to
add
itself.
So,
even
though,
like
moving
a
module,
decor
doesn't
sound
really
hard
in
the
case
of
date.
There
are
some
hard
questions
we
need
to
figure
out.
A
On
the
other
hand,
we
have
a
bunch
of
other
modules,
are
moving
to
court
like
link
and
email
field,
and
I
think
for
some
of
those
it
is
really
a
simple
eustacia.
Just
take
this
module
and
stick
it
inside
the
you
know,
fields,
module
or
just
inside
the
core
modules
folder
and
we'll
call
it
good
I
think
there
are
there's
room
there
for
usability
improvements
and
in
terms
of
looking
at
the
UI
and
trying
to
figure
out.
A
If
all
these
features
are
necessary,
but
I
think
for
the
most
part
like
these
are
proven
and-
and
there
aren't
there
aren't
a
lot
of
bells
and
whistles
attached
to
something
like
a
link
view,
and
we
can
just
that
in
a
be
fine
I
know,
people
have
been
working
on
it
and
haven't
been
looking
at
the
poor
across
lately,
but
it
would
be
great
if
we
could
get
parish
for
those.
Oh
wait.
We
have
some
yeah.
B
B
Basically,
the
controversial
of
link
module
just
straight
up
with
no
modifications
but
looks
like
all
the
tests
are,
are
completed,
ported
and
functioning
other
than
that's
one
failure,
but
we've
got
that
resolved.
So
fantastic
I
think
it's
time
for
us
to
take
a
look
at
it
and
kind
of
decide.
If
there's
any
functionality
that
we
absolutely
like
should
not
include
in
core
and
consider
perhaps
trimming
it
down
a
little
bit,
but
it
looks
like
it's
doing
really
well,
I'm,
not
sure
about
upgrade
path
on
that,
but
we
might
need
to
take
a
look
at
that.
A
Great
alright,
so
we
also
have
a
github
issue
tag
for
1.2
right
now.
There
are
a
lot
of
things
slated
for
that
other
than
these
field
modules
for
the
email
link
and
then
the
rich
text
editor.
But
if
we
have
people
who
are
working
on
things
that
they
think
field
modules
in
particular,
I
think
should
be
added
to
core.
We
got
a
working
for
work,
West,
there's,
no
reason
we
can't
add
those
to
the
next
release
as
well.
A
We
also
have
our
public
road
map
in
terms
of
what
is
in
store
for
the
future
of
backdrop
of
backdrops
and
last
org,
slash
road
map,
and
that
contains
one
point
to
which
we
just
talked
about,
but
also
1.3,
and
then,
of
course,
what's
going
to
go
into
serious,
long-term
things
and
still
under
debate
that
will
be
determined
by
you
guys
and
what
you
do
with
backdrops
today
and
we
think
it
gets
do
in
future.
So
keep
that
in
mind
too.
A
A
There's
a
whole
bunch
of
stuff
we're
always
working
on
improving
in
back
jobs,
user
experience,
issues
and
developer
experience.
Issues
in
particular
are
things
that
are
really
important
to
us,
because,
even
though
right
now,
our
target
audience
are
people
who
have
existing
Drupal
7
sites
and
want
to
upgrade
to
backdrop
long-term.
A
A
Every
Thursday
we
usually
have
a
little
backdrop
sprint
we
meet
after
this
meeting
in
IRC.
The
channel
is
pound
backdrop
where
we
can
all
talk
about
github
issues
or
points
for
the
future
or
what
you're
doing
effective
tomorrow
and
try
and
get
a
bunch
of
work
done.
So
if
you
can
get
your
boss
or
your
client
to
devote
some
time
to
backed
up
to
development,
Thursday's
are
really
great
time
to
do
that,
because
there's
a
whole
bunch
of
other
people
working
on
backed
up
at
the
same
time.
A
Of
course,
any
day
is
fine
evenings
and
weekends
also
accepted.
If
anyone
has
time
they
want
to
work
on
backed
up
we'll
take
whatever
you
got,
the
IRC
channel
pound
backdrop
is
a
good
place
to
find
help.
You
can
also
jump
in
if
IRC
isn't
your
thing,
we
have
a
subreddit
at
reddit
com,
/,
r,
/
backdrop.
A
So
if
you
guys
are
giving
a
talk
about
backed
up
somewhere,
let
us
know
and
while
I
just
calendar,
I
think
we
currently
have
science
on
drupal
coming
up
july,
14
through
17
drupal
corn
july
30,
throughout
august
first
and
pennsylvania,
drupalcamp
august
first
to
second
in
drupalcamp
la
August
twenty-ninth
through
30th.
Those
are
what's
coming
up
in
the
next
two
months
and
if
anyone
has
anything
else,
let's
no
throw
it
on
calendar
in
general.
It's
really
great
to
have
people
talk
about
backdrop
that
are
not
me
and
myself.
A
So
if
any
of
you
want
to
focus
on
a
specific
area
that
would
be
fabulous,
we
have
had
I
think
three
different
people
giving
backdrop
luck
so
far
and
we
have
a
couple
of
sets
of
slides.
That
I
think
would
be
useful
for
us
to
put
in
some
public
domain
if
anyone
wants
to
give
a
talk
or
later
to
any
of
those
with
you
give
those
resources
out.
But
you
know
more
opinions
are
always
good,
so
come
up
with
your
own
stuff,
that's
even
better
or
bottom.
You
know
take
ours
and
improve
them
right.
A
Let's
see
the
last
version
of
the
Drupal
watch.
Jaws
magazine
had
a
seven
page
feature
article
on
backdrop
that
just
became
available
online
I
think
today
or
maybe
yesterday.
So
if
anyone
who
hasn't
read
the
paper
version
of
the
magazine
wants
to
read,
the
online
version
go
ahead
and
check
out
triple
walk
jog
and
you
can
find
backdrops
article
there
really
useful
stuff.
A
There
is
that
it's
outlining
the
significant
differences
between
backdrop
for
Drupal
7,
including
how
your
code
will
differ
in
your
theme,
how
to
use
cmi
the
configuration
management
tools
to
deploy
your
code
in
files
and
how
to
use
the
new
layout
system.
So
people
who
are
super
technically
interested
in
what
those
differences
are
and
what
problems
they
solve
will
be
able
to
read
more
about
it.
There
is
there
anything
else.
We
should
talk
about
how
we
didn't
talk
about
project
browser
again,
Nate
I,
don't
know
it's
like.
A
We
have
some
kind
of
mental
block
to
actually
talking
about
this
tool,
which
is
sad
because
it
is
going
to
be
the
coolest
feature
ever.
But
basically
we
have
we're
going
to
have
this
modules
page
on
back
from
CMS
org,
where
you
can
search
for
a
module
and
then
you
can
like
download
it
put
on
your
site,
but
it'll
be
so
much
better.
A
If,
when
you
were
actually
on
your
back
drops
that
you
could
go
to
the
modules
page
and
search
for
a
module
right
there
and
click
a
button
and
how
to
automatically
install
this
is
a
tool
that
WordPress
has
worked
as
users
love
it.
We
have
like
half
of
this
tool
right
now
because
it
lives
in
Drupal
7,
where
you
can
paste
a
URL
into
a
page
on
your
site
and
it'll
install
module,
but
we
want
the
actual
browser
in
there
and
we've
been
doing.
A
There's
a
whole
ton
of
people
doing
a
whole
bunch
of
work
on
this.
On
a
for
backdrop,
which
I
think
is
greatly
supported,
some
more
could
happen
for
drupal
7
and
I
think
we're
pretty
close
to
getting
that
done.
We
are
trying
to
set
up
a
second
server
just
for
the
module
searches
so
that
we
don't
end
up
overloading
our
primary
sites
with
people
who
are
searching
for
modules
on
their
sites,
but
I
think
as
soon
as
we
get
that
done.
A
This
is
going
to
be
ready
for
some
serious
testing
and
I
would
love
it.
If
we
could
get
this
feature
in
for
1.2,
I.
Think
it'll
be
game
changer,
any
other
updates
on
that
No,
ok,
father
than
that
is
there
anything
else
that
we
haven't
talked
about
in
this
meeting
that
we
should
talk
about
or
any
questions.
Anyone
has
that
we
can
answer.
A
Sounds
pretty
quiet?
Okay?
Well,
then,
what
we'll
do
is:
go
ahead
and
wrap
up
this
meeting
and
jump
in
IRC
start
working
on
the
issue.
Queue
I
have
a
bunch
of
issues
that
I
want
to
play
with
today
and
yeah.
Hopefully
we'll
keep
pushing
this
thing
forward.
So
thank
you
all
for
joining
and
we
will
see
you
on
the
Internet
I
guess.