►
From YouTube: Backdrop CMS weekly meeting 11/12
Description
Weekly check-in on development tasks.
A
Alright,
we
are
on
air,
it
is
Thursday
November
twelfth.
We
are
very
excited
to
have
this
meeting
for
some
reason,
not
in
particular,
but
something
going
on.
So
thank
you
all
for
coming.
I
want
to
start
off
with
a
quick
set
of
announcements.
In
general
we
have
dragon
t-shirts
and
hoodies
available.
If
you
go
to
backdrop
CMS
to
org
slash
contribute,
you
can
see
photos
both
of
them.
A
If
you
might
get
twenty
five
dollar
donation
will
send
you
a
dragon
t-shirt
you
make
a
fifty-dollar
carnation,
will
send
you
a
dragon
hoodie
if
you
are
back
to
have
contributor
already
you're
actually
entitled
to
a
teacher,
so
send
an
email
to
info
back
type
seemest
at
work,
and
we
can
get
one
in
meet
your
preferred
size.
Mailed
off
to
you.
We
have
a
drupalcamp
organizer
for
drupalcamp.
A
Utah
had
contacted
us
about
getting
backdrop
speakers
at
their
event
that
will
be
march
forth
in
fifth
grade
ski
time
and
utah
if
you're
a
nursing
going
there,
I'm
not
sure
what
they've
got
on
their
schedule
already,
but
last
I
heard
they
were
still
interested
in
getting
backed
up
people.
So
if
you're
interesting
going,
that
could
be
fun
and
then
we
also
have
free
phpstorm
licenses
for
backdrop
kinship
developers.
B
There
we
go
yes,
so
let's
see
some
things
happens
this
week.
So
we
talk
about
new
projects
that
have
been
popping
up,
whether
ported
or
new,
into
the
backdrop
community,
and
we
currently
have
a
total
of
a
hundred
and
sixty-eight
total
projects,
including
modules
themes
and
layouts
available
for
backdrop
that
are
available
off
of
the
github
backdrop,
Ashton
trib
group,
one
new
module
published
since
last
week,
thanks
Andy
for
that
they
to
see
at
least
we
have
one
module
to
report
we
didn't
an
hour
ago.
B
So
that's
one
good
thing
about
having
a
meeting
at
the
right
time.
Rather
than
early
is
in
that
window.
Somebody
came
up
with
a
new
module.
If
you
visit
backdrops
you
my
start
org.
B
That's
10
new
project
since
last
week,
which
is
pretty
bananas,
because
one
of
our
large
contributors
Jerome
finally
went
through
and
tagged
a
bunch
of
releases,
which
is
fantastic
lots
of
great
modules
in
there
that
now
I
finally
popped
up
on
the
main
website,
including
things
like
transliteration
views,
load
more
and
pathologic,
a
bunch
of
really
great
projects
that
we're
really
happy
to
see
on
the
main
website.
Let's
see
I
also
let
it
be
interesting
to
start
counting
the
number
of
releases
that
we
have,
which
kind
of
reflects
the
amount
of
maintenance
that
happens.
B
So
new
point
releases
that
come
out.
There
are
a
total
of
128
releases
on
backup,
CMS
org,
which
right
now
doesn't
mean
a
whole
lot
other
than
several
projects
that
had
more
than
one
release,
but
we'll
see
you
next
week
how
frequently
modules
are
coming
out
with
new
releases,
basically
maintaining
their
current
code,
in
addition
to
just
making
new
modules
all
the
time.
B
Let's
see
we
have
42
total
authors
and
the
backdrop
contribute
if
you're
interested
in
joining
the
backdrop
contribute
to
have
you.
You
can
apply
to
the
group
by
visiting
github.com
/
backdrop
dash,
ops,
/,
can't
read,
and
that's
our
cue
where
we
manage
the
application
process
of
just
doing
a
basic
route
to
you
with
any
code
the
imported
and
you
can
go
through
the
process
and
get
access
to
the
backdrop
contribute
there.
B
Let's
say
we
still
have
this
item
in
here
for
update
status,
checking
which
has
been
working
for
a
really
long
time,
but
the
one
thing
that
hasn't
been
working
is
calculating
the
statistics
on
how
many
sites
are
out
there
and
what
modules
they
have
installed.
We've
been
accruing.
This
data,
but
our
number
crunching
script
hasn't
been
working,
and
so
we
don't
have
these
numbers
on
backdrop.
Cms
daughter
work
yet,
but
once
we
fix
the
script,
we
will
be
able
to
tell
people.
B
You
know
how
many
backup
sites
are
out
there
and
what
modules
they're
running,
all
of
which
would
be
a
really
useful
set
of
analytics
for
us
to
start
it's
calculating.
So
there's
an
issue
in
project
module.
Project
module
is
just
like
drupal.org.
The
module
we're
using
for
managing
what
projects
are
out
there.
What
releases
there
are,
but
ours
has
been
modified
to
substantially
work
with
github
instead
of
drupal.org,
but
in
project
module.
In
the
backdrop
intra-group,
there
is
one
issue
that
is
open.
B
It's
issue
number
nine,
and
that
is
that
that
is
the
analytics
not
occurring
correctly.
So
if
anybody
is
interested
in
working
on
the
issue,
you
can
set
up
a
local
version
of
project
module
or
if
you
want
you
can
reach
out
to
us
at
info
at
backdrop
CMS
org
and
we
will
set
you
up
with
the
database
dump
of
backdrop
semester
org.
So
you
can
work
with
the
real
data
and
try
to
get
those
numbers
calculating.
B
Once
we
get
update
status
analytics
working,
we
want
to
make
so
that
websites
will
start
reporting,
not
just
what
modules
they
have
installed,
but
also
what
features
or
functionality
they
have
turned
on.
So
we
can
tell
like
how
many
sites
out
there
have
clean
urls
turned
on
things
like
that,
and
that
will
make
it
so
that
we
will
have
better
numbers
to
guide
our
decisions
around.
What
features
are
eighty
percent
features
and
what
features
are
one
percent
features
and
what
should
be
removed
too
much
be
kept
and
and
so
forth?
B
Let's
say
that
is
issue
number
99
on
backdrop,
CMS
org
and
the
core
issue.
We
want
to
make
it
so
that
update
notifications
are
a
little
less
obnoxious
and
instead
of
screaming
giant
red
errors,
the
top
of
every
administrative
page
put
a
little
notification
icon
in
the
admin
bar
instead
and
that's
issue.
639.
B
That's
a
project
browser
server
as
we
have
it
right
now
has
a
bug
in
it
that
has
an
outstanding
pull
request
that
we
need
to
get
merged
in
then
deploy
to
the
live
site
to
make
it.
So
that's
the
contributes
to
our
server,
so
that's
been
waiting
on
a
pull
request
for
a
week
or
two.
Now
that's
that's
on
on
me,
but
if
anybody
else
is
interested
in
reviewing
that
pull
request,
that
would
be
super
useful.
The
main
issue
for
that
is
issue
870.
B
Let's
go
on
to
drush.
Josh
has
been
really
pretty
exciting
in
the
past
two
weeks,
we've
had
some
real
substantial
improvements.
There
josh
is
our
outstanding
longest
infrastructure
issue.
It's
issue
number
47.
In
the
backdrop,
issue
queue.
Basically
it's
been
there
since
the
beginning
of
time.
Since
the
beginning,
since
the
beginning
of
backdrops
existence,
we've
been
wanting
to
make
backdrop
work
better
or
work
at
all,
with
drush
and
in
the
past
two
weeks
that's
kind
of
become
a
reality.
B
B
Let's
see
whether
the
commands
drush
cron
dress
to
dress
sequel
commands,
drush
update,
DBZ
update
dot
PHP
we've
got
like
a
half
dozen
commands
that
are
properly
working
now.
Ind
rush
and
rush
can
identify
backdrop
and
tell
what
it
is
and
see
that
it
can
work
with
it,
and
it
knows
how
to
bootstrap
making
a
lot
of
really
great
progress.
There
I've
been
filing
more
issues
with
the
brush,
a
team
to
try
to
make
it
more
flexible,
because
right
now
the
approach
that
we're
using
is
really
kind
of
tedious.
B
We
basically
to
rewrite
all
of
the
commands
for
rush
into
backdrop
versions
which
isn't
ideal.
It
would
be
creative.
You
know
we
can
use
the
Drupal
7
version
of
commands
whenever
those
commands
were
totally
compatible,
but
really
as
I'm.
Finding
out
that
there's
really
not
a
lot
of
commands
are
like
100
person
compatible,
especially
if
you
turn
off
the
backwards
compatibility
layer
in
backdrop.
B
So,
but
we
can
still
do
better
things
to
make
it
so
that
we
have
less
work
to
do
by
making
it
so
that
Russia's
a
little
bit
more
a
good
at
using
what
code
it
can
reuse
and
then
only
swapping
out
the
parts
that
are
actually
different.
So
that's
been
really
beneficial
to
us
as
the
backdrop
project,
but
it's
also
been
really
pretty
beneficial
to
drush
as
a
project
for
managing
the
differences
between
Drupal
7
and
Drupal
8.
B
So
here's
hoping
that
we
can
continue
working
with
those
guys
to
make
drush
better
and
make
it
so
that
we
get
the
benefit
of
making
it
work
with
backdrop.
At
the
same
time,
if
you
want
to
follow
up
on
that,
we
read
about
it.
It's
issue
number
47.
In
the
main
backdrop,
issues
queue
which
I
think
I've
updated
just
as
of
this
last
couple
of
days,.
B
Yeah,
so
there's
a
working
prototype
right
now,
it's
in
my
personal
repository,
which
isn't
the
best
place
and
it
won't
be
where
it
stays
ultimately
but
yeah.
You
can
visit
quick,
Skinner,
sorry,
github.com,
/,
quick,
sketch,
/
backdrop
dash
brush
and
that's
the
preliminary
version
of
cases
in
the
jet.
The
preliminary
version
of
a
brush
that
works
really
pretty
well,
but
you
need
to
use
like
the
absolute,
very
latest
version
of
dress.
B
You
can't
even
use
like
the
light
the
last
release
candidate
that
they
made
you'll
need
to
actually
download
the
the
one
at
a
master
which
makes
a
little
bit
inconvenient
to
to
test
out,
but
but
it's
there
and
it's
working
meant
to
be
clear.
Bag
job
will
only
work
with
drush
8.
Once
drush
8
is
released,
it
won't
work
with
any
previous
version.
B
It
would
have
been
nice
to
make
it
work
with
josh
7,
but
I
think
that
the
dredge
team
is
totally
reasonable
and
in
wanting
to
only
support
the
latest
version
of
josh,
that
is
also
the
only
version
of
trash
that
will
support
Drupal,
8,
so
I
think
that's
fair
enough
and
a
triple-a
coming
out.
Next
week
that
right,
you
know,
the
demand
for
a
stable
version
of
Josh
to
be
out
is
going
to
follow
really
quickly
behind
that.
A
Right,
so
we
have
a
list
of
tests
that
we
want
to
work
on
for
our
website.
The
next
thing
on
our
list
is
to
get
user
logins
working.
We
feel
it's
nice
to
let
people
feel
like
they're
joining
something,
even
if
there
is
necessarily
anything
important
for
them
to
be
able
to
do.
They're
like
reation
keys,
not
give
up,
and
that's
the
number
one
thing
that
people
tend
to
do
on
drupal.org,
but
backed
up
semester
or
should
let
people
log
in
we
should
flex
the
profile
information
to
figure
out
who
our
people
are.
A
We
should
give
some
other
things
for
people
to
do
there
as
well
like
we
want
to
be
able
to
let
them
post
links
to
their
websites
into
a
showcase
who
want
to
let
people
list
themselves
as
service
providers
or
post
jobs
trying
to
find
and
hire
people.
We
want
to
have
event
calendar
so
event:
organizers
can
post
their
information,
their
central
location
for
going
to
go
to
find
out
where
they
can
hear
more
about
backdrop.
A
But
in
order
to
allow
any
of
that
stuff
to
happen
personally
have
to
let
people
log
in
so
working
on
now
is
taking
lucky
triple
dot,
org
and
figuring
out.
What
kind
of
information
really
worked
to
collect
from
jerboa
org
members
and
see
if
we
want
to
the
same
thing
for
people
on
it
backed
up
Cena
at
work?
A
We
might
also
look
at
other
example
sites
like
what
WordPress
does
for
their
developer
community
and
see
if
there's
information
that
ripples
not
connect
collecting
that
we
might
think
is
available
or
stuff
that
we
may
be
think
that
we
don't
need,
and
then
we
also
want
to
build
out
the
profile
page.
Have
it
designed
to
make
sure
that
it
looks
nice
for
people
who
get
there.
A
We
want
a
fairly
positive
first
impression
and
then
we
also
want
to
add
single
sign-on
so
that,
if
you
are
already
github
member
and
you
have
projects
that
you've
authored
or
are
maintaining
on
github
for
backdrop,
we
would
then
be
able
to
sync
those
two
together
recognize
who
you
are
and
allow
you
access
to
edit,
for
example,
your
project
pages.
On
that
backdrop,
zoomass
website.
So
that's
something
that
we're
working
on
I
think
what
the
action
item
we
have
right
here.
A
Next
and
I
would
love
it
if
we
can
get
that
at
least
ready
by
next
week.
But
I
feel,
like
the
design
part-
probably
isn't
gonna
be
done,
but
fairly
soon.
I
think
we
had
like
december
first
or
something
by
when
we
want
to
have
that
ready,
alright,
so
backdrop
itself,
our
next
bug-fix
release
is
going
to
be
version,
1.2
point
3,
which
is
a
cute
number.
Oh,
we
don't
have
anything
urgent,
Lee
scheduled
that
needs
to
go
into
that
release
there
in
any,
really
critical,
bugs
that
are
demanding
a
release.
A
Do
that
release
as
soon
as
we
cao
tall
of
the
patches
that
went
into
the
latest
version
of
Drupal,
which
was
740
essentially
get
those
merged,
and
that
might
be
a
good
time
to
cut
a
new
release
for
backdrop,
even
though
it's
not
particularly
urgent
and
the
next
minor
release.
One
point
three
point:
zero
currently
scheduled
for
january
fifteenth,
it's
going
to
be
usability,
focused
release,
and
so
we
have
a
pretty
large
set
of
issues
if
you
check
the
issue
queue
under
the
milestone.
A
One
point
three
point:
zero,
so
pretty
big
set
of
issues
we
want
to
get
done
by
then,
of
course,
most
of
them
don't
need
to
wait
until
1.3
to
be
merged
in.
We
can
merge
them
in
whenever
so
soon
as
they're
ready.
We
can
merge
them
and
include
them
in
whatever
release,
but
I
would
love
to
see
as
many
as
possible
of
those
get
done.
For
one
point
three
point:
oh
there
are
some
really
big
doozies
in
that
list.
Like
the
idea
of
redesigning
the
field,
you
I
and
we
know
it's
bad.
A
It's
been
bad
since
triple
six
trying
to
solve
that
problem
is
going
to
be
really
hard
and
it's
probably
going
to
require
rewriting,
maybe
the
entire
field
ey
module,
and
so
that's
something
that's
something
that
might
not
go
until
1.3,
but
anything
little
like
changing
terminology
from
edit
to
configure
restructuring
the
menu
you
I,
all
that
stuff
can
go
in
at
any
point.
I
think
it
will
be
good
to
have.
A
You
know
this
bullet
list
of
a
fairly
minor
but
important
issues
and
give
us
a
chance
to
just
go
back
and
say,
like
we
put
in
layouts
module.
We
know
it's
not
done
yet.
Let's
put
some
polish
on
what
we
have
there
and
make
it
more
complete
as
a
as
a
tool.
We
know
I
actually
spent
some
time
looking
for
earlier
this
week.
There
is
a
follow-up
issue
for
vyas
to
make
leu
I
responsive
I
couldn't
find
it
I,
don't
know
if
that
I
already
went
in
me.
A
That's
the
redesign
the
views
you
I
issue.
There
was
one
that
Wes
was
working
on.
That
was
just
to
take
them.
You
see
why
from
Drupal
7
and
make
it
responsive,
because
it
wasn't
oh
right:
okay,
I,
don't
know
if
that
one
got
done
already
and
I
was
just
looking
in
open
issues
or
something
but
I
couldn't
find
the
issue,
and
that
was
something
that
we
had
originally
scheduled
for
1.3,
but
I
think
an
entire
redesign
of
the
views
you
I
might
not
be
a
good
kidding
for
1.3
number.
One
is
really
hard.
Yeah.
A
We
could
test
it
out
and
we
could
then
you
know,
depending
on
how
well
that
works
and
how
soon
we
need
to
get
it
in
it
could
be
scheduled
for
like
include
this
in
tuna
X
or
before
that,
if
it
becomes
necessary
like
becomes
obvious,
if
it's
obviously
better,
we'll
put
it
in,
but
I
would
love
to
focus
on
field
dy.
First,
just
cuz,
it's
been
broken
longer,
but
we
can
see
how
that
goes.
A
Let's
see
so
yeah
long
list
at
one
point
three
also,
if
you're
just
interested
in
usability
fixes
in
general
search
the
issue
queue
for
square
brackets
with
you
x,
between
them
and
you'll,
get
a
much
longer
list
of
issues,
not
all
of
which
are
scheduled
for
one
point:
three
that
would
be
worth
focusing
on.
A
So
there's
a
ton
of
usability
issues
and
in
fact
up
there
were
a
ton
of
Drupal
or
obviously
starting
from
a
place
where
we
know
there's
room
for
improvement
and
any
of
those
can
go
into
any
time
to
those
don't
need
to
be
scheduled
for
specific
release.
If
we
get
a
good
polar
cost,
we
can
just
merge
it
for
most
of
them.
A
So
since
1.3
is
not
an
issue
that
will
include
any
major
new
features,
we're
also
starting
to
think
about
what
we
should
put
into
1.4
and
so
far
the
two
candidates
we
have
for
that
are
some
kind
of
references
module.
We
really
like
the
code,
that's
in
references
module,
but
we
like
to
feature
that
the
entity
reference
module
provide.
C
A
We'd,
fantastic,
yeah
and
I
think
that
that
you
know
that
that
is
the
kind
of
thing
that
we
could
put
into
1.4.
We
just
need
to
see
if
there's
a
way
that
we
can
get
the
taxonomy
term
reference
module,
that's
already
in
core,
also
into
that
which
might
make
things
a
little
bit
more
complicated
because
it
may
not
be
written
as
a
reference.
This
mystery.
C
A
So
I
think
I
think
what
makes
trying
to
say
is
that
it
shouldn't
be
hard
to
make
the
code
work.
The
way
we
want
we'll
just
need
to
my
point,
I
think
we
just
need
to
write
an
update
hook
for
anyone
who's
done.
It
term
reference
the
old
way,
if
it's
necessary
to
change
the
data
model
too
much
references
in
the
future
and
they
doing
just
remove
all
the
code.
That's
in
cornell
soon,
as
we
put
in
references
we've
got
that
problem
solved.
A
Another
way
I
like
removing
code
okay,
so
if
you're
interested
in
future
plans
for
a
backdrop,
we
do
have
most
of
this
busted
on
our
website.
Excerpts,
I,
messed
up,
org,
slash
roadmap,
I'm,
not
sure
we
have
the
1.4
items
on
there,
just
cuz
there,
it's
so
far
in
the
future,
we're
still
kind
of
abstractly
thinking
about
what
that
should
be,
but
in
general,
that's
where
we
like
to
post
what
we're
going
to
be
working.
A
The
problem
is
not
how
the
problem
was
actually
solved.
Let's
make
a
note
of
that,
because
those
are
the
places
that
people
who
are
new
to
the
project
in
the
future
are
going
to
find
pain.
It'll
be
really
nice.
If
we
could
solve
those
issues
by
either
making
it
easier,
adding
helper
functions,
better
documentation
just
to
try
and
help
people
get
over
the
learning
curve
we
already
know
Drupal
7
is
a
huge
one.
A
We
want
to
decrease
ours,
and
so
that
means
we
have
to
keep
our
eyes
open
for
places
where
we
can
actually
do
that.
I
feel
like
the
theme
layer
is
also
super
important,
because
most
web
developers
start
with
HTML
and
CSS.
They
don't
start
being
a
my
sequel,
query,
expert
and
so
I
feel
like
that
on-ramp
they're
like
getting
the
theme
layer
more
friendly
for
people,
it's
going
to
be
really
important
and
then
deep
digging
in
like
okay,
now
I've
written
themes,
I'm
going
to
write
a
module.
What
is
my
first
experience?
Writing
in.
D
A
Like
does
it,
you
know,
is
there
anything
really
weird
and
that
process
and
making
sure
that
we
can
kind
of
sort
that
out
and
make
it
a
more
approachable
system
to
anyone,
regardless
of
their
former
experience,
so
keep
your
eyes
out
for
that
create
issues
on
github
tag
them
with
DX
and
we'll
try
and
solve
those
problems,
mostly
probably
for
backdrop
to.
But
if
there
is
anything
we
can
do
a
backdrop
one.
A
We
hang
out
in
IRC,
we've
also
started
a
new
get
er
chat
account
for
backdrop,
which
is
which
is
pretty
exciting,
I,
actually
really
like
it,
because
anyone
who
is
participated
in
the
backdrop
issue
queue
automatically,
has
access
to
hang
out
and
chat
with
us
there,
which
is
pretty
nice
but
I'm,
curious
to
see
how
the
old-school
Drupal
people
or
used
to
IRC
are
going
to
take
to
it
anyone's
going
to
be
as
eager
to
hop
over
from
one
to
the
other.
A
But
we'll
see
you
at
four
me
get
her
feels
a
lot
like
slack,
which
I
also
really
like
in
that
it
like
e-mail.
You
if
you
miss
something
it's
not
very
prompt
about.
It
sometimes
find
out
two
hours
later
and
so
people
shouting
my
attention,
but
it
is
better
than
nothing
like
an
IRC.
If
you
miss
someone
trying
to
get
your
attention,
it's
gone
forever
unless
you
have
a
logging
and
actively
check
it.
A
So
I
think
it
is
a
pretty
good
alternative,
I'm
happy
to
keep
trying
that
for
a
while
and
see
how
everyone
feels
about
it.
So
our
little
a
little
spreads
people
have
asked
look.
Is
that
only
on
Thursday?
The
honest
answer
is
no,
it
kind
of
happens
all
the
time
whenever
I'm
working
on
backdrop,
projects
I'm
hanging
out
in
there.
Whenever.
D
A
Getting
really
grumpy
about
something
in
the
backdrop
you
I
want
to
fix
issues
I'll
go
in
there
and
complain
about
it.
We
work
on
active
all
the
time.
So
if
you,
if
there's
a
good
time
for
you
to
work
on
back
up
and
it's
not
a
Thursday
afternoon-
and
you
want
to
do
some
sprinting,
there's
friends
in
there-
you
can
chat
with
whoever
and
get
help
on
thinks
if
you
need
it
or
share
ideas.
A
So
anytime,
you
have
to
give
we
appreciate,
let's
see,
so
we
also
have
a
list
of
upcoming
events
we
usually
talk
about,
but
now
that
it
is
the
end
of
the
year
and
approaching
holiday
season.
Our
next
backdrop,
events
aren't
scheduled
until
febuary
there's
a
couple
of
upcoming
things
here
in
san
francisco
bay
area.
A
If
anyone
is
interested,
there
is
a
oakland
two
point,
oh
group,
which
I
think
will
probably
go
to,
which
is
just
kind
of
a
place
for
people,
have
tech
ideas
to
talk
about
stuff
and
meet
and
greet
with
other
people
who
have
good
ideas
and
which
is
a
fairly
casual
like
three
hour
event
one
evening
which
I
think
ninel
probably
be
going
to,
and
then
there
is
Mike
I,
don't
know
if
you
want
to
talk
about
it,
but
there's
like
a
non:
a
non-profit,
specific
developer,
experience
sharing
event,
which
is
three
days
long,
I
think
and
it's
very
casual
kind
of
everybody
gets
together
or
breaks
out
into
groups
and
talks
about
solutions
that
have
worked
for
them,
which
I
think
I'm
planning
on
going
to
I'm,
not
sure
Nate
and
I
are
both
going
to
go
to.
A
It
has
kind
of
a
hefty
take
a
price.
There's
include
food,
so
there's
that
too,
but
I
think
that
that
would
be
good.
I'm,
not
sure
I
have
a
lot
of
experience
in
the
nonprofit
space.
I
have
a
little,
but
it
would
be
good
to
hear
about
the
kinds
of
problems
they're
facing
into
backdrop,
a
solution.
Even
though
I
might
not
yeah
I,
don't
know
we'll
see
I
think
it'll
be
a
fun
event.
That's.
C
Which
is
a
couple
blocks
north
of
the
19th
street
bart
station,
so
it's
really
convenient
and
yeah.
It's
it.
It's
one
hundred
fifty
dollars
to
register
unless
you're
a
giant
company
and
that
covers
three
days
of
unconference
breakfast
and
lunch
and
then
also
usually
there
is
a
party
which
they
provide
some
a
couple
of
free
drinks
or
people
and
stuff
and
there's
also
other
sort
of
hang
out
there
afterwards
for
socializing.
D
A
Okay,
I'll
put
it
on
the
calendar
too.
So
if
anyone
here
is
interested
they'll
know
about
it.
Okay,
thanks
Mike,
let's
see
how
are
we
doing
on
our
agenda?
I
think
that's
everything
that
we
had
actively
scheduled
to
talk
about,
but
does
anyone
have
any
questions
or
comments
or
anything
while
we're
all
here?
Yes,
all
right.
Here's
far-out
question.
A
And
so
yeah,
this
is
kind
of
an
interesting
situation
that
we're
in
right
now
we're
backdrop
is
kind
of
by
developers
for
developers,
but
if
our
target
target
audience
is
aiming
at
non
coders,
maybe
we
should
have
marketing
people
involved
or
target
marketing
people
in
some
way,
and
it's
a
little
bit
better
than
what
we're
doing
now.
Yeah
I
would
love
to
get
a
non
coder
marketing
type
person
involved.
I,
don't
know
how
to
do
that.
A
First
of
all,
we
need
to
find
one
and
I
think
we've
got
a
bunch
of
people
in
the
backdrop
community
or
like
I
can't
code.
How
can
help,
which
would
be
great
but
I,
don't
I,
don't
know
how
to
make
like
actionable
tasks
for
them
to
do,
or
it's
just
like
tell
all
your
friends,
but
that's
kind
of
like
than
what
I
would
love
it.
A
Yeah,
okay.
Well,
then,
I
think
we
should
maybe
wrap
this
meeting
and
go
back
to
working
on
/
playing
with
/
dreaming
about
doing
things
with
backdrop,
but
thanks
all
for
coming
for
this
meeting
today,
Oh
anytime.
B
Honey,
why
don't
you
give
a
shout
out
to
your
new
backdrop
website
that
launched
yesterday
box
lunch.
A
A
It's
just
like
soft
lunch
done
so
once
I
go
through
some
of
the
follow-up
stuff,
then
I
can
definitely
make
a
bunch
of
noise
about
the
actual
website
because
it's
gonna
be
really
pretty
and
what
you
guys
to
see
it,
but
it's
not
like
approved
by
Zener.
Yet
so
I
meet
a
bunch
of
people
start
seeing
it
and
complaining
about
things.
He's
gonna
be
curvy.
Look
at
those
changes
dad,
but
yeah
and
yeah.
Well:
okay,
fine
supposed
to
ear
it's
in
the
it's
in
the
google
hangout
chat.
A
A
Everybody
for
coming
and
yeah
more
of
the
same
I.
Wouldn't
we
happy.