►
From YouTube: 2021/12/23 - Backdrop Weekly Dev Meeting
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
are
live
today
is
thursday
december
23rd
most
places.
This
is
our
weekly
developer
check-in
meeting
for
backdrop
cms.
Before
we
get
into
the
agenda,
we
should
go
around
them
and
do
some
quick
introductions.
If
you
can
share
what
your
name
is
where
you're
from
and
something
else
you'd
like
to
share
with
us.
That's
not
in
our
agenda.
A
We
can
go
around
pop
popcorning
through
it,
I'm
happy
to
go
first.
My
name
is
jen
lampton
joining
from
oakland
california.
I
have
a
soft
warm
cat
on
my
desk,
which
is
pretty
exciting
every
time
I
go
to
touch
the
mouse
to
move
it.
He
flicks
his
foot
because
he
doesn't
like
it
when
I
touch
it,
it's
my
adventures
today,
let's
see
tim,
do
you
want
to
go
next.
B
C
Robert
lang
folder
on
the
internet,
from
coming
to
you
from
altadena
california,
where
it
is
raining
but
not
so
hard,
is
to
create
flash
floods
like
we
had
last
week.
D
Hi,
I'm
greg
I'm
joining
from
greece.
The
weather
is
floating
with
the
minus
degrees,
but
I
don't
see
it
snowing.
We're
not
gonna
have
a
white
christmas,
hoping
for
it
still
interested
in
general
about
anything
related
with
to
backdrop,
in
any
way
that
I
can
help
I'll
pass
it
on
to
wilbur.
C
C
B
E
Yep
peter
anderson.
F
Hi,
I'm
peter
from
australia
just
checking
in
and
seeing
what's
up.
A
Thanks
everybody
before
we
get
into
backdrop
core
status,
I
just
want
to
do
a
couple
quick
updates.
We
had
a
lot
of
new
contributed
projects
in
the
last
week,
which
is
kind
of
exciting.
We
have
github
labels,
which
is
a
new
module
duo,
barrel
roll
which
is
a
module
that
was
ported
from
drupal
password
list,
which
I
think
is
also
a
module
ported
from
drupal
and
email
confirm.
A
I
think
I'll
support
it
from
triple.
I
didn't
check
on
that
one,
and
then
we
have
a
new
one
for
backdrop
for
mini
layouts,
which
is
really
excited
really
exciting
for
me,
because
I
have
been
wanting
to
work
on
that
for
a
really
long
time
and
not
had
time
to
do
it
and
now
someone
else
has
done
it,
and
now
I
get
to
go
use
it,
which
is
the
best.
So
I
love
it
when
something
you
want
to
happen
happens
and
then
you
get
the
benefit
of
it.
A
I've
got
to
figure
out
how
to
help,
but
it's
pretty
exciting
for
the
general
discussion.
This
week
we
have
indigozella
reminding
us
that
jquery
update
came
out
with
a
new
version
recently
and
we
need
to
update
backdrop
core
our
issue
number
for
that
in
the
queue
is
54.01
and
it
looks
like
there's
been
a
lot
of
progress
on
that.
There
is
both
a
pull
request
that
needs
a
code
review
and
manual
testing
on
there.
A
I
do
think
that
jquery
sorry,
this
is
jquery
ui,
not
jquery
itself,
I'm
not
sure
if
I
said
that
incorrectly
last
time
we
use
jquery
ui
a
lot
of
places
in
core.
It
manages
a
lot
of
our
interface
widgets,
so
we're
going
to
need
to
do
some
pretty
extensive
testing
on
all
the
little
bells
and
whistles
on
our
forms.
Things
like
date,
pickers
and
stuff
like
that
to
make
sure
that
everything
is
still
working
as
it
did
before.
B
A
C
Are
we
keeping
track
of
those
items
in
that?
Is
that
a
meta
ticket
for
keeping
track
of
all
those
places.
A
It's
not,
I
don't
see
a
clear
like
a
bullet
list
of
stuff
to
test,
but
there
are
like
a
bunch
of
comments.
That's
like
oh,
auto,
complete
and
then
there's
a
mention
of
how
autocomplete
was
tested.
So
it's
sort
of
scattered.
We
could
do
with
a
summary
update
that
could
make
it
a
little
better
color
color.
C
D
And-
and
the
same
goes
with
when
we
update
cked
here,
there's
a
bunch
of
things
that
we
need
to
test
and
then
some
people
do
that
our
memory,
but
it
would
be
great
to
have
these
bullet
points
before
it
needs
to
be
tested.
A
On
the
parent
issue,
there
is
a
list
of
things
to
test
specifically
for
jquery,
so
I'm
not
sure
if
this
covers
everything
in
ui,
but
we
we
should
make
sure
that
list
ends
in
a
more
question
mark.
So
we
should
make
sure
that
that
list
gets
updated
too,
with
everything
we
find
in
this
issue.
C
As
I
look
at
the
ticket,
there's
already
a
meta
issue
about
this
two
four
come
on.
G
Sure
I'm
gonna
share
my
screen.
G
Okay,
oh
so
march
this
year
I
was
showing
I
did
a
presentation
where
I
showed
off
the
basically
tools
I
used
for
performance
monitoring
and
nate
had
the
idea
of
including
these
in
our
tugboat
sandboxes
or
yeah
sandboxes,
and
to
be
able
to
see
like
how
long
everything
takes
and
find
problems
if
there
are
any
and
then
there's
also
a
module
for
drupal
8
called
web
profiler,
which
gives
you
a
lot
of
information
into
like
how
the
page
was
generated
and
provides
a
little
toolbar
at
the
bottom,
with
different
steps,
and
I
have
been
working
on
a
contrib
module.
G
I
haven't
posted
it
up
yet
because
it's
so
it
doesn't
really
work
100,
but
you
essentially
just
drop
it
in
and
enable
it.
And
if
you
have
the
xh
profit
extension
installed,
it'll
collect
all
that
data
and
it'll
display
like
execution
time
and
different
stats,
that
it
collects
from
backdrop
and
you
can
go
in
and
it'll
sound.
B
G
D
Joseph
you
mentioned
something
about
the
demos:
were
you
referring
to
the
ones
that
we
do
follow?
Pull
requests
as
in
automatically
looking
for
regressions,
as
in
okay,.
D
Because
you
wouldn't,
you
would
need
a
reference
like
the
baseline,
so
just
to
distinguish
if
we're
having
regressions
right,
all
right
cool
but
but
but
I
can
see
how
the
the
contrib
module
will
be
beneficial
for
people.
You
know,
building
new
sites
and
trying
to
optimize
things.
Thanks
really
awesome.
Yeah.
G
A
I
think
it
could
be
really
useful
too,
like
even
if
we
don't
have
a
baseline
on
the
page
for
a
particular
sandbox
site,
just
seeing
them
all
the
time
we
would
sort
of
all
have
a
good
idea
of
what
a
normal
response
looks
like
and
then,
if
you
get
one,
that's
a
major
outlier
be
like.
Oh
that's
not
what
that
picture
usually
looks
like
and
you'd
be
able
to
reference.
The.
F
G
A
G
Big,
a
big
advan,
a
big
advantage.
This
has
some
most
of
the
tools
that
are
available
out.
There
require
a
lot
of
setup
and
like
external
services-
and
this
is
just
it's
just
a
module-
you
drop
it
in
your
site
and
it
shows
you
the
data,
that's
great.
A
All
right
so
looking
at
upcoming
releases
for
activecore,
the
next
bug
fix
release
is
going
to
be
version
124,
and
we
have
a
handful
of
issues
that
we're
working
on
for
that
there's
one
here
in
the
agenda
number
5245,
which
is
adding
php
code
standard
checking,
which
is
pretty
cool.
This
has
a
pull.
A
I
think
my
last
time
I
heard
nate
talk
about
it.
He
said
it
was
pretty
close
and
he
was
really
excited
about
it,
but
there
might
have
been
some
decisions
we
need
to
make
about
how
to
handle
all
of
the
current
code.
I
don't
know
if
anyone's
heard
anything
about
that
recently.
D
The
only
thing
that
we
were
working
on
was
the
implementation,
as
in
have
it
run
for
our
pull
requests,
but
only
check
the
portions
that
we're
changing
instead
of
the
entire
code
base.
So
we
don't
have.
You
know,
lists
of
failures
all
over
the
code
base
and
I
think
that
nicosella
figured
that
out
so.
A
I
don't
have
a
look
at
it
and
then
there's
no
other
issues
that
are
specifically
indicated
for
the
bug
fix
milestone,
but
that
of
course
does
not
mean
that
we
don't
have
bug
fix
issues
so
in.
A
The
github
queue
you
can
look
for
any
issue
with
type
equals
bug
or
you
can
look
in
the
124
milestone
and
there
are
handfuls
of
issues
that
are
probably
pretty
close
to
getting
resolved.
There
are
some
that
are
really
complicated
plenty
of
bugs
to
go
around
if
people
want
to
work
on
bugs
more
excitingly.
Our
new
feature
milestone.
120
zero
is
right
around
the
corner.
Someone
mentioned
before
the
recording
started
that
we
have
a
week
before
feature
freeze,
so
this
year
we're
gonna
extend
future
freeze
to.
A
In
in
north
america,
anyway,
it's
sunday
january
2nd,
because
the
first
falls
on
a
saturday
and
we
usually
like
to
do
sprinting
over
the
weekend
and
try
and
get
as
much
as
we
can
in
before
that
date
and
then
once
feature.
Freeze
is
closed.
We
have
about
two
weeks
to
clean
up
any
issues
in
those
new
features,
so
we
will
all
start
testing
like
crazy
and
try
and
get
that
cleaned
up
before
release
on
the
15th.
A
Thank
you
so
for
120.
A
A
There's
one
issue
on
our
agenda
to
talk
about
today,
and
that
is
issue
number
5044..
This
is
to
add
a
custom
css
class
to
regions
in
the
flexible
template
user
interface.
It
looks
like
this
issue
is
pretty
close,
but
it
does
not
have
an
advocate,
so
I
would
say
if
anyone
is
really
passionate
about
this
issue,
you
can
sign
up
to
be
its
advocate
and
that
will
help
move
it
closer
to
core
conclusion.
A
There's
a
note
here,
greg
that
says
you're
working
on
a
different
issue,
but
that
one's
not
on
our
agenda.
For
today
I
didn't
know
if
that
was
something
you
wanted
to
talk
about
or
not
entity,
identity
view
decor.
D
Yeah,
I
think
that
herb
is
advocating
for
that,
I'm
not
sure
or
maybe.
B
As
as
I
mentioned
last
week,
the
problem
is:
is
that
herb
is
there's
two
different
issues?
One
is
adding
automatic
classes
to
good
layouts
and
one
is
adding
custom
classes
and
I
think
herb
has
pull
requests
for
both
and
it's
a
little
bit
unclear
like
which
one
he's
advocating
for
more
or
more
actively
or
first
or
whether
they
he
wants
them
both
or
I
don't
know
so.
I
haven't
looked
he
if
he's
updated,
that
in
the
last
week.
A
B
Actually,
there's
another
one
about
adding
ids
in
the
issue
field
and
greg
was
supposed
to
be
working
on
on
that
one.
But
then
I
think
he's
working
on
something
else.
Right
now,
but
again,
I
I'm
a
little
bit
concerned
that
these
three,
the
adding
ids
to
templates
the
adding
automatic
classes
to
to
templates
and
adding
custom
classes
that
the
fact
that
that
the
fact
that
all
of
them
impact
each
other
but
they're
having
three
different
discussions
is
kind
of
holding
them
up.
B
Like
you
know,
greg
has
said
like
he
doesn't
want
to
work
on
the
id
one
right
now,
because
there's
work
going
on
in
the
classes
and
the
classes
ones
like
there's
some
people
who
want
one
and
some
people
who
want
the
other
and
they're
and
they've
all
kind
of
stalled.
Because
of
that,
I
think.
A
I
don't
know
so
issue.
5032
currently
looks
like
it's
identical
to
issue
5044
by
the
title
and
the
description,
so
that
could
be
causing
some
confusion.
They
both
seem
to
be
wanting
to
add
an
additional
custom
class,
and
then
there
is
issue.
D
A
B
B
C
D
A
A
B
B
so
identical
no,
because
the
first
one
is
automatically
adding
the
names
of
regions
and
remember
again,
that
was
the
one
where
there
was
consensus
on
automatically
adding
stuff,
but
herb
wants
to
add
custom
ones.
So
there's
a
custom
field
and
we
broke
those
out.
So
there
are
two
different
issues.
Now:
okay,.
B
A
A
B
H
B
Let's
check
zulu
and
see
if
herb
is
updating
us
yeah
he's
just.
He
said
he
needs
feedback
on
whether
purple
people
prefer
54
44
on
its
own
or
with
50
32.
D
B
B
50
44
was
a
little
bit
controversial,
but
I
don't
know
if
that's
still
the
case,
so
it
could
be
that
there's
sufficient
consensus
now
to
do
both
and
genuine
or
where
somebody
was
a
little
bit
pushing
against
the
custom,
and
I
don't
know
if
you've
changed
your
opinion.
A
No,
I
still
do
not
like
5044.
My
perspective
is
just
that
the
layout
user
interface
is
already
very
complicated.
A
Adding
another
text
field
to
every
region
adds
a
lot
of
clutter
to
the
page
which
instinctively,
if
you
show
someone
a
cluttered
form,
even
if
it's
not
hard
to
use,
there's
like
a
psychological
impact
of
that,
then
think
I'm
thinking
that
it's
harder
to
use
than
it
might
actually
be,
and
because
this
isn't
something
that
people
will
necessarily
need
if
we
can
add
automatic
classes
in
there,
I'd
rather
give
them
a
tool
that
you
know
some
that
doesn't
require
a
user
interface
change
that
they
can
use
for
the
same
thing,
and
I
think
that
if
people
do
want
custom
classes
like
there,
I
believe
people
will
want
this
feature.
A
It
could
go
in
core.
It
could
go
sorry
in
contrib,
perhaps
in
a
module
that
lets,
you
add
glasses,
to
lots
of
other
things
that
might
not
only
be
flexible
layout
templates.
I
don't
know
if
we
have
one
of
those
yet,
but
it
could
be
like
I'll.
B
Just
if
you
haven't
looked
at
the
second
pull
request
later,
I
recommend
you
do
that
because
herb
has
put
it's
a
little
check
box
now
that
just
says
so
right
now,
all
you
see
is
a
check
box.
That
says,
add
custom
classes
you
check
on
that,
and
then
you
would
see
the
field
so
at
least
take
a
look
at
that
just
to
see
how
it
is.
A
D
A
Would
I
prefer
that
we
give
people
the
tool
they
need
that
doesn't
provide
any
user
interface
that
we
have
to
maintain
rather
than
giving
something
they
want
and
have
to
use
if
they
need
it,
because
we
didn't
give
them
what
they
needed.
It
just
seems
like
it
might
be
an
easier
way.
H
D
D
D
B
Nodes:
okay,
yes,
we're
short
of
time-
and
I
want-
and
we've
spent
a
lot
of
time
in
meetings
talking
about
this.
So
what
my
quick
update
would
be
that
I
think
we're
really
close
on
a
lot
of
things:
I'm
not
getting
much
feedback
on
the
actual
text,
which
I
thought
there
would
be
more
discussion
of,
but
I
think
there's
still
time
for
people
to
give
feedback
on
the
specific
text.
The
discussion
right
now
is
one
around
we've.
B
Olaf
gave
us
six
great
options
for
images
to
include
in
our
new
nodes
and
we're
debating
or
discussing
which
of
those
to
do.
Olaf
seems
to
think-
and
I
think,
he's
right
that
we've
probably
narrowed
it
down
to
two
of
those
options
and
if
people
have
opinions
on
which
of
those
two,
they
should
chime.
In
the
other
thing,
though,
that
this
is
where
I'd
like
some
feedback
in
this
meeting
is
another
discussions
that
started
happening
in
on
the
pr
discussion
is
doc.
B
Wilmont
has
pointed
out
we're
currently
our
three
pageless
nodes
on
the
front
page
are
a
view,
and
originally
the
view
was
just
sorted
by
bait
created,
but
I
found
on
the
tugboat.
It
wasn't
lining
up
the
way
I
expected,
and
as
far
as
I
can
tell
talk
about,
maybe
creating
all
three
of
those
nodes
at
exactly
the
same
time.
So
sorting
them
by
date
created
does
means
that
we
don't
know
which
direction
they're
going
to
go
and
that
triggered
a
discussion
about.
B
Well,
maybe
we
just
added
an
order
field
so
that
people
can
manually
sort
them
and
then
doc
wilbon
pointed
out,
which
I
think
is
true,
that
the
the
best
you
or
the
most
usable
use
case
for
end
users
would
be
if
these
were
actually
just
existing
content
blocks
and
not
a
view
at
all
and
the
reason
which
I
think
he's
right
about,
but
part
of
the
reason
we
used
to
view
was.
We
were
looking
for
a
way
to
showcase
views
on
the
front
page,
so
one
I
think
we
could.
B
I
mean
I
agree
with
doc
wilmot
that
having
existing
content
blocks
would
be
sort
of
easier
for
the
end
user,
but
then
or
we
should.
We
just
forget
about
the
showcasing
views
for
now
and
deal
with
that
later
in
another
way
and
all
but
also
there's
another
issue,
which
is
if
we
did
do
existing
content
blocks.
B
A
I
think,
especially
now
it's
too
late
to
possibly
catch
all
the
unattended
effects
of
making
a
change
to
the
homepage
layout.
I
don't
think
we
can
change
the
layout
itself.
We
can't
change
boxed
and
add
new
regions.
That
would
be
actually
technically
possible
without
a
lot
of
ramifications,
but
we
could
change
the
layout
that
was
in
use
on
the
home
page
for
fresh
install.
So
we
could
choose
a
different
layout
out
of
the
box.
That
would
be
an
option
not
touch
existing
sites.
A
But
yeah
I
mean,
I
think
on
also
another
reason
that
we
chose
to
do
interview
is
because
we
sort
of
sidestepped
this
issue
where
like,
if
we
can
put
it
in
a
view,
we
can
put
a
single
block
in
a
column
and
we
don't
need
to
worry
about
the
layout
problems.
I
don't
know
if
that's
the
best
solution
to
the
problem,
but
it
was
part
of
the
reasons
we
landed
on
the
view.
B
I
I
agree
100,
then
yeah,
but
there
were
the
two
main
reasons
for
one
to
avoid
the
decision
about
layouts
and
two,
because
we
did
want
to
showcase
views.
I
had
also
I
I
had
suggested
changing
the
layout
and
adding
more
posts,
but
then
people
looked
at
three
existing
content
blocks
and
two
posts
and
they
said
that's
too
much
content
and
they
wanted
to
get
rid
of
the
extra
posts.
So
then
that
left
us
with
only
one
place
to
showcase
views
anyways.
B
B
It
is
absolutely
clear
that
some
of
the
concur
contrib
themes
just
will
break
on
the
home
page
with
this
change
either
way
we
go
now
like
indigozella
is
one
of
the
contrib
maintainers
that
this
would
be
affected
by
and
her
position
is
that
that's
she
understands
that
would
just
want
to
update
her
themes
so,
and
I
think
that
that's
a
reasonable
position
is
that
you
know
if
we
gave
people
an
opportunity
to
upgrade
their
contributions
and
maybe
help
identify
those
that
have
problems
fixing
it
probably
isn't
too
hard.
B
But
how
much
time
do
we
need
to
allow
for
that
like?
Is
it
fair
to
to
push
this
in
and
not
give
contrib
themed
authors,
and
this
is
going
to
affect
either
way?
So,
even
if
we
leave
it
as
it
currently
is
contrib
some
of
the
contrib
themes
need
time
to
update.
B
I'm
just
thinking
about
giving
them
more
time,
but
it's
not
clear
to
me.
We
need
to
that's
I'm
asking
if
people
have
input
on
that
so
yeah
you
know,
will
three
months
be
better
than
two
weeks
and
I
don't
know
I
I
think
india
goes.
Ella
would
probably
argue
that
she
could
get
this
done
and
it's
for
her
things
and.
A
B
B
All
right-
and
you
know,
we've
only
got
about
20
contributions,
so
it's
not
like
unmanageable,
but
the
question
is
you
know
I
I'm
okay
with
us,
releasing
it
part
of
one
two
one,
but
I
just
wanted
to
raise
that
issue
and
give
people
a
chance
to
object
or
offer
alternatives.
B
Silence
peter
peter,
you
might
have
some
contrib
themes.
G
B
Exactly
but
the
day
after
this,
if
somebody
were
to
download
the
new
install,
you
know
the
the
new
site
and
then
add
a
contrib
theme,
some
of
the
concrete
things
would
look
pretty
bad
so,
but
they
again
they
can
fix.
You
know,
like
indigozella,
said
she.
She
just
wants
a
little
enough
notice
or
enough
time
to
fix
her
teams.
C
You
know,
I
think,
if
we
add
this
to
the
next
release
candidate,
we
could
have
as
part
of
that
meta
issue.
That
would
be,
you
know,
go
in
and
check
existing
themes
and
make
a
checklist
and
check
in
with
the
authors
of
those
and
see
if
we
can
get
those
updated
and
have
them
issue
a
release.
When
you
know
with
the
new
dated
core
compatibility
note.
A
I
think
that
you
know
my
initial
instinct
was
like
well,
let's
we're
so
close.
Let's
get
it
done,
but
tim
now
that
I
know
that
you're
willing
to
do
the
legwork
of
reaching
out
to
the
maintainers
to
all
the
themes
and
letting
them
know
that
this
is
coming
and
that
they
can
adapt
for
it.
I
think
you
know,
maybe
what
we
should
do
is
get
it
ready
now,
issue
the
release,
the
next
release
of
121
and
then
commit
it
immediately
to
122,
so
that
people
can
pull
it
down.
A
B
A
B
D
B
A
We
might
still
want
to
mention
it,
especially
if
it's
already
being
committed
to
122,
because
we'd
be
like
by
the
way
coming
soon
to
122
already
committed,
and
we
can
sort
of
give
a
little
preview
of
it,
and
that
also
would
help
get
the
word
out
for
people
who
have
themes
that
they
want
to
update
for
it.
So.
B
A
lot
of
people
have
been
involved
in
this
issue.
Anybody
else
want
to
say
anything
about
how
they
feel
about
pushing
this
off
one
more
release,
but
we,
I
think
we
should
make
sure
that
this
doesn't
become
an
excuse
to
not
finish
it.
We
got
to
finish
this
issue
in
this
release
cycle
so
that
it's
ready
to
go
and
so
that
we
don't
lose
momentum
and
push
it
off
until
two
weeks
before
1.22,
okay,.
A
Oh
all,
right
we're
out
of
time
for
today,
but
I
wanted
to
see
if
anyone
had
any
other
last
minute
thoughts
they
wanted
to
bring
up
while
we're
all
here,
nope
robert.
Thank
you
for
all
of
your
continued
work
on
backdrop.
Cms.Org.
I'm
really
excited
about
the
label
closer.
A
G
G
E
Yeah,
sorry,
I
thought
I'd
just
bring
up.
8.50
I've
been
trying
to
get
to
the
server
upgrade
for
a
while,
but
I
promise
I'm
going
to
get
it
done
by
the
first.
Okay
really
trying.
D
One
thing
that
I
wanted
to
bring
up
is
fortunately
where,
unfortunately,
this
weekend
happens
to
be
christmas
and
I'm
not
sure
if
anyone's
gonna
be
sprinting,
but
those
those
in
australia
were
working
for
people
in
australia.
I'm
gonna
have
a
long
weekend
like
four
days
off,
so
I'm
gonna
be
sprinting.
If
anyone
happens
to
have
time
not
on
christmas
day,
but
otherwise,
yeah.
A
I
was
also
hoping
to
have
time
this
weekend
on
sunday,
so
even
if
no
one
else
greg,
maybe
you
and
I
can.
B
Yeah,
I
don't
sounds
like
I'm
going
for
a
bike
ride,
so
can
I
offer
a
quick
I'm
afraid
that
some
people
not
on
this
call,
are
going
to
be
very
unhappy
with
postponing
this
nodeless
issues.
So
what
I'm
going
to
just
suggest
as
a
compromise,
is
that
we
see
what
we
can
do
in
the
next
week
and
at
the
the
dev
meeting
next
week.
B
A
final
decision
is
made
whether
or
not
maybe
we've
made
enough
progress
where
we
feel
in
the
contrib
authors
feel
comfortable
so
and
just
give
them
other
people
a
chance
to
give
feedback.
So
let's
leave
it
as
attentively.
We've
decided
to
put
this
off,
but
that
people
can
still
do
feedback
and
we
can
still
revisit
this
decision
next
week
based
on
how
much
progress
we
make
in
the
next
week.
A
I
think
that
sounds
good,
and
if
it's
close
enough
to
get
committed
on
january
16th,
then
it
should
probably
be
close
enough
to
be
committed
on
january
2nd
anyway.
So
I
think,
like
the
amount
of
work
we
have
to
do
either
way
is
minimal,
but
that
does
give
people
a
little
more
room
to
say
how
they
feel
about
it.
So
I
like
that.