►
From YouTube: Backdrop Weekly - July 12th
Description
Today’s development agenda: http://bit.ly/2zdA12T
A
Hello,
everyone,
it's
July,
12
2008
een,
and
this
is
the
weekly
backdrop
dev
check-in.
We
get
together
every
week
and
talk
about
progress,
development,
progress
on
backdrop
and
peripheral
projects
around
backdrop,
software,
let's
see
we
always
started
off
with
any
updates
from
the
product
management
committee.
We
don't
have
any
things
to
announce
this
week,
so
we
will
just
proceed
onward.
A
Talking
about
website
related
development
tasks,
so
websites
that
are
around
backdrop
including
backdrop,
CMS
dot,
org,
the
forums
and
things
of
that
nature.
I,
don't
think
that
there's
been
substantial
updates
to
back
up
CMS
or
I
did
mention
during
the
outreach
meeting
that
we
made
a
new
security,
page
I,
think
dragger,
you
may
have
had
a
hand
in
making
that
security
page.
Thank
you
for
putting
that
together
and
so
now
we
have
backup
CMS,
Touareg,
slash
security,
which
previously
was
just
a
listing
of
all
of
the
individual
security
notices.
B
A
It
works
a
little
bit
more
about
reporting
issues
if
you
have
an
issue,
if
you
have
a
problem
there
how
to
subscribe
to
the
mailing
list,
lots
of
kind
of
important
details
so
that
new
page
is
there
and
then
we
moved
the
security
notifications
to
a
dedicated
page
as
well.
So
you
can
still
access
all
of
those
in
the
same
same
ways
before
other
than
that
I.
Don't
think,
there's
substantial
updates
to
bankruptcy
and,
let's
start
already
itself
since
last
week,
yeah.
B
We
have
you,
have
a
new
site
as
well
for
the
Drupal
country
bug
dates
site,
so
we
have
a
dedicated
site
which
will
help
us
to
keep
the
modules
that
got
made
into
core
up
to
date.
So
I
haven't
started,
doing
actual
work
on
that,
but
eventually
I
will
need
some
help.
Maybe
the
next
dev
meeting
I
will
have
some
updates
but
or
to
say
now
is
that
side
exists
and
we
sort
of
like
we
can
start
now.
A
Yeah
that
really
gave
me
a
little
chuckle,
because
it's
Drupal
can
trip
up
dates.
Isn't
that
what
it's
called
it?
So
it's
DCU,
which
is
like
you
know,
DC
Comics
universe,
that's
one
Saudi
ciudad
backdrop:
cement
org
is
where
that
lives.
Although
yeah
there's,
there's
not
much
to
see
yet
at
this
point
there
all
right,
let's
see,
I,
also
want
to
give
a
little
recap
on
the
translation
or
the
localization
server.
Since
it's
been
a
while,
since
we've
mentioned
anything
there,
I
was
just
revisiting.
B
A
A
So
it
looks
like
what
we're
now
waiting
on
is
just
an
official
release
of
the
Pio
TX
module,
because
it
seems
to
be
working
fully
at
this
point
and
then
then
we're
effectively
unblocked
on
doing
large-scale
translations
of
a
lot
more
projects
but
similar
to
the
Drupal
localization
server.
I
believe.
B
A
Right
now,
the
process
of
uploading
like
extracting
the
strings
from
kindred
modules
or
from
core
is
an
entirely
manual
process.
So
every
time
a
new
version
of
a
module
comes
out,
some
volunteer
has
to
go
in
run
the
Pio
T
extractor
on
the
new
release
of
the
control
or
the
new
release
of
core
upload
it
to
the
localization
server,
and
then
other
volunteers
can
actually
do
the
translations
of
those
strings.
So
we're
set
up
to
at
least
match
that
functionality
right
now.
A
A
Thinking
so
backdrop
CMS
org,
the
package
runs
through
when
a
new
release
is
made
on
github
and
modifies
the
dot
info
files.
Backdrop
CMS
org
could
also
run
the
string
extractor
at
that
point
and
and
then
send
that
information
over
to
the
localization
server.
Of
course,
that's
you
know
talking
about
a
little
bit
of
custom
implementation
there
and
having
two
sites
talk
to
each
other,
so
it
could
be
a
little
bit
ambitious.
Your
any
other
Jeff
is
actually
a
really
good
one
where
we
could
have
the
localization
server
just
check
for
updates.
A
You
know
of
all
the
contribs
like
download
the
zip
files
run,
the
string
extractor
on
the
code
and
then
create
a
node,
and
then
it
wouldn't
have
to
do
any
kind
of
cross
like
communication,
it
would
literally
just
check
the
latest
releases
and
then
then
download
and
expand
the
files
and
then
run
the
extractor
on
there,
and
that
would
be
nice
because
then
it
wouldn't
we
wouldn't
need
any
remote
API.
It
would
just
be.
You
know,
create
the
localization
information
using
the
you
know,
direct
PHP
code
from
that
server.
A
Yeah
great
ideas
so
anyway,
I
think
I,
trying
to
point
out
the
fact
that
we
are
in
a
good
place.
Therefore,
the
localization
server
I
think
that
we
just
haven't
put
any
attention
towards
it
recently,
because
you
know
things
get
stuck
and
then
we
get
distracted
with
other
things,
but
that's
a
really
great
area
for
taking
that
one
to
the
finish
line,
basically
and
making
that's
really
an
official
service
of
backdrop
CMS,
because
it's
really
close
to
completion.
A
Yeah,
so
you
can
make
it
and
once
you
have
an
account
on
the
localization
server,
I
think
that
you
can
like
the
and
you
can
make
another
language
just
like
on
the
fly
it
just
entirely
is
like.
If
you
want
to
translate
it
into
another
language,
then
you
can
create
the
language
and
then
start
translating
strings
I.
B
A
Yeah
very
true,
and
so
also
interesting,
like
this
localization
server.
This
is
not
running
backdrop.
This
is
literally
a
Drupal
7
site,
which
is
the
same
thing
that
localized
drupal.org
is
running
so
because
localize
dead,
your
bullet
org,
is,
is
actually
you
know
translating
all
of
Drupal
8
modules
as
well.
Even
though
it's
not
a
Drupal
8
site,
the
rationale
here
was
that
it's
like
well,
the
localization
server
doesn't
need
to
be
running
backdrop
like
in
order
to
translate
backdrop.
It
has
all
of
the
capabilities
we
need.
B
A
Ok,
that's
it
for
the
peripheral
websites.
Let's
talk
about
backdrop
itself,
the
next
bug
fix
release
is
going
to
be
1
dot.
10.2.
There
is
a
list
of
issues
that
are
on
the
10
that
you
anticipated
to
be
in
those
we've
got
a
couple
of
them
merged.
It
looks
like
a
couple
of
more
issues
that
moved
back
into
needs
review
status
in
this
past
week,
so
I'll
take
a
look
at
those
as
soon
as
possible.
A
The
only
issue
that
we've
got
that
we've
been
bringing
up
for
a
long
time
as
being
of
large
importance
is
the
database
credentials
in
southern
PHP,
their
syntax
changed.
You
know
in
a
minor
way
that
can
affect
some
sites
that
manually
type
in
the
settings,
dot,
PHP
database
credentials,
and
we
have
a
suggestion
there
on
how
to
make
it
so
that
week
make
that
a
little
bit
more
robust
in
issue
2904.
A
We
have
workaround
in
that
issue.
We
just
need
to
expose
some
more
information
to
the
user,
but
when
we're
using
the
workaround,
so
no
real
updates
on
that.
One
21:04
still
needs
work.
That's
it
for
1.10.
Unless
there's
anything
else
that
you
guys
would
like
to
add,
no
ok,
so
one
9/11
1.11
is
a
next
minor
release
which
will
be
coming
out.
September,
15th,
2018
and
we've
been
seeing
a
lot
of
improvement
in
a
lot
of
different
areas
over
this
past
week.
So
first
up
is
contact.
Module
contact.
A
A
That
has
a
number
of
items
that
could
be
implemented
and
all
of
them
are
pretty
good
ideas.
I
know
this
past
week
a
new
sub
issue
was
added
to
that
3190,
which
makes
a
very
reasonable
suggestion
of
now
that
we
have
a
settings
page
for
the
contact
module.
That's
not
just
the
categories
page.
We
should
duplicate
the
permissions
for
who
can
submit.
B
A
Contact
form
on
to
the
settings
page
very
similar
to
the
way
that
we
put
permissions
for
who
can
create
particular
content
types
on
the
content.
Type
page
like
duplicating
the
permissions
grid
for
particular
segments
of
modules,
makes
it
so
that
users
don't
need
to
go
to
places
to
configure
a
module.
So
it's
a
great
a
great
suggestion.
It's
just
an
idea
at
this
point,
so
3190
is
kind
of
an
obvious
improvement
that
that
were
up
for
implementation,
hoping
to
get
to
implementation.
Volunteers.
A
A
Let's
see
extra
color
module
color
module.
There
is
also
a
large
metaphor
it
at
1905,
but
that
meta
has
gotten
a
little
a
little
overwhelming
the
the
issue
where
most
work
has
been
happening
for
color
module
and,
if
you're
looking
to
jump
in
on
improving
it
is
thirty-one
eighty
six
which
was
separated
out
from
that
meta,
and
it
is
specifically
the
user
interface
work
that
Joseph
blan
has
been
doing
to
make
configured
color
module
much
much
better.
A
In
backdrop,
there's
also
a
self
issue
of
the
meta
for
colorizing
basis,
which
would
also
be
a
great
enhancements.
I
know
basis
is
proven
to
be
pretty
popular
and
it
has
always
intended
to
be
colorized,
but
we
got
a
little
bogged
down
and
trying
to
in
trying
to
like
get
a
little
too
ambitious
about
color
module
so
so
colorizing.
It
is
not
actually
that
difficult.
There's
a
pull
request
there.
I
know
it
has
Wes's
blessing.
That
could
just
use
some
testing,
and
this
currently
needs
review.
A
Okay,
next
up
node
preview
so
or
bring
back
node
preview,
which
is
thirty
sixty
two
thirty
sixty
two
currently
needs
work,
functionality
and
testing
or
technically
it
looks
good
functionality.
Wise
I
think
people
are
really
pleased
with
it.
The
current
holdup
is
that
we
have
some
styling
challenges
that
the
buttons
for
returning
back
to
the
node
form
basically
need
to
be
shown
as
though
they
are
using
administrative
styling,
but
you're
on
a
page
that
is
on
the
front
end
of
the
site.
So
this
is
kind
of
like
the
inverse.
A
A
problem
of
its
ckeditor,
we
show
something
in
the
front
end
theme
inside
of
the
admin
theme,
and
now
we
need
to
do
the
opposite.
We
need
to
show
the
back
to
node
edit
form
button
as
something
that
is
displayed
in
the
admin
theme
on
the
front-end
site,
and
so
that
is
our
current
challenge.
I
think
with
that.
Ok.
B
It's
not
only
the
stylee,
ideally,
we
would
like
any
contribute
or
anything
that
adds
buttons
in
that
submit,
read
them
to
be
reflected
there
like
looking
to
integrating,
for
example,
save
draft
which
adds
a
few
buttons.
So,
ideally,
we
would
have
the
same
buttons.
There
wouldn't
be
rewriting
different
code
for
that
bit,
so
we
shouldn't
be
reusing.
The
code
that
sort
of
like
renders
the
submit
button.
If
we
can
do.
B
A
A
So
still
some
challenges
there,
although
the
core
functionality
of
that
is
looking
pretty
solid,
I
think
that
we're
looking
for
just
more
collaboration
on
that
issue,
dark
Holman,
has
been
taking
the
lead
on
it
and
looks
like
he's
been
open
to
doing
just
about
anything
to
make
that
happen,
but
I
think
that
we
need
to
resolve
that
particular
problem
and
any
ideas
as
to
how
to
do
that
or
anyone
looking
to
try
to
take
that
on
themselves.
I'm
sure
that
additional
help
would
be
appreciated
there
yeah.
A
A
Very
exciting
stuff,
next
up
core
updates.
Our
automatic
core
updates
is
issue
2018,
that's
a
large
another
meta
and
we've
got
a
number
of
sub
issues
underneath
that,
let's
see,
we've
got
two
issues
that
haven't
had
any
real
substantial
changes
in
the
past
week,
issue
30
105,
which
is
allow
core
updates
via
the
user
interface-
that
one
currently
needs,
testing
and
I
think
still
has
a
problem
with.
If
authorized,
PHP
is
necessary
than
the
automatic
core
update
or
the
user
interface
update
doesn't
work
correctly.
A
We
kind
of
a
larger
issue
kind
of
have
a
larger
issue
around
authorized,
dot,
PHP
and
what
its
future
is
anyway,
authorize
that
PHP
is
currently
used
when
applying
contribu
updates
to
allow
if
the
web
server
user
and
the
user
that
owns
the
files
on
disk
are
different,
authorized
dot.
Php
allows
you
to
type
in
a
username
and
password
of
an
FTP
user
to
write
those
files
to
disk,
but
we
only
use
that
during
can
trip
up
dates
currently
during
CRO
or
updates.
It
also
injects
itself,
but
then
it
doesn't
work.
A
A
C
A
That's
correct
and
that's
why
it's
interesting
you
know
for
a
can't
be
on
upstream
and
for
some
other
services
like
that
I
think
I
haven't
trying
to
on
on
platform,
but
in
pantheon
land.
When
you
switch
your
site
to
FTP
mode,
it
makes
it
so
that
the
web
server
and
the
files
are
owned
by
the
same
person,
and
it
makes
it
makes
things
writable,
and
so
they
have
that
functionality
largely
because
WordPress
functions
the
same
way
it
weird
press
doesn't
have
any
concept
of
you
have
to
type
in
a
username
and
password.
A
What
WordPress
just
has
the
ability
to
write
to
the
file
system
if
you're
using
the
automatic
updates
and
that's
the
end
of
the
story
which
I
know
from
a
security
aspect,
people
get
nervous
about
that
particular
capability.
But
at
this
point
it
seems
like
that's
the
lesser
of
two
evils
like
not
having
automatic
updates
and
having
you
know,
Drupal
geddens
like
we
seem
to
think
that
automatic
updates
here
are
either
not
worth
it
or
are
required
too
many
compromises
until
we
need
them
and
then
and
then
all
of
a
sudden
it
just
like.
C
Thing
I
have
a
question
about
there,
like,
like
I,
think
we
should
have
some
kind
of
a
description
about
that
like
on
that
Settings
tab
in
for
14
issue
for
14
I,
don't
know
it
could
get
pretty
wordy
though
right
like,
but
but
we
should
probably
say
something
that
summarizes
what
you
just
said
that
you
know
if
you're
not
using
git
and
you
want
as
little
maintenance
as
possible.
Then
you
know
turn
this
on.
But
if
you
are
using
git,
then
you
probably
don't
want
to
turn
this
on
something
like
that.
Mm-Hmm
yeah.
B
So
always
thinking
something
similar
like
if
the
correct
permissions
are
not
says,
we
do
not
block
the
installation
of
backdrop,
but
once
the
site
has
been
installed,
then
automatic
updates
has
the
page
for
the
automatically
Bates
has
a
message
that
says
you
need
to
correct
the
permissions.
If
you
want
automatic
updates
to
work,
so
this
would
be
the
owner
of
Suites
so,
and
we
can
point
to,
we
can
point
to
documentation
there
like
we
can
have
a
link
that
points
to
documentation
which
people
can
read.
That's.
C
A
A
A
Would
make
sense
to
do
that,
but
the
installation
of
modules
is
is
handled
in
installer
module,
so
it
is
possible
to
have
update
module
turned
on,
but
not
installer
module,
which
tells
you,
if
updates,
are
available
but
doesn't
actually
apply.
The
updates,
because
right
now,
update
module,
shows
you
if
there
updates
available
and
then
the
link
to
actually
apply
the
update,
friction
trip.
Module
is
for,
controls
is
only
shown
if
installer
module
is
also
enabled,
and
so
we
can
put
the
warnings
and
the
filesystem
permission.
A
Tex
and
all
of
the
things
like
that
in
installer
module,
because
it
is,
it
should
be
exclusively
responsible
for
installing
new
modules
and
updating
modules.
It
basically
does
the
job
of
putting
the
code
in
place,
which
is
actually
where
you
know
this
update
modules
via
the
UI
3105,
like
that
changes
some
core,
but
also
install
our
module.
A
Anyway,
so
the
overall
meta
issue,
though
2018
for
core
updates,
we
are
still
stuck
on
3105
because
of
that
authorized,
dot,
PHP
problem,
one
way
to
solve
that
would
be
to
either
fix
the
author
as
that
PHP
issue
that
we're
faced
with
right
now
or
take
a
longer-term
view
and
and
potentially
consider
removing
the
authorized
dot
PHP.
So
we
don't
need
to
fix
that
problem
and
that
that
might
solve
the
problem
in
a
different
way.
A
Let's
see
package
signing
this
is
an
issue
in
1992,
where
we
want
to
increase
the
security
of
the
delivery
packages
to
make
sure
that
they're
not
tampered
with
in
delivery
and
that
they're
uncorrupted
in
download.
That
hasn't
been
any
updates
this
past
week,
but
that
issue
has
got
some
exciting
things
going
on
in
1982
issue.
A
B
A
B
A
And
and
yeah
exactly,
we
also
can
start
the
package
signing
improvements
on
like
backdrop,
CMS
org,
and
go
ahead
and
start
adding
the
signatures
and
then
build
out
cores
use
of
the
signatures
at
a
later
point,
yep
and
then
right
now,
there's
a
pull
request
in
1992.
That
makes
those
changes
like
in
all
three
places,
in
fact
ropes.
We
messed
org
in
project
module
and
in
core,
and
we
could
separate
that
up.
Those
we
almost
inevitably
will
need
to
separate
those
out
in
two
separate
ones
right
now.
It's
just
all
together
for
demonstration
purposes,.
A
Okay,
more
issues
here,
let's
see
tags
for
modules,
issue
number
37.
This
is
a
small
enhancement
that
makes
it
so
that's
modules.
In
addition,
having
a
category
also
have
tags,
this
got
rear
old
in
the
past
week,
but
took
it
a
little
bit
too
far
and
when
tanks
were
added,
categories
were
actually
removed
and
prayer.
Our
previous
discussions,
in
that
we
were
planning
on
just
simply
adding
the
ability
to
have
tags
and
not
substantially
overhauling
the
modules
page,
but
the
most
recent
re-roll
took
it
a
little
bit
too
far.
A
So
it's
been
stated
in
the
issue
that
we
prefer
to
keep
the
user
interface
pretty
much
exactly
the
way.
It
is
now
and
only
add
the
tagging
capability,
so
we
actually
just
need
to
be
a
little
less
ambitious
about
the
current
pull
request,
so
it's
been
reroll,
but
we're
still
back
or
still
in
a
situation
where
that
issue
needs
work
or
the
poor
request
needs
work.
A
Next
up
is
better
statistics
tracking
issue
218.
This
is
a
concept
that
we've
been
talking
about
for
a
long
time.
We
basically
need
a
volunteer
to
champion
this
particular
issue.
We
have
lots
of
ideas
about
the
way
that
this
should
be
implemented,
but
no
no
undertaking
of
implementation
at
this
point.
In
short,
we
want
to
decouple
the
checking
of
updates
from
the
sending
of
statistics
to
make
it
so
that
you
can
have
your
site
check
for
updates
and
get
automatic
updates,
but
not
report.
A
The
fact
that
your
site
is
running
backdrop
where
your
site
lives
or
any
of
the
modules
that
we're
using
make
it.
So
you
can
get
updates
without
sending
that
information
and
then
have
a
separate
module
that
is
responsible
for
sending
the
information
about
what
your
site
is
running
and
not
just
the
modules
you're
running,
but
also
what
functionality
you're
using
and
then
that
alleviates
some
privacy
concerns,
but
also
allows
your
site
to
have
automatic
updates
once
that
happens,
while
also
maintaining
privacy.
A
So
there's
a
lot
of
discussion
there
in
285
and
I
suggest
reading
over
that.
If
you're
interested
some,
this
one
is
a
slightly
more
minor
issue
issue.
28
87
is
just
a
small
feature
to
automatically
rotate
images
based
on
exif
data.
There
were
some
feedback
posted
this
past
week
and
gram.
72
has
volunteered
to
take
that
on
and
it's
working
on
a
reroll
of
that
particular
issue.
A
Rich
text
editor
file
uploads.
Actually,
these
next
two
issues.
Last
two
issues
are
both
file
and
media
image,
related
hand,
media
and
image
related
issue.
31
34
is
about
the
reusability
of
images
when
placed
inside
of
a
rich
text.
Editor
Gregory
I
know:
you've
said
that
you
haven't
been
doing
too
many
updates,
but
I
know
you've
been
active
in
this
issue.
Can
you
give
us
a
summary
of
this?
One
yeah.
B
Although
I
missed
Graham's
comments
three
days
ago
and
then
yesterday,
so
this
is
mostly
ready
to
go
small
UX
issues,
one
of
them
was
in
wide
screens.
We
first
of
all,
we
have
decided
that
the
library,
the
the
thumbnail
library
would
be
on
the
left
and
then
because
that's
what
the
user
most
uses
a
lot
of,
but
when
we
are
and
that
dialogue,
but
then
this
makes
it
so
that
all
the
controls
that
change
the
file
name
or
the
alt
text,
or
whether
the
image
is
centered
on
order
on
the
far
right
of
the
screen.
B
So
if
you
want
to
switch
between
a
bloating
file
and
selecting
from
images
from
the
library,
then
you
have
to
travel
with
your
mouse
across
the
screen,
and
this
makes
it
videos-
and
this
could
be
solved
the
way
that
I
saw.
It
is
more
easily
solve
this.
If,
when
this
dialog
pops
up,
we
have
it
so
that
it's
aligned
to
the
right
side
of
the
screen
so
that
the
library
expands
towards
the
left.
B
A
B
Other
thing
is
that
we
we
made
it
so
that
it's
clear
now
when
you
select
an
image
and
I
think
holder
works
as
well.
It's
more
obviously
styling
like
there's
a
border
around
it,
but
it's
not
so
other
examples
from
other
applications
and
how
that's
used
like
MailChimp,
make
the
images
sing
more
tidy
like
they
Center
it
and
they
put
a
very
light
gray
background
so
to
make
the
files
sing
that
are
they're
all
the
same
size.
B
A
We
should
try
to
rope
him
in
specifically
into
that
one
he's
been
looking
for
additional
areas
in
which
he
can
play
some
design
skills,
so
that
would
be
a
really
great
one
and
a
large
impact
one
okay,
okay
and
lastly,
we're
still
moving
bits
and
pieces
of
file
entity
module
largely
from
the
contraband
into
core
most
there's
a
meta
issue
prevent
at
1448,
which
has
a
bunch
of
areas
in
which
the
power
and
capabilities
files
could
be
extended
further.
Most
recently,
one
that
has
seen
some
activity
is
26:32
which
dr.
A
Elmont
is
working
on,
making
it
so
that
files
are
filled
bolt
so
that
you
can
put
additional.
You
know,
field
data
on
to
individual
files
without
any
other
entities
associated
Erie
rolled
that
functionality.
I
think
that
it's
conceptually
working,
although
tests
are
currently
failing
and
he's
having
some
problems
with
pre
configuring
that
during
the
installer,
so
we've
got
some
issues
there
to
work
through,
looks
like
some
underlying
issues,
but
we
have
been
saying
some
progress
in
there
and
26:32
could
be
a
useful
area
for
some
technical
capacity.
B
It
offers
this
functionality
in
use,
whereas
we
claim
that
we
have
coordinated
amended
in
the
core
and
I'm,
not
sure
if
it's
a
decision
that
we
made
when
we
ported
the
module
of
which
bits
are
going
to
go
into
backup
core
or
if
it
was
that,
because
we
have
not
been
tracking
the
progress
of
that
more
we
sort
of
like
we
got
left
behind.
So
it's
either
one
of
those
cases
this
this
is
actually
what
triggered
the
creation
of
the
DCU.
B
A
B
So
we
have
been
thinking
about
keeping
up.
There
was
an
old
issue
about
our
keeping
up
to
date
with
contributors
in
general,
and
this
this
would
be
useful
not
only
for
modules
that
have
been
made
into
core,
but
to
contribute
self.
We
should
find
a
way
to
notify
the
maintainer
of
modules
that
you
know,
hey,
there's
a
new
version
of
the
respecting
the
seven
module.
Maybe
you
should
check
out
what
what
improvements
impact,
which
is
pretty
much
what
we
do
with
the
with
core.
A
Okay,
all
right,
there's
more
one
down
eleven
issues
in
the
one
nine
eleven
milestone
you
can
check
it
out
on
github
and
that's
it
for
the
1.11
updates,
lots
of
things
happening
there
and
there's
more.
That
is
always
happening.
This
isn't
this
isn't
by
any
means
that
comprehensive
list
of
what's
happening.
It's
just
where
we're
trying
to
put
some
focus
for
the
next
release.
A
C
So
Larenz
I've
got
some
issues
when
he
communicated
with
the
partner
and
the
pack
for
Western
Mass,
which
I'm
also
part
of,
and
they
have
very
similar
focus
as
backdrop
for
good,
so
they're
interested
in
collaborating
so
I
added
a
couple
people
from
there
to
the
repo
no
work
started
on
that
yet,
but
that's
on
the
slate
they're,
probably
their
next
month's
meeting.
So
that's
great.
A
Yeah,
it
is
great
yeah,
there's,
no
reason
why
this
needs
to
be.
You
know
backdrop
names
typically
like
if
other
volunteer
groups,
for
you
know,
building
websites
for
nonprofits,
just
so
I'm
going
to
want
to
use
backdrop.
That
would
be
a
great
foothold
for
for
backdrop
in
those
organizations
and
a
great
help
to
those
organizations
to
have
a
tool
that
you
know
we're
building
it
for
them.
A
Okay,
if
there's
anything,
you
guys
would
like
that
to
the
agenda,
please
let
me
know
or
post
together
or
if
you
have
edit
access.
Just
just
add
it
right
in
there
and
that's
it
for
today.
Thank
you
guys
all
for
joining,
there's
lots
of
really
exciting
things.
Thank
you.
Everyone
for
watching
this
meeting
join
the
meeting
or
for
your
work.
In
the
backdrop,
issue
queue,
there's
lots
of
exciting
things
and
more
to
come.
So,
thank
you
all
see
you
all
on
the
Internet
bye.