►
From YouTube: Backdrop weekly 2/13
Description
Backdrop CMS weekly status meeting.
A
All
right
we
are
on
air,
so
I
guess
we
have
a
couple
of
exciting
updates
since
last
week,
hi
andy
welcome
to
the
hangout.
Thank
you
for
all
the
awesome
work
you've
been
doing
as
of
late.
A
Okay.
So
thank
you
everybody
for
who's
here
on
the
call.
I
think
we
have
one
viewer.
So
thank
you
for
viewing
at
the
moment,
we'll
probably
have
more
later-
and
I
know
people
like
to
come
and
watch
after
the
fact,
if
they're,
working
or
otherwise
busy
on
thursdays
at
1pm.
So
it's
good
that
we
have
a
little
recording
for
people
to
watch
later,
which
is
great.
A
Thank
you
all
for
watching
backdrops
goals,
there's
a
cost
that
comes
with
change,
and
we
think
that
drupal
8
will
be
very
expensive
and
there
are
a
whole
bunch
of
people
who
know
and
love
drupal
7,
and
we
want
them
to
be
able
to
continue
to
use
a
similar
platform
with
features
that
are
comparable
to
what
you
get
with
drupal
8,
but
an
architecture,
that's
something
that
they
already
know,
which
is
why
we're
working
on
backdrop,
so
backdrop
will
include
a
drupal
8,
comparable
features
on
a
drupal
7,
like
architecture
and
bug,
fixes
that
have
gone
into
both
drupal
7
and
drupal
8.
A
Our
timeline
is
to
release
backtrack,
one
sometime
this
summer,
we're
thinking,
maybe
june
or
july,
but
definitely
before
drupal
age
is
released
and
then
we'll
have
some
time
to
work
on
getting
contrib
at
least
ready.
So
if
people
want
to
build
sites
on
backdrop,
they'll
be
able
to
do
that
and
compare
them
to
sites
on
drupal
8,
which
will
be
great
original
seven.
A
So
we
have
a
couple
of
major
issues
that
need
to
get
resolved
before
we
can
release
backdrop
one
and
we're
going
to
review
those
today.
There's
of
course
a
whole
bunch
of
other
issues
in
our
queue
that
are
not
a
1.0
release
blocker.
So
if
you
have
something
you
want
to
work
on,
feel
free
to
jump
in
on
it,
but
we
just
covered
the
most
important
things
in
this
meeting.
A
We
have
a
bunch
of
back
ports
from
drupal
8,
and
michelle
has
been
a
issue
creating
machine
lately
going
through
the
git
log
and
making
sure
all
of
the
changes
that
happened
to
drupal
8
have
been
documented,
so
we
can
either
decide
whether
we
want
to
include
those
changes
or
something
similar
in
backdrop
or
not,
which
is
great.
Some
of
them,
of
course,
won't
apply
to
us
like
converting
system
x
to
system
y,
but
a
whole
bunch
of
other
things.
Like
the
user
interface
improvements
and
stuff.
A
We
would
want
to
reconsider
and
we
also
have
a
list
of
drupal
7,
what
we're
calling
cross
ports
so
all
of
the
fixes
bug,
fixes
and
minor
enhancements
that
have
gone
into
drupal
7.
We
want
to
make
sure
that
we're
also
including
in
backdrop,
so
we've
got
meta
issues
of
those
andy.
I
know
you've
been
working
like
a
champ
on
getting
all
those
cross
ports
in
which
is
great.
A
A
I've
got
well
they're
not
committed
yet,
but
I've
got
a
couple
of
those
merged
in
no
problem,
which
is
great
so
with
a
little
help
from
nate,
figured
out
some
wonkiness
on
one
of
them,
but
yeah
so
that
that's
progressing
along
and
I'm
hoping
to
have
that
done
today,
which
will
be
good,
then
we'll
just
have
two
issues
for
two
meta
issues
for
drupal,
7
cross
course.
A
Instead
of
three,
which
is
great,
and
then
we
have
a
another
issue
that
I
added
on
here
since
last
week,
which
is
drupal
7
security
updates.
A
So
we've
had
a
couple
of
people
in
our
queue
coming
and
posting
information
about
security
announcements
that
have
come
out
for
drupal,
saying,
hey,
you
know,
dribble
7
had
a
security
announcement
by
the
way
you
guys
should
know
about
it,
because
you
need
to
include
some
fixing
backdrop
and
we
had
that
happen
a
couple
of
times,
and
I
thought
you
know
what
we
need
to
be
careful
about
this.
A
I
should
create
a
meta
issue
that
lists
all
of
the
security
advisories
that
have
come
out
against
drupals
to
make
sure
that
we
can
get
equivalent
fixes
in
to
backdrop,
so
I
went
back
through
all
of
those
that
that
have
come
up
since
our
fork
date
and
made
sure
that
we
had
an
issue
for
each
one.
A
So
those
aren't
going
to
come
up
on
our
metal
list
for
drupal
7,
because
there
aren't
public
issues
in
the
drupal
queue
and
patches
that
we
can
apply,
but
we
do
need
to
still
make
sure
that
we
fix
those
problems.
So
I
made
a
meta
issue,
so
we
can
keep
track
of
those
a
couple
of
them.
We
already
had
in
our
queue
for
other
reasons,
but
there's
definitely
more
of
them
that
we
should
be
working
on
so
now
we
have
a
way
to
check
those
as
well.
B
Yeah
speaking
of
those
security
fixes
some
of
the
the
backboarding
issues
like
the
drupal
7
issues
they've
been
coming
in
and
we
get
like
tests
that
test
the
security
functionality
to
make
sure
that
they
that
it
works,
but
the
fix
themselves
isn't
included
in
the
drupal.org
issue
queue
so
like
andy,
some
of
your
pull
requests
actually
tests
that
the
security
fix
works,
but
the
security
fix
itself
wasn't
there
because
there's
no
there's
no
issue
for
it,
but
we
found
that
it's
it's!
Oh,
it's
not
not
your
fault,
not
your
fault.
B
It's
just
funny
workflow
on
drupal.org,
but
we
found
out
that
if
we
want
to
pull
in
security
fixes,
it's
actually
relatively
easy.
I
think
we'll
make
this
like.
Yeah,
like
jen
put
together
that
meta
list
and
we'll
go
through
them,
but
pulling
in
security
fixes
is
relatively
easy,
even
though
there's
no
official
issue
for
it.
The
commit
messages
basically
are
for
each
one
of
those
security
issues
at
the
time
that
that
version
of
drupal
was
was
released
like
7.14
or
whatever.
B
There's
a
single
commit
that
contains
all
of
the
security
fixes
in
one
single
commit.
That
is
at
the
same
time
as
the
release
date.
Basically,
so
it's
it's
actually
really
pretty
easy
to
pull
in
security
fixes
all
at
once,
because
they're
all
just
in
in
a
single
commit
it's
just
that
they're
kind
of
not
very
well
labeled.
B
So
anyway,
wait
we'll
we'll
be
pulling
all
of
those
in
and
that'll
help
with
the
back
port
list,
like
making
sure
that
all
of
our
tests
continue
to
pass,
because
sometimes
those
security
issues
sneak
in
new
functions
and
new
tests.
A
A
Other
major
projects
that
we're
working
on
before
we
release
1.0
the
first
one
is
config
management,
and
for
the
last
few
weeks
I've
been
talking
about
how
I
was
going
to
make
a
meta,
and
then
I
hadn't
done
it
well,
I
did
it
this
week,
so
we
now
have
that
issue
for
our
config
management
initiative,
which
is
good.
I
basically
went
through
the
drupal
8
meta
and
picked
out
all
of
the
relevant
tasks.
So
there
are
simple
things
like
converting
variables
and
converting
states
which
we
already
knew
about.
A
We
already
had
issues
for
and
then
there
are
more
complicated
subsystems
that
need
to
be
converted.
So
I
grabbed
the
issue
from
drupal.org
for
each
subsystem
system
conversion
and
linked
it
on
a
new
issue
in
our
queue.
So
we
can
see
what
drupal
8
did
about
converting
that
subsystem
and
then
also
find
out
how
we
should
do
it
for
for
backdrop,
which
might
be
a
little
different
in
each
case,
but
at
least
we
have
the
list
of
everything
we
have
to
convert.
A
There
are
a
couple
of
systems:
drupal
8
had
to
convert
that
we
don't
have
to
convert
just
because
we
removed
those
things
from
backdrop
which
is
great,
but
for
the
most
part
it's
almost
exactly
the
same
list,
so
we'll
just
need
to
kind
of
turn
through
those
which
is
good,
and
there
aren't
nearly
as
many
as
I
thought,
I
was
really
worried
that
it
was
going
to
be
a
vast
amount
of
well,
it's
probably
still
a
lot
of
work,
but
I
thought
there
was
going
to
be
a
really
long
list
of
things
that
need
to
be
converted,
but
it
turns
out
it's
just
a
handful,
so
I
was
like.
A
Yeah
that
that
issue
itself
might
turn
into
another
meta.
They
did
the
same
thing
on
on
drupal.org,
where
there
was
a
meta
issue
for
all
of
the
conversions
that
included
a
list
of
variables
and
then
the
variables
this
was
another
meta,
and
so
they
could
split
that
off
into
more
manageable
chunks.
So
it
was
like
okay,
you
know,
here's
all
these
variables
that
go
together
and
here's
all
those
and
they
they
merge
them
in
and
occasionally
they
were,
as
they
were
working
through
those
issues.
A
They
would
discover
other
problems
that
needed
to
be
solved
that
weren't
necessarily
variable
conversions
but
were
related,
and
I
imagine,
we'll
probably
run
through
the
same
thing.
Fortunately
they've
done
this
all
before,
so
we
can
try
and
get
as
much
direction
from
previous
work
as
possible,
so
yay
meta
issue
created
and
victor's
still
not
here
at
our
meeting,
but
I
know
that
he's
back
I've
gotten
a
lot
of
positive
feedback
from
the
talk
that
he's
done
on
backdrop
already.
A
Other
people
are
kind
of
starting
to
look
at
the
drupal
landscape
and
try
and
figure
out
what
they
want
to
do,
which
I
think
is
important.
Sometimes
people
don't
really
think
about
you
know
what's
going
to
happen
when
they
get
there
until
all
of
a
sudden,
it's
like.
Oh,
let's
do
a
drupal
8
site,
and
then
they
you
know,
have
to
get
caught
up
in
everything.
So
I
think,
having
the
drupal
community
look
forward
is
is
really
good.
It'll
be
good
for
us
and
it'll
be
good
for
your
blade
as
well.
A
So
that's
great
so
when
he
gets
back,
we
can
update
him
on
that
on
the
meta.
But
even
if
we
have
new
people
who
want
to
get
working
on
config
management,
we
now
have
a
discrete
list
of
tasks
they
can
jump
in
on
any
time
before
then.
So
I
think
that's
good.
A
The
next
thing,
the
big
feature
that
we've
got
to
work
in
before
backdrop,
1.0
is
using
core
and
we
do
have
a
meta
issue
for
that
and
there's
just
a
whole
bunch
of
stuff
in
backdrop
that
should
be
converted
to
user
view.
A
Instead
of
not
using
a
view,
things
like
the
node
page
and
the
administrative
listings,
and
we
went
through
all
of
the
little
subsystems
that
needed
to
be
converted
or
updated
ahead
of
that,
so
getting
the
these
bulk
operations
tools
in
and
all
that
stuff
is
done,
so
I
think
we're
ready
to
just
start
working
through
our
conversions
as
of
now.
So,
if
you,
if
you
are
watching
this
later
or
now,
there's
a
bunch
of
you
watching
now
who
want
to
work
in
on
a
fuse
conversion.
Those
are
ready.
A
A
B
Yeah,
so,
okay,
let's
see
there's
no
real
serious
updates
here.
I
don't
think.
I
think
that
we,
I
guess
just
status
wise,
like
vbo,
got
finished
and
the
entity
api
got
converted
over
so
so
now
we
can
act
on
various
different
entities
in
a
consistent
manner.
B
The
most
of
the
listings
are
actually
just
literally
like
could
just
create
a
view
and
then
yeah
and
then
and
then
export
it
and
then
replace
the
the
previous
listing
with
with
that
new
export,
but
the
the
two
for
replace
administrative
pages
admin,
slash
people
and
admin,
slash
content.
B
Vbo
functionality
exists
for
both
users
and
nodes,
but
we
need
to
expand
the
functionality
in
those
issues
like
admin.
Slash
people
needs
to
be
able
to
do
things
like
cancel.
B
So
so
we
kind
of
need
some
new
actions
as
well,
so
some
of
them
are
trivial,
but
the
administrative
pages
ones
are
still
a
little
bit
a
little
bit
more
involved.
Yeah.
Okay,.
A
And
is
there
documentation
on
how
to
add
actions
for
vbo
in
backdrop
land,
yet.
B
There's
not
any
documentation,
because
it's
not
any
well,
not
any
new
documentation.
It's
it's
still
the
action
system
from
drupal
7.
Actually,
it's
it's
unchanged.
Essentially,
so,
however,
you
add
an
action.
Drupal
7,
you
add
an
action
in
backdrop.
Okay,
that's
great.
A
All
right
so
next
on
our
list
here
is
the
blocks
and
lands
initiative.
This
is
again
something
that
we
haven't
been
working
on
yet
because
it
is
not
actually
a
release
blocker
for
backdrop
1.0.
It
is
a
really
good
idea
and
we
think
that
if
we
can
get
something
in
that's
an
awesome,
layout
builder
tool
for
backdrop
that
would
kind
of
set
us
apart
from
drupal
8.
A
So
I
think
that
it's
important
to
work
on,
but
not
as
important
as
making
sure
that
our
existing
system
is
ready
to
ship
on
time,
which
is
something
that
posts.
It
also
starts
apart
from
triple
h,
if
we
can
set
a
deadline
and
then
deliver
on
time
that
that'll
be
pretty
cool
too.
So
no
progress,
no
updates
for
blocks
and
layouts,
but
if
you
we
have
someone
who
wants
to
work
on
it,
we've
got
a
addition,
an
issue
where
we're
discussing
about
how
we're
going
to
do
that.
A
We've
also
got
a
bunch
of
other
minor
projects
that
we
want
to
work
on
kind
of,
in
conjunction
with
the
we're
making
usability
improvements
is
something
that's
really
near
and
dear
to
my
heart,
and
we've
got
a
bunch
of
specific
changes
that
are
really
important
like
getting
wizzy
awaken
core,
adding
a
new
dialog
system
that
views
and
wizzy,
we
can
use
replacing
the
current
toolbar
with
a
better
toolbar,
hopefully
a
responsive
one,
maybe
not
the
same
one,
that's
in
drupal
8,
but
something
that's
a
little
savvier
than
what
we
have
now
improving
the
node
add
and
edit
forms.
A
We've
already
got
a
lot
of
really
great
work
going
on
that
in
drew
blatt,
and
if
we
ship
with
one
that
looks
more
like
drupal
7,
there
might
be
a
little
push
back
on
that,
so
be
good
to
get
some
great
stuff
done
there.
We
want
to
include
a
new
administration
theme
which
will
help
us
look
and
feel
different
from
using
drupal
8
and
help
us
with
our
own
brand
and
then
there's
a
bunch
of
other
smaller
changes.
A
I
know
we've
gotten
some
patches
committed
in
the
last
week
for
stuff
that
made
me
really
upset
about
drupal,
and
so
I
would
go
in
there
and
be
like
I'm
going
to
fix
this,
and
then
you
know
you
find
an
issue
on
drupal,
that's
been
sitting
there
for
forever
and
hasn't
gotten
fixed
and
then
you're
like
fine.
I'm
gonna
make
this
work
and
I
know
we
got
the
password
reset
functionality
into
backdrop
this
past
week,
which
is
really
great.
A
So
when
you,
you
click
the
password
reset
link,
it
asks
uber
password
right
there,
so
you
don't
get
logged
in
and
then
forget
to
reset
your
password,
which
is
something
that
I've
been
getting
complaints
about
on
a
drupal
7
site
that
I'm
running
right
now.
So
I'm
running
a
patched
version
of
drupal
7
to
get
that
functionality
in
people
liked
it.
So
I'm
like-
let's
just
put
this
in
backdrop.
So
it's
been.
A
I
don't
know
two
or
three
weeks
trying
to
get
that
in
but
yeah
it's
a
little
better,
a
little
bit
little
steps
at
a
time.
So
if
there's
anyone
else,
who
cares
a
lot
about
usability?
Making
people
happy
the
whole
user
experience
improvements,
goal
of
ours
needs
to
have
a
lead
and
you
need
to
have
some
kind
of
manage
it
and
keep
an
eye
on
the
things
that
we
want
to
work
on
and
keep
those
moving
forward.
So
let
us
know
about
that.
A
A
So
hopefully
I'll
get
issue
135
for
the
drupal
7
stuff
done
today
and
then
we'll
be
a
third
of
the
way
through
that
and
then
andy
will
probably
wrap
up
134
and
then
we'll
get
ronnie
to
wrap
up
133,
and
then
we
can
start
a
theme
system
conversion,
so
yeah.
It's.
A
And
then
there's
a
bunch
of
other
stuff
that
we're
working
on
as
well
in
in
over
in
backdrop
land.
We
obviously
don't
have
our
own
website.
Yet
we
need
some
help.
Working
on
that
we've
already
got
kind
of
a
team
in
place
in
terms
of
a
content,
strategy
and
design.
A
We
don't
have
anyone
who's
volunteered
to
development,
yet
we're
not
quite
ready
to
get
started
on
that.
So,
if
you
want
to
do
development
on
the
backdrop.org
backdropcms.org
website,
let
us
know
and
we'll
add
you
to
the
team
and
then
when
we
get
some
wireframes
and
designs
done,
we
can
start
building
it,
but
we're
still
working
on
the.
What
are
we
going
to
say?
How
are
we
going
to
say
a
piece?
A
A
Those
are
hard
all
right,
so
we
also
need
an
update
server.
This
is
so
how
all
of
our
backdrop
sites
can
tell
if
they're
up
to
date
or
not
just
like
all
drupal
sites
now
currently
know
if
they're
up
to
date.
I
think
that's
an
awesome
feature.
We
need
to
do
that,
so
we
need
to
figure
out
how
to
create
one
of
those.
A
If
anyone
is
really
passionate
about
that
wants
to
figure
it
out,
let
us
know,
and
we
will
let
you
loose
on
a
project
to
get
going
on,
that
we
also
need
a
github
service.
So
anybody
who
creates
a
backdrop,
module
or
theme
can
register
just
being
an
official
backdrop,
module
or
theme,
and
then
we
can
aggregate
all
that
information
onto
our
website
and
show
people
a
single
place
to
search
for
stuff,
rather
than
forcing
them
to
search
on
github,
which
could
be
a
little
painful.
A
So
that's
going
to
be
really
important
and
also
kind
of
cool
and
new,
because
we
don't
do
that
in
drupal
land.
So
if
anyone
has
any
experience,
I
think
with
ruby,
I
think
it
was
ruby.
I
don't
remember
now
could
have
been
node.js
anyway.
It's
something
I
don't
know
it
does
not
drupal
and
we
need
some
help
creating
github
service.
So
if
anyone
wants
to
work
on
that,
let
us
know
about
that
too,
and
then
the
other
thing
that
we
should
start
thinking
about
is
a
api
reference
website.
A
We
need
to
have
change
notices
about
each
one
of
those
changes
posted
somewhere,
so
that
someone
who
does
want
to
upgrade
from
drupal
7
knows
what
has
changed
and
what
they're
going
to
need
to
consider
in
their
own
modules
or
teams.
So
that's
also
fairly
important,
so
we
should
get
started
on
that
pretty
soon.
So,
if
you
are
interested
in
building
a
api
site,
let
us
know
about
that
and
then
we
also
have
every
thursday.
After
this
meeting
we
do
a
little
mini
sprint
in
irc.
A
So
I've
we
usually
work
all
day
thursday
on
backdrop,
but
in
the
afternoon
we're
publicly
available
for
people
to
ask
us
questions.
If
you
want
to
get
started-
and
you
don't
know,
you
can
come
into
the
issue
queue
and
ask
us
for
issues
and
we'll
assign
them,
and
we
can
work
together
on
stuff,
it's
really
fun.
You
should
come
and
then
we
also
are
going
to
try
and
have
some
more
official
like
in-person
sprints
at
drupal
events
in
the
future.
As
long
as
the
drupal
events
are
okay
with
it.
A
So
again
we
want
to
make
sure
that
we're
not
stepping
on
too
many
toes,
but
there
are
people
who
are
interested
in
this
who
are
going
to
meet
us
at
camps
in
the
future.
So
it
will
be
good
to
kind
of
organize
and
and
get
some
task
lists,
maybe
for
for
those
events
to
see
if
we
can
get
people
working
together
in
person,
we
also
have
a
bunch
of
publicity
stuff
coming
up
as
well.
A
So,
let's
see
I'm
going
to
go
to
drupal
camp
florida,
I'm
not
officially
talking
about
backdrop
there,
because
there's
only
one
day
of
sessions,
but
I
will
be
chattering
with
everybody
about
it
at
you
know,
lunchtime
and
parties
and
all
that
stuff
and
then
they're
going
to
be
doing
a
like
coding
for
good
sprint
on
sunday.
So
we're
not
going
to
be
working
on
backdrop.
We're
just
going
to
be
working
on.
A
You
know
some
local
company
that
needs
a
website
or
some
good
cause
that
needs
a
donation
former
I
don't
know
well,
there's
going
to
be
like
a
vote.
People
decide,
but
I
will
be
spreading
the
word
of
backdrop
over
there,
which
is
pretty
good,
mid
camp
annie.
I
think
you
were
planning
on
going
to
that,
and
so
hopefully
we
can
get
you
to
present
a
session
on
backdrop,
if
you're
not
interested
in
doing
that,
just
talking
to
people
about
it
while
either
while
you're
there.
A
It's
also
really
good
so
don't
feel
pressure
to
give
a
talk.
But
if
you
want
to
we'll
definitely
help
you
out
with
any
materials
or
information
that
you
want
for
that,
there's
going
to
be
a
drupal
camp
at
stanford
in
april,
which
I
think
is
something
that
nate
and
I
will
probably
both
attend
and
we'll
talk
about
backdrop.
I'm
not
sure
they're
going
to
want
us
to
present
on
it
I'll
talk
to
them
and
see
what
they
think.
A
I
know
that
they
there
there's
a
bunch
of
really
great
people
at
stanford
who
have
different
opinions
on
on
how
they're,
personally
going
to
support
their
own
infrastructure
in
the
future.
So
I'd
like
to
talk
to
them
about
that,
regardless
of
whether
backdrop
is
a
part
of
their
plan
currently
or
not
so
that'll
be
good
for
us
too,
and
then
drupal
camp
mexico
nate.
Do
you
want
to
give
an
update
on
that?
B
Yeah
well,
we
have.
We
have
an
invitation
to
give
a
talk,
but
but
we
haven't
officially
like
accepted
at
this
point.
I
don't
think
so,
I'm
not
really
sure
about.
If
that,
if
that'll
happen
for
us
or
not,
okay,.
A
But
it's
on
our
calendar.
There
is
going
to
be
a
drupal
camp,
mexico,
they're
interested
in
hearing
about
backdrops,
specifically,
which
is
good,
and
I
think
that
if
we
do
go
and
give
a
talk
there,
we
should
probably
organize
an
official
sprint.
That's
okay
with
them
as
well,
and
see
how
that
goes.
A
I'm
kind
of
in
the
same
boat
with
drupal
camp
ireland,
I've
been
invited
to
go
and
give
a
talk.
I'm
trying
to
figure
out
if
I
can
afford
to
go
all
the
way.
A
Or
not,
it's
a
it's
a
long,
expensive
international
flight,
unlike
mexico,
which
is
really
close
to
here,
so
we'll
probably
have
to
choose
between
those
two.
A
We
won't
be
able
to
do
them
both,
but
if
anyone
else
is
going
to
the
drupal
camp
in
ireland
and
is
interested
in
talking
about
backdrop
or
hearing
about
backdrop,
let
us
know
we
can
try
and
figure
out
something.
A
We
also
have
drupalcon
austin,
which
I
sadly
won't
be
attending
I'll,
be
in
canada
that
week
nate
will
probably
attend
again.
This
is
the
place
where
I'm
not
sure.
We
should
give
a
talk
about
backdrop,
because
it
is
a
drupal
official
drupal
sanctioned
event,
but
we
can
definitely
talk
to
about
people
about
it
while
we're
there
and
so
we'll
see
how
everyone
feels
about
it,
probably
not
a
good
place
for
a
sprint.
A
But
you
know
everyone's
got
hotel
rooms.
We
have
to
make
it
happen.
We
can
and
then
drupalcorn
in
iowa
in
july
nate,
and
I
will
be
going
to
do
a
keynote
about
backdrop,
which
will
be
pretty
fun.
They've
done
a
bunch
of
non-drupal
keynotes
in
the
past,
so
their
audience
is
pretty
open
to
kind
of
hearing
how
the
other
side
lives.
I
think,
in
our
case,
it'll
be
more
of
the
same
side.
A
A
different
perspective
to
be
like,
oh
we're,
going
to
do
it
in
a
different
way,
at
least
if
it's
not
not
any
different
in
the
code
side,
but
yeah
that'll
be
really
fun.
Josh
koenig
who's,
also
from
the
san
francisco
bay
area,
is
going
to
be
the
other
keynote
speaker.
So
it's
like
a
bay
area
takeover
of
corn
camp,
so
that'll
be
a
lot
of
fun.
If
nothing
else-
and
I
think
they'd
probably
be
open
to
having
us-
do
a
sprint
there
as
well.
A
One
other
thing
that
that'll
be
really
interesting
is
that
we
are
going
to
be
doing
a
a
big
article
in
drupal
watchdog,
which
will
the
issue
will
come
out
right
about
the
same
time
as
drupalcon
austin.
So
it
gives
us
a
chance
to
kind
of
tell
our
story
from
the
right
perspective.
I
feel
like
there's
a
lot
of
people
out
there
who
don't
really
understand
why
we're
doing
this.
A
They
don't
see
why
it's
necessary
and
they
don't
get
it,
and
so
I
think,
having
a
big
article
like
this
in
a
drupal
publication,
will
let
us
kind
of
set
the
record
straight
and
say
it's
not
what
you
think
it
is
it's
not
what
you
want
it
to
be.
This
is
what
it
is
and
kind
of
tell
the
story
in
a
way
which
I
think
will
be
really
good
for
our
brand
and
our
messaging.
So
I'm
really
looking
forward
to
working
on
that.
A
I've
already
written
a
couple
of
emails
to
people
lately
and
really
liked
what
I
said
and
I'm
like
this-
should
go
in
the
article
and
I'm
throwing
it
all
in
giant
google
doc.
So
we
can
organize
the
thoughts
over
there
and
get
that
out.
A
So
if
any
of
you
are
interested
in
reviewing
that
for
us,
let
me
know
I
can
send
that
over
too
I've
already
got
I'm
hoping
to
send
it
to
our
copywriter
for
the
website
and
have
him
review
it
for
us
to
make
sure
we're
kind
of
all
on
the
same
page
about
our
message
and
branding
and
everything
too
so
that'll
be
really
fun.
I'm
excited
about
it
if
there
are
any
questions
or
anything.
Anyone
else
wants
to
add
to
this
weekly
agenda.
A
A
B
Yeah
we
had
darren
join
our
our
call.
Do
you
have
any
anything
to
add
darren.
Daryn
might
not
be
listening.
Okay!
Well,
I'm
here:
okay,.
C
I
was
the
only
other
thing
that
I
had
to
add
was
next
week
since
some
of
the
summer,
most
of
us
are
in
the
bay
area.
Silicon
valley,
drupal
user
group,
has
a
single
sign-on
and
ibm
being
discussed
next
week
down
in
santa
clara.
C
B
C
Yeah
I
I've
been,
I
get
all
these
extra
announcements
from
all
over
the
place,
so
you
guys
probably
do
too.
C
B
Okay,
well,
cool!
I
don't
have
anything
else
for
this
phone
call
for
this
meeting.
A
Okay,
well,
then,
I
will
go
back
to
the
issue.
Queue
and
I'll,
see
you
all
in
irc
and
hopefully
we'll
get
a
couple
steps
closer
this
week.