►
From YouTube: Backdrop Weekly - Dec 31st 2020
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
All
right
we're
live,
it
is
december
31st.
This
is
our
last
meeting
2020
and
this
is
our
weekly
development
meeting.
So
let's
go
ahead
and
start
introductions
with
nate.
B
C
Sure
I'm
luke
mccormick
in
ceremony,
california,
I'm
a
web
developer
manager
type
and
I
talk
too
much
so
I'll,
just
flip
it
to
can,
I
say:
mamadou.
D
E
So
can
you
please
sure
I'll
go
next?
I'm
tim
erickson
in
sync
username,
saint
paul
team.
I
am
coming
to
you
from
dearwood,
minnesota
and
yeah
just
here
to
check
up
on
what
priorities
are
in
our
last
few
days
before
future.
Freeze
joseph.
A
A
Can
all
right
this
week
we
have
one
new
member
to
backdrop
kim
trib.
A
Dj
zwerg
intended,
but
I
gave
it
a
shot:
ported
the
pack
and
upload
module.
I
got
their
maintainer
application,
I
think
approved
and
the
module
is
in
backdrop
and
trip.
So
that's
fantastic,
yep
new
people
coming
in
this
week.
We
also
had
two
brand
new
modules
released:
uber
current
discounts
and
visitors.
A
So
thank
you,
everybody
for
continuing
to
work
on
backdrop,
game
trip
this
past
week.
I
also
wanted
to
say
a
special
thank
you
to
bw
panda
who's
been
working
on
getting
our
tugboat
sandboxes
set
up
for
backdrop,
cms.org
properties.
So
if
anyone
wants
to
make
a
change
to
the
main
website,
they'll
be
able
to
do
that
file,
pull
request,
and
then
we
can
test
the
change
to
the
main
website
in
the
same
way
that
we
test
pull,
request,
changes
for
backdrop
core,
so
that's
coming
along
well
too,
which
is
great
all
right.
B
All
right
so,
as
always,
we'll
go
over
117.
First
there's
just
a
couple
of
items
here
that
are
on
the
agenda.
We
have
lots
of
issues
that
are
in
the
bug
fix
queue,
though,
and
lots
of
things
that
have
been
moving
forward
this
past
week.
One
item
that
we
haven't
yet
merged
is
the
regression
from
117.2
that
the
mysql8
supports
breaks
database
queries
across
databases
which
is
particularly
affecting
civvy
crm,
so
47.45
that
ticket
or
that
issue
has
been
marked
rgbc,
so
that
will
be
probably
moving
in
shortly.
B
Another
sort
of
regression
is
field
set,
css,
the
collapsible
css
and
the
seven
theme
sometimes
can
look
a
little
bit
wonky.
We
have
issue
4766
to
help
address
that
it's
marked
needs
review,
but
we've
had
multiple
reviewers
say
that
it's
an
improvement
on
what
we
have
currently
so
I'm
tempted
to
proceed
with
that
one,
as
is
because
we
haven't
actually
had
any
notes
of
any
problems
with
the
new
css,
so
it
seems
like
it's
probably
ready
to
go,
but
it's
currently
still
marked
needs
review.
B
Just
market
rtbc,
nice,
okay,
yeah,
nothing
like
saying
that
should
probably
be
our
tbc,
but
it's
not
for
some
reason
and
then
yeah
it
doesn't
take
much
now
it
is
okay.
Next
up
site
gets
stuck
in
maintenance
mode.
When
updating
modules,
issue
39.56
it
needs
review,
there's
a
pull
request.
There
gregory
colonos
said
that
he
was
going
to
take
a
look
at
it,
but
we
haven't
gotten
around
to
that.
Yet
that
could
use
some
additional
eyeballs
at
the
code.
B
That
is
there
setting
a
reasonable
or
sorry.
This
is
actually
display
warning
for
max
input
vars
if
it's
too
low
issued
38-24.
B
This
hasn't
seen
work
too
recently,
but
it
needs
needs
some
work
still.
A
B
Okay
yeah,
it
sounds
like
that's
something
I
should
take
a
look
at
too.
That
would
be
nice
to
because
I
haven't
seen
any
of
what's
happening
there.
B
B
The
poll
request
needs
to
be
updated
to
match
the
objective,
there's
pictures
of
what
we
want
and
then
the
pull
request
is
doing
something
slightly
different,
and
so
it
looks
like
the
pull
request
needs
to
be
updated
to
match
the
screenshots.
That
are
what
the
final
goal
is,
which
I
think
is
just
a
change
in
the
in
the
configuration
but
yeah
that
issue
has
been
open
for
a
long
time
is
something
that
was
simple
but
keep
going
back
and
forth
about
what
it
is
that
we
want
to
do.
B
And
lastly,
the
views
or
behavior
sometimes
doesn't
work
as
expected.
The
issue
is
34
15..
Last
we
saw
on
this
one.
The
sandbox
is
no
longer
working
and
it
just
needs
to
be
rebuilt.
The
pull
request
might
need
to
be
rebased
as
well.
I'm
not
quite
sure
how
much
additional
work
is
there,
but
the
sandbox
isn't
working
for
people
to
test
out
the
pull
request
currently
and
that's
it
for
the
items
that
we
bring
up
for
the
next
bug
fix
release.
B
There
are
a
total
of
64
issues
in
the
117.5
milestone,
13
issues
that
have
been
closed
since
the
last
release.
That's
great
we're
making
some
progress
getting
through
the
the
current
bug
list,
but
of
these
1175
ones
hang
on.
Let
me
check
the
count
here.
There
are
five
rtbc
ones.
That's
awesome,
I'm
working
through
those
today
and.
B
118
money
team
will
be
the
next
minor
version
of
backdrop.
It
will
be
coming
out
january,
15th
2021.
As
always,
we
have
three
releases
a
year.
They
always
occur
on
the
15th
of
let's
see
what
is
that
january.
B
What's
the
one
that
said
april,
bro
may
january
april
and
sorry
january
may
and
september
there
we
go
three
times
a
year
and
we
haven't
missed
one
yet,
and
I
doubt
that
this
will
be
any
different,
so
january
15th
will
be
the
release
of
118.
feature.
Freeze
normally
is
on
the
first
of
the
month,
but
because,
if
feature
freeze
lands
on
a
holiday,
we
push
the
first
weekday
that
makes
it
so
that
feature
freeze
is
going
to
be
january.
B
4Th
that's
monday
and
as
always,
what
that
really
means
is
a
little
bit
fuzzy.
We
can
still
commit
stuff
pretty
much
anytime
on
january
4th,
but
our
hope
is
that
we
really
get
things
wrapped
up
as
for
what
we
expect
to
be
in
118
by
the
end
of
the
weekend.
B
So
let's
go
over
what
it
is
that
we've
got
here.
We've
got
a
number
of
items
that
have
been
merged
into
118
and
we'll
only
go
over
these
ones
that
we're
still
working
through
and
we'll
start
off
with
the
issue
that
herb
dual
is
advocating
for
provide
an
option
to
skip
deleting
the
config
staging
files
after
config
sync
issue:
44
47.
B
jen
reviewed
that
thank
you
very
much
saying
that
we
needed
an
update
hook,
which
is
correct,
herb
tool
added
the
update
hook.
Now
this
needs
just
the
final
review.
I
already
reviewed
it
as
well.
It
looked
great
other
than
the
update
hook
thing,
and
so
I
think
this
is
very
very
close
to
completion
just
needs
one
last
review:
jen,
that's
another
good
one!
If
you
want
to
mark
rtbc,
you
can
do
that
right
now,.
B
Okay,
next
up
is
exposed
file,
name
filter
for
the
media
dialogue
issue.
3293
lauren
has
been
the
advocate
for
this
and
he
has
been
getting
some
help
from
el
muche,
which
has
been
very
helpful.
B
This
has
been
on
my
list
to
do
a
code
review
yeah
lauren
posted
two
days
ago,
saying
that
a
few
weeks
ago
he
said
he
was
going
to
look
at
it,
but
he
hasn't
yet-
and
that's
that's
true,
so
I'm
hoping
I'll
be
able
to
get
to
review
that
either
today
or
over
this
weekend,
when
we
do
the
code
sprint,
so
that
still
needs
your
view
on
the
approach.
B
Next
up
is
adding
a
setting
to
the
menu
block
for
changing
the
break
point
at
which
the
hamburger
appears
issue.
46.63
bw
panda
is
the
advocate
for
this.
It
has
been
reviewed
and
reviewed
and
reviewed,
and
this
is
currently
marked
works.
For
me,
it
needs
final
review
to
mark
rtbc,
but
I
think
this
has
been
reviewed
so
many
times.
I
think
the
approach
is
all
solid.
B
I
think
indigo
zella
tested
in
six
different
themes.
So
it's
all
looking
really
really
good
here.
I
think
I'm
not
sure
what,
if
anything,
is
really
necessary
there,
so
that
could
be
another
one
that
we
could
move
to
rgbc.
A
If
we
could
test
that,
one
on
fights
with
custom
themes
to
make
sure
that
the
custom
themes
aren't
modified
in
any
way,
because
it
does
do
a
lot
of
reworking
of
how
css
is
added
to
the
page.
And
so
if
you
have
a
custom
theme
and
you've
added
css
to
the
page,
there's
a
lot
of
risk
that
that
could
cause
problems.
B
Yeah,
so
that's
the
the
thing
that
indigozella
took
a
look
at.
She
was
checking
like
if
it
worked
with
contrib
themes
and
her
own
custom
theme
and
the
updating
just
to
the
new
version
with
the
change
applied,
didn't
affect
it
because
it's
exactly
the
same
output.
But
if
she
enabled
the
option
to
use
it,
then
it
was
hit
and
miss
whether
or
not
it
worked
with
a
contrib
or
a
custom
theme
or
not.
A
B
Okay,
next
up
is
tim.
Your
issue
for
re-labeling
the
full
html
text
format
to
raw
html
issue.
44.99,
it
says
here:
rtbc:
do
you
have
any
additional
information
there.
E
Nope,
I
haven't
heard
anything
since
we
market
rtbc,
so
anybody
has
concerns.
They
better
speak
up,
quick.
B
B
Let's
see
next
up,
we
have
advanced
caching,
adding
hashtags
and
better
support
for
the
max
age.
Header
issue
issue4127
joseph
you're,
the
advocate
for
this
issue:
do
you
have
any
updates.
B
Yeah,
I
think
it's
pretty
clear
at
this
point
that
this
isn't
going
to
be
118
material,
but
it's
still
great
for
us
to
be
making
progress
in
this
one.
B
Yeah
yeah,
considering
we
haven't
had
anyone
look
at
it.
I
don't
think
besides
yourself,
so
right.
B
Yeah
totally,
okay,
great,
let's
see
next
up
jen
you
advocated
for
this
issue.
4728
a
field
has
value
visibility,
condition
for
layout
blocks.
What's
the
update
on
this
issue
so.
A
B
What
was.
A
The
user
interface
on
the
drupal
7
solution
was
not
great,
and
so
I
wrote
a
new
interface
so
that
it
used
to
be
like
every
content.
Type
and
field
were
listed
in
a
select
list,
and
so
it
exploded.
It
was
too
much.
I
think,
I'm
getting
this
right
and
now
it's
set
up,
so
you
only
get
every
content
type
and
then
you
can
choose
the
field
on
the
second
form,
so
it
makes
it
a
little
bit
better
of
an
experience
and
my
input.
Widget
is
really
rudimentary.
A
It's
just
like
a
text
field
and
you
have
to
type
in
a
value,
so
you're
sort
of
matching.
What's
in
the
database,
but
doc
wilmod's
solution
uses
the
fields
that
the
field
api
uses
or
maybe
maybe
not,
maybe
someone
that
views
uses.
You
know
when
views
lets.
You
do
a
filter.
It
gives
you
like
a
certain
filter
for
different
types.
So
it's
like
a
taxonomy
term.
A
You
get
the
option
to
choose
multiple
values
or
whatever,
so
it
uses
whatever
that
widget
is
which
is
better
than
mine,
and
so
I
want
to
take
the
code
from
his
conversion
of
the
panels.
Plugin
and
add
it
to
my
core
pull
request
and
see
if
we
can
get
the
best
of
both
worlds,
so
yeah,
that's
where
we're
at.
B
So
I
I
maybe
I
didn't
read
this
issue
closely,
but
it
says
I
thought
that
this
was
just
checking.
Does
the
field
have
any
value
or
not,
but
this
is
actually
does
this
field
have
a
particular
value
as
well.
Yeah,
that's
quite
a
bit
larger,
a
larger
problem
than
just
saying:
is
it
empty?
There.
A
B
A
Preferable,
there's
like
an
option
for
like
is
null
or
is
empty.
In
addition
to
like
is
one
of
is
any
like,
so
I
think
that
that's
the
same
pattern
here.
G
For
me,
using
this
on
panels,
I
would
just
leave.
I
would
just
leave
it
blank.
So
if
it
was
a
text
field,
I
would
just
leave
it
blank,
and
that
was
null,
and
that
was
the
problem
I
was
running
into.
Was
that
leaving
it
blank?
It
was
not
recognizing
that
it
was
null
that
it
was
blank,
and
so
it
would
still
show
information
until
you
do
that
c
tools,
access
patch
that
fixes
that
this
also
would
expand
into
paragraphs
for
example.
G
B
A
B
G
That
port,
that
doc
has
out
there
is
I'd,
say
that's
about
90
there,
and
that
can
trip
it's
just
the
null
value.
B
Great
okay
phil:
could
you
actually
keep
going
if
you
would
be
willing
to
give
us
an
update
on
the
next
issue,
which
is
merge
all
of
the
update
pages
into
a
single
page
issue,
27
14.?
B
This
is
gregory's
issue
that
he's
advocating
for
he
and
indigo
zell
have
been
going
back
and
forth
an
awful
lot
with
phil.
You
you've
also
been
commenting
on
this
issue
recently.
Would
you
be
available
to
give
us
an
update
on
this.
G
I
don't
know
if
I'm
the
best
person
for
that
update.
I
had
just
thrown
out
some
ideas
regarding
being
able
to
pick
and
choose
updates,
which
greg
said
that,
yes,
that's
totally
available
and
it's
not
gonna
be
an
issue,
I'm
honestly
not
exactly
sure
how
far
along
he
is
in
that
but
kind
of
from
what
I've
seen
it's
it's
looking
pretty
good.
I
think
it's
getting
pretty
close
to
being
there.
B
Yeah
yeah:
that's
what
I'm
I'm
getting
that
vibe
as
well,
that
the
pull
request
is
in
indigozala
has
been
reviewing
both
the
code
and
the
interface,
so
those
things
have
been
greatly
appreciated.
I
haven't
had
a
chance
to
look
at
this
yet,
but
yeah.
F
B
I'm
optimistic
about
this
one
could
could
conceivably
be
completed,
even
though
it
just
got
to
the
public
realm
like
a
couple
of
weeks
ago,
so
yeah.
This
would
be
great.
All
these
different
update
pages
going
away
and
pointing
at
one
would
be
a
big
improvement.
B
Okay,
that's
it
for
the
118
issues.
There
are
also
a
number
of
118
issues
that
have
been
completed.
Hang
on
I'll
pull
up
the
list
here.
I
guess
this
might
not
be
particularly
exciting,
but
we
did
merge
something
that
we
only
put
into
118
and
that
was
changing.
The
expires
header
that
used
to
it's
fun,
drupal,
trivia,
fact
that
the
expires
header
is
just
any
random
date
in
the
past
and
in
all
of
drupal's
history.
B
That
has
been
dries,
the
founder
of
drupal's
birthday
as
being
that
expires
header,
and
there
was
an
issue
48
to
27,
opened
by
alan
melz.
That
suggested.
Maybe
we
shouldn't
do
that
anymore,
and
so
we
changed
the
expires
header
that
is
now
just
simply
backdrop's
birthday,
the
release
of
backdrop
1.0
and
that
fulfills
the
same
need
as
being
any
date
in
the
past.
So
that's
kind
of
an
interesting
change
that
will
be
in
118
that
just
kind
of
separates
us
a
little
bit
further
from
from
the
drupal
history.
B
It
it
doesn't
affect
hd
access.
I
mean
it's
not
in
the
htaccess
file,
it's
just
one
when
sorry
when
backdrop
sets
its
header
and
really
even
setting
the
expires.
B
Header
is
kind
of
a
non-issue
at
this
point,
because
the
expires
header
isn't
it's
a
deprecated
header
that
is
only
used
by
old
http
clients,
ones
that
are
using
http
1.0,
which
is
basically
nothing
at
this
point,
so
we
could
have
actually
just
removed
it
honestly,
but
this
decision
about
like
let's
change
it
and
as
a
bw
panda
found
the
date
of
drees's
birthday,
is
not
just
in
the
expires
header.
B
It's
also
like
strewn
throughout
tests
and
various
other
places
wherever
we
need
a
date,
and
so
he
went
around
and
fixed
or
changed
every
one
of
those
examples
as
well.
So
that
was
great
okay,
that's
it
oh
for
the
118
updates.
Let's
see,
we
also
have
initiatives,
I'm
not
sure
that
there's
been
things
that
are
that
are
notable
here,
documentation,
we'd
like
to
increase
the
documentation
processes
and
keep
it
up
to
date.
This
is
an
initiative
that
isn't.
F
B
Quite
an
initiative
just
something
we'd
like
to
discuss.
We
had
a
pull
request
this
week,
actually
that
bw
panda
added
extensive
new
documentation
for
pound
states,
the
form
api
property
that
is
notoriously
difficult
to
understand,
and
I
I
don't
think
he
can
really
help
the
difficulty
of
its
understanding
with
documentation.
But
he
did
add
a
lot
more
examples
into
the
form
api
documentation
about
how
to
deal
with
oring
different
conditionals
together.
So
that
was
very
cool,
appreciated.
B
And
then
last
up
is
the
ready
to
wear
initiative.
I'm
not
sure
if
you
guys
covered
that
you
guys
usually
do
during
the
design
call.
Did
I
get
covered
in
the
call
before
this
today?
No.
B
Well,
luke
any
updates
on
regulatory.
C
Nothing
nothing
super
major
like
it's.
It's
close,
I'm
negotiating
with
my
hosting
provider
to
try
to
get
a
new
version
of
the
dev
module.
That
of
the
I'm
not
saying
because
it's
tim,
it's
my
hosting
spider.
I.
C
It's
at
this
point
like
like
a
blog
post
away
like
like,
like
an
hour
of
writing
text
to
them,
have
it
at
mvp,
including
kind
of
like
what
the
next
steps
are
so
and
it's
been
there
moving
slowly
for
a
couple
weeks,
although
I
did,
I
did,
you
know,
write
an
update
to
a
module
since
then,
which.
E
C
Oh,
oh,
oh,
I
didn't
see
that.
E
It's
on
my
yeah
so
check
that
out
and
and
luke
that's
all
indirectly
been
inspired
by
the
your
initiative.
So
so
you
make,
I
mean
I
think
indigo's
ele
made
it
very
clear
that
that's
what
inspired
her
working
on
this
module
for
this
theme.
C
No
cool
look
it.
It's
definitely
moved
the
ball
forward
and
a
lot
of
backward
laterals.
If
you
want
to
stretch
that
metaphor
to
a
breaking
point
but
but
yeah,
no,
it's
good
all
right!
So
that's
the
update.
B
Great
all
right,
that's
it
for
the
product
updates.
We
have
some
small
announcements
as
well
tim.
We
have
backdrop
sprint
coming
up
this
weekend.
Can
you
give
us
some
details
on
it.
E
Yup
there
it's
on
the
event
calendar
for
for
backdrop,
I
don't
know
if
I've
set
up
the
the
room
yet
virtual
room,
we
used
what
did
we
use
the
jitsi
last
time
and
I
think
we'll
probably
do
that
this
time,
but
it's
I
think
noon.
E
I
I
think
I
have
it
scheduled
noon
to
six
this
saturday
from
central
time,
which
should
be
ten
to
four
pacific
time,
but
whenever
anybody's
available
they
can
get
online,
but
I'll
try
to
be
in
the
room,
for
you
know
from
again
pacific
time,
ten
to
four
I'll
verify
that
that's
the
time
I
scheduled.
E
It's
saturday,
so
people
can
continue
to
work
on
sunday
if
they
want,
but
we've
scheduled
our
time
for
saturday.
B
B
E
So
I
added
this
to
the
agenda
without
talking
to
anybody
so
because
I
it's
something
I
thought
about
recently
and
then
forgot
until
the
meeting
had
already
started,
so
we
have
had
the
last
two
years:
we've
had
some
face-to-face
birthday
parties
around
the
country
or
maybe
the
last
three
years.
I
don't
know
this
year.
Obviously
that's
not
going
to
happen
just
occurred
to
me.
We
could
pull
together
six
or
nine
months
ago.
E
E
So
yeah
anyways
it'll
be
friday
night.
If
we
do
it
well,
we'll
have
to
think
about
the
time
zone
issues
and
who
wants
to
participate
and
when
we
want
to
do
it
and
if
we
should
do
it
on
the
15th
or
if
we
should.
I
learned
recently
that,
depending
on
your
time
zone
that
apparently
the
backdrop's
birthday
is
then
the
16th
in
in
england.
E
So
we
could
maybe
we
could
maybe
justify
putting
this
off
until
saturday.
So
we
we're
not
conflicting
with
what
do
people
think
should
we
do
something?
And
if
so,
when
should
we
do
it.
D
Yes,
on
those
days
here
will
be
1.18
launching,
so
we
can
party,
you
can't
participate
or
you
can.
Yes,
we
can
good
because
launching
date,
one
point
one
eight,
so
it
all
stayed
badly.
So
we
can.
B
Yeah,
from
my
perspective,
launching
or
releasing
the
backdrop
118
and
having
the
birthday
party
on
the
same
day
is
always
a
little
bit
stressful
right.
But
honestly,
I
prefer
that
way
as
having
like
an
extra
cause
for
celebration,
like
I
like
them
having.
I
like
it
all
happening
at
the
same
time
like
yeah,
we
just
released
118
and
it's
backdrop's
birthday.
That's
like
multiple
reasons
to
celebrate,
even
though
it's
slightly
stressful
but.
B
Which
is
the
way
our
releases
usually
go.
I'd
say
two
out
of
three
releases
for
a
minor
version,
especially
there's
nothing
that
happens
like
the
last
day
or
the
last
24
hours.
It's
just
literally
the
release,
unlike
bug
fixer
releases,
where
we're
putting
stuff
in
all
the
way
up
into
the
last.
Second,
almost
every
single
release.
E
F
E
If
we
do
that
this
year,
most
of
the
world
is
going
to
be
asleep.
I
E
Not
24
hours
straight,
but
maybe
we
have
two
blocks.
We
have
a
block
on
friday
night
and
a
block
on
saturday
afternoon
that
other
people
can
participate.
Yes,
all
right,
the
the.
E
E
E
D
But
I
think
make
it
it's
from
u.s
time
so
use
its
usa
standard
time.
Its
est
will
be
fine
because
it's
made
this
time
so
whatever
it
is,
so
make
it
as
a
benefit.
B
G
G
I
know
we
were
planning
on.
We
were
thinking
about,
add
that
in
with
the
other
hd
access
change,
but
I
don't
know
what
milestone
that
went
on.
B
B
I
was
kind
of
hoping
that
john
would
come
back
in
and
concede
on
this
that,
like
that,
there
was
some
argument
about
whether
or
not
it's
necessary
or
whether
or
not
we
should
be
supporting
broadly
at
all
or
other
compression
algorithms,
but
yeah.
We
haven't
gotten
that
so,
but
yes,
we
can
add
it
into
the
next
milestone
I'll.
B
What
should
happen
here?
Phil
if
we
follow
our
processes,
is
that
you
should
give
it
the
tag
milestone
candidate.
That's
basically
like
a
request
saying
I
would
like
it
to
be
in
the
next
issue:
milestone
candidate
bug,
and
then
somebody
basically
comes
in
and
seconds
it,
and
I
can
do
that
saying
yeah.
I
think
that
this
should
be
the
next
release
and
then
we
add
the
milestone
tag.
So
if
you,
if
you
would
add
the
label,
milestone
candidate
bug,
then
I'll
remove
that
label
and
then
add
to
the
next
milestone.
G
Okay,
yeah,
I'm
just
kind
of
curious
about
that.
I
don't
know
we
talked
about
a
couple
weeks
back
and
then
I
wasn't
sure
what
that
hd
access
change.
You
said
there
was
another
one,
that's
coming
down
the
pipe.
I
didn't
know
really.
Those
it'd
be
good
to
have
both
of
those
put
in
at
the
same
time,
but
fortunately
this
one
if
it
gets
if
it
doesn't
get
put
in
it's
not
going
to
really
affect
most
people
anyway.
So.
E
G
Really
yeah
just
a
a
server
platform
that
is
going
to
dynamically
serve
broadly
as
the
content
encoding
and
push
that
over.
You
know
over
gzip,
so
an
apache
server
with
mod
broadly,
I
would
recommend
just
disable
mod
gzip,
and
that
way
you
know
make
sure
that
your
pages
are
being
dynamically
compressed
with
mod
broadly
and
then
from
there.
It
should
be
a
matter
of
when
you
enable
and
performance
they
aggregate
and
compress
css
files,
and
it
should
be
doing
the
same
with
javascript.
E
B
Well,
I
think
it
would
be
good
to
have
additional
testing,
but
we
could
also.
I
feel
that
the
this
patch
is
applying
a
fix
that
drupal
has
already
applied.
That
has
had
multiple
testers
on
this
exact
same
change
and
I
feel
like
that's
sufficient
testing.
Okay,.
G
B
Okay,
let's
close,
then
I'm
I'm
working
today
through
the
rtbcq
which
just
got
a
lot
bigger
after
this
meeting,
so
I'll
be
going
through
those
today
and
I'm
I'm
trying
to
get
through
the
118
list
and
at
least
provide
a
comment
on
all
of
these
items
that
we
discussed
today.
B
So
I'm
hoping
to
get
feedback
on
all
of
those
issues
so
that
well
as
we
close
in
on
the
118
deadline
and
as
we
get
to
the
code
sprints,
hopefully
everybody
will
have
what
they
need
to
move
forward
on
these
items.
So
anything
else.
B
Okay,
let's
call
it
a
meeting.
Thank
you
all.
Oh
muhammadu
left,
but
I
was
gonna
say
happy
new
year
again,
but
thank
you
guys
all
for
joining.
Thank
you
out
there
for
our
regular
viewers
that
that
watch
these
meetings
and
thanks
everybody
for
all
of
the
hard
work
they've
been
doing
on
backdrop.