►
From YouTube: Weekly Status meeting 2/10
Description
Backdrop CMS
A
All
right
we
are
on
air.
I
just
wanted
to
start
off
by
thanking
everybody
for
joining
the
call
watching
live
or
watching
the
video
afterwards
we're
still
getting
a
lot
of
feedback
from
people
they're
enjoying
the
video.
So
that's
good.
We
are
here
because
we're
working
on
backdrop
cms
and
we're
doing
that,
because
there's
a
cost
that
comes
with
change
and
we're
concerned
that
not
all
of
the
drupal
community
is
going
to
be
able
to
afford
the
price
winter
blade
comes
out
and
we
want
to
leave
them
a
path
forward.
A
We're
going
to
try
and
include
all
the
bug
fixes
that
are
currently
in
drupal
7,
as
well
as
a
lot
of
the
bug
fixes
that
have
gone
into
drupal
8,
maybe
not
exactly
the
same
solutions
that
went
into
drupal
8,
but
we
need
to
find
comparable
solutions.
So
we
can
jump
our
own
project
and
we're
also
assuming
we
can
do
it
without
changing
the
apis
too.
Much
looking
to
simplify
existing
systems
and
add
new
features,
our
timeline
is
to
get
backtrack.
1.0
released
sometime
before
dribbling
comes
out.
A
Our
our
goal
right
now
is
to
get
it
out
this
summer,
we're
thinking
july
or
june.
If
we
can
get
that
done,
and
so
we've
got
kind
of
a
road
map.
A
We've
been
creating
meta
issues
to
keep
an
eye
on
the
things
that
are
most
important,
that
are
going
to
be
blocking
our
1.0
release
and
as
soon
as
we
get
some
momentum
going
on
those,
we
can
come
up
with
an
actual
release,
date
and
kind
of
hunker
our
efforts
down
on
those
things
and
make
sure
that
we
are
moving
towards
that
goal.
We're
going
to
stick
to
the
date
once
we
have
it
and
we're
going
to
ship
on
time
no
feature
creep
allowed
here.
A
So
in
terms
of
the
things
we
need
to
get
done
before,
we
can
release
a
1.0.
We've
got
a
couple
of
really
important
things,
including
cross
ports
from
drupal,
7
and
back
ports
of
issues
from
triple
8,
including
all
the
security
updates
that
have
already
gone
into
drupal
7
and
a
couple
of
major
projects.
A
A
Patches
that
exist
for
drupal
7
over
to
backdrop,
which
is
great,
there's
a
bunch
of
pull
requests
with.
You
know
gazillion
commits
on
each
one,
which
is
great
to
get
us
moving
forward.
There
are
a
few
left
on
the
meta
issue.
135
that
I've
been
working
on.
I
created
one
giant
pull
request
last
week,
which
of
course
failed
all
of
its
tests.
A
So
this
week
I've
been
breaking
them
down
into
smaller,
pull
requests
to,
hopefully
get
the
ones
that
are
really
easy
right
in
and
then
go
back
and
focus
on
the
ones
that
are
really
tricky.
So
these
are
the
patches
that
didn't
apply
cleanly,
and
so
they
required
either
some
finessing
or
rewriting
of
the
original
patch.
In
order
to
get
to
apply
to
backdrop
so
there's,
I
think
nine
of
those
left
on
the
last
issue
and
then
I'm
going
to
start
those
bang
out
today.
A
A
lot
of
those
are
passing,
maybe
half
of
them
we'll
just
go
straight
in
the
other
half.
We
need
some
more
work
on.
So
if
anyone
is
really
excited
about
running
tests
and
figuring
out,
why
they're
failing
and
re-rolling
pull
requests
they're
a
couple
of
those.
A
That
could
use
some
attention
and
then
I'll
move
on
to
issue
134,
which
is
the
next
one
on
my
list
I
know
andy
did
all
of
the
once
it
applied
cleanly.
We
should
probably
do
a
a
pass
on
the
ones
that
don't
apply
cleanly,
make
sure
we
even
need
them
and
then
the
ones
that
are
going
to
need
a
little
bit
more
love
we'll
spend
some
time
on
this
as
well.
A
We
also
have
major
projects
we're
working
on
for
backdrop.
Those
include
things
like
getting
config
management
done.
We
currently
have
the
config
management
engine
in
core.
We
have
a
meta
issue
that
documents
all
of
the
subsystems
that
need
to
be
converted.
Things
like
image
styles,
image
styles
is
actually
one.
That's
already
done,
because
that
went
in
with
the
original
conversions.
There
are
other
things
like
fields,
and
and
all
of
that
that
also
need
to
be
converted.
A
So
we
have
a
short
meta
of
a
handful
of
those
things
that
need
to
be
converted
and
then
there's
also
some
things
like
variables
and
those
just
need
kind
of
a
mass
conversion,
one
module
at
a
time
or
as
many
as
you
can
do
at
a
time,
some
of
those
things
are
going
to
be
really
straightforward
and
some
of
them
are
going
to
be
kind
of
tricky.
A
So
if
anyone
is
interested
in
learning
how
cmi
is
going
to
work
in
backdrop,
it's
pretty
similar
to
drupal
8,
but
the
code
is,
is
vastly
different,
obviously,
because
we're
not
using
the
drupal
8
code
style
but
yeah.
If
we
have
anyone
who's
interested
in
learning,
that
we've
got
a
great
learning
opportunity
where
you
can
come
work
on
converting
subsystems
and
and
seeing
how
all
that
fits
together.
A
A
So
let
us
know
we're
going
to
start
trying
to
get
more
development
underway
starting
in
the
next
few
weeks,
so
it
would
be
good
to
have
someone
to
kind
of
help
wrinkle
our
developers,
the
next
I'm
sorry,
I'm
gonna,
add
anything.
A
Okay,
so
the
next
major
issue
that
we've
been
working
on
is
getting
views
in
core.
We
also
have
the
view
subsystem
already
committed
and
we
have
a
meta
issue
documenting
all
of
the
views
pages
or
displays
in
some
cases,
they're
blocks
that
need
to
be
converted
from
the
current.
A
You
know
hard-coded
queries
and
core
style
to
views,
and
I
think
all
of
our
blockers
that
we're
preventing
getting
those
converted
are
also
in
so
we
now
have
vbo
like
functionality
and
core,
although
we're
going
to
need
a
couple
of
new
options
added
when
we
get
to
certain
lists
like
adding
and
removing
permissions
and
and
or
adding
and
moving
roles
and
stuff
like
that.
A
So
if
you
want
to
build
views
in
backdrop,
if
you
love,
building
views,
building
news
and
exporting
views
is
the
majority
of
what's
gonna
need
to
be
done
for
that.
There
are
some
heavy
coding
tasks
in
there,
but
for
the
most
part,
we've
got
it
all
documented
and
it
should
be
very
straightforward.
A
So
you
can
definitely
pick
up
on
those
things.
If
you
want
to,
we've
got
a
mesh,
a
meta
issue
for
that
as
well.
We
also
don't
have
anyone
to
kind
of
manage
our
our
views
queue
also.
So
if
you
wanted
to
do
some
wrangling
of
developers
for
us
on
that
front,
we
could
also
use
help
there
and
the
next
thing
that
we
would
like
to
work
on.
But
it's
not
actually
a
release.
Blocker
for
backdrop
is
getting
in
a
blocks
and
layout
system.
A
This
is
something
that
would
start
to
set
us
apart
from
drupal
8.
If
we
can
get
a
better
user
interface
for
putting
things
on
the
page,
I
think
that
would
be
killer.
So
it's
kind
of
a
pipe
dream
of
ours.
We
have
some
ideas.
A
We've
talked
to
some
usability
experts,
we've
got
kind
of
a
road
map,
but
we
don't
want
to
start
working
on
that
yet
because
we've
got
other
things
that
are
released,
lockers
that
we're
working
on
now
minor
projects.
So
these
are
things
that
are
also
really
important
to
the
success
of
backdrop,
but
aren't
necessarily
you
know.
Huge
chunks
of
work
like
cmi
reviews
include
things
like
the
user
experience
improvements
we've
been
talking
about
for
the
last
few
weeks,
getting
a
wysiwyg
editor
in
core
redoing.
A
The
node
add
edit
form
redoing
the
menu
stuff
like
that.
That
just
needs
to
kind
of
help
us
polish
the
product.
If
we're
going
to
be
competing
with
wordpress,
our
user
experience
needs
to
be
better
than
it
currently
is
now.
So
we've
got
a
bunch
of
little
tiny
issues
that
come
up
that
we've
already
nailed
down.
We've
got
some
kind
of
bigger
pieces.
It
would
be
good
to
keep
an
eye
on
make
sure
we
get
those
done
also.
A
So
if
anyone
is
particularly
interested
in
user
experience,
we
need
not
only
someone
to
kind
of
manage
the
list
of
tasks
that
we
need
to
do,
but
also
to
help
us
kind
of
direct
and
get
some
of
that
work
done
as
well,
and
then
one
of
the
other
minor
projects
we're
working
on
is
theme
system.
Cleanup.
We
thought
minor
project
is
totally
minor
and
I
am
itching
to
get
that
done.
I've
got
a
lot
of
ideas.
I've
got
some
spreadsheets.
I've
got
a
bunch
of
stuff.
A
I
want
to
do
on
theme
system
cleanup,
based
on
my
work
on
the
twig
initiative
and
dribble8,
where
we
need
to
clean
up
our
template
files.
We
need
to
make
them
approachable
to
front-enders,
and
a
lot
of
the
stuff
that
we
did
in
tripoli
is
also
doable
in
a
drupal
7
world.
It
just
won't
be
there
won't
be
any
tweak
involved,
but
I
still
think
we
can
make
the
experience
a
lot
better
for
a
front
end,
or
so
I'd
like
to
focus
on
that.
A
A
So
that's
what
I've
been
working
on
for
the
last
few
weeks
and
then,
in
addition
to
backdrop,
the
project
we
also
have
kind
of
the
backdrop
ecosystem
that
needs
a
lot
of
attention,
we're
working
on
primary
website
for
backdrop
cms.org,
where
we're
going
to
have
a
short
term,
just
a
a
better
statement
of
what
it
is.
A
Why
we're
doing
what
we're
doing
and
trying
to
help
set
the
record
straight
about
what
our
intentions
are
with
this
project,
which
I
think
is
really
important
for
us
to
get
out
so
we've
got
we've
had
meetings
with
content,
strategists
we're
working
on
wireframes.
Currently,
we've
got
a
designer
in
the
ranks
ready
to
do
some
work
for
us.
We're
gonna,
get
a
new
logo,
we're
gonna,
get
some
branding
done
and
we're
gonna
try
and
roll
this
thing
out
sooner
rather
than
later,
which
I
think
is
good.
A
We've
got
a
estimated
launch
date
for
april
1st,
which
I
think
is
reasonable
for
the
first
version
of
what
we
want
and
then
longer
term
we're
going
to
add
things
like
the
ability
for
somebody
to
search
for
a
particular
modular
theme,
showcase
of
sites
built
with
backdrop
just
kind
of
all
of
the
stuff
that
goes
around.
You
know
the
primary
website
and
and
we've
got
some
ideas
on
how
to
get
all
of
those
going
too.
So
first
things.
A
First,
we
want
to
get
our
message
out
there,
because
that's
of
course
the
hardest
thing
for
us.
So
I
think
I
think
focusing
on
that
would
be
really
good.
I
think
we
have
volunteers
to
help
with
every
aspect
of
the
theme,
except
for
maybe
some
development.
So
if
we
have
anyone
who
wants
to
help
us
build
a
site
initially
it'll
be
in
drupal,
but
the
backdrop
cms
website
might
be
one
of
the
first
examples
of
something
that's
cross-graded
from
drupal
7
to
backdrop.
A
A
Then,
let's
see
we
also
have
some
other
things.
We
need
like
an
update
server.
We
need
an
official
github
service
and
we
need
an
api
site
and
I
think
the
api
site
is
probably
one
of
the
most
important
things
just
because
we
need
a
place
to
start
putting
our
change
records
so
that
people
who
are
going
to
be
doing
updates
from
drupal
7
to
backdrop
have
a
place
where
they
can
go
and
see.
A
Okay,
if
I'm
gonna
import
a
module,
what
are
the
functions
that
have
changed?
If
I'm
gonna,
you
know
use
cmi?
What
is
it?
What
does
that
look
like
compared
to
how
I
stored
my
variables
before,
and
I
think
that
it
would
be
a
a
good
idea
to
get
that
side
up
sooner
rather
than
later?
A
A
You
know
closed
until
that
change
request
exists
and
we're
already
in
a
state
now,
where
we're
closing
issues
that
don't
have
change
requests
associated
with
them,
so
we're
going
to
need
to
either
create
a
meta
issue
that
includes
all
of
the
information
about
change,
requests
and
kind
of
go
back
through
that,
just
to
make
sure
that
we
have
a
good,
solid
starting
point
for
our
documentation,
which
I
think
is
going
to
be
really
important
for
us.
So
there's
not
it's.
A
Obviously,
our
goal
is
not
to
change
too
much
from
drupal
7,
so
it
won't
be
quite
like
it
is
for
drupal
8.,
but
I
do
still
think
it's
important
to
have
a
comprehensive
list
of
changes
for
people.
B
Yeah
everything
jen
as
we
encounter
change
log
entries
when
I
close
the
issue,
I'm
tagging
it
with
needs
change,
request.
A
B
A
For
something
like
like
issue
135,
that
issue
obviously
isn't
closed
yet,
but
it
contains
you
know,
100
patches,
some
of
which
need
change
records
so.
A
Yes-
and
there
are-
I
mean
there
are
yeah
there-
there
are
change
record
change
records
that
go
out
from
like
drupal
7
13
to
7
14..
So
if
somebody's
implementing
something
in
contrib,
they
have
to
put
a
requirement
in
their
module.
That
says
it
requires
like
714
or
higher,
or
they
need
to
introduce
their
own
backwards
compatibility
layer,
that'll
check
the
version
of
triple
and
call
one
function
before
and
a
different
function
after
so
there
are
a
few
of
those
that
we
need
to
just
kind
of
keep
in
mind.
A
Do
you
want
me
when
I
run
in
when
I
run
across
one
of
those
patches?
Do
you
want
me
to
instantly
create
an
issue
that
requires
to
change
notice,
or
should
we
do
it
once
like
at
the
end
of
like
issue
135?
Should
we
go
through
all
of
those
and
say
to
any
of
these
required
change,
notices
and
then.
B
Right
yeah,
I
think
I
think,
an
issue
every
time
the
change
is
needed
would
be
appropriate
for
those
meta
issues.
I
mean
the
other
issues
that
you
know
are
already
individual.
We
don't
need
separate
ones
for
those
change
requests,
because
we
already
have
the
issue
itself
but
yeah,
but
yeah.
We
should
have
anything
that
requires
more
than
just
a
pull
request
on
the
meta
should
actually
have
its
own
issue.
So.
A
So
yeah
the
api
site,
probably
in
its
infancy,
could
just
be
a
drupal
7
site
with
a
content
type
for
a
change
record,
and
we
can
maybe
set
that
up
as
early
as
today.
It
doesn't
need
to
look
like
anything.
Yet
we
just
need
a
place
for
it
to
live
and
then
yeah.
We
need
to
start
creating
those.
So
if
anyone
is
really
excited
about
documentation,
we
have
a
good
job.
It
doesn't
require
any
code.
A
A
So,
let's
see
we
also
have
upcoming
sprints.
We've
got
every
thursday
after
this
meeting
so
today,
starting
in
about
10
minutes
we're
all
going
to
be
in
irc
working
like
crazy
on
whatever
it
is
we're
working
on,
and
if
you
wanted
to
jump
in
and
figure
out,
you
know
you
don't
know
what
to
do,
but
you
want
to
do
something
find
us
in
irc.
Ask
us
what
needs
to
be
done.
A
I've
been
pretty
good
about
handing
off
first
issues
or
second
issues,
but
after
a
few
I'm
like
you
can
probably
figure
it
out,
go
ahead
and
play
with
it,
but
if
you're
new-
and
you
don't
know
where
to
get
started,
definitely
jump
in
and
tell
us
what
you
want
to
do
and
we
can
help
point
you
in
the
right
direction
and
then
we're
going
to
try
and
do
some
in-person
sprints
later
this
year
to
possibly
triple
camp
mexico
and
drupal
corn
in
iowa.
A
So
if
you
want
some
kind
of
hands-on
everyone
working
at
the
same
table
coding
on
the
same
project
talking
about
crazy
new
future
worlds
in
backdrop,
land,
we
can
definitely
make
that
happen
as
well,
so
that'll
be
fun
or
if
you
want
to
host
your
own
backdrop,
sprint.
Definitely
let
us
know
about
that
too.
A
We
also
have
a
bunch
of
publicity
coming
up,
there's
a
bunch
of
drupal
camps
where
we
may
or
may
not
be
giving
sessions.
We
may
or
may
not
be
having
sprints,
but
we'll
definitely
be
talking
about
backdrop,
if
nothing
else,
just
to
kind
of
help
set
the
record
straight
about.
Why
we're
here?
A
What
we're
doing
what
we
envision
our
future
to
be
like
and
who
this
project
is
really
for,
and
so
I
think
it
would
be
good,
even
if
you
know
we're
not
doing
anything
official,
just
kind
of
help,
tamp
down
the
hysteria
and
be
like
no
no
everything's
fine.
This
is
gonna,
be
awesome
and
just
kind
of
set
set
the
right
tone.
The
first
one
is
drupal
camp
florida,
which
is
in
orlando.
A
In
the
beginning
of
march,
I've
submitted
a
session
on
backdrop
there,
I'm
not
sure
it's
going
to
get
accepted
just
because
there's
only
one
day
camp,
but
I'm
happy
to
talk
about
it.
Even
if
that
doesn't
get
accepted.
Just
you
know,
everyone's
gonna
be
like.
What's
going
on
and
and
we'll
kind
of
tell
them,
we
need
help,
and
you
know
it's
a
big
project,
but
it's
gonna
be
better
for
everyone.
If
we
do
it,
which
will
be
good,
we've
got
mid
camp
coming
up
in
chicago,
which
andy
is
probably
attending.
A
We've
got
nyc
camp
in
april.
I
don't
know
if
we
have
anyone
in
our
midst
who
is
in
our
near
new
york
or
wants
to
go
to
nice
camp,
but
we
definitely
could
use
someone
there
on
our
side.
A
Talking
about
this
thing
there,
the
drupal
camp
stanford
here
in
the
bay
area
in
april,
immediately
followed
by
the
html5
developer
conference
the
next
week,
which
nate
now
probably
go
to
one
and
or
both
of
those
I
think
html5
conf
is
one
of
my
favorite
conferences,
because
it's
not
a
drupal
conference
and
it's
kind
of
good
to
see
like
what
the
rest
of
the
world
is
doing
and
so
that'll
be
good.
A
For
backdrop
too,
to
say
like
what
does
the
front-end
community
want,
particularly
since
we're
trying
to
do
a
little
cleanup
on
the
front
end
of
backdrop
and
just
kind
of
see
what
what
html
css
javascript
people
are
doing
these
days
and
make
sure
that
our
platform
is
going
to
be
able
to
help
them
with
those
goals
too
so
that'll
be
fun.
I
submitted
a
conference
or
a
session
for
that,
but
I'm
also
not
sure
that's
going
to
get
accepted
and
there's
no
public
link
to
that.
A
So
it's
not
in
here
then
the
following
week
in
the
bay
area,
we
also
have
civicon,
which
is
a
civil
crm
conference
which
is
happening
here
in
berkeley.
So
I've
also
submitted
a
session
for
that.
It
might
be
a
little
early
to
try
and
sell
the
civic
crm
people
on
backdrop,
just
because
we're
not
going
to
have
a
vcr
and
backdrop
port
quite
yet.
A
But
I
do
think
that
backdrop
and
civic
crm
are
going
to
be
right
in
the
same
market
right
we're
both
targeting
nonprofits
and
people
without
huge
budgets,
and
I
think
that
it
would
be
good
for
us
to
kind
of
pair
up
and
figure
out
how
we
can
work
together.
So
I
would
really
like
to
go
to
that
conference
and
at
least
kind
of
plug
in
and
talk
to
those
people
and
make
sure
that
we're
all
kind
of
in
line
with
what
we
need.
A
We
had
someone
from
civvi
serum
in
our
irc
channel
last
week
asking
questions
and
trying
to
figure
out
how
to
get
involved
and
how
to
get
more
up
to
speed
on
what
backdrop
is
doing,
which
I
think
is
really
good.
So
I
think,
there's
a
great
potential
there
for
good
relations
in
the
future.
So
that's
good.
A
We
also
have
a
drupal
camp
mexico,
as
I
mentioned
before,
nate
and
I
were
invited
to
go
down
there
and
give
a
talk.
So
we
probably
will
mexico
is
close
and
we
really
like
mexico.
So
I
haven't
been
to
mexico
city,
but
it
should
definitely
be
an
adventure
if
nothing
else,
so
that's
kind
of
a
tentative.
Yes
on
our
schedule,
and
then
we
have
drupal
camp
ireland,
which
is
in
may,
which
I've
also
been
asked
to
go
and
speak
there.
B
A
A
Probably
not,
but
we'll
see
how
how
things
shape
up.
I
would
love
to
go
to
ireland.
I've
never
been
there,
but
not
not
nearly
as
as
probable
as
mexico
city.
A
Then
we
have
drupalcon
austin
in
texas
in
july
and
I
will
not
be
there,
but
I'm
sure
nate
will
be.
We
probably
won't
be
doing
a
lot
of
official
backdrop
stuff
at
triplecon
austin,
but
we
will
have
lots
of
people
to
talk
to
you
about
it.
A
If
people
have
questions
so
that'll
be
a
good
place
for
that,
then
we
have
drupalcorn
in
iowa
where
nate
and
I
are
giving
a
keynote
talk
about
backdrop
which
should
be
fun
and
exciting
and
we'll
try
and
also
organize
the
sprint
while
we're
there
too,
and
then
we
have
drupalcon
amsterdam
where
nate
and
I
will
probably
be
again
not
sure
how
much
backdrop
stuff
we
can
do
while
there
but
good
for
talking
if
nothing
else
and
then
we'll
have
bad
camp
in
october.
A
If
we
have
anyone
who's
watching
this
broadcast
or
attending
any
of
these
events
and
wants
to
you
know
talk
about
backdrop
to
these
groups
of
people,
you
don't
have
to
give
a
session
if
you
want
to
give
a
session,
we'll
help
you
with
that,
but
it's
more
important
to
just
kind
of
get
out
there
and
say
what
we're
doing
and
kind
of
the
place
we're
coming
from
that
this
is
you
know
or
something
something
we're
doing
to
help
the
community
that
you
know
we
don't
want.
We
don't.
A
We
have
you
know,
sites
and
businesses
that
need
something
like
drupal
and
that
they,
you
know,
would
be
in
a
financial
hard
place
if
they
had
to
start
over
or
if
they
had
to
move
to
dribble
eight,
and
so
we
want
to
kind
of
make
them
able
to
do
what
they
need
to
do
as
a
business
via
the
web
in
a
way
that
is
sustainable
and
affordable
for
them
and
hopefully
fun
for
their
developers.
A
We'll
see
about
that
so
yeah,
hopefully
that
that
will
all
those
camps
will
just
give
us
a
place
to
kind
of
talk
to
people
and
and
get
things
going,
which
is
good.
A
We
also
have
an
article
coming
up
in
drupal
watchdog,
which
should
be
released
around
around
the
same
time
as
drupalcon
austin,
which
I
think
will
be
good
to
do
the
same
sort
of
thing
and
nate,
and
I
decided
earlier
this
week
we
were
trying
to
come
up
with
like
a
tagline
or
slogan
or
some
kind
of
way
to
position
ourselves.
That
would
resonate
with
people
and
we
decided
we
started
well.
A
Tentatively,
we
started
saying
the
backdrop
is
the
comprehensive
cms
for
non-profits
educations
and
small
and
medium-sized
businesses,
and
I
think
that
if
we
focus
specifically
on
those
markets
like
not
the
big
fish
but
all
the
other
fish
right,
the
little
fish
and
the
medium-sized
fish,
and
particularly
on
the
groups
that
we
know
are
already
interested
in
us
like
nonprofits
educations
right.
A
Those
two
they're
people
who
are
always
looking
for
a
product
that
is
is
good
specifically
for
them,
and
the
small
to
medium-sized
businesses,
the
ones
that
are
currently
using
drupal
right
because
they
found
that
it
does
exactly
what
they
need.
It's
a
little
bit
more
than
wordpress.
It's
I
don't
know
a
little
bit
easier
to
turn
to
exactly
what
they
need,
as
opposed
to
being
the
same
site.
Everyone
else
has
it's
flexible.
A
It
allows
them
to
do
anything
in
the
future
target
those
people
and
say
this
is
a
product
for
you,
and
you
know,
that's
not
to
say
that
there
aren't
other
products
for
them,
but
that
that's
specifically
what
we're
after
and
I
think
that
that'll
help
us
kind
of
focus
rather
than
saying.
Oh,
you
know
we're
we're
like
trouble
but
different.
Let's,
let's
stop
with
this
comparisons
to
drupal
and
say
we're
a
product
for
them
and
then
focus
on
what
it
is
that
they
want
and
make
sure
that
we
deliver
those
things.
A
So
I
think
that
that's
kind
of
what
we're
going
to
start
doing
now
in
our
branding.
I
changed
the
topic
in
the
irc
channel
to
match
that
and
we're
going
to
start
putting
that
some
of
that
branding
out
on
the
web
too.
So
hopefully,
that
resonates
with
everyone
here.
A
All
right,
so
it's
almost
the
end
of
our
time.
So
I'd
like
to
open
this
up
to
general
questions.
If
anyone
has
one
comments,
updates
anything
for
me.
B
Yeah
update
some
on
my
site
just
going
through
the
the
pull
request
list.
Andy.
I
owe
you
a
couple
reviews
on
things,
but
I'm
chugging
through
them.
I
think
we
should
get
all
of
your
current
pull
requests
merged
in
today.
No
problem
they'll,
look
good,
it's
just
that
they're
or
having
some.
There
have
been
some
updates
since
you
made
the
pull
request,
so
just
some
merging
that
needs
to
go
on
so
I'm
working
on
resolving
those
and
I'll
get
them
pushed
up.
Today.