►
From YouTube: Node.js Internationalization (i18n) Working Group
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
Great
so
hello,
everyone
and
welcome
to
the
weekly
meeting
of
ITM
initiative
of
nodejs.
Today,
I
am
going
to
talk
about
current
status
and
what
is
in
our
to-do
list
for
next
week.
I
hope
we
resolve
a
lot
of
currently
open
issues
that
give
us
a
big
progress.
B
For
example,
Jose
risen
call
now
he
did
a
lot
of
stuff
when
I
wasn't
busy
with
my
main
position
and
has
I
did
great
stuff
or
mojeid
org.
They
his
created
a
get
get
hook
for
that,
and
now
we
have
some
premature
preventing
for
not
usable
work
for
translators,
something
I,
don't
know
how
to
say
it's
better.
B
So
here's
this
PR
and
it's
waiting
for
somebody
else
approval
because
we
had
it
shared
with
Nick
and
he
stay
against
of
the
using
husky
like
and
get
hooks
in
general,
because
it's
not
using
on
no
GS
death
and
they
are
also
removed
from
no
GS
org.
But
it's
weird
situation,
because,
when
I
investigated,
in
the
reasons
why
they're
removed
from
the
I
know
she
has
the
death
I
figure
it
out
that
it's
not
related
to
Husky.
It's
related
to
other
stuff
and
I
pointed
about
this,
and
it's
like.
B
Another
issue
not
related
actually
two
sensations,
so
our
points
like
should
we
use
Oscar
or
not,
is
stay
open
and
we're
waiting
for
somebody
else
at
Google
know,
for
example,
you
pan
or
music,
because
I
already
approved,
but
after
a
long
discussion
I,
we
decided
to
wait
for
somebody
else
approval
and
then
we
going
to
merge
this
peer.
So
that's
what
is
the
current
state
and
also
a
Zeke
requested
changes,
but
then
not
reproved
it
so
we'll
kind
of
blocked.
Okay,.
A
B
A
B
Is
it
like
main
feature
or
last
few
weeks
and
the
real
way
is
to
waiting
for
big
results,
so
yeah
I
hope
there's
this
call.
We
will
have
some
approvals
next
question
is:
let's
open
our
issues
list
yeah
publish
the
current
model
to
NPM.
It's
related,
it's
more
related
to
Zika,
because
he
is
a
person
who
forcing
NPM
package
stuff,
I
I'm,
not
against
this,
but
I,
just
not
very
confident
and
I'm,
not
really.
B
I'm
not
forcing
this
idea
so
I
haven't
any
points
about
this
I'm.
Okay,
but
I,
don't
know
with
somebody
else
have
some
opinion
about
it.
So
the
final
decisions
that
we
had
is
we
are
making
our
repo
as
NPM
package,
but
we
are
not
not
publishing
it
to
the
NPM
and
keeping
everything
on
a
repo,
because,
with
the
current
afterafter
and
BM
version,
5
I
believe
we
can
install
packages
jerky
from
github.
So
there
is
no
any
reasons
to
publish
it
to
NPM,
but
journey.
B
B
B
Yeah
repo
contain
content,
contains
content
for
disabled
languages,
there's
something
that
we
I'm
trying
to
make
automaticall
to
remove
all
stuff
that,
like
duplicate,
but
it's
a
beer,
but
it's
a
bit
tricky
to
check
what
content
we
should
remove
and
what
content
we
shouldn't
for
that
I
already
created
not
created,
updated.
Some
workflow
I
believe.
B
And
here
also
related
to
another
stuff.
Oh
no,
sorry,
sorry
III
missed.
So
no,
it's
not
related
to
requests,
but
it's
like
kind
of
so
disabled
languages
is,
if
you
about
integration
between
github
and
crowding
after
we
alternate
of
language
and
crowding
it.
We
are
still
keep
this
content
on
github
site
and
it's
not
removing
I'm,
not
sure
that
it's
really
big
issue.
But
it's
issue
I
agree.
So
should
we
remove
this
I,
don't
know
and
yeah
here's
some
decision
like
to
drop
it
manually
and
what
is
the
next
automation?
B
A
Yeah
I
think
my
two
cents
or
my
opinion
is
that
it's
going
to
create
it
might
be
a
potential
source
of
friction,
especially
if
documentation
changes
or
something
like
that,
and
it's
not
you
know
it's
not
up
to
date
or
I
mean
there's
there's
like
there's
a
lot
of
different
reasons.
Why
I
like
I
guess
I
would
hope
that
no
one
who
speaks
a
specific
language
and
somehow
ends
up
looking
on
this
repository
for
some
information
in
their
language,
you
know
like
tries
to
access
information
that
may
be
out
of
date,
or
you
know
incorrect.
A
So,
like
there's
a
chance
that
you
know
there
could
be
a
lot
of
errata
generated
over
time
as
things
are
updated
and
it's
just
I
think
removing
it
keeps
you
know,
keeps
things
simpler
and
more
easy
to
reason
about
over
time.
So,
in
my
opinion,
if
there's
not,
if
it's
not
an
active
project
and
there's
no
real
reason
to
have
it
here
in
our
repository,
you
know
so
that's
just
my
opinion,
but
yeah.
B
And
another
thing
is:
if
we
are
turning
off
this
language
and
crawled
inside
all
translations,
that
is
already
done.
That
is
not
removing,
and
if
we
are
removing
content
on
a
github
site
and
then
we
are
turning
on
turning
back
this
elongation
crowd
inside
it
will
synchronize
and
we
again
will
have
all
translations
it
already
done
before
so
I,
don't
see
any
issues
here
and
I
I
think
I'm
going
to
create
a
PR
with
moved
removed.
Content
for
this
language
is
so
yeah
and
I
think
it's
solved.
A
B
There
are
some
bureaucracy-
stuff
I'm,
not
familiar
with
that,
but
to
use
no
GS
logo
on
your
personal
website
or
on
your
company
website.
You
should
have
some
approval
from
Logie
esque
foundation
and
crowd.
Dean
can
contact
it
to
me
to
ask:
can
we
use
logo
and
they
say
I'm,
okay
with
that,
but
I
and
I'm
not
sure.
B
B
A
It
could
is
it
as
a
translator,
translator,
agent
crowd
and
it's
not
a
good
advertisement
for
the
country's
plan
accumulated
sources
in
there
yeah
it
sounds.
It
looks
pretty
negative.
My
Questor
close
source
tool
that
only
operates
was
I,
see.
Okay
and.
B
A
That's
not
a
problem.
I
can
respond
to
this
person.
I
think
that
the
issue
here
is
that
they
they
think
they
think
that
there
are
certain
like
social
ramifications
for
using
crowd
in
that
are
a
problem
and
I.
Think
it's
more
like
this.
At
first
look,
I
thought
this
was
a
troll,
but
I,
don't
think
it
is
I.
Think
I
think
it's
someone
who's
just
concerned
about
the
integrity
of
like
no
js'
associating
itself,
with
the
crowd
crowd
and
as
a
company
or
a
platform,
so
I
can
respond
to
that.
Another
problem:
oh
okay,.
B
A
B
B
B
Project
machine
translation
risks
something
like
that
and
he
conducted
with
me.
He
makes
some
demo
for
me
and
I
said:
okay,
it's
it
looks
great
and
we
decided
that
we
probably
can
keep
this
for
a
future,
because
for
now
we
are
not
using
machine
translations,
but
if
we
start
using
it,
probably
we
can
integrate
in
some
way
with
model
front
another.
Another
thing
is
model
front.
B
Haven't
some
strong
API
that
we
can
use
for
I
me
know
daily
basis
to
check
our
check
our
content
and
unfortunately
it
should
be
did
manually
and
it's
not
very
comfortable,
but
he
he
said
like
it's
it's
in
his
plans
to
do
with
API.
For
that,
and
probably
when
we
start
using
machine
translations
Ave,
we
also
done
API
and
we
can
connect
and
you'll
be
good
communication.
B
A
Just
had
a
question
about
machine
translations
ml
translations
here.
So
what
does
the
has?
There
been
any
discussion
within
the
last
couple
week
or
a
couple
months
within
the
internationalisation
working
group,
about
like
the
reasons
for
ml
translations
versus
like
crowding
translations,
and
how
how
and
when
we
would
want
to
use
each.
You
know
like:
what's
the
advantage
of
doing
machine
translations,
you
know
versus
fully
relying
on
crowd
in
and
all
that
and.
C
A
B
The
reality
of
manual
translations,
like
using
crawled
in
and
in
enthusiast,
is
that
join.
It
is
going
so
slow
and
machine
translation
can
handle
all
all
stuff
for
one
day
and
we
have
all
translations
done,
but
it's
not
high
quality
and,
like
general
opinion,
we
can
appear,
translate
all
content
base
with
machines
and
then
new
translators
just
can
proofread
everything,
and
it's
like
reduce
a
lot
of
job
as
it
should
be
done.
B
Yeah,
yeah,
I
think
it's
possible
and
also
if
we
are
going
to
use
model
front,
the
main
idea
is
to
check
and
all
translations
and
predict
what
is
there,
what
can
be
translated
back
and
sort?
The
list
of
all
sentences
of
all
words
like
some
sentence
will
be
translated
correctly
for
99
percent,
and
some
sentence
will
be
translated
incorrectly
with
99
percent
and
better
to
focus
for
our
translators
to
this
top.
B
A
Seems
like
the
advantage,
the
advantage
of
using
machine
translations
and
then
proofreading
them
would
get
us
most
would
get
translators
in
most
of
the
way
there
right
is
what
you're
saying
so
like
having
the
translation,
be
like
seven
just
say,
70%
done
or
80%
done,
because
you
know
like
you're,
going
to
step
through
and
verify
that
each
sentence
is
correct
or
whatever
versus
having
to
translate
from
the
ground
up.
Yeah
I
mean
that's
not.
That
sounds
good.
It
sounds
like
a
positive
thing
and
it
would
save
a
time
for
our
translators.
That's
awesome,
yeah.
B
I
I
think
I'll
miss
to
get
a
bit
more
in
this
question.
Probably
some
API
is
already
done
and
we
can
make
some
experiments
for
now,
because
in
my
personal
roadmap
that
should
what
should
be
done
is
we
need
to
complete
migration
from
github
flow
to
crawled
in
and
then
we're
going
to
switch
I'm
going
to
switch
to
features.
So
it's
most
important,
so
it's
like
for
the
next
few
weeks
and
the
high
strings
is
or
things
that
I
discovered
is
to
protect
some
words
from
translation.
B
So
I
thought
this
is
there
some
that
we
can
set
it
on
our
side
on
on
repo,
with
some
JSON
file
and
Crowley
never
reached
out
to
this
sentences,
and
it
will
be
never
translated.
Like
some
links,
some
titles,
some
I
don't
know
some
pass
use,
do
the
file
name,
I,
don't
know,
and
unfortunately
it's
impossible
with
JSON
file
and
but
I
figure
it
out
another
way,
and
it's
like
you,
some
video,
how
we
can
do
this
with
crawled
in
and,
unfortunately
it
can
be
done
manually
or
this
API.
B
Oh
yeah.
So
something
like
that,
so
you
should
to
click,
should
click
on
there,
some
strings
and
click
on
hide
and
this
strings
will
still
be
shown
for
translators.
But
with
mark
height
and
after
each
translator
tried
to
suggest
some
translation,
it
will
show
some
warning:
that's
right,
yeah,
so
yeah
and
I
open
this
issue
like
to
discuss
with
everyone,
because
we
have
two
options.
First
option
is
to
do
like
I
show.
B
Another
video
is
to
do
this
manually
and
I
already
hide
some
links
like
no
GS,
JavaScript
and
other
stuff,
and
it
was
easy
and
we
and
fast
are
we
going
to
use
some
API
stuff.
But
from
my
personal
point
of
view,
it
will
be
harder
to
implement
this
script
because
we
should
handle
a
lot
of
things
like
plural
stuff.
We
should
handle
all
cases,
reject
stuff
and
Crowden
api.
Doesn't
support
reject,
so
we
should
send
a
lot
of
all
of
the
possible
options
of
the
world
to
api
to
hide
all
the
strings.
B
A
That's
yeah:
this
is
a
really
good
step.
I'm
glad
that
I'm
super
glad
to
see
that
you
discover
that
at
option
within
crowding
the
common
platform,
yeah
kind
of
plays
into
conversations
that
we
had
at
the
at
the
beginning
of
this
working
group
where
and
we
tried
to
figure
out,
you
know
we,
you
know
obviously
like
what
what
does
a
glossary.
Look
like
I've
reserved
words,
you
know,
and
how
do
we?
A
How
do
we
do
that
efficiently
and
I
think
it
if
there
is
a
so
if
we
can,
you
know,
move
forward
simply
with
a
solution
like
that.
That
already
puts
that
in
place
on
crowd
in
where
the
laterz
are
going
to
be
looking
anyway,
where
it's
already
going
to
be
generating
mornings.
You
know
that
is
a
good
place.
Not
for
that,
because
that's
all
we,
you
know
we
like,
like
you,
said,
maintaining
a
script
around.
A
That
is
just
extra
burden,
so
if
we
can
maintain
that
on
the
crowd
inside,
that
sounds
great
to
me,
maybe
with
you
know
some
kind
of
reference
to
it
or
documentation
or
no
you
know
within
our
API.
You
know
just
to
mention
something
about
reserved
words
or
something
but
yeah
yeah.
That's
really
great
I.
Think
I
just
want
to
look
at
that
a
little
deeper
and
see
what
the
you
know
what
the
options
are
and
what
people's
opinions
are
on
that,
but
yeah.
B
B
A
A
A
A
B
So
we
need
to
do
this
from
scratch
and
we
need
to
start
working
with
build
team,
because
I,
never
I
actually
saw
the
script
on
the
main
repo,
but
I'm
not
really
confident
what
is
kind
of
language
and
how
its
building
so
I
need
to
I
need
help
from
somebody
else
from
build.
Team
and
I
am
going
to
contact
with
somebody
later
so
maybe.
A
You
know
we
could
even
invite
someone
from
the
Builder
to
next
week's
meeting
if
that's
easy
or
if
you,
obviously,
if
you
were
going
to
meet
with
them
before
then
that's
totally
cool,
but
if
not
at
the
very
least
we
could
reach
out
and
see
if
somebody
can
join
us
for
next
week.
So
we
can
discuss
that
issue.
Yeah.
B
Yeah
I
think
if
he
is
it's
a
way
that
we're
going
to
to
use
so
because
I
don't
understand
how
it
works,
we
have
make
file
I,
don't
know
what
is
what
that
is
C++
or
what
is
that?
It's
in
subway,
it's
building
documentation
and
then
it's
bending,
no
Gaea
the
tour
website
and
I,
don't
know
how
it's
going
on
what
is
going
on.
So,
let's
ask
somebody
familiar
visit.
B
B
After
is
dead
end
of
life
and,
from
my
point
of
view
it
looks
it's
not
right
strategy,
because
we
have
the
commutation
for
all
versions
of
no
GS
on
the
website
and
it's
expected
result
to
have
all
translations
for
all
these
versions:
I'm,
not
forcing
translators
to
make
some
sessions
for
duplicated
versions.
My
point
is
just
to
not
remove
already
translated
content
from
our
repo
because
how
it
works.
B
Now
we
are
removing
it
and,
as
you
can
see,
is
already
removed
version
6
and
version
8,
I'm,
ok
with
it,
because
I
am
not
using
it,
but
let's
imagine
somebody
from
exactly
crane
want
to
use
it,
and
he
also
worked
on
the
translations
for
version
6
and
now
it
disappear.
So
it's
not
really
expected
so
I
created
this
issue
because
it's
easy,
yeah
and.
A
B
B
I
updated
script
to
not
remove
this
versions,
so
it's
still
open
and
I
have
won
approval,
but
there's
some
discussion
with
Nick
I'm
still
waiting
for
some
somebody
else
again.
When
I
have
some
discussion
with
Nick
hehe
like
he
convinced
me
to
let's
investigate
more
and
I
start
struggling
in
my
idea
exactly
what
is
work,
let
me
just
translate
because
it's
really
interesting.
A
B
A
Here's
a
here's,
the
thing
so
if
this
is
the
source
of
like
my
question,
is
source
of
truth
for
documentation
for
all
versions.
So
if,
if
you
know
like,
where
does
the
source
of
truth
for
no
longer
supported
versions
live?
And
you
know
obviously
like
we
want
people
to
use,
you
know
supported
versions,
an
LTS,
and
you
know
newer
versions,
and
that
sort
of
thing,
however,
like
you
said
there,
may
be
other
people
out
there
who
are
dependent
on
an
old
version
of
node
or
have
some
project
that
shrink-wrapped.
A
If
there
is,
you
know
like
where
the
like,
where
the
source
of
truth
is
for
all
the
older
versions
of
you
know,
nodejs
as
far
as
documentation
of
those
api's
and
if
there
is
not
I,
haven't
actually
looked
at
the
nodejs
org
site
to
see
like
how
far
back
the
documentation
goes,
but
if
they're,
for
the
first
version,
like
is
zero
point.
Oh,
what
goes
all
the
way
back
then
yeah,
okay,
okay
versions,
okay,
cool!
Well,
if
all
the
versions
live
on
the
nodejs
network
side,
okay,
yeah,
okay!
Well,
then
that's
fine!
A
Yeah
I
was
worried
about
like
if,
if
someone
needs
to
reference
like
all
the
documentation-
and
they
can
now
does
that
need
to
be
translated
into
every
language
and
have
references
for
those
over
time-
that's
debatable!
Yeah.
You
know
like
as
long
as
there's
some
kind
of
single
source
of
truth
for
every
version.
That's
documented
somewhere,
but
again,
like
you
said
you
know,
maybe
have
somebody
if
somebody's.
B
A
B
B
It's
something
about
repos,
but
I
think
this
enough
is
and
we
can
switch
to
pull
requests
because
it's
more
important
from
my
point
of
view.
Yes,
so
let's
just
yeah
this
PR
we
already
discuss,
is
about
adding
documentation
back
okay
next
stuff
is,
is
about
discuss.
It
is
about
our
roadmap,
how
we're
going
to
protect
our
fans
from
direct
updates,
so
I
created
and
github
actions.
Workflow.
For
these
reasons
and
again,
I
am
waiting
for
okay,
I
have
one
approval.
Probably
I
can
merge
it
yeah.
So
this
we
have
two
lines
of
protection.
B
First,
first
is
github
that
we
are
making
initial
steps
to
to
avoid
some
unusable
work
get
by
a
translator,
and
the
next
step
is
when
potential
translator
ignored
all
our
warnings
and
committed
in
some
way
after
he
is
making
requests
with
translations.
We
are
saying:
okay,
man,
but
sorry
we
are
not
using
this
approach.
Please
use
Croton
and
we
believe
this
polite
as
much.
C
A
B
This
functionality
between
all
no
J's
projects,
because
we
have
three
projects
and
we
need
to
have
the
same
functionality
for
each
of
them.
For
example,
Jose
I
already
created
a
get
hoop
for
no
J's
dot,
org
or
but
doesn't
for
idea
and
I
thought
about
and
beam
package.
But
then
I
decided
it's
overhead
and
probably
we
should
copy-paste
it
for
whole
projects
and
let's
see
how
it
will
be
so
for
now,
I'm
working
with
89
and
then
I
am
going
to
create
the
same
request
for
new
website
and
for
old
website.
A
Awesome,
yeah
I
think
it's
it's
more,
just
like
maybe
a
rule
of
three
or
four.
You
know
if
we
end
up
having
more
projects
than
we
might
need
an
NPM
project,
MPM
package,
but
for
now
just
you
know,
copy
and
paste
is
like
name
was
like
three
projects.
So
it's
not
nothing's
good
Oh
on
the
chat,
hello,
Steven,
oh
gosh,
we
have
a
couple
more
people
here
that
need
to
be
added.
A
Co-Host
I'm
making
everyone
co,
those
two
just
so
sorry
for
you
were
I
just
got
here:
okay,
cool
just
didn't
want
to
be
late
to
the
driver.
Okay,
cool
everyone
should
be
a
co,
so
you
are
able
to
talk
and
say,
hello.
I'll
show
you
video!
If
you
want
Steven
welcome,
hey,
we
just
ran
through
a
bunch
of
kind
of
a
current
status
on
you
know
where
we
are
with
Cronin
and
translations
and
the
npm
module
and
different
things
like
that.
A
C
Generally,
okay
I
a
couple
of
PRS
merged.
Recently
one
is
the
ICU
67.1.
It
was
just
latest
list
update
and
and
content.
Another
one
was
a
document.
That's
been
sitting
for
a
while
on
how
to
do
how
to
do
timezone
updates,
you
know,
Morocco
is
on
and
then
off,
timezone
I,
don't
remember,
I,
never
keep
trying
on
straight
I,
just
trust
the
code
that
data
so
anyway,
Morocco
is
wrong.
C
Unless
you
get
timezone
2028
well,
one
one
thing
is
that
I
think
that
how
to
load
time
zone
data
on
the
side
without
needy
rebuild
everything,
it's
an
open
issue.
It's
been
open
since
no.12
I
need
some
attention.
So
if
anyone
has
thoughts
on
how
that
can
can
be
handled,
you
know,
let
me
know
it's
that
definitely
needs
work
here.
I'm.
D
C
D
C
Lot
happening
with
there,
the
the
ECMO
for
to
progression
and
there's
also
a
new
project
called
ICU
for
X
long,
which
is
targeting
rust,
but
it
may
eventually
be
a
good
source
for
a
building
for
linking
in
with,
because
you
could
target
you
can
target
web
at
webassembly.
Icu
is
in
India,
II
ECU.
Oh
sorry,
I.
C
C
A
C
D
A
B
It's
like
some
problems
with
that,
because
it's
it's
really
hard
to
explain
so
workflow
cannot
trigger
workflow
and
this
an
issue
and
if
pull
requests
created
but
github
bought,
they
cannot
start
running
any
test
checks,
and
this
is
a
problem
in
the
quick
workaround
is
to
close
and
immediately
reopen
this
pull
request
and
they
just
edit
these
instructions
here
and
I
I
spend
more
time
to
plan
this.
Your
then
I
detection,
so.
B
So
yeah
he
is
just
a
pretender
I'm
going
to
merge
it
there's
no
any
functional
changes.
Yeah
another
thing
is:
I
updated
our
script.
Our
citizens
content
sync
script
to
remove
translations
for
removed
regional
files.
So,
for
example,
we
have
file
a
and
file
B
on
original
content
and
we
have
the
same
files
for
the
translation
after
we
are
removing
file
a
for
original
for
translations
file.
A
still
keep
keeps,
and
we
are
not
handling
this
case.
So
I
updated
our
script
to
remove
this
files
like
this
and
welcome
to
review
and
Wow.
B
Thank
you.
That's
great
yeah
and
last
top.
Oh,
oh
yeah
and
I'm,
going
to
make
everything
automated
and
I
want.
I
want
to
make
our
issues
to
create
automatically
so
I
created
this
pull
request
and
yeah.
Please
welcome
to
review.
It
will
be,
it
will
create
if
you
like,
we
have
for
our
meeting
on
weekly
basis
for
each
Wednesday
and
yeah
I.
B
B
So
yeah
just
please
check
and
yeah,
and
it's
that's
basically
it
from
my
side
and
also
I
have
some
update.
Yesterday,
I
I
had
a
chance.
I
had
a
meeting,
not
a
meeting
had
a
call
with
Giuseppe
from
OpenGL
foundation
and
I
promoted
our
eye.
18-Inch
initiator
I
talked
about
what
is
going
on.
What
we
have,
what
is
the
progress
and
what
is
the
current
status?
So
I
I
felt
that
we
did
a
lot
of
people
joined
to
our
team
after
this
call,
but
unfortunately,
for
now
it's
just
one
person,
but
it's
also.
B
A
B
A
Thankful
to
do
that,
I'm
gonna
try
to
continue
to
do
my
best
to
promote
things
on
Twitter
who
seem
to
get
a
good
response
for
that.
I
think
the
one
thing
I'd
like
to
help
focus
on
since
my
working
hours
are
coming
back
to
me.
I
feel
like
one
thing:
I'd
like
to
help
is
making
translator
resources
like
how
to
get
involved
more
main
term
or
more
visible.
You
know
for
people's,
because
I
feel
like
every
time
we
tweet
about
it.
You
know
people
are
excited.
A
You
know
in
different
localization
groups,
so
there
was
definitely
some
work
to
be
done
to
enable
those
groups
you
know
like
within
there
within
crowd
and
within
their
repositories
and
whatnot.
So
yeah
excited
to
attack
this
from
all
angles
and
man.
Thank
you
for
all
your
great
work,
Alexander
think
thank
you
Jose.
A
You
know
for
the
work
you're
doing
Zeek
who's,
not
here
Thank,
You
Steven,
for
the
the
update
today
and
joining
yeah,
and
just
look
forward
to
seeing
you
all
next
week
and
pay
it
can
up
some
more
steam
here.
So
I
think
I.
Think
that
should
do
it
for
today.
Unless
anybody
has
any
last
thoughts,
they
want
to
share.
I
did.