►
From YouTube: 2020-10-07 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
A
A
A
C
I'm
gonna
have
to
drop
in
30
minutes,
unfortunately,
but
I
really
wanted
to
attend
my
first
one
and
find
out
what's
going
on,
so
I'm
excited
to
hear
what
you
guys
are
doing.
Okay,
great.
A
Well
I'll
I'll
put
the
agenda
here,
so
everyone
please
take
a
time
to
put
your
name
there
and
if
you
have
agenda,
please
open
them
to
them
to
the
mickey
mouse.
A
Okay,
I'm
sharing.
Can
you
see
my
screen?
Please
let
me
know
yep,
okay,
so
so
josh
just
to
give
you
a
quick
heads
up
like
we
have
a
few
interns
from
aws
like
mark
and
karen
here
online,
and
we
have
maintainers
and
approvers
here
as
well.
So
I'm
I'm
the
maintainer.
We
have
another
maintainer
from
google
email
he's
not
here
today
and
we
have
other
approvers
like
johannes,
so
you
can
find
the
list
on
the
main
rip
hall.
Read
me
and
normally
we
have
a
new
member,
will
welcome
and
have
a
like,
quick
introduction.
A
So
would
you
help
us
to
know
like
like
where
you're
coming
from
and
what's
your
interesting
area
and
how
we
can
help
you
get
started.
C
Oh
sure,
do
you
want
me
to
say
who
I
am
and
where
I'm
from
and
stuff
no
yeah?
Yes,
okay
yeah!
So
I'm
I'm
josh
thorett,
I'm
coming
from
google,
and
so
I
I
know
emil
and
I'm
looking
to
kind
of
more
actively
help
kind
of
get
things
implemented
and
and
through
the
door
and
kind
of
make
sure
it's
everything
that
comes
out
of
here
we
can
use.
So
that's.
A
It
okay,
so
I
I
know
for
google,
like
we
started
on
the
open,
sensors,
c-plus
class
and
it's
already
used
by
several
teams
inside
google.
So
I
I
think
the
immediate
goal
here
is
to
build
the
open,
telemetry
and
probably
with
the
open
sensors
bridge,
help
to
migrate.
So
we
can
deprecate
the
open
sensors
part
and
for
the
overall,
like
project
status,
currently
we're
focusing
on
tracing,
although,
like
we
have
separate
work
streams
to
do
the
pilot
work
for
logging,
and
we
already
have
something
for
matrix,
but
those
are
still
very
early
stage.
A
So
the
current
focus
is
we
want
to
get
tracing
part
initial
release
by
end
of
this
year
and
have
some
pilot
customers
trying.
I'm
not
sure
whether
we
can
call
that
a
ga
release,
because
I
anticipate
will
still
have
some
epi
changes.
So,
although,
like
the
open,
telemetry
spike
and
most
of
the
languages,
they
can
announce
ga
for
this
project,
I
I
think
it
will
be
a
little
bit
slow
and
we
can
take
the
time.
So
now
the
focus
is
on
tracing
and
I'm
I'm
doing
the
pilot
work
on
logging.
A
A
So
you
have
a
connection
with
max
right
right.
Yes,
okay,
cool.
A
Okay,
so
it
looks
like
I
got.
Everyone
covered
okay,
so
so
the
number
one
topic
I
have
is
I
want
to
have
like
mark
here
and
not
sure.
If,
karen
I
I
didn't
see
you,
I
assume
you're
here
somewhere,
hidden,
yeah,
okay,
okay,
so
so
mark
and
karen,
like
I'll,
give
you
the
opportunity
to
give
a
quick
update
on
where
we
are
on
the
vlog.
I
know
we
have
like
several
offline
meetings
with
you,
guys
and
alita,
and
so
far
I've
seen
the
progress
so
just
give
some
transparency
to
the
other
folks.
D
E
Not
much
but
right
now,
I'm
looking
into
how
to
actually
create
the
api,
so
I'm
going
through
the
meter
and
trace
interface,
that's
already
in
the
cpp
repository
and
I'm
just
looking
at
how
there's
like
a
main
provider
class
and
then
that
provides
a
static
definition
of
how
to
return
like
a
meter
provider
or
a
trace
provider.
A
Awesome
so
so,
just
to
give
a
quick
summary
so
like
in
the
open,
telemetry
spec,
we
have
covered
what
the
tracing
and
matrix
part
will
look
like.
We
have
the
api
and
we
have
the
sdk
and
some
of
the
common
components,
but
for
logging,
it's
still
a
work
stream
currently
working
progress
and
we
have
some
drafts
back.
A
We
talk
about
protocol
schema,
but
the
api
is
still
somewhere
in
the
air
and
I
I
think
when
it
comes
to
logging,
the
number
one
challenge
is:
people
have
been
doing
that
for
the
past,
like
40
years
or
even
longer
and
there's
so
many
logging
apis
existing
and
based
on
the
language.
There
might
be
different
decisions,
for
example
like
open
telemetry.net.
We
have
decided
we're
not
going
to
invent
any
new
login
api
people
should
just
go
and
use
I
logger
for
python.
A
The
language
has
awesome
built-in
login
api,
so
there's
no
interest
for
us
to
invent
another
login
and
compete
with
the
language
runtime
itself,
and
so
it's
just
different
and
for
java,
there's
log4j
and
people
are
debating
whether
they
should
use
log4j
or
use
another
login
library
for
c
plus
plus
we're
in
a
in
a
situation
where
there's
several
existing
logging,
libraries
or
the
api.
A
Like
isd
case,
none
of
them
are
dominant,
like
kind
of
they're
like
few
famous
one
and
they're
a
lot
of
not
very
popular
one,
and
we
also
have
other
constraints,
for
example,
in
open
telemetry
c
plus
plus
we
have
the
design
goal
where
we
want
all
the
apis
to
be
header
only
library,
so
people
can
just
take
dependency
on
the
header
files
without
any
binary
dependency,
and
this
will
give
us
restriction
and
also
we
target
multi-platform.
A
So
if
a
like
famous
logging,
api
for
c
plus
plus,
is
not
going
to
cover
like
mac
os
or
like
linux,
then
it's
a
no
go
for
us
and
also
we
care
about
the
the
dependency
and
license
and
all
the
stuff.
So
currently,
we're
like
having
great
help
from
these
interns
to
evaluate
all
the
options
we
have
and
based
on
that
we'll
make
a
decision
should
we
introduce
another
logging
man,
and
that
sounds
scary,
because
people
have
been
doing
that
for
the
past
40
years.
A
I
like
I'm,
trying
to
avoid
like
inventing
another
set
of
api
unless
we
have
a
very
good
reason.
So
this
is
why
we're
taking
probably
like
one
or
two
weeks,
just
to
make
sure
we
make
a
a
reasonable
decision
instead
of
like
rush,
and
we
can
take
the
time
and
thank
for
karen
mark
for
the
progress
so
far,
good
stuff.
A
Okay,
any
questions
about
logging
or
any
like
concerns
or
like
or
like
your
interest.
You
won't
get
like
like
participate
in
this
thing.
I
I
think
the
eventual
goal
is
we
want
to
make
everything
public
like
on
github
pr,
but
for
now
it's
a
like
initial
discussion
and
a
lot
of
crazy
ideas,
so
just
to
avoid
the
the
noise
is
like
a
private
meeting
between
aws
and
microsoft
and
those
interns.
But
nothing
is
private
and
the
document
is
shared
on
the
google
docs.
So
my
plan
is
to
move
them
to
the
public
to
make
that.
E
Transparent
sure
we're
also
working
on
a
requirements
and
a
design
document.
So
that's
probably
going
to
be
done
by
the
end
of
this
week.
Do
you
think
karen
and
those
we
can
put
on
the
github,
so
there
will
definitely
be
some
yeah.
D
I
think
during
friday's
meeting
with
just
the
microsoft
and
aws
team,
we
can
maybe
go
through
that
then
and
then
decide
how
to
proceed
forward.
A
D
And
riley
mark-
and
I
were
thinking
of
filing
the
rfc
soon,
maybe
sometime
before
friday,
should
we
maybe
send
you
a
draft
on
gitter.
So
if
there's
anything
you'd
like
to
add,
we
can
do
that
before.
It's
posted.
A
A
A
Thank
you
so
my
next
topic,
so
I
could
wonder
like
in
this
project
we
initially
we
have
like
several
maintainers
and
approvers
and
they
were
moved
to
some
other
projects.
So
I'm
now
the
only
acting
maintainer
holding
these
meetings
and
facilitated
staff.
So
I
want
to
build
a
path
we
can
get
more
brewers
and
maintainers
just
to
build
a
healthy
community
and
so
number.
One
thing
is:
I
want
to
have
people
coming
from
different
companies
to
represent
different
voice,
and
so
we
have
a.
A
A
That
looks
exactly
the
same
as
what
I
used
to
have
before,
so
so
with
that,
like
please
say
like
if,
like
folks
from
aws
from
google,
you
guys
are
like
interested
in
putting
like
your
energy
in
this
product
and
eventually
become
a
program
maintainer
just
to
help
this
product
to
stay
more
than
the
neutral.
A
But
meanwhile,
we
have
two
folks
from
from
my
team
and-
and
they
were
like
spending
a
lot
of
time
here
and
just
joined
the
team
a
few
months
ago,
but
the
plan
is
for
them
to
dedicate
like
at
least
50
of
the
time
on
the
project
so
so
far
they
have
made
some
like
progress
and
based
on
the
the
community
guideline
I
want
nominate
for
like
approvers,
want
to
see
like
if
any
like
objection
or
anything,
you
think
we
should
just
give
people
more
time
to
observe
just
want
to
see
like
where
we
are,
and
I
I
think
my
main
goal
is
to
get
more
contributor
approvals
to
this
project,
so
we
can
scale
better.
A
So,
just
for,
like
the
two
names
so
lilith
and
tom,
do
give
a
introduction
like
where,
like
where
you
are
like
working
on.
What's
your
focusing
area
and
what
you
have
done
so
far
just
give
people
some
idea.
F
Yeah
sure
so
I
mean
london
here,
so
I've
been
working
with
rayleigh
team.
I
mean
mostly
involved
in
more
of
the
I
mean
from
past
six
months,
I've
been
working
more
internal,
microsoft,
telemetry
apis
sdks,
which
have
been
contributing
and
recently
started,
focusing
more
on
the
openly
open,
telemetry
c
plus
plus
part.
So
I
have
been
focusing
on
the
tracing
api
because
that's
something
which
we
have.
We
could
say
that
we
are
going
to
reach
to
the
level
where
we
can
definitely
have
alpha
release.
For
that.
F
There
I
mean,
if
I'm
missing
some
of
the
platforms
plan
to
really
definitely
going
ahead,
develop
the
exporters
I
mean
have
already
started
working
on
the
http
api
and
which
would
be
subsequently
used
for
the
exporters
which
we
are
going
to
use
and
I
would
be
focusing
on
one
status
apart
from
tracing
part,
would
be
focusing
in
that
area.
Also
and
yeah
I
mean
that's,
that's
that's
a
bit
important.
A
Yeah,
thank
you
so
so
late
has
a
lot
of
experience
in
the
mobile
like
telemetry
story
and
he's
he's
one
of
the
owner
of
the
microsoft
like
client
telemetry,
which
is
used
by
like
office
apps
and
like
teams
and
other
stuff
and
like
here.
I
I
think
one
thing
really
could
give
a
lot
of
help
is
on
like
the
performance,
part
and
reliability
part,
because
this
part
is
critical
for
the
mobile
thing
and,
and
also
I
I
think,
gladys
in
general
is
a
very
good
class.
Class
developer
has
more
experience
than
me.
G
A
G
You
tom,
okay
yeah,
I'm
time
time
and
I
also
work
working
wireless
team
and
in
the
past
three
months
I
was
working
on
integrating
open
telemetry
to
our
internal
pro
products,
building
collector
and
receive
otp
protocol,
and
with
that
part,
almost
done
and
I'm
going
to
at
least
as
well,
I
mentioned
spend
at
least
50
of
my
time
to
improve
open,
telemetry
c
plus
plus
and
help
reach
the
on
the
ga
goal
of
tracing
increasing
part
and
yeah.
I'm.
G
A
Yeah,
so
just
for
information
tom,
it's
also
helping
on
the
open,
telemetry
download
and
it's
driving
the
open,
telemetry
spec
for
the
ga
requirement
related
to
the
performance
benchmark
and
those
like
criterias
and
and
also
time
is
coming
from
a
very
like
low
level
like
like
work
stream.
So
he
used
to
work
on
the
the
windows
kernel
team
in
charge
of
like
magically
transcompile,
like
old
x86
and
x64,
called
on
the
flight
run
on
arm64.
So
something
like
blackmagic.
H
G
Okay,
then,
move
to
the
next
question
right:
yeah,
okay,
yeah,
I
was
reviewing
the
to-do
items
and
yeah.
There
are
many
informations
there.
Already
there
like
priorities
like
or
help
link,
I'm
wondering
when
we
add
such
to-do
items
can
we
add
some
time
estimation
which
could
help
us
or
even
not
not
just
us
when
a
newcomer
to
pick
up
like
run
some
rough
estimates,
maybe
one
day
or
less
than
one
day
work.
Maybe
we
can
plan,
do
more
planning
or.
A
H
Well,
after
that,
I
also
hesitated
to
put
some
estimates
in
the
issues
that
I
wrote,
because
it
it
heavily
depends
on
who
picks
up
the
issue
and
who
works
on
it,
and
it
also.
Some
of
the
things
are
hard
to
estimate
because
we're
still
like
in
some
or
the
exploration
state,
for
example,
this
all
the
exporters
like
the
zip
king,
the
jaeger
that
include
event
on
like
this
http
api.
I
think
it's
hard
to
give
any
estimate.
G
I
totally
agree,
but
yeah
I
mean
even
we
don't
need
to
be
too
accurate
right.
Maybe
some
rough
estimates
maybe
just
weeks.
This
is
what
item
of
weeks.
Maybe
people
will
be
more
more
careful
to
pick
up
such
work
item
and
reserve
time
for
that
right
and.
I
I
G
A
A
Okay
and
in
the
community
meeting
we
asked
if
folks
could
come
and
help
and
there's
some
big
change
that
will
affect
everything
in
the
repo
like
change,
some
very
fundamental
apis
or
the
components
that
touch
almost
every
corner,
and
normally
we
don't
need
any
help.
We
let
the
maintainers
do
the
job
because
they
need
to
make
sure
it's
not
going
to
step
on
the
other
folks
like
toast,
and
it's
not
going
to
like
ruin
all
the
existing
pr
and
people
have
to
do
some
like
crazy
merch.
A
I
think
here
we
probably
can
can
can
start
from
like
two
levels.
One
is,
we
think
it's
something
relatively
easy
for
people
to
pick
up
another
one
is
we
expect
approvers
and
maintainers
to
work
on
because
they're
more
attached
to
the
project
and
later
we
have
I'm
the
only
maintainer
and
I
haven't
written
a
lot
of
code
just
because
I
don't
have
time
barely
survived
by
running
this
community.
So
when
we
have
more
maintainers,
I
think
entrepreneurs
should
definitely
do
more
coding
work.
That's
my
expectation.
I
So
I'm
certainly
seeing
like
there's
a
there's.
A
couple
of
bugs
that,
I'm
sure
are,
you
know,
should
be
fairly
small
pieces
of
work
relatively,
but
otherwise
on
there
to
do
in,
at
least
in
the
project
view,
it
looks
like
all
the
to-do
items
are,
are
not
really
bite-sized
right
now,
they're
they're,
all
a
little
bit
bigger.
C
C
I'm
not
I'm
not
sure
what
that
means.
I've
been
attending
random
sigs
and
like
compiling
code
and
writing
stuff
internally
to
like
learn
it.
But
I
don't
know
if
I've
clicked
the
right
buttons.
Okay,
so
so
there's
a
requirement
to.
A
Yeah,
I
I
I
can't
work
on
that,
probably
like
I
I
can
work
with
tom
and
lalit
just
to
help
them
to
run
path
in
this
area
as
well
so
josh
once
you
join
the
community,
you
can
like.
We
can
assign
issues
to
you.
So
when
you
join
the
community,
go
through
the
the
steps
there-
and
you
can
put
me
as
one
of
the
nominator
and
you
can
find
the
others
who
are
already
here
just
reach
out
to
them
and
see.
A
F
A
I
H
A
Okay,
so
now
it
and
tom
I
have
one
ask
for
you
like,
when
you
put
those
comments,
make
it
explicit
whether
it
is
a
blocking
issue
from
the
pr
or
you
think
it's
just
a
net
like
here.
A
I
I
think
this
is
great
and
once
you
feel
like
all
the
major
like
issues
are
addressed,
you
give
x
play
signal
whether
you're,
okay
or
not
like
either
approve
that
or
you
don't
have
proof
by
telling
people
why
you
don't
approve
that
and
what
would
make
you
approve
that
that
way
would
help
us
to
have
a
better
communication.
G
I
have
a
question
on
the
latter
part
if,
like
for
for
pr
which
is
pending
for
some
days,
we
we
need
to
comment
why
this
is.
We
are
not
going
to
merge
it.
G
A
A
We've
done,
I
download
I'm
trying
to
give
explicit
signal
by
telling
people
hey
if
this
is
something
that
is
nice
to
have,
but
not
required
in
the
vr
we
can
put
like
the
the
driver,
like
the
people
who
send
the
pr,
should
drive
this
com
like
communication
by
saying,
hey,
let's
take
this
apart,
I'm
going
to
create
an
issue
to
track
this,
but
I
want
to
get
this
pr
merged
or
they
can
tell
like.
I
want
this
pr
to
stay
there
forever.
It's
their
choice.
A
Got
it?
Okay,
I
think
that
covered
all
the
recent
prs.
There
are
some
like
old
pr's
have
closed
the
obvious
one
that
is
not
going
to
make
progress
for
some
of
the
prs
had
already
approved,
but
they
got
some
merge
issue
or
I
have
minor
suggestions,
but
the
intern
already
like
left
they
haven't
like
we
haven't,
got
a
chance
to
fix
all
the
the
comments
that
I
have
put
there
I'll
I'll
see
like
whether
I
can
I
can
take
some
time
to
fix
those
before
I
merge
or
I'll
just
call
the
pr.
H
H
I
think
that
would
be
a
great
ticket
to
pick
up,
because
it's
basically
making
our
simple
spam
processor
thread
safe,
which
it
currently
is
not.
I
think
his
ticket
has
a
pretty
good
description
about
what
to
do
and
should
not
be
too
complex
to
be
done
and
yeah.
If
you
have
any
questions,
you
can
just
also
reach
out
to
me.
C
Yeah-
that
sounds
great.
I
I
will
do
that
cool.
A
Okay,
I'll
give
you
another
pointer
from
the
open
time
to
donate
like
we
have,
we
had
a
debate
in
open
telemetry.net
and
we
decided
for
the
the
simple
one
we
just
make
it
really
simple:
there's
a
there's,
a
global
log.
Everything
is
like
sequential
and
there's
scenario
where
we
want
to
re-entrant
one.
So
we
like,
I
just
invented
one-
and
I
convinced
the
others
and
I'm
going
to
put
that
as
a
like
a
spec,
a
pr,
but
it's
not
going
to
be
part
of
the
initial
ga
release.
A
A
And
just
for
you,
information,
johannes,
so
the
the
simple
one
is
following
the
spec
exactly
like
we
take
the
contention
every
time,
there's
only
only
one
exporting
activity
happen
and
it's
not
re-entrant,
and
on
the
other
side
we
have
scenario.
We
want
multiple
threads
to
to
have
the
freedom
to
export
to
some
places.
For
example,
they
can
dunk
the
data
to
a
shared
memory.
There's
no
synchronization
at
all,
and
this
is
the
entrant
takes
power.
H
A
A
H
So
currently,
just
for
trust
understand
in
our
c
plus
plus
a
repository.
Simple
exporter
is
re-entrant
yes
to
the
exporter,
but
it
should
be
not
to
enter
and
it
should
actually
be
have
a
lock
and
then
sure,
once
at
a
time.