►
Description
Today’s development agenda: http://bit.ly/21lg9Nt
A
There
we
go
all
right:
it
is
a
Thursday,
March,
seventeenth,
happy
st.
Patrick's,
Day,
everyone
I
think,
that's
something
you
can
be
happy
about:
nobody's
wearing
green,
it's
a
price.
Anyway.
Everybody
forgot.
That's
all
right,
we're
all
on
the
internet.
We
aren't
gonna,
get
pinched,
it's
fine,
okay,
so
today
general
announcements
as
usual.
If
you
want
to
make
a
donation
to
backdrop
CMS
you
can
do
that
factor
of
CMS
org,
slash,
contribute
we
hand
out
a
fantastic
dragon
t-shirt
for
twenty
five
dollar
donation.
Everyone
should
have
gotten
your
dragon
t-shirt
since
last
week.
A
Yes,
no
maybe
yeah,
I'm,
good
and
hoodies
I
get
handed
out
for
a
fifty
dollar
donation
or
more
you're,
of
course,
always
welcome
to
contribute
code
or
documentation
or
feedback
on
any
of
our
issues.
It's
equally
appreciated.
You
guys
may
have
noticed
there
is
a
new
version
of
PHP
storm
out.
So
if
you
haven't
tried
it
yet
and
you're
itching
to
try
it,
we
have
free
licenses
available
for
contributed
developers
to
vector
of
CMS.
A
So
if
you're
a
member
of
the
contribute,
you
can
make
sure
that
membership
is
public
so
that
the
PHP
for
storm
folks
can
check
on
it
and
then
we
can
send
you
a
license
if
you're
on
a
member
of
the
contribute
and
so
on
a
license.
But
you'll
have
to
get
yourself
to
be
a
member
of
that
group.
First
they're
definitely
ways
you
can
do
that.
You
could
volunteer
to
co,
maintain
some
recently
imported
modules.
You
can
help
manage
issue
cues
on
things.
A
Alright,
updates
from
the
project
management
committee
last
week,
I
think
we
announced
that
we
added
a
new
member
two
weeks
ago
this
week
anyway,
we're
working
on
reviewing
two
new
applications
right
now
or
nominations
I
suppose
for
pnc
members.
So
we
should
have
some
more
updates
in
the
near
future:
Nate,
Mike
and
Wes.
A
A
We're
growing
our
management
structure,
which
will
help
backdrop
girl,
we're
hoping
and
then,
as
soon
as
we
get
our
pnc
nailed
down,
we'll
start
talking
about
adding
pork
committers,
but
we
figured
we
should
have
a
group
of
people
who
could
make
decisions
about
coroner's,
we're
going
to
start
adding
everyone
all.
So,
hopefully
we
get
this
all
organized
and
settled,
and
then
back
Jeff
well,
when
it'll
be
great
okay,
so
we
currently
have
several
constituents
that
we're
trying
to
get
represented.
A
C
Okay,
so
community
growth,
so
there
are
currently
231
total
projects
for
backdrop,
CMS
on
github
231
is
two
new
projects.
Since
last
week,
math
jacks
and
auto
log
out
modules,
which
are
exciting
new
projects
out
there.
We
also
have
two
new
contributors,
one
of
which
posted
that
mathjax
module,
welcome,
Roberts,
callous
and
auto
log
out
hang
on
there's
another
person-
oh,
that
was
Graham
anyway.
Two
new
contributors
I
feel
really
bad.
That
I
don't
know
who
they
are.
C
Let's
see,
there
are
153
total
projects
with
official
releases
on
backdrop,
CMS
org,
that's
one
new
project
that
has
a
its
first
release
on
backdrop:
CMS
org
since
last
week
there
are
two
hundred
and
seven
total
releases
of
all
of
those
projects.
Three
new
releases
since
last
week
and
115
total
user
accounts
on
backdrop,
CMS
torg,
only
three
user
account
since
last
meeting.
C
Ok,
that's
it
for
growth.
We
go
right
into
infrastructure,
there's
a
lot
of
crazy
stuff
that
happened
this
week,
mostly
thanks
to
Gore,
and
when
we
get
down
there
course
here
so
he'll
be
able
to
give
an
update
on
our
github
automation
section.
But
first,
let's
see
usage
statistics
and
analytics.
We
finally
deployed
the
number-crunching
analytics
script
last
week
or
the
week
before,
so
we
actually
have
usage
information
on
backdrop
see
my
story
about
how
many
backdrop
sites
are
out
there.
C
We
know
there's
around
200
that
are
reporting
usage
right
now,
but
what
that
actually
means
we're,
not
totally
certain
about
that.
Yet
we
started
to
go
back
through
and
confirm
the
numbers
to
make
sure
Travis
isn't
getting
in
there
and
I
haven't
looked
at
the
numbers
since
last
week
to
see
if
we
suddenly
got
a
spike
because
of
pull
requests,
firing
usage
updates,
but
they
shouldn't
do
that
anymore.
We
should
have
fixed
that
so
we'll
be
posting
that
the
usage
total
is
publicly
here
in
the
near
future,
which
is
great.
C
Let's
see,
we
also
have
a
couple
of
issues
to
follow
up
on
that
we'd
like
to
make
it
so
the
update
module
starts
reporting
more
information
than
just
what
projects
are
being
installed.
There's
an
issue
in
the
backdrop
suemez
or
Q
issue
99
for
that
and
issue.
98
is
an
issue
just
that
we
want
to
add
some
theming
or
a
custom
module
2
back
to
up
CMS
torg.
C
Josh
for
backdrop,
dress
for
backdrop,
we
have
apparently
still
an
issue
in
the
main
issue:
queue
issue
47
for
getting
dress.
With
backdrop,
but
the
fundamentals
of
getting
dressed
working
with
backdrop
have
kind
of
been
there
in
place
for
a
long
time.
We
have
address
extension
now
that
lives
in
the
contribute
backdrop
contribs
/
brush
and
it's
an
extension.
You
drop
in
to
your
drush,
install
into
your
home
directory
and
it
makes
backdrop
identify
or
makes
drush
identify
backdrop
yeah.
It
might
be
kind
of
broken
right
now.
I
think
it's
actually.
C
It
actually
works
with
backdrop,
but
we're
still
having
that
funny
issue
where,
if
you
have
the
same
copy
of
drush
for
drupal,
7
and
backdrop,
dress
kind
of
ceases
to
work,
drupal
7,
which
is
funny
because
I
tried
to
reproduce
that
when
we
were
at
sand
camp
when
I
had
dragged
Anderson's
ear
but
I
couldn't
reproduce
it
at
the
time
and
I
thought
it
must
have
gotten
fixed.
But
then
I
went
back
home
and
of
course
it
started
happening
again.
A
This
has
been
a
bunch
of
time
last
week
trying
to
get
it
going
again
and
I
think
Josh
8
board
rush.
Josh's
master
branch
has
diverge
significantly
from
Josh
8,
and
so,
if
you're
trying
to
run
the
backdrop,
extensions
on
Josh
master,
it
does
not
work
anymore,
and
so
you
have
to
go
find
like
the
tip
of
the
dress,
aight
branch
to.
D
A
With
and
so
it's
a
little
a
little
tricky,
and
so
I
tried
to
update
the
documentation
last
week
to
mention
that,
but
then,
even
on
the
tip
of
the
trust
branch,
there's
some
stuff
that
was
working
before
it
isn't
working
anymore,
like
the
chron
command,
which
is
what
we
were
telling
people
to
use
to
try
and
test
and
see.
If
josh
worked,
that
doesn't
work
and
then
the
judge
status
command
also
doesn't
work
right
now,
because
it's
not
allowed
for
backdrop
to
run
Josh
status.
C
What
happened
and
Greg
gave
us
a
heads
up
on
this-
is
that
they
forked
drush
for
drush,
nine,
actually
master
stayed
as
master
turned
into
drush
nine,
any
Forks
Ford
rush,
eight.
So
now
you
have
to
be
on
the
eight
point.
0
point:
X
branch
instead
of
master,
but
it's
actually
it's
those
the
same
code.
It
just
changed
branches
as.
E
C
C
Let's
see
next
item
on
the
agenda
here
is
Oh
github,
automation,
great
and
there's
been
a
lot
of
great
work
that
Gore's
been
doing.
He
posted
a
bunch
of
custom
modules
into
a
new
repository
in
the
backdrop
ops
group
and
it
looks
like
they
are
very
promising
and
it
solves
a
number
of
the
github
automation
issues.
I
wanted
to
put
it
in
the
agenda,
but
I'll
fill
those
out
as
as
we
go
along
in
this
meeting
gorg.
Do
you
want
to
give
an
update
on
what's
approach
you've
taken
and
how
that's
coming
along?
D
D
So
the
girl,
automation,
very
cool
stuff
that
I
really
want
to
tell
is
that
because
I'm
doing
some
project
for
myself,
it's
automation,
process,
continuous
integration
and
blah
blah
blah
I
was
able
to
hook
up
basically
with
a
custom
module,
my
own
for
called
backdrop
to
automatically
create
a
branch
ocean
and
also
a
PR
version
of
whatever
code
right
now
in
a
branch
in
a
in
my
for
and
how
it
works
like
I,
created
website
in
some
way.
I
just
don't
remember
a
link
right
now,
so
how
it
works.
D
It
works
via
web
hooks
for
a
branch
for
repository
and
when
somebody
push
pull
request
or
apply
commit
to
the
branch.
This
code,
flying
on
the
server
and
automatically
update
website
and
for
the
last
few
days,
I
was
working
in
even
more
exciting
part
is
that
we
can
apply
the
same
to
every
country
project.
So
as
soon
as
like,
we
enable
this
feature
for
specific
country,
a
country
project
we
automatically
have
sort
of
a
sandbox
with
the
same
features.
If
somebody
sent
the
pull
request
to
backdrop
country
repository,
we
have
a
website
called
wake.
D
For
example,
Pierre
7,
whatever
name
is
it
q,
a
bad
drug
CMS,
the
torque
and
the
owner
of
the
project
can
actually
go
and
check
out
looks
like,
and
also
the
guy
who
sent
a
pull
request
can
see
how
it
looks
like
as
well.
So
it's
kind
of
might
automated
process
of
checking
stuff,
but
it's
a
general
information
how
it
works
like
and
I'm,
not
sure
that
I'm
representing
it
properly
like
that
it
makes
clear
for
you.
C
Yeah
some
things
that
I
saw
were
included
so
github
auto.
He
has
the
repository
right
now.
May
it
contains
a
suite
of
modules
that
provide
the
basic
integration
and
it
looks
really
good
from
a
from
a
starting
standpoint.
Jen
and
I
were
discussing
beforehand
what
we
should
do
with
these
modules.
Obviously
you
had
it
set
up
so
that
it
would
be.
C
We
could
throw
this
in
a
standalone,
a
backdrop
website,
but
from
the
perspective
of
maintenance,
we
were
considering
putting
it
on
backdrop:
CMS
org,
with
our
other
custom
modules,
just
to
make
it
so
that
we
had
fewer
backdrop
websites
that
we
needed
to
maintain
every
time
a
new
version
came
out
possible
I
mean
they
they're,
so
independent
right
now
they
could
run
on
their
own
install,
but
for
the
sake
of
maintenance,
we
might
put
them
on
backdrop,
CMS
org,
just
to
deal
with
all
of
the
github
integration.
All
in
the
same
place.
We.
A
Also
might
have
future
github
integration
tests
that
require
information
from
my
crop,
CM
esta
or
like.
If
we
wanted
to
check
your
github
user
account
and
grant
you
access
to
a
project
that
you
are
a
maintainer
for,
we
would
need
the
user
role.
Information
from
backdrop
see
mr.
Orrick,
as
well
as
the
information
from
github.
So
even
though
that's
not
included
in
anything
we're
doing
now,
we
thought
long
term.
Happy
now,
on
the
same
place,
might
make
more
sense
that
we
could
do
a
tighter
integration
between
get
heaven
and
back
trip.
See
mr.
D
Doesn't
sounds
like
a
problem
to
me:
I
actually
can
provide
a
where
you
tell
with
how
to,
and
you
can
actually
install
these
modules
and
enable
cook
them
up,
and
they
will
start
to
work.
One
thing
that
I
did:
if
you
go
to
this
repository,
you
know
seasons,
it's
actually
hook
it
up
to
automatic
deployment.
D
So
literally,
any
updates
to
master
to
these
modules
will
fly
out
on
this
automatic
website
and
automatically
will
be
available.
Features
will
be
able
available
and
working
on,
so
this
one
part
is,
can
be
discuss
about
how
it
can
implement
it
into
bankruptcy.
Ms,
the
tour,
because
I
am
sure
that
these
fissures
that
you
said
like
hooking
up
users
in
etc.
It's
all
need
to
be
implemented.
So
what
of
course,
anna
code?
C
But
anyway
it's
looking
really
cool
some
of
the
features
that
are
implemented
so
far,
the
automatic
associating
between
pull
requests
and
issues
that
which
was
backdrop
CMS
org
issue,
number
four
is
implemented
automatic,
sandbox
creation.
That
is
very
cool.
I
also
like
the
way
that
that's
implemented.
C
But
we
have
the
control
of
responding
to
the
github
web
hook
and
then
posting
back
to
the
repository
or
pull
request,
saying
where
the
sandbox
lives
I,
like
the
way
that
that's
separated,
where
the
the
servers
are
not
our
responsibility,
but
the
integration
with
github
will
be
supposedly
residing
on
our
servers.
Is
that
sound
all?
Well.
D
Almost
will
clarify
it
with
the.
We
have
actually
two
integrations
if
we
take
a
simple
integration
for
issues
when
somebody
%
pull
request-
and
we
check
a
number
dash
number-
and
we
automatically
add
comment
on
this-
pull
request
that
it's
related
to
this
issue.
It's
complete
it's
completely
inside
of
these
modules,
yo
you
hook
up
this
one
directly
to
github.
We
are
their
pork
and
you
receive
this
information
about
the
issue.
You
do
some
stuff
and
you
put
a
comment
on
pull
request
which
is
linked
it
together.
D
It
works
a
little
bit
different,
so
we
are
hooking
up
my
project,
little
seed
to
the
country,
repository
or
two
backdrop,
CMS
backdrop
/
backdrop
repository
and
when
somebody
pull
request
or
push
code
with
who
going
to
get
OC
project
but
just
sent
him
over,
there
is
a
push
request
or
there
is
a
pull
request,
create
a
sandbox
for
it
and
then
get
all
seek,
connect
to
buddy
backdrop,
CMS
the
torque.
If
we
all
set
up
it
there
and
ask
okay
what
is
domain
name?
D
Where
is
data
base?
Where
is
user
for
the
to
base?
What's
the
folder
to
put
god?
Where
should
they
deploy
it
back
door?
Cmas
answer
back,
we
get
OC
web
hook.
Okay,
you
hope
you
have
to
go
there
and
create
it
over
there
and
then
get
all
say:
okay,
Garrett
you
connect
via
sage
by
public
key
to
the
server
and
okay.
This
directory
I
put
code
here
this
database
name
so
I
start
install
script
with
these
credentials
and
I
put
result
in
to
deploy
look
gotcha,
okay,.
C
So
this
isn't
actually
quite
I,
see
so
there's
a
couple
more
services
in
here
then
then
it
may
seem
at
first
that
get
LC
is
actually
the
one
that
is
prompting
backdrop
CMS
org
or
wherever
this
module
lives
for
how
to
setup
the
server
yea
rather
than
this
module,
prompting
whatever
server
it
is,
it
doesn't
initiate
it.
It
responds
to
get
LC
having
already
created
a
server,
and
then
it
just
does
this
setup.
D
Yeah,
there
is
one
small
step
that
I
forgot
to
mention,
so
if
you
went
to
through
the
code
and
sorry
guys
that
it's
getting
a
little
bit
too
long,
there
is
a
mod
module,
co-heir,
PAP,
I
and
so
modular
pap.
Actually,
this
module
is
creating
on
my
server
at
the
main
name,
a
database
and
a
user
for
the
two
base
and
then
send
this
information
to
get
Oh
Sees
use
this
information
to
create
to
put
all
this
cotton
database
over
there.
C
D
Actually
awake
if
we
could
learn
five
everything
we
have
backdrop
CMS
the
torque
that
is
responsible
to
giving
information
where
to
put
everything
for
sent
box
and
responsible
to
connect
to
send
box
server
and
create
domain
name
database
and
user
database
over
there
before
God
get
deployed.
And
then
we
have
a
Gitto
sees
that
actually
doing
deploy
when
entra
structure
is
already
created
by
our
peopie
module.
D
C
Wow
alright,
so
we
got
a
couple
of
things
going
on.
Oh
that
really
clarify
some
things,
though
sorry
everybody
that
might
not
find
that
interesting,
but
I
think
that
it
I
mean
it's
really
fascinating
and
it
looks
like
it's
all
to
think
about
that
a
little
bit
more
since
I'm
just
getting
familiar
with
it,
but
it
sounds
overall
like
it,
it
sounds
like
it's
a
work
ball
and.
B
D
Sure,
like
it's,
it
looks
similar
like
Travis
does.
It
is
then
start
virtual
server
for
you
and
then
run
tests
over
there,
but
the
difference
is
that
we
don't
really
start
virtual
server.
Every
time
we
have
a
shot
hosting
server
is
ready
to
do
everything
and
everything
is
already
see
top,
so
it
just
tell
server
okay
and
need
the
this
website
created
the
debates,
create
a
user
and
then
we'll
pass
it
back
to
get
OC
to
use
it
to
deploy
sandbox.
C
Yeah,
pretty
cool
so
the
way
that
works
right
now
correction,
I
reposted
a
proof
of
concept
that
has
it
all
set
up
on
his
servers
that
he
filed
a
poll
request
against
one
of
his
own
sandbox
projects
where
all
the
web
hooks
already
set
up,
and
you
can
see
the
PO
request
being
made
and
then
a
server
spun
up
that
contains
that
pull
request,
and
then
you
can
go
in
and
browse
it.
So
the
idea,
basically,
is
every
time
a
pull
request
is
filed.
There
would
always
be
a
sandbox.
C
C
You
know
if
we
had
a
lot
of
pull
requests
and
really
overall,
like
he's
got
a
good
point
that
right
now,
we've
only
got
like
70
80,
open
poll
requests
like
having
seven
seventy
or
eighty
open
sand
boxes
in
any
given
time
would
be
a
piece
of
cake
because
it's
not
actually
putting
strain
on
the
server.
If
they're,
just
websites
that
are
sitting
out
there,
I
think
if
we
probably
put
some
kind
of
like
HTTP,
authentication
and
front
of
things
to
keep,
you
know
bots
and
browsers
out
of
it
or
crawlers
out
of
it.
C
D
C
Well,
anyway,
it's
all
looking
very
sweet.
It's
awesome
to
see
that
coming
along
I'll
try
to
figure
out
how
to
work
together
to
get
those
modules
kind
of
into
the
backdrop,
CMS
dot,
org
ecosystem
in
a
way,
that's
like
lines
up
with
the
current
approaches
that
we're
doing,
because,
right
now,
it's
just
made
to
just
hang
out
on
its
own
server,
which
I
think
was
a
good
start.
But
let's
work
on
integrating
that
into
the
backdrop
CMS
org
repository
and
then
we
get
that
pushed
out
to
production.
C
A
Alright,
so,
as
you
all
know,
you
can
log
into
backdrop
CMS
to
org.
Now
there
are
several
things
that
you
can
do
there.
As
of
today
you
can
create
a
testimonial.
You
can
post
an
event
and
that
you're
going
to
are
seeking
a
tour
want
to
hear
more
about
backdrop
at,
and
you
can
fill
out
your
user
profile.
We
also
are
making
it
or
in
the
near
future,
going
to
make
it
so
that
you
can
add
a
showcase
of
a
site
that
you've
built
on
backdrop
or
list
a
company.
A
You
are
responsible
for
in
the
service
provider
listing
those
are
currently
underway
and
we
want
to
make
it
so
that
you
can
have
single
sign-on
with
github,
so
that
if
you
are
already
a
github
user
and
do
not
have
a
backdrop
account,
you
can
just
kind
of
log
in
rather
than
needing
to
go
through
the
process
of
creating
an
account.
But
we
could
use
a
volunteer
for
that
task.
If
anybody
loves
writing
single
sign-on
solutions,
there's
one
here
waiting
for
to
be
written
and
Jeff
I
know
I.
A
Think
you
looked
at
what
was
available
in
Drupal
in
there
didn't
seem
to
already
be
a
triple
solution
for
single
sign-on
with
github,
but
there
are
a
couple
of
things
that
might
be
useful
to
look
at
if
anybody
wants.
So
in
terms
of
the
showcase
we
went
through
and
made
a
list
of
the
information
we
want
to
collect
about
each
website.
A
A
For
the
service
provider
contractor
listing
will
probably
just
set
up
a
content
type
for
a
service
provider
that
you
can
fill
out.
That's
really
similar
to
what's
on
drupal.org
now
and
then
we'll
just
list
those
on
a
specific
page,
so
that
people
can
find
them
and
then
we're
going
to
put
all
the
people
that
are
currently
signed
up
as
supporters.
So
backdrop
in
the
footer
on
that
page,
at
least
in
the
meantime
before
we
have
companies
that
have
filled
up
their
profiles,
will
at
least
have
links
to
these
are
companies
that
support
us.
A
A
Now
that
we're
getting
more
information
from
github
like
the
pages
where
the
modules
can
be
found
in
the
issue,
queues
and
the
number
of
downloads
and
we'll
get
those
going
and
now
that
we
have
use
of
statistics
tracking
or
in
the
near
future,
uses
statistics
accurately
tracking
will
be
able
to
put
those
numbers
up
on
those
pages
as
well.
So
we'll
get
that
updated
soon,
so
people
can
have
an
easier
way
of
finding
modules
things
and
layouts
and
I
of
course
follows
right
in
with
the
project
browser
too.
A
So
that
should
all
tie
together
and
we've
got
a
couple
of
design
reviews
for
working
on
too.
We
have
this
new
news,
/
blog
section
that
we
just
kind
of
threw
up
and
we're
gonna
hit
that
we
put
on
the
website
we're
going
to
have
that
reviewed,
to
make
sure
that
same
line
with
our
design,
aesthetics
and
then
same
thing
with
the
upcoming
events.
Right
now.
A
It's
just
a
name
of
an
event,
a
date
of
groupon
and
a
link
to
where
you
can
find
more
information
about
that
event,
probably
and
add
some
stuff,
like
location
and
in
the
future,
maybe
even
put
up
maps
or
some
lady
who
can
filter
by
your
area
all
right.
So
in
the
news
and
announcements
section
neat
is
on
the
hook
for
writing
a
blog
tomorrow.
B
C
A
We
have
a
couple
of
other
people
that
have
expressed
interest
in
writing:
blog
posts,
I,
don't
know
Mike.
If
you
have
had
any
time
to
work
on
your
config
management
post
and
specifically
for
Pantheon,
they
they
keep
their
files
directory
in
a
different
place
than
where
you
would
ideally
like
to
store
your
config
and
so
Mike's
come
up
with
a
clever
solution
on
how
to
manage
your
config
files
in
the
pantheon
environment.
He's
gonna
write
a
post
about
that,
and
Doug
van
is
not
here
today
either.
A
He
had
also
mentioned
writing
up
a
post
on
Cal
box.
I'd
also
reached
up
to
the
guys
at
Cal
box
to
see
if
they
wanted
to
contribute
to
that
post
as
well.
I
thought
that
would
be
interesting
collaboration
and
then
we
are
going
to
be
attending
Civic
on
in
then
of
May
early
June
this
year.
So
I
thought
it
would
be
good
to
write
a
post
on
better
than
CBC
I'm
working
together,
but
I
haven't
made
any
progress
on
that
ether.
A
So
if
anyone
has
anything,
they
think
might
be
fun
and
interesting
and
wants
to
throw
up
a
quick
blog
post
for
tomorrow.
We
could
definitely
do
that.
I
know
a
couple
weeks
ago
we
mentioned
since
we
don't
have
a
showcase
up.
It
might
be
good
to
just
do
a
here's,
a
link
to
add
you
know
12
sites
that
are
currently
running
backdrop
kind
of
blog
posts.
Like
look
these
these
backdrop,
sides
are
in
the
wild
and
I
think
in
the
issue.
Queue
a
bunch
of
people
have
posted
links
to
sites
that
they
made.
A
It
goes
in
the
h,
eq,
it's
not
this
issue,
so
that
might
be
something
really
quick
and
easy
that
I
can
throw
together
for
tomorrow,
a
large
breasts.
So
if
anyone
has
anything
new
name
new
websites,
they
want
in
there.
Thank
you
Oh
thinking
about
it
and
throws
stuff
tomorrow
too
so
that'll
buy
you
another
two
weeks,
Nate
for
your
benchmarking,
blog
post.
A
Other
things
we're
working
on
we've
got
newsletter
that
needs
to
go
out.
Last
week.
I
said
I
would
write
a
newsletter.
I
created
a
google
doc,
but
I
didn't
get
very
far
and
actually
Thank
You
sweater,
yeah
I
grams
got
a
bunch
of
websites.
I
know,
Andy
I
think
you've
got
a
couple
to
well
we'll
definitely
throw
up
a
blog
post
and
a
little
quick
dirty
one
with
a
couple
of
links
in
which
I
think
would
be
good
and
then
I
the
newsletter
needs
to
go
out
as
well.
A
I
would
love
it
if
somebody
could
review
that
I'll
whip
something
up
a
mailchimp
and
send
out
a
test,
but
there's
so
much
stuff.
That's
happened.
It's
kind
of
hard
for
me
to
figure
out
what
the
priorities
are.
I
mean
obviously
telling
people
at
one
point
three
is
out
and
it's
got
easier
experience,
improvements
and
new
features
and
stuff
is
good.
But
what
else
like
the
book?
We
should
talk
about,
there's
a
book
we
should
talk
about,
but
all
the
stuff
you
can
do
on
the
website.
I
mean
I,
don't
know
so.
A
There's
a
little
long
list,
I'll
call
plus
some
stuff
together
and
send
out
a
test,
I
guess
if
anyone
wants
to
help
me
review
that
and
decide
what
to
be
in
there.
That
would
be
great,
let
me
know,
and
then
all
right
next
on
the
list,
a
backdrop
CMS
itself.
So
one
point
three
point:
three:
it
was
the
latest
version
that
came
out
febuary
24th.
One
point
three
point:
four
is.
B
A
Coming
soon
we
found
a
couple
of
a
key
and
issues
that
need
to
get
resolved,
so
we've
got
a
bug
in
views
and
a
bug
in
layouts
that
we
want
to
get
fixed
in
as
soon
as
those
are
done,
we'll
release
them.
I,
don't
know
if
there's
been
any
progress
that
the
problem
with
layouts
was
and
that
sometimes
your
blog
positioning
gets
forgotten
somehow
and
then
blocks
disappear.
So
we
wanted
to
fix
that
one.
A
It
was
kind
of
hairy
and
then
the
views
one
is
just
we
when
we
changed
all
of
the
names
from
edit
to
configure
one
of
the
links
to
edit
the
name
or
description
of
your
view
got
broken.
So
now
people
can't
change
the
name,
search
descriptions
of
their
views.
The
paperwork
oh
but
I
think
there's
a
whole
Krista
easy
one.
It's
just
kind
of
oops.
What
should
fix
it,
so
those
two
I
think
are
important
that
the
layouts
one
is
definitely
a
bigger
deal.
It's
also
much
harder
to
fix.
A
So
there's
a
tag
here
for
134.
If
you
want
to
see
what's
going
to
come
up
in
that
release,
and
then
1.4
is
our
next
minor
release
is
scheduled
for
May
fifteenth
and
we
have
a
lot
of
hard
things
to
get
done.
For
that.
We've
got
a
lot
of
little
bug
fixes
for
the
rich
text.
Editor
we've
got
a
new
rewrite
for
the
references
module,
a
new
redirect
module
a
front.
End
theme
that
Wes
has
been
working
really
hard
on
in
a
new
set
of
coorg
layouts
Mike.
E
B
Yeah
we've
been
spending
most
of
my
time,
cursing
making
Mike
for
forcing
me
to
rewrite
it.
Good
yeah
that
has
more
heads
tapi
integration,
that
I
thought
in
terms
of
the
way
it
loads
for
your
ex
and
stuff.
So
so
I
just
have
to
go
down.
If
you
rabbit
holes
to
do
a
me
right
to
make
that
an
object
rather
than
an
entity.
A
Okay,
well,
I'm
really
happy
that
both
of
you
guys
are
working
on
that
and
even
if
you're
not
doing
it
right
now.
So
thank
you.
New
friend
theme
I
think
we
got
a
demo,
maybe
two
weeks
ago,
from
Wes
on
what
that
looks
like
he's
currently
using
it
on
a
backdrop
project
and
trying
to
get
some
experience
of
how
it
works
as
a
base
theme,
so
that
we
can
you.
A
We
want
to
use
the
bootstrap
grid
system
and
I
think
so
far
everyone
is
leaning
towards
yes,
just
because
people
will
be
familiar
with
it,
but
then
also
once
we
have,
that
decided,
we
need
to
figure
out
how
to
actually
integrate
that
into
me
in
a
way
to
make
sense
before
so
that's
kind
of.
What's
on
our
plate
for
getting
those
layouts
done
too,
we
do
have
an
awful
lot
on
our
list
for
14,
so
we've
also
carried
over
a
handful
of
issues
that
were
scheduled
for
13
that
didn't
get
done
in
time.
A
So
if
you
want
to
check
what's
on
our
to-do
list,
there
is
milestone
for
1.4
in
the
give
issue
queue.
Some
of
them
are
quick
and
easy.
Some
of
them
are
really
difficult,
but
we
there's
a
lot
on
on
the
plate.
So
if
anyone
who
wants
to
help
there's
a
lot
of
squeaky,
you
subway
in
particular,
there
are
a
couple
of
user
experience
and
workman
tasks
that
are
a
bit
hairy.
A
We
wanted
to
include
the
project
browser
in
fourth
something
I
mentioned
earlier:
it'll
allow
anyone
who
has
a
backdrop
site
to
install,
find
and
install
new
modules
things
and
Leon's
directly
from
their
existing
backdrop
site
without
needing
to
visit
backdrop
seamless
to
order
to
search
for
modules
clean,
sir
layouts.
That's
something
that
I
think
we
got
super
close
on
last
time.
I
would
love
to
see
that
get
in
it's
going
to
be
a
huge
user
experience.
Improvement
for
people
who
are
new
to
back
up
in
the
future
I
work
a
lot
more
like
WordPress.
A
It's
been
really
successful
in
WordPress,
so
I'm
looking
forward
to
getting
that
done,
and
then
the
new
field
UI,
is
also
a
huge
chunk
of
work
field.
You
I
has
been
less
than
ideal
since
Drupal
6,
that's
been
a
good
chunk.
The
years
that
we've
known
it
hasn't
been
great
trying
to
get
a
rethink
that
problem
and
design
something
that's
more
intuitive
people
is
super
tough.
We've
got
a
bunch
of
great
mock-ups
from
West
in
that
issue.
It's
issue
779.
A
If
anyone
wants
to
work
on
that,
it's
also
a
good,
a
good
place
where
we
could
make
it
a
big
amount
of
significant
improvement,
in
fact,
travel.
If
you
get
that
sorted
as
fun
all
user
experience
issues
are
always
welcome
for
backdrop
and
we
are
indicating
those
by
putting
UX
in
the
tag
or
in
square
brackets
and
then
in
the
title
of
that
issue.
So
if
you're
specifically
interested
in
user
experience
or
want
to
help
fix
user
experience,
you
can
either
create
issues
or
work
on
issues
with
that
tag.
A
The
same
is
true
for
developer
experience
issues
since
we're
trying
to
make
backdrop,
software
that
is
accessible
to
anyone.
If
you
find
something
funky
about
how
the
code
works,
create
an
issue
and
type
of
DX
and
again
depending
on
the
scope
of
that
change,
we're
going
to
try
and
get
those
developer
experience,
improvements
and
anytime,
but
if
it
requires
an
API
changeable
need
to
wait
until
backdrop
to
its
own
API
edition,
though
we
can
get
it
in
sooner
rather
than
later.
A
A
So
that's
all
we've
got
for
our
backdrop.
The
product
we
do
usually
have
friends
to
our
front
backdrop
every
Thursday,
so
you
can
hang
out
either
in
the
github
issue,
queue
which
is
where
we
are
all
almost
all
of
us.
Almost
all
the
time
we
have
a
git
er
channel
to
chat
in
which
is
pretty
good,
because
anyone
who
has
a
get
account
can
jump
right
in
and
chat
with
us
there.
He
also
have
an
IRC
channel
a
pound
backdrop
and
that's
super
handy,
because
most
Drupal
bulk
store
an
IRC.
A
So
if
you're
interested
in
what
is
going
on
in
the
war
world
of
drupal
and
backtrack,
we
now
have
an
event
calendar
at
backrub,
CMS
to
org,
slash
events,
and
if
you
go
there,
you
can
see
that
this
week
is
this
week
is
not
up
there
anyway.
This
weekend
is
a
mid
camp.
I,
don't
think
the
organization's
with
mid
camp
ever
got
back
to
me
about
putting
that
event
on
the
calendar,
but
big
campus
this
weekend
in
Chicago.
A
So
I
don't
know
if
Andy
you're
planning
on
darling
wes
is
there
I
know
I
think
we've
got
a
bunch
of
people
that
are
gonna,
be
there
this
week.
I
don't
know
if
there's
any
actual
talks
on
backdrop,
but
there
probably
will
be
talking
about
backdrop.
Even
though
they're
an
itty
isn't
anything
on
the
schedule
coming
up
soon.
Next
month,
April
7th
to
9th
is
triple
camp
Guadalajara
in
Mexico.
I
am
very
much
hoping
to
be
there.
A
I
love,
Mexico
and
the
folks
in
Mexico
seem
to
be
very
receptive
to
backdrop
they're
right
in
our
target
audience
so
I'm
hoping
that'll
work
and
then
civic
on
in
June
June.
Second
to
third
looks
like
now.
The
official
dates
in
Fort
Collins
Colorado,
so
that'll
be
a
good
one.
Twin
Cities
drupalcamp
anyone's
interested
in
going
that
one
in
Minneapolis
is
a
fantastic
camp.
I,
don't
know
if
we're
gonna
be
going
or
not,
but.
A
Be
good
if
somebody
were
to
go
and
talk
about
backdrop
there
so
I
know
they're
open
to
that
and
then
Drupal
corn
camp,
which
is
august
four
through
seven,
also
a
good
friendly
bunch
of
folks
there.
We
had
a
really
fantastic
spread,
they're
not
last
year
with
year
before
so
upcoming
events.
If
anyone
else
is
attending
anything
on
giving
a
talk
on
backdrop
or
not
a
talk
on
backdrop
feel
free
to
add
it
into
our
events,
listing
on
vector
to
nest
at
work,
and
we
would
ask
that
you,
please
don't
add
drupalcon.
A
Alright,
let's
see,
if
you
guys
are
interested
in
books
on
back
Jeff
there's
a
book
out
right
now
called
migrating
from
triple
the
backdrop
that
you
can
get
on
a
press
or
Amazon,
and
there
will
be
another
drop
book
coming
very
soon
from
beginning
project.
That's
all
for
the
agenda.
Does
anyone
have
anything
they'd
else,
I'd
like
to
talk
about
open,
Q&A.
A
A
So
speaking
of
most
of
the
talking,
if
anyone
is
like
super
passionate
about
part
of
this
meeting,
it
would
be
nice
to
not
have
to
do
this
justice
optical.
So,
if
you
guys
want
to
like
you
know
or
obviously
get
a
great
update
today
on
the
integration
part,
but
if
there's
anything
that
you're
like
I,
don't
really
you
know
I'm
not
really
involved
in
this
part
of
backdrop,
but
I
really
would
like
to
talk
about
in
the
meeting
that
is
just
as
good.
So
definitely
speak
out.
A
It's
good
to
have
more
people's
faces
on
the
video
to
somebody
mentioned
that
you
know.
There's
a
lot
of
us
in
the
community
and
like
we
should
all
share.
Whatever
is
the
way
the
video
works
is
it
takes
like
whoever
top
the
most
and
puts
their
photo
up,
so
other
people
will
be
good.
So
when
I,
oh,
no
I,
don't
know
whatever.
This
is
books,
hope
you
could
do
that
alright
guys.
Well,
thanks
all
for
joining
today,
we're
gonna
retreat
to
the
issue.