►
From YouTube: Backdrop weekly 2/5
Description
Weekly development check-in call for Backdrop CMS.
A
All
right,
it
is
Thursday
februari.
Fifth,
we
are
here
to
talk
about
development
tasks
for
backdrop
CMS.
If
you
join
this
call
later
and
they're
two
ends
up
being
a
whole
bunch
of
people
on
here,
you're
outside
or
some
more
annoyed.
Please
mute
yourself
when
you
come
in.
Otherwise
you
know
speak
freely
when
you
would
like
to
meet
yourself,
etc.
Okay,
so
we
have
a
couple
of
updates
from
the
PMC
this
week,
the
first
and
most
exciting
Nate.
Do
you
want
to
dance.
B
B
Well
I'll
talk
about
growth
and
then
I'll
actually
go
into
the
exciting
thing,
because
I
think
I
think
they're
all
exciting.
So
we've
had
a
huge
number
of
applicants
to
join
the
contributed
group.
I
think
we've
got.
Let's
see,
we
have
21
total
people
that
have
applied
and
been
accepted
into
the
control
group
in
just
a
few
short
weeks,
which
has
been
fantastic.
They
ported
a
total
of
thirty-five
or
started
porting
or
have
completely
porting
35
total
contributed
projects,
including
three
or
four
themes,
and
the
rest
of
them
are
modules
which
is
really
really
exciting.
B
We've
also
got
another
dozen
or
so
modules
that
are
currently
going
through.
Actually
I
guess
not.
Modules
of
themselves
aren't
really
going
through
review,
but
the
authors
are
going
through
the
application
process,
which
basically
is
just
making
sure
that
you
include
read
me:
you
include
a
license
file
and
that
you
maintain
the
history
if
you're
doing
the
port
of
of
a
triple
seven
module.
B
So
now
it's
great
to
kind
of
distribute
that
responsibility
a
little
bit
and
help
Shepherd
more
contributors
into
the
project
with
with
the
lower
bottleneck.
If
there
are
more
people
out
there
that
are
interested
in
taking
on
responsibility
of
helping
review,
contributed
module
applications.
That
would
be
great.
Our
process
is
really
simple:
it's
not
really
a
code
review
process
so
much
as
it
is
just
making
sure
that
that
certain
requirements
are
met.
That's
those
three
that
I
just
mentioned
some
nice
didn't
happen.
That
I'ma
great
is.
A
B
A
A
The
other
thing
that
is
actually
pnc
update
and
is
that
last
week
we
talked
about
needing
to
establish
a
code
of
conduct
for
backdrop.
We
had
one
contributed
author
application,
that
we
had
to
reject
/
postponed
for
a
month,
and
so
we
realize
we
better
come
up
with
some
terms
around
when
that
kind
of
thing
becomes
appropriate.
So
we
set
up
a
pretty
good
set
of
standards
for
contributed
author
applications,
which
I
think
is
good,
but
I
think
backdrop
needs
a
bigger
and
code
of
conduct
itself
around
just
telling
people.
A
You
know
I
respect
each
other,
all
that
good
stuff
and
so
I
found
this
good
one.
Last
week,
I
didn't
have
a
link
to
it,
but
it
is
a
conf
code
of
conduct,
calm,
which
is
what
we
used
as
a
starting
point
for
a
bad
camps
code
of
conduct
last
year,
and
it
is
specifically
intended
for
conferences,
but
I
think
that
it
applies
to
communities
as
a
whole.
So
I
went
ahead
and
forked
that
on
github
they
have
one
on
github.
I
posted
a
link
to
our
fork
of
it
and
I
can
use
some
help.
A
Reviewing
that
and
help
figuring
out
like
should
we
take
out
the
stuff
specifically
applies
to
conferences,
or
should
we
add
a
section
that
says
you
know
this
goes
beyond
conferences
is
a
place
for
a
whole
community,
just
some
kind
of
thought
on
how
we
should
manipulate
this
code
of
conduct
that
wasn't
it
for
conferences
and
make
it
work
for
a
community
as
a
whole.
We're
obviously
at
some
point
going
to
need
a
code
of
conduct
for
conferences
as
well,
so
keeping
them
together.
A
What
I
think
would
be
ideal,
but
finding
some
way
to
rework
them
I
think
would
be
great
too.
So
that
was
the
only
update
there
is
that
we
have
a
forked
version
of
this
thing
and
we
need
to
make
some
changes
specifically
for
vector
alright.
So
in
terms
of
timeline,
what
we're
working
on
right
now
is
we're
going
to
do
another
bug-fix
release
for
backdrop.
A
Next
week
we've
got
a
couple
of
changes
that
aren't
necessarily
critical
bugs
that
need
to
get
fixed
soon,
but
there
are
bugs
that
we
want
to
fix
sooner
rather
than
later
so
we're
just
gonna
do
a
release.
We've
got
enough
fixes
I.
Think
in
the
queue
to
do
that
it
looks
like
Nate's
estimating
on
deal.
It
says
911
early.
A
The
backdrop
needs
in
particular:
we
are
working
on
trash
and
I,
know
personally,
I
really
love
Josh
I
use
it
on
every
triple
society's
every
day.
I
really
want
it
for
backdrop.
There
are
a
couple
of
things
that
are
preventing
Josh
from
working
with
back
job.
The
first
is
the
biggest
is
that
Josh
doesn't
know
that
backdrop.
A
It
is
a
working
Drupal
site,
so
we
need
a
way
to
convince
josh
that
it
is
Drupal,
and
then
we
need
to
tell
it
how
to
do
all
the
things
that
it
likes
to
do
like
clear,
caches
and
all
that
good
stuff.
So
in
Josh
that
in
the
josh
q,
the
maintainer
star
have
been
working
on
trying
to
abstract
the
Drupal
out
of
trash
a
little
bit,
because
Drupal
itself
needs
to
be
able
to
know
whether
it's
triple
six
you're,
both
seven
interpolate
and
all
three
of
those
things
might
do
a
cash
clears
differently.
A
So,
even
though
we
are
not
Drupal,
Drupal
itself
requires
this
kind
of
changed
too,
and
so
we
thought
and
sign
off
from
the
dress
containers
that
they
are
interested
in
supporting
this
kind
of
abstraction
just
because
they
want
it
anyway,
and
we
haven't
have
people
who
are
motivated
to
help
get
it
going.
So
we've
got
someone
who's
working
on
helping
refactored
rush
to
have
this
abstraction
and
the
way
that
we
were
planning
on
dealing
with
it
and
the
backdrop
side
of
it
is.
We
want
to
include
a
file
that
will
just
contain
all
the
information.
A
The
josh
needs
to
know
about
how
to
do
things
for
backdrop,
so
we
would
have
some
kind
of
a
backdrop
josh
inc
file.
We
can
even
put
that
in
core
long
term
or
short
term.
We
could
have
a
control
that
says:
hey
put
this
in
the
site
group,
because
josh
by
default
will
look
in
the
root
of
your
site
for
that
file
and
that
should
be
able
to
get
us
going.
So
we've
gotten
some
great
feedback
from
judgment,
a
nurse
on
how
to
do
it.
A
A
Just
because
there's
a
lot
we
have
to
do
in
terms
of
refactoring
and
making
dressed
be
able
to
find
the
ink
file,
but
I
do
think
that
I
getting
a
version
of
Josh
working
with
backdrop
is
going
to
happen
in
the
near
future,
although
it
might
be
a
diversion
for
a
little
while
so
I
think
that's
exciting
news.
We
definitely
could
use
some
help,
testing
it
as
soon
as
we
can
get
ready
if
anyone's
super
motivated
and
working
on
it.
You
can
join
that
the
issue
in
the
truck
you
and
see
how
that's
going.
A
Let's
see
how
puts
that
in
the
Hangout
to
for
anyone
who's
interested
okay-
oh
that's
just
coming
soon
other
things
that
we
need
for
backdrop
is
an
update
server.
So
this
is
when
your
backdrop
site,
tells
you
that
it's
modules
or
themes
are
out
of
date.
It
determines
that
by
comparing
the
modules
and
themes
on
your
site
to
some
master
list
somewhere
and
then
saying,
okay
master
list
says
that's
update.
We
don't
have
that
service
working
right
now.
A
We've
got
a
our
servers
up
and
it
right
now
returns
a
header
that
says
it
is
not
yet
implemented
and
we
have
a
couple
of
things
that
are
preventing
that
process
from
being
completed,
and
then
I
talked
about
this,
I
think
pretty
extensively.
Over
the
last
week
we
have
some
pretty
good
ideas
about
how
to
solve
the
contributed
version,
control
or
version
contributed
version
string
problem,
and
so
with
that
job
corps.
A
It's
pretty
easy
because
we
have
our
own
repository
and
they
can
check
what
version
it
is,
and
it's
not
going
to
be
that
big
of
an
issue
but
with
any
contributed
project,
and
they
don't
necessarily
have
to
live
in
the
same
place.
Right
like
I
could
be
hosting
my
own
module
on
I,
don't
know
fit
bucket
or
something,
and
that
could
be
the
defective
source
for
my
module.
A
But
the
backdrop
update
server
needs
to
be
able
to
find
that
source
for
the
module
and
then
tell
me
or
tell
anyone
who's
running
my
module,
whether
that
module
is
out
of
date
or
not.
So
we
have
kind
of
this
distributed
information
problem
that
we're
looking
at
solving
and
Nate.
You
came
up
with
a
pretty
good
solution
on
how
to
solve
that.
You
want
to
share
that
here
with
people
who
might
be
interested
in
it.
Yeah.
B
Sure
so
sure,
so
what
we're
going
to
do
and
I
think
we've
talked
about
this
in
the
past
a
couple
of
times,
but
now
it's
become
clear
that
it's
actually
ssible,
which
is
great
for
contributed
modules.
What
we're
planning
on
doing
is
using
the
backdrop,
contribute
that
people
are
currently
actively
joining
and
putting
code
in
which
is
fantastic.
What
we're
going
to
do
is
we're
going
to
set
up
a
set
of
web
hooks
on
that
particular
organization.
B
So,
on
that
github
account
all
projects
that
are
within
that
group
will
automatically
all
have
certain
web
hooks
fire
that
say
when
they
create
new
releases
or
when
they
tag
certain
versions.
All
that
information
will
be
passed
back
to
kind
of
the
mothership
backdrop,
CMS
org
website
and
so
backdrop,
CMS
org
will
then
use
those
web
hooks
to
create
project
notes
on
the
main
website
and
also
to
do
things
like
when
a
new
release
is
created,
update
its
information
within
that
note.
B
We
have
the
ability
to
say
that
an
external
website
like
backdrop
CMS
org,
has
the
ability
not
only
to
respond
to
a
web
hook,
but
actually
to
do
things
like
modify
the
art
I
date
pub.
It
observes.
So
you
can
get
notified
of
a
new
release
being
created,
download
that
zip
file
or
that
gzip
file
onto
your
server,
which
will
be
the
main
factor
of
CMS
torg
server,
expand.
B
It
modify
the
contents
of
the
archive
to
include
the
project's
version,
information,
re
archive
it
and
then
push
that
back
to
github
and
then
github
will
effectively
serve
our
modified
versions
of
the
archives
that
include
the
tagged
version
information.
So
that
way,
we'll
get
the
same.
It'll
be
really
similar
to
the
functionality
that
we
have
on
on
drupal.org,
where
you
won't
need
to
update
your
info
file
every
single
time.
B
Every
time
you
make
a
new
release,
and
so
you
just
cut
a
tag
and
then,
when
you
create
their
release
on
github,
that
information
will
automatically
be
appended
into
your
info
files.
So
that
way,
Drupal
itself
sorry
backdrop
itself
will
be
able
to
tell
which
version
of
a
project
you're
actually
running,
and
then
that
in
turn
will
that
information
will
be
sent
to
the
update
server
which
will
live.
It
backdrop
CMS
org.
B
To
let
backdrop
CMS
org
actually
modify
the
archives
of
their
releases,
but
we'll
see
we'll
see
how
this
works
if
they
can
dribble
first
and
then,
if
it's
possible
for
us
to
expand
that
out
to
other
organizations
or
groups
on
github
or
perhaps
even
things
that
aren't
github,
then
you
know
we'll
look
into
that
in
the
future.
But
for
the
time
being,
I
think
it's
important
that
we
get
a
directory
listing
of
modules
that
are
that's
a
little
easier
to
browse.
B
Then
then
the
backdrop
can
drip
drip
on
github
and
also
cater
towards
towards
people
in
that
group,
because
that's
really
the
group
already
is
helping
reduce
a
lot
of
redundant
efforts
of
around
porting
a
lot
of
the
modules
that
that
are
out
there.
Well,
we've
accidentally
ported
a
couple
modules
like
twice
already,
which
we're
trying
really
hard
to
avoid,
but
with
so
many
modules
out
there
to
port
and
everybody
going
after
the
most
popular
ones,
we're
getting
a
little
bit
of
redundancy.
B
A
So
for
the
update
server
problem
and
we're
going
to
have
the
update
server
check
the
canonical
source
of
any
module
regards
of
whether
it's
on
github
or
not
and
read
it
info
file.
So
that
means
that
if
you're
not
in
the
contribute
and
the
version,
information
does
not
get
package
to
automatically
you'll
have
to
add
the
version
string
to
your
info
file.
Manually
yep.
A
B
Yeah,
basically,
for
now
yeah
there's
additional
incentive
to
use
the
contribute,
because
it
will,
it
will
do
the
packaging
and
the
versioning
automatically
for
you
and-
and
that's
only
in
the
first
pass
like
we'll
see
if
we
can
make
that
possible
for
for
projects
that
are
hosted
outside
of
the
contribute
and
potentially
outside
of
github.
But
those
will
all
be
kind
of
like
later
implementations.
Okay,.
A
And
there
are
other
benefits
to
being
in
the
control
group.
Two
of
the
kinship
group
is
where
the
doctor
of
security
team
will
be
working.
So
if
you
want
security,
reviews
of
your
stuff
it'll
need
to
be
in
there
and
yeah.
Just
generally,
we
are
going
to
encourage
most
people
to
do
their
work
there,
but
there
are
sometimes
business
requirements.
A
So
we
have
a
plan
other
things
that
we're
working
on
gonna
buy
my
agenda.
Here
we
go
so
we
did
originally
talked
about
needing
to
create
a
fish
yet
hub
service
on
github.
So
anyone
who
has
a
project-
that's
not
on
the
control
group-
can
register
as
being
a
backdrop,
project
I
think
that's
still
important
for
the
it
would
be
the
equivalent
of
creating
a
sandbox
project,
but
it
is
not
as
important
as
we
thought,
because
it's
not
that
service.
A
That's
going
to
allow
us
to
provide
the
ability
to
package
the
version
information
on
it.
Is
the
group
that
you
post
your
stuff
in
so
it's
a
nice
to
have
but
I,
don't
think
it's
a
requirement
and
I
think
we
also
made
some
progress
on
that
front
where
it
turns
out.
We
don't
those
are
something
neat
about
not
needing
to
use
their
API
or
something
we
can
do
it
a
different
way.
Yeah.
B
Yeah,
so
officially
that
this
conflicting
documentation
on
github
about
whether
or
not
services
are
even
still
being
supported
or
not,
basically,
there's
documentation
saying
that
they're
no
longer
accepting
any
new
services
into
into
the
the
master
list
of
supported
services.
A
service
basically
is
nothing
but
a
predefined
web
hook
that
it
it
configures
the
web
hook
for
you
essentially,
but
it
the
appealing
thing
about
it
is
that
people
just
select
it
from
a
drop-down
or
from
an
autocomplete
on
their
github
project,
and
then
it's
set
up.
B
So
it
requires
a
lot
less
effort,
but
officially
github
is
said
that
they're
no
longer
adding
new
services
of
any
kind
to
that
list,
so
they're
trying
to
deprecate.
But
unofficially,
if
you
go
and
look
at
the
repository
that
includes
all
of
the
list
of
services,
they're
still
actively
adding
new
services
almost
on
like
a
daily
basis,
so
so
I
can
see
kind
of
why
they
want
to
get
out
of.
B
So
we'll
see
by
the
time
that
we
actually
get
this
up
and
running
I
mean
we're
going
to
do
this
on
the
contributory
first
and
we're
going
to
use
it
as
a
web
hook
initially.
But
then,
once
that's
all
set
up,
we
could
potentially
expand
that
out
to
be
a
github
service,
but
only
if
github
will
actually
accept
our
service
in
the
first
place.
So
it's
a
little
bit
unknown.
B
A
A
All
right
so
other
things
we're
working
on
our
API
website,
friends
knew
who
weren't
here
last
week.
We
recently
got
that
ported
to
backdrop.
It's
just
great
for
dolls
modules.
I
was
running
on
and
moved
it
over.
We
swapped
out
its
theme
with
a
version
of
Bartok.
That's
just
got
a
black
header
apparently
looks
fabulous,
so
go
back
drop
cloths,
Part
A.
We
are
gonna,
try
and
work
on
porting
our
front
end
theme
from
our
AP.
A
From
our
backdrop,
CMS
George
site,
we're
going
to
port
that
to
backdrop
and
we're
gonna,
try
and
put
that
on
the
API
site,
but
we
want
to
make
sure
the
API
say
it
still
looks
good,
even
with
that
theme
on
it.
So
we're
going
to
do
some
design
review
of
that
before
we
get
it
done,
but
other
things
that
are
going
on
on
the
API
site,
the
change
records
we
thought
I
think
to
change
records
left
new
ones
that
need
to
be
created
that
weren't.
A
That
have
happened
since
the
one
point,
0
point
0
release
and
we
have
a
bunch
of
chain
or
critical,
probably
use
another
set
of
eyes,
just
to
review
them
and,
speaking
of
other
sets
of
eyes,
we
have
a
whole
bunch
of
really
great
developer,
documentation
being
posted
on
the
API
site,
and
it
would
also
be
really
good
if
other
people
could
read
and
review
that
as
well.
I
went
through
yesterday
and
made
a
couple
of
changes
to
some
of
the
developer
documentation.
A
Zit
was
mostly
stuff
like
putting
PHP
tags
around
PHP
code
and
formatting
and
cleaning
a
language
more
than
anything
else.
The
content
was
fabulous,
but
if
anyone
else
wants
to
do
that
kind
of
thing
do
a
little
review
of
the
stuff
on
there
I.
You
know.
Let
us
know
we
can
probably
give
you
access
to
edit
the
content
there
and
then
help
us
clean
nada.
I
have
a
feeling.
A
A
lot
of
people
are
using
particular
the
upgrading,
your
modules
from
Drupal
7
to
backdrop
pages
or
upgrading
your
themes,
and
so
we
can
do
some
more
eyes
on
those
to
make
sure
that
we
haven't
missed
anything.
I
found
a
couple
of
things
that
we're
missing
from
the
port
of
your
modules
page
just
because
they
don't
apply
to
all
module
so
getting
those
at
it.
In
there
good,
also
cross-linking
to
change
records,
I
added
a
couple
of
those
into
then
we
don't
have
to
put
all
the
documentation
in
the
porting
page.
A
We
can
say
you
know,
check
out
the
new
book
registry
info
or
whatever
it
is
a
link
to
it,
and
then
we
don't
have
to
have
all
the
details
in
that
one
page
makes
a
little
easier
to
read
so
other
stuff,
we're
working
on
our
backdrop,
CMS
website
and
mention
we're
going
to
be
porting
it
to
backdrop.
I've
got
a
couple
of
modules
that
I'm
working
on
porting
right
now
for
that
project.
A
Animate
really
wants
to
get
that
primary
website
moved
over
to
there's
a
couple:
more
modules
there
that
need
ports
to
so
we'll
try
and
get
that
done
here
in
the
next
week
or
so,
and
then
I
think
I'll
make
us
look
a
little
bit
better
if
backdrops
website
back
Joe.
So
that's
high
on
our
priority
list.
Yeah.
B
A
You
very
much
and
then,
as
soon
as
we
get
that
ported,
our
next
task
will
be
setting
up
the
process
of
adding
nodes
on
the
site
for
much
of
things
and
layouts,
and
so
as
soon
as
we
can
have
modules
names
and
layouts
on
there,
we
could
start
to
build
a
fine.
Your
module
seems
in
the
land.
It's
tools,
which
I
think
is
something
that
people
are
going
to
start
needing
here
really
soon.
A
Now
that
we
have
listings
and
layouts
for
people
to
find
I
think
getting
getting
a
easy
way
for
them
to
find
them
that
doesn't
involve
searching
the
backdrop.
Contribute
is
going
to
be
of
high
importance.
Last
week,
I
mentioned
that
we
started
a
subreddit
for
our
forums.
I
think
it's
been
going
pretty
well,
there's
been
a
whole
bunch
of
activity
over
there
least
for
a
handful
of
people
every
time,
I
look
at
it.
A
I'm,
like
wow,
there's
all
went
to
new
forms
and
then
I
spend
way
too
much
time
like
poking
around
not
answering
questions
and
doing
stuff,
which
is
good.
So
only
why?
But
I
would
love
to
get
some
feedback
to
on
whether
there's
anything
we
can't
do
there.
One
thing
I
had
trouble
doing
yesterday
was
posting
an
image
and
I.
Think
that's
going
to
be
something
that's
going
to
be
a
requirement
long
term.
If
you
have
a
problem,
you
want
to
post
a
screenshot,
or
you
want
to
show
someone
how
to
do
something.
Getting
images
on.
A
There
would
be
good,
so
I
don't
know
if
I
just
couldn't
figure
it
out
and
you
can
post
images
or
if
it's
a
setting
with
it
it
just
to
allow
people
the
post
images,
but
other
feedback
like
that.
I
think
on
limitations
of
that
system
would
be
good
to
know
about,
because,
if
we're
going
to
change
it
in
the
future,
we
need
to
find
something
that
can
solve
all
those
problems.
A
So
far,
though
I
think
it's
been
really
great
other
than
that
it
seems
to
be
doing
its
job
of
providing
place
for
people
to
chat
about
stuff,
just
really
good,
okay,
so
backed
up
itself.
We
have
a
couple
of
things
that
we're
working
on
for
the
next
bug-fix
release.
There's
the
milestone
for
one
point
no
point
to
if
anyone
wants
to
help
us
crank
out
any
more
bugs
before
that
release
comes
out
any
bugs
that
don't
get
fixed
before
that
release
will
just
get
pushed
to
the
next
bug-fix
release.
A
Nothing
super
critical,
but
always
good
to
fix,
bugs
and
and
then
in
the
one
point
one
point
0
release.
This
is
one
that's
coming
out
in
May
we're
planning
on
doing
a
couple
of
different
things:
adding
a
rich
text
editor,
which
is
going
to
be
the
biggest
hardest
issue,
putting
in
token
and
path
auto,
which
are
two
controls
now
that
we
need
to
get
into
court
and
updating
the
administrative
look
and
feel
so.
A
I
only
had
a
bunch
of
progress
on
both
token
and
pasado
modules
and
canned
rib,
which
is
good,
assess
the
first
point,
and
then
we
also
have
a
strategy,
a
couple
of
issues
talking
about
strategy
and
how
to
move
these
things
before
like
which
features
should
be
included
which
ones
shouldn't
wear.
These
are
interfaces
should
live
stuff
like
that,
so
I
think
we're
making
progress
on
token
papad.
Oh
I,
don't
think
anyone
has
even
thought
about
the
rich
text
editor.
A
Yet
that's,
obviously
a
bigger
harder
task
than
the
moving
things
from
contributor
core
issues,
but
I
think
it
is
the
one
thing
that
is
potentially
not
going
to
get
done.
So
that's
something
anyone
wants
to
work
on
that.
We've
got
some
issues
there
on
how
to
get
moving
on
that
to
get
weighed
in
on
other
things,
we're
working
on
that
aren't
necessarily
scheduled
for
any
particular
release,
our
user
experience
issues.
Anyone
has
any
joke
was
using
backdrop.
A
You
can
go
ahead
and
create
an
issue
in
the
queue
that
has
the
letter,
C,
U
and
X
and
square
brackets
in
the
title,
and
then
we'll
be
able
to
find
those
issues
later
and
work
on
them.
There's
a
ton
of
stuff
that
has
always
bothered
me
about
Drupal
that
just
go
create
some
issue,
and
sometimes
people
just
come
in
and
fix
them,
which
is
amazing,
so
that's
really
fun.
And
then
we
also
have
developer
experience
issues.
A
So
if
you
can
go
and
tag
something
with
DX
and
square
brackets,
that
would
be
you
know,
as
reporting
modules.
If
you
find
things
that
are
frustrating
or
things
that
you
want
changed,
let
us
know
what
those
are.
There's
a
limited
amount
of
developer
experience
changes
we
can
get
in
in
one
point
0,
because
they
have
to
think
about
not
breaking
api's
in
keeping
backwards
compatibility.
A
But
having
documented
what
the
problems
are
is
good
for
us,
because
then
we
can
talk
about
potential
solutions
and
things
we
can
fix
into
taxi,
but
if
I
can't
fix
them
right
away.
So
those
are
too
high
areas
of
focus
that
aren't
necessarily
on
our
road
map
for
the
next
release,
but
things
that
we
should
be
thinking
about
the
whole
time.
A
So
today,
after
this
meeting,
we
had
a
little
backdrop:
sprint,
which
is
good.
We
don't
have
any
other
Sprint's
on
the
calendar
just
yet,
but
there
are
a
couple
of
upcoming
backdrop:
friendly
Drupal
camps,
we've
created
a
calendar
in
the
last
few
weeks
that
contain
all
of
backdrops
infants
and
another
one
that
contains
all
of
these
weekly
meetings.
A
So
if
you
want
to
subscribe
to
and
ical
feed
for
either
of
those
there
now
links
on
that
weekly
agenda,
so
hopefully
that'll
make
it
easier
for
you
to
figure
out
where
we're
going
to
be
in
terms
of
attending
events,
as
well
as
where
you
know
when
these
meetings
are
happening.
If
you're
interested
in
design
meeting,
we've
got
one
of
those
fortnightly
and
then,
of
course,
this
developer
meeting
is
every
week
and
if
there
are
any
events
that
you
guys
are
attending
that
we
don't
know
about
that.
Our
backdrop
friendly.
A
We
want
to
put
those
on
the
calendar
too,
and
eventually,
of
course,
we'll
have
our
own
backdrop
camps
instead
of
drupal
camps,
but
for
now
because
our
primary
audience,
people
who
know
and
love
Drupal,
we
also
know
enough
Drupal.
We
still
are
attending
a
triple
events,
but
Nate
Myles,
a
general
rule,
will
not
offer
to
give
a
talk
about
back
trap
unless
were
specifically
asked
to
either
by
the
organizers
of
the
event
or
someone
who's
attending
the
event
and
wants
to
hear
more
about
backdrop.
A
So
I
guess
you
know
it's
up
to
you
guys
how
you
want
to
deal
with
attending
Drupal
events,
but
we're
trying
to
kind
of
stretch
softly
in
that
general
area.
So
if
you
find
a
Drupal
fun,
drupal
friendly
backdrop
friendly
drupalcamp,
our
Drupal
friendly
back
drafting
with
either
one
and
you
want
to
put
on
our
calendar-
let
us
know
I
will
definitely
add
anything.
You
guys
are
interested
in
attending
on
to
there
and
then,
let's
see,
we've
got
other
stuff
coming
up
to
last
weekend,
I
wrote
a
really
really
really
long.
A
Article
about
back
job
for
drupal
watchdog,
I
ended
up
had
a
whole
section.
I
want
to
add
on
frequently
asked
questions.
I
ended
up,
cutting
it
and
then
neat
wrote
an
article
specifically
on
freak.
We
asked
questions
were
like
just
in
case.
You
have
room,
here's
another
one,
so
hopefully
we'll
get
those
articles
trimmed
down
to
like,
so
that
they
can
both
be
published,
but
I
think
I
got
really
excited
in
wrote,
a
lot
of
words
but
yeah
I.
A
Think
it's
gonna
be
great,
that
that
issue
of
Drupal
watchdog
will
be
out
in
they
I
think
it'll
be
ready
for
triple
con
los
angeles,
so
hopefully
by
then
we'll
have
a
huge,
flourishing,
contribute
and
a
whole
bunch
of
people,
writing
modules
and
building
sites,
a
backdrop
and
everyone
being
really
happy
and
the
article
is
just
kind
of
a
detailed.
You
know
what
you
need
to
know
to
build
the
site
and
backdrop
kind
of
explanation
of
what's
different
with
code
samples
and
stuff
like
that,
so
I
think
it'll
be
really
great.
A
It's
very
positive,
I
think,
there's
we
don't
really
mention
drupal
at
all.
Just
kind
of
this
is
what
backdrop
is
now
that
we
have
something
we
can
just
talk
about
it,
which
I
think
is
good,
so
that
was
pretty
exciting,
but
a
lot
of
time.
Writing
so,
is
there
anything
that
anyone
wants
to
talk
about
that
isn't
on
the
agenda
or
that
we
haven't
been
thinking
about
lately
and
should.
A
A
Okay,
well,
is
there
anything
that
we
should
be
talking
about
weekly
that
we
should
add
to
the
agenda.
We
obviously
added
a
section
this
week
for
our
growth,
where
we
can
track
the
number
of
people
who
are
working
on
Patrick
infant
rough
but
contribs
the
projects
we
have,
which
I
think
is
good
anything
else
like
that.
We
add
just
let
us
know
we
usually
do
a
little
sprint
on
Thursdays
after
this
meeting,
so
Nate
Naomi
and
IRC,
who
probably
have
a
sandwich
I'll,
have
a
little
sprint
tonight.
A
You
see
where
we
can
work
on
a
bunch
of
stuff.
I
have
a
whole
to-do
list,
but
I
came
up
from
today's
meetings
that
I'm
hoping
to
get
through
and
then
working
on
back
joe
a
backdrop
CMS
network
getting
that
poured
into
backdrop.
So
that's
super
exciting
and
then
yeah
I!
Guess
you.
If
you
need
to
get
ahold
of
us,
we
have
a
contact
form
on
our
website,
which
is
great.
That's
new,
so
excited
about
that.
You
can
tweet
at
us
or
back
to
have
CMS
on
Twitter.
A
B
A
I
don't
have
an
official
plan
and
not
sure
the
backdrop
should
have
an
official
official
plan
for
e-commerce.
I
think
we
should
let
the
community
as
a
whole
figure
out
how
they
want
to
solve
it.
I
know,
personally,
I
don't
really
like
using
drupal
commerce.
A
I
think
the
same
reason:
I,
don't
really
like
Jubilee,
don't
really
like
using
triple
e
is
the
reason
I
don't
really
like
using
triple
commerce,
it's
very
abstract,
dude
and
there's
lots
of
little
pieces
and
it's
kind
of
hard
to
wrap
your
head
around
and
development
is
a
little
bit
slow.
So
there
are
a
bunch
of
other
e-commerce
solutions.
Annie
I
know
you've
noticed
you've
been
working
on
simple
card
or
basic
cart.
Those
are
two
modules
that
I
really
like
for
Drupal
7,
that
is
just
very
straightforward:
clean
checkout
process
I
have
lands.
A
She
moved
those
two
backdrop,
but
I
have
not
been
working
on
any
of
it.
So
if
anyone
else
wanted
to
move
those
two
back
up,
I
would
love
to
to
get
that
I'm
showing
if
you
might
have
already
been
working
on
this
already,
but
I
also
don't
think
we
should
limit
what
people
want
to
do
with
backdrop
either
within
any
kind
of
official
policy.
A
I
think
if
someone
wants
to
take
an
uber,
cart
or
drupal
commerce
and
make
them
work
on
backdrop,
they
could
it's
going
to
be
a
lot
of
forwarding,
but
it
could
totally
happen.
You
know
we're
very
compatible
triple
seven
and
taking
something
that
works
on
Drupal
7
and
moving
it
over
even
something
as
extensive,
a
triple
crown,
which
is
definitely
possible.
I.
Just
don't
I,
don't
see
the
kinds
of
people
who
like
working
on
that
code,
preferring
backdrop
/
Drupal
8
in
the
same
way
that
I
don't
prefer
to
work
on
that
code.
B
Yeah
and
Luke
had
a
question
about
doing
all
many
people
with
downloaded
backdrop
or
I
think
people
are
using
it.
We
don't
know
how
many
people
downloaded
it
because
github
doesn't
track
downloads
anymore
it
used
to,
but
they
took
it
off
because
apparently
they
had
a
scaling
problem
tracking
downloads,
so
so
good
up
those
in
track
downloads
anymore.
However,
we
can
get
information
on
how
many
people
have
started
at
Pantheon
instances
and
I.
Think
last
we
heard
how
many
was
it.
Jen
I
think.
A
B
B
We
do
have
the
update
module
actually
enabled
by
default
on
new
installs,
and
they
are
reporting
to
backdrop
CMS
gorg,
it's
just
the
backdrop.
Cms
org
isn't
actually
capable
of
ingesting
that
information.
Yet
so,
as
soon
as
we
set
up
the
update
server
and
actually
have
that
storing
information
about
what
sites
are
out,
there
will
know
right
away
how
many
backdrop
sites
are
out
there
that
have
update
module
enabled
so
as
soon
as
the
server
is
actually
up.
B
A
I
think
that
would
be
super
useful
information
for
us
to
have
I,
don't
know
what
the
plan
is
for
the
updates
over
I
know
we're
kind
of
in
on
hold
in
terms
of
actual
update
information,
because
we're
waiting
on
all
of
our
processes
to
be
in
place
for
collecting
statuses
of
stuff,
to
tell
whether
there's
updates,
but
it
can.
A
We
set
up
the
statistics
part
of
it
earlier,
so
that
it
can
count
at
least
the
number
of
sites
that
are
asking
rather
than
you
know,
I,
don't
know,
I,
don't
know
what
the
process
is
for
that,
but
it
seems
like
there
might
be
a
way
that
we
can
get
statistics
before.
We
actually
are
delivering
update
information
through
the
service,
so
yeah.
B
B
It
just
looks
like
it
so
on
on
drupal.org.
They
have
updates
drupal.org,
but
updates.
Drupal.Org
is
actually
just
an
alias
to
drupal
org
that
has
a
CDN
in
front
of
it.
So
they're
all
actually
the
same
server
are
the
same
set
of
servers
but
they're
just
locked
down
to
only
do
certain
things.
So
at
least
that's
my
understanding
or
maybe
they're
they're
they're
separate
service,
but
they
all
pointed
the
same
database
like
it's
possible.
B
They
have
to
web
servers
that
are
both
running
the
same
code
base,
but
one
of
them
is
one
of
them
is
just
for
updates
and
the
other
one
is
is
just
for
for
the
rest
of
your
plot,
org
yeah,
yeah
I'm,
pretty
sure
you
can
do
things
like
I'm,
you
can
go
to
drupal.org
and
you
can
get
the
update
list
from
triple
dot
org.
It's
just
that
the
update
module
has
a
hard
coded
to
use
updates
dr.
Pillai
to
work
instead,
for
example,
okay,.
A
B
A
Well,
that's,
okay,
we
can.
We
can
figure
it
out.
Alright,
so
first
things.
First,
let's
get
back
job,
CM
esta
or
accorded
a
backdrop,
and
then
we
can
figure
out
how
to
start
tracking
statistics
on
how
many
people
are
running
back
drop
sounds
like
a
good
plan.
All
right
was
there
anything
else.
Anyone
else
like
to
ask
about
no
all
right.
Well,
then,
it's
time
to
go
work
on
back
job
Oh,
we'll
see
you
on
IRC
and
the
suq
on
github
on
twitter
or
elsewhere,
as
as
it
as
it
is
thanks
for
joining
everyone.