►
From YouTube: 2021-03-17 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).
B
B
B
Yeah,
I
think
we
can
start
keep
a
quick
update
on
the
agenda
which
I
have
put
here.
I
don't
think
anyone
had
took
anything
else
here,
so
I'll
just
go
over
the
things
which
I
have
put
here.
So
the
first
thing
is
about
the
next
release.
Let
me
open
the
milestones
so
we
have
like
pushed
this
by
another
week.
It
was
supposed
to
go
out
last
week,
but
we'll
be
doing
a
1.1
release
sometime
next
week
or
maybe
like
this
friday.
B
B
B
Speaking
of
releases,
we
have
another
update
for
the
instrumentations
from
the
contrib
repo.
It
looks
like
most
of
the
instrumentations
in
this
repo
are
unblocked.
I
think
yeah.
Even
this
one
is
ready
to
be
merged.
It's
just
that
we
are
waiting
for
forgot.
What?
What
was
it
that
we
were
waiting
for,
but
mostly
the
instrumentations
like
elasticsearch,
must
transit
were
all
unblocked
last
week,
so
there
shouldn't
be
any
dependency
on
activity,
source,
adapter
or
any
internal
classes.
Those
those
should
all
be
cleared
by
now.
B
But
then
the
question
is
like:
how
do
we
like
do
a
release
of
things
from
the
contrib
repo?
So
I
think
we
did
like
a
manual
push
for
wcf
last
week
and
for
this
week,
what
I'm
planning
to
do
is.
I
will
do
a
manual
release
for
each
components
which
were
blocked
previously
on
the
main
ripper,
but
I
want
to
use
this
chance
to
like
discuss
like
what
should
be
the
actual
process
going
forward
like
how
often
should
be
released
and
what
would
be
the
actual
release
process.
B
C
Yeah,
hey
sorry,
I've
been
out
for
the
last
a
couple
of
weeks
and
been
like
involved
in
a
other
project,
so
I
I
did
not
get
a
chance
to
actually
document
the
release
release
process
that
I
followed
for
the
aws
components
so
yeah.
I
can
completely
do
that
this
week,
like
put
down
a
releasing.md.
C
File-
and
I
also
noticed
that
yeah
a
wcf
instrumentation
was
released
and
I
was
thinking
it
would
be
good
to
mark
those
releases
under
the
release
page
on
the
repo
as
well,
so
that
whoever
is
watching
whoever
is
watching.
The
repo
would
get
a
notification
of
the
releases.
C
B
So,
okay
yeah,
I
think.
C
B
Be
just
happy
like,
if
you
have
it
documented
at
least
four
main
repo.
We
have
documented
just
a
matter
of
time
before
we
can
write
some
scripts
to
automate
it,
but
yeah,
and
I
think
I
try
to
reflect
like
michael
did
mention
the
things
which
he
did.
But
I
don't
know
where,
where
I
found
that
yeah.
C
I
think
if
there
was
a
tag
created
then
I
also
saw
that
the
action
was
triggered
for
the
release,
which
is
the
but
it
only
packages
and
uploads
to
my
git.
I
think
he
would
have
done
manual
release
to
new
get
by
manually,
pushing.
C
Yeah,
yes,
so
I
think
that's
a
good
touch
that
we
can
add
to
yeah.
You
can
do.
B
Okay
yeah,
so
just
the
only
action
item
is
like
you
can
do
the
like
steps,
which
you
just
did
for
aws
and
I'll
ask
michael
to
also
review
so
that
we
know
like
at
least
two
persons
have
gone
through
the
process,
and
then
we
can.
We
still
need
to
decide
like
what's
the
frequency
of
release,
because,
unlike
the
main
repo,
this
is
like
individually.
B
Really
so
I
mean,
since
it
is
manual
we
need
to
set
aside,
like
some
expectation
that
we
won't
be
releasing
it
like
every
week,
because
it
involves
some
manual
effort.
So
I
can
try
to
document
that
like
when
you
submit
the
pr
like
we
can
discuss
settings
up
here
like
we
should
set
expectations
that
this
will
be
released
like
on
a
monthly
or
even
like
once
in
two
months
cadence.
C
Oh
come
again
like
so
would
we
be
releasing
if
on
a
regular
basis,
then?
What
about?
If
there
is
no
update
to
the
project,
then
oh
yeah,
if
there
is.
B
B
Because
it
doesn't
look
like
if
each
project
will
have
an
update
like
monthly
or
even
once
in
two
months
or
six
months,
like
after
the
initial
yeah,
I
think
most
of
them
will
get.
C
I
think
what
we
can
discuss
is
that
the
maximum
amount
of
time
that
like
if
there
is
a
change
we
shouldn't
wait
like
six
months
well
between
the
releases
or
so.
If
there
is
no
change,
then
that's
fine.
B
Yeah,
so
if
it's
automated
like
happy
to
do
like
release
or
ad
hoc,
because
that
would
be
just
a
matter
of
pushing
attack
like
people
with
admin,
rights
to
this
report
can
just
push
the
tag
and
trust
will
be
taken
care
of
by
the
github
action.
But
until
then
we
need
to
like
set
expectation
that
it
may
not
be
released
right
away.
B
Yeah,
if
you
can
include
like
some
like
cadence
in
the
releasing
md
or
even
in
the
like
main
readme
file,
that
would
be
right
and
like
while
we
are
doing
that.
Can
you
also
borrow
some
wordings
from
the
collector
control
repo
because
it
has
like
fairly
detailed
note
on
who
owns
it
and
what
should
be
the
process
if
some
components
become
like
unattended,
without
any
approval?
What
would
be
the
policy?
B
So
we
can
just
borrow
things
from
collector
country
repo.
You
probably
have
mentioned
that
sometime
in
the
past.
Yes
yeah,
I
I
still
have
those
action
items.
So
let's
do
that
and
then,
in
the
same
topic
like
we
just
need
to
ask
like
because
we
have
around
eight
projects
right
now.
We
don't
think
we
have
anyone
who
can
be
identified
as
an
owner
for
stackdriver.
B
I
did
search
history
and
it
was
like
shifted
from
the
main
report
to
here.
So
since
there
is
no
owner,
I
don't
know
like
if
this
is
broken
like
there
is
no
one
who
can
fix
it.
So
I
I
want
to
ask
like
if
there
is
any
honor
like
suggest
here
today
right
here,
if
not,
I
would
propose
to
remove
it
because
there
is
a
pr
which
says
this
is
not
supported.
B
Of
course,
this
is
given
that
this
is
not
supported
by
google,
but
I
want
to
make
sure,
like
you
said,
okay,
to
remove
it.
I'm
trying.
D
To
follow
up
on
on
that,
so
it
is
not
supported
by
google
because
there
is
no
official
team
behind
it.
I'm
trying
to
understand
what
we
want.
I
wanted
present
and
community
supported.
D
It's
an
interesting
question.
I
I
think
if
we
will
want
it,
I
will
be
an
owner
for
that
one
specifically
for
other
ones.
I
don't
know
like
for
wcr,
for
instance,
did
we
define
who
will
be
nominated.
B
Yeah
for
all
the
recent
peers,
I've
been
asking,
would
you
be
willing
to
be
a
owner
and
we
got
owners
for
like
grpc
call
or
let's
look
at
the
actual
code
owner
file
and
see
the
one
which
is
missing
an
owner.
So
I
think
it's
track.
Driver
is
missing,
elastic,
search
and
any
difference.
So
I
have
asked
the
pr
author
to
update
the
industry
framework
I'll
do
the
same
for
elasticsearch.
B
Wcf
is
missing
from
here,
so
that
is
another
thing
to
be
added,
so
I
can
ask
the
persons
who
originally
contributed
that
to
see
if
they
are
willing
to
be
listed
as
an
honor
here,
but
the
question
is
like
what,
if
they
say,
no,
they
are
not.
They
are
not
interested.
Should
we
still
keep
it
or
should
we
just
remove
it.
D
B
I
can
do
that
so
for
the
google
one
I
I
will
initially
assume.
That's,
okay,
you
are
the
owner
and
if
I
don't
hear
anything
otherwise,
I
I'll
just
keep
you
as
the
stronger.
D
B
Yeah
but
like
there
may
be
some
reasons
why
people
want
to.
D
B
Okay,
yeah
and
I
want
to
just
share
something
from
the
maintenance
specification
meeting.
Okay,
I
have
a
hard
time
opening
this
link
so
thing
I
mentioned
briefly
last
week
that
there
is
a
overall.
There
are
two
or
three
efforts
being
tracked
in
the
maintenance
meeting.
One
of
them
is
the
instrumentation,
so
people
are
signing
up
to
be
volunteers
for
driving
this
effort.
So
if
anyone
is
interested
in
helping
out,
you
can
either
mention
your
name
or
reach
out.
B
I
think
there
is
a
tag
created
in
in
the
slack
channel
hotel,
hyphen
instrumentation.
So
please
join
that.
So
one
of
the
things
which
is
being
tracked
as
part
of
this
is
ownership
who
would
be
the
owner
for
instrumentation
like
this
part.
B
This
is
where,
like
whatever
we
are
doing
in
the
country,
repo
would
come
into
picture
like
the
ownership
discoverability,
all
those
things
so
I'll
see
if
we
can
get
like
an
official
guidance
from
the
spec
ripper
or
like
gc
about
what's
the
right
way
of
managing
it
looks
like
we
are
doing
it
somewhat
same
as
what
collector
control
is
doing,
but
I
just
don't
know
whether
it's
the
same
as
other
repo.
B
So
if
anyone
else
wants
to
contribute
to
this
effort,
instrumentation
please
enjoy.
I
think
the
best
way
to
get
started
is
join
the
tag
I
mean
slack
channel
called
hotel,
hyphen
instrumentation,
that's
the
best
way
to
get
started,
just
an
fa,
no
specific
action
for
this
repo,
or
this
thing.
B
Okay,
let's
see
what
else
we
yeah,
so
I
I
did
not
have
any
update
on
reorganizing
the
talks.
This
was
something
an
action
item
which
I
took
from
last
week,
which
is
basically
we
are
having
a
lot
of
dogs
getting
started,
but
there
is
no
not
enough
information
on
what
to
do
after
you
get
started
like
it
says,
getting
started
in
five
minutes,
but
that's
it
like,
after
that,
there
is
no
clean
transition
into
the
more
advanced
topics.
B
So
one
of
the
proposal
was
to
do
a
thing
I
mentioned
like
the
blob,
which
gated
in
open,
telemetry
medium
sometime
back,
which
was
titled
beyond
getting
started
so
planning
to
do
like
something
similar.
It
could
be
a
blog
or
it
could
be
just
a
like
dog
things
here
after
getting
started,
we'll
do
a
natural
transition
to
more
advanced
topics
so
that
people
don't
get
lost
after
they're
getting
started.
B
A
Yes,
hi,
I
just
wanted
to
lurk
in
here,
totally
excited
about
the
the
project
and
where
things
are
going,
I
particularly
on
that
topic
of
the
docs.
I
think
there
was
a
github
issue
that
someone
had
raised
in
the
in
the
net
repo.
It
explicitly
says
more
of
like
a
real
world
kind
of
an
example
they
mentioned.
You
know
api
controllers
and
ocelot
and
linking
between
multiple
projects
with
http
client.
A
B
B
I
I
still
need
to
find
the
actual
link
which
has
a
shopping
app,
which
is
built
from
ground
up
using
micro
services,
and
it
has
like
it
can
be
like
a
very
good
example
for
a
real-world
application.
It's
right
now,
instrumented
using
azure,
monitor
slash
azure
application
insights.
We
are
trying
to
see
if
we
can
modify
that
entire
e-shop
on
containers,
which
is
a
good
example,
very
complex
one
to
use
or
switch
to
open
telemetry.
B
I
think
allen
did
an
initial
pr.
I
mean,
like
allen,
is
already
in
the
connect
ellen.
Did
you
like
actually
submit
a
pr,
or
you
were
planning
to
forget
assistant.
E
B
B
Basically,
there
is
a
lot
of
rewrite
occurring
in
the
dot
net
side,
which
is
to
add
documentation
about
all
the
recent
changes
in
diagnostics
like
activity
source,
all
those
things,
but
as
soon
as
that
is
done,
we
should
be
able
to
remove
a
lot
of
documentation
from
our
main
repo,
because
we
are
pretty
much
documenting
on
behalf
of
dotnet.
Here
like
we
are
specifically
like.
If
you
could
look
look
at
the
api,
we
are
documenting
the
dot
net
api
here
at
the
end
of
the
dot
net
teams
update.
B
We
should
be
able
to
simply
link
from
our
repo
to
the
dot
net
repo
part
one
and
second,
is
I'm
hoping
that
they
will
modify
the
actual
distributed
application
with
the
knight
five
based
approach,
which
is
activity
source,
like
maybe
we'll,
have
to
help
like
alain,
and
I
will
be
doing
some
work
to
make
it
happen.
And
after
that
we
can
get
rid
of
all
the
like
simple
examples.
B
From
this
repo,
I
mean
we
can
keep
the
very
basic
console
example,
but
everything
else
which,
like
microservice
and
all
they
are
very
close
to
real
world,
but
not
as
good
as
these
guys
so
long
time.
We'll
just
remove
everything
and
put
it
on
like
dotnet
architecture
to
design
or
keep
maintain
these
temporary
or
maintain
these
real
world
applications.
So
you
can
just
focus
on
shipping
the
api
and
sdk.
E
Yeah
and
and
this
week
I
spent
I
plan
to
spend
another
afternoon
just
kind
of
getting
all
the
services
to
light
up
with
open,
telemetry
and
and
I'll
I'll
push
an
update
in
the
slack
channel
there.
Just
when
I've
got
it
flushed
out
a
little
bit
more
and
maybe
with
some
instructions,
and
if
anybody
wants
to
give
it
a
shot,
that'd
be
great
feedback,
whatever
yeah.
B
B
Yeah
interesting,
interesting
thought
yeah.
I
saw
that
too.
I'm
pretty
sure
like
if
it's
already
like.
If
the
server
side
is
instrumented
with
application
insights,
I
I
would
assume
that
even
the
client
side
would
be
instrumented
with
app
insight,
so
but
that's
something
which
we
can
figure
out.
As
we
I
mean
it's
fairly
big.
It's
not
like.
B
We
can
finish
it
in
one
week
it
looks
like
there
are
like
several
apps
yeah,
let's
work
on
it
like
please
give
me
like
another
day
or
two
to
confirm
whether
they
have
like
any
other
plans
or
maybe
like
we'll,
get
some
support
from
the
owners
of
this
repo
itself
to
update,
rather
than
be
doing
the
job.
So
I'll
get
back
as
soon
as
I
hear
from
them,
cool,
yeah
and
I'll.
Do
a
draft
like
this
is
what
I
promised
for
the
dogs
part
I'll.
B
Do
a
sorry
I'll
do
a
draft
about
what
the
overall
dock
would
look
like
like
here
like
after
getting
standard.
What
next
I'll
do
a
draft
as
soon
as
possible,
so
we
can
get
some
feedback
and
see
if
we
need
to
use
a
different
approach
or
the
one
which
I'm
proposing
is
okay,.
B
A
Element
yeah,
I'm
using
the
whatever
version
it
is
the
old
one
and
when
it
was
still
using
tracing
and
active
spans,
I
forget
what
the
version
number
that
is,
it's
like
08,
or
something
like
that
and
yeah.
So
I'm
using
it
in
an
api
project
and
on
ocelot
and
passing
through
that
load,
balancer.
B
If
there
is
no
other
topic,
there
are
no
other
topics.
I
just
want
to
briefly
discuss
some
open
tiers,
so
I'll
just
ask
around.
If
you
have
any
pending
questions.
B
Okay,
yeah
I'll
just
open
a
couple
of
pr's
just
to
make
sure
everyone
get
a
chance
to
look
at
it.
So
michael
is
not
in
this
meeting
today,
so
I
can
briefly
explain
what
this
is
attempting
to
do.
There
has
been
a
lot
of
ask
recently
about
converting
from
one
signal
to
another,
so
this
one
is
specifically
converting
from
logging
to
tracing.
So
this
is
something
feature
which
existed
in
the
open
tracing
world,
where
an
I-logger
based
login
messages
would
be
attached
to
a
active
span.
B
B
If
yes
convert
the
log
messages
or
attach
the
log
message
as
a
activity
event,
that's
one
way
of
thinking
of
it
and
then
there
is
a
opposite
direction,
which
is
you
have
activity
and
it
has
activity
even
and
you
don't
want
your
tracing
back
in
to
take
the
log,
so
you
want
to
send
the
activity
events
as
long
messages
to
your
logging
back
end
and
of
course
there
are
other
combinations
possible
like
converting
traces
into
metrics.
B
B
So
I
encourage
everyone
to
take
a
look
at
this
and
see
if
you
have
any
comments,
so
I
think
I
try
to
put
this
initially
as
a
like
a
separate
project,
not
part
of
the
core
sdk,
we'll
figure
out
a
different
name.
This
is
too
generic
now,
but
there
will
be
I
mean.
Basically,
it
will
be
a
separate
thing
from
the
original
sdk,
but
if
there
is
enough
interest
in
this,
we'll
probably
make
it
as
part
of
the
core
sdk
itself.
It's
very
small
like
there
is
only
like
one
like
really
like.
B
There
is
one
class
which
just
converts
the
log
record
and
activity
event.
Everything
else
here
is
just
like
internal
implementation,
so,
depending
on
the
interest,
we
could
make
it
as
part
of
the
main
sdk
itself,
but
to
begin
with
we'll
keep
it
a
separate
package
and
we'll
keep
it
as
a
pre-release,
so
that
we'll
have
enough
time
to
like
sort
out
the
fine
details.
So
please
take
a
look
and
share
your
comment
on
this
pr.
While
doing
this,
we
are
like
we
actually
improved
logging
quite
a
lot,
so
it's
already
merged.
B
B
There
is
another
one
which
was
briefly
discussed
last
week
about
dependency
injection.
I
think
it's,
oh
this
one
and
one
eight,
eight
nine.
So
together,
these
two
are
like
two
attempts
at
improving
the
configuration
story.
So
I
mentioned
last
week
that
there
is
a
strong
interest
in
making
the
overall
onboarding
experience
easier.
B
So
from
this
dot
net
sig,
we
are
mostly
targeting
asp.net
core
scenarios.
It's
the
most
common
application
type
these
days
so
but,
unfortunately,
our
support
for
asp.net
core
configuration
is
not
very
good.
B
So
these
two
are
like
attempts
at
fixing
it
it's
much
more
trickier
than
expected,
because
we
don't
want
to
take
a
dependency
on
microsoft,
extensions.da
or
hosting
into
the
main
sdk.
We
want
to
restrict
that
dependency
to
only
this
package
and,
unfortunately,
certain
classes
like
eye
options
are
not
part
of
the
framework
library.
It
is
only
part
of
open,
sorry,
microsoft,
extensions.da.
B
So
all
this
pr
is
doing
is
working
around
these
limitations
and
still
offering
a
good
experience
for
onboarding.
So
please
take
a
look,
and
you
can
see
like
the
examples
are
already
here
like
one
example
is,
if
you
want
to
add
eager
exporter-
and
you
want
to
configure
it,
you
can
do
like,
I
mean,
add
one
place
and
you
can
configure
either
exporter
from
your
configuration.
B
It
can
be
like
in
different
places,
because,
right
now,
this
option
is
not
there
like
you
have
to.
You,
have
to
have
the
logic
of
reading
from
config
and
configuring.
The
eager
exporter
option
everything
in
the
single
line,
so
this
is
an
attempt
to
fix
that.
It's
addressing
like
several,
probably
like
more
than
one
near
plus
old
issue.
So
please
take
a
look
and
there
are
like
two
options:
eric
has
a
different,
slightly
different
approach
of
solving
it.
B
I
didn't
have
the
chance
to
fully
look
at
it,
but
if
you
can
look
at
it,
that
would
be
great.
Just
keeping
in
mind
like
why
it
is
a
big
or
complex
project
is
because
the
main
goal
is
to
avoid
depending
adding
a
dependency
on
microsoft,
extension
story
da
package
and
the
core
sdk.
So
that's
what
all
this
pr
is
trying
to
circumvent,
hey.
E
B
I
mean
that
would
be,
let's
take
a
look
here.
We
intentionally
depend
on
logging
and
if
that
is
indirectly
bringing
us
extensions,
dot
d
a
so,
but
you.
B
Which
is
interesting
and
the
configuration
yeah
there
was
some
open
issues
about
this
earlier
as
well.
Let's
see
if
I
can
get
to
the
nuclear
yeah
yeah.
If,
if
you
already.
C
B
A
dependency
then,
like
the
point,
is
like
already
gone,
like
yeah
I'll,
see
like
how
can
leverage
this
fact,
because
we
have
a
dependency
and
what
was
the
version
which
we
depend
on.
B
My
searching
skills
are
not
true
supposed
to
show
yeah,
okay,
okay,
it
says
like
minimum
of
five
up
to
six
okay
yeah.
This
is
interesting.
Like
this
means
we
already
have
a
dependency
on
the
da
anyway,
we
already
broke
the
like
premise
on
which
we
were
working
right
yeah.
I
didn't
notice
that
at
first
yeah
we
found
a
lot
of
interesting
things
about
working
on
the
other
pr's,
like
one
of
them
being
the
fact
that
the
iservice
collection-
sorry,
I
think
I
service
provider,
is
like
not
really
a
part
of
microsoft
extension.
B
It
is
part
of
the
framework,
so
that
allowed
some
optimization
but
yeah.
This
should
be
like
it
should
try
to.
It
should
make
things
more
easier.
I'm
still
not
sure
if
that
eye
options
is
something
which
we
already
use
here
so
eye
options
is
other
thing
which
we
want
to
get
a
hold
off.
B
Yeah
we
do
have
eye
options
here
so
which
means
we
already
have
the
dependency
yeah.
So
let
me
comment
on
this
vr,
because
if
you
already
have
dependency
for
some
other
reason,
then
we
might
very
well
use
that
some
other
aspect
like
I
think
I
wanted
to
share
that
as
well.
So
in
the
comments
yeah.
B
So
all
these,
for
example,
this
is
jaeger,
and
I
mean
one
of
the
initial
assumption
was
that,
like
jager
is
able
to
do
something
like
eye
options
of
options,
options
of
jaeger
exporter
option
we
thought
actually,
depending
on
I
options,
because
this
is
coming
from
the
microsoft
extensions
package,
so
that
problem
is
like
mostly
sold,
so
this
might
make
things
much
more
simpler,
yeah
thanks
ellen
for
like
bringing
our
attention
to
that.
So
this
should
be
a
good
discussion
by
next
week
when
we
get
some
more
time
to
work
on
it.
B
Right,
I
think
there
was
oh
yeah.
These
are
the
three
main
peers
which
were
like
fairly
big,
so
I
wanted
to
get
more
people
to
look
at,
but
on
the
topic
of
pr's,
there
are
like
quite
a
lot
of
peers.
B
I've
been
trying
to
clean
up
some
of
them,
so
if
you
are
like
other
of
one
of
the
peers
in
the
like
which
are
not
yet
merged,
please
indicate
if
you
are
actively
working
on
it
or
is
it
okay
to
be
close,
because
I
don't
want
to
review
a
pr
which
is
not
being
actively
work
on.
So
if
you
are
actively
working,
please
merge
from
the
latest
main
and
just
mention
like
hey.
This
is
ready
for
review,
so
we
can
come
back
to
it
and
take
a
look.
B
B
Okay,
yeah,
no
other
topics
left.
So
if
there
are
any
questions
we
can
take
it
now.
Otherwise,
we'll
see
you
all
next
week.
B
Just
to
remind
everyone
that
there
is
some
work
going
on
in
the
metrics
sake,
which
I
hope
that
we
will
get
like
some
bits
from
the
dot
net
one
time
in
the
next
two
three
weeks,
so
we'll
actually
start
doing
some
work
in
the
matrix
branch
at
that
time
and
victor
from
he's
already
in
this
he's
already
working
very
closely
with
the
dotnet
team
on
the
prototype.
B
So
as
mentioned
last
week,
if
you
are
interested
in
joining
this
effort,
please
ping
us
in
jitter
or
sorry
in
slack,
and
we
can
get
you
in
the
right
group
of
people.
As
of
now,
it's
a
dotnet
team
and
victor
from
this
group
is
doing
the
prototype.
B
B
All
right,
I
think
we
can
end
a
bit
early
today.
If
you
know
the
topics,
we
can
see
you
all
on
next
week.
Once
again,
there
are
some
messages:
okay,
yeah!
Thank
you.
Everyone
we'll
see
you
all
next
week,
bye,
bye,.
F
Thanks
awesome,
thank
you.
Awesome
cj.
I
have
one
of
the
outstanding
prs,
but
I
think
I'm
just
gonna
narrow
the
scope
and
make
it
sound.
It's
easily
passable
yeah
just.
B
Mention
like
one
of
us
in
the
pr,
so
we
get
notified
because
there
are
too
many
of
them
to
look
at.
So
we
just
want
to
prioritize
so.