►
From YouTube: Backdrop Weekly 3/24
Description
Today’s development agenda: http://bit.ly/1nS8skF
A
Alright,
we're
on
air
is
Thursday
March
24th
today,
and
we
have
the
usual
backdrop
general
announcements,
that
if
you
want
to
make
a
donation
to
backdrop
CMS,
you
can
do
so
on
our
contribute
page.
We
send
you
a
thank-you
gift
at
the
t-shirt
for
a
$25
donation
or
a
hoodie
for
a
fifty
dollar
donation.
You,
of
course,
are
welcome
to
pass
on
the
thank
you
gifts
if
you
like,
but
there
are
there
because
they're
cute
and
warm
and
fuzzy
people
like
that.
A
We
also
have
free
phpstorm
licenses
for
backdrop
kinship
developers.
So
if
you
have
a
module,
themer
layout,
you
want
to
contribute
or
you
want
to
support,
and
you
want
to
try.
Phpstorm
we've
got
licenses
for
everyone
in
our
community,
so
I
send
an
email
to
info
I
factors
in
the
store.
Can
we
can
help?
Get
you
hooked
up
there,
news
from
the
PMC.
We
have
a
new
pmc
member
this
week.
Jack
welcome.
Thank
you
for
being
a
part
of
our
growing
community
and
I
will
continue
to
add
pmc
members.
I.
A
A
All
right
meet.
You
wanted
sorry.
C
A
Well,
we're
excited:
we've
already
changed
a
couple,
really
good
emails,
where
a
jack
has
been
helping
us
think
about
things
we
haven't
thought
about
yet,
which
is
already
fantastic,
exactly
we're
looking
for
so
so
so
looking
forward
to
working
with
you
and
in
the
near
future,
awesome
alright
mate.
Do
you
want
to
talk
about
community
growth,
yeah.
B
B
Eight
new
project
releases
since
last
meeting,
which
is
great,
more
updates
and
more
maintenance
on
all
of
our
existing
modules,
as
well
as
new
modules
coming
into
the
fold
very
exciting,
we
have
52
total
backdrop.
Contributes
there
aren't
any
real
new
authors
since
last
week,
but
they're
the
number
did
go
up
by
one,
because
we
added
the
new
IRC
bot,
so
our
new
sorry
get
ur
bhat,
so
dragon
bought
joined
the
group
for
the
sake
of
being
able
to
access
all
the
repositories,
but
we
now
have
an
IRC
bot.
B
Oh
dang
I
keep
saying
that
a
get
ur
bhat
hanging
out
in
all
of
our
get
er
channels.
If
you
haven't
joined
us
on
git
er,
it's
a
great
tool
that
we
seem
to
be
more
regularly
moving
towards
full
adoption.
As
far
as
our
chat
solution,
if
you
still
have
IRC,
you
can
also
connect
to
get
er
via
IRC,
just
by
setting
up
a
using
whatever
IRC
connection
or
client.
You
want
and
then
just
joining
the
backdrop
/
backdrop
issues
IRC
channel
through
the
IRC
get
er
diam
server.
So
it's
all
it's
all
options.
B
B
Let's
see
infrastructure,
usage
statistics
and
analytics
I
took
a
look
at
that
this
week
and
looked
like
the
cron
job.
I'd
set
up
for
crunching
analytics,
wasn't
actually
working
quite
right,
but
I
fixed
it,
but
last
week
before
lasts,
numbers
didn't
get
crunched,
but
this
week's
did
I'm
gonna
go
back
and
see
if
I
can
retro
actively
fix
the
missing
week.
But
it
looks
like
the
script
is:
what
actually
was
working
fine
and
just
set
it
up
incorrectly
yeah
I
know
I'll
get
this
thing
running
eventually,
but
but
it's
it's.
It's
really
close.
B
We
haven't
published
the
numbers
publicly
yet
because
we're
still
working
out
all
the
kinks
and
making
sure
travis's
and
end
up
in
the
results
and
that
sort
of
thing,
but
that
would
be
published
in
the
near
future.
Once
it
is
published,
we
want
to
add
a
charting
solution
just
to
back
top
CMS
org.
So
you
can
see
those
numbers
is
charts
rather
than
is
tables
which
is
issue
98.
B
In
the
backdrop,
CMS
org
queue
and
we'd
like
to
make
it
so
that
update
module
starts,
reporting
more
information
to
backdrop
CMS
org,
so
you
can
track
what
features.
People
have
what
features
people
using
inside
of
those
modules,
rather
than
just
what
modules
they
have
turned
on
or
off.
That's
issue
99.
In
the
backdrop
CMS
org
q,
although
that
will
require
some
work
in
update
module
in
core
and
in
project
module
on
backdrop,
CMS
org,
so
that
will
require
some
coordination
across
platforms
to
get
that
going.
B
D
So
the
biggest
changes
that
you
need
to
use
the
8x
scratch
that
Greg
Anderson
cute
us
into
that
there
Master
branches
for
Josh
nine.
Now
so,
if
you're
using
backdrop
extension
make
sure
you're
on
the
heat
I
experienced
and
jen
to
the
pr
cop
they've
read
me
so
thanks
Jen
for
that
that's
merged
and
I
took
a
stab
at
rush
status
and
that's
sort
of
working.
So
that
could
use
some
eyes
not
exactly
sure
why
it
doesn't
report
everything,
but
it
reports
some
stuff
and
a
pantheon.
D
D
B
B
Okay,
yeah
I
want
to
take
a
look
and
swing
background
to
drush
stuff,
hopefully
today
Jeff
because
I
I
know
that
we've
got
dressed
working
and
like
it.
You
know
with
the
right
version
of
dress,
rush,
8
and
the
the
backdrop
extension
then
everything's
I'll
fine,
but
the
fact
that
the
drug
backdrop
extension
still
kind
of
breaks
triple
seven
for
some
reason
and
you
need
to
have
a
separate
drush
install,
is
really
obnoxious,
so
I'm
going
to
take
another
pass
at
that
and
try
to
figure
out
what
we
can
do
to
get.
B
B
Okay,
great!
Let's
see
the
next
item
on
the
agenda:
github
automation,
oh
my
gosh
leaps
and
bounds
of
progress
this
week,
just
crazy
stuff.
Let's
see
Gords
been
doing
all
the
work
on
that.
Almost
all
the
work
on
that
I.
Do
you
want
to
give
us
an
update,
gore
sure.
E
I'm,
just
not
sure
about
connections,
so
first
saying
that
I
want
to
say
that
yesterday
had
a
lot
of
fun
to
making
wife
for
bug
the
ropes
jml
pie
when
the
fight
was
an
eighth
time
at
the
time.
But
we
had
the
water
fun
in.
It
was
really
interesting
watching
her,
but
bugs
was
coming
out
from
everywhere
that
even
not
related
to
whatever
we
was
doing.
Yeah
we've
owned,
probably
some
new.
E
Yeah
mof
again
sorry
is
very
some
interaction.
Interruption
on
the
connection,
okay,
yeah,
so
about
update,
send
boxes,
that's
cool!
Actually,
it
works
when
somebody
create
a
new
pork
wears
it
automatically
creates
in
boxing
in
a
minute
you
have
a
credential
to
log
in
it.
There
is
a
measured
problem
with
boo
request
when
you
update
pull
request,
as
there
is
an
issue
I'm
going
to
work
on
it,
it's
so
not
only
get
pushing
or
pulling
issue,
but
also
I
want
to
make
it
possible
to
work
with
CM
updates.
E
So
if
poor
request
get
updated-
and
there
is
news
here
means
so
I
would
avoid
rush.
Update
need
to
be
called
process
it
and
set
result
is
some
things
to
need
to
figure
it
out
how
to
do
properly
it
for
backdrop.
I
can
do
it
for
drupal,
but
we
need
to
make
it
work
for
backdrop,
know
what
tells
us
association
yeah
it
works.
So
if
you
now,
you
can
type
just
this.
What
design
is
dash?
What
is
it
I?
Don't
know
how
to
call
it
properly
and
numb.
E
Where
all
the
dropsy
I
will
immediately
comment,
oh
gosh,
we
all
right.
We
will
immediately
comment
a
pull
request
with
the
proper
link
to
backdrop,
backdrop
issues
a
hash
number
of
the
issue,
so
you
don't
need
to
type
all
that
stuff
and
pretty
much
these
two
issues
get
covered
and
it's
working
right
now.
Everything
else
is
coming
up
question
and
to.
B
It
would
always
it
would
identify
the
wrong
things,
and
so
what
we've
done
is
yeah.
We've
we've
used
the
API
to
compensate
for
that
and
when
you
file
a
poor
request
that
says,
you
know
issue
number
ten.
It's
references
issue
number
10
/
in
the
issue
repository
not
in
the
core
code
repository,
so
it
makes
it
so
they're
related
against
each
other
without
having
to
do
anything
now,
which
is
great.
That's
actually
one
of
our
oldest
issues.
That's
issue
number
four.
B
In
the
backdrop,
CMS
org
too
awesome
to
get
that
one
taken
care
of,
and
then
right
after
that
is
issue
number
five,
which
is
the
automatic
sandbox
functionality,
which
is
also
now
up
and
running.
Yeah
gore,
you
might
have
been
mentioning
the
the
parts
that
aren't
working
part
is
working
is
the
fact
that,
when
you
file
a
new
poll
request,
it
automatically
gets
a
sandbox
set
up
now,
just
like
Travis
CI
automatically
test
these
things.
B
We
now
automatically
get
live
sand
boxes
for
users
to
actually
go
and
test
the
functionality,
which
is
awesome,
we're
still
working
out
the
kinks
in
when
a
pull
request
gets
updated,
fixing
fixing
the
sandbox
to
accommodate
for
the
updates,
but
for
right
now
we
can
just
close
the
poll
request
and
open
it
again
and
that
will
tear
down
the
sandbox,
then
open
it
back
up
again
and,
and
it
all
works,
actually
really
pretty
well.
Yeah
I'm
really
excited
about
that
functionality.
B
B
It's
awesome
and
it
and
I
know
eventually
that
will
probably
be
a
more
reusable
service
outside
of
just
backdrop.
So
that's
all
so
exciting
to
see
that
offering
like
coming
coming
on
to
the
market
so
anyway,
but
really
excited
that
that
it's
here
for
backdrop,
okay,
Jenna
I'll,
turn
it
over
to
you
to
talk
about
backdrop,
CMS
org,
alright,.
A
So
we
haven't
made
a
whole
bunch
of
progress
since
last
week
there
were
a
couple
of
bugs
that
were
fixed
by
the
larger
community.
So
thank
you.
Everybody
who
found
found
the
problems
fix
the
problems
and
then
in
the
full
request,
so
nice
to
have
other
people
just
kind
of
jumping
right
in
and
cleaning
up
my
mess
stuff
thanks,
also
working
on
right
now.
A
We've
got
a
list
of
all
of
the
bits
of
content
that
we
want
to
include
in
our
showcase,
so
that
people
can
see
sites
built
with
backdrop
and
post
sites
that
they've
built
with
backdrop
which
I
think
will
be
really
great
and
we're
waiting,
I
think
on
a
design
for
that
section.
A
So
what
I
wanted
to
work
on
this
week
was
getting
service
provider
and
contractors
started
in
terms
of
architecture,
so
I'm
going
to
start
drawing
up
content
buckets
for
that,
based
on
Drupal
and
WordPress,
and
anything
else
where
I
can
find
a
good
listing
of
service
providers.
A
We
could
start
setting
that
up
and
then
people
will
populate
that
before
backdrop,
one
point
pours
out
and
we
get
some
kind
of
a
references
solution
in
there
and
as
soon
as
references
is
there,
we
can
start
letting
people
reference
service
providers
from
things
like
their
personal
profile,
like
oh
I
work
for
this
company
or
from
the
showcase
like
this
is
the
company
that
made
the
website.
We
could
start
to
get
a
lot
of
really
good,
dynamic,
relational
content
going
on
our
site.
A
So
that's
the
plan
we'll
see
how
much
of
it
we
can
get
done
before.
Then.
We
also
have
a
task
to
set
up
single
sign-on
with
github,
so
people
who
already
github
users
don't
have
to
create
a
new
account
on
backdrop,
CMS
work,
but
we
need
somebody
to
volunteer
for
writing
a
single
sign-on
solution.
So
if
you're
particularly
passionate
about
single
sign-on,
that's
definitely
up
for
grabs.
A
Another
thing,
too,
would
be
to
add
a
jobs
board,
so
once
people
start
trying
to
hire
developers
first
specific
job,
rather
than
as
a
contractor,
we
can
start
to
build
that
out,
but
I
think
it
would
be
good
just
to
get
a
list
of
people
who
are
contractors
that
are
available
first
and
so
today,
I
went
ahead
and
added
a
checkbox
on
the
user
profile
for
is
available
for
hire,
which
I
think
is
something
I
found
on
github
and
thought
was
super
useful
and
since
it
was
easy
to
set
up,
I
just
threw
it
on
there.
A
We
can
start
to
aggregate
people
who
have
listed
themselves
as
available
for
hire
on
our
contractors
and
services
service
providers
listing
page
as
well.
So,
if
you're
looking
for
a
company,
you
can
find
it
individuals
too.
So
you've
got
a
lot
of
progress
under
way.
We
have
a
bunch
of
stuff
that
we
have
already
started
on,
but
not
finished.
That
also
needs
some
attention.
A
Our
find
modules
page
or
find
themes
and
find
layouts
pages
have
some
serious,
follow
up
issues
and
there
are
some
development
tasks
that
all
spinoff
from
all
of
this
great
work,
we're
doing
with
all
the
github
integration
and
so
we'll
be
able
to
pull
in
information
from
github,
which
I
think
will
be
fantastic
and
then
there's
a
bunch
of
just
implementation.
Once
we
have
all
the
data
we
need
just
to
get
them
in
the
views
and
to
build
them
onto
the
nodes.
So
we've
got
some
follow-ups
there.
E
A
A
Don't
know
if
we
want
to
try
and
copy
the
files
over
just
linked
directly
to
the
github
version,
but
I
think
that's
one
piece
of
the
puzzle
we
just
haven't
figured
out
yet
but
other
than
that
I
think
that's
ready
to
start
implementing.
Someone
wants
kind
of
a
good
standalone
task
and
we
also
have
a
couple
of
follow-up
issues
for
some
of
the
new
features.
We've
added,
like
our
blog
news
section
and
our
event
listings.
A
So
speaking
of
news
and
announcements,
I
did
manage
to
write
up
a
super
quick
blog
post
last
week
on
just
a
bunch
of
sites
that
people
have
already
published
on
backdrop.
So
anyone
else
who
has
more
sites
they
want
up
there.
I
can
send
an
email
to
info
effective,
CMS,
dark,
I'm
going
to
collect
them
and
then
maybe
every
time
we
don't
have
a
blog
post
ready.
A
We
can
do
fa,
here's
what's
new
and
just
kind
of
publishing
on
more
sites,
and
hopefully
won't
have
to
do
that
too
many
times
before
we
actually
have
the
showcase
section
ready
to
go,
but
I
throw
a
couple
of
sites
on
there.
Wes
I'm,
not
sure
you
wanted
that
there,
but
I
put
it
up
anything
I,
wanna
beer
side,
so
I.
Let
me
know
if
you
want
me
to
take
it
down
and
then
yeah
everything
yeah
and
of
the
our
sites
site.
So
both
of
those
were
up
there.
A
It's
in
beta,
so
okay
I
wasn't
sure
how
much
of
that
was
ready
for
the
world,
but
good
you
want
to
take
it
down.
We
can
take
it
down
so
yeah.
Those
are
up
and
then
I
think
that
I'll
bias
two
weeks
for
Nate
to
write
his
performance,
benchmarking,
blog
post,
if
make,
if
you're
not
going
to
be
ready.
Next
Friday
we've
got
a
couple
of
other
people
who
have
interesting
blogs
in
the
queue
we've
got.
Mike
McCaffrey
was
going
to
write
one
on
config
management.
A
Jack
wanted
to
write
one
on
why
to
support
Bactra
Doug
van
in
mic.
Pre
parag
are
both
interested
in
writing.
One
on
Kalibak,
so
I
thought,
maybe
when
we
get
them
to
team
up
on
that
one,
and
if
anyone
has
any
of
that
or
think
they
can
have
any
of
those
posts
ready
by
next
Friday.
That
would
buy
need
two
more
weeks
to
work
on
his
bench
marking,
which
you
would
probably
appreciate
it.
A
But
we
are
kind
of
losing
the
the
excitement
of
PHP
7
being
available,
getting
to
kind
of
write,
a
blog
post
about
something
that's
new,
because
it's
not
really
new
anymore.
But
people
do
still
want
benchmarks
on
backdrop
than
if
we
could
do
a
backdrop
on
PHP,
seven
well,
I
think
that
would
be
a
real
one.
So
whenever
we
can.
A
Eight,
in
addition
to
blog
posts,
I
somehow
managed
to
write
a
newsletter
last
week.
So
I
started
writing
in
I'm
like
there's
so
much
stuff.
We
need
to
tell
people
about
in
the
newsletter,
got
really
really
long
and
then
I
realized
that
we
never
have
content
for
newsletters
and
so
I
split
it
into
two
and
the
one
that
I
ended
up.
Sending
last
Friday
was
just
kind
of
a
recap
of
our
blog
post
from
the
1.3
release.
It
was
like
this
is
what's
new,
what
you
need
to
know
about
and
then
I
figured.
A
We
have
another
one
scheduled
for
able
to
plenty
of
in
about
a
month
and
I
think
you're
on
that
one.
What
we
could
do
is
do
a
what's
new
on
backdrop,
CMS
org
and
have
the
call
to
action
there
be
to
create
an
account
and
log
in
and
do
some
of
the
things
like
use
the
showcase.
If
it's
up
or
add
your
company
is
the
service
provider
whatever
it
is
that
we're
ready
to
have
people
do
in
a
month
we
can
kind
of
have
a
separate
call
to
action
rather
than
being
one
newsletter.
A
That
was
like.
Try
the
new
software
created
an
account
download
the
whatever
by
the
book
like
it,
was
just
too
much
stuff
at
once
so
figured
we
have
a
problem
with
content:
what's
not
don't
never
home
the
content
we
have
at
once
so
I
hope
that
I
hope
you
guys
got
it
if
you're
on
the
list
and
no
I
was
a
little
worried
that
I
didn't
get
it
then
I
realized
that
I
did
get
it
or
I
wasn't
on
the
list.
A
As
me,
I
was
almost
as
my
test
email,
so
I
could
do
a
find
it
but
dig
about
last
Friday.
So
I
was
exciting
yeah.
So
if
anyone
else
is
super
interested
in
writing,
blog
posts
or
sending
newsletters,
this
is
definitely
an
area
where
we
are
not
super
strong
and
we
would
love
all
the
systems
we
can
get
in
either
area
I'm
happy
to
turn
over
the
mailchimp
details.
If
you
want
to
log
in
there
and
start
creating
messages
and
we
can
promote
anyone's
blog
posts
to
if
that's
interesting.
A
So
let's
know-
and
we
can
put
you
on
schedule-
we've
got
schedules
for
both
of
those.
The
blog
post
issue
is
158
in
the
backdrop
seen
esta
hora
q.
A
newsletter
is
177
all
right.
So
next
on
the
list
is
backdrop
CMS
project
update
and
Nate
I've
got
you
down
for
talking
about
releases.
So
there's
this
week.
A
B
That
has
now
been
rectified.
Yeah,
sorry,
sorry,
new
versions,
all
the
time
I
know
it's
just
the
worst
so
backdrop,
135
will
be
the
next
bug
fixing
release.
We've
created
a
new
tag
for
that
on
github
or
any
release
for
that
on
github.
If
you'd
like
to
see
things
that
in
the
next
bug-fix
release,
filed,
pull
request,
market
needs,
review
and
I'll
take
a
look
at
it.
If
it's
trivial,
you
can
go
ahead
and
tag
it
for
the
next
release.
B
Sometimes
that
helps
me
go
through
all
of
the
critical
items
for
the
next
release
and
make
sure
that
that
the
all
the
issues
for
the
next
release
are
all
taken
care
of
before
and
make
the
new
tag
unless,
unless
is
not
done
and
then
I
just
unmarked
it
from
their
release.
Sometimes
a
release
needs
to
go
out
and
not
everything's
ready,
which
yeah
that
happens.
B
B
B
There,
our
ports
of
things
like
no
reference
and
user
reference
from
Drupal
7,
in
the
backdrop
contributory,
but
what
we
would
like
to
see
in
core
is
the
capabilities
of
entity
reference
where
you
can
reference
anything
and
it's
all
one
module,
instead
of
being
a
bunch
of
little
separate
ones,
but
the
references
module
entity,
reference
module
from
Drupal
7
is
also
like
a
big
mess
compared
to
compared
to
backdrops
implementation
of
things.
It's
it's
not
written
in
line
with
the
rest
of
core
and
so
we're
wanting
the
functionality
of
entity
reference
written
in
a
way.
B
That
is
more
compatible
with
the
implementations
in
backdrop
core,
so
that
basically
means
a
large
rewrite
of
that
module
plus
way
to
worry
about
upgrade
pads.
So
so
there's
a
lot
of
things
that
need
to
be
done,
but
that
issue
hasn't
seen
any
progress
since
january
twenty
seconds.
So
if
anyone
is
interested
in
helping
mike
was
taking
the
lead
on
that,
but
I'm
sure
that
he
would
appreciate
some
assistance
on
moving
references
module
forward.
B
D
B
Well,
I
can
take
a
look
at
that
and
make
some
suggestions
there,
because
I
think
the
easiest
way
to
go
about
it
is.
We
already
have
this
controller
class,
that
is
the
entity
controller
class
right
now
and
if
we
just
add
new
methods
to
it
for
loading
and
saving,
then
that
will
replace
what
entity
the
entity
system
previously
provided
in
that
area.
But
I
can
see
how
that's
like
all.
That
code
is
like
so
deeply
buried
in
the
entity
system.
B
B
Yeah
I
think
actually
that's
the
thing
is
that
you
don't
even
want
to
read
them
because,
because
it's
so
complex
in
its
nature,
especially
because
we
still
have
some
underlying
things
that
we
inherited
from
Drupal
7,
like
the
storage
mechanism,
is
swappable
and
all
of
that
business
is
not
even
possible
in
backdrop
like,
we
still
have
the
swappable
layer
in
there,
but
we've
locked
we've
removed
the
ability
to
actually
swap
it
out
with
something
else,
and
so
there's
a
lot
of
this
abstraction.
B
B
F
As
far
as
any
work,
I've
done,
nothing's
changed.
Unfortunately,
last
week
was
mid.
Camp
and
I
was
swamped
before
that
and
I'm
recovering
a
little
bit
still
trying
to
take
care
of
some
stuff
on
behind
on,
but
yeah
I
should
this
weekend.
I
think
I'm
gonna
have
a
fair
amount
of
time
to
devote
to
it,
and
I
have
been
using
it.
The
theme
that
I
think
we
might
use
I'm
using
it
on
a
site
that
will
be
coming
out
before
too
long
and
so
I'm
trying
to
make
it.
F
So
it
can
be
an
admin
theme
and
a
front
end
theme
and
that's
a
requirement
for
that
site
as
well.
So
that's
going
pretty
well
and
yeah.
I
just
need
to
to
flush
it
out
some
more
and
then
put
in
some
graceful
degradation
and
then
think
about
the
layout
system
and
how
that
should
work,
which
doesn't
necessarily
directly
affect
the
theme,
but
maybe
yeah
so
we'll
see.
Okay,.
B
The
last
major
item
on
here
is
that
we
would
like
to
add
additional
layouts
into
core,
so
some
more
layouts,
besides
our
two
column
and
our
two
column,
flipped
in
our
single
column
and
then
the
bartok
like
layout,
so
the
four
let's
we
have
in
core
currently
and
that
discussion
is
currently
ongoing
in
issue
698
and
there's
too
much
for
me
to
summarize
so
take
a
look
at
that
yeah
or
we're
still
going
back
and
forth
a
whole
lot
in
that
issue.
Deciding
what
approach
we
should
take.
B
Let's
see
and
there's
an
issue
for
fixing
the
rich
text.
Editor
I
really
should
be
improving
the
rich
text
editor
more
than
fixing,
but
there
are
a
bunch
of
issues
that
are
actually
bugs
that
are
in
our
rich
text
editor
and
we
can
fix
those
at
any
time,
they're
not
being
held
up
until
May,
fifteenth
and
there's
a
meta
issue
with
a
bunch
of
issues
that
all
relate
to
the
rich
text
editor
in
1087,
and
so
some
of
those
are
bug
fixes
we'd
like
to
fix
in
this
as
possible.
B
D
B
Let's
see
yeah
there's
one
of
to
do
bug
bad.
This
isn't
meta!
Isn't
it
oh
I
see
here
it
is
yeah,
it
got
retitled,
okay,
yeah,
it's
issue,
1373,
so
I
think
yeah,
there's
an
easy
solution
of
that.
I
think
that,
in
in
the
case
of
blocks
themselves,
that
we
should
just
implement
hook,
block
save
or
hook
block,
insert
and
hook
block
update
and
just
mark
the
files.
B
B
So
yes,
this
was
in
the
filter
system
that
you
had
it
in
here
and
instead
of
because
this
this
would
apply
to
all
images
in
all
entities
everywhere
and
instead
yeah.
My
suggestion
is:
do
it
in
hook,
block
save
and
hook
block
our
hook
block
insert
a
block
update,
which
will
only
happen
when
the
block
is
actually
saved
rather
than
every
entity
everywhere
being
having
that
happen.
B
B
B
There
are
also
some
other
items
that
are
moving
forward
for
the
next
release,
even
though
they
weren't
they
weren't
in
our
long-term
road
map.
We're
still
really
hoping
to
get
these
improvements
in
for
1.4,
and
that
includes
project
browser
which
is
coming
along
really
nicely.
We
have
the
server
fully
capable
now
up
and
running
on
backdrop
CMS
org
and
we
have
the
contribute,
is
fully
functional
and
working
that
you
can
install
and
we're
currently
working
on
merging
that
into
core
as
a
pull
request.
B
So
so
anyway,
so
he's
he's
moving
that
functionality
right
now,
even
in
Drupal
7.
If
you
had
update
module
turned
on,
you
also
could
install
modules
through
it,
which
is
really
not
great,
especially
because
the
only
interface
that
we
had
for
it
was
copy
and
paste
a
zip
file.
You
know
URL
and
then
just
hit
in
stall,
and
it's
like
just
encouraging
people
to
just
like
install
modules
from
who
knows
where
you
know
it's
like
copy
and
paste
this
into
your
command
terminal.
Don't
forget
to
type
your
sudo
password.
You
know.
B
So
anyway,
so
he's
moving
that
code
out
of
update
module
and
into
installer
module.
I
actually
haven't
had
a
look
at
this
in
the
past
couple
of
days
but
day
before
yesterday,
posted
a
big
update
and
looks
like
there's
another
poll
request
for
me
to
look
at
as
well
as
everybody
else.
If
you'd
love
to
test
that
out,
you
know
what
I'm
gonna
do
is
I'm
gonna,
close
and
open
this
pull
request
and
then
we're
gonna
get
a
live.
Sandbox.
B
B
Okay,
let's
see
oh
and
the
other
item
that
we
have
on
here
for
1.4
west
did
some
work
on
new
field.
Ui
improvements,
this
issue
779,
and
there
are
some
things
that
are
actually
implementable
in
there
I
think
it's
a
matter
of
making
decisions
about
which
approach
we
want
to
take
and
then
trying
them
out.
I
think
so.
I'd
love
to
see
some
progress
there,
we're
not
talking
about
a
rewrite
of
field.
B
You
at
this
point
we're
mostly
talking
about
improving
the
way
that
you
add
and
configure
fields
doing
some
work,
like
we've
been
doing
in
layouts
that
we
can
use
more
Ajax
and
use
more
dialogues
and
that
will
reduce
the
overall
number
of
screens
and
page
loads
and
changes
that
you
need
to
do
to
go
through
in
order
to
manage
your
fields.
So
there's
some
interesting
work
going
on
over
there,
not
a
lot
of
code,
but
a
lot
design
and
we'd
love
to
see
some
of
that
implemented
in
general.
B
A
I,
muted,
you're,
good,
okay,
good
I
always
get
to
check
so
every
Thursday.
After
this
meeting,
we
usually
hang
out
in
the
github
issue,
queue
we
chat
on
gear
and
we're
in
IRC,
where
we
can
kind
of
work
together
on
solving
some
of
these
problems.
So
anyone
who
got
stuck
on
anything
and
Thursdays
a
good
idea
good
day
to
set
aside
to
get
unstuck.
It's
usually
a
lot
of
people
around
we're,
also
working
on
backdrop.
A
If
you
need
to
work
on
backdrop
and
it's
not
a
Thursday,
that's
also
fine,
there's,
usually
people
in
those
locations
as
well,
just
probably
less
of
them,
but
most
of
us
are
reachable
most
of
the
time.
You
can
leave
someone
messages
in
theatres
and
if
they
are
open
to
it,
it
will
send
them
an
email,
so
don't
feel
like
you
have
to
participate
on
Thursdays.
That's
just
the
kind
of
the
time
that
we've
set
aside
to
be
specifically
for
backdrop.
We
also
have
a
reddit
at
reddit
com,
/
r,
/
backdrop.
A
So,
if
you're
not
into
hanging
out
on
github
in
issue
queues
or
in
online
chat,
because
some
people
aren't,
we
also
have
a
forum
that
we're
using
for
now
anyway,
for
people
to
chat
about
backdrop
in
a
less
formal
setting.
But
we
are
still
interested
in
other
places
where
a
community
can
meet
online
and
collaborate,
so
we're
still
trying
to
figure
that
out.
A
We
also
have
a
couple
of
upcoming
events
where
you
can
meet
in
chat
with
people
who
are
talking
about
Mack
truck
in
person,
and
there
is
now
on
a
page
on
vector,
seamless,
org
at
/
events
that
lists
the
upcoming
events,
that
we
know
about
your
hosting
event,
and
you
want
backdrop
to
be
a
part
of
it.
You
can
go
ahead
and
put
that
up
yourself
onto
our
website
and
just
let
some
information
about
the
event
like
a
link
for
people
can
get
more
info
and
the
dates
and
that's
available
for
anyone
to
do.
A
Usually
it
doesn't
have
to
be
a
backup
specific
event.
There
are
not
a
lot
of
those
there's
been
maybe
one
date,
but
there
are
a
lot
of
technology
conferences
in
Drupal
conferences
where
people
will
be
sharing
and
talking
about
backdrop
as
well,
so
that's
kind
of
what
we're
putting
up
now
anything
that's
relevant
where
you
either
want
to
hear
about
back
to
forgiving
and
talks
a
good
item
to
post
in
that
calendar.
There's
an
RSS
feed
for
it
from
our
google
calendar.
A
There's
also
a
couple
of
books
for
the
very
interested
in
upgrading
from
Drupal
to
backdrop.
There
is
a
book
called
migrating
from
Drupal
to
backdrop
on
a
press
that's
available
now,
and
there
is
a
larger,
more
comprehensive
book
called
beginning
backdrop,
which
should
be
coming
out
pretty
soon
in
that
in
the
next
few
months
here.
So
that
is
pretty
exciting.
A
A
Dragon
videos
always
welcome.
Ok.
Well,
if
nobody
has
anything
particularly
urgent,
then
we
should
wrap
up
the
call
and,
if
you
think
of
something
later
plus
an
issue
in
the
issue,
queue
or
tweet
write
a
blog
post
for
what
you
want.
Look
you're,
gonna
happen
and
try
and
address
it
and
we'll
meet
again
this
time
next
week
to
talk
about
our
development
tests
and
an
hour
earlier
at
noon.
We
have
a
design
meeting
next
week,
so
yeah
Pearson
design
stuff.
That
could
be
fun
too
all
right.