►
Description
Today’s development agenda: http://bit.ly/1WMh2gR
A
Alright,
we
are
on
air,
a
happy
Thursday,
March,
31st
everybody,
it's
the
last
day
of
March,
pretty
exciting.
It's
we're
coming
up
on
backdrop
1.4
month,
all
right
couple
of
quick
announcements
as
usual.
If
you
would
like
to
make
a
donation
to
backdrop
CMS,
we
have
really
adorable
t-shirts
and
hoodies.
We
will
send
us.
Thank
you,
gifts,
t-shirts
for
twenty-five
dollars.
In
phase
4
50,
you
can
make
donations
for
either
of
those
amounts
or
any
other
amount.
You
would
like
to
on
the
contribute
page
at
factor
of
CMS
network.
A
If
you
are
already
a
backdrop
contributor
and
contribute
code,
we
can
give
you
a
free
phpstorm
license.
Phpstorm
is
giving
us
a
bunch
to
hand
out.
So
if
you
want
to
give
phpstorm
a
try,
you
can
send
an
email
to
info
@
factor
of
CMS
org
and
we
can
send
you
a
license
key
or
at
least
a
way
to
get
your
license.
Key,
alright
updates
from
the
PNC
we
currently
PMZ
members
have
someone
in
the
issue
queue.
A
We
need
to
vote
on
this
week,
so
if
you
guys
could
go
and
make
votes,
I
notice,
westie
voted
this
morning.
Thank
you
very
much.
I'll
send
an
email
to
everyone
later
today
to
to
make
sure
that
the
github
noise
is
not
too
much
that
we've
missed
a
need
to
vote,
but
there
is
a
potential
new
PMC
member.
Hopefully
next
week
is
exciting
and
then
hopefully,
after
this
edition,
we
can
kind
of
change
gears
a
little
bit
and
start
to
look
at
adding
core
committers.
B
Okay,
and
let's
see
oh-
and
this
is
really
exciting-
a
herb
duel
did
some
work
and
actually
Jeff
as
well
did
some
work
on
civvy
crm.
This
week
we
ported
to
more
of
the
sub
modules
in
civvy
crm.
I
should
say:
herb
did
and
we
merged
in
that
into
the
Soviet
integration,
and
we
also
removed
the
rules,
integration
which
wasn't
working
at
all.
So
until
until
that
actually
gets
ported,
it
was
better
to
have
it
removed
rather
than
broken.
B
At
least
those
are
the
only
reports
we
got,
or
you
know
here,
let's
port,
some
more
modules
which
which
seems
to
imply
that
things
are
going
pretty
well
over
there.
So
that's
great.
Let's
see
we
have
a
hundred
and
fifty
eight
total
projects
on
backdrop.
Cms
org
that
have
been
listed
with
official
releases.
One
new
project
has
been
published
to
back
top
CMS
org
since
last
week
and
217
total
releases
of
all
of
those
projects,
including
two
new
releases.
B
Since
last
meeting
we're
still
at
52
total
can't
rib
authors
if
you're
interested
in
porting
a
module
to
backdrop
well
go
ahead
and
get
porting.
But
if
you'd
like
to
publish
that
that
project
on
to
github
in
the
official
backdrop
can
trip
group,
then
you
can
do
so
by
applying
to
join
the
group
at
github
com,
/
backdrop,
cash
ups,
/
can't
rib
and
that's
where
we
handle
the
issue
queue
for
reviewing
new
modules
that
are
going
to
be
added
to
the
repository
and
then
granting
access
to
new
authors.
B
So,
if
you're
interested
in
joining,
please
do
so
at
that
github
issue
queue
and
we
would
love
to
have
your
projects
listed.
In
the
official
backdrop
contributory
there
are
133
total
users
who
have
created
accounts
on
backdrop,
CMS
org
15,
new
users,
who
have
created
account
since
last
meeting,
which
is
great,
but
we
still
don't
have
a
whole
lot
of
things.
You
can
do
on
backdrop,
CMS
org,
but
we're
slowly
rolling
out
more
functionality
there.
What.
A
B
B
Okay,
that's
all!
We've
got
for
community
growth
over
all
right
into
infrastructure
tasks,
items
around
backdrop
that
aren't
the
software
itself,
mostly
github
tools
and
work
on
backdrop,
CMS
org
usage
statistics:
oh
man,
usage,
statistics,
kind
of
working,
yeah,
but
kind
of
not
working.
So
it's
been,
we've
got
a
lot
of
usage
statistics
calculated
all
the
way
from
gosh
I,
don't
know
sometime
this
past
summer,
all
the
way
up
until
two
weeks
ago,
but
our
number
crunching
script
still
seems
to
have
some
kinks
in
it.
B
So
it's
been
crunching
numbers,
but
apparently
we
have
to
run
it
manually
in
order
to
get
it
to
go,
which
is
a
little
bit
silly.
Obviously,
it's
not
it's
not
far
from
working
entirely,
but
it's
just
not
quite
right
yet
so
we're
still
working
out
the
kinks
in
that,
but
we're
getting
close
once
the
usage
statistics
are
calculating
correctly.
B
We
have
a
couple
of
follow-up
issues
in
the
backdrop,
CMS
or
guess:
uq,
basically
expanding
the
functionality
of
usage
statistics
making
it
so
that
we
can
pull
in
not
just
what
modules
people
have
installed,
but
what
features
they're
using
within
those
modules
potentially
so
that
we
can
start
generating
some
useful
information
about
what
features
people
use
in
backdrop
and
what
features
they
don't.
And
we
also
like
to
add
charts
to
these
statistics
pages.
There's
an
issue
issue
98
in
the
backdrop
CMS
torgus,
uq
and
I,
don't
think
that
needs
to
be
complicated.
B
C
Sure
so,
as
always
just
remind
you
to
go
to
the
dresser,
eq
and
state,
what
you
want
you
can
get
to
those
priorities.
Reminder
use
a
point
x
branch,
as
the
master
branch
is
now
drush,
9
and
nate.
The
did
a
nice
fix
that
gave
us
at
least
a
2,
for
maybe
three
issues
solved
with
name
spacing
issue
fixed
number
14.
C
So
if
you're
writing
for
josh
all
new
convention
here
backdrop
underscore
command
underscore
whatever
the
handbook
that
you're
trying
to
write
is
so
thanks,
Nate
for
that
and
then
Jack
review
tested
by
the
community.
Even
though
I'm
bad
at
letters
see
if
I
get
a
right
RT
bc,
so
we
got
brush
status
merged.
So
now
you
can
check
status
on
websites
with
brush.
Oh
and
nate's
allows
it
to
work
with
drupal
7
without
breaking
it,
which
is
pretty
important
thanks
for
that
and.
C
B
Awesome
awesome,
yay,
yeah
that
it's
that's
really
exciting.
Now
the
dress
is
finally
working
and
it
doesn't
break
Drupal
7
at
the
same
time
like
yay.
So
last
week,
drush
broke
Drupal
7.
When
we
had
the
backdrop
extension
this
week
it
works
yay.
So
we
now
have
one.
You
can
use
rush,
eight
and
the
backdrop
extension
and
you
can
use
brush
now
consistently
across
triple
seven
triple
eight
and
backdrop
with
one
version
very
exciting
and
I.
Think
that
really
yeah
we
had
just
some
terrible
name
spacing
problem
it
was.
B
It
was
kind
of
ridiculous
that
our
commands,
the
function
name
somehow
is
accidentally
a
hook,
and
so
when
you
were
in
Drupal
7
and
he
tried
to
run
a
dress
command,
it
would
accidentally
fire
a
backdrop
hook
or
a
backdrop
function.
It
was
like
a
classic
Drupal
namespacing
blunder
like
accidental
hooking
vocation,
but
now
that
that's
been
solved
and
so
we're
in
a
much
better
state.
B
Let's
see
github
automation,
we
have
a
whole
tag
under
the
backdrop
CMS
or
guess
you
queue
for
all
things
related
to
github,
automation,
I,
don't
think,
there's
been
anything
new
this
week,
but
it's
worth
mentioning
if
you
didn't
watch
last
week's
phone
call
that
we
have
a
really
exciting
feature
that
is
out
in
the
wild.
Now
that
is
the
live
sandboxes.
B
So
every
single
poll
request
that
you
make
automatically
will
get
a
sandbox
spun
up
so
that
you
can
test
that
pull
request
on
a
la
live
web
site,
which
is
really
cool
and
I'm
really
excited
about
the
the
lowered
barrier
there
for
helping
new
users
test
functionality
without
needing
to
know
how
to
do
hardly
anything,
no
get
checkouts,
no,
no
merging,
no
patches,
no
nothing!
They
can
just
try
out
the
functionality
right
there
from
the
pull
request,
which
is
really
great.
B
Some
of
those
more
things
you
would
like
to
help
us
on
yeah.
Take
a
look
at
that
tag.
In
the
backdrop,
CMS
org
issue
queue
and
we've
still
got
a
lot
of
other
things
that
we're
pushing
forward
on
to
help
tightly
integrate
backdrop,
CMS,
org
and
github,
and
to
smooth
over
some
more
of
our
development
processes.
B
It's
also
great.
We
have
a
new
one
of
the
new
control
modules
that
was
published
a
couple
weeks
ago.
Is
the
github
API
module
that
Gore
wrote
and
we've
that
basically,
is
like
a
central
functionality
for
setting
up
an
application
having
backed
up
to
CMS
act
as
an
application
for
other
github
integrations,
and
we
previously
had
a
project
module
kind
of
doing
the
cheating
way
of
integrating
with
github
that
had
just
used
a
private
access
token,
which
is
basically
like
a
stored
password
and
with
the
new
github
API
module
project.
B
Module
now
uses
it
to
set
up
a
proper
application
where
you
grant
the
application
access,
and
then
it
can
do
things
on
behalf
of
your
account.
So
that's
great
that
we
have
that
module
available
now
and
project
modules
depending
upon
it
and
the
new
sandboxes
are
depending
upon
it
and
it
paves
the
way
in
the
future
for
making
it
so
that
our
single
sign-on
solution
potentially
could
depend
on
in
the
future
as
well.
So
that's
an
issue
that
we've
got
in
the
next
category,
which
is
improvements
to
backdrop.
A
Right,
so
what
we've
been
working
on
most
recently
is
getting
ready
to
build
a
showcase
for
websites
that
are
built
with
backdrop,
and
last
week
we
actually
were
able
to
get
up
a
blog
post,
thanks
to
a
bunch
of
you,
that'd
emailed
insights
that
you
are
working
on
and
we've
got
a
couple
more.
Actually,
since
we
made
the
blog
post,
I
was
like
emailing
and
let
us
know
a
couple,
people
will
be
emailed.
A
Other
sites
have
been
working
on,
so
I
think
we
should
kind
of
do
this
routinely
until
we
get
our
showcase
up
is
where
we
can
just
kind
of
put
a
couple
sites
in
the
blog
every
now
and
then.
A
People
excited
about
new
stuff
coming
out
in
Bactra,
but
the
showcase
section.
Hopefully
we
can
also
get
done
soon.
We
evaluated
a
bunch
of
other
websites
out
there
that
had
showcases
Drupal
actually
has
two
of
them,
and
there
was
one
that
was
WordPress.
We
looked
at
a
couple
of
others
as
well
tried
to
figure
out
what
kinds
of
content
Lee
wanted
to
put
into
the
showcase,
and
now
that
we
know
what
we
want
to
show
off.
We
also
need
to
figure
out
how
to
display
visually.
On
the
page.
A
That's
turned
over
to
design
and
Darius,
though,
usually
our
elite
designer
has
been
pretty
busy
lately,
and
so,
if
we
have
anyone
who
wants
to
take
a
stab
at
working
on
design
for
a
showcase
section
of
our
site,
that's
definitely
something
that
we
need
and
I
think
it's
ready
for
that
now,
so
definitely
love
still.
If
that's
something
you
want
to
work
from
and
weekend
and
figure
out
what
next
steps
are
for
them.
We
also
want
to
be
able
to
put
a
service
provider
contractor
listing
as
part
of
backdrop
CMS
to
org.
A
So
if
you
are
a
company
that
provides
backup
services
or
a
person
who
wants
to
be
hired
to
work
on
backdrop
and
we
can
get
those
listings
up,
and
so
what
I've
done
since
last,
because
I've
added
a
checkbox
on
user
profile
pages
that
you
can
list
yourself
as
being
for
hire,
which
is
something
I
saw
on
github.
I
think
that
I
copied
that's.
All
I
need
to
do
is
set
up
a
view
with
people
who
want
to
be
a
list
of
this
for
hire.
A
A
These
are
the
people
that
were
involved
in
making
them
and
kind
of
record
cross-reference
everything
and
get
those
super
rich,
relational
bits
of
data
at
you,
but
for
now
I'll
just
create
the
content
buckets
people
can
enter
them
into.
We
do
also
want
to
do
single
sign
on
github,
as
Nate
mentioned
earlier.
That's
something
that
would
allow
people
who
already
have
an
existing
github
account
to
click
a
button
to
be
able
to
log
into
backdrops
a
mess
torch.
They
wouldn't
need
to
spend
time
creating
account
in
order
to
do
that.
A
I
think
that's
going
to
be
more
important
going
forward
as
we
start
to
kind
of
grow,
our
community
beyond
Drupal,
the
more
used
to
having
special
accounts
and
special
places,
but
we
need
a
volunteer
to
actually
hand
handle
creating
that
single
sign-on
solution.
So,
if
anybody's
really
interested
in
writing
code
to
login
with
your
github
account
on
vector
of
CMS
to
org,
that's
definitely
up
for
grabs.
A
So
I
think
that
that's
important,
but
we
don't
have
anyone
working
on
it
right
now
and
in
longer-term
we're
also
gonna
look
at
some
of
the
other
things
that
were
super
successful
on
drupal.org
and
make
them
on
factor
of
CMS
torque,
and
one
thing
that
I
really
liked
was
the
jobs
section.
Of
course
it
would
be
good
if
we
had
jobs
and
a
need
for
job
listings
before
that
one
up,
but
it
is
kind
of
on
our
long-term
trade
are
being
like
wow.
Look
how
great
that
worked
for
Drupal.
A
We
should
consider
doing
that
as
well.
So
there's
a
bunch
of
other
stuff
that
we
have
already
built
on
backdrop.
Cms
torque,
that
needs
improvements,
defined
modules,
page
the
find
themes
page
and
find
lay
odds
page
in
particular,
and
we
have
designs
for
all
of
them
with
well
have
designs
for
modules
and
themes
with
only
implemented
modules,
and
that
current
design
is
across
all
three
of
those
find
pages.
We
have
designs
for
themes.
If
somebody
wants
to
work
on
building
out
that
I
think
that
would
be
probably
our
next
high
priority.
A
I
am,
and
then,
when
it
comes
to
layouts,
we
need
to
kind
of
rethink
that
space
and
try
and
figure
out
what
the
use
cases
are,
what
the
user
stories
are
for
people
trying
to
find
layouts.
What
do
they
need
to
see
and
then
come
up
with
a
design
there
that
off
initially,
because
we
didn't
really
know
what
people
were
going
to
be
doing
with
layouts
and
maybe
now
that
we
have
a
little
more
insight.
We
can
design
that
a
little
better.
A
So
we
need
some
work
done
there,
and
then
we
also
have
follow-up
issues
for
the
find
modules
page.
We
haven't
completely
implemented
the
designs
because
there
were
some
development
tasks
blocking
it.
We've
also
had
some
feedback
on
what's
there
and
we
need
to
do
a
little
kind
of
a
improvement
on
that.
We've
got
a
set
of
follow-up
issues
that
need
to
be
resolved
around
getting
information
and
people
need
and
in
ways
that
this
useful
for
them
onto
those
pages.
We've
got
a
set
of
those
and
we've
also
added
the
blog
section
recently.
A
The
events
section
that
could
those
could
use
a
design
review.
So
if
we
have
someone
that
has
that
I
for
designed
to
just
kind
of
look
at
it
and
say
this
particular
element
is
an
inline
with
this
that
I've
got
the
rest
of
the
backdrop
site.
We
can
clean
that
and
fix
that
too.
So.
A
C
A
That
would
be
part
of
the
project.
Github
module,
the
one,
the
implements
project,
module
with
github
and
I,
don't
think
we're
pulling
downloads.
We
need
to
pull
downloads.
We
also
need
to
pull
like
the
github
page
for
each
project
so
that
we
can
build
link,
select
the
wiki
in
the
issue,
queue
for
the
module
page
and
even
though
we
might
be
able
to
construct
those
URLs
out
of
like
the
project
name
that
we
already
have.
We
don't.
We
have
that's
just
not
done
yet.
We
just
don't
have
a
way
to
get
that
information
out.
A
So
we
either
need
to
do
some
kind
of
display
on
like
the
node
or
some
kind
I,
don't
know
how
we
definitely
need,
like
a
field
in
the
database
for
downloads,
but
on
other
should
be
a
field
field
or
whether
it
should
be
part
of
project
github
that
just
pulls
in
the
data,
but
there
we
don't
have
all
the
information
we
need.
We
have
a
place
to
put
it,
we
haven't
really
thought
about
how
to
get
it.
There
yeah.
B
We'd
probably
need
to
need
to
be
more
than
a
field,
because
if
you
want
to
do
like
downloads
/
we
you
know
that
sort
of
thing,
then
you
would
need
to
store
it
in
it.
There
would
have
to
be
a
lot
of
entries,
yeah
I'm,
not
actually
sure
that
we
could
do
downloads
per
week.
Now
that
I
think
about
it,
like
github,
is,
has
the
total
number
of
downloads
for
sure,
and
we
can
retrieve
that
information
from
github
and
the
way
that
actually
works.
Is
they
only
track
downloads
of
releases?
B
So
you
you
get
information
about
the
release
via
the
API,
and
it
tells
you
how
many
downloads
that
there
been
total
and
I
suppose
if
we
got
really
smart
and
we
executed
on
a
regular
basis,
we
could
calculate
downloads
over
time.
You
know
like
if
we
did
it
on
a
weekly
basis.
We
could
say
this
many
downloads
this
week
by
comparing
the
numbers
against
each
other.
So
it's
all
options.
Yeah.
A
Okay,
so
we
know
we
can
do
it,
we
just
aren't
doing
it.
This
is
we
need
to
think
about
how
but
yeah
it
would
be
great
to
get
the
download
numbers
would
also
be
great
to
get
the
links
to
the
github
project
page
and
the
github
wiki,
and
all
that
stuff
to
issue
queue
yeah
event
listings.
We
also
have
a
way
that
anybody
who
has
a
backdrop
CMS
to
org
account
can
add
an
event.
A
So,
if
you're
an
event
organizer-
and
you
want
back
for
people
to
know
about
it,
you
can
put
it
up
there.
If
your
speaker
you're,
giving
a
talk
in
event,
you
don't
people
know
about
it.
You
can
add
that
as
well
and
hopefully
that
will
prevent
the
need
for
the
google
calendar.
We're
also
going
to
try
and
add
ical
links
to
each
one
of
those
events
so
that
anyone
can
add
an
individual
than
to
their
calendar
without
having
to
add
an
entire
calendar
to
their
calendar
to
get
all
of
the
months.
A
A
So
speaking
of
news
last
week
we
did
post
the
showcase
blog
I
and,
in
theory
tomorrow
table
be
writing
a
blog
post
about
benchmarking,
a
backdrop
on
the
HP.
Seven
I
hope
you
like.
That
won't
really
happen.
So
if
anybody
has
another
blog
post,
you
have
an
idea
you
want
to
get
up.
We
would
love
to
have
bluquest
by
anyone
on
any
topic
about
backed
up
for
tomorrow.
Whoo
jeff
has
a
benchmarking,
blog
post.
D
B
B
Is
fun?
Maybe
this
one's
going
to
be
easier
because
the
last
yeah
I
was
trying
to
follow
somebody
else's
sandbox
set
up
and
it
was,
it
was
kind
of
all
hacked
together
and
the
instructions
weren't
actually
accurate.
It
was
funny
because
he
was
like
at
the
end
of
his
article.
He
was
saying
you
know,
feel
free
to
like
double
check
my
work
by
using
this
github
project
and
then
I
went
and
tried
to
duplicate
what
he'd
done
and
it
was
like
it
complete
it
completely
impossible.
B
A
D
A
And
so
we've
got
a
blog
post
in
the
works
about
backdrop
on
Kayla
box,
but
we've
got
a
couple
of
tasks
to
set
up
before
that
I'll
be
ready,
and
we
want
to
make
sure
that
backdrop
has
its
own
docker
information
right
now
we're
just
using
the
Drupal
7
stuff.
We
think
it
would
be
good
to
have
like
official
backdrop
stuff
to
you-
maybe
upgrade
our
PHP
version
to
the
HP
seven,
something
like
that,
but
we
are
definitely
open
to
getting
new
blog
on
the
radar.
A
So
just
let
us
know
if
you
have
any
of
that
and
we
did
actually
get
a
newsletter
out
on
the
20th,
which
was
fantastic.
I'm
not
sure.
I
think
it's
not
really
last
friday
or
the
friday
before,
not
sure.
If
you
guys
got
it,
I
actually
didn't
get
it.
I
had
to
go
and
subscribe
to
the
newsletter.
Oh
it's
just
like
news
are,
went
out
and
I
didn't
get.
It
was
really
sad.
I'll
get
the
next
one,
and
so
we've
got
a
schedule
where
the
next
newsletter
to
God
is
going
to
be
right.
A
After
a
backdrop,
1.4
I've
got
one
is
what
are
going
out.
Every
month
we
missed
februari,
we
got
March
so
hopefully
we'll
keep
doing
that.
You
can
sign
up
for
the
newsletter
on
the
footer
of
any
page
on
vector
of
CMS
org
I
was
thinking
about.
A
How
do
I
sign
up
when
I
went
to
the
news
page
now,
psychology
put
here
and
so
we'll
try
and
make
that
a
little
easier
for
people
to
sign
up-
and
I
think
getting
kind
of
a
constant
stream
of
updates
to
everybody
on
the
newsletter
will
also
be
good
good
for
letting
everyone
else
going
on.
So,
let's
see
ya,
okay
april
twentieth,
I
skipped
an
issue
april
twentieth.
A
A
Alright,
so
backdrop
CMS
itself
we
have
this
is
last
week's
134
was
out
Nate.
Do
you
want
to
give
an
update
on
135.
B
Yeah,
there's
not
a
whole
lot
going
on.
We've
got
a
couple
of
you
know
bugs
that
we
know
about
some.
As
always
like
there's
outstanding,
you
know
security
issues,
but
we're
coordinating
with
the
Drupal
team
on
those
I.
Don't
think
that
there's
likely
to
be
the
security
release
for
the
next
couple
of
weeks,
but
that
might
be
what
135
is
or
it
might
be
more
more
bug
fixes,
so
just
as
needed
for
one
through
five,
when
that
happens,
it'll
it'll
happen,
but
it's
not
on
the
immediate
horizon
and
there's
not
really
any.
B
It
basically
means
we
need
to
do
like
a
rewrite
or
a
new
version
of
a
module
that
has
the
simplicity
of
node
and
user
reference
modules,
but
the
flexibility
of
entity,
reference
module
and
we
need
to
think
about
an
upgrade
path.
So
we've
got
a
lot
of
problems
that
we're
facing
with
references
and
there's
an
issue
where
there's
a
start
on
the
module,
but
not
really
it's
not
really
useful.
Yet
so,
if
you'd
like
to
put
some
help
towards
1.4,
that
would
be
great
issued
1301.
B
C
Sure
my
updates
are
the
dates,
doing
all
the
work
and
rush
and
redirect,
but
it's
great
though
Nate
DM
tified,
redirect
into
just
the
class
instead
of
extending
entity
class
just
its
own
class
now
and
that's
working
great
from
what
I've
tested
other
testers
are,
of
course
welcome.
Now
I
didn't
test
like
the
views
and
managing
of
it,
but
yeah
I
should
do
that,
but,
like
on
the
node
manage
form
it's
working
great
and
if
you
changed,
you
know.
C
I
I
would
vote
for
making
that
a
new
issue,
I
guess,
there's
two
ways
we
could
go
with
that,
like
one
thing,
is
I
kind
of
had
my
eye
on
helping
out
on
references
module,
but
if
we
like
wanna
focus
on
more
work
on
the
redirect
I
can
keep
my
efforts
there
or
we
can
make
a
new
issue
to
make
that
better
with
the
UX
and
stuff
and
I
could
Aaron
some
attention
to
references.
C
B
Okay,
but
we
just
have
new
abilities
with
like
dialogues
being
part
of
core
to
make
some
UX
improvements
that
would
make
redirect
better
than
it
ever
has
been
before,
which
ought
honestly
it's
already
better
than
ever
has
been
before,
because
like
getting
rid
of
those
stupid,
infinite,
looping
redirects
is
probably
like
yeah.
That's
that's
got
to
be
the
biggest
win
that
redirect
is
seen
in
the
last
five
years.
B
Okay
yeah,
so
that's
looking
great
issue:
9
05!
We
could
use
some
additional
testing
on
that
and
looks
like
we
have
to
fix
a
test,
but
yeah
I
think
I
think
you're
right
that
we
should
merge
that
in
in
the
near
future
and
get
the
pr
updated
and
then
and
then
make
a
new
issue
for
for
additional
follow-ups.
Oh.
B
B
E
E
Bootstrap
for
is
making
a
flexbox
grid
system,
so
I
took
what
they
have
and
I'm
modifying
it
for
our
use
and
I'm
also
I
want
to
make
sure
that,
like
people
know
that
we
took
in
modified
what
they
have,
even
though
you
know
we're
allowed
to
I
want
to
make
sure
that
we
give
them
some
credit
in
the
code
there.
So
there's
a
little
comment,
but
yeah
we're
modifying
it
enough
that
we're
probably
not
going
to
keep
it.
Keep
that
at
least
that
CSS
file
up
to
date.
E
I,
don't
think
that'll
happen,
but
I
want
to
give
people
the
option
until
it's
more
adopted
than
it
is
now
I
think
it
has
reach
maturity,
though
so
yeah
and
then
there's
there's
lots
of
updates
and
some
demos
on
from
the
design
call.
So
if
you
look
up
the
YouTube
video
for
that,
you
can
get
a
detailed
update,
but
yeah
it's
in
so
I'm
working.
It's
in
backdrop,
contribs.
E
And
like
and
make
stuff
work,
but
definitely
if
you
want
to
mess
with
it
see
what
the
grid
system
looks
like
all
that
it
is.
It
is
far
enough
that
you
could
do
that
so
yeah
taking
any
issues.
Any
people
that
want
to
help
work
on
it
would
be
welcome.
Just
shoot
me
a
message
and
I'll
get
you
set
up
and
give
you
a
breakdown.
Tada.
B
Managed
to
fit
in
just
as
the
dogs
exploded,
great
yeah
we've
got
an
issue
for
adding
new
chord
layouts,
as
well
as
a
new
front.
End
Dean,
that's
separate
issue,
698
and
I
think
I'm
an
agreement
to
it's
putting
the
agenda
here
that
it's
looking
a
little
unlikely,
we're
still
kind
of
figuring
out
the
relationship
between
layouts
and
themes
and
I
kind
of
feel
like.
We
should
figure
that
out
completely
before
we
rush
anything
and
start
making
a
lot
of
problems
for
ourselves
in
the
future
by
having
things
that
were
kind
of
not
completely
understood.
B
So
we've
got
that
one
it
might
be
tabled
for
the
next
release.
We've
got
a
lot
of
things
that
are
meeting
a
lot
of
work
before
1.5,
and
if
we
had
to
focus
our
efforts,
we
would
focus
them
elsewhere
and
probably
leave
that
one
for
later
we've
got
an
issue
for
improving
the
rich
text.
Editor
issue
1087,
and
this
is
a
meta
that
has
a
whole
bunch
of
sub
issues.
The
bugs
that
are
in
the
rich
text.
Editor.
We
can
solve
any
time,
but
one
item.
B
We
definitely
need
to
do
for
sure
before
the
next
releases
we
have
to
upgrade
see
can
deter
to
the
latest
version
or
quite
a
bit
behind
at
this
point,
but
there's
a
lot
of
other
items
in
that
meta
in
ways
that
we
can
improve.
The
rich
text
editor
if
you're
looking
to
improve
the
editorial
experience,
have
a
big
great
issue
to
look
at
and
we've
gotten
a
number
of
other
issues
that
are
just
tagged
for
the
one
point.
B
Four
point:
no
release
that
you
can
see
by
just
using
the
tag
or
the
release
number
on
the
github
issue-
tracker.
Oh
here
they
are,
I
was
I
was
wondering
if
they
got
dropped
off
the
agenda,
but
they're
still
here.
We
also
have
two
things
that
weren't
on
the
road
map,
but
we're
trying
to
get
them
integrated.
In
any
case,
the
first
one
is
project
browser
and
project
browser
has
been
seeing
some
really
exciting
work.
In
recent
days.
I
think
doc
wellmont
made
a
bunch
more
made
a
whole
lot
more
progress
on
project
browser.
B
Actually,
it
looks
like,
as
of
yesterday,
he
posted
a
huge
amount
of
feedback
that
I
haven't
managed
to
read
over
yet,
but
the
project
browser
is
really
exciting.
If
you'd
like
to
give
it
a
shot,
you
can
do
so
using
the
new
sandboxes
feature
and
it's
really
quite
fun.
It's
also
really
kind
of
terrifying.
That's
like
you're,
using
somebody,
elses
computer
and
installing,
when
I
her
module.
You
want
from
backdrop
CMS
done
or
gone
to
it,
including
do
del
naja.
You
can
just
you
know.
B
I'm
just
gonna
run
some
PHP
code,
but
yeah
we're
working
on
untighten
endowment
of
those
same
boxes
as
well,
but
but
it
is
really
cool
to
see
it
in
action,
and
so
I
will
be
taking
a
look
at
that
later
today,
and
anybody
else
that
as
an
opportunity,
it
would
be
really
great
to
take
a
look
at
that
its
last
I
looked
at.
It
was
looking
really
good
and
so
I
think
that
that's
I
mean
that's
probably
with
redirect
the
thing
that
is
most
likely
to
be
finished
in
the
nearest
timeline.
B
So
that's
that's
great,
oh
and
also
exciting,
about
project
browser.
It's
separated
out.
It's
been
separated
from
update
module,
it
still
depends
on
update
module
now,
but,
but
it
makes
it
now.
So
if
you
don't
want
the
ability
to
install
a
module
on
your
site
right
now,
if
you
have
update
module
turned
on,
you
have
the
ability
to
also
install
a
module
through
update
module,
which
is
very
weird
that
those
things
are
tied
together
and
so
that
functionality
to
install
a
module
has
been
moved
into
the
Installer
module,
which
is
now
the
browser.
B
B
If
you
turn
on
the
Installer
module,
it's
actually
like
reasonable,
like
a
way
to
find
and
install
modules
rather
than
copying
and
pasting
a
URL
yeah,
so
yeah,
it's
very
cool
issued
1399.
If
you'd
like
to
give
that
a
shot
and
help
do
some
review
on
it.
What
s
have
an
issue
for
improving
the
field?
You
I
there's
a
lot
of
really
excellent
ideas
in
this
issue.
Issue
779.
In
the
backdrop
cork,
you-
and
that
again
is
like
we've-
got
a
lot
of
great
ideas
there,
but
implementation
hasn't
hasn't
moved
forward
very
far.
There's
really!
B
Yes,
simple
ideas,
we're
not
talking
about
a
rewrite
of
field!
You
I
we're
just
talking
about
iterating
on
some
basic
improvements
and
so
I'd
love
to
see
some
some
progress
moving
forward
there,
but
we've
all
got
priorities.
So
that's
it
a
good
one
to
keep
an
eye
on.
Nonetheless,
okay,
there's
also
a
whole
bunch
of
you
x,
+
DX
issues
tagged
as
such,
with
square
brackets
before
their
name
on
github.
That
we'd
always
like
to
keep
an
eye
on
those
and
continuously
improve
the
user
experience
throughout
backdrop.
B
B
E
Had
one
thing
that
I
forgot
to
mention
with
the
new
theme
we're
probably
going
or
we
are
going
to
have-
to
update
the
mark-up
of
the
existing
theme
somehow,
but
we're
also
going
to
have
to
respect
that
sites
are
currently
using
the
existing
layouts.
We
don't
want
to
break
that,
so
we
might.
They
do
something
rude,
but
all
right
there
is
going
to
be
some
update
to
layouts
if
the
new
theme
gets
in,
but
maybe
not
the
addition
of
a
bunch
of
layouts
yeah.
B
B
A
B
So
something
from
doc,
well,
mutt,
one
thing
I
really
need
to
help
for
is
to
figure
out
why
project
browser
pull
request,
passes
locally
but
fails
on
Travis.
Basically,
okay,
yeah
they're.
There
are
some
funny
things
with
Travis,
because
Travis
runs
through
a
fast
CGI
back
end
rather
than
using
the
built-in
Apache
PHP
like
mod
PHP.
So
there's
a
difference
there
that
sometimes
can
cause
some
unusual
behavior
between
a
local
host,
which
is
usually
running
Apache
and
the
remote
one,
which
is
also
running
Apache,
but
is
running
PHP
through
fast
CGI.
B
So
that
would
be
my
guess
as
to
a
difference,
and
it
would
be
good
if
it's
happening
on
Travis.
That
means
it
also
would
be
happening
to
other
sites
that
were
running
like
engine
X,
for
example,
which
is
what
we're
doing
on
backdrop.
Cms
don't
work
so
yeah
I
can
I
can
take
a
look
there,
there's
a
lot
of
feedback
there
that
needs
reviewing,
and
that
is
on
my
agenda
for
today.
D
A
B
Cool
well,
if
there's
nothing
else,
every
Thursday
we
like
to.
We
call
them
backdrop
days,
I'm,
not
sure
if
it's
the
same
for
everybody,
but
black
up
Thursday's
to
do
sprinting
and
we
mostly
coordinate
through
the
backdrop
issue
queue
github.com
/
backdrop
we're
also
regularly
or
increasingly
using
git
er
for
live
communications.
So
there's
a
link
to
get
er
from
the
backdrop.
Cms
org
issue
queue
it's
in
the
readme.
No,
it's
also
in
the
agenda
get
ur
da
IM
/
backdrop
/
backdrop
dash
issues.
B
I
know
it's
a
little
bit
of
a
long
URL
for
a
chat
channel
but
get
ur
is
actually
really
pretty
great.
It's
got
great
native
apps.
It's
got
a
great
in
browser.
Experience
is
basically
identical,
the
slack,
but
it's
it's
integrated
with
github
and
it's
free,
unlike
slack
so
well,
yeah,
select
as
complicated
as
far
as
its
business
all
goes,
but
Gators
actually
been
proving
to
be
a
really
pretty
great
tool,
and
we
now
have
an
IRC
bot
in
there.
That
is
very
friendly
dragon
bot.
B
So
you
can
work
on
building
your
karma
in
the
get
er
channel.
We
also
still
have
the
IRC
channel
pound
backdrop
on
freenode
we've
been
considering
get
er
runs
in
IRC
network
as
well.
B
We've
been
considering
deprecating
the
channel
on
freenode
and
telling
people
to
join
the
Gator
server
instead
and
then
ever
all
of
the
chat,
whether
you're
in
IRC
or
on
kiddo,
would
all
be
in
the
same
place,
but
obviously
a
git
er
chat
server
is
not
the
same
as
freenode,
and
really
almost
everybody
is
familiar
with
freenode
and
not
very
many
people
are
actually
familiar
with
setting
up
separate
chat
servers
like
joining
an
authenticating
into
a
separate
shots
over.
So
there's
some
barriers
there,
but
we
are
also
an
IRC
pound
backdrop
on
freenode.
B
If
IRC
is
your
preferred
mechanism,
there's
still
a
good
number
of
people,
there
hang
out
there
as
well
rabbit
channel,
it's
kind
of
not
really
sure
if
there's
a
lot
of
activity
happening
over
on
reddit
these
days,
but
we
do
have
a
channel
ready
to
calm,
/
r
/
backdrop
for
talking
about
kind
of
water,
cooler,
discussion
about
backdrop
and
things
that
are
happening
around
it.
B
We
have
an
ical
feed
of
upcoming
backdrop.
Events,
including
I,
think
these
meetings,
so
you
can
see
when
the
meetings
occur
and
events
at
which
backdrop
is
either
people
are
presenting
on
backdrop
or
the
organizers
have
just
stated
that
they
would
like
backdrop,
people
presence
to
kind
of
increase
the
diversity
of
their
of
the
talks
and
topics
and
attendees
drupalcamp
guadalajara
is
coming
up
next
weekend.
Jen
and
I
are
going
to
be
there
for
anyone
in
Mexico.
B
We
would
love
to
see
you
and
we
love
Mexico,
so
we're
really
excited
to
be
going
down
there
and,
and
speaking
on
backdrop
of
course,
and
now
on
the
website
backdrop
see
my
storage,
/
events,
a
real
lightweight.
This
is
really
lightweight
a
list
of
events
that
are
coming
up
at
which
you
can
find
backdrop,
people,
but.
A
B
B
Okay.
Last
item
of
news:
we
have
a
Bookout
migrating
from
Drupal
to
backdrop
from
a
press
by
Todd
tom
olson.
You
can
order
from
a
press
or
from
amazon,
and
I've
been
hearing
a
lot
of
news.
Oh
yeah,
there's
copy
of
it
right
there,
great
book,
technically
accurate,
really
pretty
short,
it's
only
80
pages
or
so,
but
a
great
introduction
to
getting
your
site
moved
from
Drupal
7
to
backdrop,
he's
also
doing
a
lot
of
work
publishing
beginning
the
backdrop
which
will
hit
this
hit.
The
shelves
second
quarter.
Second
quarter
starts
tomorrow.
B
Actually
so
sometime
in
the
next
three
months,
we'll
probably
be
seeing
the
first
full
book
on
backdrop
and
I've
been
seeing
some
activity
in
the
get
er
channel
from
Goldman,
tix
I.
Think
saying
that
he's
been
doing
some
reviewing
on
that
book
as
well.
So
it's
definitely
happening
it's
coming
along
and
I
can't
wait.
It's
going
to
be
great.