►
Description
Today’s development agenda: http://bit.ly/1Ub2ZlZ
A
There
we
go
all
right
we're
on
her.
Oh,
it
is
Thursday
March.
Third,
thank
you.
Everybody
for
joining
our
call
today.
We're
gonna
do
a
quick
rundown
through
our
agenda.
For
the
backdrop
developer
check
in
meeting
and
starting
off.
Let's
see,
we've
got
a
couple
of
general
announcements.
If
you
would
like
to
make
a
donation
to
backdrop
CMS,
you
can
do
that
on
our
contribute
page.
We
said
on
a
thank
you:
gift
of
a
t-shirt
for
twenty
five
dollar
donation
or
hoodie
for
fifty
dollar
donation.
A
We've
got
three
items
getting
shipped
out
today,
so
if
you
made
a
donation
recently,
those
should
be
on
the
way
should
be
great.
Also
if
you
are
a
backdrop
contribu,
which
means
you
have
joined
the
kin
trip
grip
and
set
your
appt
your
status
on
that
group
to
public
so
that
the
phpstorm
folks
can
find
you
there,
then
you
can
have
a
phpstorm
license.
So
if
he's
in
an
email
to
info
about
Jeff
CMS
work,
we
can
send
that
out
to
you.
Let's
see,
updates
from
the
project
management
committee.
A
We
are
hoping
to
expand
the
project
management
committee
in
the
next
few
weeks
and
we
have
kind
of
outlined
our
general
representatives,
I
suppose
our
constituents
we'd
like
to
have
represented
we're
looking
for
somebody
who
owns
or
manages
a
web
development
company
and
I'll
be
a
lymphoma
company
of
more
than
one
person.
It
doesn't
have
to
be
huge
company,
I
probably
bought
the
one
person
that
way
we
can
have
kind
of
a
business
perspective
on
decisions
were
making
for
a
backdrop.
A
The
software
we
want
to
have
somebody
who's,
not
a
coder,
but
it's
a
very
active
site
builder.
Somebody
who
put
together
a
lot
of
sites
that
movie
doesn't
write
a
lot
of
code.
We
want
to
have
somebody
with
HTML,
CSS
and
JavaScript
experience
to
have
kind
of
a
front-end
expert
to
make
sure
that
we
are
making
decisions
that
are
in
line
with
what
the
friend
developer,
communities
want
and
we'd
like
to
have
somebody
who's
really
familiar
with
a
lot
lot
of
contributed
modules
so
familiar
with
the
eight
guys.
A
So
we
have
people
in
mind
for
some
of
these
positions
already,
but
there
are
always
opportunities
to
get
more
people
on
board
and
not
sure
we
have
an
official
process
for
how
to
add
people
to
the
BMC
like
if
we
should
have
some
kind
of
a
an
election
cycle
or
something
like
long
term
I
think
initially,
we
don't
have
anyone
to
vote
off
the
island.
Yet
company
might
decide
to
vote
me
off
the
island,
but
I
think
like,
and
once
we
get
people
added.
A
We
should
try
and
figure
out
like
what
our
process
is
going
to
be
for
maintaining
that
group,
so
that,
if
somebody
needs
to
leave
or
something
does
want
to
get
voted
off,
we
have
a
process
for
filling
that
spot.
I,
don't
know
if
you
have
any
thoughts
about
that
already
me
or
make,
but
we
can.
We
can
definitely
figure
that
out,
as
we
start
to
grow,
I
might.
D
D
Just
to
lower
the
level
of
commitment
from
people
like
you
know,
if
you
say
you're
going,
you
join,
the
PMC
will
be
for
the
rest
of
your
life
versus
you
know
for
the
next
year
and
then
we'll
come
back
and
evaluate
that
again
a
year
from
now.
Then
then,
that's
less
less
pressure
on
people
as
well.
So
it's
it's
good
in
all
situations.
I
think
yeah.
A
We
do
that
for
a
non-profit,
then
I'm
working
on
right
now,
where
everybody
gets
a
two-year
term,
but
it's
saying
there's
also
written
in
like
if
you
need
to
get
off
soon
or
you
can
you
just
say,
like
help
get
me
off
or
whatever,
and
so
there's
an
out
even
before
that
two-year
period
of
time,
but
we
don't
have
to
reelect
everywhere
we
can.
We
watch
every
two
years
and
then
end
of
the
two
years.
A
If
you
want
to
remain
on
that's
also
option,
so
it's
like
you
can
opt
yourself
back
in
and
then,
if
we
need
to
fill
someone,
we
can
hold
an
election
and
that
kind
of
decreases
the
amount
of
like
administration
and
associated
with
managing
the
group's
just
say
like
do
you
want
on
do
want
off?
If
you
need
a
half
we'll,
let
you
off,
but
obviously
we'd
love
to
have
people
want
to
be
on
there
for
life
but
commit
you
for
life.
First,
okay,
great
ideas,
all
right!
Nate!
D
Okay,
so
it's
been
two
weeks
since
our
last
actually
I
heard
there
was
a
there
was
a
rogue
meeting,
not
really
Road
but
leaderless
meeting
last
week,
because
Jen
and
I
Jenna
and
I
were
not
around.
We
were
at
sand
camp
last
week,
so
there
was
no
official
meeting
last
week,
but
that
means
that
all
these
statistics
are
double
what
I
normally
are
because
because
it's
been
two
weeks
since
I
was
meeting
so
okay,
so
total
projects
for
backdrop,
CMS
dot
org,
including
layouts
themes
and
modules,
222
modules,
themes
and
layouts.
D
Since
last
meeting
we
released
one
point
three
point:
just
let's
see
that
was
februari
24th,
which
included
some
security
fixes
and
was
coordinated
with
the
drupal.org
team.
So
all
very
exciting.
Let's
see!
Oh
yes,
can't
rip
authors.
We
have
48
total
contributors
they've
been
to
new
applications
that
have
been
open
in
the
past
couple
of
days.
That
are
looking
really
good.
So
that
would
be
great
to
welcome
in
those
new
members
probably
this
week
and
we
have
110
accounts
on
backdrop,
CMS
org,
including
five
new
ones.
D
We
haven't
publicized
it
real
heavily,
but
you
can
create
an
account
on
backdrop.
Cms
org,
if
you
have
not
already
right
now,
just
about
the
only
thing
you
can
do
is
is
configure
your
profile
page,
but
in
the
near
future
there
will
be
more
integration
in
between
backdrop,
CMS
gorg
and
github,
and
publishing
things.
There
will
be
a
lot
more
things
that
you
can
do
on
on
backdrop:
CMS
org
so
go
ahead
and
reserve
your
low
user
IDs.
Now,
if
you're
interested-
and
you
can
do
so
by
visiting
backdrop,
CMS
org,
slash
user.
D
Alright,
that's
it
for
community
growth.
We
can
roll
right
into
infrastructure
tasks,
things
that
are
around
the
backdrop,
software
that
helps
support
the
project.
We've
got
a
couple
of
items
on
here
that
are
the
usual
suspects
and
there's
been
some
modest
progress
in
some
of
these,
but
I
think
a
lot
of
these
are
the
same
things.
We've
been
talking
about
for
the
last
several
weeks
or
even
months.
Actually,
usage
statistics,
we've
had
usage
statistics
for
a
really
long
time.
That's
update
module,
checking
into
backdrop
CMS
org.
D
We
haven't
gotten,
though
the
numbers
of
how
many
sites
that
are
out
there
calculating
properly.
We
have
it
all
the
code
ready.
We
just
need
to
review
it
and
get
it
merged
onto
the
site,
so
that's
been
pending
review
for
quite
a
while
now,
but
hopefully
in
the
near
future,
we'll
get
that
merged
and
and
get
those
usage
statistics
up
on
backdrop,
CMS
org
separate
from
the
the
bugs
that
we've
been
having.
D
We
also
want
to
add
new
capabilities
to
update
module
to
make
it
so
that
it
can
check
in
and
tell
backdrop
CMS
talk
about
certain
features
that
are
enabled
on
on
your
mod
or
on
your
site,
rather
than
just
which
projects
are
in
use.
So
there's
an
issue
for
that.
In
the
backdrop
CMS
Gorgas
uq
issue
99,
if
you're
interested
in
in
working
to
improve
both
projects,
module
on
backdrop,
CMS
org
and
update
module
in
core.
It
requires
some
effort
on
both
sides
in
order
to
make
a
feature
like
that
happen.
D
Next
item
on
the
infrastructure
list
is
drush
for
backdrop.
We've
been
working
to
make
drush
compatible
with
backdrop
for
a
while
now
there's
now
a
copy
of
AD
rush
extension
in
the
contribute
which
works
to
some
degree.
What
you
do
is
you
download
the
latest
version
of
josh,
Josh
eight
and
then
drop
the
backdrop
extension
into
either
the
draw
shade
directory
or
into
your
profile
directories
brush
folder.
D
D
Right
now,
if
you
install
the
dress
extension,
it
can
break
drush
on
Drupal
7
sites,
which
is
a
big
issue,
so
we're
trying
to
figure
out
why
that
is
this
past
week
at
sand
camp
actually
Greg
Anderson
who's,
one
of
the
maintainer
zuv
Josh,
had
been
working
with
myself
to
try
to
figure
out
why
that
was
happening,
and
we
we've
got
some
new
ideas
to
implement.
That
should
help
that
should
help
backdrop
and
and
rush
integrate
well
together
or
better
together.
D
D
D
Once
we
get
this
drush
integration
working
and
once
pantheon
can
run
up
DB
through
drush,
then
it
makes
it
so
that
possibly
we
can
get
backdrop
listed
on
the
list
of
projects
officially
supported
projects
for
pantheon,
because
right
now,
even
though
Pantheon
supports
backdrop,
there's
some
user
interface
glitches.
Basically,
that
Pantheon
says
that
it
can
run
update
dot
PHP,
but
then
it
actually
doesn't
and
we
need
to
get
that
fixed
before
pantheon
lists
backdrop
as
a
piece
of
officially
supported
software
when
you
spin
up
a
new
instance.
D
E
D
I
think
what
are
you
saying
not
just
inside
core
I
mean
we
could
do
that.
But
you
know
we
have
a
separate
upstream
repository
that
we
manage
for
Pantheon
and
I.
Think
he's
saying
that
if
we
include
drush
like
he's,
saying
and
or
dress
the
dress
extension
in
the
upstream
repository
for
pantheon,
then
pantheon
could
start
supporting
drush
immediately
because
it
would
use
our
copy
of
drush
with
the
backdrop
extension
rather
than
the
installation
that
is
on
pantheon.
D
So
that's
really
cool
we'll
have
to
give
that
a
shot
that
could
that
could
really
accelerate
Pantheon
support
for
backdrop.
If
we
can
ship
our
drush
extension
in
our
upstream
repository,
and
that
upstream
repository
is
not
backdrop
core,
we
have
a
separate
repository,
that's
just
for
Pantheon,
which
would
be
a
combination
of
core
plus
drush
that
might
be
really
cool,
yeah,
I
love
it
that
he's
like
might
work,
give
it
a
shot.
E
D
D
We
won't
go
through
each
of
them,
but
if
you're
interested
in
playing
around
with
the
github
API
and
working
on
backdrop,
CMS
don
org
wiki,
some
assistance
setting
up
more
automation
to
streamline
our
processes
on
github,
alright
backdrop,
CMS
org
we've
got
a
number
of
items
that
we're
looking
to
improve
on
backdrop,
so
you
must
not
work
itself.
Jen
I
usually
turn
it
over
to
you
at
this
point.
If
you
would
like
to
pick
it
up.
A
Sure
so
yeah
we've
got
a
couple
of
issues
related
to
allowing
people
have
user
profile
pages.
One
of
those
is
just
good
letting
the
medical
pages
which
we're
working
on
I'll,
try
and
get
that
merged
in
today,
edit
their
pages.
In
the
front
end
theme,
we
also
want
to
allow
single
sign-on
with
github,
so
somebody
is
already
a
github
user
and
they
come
to
join
the
backdrop
community.
They
don't
necessarily
need
to
spend
a
bunch
of
time
creating
the
profile
on
the
back
back
drop
site.
They
can
just
like
to
single
sign-on.
A
C
A
Pull
all
the
relevant
information
over
that
I.
Don't
know
how
sin
is
going
to
happen,
but
I
think
it
would
be
something
it
would
be
really
beneficial
for
us
getting
people
who
have
getting
up
accounts
and
our
contributors
to
backdrop
on
blacktop,
CMS,
org
site
faster,
there's,
a
couple
of
other
things.
E
A
A
We
also
want
to
put
up
a
service
provider
contract
or
listing,
and
that's
probably
also
something
that's
going
to
get
done
before
the
showcase
gets
built,
because
it
might
not
need
an
initial
design.
We
can
do
a
design
review
after
the
fact
and
that'll
just
be
so
that
anybody
who
is
a
service
provider
can
post
that
they
are
searched
butter
on
the
website,
and
then
people
are
looking
for
help
building
it
back
job
site
and
they
want
to
hire
a
developer
designer
hosting
provider.
A
They
can
go
to
that
patient,
find
them
and
that'll
be
initially
modeled
off
of
the
service
provider
listing
on
drupal.org
as
well.
You
can
modify
as
needed
and
then,
of
course,
the
jobs
board.
Something's
been
really
successful
for
drupal
long
term,
only
one
of
those
from
back
job
also
right
now,
but
it's
lower
priority.
A
We
do
have
a
couple
of
things
that
we
have
recently
added
to
the
backdrop
website
that
need
a
little
improvement
are
find
and
modules
themes
and
layouts
pages
have
a
big
chunk
of
follow-up
issues
that
need
some
development,
just
to
make
sure
that
we
get
all
the
information
center
designs
made
available
on
the
website.
We've
got
some
technical
issues
like
getting
fuse
integration
working
in
getting
our
a
statistics
crew
incorrectly,
but
we
will
eventually
get
that
done
and
then
we
have
a
design
for
the
themes.
A
Page,
that's
different
from
the
size
of
the
module
page
has
been
implemented.
Yet
we'll
get
that
done
too.
Once
we
get
all
of
our
technical
implementation
details
on
pulling
in
the
information
we
need
wrapped
up,
then
we
just
have
a
couple
of
you
know:
design,
review
issues
as
well
like
getting
our
news
section
sorted
out.
It's
also
been
a
couple
of
requests
to
call
it.
A
blog
I
think
that
kind
of
makes
sense.
We've
got
stuff
in
there
that
isn't
really
news,
but
there's
also
stuff
in
there
that
isn't
really
bloggy.
A
So
I
don't
know
if
anyone
has
a
better
name
for
probably
should
call
that
section
of
the
site
naming
this
is
hard,
so
it's
kind
of
done,
but
can
use
improvement
same
thing
with
the
event
calendar.
That's
for
a
new
that's
going
to
need
a
design
review
Tom!
It's
currently
under
news.
This
event,
sir
I'm
related,
but
I,
don't
know
if
we
could
reorganize
that
section
two.
A
If
someone
has
some
good
ideas
about
how
to
clean
up
speaking
of
news,
we
are
planning
on
writing
up
a
blog
post
on
benchmarks
of
backdrop,
vs
triple
seven,
also
PHP,
5,
vs
PHP
seven
should
be
kind
of
interesting.
We
also
are
planning
on
doing
a
blog
post.
That's
a
wrap
up
of
sand
camp
where
we
did
our
first
of
all
day
backdrop
training
last
week,
which
I
thought
went
really
well
and
so
Nate.
A
If
you
need
time
to
get
your
benchmarking
done,
I
can
do
the
wrap
up
on
Sam
camp
post
first
and
then
I
know
we
have
a
couple
of
other
people
are
interested
in
doing
blog
posts
as
well.
We
have
on
that
issue,
158
that
talks
about
I'm
scheduling
for
posts
and
I
think
Mike
I,
don't
know
what
your
timeline
is
for
doing
a
config
management
post,
but
whenever
you
want
to
get
that,
we
can
get
that
on
schedule
to
I
know.
Doug
fan
also
want
to
do
one
on
cala
box
and
backdrop.
A
They
were
also
some
people
came
to
our
backdrop.
Training
last
Thursday,
with
local
instance
of
backdrops,
set
up
and
running
in
cow
box,
says
they
went
to
the
Kalibak
shooting
today
before,
which
was
fantastic
khmer.
Is
this
version
that
was
set
up
with
Calla
box,
so
that
was
great
it'll
be
great
to
get
more
kind
of
publicity
on
how
easy
those
things
so
I'd
get
running
together.
So
I'll
have
jug
band.
Do
that
one,
and
then
we
also
will
have
an
upcoming
post
at
some
point
about
backdrop.
A
In
civvy
crm
working
together,
we
gotta
get
those
working
together
and
I'd
like
to
set
up
factor
up
itself
to
use
sibi,
and
we
can
have
kind
of
a
use
case.
Showcase
case
study
case
study,
look
like
what
is
that
word
on
how
we
got
it
working
and
what
we're
doing
with
it.
So,
hopefully
that
will
come
soon
as
well.
Anyone
else
is
in
the
ideas
for
blog
posts.
You
can
add
a
comment
to
that
issue
and
we'll
stick
you
on
schedule
yeah,
but
definitely
the
more
people
have
information
to
share.
A
I
think
getting
everybody
to
post
things
up,
there's
good.
There
was
also
some
discussion
about
just
kind
of
opening
up
so
that
anybody
can
write
a
blog
post
and
just
have
them
only
go
to
the
lake
front
of
the
news
blog
section
when
they're
promoted,
like
we
could
just
kind
of
pick
and
choose
and
be
like.
A
Oh,
this
is
a
great
one
and
we'll
just
put
it
over
there,
but
we
need
to
figure
out
where
those
posts
would
go
if
they're
not
promoters
of
new
section
like
the
way
it's
set
up
right
now.
That
would
just
disappear.
Rachel,
something
created
it
so
I
think
Mike.
It
was
either
recommended
like
on
their
profile
page.
A
We
could
have
everybody
have
their
own
posts,
but
that
will
kind
of
turn
backdrop
CMS
at
work
into
like
a
massive
blog
site,
so
people
will
be
like
Oh
need
a
blog
sign
up
the
backdrop
CMS
org
and
you
can
write
your
own
blog
posts
and
that's
kind
of
an
interesting
idea.
I
had
never
thought
of
that
before
not
really
sure.
We
want
to
support
that,
but
it
I'm
like
drawn
to
the
idea.
A
So
I
don't
know
if,
if
you
guys
have
any
strong
feelings
about
that,
but
it's
definitely
something
we
can
think
about,
try
and
figure
out.
If
we
want
to
encourage
that
kind
of
behavior
or
not,
we
get
a
lot
of
feature
requests.
They
might
be
really
good
if
you
into
the
kinds
of
things
people
want
to
do
on
websites,
and
maybe
that
would
inform
our
decisions
and
let's
do
in
core,
but
I
also
might
end
up
with
us,
adding
like
gazillion
kinship
modules,
to
backdrop
see
mr.
A
A
We
could
lump
in
there
as
well
I
guess
maybe
I'll
I'll
draft
from
those
in
in
Google,
Docs
and
post
a
link
in
higher
newsletters
meta
issue
and
see
if
anyone
wants
to
review
that,
but
we
should
try
and
get
went
out
pretty
soon
and
me
also
did
a
webinar
recently.
It
is
now
there's
a
link
in
the
agenda.
I
can
throw
it
into
the
meeting
to
a
Google.
Are
sorry
YouTube
video,
it
was
a
layouts
deep
dive.
A
D
D
D
Got
me:
go
right
into
134,
went
into
one
for
now,
I
think
now:
you're,
muted,
Jen,
but
I
guess
leave
out
toward
sure:
okay,
okay,
okay,
so
140.
The
next
minor
release
of
backdrop
is
due
or
scheduled
for
May
fifteenth
and
there's
a
number
of
items
here.
Fixing
the
rich
text
editor
is
a
little
bit
of
a
vague
thing,
but
there's
a
bunch
of
follow-ups
to
fixing
up
ckeditor
and
its
integration
into
backdrop.
We
actually
had
one
of
those
things
come
out
in
the
last
bug-fix
release.
D
133
solves
one
of
the
problems
with
uploading
images
that
you
don't
need
to
click
the
upload
button
anymore.
It
automatically
uploads
when
you're
in
the
dialog
and
all
those
things
that
are
bug
fixes.
We
can
fix
those
anytime.
It's
really
that
we
have
some
issues
for
deeper
integration
that
are
scheduled
for
140.
D
But
we
are
repulsed
by
the
implementation,
and
so
our
intention
there
is
that
we
will
do
essentially
a
an
updated
version
of
reference
module
references,
module
called
reference
that
will
provide
all
that
same
functionality
in
the
same
UI
and
features
but
implemented
in
kind
of
a
less
abstract
way
and
built
upon
backdrops
entity
API,
which
we
didn't
have
Drupal
7
I,
don't
know,
I've
seen
any
activity
on
that
Mike
you're
kind
of
taking
the
lead
on
it.
You
want
to
provide
any
info
mostly.
B
Activity
is
actually
sort
of
making
me
issue
bigger
by
getting
into
all
the
entity
stuff.
Basically,
we
need
to
do
some
editions
of
of
there's
the.
What
is
it
called
in
the
entity
in
the
entity?
Object.
There's
a
array
that
matches
some
basic
fields
like
ID
and
label
to
whatever
the
IDM
label
is
like
node
has
you
know
the
label
is
title
and
the
IDS
NID
I
think
in
order
to
get
reference
to
work
in
a
sort
of
very
easy
way.
B
We
should
update
all
of
our
existing
core
entities
to
have
a
couple
additional
fields
to
make
things
easier,
including
just
basically
like
a
14
status
which
which
which
field
in
your
object,
like
a
status,
because
you,
obviously
you
probably
only
want
to
be
able
to
have
options,
only
select
entities
that
are
published
or
users
that
are
active
and
yet
a
couple
more
of
those.
So
but
you
know
that
isn't
breaking
the
API
because
we're
just
adding
a
couple
additional
items
into
that
array.
B
So
so
weird
use
the
reference
modules.
Like
you
know,
they
would
any
any
entities
packages
have
a
couple
extra
fuel,
just
just
a
point
or
if
they
want
to
or
not,
but
if
you
have
like
a
status
field
in
your
entity,
you
just
say
status.
Is
this
field
and,
like
you
know,
created?
Is
this
field
or
author?
Is
this
field
and
stuff
like
that,
just
to
make
it
easy
to
to
filter.
D
B
D
Okay,
yeah,
okay
cool,
let's
see
so
redirect
module.
We
added
path,
auto
and
token
to
previous
minor
releases
of
backdrop,
and
so,
and
the
next
release
would
also
like
to
include
redirects
to
make
it
so
that
when
your
aliases,
your
automatic
aliases
change
that
the
old
pads
are
given
redirects
and
there's
a
pull
request.
That's
coming
along
very
well!
Actually
an
issue
9
05
that
jeff
has
been
working
on.
That
looks
just
fantastic
Jeff.
Do
you
want
to
do
an
update
on
on
redirect.
E
Yeah
it's
working.
As
far
as
I
can
tell
my
manual
testing,
I
updated
a
lot
of
the
tests,
the
Kevin,
where
exactly
where
I
staying
with
that
I,
don't
think
they're
all
passing,
but
I
think
a
good
chunk
of
them
are
passing
and
I
did
an
upgrade
path.
I
have
to
keep
an
eye
on
the
update
hooks
in
case
something
else
gets
into
system
module
and
I
need
to
write
a
chamber
or
someone
does
I
I'd
be
willing
to
do
that.
E
D
I
was
like
well,
it
is
nice
that
it's
a
real
object
and
that
you
can
do
things
like
you
know,
redirect
arrow
save
and
things
like
that,
but
we
might
consider
like
it
might
not
need
to
be
extending
the
entity
type
object
that
maybe
it
can
just
be
a
standalone
object
which
is
the
same
way
like
blocks,
for
example,
blocks
or
objects,
but
they
are
not
entities.
You
know
you'd
like
there's
nothing
wrong
with
having
an
object
that
provides
methods
that
isn't
an
entity.
D
It's
just
I
think
that's
what
everybody
defaulted
to
in
Drupal
world
is
because
it's
like.
Oh,
we
only
have
one
type
of
object,
so
everything
must
extend
it
right,
but
it
would
be
completely
reasonable,
for
us
just
have
a
different
type
of
object,
because
a
redirect
is,
you
know
it's
a
different
situation
than
then
a
piece
of
content.
D
D
Okay,
new
front
end
theme
next
item
on
the
list.
I've
actually
talked
about
this
a
whole
bunch.
Today
we
had
an
earlier
meeting
in
the
design
call
an
hour
ago.
I'm
talking
about
the
new
front.
End
theme:
wes
is
working
on
one
called
basis,
which
is
looking
really
exciting.
He's
not
here
in
this
meeting
so,
and
we
just
talked
about
it
it's
an
hour
ago.
So,
if
you're
interested
in
hearing
about
the
new
front,
end
theme
is
like
just
watching
the
design
call
that
happened
earlier
today.
D
The
issue
for
that
is
issue
1361
lots
of
really
exciting
work
going
on
over
there
and
then
also
new
core
layouts
issue.
698
we're
thinking
about
expanding
the
number
of
layouts
that
are
in
core
to
go
beyond
the
current,
like
left,
sidebar
right,
sidebar,
single
column
situation
that
we
have
now.
That
would
allow
for
more
flexibility
out
of
the
box
when
doing
site.
D
Building
that
issue
we're
kind
of
going
back
and
forth
about
whether
or
not
that
means
the
radix
layouts
or
whether
it
means
a
bootstrap
based
set
of
layouts,
but
I
would
suggest
just
joining
in
that
conversation
and
providing
your
input
there.
If
you're
interested
in
that,
there's
also
other
items
for
140
that
they're
all
just
tagged
for
that
relief
or
that
milestone
in
github
and
a
bunch
of
minor
issues
there.
D
If
you've
got
changes
that
you'd
like
to
see
implemented
in
backdrop,
were
always
open
to
new
features
that
aren't
particularly
on
the
schedule,
but
if
they
make
API
expansions
or
new
user
interfaces,
they
need
to
be
in
in
the
next
minor
release.
Api
changes
not
allowed
in
the
one
da
x
release
cycle.
Those
will
need
to
wait,
2
dot,
X,
which
at
this
point
we
don't
have
a
schedule
for
me.
E
E
D
D
Let's
see
other
items,
we
also
have
continuous
user
improvements
that
we're
trying
to
do
just
at
any
time
two
big
ones
that
may
be
seen
in
the
next
release.
We'd
like
to
add
project
browser
decor
to
make
it
so
that
you
can
find
and
install
projects
from
directly
within
core,
and
that
has
a
pull
request
that
is
actually
working
at
issues
1399,
but
may
need
some
work
to
kind
of
properly
integrate
it
into
into
backdrop
core,
and
we
also
have
a
lot
of
amazing
mock-ups
for
making
a
better
field.
You
I
in
issue
779.
D
There
hasn't
been
any
code
implementation
on
that,
but
there's
been
a
lot
of
great
ideas
around
making
modest
improvements
to
field
UI
that
can
be
done
within
the
1x
release
cycle,
mostly
just
around
improving
the
way
that
we
add
fields
and
show
previews
of
what
those
fields
are
changing.
Widgets
those
sorts
of
things,
reducing
the
number
of
steps
that
are
involved
in
adding
fields
to
a
content,
type
or
another
type
of
entity,
and
so
that
network
is
really
exciting.
And
it's
not
particularly
huge
like
the
amount
of
work
involved
there.
It
is
not
massive.
D
Let's
talk
about
sprints
every
Thursday
such
as
today,
we
have
sprints
afterward
after
the
meeting
and
before
the
meeting
where
you
can
meet
up
with
us
in
the
github
issue.
Queue
github.com
/
backdrop
is
where
most
of
our
primary
communication
happens,
although
we
also
have
been
using
git
er
a
lot
recently.
That's
an
online
chat
tool,
get
ur
da
IM
/
backdrop,
and
you
can
join
to
the
channels
there
and
communicate
more
real-time
with
backdrop
contributors.
D
We
also
are
in
IRC
at
pound
backdrop:
IRC
seems
to
be
fading
in
popularity,
mostly
because
get
er
seems
to
be
working
more
effectively,
but
we're
still
there
in
pound
backdrop
for
anyone
that
has
a
strong
commitment
to
IRC.
You
can
reach
us
out
there
and
in
if
you
have
just
general
watercooler
chat
or
discussions,
you
can
use
reddit
reddit
com,
/,
r,
/
backdrop.
D
Upcoming
events,
we
have
an
ical
feed
of
upcoming
events
that
you
can
get
from
the
weekly
agendas
and
we
also
now
have
an
events
page
on
backdrop,
CMS
org,
which
is
really
exciting
backdrop.
Cms
org,
slash
events,
just
listing
upcoming
presentations
and
events
that
are
back
job
friendly
and
you
can
meet
some
back
top
contributors
at
those
events.
D
D
D
Yeah
the
last
item
we've
got
here
on
the
oh
I
want
to
say:
drupalcamp
Utah
is
this
weekend.
Is
that
right,
starting
tomorrow,
think
so
yeah
and
I'm
not
actually
sure?
Yes,
that
there
is
a
session
on
backdrop
at
drupalcamp
Utah.
So
if
you're
in
the
area
Friday
or
Saturday
tomorrow
and
day
after
tomorrow,
then
you
can
catch
Lala,
bots,
Jared,
Vitner
he'll
be
giving
a
presentation
on
backdrop
very
exciting.
D
D
A
A
This
is
something
we're
working
on
right
now,
with
Drupal
commerce
and
Interpol,
there's
commerce
and
in
fact,
up
we're
going
to
get
back
shop,
which
is
going
to
be
a
simplified,
lighter
weight
version
of
the
same
thing
personally,
like
that,
it's
pretty
clear
that
we
want
something
different.
A
lot
of
these
smaller
modules.
A
Then
there
is
to
port
it
in
its
complete
form
and
then
simplify,
but
I
definitely
would
say
you
know,
I,
don't
know
any.
If
you
have
a
use
case
for
using
field
group
or
you're,
like
my
site,
only
needs
these
two
subsets,
you
comport
those
two
subsets
and
then
put
something
in
there.
That
said
like
this
is
a
simplified
version,
includes
these
two
subsets
and
then,
if
somebody
else
comes
along
and
they
need
one
of
the
things
that
you
have
imported,
they
could
either
add
that
to
the
module
requests
become
filming
tan
or
whatever.
A
If
you
wanted
to
or
develop
a
different
branch,
it'll
really
depend
per
module.
How
that
should
go?
I
personally
would
like
to
see
it
simplified,
because
I
look
at
feel
curved
module
now
and
go
that's
way
too
much,
but
you
see
how
it
got
that
way
like
you
got
that
way,
naturally,
over
time,
where
everybody's
like,
oh,
what,
if
we
did,
this
would
have
with
us.
You
had
a
feeling
really
different,
yeah
I,
don't
know
what
do
you
guys
think.
F
A
Yeah
I
would
say
it
would
probably
be
best
to
start
simple
and
if
you
only
need
part
of
it
just
forth
apart,
you
need,
and
then
you
can
put
something
in
the
readme.
That's
like
these
are
the
parts
that
have
been
ported
for
Drupal
7
and
then
that
way,
if
somebody
else
needs
it,
they
can
look
at
that
and
say
Oh
Liam
either
the
part
I
need
hasn't,
been
ported
or,
and
it
has
or
I
can
use
it
in
its
current
state.