►
From YouTube: Backdrop Weekly August 11, 2022
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
it's
august
11th
2022,
and
this
is
the
weekly
backdrop
developer
meeting.
We
get
together
every
week
to
talk
about
development
activity
in
drupal
or
drupal
backdrop
core
and
beyond.
A
My
name
is
nate
lampton,
I'm
quick
sketch
on
the
internet,
I'm
core
committer.
For
the
backdrop
project
we'll
do
some
introductions,
robert
and
then
martin.
B
B
I'm
robert
lyon
bud
boulder
on
the
internet
coming
from
altadena
california.
A
All
right
great
yeah,
that's
it!
For
today
we
were
talking
about
what
we're
gonna
do
with
this
meeting,
we're
a
little
low
on
attendance
and
also
on
agenda
items.
There's
nothing
in
the
forum
post
for
this
week
to
discuss
and
the
core
updates
are
also
a
little
bit
quiet.
I
think
that
this
is
like
you
know,
we're
we're
right
in
in
the
middle
of
august,
almost
when
it's
like
peak
vacation
time,
I
think
so.
A
I
hope
everyone
out
there
is
enjoying
vacations
if
you're
taking
one,
we
only
had
one
so
we're
going
to
keep
things
a
little
less
formal
today
and
just
kind
of
banter
a
little
bit.
A
We
did
have
one
thing
come
up
in
zulip
this
week,
indigozella
posted
a
question
about
jquery
ui
that
she
would
like
to
be
discussed.
So
there's
a
backdrop.
Issue
already,
hang
on
I'll.
Just
share
my
screen
for
this,
so
this
perennial
issue
actually
keep
jquery
ui
up
to
date
is
the
issue
being
discussed
and
in
particular
because
of
the
security
announcement
that
came
out.
A
This
is
a
dribble
security
announcements
regarding
an
issue
with
jquery
ui
that
jquery
ui
released
a
security
advisory
that
the
checkbox
radio
elements
have
a
potential
vulnerability
in
them.
We
were
checking
this
out
beforehand.
A
I
wasn't
even
sure
what
checkbox
radio,
what
it
does
you
know
neither
did
robert
or
martin,
so
what
it
does
is
doesn't
seem
to
do
a
whole
lot.
Maybe
add
some
events
or
something
like
that,
but
but
we're
not
using
this
anywhere
in
core,
even
though
it
is
bundled
with
core.
A
So
we
end
up
in
this
situation
kind
of
similar
to
drupal,
potentially,
where
there's
a
vulnerability
in
a
library
that
we're
using
but
sorry
that
we're
bundling
but
we're
not
actually
using
it,
and
so
it
is
in
no
way
exploitable
in
backdrop
core
and
and
not
exploitable.
Otherwise,
unless
your
module
or
site
is
actually
using
this
particular
portion
of
jquery
ui,
which,
from
our
analysis
we
can't
figure
out,
we
can't
fathom
why
you
would
want
to
use
this
particular
component
because
it
doesn't
seem
like
it.
It
doesn't
matter
the.
C
A
C
A
Well,
in
any
any
case,
we
still
have
the
problem
that
we
need
to
resolve
this
issue
anytime.
We
have
a
bundled
library.
If
it
has
a
vulnerability,
then
you
know
it's
our
responsibility
to
update
it.
A
C
Yeah,
a
lot
of
the
the
vast
majority
of
files
seem
to
be
in
the
to
do
with
i18n,
so
they're
kind
of
internationalized
files.
A
Yeah
this,
let's
see
what's
in
one
of
these,
oh
well,
it's
a
little
bit
hard
to
tell
since
it's
compressed
but
yeah
it's.
This
is
like
translations.
A
Well
looks
like
she
managed
to
do
it,
but
it
is
super
tedious
to
do
this
process,
because
what
our
our
folder
structure
directory
structure
is
different
than
that
of
jquery
ui,
and
it
used
to
be
that
when
you
downloaded
jquery
ui,
it
would
use
this
structure,
but
they
then
they
changed
it,
and
I
think
that
even
I
think
that
even
getting
these
compressed
files
now
individually
is
difficult,
and
so
the
process
that
we've
done
in
the
past,
if
I
recall
correctly,
is
that
you
have
to
download
the
original
source
files
for
each
one
of
these
jquery
ui
components
manually
or
through
a
script,
run
them
through
a
compressor
of
some
kind
like
uglify
and
then
replace
all
of
the
files
in
their
current
locations.
A
I
was
expecting,
and
it
goes
out
to
say
something
about
how
difficult
this
is,
but
that
she
seems
to
have
just
done
it.
B
A
Yeah
well,
this
is
great
yeah,
thanks
into
gazelle
for
your
work
there
to
get
this
up
to
date,
because
we
do
need
to
update
core.
It
will
probably
be
a
security
release
because
that's
our
pattern
for
doing
all
this
stuff.
However,
the
potential
for
actual
exploitation
of
this
is
extremely
low.
A
Yeah,
so
all
all
very
interesting,
I
wonder
let's
check
zulu
up
one
more
time
if
she
had
anything
else
she
was
asking
about.
In
particular,
we
should
update
oh.
B
A
A
All
right!
Well,
that's
that's
kind
of
it.
That
was
the
only
major
topic
for
today
it
might
be
kind
of
fun.
Just
to
since
this
is
a
little
less
formal
to
gossip
a
little
bit.
A
Did
you
guys
see
the
the
zulu
post
and
the
video
from
dribble
camp
colorado
jen
participated
in
drupal
camp
colorado
as
well,
in
an
open
q,
a
and,
and
the
kind
of
exciting
thing
is
that
dries.
The
founder
of
drupal
had
a
also
a
q,
a
in
which
the
moderator
asked
pre-set
questions
that
were
asked
from
the
community.
Hey
do
you
have
any
questions
for
dries
and
one
of
the
questions
was
asked
by
our
own
saint
paul
tim
about
about
backdrop
and
like
how
is
you
know?
A
What's
the
potential
for
backdrop
and
drupal
to
collaborate?
Kind
of
continuing
the
discussion
that
we
had
from
you
know
is,
is
backdrop
drupal
classic.
You
know
it
backed
up
live
and
we
kind
of
got
an
answer,
but
it
was
a
little.
A
It
was
a
little
bit
like
double
edged.
A
Yeah
yeah,
so
here
I'll
I'll,
read
tim's
comments
here,
while
dries
didn't,
say
everything
I
would
have
liked
him
to
say.
I
think
his
answer
was
helpful
and
generally
positive.
He
stated
two
things
which
were
not
clear
to
me
before
one
that
he
considers
backdrop
part
of
the
drupal
family
and
two.
The
backdrop
is
welcome
at
drupalcon.
A
I
think
he
even
mentioned
sessions.
The
second
one
is
interesting
because
it
has
not
been
clear
to
us
as
a
community
that
backdrop
sessions
are
welcome
at
triplecon,
I'm
inclined
to
reach
out
to
the
da
and
ask
for
official
clarification
on
that
to
make
sure
it's
official
policy
not
just
theresa's
opinion.
B
Yeah
I
watched
the
video
and
it
was
generally
quite
positive,
which
was
great.
You
know
he
did
and
he
he
said
that
they
learned
from
backdrop
about
backward
the
importance
of
backward
compatibility,
and
so
they
put
all
these
things
in.
You
know
to
improve
backward
compatibility,
which
is
great,
but
it
was
sort
of
improving
backward
compatibility
going
from
eight
to
nine
and
so
forward,
but
nothing
that
kind
of
a
limited.
B
There
wasn't
anything
that
addressed
the
big
jump
from
from
seven
and,
of
course,
that's
kind
of
our
the
thing
that
backdrop
offers
so,
but
overall
it
looked
pretty
good.
C
But
yeah
there's
a
there's
a
few
bits
so
well.
Is
that
a
compliment
or
is?
Is
that
not
a
compliment?
I'm
not
sure.
B
A
Yeah
some
things
it
didn't
yeah
kind
of
thinking
that
I
mean
almost
saying
that
backdrop
is
drupal7
like
if
you
move
to
to
then
your
quote's
still
on
drupal
7.,
which
is
interesting.
I
would
actually
kind
of
love
it.
If
people
did
think
that
because
that
would
that
would
be
great,
that
would
that
would
be
a
really
big
win
for
you
know:
half
a
million
sites
that
are
on
drupal
7
if
they
could
use
backdrop
that
easily.
I
wish
it
was
actually
that
easy.
A
But
it's
you
know,
as
as
everybody
knows
here,
moving
to
backdrop
isn't
exactly
trivial
either
it's
a
lot
easier,
but
it's
yeah.
It's
still
a
lot
different.
B
Yeah
there's
I've
got
something
I
kind
of
was
wondering
after
seeing
that
from
this
last
my
last
year
of
being
in
backdrop,
land,
it
seems
like
the
two
biggest
changes
from
drupal
7
are
layouts
and
configuration
all
the
stuff
that
moved
into
configuration,
management
files,
and
my
question
to
both
of
you
and
folks
out
in
in
youtube
land
is:
does
that
move
make
it
easier
to
then
go
to
eight
or
is?
B
Would
it
be
harder
to
go
to
eight,
or
about
the
same
I
mean
that
is
once
you've
moved
all
your
stuff
into
configuration
files?
Would
that
make
it
easier
to
move
to
drupal
8,
because
it's
got
configuration
files
or
is?
Is
it
there's
they
sufficiently
different
that
it
doesn't
really
buy?
You.
A
A
Yeah
yeah,
but
in
in
drupal
land
the
active
configuration
is
actually
stored
in
the
database,
not
in
files
at
all,
so
files
are
actually.
It
looked
like
at
one
point
that
they
were
going
to
use
files
like
we
do
files
on
disk,
but
pricing
yaml
is
expensive
and
slow,
and
so
they
and
there's
other
disadvantages
like
disk,
isn't
always
necessarily
a
fast
access
thing.
It's
also
not
potentially
centrally
stored.
You
know.
So
we
have
we
face
some
of
those
problems,
but
json
files
don't
have
the
same
problem
at
cml.
A
That
json
file
is
extremely
fast
to
parse,
and
so
ammo
files
are
actually
only
used
kind
of
as
an
intermediary
when
you
export
or
synchronize
your
configuration
and
other
than
that,
the
configuration
is
still
all
in
the
database
in
in
drupal,
8
and
9..
A
So
yeah
it
doesn't
really.
I
mean
yeah,
it's
it's
like
getting
the
like
the
configuration
it's
easier
to
read
in
backdrop,
but
you
still
have
to
do
the
mapping
between
what
it
was
and
what
it
is
now
and
because
we
have
been
changing
things
ever
so
slightly.
You
know
I
don't
know
about.
I
mean
a
lot
of
like
there's
a
huge
difference
already
that
drupal
8
and
9
never
really
achieved
full
configuration
migration
anyway,
like
views
don't
move
they
they
they're.
A
As
far
as
I
know,
there's
no
way
to
move
your
s,
your
your
views
from
drupal
7
to
blade
and
9.,
and
so
that's
also
been
kind
of
my
experience
for
a
lot
of
stuff
configuration
wise
that
in
drupal
it's
really
kind
of
better
to
just
rebuild
everything
and
then
write
the
migrations,
because
your
configuration
is
just
like
there's
too
much
different,
you
just
throw
it
away.
A
Yeah
going
back
to
this
talk,
though,
there
is
some
really
interesting
things
yeah,
I
I
am
surprised,
because
I've
never
seen
dress
acknowledge
that
the
drupal
community
learned
anything
from
backdrop.
You
know
like
that
saying
that
back
that
drupal
actually
acknowledges
that
backwards.
Compatibility
is
important,
our
number
one
core
value
and
that
also
the
the
pivot
in
the
slogan
for
drupal,
from
ambitious
sites
to
ambitious
light
builders
that
that
he
talked
about
that
and
at
the
last
drupal
con.
A
That
was
an
acknowledgement,
essentially
that
drupal
basically
lost
sight
of
the
site.
Builder
role,
the
idea
that
you
could
build
a
site
without
code,
and
so
therefore,
that
drupal
lost
sight
of
the
smaller
and
medium-sized
sites,
and
so
I
think,
they're
trying
to
make
drupal
more
perceived
more
broadly
again
to
be
like
the
drupal
is
for
everyone.
A
But
I
I've
often
found
that
that
ambiguity
in
drupal
is
not
actually
been
a
like
that
that
that
wide
of
an
audience
has
not
been
an
asset
to
drupal.
It's
been
a
hindrance
because
you
can't
make
something:
that's
literally
for
everyone,
you
need
to
choose
an
audience
in
order
to
best
serve.
A
That
particular
group
of
people,
so
I
continue
to
think
that
that
that
drupal
will
continue
to
be
enterprise,
software
and
enterprise
first,
and
that
the
efforts
to
try
to
cater
to
smaller
sites
to
try
to
get
their
usage
numbers
back
up
because
that's
what
I
think
is
going
on
here
is
they're
after
market
share,
that
it
looks
bad
that
they
never
will
have
as
many
sites
on
drupal
8
9
as
they
did
on
drupal
7,
because
it's
just
built
for
too
large
of
an
organization
for
most
small
sites
to
handle,
and
there
are
more
small
sites
than
there
are
large
ones,
so
they're
they're
trying
to
basically
cater
to
smaller
sites,
just
to
get
numbers
back.
A
I
think
that's
what
this
is
all
about,
but
I
don't
think
that
they
will
necessarily
be
successful,
because
I
think
that
drupal
has
already
permanently
put
itself
in
an
enterprise
space
and
that's
going
to
be
their
primary
audience.
A
I
I
believe
they're
trying
to
do
composer,
build
a
ui
on
top
of
composer,
because
I
just
can't
fathom
any
other
way
that
that
would
possibly
work
but
yeah
yeah.
I'm
I'm
a
little
dubious
of
that
entire
effort,
because
I'm
not
sure
that
it's
funny,
because
that's
not
an
enterprise
feature.
You
know
it's
like
it's
not
going
to
be
useful
for
the
audience
that
drupal
has
because,
when
you're
using
composer
like
it's
like
you're
you're,
really
tied
into
using
the
command
line
already.
C
A
Yeah
well
yeah
anyway,
the
the
yeah
I
think,
I'd
like
to
at
least
go
back
to
what
we
did
get
out
of
this,
that
is,
that
is
positive,
yeah
that
he
considers
back
to
our
part
of
the
dribble
family.
That's
something
that
I've
not
heard.
I
I
continued
to
kind
of
I
continued
to
think
that
he
was
looking
on
backdrop
as
a
hostile
competitor,
hostile
project.
A
A
And
he
also
said
that
backdrop
is
welcome
at
drupalcon,
which
is
very
surprising
because
we
know
for
sure
that
that
has
not
been
the
case
like
jen
has
been
asked
multiple
times
by
backdrop
or
by
dribblicon
planning
committees
to
speak
and
even
keynote
and
when
they
this
is
like
the
planning
committee,
you
know
the
people
that
the
community
portion
of
things,
that
does
the
outreach
and
actually
does
the
volunteering
and
stuff
like
that.
A
But
drupalcon
is
financed
by
the
drupal
association,
and
so
they
have
final
authority
in
in
everything,
and
every
time
this
has
happened.
The
planning
jen
has
asked
the
planning
committee
to
check
with
the
drupal
association
first
and
the
dribble
association
has
come
back
and
refused
or
rejected
the
the
proposals,
and
so
the
unofficial,
or
you
know,
real
response
that
we've
had
previously
is
that
proposals
to
speak
at
drupalcon
have
been
rejected
by
the
drupal
association.
A
Explicitly
and
so
saying
that
that
that
were
that
backdrop
is
welcome
at
drupalcon
is
a
really
big
shift,
and
I
I
don't
think
that
yeah
like
like
tim,
says,
if
that's
his
opinion,
that's
one
thing
or
if
this
is
actual
official
policy,
I
think
what
he
kind
of
may
have
been
inferring.
There
was
that
members
of
the
backdrop
community
have
been
present
at
drupalcon
and
that's
not
quite
the
same
thing.
A
But
maybe
also
like,
maybe
finally
buried
the
hatchet.
You
know,
like
you
know,
I.
I
don't
think
that
you
know
I
mean
our.
The
collaboration
between
community
members
between
our
two
projects
has
actually
been
really
excellent.
I
think
the
security
coordination
in
particular
has
been
really
excellent,
even
though
it
hasn't
been
perfect.
A
The
effort
and
the
thoughtfulness
of,
like
you
know
both
communities
working
with
each
other
backdrop,
helps
refine
and
test
drupal
7
patches,
for
example,
which
the
drupal
community
appreciates,
and
we
appreciate
that
we
have
access
to
security
issues
that
are
affecting
all
versions
of
drupal
so
that
we
can
cross
check
if
those
same
vulnerabilities
exist
within
backdrop
and
that's
you
know
been
done
without
really
any
explicit
approval
other
than
from,
like
the
security
team
lead
at
drupal
and
and
and
our
and
our
community
members.
A
So
I
I
yeah.
I
definitely
think
the
community
effort
is
there
and
that
you
know
it's
not
universal,
but
you
know
it's
overall,
it's
it's
generally
still
pretty
positive,
but
this
is
this
is
some
real
advancement
in
the
potential
like
thawing
of
relationships
if
this
is
actually
if
we
can
actually
act
on
some
of
these
things
that
that
teresa
said
about
how
we
can
work
together
so
very
interesting,
I'm
yeah,
I'm
also
just
really
surprised.
A
Well,
I
think
some
of
this
thing
rachel
lawson,
who
I'm
not
sure
I
don't
think
she's
at
the
drupal
association
anymore,
but
she
had
been
quite
prominent,
but
she
was
the
moderator.
I
think
that
she,
she
has
a
generally
fond
opinion
of
backdrop,
and
I
really
appreciate
her
surfacing
and
asking
the
question
that
tim
asked
very
specifically
about
backdrop
to
dries,
and
even
though
this
was
a
pre-recorded
session,
that
makes
it
even
more
notable
because
it
wasn't
like
sprung
on
him
as
a
surprise.
A
It
actually
was
asked
in
a
pre-recorded
environment
and
then
later
posted,
which
means
they
had
an
opportunity
to
remove
it
if
they
wanted
to.
So
it's
a
really
big
deal.
I
think
that
it's
some
official,
maybe
not
official,
but
it's
some
acknowledgement
of
backdrop
and
its
effects
on
the
triple
project
and
it's
yeah,
generally
kind
of
positive.
C
Just
possibly
mentioning
not
in
the
forum
post
about
the
meetings,
but
there
was
a
a
guy
asking
about.
You
know
thinking
about
moving
to
backdrop
but
wanting
to
know.
C
Well
what
will
it
look
like
moving
from
backdrop,
one
to
backdrop
two
and
do,
and
so
I've
tried
to
sort
of
provide
some
reassurances,
so
we're
very
committed
to
trying
to
make
update
upgrades
as
painless
as
possible,
and
this
is
what
the
current
road
map
looks
like
and
that
that
might
change
as
drupal
7
if
drupal
7
end
of
life
changes
but
in
in
terms
of-
and
I
think
the
particular
point
he
had
was,
if
he's
developed
lots
of
custom
modules
and
then
there's
changes
how
how
big
a
job
is,
it
gonna
be
moving
from
one
to
two.
C
A
Yeah
yeah,
I
think
we
do,
although
first
of
all,
I'm
not
sure
if
you
pointed
out
like
our
timeline
for
this,
that
backdrop,
two
isn't
going
to
be
around
for
quite
a
while.
Yet.
C
C
A
But
that's
that's
the
plan
yeah
yeah
and
yeah.
Also.
What
that
actually
looks
like
will
be
kind
of
similar
to
it
would
be
nice
if
we
could
have
some
killer
feature
in
backdrop.
2..
We
don't
even
know
what
that
is.
Yet,
though,
because
we
have
found
that
with
adequate
planning
and
effort,
we
can
introduce
nearly
any
feature
in
backdrop,
one
without
major
breaks
in
compatibility,
and
so
we've
been
really
kind
of
struggling
to
find
really
big
features.
A
It
would
be
nice.
It
would
get
a
major
feature
in
there
to
incentivize
people
to
upgrade,
but
primarily
backdrop.
Two
is
going
to
be
removing
deprecated
code,
and
so
the
good
news
is
is
that
at
least
as
far
as
like
deprecated
functions
are
concerned
and
deprecated
methods.
Those
are
really
easy
to
spot,
especially
if
you
use
an
ide
because
it
will
read
those
at
deprecated,
php,
doc
or
doc
blocks,
and
it
will
like
put
a
strike
through
through
your
function.
Saying:
hey,
you
shouldn't
be
using
this
function.
A
You
should
be
using
some
other
replacement
for
it
instead,
and
so
so
that
could
be
sometimes
things
that
might
be
a
little
bit
far
reaching
like
one
function.
That
really
bothers
me
to
no
end
is
cash
clear
all
which
is
used
everywhere,
but
cash.
Clear
all,
is
a
horrible
function.
A
It
does
like
six
different
things
and
what
you
should
use
instead
is
like
cash
flush,
cash,
clear
cache,
there's
like
all
of
these
different
methods
on
the
cache
object
that
you
should
be
using
instead,
so
you
know
there
are
things
like
that
that
you
know
what
we
had
been
doing.
A
You
should
be
doing
something
else,
but
you
know
with
like
code
or
upgrade,
for
example,
it
can
identify
those
sorts
of
issues
and
could
it
would
and
and
can
make
it
so
that
your
backdrop
site,
ideally,
if
you're
writing
custom
code
now
you
should
strive
to
avoid
deprecated
stuff,
and
you
also,
unfortunately,
kind
of
need
to
keep
an
eye
out
for
new
stuff.
A
That's
being
deprecated
as
time
goes
on,
but
you'd
have
a
couple
year
period
there,
where
the
list
of
deprecations
is
locked,
there's
no
new
changes
because
backdrop,
one
is
no
longer
getting
new
minor
releases
and
you
can
use
that
two-year
period
to
transition.
Your
your
any
deprecated
code
to
the
new
equivalence
and
then
in
theory,
you
can
upgrade
from
backdrop
one
to
backdrop,
two
with
no
modifications
to
your
code
at
all
if
you've
already
removed
all
the
deprecated
stuff,
so
that
that's
that's
where
what
we're
shooting
for
yeah
it
also
is
possible.
A
C
B
A
C
A
Yeah
totally,
I
I
see
that
every
now
and
then
it's
it's.
It's
particularly
prevalent
in
contrib
modules.
Sometimes
you
just
get
like
random
things,
and
it
also
happens
sometimes
when
people
are
cross
boarding
stuff
from
drupal
like
patch
or
something
like
that,
and
they
just
forget
to
do
the
replacement
in
the
application
of
the
patch,
and
then
you
end
up
with
the
one
straight
drupal
function
or
something
like
that
in
there,
but
yeah
all
of
these
things
I
mean
you
know:
we've
got
several
years
to
sort
it
all
out.
A
A
That's
what
I
would
like
to
see
at
least
yeah.
It's
really
bad.
I
mean
major
versions
for
us
are
almost
like
more
like
a
a
housekeeping
sort
of
thing
than
they
are
like.
You
know
major
new
features,
but
eventually
what
we'd
probably
see
is
that
there
would
be
compelling
features
in
backdrop,
two
that
aren't
being
ported
to
backdrop
one,
and
that
would
be
the
reason
why
you'd
want
to
upgrade
not
to
mention
the
end
of
life
of
backdrop,
one
so.
A
A
We
haven't
even
made
the
backdrop
to
branch,
yet
so
we
haven't
actually
done
any
of
that
work,
but
it
is
kind
of
an
interesting
question
about
like
what
stuff
should
we
stop
using,
and
I
think
that
you
know
there
is
the
potential
for
doing
things
like
reducing
substantially
reducing
our
use
of
jquery,
for
example,
because
that's
definitely
a
trend
that
is
ongoing
is
that
jquery
is
much
less
commonly
used
than
it
used
to
be,
and
it
also
is
a
lot
less
valuable
than
it
used
to
be
because
browser
compatibility
has
gotten
so
so
good
and
so
wide
that
it
serves
less
of
a
purpose.
A
However,
I
think
we'd
probably
still
include
it
same
as
as
drupal.
Does
it's
a
lot
of
effort
to
remove
it
from
absolutely
everywhere
and
it's
a
lot
of
effort
and
really
for
not
a
whole
lot
of
benefit
either
I
mean
jquery
itself.
Is
you
know,
20k
of
javascript?
I
think
it
actually
compressed.
Isn't
it
like
8k
or
something
like
that?
A
It's
like
it's
completely
insubstantial
in
this
grand
scheme
of
javascript
sizes
and
there's
just
so
much
functionality
that
uses
it
yeah
and
actually
jquery
ui,
rather,
interestingly,
has
kind
of
started
being
supported
again,
like
the
security
announcement
that
we
were
talking
about.
There
wouldn't
be
a
security
announcement
if
it
was
totally
unsupported,
it
actually
got
moved
to
github,
has
new
maintainer
and
is
receiving
some
minor
updates.
A
Now
it
would
really
be
lovely
if
it
finally
got
official
support
for
touch
support,
because
it
really
doesn't
have
that
right
now
and
I
don't
know,
maybe
the
tide
will
will
turn
again
and
maybe
jquery
will
never
go
away,
it'll
be
like
jquery's,
so
valuable
and
so
widely
used
by
millions
of
websites
that
it's
worth
the
effort
to
maintain
it.
It
is
kind
of
surprising
that
something
as
popular
as
jquery,
maybe
not.
B
A
A
Yeah
all
right,
do
you
guys
have
anything
else
to
discuss,
I
think
maybe
we'll
wrap
it
up
for
today.
This
is
kind
of
fun
to
just
do
a
little
change
of
pace.
I
hope
everybody's
enjoying
their
vacation
once
again
hope
you
guys
get
a
vacation
too.