►
From YouTube: 2020-05-04 C/C++ SIG
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
Ok,
so
I
got
more
trouble
on
the
guard
outside
that's
another
story:
okay,
like
like
Sergei
Microsoft,
and
the
macro
writer
left
like
that.
So
we
have
no
active
like
maintainer
for
on
that
and
I
have
a
developer
put
in
full-time
there,
I'm
spending
some
time
there
as
well.
The
part
got
more
pressure
because
countries
if
Hospice
is
not
listed
as
the
like
targeting
end
of
this
year's
g8,
which
they
have
not
so
nice
to
happening,
not
a
required.
Now
that
is
a
recording.
A
D
Name
is
yes,
my
name
is
Owen
I'm
with
Google
I,
don't
know
if
you
guys
have
heard
about
the
ops
management
effort
to
on
board
like
a
ton
of
interns,
basically
to
work
on
open
telemetry,
oh
yeah,.
D
Yeah
yeah
a
lot
of
interns,
so
four
pairs,
which
would
be
eight
interns,
are
interested
in
C++
work
and
that's
why
I
dialed
in
today
to
see
what
the
status
is
at
and
if
we
can
identify
some
work
for
some
of
these
interns
to
do.
Oh.
D
A
So
the
current
state
is,
we
don't
have
a
ready
to
use
eyes
decayed
or
the
API
for
tracing
matrix.
Work
is
not
even
started,
and
we
have
some
initial
idea
about
logging,
okay
and
for
tracing.
We
have
the
basic
like
tracers,
then
interface,
but
they're
not
like
up
to
date
with
the
current
open
country
specification
and
we
don't
have
the
contacts
API
implemented.
Yet
that's
a
what
are
the
two
biggest
belong
occurs
for
tracing.
A
We
do
have
some
like
exporter
interface,
implemented
by
Johannes
and
that
part
already
powered
by
the
CI
and
regarding
the
CDI
I
believe
like
it's
pretty
comprehensive.
It
covers
like
many
different
platforms,
performance
and
risk
evasion,
those
things.
So
if
we
have
interest,
obviously
things
we
can
like,
potentially
how
is
first
to
find
a
lender
here,
like
neither
micronics
or
me,
to
welcome
the
contacts
API.
The
second
part
is
to
build
some
examples.
A
Very
simple
start
by
saying,
like
what
a
customer
could
do
like.
Basically,
you
take
a
look
at
open
time.
Quite
nice.
You
can
see
the
customer
what
you
can
do
with
yeah
and
try
to
see
if
you
can
do
the
same
thing
in
C++
and
it
is
now.
Let's
see
was
her
amazing
pieces
and
the
third
thing
was
to
compare
the
current
implementation
back
and
see
what's
the
difference
and
cover
the
difference
initially
in
the
document.
No,
we
do
have
a
lot
of
different.
A
D
One
intern
is
starting
today:
I
have
another
intern,
that's
starting
next
week,
so
our
team
has
prepared
some
starter,
just
warm-up
projects
for
them
just
like
create
a
basic
GCP
project
and
create
a
service
and
use
open,
telemetry,
very
quicky,
cutter
style
of
projects.
I,
don't
know
how
long
the
project
will
take
interns,
I
would
say.
Maybe
two
weeks
three
at
the
most
at
this
point.
That's
nest
in
this,
so
I
would
say.
Probably
end
of
May
is
at
the
latest
one.
We
need
to
start
working
on
the
the
real
project.
B
D
B
B
E
Can
also
think
about
some
like
a
GU
thread,
so
the
export
aside
to
tie
I
mean
I
could
write
issues
about
that.
Like
some
kind
of
issues,
and
somebody
could
pick
it
up,
I
mean
one
issue
would
be
I,
could
think
of
yeah.
Just
writing
a
standard
out
exporter
modeled
after
other
languages.
That
might
be
a
start,
or
we
have
like
long
issue
with,
like
certain
things
that
we
are
still
open
on
our
export
aside,
like
making
the
export
of
WorkSafe.
That
would
be
maybe
a
bigger
project,
but
I
can
trust.
A
E
Thinking
about
a
standard
Alex
border
for
beginning
I
mean
that,
like
that,
could
be
modeled
easily
model
of
the
other
open
telemetry
project.
It
already
have
that
yeah
it
pretty
simple
start
for
check
tech
and
there's
an
other
other
thing
that
will
be
more
complex
to
be.
Are
making
our
current
export
of
work
safe.
We're
talking
about
that
that'd
be
a
more
technically
challenging
thing,
depending
on
what
the
person
wants
to
become.
B
And
just
like
another
idea,
like
we're,
probably
close
to
having
like
the
tracing
part
of
the
API
filled
out,
so
there
there's
a
few
like
instrumentation
projects.
It
might
be
interesting
so
like
with
open
tracing.
We
we
have
a
module
for
nginx
that
would
need
to
get
ported
over
to
open
telemetry
and
I
just
interacts
with
the
API
too.
So
it's
it's
possible
to
do
that
project.
Even
if
the
exporter
side
of
it
isn't
finished.
D
D
D
D
C
A
C
A
Probably
like
we
can
follow
up
offline
with
the
Ryan,
Jonas
and
Max,
or
familiar
always
been
with
this
product,
to
review
those
issues
and
tag
them
properly,
and
we
can
use
the
next
meeting
to
go
through
the
issue
and
see
which
one
is
a
good
fit
for
the
intern.
And
probably
that's
the
time
we'll
also
in
by
the
interns,
because
different
people
have
different
background
and
strains
to
see.
There's
a
bee
need
to
take
the
picker
part.
D
D
Yeah
and
I
think
it's
a
great
idea
to
just
make
a
list
of
potential
projects
with
maybe
a
couple
sentence
summaries
for
the
interviews,
as
well
as
the
hosts
just
to
get
a
sense
of.
What's
there
I
think.
One
more
thing
on
my
mind
is
whether
we
can
establish
some
sort
of
Mentor
or
sig
contact
that
could
be
a
pianist
yeah
yeah.
A
Definitely
so
I
can't
will
endear
myself
for
interns
who
won't
work
on
the
contacts
API
or
they
want
to
know
like
overall,
open
telemetry
project.
I
will
count
the
trace
a
trace
contacts
and
I
work
across
multiple
SDKs,
probably
the
least
time
I
spend
here
is
a
sip
as
class.
Still
a
lot
of
time
on
Python
is
some
time
I'm
done
that
in
this
bag,
like
a
half
on
that
part
and
yeah
Ryan,
you
want
to
volunteer
yourself
I'm.
D
D
I,
don't
think
we're
expecting
a
huge
amount
of
commitment
from
the
mentors
here,
I'll
sync
up
with
the
ops
management
group
within
Google
as
well
to
see
what
we're
expecting
from
the
mentors.
It's
likely
just
you
know,
pointer
to
documentation,
someone
who
can
say.
Oh
here's
documentation
something
yeah.
A
A
Yeah,
so
we
can
probably
start
by
inviting
the
interest
Gator
channel
and
find
out
the
background,
and
meanwhile,
like
we
like
the
developers
here,
we
come
welcome
to
github
issues,
break
them
down
and
I'll
make
sure
those
are
probably
tagged,
something
like
Frisco
issue
or
up
for
grab
the
interest.
I
have
some
idea.
Then
we
can
spin
next
week's
meeting
to
talk
about
it,
which
part
seems
to
be
interesting
to
the
interest
and
based
on
that,
we
figure
out
who's
going
to
be
the
mentor
I.
Think.
D
A
F
A
A
Okay,
okay,
so
so
previously,
like
you
know,
sometimes
we
figured
like
teams,
they
are
the
ones
at
different
pace
and
some
stump
teams
they
they're
understaffed.
So
the
initial
thinking
is
like
we
want
to
see
like
which
say
needs
more
cow,
and
later
we
realized
like
a
lot
of
teams.
They
have
the
practice
of
a
better
integration
past
some
of
the
the
infrastructure
facilities
for
planning,
whether
there's
a
breaking
change
and
how
how
to
make
sure
there's
a
backward
compared
to
this
is
a
initial
thinking.
A
We
won't
be
able
to
come
here
and
share
some
of
the
best
ideas
and
ask
for
help
and
guidance
for
the
community
and
liver
like
we
is
this
virtual
group
to
drive
for
the
release
cadence
and
that's
the
point
we
realized.
We
need
a
real
meeting
here.
The
first
meeting
is
more
focusing
some
generous,
a
man
who
needs
help,
but
here
more
more
importantly,
we
want
to
see
what's
the
timeline
for
each
SDK
and
I
believe
the
discussion
is
like
we
won't
have
the
initial
release
of
Python
donut,
JavaScript
and
some
of
our
secrets.
A
But
one
thing
is:
if
Hospice
is
not
on
the
list,
what
we're
trying
to
get
GA
by
by
November
this
year,
and
even
for
that
November
date,
is
it's
not
settled
so
so
for
some
iced
tea
case,
they
probably
won't
be
able
to
make
a
GA
by
September
if
the
spec
to
make
a
ga.
So
the
other
things
are
still
on
the
air.
A
So
for
the
past
parts
I
explained
to
people
at
hundred
were
not
well
from
dead
and
like
we
have
stream
and
tenors,
we
all
right
and
me
and
Ryan
is
contributing
most
of
the
code
with
a
half
from
Jonas,
so
I'm
hiring
more
developer
to
join
this
and
there's
a
special
interest
from
Splunk,
so
they
might
be
able
to
get
some.
You
know
to
help
as
well,
and
also
we
got
interest
from
Google
like
all
in
the
six
plan.
So
those
are
using
some
simple
sites
were
getting
more
help.
A
Meanwhile,
I
want
to
see
if
there's
any
any
like
timeline
or
commitment,
we
think
we're
able
to
achieve
so
far.
We
have
no
promise.
This
is
probably
something
won't
come
out.
The
next
maintainer
is
meeting
and
those
are
Ryan
seems
you're
the
maintainer
for
this
project.
So
if
you
don't
have
that
meeting,
please
take
a
look,
and
if
you
want
the
link
I
can
share
with
you
I
believe
you
already
got
it
so
you
can
join
the
meeting
so
weekly
one,
that's
the
current
status.
A
A
Your
million
sorry
was
a
question:
are
you
aware
of
this
maintainer
Smita?
No,
no
I
haven't
heard
of
it.
This
is
kind
of
strange
so,
like
a
lot
of
people
like
I
pinned
a
few
other
manners,
and
they
were
not
aware
of
this.
So
probably
the
the
first
meeting
is
to
ask
all
the
people
who
attended
to
spread
the
message,
so
you
all
know
to
join
next
time.
This
is
more
at
living,
it
need
help
or
you
want
to
see
what
other
projects
are
going
on.
A
We
want
to
share
some
see
ideas,
so
one
thing
I
do
want
to
propose.
Next
one
is
I
want
to
see.
If
we
can,
we
don't
have
all
the
iced
tea,
hey,
repost,
leveraging
the
github
actions
currently
like
you
are
eating
like
either
Chavez
circusy
or
something-
and
you
see
char-
please
either
pipeline,
which
have
some
stability
issue,
and
now
the
Gator
action
is
more
stable
and
this
supports
actually
more
platforms
than
Travis,
so
I
want
to
know
or
a
circle
CI,
and
it
is
something
like
like
you
think,
will
be
interesting.
A
So
right
so
for
soup
has
hot
side.
I
think
will
ask
for
them
is:
do
we
have
a
plan
to
release
some
like
revealed
version
and
what
had
they
asked
from
us?
Are
we
under
funded
and
I,
think
I've
covered
eyes?
So
currently
we
don't
have
a
plan
and
we're
working
on
the
trace
in
part
matrix
part
is
yet
unknown
and
we
were
definitely
underfunded
and
we
got
an
interest
and
for
the
next
meeting,
I
want
to
ask
if
you
want
to
move
to
github
actions
for
a
better
CI
across
all
ice-t
case.
B
A
I
think
so
so
recently,
like
like
marks,
switched
some
of
our
internal
staff
tool
to
github
actions,
and
it
was
quite
successful
and
like
him
in
open,
climb
tree
python,
we
started
with
github
actions.
Try
that
at
that
time
it
was
a
preview
not
very
stable,
so
we
decided
to
stick
with
circle.
Ci
I
know
Travis
CI,
actually
not
how
it's
time
to
repeat
it.
A.
F
A
F
Offer
OS
X
as
physical
machines
and
windows
as
docker
OS
X.
It's
unique.
It
is
actually
hosted
on
physical
Harper
and
they
offer
certain
machines
imaged
to
in
a
specific
way,
I
think.
Usually
they
upgrade
things,
but
they
keep
also
older
versions
of
Xcode
and
older
versions.
Follow
vm
in
that
image.
A
E
Just
both
in
a
bundle
when
we
are
like
asked
about
estimates
and
how
far
we
are,
and
the
alpha
and
beta
releases
I
wonder
if
you
feel
to
come
up
with
some
kind
of
milestone
list,
because
who
me
currently
is
not
even
flora
but
should
be
in
the
Alpha
release
or
truth
paint
of
data
released.
And
then
it's
hard
to
give
any
estimate.
I.
Think,
okay,.
A
A
B
So
I
was
working
on
that
this
this
morning.
The
only
thing
that
I
have
to
add
is,
if
you
remember
we
wanted
to,
we
discussed
having
a
mode
where
you
could
run
it
without
live
event,
just
have
that
the
timer
dispatcher
build
off
about
like
SEO
types.
So
that's
the
one
piece
that
I
was
working
on
this
morning,
there's
still
a
little
bit
of
test
coverage
and
possibly
some
changes
that
I
need
to
finish
that
part
of
it
yeah.
A
A
B
A
And
you're
nasai
until
this
one
still
have
some
some
interfaces
that
are
not
a
hundred
percent
aligned
with
the
this
bag,
but
I
think
that's
a
reasonable
balance,
any
cost
anything
you
want
to
change.
I
blithering
in
line
now
changes
so
I
think
the
last
time
I
look
at
still
some
some
minor
patients
with
eighty
I
think
that
the
reality
and
a
tracer
is
taking
reference
to
the
processor.
E
A
E
That's
what
we
changed
so
then,
basically,
the
processor
for
all
traces
can
be
set
via
the
provider,
and
you
think
that
photo
spec
requires
yeah
I'm
reading.
We
are
in
that
regard,
conformant
mr.
speck
I
mean
in
addition,
in
addition,
here
we
have
the
option
that
we
can
use
a
trace
of
its
outer
provider.
I
mean
that's
not
even
say
just
something:
B
we
added
to
it
for.
B
B
Okay,
yeah
and
then
just
like
scroll
down,
so
the
access
there
to
get
the
processor
yeah
so
that
one
can
we
return
that
as
a
shared
corner
to
the
processor,
so
that
the
is
right
now
if
we
return
a
reference
like
that
and
you
set
the
processor,
then
you'll
invalidate
the
reference
between
stage,
oh
yeah
and
then
there's
just
one.
Other
thing
is:
can
we
use
the
atomic
shared
pointer,
so
it's
thread
safe,
just
the
same
sorta,
the
same
design,
that's
in
the
tracer,
the.
B
A
A
B
Variant
and
now
that
the
variant
is
merged
it,
it's
a
much
smaller
PR,
so
it
should
be
easier
to
take
crack
sure
this
just
takes
the
variant
and
builds
out
the
event
interface
on
on
top
of
it.
Okay,.
F
C
B
Max,
if
you,
if
you're
using
a
long
term
span
like
that
it
never,
it
doesn't
actually
send
its
data
until
after
the
span
has
been
finished.
So
if
you're
like
using
it
as
an
applicant
in
an
application
to
collect
the
logs,
but
you
wouldn't
be
able
to
get
any
useful
information
until
you
know
the
application
is
linking
at
its
end
point
and
then
you'd
have
like
a
span
with
like
a
huge
number
of
events
attached
to
it.
Right.
F
F
A
No,
it's
not
that
event
is
not
a
logging
idea.
It's
a
specific
part
of
the
tracing
API
and
the
reason
of
having
an
event
is
because
some
traces
they
might
have
a
high-level
logic
operation,
where
you
want
to
add
like
more
details
to
that.
So
it's
part
of
the
trace
exam
hi
can
give.
For
example,
when
you
send
a
like
storage
ball,
we
try
to
upload
blah.
The
the
span
could
be
called
upload
blah
and
the
actual,
like
ECB
requires
could
be
like
uploading,
the
blobs
in
chunks,
and
you
want
to
show
the
progress.
A
A
There's
no
official
way
that
you
can
subscribe
to
add
events
they
only
subscribe
when
the
span
got
finished.
The
second
is
the
way
I
described
is
a
misuse
of
adding
event
API,
it's
not
supposed
to
be
used
in
this
way
really
same
way.
The
behavior
is
undefined
according
to
oven,
clam
juice,
bag,
okay,.
A
F
A
A
A
A
Said
how
did
we
place
in
them
yeah
sure
and
a
wonderer
like
for
the
next
step,
like
we
know
like
for
tracing?
We
still
have
this
contacts
API
and
like
either
I
need
to
spend
some
time
here
or
I
can
work
with
the
intern
so
that
heart
shouldn't
be
too
big
and
for
the
next
part
like
vulnerable
metrics,
if
you
guys
have
expertise
or
any
of
you
want
to
walk
on
the
metrics
or
I
think
this
is
not
something
you
will
have
energy
I.
A
And
another
thing
is
the
matrix:
API
is
still
evolving,
like
I
have
a
full-time
developer,
working
on
the
c-sharp
and
he
just
finished
the
matrix
indentation,
and
now
we
were
told
that
magic
expect
change
again.
So
so
this
part
like
like
do
you
think
like
we
want
to
work
on
some
like
catch
up
the
spec
or
we
want
to
first
focus
on
traces
and
then
and
logs,
and
let
her
come
to
the
magics.
So
what's
the
preference
I.
E
Mean
for
me
personally
anything
for
the
project
when
I
throw
a
party
but
for
I
think
I
was
working
for
anyway.
I
liken
for
a
project
in
general
I
think
it
would
be
great
if
we
could
come
to
an
alpha
beta
release
date,
trust
for
traces,
so
basically
making
this
usable
for
four
people.
I
think
I
would
prioritize
this
higher
than
the
metrics
work
started.
Yeah
I.