►
From YouTube: Backdrop CMS weekly meeting 1/22
Description
Backdrop 1.0 is here! Let's talk about what comes next. Today’s agenda: http://bit.ly/1zjJCyh
A
Alright,
we
are
on
air,
it
is
thursday
january
twenty.
Second,
every
thursday,
here's
back
to
update,
so
it's
pretty
exciting
today
is
our
first
backdrop
status
meeting
after
the
release
of
backdrop,
one
point:
oh
so
everybody
is
really
excited
about
that.
Nate
is
not
here
today.
Unfortunately,
I
was
hoping
you
would
come
join
us
later,
but
we'll
see,
okay,
give
an
end
the
meeting,
so
we
can
all
celebrate
in
his
absence
and
then
I'll
tell
him
how
much
funny
missed.
A
So
that's
the
plan,
and
so,
let's
see,
obviously
the
big
news
is
at
backdraft
backdrop,
one
point
0
point:
0
was
released
last
thursday
and
if
we
did
it
around
eleven-thirty
after
the
meeting
we
had
to
release
blockers
that
we
were
working
on
that
just
involved
merging
and
all
the
latest
things
from
Drupal
7.
So
any
changes
the
cotton
into
Drupal
7.
Recently
we
wanted
to
make
sure
we're
in
backdrop
one
before
we
released.
We
also
then
decided
to
rearrange
all
of
the
files.
A
What
you
made
today
really
nervous,
but
I
wanted
to
make
sure
that,
like
all
of
the
CSS
files
were
in
CSS
directories,
not
the
JavaScript
files
were
in
JavaScript
directories
he's
like
every
time
you
move
the
JavaScript
something
could
break
and
like
we
don't
have
automated
testing
a
JavaScript
I'm
like
it'll,
be
fine
I'll,
just
test
it.
So
you
said
it
going.
This
is
a
bad
idea
that
it's
a
bad
idea,
but
I
tested
the
snot
out
of
it.
He
pushed
it
in
and
seem
to
be
working
he's
like
okay.
A
He
really
shouldn't
he's
like
I've,
never
letting
you
jump
into
this
again,
but
I
worked
out
fine.
We
did
a
bunch
of
testing
after
the
fact,
and
all
of
the
problems
that
we
had
over
the
weekend
were
not
related
to
moving
files
around.
So
that
idea,
though
it
may
have
been
a
way
somehow
succeeded
so
I'm
so
excited
we
got
it
out.
Files
were
in
a
great
order.
A
We
did,
of
course,
release
and
then
all
weekend
long
everybody
started
using
it
and
we
came
up
with
a
whole
bunch
of
bugs
which
is
kind
of
what
we
were
expecting.
But
the
most
amazing
thing
to
me
was
that
I
was
going
through
doing
stuff
and
I
would
create
an
issue
on
drupal.org
and
say:
oh
I
found
a
problem
and
then
I
would
go
back
to
fix
it
like
an
hour
later
and
it
was
already
fixed
like
this
is
so
amazing
and
it's
like.
Why
are
you
creating
all
these
issues?
A
A
Nobody
ever
goes
to
that
page
on
their
sites.
When
you're
testing
the
product,
it's
one
of
the
top
links,
and
so
it
was
something
that
almost
everyone
landed
on
and
noticed
that
it
was
broken.
So
it
was
like
well,
even
though
it's
not
a
really
big
problem,
it's
a
really
ugly
air.
So
we
should
probably
get
that
fixed
out.
So
as
people
start
testing
it,
that
won't
be
their
first
impression
of
backdrop,
and
so
we
released
one
point
I'll
point
one
and
then
after
we
got
that
first
bug-fix
release.
A
So
we
packed
practice
the
process
of
pushing
the
up
student
release
to
Pantheon
and
making
sure
that
you've
got
a
little
warning
on
your
Pantheon
dashboard
telling
you
there
was
a
new
version
of
backdrop,
and
then
you
run
the
merge
on
Pantheon
and
everything
got
fixed,
which
was
great.
So
we
have
our
process
of
washing
updates
sorted
out.
But
then,
of
course,
after
we
push
the
update,
we
instantly
discovered
two
more
problems
that
are
related
to
pushing
updates.
A
So
we'll
probably
do
another
really
quick
iteration
on
fixing
those
bugs
and
then
trying
to
get
another
book
release
out
pretty
soon
too
again,
not
urgent,
because
the
first
update
did
not
require
database
update.
The
second
update
might
so
I
think.
As
long
as
we
get
this
fixed
in
with
the
next
version,
we
should
be
fine,
so
yay
back
trap
is
out
back
drop.
One
point
01
at
this
point
with
that
a
whole
bunch
of
really
great
feedback
from
people
who've
been
using
it
we've
gotten
a
ton
of
brand-new,
contributed
module,
authors
or
porters.
A
We've
got
a
ton
of
requests
in
the
queue
for
more
people
working
on
it,
there's
a
bunch
of
really
good
buzz
on
Twitter
people
or
any
blog
post,
but
I
think
our
guesses
were
correct.
That
people
wanted
this
thing,
so
I'm
really
excited
that
actually
looks
like
we
were
right.
Oh
those
little,
you
know
it's
always
nerve-racking
there.
So
yay
I
talked
to
Matt.
A
Last
night
he
said:
we've
got
about
125,
sights
on
pantheon,
so
that
includes
you
know,
people
who
just
clicks
the
button
to
try
it
and
see,
but
also
people
are
developing
sites
so
uses
in
various
stages
of
development,
which
is
great,
I.
Think
for
the
first
week
that
is
fabulous.
Who
knows
how
many
other
people
have
been
stalled?
It
locally,
so
I
think
I
think
we're
doing
pretty
well.
A
Release
on
our
wish
list
is
also
to
get
ckeditor
or
a
rich
text
editor
in
court
by
then
too,
and
that's
a
lot
of
work
to
do
in
the
next
four
months,
but
we're
going
to
give
it
a
shot.
We've
already
got
initial
ports
of
token
and
pasado
that
they
both
need
a
bunch
of
work
and
which
I
think
is
a
good.
It's
a
good
point.
I
mean
we
didn't
do
that.
Someone
else
did
if
someone
came
into
the
community
was
like
I
ported
these
modules,
which
is
amazing,
first
start.
A
So
we'll
start
there
ckeditor,
I
think,
is
going
to
be
the
trickiest,
but
we'll
see
how
much
you,
but
we
can
get
in
in
the
first
pass.
They
might
have
to
hold
off
on
stuff,
like
inline
image
handling
until
the
next
minor
release,
but
I
think
getting
something
at
all
in
there.
It's
better
than
that
thing
right
away.
So
that's
our
plan,
there's
some
other
stuff.
That
is
less
urgent,
that
we
want
to
get
in
that
release
to
things
like
a
new
administration
theme
or
maybe
a
new
look
and
feel
for
the
current
one.
A
We
still
have
technically
to
figure
out
which
way
we
want
to
handle
that,
but
go
out
on
our
list.
So
we'll
see
we'll
see
how
far
we
get
I
rearranged
the
agenda
a
little
bit
since
our
last
weekly
meeting,
so
that
we
could
talk
about
things
that
we
needed.
That
are
not
backdrop
because
we've
been
stead
spending
a
ton
of
time
on
all
the
stuff.
We
need
to
do
in
backdrop
and
on
the
backdrops
and
it's
like
okay,
let's
think
about
all
of
the
other
stuff.
A
A
It
really
into
things
for
it's
got
kind
of
a
triple
boot
face
and
it's
got
trying
to
figure
out
where
to
do
things
before
it
does
them.
It's
not
completely
ready,
though,
that
it
still
needs
to
be
refactored
a
little
bit,
so
we
talked
with
Greg
Anderson.
He
gave
us
some
great
suggestions
on
how
the
refactoring
should
be
done,
and
we
also
need
to
add
a
system
for
Josh
to
recognize
what
system
it's
running
on.
A
So,
if
it's
Drupal
it
will
figure
out
whether
it's
Drupal
6,
you
triple
seven
in
triple
eight,
if
its
backdrop
it
well.
No
it's
not
Drupal
and
it'll
robber,
eight
more
like
it
does
for
Drupal
7,
and
so
we
have
kind
of
a
clear
set
of
tasks
designed
now
in
terms
of
getting
a
ton
and
we've
got
someone
who's
volunteered
to
work
on
cleaning
up
Josh
this
weekend.
A
So
I
think
after
this
we
can
all
have
a
much
better
idea
of
how
much
work
is
involved
if
we
can
get
it
close
and
how
you
know
if
we
can
get
a
timeline
for
you
know
when
when
we
think
we
can
have
that
ready,
but
the
good
news
is
that
it's
not
insurmountable,
there
are
changes
we
can
put
into
josh.
The
judge
maintainer
is
like,
which
would
then
allow
us
to
put
changes
into
backdrop.
That
would
make
backdrop
work
with
dress,
so
backup
will
basically
include
a
drink
file.
A
That
will
say:
hey
I'm
backdrop,
and
this
is
where
you
can
find
all
of
my
functions,
and
this
is
what
should
happen
when
you
type
you
know,
josh,
Josh,
clear,
all
and
so
I
think
it's
a
great
path
forward
and
there's
a
lot
of
hope
for
getting
and
backdrop
support
in
josh
without
having
to
fork
Josh
so
and
something
that
Judge
maintain
errs
will
want
to
maintain.
If
we
need
to
get
a
backdrop
person
on
the
team,
we
could
probably
worried
about
that
too.
But
it
looks
right
now
that
that's
not
necessary.
A
So
that's
super
excited
yay.
So
the
next
thing
that
I
think
we
need
to
start
thinking
about
is
getting
update.
Checking
for
backdrops
this
is
update
module.
Its
usual
process
on
a
Drupal
site
would
be
to
check
from
your
Drupal
instance,
with
drupal
org,
to
figure
out,
update
touchable
or
to
figure
out
if
your
course
of
today,
in
a
few
controls
are
up
to
date
and
with
backup
we've
implemented
an
update
server
and
in
backdrop,
the
update
service
checks
with
the
server,
but
the
server
just
says.
A
Actually
the
thing
you're
asking
for
is
not
implemented.
It
returns
a
message,
so
if
you
go
to
your
status
report
on
a
backdrop
site
today,
it'll
say
updates,
not
implemented,
and
so
we
need
to
do
is
implement
that
we
need
to
actually
make
the
update
server
capable
of
checking
your
core
version
of
backdrop
and
saying
you're,
running
back
chapel
in
point
0
or
1
point
0,
point
1
or
whatever
it
is,
and
feed
the
information
back
to
the
user
and
then
notify
them.
A
A
And
that
is
number
one
making
sure
that
our
contributed
modules
have
a
process
of
defining
their
versions,
so
on
triple
dot
org,
the
version
was
automatically
packaged
with
the
tarball
that
you
downloaded.
The
version
string
was
in
there.
It
was
added
by
drupal
and
it
was
based
on
a
tag
on
github.
We
don't
have
that
same
feature
built-in.
It
is
possible
that
we
could
add
that
so
that
when
you
get
those
zip
files
off
with
github,
they
might
already
contain
a
version
string
based
on
a
tag.
A
I
think
that
would
probably
be
the
best
path
forward
for
us,
because
it
works
a
lot
similar
to
the
way
people
did
think
Sun
drupal.org,
but
that's
kind
of
a
you
know.
It
requires
a
lot
of
steps
in
order
for
us
to
get
there.
So
we
ever
thinking
is
that
maybe
short
term,
what
we
should
do
is
have
contributed.
A
Module
offers
actually
hard
code
in
that
version
string
today
their
info
file
and
commit
that
and
it's
a
pain
in
the
butt,
because
when
you
come
out
with
a
new
version,
you've
got
to
remember
it
up
to
info
file
and
nobody's
ever
going
to
do
that.
But
I
think
for
the
first
versions
of
modules
that
might
be
satisfactory
and
it'll
buy
us
enough
time
to
build
the
bundler
tool
that
we
want
on
github
or
at
least
figure
out,
if
that's
possible.
A
So
that's
where
we
are
on
that.
Once
we
have
that
version
string
in
there.
We
also
need
you
get
the
update
service
to
read
the
version
string
from
your
current
Drupal
site,
which
it
can
probably
do
already,
but
then
from
your
about
chance
night.
But
then
it
also
needs
to
check
that
against
the
current
latest
version
of
that
module,
and
that's
also
going
to
be
a
little
bit
harder
because
it's
going
to
need
to
figure
out
the
repository
for
that
module
and
what
the
version
is
such
relate
to
that
repository.
A
So
if
we
are
able
to
do
this
based
on
tags,
I
would
be
ideal
because
we
could
get
that
tag
from
github.
But
if
we
aren't
able
to
do
that
based
on
tags
and
that
has
to
read
it
from
the
info
file,
there's
a
little
bit
more
work
where
it
would
need
to
find
the
repository
look
in
the
source
code,
pull
out
the
immersion
stripping
and
then
check
it.
That
way,
so
there's
a
little
bit
of
magic
involved
in
and
trying
to
get
that
to
work
so
yeah.
We
have
to
get
that
going.
A
Also,
speaking
of
magic
thinks
we
need
to
do
on
github.
We
need
to
figure
out
how
to
register
a
github
service
so
that
someone
can
create
a
contributed
module
or
theme
they
can
edit
the
settings
for
that
project
check
a
box
saying
this
is
a
get.
This
is
a
project
specifically
for
backdrop,
and
then
that
way,
our
update
service
will
be
able
to
check
for
backdrop
projects.
A
Our
primary
API
website
will
be
able
to
pull
in
backdrop,
projects
and
we'll
just
be
able
to
build
listings
like
easier
to
browse
listings
of
modules
for
our
themes
or
layouts
or
anything
on
backdrops
primary
website.
But
right
now
we
have
no
way
of
determining
which
projects
on
github
our
backdrop
projects
other
than
the
ones
that
are,
in
the
backdrop,
can
trip.
So,
even
though
that
is
where
we
want
contributed
projects
to
live,
there
are
going
to
be
plenty
of
people
who
just
create
their
own
things,
and
they
don't
want
to
be
part
of
contribs.
A
They
don't
want
to
maintain
it.
This
is
the
equivalent
of
a
sandbox
project
on
Drupal
today,
and
we
want
to
be
able
to
for
people
to
still
be
able
to
list
those
so
that
they
can
be
found
through
the
backdrop
website,
although
they
would
come
up
as
a
sandbox
project
rather
than
this
an
official
project.
So
we
need
to
get
that
implemented
as
well,
and
that
actually
doesn't
look
like
a
lot
of
work.
There's
some
great
documentation
on
github
that
talks
about
how
to
create
a
github
service,
and
you
basically
just
fork
their
project.
A
Add
your
issue
your
service
and
then
create
a
pull
request,
so
it
is
a
different
language
than
we're
used
to
using,
but
it
is
not
a
terrible
amount
of
work.
Okay,
so
the
next
thing
we
need
to
work
on
is
the
API
reference
website.
I
talked
about
this
a
little
bit
in
our
design
meeting
earlier
today,
too,
we
know
the
design
on
that
website
needs
a
little
bit
of
work.
A
The
sticky
point
there
is
that
we
want
to
port
both
backdrops
primary
website
and
backdrops
API
site
to
backdraft
and
we're
working
on
that
right
now.
That
process
involves
supporting
a
bunch
of
modules.
We've
already
got
code
filter
we've
already
got
the
API
module,
we're
working
through
all
of
the
other
ones
for
using
getting
imported
over
to
backdrop
then
laporte
the
site's
over
to
backdrop
and
then
we'll
build
a
backdrop
version
of
the
primary
websites
theme
and
then
we'll
adapt
that
for
the
API
site.
A
So
for
a
couple
of
steps
away,
we
are
working
on
it.
We
know
the
API
side
is
not
the
most
beautiful
thing
to
look
at,
but
it's
functional
and
we
are
making
improvements
to
content
as
we
go
along
so
yeah.
Well,
we'll
figure
out
how
to
get
get
the
API
side
cleaned
up
your
brazen.
It
currently
contains
a
bunch
of
change
records.
I.
Think
most
of
them
are
pretty
good.
A
We
might
need
a
review
on
some
of
them
and
I
think
we
made
to
Apia
changes
last
Thursday
right
before
we
were
released,
or
we
did
two
things
that
required
and
change
notices
that
probably
haven't
been
created.
So
I
think.
That's
all
we
know
in
terms
of
what's
missing
from
the
API
site.
We've
also
started
moving
off
the
developer,
documentation
off
of
the
primary
website
and
on
to
the
API
site.
A
So
in
a
perfect
world,
the
primary
website
will
contain
a
user
guide,
something
like
oh,
you
have
a
backdrop
website
click
this
button
that
kind
of
instructions,
whereas
the
API
site
will
contain
you
want
to
write
a
module.
You
want
to
write
a
theme.
You
want
to
write
a
layout.
You
want
to
know
our
coding
standards.
You
want
to
know
how
to
create
a
pull
request.
A
All
of
that
condition
is
specifically
for
developers
will
live
on
the
API
site,
and
hopefully
that
will
help
people
know
where
to
find
something
and
figure
out
what
what
belongs
on
which
site.
So
we
are
starting
to
work
on
some
developer
documentation.
There
we've
got
a
couple
of
really
great
starts
on
posts
for
those
three
things:
how
to
create
a
module
theme
and
I
layout,
as
well
as
some
really
great
starts
on
how
to
pour
your
modules
and
themes
from
Drupal.
A
Porting
layouts
was
going
to
be
a
lot
of
their
bag
of
herbs
because
we're
gonna
have
to
have
versions.
For
you
know,
mega
base
layout
sources
panel
is
based
in
yeah,
that's
but
we'll
get
it
figured
out
we'll
get
it
all
documented.
Eventually,
so,
hey
I
web
sites
under
way,
I
think
for
the
most
part,
we're
pretty
happy
with
it
in
terms
of
content,
but
it
is
being
updated
every
day.
Our
primary
website,
for
the
most
part,
is
kind
of
in
a
we're
happy
with
a
holding
pattern.
A
The
documentation
could
use
some
updates
if
anyone
finds
anything.
That's
out
of
date
on
there,
let
us
know
we'll
update
it
pretty
quickly
and
it
needs
some
more
user
guide
pages
like
the
one
thing
that
bothers
me
is
there's
no
concepts
you
need
to
know
in
backdrop,
something
that
is
also
kind
of
missing
in
Drupal
land,
but
like
what
is
a
block
versus
what
is
a
layout
versus?
What
is
the
field
really
basic
things?
A
I
think
it
would
be
great
to
have
a
user
guide
of
that
level
even
more
than
how
to
install
a
module.
I
had
a
song
theme,
so
I'll
tie
together
so
we'll
work
on
that
as
well
and
then
yeah.
The
other
thing
that's
on
our
agenda
in
the
near
future
is
the
how
to
find
a
module
or
how
to
find
a
theme
or
how
to
find
a
layout
pages.
We
have
temporary
holding
pages
for
those
that
say
coming
soon.
A
Alright,
so
that's
where
we
are
on
all
of
the
stuff
that
backdrop
also
needs
I
actually
should
probably
add
something
here
about
forums
too.
There's
been
a
lot
of
noise
in
the
issue:
queue
about
creating
a
place
for
people
to
talk
about
backdrop
and
not
necessarily
issues
right.
We
already
have
a
place
in
issue
queue
where
people
can
ask
questions
about
specific
modules
or
report
problems,
but
this
is
something
that
you
know.
A
We
want
to
avoid
adding
more
stuff
to
backdrops
website,
just
because
we
want
to
avoid
the
additional
development
and
support
and
maintenance
that
comes
along
with
that,
especially
at
scale
like
right.
Now,
it's
not
a
big
deal
to
start
that
many
of
us,
but
two
years
from
now,
we
don't
want
to
be
creating
significant
costs
because
of
eating
our
own
dog
food.
That
said,
we
definitely
do
not
want
to
support,
maintain
or
build
something
that
is
not
made
of
backdrop.
A
So
I
think
anything
like
discourse
that
we
can't
get
hosted
that
we
would
have
to
post
ourselves
is
completely
off
the
table.
So
if
we
are
going
to
develop
and
build
and
maintain
it
ourselves,
a
will
be
backdrop,
but
ideally
that
is
not
what
we
want
either,
so
that
limits
us
to
existing
forum
software
that
we
could
get
for
free,
which
none
of
which
is
super
great.
But
there
are
some
good
examples
out
there
or
maybe
existing
forms
software
that
we
could
qualify
for
some
kind
of
nonprofit
account
with
a
backdrop.
A
We
have
a
backdrop
foundation.
We
are
not
officially
a
non-profit,
yet
we
have
a
application
impending
with
the
free
software
Conservancy,
where
we're
trying
to
get
kind
of
under
their
nonprofit
umbrella,
but
they
have
kind
of
a
back
list
of
projects
that
all
will
be
part
of
them
and
they
only
review
them
once
a
month.
So
it's
kind
of
a
long
process.
So
right
now
we
don't
actually
have
any
legal
ground
to
stand
on
as
a
non-profit.
So
we
need
to
find
a
company.
A
That
would
say:
oh
you
know,
free
for
open
source
rather
than
free
for
nonprofit.
That's
something
we
could
leverage
there,
and
so
we
will.
We
will
see-
and
we
have
talked
about
stack
overflow,
I-
think,
that's
something
that's
going
to
happen
anyway.
People
are
going
to
ask
questions
on
stack.
Overflow
people
are
getting
answers.
One
of
the
things
we
wanted
to
do
was
create
a
backdrop,
specific
Stack,
Overflow
kind
of
like
drupal
answers,
and
that
is
something
that
is
really
hard
trying
to
get
your
own
version
of
that
and
Kevin
I.
A
Think
you
mentioned
that
too,
that
there's
a
ridiculous
process
and
trying
to
get
your
own
web
those.
So
we
will
let
everyone
ask
and
answer
questions
on
stack
overflow.
We
had
originally
decided
to
send
one
there
and
like
tag
issues
with
it,
but
there's
also
some
usability
issues
with
you
need
to
have
a
certain
amount
of
credit
before
you
can
ask
a
question:
you
need
to
have
more
credit
for
you
answer
a
question.
Maybe
you
can
answer
right
away,
but
you
need
to
have
more
credit
to
like
add
a
comment.
A
It's
kind
of
a
weird
experience
for
someone
who's,
not
already
an
expert
in
Stack
Overflow.
So
if
you're,
you
know
a
client
that
has
a
website,
you
have
a
question,
it's
a
great
place
to
go
and
read
answer.
So
it's
a
really
hard
place
to
get
your
own
questions
answered
so
it'll
happen.
Naturally,
anyway,
we'll
let
it
happen
naturally,
but
it
might
be
good
to
consider
another
tool
that
is
easier
for
people
to
get
to
what
that
actually
means.
Who
knows
so?
A
We
have
a
couple
of
options.
We
could
I
sign
up
for
some
random
piece
of
forum
software.
We
could
just
tell
people
to
use
stack
overflow
and
get
over
it.
We
could
use
a
Google
Group
Luke
set
up
a
mailing
list
already
through
good
works,
which
works.
I
think
for
great
for
people
who
understand
mailing
lists.
I
think
people
who
are
new
to
technology
these
days
do
not
think
mailing.
This
people
who
have
history
and
technology,
do
and
so
there's
kind
of
a
philosophical
divide
there
on
that.
A
I
think
today
everybody
just
googles
for
everything
so
having
something
I
know
trying
to
get
access
to
a
Google,
Group
mailing
list,
that's
posted
on
the
Internet
can
be
really
difficult
because
the
way
people's
emails
add
you
know
ugly
markers
to
try
and
determine
whose
email
is
who's
and
how
long
thread
is
and
what
have
a
little
messy.
But
we
need
something.
So,
let's
see
I,
don't
remember
the
issue.
Does
anyone
happen
to
know
what
github?
A
Don't
have
it
handy
anyway,
I'll
find
it
and
I'll
post
a
link
in
the
agenda
after
the
meeting.
If
no
one
else
gets
to
it
before
then
so
yeah.
We
need
to
figure
out
some
easy
way
for
people
to
ask
and
answer
questions
right
now.
Our
only
tool
for
that
is
the
question
tag
in
the
github
cube.
So
if
you
have
a
that's,
where
you
go
to
ask
it,
we
also
have
I
your
seat.
A
If
you
are
super
nerdy
and
know
how
to
get
on
IRC,
we
have
twitter
people,
ask
questions,
don't
go
or
sometimes,
but
none
of
these
are
really
great
solutions
for
for
for
this
problem.
So
thanks
Kevin
for
that
link
to
it,
icity
sure
and
we'll
take
a
look
at
that
too.
They
apparently
just
got
there
seventy-five
percent
on
a
stock
exchange,
so
it's
great
read
it
yeah,
we'll
try
and
figure
out
some
looted.
I.
Think
at
this
point.
If
we
just
choose
one,
it
doesn't
matter.
If
it's
not
perfect,
we
can
choose
one.
A
We
can
try
it
for
a
couple
of
months.
We
can
see
what
people
like
and
don't
like
about
it,
and
we
have
the
opportunity
to
change.
It
is
sometimes
hard
to
change
later,
depending
on
how
much
activity
happens
there.
But
I
think
if
we
find
serious
shortcomings
with
whichever
decision
we
make,
it
would
be
wise
to
change.
So
we
can
figure
that
out
all
right,
nice
teeny
agenda.
What
else
here.
A
Let's
talk
about
backdrop,
the
software
okay.
So
let's
see
we
have
one
point
Oh
point
one
out:
we
have
a
milestone
for
one
point,
0
point
to
which
is
what
we're
working
on
next.
Those
are
bugs.
We
also
have
a
milestone
for
one
point,
one
point:
oh
so
as
we're
finding
issues
that
we
think
definitely
need
to
be
in
the
next
bug-fix
release
will
tag
it
with
a
milestone.
As
we
come
across
issues
we
think
need
to
be
in
the
next
major
minor
release
will
tag
it
with
that
issue.
A
If
you
have
something
and
I
think
that
in
theory,
anyone
who
creates
a
pull
request
should
have
access
to
fiddle
with
labels
and
milestones
and
stuff
on
the
issue,
queue
and
github
repository,
but
I'm
not
entirely
sure,
that's
working.
So
if
you
are
someone
who
spends
a
lot
of
time,
the
issue
queue
and
you
want
access
to
these
things.
A
Just
let
us
know,
and
if
you
haven't
been
granted
access
already,
we
can
give
it
to
you
if
you
haven't
created
a
pull
request,
but
you
are
really
super
active
in
the
issue
queue
and
want
to
have
access
anyway.
That's
fine!
Well
or
open
up
to
anyone,
we're
going
to
try
in
at
some
point
build
a
tool
that
just
gives
you
a
button
that
says.
Let
me
edit
these
things
and
anyone
it'll
grant
themselves
access.
We
don't
need
the
restrictions
that
github
on
replies
or
applies
for
this
particular
repository.
A
That's
why
we
have
a
separate
repository
for
issues
it's
because
we
want
to
let
everyone
have
access
to
edit
them.
So
if
you
have
any
problems
trying
to
edit
milestones
or
labels
or
anything,
let
us
know
and
then
we're
pretty
good
about
actively
checking
the
milestone
lists
of
issues
to
make
sure
that
all
of
the
bugs
have
four
requests.
Those
pull
request
get
reviewed
quickly.
That
sort
of
thing
we're
not
so
good
at
looking
at
the
meta
list
of
issues.
A
So
if
you
find
a
way
to
slice
and
dice
that
list
of
issues
to
find
exactly
what
you
want
to
work
on,
that's
definitely
good.
We
do
keep
an
eye
on
things
that
are
posted
recently.
If
you
want
someone
to
look
specifically
at
an
issue,
put
their
name
in
it,
because
at
least
nate-
and
I
have
it
set
up
to
email
us
if
someone's
name
is
mentioned-
I
think
most
people
do
so
it's
a
good
way
to
get
attention
on
your
issue
if
you
need
feedback
from
a
particular
person,
okay,
so
young.
A
For
one
point,
one
point:
oh,
we
have
built
in
rich
text,
editor
token
module,
pasado
module
I
want
to
get
the
theme.
Admin
theme
changes
in
weather,
it's
seven
or
new
admin
theme
just
so
that
it
starts
to
feel
like
a
different
product
and
Drupal
and
then
with
the
other
stuff,
going
on,
like
a
bunch
of
user
experience,
issues
a
bunch
of
developers,
efficient
experience
issues
and,
of
course,
bugs
as
they
need
to
get
fixed.
A
So
today,
after
this
meeting
we're
going
to
have
a
little
sprint
in
IRC,
as
with
every
Thursday,
we
will
be
able
to
kind
of
crank
through
a
couple
of
these
new
issues.
Maybe
we'll
get
a
resolution
for
the
forum
option
Luke
found
the
issue
is
in
the
factor
of
CMS
org
q
issue
number
18.
If
you
want
to
look
there
for
that,
and
then
upcoming
things,
we
have
a
sand
camp
which
is
here
in
the
end
of
februari,
we're
going
to
have
a
super
session
like
a
two-hour
session.
A
A
I
think
that
camp
is
just
friday
saturday
and
adds,
but
that's
are
playing
for
that
and
then
we'll
also
be
at
mid
camp
in
march
in
chicago
chicago,
in
March,
Jason,
cold,
nice
change
from
San
Diego
for
sure,
and
it's
mostly
I
think
going
to
be
a
drupal
focus
conference.
So
we're
probably
not
going
to
have
a
sprint.
A
We
have
offered
to
sponsor
this
friend
if
they're
going
to
have
one
we
haven't
heard
back
from
them
on
whether
they're
interested
in
doing
that
or
not
if
they
are,
will
be
sprinting,
I'm,
not
sure
what
their
plans
are,
but
we'll
see
how
we
can
try
and
make
that
work.
So
lots
of
stuff
coming
up
on
the
schedule.
We
also
have
a
post
release
backdrop
CMS
article
coming
out
a
drupal
watchdog,
which
I
think
will
be
out
later
this
spring,
so
I
really
found
that
something
I'm
working
on
and
just
in
general.
A
If
anyone
wants
to
make
any
noise
about
backdrop-
and
now
is
a
great
time
to
do
it,
everybody
seems
to
be
super
excited
trying
it
out
for
the
first
time,
I've
defend
any
problems.
Obviously
let
us
know
we're
still
working
on
some
of
the
kinks,
particularly
around
cmi
stuff.
We
need
more
testing
on
that.
So
that's
the
most
fun
I
think
try
a
new
toys
but
yeah.
So
that's
all
I
have
for
the
agenda
today.
Thank
you
all
for
joining.
Did
you
have
any
comments
or
questions
or
anything
you
guys
want
to
add
today.
A
Nice
and
quiet
alright.
Well,
thank
you
for
joining.
If
there's
anything
we
talked
about
today,
you
guys
really
want
to
work
on.
You
can
let
us
know
and
I
see
or
the
Sheikh
you
or
what
have
you
and
we'll
try
and
help
as
much
as
possible.
I'll
try
to
find
Nate
and
see
if
these
in
our
student
working
on
backed
up
today
and
our
sprint
as
well,
but
alright
thanks
everybody
for
coming
and
we'll
see
you
next
week.