►
From YouTube: Backdrop weekly 8/20
Description
Weekly check-in on Backdrop CMS
A
Alright,
we
are
on
air,
it
is
Thursday,
August,
twentieth,
2015,
we're
just
going
to
do
a
quick
check
in
on.
What's
going
on
with
backdrop,
get
some
exciting
news
today,
I
want
to
start
by
saying
that
if
you
want
a
phpstorm
licensed
backdrop,
CMS
contributors
are
welcome
to
have
one.
We
have
a
handful
left,
send
an
email
to
info
@
backdrop,
CMS
org,
and
we
can
send
a
tip
of
your
mum
updates
from
the
PMC.
A
We
got
a
very
exciting
piece
of
mail
so
for
united's
to
have
officially
gotten
our
trademark
approved,
which
is
really
exciting.
That
means
that
nobody
else
can
call
something
backdrop
and
compete
with
us
in
ways
that
may
be
fair
or
unfair.
I,
don't
know
exactly
what
all
the
details
are
about
having
a
trademark,
but
no
Drupal
has
one
and
we
wanted
one.
So
we
got
one
it
took
us
a
while.
A
We
had
a
really
great
phone
call
with
a
lady
at
the
US
Patent
and
Trademark
Office,
who
helped
to
kind
of
explain
to
us
what
it
meant
to
have
one
in
specific
categories,
and
we
were
able
to
choose
the
categories
that
we
thought
were
most
relevant
for
us
and
get
that
ironed
out.
So
we've
got
the
trademark,
which
is
fantastic.
The
follow
up
for
this
is
to
get
instead
of
just
a
trade.
A
My
friend,
the
name,
which
is
what
we
have
nelly,
also
eliminate
very
much
less
important
because
we
weren't,
I
don't
know
the
name,
people
type,
the
name
on
the
internet.
The
logo
is
just
kind
of
a
visual
thing
or
on
the
internet,
so
there
will
be
more
typing
than
picturing.
I
suppose,
but
we
are
going
to
do
a
follow
up
and
get
the
load
logo
trademarked
as
well
and
you're
not
going
to
trademark
the
dragon.
The
dragon
is
for
the
world.
We
want
everybody
to
steal
and
use
the
dragon
as
much
as
they
want.
B
There
are
141,
total
contributes
for
backdrop,
CMS
one
new
one
since
last
week,
I
think
it's
another
theme
which
is
exciting
and
I
didn't
do
update
the
count
this
week,
but
around
61
projects
total
to
have
official
releases,
but
the
number
keeps
going
up
as
well.
So
it's
great
to
see
those
official
releases
being
created
and
pushed
out.
Let's
see,
I
usually
roll
into
the
next
category,
which
is
which
is
infrastructure.
B
Let's
see
on
a
whole,
lot
of
things
have
been
changing
here,
so
update
status
check
king
will
get
to
this
later,
but
the
update
status
has
been
working
in
functioning
for
a
long
time
now.
You
may
have
noticed
that
yesterday,
if
you
have
running
a
backdrop,
one
point
one
point
to
site
that
your
backup
site
notifies
you
that
it
one
point.
One
point
three
was
out
because
that
happened
yesterday,
which
is
exciting
to
get
some
of
those
fixes
up.
B
But
we'll
talk
about
that
later,
let's
see
the
one
things
that
we're
still
stuck
on
as
far
as
update
status.
Checking
ghost
is
that
we're
not
displaying
analytics
numbers
anywhere
yet
once
the
modules
and
themes
pages
get
styled
out
on
backdrop,
CMS
org,
then
we'll
put
usage
statistics
up
on
there,
since
we
are
gathering
that
data
and
see-
and
also
we
want
to
make
it
so
that
we
build
a
server
side.
B
Well,
server
side,
/,
client,
side
project
browser
to
make
it
so
you
can
find
and
install
modules
from
within
your
own
backdrop
website,
and
that
client
side
is
pretty
well
done,
but
the
server
side
is
still
hung
up.
Sorry,
it's
me
again,
a
constellation.
My
mother
thinks
it's
been
thing
that
has
been
going
on
this
week,
so
hopefully
soon
we'll
get
to
the
server
side,
taking
our
taken
care
of
and
started
up,
and
then
we
can
keep
looking
into
merging
that
client
side
project
either
just
as
contributors
or
in
decor
in
the
near
future.
B
A
Local
version
of
document
in
the
issue
and
finally
got
it
all
set
up
and
I
got
it.
Working
and
I
ran
into
exactly
the
same
problems
that
Jeff
ran
into
before,
which
I
thought
was
a
lot
of
progress
and
then
I
started
kind
of
sorting
through
them
and
I.
Think
I
figured
out
what
we
need
to
do
for
next
steps.
A
Basically,
when
Josh
bootstraps
Drupal,
it
has
this
class
that
has
all
of
these
functions
that
are
calls
to
make
stuff
happen
and
when
Josh
bootstraps
backdrop,
it
extends
that
same
class,
and
I
think
that
there's
two
sets
of
functions
there.
One
of
them
are
like
functions
that
it
calls
to
do
things
and
the
other
one.
A
Is
this
like
validate
functions
that
it
calls
before
it
does
the
things
and
I
think
that
we
also
need
to
override
validate
functions
in
addition
to
the
regular
functions
and
some
of
those
aren't
listed
in
there's
like
a
like
a
class
mapping,
part
of
the
class,
and
I
think
that
the
validate
functions
are
called
just
by
naming
convention.
They
aren't
specifically
mapped
in
the
mapping,
and
so
I
think
that
if
we
just
start
over
them,
they'll
be
called
by
naming
convention
and
well
I,
don't
know
so
I
think
there's
just
a
couple
of
missing
pieces.
A
A
But
I'm
just
very
excited
to
have
gotten
to
the
same
problem
last
week
when
and
we
had,
this
call
was
like
well
I,
don't
really
know
why
it's
not
working
and
now
I
know
exactly
why
it's
not
working
so
I.
Think
that's
good
and
it
doesn't
look
like
there's
too
much
work.
There
I
left
to
be
done
so
I'm
hopeful
about
getting
that
going
soon.
A
C
See
if
my
dog
stops
working
yeah,
so
I
made
a
lot
of
progress
over
the
weekend
and
there's
one
kind
of
underlying
thing
that
I'm
working
on
that
just
to
make
sure
that,
as
we
have
more
more
pages
that
are
using
this
one
layout,
that
it's
going
to
work
well
for
us,
so
yep
so
yeah,
the
modules
page
looks,
is
looking
good
and
then
I
have
some
questions
about
the
view
we
can
talk
about
later.
So
yeah
should
be
done.
Hopefully,
after
this
weekend,
yay.
A
You
know
ready
to
roll,
which
I
think
is
super
exciting,
as
people
are
going
to
start
hearing
and
backdrop
and
drupal
8
soon,
as
that
happens
so
very
cool
and
got
a
whole
bunch
of
other
stuff
coming
down
the
pipe
for
the
flagship
website
that
is
low,
lower
priority.
Just
so
those
things
really
quickly.
You
guys
have
heard
this
a
million
times
already.
You
want
to
do
a
showcase
site,
so
people
can
post
sites
they've
built
in
backdrop.
We
want
to
do
a
jobs
board,
so
people
can
post
jobs
and
find
jobs.
A
We
want
to
do
a
list
of
service
providers
if
you're
looking
for
a
hosting
company,
a
developer
or
designer
marketing
experts.
All
of
that
we
want
to
do
an
event
calendar.
So
if
you
want
to
go
to
a
backdrop,
specific
events,
you
can
find
one
and
if
anyone
has
any
other
great
ideas
about
things
that
drupal.org
has
that
we
don't
have
or
things
that
you're
both
at
work
doesn't
have
that
we
also
want
to
include.
We
are
open
to
listening
to
those.
A
We
are
also
going
to
start
trying
to
set
up
a
single
sign-on
with
github,
so
that
people
can
create
accounts
on
the
backdrop
site,
that'll
give
contribute
a
nurse
and
the
ability
to
edit
their
module
node
on
backdrop
CMS
to
org.
The
same
is
true
for
layouts
and
themes,
of
course,
and
we'll
also
try
and
see.
If
there's
other
things,
we
want
people
to
be
able
to
do
like
give
us
Democrat
demographic
information.
Where
do
you
live
what
language
do
you
speak
anything
like
that
that
we
think
could
be
useful?
A
Are
you
a
developer
you
designer?
Are
you
interested
in
hiring
I,
know
being
hired
some
some
other
information
that
might
be
valuable?
We
could
collect
on
on
people
there
as
well.
Okay,
so
lots
of
cool
stuff
going
on.
Let's
talk
about
backdrop,
the
correct
itself
me:
do
you
want
to
talk
about
the
release
that
came
out
yesterday,
yeah.
B
Who's
really
exciting,
really
exciting
and
kind
of
the
wrong
ways.
Actually,
so
yesterday
we
coordinated
with
the
Drupal
security
team
they've
been
preparing
to
get
out
a
bunch
of
fixes
for
a
while
now,
and
so,
although
it
was
a
little
bit
of
a
whirlwind,
we
got
all
of
those
fixes
fixed
in
triple
and
fixed
in
backdrop.
There
were
five
security
fixes,
total
in
backdrop
and
actually
I
think
there
were
six
in
Drupal.
There
was
a
bug
and
overlay
that
we
did
not
include
so
I
don't
have
over.
Let's
but
yeah.
It
was
great.
B
It
was
good
to
see
all
of
the
security
fixes
go
in
they'd
been
queued
up
for
a
long
time.
They
all
ported
really
easily
over
the
drupal,
but
we
maintain
our
parody
and
thanks
again,
it's
always
to
the
triple
security
team
for
upping
coordinate
a
release
with
us.
That
is
always
super
helpful.
It
also
included
some
other
stuff
that
was
nice
included
like
two
dozen
some
small
fixes,
or
so
lots
of
paul's
work
has
been
getting
in
there.
B
B
B
The
rich
text
editor
is
coming
on
great.
It's
already
in
sync.
Editor
has
been
in
there
for
a
couple
weeks.
Now,
all
of
the
testing
that's
been
going
on.
It's
been
really
positive
and
there
yeah
it's
been
really
great
right.
Now.
We're
working
on
improving
upload
of
images
into
ckeditor
it
actually
doesn't
need
to
us
anymore,
is
actually
ready.
So
we
added
tests.
We
back
board
all
this
stuff
from
Drupal
8
and
added
some
of
our
own
tests
in
there.
B
So
we
now
have
that
ready
for
commit
it's
been
tested
by
a
couple
people,
but
if
you
have
a
chance
to
review
issue
1088
that
adds
file
uploading
into
WYSIWYG
and
it's
it's
nice
innit
there's
also
some
other
follow-up
issues
for
WYSIWYG
stuff,
all
of
which
can
be
done
after
release.
I
think
the
file
uploading
was
the
thing
that
we
really
really
wanted
to
get
in
before
hand,
and
that
issue
is
issue
1087.
B
That
includes
a
bunch
of
other
stuff.
I
know
doc.
Ball
mods
been
working
on
things
like
reworking
the
text
format
you
I,
because
now
with
the
addition
of
the
editor
settings
plus
the
filter
settings,
it
can
be
a
little
bit
overwhelming
in
there
and
that
came
along
pretty
well,
but
it's
it's
a
little
bit
stuck
because
we
ran
into
some
problems
around
form,
validation
and
age,
axing
of
dialogues
but
I'm,
hoping
that
we'll
still
be
able
to
get
that
and
other
improvements
in
before
release.
B
B
However,
I
haven't
had
a
whole
lot
of
time
to
give
it
a
full
in
depth,
review
and
I.
Think
if
anything
needs
a
lot
of
review
right
now,
the
date
module,
because
that's
the
one-
that's
probably
the
most
complicated
and
the
one
that
we've
looked
at
the
least
other
than
think
grandma's
been
going
at
it
hard
and
I'm
most
worried
that
that
would
be,
if
anything,
the
thing
that
gets
bumped
out
of
the
release.
So
I'd
love
to
see
that
not
happen.
However,
so
I
would
take
a
look
issue
478.
B
If
anybody
has
time
and
and
help
get
that
reviewed,
let's
see,
link
module
or
link
field
issue,
2
40.
I
did
a
bunch
of
work
on
this
this
week.
Unfortunately,
I
kind
of
got
stuck
in
a
rabbit
hole
because
a
first
of
all
it
all
worked
really
well,
but
then
I
was
trying
to
figure
out
there's
like
a
number
of
like
kind
of
critical
bugs
in
link
module
right
now
in
the
contribu
in
particular,
like
it,
doesn't
support
top-level
new
top-level
domains.
B
So
there's
stuff
like
there's
a
whole
bunch
of
domains
like
you
know,
got
construction
and
dot
jeweler
and
all
of
those.
So
there's
a
couple
hundred
of
those
and
none
of
those
domain
names
work
with
link
module,
which
I
think
will
be
an
increasingly
large
problem,
but
getting
rid
of
that
functionality
turned
out
to
be
a
little
messier
than
I
had
expected.
The
validation
so
I'm
not
quite
sure
what
to
do
that.
I
think.
B
So
maybe
I
should
do
that
and
just
kind
of
real
in
the
perfectionism
a
little
bit.
But
it's
looking
really
good
I
think
if
I
can
push
up
my
a
cleaned-up
version
a
little
bit,
maybe
I'll
roll
back,
all
that
validation
and
then
Jeff,
maybe
could
give
it
another
review
and
then
and
then
we
can
push
that
in
I.
Don't
think!
That's
that's
far
away
from
being
done
at
all.
It's
super
close,
hey.
B
B
However,
we
need
to
deal
with
people
upgrading
from
Drupal
7,
so
one
way
or
the
other
like
keeping
them
right
now
makes
it
so
that's
more
compatible
and
we'll
need
to
write
an
upgrade
path
eventually
to
to
rename
that
into
a
single
format.
I
think
so
I
would
say
for
now:
let's
just
stick
around
with
the
ones
that
we've
got,
because
it's
important
for
upgrading
and
important
for
compatibility,
and
then
we
can
work
on
an
update
paths
in
the
future
sounds
good.
B
That's
it.
Let's
see,
there's
also
some
issues
tagged
for
one
point,
two
point,
oh
some
of
which
are
kind
of
exciting,
but
all
of
which
could
be
a
postponed
to
1.3,
if
necessary,
there's
some
stuff
like
a
global
redirect
functionality,
which
would
be
really
cool
and
some
other
things
that
if
we
get
around
to
it-
and
if
we
have
time,
then
then
we're
all
up
for
expanding
functionality
in
one
point
to
where
ever
possible.
But
the
focus
is
really
on
these
fields
and
on
the
WYSIWYG
functionality.
B
We
are
looking
ahead
also
to
the
next
major
or
sorry.
Next,
minor
release,
1.3
and
1.3
won't
come
out
until
january
fifteenth
and
that's
not
2015,
that's
2016,
yeah,
John,
Henry,
15
2016
and
our
plan
for
1.3.
At
this
point
we
don't
have
anything
marked
on
the
road
map
because
we're
reaching
the
level
of
feature
parity
with
Drupal
8
that
we
have
set
up
to
to
accomplish,
which
is
fantastic,
because
it
looks
like
we'll
probably
get
pretty
much
there
before
drupal
8
is
actually
released,
but
1.3.
B
Our
plan
is
to
mostly
do
clean
up
clean
up
on
the
layouts
punctuality,
not
clean
up,
but
expansion
of
the
features
that
are
already
there
layouts,
although
great
and
the
base
system
is,
is
really
flexible.
The
a
lot
of
expanded
functionality
isn't
there
yet
to
reach
parity
with
panels,
and
so
we
want
to
expand
out
layouts.
We
want
to
expand
out
a
lot
of
the
UI's.
We
want
to
improve
things
like
the
wave
fields
are
added
in
things
like
that.
B
So
there's
a
bunch
of
UX
improvements
that
we
want
to
expand
upon
for
the
1.2
release,
but
we
don't
actually
have
any
real
killer
features
for
that
release.
I
think
that
that
alone
will
get
end
up
with
a
lot
of
stuff.
If
we
start
focusing
on
cleaning
and
polishing,
that's
there's
so
much
work
to
be
done,
but
I
think
that
1.3
will
still
be
a
really
great
release,
even
without
any
new
like
major.
You
know,
headline
modules
really
and
that.
A
Still
growing,
that
was
just
kind
of
like
going
through
the
issue
queue
when
saying
these
are
the
things
I
think
we
should
work
on,
but
I
think
we
should
definitely
spend
more
time
on
user
interface
usability
stuff
and
if
anything
else
comes
up
that
we
need
to
improve.
We
should
just
add
that
to
the
milestone,
so
I
think
it's
a
great
idea
to
kind
of
spend
some
time
polishing
stuff.
I
also
think,
would
be
great
idea
to
spend
a
bunch
of
time
and
can
trim.
B
It'd
also
be
a
great
time
to
kind
of
cool
down
our
core
development
focus
and
start
working
on
our
community
aspects.
I
know,
there's
been
some
mutterings
that
we
really
would
be
better
off
in
a
lot
of
ways.
If
we
actually
gave
a
backdrop,
CMS
some
love
and
turned
it
into
a
community
website
which
we're
still
looking
into
and
considering
I
wiii
and
things
like,
we
need
to
get
people
able
to
log
into
the
website
and
able
to
create
content
directly
on
it
and
then
from
there.
C
B
Let's
see
yeah,
we
always
mention
it,
there's
a
tag
for
UX
and
tagged
for
DX
that,
if
you're
just
looking
for
general
improvements
to
backdrop,
small
issues
that
can
be
tackled-
or
maybe
sometimes
not
so
small,
there's
dozens
and
dozens
of
UX
issues
that
we
would
like
to
improve
the
experience
of
using
backdrop
continuously
and
when
any
one
of
those
issues
is
ready
to
be
committed.
We
will
get
it
in
as
soon
as
possible
for
the
next
remaining
release
every
Thursday.
Today
we
get
together
and
we
do
some
work
on
backdrop.
B
You
can
hang
out
in
pound
backdrop
in
IRC
and
we'll
be
around
in
the
afternoon
/
evening,
pounding
away
on
backdrop
stuff.
We
also
do
code
reviews
and
pull
requests
and
all
of
the
excitement
in
the
github
queue,
and
also
we
have
a
reddit
channel
for
a
general
like
a
water,
cooler
kind
of
conversation
stuff.
If
you
just
want
to
post
things
that
are
relevant
to
backdrop
or
presentations
that
you've
seen
or
or
done
or
any
other
things
related
to
all
thanks
backdrop:
we
have
a
groove
com,
/
r
/,
my
job.
A
So
we
have
see
it
is
the
end
of
august
right
now.
I
I
think
next
week.
Yeah
next
weekend
is
drupalcamp
LA.
So
if
you
are
in
our
near
la
or
want
to
travel
to
la
drupalcamp,
la
is
a
great
event.
We
were
there
last
year.
It
was
fantastic
and
it's
at
UC
Irvine,
which
is
a
really
beautiful
part
of
that
part
of
the
world,
and
it
is
backdrop
friendly
event.
Most
importantly,
so
if
you
want
to
talk
to
other
people
about
backdrop,
that's
a
good
place
to
go
and
do
it.
A
John
is
often
in
our
hangouts
here
he's
not
here
today
that
would
be
home
watch
later
and
so
definitely
recommend
attending
drupalcamp
LA.
And
shortly
after
that,
we
have
the
nerd
summit,
which
is
sep
tember
11
through
13
that
nate
and
I
will
be
keynoting
at
and
that's
an
exciting
event,
because
it's
not
a
drupalcamp.
It
is
a
of
an
open
source,
CMS
event
where
they're
going
to
have
wordpress
stuff
and
they're
going
to
have
other
CMS's
as
well,
and
we
volunteered
to
be
on
a
CMS
panel.
A
So
it'll
probably
be
a
bunch
of
people
talking
about
doing
things
differently
on
different
CMS's
I,
don't
know
exactly
what
it
will
entail,
but
I'm
excited
to
be
a
part
of
that,
so
hopefully
we'll
get
our
first
shot
at
being
on
stage
with
that.
Other
big
players
in
the
CMS
world
there's
a
whole
bunch
of
other
events
too,
coming
up
rather
into
the
future
they're.
All
on
a
I
cal
feed
we
have
available.
Currently
you
can
get
it
from
the
contribute
page
on
by
trip
CMS
to
org.
It's
also
on
our
reddit.
A
We've
got
some
potential
speakers
lined
up,
but
we're
always
looking
for
more
so
if
anyone's
watching
this
video
wants
to
present
on
something
specific.
Let
us
know
we're
definitely
open
to
that,
and
then
the
afternoon
we
thought
we
would
do
a
little
sprint
or
break
out
into
sessions
where
people
can
talk
about
solving
certain
problems.
If
anyone
wants
to
do
working
groups
where
you're,
actually
building
a
site-
and
you
want
to
you
know-
focus
on
something
in
particular
problem
you're
having
her
ways
to
improve
things.
A
In
fact
up
we
definitely
love
to
talk
about
that.
It'll
be
a
little
more
free
form
based
on
who's
in
the
room,
will
try
and
form
working
sessions
based
on
what
people
want
to
hear
about
so
definitely
come
to
bad
camp.
It's
a
free
camp
in
berkeley,
and
if
you
are
traveling
from
out
of
town,
we
also
have
scholarship
at
scholarships
available.
Usually
we
expected
a
shift
or
two
to
be
volunteered
in
exchange
for
the
scholarship,
but
we
do
have
a
budget
for
getting
people
out
there.
Okay,
so
I
guess
that's
it
for
now.
B
B
Isn't
it
I
can
work
a
little
bit
next
week
if
that
would
help
okay
well,
of
course,
we'll
take
it
all
of
the
help
that
you
can
give
us,
because
you've
been
tremendously
helpful
over
the
course
of
the
summer
and
the
event
that
you
don't
have
in
an
event
that
you're
heading
back
to
school
and
don't
make
it
to
more
meetings.
I
do
want
to
officially
thank
you
all
for
your
amazing
summer,
internship
with
backup
and
everybody
give
them
a
silent
applause.