►
From YouTube: Backdrop CMS weekly meeting 1/29
Description
Weekly status meeting for Backdrop CMS. What's new, what's pressing, and what we're doing about it all.
Agenda document: http://bit.ly/1yTOw5i
A
Alright,
we're
on
air.
It
is
Thursday
January
29th.
We
are
having
a
backdrop
CMS
weekly
status
meeting.
It
has
been
two
weeks
since
the
release
of
backdrop
1
point
0,
which
is
to
differ
exciting,
so
we're
going
to
go
through
a
couple
of
high-level
items
to
discuss
today.
One
thing
that
I've
been
asked
to
mention
beginning
of
meetings
is
if
anyone
is
on
a
meeting
now
or
joins
the
meeting
mate
later.
A
So
the
first
item
on
our
agenda
every
week
is
updates
from
the
project
management
committee
and
a
lot
of
times
there's
a
lot
of
silence.
There
actually
don't
have
anything
super
important.
We
need
to
talk
about
this
week.
We
had
a
couple
of
things
happen
that
how
are
both
good
and
bad?
The
first
thing
is
that
we've
had
a
whole
bunch
of
activity
in
backrub,
since
bactrim
has
been
out,
which
is
great
and
part
of
that
activity
is
a
whole
bunch
of
new
people.
A
Coming
into
a
backdrop
working
on
things,
porting
modules,
creating
new
themes
and
requesting
access
to
join
the
backdrop
contributed
a
group
on
github
and
we
have
a
pretty
straightforward
process
for
that.
You
just
ask
for
access,
and
we
ask
to
see
your
code
will
do
a
really
quick
spot-check
review
just
to
make
sure
that
you
understand
the
significant
differences
between
backdrop
and
Drupal.
The
Rio
is
really
more
to
help
you
than
it
is
anything
else,
and
then,
once
we've
looked
at
your
code,
confirmed
that
you're
willing
to
agree
to
the
agreement.
A
That
is
part
of
being
part
of
backup
group.
Then
we
grant
you
permission.
But
this
week
we
had
a
one
person
in
particular
who
applied
to
the
group
and
then
wouldn't
work
with
us
in
order
to
get
through
that
process
to
get
granted
access,
and
so
we
started
kind
of
evaluating
like
well.
Maybe
we
should
have
some
more
rigorous
standards.
Maybe
we
need
a
code
of
conduct.
Maybe
we
need
some
more
clear
definitions
of
what
it
means
to
be
part
of
this
group
and
going
through
that
process.
A
We
realized
that
three
things
we're
going
to
be
super
important
to
us
as
a
community
going
going
forward.
The
first
one
is
the
ability
to
communicate
clearly
in
an
issue
queue.
So
someone
asks
a
question
and
someone
gets
an
answer
and
then
someone
asks
the
question
again
and
someone
gets
the
answer
in
a
different
way
and
that
continues
for
a
really
long
period
of
time.
A
If
there's
a
problem
with
that
communication
happening,
that's
going
to
be
a
problem
for
the
community
as
a
whole
is
how
do
you
get
anything
done
if
you
can't
communicate
clearly
in
the
issue
queue?
We
know
some
people
don't
have
English
as
their
first
language,
when
we
are
generally
trying
to
be
su
cama
dating
it's
possible
for
those
people.
Communicating
in
English-
maybe
not
usually
speaking
in
English,
but
just
being
able
to
make
progress
in
that
queue
is
important.
The
second
thing:
that's
suchen,
so
the
ability
to
share
and
work
on
things
together.
A
If
someone
says
hey,
can
I
see
your
code,
the
answer
should
be
door.
Here's
my
code,
especially
if
it's
going
to
be
open
source
code
anyway
and
we're
going
to
be
sharing
in
the
long
term.
If
you
say,
hey
can
I
see
your
code
and
someone
says
no
for
various
different
reasons.
You
know
we'll
try
and
get
to
the
bottom
of
what
the
reasons
are:
try
and
work
out.
Any
issues
with
you
know
why
that
code
doesn't
want
to
be
shared
and
figure
out.
A
If
there's
a
way,
we
can
help
get
through
that.
But
at
some
point,
if
you're
not
going
to
share
your
coat,
that's
not
not
very
collaborative,
and
that
that's
going
to
be
a
problem
as
well
and
then
the
third
thing
is
making
sure
that
people.
This
is
the
most
important
one,
making
sure
that
people
have
respect
for
each
other.
So
we're
going
to
be
a
community
of
a
bunch
of
different
developers
of
various
different
skillsets
experiences.
Whatever
people
are
really
proud
of
their
work,
you
do
a
bunch
of
work.
A
You
poured
something
tobacco
if
you
write
something
new,
you
post
it,
you
don't
want
to
have
someone
who
is
a
talented
developer,
look
at
junior
developers,
code
and
say
this
is
broken
or
you
know
this
is
equivalent
to
like
a
dev
release
on
drupal.org.
It
needs
to
be
the
kind
of
thing
where
yeah
sometimes
code
doesn't
work.
Well,
sometimes
it's
not
done
yet,
but
helping
people
through
that
process
of
making
code
better
in
a
way
that
is
positive,
is
going
to
be
super
important.
A
Queue
is
also
something
that's
really
important
and
we
ran
into
all
these
problems
with
this
one
application
where
we
were
having
problems,
communicating
problems,
collaborating
and
didn't
see
a
respect
for
other
developers,
and
so
we
decided
to
reject
this
person's
application
for
access
to
the
contribute.
We
also
decided
that
no
rejection
and
any
application
should
be
final,
so
it's
basically
just
a
delay
that
says
you
know
hey.
A
These
are
the
problems
we're
having
today,
you
can
have
a
30
day
grace
period
and
then
you
can
try
and
apply
again
and
if
the
second
application
doesn't
have
any
of
those
problems,
we
can
communicate
clearly
we're
able
to
collaborate.
You
understand
how
to
be
respectful
for
other
developers.
You
get
a
second
shot,
so
no
one
is
ever
completely
nixed
from
the
backdrop
community,
but
we
do
want
to
kind
of
set
some
standards
about
how
people
and
code
should
be
treated,
and
so
along
those
lines.
A
We
are
now
also
working
on
a
code
of
conduct
and
we
have
a
couple
of
really
great
sources
to
start
from.
I
have
one
here
on
github
that
we
used
for
bad
camp
last
year,
which
I
think
is
a
great
starting
point.
It
is
at
a
comp
code
of
conduct
com,
we're
going
to
adapt
a
little
bit
to
work
for
communities
and
not
just
conferences
and
we're
going
to
try
and
make
that
backdrops
code
of
conduct
will
post
it
somewhere.
A
A
How
do
we
solve
this
in
a
way
that
is
not
too
off-putting
to
the
person
who
is
applying
like
we
want
them
to
come
back
and
try
again
in
a
month,
but
does
set
set
a
standard
for
how
people
should
be
treated
in
the
factor
of
community,
and
so
that's
kind
of
a
big
important
update
their
from
from
the
PMC
and
I.
Don't
know
neat
if
you
want
to
add
anything
to
that.
B
Well,
I
yeah.
Let's
also
add
that
it's
not
a
very
complicated
process
to
go
through
to
get
access
to
the
contributory
and
there's
also.
We
make
it
really
clear
at
the
top
of
the
repository
application
from
repository
I
guess
it
is
the
you
know.
The
issue
queue
that
we
use
for
managing
who
gets
access
to
the
repository
that
you
don't
need
access
to
it.
In
the
first
place,
you
can
put
your
code
anywhere,
you
want.
B
This
is
really
just
a
central
love
it
it's
the
only
central
location
we
have
now
until
we
build
out
the
repository
on
backdrop,
CMS
org,
so
there's
some
value
there
that
it
will
make
it
so
people
can
find
your
modules.
But
the
purpose
of
this
group
is
to
allow
people
to
collaborate
together
and
to
share
the
responsibility
of
module
maintenance
and
to
help
it
so
that
them,
if
we
need
to
make
security
updates
within
the
contributory
that
other
people
are
empowered
to
do
that.
B
A
But
if,
if
you
put
that
code
into
the
backdrop,
contribute
pastor
and
then
go
on
vacation
for
a
couple
of
years,
we
can
then
reassign
that
project
to
another
maintainer
for
a
period
of
time
or
you
know,
and
definitely
if
we
may
need
to
move
stuff
around.
So
it
does
help
us
with
abandoned
projects.
If
it's
all
in
a
group,
it
helps
us
security
and
it
helps
us
with
collaboration.
So
we
would
like
to
encourage
that
people
put
their
contributed
modules,
especially
once
they're
going
to
be
super
important
into
this
group.
A
But
it
is
by
no
means
a
requirement.
If
you
have
a
company
policy
that
you're
contributed
code
needs
to
be
under
your
company's
account.
That's
also
perfectly
fine,
and
once
we
do
have
module
listings
on
backdrop,
CMS
network,
there
will
be
a
place
in
there
where
you
can
create
basically
a
note
for
your
project
and
you
can
link
to
its
canonical
source.
So
if
that
source
is
not
backdrop,
contribu
can
enlist
that
they're.
A
Obviously
right
now,
we
don't
have
that
tool
built
me,
but
so
the
canonical
source,
where
everything
is
in
this
backdrop,
contribute
for
now,
but
we
will
get
that
up
before
too
long
and
hopefully
that
will
help
resolve
some
of
these
issues.
So,
although
there's
a
whole
bunch
of
happening
right
now,
there's
a
whole
bunch
of
ports
going
on
and
there's
a
whole
bunch
of
people
collaborating
in
the
kinship
group,
which
is
good.
That
is
not
the
only
way
to
do
things.
A
So,
if
you
apply
to
the
backdrop
kinship
group
and
for
whatever
reason
you
end
up
being
one
of
these
edge
cases
that
gets
rejected,
that
doesn't
mean
you
can't
contribute
your
code
to
back
Jeff.
It
just
means
it
won't
go
in
that
group
for
now
and
then
a
month
from
now.
If
you
wanted
to
apply
again,
it
can
so
yeah
Ted.
What
I
think
it
was
important
for
us
to
to
come
to
the
realization
that
we
did
need
a
code
of
conduct
and
we
didn't
have
some
standards
around
how
people
should
be
treated.
B
One
more
thing
on
the
good
news
side
of
things
is
a
status
report,
how
many
people
we've
had
joined
in
the
past
two
weeks,
we've
had
a
dozen
new
people
join
the
contribute,
which
is
fantastic,
and
in
that
time
they
ported
or
started
porting
29
total
projects,
which
is
fantastic.
A
lot
of
those
like
top
10
contributed
modules
are
well
underway.
B
We've
got
three
or
four
themes
that
are
underway
that
have
been
actually
a
couple
of
them
are
complete
full
ports,
and
it's
just
really
exciting
that
in
that
very
short
window
of
time,
a
lot
of
people.
This
is
the
very
first
time
they've
looked
it
back
drop
in
the
last
two
weeks
since
backdrop
came
out
and
in
that
time
they've
already
not
only
downloaded
and
installed
back
job,
but
they've
managed
to
do
a
port
of
their
code
from
Drupal
7
to
backdrop
in
that
time.
B
So
that's
a
huge
accomplishment
that
just
that
short
window
they're
able
to
not
only
download
and
use
backdrop
but
they're
also
able
to
port
all
of
their
code
to
backdrop
and
I
think
that
that
validates
a
lot
of
everything
that
we've
been
working
towards
for
the
last
year
and
a
half
making
it
so
that
people
had
an
easy
way
forward
to
another
another
platform
that
we've
sustained
for
a
long
time
to
come.
So
I'm
really
excited
and
I
think
the
ease
of
porting
has
already
really
kind
of
proven
itself.
A
All
right,
that's
the
end
of
our
pnc
updates,
a
lot
of
good
stuff,
a
little
workers
and
stuff,
but
I
think
we
got
it
all
under
control.
Next
on
our
agenda
here
is
that
we
have
upcoming
releases.
We
have
a
patch
release.
We
haven't
yet
determined
to
the
date
for
our
next
patch
release,
because
we
don't
have
any
super
serious
bugs
that
need
to
be
fixed
urgently.
A
We
didn't
find
some
bugs
since
the
last
patch
release
and
we
have
started
fixing
them,
but
we
don't
have
anything,
that's
rich
enough
that
we
need
to
schedule
a
new
patch
release,
which
is
good
if
anyone
is
using
backdrop
when
you
have
discovered
above
that,
you
think
is
super
problematic
in
or
just
urgent.
Let
us
know
I
file
it
in
the
issue.
Queue
will
fix
it
and
we'll
get
a
release
out
shortly.
So
that's
our
perhaps,
is
therefore
that
our
next
minor
release
will
be
released
on
May
fifteenth,
and
that
should
be
one
point.
A
One
point:
oh
things
on
the
agenda
for
that
release.
Let's
say
this
is
lower
in
the
meeting
here,
but
we're
currently
planning
on
including
a
built-in
rich
text
editor
a
version
of
the
token
module.
Those
are
ready,
token
support
and
for
but
we
want
to
get
token
UI
and
a
little
more
support
for
tokens
into
core,
and
then
we
want
to
include
pasado
module,
and
so
our
process,
for
that
is
first
things.
A
First,
we're
going
to
port
these
modules
to
backdrop,
and
we
do
have
beginnings
of
both
of
them
in
the
backdrop,
contribute
positive,
and
this
is
not
the
forum
these
things
are
going
to
be
in
when
they
get
into
poor
we're
going
to
refactor
them
a
little
bit
when,
as
they
go
into
core,
make
the
user
interfaces
more
integrated
with,
where
they're
supposed
to
be
changing,
stuff
and
and
maybe
even
pare
down
features
we'll
see
how
much
of
it
we
can
get
in.
But
the
first
thing
is
to
get
the
imported,
so
that
is
underway.
A
The
rich
text
editor,
that's
not
something
we
have
necessarily
a
module
in
Drupal
7.
That
would
be
an
exact
port.
We
have
some
expertise,
though,
on
to
you:
oh,
we
can
take
our
starting
point:
drupal
7
module
and
get
it
into
stake.
We
think
is
suitable
for
for
backdrop,
so
we
will
be
working
on
that
in
the
next
few
months
to
hopefully
we
can
get
that
in.
If
not,
that
might
be
something
that
gets
pushed
to
a
1.2
release,
depending
on
how
close
we
can
get
with
token.
A
In
top
of
it
and
other
things
that
may
or
may
not
be
on
the
chopping
block
are
getting
a
new
administrative
look.
We've
already
got
a
bunch
of
feedback
that
they
think.
It's
weird
that
backdrop
looks
like
triple
seven.
We
know.
We
also
think
it's
weird
the
backdrop
looks
like
drupal
7.
We
have
a
style
guide,
that's
getting
work
done
as
we
speak.
A
That's
getting
some
new
admin
elements
added
to
make
them
look
more
backdrop,
Ian
Lester
Bowie,
and
then
we
have
someone
on
hand,
who's
ready
to
help
us
figure
out
how
to
get
these
style
guide
changes
into
our
administration
experience
in
backdrop,
and
we've
got
two
current
approaches
on
the
table.
We
could
either
add
a
new
administration
theme
and
set
that
theme
to
be
the
default
administration
theme
for
new
backdrop
installs.
A
Instead
of
one
you
could
just
toggle
it
and
another
option
which
I
think
might
be
a
little
slicker
is
if
we
were
able
to
merge
a
lot
of
these
changes
into
either
the
7
theme
or
into
core
where
they
come
from,
and
some
of
these
things
like
that
that
have
been
bothering
me
for
a
really
long
time
or
like
this
styles
for
tabs,
so
I
on
the
front
end
of
your
site.
There's
this
really
old
style
square
block,
e-tab
thing.
A
Where
do
you
get
redirected
to
stuff
like
that
and
it
doesn't
require
any
API
changes
and
developer
experience?
Changes
are
much
harder
to
get
into
one
point:
oh,
but
this
sometimes
they
involve
refactoring
how
code
is
written
or
how
code
works
and
that
sometimes
will
break
the
api's.
So
if
you're
a
developer
and
you're
working
on
backdrop-
and
you
find
something
confusing
open
an
issue,
we'll
evaluate
it
and
see
if
that's
something
we
can
fix
soon
or
if
that's
something
that
has
to
be
fixed,
a
2
point.
A
0,
but
it
is
something
that
we
are
constantly
thinking
about.
How
do
we
make
this
code
easier
for
people
to
learn
easier
to
work
with
all
of
that
stuff?
So
those
are
two
ongoing
issues
we're
working
on
and
we
have
for
those
two
kinds
of
issues:
we
don't
have
tags
in
our
queue,
but
the
issues
start
with
square
brackets
and
either
you
xor
DX
at
the
top.
A
So,
okay,
that's
what
we're
working
on
in
backdrop
itself.
We
also
have
a
bunch
of
other
stuff
that
we're
working
on
another
backrub
is
out
that
helps
support
our
community.
So,
rather
than
just
being
backdrop,
the
software
we
have
to
think
about
all
of
the
stuff.
The
people
working
on
backed
up
also
need
and
first
on
our
list
and
priorities
of
that
I
think
is
trash
directly,
something
that
I
use
every
day
on
my
Drupal
sites.
A
I
will
really
seriously
be
sad
if
we
can't
get
some
equivalent
thing
for
back
for
backdrop,
as
opposed
to
for
a
Drupal,
and
so
we've
been
making
a
bunch
of
progress
in
the
direction
cutie.
You
guys
were
here
last
week,
Curtis
talk
about
how
we've
gotten
some
feedback
from
greg
greg
anderson,
who
is
one
of
the
josh
containers
about
how
refactoring
josh
to
remove
the
drupal
from
it,
or
at
least
abstract
the
drupal,
in
a
way
that
we
could
swap
it
out
with
something.
That's
not
drupal
like
something
its
backdrop
has
been
on.
A
The
jesh
maintain
errs
to-do
list
for
a
really
long
time.
They
merged
a
patch
I,
think
back
in
June
or
July
that
started
on
that
refactoring,
so
that
Josh
could
support
Drupal,
7
and
Drupal
8,
actually
I
think
it
had
been
supporting
them
both
before
that
anyway.
But
this
is
kind
of
to
ease
that
pain,
but
it
never
got
fully
completed,
and
so
there
were
some
other
people
who
wanted
to
run
Josh
on
some
really
strange
platforms
like
a
symphony
based
Drupal
7,
who
waited
in
the
queue
and
said
you
know.
A
A
Rectory
and
it'll
be
able
to
swap
out
of
the
Drupal
specific
and
behaviors
with
backdrop
specific
behaviors.
So
when
you
do
address
CCL
instead
of
calling
a
Drupal
cache
clear,
it'll
call
a
backdrop
cache
clear
and
there's
just
one
class
that
we
can
swap
out
in
in
Drupal.
It's
a
classic
whole
bunch
triple
functions
and
backup
that
will
be
a
classic
false.
A
bunch
of
a
crop
functions
and
it
should
be
fairly
uncomplicated
in
theory,
in
order
to
just
write
that
class
and
put
it.
In
our
backdrop,
fresh
ink
file
in
core.
A
A
We
can
then
move
that
a
file
into
poor,
so
I
think
we
have
like
a
short
term
kinship
solution,
path
that
we
can
work
on
in
a
longer
term
and
Josh
support
in
court
path
that
we
can
work
on
as
well,
and
so
there's
been
a
bunch
of
progress
on
that
I
think
over
the
weekend
and
that's
running
once
at
any
time
since
Monday
to
work
on
it.
But
there
we
are
solving
the
Josh
problem
for
backdrop,
which
is
super
exciting
in
a
way
that
the
judgment
a
nurse
want
it
solved
anyway.
A
So
we
can
put
the
backdrop
specific
code
and
backdrop
and
just
let
Josh
be
brush
and
I.
Think
that
keeps
everyone
super
happy,
so
I'm
really
excited
about
getting
dressed,
Rebecca.
So
big
update
on
other
stuff
that
we're
working
on.
We
have
an
update
server
for
backdrop
that
currently,
when
your
site
checks
to
see
if
it's
up
to
date,
it
returns
them
message
saying
not
implemented.
A
So
we
need
to
implement
that
it's
on
something
we've
been
working
on
in
the
past
two
weeks,
but
if
we
have
anyone
that
wants
to
help
us
work
on
and
updates
over,
we
could
use
that
we
do
need
to
do
a
little
bit
of
thinking
about
how
that
determines
which
version
is
running
and
how
backdrop
determines
which
versions
of
modules
it's
running
right
now.
All
of
our
modules
are,
in
the
backdrop,
kyndra
were
positive
and
I.
A
Think
none
of
them
contain
a
version
number
and
version
numbers
or
something
that
was
added
on
drupal.org
by
the
packaging
script.
We
obviously
don't
have
a
packaging
script
on
github
the
packages
in
version
numbers,
so
we
could
either
try
and
make
one
which
is
one
option
or
we
could
require
that
people
who
are
releasing
specific
versions
of
modules,
tag
them
as
such
and
we
could
use
the
tag
from
get
or
we
could
require
the
people
who
are
working
in
specific
versions
of
modules.
A
Add
that
version
string
into
their
info
file,
which
I
think
is
the
easiest
thing
for
us
to
do
short
term.
So
we
need
to
figure
out.
You
know
short
term
solution
for
this
and
then
kind
of
the
best
practices,
long-term
solution
and
work
towards
that
as
well.
So
those
things
need
to
be
figured
out
as
well
as
actually
building
the
server
the
checks,
the
updates
that
notifies
your
web.
It's
nice
updates.
A
It
can
just
go
to
get
up
and
say:
hey
get
me
all
the
things
that
exist
for
backdrop
and
anything
that
exists
for
backdrop
would
have
a
return
element
in
our
search.
So
it
would
say
hey
by
the
way
there's
this
thing,
that
someone
has
designated
this
being
a
thing
for
backdrop
and
we
can
put
it
into
the
list
and
that
would
be
equivalent
to
a
sandbox
project,
Ardra
bullet
org.
So
all
I
need
to
use
check
the
box.
A
Then
you
have
a
sandbox
project
and
then
official
projects
again
you'll
be
able
to
create
a
note
for
you
can
define
a
canonical
source
if
it's
not
github.
So
there
are
other
ways
to
list
things
that
aren't
part
of
github
them.
If
you
don't
have
that
box
checked,
but
getting
the
box
I
think
it's
going
to
be
important.
So
if
we
have
someone
and
there's
some
really
good
examples
on
github,
all
you
need
to
do
is
fork
their
project.
Add
your
item
into
a
list
and
then
apply
a
pull
request.
A
I,
don't
know
the
language
it's
written,
none,
but
I
think
that
it
would
be
fairly
easy
to
handle.
Even
if
you
don't
so
could
be
worth
a
shot
from
for
a
Friday
mine
if
you
wanna
get
moving
on
that
other
good
news,
o
our
API
website
has
been
ported
from
Drupal
7
to
back
job
and
need
I,
don't
know
if
you
want
to
talk
more
about
that
since
you're
inland
that
made
it
happen.
Yeah.
B
It's
it's
great
I'm,
also
doing
a
little
bit
of
cross
collaboration
with
the
Drupal
community,
because
I'm
trying
to
figure
out
a
way
to
improve
the
autocomplete
on
the
API
website
and
autocomplete
is
something
that
they're
still
trying
to
improve
in
triple
8
as
well.
So
we're
having
some
low
cross
communication
they're,
trying
to
figure
out
what
the
best
auto-completion
library
is,
or
actually
we've
already
figured
out
what
the
best
auto-completion
library
is.
A
B
Yeah,
the
JavaScript
library,
the
select
to
JavaScript
library
how
it
it
we,
the
Drupal
community,
had
a
solution
that
looked
like
it
was
going
to
work
for
Drupal
8
and
it
was
in
needs
review.
But
then
a
new
version
of
select
two
came
out
and
totally
broke
all
of
the
implementation
that
they
had
written,
and
so
now
it's
like
now.
A
B
But
the
API
website
totally
converted
its
I
mean
it's
it's
it's
nice
documents
also
I've
been
doing
a
huge
amount
of
work
documenting
all
of
our
change
records
and
just
writing
general
documentation
how
to
port
code,
how
to
port
themes
and
all
of
that
information
is
now
being
populated
on
the
API
website.
So
it's
getting
better
by
the
day,
which
is
really
exciting.
B
A
Of
change
records,
there
are
two
issues
on
github
that
have
had
changes
recently.
I
think,
since
one
point,
L
came
out
that
need
change
records
and
there
are
a
ton
of
change
records
on
the
API
site
that
could
use
a
review.
So
if
anyone
is
interested
and
backdrop
wants
to
see
what
our
changes
are
and
is
really
good
at
reviewing
writing
supposed
to
code,
you
could
definitely
use
some
help
reviewing
those
too.
A
So
if
you
want
to
give
those
a
read,
you'll
get
an
idea
of
the
kind
of
changes
that
we're
making
and
make
sure
that
that
they're
all
legible
easy
to
understand
all
that
stuff.
We
could
definitely
use
some
more
feedback
on
that.
I
have
not
given
any
of
those
or
review
since
they've
been
up
I
think
we
haven't,
got
any
complaints,
which
is
good,
but
I
also
think
we
haven't
had
that
many
people
using
them
so
be
good
to
to
get
some
more
eyes
on
them.
A
Also,
all
right
all
right,
flagship
website
vector
up
CMS
to
org.
We
have
been
getting
a
little
flack
about
that,
not
being
ported
to
back
Jeff.
So
that's
the
next
thing
on
our
list.
There's
a
few
more
contribs
like
jeff
website.
Then
there
were
on
the
api
website,
so
those
obviously
need
to
be
ported
first
and
that's
what
we're
working
on
for
that
I
know:
there's
a
bunch
of
them
already
underway,
but
we've
got
a
bunch
more.
A
We've
got
to
think
about
too
and
then,
after
that,
we're
going
to
need
to
worry
about
building
pages
for
modules
and
themes
and
searching
for
modules
and
themes
that
sort
of
thing.
So
we
will
things,
start
thinking
about
again
the
service
for
github,
so
that
we
can
search
github
as
well
as
searching
our
own
nodes
and
getting
that
all
set
up
and
ready
to
go
there
too.
A
So
we've
got
a
handful
work
to
do
there
and
then
other
new
things
that
we've
added
in
the
last
week
we've
had
a
discussion
actually
been
going
on
for
a
couple
of
months
about
what
we
should
do
about
a
discussion
forum,
forums
or
something
that
I
personally
feel
haven't
been
super.
Successful
and
drupal.org
people
seem
to
get
forms
confused
with
issue
queues
and
don't
you
ask
questions
someplace
and
maybe
no
one
will
ever
see
it.
I
move
on.
A
A
So
forums
so
we've
had
this
conversation
for
a
while
about
where
we're
going
to
handle
forums.
We
need
one
into
place
for
people
who
aren't
technical
to
talk
about
backdrop
to
do
things
like
which
theme
are
you
using,
and
what
do
you
like
and
dislike
about
it
things
that
aren't
necessarily
questioning
the
answers
that
are
actually
discussions
and
when
we
first
started
this
were
like.
Oh
all,
discussions
will
happen
on
Stack
Exchange,
and
then
we
realize
that
stack
exchange
actually
discourages
discussions.
It's
for
you
have
a
question.
A
You
got
an
answer,
so
that
will
happen
anyway.
People
are
going
to
be
posting
questions
and
inches
on
Stack
Exchange
over
time,
because
that's
where
people
go
for
that
kind
of
thing,
but
it's
not
quite
the
same
thing
as
a
discussion
forum,
and
so
we
made
this
giant
list
of
pros
and
cons
for
discussion
forums
and
the
one
that
ended
up
being
a
winner
for
some
reason
that
ended
up
being
rabbit.
A
So
we've
created
a
backdrop
subreddit
and
we're
going
to
give
it
a
chat,
we're
going
to
use
it
for
a
couple
weeks
and
see
what
we
think
and
jared
is
very
nicely
set
up.
The
I
don't
know
he's
moderating
it
or
whatever.
That
means
over.
There
he's
got
a
fact
job
branding
on
it.
People
are
using.
It
will
see
what
we
think.
We've
got
a
couple
of
other
options
in
the
list
too,
there
was
no
like
definitive,
clear
leader.
A
Everything
was
all
kind
of
about
the
same
other
suggestions
included
using
a
Facebook
group,
which
is
definitely
friendly
for
non-technical
people,
but
we
might
not
get
any
technical
coordinator,
zoho
forums,
which
is
something
that
I
think
the
jQuery
community
ended
up
adopting
and
google
groups,
which
is
an
email
list
based
system.
So
I
think,
depending
on
what
your
personal
preferences
you
might
end
up,
having
a
favorite
place
to
go
to
do
these
things
anyway.
All
of
these
things
are
immediately
available
and
already
set
up.
A
So
if
you
want
to
try
one-
and
you
know
you
think,
I'll
never
use
reddit,
but
I'll
definitely
use
Facebook
group.
We
have
a
Facebook
group.
You
can
use
it,
you
can
see
if
there's
anyone
on
there,
you
can
ask
questions.
You
can
answer
questions
if
you
want
to
try
and
do
I
think
even
we
have
a
linkedin
group.
If
you
want
to
use
that
because
that's
where
you
spend
your
time,
you
can
use
that
we're
just
going
to
kind
of
say
all
of
these
things
already
exist.
A
Let's
see
what
people
want
to
use
and
I
think
for
right.
Now
most
people
are
using
the
subreddit
because
that's
where
the
majority
of
people
are
so
if
you
have
questions
you
want
to
talk
about
back
Jeff,
you
can
visit
our
subreddit
I
put
a
link
in
the
agenda,
but
it's
also
just
reddit
com,
r
/
backdrop.
So
if
you
want
to
log
in
there
and
see
what
people
are
talking
about,
that's
a
good
place
to
go
to
have
discussions
so
yeah.
There's
also
I
linked
to
the
issue
here.
I
think
too.
A
If
anyone
wants
to
see
the
other
things
that
we
looked
at,
there
were
a
lot
of
recommendations
for
us
to
use
discourse,
which
I
think
is
what
the
bun
to
community
decided
to
use
performs.
But
that
was
not
only
software
that
we
would
have
to
host
build,
maintain
and
support
ourselves,
but
also
in
a
language
that
we
don't
understand
if
we're
going
to
host,
build,
maintain
and
software,
so
that
should
probably
be
back
drop
boom,
which
is
also
on
the
list.
A
But
we've
decided
not
to
invest
in
that
just
yet
we're
going
to
start
trying
one
of
these
previously
existing
form
solutions
and
see
if
we
can
get
that
going
so,
hopefully
that'll
be
a
good
place
for
people
to
talk,
we'll
see
how
much
it
takes
off
and
if
it
was
the
right
choice
and
if
not,
we
can
choose
something
else.
So
yeah,
let's
see
it's
all
we
have
on
performs
every
Thursday.
After
this
meeting
we
usually
have
a
little
backdrop
sprint,
so
you
can
meet
us
in
IRC.
Our
IRC
channel
is
pound
backdrop.
A
You
can
tweet
at
us
we're
at
backdrop
CMS
on
Twitter.
You
can
just
start
working
on
stuff.
You
have
any
questions.
You
know
our
to
find
us
there's
also
now
contact
form
on
our
website
crazy,
but
yeah.
We
all
usually
end
up
working
together
on
backdrop
or
backdrop
related
projects
in
it's
a
good
place
to
get
help
and
feedback.
A
If
you
want
to
on
Thursday
afternoons
other
things
we
have
set
up
some
backdrop:
calendars
in
Google
calendars,
which
I
was
hesitant,
do
because
I
had
to
create
yet
another
google
account
to
do
it,
but
we
do
have
a
calendar
specifically
for
backdrop
friendly
events.
We
don't
have
any
backdrop
official
events
yet
so
there
are
currently
just
events
where
we're
going
to
be
doing
fact
related
things
on
that
calendar
upcoming.
A
We
have
sand
camp,
which
is
the
San
Diego
drupalcamp,
which
will
be
happening
here
at
the
end
of
februari
they're,
going
to
be
doing
a
backdrop
training
the
day
before
the
camp.
We've
got
a
backdrop
supersession
during
the
camp.
I,
don't
think,
there's
going
to
be
any
sprinting,
but
if
there
will
be
in
you
know,
lunch
rooms
or
before
after
whatever
neat
and
I
will
be.
There
will
be
sprinting
alongside
anyone
who
wants
to
work
on
backdrop.
There
another
backdrop
friendly
event
we
have
on
the
calendar
is
mid
camp
in
Chicago.
A
We're
going
to
be
there
anyway
I'm
going
to
be
doing
giving
a
keynote.
That's
unrelated
to
backdrop
just
about
PHP
in
general,
and
we're
going
to
be
able
to
talk
to
it
when
they're
they
do
have
a
sprint.
We're
going
to
try
and
sponsor
this
red
haven't
heard
back
from
them
yet
on
whether
they
actually
need
sponsorship
for
their
sprint
or
not.
But
that's
also
another
place
where
people
will
be
nice
to
us
and
talk
about
that
job,
and
then
we
also
have
our
meeting
schedule.
A
So,
if
you're
interested
in
joining
in
on
this
meeting
or
in
our
design
meeting
which
happens
fortnightly,
those
are
both
on
that
schedule
too,
and
you
can
click,
there's
an
ical
link
for
both
of
those
in
the
agenda.
We're
also
going
to
put
the
icon
links
to
both
of
those
schedules
on
the
forum
in
the
subreddit.
So
if
you
want
to
grab
those
there,
you
can
as
well.
A
So
hopefully,
people
who
want
to
have
more
official
updates
of
things
backdrop
is
doing
will
be
able
to
subscribe
to
this,
and
then
we
also
have
an
article
coming
up
in
the
next
issue
of
drupal
watchdog.
I've
got
to
write
a
draft
of
it,
get
that
ready
for
Monday.
So
guess
what
I'll
be
doing
this
weekend
and
then
that
will
be
out
about
the
same
time.
Mr.
Buchan
dribble
con
los
angeles.
So
we're
hoping
that
by
then
dr.
Bachman
long
enough
that
it'll
be
something
that
we
can
actually
tell
people.
A
It
is
ready
so
by
May,
I'm
hoping
we'll
have
enough
control,
so
people
can
start
building
sites
on
this
and
obviously
we're
building
a
few
sites
on
it
now
but
modules
or
what
makes
triple
what
it
is.
So
modulus
need
to
be
what
makes
backdrop
successful
as
well,
so
hopefully
we'll
get
more
modules
and
more
people
using
it
more
feedback
and
all
that
good
stuff
and
it'll
be
good
to
go
by
Nick.
So,
let's
find
hoping
for,
let's
see,
is
there
anything
else
we
should
talk
about
in
today's
meeting?
B
I,
don't
have
anything
I
would
say
if
you're
looking
to
get
involved
and
in
backdrop,
but
haven't
yet
a
the
easiest
thing
to
do,
and
the
thing
that
we
need
the
most
help
in
right
now
is
porting
modules.
So,
if
you
maintain
any
Drupal,
7
modules
would
be
graded.
You
could
take
a
look
at
porting
room
or,
if
you
are
just
familiar
with
doing
drupal
stuff,
you
can
pour
any
module.
A
All
right,
port
away
and
okay
well,
I
think
that's
all
we
had
for
today's
meeting.
This
one
meeting
ran
longer
than
usual,
for
whatever
reason
I
guess
I
was
at
extra
chatty
but
yeah.
You
know
how
to
reach
us.
Irc,
github,
twitter
contact
form
on
a
website.
Thank
you.
So
much
Reverend
for
your
support.
So
far,
we've
had
a
ton
of
people
using
backdrop
upon
a
time
people
trying
backed
up
town
people
40
modules.
We
really
appreciate
that
and
we're
super
excited
that
you
guys
are
excited
too.