►
From YouTube: 2023-03-14 meeting
Description
Instrumentation: Messaging
A
A
B
B
D
D
B
D
B
B
B
I'm,
not
sure
if
we
just
want
to
like
do
a
quick
sync
and
maybe
maybe
talk
on
the
the
channel
to
kind
of
wrap
some
things
up.
But
one
thing
I
was
trying
to
kind
of
like
at
least
just
discuss
is
we
will
have
access
to
the
community
account
soonish,
we're
still
waiting
for
the
email
to
be
sent
to
Anthony,
Alex
and
myself
to
get
credentials
or
whatever,
but
I'm
kind
of
thinking
like
what?
B
What
PRS
do
we
need
to
do
in
order
to
you
know
a
get
the
community
layers
being
published
and
B
to
like
update
the
layers
to
whatever
spec
changes
we
made
like
the
cloud
resource
ID
for
instance,
and
then
trying
to
kind
of
tentatively
Target,
maybe
kubecon
for
a
lot
of
this
work
to
be
done.
Just
because
you
know
it's
about
a
month
away.
We
already
have
all
the
spec
PRS
merged,
so
it's
really
just
get
the
account
get
the
layers
published
and
then
you
know
kind
of
go
from
there.
But
what.
D
Yeah,
so
regarding
the
publishing
the
layers,
I
think
right
now,
the
way
the
ADOT
is
doing,
we
can
use
most
or
a
part
of
it
like
so,
basically
what
we
do
is
we
use
shell
script
to
push
that
to
S3
bucket
and
from
S3
to
the
layer.
That's
how
it's
basically
done
right
now
at
the
moment,
but
I
think
I
think
I'm,
confident
that
we
can
use
at
least
half
our
three-fourth
of
the
way
that
current
header
laminated
release
process
is
going
on.
Mm-Hmm,
I.
D
Yeah
yeah,
that's
my
one
of
my
next
question
as
well,
so
I
think
right
now
we
don't
have
any
integration,
testing
or
right,
but
yeah.
It
would
be
really
interesting
and
I
think
it
could
also
make
things
simple
for
adult
as
well
like
having
tests
sitting
upside,
although
most
of
the
code
has
been
sitting
up
in
the
Upstream
a
few
minutes
since
we
movement
but
yeah
I-
think
the
validation
I,
think
that
would
be
the
challenging
task
for
us
to
see.
D
D
C
A
E
D
Right
and
also
talking
on
the
contest
regarding
the
CI
I
think
our
team
is
also
making
efforts
to
paste
the
Matrix
as
well
right
now,
we
are
only
testing
traces.
Yes,
at
the
moment,
yeah
we're
also
looking
for
working
on
to
test
the
Matrix
and
standardize
the
test
Downstream
and,
with
from
there
dot
I'll,
be
happy
to
check
with
the
team
to
see
how
we
can
be
Cascade
that
to
Upstream,
because
we
are
thinking
of
having
a
CI
in
Upstream.
B
D
A
B
Yeah,
whatever
conversation
yeah,
I,
guess
we'll
we'll
have
the
account
within
two
weeks,
like
I
said
so,
I
would
like
to
be
able
to
hit
the
ground
running
to
an
extent,
or
at
least
be
able
to
start
running
through
like
some
of
these
issues
and
importing
them
over.
So
you
don't
get
hung
up
too
long.
D
B
Awesome,
that's
great,
and
so
we'll
talk
about
this
again
at
I.
Think
our
next
week
meeting
and
hopefully
more
people
are
able
to
attend.
But
if
people
have
concerns
about
the
keep
con
timeline,
I
mean
feel
free
to.
Let
me
know-
and
we
can
you
know
each
other
outside,
but
I
think
we
we
should.
We
should
be
on
track
for
right
now,
I'm,
not
seeing
anything
super
flashing,
I
guess.
B
C
B
B
B
We'll
get
that
figured
out,
I
was
hopeful,
you
know,
that's
the
count
thing,
that's
just
when
I
know
it's
like
just
wait
for
weeks
and
then
you
get
one
message
back
and
then
you
wait
for
a
week,
so
yeah
agreed
I
was
hopeful.
We'd
have
it
sooner
and
actually
have
like
the
implementation
discussion.
But
here
we
are
cool,
so
you
added
these
two
items.
Tristan.
Do
you
want
to
talk
about
these
this
week
or
you
may
want
to
talk
about
it
more
in
depth
next
week,
totally.
C
C
I
mean
the
the
first
one
is
just
like.
We
Splunk
are
very
interested
in
getting
this
one
in
because
we
do
have
some
execution
API
stuff
or
what
was
that
extension
API
stuff
whatever
it
is,
the
previous
to
the
Telemetry
API
that
we
use
and
we'd
like
to
get
it
replaced
with
Telemetry
API,
and
this
has
been
now
sitting
here
after
being
approved
by
I.
Guess
it's
only
approved
by
us
as
well
so
but
get
more
eyes
on
it
and
we're
happy
to
help
more.
B
It's
languished,
I
bet,
it's
probably
fair,
to
say,
yeah,
okay,
well,
I
was
having
four.
We
could
use
today,
we'll
probably
end
up
using
next
week
as
more
of
a
working
session
to
triage
some
of
these
open
PRS,
because
we
also
have
like
a
python
just
like
adding
to
the
support.
Matrix
was
never
merged
and
then
we
have
the
Java
thread
PRS
as
well.
So
let's
talk
about
this
again
next
week,
though
I
think
getting
like
Alex
and
Anthony's
attention
will
probably
be
helpful
there.
B
A
C
B
A
B
C
A
A
E
Yeah
totally
yeah
I
need
to
check
it
out
again.
I
was
reviewing
that
Friday.
So
ever
since
that
day,
I
haven't
reviewed
this
yeah.
That's
a
good
reminder.
Basically,
this
is
breaking
you
know
semantic
comprehensions
of
facto,
and
people
cannot
update
the
latest
yeah.
So
what
do
a
review
of
these
today
before
the
end
of
the
day,
because
it's
very
urgent,
yeah,
okay,.
C
E
E
B
B
Cool
well
just
a
quick
review,
I
guess
of
tracking
items
for
the
cubecon
release,
so
we
have
Community
releases,
we're
tracking
and
the
release
tooling
kind
of,
underneath
that
we
need
to
finish
our
initial
group
of
spec
PRS,
which
are
mostly
done
or
in
progress.
At
this
point,
we
need
to
open
and
kind
of
finish
the
second
group
of
spec
PRS
around
the
spec
changes,
and
then
we
need
to
produce
some
basic,
just
Lambda,
open,
symmetry.io,
docs
or
just
representation,
or
something
like
that
that
we
can
iterate
on.
B
Good
from
you
guys
cool,
well
we're
gonna,
keep
this
meeting
pretty
short,
but
Mike
I
know
you
joined
kind
of
late.
We
don't
have
a
huge
amount
of
war
in
today,
so
I'm
basically
going
to
be
discussing
a
lot
of
topics
in
depth
next
week,
but
kindness
just
got
disgusting
like
the
overall
project
road
map.
Do
you
have
any
specific
topics
or
feedback
for
us
from
the
field?