►
Description
Today’s development agenda: http://bit.ly/2acSBdH
A
Alright
we're
on
air.
It
is
thursday
july
21st,
happy
middle
of
year.
Everybody,
let's
see
general
announcements,
gala
box
to
cala
box
beta
2
is
out.
That
is
a
local
development
environment
using
docker
that
has
native
support
for
backdrop.
You
want
to
give
that
a
try.
It's
a
pretty
cool
product.
If
you
would
like
to
make
a
donation
to
backdrop,
CMS
will
send
you
a
thank-you
t-shirt
or
hoodie
or
if
you're,
already
a
backdrop
contributor.
A
It
turns
out
you've
already
earned
your
t-shirt
and
send
an
email
to
info
@
back
trip,
CMS
org
we
can
send
those
out
or
if
you
would
like
a
phpstorm
license.
Those
are
available
as
a
backdrop
contributor,
so
anyone
who's
a
member
of
the
backdrop,
contribute
again
send
an
email
to
info
a
backrub,
see
mr.
org
feel
like
a
phpstorm
license.
A
B
Not
really
an
announcement
but
is
related
to
t-shirts,
and
that
is
that
we're
almost
entirely
out
of
the
dragon
t-shirts
and
so
we're
going
to
be
printing
new
backdrop.
One's
the
black,
the
dark
gray
ones,
would
service
the
word
back
dropping
in
the
square
across
the
front,
because
those
were
both
popular
and
asked
for,
and
we
didn't
have
very
many
of
them
in
the
first
place.
So
so
next
round
of
t-shirts
should
be
coming
up
soon.
Oh.
A
C
B
So
the
first
time
we've
got
here
is
testing
infrastructure,
testing
infrastructure.
We've
had
this
ongoing
issue
that
Gore
has
been
making
leaps
and
bounds
of
improvements
to
zen
sia,
which
is
what
we're
currently
using
for
a
testing
framework.
We
still
have
travis
CI
turn
on.
I
had
anticipated
turning
that
off,
but
hadn't
gotten
around
to
it.
But
at
this
point
we
really
can
turn
travis
off
any
time.
Now.
It's
really
just
kind
of
giving
us
unnecessary
redundant
testing
is
MC.
I
runs
usually
in
about
five
minutes,
which
is
awesome.
B
Some
recent
updates,
I
heard
from
Gore,
but
I
haven't
actually
had
seen
them
in
action.
Is
that
I
think
that
we
now
have
or
will
have
in
the
very
near
future,
live
updating
as
the
test
results
are
posted,
so
we
have
Ajax
updating,
as
that
happens.
Yes,
yay,
that's
so
exciting,
although
reloading
the
page
really
wasn't
that
bad,
since
it
only
took
a
couple
minutes
anyway,
the
live
updating
of
test
results
is
also
a
huge
welcome
improvement.
B
So
that's
great,
oh
and
the
ability
to
restart
tests
right
I'm
reading
here
from
the
chat,
because
side,
of
course
got
a
shitty
internet
connection,
but
I've
heard
that
does
it
is
glitchy,
sometimes,
okay.
Well
it's
getting
there
so
every
now,
and
then
we
still
have
random
failures.
Occasionally,
although
we've
really
mitigated
a
huge
number
of
random
failures,
so
they're
happening
a
lot
less
frequently
now
so
in
the
near
future,
we
should
also
be
able
to
restart
tests
in
the
event
that
they
fail.
I
know
on
travesty.
B
B
1947
is
the
we're
using
this
NCI
and
Travis
CI
issue
I
think
enable
oh
actually,
that
one's
already
been
closed,
mm-hmm
no
see
I
think
maybe
all
of
these
may
have
been
closed.
Okay,
we
still
just
have
one
issue:
that's
like
research,
continuous
integration,
testing
platforms,
besides
Travis
CI,
but
I.
Think
at
this
point
you
should
probably
close
that
one,
not
two,
because
we're
pretty
satisfied
with
things.
There
is
still
the
random
test
failures
issue,
which
is
a
giant
meta
issue
at
1478.
B
B
Okay,
let's
see
here
a
project
packager,
so
Gord
did
some
additional
updates
on
the
packager
that
are
on
my
plate
to
actually
get
them
deployed
backdrop
CMS
org
I
did
do
a
code
review
of
the
changes
to
project
module
and
they
all
look
great
I
chose
in
the
process
of
reviewing
and
committing
them
before.
I
went
on
vacation
but
didn't
actually
get
around
to
it.
So
the
new
package
manager,
stuff
or
sorry
up.
B
Some
people
have
noted
that
if
you
are
creating
releases
right
now
that
they're
not
showing
up
on
backdrop
CMS
org,
that's
the
packager
and
we're
working
on
fixing
that
the
link
for
some
reason
is
missing
from
the
agenda,
but
we'll
get
the
link
add
to
agenda
and
hopefully
we'll
get
that
fixed,
tested
completely
and
deployed
today
or
tomorrow
and
next
week
at
the
latest.
Because
that's
that's
a
big
problem.
B
So
you
can
retrieve
the
md5
and
then
retrieve
the
archive
and
compare
them
to
make
sure
they're.
The
same
thing
yeah
that
looks
great
I
haven't
had
a
chance
to
look
at
that,
but
it
looks
like
it
isn't.
It
is
interesting
issue
1992,
okay,
great!
Thank
you
for
the
issue
on
the
packager.
That's
backed
up
CMS
org
issue
264
for
the
packager.
B
D
Know
the
biggest
thing
is
we
could
use
some
testers
for
drush
site
install
command
unless
I
don't
know
if
people
have
opinions,
if
I
should
maybe
just
merge
this
stuff
and
then
I'm
the
idea
that
it's
useful
people
and
then
they
can
report
bugs
if
they
find
them
I,
don't
know,
but
no
nobody's
bit
a
nun
testing
for
that
so
far,
that's
it
and
that's.
What's
in
the
air
for
rush
right
now,
okay,
awesome.
B
Let's
see
you
next
item,
you
had
to
go
to
it:
yeah,
let's
the
dress
hasn't
been
like
yay
dresses
there.
It
works,
Jen
just
removed
it
from
most
of
it
from
the
agenda,
which
I
think
is
great,
but
then
she
put
it
back,
maybe
she's
just
reorganizing
things,
I'll
stop
talking
about
what
she's
doing
today
agenda.
B
A
So
sorry
I
was
just
trying
to
remove
this
definitely
weren't,
acting
like
this
week
but
anyway,
yes,
dr.
Thomas,
to
org.
We
are
currently
working
on
the
showcase
section
and
the
design
fall.
Today
we
did
another
review
of
what
the
showcase
section
looks
like
we've
got
two
signs
ready.
We
just
need
to
build
that
out.
So
if
anyone
has
sites
they
want
to
throw
in
to
choke
a
section.
Now
would
be
a
good
time
to
do.
A
A
That
would
be
great,
and
we
also
have
single
sign
on
with
get
I've
got
a
local
version
of
that
working,
but
I
want
to
push
it
up
to
our
servers
and
do
some
testing
on
it
in
the
wild,
where
my
tests
machine
can
actually
connect
to
github,
so
I'll
try
and
get
to
that
today
and
see
if
we
can
get
some
feedback
on
that.
We
also
are
continuing
to
flush
out
the
support
section
of
our
website,
including
two
really
important
additions,
the
documentation
section
which
is
coming
along
really
well.
A
We've
got
a
bunch
of
great
content
on
the
site
already
getting
flushed
out,
which
all
I
think
to
help
people
find
their
way
around
backdrop
better
and
also
the
forum
section
which
I
know.
If
the
past
few
weeks
there's
been
a
lot
of
progress
on
the
forum
module
which
we
removed
from
core
added
to
contribute,
then
they
started
cleaning
that
up
and
making
it
work
more.
A
Like
we'd
like
to
see
it
work
in
backdrop
with
default
views
in
configurations
that
put
stuff
together,
rather
than
a
whole
bunch
of
custom
code,
so
I'm
going
to
take
a
look
at
that
see
where
that's
coming
along
and
see.
If
there's
anything,
we
need
that,
isn't
there
or
anything
that
we
don't
need
the
disk
there
I
see
kind
of
what,
if
is
between,
where
we're
headed
and
where
we're
at
I'm,
looking
forward
to
playing
with
that,
so
a
bunch
of
other
stuff
we're
working
on
that
can
always
use
some
attention.
C
A
C
A
Actually
implemented
on
the
site,
so
if
anyone
wants
to
couple
for
a
couple
minutes
and
getting
some
of
those
new
features,
that
would
be
good
and
there's
also
a
bunch
of
follow-up
issues
for
blog
news.
The
blog
news
section,
that'll
just
kind
of
make
it
a
little
bit
more
useful
to
people
same
thing.
We've
got
some
fall
of
issues
for
event
listings
that
will
allow
people
to
filter
for
events
near.
A
Same
thing
for
service
provider
listing
food
got
polyps
that
will
allow
you
to
look
for
certain
fighters
are
contractors
in
your
area
or
for
a
specific
focus.
So
if
we
could
just
get
like
filters
headed
to
views
and
that
stuff
there's
a
couple
of
kind
of
low-hanging,
fruit,
sitebuilder
e-type
tasks
that
we
could
knock
off
pretty
quickly,
I
think
all
right.
Let's
should
we
turn
it
back
over
to
Jeff
Jeff
for
release
information.
D
Yeah,
that's
a
issue
2013
regarding
Drupal
7
50,
which
was
a
ton
of
features
and
bug
fixes.
So
some
of
those
I
think
should
be
a
1.5
target.
I'm,
not
some
of
the
like
a
one
is
adding
support
for
EGF
eight
characters,
which
would
be
great
but
probably
put
that
x
rather
poor
floor.
So
I
think
we'll
have
to
you,
go
through
the
list
and
say
this
one's
1.4
for
this
15.
D
A
B
B
You
wanna
say
it
out
loud:
oh
sorry,
I
didn't
I
gephart,
yeah
Jeff
was
done
with
one
point,
four
point:
four
yeah
thanks
for
making
that
issue
by
the
way.
That's
really
great
that
we
for
people
that
haven't
seen
this
before
every
single
time
we
make
a
new
version
of
Drupal
comes
out.
We
work
to
make
sure
that
every
change
that
is
in
the
minor
release
for
Drupal
7
also
ends
up
in
the
next
release
of
a
backdrop.
B
So
it's
great
to
get
those
things
ported
over
I
wanted
to
make
a
note
because
the
dribble
corrib
they
came
out
this
week
and
there
was
a
public
service
announcement
the
week
before
about
several
backdrop:
contribs
that
have
remote
code
execution
problems
in
them
and
we
posted
an
announcement
via
twitter
that
the
core
issue
or
sorry
the
contribute
that
happened
last
week
did
not
affect
any
existing.
The
backdrop
contribute
products,
so
that's
great
and
also
oops.
That's
meant
to
be
a
passat
one
that
13
the
HTTP
proxy
vulnerability
that
was
announced
to
move
this
past.
B
Monday
also
does
not
affect
backdrop,
because
that
dick
will
do
was
in
guzzle
not
in
core
proper
and
so
backdrop
and
I
using
guzzle.
We
also
didn't
have
have
that
problem,
but
we
have
not
made
an
announcement
to
that
effect.
That
the
core
issue
also
does
not
affect
backdrop,
although
under
not
like
every
time,
Drupal
8
comes
out
by
the
core
release
and
I
mean
in
the
future,
that's
going
to
become
increasingly.
B
Inconsistent
I
guess
you
could
say
like
it
when
Drupal
8
has
release
its
kind
of
unlikely
to
affect
backdrop
or
Drupal
7
for
that
matter,
because
the
code
bases
are
extremely
different
at
this
point,
however,
I
do
think
for
the
sake
of
putting
hearts
and
minds
at
rest
that
it
would
be
a
good
idea
for
us
to
make
an
announcement
every
time
any
core
security
issue
is
is
announced.
That
doesn't
affect
backdrop
anyway.
That's
all
I
got
there.
Is
that
backdrop
just
is
not
affected
by
those
issues.
So.
A
I
think
we
should
do
both
a
note
on
the
back
drop
site
under
the
Security
section.
We
should
also
tweet
too,
because
though
I
did
well,
it
does
two
things
number
one
nè
was
worried
about.
It
will
find
out
via
Twitter
if
they're
on
Twitter,
but
it
also
kind
of
makes
backdrop
looks
good
where
it's
like.
Oh
we're
on
top
of
things,
and
no
you
don't
need
to
worry
about
it.
A
So
I
was
thinking
about
that,
making
sure
enough
people
have
access
to
the
Twitter
account
so
that,
if
something
like
that
needs
to
come
out-
and
you
know
the
four
of
us
who
usually
tweet
or
otherwise
indisposed
just
making
sure
like
everybody-
had
access
to
it.
So
maybe
we
should
come
up
with
some
like
clever
way
to
like
share
important
passwords
through
the
PMC,
so
we
can
just
throw
all
that
stuff
up
and
then
that
way,
it's
like
oh
I
need
access
to
whatever,
and
then
you
can
go
to
whatever
and
get
I.
B
Yeah
but
there's
not
a
great
solution
to
that:
Oh
mal
diem
I'll,
all
about
used
for
a
little
while
we
we
just
over
the
last
pass
at
Lobot,
but
last
bus
I,
don't
think
is
free
for
those
sorts
of
services
yeah,
but
great
ideas,
I
love
the
idea.
More
access
to
more
people
is
always
I
mean
to
a
certain
point.
This
is
always
a
good
thing,
because
yeah
we
really
want
to
share,
distribute
that
responsibility.
B
There's
one
issue
1985
that
if
you
are
a
CSS,
wizard,
specifically
flexbox
and
solving
browser
specific
bugs
just
sounds
like
your
idea
of
a
great
weekend,
then
please
take
a
look
at
issue
1985,
which
is
a
safari
specific
bug
that
we're
trying
to
work
out
with
our
flexbox
based
layouts,
I.
Think.
What's.
E
E
E
B
E
E
D
B
C
B
Bug
great
bug
that
we
need
to
get
fixed.
Is
it
upload
an
image
via
ckeditor
in
certain
contexts
like
when
editing
a
block?
For
example,
the
images
can
get
deleted
by
the
temporary
file
cleanup,
which
is
really
not
annoying.
Let's
issue
1373
I
know
Jeff.
You've
done
some
work
on
fixing
that
have
been
waiting
for
review
for
ages.
I've
got
the
packager
I
think
is
going
to
be
my
first
thing
and
then
I'll
return
back
around
to
that
one.
B
Let's
see
ckeditor
unloads
on
ajax
requests
is
issue
1564.
There
is
an
rit
bc
for
this,
but
I
don't
think
it's
possible
to
write
test
for
this
yeah.
That's
totally
true
because
they
don't
have
javascript
testing
at
this
point
in
time.
Awesome
I'll
take
a
look
at
that
and
if
it
just
looks
like
it's
a
straight
up
fix
and
you've
already
looked
at
it
jeff,
then
we
could
get
it
merged
in
okay,
great
well.
That
might
be
the
reason
for
making
one
point
four
point.
Four.
B
Then,
okay,
let's
see
the
next,
that's
it
very
important
bug
fixes
the
next
release.
Minor
releases,
September
15,
2016
1.5
point
0
release
that
ricotta
the
editorial
experience
release
the
biggest
ticket
item
for
this
release
is
the
addition
of
reference
module,
which
right
now
is
moved
in
content
to
contribute
1301.
B
It
doesn't
look
like
references
seeing
a
whole
lot
of
action.
Recently,
it
looks
like
a
bum
month
ago
we
had
a
couple
of
changes
to
reference
module,
which
is
great,
but
there's
still
a
whole
lot
of
things
that
need
to
be
done.
There
mike
has
moved
it
into
a
contributed
in
collaborating
on
that
and
you're.
A
member
of
the
contributor
pio
actually
already
have
access,
but
for
now
you
can
file
pull
requests,
Michael
Byrne
view
them.
He
also,
I'm
sure,
would
be
open
to
collaborating
directly.
B
If
you
feel
experienced
enough
to
just
commit
directly
to
the
project,
then
that
would
be
a
great
way
to
do
that
as
well.
Once
the
contributor
is
looking
good
and
will
do
a
review
as
a
pull
request
to
get
merged
into
core
itself,
and
we
do
need
to
worry
about
a
lot
of
other
things
like
upgrade
paths
for
existing
modules,
node
reference
user
reference
and
entity
reference
modules,
but
how
we
tackle
those
hasn't
yet
been
officially
resolved.
So,
whether
that's
like
there's
a
contributor
to
get
that,
does
it
or
add
rush
command?
B
B
E
I
asked
for
a
review
last
week
and
got
lots
of
issues
so
I'm
going
to
take
a
look
at
those
today
and
yeah
Nate.
Whenever
you
get
a
chance,
probably
after
I
fix
these
issues,
I
want
to
make
sure
that
there's
nothing
else,
standing
in
the
way
and
yeah
blocked
on
responsive
menu
right
now
and
need
some
back-end
help.
If
anyone
wants
to
help
me
with
that,
and
then
can
also
try
and
work
on
a
color
module
or
some
sort
of
color
settings,
integration.
B
Cool
yeah-
this
is
probably
been
mentioned
before,
but
I
do
I
am
really
fan
of
you
know
putting
in
this
up.
For
that
we
have
and
then
iterating
on
it
later.
That
means
the
basis
becomes
like
the
new
core
theme
in
1.5,
but
the
color
module
integration
doesn't
land
into
1.6.
I
would
be
totally
fine
with
that.
B
E
B
B
Ok
well,
the
last
item
that
we
have
in
here
for
1.5
major
features,
as
you
called.
My
new
features
is
improving
the
rich
text,
editor,
which
is
issued
1087
and
that's
a
meta
issue
that
has
a
number
of
different
things
and
it
thinks
like
copy
paste
image,
supports
better
Media
Browser,
a
lot
of
different
items
that
would
really
improve
our
rich
text.
B
Editor
I
would
looked
at
them
recently,
but
I
don't
think,
there's
any
real
lead
on
that
particular
issue:
I'm
really
familiar
with
the
security
stuff,
but
I'm
tied
up
in
a
lot
of
other
things.
So
if
anybody
is
interested
in
becoming
kind
of
the
project
laid
on
improving
our
rich
text,
editor
experience
we're
looking
for
contributors
there
and
I'm
happy
to
help
anyone
that
that
is
looking
into
it.
B
B
Let's
see
also
things
beyond
1.5,
we
have
a
roadmap
backdrop:
CMS
org,
slash
roadmap,
although
I
think
items
for
1.6
are
really
pretty
open
at
this
point,
yeah
one
yeah.
So
I
guess
it's
a
great
idea.
If
you're,
if
you
have
ideas,
big
long-term
plans,
we'd
love
to
get
those
added
as
potential
items
in
the
future,
which
I
know
some
of
them-
we
will
be
talking
about
really
shortly
here,
yeah.
So
I'll,
just
throw
it
a
note
in
here,
because
it's
in
the
agenda
we're
also
always
trying
to
improve
user
experience
and
developer
experience
issues.
B
You
can
find
those
issues
by
searching
for
you
x
or
DX
and
square
brackets
in
the
kid
hubby
issue,
cute
speaking
of
later
than
1.5
releases
later
than
1.5
features
mike,
is
here
hello,
Mike,
thank
you
for
joining
us
and
you've
been
working
on
doing
some
items
to
address
long-term
quarter
security
releases
like
making
automatic
updates
possible.
I
know
it
was
mentioned
last
week
during
a
call,
but
Jen
and
I
went
they.
F
You've
read
my
my
article:
have
you
looked
I've
got
a
number
of
other
things
that
I've
thrown
out
online
since,
since
the
TC
drupalcamp
we
just
kind
of
what
got
me
going
on
this.
So
probably
the
most
interesting
one
is
sort
of
a
design
document
that
I
have
on
github
and
and
sort
of
my
intention
there
is
to
you
know,
because
this
is.
C
F
Hard,
and,
and
and
doing
it
correctly
is,
is
an
iterative
process
and
so
I'm
just
having
a
markdown
document.
That
sort
of
evolves,
as
as
better
ways
are
discovered,
might
be
a
nice
way
to
come
up
with
a
good
plan
if
I
have
that
I
I
have
been
been
sorely
a
guilty
of
not
really
posting
issues
to
the
the
backdrop
issues
in
your
github
repo,
but
it
looks
like
other
people
have
totally
picked
up
the
slack
on
that
is
that
Gregory.
It
looks
like
issue
20,
24
and.
F
That
I,
oh
nice,
that
actually
links
to
my
CMS
auto-update
design
proposal
as
it
as
it
exists
so
far,
I
guess
one
of
the
things
that
I
said
last
week.
That's
worth
mentioning
is
that
I
just
feel
like
auto
updates
should
be
a
thing
in
CMS's
and
right
now,
one
of
the
big
three
has
it
and
I've
looked
into
how
they
do
it
and
they
could
do
it
a
lot
better,
so
I'm
sort
of
thinking
my
strategy
here
is
I
want
to
do
like
the
technical.
F
Whatever
you
know,
project
wants
to
take
this
on.
If
it's,
if
it's
backdrop
or
if
it's
Drupal
or
if
it's
another
one,
that's
that's
that's
cool
with
me
or
multiple
of
them,
but
I'm,
just
hoping
that
that
at
least
one
of
them
does
and
then,
if
I
work
on
trying
to
solve
some
of
these
problems,
it'll
get
used.
So
so
with
that
said,
I'm
interested
to
hear
what
the
backdrop
community
thinks
about
all
of
the
other.
F
You
know
requirements
that
this
would
imply
in
terms
of
like
you
know,
it's
idiot
new,
at
least.
If
you
ask
me,
you
shouldn't
do
auto
updates.
Unless
you
are
supporting
releases,
you
have
supporting
past
releases
as
well,
because
I,
don't
think
that
you
should.
You
know
I
I,
don't
think
that
it's
that
great
of
user
experience
to
push
out
a
lot
of
moving
parts
that
that
the
site
owner
doesn't
even
have
a
chance
to
see
if
this
is
still
doing
all
the
things
that
I
want
I
mean,
like
it's
almost
surely
not
going
to
break.
F
But
you
know
if
you
keep
the
the
changes
to
the
very
minimum
possible,
it's
much
more
likely
than
a
terrific
and
and
consequently
that's
that's
an
additional
sort
of
burden
to
the
backdrop
project
then
right
to
maintain
those
backwards
yeah.
Also,
it's
just
a
sort
of
a
philosophical
question
of
do
you
want
to
have
auto
updates
at
all
because
it's
complicated
software
and
it
might
have
problems
too,
and
that
might
know
that's
it's
a
risk
just
to
have
the
feature
too
right.
So
yeah.
B
Yeah,
we've
got
a
lot
of
items
here,
philosophically,
even
to
solve,
like
all
implementation
aside
right
now,
the
reality
it's
hardly
even
policy.
It's
just.
What
is
actually
done
is
that
we
haven't
yet
encountered
a
situation
in
which
we've
felt
the
need
to
extensively
provide
like
a
patch
based
release
for
every
version
of
back
job,
because
we
haven't
had
a
security
release
that
it's
been
like.
Oh,
my
gosh
is
terrible,
like
we
should
make
a
minor
release
of
like
up
sorry
bug-fix
release
of.
B
If
we
were
able
to
make
a
bug-fix
release
for
every
version
of
minor
release,
sorry
yeah
every
minor
released
to
it
within
limits
like
let's
say
like
within
the
last
two
years,
or
something
like
that,
which
in
our
case
would
be
because
we
have
for
minor
losses
a
year.
That
would
be
the
way
three
minor
releases
here.
B
That
would
be
two
years
worth
of
support
if
you
supported
six
minor
releases
backwards
and
I
think
that
that
would
be
like
a
good
thing
for
us
to
strive
for
what
that
would
mean
like,
like
how
automatic
updates
that
actually
be
facilitated.
I
mean
there's.
Definitely
some
processes
that
need
to
be
changed.
B
Yeah
like
we
would
need
to
make
releases
first
of
all
of
each
minor
version
coming
back
for
two
years,
if
that
occurred,
and
we
would
probably
also
needed
additional
tools
like,
but
in
my
opinion,
I
thought
about
my
handling
automatic
updates
in
various
ways,
but
I
think,
like
you
pointed
out,
Drupal
gettin
was
a
great
example.
That
was
a
one-line
change.
B
You
know,
and
if
that
one
line
change
could
have
been
automatically
deployed,
if
we
would
have
had
some
tool
to
do
that,
then
that
would
have
been
great,
but
just
replacing
files
wholesale
like
taking
the
core
directory
and
like
replacing
other
people's
core
directories,
automatically
super
dangerous
because
lots
of
people
hack
or
modify
core,
and
we
can't
really
in
order
to
actually
be
effective,
we'd
want
it
to
apply
even
if
they
had
had
score
because
we
don't
agent
I
mean
not.
Everybody
follows
everything
yeah
exactly
so
gorgeous
brought
up,
patching
and
I.
B
Think
that's
really
probably
the
most
universal
way
of
doing
it
would
be
if
we
could
somehow,
when
we
made
a
chord
release,
also
make
a
core
patch
and
then
have
a
checkbox
on
backdrop.
Sticky
mess
don't
work
that
was
like
you
know.
This
is
a
security
update,
automatically
push
it
possible
kind
of
functionality.
That
said,
you
know
this
is
a
core
released,
that
we
have
a
patch
for
word
that
should
automatically
be
applied
to
all
existing
installations,
and
then
the
actual
problem
of
applying
the
patch
is
a
hole.
B
F
F
B
Just
from
a
community
standpoint,
I
think
that
we
want
to
make.
We
want
to
try
to
make
automatic
updates
possible.
That's
kind
of
all
that
I
that
I
really
know
for
certain
and
I
think
your
article
makes
all
of
the
good
points
and
that
that
you
used
to
set
it
quite
eloquently
that
it's
written
into
our
mission
statement
to
make
things
affordable,
and
this
is
the
big
issue
for
affordability
and
that
it
would
be
really
walking
the
walk
if
we
could
make
that
happen.
Yeah.
F
He
really
sports,
like
you
should
put
that
if
you
ask
me
front
and
center
on
your
website
somewhere
the
number
of
years
right,
this
release
is
supported
until
whatever
date
it
comes
out
to
be
so
that
that's
really
easy
for
people
to
know.
You
know
I,
don't
to
me.
That's
that's
like
a
big
selling
point.
Maybe
maybe
other
people
wouldn't
feel
that
way,
but.
A
Yeah,
after
think,
I
think
that
is
super
important.
I
think
that
there's
a
lot
that
we
can
do
right
now
to
kind
of
help
us
get
there
like
I,
think
if
we
could
take
a
look
at
and
we
haven't
had
a
lot
of
serious
security
issues,
but
if
we
could
take
a
look
at
our
releases
and
say
like
okay,
well,
we
do
have
the
security
release.
A
I
just
kind
of
put
all
the
pieces
together
now,
even
though
they
aren't
necessarily
doing
anything,
and
we
can
figure
out
like
how
do
you
auto
update
thing
if
we
even
already
have
an
issue
for
that,
because
it's
been
on
our
mind
for
a
while
about
that,
making
long-term
looks
like
ownership
cheaper,
but
as
far
as
the
security
release
is
going
being
ready
and
having
a
process.
That's
like
okay.
Should
module
gettin
happen
again
only
it
is
relevant
to
triple
seven
core
and
backdrop
or
like
how
are
we
gonna?
A
When
is
our
process
for
doing
this?
How
many
releases
for
we
gonna
make
for
backdrop
I,
think
that
would
be
good
to
have
a
plan.
Doesn't
let
us
say
okay,
we
will
make
her
lease
for
every
version.
Back
to
one
point:
oh
we'll
put
a
package
file
for
every
version,
12
1
point:
0
we
bright
bright
somewhere
1
point
0
is
supported
until
January,
15
2017,
and
we
just
start
doing
that.
A
I
think
that
would
be
great
for
status
and
then,
when
we
get
auto
updating
out,
we
can
figure
out
how
to
cross
some
of
these
other
technical
problems.
We
have
in
terms
of
what
people
may
or
may
not
have
done
to
their
own
sites,
whether
we
give
people
an
office
which
to
be
able
to
save
themselves
from
themselves
if
they
know
how
to
find
it.
A
If
we
can
find
a
way
that
will
work
I've
massively
on
all
posting
platforms
or
you
know
how
we're
going
to
be
able
to
actually
apply
the
patches
when
they
when
they
come
out
and
then,
if
you
have
a
patch
version
of
core,
how
do
you
notify
the
person?
The
person
that,
like
the
immersion
they're
running,
is
a
patched
version.
There's
a
bunch
of
little
tiny
turtles
will
have
to
resolve
to.
B
C
A
A
Needs
walk
away,
so
I
guess
I'll
take
over
it.
Thanks
for
that
update,
I
went
ahead
and
look
the
community
growth
section
to
the
end
of
the
agenda.
We
can
do
that
for
a
couple
weeks
and
see
how
that
goes
it.
My
slip
might
also
be
kind
of
exciting
to
end
on
a
positive
note
where
it's
like
living
was
growing,
so
that
could
be
a
good
permanent
place
for
that
anyway,
and
we
do
have
a
community
outreach.
A
So
next
week
the
28th
we
are
supposed
to
be
doing
another
community
outreach
meeting.
So
that's
something
that
Mike
and
I
met
together
last
week
or
last
month
to
talk
about
what
kinds
of
outreach
we
could
be
doing
in
the
meeting
was
kind
of
focused
around
like
how
to
target
the
content
on
the
website
towards
our
intended
target
audience
from
just
ideas
that
the
people
who
made
it
had
fun.
It
has
been
and
I
think
he's,
got
two
pretty
good
ideas
about
how
to
do
that.
A
I
would
love
to
get
some
more
involvement
for
people
who
know
how
to
do
community
outreach.
This
other
than
our
website
like
that,
are
ways
to
use
our
newsletter
better
things
we
should
be
doing
with
social
networking
if
we
should
be
placing
ads
on
Google
or
other
sites
that
specifically
target
people
who
are
trying
to
get
off
Drupal.
Be
like
no.
No,
don't
leave
come
to
backdrop.
I,
don't
know
how
to
do
any
of
that
crazy
marketing
stuff.
A
So
we
good
to
get
some
help
with
that
too.
So
next
thursday,
this
is
the
going
to
be
the
hour
before
I
usual
developer
meeting,
so
it'll
be
12
noon,
pacific
time
we're
going
to
try
and
do
a
content
strategy
meeting
any
of
you
want
to
come
I'll,
try
and
woke
up
an
agenda
today
and
we'll
tweet
about
it
and
actually
can
see
if
we
can
get
some
more
feedback
and
figure
out
what
to
do.
A
G
Yeah
Tim
folks
hear
me:
am
I,
audible,
yeah.
Oh
sorry,
just
on
the
community
involvement
thing,
I
don't
know.
This
is
the
right
moment
for
a
report
that
but
the
I
did
the
n10
Drupal
community
of
practice,
antennas
the
nonprofit
technology
education
network,
yeah,
it's
a
mouthful
I
did
that
call
a
few
weeks
ago
there
was
lots
of
positive
reaction.
People
were
definitely
interested.
It
was
hard
to
figure
out
exactly
how
to
channel
folks
after
that,
like
folks,
were
like
yay.
I
didn't
really
know
how
to
harness
that.
G
So
that
might
be
something
to
think
about
in
terms
of
what
we're
doing
the
community
outreach
so
kind
of
just
it
went
well.
People
are
interested
in
the
Drupal
community,
the
nonprofit
community
for
sure,
but
yeah
thinking
about
continuing
that
engagement
after
we
do
like
a
one-off
event.
I
think
is
also
important.
So.
A
G
G
Of
what
I
was
thinking
right
now,
the
call
to
action
was
I
should
have
mentioned
Calla
box,
but
just
mentioning
Pantheon
was
actually
kind
of
helpful.
I
mentioned
you
could
spin
it
up
and
play
with
it
and
that
definitely
sold
some
folks
so
mailing
list.
Even
if
we're
not
using
it,
you
know
we
can
always
gather
the
folks.
G
G
A
E
A
G
F
A
What
happened
in
Twin
Cities
drupalcamp
is
not
the
content
of
the
talk,
because
that
is
very
similar
from
time
to
time,
but
what's
kind
of
sparked
from
it
and
I
think
the
reason
I
would
love
to
have
you
write
that
as
because
what
the
most
exciting
thing
to
me
is
coming
out
of
Twin
Cities
camp
is
all
of
this
talk
about
Oh,
actual
commitment
to
security
updates
automatic
updates,
like
sentient
like
that
is
the
most
exciting
piece
to
me
of
what
came
out
of
that
whole
thing.
It's
like
yeah.
A
We
did
to
training
and
yeah.
We
did
the
session
mention
those,
but
that's
like
just
kind
of
one
sentence
and
then
works.
Anything
is
like
look
at
all
this
cool
stuff
we're
doing
now,
because
if
that
thing
happened
and
I
don't
have
nowhere
decided
on
any
of
that
yet,
but
just
kind
of
sitting,
like
one
person's
idea,
can
change
the
world.
It's
kind
of
the
message
there
so
we'll.
A
It
be
okay
if
I
wrote
the
post
up
that
linked
to
all
of
these
things,
that
you've
been
writing
and
had
you
review
it
before
it
went
out.
Okay,
let's
do
that
then,
because
I
think,
like
that's
the
angle,
I
want
to
take
it's
like
look.
What
Mike
did.
It
would
be
good
if
it
was
coming
from
you,
but
I
understand
that
you've
done
a
lot
of
that.
So
if
we
could
just
get
you
to
review
what
goes
up,
that
would
be
enough
for
me.
A
A
Especially
if
we
can
get
this
last
bug-fix
release
for
into
144,
that
would
be
good
too
alright.
So
that's
the
end
of
our
news
announcements
section.
Today,
everybody
will
meet
together
on
github
and
get
her
in
solve
all
of
our
problems.
It'll
be
fantastic,
or
at
least
we'll
just
floats
the
phone,
which
is
also
pretty
fun
upcoming
events.
We
have
a
list
of
events
on
vector
of
CMS
org,
their
events
that
are
back
Jeff
related
in
when
we
or
another
whether
their
events,
where
were
presenting.
A
A
training
or
just
doing
ab
off
they're
all
available
for
you
to
browse,
and
if
anyone
is
attending
any
websites
or
any
conferences
that
are
not
on
the
website,
please
feel
free
to
add
them.
It
should
be
available
for
anyone
to
create
a
event.
Node
and
we've
also
have
two
books
out
now
on
backed
out
beginning
backdrop
is
out
in
my
own
on
a
press
or
Amazon
migrating
from
Drupal.
The
backdrop
is
also
I
have
an
order.
I
want
to
order
the
other
book
the
beginning
backdrop
book.
A
It
looks
like
it's
gonna,
be
super
exciting
too,
so
we'll
show
those
off
shortly
all
right
anything
else.
Anyone
is
dying
to
talk
about
today.
Got
four
minutes
left
everyone's
exhausted
all
right!
Well,
I've
get
up
a
lot
of
two
caps
of
things.
I
want
to
check
in
on
today.
Well,
I'll,
see
you
guys
in
Gator.
Thank
you
all
for
coming
and
joining.
Thank
you
especially
my
for
your
diligent
writing
for
last
few
pieces.