►
Description
Today’s development agenda: http://bit.ly/1mvVkky
A
Alright,
we're
on
air
a
happy
Thursday
februari
18th
same
for
my
birthday
whoo,
we
are
gonna,
do
a
quick
rundown
of
all
of
the
stuff
in
our
agenda
as
usual,
starting
with
general
announcements.
If
you
want
to
make
a
donation
to
backdrop,
CMS
will
send
you
a
t-shirt
and
hoodie
upcoming
events.
Is
a
sand
camp
will
have
a
bunch
there
in
person.
So
if
you're
going
to
be
in
san
diego-
and
you
really
want
a
hoodie,
you
might
try
it
on
first,
that's
totally
fine,
you
can
come,
try
it
on
there.
A
So
don't
pay
online
in
person.
If
you
want
a
free
phpstorm
license,
those
are
available
to
all
the
backdrops.
Can't
ribbed,
avella
purrs
I
need
to
do
is
join
the
backdrop
contribute,
and
we
can
help
you
through
that
process.
If
you
want
either
need
to
have
ported
a
module
theme
or
layout
or
want
to
Co
maintain
one,
we
can
get
you
set
up
there.
One
important
thing
to
note:
you
should
make
your
membership
to
that
group
public.
This
is
something
that
Mike
noticed.
A
I
think
in
this
last
week
is
that
a
lot
of
people,
including
myself,
had
not
set
their
membership
for
that
group
to
public.
If
you
can't
see
that
your
public,
then
on
the
phpstorm,
people
can't
verify
that
you're
allowed
to
have
a
license.
So
that's
kind
of
one
thing:
if
you
want
the
license
and
another
thing,
it's
just
a
kind
of
doesn't
look
like
there's
as
many
people
involved
as
there
actually
are.
A
It
is
tricky
to
find
that
setting
it
took
me
a
minute,
but
if
you
go
to
the
backdraft
contribute
and
look
at
the
settings,
there's
a
list
of
all
the
contributors
and
it'll
say
next
to
your
name:
whether
your
status
is
public
or
not.
I
also
don't
think
anyone
else
has
the
ability
to
change
your
visibility.
Setting
I
was
looking
at
that
today,
and
it
looks
like
everyone
is
only
allowed
to
change
their
own.
A
So
if
you're,
okay
with
contributing
to
backdrop
being
public,
then
you
should
change
that
setting
and
it'll
definitely
help
for
phpstorm
licenses,
so
related
a
couple
of
new
updates
from
the
pmc
this
week.
You
guys
remember
a
couple
of
weeks
ago.
We
announced
that
we
added
Mike
McCaffrey
is
a
new
member.
A
So
I
just
wanted
to
go
over
these
now
we're
looking
for
somebody
who
is
owner
or
representative
of
a
web
development
company,
so
it
doesn't
have
to
be
a
huge
company,
but
having
more
than
one
developer
would
be
good
just
so
that
we
know
what
it's
like
as
a
company
that
builds
websites
for
people.
What
kind
of
problems
are
you
facing?
What
kind
of
solutions
are
you
looking
for
and
is
backdrop
meeting
those
needs,
so
it
would
be
good
to
have
that
voice
in
the
mix.
A
What's
going
on
with
the
modern
web
versus
you
know
what
the
majority
of
people
are
doing
kind
of
has
a
good
feel
of
what
front
ender's
want
versus.
What's
realistic
for
people
owning
websites
I'm
getting
at
that
kind
of
feedback
on
the
PMC
would
also
be
really
good,
so
Mike
I
think
you
also
mentioned
would
be
good
to
have
somebody
who's
super
in
tune
with
contribs
cub
leon.
Contributed
modules.
A
I
wasn't
really
sure
how
to
list
that
as
a
constituent,
because
there's
a
lot
of
people
that
could
just
be
like
contributors,
Oh
figure
out
terminology,
but
people
that
are
you
know
very
good
at
working
with
contributed
modules
and
understand.
How
can
trip
stuff
works
with
core
api's
would
be
great
to
have
one
of
those
people
in
there
as
well,
and
that's
kind
of
what
we
basically.
B
And
say
basically,
I
think
we
need
someone
basically
who's
familiar
with
a
lot
of
the
contributed
modules.
Who
can
make
sure
that
any
changes
that
we
make
to
core
are
don't
break
things
sort
of
on
the
contributed
side
and
that
we
aren't
yeah,
because
we're
I
think
we're.
The
three
of
us
are
like
pretty
much
like
very
core
focused
and
maybe
if
someone
is
more
contributed,
make
sure
that
we
don't
make
any
changes
that
a
bunch
of
core
people
might
get
upset
about
our
control
people
might
consider
about
okay.
A
Contribute
yeah,
that's
good
I,
don't
yeah!
Well,
we'll
figure
out
the
exact
terminology,
but
I
think
that
all
sounds
very
good.
So
we
are
going
to
be
looking
for
people
who
are
interested
in
filling
these
roles
in
the
PMC.
We
have
kind
of
a
couple
people
in
mind
for
some
of
them
and
we'll
reach
out
to
you
and
see
if
you're
interested.
But
if
your
name
is
not
our
shortlist
in
there
is
something
that
you
really
want
to
be
involved
in.
A
Definitely
let
us
know
as
well,
especially
the
kind
of
site
owner
or
website
builder
company
owner
role.
That's
not
something
that
someone's
been
super
involved
in
core
I.
Maybe
even
watching
these
videos,
it's
gonna,
you
know
be
on
our
radar,
but
if
we
have
people
who
are
super
interested
in
what
backdrop
is
doing
but
haven't
contributed
yeah
cuz,
they
don't
write
code
wants
to
be
involved
in
some
way.
It's
a
good,
a
good
place
to
kind
of
pop
your
head
in
the
door.
A
So
definitely
let
us
know
if
you're
interested
in
any
of
those
roles
and
we'll
try
and
figure
out
a
process
for
getting
people
in
and
managing
that
as
well.
So
we
are
thinking
about
expanding.
This
is
where
we're
going.
Oh,
my
god.
I
do
think
that
we'll
get
there
me.
Let's
turn
our
view
for
community
growth.
C
Okay,
Wow
lots
of
stuff
happening
this
past
week.
Let's
see
we
have
213
total
projects
or
backdrop
CMS,
in
the
backdrop,
contribute
hub
group.
That's
five
new
modules
since
meeting,
including
a
couple
of
ones
that
are
super
handy
and
I'm
greatest
I'm
really
happy
to
see
them
in
our
contributory
views.
C
So
it's
so
awesome
to
see
all
of
those
modules
being
ported,
Andy
I
know
you
are
responsible
for
several
of
those,
so
thanks
again
and
also
Graham
for
doing
views
sends
it's
so
great
to
see
so
many
new
modules
being
available
for
backdrop,
let's
see
on
backdrop
CMS
org,
there
are
144
projects
that
have
official
releases,
which
differs
from
the
ones
on
github,
because
github
is
kind
of
like
all
modules
that
are
in
development,
whether
they're,
ready
or
not,
and
once
they're
ready.
We
make
an
official
release
on
github
and
then
synchronizes
over
to
backdrop.
C
But
we
have
three
new
members
since
last
week,
moving
up
from
45
contributors
to
48,
welcome,
new
people
gave
super
excited
to
have
you
and
there
are
0
8
open
applications
for
the
kinship,
all
of
which
are
just
waiting
for
feedback
from
the
original
applicants.
So
we've
been
keeping
on
top
of
those
applications
pretty
effectively,
which
is
great
if
you'd
like
to
join
the
backdrop
contribute
you
can
do
so
by
visiting
github.com
/
backdrop,
ops,
/,.
C
Contribute
for
people
that
are
interested
in
moving
backdrop,
modules
or
themes
into
the
backdrop,
contribute
on
github,
let's
see
and
over
on
backdrop,
CMS
org.
We
have
105
total
user
accounts.
Eight
new
users
have
signed
up
since
last
meeting
all
Wow
pretty
impressive
week.
As
far
as
a
community
growth
goes
lots
of
new
modules,
lots
of
new
contributors.
It's
really
awesome
to
see
so
much
activity,
let's
see
so
next
item
on
the
agenda
is
infrastructure.
C
We
talked
about
the
things
that
are
round
the
backdrop
project
every
week,
that
isn't
the
software
itself
and
most
of
those
things
are
related
to
backdrop,
CMS
org
and
tools
around
using
back
job.
So
this
one
item
we've
been
talking
about
for
a
long
time.
We've
got
a
lot
of
things
that
are
in
needs
review,
but
haven't
been
deployed
yet
and
that's
around
how
project
module
and
update
module
interact
with
each
other.
We
have
update
module
on
all
of
the
backdrop
sites
that
are
out
there.
C
Travis
CI
tests
right
now
are
also
in
our
raw
data
and
we'd
like
to
get
that
information
out
gen
file,
the
pull
request
to
make
it
so
that
Travis
will
stop
checking
in
into
into
backdrop
core
to
make
it
so
that
test
runners
won't
actually
be
pinging
backdrop,
CMS
org,
all
the
time
so
step.
One
is
to
merge
that
step.
Two
is
to
remove
all
of
the
current
Travis
CI
IP
addresses
from
our
raw
data
on
the
server
and
then
step
three
is
to
actually
enable
the
analytics
like
calculation
script.
C
We
have
a
pull
request
for
it,
but
it's
not
deployed
to
backdrops
in
the
store.
Yet
once
those
things
are
in
place.
We'd
like
to
expand
out
what
kind
of
data
we
collect
from
backdrop
CMS
sites
that
are
out
there,
including
things
like
certain
features
that
are
enabled
on
their
sites
or
what
themes
they're
using
or
theme
settings
they're
using
if
you're,
using
color
schemes
or
things
like
that,
so
that
we
can
make
more
decisions
based
on
what
features
are
actually
being
used
on
sites
based
on
what
the
usage
data
is
reporting.
C
Let's
see,
dress
for
backdrop,
we
have
a
working
extension
for
drush
that
makes
it
so
drush
functions
on
backdrop
websites,
you
plop
it
in
tea
or
dot
brush
directory
or
into
your
Russian
installation,
and
it
makes
it
so
that
rush
can
identify
backdrop
site
and
do
certain
commands
a
subset
of
the
available
commands,
at
least,
but
we're
always
adding
more
commands
and
I.
Think
Jeff.
Sorry
I
didn't
check
in
with
you
before
the
meeting,
but
could
you
give
an
update
on
under
essence,
you've
been
working
on
expanding?
It
recently
sure.
D
Less
just
for
you
all
I
last
week
and
we
fired
that
up
and
he
tested
it
and
we
merged
it
in
so
that's
great
one
Walkman
and
actually,
just
a
few
minutes
ago
someone
filed
a
PR
against
the
rush,
dl
I
guess
if
W
get
some
versions,
don't
have
show
progress,
so
it
was
breaking
on
his
site.
So
he
found
a
PR
to
remove
that
which
I
think
is
good
for
wider
coverage.
I'll
take
a
look
and
see
if
we
can
conditionally
included
or
something
like
that.
But
that's
good
go
ahead.
Sorry.
B
I
haven't
filed,
I
haven't
filed
yet
but
I.
Actually,
when
I
installed
the
drudge
extension
for
backdrop,
it
actually
started
breaking
commands
with
Drupal.
Suddenly
it's
starting
to
there's
a
lot
of
W,
get
errors
when
downloading
regular
Drupal
modules
and
Drupal
installation,
so
I'm,
not
sure
how
that's
possible,
but
as
soon
as
I
removed
the
extension
suddenly
be.
Ours
all
went
away.
C
C
Let's
so
another
thing
we'd
like
to
do:
we've
got
an
issue
here
that
once
we
get
this,
that
issue
resolved
as
well
as
Josh
up
t
be
working.
All
the
Jeff
you
said.
Rush
up,
DB
is
now
working
for
running,
update,
dot,
PHP
scripts.
Is
that
right,
yeah,
okay,
that
we'd
like
to
reach
out
to
the
guys
at
Pantheon
and
make
it
so
that's
pantheons
integration
with
backdrop.
C
There's
a
little
check
box
for
like
run,
update
PHP
after
a
new
version
of
backtrack
comes
out
and
you'd
apply
that
to
pantheon,
but
that
check
box
has
never
worked.
So
once
we
have
the
direction
aggression
fixed,
we
want
to
get
the
Pantheon
people
to
update
the
rush
to
load
the
dress
extension
for
backdrop
and
make
it
so
that
checkbox
can
actually
work
again,
which
would
be
great.
C
C
Some
of
our
processes
contribute
back
to
have
an
automated
code
review
functionality
syncing
between
poor
requests
and
issues
would
also
be
really
great.
In
between
our
our
issue
repository
and
our
code
repository,
we
should
have
issued
numbers
for
these
things
as
well,
but
they're
not
in
the
agenda.
We
can
get
that
updated
rather
than
me
needing
to
find
link
every
meeting,
but
there's
a
whole
tag
for
things
that
we'd
like
to
automate.
It's
the
github
automation
tag
that
is,
in
the
backdrop
CMS
org
issue
queue.
C
So
if
you're
familiar
with
github
API
is-
and
you
want
to
do
some
integration,
we
can
get
you
access
to
backdrop,
CMS
orgs,
a
continuous
integration
server
and
we
can
write
any
kind
of
integration.
We
need
to
make
it
so
that
github
and
backdrop
CMS
torg
have
further
integration
with
each
other
to
make
it
so
that
we
can
speed
up
some
of
our.
This
is
all
right
backdrop:
CMS
org
Jen.
Do
you
want
to
take
it
over.
A
I'll
take
it
overrun.
You
did
have
that
okay,
so
we
recently
have
allowed
people
to
be
able
to
sign
up
and
log
in
to
backup
CMS
to
org,
and
but
somebody
did
point
out
recently
that
we
didn't
put
a
sign
up
or
login
link
any
website.
A
So
that's,
like
my
eye,
is
priority
item
for
today's
to
get
that
added
and,
and
then
we'd
also
like
to
be
able
to
set
up,
come
some
kind
of
single
sign-on
with
github
that
if
you
already
have
a
github
account,
you
don't
need
to
create
an
account
on
backdrop.
You
can
just
click
the
button
and
log
in
then.
If
you
want
to
add
your
profile
information
you
can
but
some
of
what
we
should
be
able
to
pull
it
over
directly
from
like
your
username,
but
that
isn't
ready.
A
Yet
that's
kind
of
next
on
our
list.
We
also
are
planning
on
adding
a
showcase
for
websites
that
are
built
with
backdrop
which
will
help
those
of
us
who
are
building
sites
with
backdrop
convince
people
that
we
should
build
sites,
the
spectra
and
we're
going
to
add
a
servicing
contractor
listing,
so
that
people
who
want
to
build
size
a
backdrop
can
find
people
to
build
them
side.
A
Spectra
we're
also
going
to
add
event
calendar
so
that
anyone
who
has
an
upcoming
event
that
is
they're
interested
in
having
people
either
speak
about
backdrop
or
people
come
to
learn
about.
Backdrop
will
be
a
little
is
that
on
an
events
calendar
and
then
we
also
want
to
do
a
jocks
board
so
that
if
anneorshine
specifically
hire
backdrop
developers,
we
can
get
listings
up
for
that
as
well,
and
we
do
have
a
bunch
of
existing
things
that
need
improvements.
A
Like
our
news
page,
our
news,
I,
don't
know
if
we're
going
to
call
it
a
blog
page,
whatever
section
is,
where
we're
putting
our
blog
posts
and
announcements
and
videos
and
Twitter's
and
whatever
needs
a
design
reviews
or
working
on
that,
we
also
have
our
kind
modules,
themes
and
layouts
pages.
There's
more
design
work
that
we
have
that
we've
not
implemented
yet
because
we're
stuck
on
some
development
work
becoming
more
urgent,
since
we
have
more
and
more
module
schemes
and
layouts
being
ported
to
backdrop.
A
So
I
would
love
to
spend
some
time
getting
that
going,
in
particular
getting
the
themes,
images
to
display-
and
there
is
some
related
core
work
to
that
as
well,
where
we're
thinking
about
adding
the
ability
to
have
more
than
one
screenshot
of
a
theme
or
module
or
a
layout,
and
so
I'm
not
sure
exactly
that,
it's
going
to
work
in
terms
of
the
short
term
will
probably
just
filled
the
one,
but
I
would
love
to
be
able
to
get
like
multiple
screenshots
I
think
that
would
be
more
useful
for
module.
A
So
you
have
different
functionality
and
four
themes
that
have
support
for
more
than
one
layout
or
you
want
to
show
more
than
one
page.
So
I'll,
that's
tied
in
I,
think
it's
important
thing.
That's
high
on
our
priority
list.
A
Let's
see
moving
into
news
and
announcements
official
blog
schedule
at
158.
We
got
a
little
off
track
recently,
because
the
way
that
the
news
posting
works
is
that,
right
now
the
only
people
have
access
to
publish
stuff,
our
editors
on
the
site
and
our
regular
bloggers.
Don't
so
we're
looking
at
some
alternatives
for
that?
There
is
also
a
core
issue
about.
We
should
be
able
to
set
the
date
to
the
future
and
the
content
will
publish
at
that
date
in
the
future.
A
We
great
if
we
could
get
that
in,
so
that
we've
can
benefit
from
it
ourselves.
There's
also
some
talk
about
just
letting
anyone
on
backdrop,
CM
esta
or
be
able
to
write
a
blog
post
and
have
it
appear
somewhere
else
like,
for
example,
on
their
userpage,
and
then
we
could
look
at
the
blog
post
through
be
created
and
promote
them
to
the
front
pages
necessary
a
little
hesitant
on
that,
just
because
I
don't
want
people
to
start
using
back
Jeff
CMS
to
org
as
their
own
vlog,
but
I.
Don't
really
know.
A
Why
have
that
feeling,
like
maybe
we'll
be
good,
biblia
inspector
up,
see
this
targus
their
own
blog?
It's
just
not
been
in
my
mind,
is
something
that
we
would
support,
but
it
could
be.
It
would
definitely
be
a
good
test
case
of
the
kinds
of
things
people
want
to
do
on
blogs
and
if
we
can
actually
support
that
or
not,
but
it's
a
good
idea,
I
think
we
wish
you
to
continue
talking
about
decide
if
that's
what
we
want
to
do.
I
do
also
like
the
idea
of
having
people
write
their
own.
A
A
So
we
did
get
I
our
post
from
last
Friday
up
I
think
it
was
this
monday
or
something
so
we
have
a
have
a
recent
bust
up
there.
Now,
if
you're
not
going
to
get
that
one
done
by
tomorrow,
if
anyone
else
has
something
they
want
to
blog
about
tomorrow,
we
get
there
that
up-
or
we
can
just
push
yours
to
next
week-
and
there
is
some
other
stuff.
A
We
should
probably
be
working
a
working
on
in
marketing
anyway,
like
we
need
to
send
a
newsletter,
we
have
a
webinar
coming
up,
we
should
promote,
we
have
a
training
coming
up,
we
should
promote.
We
haven't
sent
a
newsletter
to
our
people
about
1.3
coming
out.
There's
a
lot
of
stuff
I
think
we
should
be
working
on
that,
isn't
the
blog,
so
that
needs
to
wait
a
week.
I
think
that'll
be
other
things.
A
Let's
see
we
have
a
webinar,
februari
24th
is
just
mentioned,
and
we've
been
getting
some
excellent
promotion
from
the
folks
who
are
doing
that
webinar,
which
is
I,
think
it's
pronounced
sorry
John
technologies
and
they're
doing
a
great
job
at
promoting
that
so
I'm
going
to
do
some
additional
promotion
of
that
in
our
newsletter,
etc
and
that'll
be
a
deep
dive
into
layout.
So
it'll
be
a
kind
of
a
high-level
overview
of
like
what
is
backdrop.
Maybe
a
couple.
A
You
know
10
15
minutes
on
that
and
then
a
deep
dive
until
they
ask
for
those
layouts
is
the
one
thing,
that's
significantly
different
between
backdrop
and
Drupal,
and
this
is
a
primarily
to
a
drupal
target
audience,
but
I
think
it'll
be
really
interesting.
Right
on
the
heels
of
drupalcon
Asia
should
be
should
be
fun.
A
Okay,
we've
got
a
whole
bunch
of
other
marketing
related
tasks.
In
the
backdrop,
CMS
org
issue
queue
there's
a
tag
therefore
audience
marketing.
There's.
Anyone
who
has
any
particular
affinity
for
marketing
maybe
doesn't
contribute
in
any
other
way.
There
are
a
bunch
of
low-hanging
fruit
tasks
there
that
just
be
a
couple
of
minutes
that
we
could
definitely
use
help
with
all
right.
Let's
move
on
to
backdrop,
CMS
the
project
itself
version
1.3
point
3
is
our
next
scheduled
release.
A
We
have
a
bunch
of
issues
from
the
latest
version
of
Drupal
Drupal
7
42,
that
I
think
almost
all
of
them
have
four
requests
less
than
I
looked
at
it.
There
was
only
one
left,
which
was
pretty
tricky.
It
was
upgrading
some
I
remember
exactly.
It
was
like
upgrading
at
an
external
function
that
Drupal
copied
from
something
else
to
the
latest
version
of
that
function
and
also
copied
from
something
else.
A
So
the
poor
quest
for
the
passenger
plane
was
super
messy
and
so
Jenna
to
get
that
cleaned
up
for
back
jack
was
also
kind
of
a
pain
but
I
think
everything
else
is
a
poor
request,
mostly
thanks
to
Jeff.
So
thanks
for
putting
all
that
work
in
there,
that
was
fantastic
and
I.
Think
at
me,
I,
don't
know
how
many
poor
Questor
in
q4
review
for
that,
but
there's
a
huge
chunk
foam
that
are
probably
ready
because
they're
not
all
terribly
complicated,
I'm
sure
there's
a
handful
from
the
probably
need
to
be
rerolled.
A
A
There
are
also
a
couple
of
little
bugs
that
that
emerged
from
one
point
three
point:
Oh,
none
of
them
are
super
high
priority,
but
they
anything
that
has
popped
up
as
a
bug
has
been
tagged
for
13
and
if
it's
easy
to
fix,
if
not
it'll
go
into
134
instead
of
1
through
3,
but
as
needed,
we'll
both
fix
bugs
as
they
come
up
nothing
that
is
so
broken
that
we
need
to
issue
a
release
urgently.
So
I'm
stunner
agenda
for
the
next
bug-fix
release
and
the
next
minor
release.
A
One
point
for
point:
0
is
scheduled
for
me
15th,
which
is
also
wes's
wedding
day.
It's
very
sad
and
high
on
our
list
there
to
fix
some
user
experience
issues
with
the
rich
text
editor.
A
These
are
things
that
didn't
get
into
1.3,
that
you
know
anyone
trying
to
rape,
blogs
on
backdrop
or
create
content
and
backdrop
is
running
into
pretty
often
I
would
love
to
see
those
get
fixed
on
our
before
one
point
for
coming
out,
and
we
also
have
some
big
chunks
of
code
that
we'd
like
to
get
into
1.4,
including
references
module,
which
will
be
a
slight
rewrite
from
reference
and
cilantro
and.
A
Contributing
there's
also
redirect
module,
which
is
same
thing.
Work
will
take
as
much
as
we
can
from
contribs
and
see.
If
it's
clean
enough
to
go
to
Korres
is
there
needs
a
little
rewrite
on
it,
and
that
issue
is
905.
I.
Think
that
has
a
poor
quest.
That's
ready
for
review,
putting
on
what's
sort
on
that
today,
and
then
we
have
the
two
doozies
creating
a
new
front,
end
theme
and
adding
a
set
of
layouts
to
make
backdrop
more
versatile
out
of
the
box.
A
Both
of
those
are
gonna
require
some
kind
of
careful,
careful
thought
about
how
to
get
from
current
versions.
Backdrop
effect
up
to
an
upgraded
version
that
contains
the
new
themes
and
layouts
we're
going
to
need
to
think
about
how
the
two
fit
together
in
terms
of
organizing
our
CSS.
If
we
want
to
use
some
kind
of
a
framework
want
to
make
our
own
framework
how
that's
def
it
together
ended
up
being
a
little
complicated,
but
we
do
have
some
good
ideas
based
on
contrib
for
both
Triple
M
backdrop
and
I
know.
A
E
Yeah
I,
I
conned
a
co-worker
that
it's
a
designer
to
give
me
feedback,
Marissa
Epstein
and
she
toured
a
new
one
I.
That
was
good,
so
got
me
thinking
a
lot
about
how
I
could
improve
this,
but
I
think
for
now,
since
she
didn't,
she
didn't
have
any
major
complaints
about
the
wireframe.
I
think
im
just
gonna
build
it
just
to
like
have
something
built
and
then
think
about
the
design.
She
said
she
might
be
able
to
find
some
time
to
help
me.
E
E
It's
pretty
similar,
but
has
some
some
nice
touches
so
and
I
got
the
for
anyone
who
either
wants
to
try
to
design
it
themselves
and
wants
to
use
mind
as
a
base
or
anyone
who
wants
to
try
to
code
themselves
and
wants
to
use
my
code
is
base
which
doesn't
exist
yet
I'm
going
to
make
that
stuff
available.
So
people
can
just
riff
on
what
I
have
or
like
make
something
completely
different.
It's
all
up
to
you
so
tada
yay.
A
That's
a
test,
I
think
so
much
alright.
So
we
have
milestones
for
both.
One
point
three
point
three
and
one
point
four
point:
oh
and
they
github
Q.
So
if
you
want
to
see
what
is
on
the
to-do
list
for
those
two
issues,
you
can
go
ahead
and
check
out
those
milestones
all
right.
We
also
have
a
bunch
of
other
issues
that
are
always
kind
of
in
our
mind
in
terms
of
improving
related
to
both
user
experience
and
developer
experience,
two
major
ones
for
user
experience
that
we
would
love
to
get
into
1.4.
A
If
possible,
are
the
project
browser
which
we
had
slated
for
1.3.
That
needs
a
little
little
needs
to
be
integrated
more
carefully
with
the
rest
of
backdrop
and
separated
out
from
the
update
module
but
then
integrated
into,
like
that
add
a
module
page
so
removed
in
some
places,
isn't
added.
There's
a
little
cleanup
I'm
on
the
code
there
and
then
filled
UI,
which
I
know
Wes
has
also
done
a
ton
of
work
on.
A
We
know
it's
messy,
it
is
messy,
but
it
is
what
people
know
so
we're
trying
to
kind
of
rethink
that
problem
space
and
say
how
can
we
make
it
less
messy,
more
intuitive,
but
still
not
veer
too
far
from
the
tool
of
people
know
how
to
use
today.
So
that's
also
there's
a
bunch
of
mock-ups
in
that
issue
as
well.
That's
issue,
number
7
99
would
love
to
get
more
feedback
in,
and
progress
on
that.
If
anyone
is
particularly
passionate
about
field,
you
I
and/or
project
prosper,
alright.
A
So
when,
when
do
we
do
all
this
work?
Well,
we'd
like
to
do
it
on
Thursdays
Oh,
often
right
after
this
phone
call,
we
hang
out
in
the
github
issue
Hughes.
We
hang
out
in
IRC
if
you
guys,
like
I,
receive
we've,
also
started
using
git
er,
which
is
a
chat
medium
for
anyone.
Who's
on
github
I,
actually
like
the
little
bit
better
than
IRC
there's
lower
barriers
to
entry,
but
since
most
of
our
triple
friends
are
on,
IRC
were
also
still
on
IRC.
A
For
the
time
being,
we
have
read
it
that
if
you
aren't
entire
see
or
get
our
github,
you
can
chat
on
reddit
and
we
are
talking
about
other
ways
to
let
people
communicate
with
each
other,
perhaps
by
building
something
on
fact.
Ofc
announced
at
work.
Yeah
Nate
just
asked
if
just
one
Jeff
wanted
to
give
an
update
on
redirect
module.
D
I
just
have
to
go
through
made
me
some.
A
good
review
of
it
and
I
just
have
to
go
through
his
suggestions
and
we're
changing
course.
I
was
integrating
with
path
we're
going
to
make
it
a
standalone
module
since
seems
obvious
that
that's,
it
should
be
the
case
due
to
the
books
in
there,
so
they
sneak
yeah.
C
Cool
yeah,
it
looks
really
good,
though,
like
the
I
mean
I
know
it's
mostly
just
a
port
of
the
control,
but
but
there's
adaptations
and
things
in
there
to
make
it
appropriate
for
core,
and
it
looks
it's
a
great
start
so
that
that's
great
to
see
that
coming
along
I
know
other
than
that.
Like
we've
also
got
references
and
I'm
not
sure
if
there's
been
any
update
on
that
either
I
know
Mike's
been
taking
a
stab
at
it,
but
I'm
not
sure
that
it's
moved
forward.
Yet
no.
B
A
Should
maybe
talk
about
to
is
the
entity
conversion,
because
we
have
had
the
same
conversation
two
or
three
times
recently,
where
we
took
the
parts
of
entity
that
weren't
completed
in
Drupal
7
and
completed
them
in
backdrop,
but
it
is
not
as
complete
as
the
entity.
A
Api
module
was
for
Drupal
7
can
trim,
and
we
had
this
talk
with
Ryan
serama,
because
he
has
a
drupal
commerce
uses
entities
really
heavily
about
how
there
are
parts
of
the
end
of
the
API
that
aren't
in
backdrop
and
how
to
get
around
that
and
then
Mike
I
know.
You
ran
into
that
recently
too,
when
you
were
working
on
converting
other
modules
that
use
enemies
heavily.
I'm
not
sure
like
what
our
game
plan
is
for
all
of
the
stuff
in
entity.
Api,
that's
not
in
core.
A
If
we
want
to
have
an
immediate
entity,
API
can't
rip
module
solution
or
if
we
want
to
try
and
move
the
missing
pieces
into
core
or
if
we
want
to
set
some
guidelines
around
like
what
we
want
in
coram,
what
we
don't
and
then
that
way,
it'll
be
really
clear
to
be
like
okay,
this.
If
anyone
does
need
in
entity
metadata
rapper
if
they
need
the
entity,
API
can't
rip
module.
A
But
if
anybody
wants
like
entity
load
all
info
or
whatever,
that
should
be
in
court
like
there
should,
there
might
be
like
a
clear
delineation
of
stuff.
We
want
important
stuff,
we
don't
know
if
you
have
any
thoughts
on
how
to
deal
with
that,
but
the
more
controls
that
do
crazy
stuff
with
entities
the
more
we're
going
to
have
to
kind
of
figure
out
what
we
want
back
to
have
to
do
with
enemies
and
what
we
don't
well.
B
I
was
thinking
about
since
I
was
working
on
this
and
I
feel
like
there's
a
lot
of
the
entity
code.
That
just
like,
does
the
stuff
with
entities
and
makes
them
work.
But
then
there's
also
sort
of
a
lot
of
like
that,
like
the
metadata
wrappers
and
things
like
that
or
for
developers
who
want
to
have
more
tools
to
use
with
entities
and
sort
of
the
object-oriented
land.
So
moving
as
much
of
the
sort
of
object-oriented
program
or
preference
stuff
to
a.
B
Contributes
to
be
even
if
that's
not
installed
is
there
is
probably
sort
of
a
good
it's
complicated.
Like
I
mean
the
whole
system
is
very
complicated
and
it's
kind
of
Drupal
meeting
the
rest
of
the
object-oriented
world,
like
you
know,
in
some
slow,
weird
collision.
So
it's
like
you
know
hard
to
tell
exactly
where
one
stop
someone
ends,
but
it's
yeah,
yeah.
C
Ryan's
ramens
take
was
the
same
that
for
his
commerce
platform
for
backdrop,
he's
calling
back
shop
that
it
needed
only
the
like
critical
parts
of
the
API
and
like
the
entity.
Wrappers
in
particular
is
all
just
convenience
methods
like
it's
all
just
shortcuts.
Basically-
and
he
came
to
the
same
conclusion-
that
the
shortcuts
and
those
wrappers
are
unnecessary.
C
They're
really
just
kind
of
convenience,
obviously
I'm
repeating
myself,
but
it's
really
not
crucial
for
core
or
for
his
purposes
and
I
doubt
it
will
be
for
our
references
port
either
that
we
can,
if
we
need
to,
we
can
call
entity,
load
and
load
an
entity
off
of
its
ID,
like
that's
not
hard,
rather
than
chaining
them
together
to
automatically
load
them.
So
that's
that's
about
where
we're
going
to
be,
but
he
had
a
bunch
of
other
changes
that
were
just
like
things
that
are
missing
out
of
the
entity.
C
A
Okay,
so
any
time
anyone's
working
on
any
module
that
needs
one
of
those
little
hand.
You
know
candy
developer
assistants,
make
it
less
hassle
thing.
We
should
make
a
core
issue
against
backup
and
tag
it
with
DX
and
we'll
see
when,
if,
whenever
we
can
get
that-
and
we
can
get
it
in,
but
anyone
who
wants
anything
crazy,
like
it
entity
metadata
wrapper
that
would
need
to
live
in,
like
backdrops
kenshin
version
of
vanity
API
right.
Okay,
sounds
good
yeah.
Also.
A
Another
thing,
too,
is
that
when
we
were
talking
to
Ryan
about
like
how
to
think
about
solving
problems,
we're
backed
up,
it
seems
like
on
the
Drupal
7
straight
port
for
a
lot
of
these
bigger
projects,
for
something
like
commerce,
is
not
really
the
right
solution,
because
we'll
be
best
kind
of
take
backdrops
philosophy
and
create
a
kinship
project
with
that
in
mind,
so,
rather
than
just
boarding,
Drupal
commerce
to
backdrop
which
maybe
isn't
the
right
solution,
he's
kind
of
rethinking
about
like
what
would
your
full
commerce
look
like
if
it
was
written
with
backdrops
principles
in
mind
and
I?
A
Think
the
more
people
tend
to
do
that,
the
less
we're
going
to
need
an
entity
API
for
backdrop,
because
people
will
say
like.
Oh,
you
know
these
epic
tinea
and
object-oriented
rappers
are
there
for
convenience,
but
maybe
like
in
a
backdrop
world.
We
do
different
things
for
convenience
or
we
have
fewer
layers
of
abstraction
of
just
call
these
things
directly
and
we'll
just
kind
of
Steve.
What
but
a
controlled
starts
to
look
like
for
backdrop
where
we
are
kind
of
taking
everything
into
account
too.
A
So
so,
if
I
know,
if
I'm
doing
a
lot
of
straight
porting,
just
because
we
need
to
get
things
done,
but
it
would
be
kind
of
fun
to
start
kind
of
saying
like
what
does
this
look
like
for
backdrop,
and
would
it
be
different
from
what
it
looks
like
for
Drupal?
A
That
goes
in
terms
of
what
the
code
looks
like,
as
well
as
like
what
the
user
interface
looks
like.
We
were
also
talking
about
how
a
commerce
package
for
backdraft
might
be
a
single
module
that
is
rather
than
a
suite
of
like
50
modules
or,
however,
many
are
in
commerce
where
you
can
pick
and
choose
which
once
you
want
on
and
off
I'm
kind
of
facing
that
same
thing
for
some
of
these
smaller
kinship
projects
that
usually
provide
2
or
3
contribs
modules,
where
it's
like.
A
Why
don't
we
just
package
that
together
and
make
it
one
like
you,
have
one
flex
slider
module,
rather
than
it
flips
letter
fields
and
flex
later
views,
so
just
trying
to
kind
of
think
about
like
what?
What
does
that
module
look
like
in
a
backdrop
world,
rather
than
in
a
drupal
world
I?
Think
it's
going
to
be
a
fun
fun
exercise
for
all
its
of
us
global
or
maybe
not
I
like
to.
A
Would
love
to
have
some
kind
of
like
full
width
image
element
in
core
I'm,
not
sure
I
mean
and
I
would
love
to
see
if
we
can
get
that
into
1.4
as
part
of
our
new
like
home,
page
layout,
I,
think
that
would
be
fantastic,
then
I
think
will
be
easy
to
change
that
in
the
future
to
say
like
it's
either
a
full
imager,
it's
a
slider,
I'm
I,
don't
know
how
the
JavaScript
part
would
work
like
if
we
want
to
let
people
choose
what
javascript
library
is
driving
that
slider
or
not
I,
don't
know
native.
C
Well,
if
we,
if
we
had
a
slider,
we
would
need
to
ship
with
some
core
library
and
I.
Think
that
we
would
end
I
was
I
was
suggesting
that
we
did
this
in
tech
for
menu
dropdowns,
that
we
ship
with
some
option
in
core
and
that's
the
only
option
that's
available
and
then
yeah.
If
you
have
another
library,
then
a
select
list
becomes
available
for
you
to
choose
your
library,
but
otherwise
it's
hidden
sort
of
thing,
but
yeah.
C
Also
gets
us
into
the
like
URL
less
entity
type
like
whatever.
That
would
be
to
be
items
within
the
slideshow,
because
this
probably
wouldn't
be
nodes,
so
yeah,
it's
yeah.
It's
definitely
interesting,
but
I
think
for
the
next
version
will
probably
start
with
just
an
image.
Yeah
start
with
an
image
in
the
new
theme,
like
some
kind
of
banner
and
then
slide
shows,
will
be
later
yeah.
A
G
Question
from
Doug
van
as
anybody
planning
on
going
to
Texas
camp
April,
one
and
two
no
I
didn't
even
have
it
on
my
calendar
yeah.
It's
maybe
a
secret
because
it
I
found
it
by
mistake.
But
I
have
a
couple
things.
I
can
do
in
that
area,
so
I'm
think
about
piggybacking.
On
that
I
didn't
expect
anybody
was
going,
but
I'll
do
what
I
can
to
it's
backdrop
in
there
as
well
as
opportunity
arises,
which
I
think
it
will.
G
Secondly,
I
did
retweet
the
Drupal
easy
podcast
link
from
a
couple
hours
ago,
with
the
mission
backdrop
and
George
demit
responded,
saying:
I
have
not
listened
to
the
podcast
yet
but
I'd
love
to
see
a
showcase
of
sites.
Running
back
drop,
so
I
know
it's
all
our
agenda,
but
does
anything
informal
we
could
do
in
short
term
yeah.
A
A
B
A
blog
post
on
the
website
with
a
couple
of
ones
that
we
know
about,
encourage
other
people
link
to
it
in
the
comments.
Oh
wait,
you
have
comments,
we
don't
have
comments
yet
well,
we
get
bigger
than
out
now.
You
can
write
a
post
and
I
tell
people
to
tweet
us
if
they
have
additions
and
we
can
add
them.
Yeah.
G
F
A
A
I
can
probably
write
like
a
one-paragraph
post.
It's
like
hey,
we
wanted
to.
You,
know,
establish
a
list
of
sites
that
are
built
with
backdrop.
Anyone
who
has
one
said
one
and
I
think
as
long
as
we
can
get
like
five
for
the
initial
post.
That's
probably
enough,
and
then
we
can
say
please
Like,
Tweet
or
comment
or
whatever
send
us
more
information
about
sites,
you've
built
and
then
that'll
be
like
a
good.
You
know
interim
solution
until
we
can
get
an
actual
showcase
up.
A
Excellent,
okay,
good
idea.
Alright,
so
you
mentioned
Texas
camp.
It
wasn't
on
my
list,
I
didn't
know
about.
It.
Definitely
does
let
us
know
if
you
get
a
session
in
there
about
back
Shepherd,
not
on
the
calendar.
We
do
have
I
not
this
weekend,
but
next
weekend
sand
camp
with
the
first
full
day
back.
Rub
training
then
marched
for
through
fifth,
we
have
drupalcamp
loot,
well,
drupalcamp
Utah,
with
low
abouts
Jared
bitten
are
doing
a
procession
I
session
on
backdrop
mid
camp
in
Chicago,
as
March
19
through
22nd
I
know.
A
We
have
a
lot
of
people
who
are
going
Jim,
birch,
Annie,
Doug
van
me
and
I
have
been
guilt
tripped
into
thinking
about
going,
not
intuitions,
yet
the
place
to
do
the
showcase
of
sites
filled
with
backdrop.
If
anyone's
looking
for
a
session
idea,
I
know
I,
think
Wes,
you
might
have
already
submitted
one
there
Texas
camp
April
worse
than
second,
that
Doug
just
mentioned
drupalcamp
Guadalajara,
April,
seventh,
through
ninth,
have
reached
out
to
us
today
try
and
get
involved,
and
if
anyone
wants
to
go
to
Mexico,
that's
probably
gonna
be
really
fun.
A
Drupalcon
New
Orleans
may
nine.
Through
13th
last
few
weeks
we
talked
about
maybe
trying
to
submit
a
session
again
I
think
we
have
a
couple
of
angles
if
it's
not
like
hey
Drupal
people.
This
is
backdrop
if
it
was
something
like
how
to
collaborate
across
different
health
and
source
projects
or
something
that
was
more
warm
and
fuzzy
and
less.
Let
us
tell
you
about
the
dark
side.
I
think
that
might
have
a
shot
of
getting
in
and
I
also
think
if
it
included
people
other
than
myself
a
neat
that
might
be
more
interesting.
A
So
it
was
like
coming
from
the
more
of
the
community
and
loss
of
us
I
think
that
would
probably
also
do
well
so
I,
don't
know
who
is
planning
on
going
to
Drupal
con
New
Orleans,
but
we
definitely
should
brainstorm
ideas
about
what
a
session
might
look
like
that
might
get
accepted,
might
not,
but
could
be
a
fun
exercise
anyway.
A
Semicon
which
is
coming
up,
May,
June,
I'm,
not
sure
if
they
have
a
date.
Yet
we've
been
asked
to
go
and
talk
about
backdrop
is
V
serum,
so
that
would
be
fun:
Twin,
Cities,
drupalcamp,
jun,
20th
through
23rd
PHP
summit,
mexico,
kid
city,
September,
24th,
lots
of
stuff
coming
up
on
the
calendar.
It
is
drupalcamp
season
everybody's
starting
to
get
organized.
So
definitely,
if
you
guys
have
other
cancer
conferences,
you're
going
to
be
attending
more
people
want
to
hear
about
that
job.
Or
you
want
to
talk
about
backdrop.
A
Okay,
well
then,
let's
break
go
back
to
the
issue.
Queue
do
a
lot
of
work.
If
anyone
needs
books
on
Drupal
our
drug
books
on
backdrop,
you
can
check
with
a
press,
they
have
a
migrating
from
Drupal
de
backdrop,
but
that's
out
now
and
they
will
have
a
beginning
backdrop
book
that
hits
shelves
second
quarter
2016.
Otherwise,
thank
you
guys
all
for
coming
to
the
meeting
and
watching
and
doing
all
the
fantastic
things
that
you
guys.
Superb
actor,
we'll
see
you
next
week,
hey
thanks.