►
From YouTube: Backdrop Weekly Dec 3rd, 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,
hello,
friends
of
backdrop:
it
is
december
3rd
2020,
and
this
is
the
weekly
development
meeting
where
we
get
together
and
do
a
rundown
on
just
project
updates
on
backdrop
cms
as
well
as
updates
about
what's
happening,
infrastructure-wise
in
the
contrib
world,
pmc
all
of
the
general
topics
related
to
the
running
of
backdrop.
Cms.
A
Before
we
get
started,
we
like
to
do
a
quick
introductions,
I'll
go
first,
my
name
is
nate
lampton,
I'm
a
core
committer
and
I
live
in
oakland.
California
tim.
Can
you
give
yourself
an
introduction.
C
I'm
scrambling
to
find
the
unmute
button
and
I
didn't
need
to
my
name-
is
tim
erickson,
I'm
here
in
deerwood
minnesota
today
and
I
have
the
good
fortune
to
be
so
swamped
with
work
lately
that
I
am
having
a
hard
time
keeping
up
with
my
backdrop
stuff
so,
but
we
we
have
a
release
new
release,
a
new
release
coming
out
in
a
month
code
free.
So
I'm
hoping
to
spend
time
in
december
catching
up
on
my
favorite
issues.
A
Great
thanks
tim
john.
B
B
Hi,
I'm
jen
lampton.
Sorry,
I
was
muted
took
me
a
minute
to
find
it.
I'm
working
on
a
really
exciting
backdrop,
project
we're
hoping
to
launch
the
first
version
of
our
site
very
soon,
so
I'm
hoping
to
share
it
with
everyone.
Just
making
me
very
happy.
So
that's
it.
Let's
see
justin.
D
A
Yeah
highly
appreciated,
and
some
of
those
we'll
be
talking
about
today,
so
that
that's
it
for
those
presents
pmc
updates
tim.
You
would
mention
that
there
was
an
issue
that
is
making
some
progress.
Getting
through
a
decision-making
process
over
in
the
pmc
is
your
queue.
Can
you
give
us
some
details
about
that
issue?.
C
Sure
to
update
it
for
folks
who
aren't
aware
it's
basically,
the
permissions
for
maintainers
of
contrib
modules,
and
one
of
our
concerns
in
terms
of
how
we've
set
up
permissions
in
the
past
has
been
to
make
sure
that
maintainers
aren't
not
able
to
sort
of
delete
their
repos,
which,
in
the
past,
meant
doing
some
creative
things.
C
We
thought
we
needed
to
do,
and
apparently
changes
in
github
make
it
possible
now
for
us
to
give
maintainers
full
admin
privileges
over
their
projects,
which
has
been
repeatedly
asked
for
by
contrib
maintainers,
without
giving
them
the
the
ability
to
delete
their
repo
entirely,
and
so
we'd
like
to
formalize
that
the
decision
to
sort
of
change
the
way
we're
allocating
permissions
in
the
contrib
projects
and
the
the
detailed
specification
is
in
the
pmc
issue
queue.
C
I
suppose
we
could
put
it
might
not
hurt
to
post.
That's
in
the
backdrop.org
issue
queue
as
well
in
case
people
want
to
comment
on
it.
Jen
does
that
make
sense,
but
in
the
meantime,
we're
going
to
go
ahead
and
vote
on
that.
As
far
as
I
know,
I
haven't
heard
anybody
that
has
real
concerns
about
it.
So
I
expect
it
to
be
a
widely
supported
decision,
but
if
anyone
does
have
feedback
now
is
the
time
to
get
it
in.
A
Yeah
great
tim
yeah,
that's
one
of
those
nice
things
that
the
perfect
solution,
kind
of
landed
in
our
lap
after
lots
of
bad
options,
so
also
kind
of
interesting
that
whenever
we're
working
around
a
limitation
in
github-
and
we
do
something
unusual
in
github-
I
think
that
it's
proving
to
be
a
bad
idea
like.
A
Eventually,
github
will
do
what
we
want
it
to
do,
which
is
nice
that
the
tools
are
improving
all
the
time.
Okay
next
up
is
contributed
project
updates.
A
There
are
only
a
couple
of
new
contributed
modules,
I
shouldn't
say
only
but
taxonomy
access
control
and
the
html5
details
element
are
new
projects
that
were
released
this
week
for
backdrop.
Obviously,
taxonomy
access
control
is
a
widely
known,
drupal
module,
but
it's
great
to
see
that
module
coming
over
into
backdrop.
A
We
don't
have
anything
else,
we'll
move
right
into
the
project.
Update
117.5
is
our
next,
my
or
sorry
bug
fix
release
of
backdrop.
We
have
several
well.
We
have
lots
and
lots
of
minor
issues,
of
course
that
that
we
can
go
through,
but
we
have
several
issues
that
we
like
to
bring
up.
A
One
of
them
is
ongoing
problem
since
backdrop,
117.2
that
the
support
for
mysql8
broke
the
ability
to
use
to
do
database
queries
across
different
databases
and
in
particular
that
affects
civi
crm,
that
it's
recommended
that
you
install
in
a
separate
database
and
backdrop
in
another
database,
and
then
views
is
able
to
query
across
the
two
databases
and
the
change
that
we
had
to
support.
Mysql8
made
it
so
that
querying
across
databases
stopped
working,
and
so
the
issue
is
47.45.
A
There
is
a
pull
request
in
there
that
fixes
the
problem
in
one
solution.
There
is
also
the
suggestion
that
we
adopt
the
drupal
7
patch
for
my
sequel,
8
support.
Instead,
I
feel
ambivalent
about
the
suggestions
there,
but
yeah
I'd
like
I'd
love
to
get
more
feedback
as
to
which
approach
we
should
take.
If
the
the
pull
request.
A
That's
in
there
is
kind
of
a
it's
different
than
the
drupal
7
approach,
but
it
also
will
probably,
I
believe,
have
lower
maintenance
in
the
future
because
it
just
treats
all
tables
the
same
and
the
drupal.
A
triple
seven
approach
has
a
specific
like
allow
list
of
all
of
the
special
keywords
in
all
of
my
sql
eight
and
as
my
sql
a
adds
new
keywords
or
if
we
miss
any
we'll
need
to
continue
maintaining
that
list.
A
The
backdrop
approach
just
quotes
every
table,
rather
than
quoting
just
the
keywords,
so
two
different
approaches
I
expect
both
of
them
will
solve
the
problem,
with
civvy
crm
being
unable
to
query
across
databases,
though
next
up
is
support
for
php8,
php
8
came
out
november
26
and
we
have
an
issue
tracking
this
at
47.72
we
have
a
pull
request,
that's
filed,
it
needs
testing
and
review,
but
joseph
as
the
author
of
the
pull
request.
I'd
love
it.
E
Yeah,
so
I
think
I
have
most
things
working.
It
currently
passes
tests
on
our
test
spot
and
it
mostly
passes
tests
on
my
local.
I
think
I
have
a
problem
because
I'm
running
a
pre-release
version
of
php8.
E
But
the
biggest
change
is
that
they
have
much
stricter
checking
of
method
signatures
when
you
inherit
from
an
abstract
class
or
an
abstract
interface,
and
so
before
there
were
some
scenarios.
Where
that
was
fine
like
you
could
you
could
change
the
default
values,
for
example,
or
you
could
change
what
types
were
type
hinted,
and
then
there
were
other
cases
where
it
showed
warnings.
E
Which
it
affected
us
specifically
because
we're
overwriting
the
query
method
on
the
pdo
object
in
our
database
connections,
and
so
what
I
did
and-
and
this
is
the
same
thing
that
they're
doing
in
drupal,
is
rather
than
extending
pdo,
create
a
pdo
object
that
is
just
stored
in
a
property
and
then
anytime.
You
need
to
run
a
query
or
use
one
of
the
methods
on
that.
You
just
use
it
against
the
object
in
your.
A
D
A
Yeah
that
solution-
I
looked
at
the
pull
request.
It
does
seems
fine.
There
are
some
concerns
about
compatibility,
of
course,
because
things
like
if
we're
not
inheriting
from
the
pdo,
object
anymore,
then
what
methods
are
available
change
because
we
don't
have
the
inherited
methods
anymore.
A
So
I
do
I
do
wonder
if
well
I
wonder
if
drupal
is
going
to
try
to
add
more
compatibility
into
their
object
or
if
it's
like,
just
so
infrequently
used
that
it's
not
a
factor
in
the
first
place.
You
know
those
those
changes
right.
E
A
So
anyway,
that
looks
that
the
pull
request
looks
really
good
like
from
what
I've
seen,
I'm
glad
to
see
that
it
seems
like
it's
it's
working
in
your
experience.
Even
so,
the
tests
aren't
passing,
does
backdrop
itself
seem
to
be.
You
know,
for
the
most
part,
all
functioning
and
run
through
the
installer.
Okay,
things
like
that.
E
A
So
yeah
all
right.
Well,
that's
that's
also
why
we
have
test
coverage
so
yeah.
We
will
need
to
get
all
of
those
things
coming
together.
There's
also,
if
you're
trying
to
get
all
of
the
tests
running
locally,
there's
also
an
issue
for
php
7.4
complete
test
coverage.
A
E
Okay,
yeah,
I
think
I
think
I
just
have
one
issue
remaining
to
run
them
locally
and
it's,
I
think,
that's
that's,
actually
an
issue
with
the
pre-release
of
php8
and
not
actually
an
issue
with
backdrop.
A
C
A
Next
up
is
field
set,
css
issue
4766.
This
is
a
regression
from
some
of
the
previous
changes
that
we
put
into
117.
That
collapsible
field
sets
don't
always
display.
A
Quite
correctly,
we
made
some
improvements,
so
the
field
sets
display
better
when
there's
less
space
available,
but
now
there's
some
other
small
issues
that
have
cropped
up
with
with
field
sets
missing
a
border
on
the
bottom.
It
seems
to
be
the
current
issue,
so
issue
4766
currently
just
needs
pull
requests,
there's
plenty
of
screenshots
demonstrating
what
the
problem
is
in
that
issue.
A
Next,
up
setting
a
reasonable
max
input,
vars
php
variable
38
to
24.,
I
haven't
been
keeping
up
on
this
issue.
There's
been
lots
of
different
approaches
to
it,
but
jen
would
you
be
able
to
give
us
an
update
on
the
max
input,
vars
issue.
B
I
don't
I
haven't
been
following
along
with
it
recently,
but
last
I
looked
at
it.
We've
already
set
the
max
input
bars
variable
in
the
previous
pull
request
that
added
the
missing
variable
set
for
php
7,
so
we
had
been
setting
up
for
five,
but
not
seven
in
the
htaccess
file,
so
that
issue
is
resolved.
So
this
issue
is
really
just
about
warning
people
if
their
site
is
not
fixed
by
the
htaccess
changes
that
are
in
core,
and
so
the
question
is
like
where
and
when
should
we
warn
people
about
the
problem?
B
Last
time
I
worked
on
it,
I
wrote
a
proof
of
concept
that
was
based
on
how
web
form
handled
it,
where
you
count
all
the
number
of
the
elements
in
the
form
and
if
the
number
of
elements
in
the
form
is
within
five
percent
of
the
maximum
number
of
input
bars
on
your
server
it'll,
throw
a
warning
on
the
front
of
the
form
and
if
you
submit
the
form,
it'll,
throw
an
error
saying
that
the
form
probably
didn't
submit
properly
it
also
logs
to
a
watchdog
it
it
that,
stating
that
the
number
of
max
input
bars
has
been
exceeded.
B
There's
also
in
the
pull
request,
a
warning
added
to
your
status
report.
If
your
site
has
the
default
php
value
for
max
input,
vars
instead
of
a
backdrop
safe
value,
but
there's
some
debate
as
to
whether
people
actually
want
to
know
if
their
site
is
exceeding
that
limit,
if
they
haven't
actually
run
into
the
problem.
Yet
so
this
is
sort
of
like
a.
B
B
I
launch
the
site,
but
some
people
say
that
you
know
their
site
hasn't
experienced
the
problem,
so
they
don't
want
to
change
the
value
and
so
having
the
yellow
mark
on
the
status
report
is
going
to
be
an
annoyance,
so
it'd
be
great
to
get
some
more
feedback
from
more
people
as
to
whether
you're,
okay,
with
ignoring
a
warning
on
your
status
report
or
not,
I
don't
have
problems.
I
have
some
sites
where
I
haven't
set
the
allowed
host
patterns
or
whatever
it
is,
and
it
doesn't
bother
me
but
yeah.
B
Over
oh,
he
got
a
phone
call.
Okay,
let's
see
next
up
is
the
views
or
fix,
looks
like
the
pull
request
needs
to
be
worked
on
for
that.
So
this
is
a
long-standing
issue
where,
quite
a
while
ago,
there
was
an
update
to
views
that
broke
the
or
filters.
B
This
was
an
attempt
to
fix
them.
The
fix
that
went
into
view
since
then
doesn't
actually
fix
this
problem.
So
it's
sort
of
been
a
long-standing
issue
for
drupal
as
well.
A
Sorry
I
got
a
phone
call
right
in
the
right
just
then,
and
I
had
to
drop
off
and
then
come
back,
but
I
can
pick
these
back
up
jen
if
you're.
Okay,
with
that.
B
A
Yeah
lauren
tested
it
out
and
said
that
the
sandbox
isn't
working
anymore
on
that
issue
for
testing.
It
might
be
a
good
idea
to
rebase
that
against
one.x
and
then
and
then
push
up
and
update
just
so
that
we
get
a
new
sandbox,
that's
built
on
tugboat,
okay,
the
rest
of
these
issues
that
we
have
in
the
agenda.
They
don't
have
updates.
So
we
can
skip
over
those
sections,
so
we
can
move
right
into
118..
A
Do
you
guys
have
any
other
117
issues?
You
guys
would
like
to
talk
about
before
we
proceed?
Okay,
so
118
118
is
the
next
minor
version
of
backdrop.
It
will
be
coming
out
january
15th,
like
tim
mentioned
at
the
beginning
of
the
call.
That
means
we
have
basically
one
month
before
feature
freeze
which
is
on
january
1st
and
yeah.
So
we
have
to
have
this
month
to
get
some
of
these
things
put
together.
A
Let's
see,
first
up
webp
support.
That's
a
new
image
format
that
is
a
replacement
for
jpegs
issue.
4509
indigozala
is
the
advocate
for
this
issue
and
it
moved
into
our
tbc
this
week
so
very
exciting.
I
haven't
taken
a
look
at
this
in
a
couple
of
weeks,
but
yeah.
That's
that's,
really
exciting
news
to
see
that
move
into
final
status,
let's
see
menu
block,
add
a
setting
for
changing
the
break
point
of
which
it
switches
into
hamburger
mode
issue.
4663
bw
panda
is
the
advocate
for
this
no
update
since
last
week.
A
If
anyone
else
has
has
an
opportunity
to
look
at
it,
there's
some
technical
problems
in
32
93
that
just
need
some
knowledge.
People
knowledgeable
in
the
ajax
system
to
help
assist
in
that
that
issue,
and
I
will
try
to
look
at
it
as
always,
but
you
know
it's
been
busy
so
so
I
wish
I
had
better
updates
there,
but
still
still
pending
on
a
stuck
technical
problem.
A
A
C
We
had
a
good
discussion
about
this
a
few
weeks
ago
and
I
finally
got
a
chance
to
sort
of
look
it
over
and
make
a
few
changes.
There's
so
there's
two
questions.
I
have
about
the
pull
request.
C
One
of
them
is
that
this
well,
I
got
the
tests
working,
but
I
I
got
the
tests
working
by
just
changing
them
to
test
raw
html
instead
of
full
html,
which
made
me
realize
that
if
I
don't
know
if,
if
anybody
uses
these
same
tests
on
existing
sites,
but
if
you
were
to
run
the
tests
on
an
existing
site,
these
tests
would
fail
because
they
would
still
be
an
existing
site,
would
still
be
using
the
full
html
format.
C
And
I
don't
know
if
that's
an
issue
or
not
gregory
commented
that
he
thought.
Maybe
that
wasn't
an
issue
that
it's
not
ideal,
but
it's
maybe,
okay.
What
do
you
think
nate.
A
So
an
interesting
thing
about
the
test
is
that
the
tests
don't
run
on
the
site
as
they're
installed.
The
tests
make
a
fresh
installed
backdrop
every
single
time,
they're
run,
and
so
it
doesn't
if
they
were
to
run
those
tests
on
their
own
site,
they
would
reinstall
backdrop
and
they
would
continue
to
work
with
the
new
format
as
we
renamed
it.
There
is
the
problem,
however,
of
any
contrib
modules
or
anything
that's
out
there
that
uses
the
default
profile
or
sorry.
The
standard
profile.
D
C
A
Yeah,
so
so
so,
where
does
that
leave
us
yeah?
I
I
don't
know
we
don't
have
a
there's,
not
a
real,
clear
line
there,
because
it's
not
backwards
compatibility
that
would
affect
anyone,
but
it's
backwards.
A
E
A
Yeah,
any
any
test
that
say
creates
a
sample
piece
of
content
that
uses
a
text
area
field
might
specify
the
text
format
as
being
full
html
in
their
own
tests.
So
it's
not
testing
of
the
standard
profile.
It
just
happens
to
be
a
test
that
uses
the
standard
profile,
which
is
the
default.
If
you
don't
specify
anything
else,
so
I
think
that
there's
a
good
chance
that
a
lot
of
tests
are
out
there
are
going
to
assume
that
full
hdl.
C
I
was
going
to
say
that
one
of
the
things
gregory
pointed
out
is
that
as
people
can
delete-
or
currently
I
think,
they're
still
able
to
delete
or
maybe
they're
not,
but
you
could
change
the
name
of
a
format
anyways.
C
A
C
C
A
Yeah
and
and
so
yeah
I,
as
I'm
saying
this
out
loud,
I'm
thinking
that
changing
the
machine
name
is
probably
not
a
good
idea.
I
I
would
like
to
have
it
be
the
same
as
you
know,
as
the
label,
but
I
think
doc.
Wilmot
said
the
same
thing
that,
like
changing
the
machine
name,
might
be
an
api
break
that
needs.
C
A
C
Doc,
back
wilbon
had
kind
of
a
strong
feeling
about
that,
although
he
didn't
explain
why.
So
I
wasn't
sure
if
maybe
we
had
addressed
his
concern.
I
think
jay
franklin
had
also
sort
of
questioned
whether
it
was
a
good
idea
but
anyways,
okay.
C
C
I'm
not
sure
what
that's
doing
so.
I
just
wanted
to
be
sure,
I'm
looking
for
it
right
now.
The
core
dot,
slash
module,
filter,
slash,
filter,
api.php.
We
had.
We
had
said
that
the
only
thing
we
were
changing
was
the
install
profile
and
the
tests,
and
so
that
we
didn't
think
there
were
going
to
be
a
problem
with
either
of
these
things,
and
then
I
noticed
that
I'm
also
changing
this
thing
in
the
filters
module.
Is
that
a
problem?
Well.
C
A
D
A
You
usually
inside
of
there
we
even
use
like
stuff
that
isn't
even
real
but
a
lot
of
times.
It's
easiest
just
to
copy
and
paste
an
actual
example,
and
so,
if
it's
referencing
full
html
in
there,
then.
C
A
Filter.Theme,
I
don't
know
what
that
one
is.
That
sounds
like
it
would
be,
something
that
contains
theme,
functions
or
preprocess
functions.
C
C
A
A
The
label
and
the
machine
name
don't
line
up.
I
don't
I
don't
know
what
the
trade-off
is
there.
You
know
whether
or
not
it's
it's
better
to
have
a
more
descriptive
label
or
whether
it's
better
to
have
the
machine
name
and
the
and
the
label
line
up
like
that
seems.
Like
a
you
know,
toss-up
decision.
C
Well,
I
mean
another
question
to
ask:
is
how
how
nice,
what
the
value
of
this
change
is.
I
think
for
most
of
us
that
have
gotten
used
to
backdrops
we've
gotten
used
to
this
problem,
but
to
me
it
was.
It
was
very
confusing
at
first,
and
so
you
know
I
I
hold
on
to
the
fact
that
I
think
it
would
be.
C
A
B
C
B
I
think
we
would
still
get
a
benefit
for
doing
it,
because,
most
of
the
time
people
are
going
to
be
seeing
the
user
interface
and
very
rarely
are
they
going
to
be
using
the
code
side
of
it.
I
would
guess,
but
my
preference
will
be
to
change
both
I'm.
I
heard
the
part
where
everything
was
fine
and
I
missed
the
part
where
this
was
a
problem.
C
So
we
decided
it
was
a
problem
because
people
may
have
written
tests
and
contrib
modules
that
use
the
machine
names
and
we
would
potentially
be
breaking
tests
in
control.
A
We
I
mean
we
could
also
inventory
watson,
can
trip
right
now
and
see
if
there
actually
are
problems
in
contrib
and
there's
no
way
that
we
can
know
about
people
that
have
custom
modules.
But
I
think
writing
simple
tests
against
custom
modules
is
not
a
common
situation.
Usual.
Usually
people
build
integration
testing
to
make
sure
their
whole
site
works
together.
You
know
like
using
the
hat
or
something
like
that.
It's
pretty
uncommon
to
use
you
know,
install
your
site
from
scratch
and
then
run
simple
tests
on
it.
A
That
doesn't
just
doesn't
make
sense
for
product
sites
for
custom
modules.
So
if
you
want
to
inventory
contrib
and
see
if
it,
if
it's
a
problem
at
all,
then
maybe
that
will
help
us
inform
if
we
can
rename
it.
E
A
Okay,
well,
joseph.
The
next
issue
is
the
advanced
caching
issue.
I
know
you
are
working
on
porting,
the
capability
of
hashtags
and
cash
max
age
being
variable
based
on.
What's
on
the
page,
the
issue
is
41.27
all.
E
E
Okay,
so
what
I've
done
at
this
point
is,
I
have
ported
the
the
d8
cache
module
and
that
is
in
that's
on
one
of
my
personal
repositories.
At
the
moment,
it
I
believe,
is
all
working,
except
that
I
need
to
change
how
I'm
handling
emitting
the
block
cache
tags,
because
our
block
system
is
totally
different
from
drupal
7's
blog
system.
E
However,
I
don't
know
if
we
can
include
this
in
a
core
in
its
current
state
because
of
the
change
in
php
8,
where
it's
stricter
about
method
signatures
all
of
the
function,
all
of
the
functions
on
the
on
the
da
cache
modules,
cache
interface
change,
the
like
they
add
the
two
new
things
that
you
need
to
pass
into
all
the
functions,
so
I
haven't
tested
that
yet
on
my
computer,
that's
running
php
8,
but
I
think
that
that
will
have
lots
of
problems.
A
In
that
case,
I
mean,
if
we're
just
adding
two
parameters,
because
this
is
in
theory,
going
to
be
a
core
enhancement.
Couldn't
we
just
add
the
two
parameters
to
all
of
the
parent
classes
as
well.
A
E
A
A
A
A
Thank
you,
okay!
Well,
that's
it
for
the
118
updates.
Let's
see,
I
think
we
also-
probably,
let's
see
tim,
you
already
have
some
items
in
or
a
note
in
here
on
telemetry
the
initiative
that
it
doesn't
look
like.
There's
any
updates
this
week.
Is
that
correct?
Okay?
Well,
maybe
because
we're
kind
of
running
up
against
the
top
of
the
hour,
we'll
just
say:
okay,
that's
it
for
that.
We
do
also
have
some
general
discussion
items
that
herb
herb.
A
Dual
wants
to
have
us
brainstorm
a
little
bit
on
providing
an
advanced
and
provide
an
advanced
admin
option
to
skip
deleting
of
config
staging
files
after
config
sync,
the
issue
is
4447.
A
Yes,
I
think
it's
a
great
idea
honestly,
because
for
people
that
manage
both
their
staging
and
their
live
directories
in
config
or
sorry
in
inversion
control,
it
disrupts
the
version
control
every
time
it
it
backed
up,
deletes.
What's
in
the
staging
directory,
then
now
your
your
git
history
gets
out
of
date,
and
so,
if
you
try
to
restore
it,
then
the
config
sync
tries
to
run
again
or
tries
to
show
you
differences
a
second
time
yeah.
I.
A
I
definitely
think
that
we
should
support
not
deleting
the
the
configuration
out
of
the
staging
directory
directory.
I
would
might
even
say
that
that
should
be
the
default
behavior
for
new
sites
as
we
move
forward,
but
I
think
we
can
like
kind
of
see
how
this
shapes
up
and
how
much,
how
the
the
difference
in
behavior
leaving
the
files
there
versus
not
leaving
them
there
and
then
yeah.
A
We
can
discuss
the
merits,
but
I've
I've
definitely
found
it
to
be
an
annoyance
that
those
files
get
deleted
when
I'm
using
version
control
at
the
same
time.
Jen
do
you
have
any
comments.
A
I
think
that's
that's
really
kind
of
all
there
is
to
discuss
on
that
one.
I
think.
That's
all
that
he
was
asking
for
I'll.
Try
I'll
leave
this
tab,
open
and
post
a
comment
and
jim
I'm
guessing.
You
may
have
added
this
item
about
sprints
or
blog
posts
to
promote
contribution
during
the
last
four
weeks
before
future
priests.
C
Yeah,
I
I'm
always
like
to
schedule
a
sprint
or
two
if
anybody's
interested
they
should.
Let
me
know
I
still
have
the
wednesday
afternoon
office
hours,
which
I
don't
know
if
I
added
or
if
it's
part
of
it,
that's
it
also
says
sprinting
and
we
could
use
some
of
those
times,
but
if
anybody's
interested
in
doing
planning
some
other
weekend
or
weekday
sprints
leading
up
to
that,
the
other
thing
is,
I
just
wanted
some
quick
feedback
on.
C
C
C
I'll
try
and
find
a
link
to
the
the
blog
post.
I
did
last
time
and
share
it
and
zoom
up.
A
Yeah
and
didn't
last
time
we
had
that
last
sprint
on
a
weekend.
I
think
yeah
we
did.
I
know
for
me
it's
the
case,
and
it
might
be
the
case
for
other
people
at
weekends
can
be
better
availability.
A
C
A
It
I
kind
of
feel
like
the
the
last
week
before
freeze
is
the
most
effective
one,
just
because
people
really
want
to
finish
at
the
last
minute,
but
I
feel
like
it's
a
healthier
thing
to
try
to
do
it
a
little
bit
sooner
so
so
maybe
we
could
try.
Both
I
don't
know
is
that
that
seem
like
stretching
too
much
like
do
one
in
like
a
week
and
then
do
another
one
right
before
the
end.
C
I'm
up
for
that
and
let's,
let's
just
do
it,
let's
just
put
him
on
the
schedule.
I
I
think
I'm
I
would
be
able
to
attend
both
and
I'm
always
of
the
opinion
that,
like
if
I
block
off
a
few
hours
to
sprint
and
no
one
comes,
I
haven't
lost
anything.
A
Yeah,
it
might
also
be
good.
I
wasn't
planning
on
bringing
it
up
this
meeting,
but
since
we're
talking
about
feature
freeze
already,
you
know
we
always
have
the
fun
like
when
is
feature
freeze
really
going
to
happen
discussion,
because,
for
whatever
reason
like
these
things,
always
land
on
holidays-
and
I
mean
it's-
I
guess
it's
the
nature
of
our
release
schedule
that
january
1st
is
a
holiday.
You
know
like,
and
that's
also
the
day
that
we
have
feature
freeze
today,
january
1st
or
this
year
next
year.
A
A
So,
okay,
do
you
guys
have
any
thoughts
on
that?
Like
that?
That's
if
we
follow
our
current
patterns,
that's
what
it
would
end
up
being,
and
I
don't
know
if
we
need
to
officially
sanction
that
or
not.
C
It
would
be
a
it
might
be
helpful
to
not
like
have
that
final
sprint
on
the
first,
which
is
a
holiday
if
we
have
the
option
of
doing
it.
The
day
after
or
two
days
after
on
sunday.
C
C
A
Yeah,
well
maybe,
let's
put
like
come
back
to
that.
I
think
that
that's
likely
to
happen,
because
that's
what
we've
done
in
years
past,
but
yeah,
we'll
kind
of
leave
that
decision,
I
think,
but
let's,
let's
wrap
up
for
today,
we're
we're
after
time
and
yeah.
A
Thank
you
everybody
for
for
joining
the
meeting,
thanks
for
the
great
discussions,
joseph
thanks
for
the
great
work
on
php
8
and
the
advanced
caching
stuff
yeah,
and
thanks
to
all
of
our
contributors
out
there,
making
new
contrib
modules
working
on
new
pull
requests.
Moving
these
issues
forward.
We
appreciate
all
of
the
work.
You
guys
do
to
make
backdrop
better.