►
From YouTube: 2022-07-18 meeting
Description
Open Telemetry Meeting 1's Personal Meeting Room
A
B
C
B
Okay,
cool,
I
think
I
think
we
have
a
good
amount
of
people
right
now:
okay,
hey
ollie,
jorge
great,
so
we
have
a
pretty
packed
agenda
today.
We're
gonna,
discuss
our
kubernetes
implementation,
ziki
or
fat
sheet
has
also
reached
out
to
me
about
being
an
approver.
I
like
to
discuss
that
a
little
bit
oscar
has
volunteered
to
take
up
kind
of
creating
some
sort
of
client
front-end
approach,
and
I
think
it'd
be
really
helpful
for
him.
B
I
think
he
has
a
potential
plan
he'd
like
to
discuss,
but
also
some
feedback
from
the
group.
I
think
that
would
be
really
useful
and
then,
if
we
get
to
it,
I
really
like
to
discuss
kind
of
how
we
can
mature
our
metric
story
and
actually
use
it
to
help
with
our
own
debugging,
and
things
like
that.
I
think
we
have
a
very
kind
of
basic
kind
of
use
case
today
and
then
there's
a
couple
other
items.
B
No
cool:
well,
we
can
start
with
the
kubernetes
implementation.
Then
dinesh.
Do
you
want
to
give
us
an
update
on
like
where
you're
at
today,
if
there's
any
particular
blockers
and
then
like
open
questions.
C
Yeah
sure
so
whatever
I
did
was
rather
very
simple,
all
the
k-8
files.
I
think
someone
reached
out
to
me
on
the
slack
channel.
Let
me
see
the
name
reached
out
to
me
on
the
slack
channel
that
they
wanted.
They
were
in
the
process
of
doing
health
charts.
C
My
implementation
was
pretty
straight
like
it's
not
a
helm
chart
it's
like
all
the
k8
files
it
works.
I've
been
running
it
in
a
data
dock
infrastructure,
I'm
from
data
for
people
who
I'm
from
dog-
and
I
have
been
running
it
in
that
at
all
and
seems
to
be
working
so
far,
good,
I'm
all
open.
If
you
want
to
do
health
chart
where
no
objections
to.
B
Yeah,
giuliano
and
pierre,
I'm
kind
of
curious
of
your
opinion
here
I
think
ping
han
has
been
working
on
some
sort
of
helm
chart,
but
I'm
not
super
familiar
with
kubernetes.
So
do
you
have
a
preference
on
how
we
get
this
implemented.
E
I
I
think
we
should
have
a
helmet
chart.
Yes,
we
should
have
a
way
to
one
line,
install
the
whole
thing
with
variability
and
what
I
mean
by
that
is
somebody
might
say
I
need
it
to
be.
You
know,
maybe
we
find
out
that
on
this
kind
of
flavor
of
kubernetes
or
or
maybe
they
want
to
change
that
at
the
back
end
or
not
have
all
the
services.
This
thing
is
getting
pretty
big
and
I
have
a
feeling
some
people
might
say.
I
don't
care
about
the
metrics.
E
A
F
F
Because
we,
we
have
a
service
that
that
is
in
elixir
and
airline
is
a
future
flight
service
that
we
are
not
using
at
the
moment.
So
for
scenarios
like
the
the
one
that
pr
just
described
like
hey,
I
just
wanna
see
traces
and
I
don't
want
to
see
metrics.
We
could
have
environment
variable
in
this
feature.
F
I
think
it
helps
a
lot,
but
I
also
think
that
it
will
add
something
to
our
cluster.
So
we
know
that
this
sample
is
already
big
and
then
on
top
of
it
we
will
have
to
install
helm
now
and
then
I'm
just
thinking
about
the
amount
of
knowledge
that
whoever
is
starting
with
the
sample
will
have
to
know
to
have
to
simply
start
the
sample.
You
know
just
that.
C
E
Yeah
I
agree
debugging
helm.
Is
this
pain
in
the
butt?
There's
no
clean
way
to
do
it
you,
you
could
easily
debug
a
single
thing
at
a
time
I
I
was
thinking
more
about
not
just
using
future
flights
to
say
I
don't
want
to
see
metrics,
but
maybe,
if
I
I
don't
want
to
see
magics,
I
don't
want
to
deploy
prometheus
and
grafana
either.
I
just
wanted
to
deploy
the
jaeger
piece
so.
E
Do
we
need
to
have
helm
ready
for
a
version?
One
release-
I
don't
know,
but
I
think
we
should
think
about
getting
helm
put
in
place
to
ease
deployment
for
those
who
are
familiar
with
kubernetes,
I
think,
generally
speaking,
helm
is,
is
not
far
away
from
it
and
running
a
helm.
Install
something
is,
is
pretty
easy
for
them
to
do
rather
than
having
to
perhaps
modify
the
environment
variable
for
a
bunch
of
gmo
files
and
which
would
be
much
more
problematic.
B
That's
a
good
good
discussion
on
it.
Then
we'll
wait
for
ping
hon
to
finish
that
home
chart
then,
and
then
we
can
talk
about
also
introducing
the
kubernetes
sooner.
If
we
want
to
yep.
Okay,
quick,
quick
next
item,
so
y'all
may
have
seen
him
around
the
repo
his
name's
nikki,
zao
or
fat
sheep.
I
think
it's.
His
username
makes
me
kind
of
feel
like
I'm
on
xbox
saying
that,
but
he
reached
out
to
me
as
interested
in
being
an
approver.
B
B
Okay.
So
for
the
next
item
I
guess
kind
of
small
segue.
We
also
have
ken
here
from
trace
test,
and
he
has,
I
think,
three
engineers
on
the
call-
hey
jorge
hey
mathias,
of
course,
oscar
as
well
and
they're,
trying
to
get
more
involved
in
the
demo
effort.
So
I
think
oscar
is
potentially
going
to
pick
up
the
front
end
kind
of
overall
refresh,
but
I'm
not
sure
if
jorge
and
matthias
are
going
to
contribute
to
that
or
they're
going
to
work
on
the
maturing
the
trace's
story
as
well.
B
I
kind
of
wanted
to
say,
like
they're,
making
kind
of
a
big
big
investment
in
our
group,
and
we
really
appreciate
that
king
can
you
maybe
give
us
a
current
state?
Besides
the
item
oscar
picked
up.
A
That's
the
only
thing
we
picked
up
so
far:
mathis
can
do
both
front-end
and
back-end
stuff,
but
the
problem
primarily
would
probably
work
back
in
yeah
work.
Okay,
so.
D
I
think
one
of
the
issues
that
we
have
on
our
board
is
ready
to
bring
the
demo
up
to
our
ecosystem
and
we're
using
helm
chart.
So
if
you
want
a
hand,
you
want
to
do
some
help
on
on
those
those
hamstrings,
I
think
matthews
or
someone
from
promoting
can
come
help
with
that.
B
Okay,
awesome
yeah
I'll
I'll
reach
out
to
pinghang
and
mention
that
you
can
help
out
on
that
as
well.
That'd
be
a
really.
A
And
just
a
little
background,
we
were
building
our
own
demo
app
and
and
then,
when
I
met
you
in
austin,
I
was
like
all
right.
This
makes
no
sense.
Yeah.
B
That's
all
I
saw
y'all's
pokemon
app,
that's
kind
of
funny,
okay,
anyways,
so
oscar.
Can
you
maybe
give
us
kind
of
your
rough,
like
I
guess,
vision
of
what
you
think
this
front-end
client
would
be,
or
maybe
kind
of
initial
thoughts.
D
Yeah,
so
I
I
will
give
you
a
little
bit
of
context.
So
last
week
I
was
working
on
a
plc
for
our
team
that
was
basically
instrumenting,
a
front-end
piece
for
or
pokemon
api
that
we
use
for
a
testing
trace
test.
We
did
so
based
on
that.
D
I
was
just
looking
at
the
documentation
up
until
about
open
telemetry
called
current
instrument,
the
front
end
and
react
application
that
kind
of
stuff,
and
so
I
was
looking
at
the
code,
the
code
that
we
have
on
this
demo,
and
I
saw
that
the
front
end
piece
is
a
go
application
that
is
just
printing
the
html
right.
So
I
think
you
want
to
have
a
demo
app
that
can
help
other
people
to
start
instrumenting
the
front
end.
It
would
be
good
to
have
some
something
that
is
most
widely
used
right.
D
So
my
proposal
here
is
to
move
the
front
end
piece
to
react
and
something
like
clear
react
up.
That
is
also
kind
of
the
the
mostly
the
widely
used
framework
or
scaffolding
for
for
react,
applications
and
from
there
we
can
start
thinking
about
okay,
what
type
of
architecture
or
patterns
we
want
to
use,
how
we
want
to
start
instrumenting
the
different
pieces
of
the
app.
D
I
know
that
we
open
the
metric
has
some
auto
instrumentation
tools
that
we
can
use,
but
maybe
we
can
extend
those
to
have
more
specific
as
well
for
for
things
that
want
more
control
over
the
the
specific
fans
that
I
want
to
create
on
the
front
end.
Another
one
key
point
is
that
I
feel
that
the
examples
from
connecting
the
front
end
to
the
collector
might
be
a
little
bit
confusing.
I
found
that
a
little
bit
confusing,
so
we
need
to.
D
A
E
Okay,
which
is
good
because
we
use
go
in
two
different
services.
So
that's
okay,
to
replace
this
with
something
else.
E
A
E
A
D
B
D
Yeah,
I'm
I'm
thinking
of
using
typescript.
E
D
Yeah,
and
so
if
there
is
a
create
react
app,
we
can
just
containerize
it
and
use
yeah
use
the
same
pattern
for
kubernetes
that
we
have
for
the
rest
of
the
application.
E
I
like
the
typescript
example,
because
it
just
reuses
the
javascript
sdk,
but
in
the
typescript
flavor,
so
we
would
have
code
examples
for
that
as
well
that
we
could
share
with
others.
E
So
I
I
see
a
lot
of
benefit
of
this
for
sure
I
you
know
I'm
fearful
of
level
of
effort
required,
but
net
new
contributors
doing.
It
would
certainly
help.
D
A
E
D
Yes,
yeah,
I
actually,
I
used
it
last
week,
so
I
did
approval
concert
for
for
our
team
around
okay.
B
E
Yeah
yeah,
I
hated
it
it
sucks,
especially
when
it
comes
to
instrumenting
the
front
end.
What
we
had
to
do
was
do
a
separate
node
build
and
it
was.
It
was
just
ugly.
This
would
all
be
one
build
now
to
take
care
of
it.
Also
it
would.
It
would
simplify
quite
a
few
things.
We
still
have
a
challenge
to
figuring
out.
I
I
think
best
practices
is.
E
D
Exactly
so
that
that's
the
exact
same
issue
that
I
had
last
week
when
trying
to
implement
something,
so
I
ended
up
using
the
ship
king
endpoint
for
jaeger
that
had
scorched
enabled
so
that
those
sort
of
things
is
something
that
we
can
also
kind
of
showcase
on
this
demo
right
for
people
to.
I
want
to
start
using
the
front
end
too.
E
Of
course
you
can
enable
course
with
otlp.
You
just
have
to
enable
the
options
for
it.
I
could
share
those
options
with
you
inside
of
the
pr
or
or
dig
them
up
for
you,
but
otlp
does
support
cores
to
send
it.
You
know
we
were
talking
about
kubernetes
earlier
as
well.
This
would
require
you
to
set
up
a
different
kind
of
service
which
would
receive
from
the
front
end,
so
this
would
have
to
be
a
load
balance
or
an
ingress
service
to
take
in
the
data
as
well
feed
this
into
the
the
optometry
collector.
E
E
He'd
say
the
same
thing
he's
hearing
it
and
just
there's
a
lot
to
that
challenge
that
we
need
to
make
sure
we
we
capture,
we'll,
probably
need
a
set
of
issues
to
make
sure
we
have
this
and
working
through
kubernetes
for
sure,
because
it's
gonna,
it's
gonna
require
additional
services
to
be
done.
F
No
just
I
was
while
oscar
was
mentioning.
I
was
checking
the
desired
service
map
and
we
actually
have
three
searches
in
go,
so
that's
good
that
we
will
get
rid
of
one
of
them.
So
if
we
remove
front-end,
we
will
still
have
checkout
service
and
the
product
product
catalog
service,
so
that
that's
fine,
that's
awesome!
Actually,
nice
one.
B
Pierre,
I
think
you've
been
on
vacation.
Do
you
have
any
updates
on
like
a
standard
set
of
future
flags,
or
is
that
something
you're
looking
to
pick
up
kind
of
going
forward.
E
B
Cool,
I
think
you
have
a
pr-
that's
only
blocked
by
the
branch
being
out
of
date.
So
if
you
go
ahead
and
update
that
we'll
get
it
merged
face
up
and
then
oscar
there's
there's
also
another
maintainer
austin
and
he's
very
involved
on,
like
the
open,
telemetry
website,
side
of
things
as
well,
and
so
I'm
sure
he'll
have
a
strong
opinion,
at
least
on
some
of
the
design
aspects
of
the
front
end
and
things.
B
So
I
can
introduce
you
to
and
make
sure
you
get
some
feedback
there
and
then
maybe
you
potentially
reuse,
some
of
like
the
html
and
css
kind
of
like
elements
from
the
the
current
website.
D
Yeah,
that's
great
yeah
I
was.
I
was
going
to
ask
that
like
styles
color,
that
kind
of
stuff.
B
Yeah
you
connected
for
sure,
and
then
the
next
item
we
had
was
around
metric
feature
maturity.
So
net
has
recently
added
like
some
sort
of
the
concept,
essentially
a
standard
metrics,
I
think,
into
the
runtime
itself.
I
was
hoping,
michael
or
cjo
would
have
been
here
to
talk
about
it.
I
don't
have
the
link
to
the
the
pr
on
my
mac
right
now,
so
unfortunately,
I
can't
share
the
information
I'll
go
I'll
put
in
the
chat
window
or
play
on
slack
later
today,
but
I
just
kind
of
wanted.
B
I
guess
to
open
the
floor
to
do.
We
have
any
metrics.
You
want
to
go
ahead
and
or
implement
early
on,
so
to
help
our
own
debuggy
and
dinesh.
I
remember
you
were
mentioning
like
do.
We
have
any
metrics
today
that
we
can
use
to
help
me
implement
kubernetes
and
we
didn't
really
have
a
great
answer
for
you.
So
did
you
notice
any
gaps
or
potential?
You
know
things
we
could
do
explore.
C
That
yeah,
I
created
a
pr
which
was
a
bug
fix
in
the
front
end
like
once
I
made
that
bug
fix.
I
was
able
to
see
the
metrics
coming
from
the
front
and
I
put
in
the
pr
there
and
yeah
once
I
was
running
in
kubernetes,
so
I
was
able
to
connect
the
kubernetes
metrics
but
yeah.
Those
were
the
only
things
which
I
had.
B
Okay
and
I
think
in
terms
of
metrics,
we
really
only
have
the
front
end
instrumented
today.
Is
there
a
particular
order?
We
want
to
go
and
like
prioritize
these
services?
I
don't
really
have
a
sense
of
it
today,
juliana,
maybe
from
your
experience
with
the
demo,
where
do
you
think
kind
of
like
the
hot
pass
necessarily
might
be.
B
I'm
as
up
to
date
on
the
instrumentation
libraries
for
metrics,
I
know
like
the
specs
for
a
lot
of
the
instrumentation
libraries
still
aren't
confirmed.
Do
we
think
or
does
anyone
have
a
sense
if
they're
at
the
maturity
level,
we
should
lean
on
those
first
or
should
we
default,
maybe
to
manual
instrumentation.
E
Metrics
for
you
from
the
runtime
itself,
I
know
there's
quite
a
few
go
style
things
like
number
routines
and
a
couple
other
things
I
don't
know
if
that's
part
of
any
kind
of
auto
instrumentation
kit.
Yet
in
go
sdk.
B
Yeah,
I
wonder
if
every
language
even
has
all
the
the
instruments
available
to
them.
I
think
like.net
doesn't
have
complete
instrument
coverage,
yet
we're
missing
like
the
up
down
counter
or
something
like
that,
so
we
will
be
potentially
limited
on
what
instruments
per
language
just
depending
on
where,
like
the
api
or
the
sdk,
is
today,
I
think
in
the
requirements
we
actually
captured,
which
languages
have
metric
maturity.
I
think
it's
like
five
or
six
right
now
out
of
out
of
the
10.,
so
I'll
make
a
note
to
track
those
down.
E
E
E
B
E
Like
a
lot
of
environments,
they
have
a
runtime
associated
with
them.
Even
go
has
a
small
aspect
of
a
run
time
when
it
kicks
off.
Certainly
in
java.net,
there's,
there's
the
the
jvm
and
even
a
node.
There
are
a
certain
set
of
metrics
admitted
by
all
these
runtimes,
and
I
don't
know
where
the
various
sdk
contributors
you
know
where
their
plans
are
to
add
these
that's
kind
of
an
auto
instrumentated
thing
that
you
just
three
lines
of
code.
All
of
a
sudden.
B
B
Gary
are
you
familiar
with
like
the
rust
story
at
all?
I
know
you've
been
involved
in
that
community.
What's
that,
what's
your
sense
on
the
metrics
there.
C
Yeah
I
actually
came
in
in
part
because
I
implemented
an
environment
variable
that
I
remember
you
had
asked
for
when
we
were
instrumenting
this
shipping
service
there's
a
lot
of
missing
parts
to
the
metrics
implementation
right
now
I
know
that
when
I've
talked
to
tommy
cpp
over
github
and
over,
like
the
getter
chat,
he's
mentioned
that
there's
a
lot
of
pieces
that
he
wants
to
rework
and
a
lot
of
pieces
that
we
still
need
to
build.
I
was
planning.
C
Back
into
that
repo
for
a
while
and
doing
some
work
over
there
to
get
that
stuff
in
and
then
being
able
to
thread
the
needle
and
bring
it
into
this
community
demo
app
would
help
because
it
seems
like
it's
not
as
big
of
a
community.
B
Well,
yeah
thanks
for
the
update
okay,
so
it
looks
like
we
have
a
little
bit
of
work
to
do
I'll
track
down.
The.Net
runtime
standard,
metrics
information,
and
then
it
looks
like
we
have
go
java,
python,
c,
plus,
plus
and
net
to
kind
of
target
in
terms
of
just
metric
maturity
in
general
and
maybe.net
will
be
kind
of
the
outlier
a
little
bit
in
that.
B
Besides
that,
I
don't
think
we
have
too
many
more
agenda
items.
There
is
documentation
structure,
so
we're
always
looking
to
improve
our
docs,
I'm
not
sure
if
anyone
has
like
a
specific
passion
for
documentation
or
suggestions
on
how
we
can
kind
of
implement
this
long
term.
I
know
giuliano's
are
following
kind
of
like
a
centralization
philosophy,
which
I
think
I
agree
with
just
because
we
have
so
many
documents,
and
so
many
services
spread
out.
B
It
makes
sense
to
just
do
it
all
in
one
place
and
not
have
to
kind
of
context
switch
around
but
yeah
if
anyone's,
really
passionate
about
documentation
and
one
still,
I
can
improve
our
story.
Let
me
know,
I'm
playing
you'll,
probably
be
see
me
submitting
a
documentation.
Pr
like
once
a
day
or
something
like
that
to
just
kind
of
gradually
add
stuff
and
try
and
improve
our
onboarding
information.
B
But
besides
that,
that's
kind
of
our
last
item
or
the
median
do
we
have
any
kind
of
final
comments.
I
I
think
on.
E
On
the
comments
about
docs,
I
see
this
came
in
as
a
list
of
items
I
wanted
to
get
to
as
well
is
particularly
around
our
instrumentation
things
that
we're
adding.
I
I'd
almost
feel
like.
I
want
to
have
this
driven
from
a
configuration
file
and
then
generate
the
readme
from
like
a
yamo,
yes
or
yaml,
or
something
like
that.
But
you
know
some
kind
of
format
where
you
have
the
service.
E
You
have
the
name
of
the
attribute
you
have
where
it's
used,
and
maybe
a
line
of
code
in
a
code
file
where
you
can
find
it
used.
So
it
helps
people
just
get
to
it,
and
maybe
you
can
even
link
the
direct
line
of
code.
So
when
you're
as
a
user
you're
going
in
there
and
you're
saying
okay
well
where's
this
coming
from,
they
could
just
click
on
it
and
they'll
find
it
right
inside
the
repo
and
and
having
this
put
out
in
some
kind
of
standard
format.
E
F
A
Well,
is
it
hard.
E
I
think
we'd
have
to
write
a
small
thing
that
would
parse
the
yaml
and
emit
out
some
markdown
tables
for
it.
There
might
be
something
out.
There
already
exists
to
help
us
get
this
done,
and
this
is
a
lot
of
where
I'm
getting.
This
is
when
I
look
at
a
lot
of
the
other
hotel
docs,
especially
around
specs
and
stuff,
like
that,
the
specification
is
embedded
inside
of
a
yaml
and
then
there's
a
readme
output
of
that
specification.
B
E
B
E
I
I
ideally
it's
it
would
allow
us
to
also
mix
in
certain
aspects
to
it
to
to
provide
color
which
do
not
belong
inside
of
a
instead
of
a
object
file.
I
guess
or
like
like
a
big
yaml
itself
beyond
that
it
would,
it
would
work,
perhaps
hey
I'm
going
to
pick
up
a
couple
pieces
of
markdown
and
mix
it
in
with
this
generated
these
generated
tables
and
and
here's
your
output,
cool.
B
Great
well,
I
think
we
can
probably
go
ahead
and
call
it
here.
Then
we'll
do
final
comments
again.
I
think
the
current
state
of
the
demo
we're
in
a
very
good
spot.
I
think
the
only
language
we're
missing
today
is
php
and
I'm
talking
to
those
contributors
about
you
know
kind
of
what
our
roadmap
looks
like
for
that.
B
But
really
the
main
items
we
have
today
are
mature
signals,
so
traces
and
metrics,
and
then
also
once
we
reskin
our
ui
and
develop
a
new
front
end
application
we're
actually
essentially
at
v1
release
right
there.
So
it's
a
pretty
exciting
kind
of
progression
we're
on
right.
Now.
I
think
we're
still
targeting
you
know.
We
want
to
try
and
make
it
by
kubecon,
so
we
can
get
some
of
kind
of
the
spotlight
there
and
that's
in
october.
B
So
I
think,
if
we're
in
early
september,
very
close
to
this,
like
v1
release
and
we'll
be
in
a
great
kind
of
a
great
point,
so
just
kind
of
a
timeline
for
everyone
to
be
aware
of.
A
F
Quick,
quick
one
from
my
end
as
we
have
some
guys
from
the
trace
test
here.
Do
you
guys
think
we
could
add
trace
test
to
the
sample?
F
Somehow,
because
we
we
have
a
discussion
open,
it's
called
end-to-end
test.
Oh
I
I
shared
the
link
on
the
dislike
channel.
F
What
happened
is
that
sometimes
we
change
the
the
service
and
we
would
need
to
ensure
that
the
this
service
is
producing
the
the
trace
as
it
was,
and
the
the
trace
that
is
produced
is
linked
throughout
all
the
like.
The
the
whole
end
to
end.
F
Do
you
think
I
I
saw
that
trace
test
is
some
it's
open
source
and
maybe
something
that
we
should
consider
adding
to
the
to
the
project,
at
least
at
the
the
pipeline
like
whenever
there
is
a
change.
It
runs
the
github
action
and
then
kind
of
give
the
approver
the
the
pre
approval
to
hey
it's
working.
You
can
you
can
only
validate
the
code
or
no
it's
not
working,
then
it
already
blocks
the
theme.
What
do
you
guys
think.
D
D
For
for
our
own
request,
we
do
exactly
what
you
said:
we
trigger
a
specific
request
to
assist
them,
and
then
we
run
from
text
using
the
cli.
We
can
do
the
same
for
them
for
sure.
E
F
It
requires
a
server,
but
if
we
install
another
server
like
a
public
one,
we
can
use
that
one.
Instead.
B
E
D
E
A
Yeah,
I
did
a
lot
of
dust
and
that
kind
of
set
up
the
trace
test
so
can
help
with
that.
That
is
that's
useful
for
like
finding
regressions
like
let's
say
you
break
like
the
context
propagation,
you
can
catch
that
with
trace
tests.
So
it's
useful
to
detect
problems
with
traces.
B
Yeah
watch
y'all's
demo.
Video
definitely
seemed
interesting
since
you
just
create
you
know
tests
on
top
of
your
traces.
It's
like
a
much
easier
way
to
kind
of
get
that
actual
representation
of
your
environment
to
build
those
tests
on
so
definitely
interested,
but
okay,
so
I
think
there's
an
open
issue
that,
like
gianna
mentioned,
he
put
it
in
the
slack
window
so
mathias.
You
just
want
to
take
a
look
at
that
and
start
contributing
your
discussion
there.
That
would
be
super
helpful.
E
What's
the
okay,
it's
an
mit
license.
What's
the
I
guess,
what's
the
org
behind
trace
tests.
A
It's
a
company
called
cube
shop,
so
they're
pretty.
I
think
we've
got
six
open
source
projects
running
now.
Most
of
them
are
kubernetes
dead,
kubernetes
focused
and
we're
the
one
outlier
that
is
open,
telemetry
focus.
A
So
it
is
it's
a
ventured
back
company,
okay,
you
know
so
that
everything
we
do
is
mitila,
but
mit.
D
E
I'd
have
some,
you
know
some
reservations
around
making
sure
that
this
is
truly
the
nature
of
open
source.
I
things
around
that.
It's
not
part
of
cncf,
but
you
know
it's
just
another
service.
E
A
We
are,
we
just
got
on
the
cloud
native
landscape,
so
we're
going
down
that
bridge.
Okay-
and
it
is-
I
mean
the
code-
is,
it
is
open
source.
E
So
so
I
have
reservations
to
understand
what
that
all
looks
like,
but
I
love
the
concept
of
trace
docs
like
I
said,
I
think
it's
it's
it's
a
great
concept
and
it
would
definitely
promote
a
lot
of
you
know
the
whole
observability
driven
development
landscape
that
we
try
to
get
people
to
do
with
optometry.
E
So
from
a
marketing
perspective,
it's
got
a
lot
of
bonuses
to
it.
B
Being
evil
is
a
good,
modern
type,
so
yeah
we'll
discuss
it,
maybe
as
maintainers
and
approvers
too,
just
to
make
sure
that
you
know
it's
faithful
steward
to
the
project,
we're
doing
what's
correct,
but
we
still
really
appreciate
you
know
you
contributing,
of
course,
and
we'll
hopefully
be
able
to
integrate
some
of
that.
F
Yeah
and
I
I
I
also
agree
with
yard-
I
think
we
we
have
to
consider-
and
I
I
gave
the
idea,
but
of
course
I
opened.
I
just
brought
the
idea
to
this
question
because
we
have
this
discussion
open
and
we
we've
been
discussing
for
some
weeks
and
maybe,
if
you
guys
do
not
add
to
the
to
the
to
the
main
to
the
upstream
one.
Of
course
you
can
always
fork
and
create
your
own
and
showcase
your
your
product
there
but
yeah.
I.
F
B
Great
works
for
me:
okay,
we
can
go
ahead
and
call
it
here.
Then
thanks
so
much
everyone
for
taking
the
time
to
join
hope.
You
have
a
great
afternoon
evening,
the
rest
of
your
morning.