►
From YouTube: Backdrop Weekly - Auril 23rd 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
B
A
E
G
A
C
So,
as
always,
we're
working
on
the
on
regular
bug
fixes
115
will
be
the
next
bug
fix
release.
Yet
to
be
seen
when
that
will
happen,
it's
I
guess
it's
possible
that
115
may
go.
The
entire
cycle
was
only
one
interim
bug
fix
release,
and
that
was
a
security
fix.
They
coordinated
with
Drupal,
so
that
would
that
would
be
in
a
way
it
kind
of
meets
115.
C
We
don't
have
any
urgent
issues
to
discuss
during
these
meetings.
However,
there
are
65
issues
that
have
been
bumped
into
the
115
minor
or
sorry
bug
fix
milestone
over
on
github,
so
we
do
have
a
number
of
items
that
could
be
fixed
at
any
time.
However,
we
don't
really
have
any
of
those
that
look
like
that
are
in
a
state.
That's
ready
to
go.
There
are
a
large
number
of
them
that
need
review,
though
so
I
don't
have
anything
to
say
on
115
other
than
you
know,
go
and
check
out
that
list
of
issues.
C
You
guys
have
anything
you
like
to
bring
up
regarding
bug.
Fixes:
okay,
116
is
the
next
feature,
release
the
minor
release
that
will
be
coming
up:
May
15th
with
feature
freeze
on
May
1st,
that
is
a
Friday
and
/
the
discussion
from
last
week.
It
will
actually
be
on
May
1st,
as
it's
not
landing
on
a
weekend
or
a
holiday
or
anything
so
that's
a
week
from
tomorrow,
so
things
that
we've
got
to
work
through
for
that
time.
C
First,
one
that
we've
got
up
here
is
base
and
sub
installed.
Profiles
is
an
issue
that
Peter
BW
panda
has
been
working
on,
issued,
31
74
he's
not
here
today,
but
the
update
on
that
one
is
that
we
might
not.
Even
even
though
the
code
has
been
implemented,
we
might
not
pursue
that
functionality
at
all.
There's
been
some
discussion
about
a
workaround
that
can
be
used
to
imitate
something
kind
of
like
sub
install
profiles
without
actually
having
any
kind
of
core
support.
C
But
the
issue
with
this
one
in
general
is
that
it's
difficult
to
test,
and
so
functionality
that
is
maybe
not
incredibly
common
and
is
also
difficult
to
test,
makes
a
poor
combination
so
we'll
see
if
that
work
around
it
ends
up
being
suitable
for
Peters
situation
and
for
others,
and
then
possibly
we
can
just
say:
okay.
This
is
a
workable
solution
without
any
modifications
to
core
in
the
first
place,
so
that.
G
C
E
C
C
B
I
have
to
admit
that
my
my
update
might
be
stale
because
I
haven't
touched
place
with
a
lot
of
like
what's
happening
recently
in
Baxter
plant
lack
of
time,
but
last
night
it
was
that
we
implemented
a
solution
that
involved
duplicating
the
worker
forms
being
opened
in
dialogues.
And
then,
when
the
dialogue
was
closing,
then
we
would
transfer
those
settings
that
were
saved
into
the
hidden
forms
of
the
actual
form.
This
was
not
an
acceptable
solution,
but
doctor.
What
would
with
then
refactor
that
which
he
did
I
did
a
review.
B
C
A
It
was
a
query
issue
or
the
page
underneath
like
actually
renders
all
the
buttons,
and
so,
if
you'd
like
add
an
image
tag,
it
needs
to
move
the
image
tag
and
so
that
none
of
that
is
working
herpy
add
an
image
tag.
It's
supposed
to
add
the
image
tag
in
no
allowed.
Html
tags
add
an
image
button,
so
there's
just
a
correlation
there.
That's
not
not
working
anymore
and.
A
B
E
B
If
you
disabled
one
of
the
filters
and
that
filter
was
supposed
to
remove
one
of
the
buttons
from
being
available,
see
how,
when
you
are
in
the
format
configuration
page
at
the
top,
the
big
where
you
can
drag
the
buttons
say
I
would
disable
a
filter
that
has
a
respective
button.
It
wouldn't
go
away
when
I
disable.
B
The
filter
I
would
have
to
save
the
form,
which
would
redirect
me
to
the
list
of
all
the
formats
and
then
I
would
have
to
go
andrey
edit
it
and
then
it
would
not
be
there
the
button,
but
it
seems
to
me
I,
don't
remember.
It
was
like
three
weeks
ago
when
I
tested
this,
but
I
think
the
actual
instance.
But
if
you
try
it
at
the
user
to
edit
it,
the
button
will
work
as
expected.
It
would
be
there
be.
There
is
the
I
think
that
was
six
or
not
be
there
and.
A
I
remember
the
buttons
working
on
the
note,
edit
form
being
what
I
wanted
on
the
configuration
form,
not
being
what
I
wanted,
but
I
still
think
allowing
someone
to
configure
an
editor
that
has
a
button
that
doesn't
haven't
allowed.
Html
tag
is
a
problem.
It
was
a
huge
problem
in
Drupal
it
was
really
frustrating
and
we
fixed
it
in
backdrop
and
I
would
hate
to
have
a
regression
there.
Yeah.
C
Okay,
so
that
someone's
still
kind
of
going
along,
mostly
dark
Roman
has
still
been
really
on
top
of
addressing
feedback
for
the
most
part,
and
even
though
gem
did
leave
that
feedback
six
days
ago,
it
looks
like
garnering,
more
feedback
and
more
frequent.
A
review
cycle
will
make
it
so
that
those
things
get
get
corrected
more
quickly
and
I
I,
don't
think
we
really
other
than
the
jQuery
request,
I
think
dark.
One
one
can
can
really
cycle
on
the
on
the
development.
Pretty
quickly
did.
B
D
C
C
E
I
I
can
just
say
that
we
at
the
last
last
week
we
talked
about
this
extensively,
pretty
much
decided
to
take
out
all
of
the
UI
for
this
and
just
work
on
the
backend.
The
capability
to
designate
I
think
different
statuses
for
revisions.
It
looks
like
that
Wilmont
has
a
pull
request.
I
haven't
looked
at
it
and
I'm.
To
be
honest
if
the
UI
has
been
taken
out
of
it,
I'm
not
sure
like
what
I
can
do
to
review
it.
So
I
think
the
next
step
is
like
yeah.
How
do
we?
B
So
coming
from
Dhokla
was
that
I
saw
was
that
there
was
a.
It
was
a
cool
request
for
like
50
some
commits,
and
only
the
two
of
them.
The
two
initial
ones
was
the
basic
API,
so
he
wanted
to
reverse
the
best
thing.
Basically
get
all
the
rest
of
that
commits
out
and
I
was
a
great
careful,
I'm,
not
sure.
C
C
It
looks
like
some
test
additions,
because
the
only
way
this
can
be
tested
is
through
code.
Currently,
so
there's
some
simple
additions
that
looks
like
he
just
tries,
creating
a
node
and
then
saving
a
revision
and
then
checking
to
make
sure
that
the
database
tables
all
came
out.
The
way
that
he
expected.
C
E
C
B
C
A
We
did
decide
that
we
were
since
Nate
was
probably
going
to
be
looking
at
the
code
this
weekend.
We're
gonna
do
a
little
mini
code
sprint
this
weekend
in
preparation
for
it,
so
that
it
we'll
be
working
during
the
middle
of
the
week
next
week
on
stuff
anyway.
So
if
we
could
sort
of
do
that
crunch,
early
I
think
that
would
be
good.
G
C
E
Well,
kind
of
turn
it
back
to
you
Nate
because
it
looks
like
you,
I've
worked
on
that
since
last
week
and
again,
I
haven't
actually
liked
when
you
looked
at
it
yet,
but
I
think
you
solve
some
of
the
problems
with
tests
and
it
looks
like
the
status
is
code
reviewed.
You
need
somebody
else
to
look
at
your
code
or
what
there's.
E
C
I
found
that
there's
an
there's
an
option
for
updating
the
way
that
the
submitted
by
line
looks
for
nodes
and
the
way
the
submitted
by
line
looks
for
comments.
There's
two
options
added
to
the
node
type
form.
However,
both
core
themes,
basis
and
Bartok
don't
use
the
submitted
variable
in
their
comment
templates,
and
so
you
can
change
that
setting,
but
nothing
happens
because
they're,
both
individually
printing
out
the
author
in
one
place
and
then
the
date
in
another
place.
C
C
C
So
my
suggestion
is
that
maybe
we
just
mix
it
from
the
comments
like
take
out.
The
common
setting
actually
I
haven't
even
suggested
this
in
the
issue,
but
I'm
thinking
the
most
direct
way
forward
would
be
if
we
removed
the
comment.
Setting
only
kept
a
node
setting
the
one
that's
actually
used
by
court,
and
then
only
had
this
customization
available
for
nodes
and
not
for
the
comments.
I.
A
Don't
know
that's
something
that,
as
a
theme
developer,
I
find
really
frustrating
is
when
you
fix
the
submitted
line
nodes
and
it
doesn't
fix
on
comments
having
the
ability
to
set
it.
The
same
way,
I
think
would
be
beneficial.
I,
don't
know
how
to
get
around
the
problem
where
the
existing
choice
even
separates
them.
I
mean
that's
a
perfect
example
of
how
you
want
to
separate
them,
which
I
think
is
also
important
to
have
in
for
I,
wouldn't
think
fixing.
It
would
be
a
solution
but
yeah.
This.
A
C
Would
cut
also
another
brain
just
idea
is
that
the
submitted
byline
I
think
is
the
same
for
comments
and
for
nodes.
Currently
it's
just
submitted
by
author
name
and
then
date,
our
and
then
date.
If,
if
they're
the
same
between
nodes
and
comments,
we
could
work
with
the
loose
assumption
that,
whatever
submitted
by
setting
you
have
four
nodes,
we
also
applied
to
comments
of
that
same
type
and
then
at
least
the
submitted
byline
is
customized,
but
it
applies
to
both
the
node
and
the
comments.
Even
though
the
comments
discard
the
setting
with
core
themes
so.
C
E
B
So
if
it's
not
worth,
it
would
have
been
a
good
compromise
again,
but
the
way
that
the
way
that
may
describe
the
problem
with
the
things
it
seems
to
me
that
it's
it's
a
bug
with
our
things
that
we
should
think.
So.
This
feature
is
something
that
people
expect.
We
expect
to
be
working
with
all
themes,
and
if
people
were
to
do
it,
I
would
use
the
word
proper
way.
It
would
work.
B
A
E
Unlikely
to
be
solved
quickly,
but
we
have
been
talking
in
the
past
about
how
to
add
CSS
changes
to
core
basis
that
might
like
previous
sites
by
having
some
sort
of
revision
where
they
only
affected
new
sites
or
not.
You
know
people
would
have
to
deliberately
and
I
don't
know
if
that
could
be
applied
so
that
we
could
make
the
changes
to
the
two
plates
and
basis
yeah,
but
only
apply
to
new
sites.
It's.
A
More
complicated
than
like
adding
a
stylesheet
is
pretty
straightforward
to
do
like
include
or
don't
include,
but
interrupting
the
like
render
line,
2
insert
a
new
template
or
not
is
a
little
more
complicated
and
I'm,
not
sure
we
want
to
get
that
deep
in
the
weeds
we
could.
Maybe
we
should
create
an
issue
to
talk
about
it,
but
it
I
think
it's
gonna
create
complexity.
That's
gonna
be
really
confusing.
Okay,
I.
B
Recall
this
conversation,
another
team
mentioned
it
and
I
understand
the
concerns
that
Jen
brought
up
but
pulling
out
the
we
care
more
about
end-users
rather
than
developers.
I
understand
the
overhead,
but
our
our
philosophy
is
that
we
fix
things
for
end-users
and
we
worry
about
how
hard
it
is
for
developers.
Second,
we're.
B
A
C
A
C
E
A
C
C
E
B
It's
on
Friday
made
the
first
and
this
year
is
happening
online
into
two
presentations
on
backdrop.
We're
approved
one
is
what
Tim's
presentation
on
layouts
and
then
the
other
one
is
myself
presenting
on
mostly
I.
Haven't
thought
figured
out
the
exact
way
that
this
would
work
out,
but
basically
it's
presenting
backdrop
as
an
optimal
solution
for
people
that
are
not
ready
to
move
to
the
eight
inside
of
the
sevens
end-of-life.
B
A
E
Yeah
I
think
registration
is
like
twenty
bucks
for
this
event,
isn't
it
it's
anybody
remember
there
was
a
small
dad
discount
for
presenters
anything
else.
People
need
to
know.
I
don't
know.
I
would
encourage
people
to
support
this
event,
because
we
will
support
the
idea
of
open
source
CMS
camps
or
events
that
are
cross-platform,
and
so
it
would
be
great
if
we
could
turn
out
some
people
at
this
to
show
support
for
this
kind
of
an
event.
Yeah.
B
C
And
with
our
the
way
that
our
community
functions,
you
know
we're
highly
distributed
and
they're
there
it's
difficult
to
collect
people
all
in
the
same
place.
So
even
even
though
this
is
a
virtual
event,
it
plays
to
our
favor
really,
but
it's
not
in
a
geographic
location,
so
yeah.
Another
great
reason
to
support
this.
C
D
Yes,
like
tried
yeah,
be
wonderful,
basically,
for
me,
searches
was
always
important
and
it
made
me
hesitate
to
switch
it
back.
Job
and
now
I
use
back
drop
a
lot,
but
I
still
have
plenty
of
sites
which
make
heavy
use
of
Search
API,
and
there
was
a
discussion
about
having
a
better
search
at
core,
but
from
my
personal
respective
Search
API
is
pretty
good,
pretty
great.
D
It
fulfills
all
my
needs
and
my
sights
and
then
I
lost,
I
lost
track,
and
maybe
a
week
ago
a
guy
called
dan
from
from
Oxford
UK
asked
me
if
I
could
help
him
with
a
moving
that
forward
in
the
issue.
Queue
get
up
and
I
said
no
I'm
a
guy,
but
I
will
tell
other
people
what
to
do
and
then
Tim
came
in
and
answered
and
that's
the
status
and
I
promised
to
get
a
summary
of
about
currents,
surging
core.
What
is
planned
if
there's
something
planned.
D
D
A
But
that
doesn't
mean
that
all
the
features
that
are
in
there
don't
belong
in
backdrop.
So
yeah
we
have
a
long-standing
issue
about
how
backed
up
core
search
alone
is
not
sufficient.
There's
a
lot
of
issues
with
it.
There's
a
lot
of
just
craft
left
over
from
ten
years
ago,
when
it
was
put
in
there
and
never
been
looked
at
since
and
I
would
love
to
see
some
attention
spent
on
it.
I
I,
don't
know
exactly
what
that
looks
like,
but
I
for
one
in
favor
of
improving
it,
but
I.
A
B
Some
thoughts
but
I'm
ambivalent
when
it
comes
to
that
so
Drupal
8
core
has
allowed
without
having
to
install
any
any
other
modules
to
to
be
able
to
embed
videos
from
YouTube
and
Vimeo,
because
these
seem
to
be
the
most
common
services
used.
So
the
agency
that
our
work
force
supports
gap
CMS,
which
is
a
distribution
for
government
in
Australia
and
the
platform,
is
using
solar
as
well,
but
people
have
been
bringing
up
I'm,
not
sure
if
you
guys
with
lunar
as
well
spelled
Lu
and
which
is
an
alternative.
B
So
again,
we
have
to
similarly
to
the
way
that
something
was
introduced
in
v8
for
YouTube
and
video,
which
are
the
most
commonly
used
services.
When
it
comes
to
video
hosting
ideas,
I'm,
not
sure
how
much
we
can
accommodate
what
Jen
said,
improving
the
course
it's
and
providing
a
hybrid
between
what
we
currently
have
and
easily
allowing
to
connect
the
solar
or
liver
I'm,
not
sure
how
much
of
that
belongs
to
screen.
E
Just
want
to
say
it
seems
to
me
like
a
well
that,
every
time
but
frequently
when
we
put
out
a
call
to
the
public
like
hey,
what
do
you
want
to
see
us
work
on
in
backdrop
that
somebody
always
mentioned
search?
This
is
not
something
I've
run
into
a
need
for
better
search
myself,
but
I
do
fairly
frequently
hear
this
from
other
people.
E
D
B
D
B
B
A
I
think
it's
also
important
that
we
get
a
conversion
working
cause.
There
are
a
lot
of
people,
hopefully
going
to
be
coming
from
Drupal
that
are
already
relying
on
it.
I,
don't
know
what
the
complexity
is.
I
would
imagine
that
it
is
very
complicated.
I
also
would
imagine
very
hard
to
develop
in
an
environment
where
you
don't
have
access
to
those
things,
but
we
do
have
access
to
Apache,
Solr
I
think
it's
about
your
seller
might
be
lucerne
on
pantheon
and
we
might
be
able
to
look
at
the
Pantheon
suite
of
modules.
A
E
Just
to
be
clear,
if
anybody
isn't
this
person,
this
band
Mattias
did
you
note,
did
you
just
see
Dan
in
the
issue
queue
or
do
you
know
him
outside
of
the
issue?
Queue
I
met
him
in
HQ,
okay,
I,
don't
know
him.
The
double
contact
came
tomorrow
sure,
so
he
just
popped
into
the
issue
queue
and
it
basically
looks
like
he
maintains.
It
sounds
like
multiple
sites,
Drupal
seven
sites,
yeah.
E
They're
basically
evaluating
backdrop-
and
he
said
the
church
in
a
bill
or
a
lack
of
search
api
would
be
a
blocker
for
them
now.
The
other
thing
it
wasn't
clear
to
me,
matthias
if
he
would.
He
said
he
was
willing
to
help,
but
I
wasn't
sure
if
he
has
the
coding
skills
to
like
help
with
fix
bugs
or
if
he
was
just
talking
about
testing.
Apparently
he
has
apparently.
E
Sax
has
been
that
the
church
has
just
been
held
up
by
the
lack
of
somebody
with
the
skills
and
the
motivation
to
work
on
it
right
and
then
you
know,
probably
other
people
in
the
community
would
support
somebody.
Yeah
stepped
up
and
took
initiative,
but
none
of
our
active
contributors
have
just
felt
like
it
was
enough
of
a
priority
to
that
time.
Right
now,.
C
So
it
sounds
like
the
general
direction
here
is
that
the
contributor
JPI
needs
to
be
or
should
should
be
better
maintained
and
supported,
but
I
think
parallel
to
that,
there's
a
lot
of
room
for
improvement
and
core
search
to
make
it
better,
so
that
Search
API
is
continues
to
be
like.
If
you
need
more
complex
search,
then
search
API
is
the
way
to
go,
but
core
search
is
also
like.
It's
not
great,
like
it's
really
just
the
way
that
it
works
is
just
really
kind
of
dumb
to
like
that.
B
This
was
basically
the
the
argument
that
was
brought
up
when
this
discussion
was
happening
for
Drupal
6
in
Drupal
7,
that
that
the
the
current
implementation
of
sets
is
so
crappy
that
it
would
be
better
to
replace
it
with
something
like
sit
API
and
in
the
counter
arguments
to
that
is
that
set
API
mostly
relies
on
third-party
services,
which
is
yeah.
We
need
to
be
trading
like
and.
C
G
C
C
A
There's
a
lot
we
could
learn
from
it,
though,
like
I,
don't
necessarily
think
we
should
take
this
code
and
put
it
in
court
away.
It
is
but
I
think
we
could
look
at
what
is
produced
with
a
really
good
search
experience
using
search
api
and
saying,
okay,
they
have
a
way
you
can
customize
facets.
We
need
to
figure
out
how
to
do
that
and
for
they
have
a
way
that
you
can
like
put
all
the
things
together
and
have
the
node
content
user
be
like
separate,
I,
don't
know
links
or
something.
A
Would
you
figure
out
a
way
to
put
that
encore
and
we're
probably
on
on
very
different
solutions
than
the
way
that
Search
API?
Does
it,
but
I
think
that
the
end
result
could
end
up
being
rather
similar
and
if
we
end
up
having
a
really
complicated
configuration
for
it?
As
long
as
we
set
the
defaults
to
work
the
way
people
expect
in
backdrop,
they
may
never
need
to
see
that
form
like.
G
A
B
So
if
it
is
taking
us
so
long
to
so
like
trying
to
fix
core
search,
I'm,
not
sure
how
much
more
complicated
the
simple
but
a
simple
version
of
spirit,
yeah
would
be
like
a
street
stripped-down
version
with
just
the
basics
would
be
so
yeah
I
I
have
not
taken
a
look
at
the
code.
I
wouldn't
be
able
to
judge
that
we
need
someone
with
more
experience.
I.
D
A
A
Could
use
in
our
core
search,
and
that
would
be
something
that
could
be
backwards
compatible
because
we
could
have
it
be
like
anyone
who's
previously
installed.
Backdrop
gets
the
versions
there
now
anyone
who's
in,
let's
use
instead
so
yeah
and
I
think
is
their
views.
Integration
with
this
search
index
in
core.
A
F
D
E
In
terms
of
tangible
things,
we
could
do
I'm
just
gonna,
throw
out
there
if
anybody
who
are
so
motivated
to
write
up
like
a
blog
post.
That
said
what
here's
the
status
of
search
like
what
is
available
where
it's
week,
where
the
work
needs
to
be
done,
so
that
when
we
find
somebody
with
some
skills
and
motivation,
we
could
point
them
and
say
here's
what
you
know
has
to
happen.
That's
it
seems
to
me
like
a
good
first
step.
B
Yeah
all
the
time,
I
added
that
I
didn't
about
API
there
I'm,
not
sure
if
we
have
some
time
to
discuss
even
likely
so
I
was
working
on
a
same
way
that
I
do
every
time.
I
just
picked
a
random
problem
and
it
started
solving
it
or
trying
to
push
an
existing
PR
along,
and
then
it
came
to
presenting
numbers
to
users
and
in
my
tests,
I
created
like
thousands
of
nodes,
because
it
was
related
to
search
by
the
way.
B
It's
it's.
The
the
the
issue
that
Alan
now
started
with
being
able
to
limit
which
content
types
will
be
searched
will
be
indexed
so
at
some
point
the
index
would
present
how
many
of
the
nodes
were
already
indexed
and
how
many
are
remaining,
and
this
brought
up
the
thousands
numbers
not
having
digital
sorry,
this
decimal
and
thousands
which
one
the
punctuation
and
how
this
comes.
B
This
is
different
from
country
to
country,
so
I
know
that
I
can
use
PHP
functions,
but
that
would
make
it
so
that
we
make
it
valid
for
like
I,
don't
know
us
look
out
one
week.
So
the
idea
there
is
that
d8
is
already
moving
towards
that
format.
Api
phone
numbers
in
port.
You
know
I'll
create
a
ticket
to
point
to
those
tickets.
Do
we
want
to
do
something
like
that
in
backdrop
with
respect
to
doing
more
for
multilingual
I.
C
C
The
internationalization
should
be
a
given
in
a
CMS
that
is
as
comprehensive
as
backdrop
like.
We
really
should
be
global
product
that
should
work
in
every
language
and,
in
this
case
every
locale
format
for
dates
and
time
and
and
numbers
like
it's.
It's
a
weird
omission
that
we
support,
dates
and
interface,
translation
and
content
translation,
but
not
numbers
like
it
seems
like
a
weird
shortcoming:
yeah.
B
F
Module
actually
has
a
function
that
just
you
pass
in
a
number
and
the
currency
code
that
goes
with
it,
and
then
it
checks
the
locale
for
that
currency
and
then
puts
in
the
correct
separators
for
it
yeah,
and
we
actually
had
a
website
that
had
the
commerce
module
installed
just
to
use
that
one
function,
we
didn't
actually
have
any
products
at
all.
Yeah.
B
So,
basically,
the
camera
right
now
with
a
PHP
function
that
so
like
I,
think
it's
called
number
format
number.
Something
like
that.
What
I
was
thinking
would
be
something
like
backdrop
for
Mach
number,
which
would
be
a
wrapper
to
check
which
Macaulay
is
currently
selected
and
then
and
then
have
presets
that
it
would
sort
of
like
speed.
The
numbers
like
it
seems
to
me
that
it
would
be
straight
forward,
but
I
haven't
gone
down
the
rabbit,
hole
and.
C
Places
where
so,
you're
right
number
format
is
PHP
function
and
I'm.
Just
doing
this
search
there
core
to
see
where
we're
using
that
function
already,
because
we
already
use
it
because
it's
convenient
to
make
it
so
that
you
know
commas
are
used
for
the
thousand
separators
and
stuff
like
that.
For
for
the
areas
that
use
that-
and
you
know
it's
useful
for
that
purpose,
so
where
numbers
should
be
formatted
weren't
already
using
that
function,
but
the
places
in
which
we're
using
it.
C
C
For
if
locales
also
had
number
of
formats
associated
with
them,
somehow
I'm
not
quite
sure
where
that
would
live
like
in
locale
module
or
something
like
that
that
when
you
setup
a
language
and
the
locale
you'd
also
set
up
the
number
format
for
it
and
then
everywhere
that
we
call
number
format,
there
would
be
some
option
to
use
the
appropriate
locale
site-wide
format
instead.
So,
like
use
the
number
format
rather
than
the
hard-coded
comma
or
period
configuration,
that's
at
the
field
are
viewable.
The.
B
So
what
I'm
gonna
do
is
maybe
just
create
an
issue
and
just
point
to
those
tickets
and
I
think
that
that's
the
way
that
they've
done
it
as
well,
because
there's
certain
languages
that
the
decimals
are
even
like,
they're,
not
commas
or
dots
at
all,
like
I,
think
Arabic
has
a
special
yeah
anyway.
So
so
we
need
a
you
I
thing
in
locale,
but
sorry,
language,
selection,
okay,
all
right
cool
yeah,
but.
C
B
C
C
Okay,
well
yep.
We
I'm
glad
we
fit
that
in
Gregory,
but
we
are
over
time.
We've
only
got
one
week
left.
We
still
have
one
more
meeting
before
feature
freeze,
so
we'll
see
you
guys
all
again,
hopefully
on
April
30th
the
day
before
our
future
freeze,
as
Tim
mentioned,
some
of
us
are
providing
extra
allocation
overtime
this
weekend
to
try
to
speed
up
the
cycle
of
review
and
functionality,
so
they'll
be
kind
of
an
all
weekend.