►
From YouTube: Backdrop CMS weekly meeting 6.12
Description
Backdrop CMS: the comprehensive Content Management System for small to med businesses and non-profits.
A
Alright,
we
are
on
air,
happy
Thursday
everybody.
It
is
June
twelfth.
We
are
celebrating
the
return
of
a
backdrop
day
which
will
happen
weekly
every
Thursday
meeting
at
1pm
Pacific
and
followed,
usually
by
sprint,
which
is
exciting
last
week,
as
you
all
probably
know
was
drupalcon.
You
guys
were
in
Austin.
A
Maybe
we
were
in
Hawaii,
so
meeting
Tanakh
with
a
vengeance
and
looking
forward
to
get
this
wrapped
up
and
released
soon,
just
kind
of
exciting,
so
we're
working
on
backdrop
CMS
and
we're
doing
it,
because
we
believe
that
there's
a
cost
that
comes
with
change
and
that
not
all
of
the
existing
Drupal
community
will
be
able
to
make
the
move
to
Drupal
8.
So
we
are
producing
a
system
with
Drupal
8,
comparable
features
on
a
Drupal
7
like
architecture,
the
big
idea
being
that
will
be
easy
to
migrate.
A
Existing
websites
or
upgrade
existing
websites
from
Drupal
7
to
backdrop
and
it'll
be
really
easy
to
port
existing
Drupal
7
modules
to
backdrop
as
well.
So
hopefully
we
can
help
keep
the
costs
down
in
terms
of
development
hours
towards
and
getting
code
updated,
as
well
as
building
websites
out
and
along
the
way
we're
going
to
be
fixing
bugs,
as
in
bugs
that
we're
already
in
Drupal
7
and
need
solutions
fixing
bugs
that
were
fixed
in
Drupal
8.
A
We
want
to
make
sure
we
have
those
same
solutions
into
backdrop
and
any
other
bugs
that
we
find
along
the
way
and
other
things
are
going
to
be
working
on
that
are
less
urgent,
I
suppose
are
simplifying
existing
systems,
and
that
is
where
we
don't
require
very
much
api
change
to
do
so,
and
also
adding
new
features
so
making
sure
that
our
software
continues
to
move
forward
with
technology
is
important.
We
think
we
can
do
that
quickly.
A
If
the
we
aren't
worried
about
changing
the
underlying
code,
our
timeline
we're
hoping
to
release
backdrop
in
July,
which
is
right
around
the
corner.
So
we
need
a
little
bit
of
help.
Getting
this
final
push
done,
which
I
think
we're
pretty
close.
We've
got
some
great
new
features
in
and
we're
doing
a
lot
of
tidying
up
on
major
systems
too.
So
I
think
I
think
we're
think
we
can
do
do
Morgan
ate
some
more
hand.
So
if
anyone
has
any
friends
with
any
free
time,
we
can
tap
them
take
to
get
this
all
done.
A
That
would
be
great.
So
we
are
in
terms
of
our
progress
support.
We've
got
some
major
things
that
are
going
to
be
one
point,
o
release
blockers.
You
may
have
noticed
in
the
last
two
weeks
that
we
released
backdrops
new
logo
and
identity,
so
on
our
Google
hangout
or
Twitter
our
Facebook,
our
website
kind
of
our
github
project
anywhere.
We
had
a
logo
that
used
to
be
a
drop.
We've
now
replaced
it
with
a
new
square,
which
is
the
backdrop
logo.
It's
also
in
the
agenda.
A
If
you
want
to
see
what
it
looks
like
today,
along
with
our
new
font
for
the
logo,
so
we're
going
to
be
working
on
a
complete
website,
redesign
that
includes
this
new
branding
at
some
point
in
the
future.
Probably
after
a
backdrop,
one
point,
okay,
so
so
that's
going
to
be
our
focus
right
now,
but
we
did.
We
are
trying
to
move
away
from
Drupal.
We
want
to
move
away
from
the
drop
because
we
think
that
will
be
a
little
bit
too
similar.
A
So
we've
got
this
new
idea
and
I
think
it's
really
cute.
It's
like
you
can
kind
of
see
underneath
the
the
thing
there's
another
thing,
just
exactly
what
we're
working
on
or
the
engine
behind
the
website
and
it's
a
fractal
which
is
awesome
and
I.
Think
Darius,
who
designed
it
force,
did
a
really
great
job
kind
of
fits
exactly
to
what
we're
thinking
about
with
clean
and
simple
and
and
just
kind
of
getting
the
job
done.
A
B
To
elaborate
on
that
I
think
the
same.
My
stuff
is
actually
the
biggest
Walker's
that
we've
got
I
mean
looking
like
things
like
converting.
You
know,
content
types
and
fields
hasn't
yet
been
undertaken
and
that's
probably
like
the
largest
chunk
of
like
we
have
to
finish
this
because
we
can't
release
vector
up
one
point
Oh
with
like
cmi,
and
it's
kind
of
like
halfway
done
state
right
now,
like
the
underlying
system
is
all
there
but
yeah.
B
A
So
maybe
Andy
if
you've
got
free
cycles
in
the
near
future
and
myself
as
well.
My
our
backdrop,
interns
are
gone
this
month,
we'll
get
one
or
maybe
two
of
them
back
starting
july
first,
but
I
think
that
maybe
we
should
try
and
see
if
we
can
get
to
moving
on
some
of
these
cmi
conversions
and
following
some
documentation,
that's
been
done
and
I
know
contact
module
just
got
converted.
We
can
use
that
as
a
guide.
A
B
A
All
right
and
then
and
other
stuff
we're
working
on
we've
got
a
bunch
of
crafts,
ports
from
Drupal,
7
I
think
these
are
mostly
done.
Most
of
the
final
meta
issue,
I
think,
is
even
in
a
pull
request
that
I
need
to
clean
up
a
little
bit,
which
will
be
good,
and
then
we've
got
this
most
recent
issue
that
just
contains
all
of
the
changes.
I
think
between
seven
to
four
and
seven
to
eight-
that's
also
mostly
done,
and
so
we
should
be
able
to
wrap
those
up
this
week.
A
So
hopefully,
Drupal
7
will
be
done.
The
Drupal
8
backport
list
I've
removed
the
four
giant
metis
that
we're
on
here
I
think
it's
better
for
us
to
work
through
these
lists
in
terms
of
the
things
that
are
most
important
rather
than
looking
through
every
single
issue
and
trying
to
figure
out
if
we
want
the
commit
or
not
so
I-
know,
for
example,
we're
going
to
need
to
see
my
conversions
we're
going
to
need
the
views.
A
Conversions,
we're
going
to
need
like
the
CSS
and
JavaScript
clean
up
those
the
issues
that
we
already
have,
but
there's
a
whole
bunch
of
stuff
in
there
that
we
don't
necessarily
need.
It
would
be
great
if
we
had
the
time
to
look
through
these
seven
thousand
issues
and
figure
out
which
bug
fixes
we
should
just
pour
it
over,
but
considering
the
amount
of
time
that
we
have
left
I
think
it's
best
to
just
focus
on
the
things
that
we
know
we
need.
We
can
make
Meadows
for
things
like
views,
conversions
and
then
compare
those.
A
Even
if
we
can
use
the
patches,
we
can
still
work
through
the
same
list
of
things
to
make
sure
that
we're
not
missing
anything
that
was
included
in
Tripoli.
So
if
we
manage
to
get
those
done,
then
we
do
have
7,000
issues.
We
can
review
and
pick
and
choose
the
ones
that
are
most
important.
I
know
for
me,
every
time
I
run
into
a
bug
with
Drupal
7,
like
I'm,
working
on
a
client
site
and
run
into
a
problem
like
this
thing
is
broken
and
there's
a
solution.
A
I'll
go
and
write
an
issue
for
that.
For
backup
and
try
and
get
it
in,
so
I
think
we're
going
to
be
kind
of
doing
that
for
a
while
until
we
can
get
the
most
important
bugs
down,
or
at
least
the
ones
that
we
know
about,
but
I
think
that,
in
terms
of
the
amount
of
time
we
have
left
focusing
on
most
important
things
first,
as
a
priority
and
bug
fixes,
we
can
also
always
get
in
after
the
release.
So
that's
something
to
think
about.
A
Okay,
other
things,
we've
got
going
on
minor
projects
and
we
are
working
on
separating
the
identity
of
backdrop
from
the
identity
of
Drupal.
We've
done
a
huge
service
in
terms
of
getting
a
new
logo
in
which
is
great.
We've
got
an
issue
in
the
queue
this
is
actually
higher
up,
considers
a
release
blocker,
so
it's
higher
up
in
our
agenda,
but
there's
an
issue
in
the
queue
to
replace
the
word
Drupal.
With
a
word
backdrop:
in
the
code,
we've
got
a
poor
request
on
it
and
I've
reviewed,
probably
75
percent
of
it.
A
It's
really
really
long.
I
probably
finished
up
that
review
today
and
then
what
if
we
could
get
someone
else
to
review
it
too
will
probably
will
need
another
rebase
private
I'm.
It's
ready
to
go
in,
but
I
think
that
that's
going
to
be
huge
for
making
the
code
not
say
Drupal,
which
is
going
to
be
great,
and
then
we've
got
some
other
stuff
too.
In
terms
of
separating
the
identity.
A
So
we
might
change
the
fonts
and
the
colors
and
some
some
basic
things
as
much
as
we
can.
We
might
choose
a
different
icon
set
than
than
triple
eight,
but
having
something
that
looks
different
from
Drupal
7
and
different
from
Triple
Eight
I
think
it's
getting
really
important
for
us
long
term.
So
we're
not
just
the
same
a
different,
so
we've
got
those
things
underway
and
then
user
experience
improvements.
We
need
to
add
a
rich
text.
Editor
I
think
it
would
be
great
if
we
could
focus
on
that.
A
I
think
that
might
even
be
more
important,
maybe
not
more
important,
comparably
important
with
a
the
blocks
and
layouts
thing.
It's
definitely
I
think
an
easier
piece
to
get
in
then
block
some
layout.
So
at
some
point
we
might
try
and
figure
out
what
our
resources
are
and
and
where
would
be
best
to
spend.
What
we
have,
but
I
think
will
be
slightly
embarrassing
before
you're
released
backdrop
without
a
rich
text
editor.
So
that's
on
the
agenda
as
well
and
then
there's
some
terminology
update.
So
it
should
be
quick
and
simple.
A
I
think
the
more
of
these
patches
we
can
get
in
before
we
change
terminology
the
better,
so
I'm,
leaving
that
for
the
last
we've
got
a
lot
of
stuff
that
we're
merging
in
from
Drupal
7
interpolate
keeping
it
the
same
would
be
good
and
then,
of
course
deciding
which
of
those
are
most
important
and
which
ones
are
nice
to
have.
But
not
necessarily
important
will
be
good
too.
A
So
we'll
review
that
here
in
a
week
or
two
and
see
if
there's
anything
that
we
should
just
cut
from
the
list
and
another
stuff
that
you
know
might
be
too
controversial.
And
then
the
theme
system,
cleanup
we've,
been
doing
a
lot
of
work
on
that
I
took
a
bunch
of
my
backdrop,
interns
and
gave
them
theme
system
clean,
clean
of
stuff
to
work
on
we've
already
got
some
of
the
patches
committed,
which
is
great.
We've
got
some
new
stuff
under
way.
A
Consolidation
of
template
files,
removal
of
template
files
aren't
necessary,
I
think
we're
making
great
progress
on
that
and
and
the
things
that
are
laughter.
The
trickiest
things
like
adding
new
theme
hooks
and
removing
the
process,
layer
and
I
think
those
should
I've
got
got
branches
with
work
on
all
those
things
as
well.
So
as
soon
as
we
can
get
tests,
passing
get
some
for
Crescent
for
those,
so
I
think
we're
making
good
progress
on
all
fronts,
which
is
great,
and
we
have
a
section
of
this
meeting
for
updates
from
the
PMC
we
haven't.
A
Had
any
issues
escalated
to
the
PMC,
and
so
we
don't
have
any
updates.
No
blockers,
no
updates,
which
is
great.
We
are
also
looking
to
expand
the
PMC,
so
we're
going
to
be
keeping
an
eye
on
people's
activity
in
the
issue.
Queue
or
people
who
are
talking
about
backdrop
that
maybe
aren't
producing
code
are
also
just
as
valuable.
A
So
if
you
are
interested
in
being
involved
in
backdrop,
decision-making
show
up
and
voice
your
opinions
and
make
sure
that
we
know
who
you
are
and
what
side
of
the
page
you
are
on
on
a
lot
of
issues
and
and
you'll
be
in
contention.
So
just
keep
that
in
mind
and
then
there's
also
a
bunch
of
other
stuff
that
we
need
to
work
on
wind,
an
API
site,
I.
Think
that's
fairly
important.
I
actually
have
a
dribble
code
base
with
code
committed
to
it,
so
it's
underway
and
we
need
to
get
I.
A
Think
Luke
had
volunteered
to
set
up
some
content
types
for
us
on
the
server
where
that's
going
to
live.
So
I'll
follow
up
with
him.
Now
that
we
actually
have
a
Drupal
site,
he
can
work
on,
which
will
be
great
and
and
then
we
also
need
an
update,
server.
I
think
that
can
come
probably
shortly
after
we
release
backdrop,
because
we
won't
have
anyone
needing
to
run
updates
until
there
are
any
updates.
So
we
need
to
have
an
update
server
before
the
first
update,
but
maybe
not
before
one
point.
A
Be
number
two
but
I
think
we
need
the
API
site
at
first,
so
people
can
get
to
one
point,
0
point
0
and
then
we're
gonna
need
an
official
github
service,
so
people
can
register
their
backdrop.
Projects
and
I
think
we've
got
kind
of
a
good
plan,
for
how
can
trip
is
going
to
work
where
we're
going
to
have
a
backdrop
contribute
on
github.
So
anyone
who
wants
to
write
a
module
will
just
be
part
of
this
group.
Well,
we'll
need
to
be
inducted
or
nominated,
or
something
when
we
hear
it
out.
A
Oh
and
then
they'll
be
able
to
post
their
modules
there
and
those
modules
will
be
included
in
the
official
backdrop
modules
and
then
additional
modules
can
be
registered,
a
backdrop
modules,
but
they
won't
be
supported
or
official
or
whatever
until
they
get
we'll
figure
something
out.
We
have
what
we
have
a
plan.
We
just
need
to
figure
out
language
and
how
to
make
the
plan
happen.
A
So
I
think
we're
on
the
right
track
for
that,
but
we
will
need
to
get
hub
service
and
I
know
that
we've
had
some
people
thinking
about
that
a
little
bit,
but
we
should
maybe
get
serious
about
that
too,
and
then
our
primary
website,
we
talked
about
doing
a
little
redesign
with
a
logo
and
font
that
will
again
come
after
the
one
point
0
release.
We
also
want
to
add
a
show
cakes
as
soon
as
we
have
websites
to
showcase
Oh
be
good
to
get
them
up
there.
A
A
So
having
some
place
to
put
those
up
would
be
good
and
then,
of
course,
we'll
need
pages
to
list
our
modules
and
themes
that
are
aggregated
by
our
github
service,
which
doesn't
exist
yet
I
think
that
all
this
stuff
is
is
less
urgent
than
getting
the
project
ready,
so
we'll
focus
on
that
first
and
then
build
all
the
stuff
around
it
after
it.
So
so
today,
after
this
meeting,
you
know
be
around
for
half
an
hour,
then
we
need
to
run
up
for
an
errand,
but
we'll
be
back
again
this
afternoon.
A
So
we're
hoping
that
the
drupal
corn,
which
is
july,
seventeenth
and
nineteenth,
will
either
be
like
the
week
before
the
release
or
the
week
up
the
release
and
then
Twin
Cities
drupalcamp
will
be
just
after
the
release.
So
we're
hoping
that
Drupal
corn
camp
will
be
getting
a
bunch
of
people,
helping
us
get
stuff
done
and
then
afterwards
we'll
be
reporting
first
modules
to
backtrack
so
or
if
there
are
bugs
fixing
the
bugs.
A
But
hopefully
we
won't
need
a
whole
sprint
room
worth
of
people
fixing
bugs
so
I
think
we've
got
a
lot
of
exciting
things
in
our
agenda,
which
is
really
great,
but
yeah
I.
Guess
we
should
open
up
to
see
if
anyone
else
here
has
anything
you
want
to
add
or
any
questions
or
any
concerns
anything
that
we
should
address
in
this,
be.
B
D
Well,
I,
I
think
the
controls
posting
an
IRC,
but
I
think
they
can't
rib
needs
to
be
sooner
rather
than
later,
so
the
xml-rpc
module
needed
to
be
updated
to
chase
the
change
the
info
file
to
require
back
up
instead
of
core.
So
I
pushed
a
pull
request
to
that
which
there's
no
response
for
so
in
order
for
anyone
to
find
anything
or
work
on
anything,
there's
going
to
have
to
be
some
directory
of
some
kind
pointing
to
what's
out
there.
A
D
A
A
A
Don't
think
you
used
to
be
able
to
transfer
a
project
from
owner
to
to
a
different
one,
but
what
that
does
is
it
means
that
the
project
no
not
no
longer
lives,
a
slash
user,
slash
project,
name
that
lives
at
/
backdrop,
contribs
watch
project
name
and
that's
basically
the
creation
of
an
official
github
project,
and
that
means
that
anyone
who's
a
get
a
backdrop.
Maintainer
well
then,
have
the
authority
to
do
things
like
merged
pull
requests
from
other
people,
so
it
kind
of
made
it
will
kind
of
alleviate
that
bottleneck.
I'm
like
oh.
A
We
have
one
person
who
volunteered
to
maintain
xmlrpc,
but
he
wasn't
around
that
week,
if
not
in
there
around,
that
we
can
look
at
your
poor
best
and
so
that
I
think
is,
is
going
to
kind
of
prevent
a
bottle
knife
pink
and
rib
space,
and
it
will
also
help
create
a
first
listing
of
officially
supported
module.
So
things
that
we've
removed
from
court
will
go
in.
A
Things
like
you
know,
xmlrpc
will
go
in
there,
anything
that
anyone
is
working
on
could
be
put
in
there.
It's
just
me
need
to
have
some
process
in
place
for,
like,
oh,
you
know,
I'm
writing,
X
module.
How
do
I
make
it
official
that
we
haven't
figured
out
yet,
but
I
think
you're
right
in
that
we
need
to
set
up
this
group
so
that
people
can
find
it,
especially
before
we
have
that
modules
page
where
people
can
go
to
search.
D
A
But
I
think
that
the
way
that
we're
going
to
organize
it
is
that,
if,
if
you
are
a
module
maintainer,
it
will
be
like,
like
you're
a
subsystem
maintainer
for
for,
like
you
volunteer
for
this
module
and
that's
the
only
thing
you're
responsible
for,
but
if
you
find
a
bug
in
another
module,
you'll
be
able
to
fix
it.
So,
okay,
so
we're.
D
Working
on
the
city
crm
integration,
which
there's
a
Summer
of
Code
Drupal
8
project,
combined
with
the
fact
that
cities
essentially
fan
loan
system
that
just
has
some
level
of
integration
through
these
rules,
so
that
court
should
be
relatively
easy.
However,
that
module
would
exist
within
the
city
CRM
infrastructure
not
within,
in
order
to
be
part
of
that
group
and
be
maintained
by
that
good.
So
you
have
this
issue
where
you're
going
to
have
existing
groups
that
are
maintaining
code.
B
Jen
can
I
can
try
and
explain
it.
I
don't
want
okay,
so
so
here's
the
here's
the
deal
Kevin
is
that
you
we
won't
need
to
put
every
into
into
this
backdrop,
contribute
it's
basically
kind
of
a
way
of
you
could
say
that
the
backdrop
contribs
kind
of
like
a
list
of
officially
sanctioned
projects,
if
you
will,
but
it's
supported
to
that's.
B
Like
basically
group
community
supported
modules,
instead
of
like
just
some
random
module
that
somebody
wrote
or
in
your
guys's
case,
if
there's
another
group
that
maintains
you
know
a
collection
of
backdrop,
modules,
those
would
continue
to
live
in
some
other
group
or
some
other
location.
Are
you
guys?
Are
you
guys
maintaining
stuff
on
github
or
is
it
somewhere
else?
Well,.
D
I
mean
because
we
do
stuff
with
pantheon,
everything
has
to
eventually
get
to
get
hug
okay.
So
that's
there's
this
back
and
forth
with
the
benefits
of
distribution
packaging.
This
is
the
downside
of
everything
else.
That's
through
the
lowland
infrastructure,
so
you
know
it's
if
we're
doing
both
right
now,
it's
not
very
efficient,
there's
a
lot
of
back
and
forth
and
things
get
out
of
thing.
D
But
that's
that's
the
way
it
happens
right
now,
so
spacey
Iran
has
its
own
collection
and
then
the
community
media
stuff
is
done
on
top
of
that,
going
back
and
forth
between
the
two
systems.
So
right
now
it's
a
mess.
It
would
be
nice
to
clean
that
up,
and
so
that's
why
I'm
just
trying
to
wrap
my
head
around
how
this
is
going
to
play
out.
So
really
these
modules
that
could
be
fall
into
three
different
get
help
routes
that
already
exist
in
this
case
yeah.
B
B
D
B
The
integration
with
with
github
itself,
like
the
service
that
receives
the
github
notifications
and
then
I'm,
not
really
sure
how
that
how
that
translates
into
Drupal,
but
there's
a
good
chance
that
the
the
service
that
listens
to
the
requests
from
github,
like
as
actual
events
and
actions,
happen
that
that
would
still
be
nodejs.
Just
because
it
seems
like
that's
generally
kind
of
the
preferred
API
integration
for
github.
Like.
A
B
Current
system
right
now,
where,
if
you
file
a
pull
request,
you
automatically
are
granted
administrative
privileges
on
the
on
the
issue
queue
repository,
this
uq
repository
doesn't
have
any
code
in
it.
It's
just
so
that
you
can
manage
and
like
tag
and
categorize
issues,
we've
got
that
service
in
place
already,
and
that's
that's
already
in
node.js
as
well.
Okay,
but
yeah
I'm,
not
really.
A
Source,
I
think,
is
the
the
major
issue
we're
trying
to
solve
right
where,
when
someone
Forks
a
project,
they
get
a
copy
of
that
project
under
their
name
and
then
someone
else
Forks
and
they
get
a
copy
under
their
name
and
when
it
changes
hands,
you
don't
want
the
source
of
that
project
moving
around.
So
if
we
can
say
like
the
canonical
source
of
this
project,
is
you
know
backdrop
contribs,
lash,
I,
don't
know
web
form
yeah
and
it
doesn't
matter.
If
your
web
form
maintainer,
you
know,
needs
to
take
year.
A
Sabbatical,
it's
not
going
to
come
back
drop,
calm,
/!
You
know.
If
someone
else
web
form,
it's
gonna
stay
where
it
was
so
you
can
just
add
and
remove
maintainers.
But
if
you
already
have
a
group,
that's
meeting
that
managing
that
project
so
that
it
sets
of
a
serum,
/,
City,
serum
or
whatever
it
is.
Then
you
already
have
your
own
group
of
people
where
you
can
move
it
from
place
to
place
and
it
doesn't
become
quite
such
an
issue
and
if
somebody
needs
to
leave
for
a
year,
someone
else
needs
to
come
back
now.
A
B
Yeah
sorry
I
hope
that
makes
sense
in
general,
where
the
project
lives
as
long
as
it's
on
github
isn't
isn't
an
issue.
The
only
reason
we're
suggesting
this
a
backdrop
contribute
is
to
make
it
so
that
we
can
deal
with
like
abandoned
modules
or
maintenance
of
modules
like
as
a
group
instead
of
as
individuals
just
because
the
individual
repository
set
up
on
on
kid
hub.
Just
really,
since
it's
not
really
group
friendly,
it's
it's
like
one
person,
it's
kind
of
the
king
of
the
module.
B
A
It'll
also
help
create
like,
if
you
give
people
a
sense
of
ownership
over
it.
You
know
like
not
only
here.
You
know
you
created
your
own
module.
You
already
owned
that,
but
also
like
okay
you're
you're
in
you're
in
the
group.
We,
you
know
we're
giving
your
module
this
official
status,
which
means
you
now
take
care
of
it.
But
you
know
you
can
help
other
stuff
too.
A
I
think
it'll
kind
of
help
foster
the
community
a
little
more
rather
than
being
github,
so
everyone's
on
their
own,
just
including
them
in
this
group
and
say
your
partner
to
get
you
know,
backdrop
contribute
I,
think,
will
kind
of
help
us
create
a
little
bit
more
of
a
community
in
an
environment
like
github,
where
there
isn't
really
any
community
to
be
had
so
I
think
that'll.
Help
too.
A
Think
the
issue
is
that
at
least
what
I
think
Kevin
was
bringing
up
is
that
we
need
to
figure
out
our
github
service
issue
so
that
people
who
are
working
on
community
stuff,
because
my
solution
was
like
I'll-
just
put
them
in
the
group.
But
you
bring
up
a
good
point
that
that's
not
a
solution
for
every
issue.
B
I'll
see
safeties
got
time
available.
He
brought
our
existing
integration
yeah.
Fortunately,
it's
all
really
pretty
trivial.
We
already
have
a
server
setup
that
is
like
the
continuous
integration
server
that
has
node
installed
on
it.
That's
already
listening
to
events
from
github
it
just
that
it's
not
listening
for
a
comprehensive
suite
of
events
at
this
point
which
we
need
to
expand
out
to
denigrate
this
for
the
project's
repositories.
Okay,.
A
All
right
and
then
I
can
take
a
look
at
the
projects
that
we
wanted
in
include
already
and
see.
If
we
can
get
a
subset
running
in
backdrop,
Kendra.
My
only
set
that
up
when
we
got
the
logo
I
was
like
I
want
to
put
the
logo
everywhere.
I'm
gonna
put
make
my
other
places,
but
the
logo,
we
didn't
actually
do
anything
half
of
anything
yeah.
So
you
think
they'll
make
the
listing
get
those
on
yeah.
B
Pretty
much
good
candidates,
for
that
is
everything
that
we
removed
core
yeah.
So
the
idea
I
mean
the
reason
why
we
removed
them
from
core
was
twofold.
One
was
to
reduce
the
complexity
of
core
and
the
second
one
was
to
make
it
so
that
we
didn't
have
to
maintain
it
for
like.
We
didn't
have
to
convert
it
for
the
initial
release
of
backdrop.
B
So
we
can
put
those
into
the
contributory,
but
they
won't
be
fully
converted
yet
because
in
her
one
of
the
entire
points
was
to
make
it
so
that
we
didn't
have
to
maintain
focus
modules,
but
but
yeah,
some
of
them,
like
xml-rpc,
were
basically
already
converted,
like
Marcus,
did
a
good
job
of
converting
the
xml
RPC
module.
But
now
he
shouldn't
be
the
only
one
responsible
for
that
module
like
he
should
have
a
group
of
people
that
are
interested
in
maintaining
xmlrpc,
helping
and
working
on
it
with
them.
C
A
The
in
get
help
we
were
talking
about
I'm,
trying
to
find
a
place
for
people
to
have
conversations
about
back
job,
and
we
decided
that
we
were
going
to
use
stack
exchange
for
questions
and
answers
so
that
we
didn't
have
to
have
a
you
know:
support
requests
in
our
github
issue
cues,
but
somebody
brought
up
the
point
that
if
you
ask
questions
like,
what's
your
favorite
backdrop,
theme
those
get
removed
from
stack
exchange,
those
aren't
it
isn't
a
place
for
conversations,
it's
just
a
place
for
questions
and
answers.
So
then
the
issue
became.
A
Where
are
we
going
to
have
conversations
about
backdrop
like?
Where
do
we
have
a
place?
To
put
you
know,
what's
your
favorite
theme?
Are
we
going
to
say?
No
people
should
have
this
conversation
on
Twitter
put
it
on
your
own
blog,
or
are
we
going
to
provide
place
for
those
conversations
to
happen?
Even
if
it's
something
that
already
exists
like
disqus,
I
think,
was
something
that
was
recommended
as
an
option
for
having
this
conversation?
Is
this.
B
Course
I
think
his
discourse
yeah,
although
I'm
yeah
I,
don't
think
we've
reached
any
real,
solid
conclusions
about
that.
Yet,
but
yeah
there
is
an
ongoing
issue
about.
You
know
where
does
just
general
chat
happen
like
general
discussion,
and
it's
I
haven't
posted
this
back
to
that
issue.
Yet,
although
I
have
like
some
feedback
that
the
initial
the
original
poster
dok1
lon,
actually
it
kind
of
kind
of
proved
an
interesting
point
that
he
was
trying
to
get
involved.
But
I
couldn't
find
a
place
to
actually
like
just
post
general
discussion.
B
A
Not
sure
that
github
is
the
right
place
for
that
question,
though
right,
that's
good,
that's
the
thing
and
I
also
think
that
we're
gonna
run
into
this
issue
where
there's
so
much
great
area
between
like
support,
request,
discussion,
feature
requests
like
you
know,
trying
to
Delaney
one
goes
one
place,
and
one
goes.
The
other
place
is
going
to
be
really
hard
because
we
aren't
going
to
be
able
to
say.
Oh
this
shouldn't
be
on
github.
A
It
should
be
on
Stack
Exchange
transfer
issued
a
stack
exchange
is
not
an
option
right,
so
I
think
like
setting
too
many
rules
about
where
things
happen
is
going
to
be
hard.
I.
Think,
what's
going
to
happen,
naturally,
is
that
people
who
have
questions
are
going
to
ask
them
on
Stack,
Exchange
and
people
who
have
bug.
Reports
are
going
to
put
them
on
github
and
probably
everyone
else
will
put
them
everywhere.
I
think.
A
Think
having
guidelines
of
like,
if
you
have
questions
sm
on
Stack
Exchange,
is
useful,
because
then
you
know
people
in
the
queue
can
say.
Oh
you
know
this
should
be
asked
on
Stack
Exchange
right,
here's,
an
answer
on
SEC
exchange
or
something
but
I.
Don't
think
that
we
should
build
a
forum
specifically
for
backdrop.
I
think
we
should
let
people
do
that
wherever
they
want
to
do
it.
Yeah.
C
Okay,
yeah
I'm,
just
saying
because
you
know,
since
the
backdraft
motto
is
a
small
business
and
nonprofits
and
so
forth.
You
know
like
when
you
come
into
the
Drupal
community.
It's
like
you
must
answer
all
your
questions
on
IRC
but
which,
which
contributes
to
the
dough,
well
push
centric
your
drupal
ISM
world.
But
if,
if
backdrop
maybe
he
wants
to
migrate
back
roll
back
from
that.
B
A
B
B
A
A
D
A
D
Be
back
in
time,
if
you
set
a
mailman
I
mean
all
of
the
drupal.org
lists
are
log
the
fact
that
anytime
anybody
asks
a
question.
They're
told
that
that's
the
wrong
list.
They
should
never
ask
a
question
via
email
is
a
little
ridiculous,
but
that
you
know
you
can
see
the
log
of
that
happening
over
and
over
again
every
month,
but
yeah
I
mean
you
can
have
public
email
lists
and
emails
of
pretty
easy.
We
accessible
in
the
universally
used
tool
so.
A
When
people
had
questions
you
could
answer,
but
the
volume
of
email
that
I
got
from
Drupal
was
so
ridiculous
that
I
just
set
them
all
up
to
archive
and
was
like
one
day,
I'll
read
them
and
I
never
did,
and
even
though,
like
those
email
lists
to
get
like
are
kept
in
a
way
that
you
can
search
them
on
the
web.
Like
you
know
a
lot
of
times,
you're
looking
for
answers
need
to
come
up
across.
A
Like
you
know,
Google's
mailing
list
results
I
find
them
hard
to
manage,
like
the
fact
that
some
people's
email
clients
like
copy
the
email
messages
in
different
orders
and
others
I,
don't
know
it.
Just
it
felt
like
I
feel,
like
there's
got
to
be
a
better
solution.
We've
been
doing
this
long
enough,
certainly
I'm.
B
Yeah
I
think
making
it
accessible
via
the
web
is
probably
the
most
important
thing
and
I
mean
there's
craft
yields
up
there
like
mailman.
You
know,
and
one
point
you
know:
Google
Groups
was
actually
pretty
good,
but
they
kind
of
locked
down
their
email
capabilities
recently,
which
has
been
kind
of
frustrating
but
yeah.
Somehow
I
need
to
make
it
accessible
via
the
web.
That's
that's
probably
most
important
thing,
something
like
oh
you're
just
getting
started
like
you
know:
community
dot
backdrop,
CMS,
dot,
org
or
something
like
that.
Someplace,
where
people
get
this
post.
B
A
A
Okay,
well,
I
think
it's
definitely
worth
discussing
him.
It
would
be
good
to
have
something
that
everyone
could
have
access
to.
I
feel
like
everybody
already
knows
how
to
use
their
emails.
There's
definitely
some
upsides
to
that.
I
also
feel,
like
you
know,
having
something
very
stack
exchange
like
we're.
All
you
have
to
do
is,
like
you
know,
Yahoo
Answers,
style
type
in
your
question
and
get
answers
is
easier
for
people
who
are
not
developers
to
use,
but
it's
also
like
stock
exchanges.
A
Self
is
a
very
developer,
focused
tool,
so
I
don't
know
if
discourse
is
more
or
less
developer
focused
and
that's
something
that
people
would
use
anyway.
I
just
feel
like
saying:
okay.
Well,
you
know
you
need
to
get
hub
account
if
you're
to
create
a
a
bug
report,
but
you
need
a
discourse
account
if
you
want
to
have
a
conversation,
but
you
need
to
have
a
backdrop.
Cms
account,
if
you
want
to
like
register
our
project
is
kind
of
already
starting
to
like
break
things
up
in
a
way
that
isn't
very
intuitive.
A
Where
I
feel
like
you
know,
the
reason
we
went
with
github
is
because
all
of
your
lovers
already
have
a
github
account
and,
like
you
know,
you
don't
need
to
create
a
backdrop
account
unless
you
want
to
register
your
project.
I
think,
is
valid,
but
now
saying
we
just
want
to
ask
a
question:
I
don't
know,
wait,
we
need
I.
Think
email
is
definitely
easiest,
but
we
are
going
to
run
up
with
this
scale
issue.
A
So
maybe
maybe
just
having
like
an
introductory
getting
started
with
back
job
email
list
would
be
good
but
yeah.
It
would
be
good
to
have
someone
who
is
responsible
for
actually
touching
that
in
terms
of
making
sure
questions
get
answered.
So
it's
not
just
a
whole
bunch
of
questions
and
then
people
getting
angry
Leah
having
more
more
gateways
to
getting
less
developer.
Focused
people
to
success,
I
think
is
going
to
be
important.
Problems
needs
solving.
B
A
I
think
are
important,
so
Doug's
I'm,
not
sure
if
that
the
time
for
having
this
conversation
is
on.
This
particular
call,
but
I
think
that
it's
good
to
talk
about
it.
Now
in
this
live
broadcast
format
and
say
we
do
need
to
think
about
if
we're
gonna
be
paying
for
developers
for
that
and
I
from
how
we're
going
to
be
betting
proposals
out
to
people
who
might
want
to
give
us
money
how
to
properly
encourage
people
who
believe
in
the
project
to
invest
in
it,
and
that's
definitely
good
for
that
so
dog.
A
Maybe
we
should
talk.
They
donate
and
I
have
to
leave
here
in
the
next
15
minutes.
But
later
this
afternoon
are
all
responding
your
email.
We
can
set
up
the
time
to
have
a
more
private
conversation
about
your
particular
suggestion,
but
yeah,
especially
with
that
backdrop
coming
out
soon.
It
would
be
good
to
have
a
plan
for
how
we're
gonna
support
this
long
term
in
terms
of
hiring
developers
and
guy
debate,
we
made
a
little
bit
of
money
from
our
any
google
campaign.