►
From YouTube: Backdrop CMS weekly 6/25
Description
Weekly check-in on Backdrop CMS progress.
A
We
are
on
air,
it
is
Thursday
jun
25th
and
we're
going
to
do
a
quick
check
in
check
check
up
check
in
on
all
of
the
tests
for
backdrop,
CMS
general
announcements.
We
do
still
have
some
free
phpstorm
licenses.
So
if
there
are
people
who
are
working
on
backdrop
for
a
member
of
the
contribute
and
want
a
license
to
use
phpstorm
email
info,
effective
CMS
that
organ,
we
will
help
distribute
those
for
people
who
are
working
on
backup
and
are
not
yet
members
of
the
contribute.
A
You
can
send
us
an
email
any
way
we
can.
Let
you
know
what
are
the
steps
involved
in
in
getting
in
that
contribute
to
get
you
become
a
contributed
module
theme
or
layout
author
or
maintain
here
no
updates
from
the
pmc
business
as
usual
here
at
backdrop,
land
Nate,
you
want
to
talk
about
community
growth.
B
Yeah,
so
we
have
38
total
members
of
the
backdrop
contribute.
We
haven't
had
any
new
applications
in
the
past
week,
but
we're
still
moving
forward
and
contributing.
There's
extra
been
a
lot
of
activity.
Bleeding
reports
in
particular
date
modules
been
getting
a
whole
heck
of
a
lot
of
work
as
of
late,
so
that's
been,
but
we
have
129
total
projects
for
backdrop.
C
A
B
A
C
A
Yeah,
ok,
sorry,
I,
don't
know
what
this
deal
is.
Ok,
so
we
have
30,
contributed
and
29
projects
for
backdrop.
Cms
we've
got
one
new
one
since
last
week
and
53
to
have
official
releases
on
factor
of
CMS
org
with
three
new
ones
since
last
week.
So
just
a
recap
what
Nietzsche
said
in
terms
of
our
infrastructure,
we
have
a
beep
checking
running
on
on
backdrop,
the
software,
so
that
your
individual
backs
of
sites
will
check
with
backdrops
server
to
find
out
what
versions
need
to
be
updated.
A
If
you
have
a
contributor
lease,
but
you
think
it's
ready,
you
can
tag
that
project
with
1
dot
x,
dash,
wanda,
x,
dot
y
in
order
to
have
backed
up
CMS
or
pick
up
that
official
release,
and
then
it
will
be
able
to
tell
people
to
update.
So
if
you
have
a
new
module,
that's
a
good
way
to
tag
it
also,
if
you
have
an
existing
module
or
theme
or
layout,
that
has
updates,
and
you
want
people
to
be
aware
of
it.
Hiking.
A
Those
just
like
we
did
on
the
Borg,
except
for
with
a
semantic
versioning
in
that
minor
version,
is
the
way
to
do
it.
We
have
one
bug
with
that
system
that
we're
aware
of
that.
We
will
eventually
fix
it's,
not
a
huge
deal,
but
it's
a
little
bit
frustrating.
So
we've
got
a
document
here
in
this
agenda.
A
If
anybody
wants
to
play
with
the
project
module
for
backdrop
and
the
integration
that
might
be
a
fun
place
to
take
a
look
at
that
see
if
you
can
submit
a
pull
request,
otherwise
we'll
get
to
only
get
to
it
project
usage.
So
on
drupal.org
they
have
really
cute
little
charts
that
map
project
usage
over
time.
We
don't
have
those
charts
in
a
vehicle
got
Jeff
bond.
You
will
eventually
get
there
that
were
aware
of
that.
We
will
eventually
fix
it's,
not
a
huge
deal,
but
it's
a
little
bit
frustrating.
A
We
can't
guess
eighty
percent,
if
we
don't
have
adequate
statistics
a
lot
of
times,
we
can
guess,
but
sometimes
it's
a
little
contentious
and
it
will
be
good
to
have
some
actual
numbers
associated
with
those
things.
So
you
have
some
ideas
and
then
in
mind
for
the
future
of
a
project
module
speaking
of
project
module,
which
we
forgot
in
the
last
few
weeks,
we're
also
working
on
building
a
browser
that
will
live
in
backdrop
itself.
A
So,
as
you're
running
your
backdrop
site,
if
you
go
to
the
modules
page
right
now,
it'll
show
a
list
of
all
the
modules
already
have
and
there's
a
tab
at
the
top
that
lets
you
install
new
modules
directly
from
back
dress
and
the
way
that
works
now
is
that
you
have
to
go
to
the
page
where
the
module
is
find
a
URL
and
paste
it
into
a
field
on
your
local
site
or
your
backdrop,
site,
hosted
or
otherwise,
and
it
will
copy
the
files
over
and
install
them
for
you.
So
what
would
that
would
be?
A
Even
better
would
be
if
we
could
actually
let
you
browse
for
those
projects
right
there
on
that
page.
So,
rather
than
making
you
leave
that
page
and
go
to
the
other
website
find
the
module
you
want
install
it
that
way,
we
want
the
browser
to
be
right
there
and
we've
had
a
whole
bunch
of
great
work
happening
on
that
issue,
so
that
is
issue
number
eight.
Seventy.
This
is
a
huge
usability
thing.
Wordpress
users
have
this:
they
love
this.
It's
been
an
issue,
one
triple
that
work
for
really
long
time.
There's
a
whole
bunch.
A
People,
the
Drupal
community,
who
want
it
and
it's
just
never
managed
to
get
it
in
court,
I,
would
love
if
we
get
this
feature
and
backdrop
I
think
it
would
definitely
help
solidify
our
position.
As
being
you
know,
target
a
little
bit
tour
more
towards
those
wordpress
people
and
giving
them
the
tools
they
really.
No
one
love
so
I'm,
looking
forward
to
seeing
that
move
forward,
looks
like
that's
progressing
with
lots
of
momentum.
A
So,
thanks
to
everybody
who's,
given
it
a
try,
think
someone
who's
working
on
it
and
hopefully
we'll
get
it
in
for
backdrop,
1.2
other
things,
we've
morecambe
lately
is
dressed
for
a
backdrop.
We
know
this
is
kind
of
a
deal
breaker
for
a
bunch
of
people
who
use
Drupal
today
and
love
using
dresses
if
they
don't
have
to
rush
for
backup,
they're
less
excited
about
it.
A
I
know,
for
me:
I
used
rush
all
the
time
every
day
I
use
it
and
I
love
it
and
I
comb
and
rushes
the
best
thing
ever
I
can't
wait
till
we
have
this
for
backdrop.
We've
got
an
issue,
it's
issue
number
47
and
where
we
have
abstracted
the
Drupal
out
of
josh
and
we
are
working
on
a
dress
compatibility
layer
for
drupal,
so
it's
basically
a
file
that
has
all
the
definitions
of
how
Josh
commands
will
work
in
backdrop.
A
There
are
a
couple
of
sticky
places
where
just
you
know
what's
designed
to
work
on
through
poem,
we
need
to
sort
through
the
stickiness
and
either
get
fixes
into
dress
or
fixes
into
backdrops
version
of
its
commands.
In
order
to
get
that
worked
out
and
we're
gonna,
you
know
those
those
are
going
to
go
pretty
slowly.
A
Every
time
we
get
one
of
these
huge
major
roadblocks,
there's
probably
in
the
visa
back
and
forth,
required
between
people
working
on
back
trapping
people
working
on
Josh,
but
we
are
working
on
it
and
hopefully
we'll
have
that
out
and
ready
soon.
Other
things
we're
working
on
that
are
of
urgent
importance
is
our
flagship
website
factor
of
CMS
org.
We
have
dezeen
designs
already
for
the
find
the
module
page.
A
A
After
we
get
the
find
and
module
team
in
layout
pages
done,
we
also
have
plans
for
adding
some
other
new
features
to
our
flagship
website,
including
a
showcase
site.
So
anyone
who's
built
a
site
in
backdrop
will
be
able
to
post
their
sites
and
information
about
it
and
link
back
to
that
site
right
in
our
gallery,
and
we
also
want
to
build
a
place
where
people
who
are
interested
in
backdrop
can
find
service
providers
so
hosting
companies
that
will
host
their
site
developers
that
are
developed
their
say
designers.
A
Little
designed
for
their
site,
all
of
the
same
infrastructure
that
exists
around
Drupal
projects
today
will
eventually
exist
around
backdrop
projects
and
be
great.
We
give
them
a
business
listing
service
and
throw
that
up
there
as
well
and
then,
as
it
related
to
service
providers.
We
also
want
to
build
a
job
site
Drupal.
That
work
has
a
really
great
new
job
site.
That's
out
there.
A
We
could
do
the
same
thing
for
master
up
anyone
who's
looking
to
hire
backed
up
developers
all
of
that
on
and
then,
of
course,
an
event
calendar
for
anyone,
who's,
throwing
the
backdrop
camp
or
conference
or
meet
up
and
just
have
that
all
aggregated
in
the
same
place
to
obviously
we
don't
have
that
great
big
demand
for
all
that
stuff
yet
because
we're
still
so
new,
so
that
is
lower.
Priority
want
to
make
sure
that
people
use
dr.
A
up
first
before
they
can
celebrate
the
fact
that
they're
using
backdrop
so
first
things,
first,
okay,
so
that's
all
of
the
infrastructure
tests
that
we're
working
on
right
now.
A
Next
up
we're
going
to
talk
a
little
bit
about
backdrop,
the
project,
Excel
and
all
the
things
that
we're
working
on
for
the
next
major
and
minor
versions
of
that
job.
So
in
the
1.1
version,
which
was
released
on
May
fifteenth,
we
have
included
a
whole
bunch
of
backports
from
the
latest
versions
or
Ford
for
its
cross
ports
from
the
latest
version
of
Drupal
7,
the
I
think
one
or
two
remaining
and
we've
got
poor.
What's
up
for
those
already
I'm,
not
sure.
A
All
night,
if
you're
talking,
we
can't
hear
you,
but
if
you're
typing-
okay,
not
not
yet
all
right,
we
have
a
couple
more
security
fixes.
It
looks
like
to
that
worried
that
were
included
in
the
latest
security
release,
interval
that
are
also
in
the
latest
release
of
backdrop
and
we've
got
a
whole
bunch
more
little
tiny
improvements
to
big
changes
that
went
into
1.1,
so
we've
gotten
an
entirely
new
administrative
administrative
interface,
look
and
feel
we're
going
to
have
improvements
to
that.
Coming
in
we've
got
like
layouts
to
UI
improvements.
A
We've
got
changes
to
some
of
the
status
report
and
steps
messages
and
stuff
like
that.
So
if
that
got
a
couple
of
little
follow-ups
that
we're
working
on
for
that
as
well,
in
terms
of
bugs
and
other
things,
you
know
we
don't
have
anything
seriously
urgent
in
terms
of
needing
to
schedule
our
next
bug-fix
release,
but
should
something
come
up?
A
A
1
point
2
point
0
currently
scheduled
to
be
released
on
sep
tember
15.
We've
got
a
bunch
of
really
exciting
new
features
going
in
first
and
foremost,
WYSIWYG,
which
we
are
not
calling
was
he
like
we're
calling
rich
tech.
So
maybe
once
given
up
update
on
me,
rich
text
editor
stuff.
B
B
There's
a
branch
called
wanda
x,
dash
WYSIWYG,
which
is
our
feature
branch
for
the
WYSIWYG
functionality.
I
mean
rich
text
functionality
and
it's
coming
on
great.
We
had
a
whole
bunch
of
people
jump
into
the
issue
and
that's
the
branch
this
past
week
and
it
seems
like
for
just
about
everybody.
Now
the
functionality
is
working
really
well.
We
have
native
dialogues
for
inserting
images
and
links
you
can
float
and
align
images
left
and
right
as
well
as
caption
using
CGI
editors,
widget
support.
B
All
of
the
tests
have
been
updated
so
that
they're
functioning,
so
we
have
under
percent
test
rate
right
now.
However,
we
need
new
tests
for
the
new
functionality.
That's
been
added,
so
all
of
the
old
tests
are
all
king
and
everything
was
cooked,
but
we
need
to
expand
the
test
coverage
to
actually
include
everything
else.
B
I
personally
think
they're
kind
of
at
the
MVP
level
of
of
effort
here,
where
we
have
all
of
the
base
functionality
in
and
everything
is
working
and
there's
not
too
much
that
causes
problems,
but
but
we
may
need
to
do
a
little
bit
more
testing
to
actually
establish
that
I.
Think
what
we'll
start
doing
this
will
start
spinning
off
new
issues.
Issue
101
is
currently
we're
all
that's
happening,
but
I
think
it
because
idea
to
start
something
up.
B
New
issues
for
things
like
file
uploading
into
a
WYSIWYG
which
has
a
couple
of
different
moving
pieces
right
now.
The
patches,
so
are.
The
pull
request
is
so
huge,
like
it's.
B
Stabilized
in
getting
the
test
ready
and
then
merging
that
in
and
then
completing
a
bunch
of
follow-ups
and
subsequent
issues
on
great
there's.
No
doubt
in
my
mind
that
it
will
be
ready
for
the
sep,
tember,
15th
release
and.
A
B
Be
there
in
place,
but
you
know,
as
with
everything
else,
was.
A
Well,
kick
anything
we
don't
finish
the
next
release?
Yes,
okay,
all
right,
so
that
is
our
biggest
and
most
crazy
issue
that
we're
shooting
for
for
1.2.
But
we've
got
a
whole
bunch
of
other
stuff
too.
That
we
thought
might
be
a
little
bit
easier
to
get
done
like
including
modules
that
provide
field
types
and
on
our
short
list
for
those
we've
got
date.
Date:
module
link,
module
and
email
field
module.
A
Let's
see,
let's
see
if
we
can
get
a
date
update
on
link
module
from
Jeff
I
know,
we've
got
a
pull
request
for
that.
Make
you.
C
A
Great
also
I
know,
for
date
and
email
we
have
concerns
of
both
of
those
modules
working
as
well,
so
the
process
of
getting
an
intercourse
should
be
pretty
straightforward.
It
should
be
to
take
the
control
and
drop
it
in
core
modules
folder
and
run
the
tests
and
see
if
it
works,
plus
it
obviously
as
a
human
as
well
make
sure
that
works
and
then
just
kind
of
a
high-level
overview
of
what
are
the
features
of
that
module
provides.
A
Is
there
anything
in
there
that
seems
unusual
or
overly
bloated,
or
something
that
nobody's
going
to
use
that
got?
You
know
stuck
in
back
in
Drupal,
for
something
like
that
and
just
kind
of
do
a
sanity
check
on
what
we're
putting
in
to
make
sure
we're
not
adding
coats
going
to
be
a
nightmare
to
maintain
or
anything
like
that,
but
I
think
for
the
most
part.
A
The
fact
that
these
modules
were
proven
on
Drupal,
7
ported
to
backdrop
and
working
contributes
a
really
good
starting
point
and
there
shouldn't
be
too
much
to
change,
because
you
know
that's
kind
of
the
point:
I'm
not
changing
too
much,
so
hopefully
that
that
those
ports
will
be
pretty
straightforward
and
then
again,
that's
our
short
list
because
they
link
in
email
or
the
most
popular
contribute
modules.
A
So
as
we're
working
on,
you
know
that
that's
what
honor.
What's
on
our
road
map
for
1.2,
but
as
we're
working
through
the
issue,
queue
there's,
obviously
a
whole
bunch
of
issues
that
aren't
specifically
on
our
roadmap
and
things
that
are
related
to
use
your
experience,
developer,
experience
and
bug
fixes
are
going
to
go
in
any
way.
We
want
to
make
this
easier
tool
to
use
and
easy
an
easier
tool
to
code
for
and
a
you
know,
less
buggy
tool
in
general.
There
are
a
lot
of
bugs
in
Drupal
still.
A
That
means
we
have
all
those
same
problems
and
backdrop,
and
it
would
be
great
if
we
could
fix
those
problems
in
both
places.
So,
as
bug
fixes
go
into
gerbil,
we
want
them
to
go
into
backdrop
as
well
pieces
to
go
on
going
back
up
we'd,
also
like
him
to
go
back
to
Drupal.
So
if
anyone
is
working
on
your
cheek,
you
and
they're
finding
stuff
that
you
know
can
be
fixed
pretty
easily
here
throw
up
a
patch
on
drupal.org
if
you
want
as
well.
A
That
tends
to
be
my
general
processes
to
fix
things
in
both
places.
At
the
same
time,
since
you
know,
we've
got
your
mind
and
it
doesn't
take
a
lot
longer
to
do
both
place
for
Drupal
7.
Okay,
but
you
know,
bug
fixes
for
Drupal.
7
are
still
welcome,
are
plenty
of
people
who
can
make
those
work
for
Drupal
8
as
well
or
maybe
they're,
not
even
relevant
for
eight
anymore.
That's
already
fixed,
so
issues
tagged
for
user
experience
in
RQ.
A
The
name
of
the
issue
starts
with
capital:
u
capital
X
in
square
brackets,
same
thing
for
developer
experience
as
I
shall
start
with
capital,
D
capital,
X
and
square
brackets,
and
those
are
just
two
specific
areas
where
we've
decided
to
focus
because
of
our
anticipated
target
market.
For
backdrop
and
things
that
you
know
we
know
for
this
to
be
a
successful
product.
These
are
two
places
where
drupal
has
struggled
in
the
past
and
starting
from
Cherbourg
and
have
to
make
a
significant
improvement
to
get
those
kinks
ironed
out
for
backdrop
in
the
future.
A
So
we're
always
interested
in
finding
about
finding
out
about
those
problems.
So,
if
you're
using
backdrop
file
the
issues,
if
you
run
into
them
and
then
if
you
just
have
a
free
time
on
a
Thursday
or
in
any
day
of
the
week
where
you
want
to
work
on
backdrop,
those
are
good
does
a
good
place
to
start,
because
we
are
definitely
merging
those
fixes
in
so
speaking
of
Thursday's.
We
don't
have
a
little
backdrop:
sprint
every
Thursday,
we're
usually
an
IRC.
You
know
the
entire
backdrop.
A
Community
like
saying
out,
there
chat
most
of
the
time,
but
on
Thursdays,
where
you
tend
to
be
most
active.
That's
when
we're
answering
questions
in
the
issue,
queue
or
filing
new
issues
chatting
and
IRC
chatting
on
reddit,
it's
just
a
good
day
for
all
of
us
to
kind
of
say
you
know
if
I'm
gonna
get
some
free
time,
I
want
to
do
it
on
Thursdays,
because
that's
when
everybody
else
will
be
there
too.
So
it's
a
great
place
for
us
to
kind
of
get
together
and
strategize
about
long-term.
A
What
we're
going
to
be
doing
with
backdrop
and
short-term
things
we're
working
on
right
now
and
how
to
collaborate
on
those.
If
you
can
get
an
hour
week,
a
couple
hours
a
week
from
your
job
to
our
phone
back
job.
That
would
be
fantastic.
If
you
can't
we'll
take
your
spare
time,
your
evenings
and
weekends,
whatever
you
have
to
offer,
and
if
you
can't
even
get
time
on
evenings
weekends,
because
you
have
kids
or
cats
or
whatever
that
you're
devoted
to
will
also
take
your
support.
A
So
I
just
want
to
say
thanks
to
everybody
who
is
you
know,
silently
watching
these
videos
or
lurking
in
IRC.
We've
had
a
couple
of
really
great
conversations
with
people
lately
who
have
been
around
to
all
time
who
we
just
didn't
notice
if
you
have
time
to
contribute,
but
our
interested
in
and
passionate
about
backdrop.
So,
as
you
guys
do,
we
have
a
weekly
meeting
scheduled
the
Sweden,
meaning
is
obviously
thursdays.
At
lunchtime
we
have
another
one
that
is
usually
every
two
weeks
specifically
on
design.
A
So
that's
what
we're
working
on
designs
for
the
backdrop,
CM
esta
org
means
light
as
well
as
design
improvements
to
the
backdrop,
the
project
itself.
We
had
one
scheduled
for
today,
but
we
canceled
it
because
we
didn't
have
designs
ready
to
review.
If
anyone
has
any
issue
specifically
really
design.
We
can
obviously
talk
about
this
today
in
this
meeting
as
well,
or
you
know,
punch
to
the
next
meeting.
If
they're
not
super
urgent
and
those
both
of
those
meetings,
we
have
a
backdrop
meeting
calendar.
A
The
ical
feed
is
available
both
on
the
back
dress
backdrop,
CMS
org,
contribute
page.
If
you
want
to
contribute
by
attending
meetings,
that's
definitely
really
valuable
for
us
in
on
the
reddit.
So
if
you
find
yourself
on
the
reddit,
you
want
to
subscribe
and
figure
out
when
these
meetings,
so
that's
a
good
place
to
find
that
link
to.
We
do
have
another
ical
feed,
which
is
for
our
backdrop,
events
calendar.
C
A
As
of
this
year,
almost
all
of
the
density
of
hearing
on
that
calendar,
our
Drupal
events,
were
there
either
people
talking
about
backdrop,
people
who
want
to
hear
talks
about
backdrop
or
the
event
organizers
have
reached
out
to
us
and
said
hey.
We
want
our
event
to
appear
on
the
backdrop
calendar
as
well:
we've
got
a
ton
of
event,
organizers
who've
been
super
supportive
of
backdrop,
Drupal
event,
organizers,
which
is
really
great,
that
we
can
still
kind
of
collaborate
and
work
on
things
together.
A
We
have
a
ton
of
people
who
are
giving
tux
at
bechtel
events
now
all
over
the
country,
which
is
fantastic
and
our
first
international
event
is
Drupal
north
in
Canada,
which
is
this
weekend.
So
thank
you
for
being
not
the
US
and
I'm
talking
about
backdrop,
which
is
also
fabulous
and
then
yeah.
Our
first
official
backdrop
event
is
going
to
be
a
backdrop
summit
which
is
held
at
bad
camp,
which
this
year
will
be
october
22nd,
so
we're
just
going
to
do
a
one
day.
A
You
know
that
the
day
before
God
can
start
so
it'll
be
thursday.
The
twenty
second
well
work
on
backed
up
together.
We'll
probably
do
some
intro
talks
at
the
beginning
of
the
day,
some
demos
some
how
to
get
involved,
then
maybe
some
sprints
in
the
afternoon.
A
So
if
you
guys
are
thinking
about
coming
to
bed
camp
anyway,
if
you're
a
backdrop
friendly,
that
might
be
a
fun
place
to
come
and
chat
with
all
your
friends
stick
to
so
there's
a
lot
of
events
on
the
calendar,
I'm
not
going
to
go
over
all
of
them
just
this
weekend.
In
addition
to
drupal
mark,
is
also
Twin,
Cities,
drupalcamp
and
then
coming
up
this
month.
A
We
also
have
drupal
corn
at
the
end
of
the
month,
and
then
the
Pennsylvania
drupalcamp
first
week
in
August,
but
there
will
be
more
on
the
calendar
if
you
want
to
find
an
event
here,
you
you're
looking
for
things
to
read
about
backdrop
that
are
in
print.
Okay.
We
do
still
have
a
feature
article
in
the
latest
version
of
Drupal
watchdog.
A
There
are
seven
pages
on
the
significant
differences
between
backdrop
in
Drupal
7,
which
might
be
a
good
read
for
people
who
are
interested
in
the
technical
differences
like
I
know
what
I
do
on
a
day-to-day
basis.
In
seven
and
I
want
to
know
what
that
would
be
like
in
a
backdrop
world,
anyone
who
writes
in
a
blog
posts-
let
us
know
tweet,
mentioned
at
backdrop,
CMS
and
we'll
try
in
post
those
somewhere
of
value,
will
won't
retweet.
A
You
will
put
it
in
this
agenda,
we'll
talk
about
it,
we're
always
looking
for
people
doing
right,
write-ups
on
doctor,
because
that's
good
for
all
of
us
and
that's
it
for
the
weekly
agenda.
Is
there
anything
we
should
talk
about
today?
Any
comments
or
questions
for
anyone
hear
anything
design
related
that
we
didn't
get
to
in
the
council
meeting
earlier
safe.
A
Alright
need,
is
there
anything
you
want
to
add.
I
know
your
video
hasn't
been
working
great
today,
but
no
all
right.
Okay!
Well,
then,
we'll
go
ahead
and
wrap
up
this
meeting
and
we
will
see
everyone
in
IRC
or
at
a
camp
for
conference
or
a
lot
of
else
so
John.
Thank
you
for
joining.
We
like
having
you
here.
Thank
you
for
your
support
and
we'll
we'll
see
you
in
the
future.
So
that's
everybody
online.