►
From YouTube: Backdrop CMS weekly meeting
Description
Weekly check-in on Backdrop status,
A
We
are
on
air,
it
is
thursday
October
29th,
we
are
all
recovering
from
bad
camp.
Some
of
us
are
recovering
by
camp
and
spirit,
if
not
recovering
from
backing
up
in
person,
but
went
really
well.
We
had
our
first
backdrop
summit,
which
I
thought
was
super
exciting.
We
had
probably
25
people
in
and
out
all
day
learning
stuff
sharing
stuff.
A
It
was
a
very
successful
event
we
had
a
bunch
of
who
were
super
super
interested
and
ed's
asked
a
lot
of
really
great
questions,
and
then
we
had
a
lot
of
kind
of
super
technical
answers
which
I
hope
did
not
deter
the
people
who
are
not
interested
in
technical
details,
but
that
was
a
whole
lot
of
fun,
so
we're
happy
to
have
survived
and
had
a
very
successful
initial
backdrop
event.
So
general
announcements
today,
our
t-shirts
and
hoodies-
are
here.
A
If
you
guys
I'm
sure,
if
you
can
see
this
I'm
wearing
back
dog
t-shirt,
it's
white,
but
it's
like
a
heathered
white.
So
it's
like
a
soft
super
soft
material,
but
it's
white
with
little
gray
fuckles,
which
is
pretty
nice,
and
it's
got
our
favorite
dragon
the
jar
up
on
it
and
then
there's
also
these
super
soft
hoodies,
which
is
the
same
material
from
a
bad
Kim
2013.
A
A
Good
as
a
dragon
on
the
back
and
they're
really
comfortable,
and
if
you
want
one
for
yourself,
you
can
go
to
backdrop.
Cms
networks
watch
contribute
and
it's
$25
if
you
want
a
t-shirt,
fifty
dollars
for
a
hoodie,
and
that
includes
the
cost
of
shipping.
So
if
you
weren't
able
to
make
it
to
bad
camp,
we
can
send
it
to
wherever
you
are.
Those
are
donations
to
back
Joe
Foundation,
which
will
then
help
us
pay
for
servers
and
hired
designers
and
do
all
the
stuff
that
we're
supposed
to
be
doing
that
apparently
costs
money.
A
So
that's
what
that's
for.
We
bought
a
ton
of
them,
so
we're
hoping
that
they'll
last
for
in
a
whole
year
last
year
we
bought
a
couple
of
t-shirts
for
various
events
and
they
were
all
gone
by
the
end
of
said
event,
and
then
everybody
wanted
a
dragon,
so
we
needed
new
ones
anyway,
so
we
got
a
whole
bunch,
hopefully
the
last
as
long
as
you
guys
want
them,
but
we
will
be
taking
them
with
us
as
we
parade
around
the
country.
Two
very
separate
events
can
also
get
them
in
person
Oh
t-shirts.
A
T-Shirts
are
also
free
to
backdrop
contributors,
so
if
you're
on
this
call
you're
likely
backdrop
contributor
and
if
you
have
participated
in
issue
queue
or
written
any
patches
or
rim
or
finding
modules,
we
definitely
are
happy
to
extend
t-shirts
to
you
guys,
depending
on
where
you
live.
We
can
probably
also
include
shipping,
I
would
say
anywhere
in
the
u.s
outside
US-
will
have
to
look
up
how
expensive
that
is,
but
we
would
like
to
get
you
dragon
shirts
if
you
want
dragon
trips.
A
So
let
us
know
anyone
who
watches
this
video
later,
who
wants
one
send
an
email
to
info
backdrop
CMS.
If
you
can't
find
out
how
to
get
one
on
your
own,
we
can
definitely
hook
you
up
with
soft,
comfortable
dragon,
loot,
okay,
other
announcements,
as
usual,
drupalcamp
Utah,
which
was
been
announcing
for
the
past
few
weeks,
was
the
same
weekend
as
sand
camp
has
moved
its
dates.
A
I
do
not
want
to
beat
people
choose
between
sea
and
ski,
so
the
new
event
dates
are
now
March,
fourth
and
fifth,
and
they
are
still
looking
for
talks
on
backdrop.
So
if
you
want
to
go
to
both
the
ocean
and
this
ski
land
mountains,
you
can
do
that.
We
also
have
create
free,
PHP
stored
licenses
for
backdrop
kinship
developers.
So
if
you
have
joined
the
backdrop,
contribute
and
are
working
on
or
are
working
on
any
particular
core
issues,
we
can
get
you
a
backdrop
or
phpstorm
license,
but
send
an
email
to
info
backdrop.
A
B
Yeah
sure
I
would
love
to
so.
It's
been
two
weeks
since
our
last
meeting,
because
last
week
was
the
backdrop
summit
at
bad
camp,
which
went
awesome
as
Jen
said,
and
it's
been
a
pretty
productive
past
couple
of
weeks.
In
the
backdrop
ecosystem,
we
now
have
60
s
are
sorry
166,
total
projects
for
backdrop
CMS,
in
the
backdrop,
contribute
hub
group.
That's
five
new
projects
since
our
last
meeting
so
awesome
that
we're
still
just
chugging
along
porting
modules,
every
which
way
or
writing
me
once
we
love.
We
love
new
modules.
B
There
are
91
official
log
and
91
official
projects
on
backdrop,
CMS
org.
That
discrepancy
is
because
all
of
github
is
just
every
project
that
has
been
ported
to
backdrop
that
might
not
be
yet
ready
for
production
and
then
the
modules
that
are
ready
for
production
or
stable
enough
get
tagged
with
official
releases
on
github
and
when
you
make
an
official
release
on
github,
it
synchronizes
over
the
backdrop
CMS
Borg.
So
there
are
two
new
projects
since
I
last
meeting,
which
we're
very
excited
about
even
more
exciting
than
a
new
projects
is
new
contributors.
B
It's
actually
pretty
I
mean
those
things
are
kind
of
correlated,
because
we
normally
ask
people
to
port
a
module
or
write
the
module
in
own
personal
github
account
so
that
we
can
do
a
basic
review
and
then
we
review
it
and
then
they
move
their
project
into
the
official
contribute.
So
three
of
those
new
total
projects
were
written
by
are
three
new
contributors.
So
that's
really
awesome.
B
Welcome
guys
into
the
backdrop
ecosystem
and
more
really
happy
to
have
some
new
contribute
if
you're
interested
in
joining
the
backdrop,
contribute
porting
module
or
theme
or
running
new
one.
There's
a
group
that
we
have
a
repository
we
have
specifically
for
requesting
that
you
grant
get
access
to
the
contribute
and
that
is
it
github.com
/
backdrop
dash
ops,
/,
can't
rib,
and
that
is
an
issue
queue
basically
used
specifically
to
in
some.
B
Sometimes
we
talk
about
kinship
projects
that
need
to
be
ported,
but
mostly
we
talked
about
people
that
are
applying
to
join
the
backdrop,
contribute
and
get
access
to
that
group.
Also.
I
guess
I
mean
I
can
slide
this
in
here,
I
was
setting
up
permissions
on
the
github
backdrop,
contribute
recently
and
github
recently
redid
their
permission
system,
which
is
something
we
might
look
into
in
the
future
because
they've
made
it
so
that
now
you
can
have
/
repository
access
to
individual
contributors.
B
You
don't
need
to
set
up
individual
groups
anymore,
like
you
step
to
set
up
a
group
on
github
and
then
assign
the
permissions
to
the
group
and
then
put
the
users
in
the
group
which
was
kind
of
tedious,
because
if
you
had
a
large
group,
like
the
backdrop,
contribute,
then
you
couldn't
say
certain
authors
only
have
access
to
certain
repositories.
Just
said
to
say
everybody
has
access
to
all
repositories
or
you'd,
be
super
tedious
and
make
a
separate
group
for
every
single
repository,
both
of
which
were
really
painful
management
lies.
B
They
recently
upgraded
their
permission
system
so
that
they're
more
granular
now
and
we
can
assign
permissions
to
an
individual
user
/
repository
without
setting
up
a
group
first.
So
it's
it's
actually
a
pretty
useful
enhancement
where
we
can
say
like,
for
example,
Andy
originally
reported
the
webform
module
and,
let's
say
I
was
not
a
member
of
the
king
trip
group.
B
Andy
could
add
me
or
maybe
of
the
other
maintained
yrs
from
web
form
and
grant
them
right
access
just
to
the
webform
module
without
giving
them
access
to
all
of
the
other
modules
in
the
control
group.
So
it's
kind
of
exciting
that
you
know
get
up
is
moving
towards
more
grainy
Oh
permissions
and
sites
that
we
didn't
have
to
do
when
you
work
for
that.
But
we
will
need
to
ultimately
integrate,
probably
those
permissions
with
backdrops
EMS
org.
B
Once
people
can
create
user
accounts,
then
potentially
they
could
start
managing
access
to
the
repositories
from
backdrop
CMS
org,
and
we
can
send
that
information
over
to
github
just
some
ideas
anyway.
It's
great
infrastructure
is
improving
without
any
work
on
behalf
and
we
love
it
when
that
happens.
B
Speaking
of
infrastructure,
that's
always
the
next
item
on
the
agenda,
so
infrastructure
tasks,
some
things
that
we're
trying
to
work
on
around
our
flagship
website
and
just
in
general
the
backdrop
eco
system,
update,
checking
for
backdrop
CMS
the
thing
that
tells
you
when
new
versions
of
controls
and
newer
versions,
backdrop
are
available,
that's
been
working
for
a
long
time.
There's
some
interesting
work
going
on
in,
in
the
backdrop
suq
around
making
notifications
better,
which
would
be
a
really
interesting
thing
to
improve,
to
make
it
so
that
you
know
when
your
site
has
new
updates.
B
Instead
of
like
yelling
at
you
at
the
top
of
every
single
page
of
the
administration,
section
we're
looking
at
doing
things
like
putting
a
little
like
notification
badge
in
the
admin
bar
instead,
so
rather
than
yelling
at
you
all
the
time,
maybe
they
just
like
a
red
number
one.
If
there's
one
critical
update
in
your
admin
menu,
so
that
way
you
would
go.
Oh,
maybe
there's
something.
I
should
look
at
up
there
and
then
go
to
your
status
report
or
go
to
your
available
updates
page
and
see
that
you
have
updates.
B
You
need
to
apply
rather
than
yelling
at
you
on
every
single
page,
like
with
a
big
red
air,
so
that
would
be
an
interesting
issue
to
tackle
I.
Don't
have
the
issue
number
offhand,
but
I'll
put
that
in
the
agenda
once
I
get
a
second,
so
other
things
are
on
update.
Checking
our
analytics
aren't
working
quite
right
that
we
get
all
this
information
from
all
of
the
backdrop,
sites
that
are
out
there
and
we
record
what
versions
of
all
modules
they're
running.
B
But
then
our
daily
number
crunching
script
just
throws
away
all
of
the
occurred
data,
and
it's
kind
of
sad
that
we
collect
all
this
stuff
and
then
we
just
throw
it
all
the
way
because
our
script
is
broken.
So,
if
you'd
like
to
take
a
look
at
that,
there's
an
issue
in
project
module
which
powers
the
usage
statistics
in
the
contribute
to
try
to
figure
out
what's
wrong
with
that
script,
that's
issue
number
nine
in
the
project
issue
queue
let's
see,
and
we
would
like
long-term
to
collect
information.
B
Besides,
what
modules
are
running
like
if
you
have
clean
urls,
turned
on
or
off
for
other
things
like
that
and
we'd
like
to
add
charts
as
soon
as
we
get,
that
usage
did
actually
collecting
correctly
and
charts
to
it.
So
you
can
see
a
nice
pretty
graph
of
the
increased
usage
of
your
modules
over
time.
A
I
was
just
rereading
that
issue.
I
know.
Last
week,
Jeff
tried
it
out
that
little
fact
that
we
had
in
the
queue
for
getting
it
running
and
it
looks
like
you
were
able
to
get
a
modules
downloading
in
cash
clearing,
but
still
no
database
connection,
but
that's
funny
ways.
There's
no
database
connection
of
how
can
it
clear
database
tables
I,
don't
know
anyway.
A
A
Short-Term
I,
don't
think
it's
helpful
to
us
long-term
to
try
and
figure
out
what
we
need
to
change,
but
I'm
gonna
look
through
them
anyway
and
see
if
there
isn't
anything
in
there
that
we
need
to
put,
in
our
backdrop,
Josh
loader
that
maybe
would
help
get
things
going.
So
I'll
take
a
look
at
that
today
and
see
if
we
can't
move
that
forward.
I
did
not
actually
get
to
spend
any
time.
Greg
Anderson
at
bad
camp,
except
for
at
dinner,
going
to
Ethiopian
food
is
fantastic,
but
we
were
not.
A
Our
fingers
were
messy
when
you
eat
Ethiopian
food,
so
that
does
not
make
for
good
typing.
So
we
didn't
actually
make
any
progress
on
getting
Josh
going
for
backdrop,
but
I
will
follow
up
with
him
now
and
see.
Maybe
we
can
set
up
a
time
to
like
meet
at
the
Pantheon
office
and
work
on
it
for
an
afternoon.
I
think
that
would
probably
be
a
good
plan
to
try
and
figure
out
short-term
versus
long-term
plans.
A
Should
I
carry
on
so
other
things
we're
working
on
for
backdrop?
Infrastructure
include
our
primary
website
and
now
that
we
have
much
asleep
some
layouts
appearing
there.
We
also
want
to
start
to
allow
people
to
login
to
the
website
and
do
things
like
edit
their
projects.
So
if
you
are
contributing
or
you
can
edit
the
project
page
for
that
module,
if
you
wanted
to
add
something,
we
also
want
to
add
at
once,
you
are
allowed
to
log
in
are
things
people
can
do.
A
They're
like
hosting
websites,
they've
been
working
on
into
glared
showcase
or
listing
themselves
as
a
backdrop,
service
provider
and
so
I
think
it
would
probably
be
good
to
start
thinking
about
how
to
start
supporting
our
community
a
little
better
with
our
own
website.
I
personally
want
to
see
a
single
sign
on
there
with
github
as
well.
A
So
all
of
our
people,
who
already
have
accounts
with
github,
don't
need
to
worry
about
creating
new
accounts
on
backdrop
website,
but
for
people
who
aren't
developers
I
think
it's
still
nice
to
give
them
something
to
feel
like
they're
joining,
even
if
they
aren't
already
on
get
so
I
can
link.
Will
try
and
get
a
way
to
link
those
up
later?
A
Other
things
we
have
I
guess
on
our
agenda,
for
the
main
website
include
like
an
event
calendar,
so
we
don't
have
to
keep
using
our
google
feed
and
job
boards,
and
I
think
it
would
also
be
good
to
look
out
the
other
stuff.
That's
worked
really
well
for
a
Drupal
community
and
plan
on
putting
those
up
for
the
backdrop,
communities
off
back-to-back
trap.
Backdrop
itself
at
our
next
release
is
doc
drop.
One
point
two
point:
three,
which
is
kind
of
exciting
number
wise
and
we
had
it
looks
like
740
and
I.
A
A
Annoying
even
released
you,
but
ok,
so
741
we
get
ignored,
I
just
removed
that
so
yeah
I
would
say.
We
should
look
at
what
went
into
740
and
see
if
we
can
roll
some
of
those
patches
into
the
next
backdrop
release.
We
have
a
couple
of
you
know
handful
bugs
in
backdrop.
We
could
also
nick
say
that
the
same
type
of
way
lenok
when
nothing
that
is
mission
critical
needs
cat
urgently
for
our
next
minor
release,
which
is
1.3,
which
is
supposed
to
come
out
on
january
fifteenth.
A
This
is
a
user
experience
and
clean
up
release,
so
we've
added
a
bunch
of
new
features
into
backdrop.
We
need
to
spend
some
time
making
sure
those
features
are
quality,
making
sure
our
product
is
easy
to
use
and
also
cleaning
up
some
stuff
that
was
just
left
over
and
was
a
little
achy
from
Phoebe
previous
versions
of
Drupal.
A
We've
got
a
great
metalist
if
you
want
to
look
at
the
github
issue,
tracker
milestone
for
1.3
point
Oh
of
things
that
are
bothering
people
that
we
want
to
get
into
that
release,
and
the
agenda
for
today
shows
a
handful
of
those
I.
Follow
up
for
the
layouts,
which
is
a
new
feature
we
put
in
follow-up
for
the
rich
text
editor,
which
is
a
new
feature
we
put
in
trying
to
improve
the
field
UI,
which
is
something
that's
been
problematic
since
Drupal
6.
A
Getting
that
cleaned
up
would
be
fantastic
I'm
trying
to
get
the
views
you
I
to
be
better
more
responsive,
I.
Think
there's
been
a
little
bit
of
work
going
on
in
that
interval.
Eight,
we
could
look
at
see
what
it
is
they're
doing
if
we
want
to
do
the
same
I'm
getting
our
last
administration
views
converted,
I.
Think
the
last
one
left
is
the
comment,
view
and
I
think
the
block
are.
A
There
is
making
sure
that
we
get
the
bulk
operations
working
for
comments,
and
then
we
have
a
little
clean-up
on
the
menu
you
I,
although
there's
some
debate
about
how
that
should
actually
be
done,
a
same
thing
for
a
couple
about
their
interfaces.
I
think
menu,
I
inuu
is
similar
to
field
UI
and
there
were
I,
don't
know
what
famous
we
came
and
compare
about
implementations
and
one
that
we
could
share
with
the
other
and
then
just
trying
to
get
our
terminology.
A
Correct
I
felt
a
bunch
of
issues
a
couple
weeks
ago
about
trying
to
clean
up
editing
configuring.
Some.
Those
might
still
need
some
more
work,
but
I
think
will
be
great
if
we
can
clean
up.
I
would
also
like
to
see
in
a
nut
sure
if
we
have
an
issue
for
this,
but
getting
the
admin
menu
fixed
so
that
it
doesn't
say
list,
it
would
actually
say
what
it's
listing.
I
think
I,
think
I'll
fine
I'll,
try
and
find
that
and
tie
it
for
the
release.
A
I
think
I
think
there
is
an
issue
because
we
worked
on
in
a
while
ago.
We
already
made
some
some
improvements,
but
there
are
some
other
ones
worth
like
when
I
show
this
to
site
to
someone
for
the
first
time:
I'm
like
oh,
oh,
that's,
embarrassing
and
I
love
I
would
love
to
get
rid
of
the
oh
that
that's
embarrassing
moments
for
people
who
aren't
already
familiar
with
Drupal,
don't
already
know
their
way
around.
The
UI
just
gonna
make
a
little
more
to
it
for
the
next,
a
minor
release
that
comes
after
13
14.
A
This
is
the
one
that
scheduled
for
May
fifteenth.
We've
already
started
to
talk
about
the
kind
of
features
that
we
want
to
include
in
that,
since
we
aren't
going
to
be
including
features
in
the
1.3
release,
and
the
first
thing
I
think
that
we
should
I
worry
about,
is
figuring
out
how
to
deal
with
references.
We
have
texana
midterm
reference
and
core.
We
have
user
reference
and
node
reference
and
the
references
module
it's
important
to
backdrop
and
then
the
adopted
solution
for
Drupal
has
an
entity
reference
module.
A
It
took
a
little
look
at
the
code
that
was
inside
there
and
decided.
That
was
not
the
way
we
wanted
to
go
with.
The
code
but
I
think
it
is
the
way
we
want
to
go
with
a
feature,
so
it
would
be
good
to
think
about
how
to
get
the
feature
we
want
out
of
the
code
that
we
have
and
see.
If
we
can't
build
a
UI,
it
works
more
like
entity,
reference
in
and
and
the
code
that
looks
more
like
references,
so
I
don't
think
it's
going
to
be
too
hard.
A
References
is
already
kind
of
abstracted
into
like
a
reference
type
and
are
a
reference
base
and
then
a
reference
for
nodes
and
orphans
for
users.
We
can
do
the
same
thing
reference
for
term
and
make
sure
we
have
a
consistent
interface
that
lets
us
choose,
which
1i
think
all
the
features
are
there.
We
just
need
to
work
on
cleaning
up
the
these
are
base
to
make
that
work.
We
also
talked
a
little
bit
about
adding
a
redirect
like
functionality
into
core
and
I.
A
Think
getting
global
redirected
is
going
to
be
something
we
can
handle
in
1.3
if
we
were
able
to
get
that
done
in
time,
I
just
kind
of
use.
Your
experience,
task
of
like
oh
I,
changed
the
alias
and
now
my
I
can't
get
to
my
content
for
my
own
cold,
where
else
I
think
getting
that
in
would
be
great,
I
think
also
doing
like
clean
URL
redirects
would
be
good,
I'm
not
sure
about
the
rest
of
redirect
module
like
a
UI
that
lets
you
see
the
listing.
Maybe
that
should
remain
separate.
A
Maybe
that
should
be
a
separate
modules
you
think
about
putting
in
one
for
a
nice
clean
with
people
to
manage
those
having
them
appear
on
the
node
page,
that
you
can
see
your
list
of
aliases
in
your
list
of
redirects.
That's
something
redirect
module
provides
I,
don't
know
exactly
where
that
what
we're
going
to
come
down
on
that
in
terms
of
how
much
should
mean
forum
what
should
be
left
to
contribute
how
to
make
that
whole
process
easier
for
people
to
figure
out
what
their
redirects
are.
A
So,
let's
keep
that
in
our
minds
for
1.4
as
well
and
as
you
guys
are
building
sites
with
backdrop.
We
should
take
a
look
at
the
controls,
the
ones
that
are
being
used
most
often
and
see.
If
there
are
other
things
we
should
move
into
core
are
there
have
been
a
couple
of
things
that
Nate
and
I
have
talked
about
like,
for
example,
slideshows,
there's
lots
of
different
ways
to
do
slideshows
and
Drupal
there's
none
of
them
that
come
out
of
the
box.
A
We
could
set
up
some
kind
of
slideshow
library
interview
and
shift
that
as
part
of
our
home
page
layout,
that
would
be
fantastic
for
people
just
go
a
little
log
in
didn't
change
that
going
the
way
they
wanted,
but
there's
a
little
bit
of
a
debate
over
how
complicated
that
needs
to
be
like
I
would
vote
for
flex
slider,
but
flex
letter
has
an
entirely
separate
user
interface
for
configuring,
your
sliders
and
having
different
formats
for
each
of
them,
and
is
that
too
much
for
like
a
simple
use
case
in
four?
Should
we
choose
something?
A
That's
just
you
know
a
JavaScript
application
to
a
particular
view
with
no
settings
I
don't
know
it's
definitely
up
for
debate,
I
think
getting
getting
some
information.
What
people
are
actually
actually
doing
with
their
back
job
sites
would
also
be
really
useful,
so
think
about
that
as
you're
working
and
we
can
plan
for
men
all
the
time
we
are
trying
to
work
on
user
experience
and
developer
experience.
A
Our
next
release
is
focused
particularly
on
user
experience,
but
if
we
have
issues
that
are
ready
before
1.3,
we
can
put
them
in
at
any
time
long.
Cisco
isn't
too
large
something
like
a
new
field.
You
I
will
probably
wait
to
1.3,
but
something
like
a
terminology
update
can
go
in
anytime,
so
trying
to
get
a
user
experience
improved.
A
If
we
are
going
to
be
moving
down
market
from
Drupal
and
of
trying
to
appeal
to
the
average
PHP
developer,
we've
got
to
make
this
offer
more
intuitive
for
everyone.
So
noting
the
places
where
it's
not
and
finding
a
way
to
fix
it
is,
is
going
to
be
important
for
us
longer
all
right.
There
are
tags
on
github
for
both
user
experience
in
developer
experience
issues,
but
instead
of
using
milestones
we're
using
like
square
brackets
in
the
title
with
you
x
or
DX
and
developer
experience
issues.
Are
you
know?
A
Phim
experience
is
the
same
thing
for
us
all
developers
developers
so
anything
that
you
find
odd
in
in
any
part
of
the
system
just
type
with
DX
and
what
else
we
have
going
on
here
as
sprint's,
so
every
Thursday,
usually
after
this
meeting,
we
are
in
IRC
working
on
back
up
together.
If
you
don't
have
a
Thursday
or
you
can't
give
up
any
extra
time
on
a
Thursday
and
you
want
to
work
on
packed
up
any
other
time.
That's
also
great.
A
We
love
people
who
work
on
backdrop
whenever
they
work
on
back
job,
but
you
will
often
find
a
lot
of
people
working
on
bactrim
on
Thursday.
So
if
you
need
to
chat
about
something
figure
out
something
philosophical,
it's
good
to
get
a
lot
of
feedback
on
Thursdays
we
meet
in
IRC
and
our
channel
pound
backdrop.
We
also
are
very
active
on
the
github
issue
queue
and
for
those
of
you
who
are
not
comfortable
either
on
github
or
on
IRC.
We
do
have
a
reddit
channel
and
hopefully
soon
we'll
also
be
able
to
add
a
backdrop.
A
A
A
A
A
Anyway,
I
don't
remember,
but
it's
the
November
10th
I
think
remember
10
through
12
middle
of
the
week,
and
then
we
have
nothing,
probably
through
the
entire
month
of
December,
but
in
February
we
have
sand
camp
and
emerge.
We
have
drupalcamp
Utah,
and
these
are
all
events
that
are
dribble
events
with
people
who
are
they're
interested
in
learning
about
our
talking
about
backdrop.
A
If
you
want
to
attend
it's
a
safe
place
for
you
to
offer
a
session
on
these
subjects,
we
have
in
fact
a
couple
people
requested
sessions
specifically
on
backdrop
at
drupalcamp
in
San
Diego
we're
going
to
be
doing
a
backdrop,
training
which
it
will
be
exciting,
I
think
we're
going
to
do
a
full
day
last
year
and
a
half
day
this
year
will
do
a
full
day
on
dr
phoenix.
That
could
be
the
second
ever
backdrop,
training
event,
which
could
be
really
I'm
excited
about
it
so
yeah.
A
If
you're
interested
going
to
dribble
vincent
talking
about
backed
up,
there's
still
a
bunch
where
that
can
happen
and
we'll
try
and
gauge
the
size
of
our
community
again
next
year
and
see,
if
maybe
it's
time
to
do
a
backdrop
only
event,
but
for
now
I
think
it's
all
the
same
community.
We
should
still
be
showing
information
together,
laying
out
a
dribble
lens
for
well
I.
Think
that's
all
I
had
on
my
list.
It
looked
like
we
had
a
couple
questions.
B
There's
not
too
much
going
on
we're
really
just
kind
of
chatting.
Okay
Mike
said
he's
interested
in
dealing
with
references
for
helping
with
references,
which
is
also
we
go
a
little
while
before
that
needs
to
happen.
If
we're
targeting
1.4,
but
it
would
be
great
to
see
sand
things
start
developing
the
contribs
face
and
then
iterating
on
that
and
then
moving
the
court.
B
B
Ok,
maybe
work
on
that
today
and
I'll.
Look
at
you
rush!
Oh
ok,
all
right
thanks!
Everybody
I,
really
appreciate
everybody
coming
and
joining
lots
of
yours.
Lots
of
participants
this
week
feel
free,
like
you
guys.
Can
all
these
meetings
are
public
meetings,
because
you
can
actually
say
things
if
you
so
so
desire,
so
otherwise
things
are
ready
for
dropping
in
live
and
thanks
everybody
for
watching
have
a
great
week.
Have
you
back
to
update.