►
Description
Today’s development agenda: http://bit.ly/1OUR0lo
A
We
are
on
air,
it
is
Thursday
March
10th.
Thank
you
guys,
all
for
joining
we're
gonna.
Do
a
quick
development
task
check
in
today
a
couple
of
general
announcements.
First,
as
you
all
know,
if
you
donate
to
backdrop,
we
will
mail
out
a
t-shirt
or
hoodie
as
a
thank-you
gift
for
your
donation,
for
to
my
five
dollars
to
get
a
shirt
for
a
50
go
to
hoodie
Wes
wine,
honey
I
have
some
stuff
that
I
need
to
mail
out.
A
Apologies,
it's
right,
not
getting
it
out
yet
I'll
go
today,
I'm
meeting
a
promise,
so
we
will
slowly
mail,
you
t-shirts
and
any
storage
occasions.
We
also
have
free
phpstorm
licenses,
which
we
can
get
you
right
away.
If
you
are
a
member
of
a
backdrop,
contribute
if
you
want
a
phpstorm
license
and
you're,
not
yet
a
member
of
the
kinship
group,
we
can't
give
one
to
you
because
phpstorm
needs
in
a
way
to
know
that
that
you're
allowed
to
have
one.
A
So
you
have
to
be
in
that
group
if
you've
contributed
a
module
theme
or
layout.
You
can
end
up
in
that
group.
Also,
if
you're
just
interested
in
helping
us
maintain
documentation
or
help
manage
the
issue
queue,
we
are
working
on
right
now,
in
addition
to
the
contributed
agreement
that
will
make
it
easier
for
non
coders
to
join
that
group
as
well
we're
at
least
clear
or
what
is
required.
So
that's
coming
soon
and
then
more
exciting
updates,
guys
we
have
an
OPM,
see
member.
A
We
added
Wes
to
be
our
like
runnin,
the
Constituent
guy,
to
make
sure
we're
not
doing
anything
crazy
and
backdrop.
That's
going
to
upset
the
HTML
CSS
JavaScript
ninjas
of
the
world.
So
that's
really
exciting.
We're
currently
in
the
process
of
growing
our
management
structures,
both
the
project
management
committee
and
then
followed
by
core
committers
to
try
and
make
sure
that
we
can
handle
the
massive
odds
lot
of
people
that
are
going
to
be
showing
up
in
to
backtrack
community
over
the
days
to
get
here
so
yeah
congrats.
A
Would
you
have
a
couple
of
other
constituents
we're
currently
looking
at
reviewing
we're
hoping
to
get
a
non
coder
site
builder
type
up
just
to
help
us
figure
out
user
interface
things
and
and
what
the
non-voters
like
we're?
Also
looking
for
somebody
who's
really
super
familiar
with
Kim
tricks,
so
somebody
who
is
may
be
ported
or
written
a
lot
of
modules
would
be
a
great
person
for
that.
A
It
don't
have
to
be
back
chef
company,
Drupal
company,
WordPress
company,
just
oh,
whatever
is
good
and
we've
got
a
couple
people
in
mind
for
some
of
these
positions,
but
we
are
always
interested
in
people
who
are
looking
for
ways
to
contribute
and
maybe
haven't
felt
away
yet
who
might
have
good
visions
for
the
future
of
backdrop
as
well
and
so
get
involved,
and
we
are
happy
to
have
a
growing
management
structure
for
me
on
Nate
speaking
of
growing.
Let's
turn
it
over
and
talk
about
how
our
community's
been
growing.
C
Sure
thing
yeah
I,
want
to
add
that
I'm
super
excited
about
adding
new
members.
I'm
really
also
excited,
like
we've
been
growing
pmc
first,
but
adding
more
committers.
The
committee
committee
list
ultimately
should
be
larger
than
the
PMC
and
so
that'll
be
really
exciting
to
start
working
on
expanding
that
in
coming
months
as
well.
Ok,
anyway,
community
growth,
lots
of
things
happen
this
past
week
on
the,
in
the
backdrop,
contribute
on
github.
C
There
are
49
total
backdrop
contribs.
We
have
one
new
member
this
past
week,
welcome
sentai
digital
to
the
contribute.
We're
really
excited
to
have
you.
We
also
have
to
open
applications
that
are
currently
in
the
midst
of
being
processed,
one
of
whom
eric
is
is
actually
here,
we're
working
on
it,
but
it's
so
great
to
see
new
contributors
coming
in
from
all
different
stripes
and
helping
to
make
backdrop
a
more
robust
platform.
C
Let's
see
on
backdrop
semester
org,
we
have
under
12
total
user
accounts.
Only
two
new
people
have
signed
up
since
last
week,
probably
because
right
now,
there's
not
a
lot
of
motivation
to
create
accounts
on
backdrop
CMS
org,
but
as
we
work
to
expand
the
integration
between
github
and
back
top
CMS
org
they'll
be
more
reasons
for
people
to
have
user
accounts.
C
We've
got
a
section
down
here
for
github
automation,
well,
I'll
jump
into
a
little
preview.
That's
we
currently
have
an
issue
with
the
way
that
we
manage,
contribute
or
ease
that
right
now
everybody
has
commit
access
to
every
repository
and
we're
considering
shifting
that
around
a
little
bit
to
make
it
so
that
you
only
have
commit
access
to
the
ones
that
you
actually
are
maintained
errs
for,
rather
than
this
whole
batch
thing.
C
C
C
The
one
item
that's
been
on
a
list
for
ages.
Now
one
of
the
items
is
a
usage
statistics,
usage
statistics.
We
finally
have
crunching
and
calculating
on
backdrop
CMS
org,
which
is
very
exciting.
However,
it's
not
yet
public,
so
I
have
a
URL
here
in
the
agenda.
That
is
the
like
the
usage
statistics
for
backdrop
itself,
but
I
doubt
anybody
can
actually
look
at
it
unless
they're
an
administrator
on
the
site.
That
might
be
a
couple
people
in
this
meeting,
but
you
probably
will
mostly
get
access
denied
as
a
preview.
C
We
we
know
there
are
two
hundred
roughly
backdrop,
websites
that
are
reporting
usage
from
before
we
ran
the
number-crunching
script
after
we
removed
all
the
tests
spots
and
everything
like
that.
We
know
that
there's
been
roughly
1200
websites
that
have
actually
checked
in
I
have
a
feeling
like
because
sites
are
only
calculated
if
they're
checking
in
on
a
weekly
basis.
C
So
if
you've
got
a
site
that
doesn't
have
cron
set
up
and
doesn't
have
visitors
or
you
have
local
host
websites,
that's
how
we
have
such
a
huge
discrepancy
between
like
sites
that
have
been
installed,
total
and
sites
that
are
currently
active.
So
any
what
kind
of
interesting
it
is
nice
that
we
did
finally
get
travis's
numbers
out
of
there
and
we've
updated
core
to
make
it
so
that
pull
requests
that
trigger
tests.
C
Don't
report
as
active
installs,
which
has
been
kind
of
a
big
hole
up
there,
that
we
had
hundreds
of
additional
sites
that
weren't
actually
real,
actually
Travis.
It
turned
out,
as
in
total,
reported
over
16,000
backdrop
installs,
because
we
run
a
lot
of
tests,
so
that's
great
for
our
testing,
but
is
was
highly
skewing.
All
of
our
numbers,
I
know.
A
A
I
know
people
are
probably
going
to
compare
backdrops
numbers
to
drupal
numbers
and
then
it
looks
kind
of
sad
because
you're,
like
wow
drupal,
has
a
lot
more
sites
than
us
but
like.
If
you
compare
us
to
any
other
project
in,
like
the
first
two
years
of
existence.
Having
200
sites
like
actively
running
is
kind
of
a
huge
thing.
It's
like
a
really
that's
a
lot
more
than
I
was
expecting
like
I
was
like
well
I've
got
like
three
and
you've
got
three
and
so
we're
looking
at,
like
maybe
20
but
like
200.
A
That's
that's
big,
so
I
just
want
to
say
that
I
know
that
we're
used
to
seeing
drupal
numbers
and
these
numbers
might
seem
small
but
like
to
me.
It
looks
like
success.
So
I
just
want
to
thank
everybody
for
running
back
drop
sites
and
believing
in
this
thing
and
hopefully
having
some
fun
library.
C
Let's
say
another
item
on
here:
drush
for
backdrop:
we've
had
a
prototype
of
a
brush
extension
that
works
for
backdrop.
That
is
pretty
exciting.
It
actually
works,
but
we
still
have
some
pretty
serious
issues
with
it.
It's
in
the
backdrop,
contribute
and
ur
backdrop
contribs
/
brush.
If
you'd
like
to
take
a
look
at
it
and
help
work
on
it,
it's
ad
rush
extension,
so
you
throw
in
your
brush
directory
and
you're
in
your
home
folder,
and
that
makes
it
so
that's
drush
basically
can
recognize
backdrop
and
work
with
backdrop.
C
C
That
means
that
it's
possible
for
us
to
start,
including
drush
in
our
upstream
for
pantheon,
like
a
copy
of
drush
and
the
drudge
extension
for
backdrop,
and
that
in
theory,
that
would
make
it
so
that's
pantheon
would
use
our
copy
of
dress
that
had
the
extension
already
loaded
in
it,
and
that
would
make
it
said
things
like
running,
update,
PHP
and
cron,
and
things
like
that
would
work
on
Pantheon,
which
would
be
great.
He.
C
D
C
That's
even
better
because
I
that
that
sounds
way
better
than
needing
a
whole
copy
of
drush,
because
I'd
prefer
the
dress
itself
for
updated
and
maintained
outside
of
us,
even
even
though
they'll
be
dude
in
doing
maintenance,
and
we
just
wouldn't
need
to
pull
it
in
I
like
it
a
lot
better.
That
way.
That's
great!
C
Let's
see,
we
don't
have
any
specific
items
that
we've
got
mentioned
here,
but
we
have
a
whole
section
in
the
agenda
for
github
automation,
there's
a
whole
slew
of
things
that
we
would
like
to
automate
in
between
our
processes.
Backdrop,
CMS,
org
and
github.
There's
a
tag
for
that.
In
the
backdrop,
CMS
org
issue
queue
just
labeled,
github
automation.
If
anyone's
interested
in
working
with
the
github
API,
we
could
really
use
some
help
there
and
we
can
get
you
access
to
backdrop.
C
C
A
We
currently
have
allowed
people
to
sign
in
to
the
website,
and
just
so
you
guys
all
know
what
you
can
do
there
normally
zur
should
be
able
to
create
a
testimonial.
A
They
should
be
able
to
list
an
event
in
the
on
the
news
page
there's
a
list
of
upcoming
events
that
are
backed
up
friendly
and
and
I
think
that
might
be
it,
but
in
the
near
future
we
kind
of
let
you
guys
add
organizations
that
will
be
listed
in
the
backdrop,
service
provider
section
and
add
showcases
of
websites
built
with
backtrack
in
the
far
future.
We're
also
probably
trying
to
figure
out
some
kind
of
jobs
listing.
A
You
know
list
yourself
for
hire
kind
of
service
like
github
has,
or
maybe
we'll
just
integrate
with
that
somehow
and
speaking
of
integrating
with
github.
We
also
want
to
do
some
kind
of
a
single
sign-on
solution
so
that,
if
you
already
have
a
github
account,
you
don't
have
a
backup
account.
People
don't
need
to
go
through
the
process
of
creating
a
separate
account.
I
can
kind
of
push
a
button.
A
It
will
sync
them
up
and
hopefully
that'll
end
us
end
up
letting
us
do
things
like
allow
people
to
edit
their
own
project
nodes
on
backdrop
CMS
to
org,
in
addition
to
the
projects
they
are
maintained,
errs
for
on
github
haven't
quite
figured
out
what's
necessary
for
that,
yet
we're
currently
just
pulling
in
everything
directly
so.
A
There's
other
things
like:
we
can
always
use
help
on
vector,
seamless
to
Oregon,
o
people
of
students.
Listen
to
this
meeting
later
and
they're
looking
for
ways
to
get
involved.
A
couple
of
things
we
could
use
help
with
right
now
is
the
modules
themes
and
layouts
and
search
pages
and
landing
pages
have
designs
that
have
not
been
completely
implemented,
and
a
lot
of
that
is
because
we're
missing
some
of
the
data
that
we
need
to
display.
On
the
pages
things
like
links
to
the
github
issue
queue
or
the
number
of
downloads,
all
information
that
exists.
A
We
just
don't
have
it
in
a
way
that
we
can
actually
display
it
usefully
on
the
page
and
so
there's
some
development
tasks.
There
there's
also
some
kind
of
friend,
ND
tasks
to
and
in
terms
of
taking
like
the
layout
for
the
find
a
theme
page
and
actually
implementing
it
right
now
we're
using
the
design
that
we
had
for
the
find
of
module
page
on
modules,
things
and
layouts
there.
A
We
need
to
figure
out
how
to
get
those
separated
and
then
the
layouts
page
is
also
going
to
eventually
need
its
own
design
too,
and
we're
struggling
with
this
issue
right
now.
We're
currently
our
projects,
I'd
love
to
have
one
screenshot
for
themes
and
for
layouts,
and
we
want
to
maybe
eventually
change
that
to
have
more
than
one.
So
we
just
need
to
figure
out
like
whatever
we
implement
now
in
the
future
will
will
gonna
have
to
change
it.
So
I'm
not
doing
a
bunch
of
extra
work.
A
We
know
we're
gonna
throw
away,
but
maybe
do
like
step
one
of
what
will
eventually
be
step
5.
So
if
anyone
wants
to
help
work
on
bankruptcy,
master
org,
we
would
love
help
with
those
things.
Also,
if
you
want
to
help
us
figure
out
what
we
want
to
put
into
our
showcase
section
like
what
information
we
should
be
collecting
for
people
about
sites
they're
building,
we
could
use
help
with
that,
and
also
what
information
we
should
be
collecting
about
service
providers.
A
Like
you
know,
I
looked
at
the
Drupal
organization,
page
there's
a
lot
of
information
there
collecting
I'm,
not
sure
we
need
all
of
it
at
least
now
cuz.
They
don't
have
that
many
organizations
yet,
but
I'm
also
not
sure
whether
that's
something
people
will
come
back
and
update
later.
So
maybe
we
should
collect
a
lot
of
information
that
I
so
definitely
a
lot
of
work.
We
could
use
help
with
on
our
website,
even
if
you
don't
feel
like.
Maybe
you
can
get
into
like
helping
on
job.
A
We
definitely
could
use
help
with
backdrops
EMS
network.
It's
a
great
place
to
get
started.
Render
news
announcements.
We
posted
a
review
of
sand
kept
in
sand.
The
sand
camp
drupalcamp
in
the
blog
last
week
was
just
kind
of
a
high-level
overview
of
our
full
day
training
class,
which
I
thought
was
pretty
exciting
and
I'll.
Thank
you
to
the
camp
organizers
and
upcoming
next,
which
is
not
this
week,
but
next
week
we
want
to
do
a
blog
on
benchmarks
for
a
Drupal,
7
vs.
backdrop.
I
know
knee
has
been
getting.
A
A
Okay.
So
if
you
want,
if
you
have
a
blog,
you
want
to
write.
If
you
post
an
issue
in
or
a
comment
on
issue
number
158,
we
will
add
it
to
the
schedule
and
the
sooner
you
have
it
ready.
We
could
kind
of
like
squeeze
it
in
at
any
time.
So
that
way,
if
one
of
our
other
blogs
ends
up
being
slowed
ohh,
we
can
use
something
else.
So
I
think
it's
just
really
important.
That
people
know
that.
A
We
have
a
to
do
to
send
a
newsletter
to
all
of
our
people.
Maybe
I'll
work
on
that
this
week,
since
I'm
not
writing
a
blog
post,
because
we
have
anything
sent
to
newsletter
yet
saying
the
backdrop
1.3
is
out
yet
one
point
three
point:
three:
we've
got
a
lot
of
stuff
cool
stuff
going
on
with
the
website.
If
that
a
lot
of
cool
stuff
going
on
in
the
next
version
fact
drop.
There's
a
lot
of
activity
and
excitement
in
the
air
and
I
think
everybody
should
be
notified.
A
So
I'll
try
and
get
a
draft
with
that
ready
to
go
today.
Maybe
we
can
get
that
out
for
the
next
cost.
I
don't
have
to
keep
saying
it's
not
done
yet
would
be
nice
and
then
also
speaking
of
marketing.
We
know
where
developers
not
particularly
good
at
marketing,
so
we've
created
an
issue
in
the
backdrop:
CMS
you're
not
an
issue
whole
tag
in
the
vector
of
CMS,
gorg,
q4
marketing
related
stuff,
and
maybe
that's
not
necessarily
the
right
place
for
that
issue,
but
it
is
the
place
we
had.
A
So
that's
where
all
those
issues
currently
are,
and
so,
if
you're
interested
in
marketing,
you
want
to
help
us
out
with
spreading
the
word
or
coming
up
with
ideas
about
what
we
should
be
doing.
The
spread.
The
word
go
ahead
and
check
out
the
audience
marketing
tagged
in
that
kyo
and
see
if
there's
things
were
missing
or
things
that
you
could
have
with
be
great.
Oh
right,
let's
talk
about
backdrop
itself,
sabacc.
A
One
point
three
point
three
came
out
a
couple
weeks
ago:
the
end
of
februari
and
it
included
all
of
the
changes
that
went
into
the
two
latest
versions
of
Drupal
7.
So
thank
you.
Everybody
who
worked
on
getting
those
poor
quests
at
merged
in
and
we
have
the
next
version
of
backup
1.3
point
for
upcoming.
We
know
we've
got
a
couple
of
bugs
that
we
think
may
be
our
urgent
enough,
that
we
should
roll
a
release
when
they
get
resolved,
and
so
you
can
check
out
the
issue
tracker
for
that.
A
C
There's
a
really
a
nasty
bug
that
that
we
found
that
if
you
set
a
certain
accept
header
like
Internet
Explorer
8
hook,
then
your
layout
loses
all
of
its
blocks.
And
if
that
could
saving
your
cash,
then
you
can
end
up
with
a
pretty
broken
website
so
that
the
134
will
probably
come
out
in
the
very
near
future,
like
sooner
rather
than
later.
Once
we
don't
have
a
fix
for
that.
Yet,
but
as
soon
as
we
do,
we'll
probably
make
a
new
release.
A
Okay
and
then
the
next
minor
version
of
backed
up
working
on
backed
up
1.4
has
a
bunch
of
things
queued
for
the
list
to
get
in.
There
are
a
bunch
of
little
tiny
buds
with
the
rich
text
editor
that
just
makes
the
user
experience
less
than
ideal
we'd
like
to
get
those
results.
We
would
like
a
new
version
of
the
references
module,
so
it'll
be
a
little
similar
to
a
little
bit
more
similar
to
entity
reference
from
Drupal
7,
but
we
didn't
really
like
the
code
style
and
any
reference.
A
It
wasn't
really
in
line
with
the
majority
of
backdrop
code
style,
so
we're
rewriting
it
to
be
a
little
bit
more
like
references
module
for
Drupal
7,
which
was
a
little
cleaner,
more
straightforward,
so
we're
going
to
try
and
get
that
reference
solution
into
backdrop.
1.4
we'd
also
like
to
get
a
redirect
solution.
We've
got
a
path
in
path
auto
in
core,
but
that
can
end
up
in
a
situation
where
we
sometimes
have
multiple
paths
so
the
same
piece
of
content.
A
It
would
be
much
nicer
if
they
could
just
redirect
so
we're
going
to
try
and
figure
out
how
to
get
some
global
redirect
action
in
the
maybe
some
of
redirect
module,
which
provides
a
UI
to
control
that
as
well,
more
importantly
or
maybe
more
excitingly.
We
also
like
to
get
a
new
front
and
theme
into
backdrop
1.4,
so
people
can
actually
ship
their
site
without
meaning
to
install
something
else
and
I
know.
Wes
has
been
doing
a
ton
of
work
on
the
new
friend
and
theme.
A
A
A
Okay,
we've
got
a
new
running
theme
underway.
I'm
super
excited
to
see
that
progress,
I,
really
love
the
way
it's
going
and
then
also
super
complicated,
but
very
exciting
is
trying
to
figure
out
how
to
get
a
new
set
of
front
end
or
not
fernand
all
over
layouts
in
core
and
so
right.
Now
back
to
ships
with
for
layouts,
you
get
one
column,
two
columns
on
the
right
to
cons
on
the
left
and
then
a
layout
that
matches
the
bartech
Regents
from
Drupal
7
and
that's
not
usually
sufficient
to
launch
a
comprehensive
website.
A
It's
pretty
good
to
launch
a
basic
website,
but
back
Jeff
wants
to
be
comprehensive
tool,
so
it'd
be
good
if
we
could
get
better
layouts
out
of
the
box
and
that
going
to
require
a
little
bit
thinking
in
terms
of
how
we
handle
an
upgrade
path
in
terms
of
how
our
grid
system
is
going
to
work.
Are
we
gonna
adopt
an
existing
one
or
ride
our
own
and
in
terms
of
how
classes
line
up
across
layouts
they're,
just
a
bunch
of
kind
of
careful
thinking?
A
We
need
to
do
to
make
sure
that
first
of
all,
sites
that
are
currently
running
aren't
going
to
break,
but
also
people
who
write
can't
rip
things
are
going
to
have
a
ton
of
work
to
do
to
support
all
of
the
new
for
layouts
as
well.
So
we
should
figure
out
how
to
get
that
result
and
hopefully
added
for
our
May
fifteenth
release.
Backdrop
looking
for
ok,
if
you
are
interested
in
everything,
that's
on
our
roadmap
for
a
backdrop
you
can
check
out
backdrops
IAM
org,
slash
roadmap.
A
We
also
have
milestones
for
some
of
our
releases
in
github,
so
there
is
a
milestone
for
1.4.
That
also
has
a
bunch
of
issues
that
have
rolled
over
from
1.3,
but
we'd
also
like
to
get
in
there
as
well.
At
any
time.
We
are
interested
in
fixing
both
user
experience,
issues
and
developer
experience
issues,
and
this
is
something
that
we
think
will
help
make
backdrop
backdrop
a
better
product.
So
if
there's
something
that's
bothering
you
about
the
user
interface
file,
an
issue,
we're
definitely
interested
in
resolving
those
or
if
you're,
writing
a
contributed
module.
A
So
if
you
have
a
issue
for
user
experience
or
developer
experience,
we
are
putting
square
brackets
an
issue
title
with
either
you
xor
DX.
So
if
you're
interested
in
working
on
this
issues,
you
can
also
search
the
queue
for
that
tag.
A
couple
of
super
exciting
things
that
we'd
also
like
to
get
done
in
the
near
future
relating
to
user
experience,
include
the
project
browser.
A
So
this
is
a
tool
that
will
let
you
browse
a
list
of
modules,
themes
or
layouts
directly
from
your
backdrop
site
and
it
got
a
whole
bunch
of
work,
I,
think
kind
of
in
the
middle
of
the
last
release
cycle
and
then
a
whole
bunch
of
work
at
the
very
end,
but
it
wasn't
quite
enough
to
get
it
in,
and
so
we
are
hoping
to
get
the
remaining
work
on
project
browser
done
early
in
this
cycle
so
that
we
can
get
it
into
1.4.
I.
Think
that's
going
to
be
huge.
A
C
I,
although
Andy's
here
here
in
the
meeting
is
mic,
isn't
on
but
I
know,
he'd
been
waiting
for
quite
a
while
to
get
the
project
browser
server
back
up.
We
had
a
little
bit
of
an
issue
where,
in
my
code,
review
for
the
corpo
request,
I
suggest
that
we
changed
the
query
strings
to
make
the
match
the
way
that
views
does
like
items
per
page
and
ordering
and
what
happened
was
a.
C
We
accidentally
deployed
the
change
the
backdrop
CMS
org,
but
not
to
the
contribu-
aid
it
so
that
they
were
talking
different
languages
essentially,
but
we've
now
updated
a
project,
module
project,
browser
server,
right,
wait,
project,
browser
server,
project,
browser
and
the
backdrop
semester,
org
project
browser-
all
of
them
t
is
the
new
API,
as
recommended
so
we're
unblocked
there
and
the
project
browser
server
is
now
back
up
and
running
correctly.
It's
also
really
exciting
because
we
got
the
usage
statistics
back
in
place.
C
You
can
now
sort
by
popular
projects
within
the
project,
browser
which
is
really
exciting
and
I
check
that
out
and
I
think
that
it's
working,
which
is
great
because
we
didn't
have
any
numbers
previously,
but
the
code
was
all
there
to
actually
utilize
the
numbers
and
now
that
the
numbers
are
there,
you
can
actually
sort
by
popular
projects,
which
is
great,
I,
tried
out
project
browser
server
as
well.
Now
our
project
browser
the.
A
That's
great,
thank
you
for
the
update,
so
the
other
thing
we're
working
on,
which
is
a
little
trick
steer,
is
trying
to
get
a
new
field.
You
I
the
field,
you
ice
and
something
that's
been
kind
of
a
pain
point
in
Drupal
development
since
triple
six,
let's
say
the
same:
altar:
Drupal
7,
it's
just
this
frustrating
in
backdrop
as
it
was
in
Drupal.
We
know
what
to
problem.
A
We
have
some
excellent
designs
that
West
worked
on
to
help
us
kind
of
improve
that
and
I
think
we
could
definitely
get
a
new
field
you
I
in
that
is
something
that
can
be
developed
as
a
separate
module
because
field
you
eyes,
is
suffered
module
before
so
we
could
build
something
entirely
new
in
contributed
in
at
some
point
in
the
disabled.
Oldfield.
Do
I
if
we
wanted
to,
but
I
would
love
to
see
that
for
backdrop,
1.4
not
sure
how
likely
to
see
it
done
by
then.
A
Okay,
let's
see,
let's
talk
about
sprints,
so
every
Thursday
we
usually
do
a
little
remote
sprint
and
where
we
all
hang
out
in
either
IRC
or
on
git
er
or
in
the
github
issue,
queue
or
sometimes
even
in
reddit,
and
talk
about
the
things
that
we're
working
on
in
backdrop.
We
can
get
help
from
each
other.
We
can
help
each
other
and
we
can
help
move
things
forward.
A
So
I'm
really
looking
forward
to
doing
that
today
and
if
you
have
some
time
from
your
company
to
volunteer
for
open
source
projects,
you
want
to
do
on
a
thursday
they'll
be
fantastic.
Of
course.
If
anyone
has
any
time
to
contribute
to
backdrop,
that's
not
on
a
Thursday.
That
is
also
greatly
take
evenings
weekends
and
holidays
w
out,
or
you
know
just
an
hour,
your
spine
as
well.
So
definitely
the
github
issue
queue
is
a
good
place
to
put
your
thoughts.
A
Even
if
there's
nobody
else
there,
someone
will
eventually
stumble
along
and
find
them.
Let's
see
if
you
are
interested
in
attending
an
event
where
you
can
talk
to
other
people
about
backdrop,
you
can
now
go
to
backdrops
CMS
to
forex.
Flashin
events
to
see
a
list
of
events
posted,
hopefully
by
the
event,
organizers
that
are
upcoming.
If
you
are
an
event
organizer
and
you
have
an
event
where
you
want
people
to
come
and
talk
about
backdrop,
it's
also
good
to
post
those
events
there
and
there
is
an
ical
feed
of
this
information.
A
If
you
want
to
subscribe
to
them,
it's
currently
hosted
on
Google
Calendar,
but
we
are
going
to
try
and
get
individual
event
information
available
on
our
website
to
engineer
future
so
go
ahead
and
check
that
out
shiny
new,
exciting
all
that
stuff.
And
if
you
want
books
on
backdrop,
there
is
currently
one
book
out
called
migrating
from
Drupal.
The
backdrop
that's
available
now
on
a
press
and
a
new
beginning
backdrop
book
will
be
out-
probably
second
quarter
this
year.
A
C
Updates
on
the
issues,
basically,
people
saying:
there's
things
happening
in
the
issue:
go
and
take
a
look
at
it.
Oh
there
was
actually
I
mean
you
brought
this
up
Jen,
but
there's
the
interesting
tool.
That's
out
there
for
having
user
agreements,
automated
yeah.
A
Erica
actually
found
that
sent
that
to
me
on
Gator
this
morning
on
it
only
works
for
individual
projects,
but
if
we're
going
to
end
up
moving
off
of
the
group
model
to
the
original
project
model
anyway,
that
might
be
okay.
I
filed
a
issue
asking
if
it
worked
for
groups
or
anyone
else
is
interested
in
making
it
work
for
groups.
But
that
might
be
a
good
starting
point
for
us,
regardless
of
which
direction
we
go.
Yeah.
C
B
C
Okay,
well,
everybody.
Thank
you
so
much
for
joining
a
great
meeting.
As
always,
and
we've
got
so
many
things
that
are
happening.
We
will
all
be
doing
our
normal
thursday
will
not
all
of
us,
but
a
lot
of
us
will
be
doing
our
Thursday
code
sprints.
You
can
meet
up
with
us
in
IRC
or
in
theater
and,
of
course,
github
issue.
Queue
is
where
we
will
be
conversing
back
and
forth.
So
I
hope
to
see
all
of
you
guys
on
the
Internet
thanks
so
much
for
joining
and
for
watching
happy.