►
Description
Today’s development agenda: http://bit.ly/1sB8cJr
B
B
You
need
to
be
a
member
of
the
actual
contribute
on
github,
because
that's
where
the
phpstorm
folks
check
to
see
if
you're
allowed
to
have
it,
but
if
you
don't
have
a
module
or
theme
to
contribute
yourself,
you
can
definitely
offer
to
co,
maintain
something
for
someone
else
or
help
me
initiation,
Q's
stuff,
like
that.
We
can
use
health
and
lots
of
different
places,
so
go
ahead
and
get
set
up
when
we
can
send
you
a
license
key.
If
you'd
like
to
make
a
donation
to
backtrack
CMS,
you
can
do
so
on
our
contribute
page.
B
We
have
adorable
t-shirts
and
hoodies.
We
send
notice.
Thank
you.
Gifts
and
I
think
we
are
nearing
the
point
where
we're
going
to
be
ordering
some
more
t-shirts,
because
we're
running
out
of
everybody's
favorite
size,
so
I
think
if
we
can
get
one
or
two
more
hoodie
level,
donations
will
be
ready
to
order
those
shirts.
So
that's
kind
of
exciting.
B
If
you
are
interested
in
setting
up
a
local
development
environment
using
Calla
box,
they
support
backdrop
natively,
which
is
great.
It
chooses
docker.
You
can
find
out
more
about
Kalibak
Kalibak
I,
oh,
and
that
is
it
for
our
general
announcements.
I,
don't
think
we
have
any
updates
or
p.m.
see
this
week.
So
let's
turn
it
over
to
Nate
for
community
right.
C
Hey
saw
another
exciting
week
in
the
world
of
a
backdrop:
contribs
like
v
tad
and
DK
n
have
been
porting
modules,
which
is
great
to
see
so.
We've
got
271
total
projects
for
backdrop,
CMS
listed
on
github
five
new
projects
have
been
created
since
last
meeting.
There
are
184
total
projects
on
backup,
CMS
torg,
too
new
ones,
with
official
releases
since
last
week,
with
those
184
projects,
there
are
265
total
releases,
three
new
releases
since
last
week,
53
total
backdrop.
C
Contributors
we've
got
about
a
dozen
pending
applications,
people
that
have
applied
but
haven't
completed
the
review
process,
we'd
like
to
get
those
those
all
those
process,
those
applications
all
completed.
All
of
them
are
just
waiting
on
the
original
authors
to
come
back
and
put
up
their
code
or
or
do
some
last
reviews,
so
we've
been
doing
good
job
reviewing
the
applications
that
come
in.
C
That's
all
I've
got
for
community
growth
another
good
week.
Lots
of
new
projects
coming
in
it's
always
could
see
and
of
course,
we're
always
doing
work
on
on
a
backdrop
itself,
which
also
saw
a
whole
lot
of
activity
this
week.
But
before
we
get
to
that,
we
cover
infrastructure.
Is
the
next
item
on
the
agenda
so
the
first
time
we
have
it
in
the
infrastructure
list.
Here
is
our
testing
infrastructure
course.
C
With
this
today,
gore
and
I
have
been
doing
some
work
on
improving
the
testing
infrastructure,
mostly
court
I'm,
just
their
kind
of
facilitating,
and
we
have
an
issue
issue
1906,
where
we've
been
looking
at
alternatives
to
Travis
CI.
A
couple
ago,
right
before
the
release
of
1.4,
actually
travesty
I
moved
us
from
kind
of
like
their
traditional
iron
servers
to
a
bunch
of
Google
compute
engine
servers
and
resulted
in
a
six
times
slowdown
in
our
tests,
which
took
us
from
like
15
minutes
to
an
hour
and
a
half
which
caused
us
no
end
of
problems.
C
C
So
right
now
our
tests
on
Travis
are
running
in
about
20,
some
minutes
or
so,
which
isn't
great
in
particular,
because
we're
limited
to
five
threads
at
a
time
on
Travis,
and
if
we
have
multiple
people
find
pull,
requests
or
multiple
people
merging,
then
they
all
get
piled
up
on
top
of
each
other,
and
it
can
take
like
over
an
hour
for
people's
tests
to
run
after
they
file
a
pull
request.
So
so
we're
trying
to
find
ways
of
solving
that
problem.
C
You
can
read
up,
but
at
issue
1906
for
the
background
there.
But
the
exciting
thing
is
what
we're
doing
right
now
is
we
are
expanding
our
use
of
Zen
CI,
which
currently
is
providing
our
live.
Sandboxes
Gore
has
made
it
into
a
test
running
service
as
well,
and
so
right
now
what
happens
when
you
file
a
pull
request?
Is
that
it
spins
up
the
lexan
box.
It
still
sends
the
test
requests
up
Travis,
but
we're
also
sending
test
request
off
to
off
tues
NCI.
C
Zen
CI
runs
the
entire
test
suite
on
PHP
7
in
three
minutes,
which
is
pretty
awesome
and
in
PHP
53
it
takes
about
six
or
seven
minutes.
So
it's
really
exciting.
It's
a
lot
faster.
There's
some
promise
of
speeding
it
up
further.
Yet
right
now
gori,
you
can
correct
me:
I,
think
we're
on
12
core,
no
way
acorn
machines,
but
there
are
12
and
16
core
ones
available
that
could
speed
things
up
substantially
more
if,
if
we
get
into
that
kind
of
need,
so
that
issue
is
1947.
C
The
enables
NCI
for
testing.
If
you'd
like
to
follow
up
on
that
issue
and
see
what
action
is
going
on
there.
So
that's
exciting.
Our
testing
infrastructure
is
looking
up.
We're
also
trying
really
hard
to
resolve
the
random
test
failures
that
are
happening.
Sometimes
we
have.
We
do
have
a
lot
of
random
data
input
in
places
where
we
just
use
random
my
strings
and
sometimes
those
random.
My
strings
cause
randomized
failures
or
sometimes
the
runtime.
C
The
speed
of
the
tests
actually
effects
effects,
random
failures,
and
so
we're
trying
to
track
down
all
over
random
failures
at
1478
we've
been
fixing
lots
of
them.
I
think,
would
fix
five
or
six
different
possible
random
errors
in
the
past
couple
of
weeks,
but
they're
still
once
happening
every
now
and
then
so,
if
you.
C
Alright,
that's
it
for
testing
infrastructure.
Next
item
on
the
infrastructure,
tester
we've
got:
dress.
Josh
has
been
working
for
quite
a
while
now
that
you
can
get
it
from
backdrop,
contribs
/
brush-
and
I
think
we
just
check
in
here
to
see
if
Jeff
we've
been
managing
drush.
The
josh
development
has
any
updates
for
us.
D
C
B
Yes,
if
I
can
remember
how
to
unmute
myself
alright,
so
what
we're
working
on
right
now
is
getting
single
sign-on
working
with
github
and/or
also
did
a
bunch
of
work
on
that
I
think
we
just
need
some
more
testers,
I'm
working
on
upgrading
backdrop,
CM
esta
org
to
the
latest
version
of
backdrop
today,
so
I'll
throw
in
that
patch
and
give
that
test
and
see
how
it
goes
at
least
locally.
Maybe
we'll
even
try
it
on
like
a
beta
site
or
something
like
that
as
well.
B
We've
made
any
progress
on
that
recently
we
had
Eric
gold
man,
tix
volunteer
to
do
some
of
the
site
building,
but
I
don't
think
that's
made
progress
for
maybe
the
past
two
weeks,
so
that
would
be
good
for
somebody
else
to
pick
up
if
you
wanted
to,
but
we
also
have
Darius
working
on
design
for
that
now,
so
the
architecture
might
change
a
little
bit.
It
looks
like
we're
going
to
have
three
different
fields
for
various
different
sized
images.
B
So
if
you
want
to
do
desktop
tablet
and
mobile,
that
will
be
a
little
bit
different
than
there
are
original
outline.
So
it
might
be
best
to
wait
for
designs
before
we
go
too
far
on
that,
but
we
could
use
some
additional
volunteers
in
that
area.
I
also
added
a
new
item
here
for
documentation,
because
I
know
that
doc
well
ma
and
Andy
a
viola
thick
have
been
working
on
documentation
and
that's
kind
of
their
focus
for
this
whole
release
cycle.
B
So
I
put
I
put
a
section
in
here
just
to
be
able
to
say
thank
you
guys
for
all
the
work
that
I
know
you're.
You
have
been
and
will
continue
to
put
into
that,
and
hopefully
you
have
everything
you
need
in
terms
of
access
to
the
site
after
I.
Do
the
update
today
I'm
likely
to
break
the
access
to
unpublish
notes
things
to.
B
Know
if
that
gets
broken
after
today
and
I'll
try
and
fix
it,
but
anyone
else
who
wants
to
work
on
that
I
know
I'm
clonise.
You
might
be
interested
in
that
too.
There
is
going
to
be
a
whole
bunch
of
new
documentation
coming
out
here
in
the
next
little.
While
we
could
use
a
lot
of
help
with
that
forums
which
is
the
next
bit.
This
is
also
kind
of
related
to
documentation.
B
That's
number
249
for
which
forums.
We
actually
want
like
how
many
and
what
kind
of
content
they
should
cover.
And
then
I
have
another
issue:
number
250,
which
is
kind
of
the
technical
information
implementation
details
on
what
it
would
look
like
to
build
a
forum
in
in
terms
of
running
into
some
of
the
limitations
that,
like
course,
run
into
running
a
Drupal
7
forum
running
into
some
of
the
technical
challenges
that
we're
going
to
face
by
not
having
a
forum
module
and
then
maybe
using
what
we
create
to
release
a
better.
B
Okay,
that's
cool
document
just
said
he's
working
on
porting
the
brain
forum,
module
I'll,
take
a
look
at
that
and
that
could
could
also
be
super
useful
for
us
as
well
and
then
a
bunch
of
other
stuff
that
are
currently.
We
are
currently
working
on
on
backdrop,
semester,
org
the
East
statistics.
We
want
to
make
those
visible
on
individual
project
pages
and
information
about
backdrop
itself.
We
want
the
find
module,
seats
and
layout
pages
to
be
a
little
bit
more
intuitive
and
show
some
more
information
about
the
projects.
B
So
I
would
love
to
be
able
to
get
those
things
set
up
and
we
could
definitely
use
help
if
anyone
wants
to
contribute
site
building
time
to
backdrop
CMS
org,
a
lot
of
those
things
are
kind
of
quick
one-offs
like
oh.
We
just
need
to
explode
a
filter
on
this
view
and
that's
some
of
them
are
a
little
harder
like
got
to
kind
of
step
back
and
look
at
the
whole
thing
to
say
what
should
to
find
layouts
page
look
like,
but
definitely
some
good
places
for
people
to
get
involved
there.
B
C
C
Redirect
there
we
go
yeah,
we
had
it
in
redirect
module,
which
was
a
huge
improvement.
Yay
very
exciting
features
that
we
added
in
one
point
for
cash.
It
was
not
on
the
agenda.
You
know
it
doesn't
exist
in
my
head
anyway.
So
next
bug
release
one
point
four
point:
three
is
an
as-needed
a
bug-fix
release.
We
don't
have
any
real
critical
issues
that
are
queued
up,
so
we
really
can
make
a
bug-fix
release
any
time,
but
there's
not
really
any
diamond
need
to
do
so.
C
If
you'd
like
to
see
what
is
scheduled
for
the
next
bug-fix
release
or
have
something
you'd
like
to
be
added
to
the
book
fix
released
then
check
out
the
milestone
in
the
github
issue
queue
for
one
up,
for
it
ought
to
be
so.
The
next
minor
release
is
sep
tember
15
2016,
the
editorial
experience
release,
which
has
got
a
number
of
big-ticket
items
on
it.
C
Let's
say
the
first
one
we've
got
on
here
is
the
references
module
we're
playing
wii?
We
don't
even
have
an
entity
reference
type
module
or
any
kind
of
reference
module
in
core.
What
we'd
like
to
add?
One
issue
is
issued.
1301
for
tracking
work
on
the
reference.
I
can
never
remember
if
its
reference
as
a
reference
is
Reverend.
I
want
to
call
Reverend
who
sort
of
yeah
it
won't
like
your
you're,
the
author.
So
far,
what
what
has
been
created
do
you
have
any
updates
for
the
reference
bundle?
No.
E
C
No
problem,
yeah
I,
think
yeah
I
know
a
herald.
A
was
looking
at
potentially
helping
with
that
is
that
has
I've
been
moved
into
a
contributor,
okay,
yeah
I
didn't
maybe
if
we
can
get
moved
into
into
a
public
repository,
then
when
you
get
more
collaboration
between
various
people
working
on
it,
the
episode
was
good
I'll.
Do
that
this
week,
okay
yeah,
that
would
that
would
be
great
yeah
I'm
interested
in
swinging
back
around
to
take
a
look
at
that
as
well.
I
haven't
actually
seen
it
in
action.
C
E
See
the
work,
the
basics
are
there,
the
basics
are
very
simple:
the
actual
references
is
just
essentially
storing
an
IV
and
a
entity
type
in
you
know
a
field
database
or
a
field
database
table.
It's
all
the
sort
of
integrations
and
the
sort
of
letting
users
select
things
that
is,
and
the
user
interface
stuff.
That's
actually
more
of
the
work
that
needs
to
you
know
actually
happen:
cool,
okay,.
C
A
Sure
the
biggest
thing
for
me
is
is
the
color
module,
so
I
haven't
really
been
doing
anything
on
basis
unless
someone
finds
something
a
bug
or
anything,
I
know
Graham
and
maybe
a
couple
that
people
have
been
using
it
for
some
projects,
but
yeah
I
haven't
I've,
been
focusing
on
the
responsive,
drop-down
menus
in
core
and
kind
of
working
on
the
color
module.
More
thinking
about
it
at
this
point
haven't
done
too
much
on
it.
C
A
A
C
A
C
Gritty,
okay,
yeah-
and
you
mentioned
it
already-
that
color
modules
got
some
issues
and
that
that
we'd
like
to
continue
providing
color
module
support
for
the
themes
in
core.
But
it's
really
it's
got
some
UX
issues
and
it
has
some
architectural
issues
that
make
it
really
just
not
very
friendly
to
work
with
and
then
improving.
That
would
be
a
great
thing.
C
Mike
also
opened
up
a
kind
of
a
related
issue
to
that
issue
1949
this
week,
which
basically
suggested
that,
like
some
of
the
suggestions,
you
had
four
color
modules
sound
awesome,
but
they
also
could
be
used
for
any
theme
setting
besides
just
the
colors
I'm,
not
quite
sure
how
this
it
would
work
from
an
architectural
standpoint,
but
it
I
think
it
probably
is
possible.
I
have.
E
B
A
E
We
should
make
it
easy
to
put
color
settings
of
theme
settings
that
sound
flaming
good
solution
without
without
any
sort
of
color
module
thing
right.
It
seems
like
we
need
some
sort
of
like
color
field
and
widget
to
easily
add
like
a
color
field
element
so
that
a
scene
could
just
say:
I
want
to
put
a
color
field,
a
min
value,
and
then
they
could
do
whatever
it
wants.
The
value
later,
yeah.
A
The
only
the
only
thing
I
thought
of
that
we
might
lose
if
it's
not
if
it's
the
job
of
the
theme
is.
If
a
user
says
my
brand
colors
are
blue
purple
and
white
and
then
they
change
themes
it'd
be
cool.
If
we
could
actually
keep
that
setting.
But
if
its
theme
dependent,
it
probably
wouldn't
translate
at
all,
but
if
there
is
a
module
in
might
we
might
and
that's
like
as
good
as
it
gets,
but
then
yeah,
my
other.
E
Business,
this
is
one
of
those
things.
It's
like
you
know
the
someone
having
to
like
re-enter
their
colors
in
when
they
change.
The
theme
isn't
like
that
big
of
a
deal
and
the
art
and
the
architectural
hurdles
that
we
would
have
to
jump
through
to
make
like
colors
work
across
beams
are
kind
of
crazy
and
sort
of
the
color
module
showed
that
that's
not
actually,
that
huge
of
a
priority
for
users
I
haven't
really
found
anyone
who
actually
like
oh
boy,
the
corner
module.
Lets
me
change
my
theme
without
having
to
re-enter
my
colors.
A
A
A
A
E
There's
a
lot
a
little
part
to
be
good
to
add
a
color
field,
type
of
the
field,
API
right
yeah,
that's
in
general.
Just
so,
people
can
create
color
fields
or
something
because
I
imagine
there.
It
might
be
lots
of
different
uses
and
we
might
want
to
actually
make
it
like
fully
featured
work
and
soar
like
all
three
different
types
of
color
coordinates
or
helping.
A
C
C
C
C
Taking
the
lead
on
this
one,
so
anyway,
I
guess
maybe
it's
a
good
time
to
do
a
call
it
if
you're
interested
in
working
on
making
the
homepage
of
your
new
backdrop,
websites
when
you
install
it
on
with
a
box
better
than
issue.
1042
is
a
great
issue
to
look
at
there's
a
lot
of
ideas
going
on
in
there
I
and
I.
Think.
C
The
basic
idea
for
out
of
the
box
is
that
it
will
just
simply
be
a
single-column
layout,
and
then
you
know
a
view
of
your
content
in
the
middle
placed
as
a
block
rather
than
having
/
notice.
The
front
page
will
make
up
a
new
path
like
/
front
or
slash
home
and
make
it
a
be
a
layout
that
you
can
customize
rather
than
needing
to
make
a
new
layout
or
override
/
node
or
you
jus,
something
that
will
make
it
easier
for
people
to
modify
their
homepages.
If
there's
one
there
already.
B
Know
I
was
just
going
to
mention
that
we
also
talked
about
like
it's
going
to
be
pretty
easy
to
just
switch
the
layout
to
a
single-column
layout
and
put
exactly
the
same
content
we
have
in
it,
but
as
part
of
that,
issue
might
be
good
or
as
a
follow
up
to
add,
like
as
some
kind
of
a
hero
thingy,
whether
it's
a
slider
just
in
the
image
Wow.
Just
so
that
I,
the
homepage
is
a
little
bit
different
than
it
was
before.
B
B
So
there
are
some
questions
to
go
along
with
that,
like
what
is
the
hero
thing
like?
Is
it
a
block
type
that
lets
you
upload
an
image
or
is
it?
Is
it
like
a
HTML
fields
that
we
ship
like
an
image
somewhere
in
core
like
a
mist,
kind
of
thing,
there's
a
bunch
of
questions
there
that
need
to
be
answered
to
figure
out
how
we
actually
pull
this
hero
before
we
have
feel
double
block
type
thingies.
There.
A
We
talked
about
on
the
design
meeting.
I
was
going
to
try
making
some
CTools
content
types.
You
could
just
add
the
layouts
up
and
see
how
those
feel
for
being
a
controller
core
thing
and
hero
being
one
of
them.
That
could
be
a
temporary
solution,
in
which
case
would
be
contributing
that
core,
but
yeah
thought,
but
then
there's
the
whole
making
field
bowl
and
eat
something
or
other
blocks.
C
C
Okay,
next
item
on
the
agenda
is
improving
the
rich
text,
editor,
which
we've
got
a
large
meta
issue
at
1087,
some
items
of
which
are
just
long-standing,
bugs
that
we've
got
in
the
rich
text
editor
and,
as
always,
those
bug
fixes
don't
need
to
wait
for
1.5,
but
we
would
like
to
put
a
focus
on
the
rich
text.
Editor
experience
and
improving
it.
C
There's
some
items
that
that
do
need
to
wait
like
rework
working
the
filter
tips,
improving
the
text
format
you
I,
adding
in
new
buttons
to
seek
editor
things
like
like
a
code
tag
right
now
is
ridiculously
hard
which
is
really
inconvenient
for
a
bunch
of
developers
such
as
ourselves.
So
when
we
have
writing
a
blog
post
like
on
backdrop,
CMS
done
or
you
can't
do
a
code
tag,
it's
quite
frustrating
so
we'd
like
to
improve
a
lot
of
those
items,
there's
a
whole
list
of
things
issue
1087
most
of
them
are
up
for
grabs.
C
C
That's
it
that
we've
got
for
the
1.5
release.
A
new
stuff
can
still
crop
up
that
we
could
implement.
In
one
point
five,
we
do
have
two
special
tags:
the
square
bracket,
UX
and
square
bracket,
DX
tags
on
github
that
we're
always
trying
to
do
continuous
improvements
in
our
minor
releases.
So
if
you
have
anything
that
is
a
UX
or
DX
improvement,
we'd
love
to
see
it
improved
as
soon
as
possible
and
we're
always
open
to
including
new
features
in
minor
releases
that
aren't
on
the
agenda.
C
So,
let's
see
that's
all.
We've
got
for
the
1.5
release,
updates
news
and
announcements.
We've
got
an
official
schedule
of
blog
posts
that
will
come
up
on
bankruptcy,
my
start
wearing
under
the
bankruptcy.
My
org
issue
queue
issue,
158
the
next
item
on
our
next
blog
post.
To
be
written
is
on
my
plate
for
writing
up
about
our
new
core
committers.
That's
Jeff,
dark
woman,
I'd
actually
like
to
include
you
in
there
as
well,
because
a
lot
of
people
don't
know
that
that
we
have
multiple
core
committers
as
much
as
me.
We've
actually
got
three.
C
If
you
have
an
idea
for
a
blog
posts
or
would
like
to
write
up
a
blog
post,
you
can
comment
on
issue
158
and
if
you
just
want
to
write
something
up
on
backup,
CMS
org,
you
can
do
so
everybody,
or
maybe
not
everybody.
Everyone
with
the
editorial
editor
role,
can
write
up
a
blog
post
on
backdrop
semester
or,
if
you
don't
have
that
that
role,
we're
happy
to
give
it
to
anybody,
and
then
you
can
write
a
blog
posts.
C
Let's
see
newsletter,
so
the
newsletter
were
were
caught
up
on
the
news
letter
announcing
1.4,
which
I
know
is
like
now.
It's
been
two
weeks
because
we're
waiting
on
me
to
push
out
1.42
Pantheon,
which
right
now
we're
really
by
confident
about
the
status
of
things,
and
we
should
just
push
that
out
as
soon
as
possible.
Oh.
C
We
also
have
a
whole
tag
for
for
marketing
type
items
under
the
backdrop
CMS
toward
website.
If
you
visit
github.com
/
backdrop,
ops,
the
backdrop
CMS
org
is
your
cue,
then
there's
a
whole
label
for
for
marketing
tasks.
If
you're
experienced
in
marketing,
it's
probably
the
area
that
we
need.
The
most
help
in
like
of
everything.
Marketing
is
probably
our
weakest
strength,
and
so,
if
you're,
injured,
marketing
and
you're
watching
this
video-
and
you
think
oh
I,
love
marketing
or
I
can
write
a
blog
posts
or
newsletters
or
I
like
managing
social
media
accounts.
C
Any
of
those
things
you
can
check
out
that
tag
to
see
areas
that
we
need
help
and
volunteer
and
we'd
love
to
have
have
additional
help
in
marketing
sprints
every
thursday.
That's
today
we
do
backdrop
day
it's
when
a
gemini
and
a
lot
of
people
here
in
this.
This
call
we
set
aside
some
time
to
work
on
backdrop
in
our
primary
place
of
communication
is
in
github
issue
queue,
github.com
/
backdrop,
/
backdrop
issues.
C
You
can
also
check
us
out
on
twitter,
where
we
have
more
real-time
conversations,
get
ur
da
IM
/
backdrop
/
backdrop
dash
issues.
We
also
have
an
IRC
channel,
though
it's
not
frequented
very
often
anymore,
IRC,
freenode,
dotnet
/
backdrop,
and
we
have
an
ongoing
a
reddit
channel
if
you're
interested
in
reddit.
C
And
that's
where
you
do
your
communications,
you
can
also
check
us
out
reddit
com,
/,
r,
/
backdrop,
upcoming
backdrop,
events
you
can
check
out
the
calendar
bankruptcy
last
org,
slash
events:
silicon
is
happening
right
now,
actually
and
obviously
a
we
are
not
there.
At
least
the
people
that
is
meeting
are
not
there,
but
it
is
a
backdrop
friendly
event:
we've
been
working
on
making
civvy
and
vac
talk
compatible
with
each
other,
although
that's
not
fully
done
yet
we're
still
making
some
progress
than
I
thought.
C
We
had
hoped
to
to
be
there
and
promote
backdrop
and
sippy
together,
but
I'm
afraid
that
that
not
happened.
We
do
not
have
the
the
time
available
to
actually
make
it
out
there.
So
if
you're
interested
in
the
sybian
backdrop,
we
still
love
savvy,
we
are
working
hard
to
make
it
compatible
and
if
your
rights
have
you
come
I
hope
that
you
spread
the
good
word
about
backdrop.