►
From YouTube: 2021-03-02 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).
A
B
A
Let's
wait
for
other
folks
to
see
okay
and
then
I'm
gonna
share
the
link
to
the
attendees
list.
I'm
gonna
add
your
your
name
on
it.
There's
that
docs
google
docs,
where
we
capture
the
topics
and
stuff.
B
Okay,
I
can
find
it
it's
just
off
of
the
community
one
of
the
sigs
right.
That's
the
main
thing.
A
A
He
has
another
meeting
right
now.
I'm
gonna
read
the
call,
I'm
gonna
capture
the
notes.
A
C
A
A
Let's
just
capture
the.
A
Also
from
the
last
week,
we
actually
merged
in
jenks
module
pr,
and
we
already
approved
the
first
layout
structure.
Pr.
C
A
A
So
for
that
I
think
jinx's
instrumentation.
A
Yeah
and
for
the
initial
layout
of
what
we
discussed
on
the
pr
is,
we
do
not
want
the
main
repo,
maintainers
and
approvers
to
be
automatically
the
approvers
and
maintainers
of
the
country.
We'd
rather
create
a
separate
team.
I
think
creating
a
separate
team
requires
us
to
ask
the
admins
on
open,
telemetry
sensors
to
create
one.
Then
we
can
populate
it
with
a
few
holes
and
for
individual
subdirectories.
A
A
C
There's
no
really
discussion.
I
want
to
bring
up.
The
only
thing
I
wanted
to
remark
is
that
I
was
a
bit
chatting
with
lalith
friday
and
today
regarding
the
documentation
and
how
I
will
host
the
documentation
and
he
brought
it
up
in
the
maintainers
meeting,
which
was
I
think
today
in
the
morning
and
how
we
will
go
about
that.
We
will
just
yeah
for
our
api
documentation.
C
There
will
be
a
very,
like
short,
like
overview
or
getting
started
that
will
be
hosted
on
opendelemetry.io,
but
for
our
ai
for
our
api
documentation.
We
will
just
for
start
set
something
up
on
like
read
the
docs
and
publish
there
for
api
documentation.
Each
language
goes
like
individual
base,
so
there
is
no
standard,
and
it's
also
it's
also
not
desired.
To
put
this
have
already
detailed
information
on
opendelemetry.io.
C
No
there's
like
a
readthedocs.org.com
and
we
will,
I
think,
bison
already
publishes
their
docs
there
and
we'll
also
use
that.
So
I
think
that
that's
the
reader
read
the
docs.
That's
a
free
there's,
a
free
version
of
that.
C
That
has
some
kind
of
I
think
ads
in
between,
but
I
think
I
will
start
off
with
that
and
if
we
want
we
can
then
maybe
switch
to
the
paid
version
that
has
no
ads.
I
don't
know.
C
I
plan
to
use
stock
citroen
yeah
I
mean
for
read
the
docs
you
I
think
you
for
having
some
kind
of
automated
updates
you
they
support
sphinx,
but
I
will
just
provide
like
a
sphinx
wrapper
for
out
oxygen
stuff.
I
think,
because
I
think
we
want
to
stay
with
the
encode
documentation.
C
A
Okay,
it
sounds
good,
sounds
great,
any
other
topics
we
have
from
the
last
week,
so
I'm
going
to
skip
the
contribute
structure
of
bloomers
the
pr
we
discussed
this
first
step,
the
rest
of
some
to
do
and
we're
going
to
continue.
A
We
adopt
the
owners
approach
so
for
the
other
topics,
I'm
trying
to
reconstruct
the
resources,
decay
and
documentation.
I
will
just
cover
documentation,
really
quick.
A
A
I
don't
really
have
much
time
develop
the
resource
api
in
sdk.
So
from
my
end,
I'm
still
trying
to
finalize
the
ecw
was
the
test
suite,
which
I
want
to
contribute
to
contribute,
because
ttw
is
one
of
my
mechanisms.
It's
not
exactly
the
standard
food
and
the
test
suite
and
the
illustration
how
to
use
that
to
forward
data
to
systems
like
application,
insights,
azure,
monitoring,
small
with
a
custom
contribution.
A
Of
the
next
pr
in
country
to
show
how
to
catch
all
these
hcw
events
in
different
formats
and
verify
the
terrible
economy
any
other
folks
joining
the
call.
I
didn't
see
anyone
else
actually.
C
A
Should
we
wait
for
kind
of
four
more
minutes,
any
other
topics,
you
guys
think
we
should
bring
up
here.
B
I
mean
I
don't
have
anything
so
I'm
fine
with
waiting.
A
Let's
meet
here,
we
go
so
we
don't.
A
A
All
right,
let
me
just
quickly
skim
through
that.
I
think
in
terms
of
release.
We
may
want
to
plan
on
getting
a
new
label
like
within
a
week
or
two,
I
I
know
we
were
kind
of
trying
to
get
the
monthly
cadence
for
the
release
tags.
I
don't
think
we
had
a
lot
of
content
very
recently
to
justify
creating
an
unbelievable
to
maybe
mid
mid-march
and
in
terms
of
resources
the
api
once
that
settles.
A
It
definitely
makes
sense
to
to
do
another
tag
label
with
that
just
quickly
and
scrolling
back
through
the
previous
topics
to
see
maybe
can
bring
up
something.
A
For
the
for
the
old
visual
studio
support,
I
had
something
on
my
plate
for
supporting
2015..
A
I
hope
that
the
need
for
that
amongst
some
of
our
internal
customers
is
now
diminished
as
they
are
moving
to
visual
studio,
2017
so
dynamically
in
terms
of
priority.
This
will
become
a
bit
lesser
of
a
priority
for
me
once
our
biggest
customers
are
also
in
2017
and
on
17.
We
already
have
some
ci
for
that,
I'm
not
giving
up
the
item
of
supporting
15.
I
know
that
it
works
and
compiles,
but
in
terms
of
adding
a
ci
for
that,
it's
a
bit
of
a
lower
priority.
For
me,
hope
that
makes.
A
I
don't
really
have
any
topics,
maybe
we
can
give
everybody
45
minutes
back.
It
sounds
great
to
me.
Does
it
work
for
you,
michael.