►
From YouTube: 2021-07-29 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).
C
I'm
not
leaving
the
meeting,
I'm
not
sure
who's
leading
the
meeting.
A
It's
usually
austin,
but
he
is
on
paternity
leave,
so
yeah.
C
C
Yeah
it's
I
mean
I
I
I
joined
to
this
working
group
to
be
a
collaborator.
To
be
honest,
so
yeah
yeah,
I.
C
C
Yeah,
it
would
be
super
nice
to
have
like
jonathan
here,
because
you
know
we
can
get
an
overview
of
what
are
the
next
steps
like
where
exactly
they
are
in
terms
of
like
conversations,
there's
been
some
high
level
conversations
around
like.
What's
the
scope
gonna
be
like,
should
it
be
an
ebpf
specific
thing,
or
should
we
be
more
like
you
know,
networking
diagnostics
it's
by
looking
at
the
you
know
the
working
group's
name.
I
assume
that
they
are
going
with
ebpf
there's.
A
A
C
Up,
sorry,
okay,
so
I.
D
D
Yeah,
it
happens
sometimes,
last
week
I
think
ted
was
there.
I
just
pinged
him
now
and
ted
young
yeah.
A
D
A
Yeah
I
was
just
reading
the
notes
from
the
last
one
which
I
missed.
So
I
didn't
did
you
check
for
any
open
issues,
because
we
can
definitely
talk
about
those.
D
I
did
not.
I
had
a
fortunately
a
one-on-one
with
ted
young
earlier
this
week,
I'm
from
the
cncf.
D
Tech
docs
team
I've
been
copy
pasting,
my
my
questions
from
from
week
to
week
hoping
to
to
talk
to
somebody,
but
I
got
my
questions
answered
well,
most
of
them
from
ted
earlier
this
week.
Okay,
so
I
I
was
joining
today,
just
to
say,
hi
see.
Who
else
was
there
hi
from
bzo.
B
Likewise,
first
time
I
meet
with
you
all,
I
wanted
to
join
this
meeting
before
the
august
break
off
for
the
entire
month,
but
I
also
wanted
to
say
hello
and
introduce
myself.
Maybe
I'm
currently
working
at
splunk
on
open
telemetry
under
open,
tires
distribution,
documentation
and
I
previously
worked
new
relic,
but
I
was
doing
infrastructure
docs
there,
so
yeah.
B
My
main
interest
here
is
to
help
improve
control
energy
documentation,
the
upstream
one
also
because
it
has
you
know
we'll
link
it
a
lot
and
it
just
doesn't
make
sense
from
our
perspective
not
to
have
this
that
documentation
in
good
shape
so
yeah.
Here
I
am.
A
Yep
cool
yeah
and
I'm
jonah
cowell,
I'm
the
cto
at
logs
io
and
I
joined
this
to
help
there's
some.
There
were
some
resource
challenges
around
like
graphics
and
other
things
like
that.
So
I
pulled
team
members
from
my
organization
to
work
on
it.
A
So
I'm
just
more
helping
out
with
the
you
know
the
website
and
the
you
know
some
of
the
I've
done
a
bunch
of
contributions
to
it
and
great
registry
and
a
bunch
of
other
stuff
that
I've
contributed
to,
but
I
just
hadn't
joined
in
about
a
month,
so
I
was
just
checking
in
to
see
if
austin
was
gonna
jump
on.
If
there's
anything
pressing.
I
just
had
a
quick
look
through
the
issues.
I
didn't
really
see
anything
too
pressing.
A
Most
of
the
requests
in
the
repository
are
about
like
zoom
and
other
things
like
that.
That
aren't
really
in
scope
for
this
discussion
anyway.
So
okay.
D
A
A
Not
a
maintainer,
but
I
do
reviews
and
done
a
bunch
of
contributions.
Okay,.
D
D
And
there's
the
depend,
a
bot
complaining
about
versions
so
probably.
A
A
Yeah,
I
don't
know
who
else
is
admin?
Did
you
talk
to
ted
about
that
last
week
at
all.
A
D
Okay,
so
I'm
slated
by
the
cncf
to
work
about
80
of
my
time
on
open
telemetry,
especially
with
the
the
merger
and
websites
and
documentation,
spread,
spread
out
here
and
there.
So
I'm
gonna
be
available
to
help
make
that
better.
A
Yeah,
I
was
just
dropping
austin
a
message
as
well
see
if
you
can
take
a
look
at
the
vrs
yeah,
the
other
person
that
was
doing
a
bunch
of
it
steve.
I
was
seeing
if
he
was
here
steve
flanders.
I
think
he's
at
swank
too.
Isn't
he.
A
A
Okay.
So
let's
not
bother
morgan
if
we
don't
need
to,
but
he'll
be
the
next
step.
Just
because
he's
not,
he
sometimes
joins,
but
he
doesn't
like
do
a
lot
of
contributions
really
so,
okay,
okay,
we
don't
really
have
a
channel
for
this
particular
piece.
I
don't
believe
like
on
slack,
so
I
guess
I
can
just
update
the
document.
If
I
hear
back.
D
D
If,
if
either
of
you
have
suggestions
for
the
docs
that
please
feel
free
to
open,
open
an
issue
or
I'm
on
slack
on
the
cloud
cncf
slack,
you
can
reach
out
to
me.
D
A
To
what
fabrizio
said,
we
have
our
own
docs
and
then
we
just
try
to
link
as
much
as
we
can
to
the
main
repo,
but
we're
a
pretty
small
company.
So
we
don't
have
you
know.
I
have
a
couple
tech
writers
in
the
company-
it's
not
like
over
at
splunk,
where
you
probably
got
a
team
of
people
dealing
with
yeah.
B
Yeah
yeah,
we
have
them,
but
very
few
contribute
to
docs
upstream.
Actually
I
was
iron
joseph
for
that
reason,
because
I
have
been
working
on
open
source
before
and
yeah
I
mean
I'm
mostly
trying
to
figure
out
right
now.
You
know
what
what's
the
pace
of
the
of
the
main
dogs
project?
What
sort
of
issues
I
could
contribute
to
what's
the
best
way
to
contribute.
A
Yeah
pretty
much
whatever
you
want,
because
it's
very
slow
so
any
reasonable
contributions,
I
think,
would
be
helpful.
I
know
I
did
a
bunch
of
work
on
the
tutorials
which
were
not
good
previously,
there's
still
a
bunch
of
tutorials
that
I
personally
can't.
I
just
don't,
have
the
technical
background
in
like
dotnet
like
if
you
notice,
like
compare
the
java
documentation
yeah
to
the
dotnet
and
the
instrumentation
examples,
and
like
all
of
that,
stuff's
just
missing.
D
This
is
one
of
the
things
that
I
I
one
of
the
one
improvement
I
I
was
going
to
suggest
in
that
respect
is
to
use
git
sub
modules
is
something
I've
done
on
other
projects
to
link
in
the
documentation,
rather.
C
B
I
think
that
that
might
be
more
reliable
than
some
modules
like
I
haven't
had
good
experience
with
some
models.
In
the
past
they
tend
to
break
a
bit.
So
most
solutions
and
most
alternatives
have
heard-
is
in
the
pipeline.
Having
you
know,
shell
commands
just
to
fetch,
either
through
w
guerrero
europe
as
a
version
of
the
other
dogs,
unzipping
them
putting
them
in
place,
which
you
know
it's
lots
of
yeah
lots
of
maneuvering,
but
I
mean
we
should
check,
maybe
like
some
modules.
D
I
don't
know
my
experience
has
been
including
websites
that
I've
worked
on
at
google.
We've
we've
had
sub
modules
for
a
couple
years
now
and
and
it's
been
working
fine,
there
hasn't
been
any
issue
that
we
I
if,
if
you
can
think
of
a
specific
quirk
or
scenario
in
which
things
just
break
or
don't
you
know,
go
back.
B
But
yeah
I'll
try
as
a
local
expert
here,
but
I
think
the
models
should
be
the
way
to
go.
You
know
at
least
we
can
test
it.
A
Yeah,
so
the
issue
is
that
the
documentation
and
the
repository
in
the
all
of
the
other
projects
is
inconsistent
with
the
documentation
on
the
main
site
and
we
can't
like
we
can
ask
nicely
or
provide
guidelines
to
the
instrumentation
projects,
but
it's
decentralized
so
like
there's
no
way
to
like
say:
hey
everyone
do
this
easily,
but
we
can.
I
think
we
have
to
do
that
if
we're
going
to
sub
module
right.
D
Well,
with
sub
modules,
it's
essentially
a
pull
model
that
they
you
don't
the
instrumentation
maintainers,
don't
have
to
worry
about
doing
anything
other
than
saying.
Okay,
docs
are
ready
or
the
next
iteration
is
ready,
or
you
know,
depending
on
how
we're
publishing
things.
If
we
want
the
absolute
latest,
you
can
get
updates.
You
know.
B
Every
week
I
think,
yeah,
I
think
it's
more
of
a
constant
strategy
issue
where
we
have
to
align
all
the
instrumentation
repos
using
the
kind
of
minimum
viable
content
they
need
to
have
in
there,
so
that
we
can
pull
it
in
right
now.
I've
seen
it's
very
uneven,
as
as
jonah
said,
javadocs
has,
you
know
just
way
more
well,
I
guess
it's
also
a
reflection
of
the
the
different
degree
of
maturity
of
each
instrumentation
distribution,
but
it
would
be
nice
to
somehow
think
think
about
the
minimum
content
we
should
have
like.
B
For
instance,
I
don't
know
configuration
patient
configuration
settings,
a
patient
getting
started.
You
know
something
like
that
just
for
each
and
maybe
we
could
start
with
one
language
and
then
take
it
from
there.
I
think
that
could
be
an
approach.
A
Agree
now
the
other
challenge
is
right.
Now
all
the
versions
are
not
aligned
so
like
you
could
use
one
version
of
a
collector,
a
different
version
of
the
instrumentation
and
you'll
notice
on
the
docs
page,
there's
no
versioning,
yet
that's
something
I've
talked
to
austin
about
before,
like
if
you
look,
I
work
on
jaeger
a
lot
as
well.
A
I
commit
a
lot
there
and
in
the
documentation
we
have
the
versions
on
a
pull
down,
so
you
can
pick
you
know
the
docs
and
every
time
we
do
a
release,
the
docs
get
packaged
with
the
release
in
otel.
You
can't
really
do
that
because,
like
when
java
just
did
a
release
yesterday
and
the
collector,
we
did
a
release.
You
know
a
few
weeks
ago
and
everything's
like
misaligned,
so
it's
really
hard
to
like
have
an
external
dock
site
that
reflects
the
right
versions
of
the
right
things.
A
So
I
added
some
notes
on
to
the
doc
by
the
way
of
our
discussion.
A
A
A
So
yeah,
I
think
anyone
would
be
up
for
better
docs
upstream
for
sure.
D
Bias
so
I'm
I'm
wanting
to
test
that
channel
for
newcomers.
There
may
be
a
need
to
move
over
some,
some
of
that
material.
D
D
A
A
B
I
I
can
see
now
that
one
issue
for
the
getting
started
is
there's
like
a
lack
of
parallel
construction
like
if
you
click
the
say
the
elixir
getting
started
is
starts
slightly
differently
than
says
the
the
go
one
or
the
child
one.
B
So
and-
and
that
brings
the
experience-
maybe
a
bit,
whereas
if
you
go
to
open
tracing
everything
is
in
there
it's
a
bit
messy,
maybe,
but
you
get
everything
there
and
I've
seen
I've
seen
getting
started
tutorials
in
for
other
products
out
there
with
just
like
a
tapped
interface,
where
you
simply
choose
each
language,
you
know,
and
then
there
are
common
steps.
So
this
is.
D
B
On
a
slightly
related
note,
I
just
wanted
to
share
like
this
this
crazy
idea
at
well
getting
acquainted
with
telemetry.
I
don't
know
if
you've
ever
heard
about
that
website,
which
is
apache
kafka
for
kids
for
children.
It's
like
a
children
book
explaining
apache
concept.
If
I
die
for
you
and
you
know
I
was
just
thinking.
It
would
be
great
to
have
something
like
that
from
television,
because
it's
way
more
adult
than
it
seems-
and
that
is
also
like
very
viral-
not
a
priority
at
all.
B
But
it's
more
like
a
nice
to
have
idea
kind
of
look
for
dates.
B
B
I
was
wondering:
do
we
have
like
a
roadmap
for
say,
communication,
documentation
somewhere
just
a
link
so
that
you
know
I
might
start
thinking
about
initiatives.
But
I
wouldn't
want
to
reinvent
the
wheel
or
overlap
with
existing
efforts
or
plans
or
anything.
A
I
haven't
seen
a
roadmap.
I
think
it's
mostly
been
tactical
trying
to
fix
stuff
really
and
there's
not
a
lot
of
people
participating
in
it,
so
austin's
definitely
doing
80
of
the
work.
So
when
he
went
out
on
paternity
leave,
we
were
like
we
don't
know
what
we're
gonna
do
if
something
has
to
get
done,
which
is
why
there's
all
those
pr's
he's
been
gone
for
almost
a
month?
Now
I
want
to
say:
okay,
okay,
so
we
can
get
down
and
look.
He
said
he
was
gonna
check
in
every
once
in
a
while.
A
D
A
D
B
All
right,
all
right
so
in
terms
of
the
collaboration
model,
because
this
is
the
first
time
I
I
work
in
a
big
open
source
project
like
this
and
steve
said
something
along
the
lines
of
you
know
to
get
started
like
file
a
pr
and-
and
that
is
like
some
sort
of
requirement
to
get
into
the
the
group
or
something,
but
I
don't
know
how
it
works.
Really
I
I
know
I
got
an
mri
merged
into
each
other
little
dogs.
But
beyond
that,
like
how
should
I
get
started
to
be
like
more
involved.
A
If
you
have
questions
about
something
open,
an
issue
in
github
and
explain
the
problem,
there's
a
template
in
there
that'll
kind
of
guide
you
through
opening
the
issue
and
what
you
should
include
and
then
it's
either
discussed
in
github
or
if
there
are
further
questions.
We
end
up
discussing.
B
A
Nope
maintainer
will
approve
your
pull
request
and
then
the
the
website,
I
believe,
is,
I
think,
it's
on
netlify
or
something
like
that.
So
it
has
an
automated
system
once
it's
approved,
then
it
gets
pushed
out
automatically
and
you'll
see
the
changes
so
yeah
excellent
yeah,
but
there's
no
it's
very
informal
in
most
projects.
This
is
especially
informal
because
there's
so
few
people
working
on
it
this
part
so.
D
Fabrizio,
if,
if
you
feel
inclined
to
ping
me
now
and
again,
if
you
know
what
you
want
to
work
on
sure
just
let
me
know
if
you
want
to
work
on
the
get
started.
B
B
I'll,
probably
at
some
point
like
take
note
about
the
documentation
potential
documentation
improvements.
I
see
that
weren't
filed
at
any
time
I
was
wondering,
is:
does
the
foundation
have
some
sort
of
internal
documentation
system
or
google
drive
folder?
Anything
where
say,
if
I
want
to
say
take
note
of
all
the
things
I
see.
Should
I
just
raise
issues
in
github
or
do
you
maintain
anything
internal
or
is
still
transparent.
B
Okay,
that
would
be
the
the
closest
to
say,
a
roadmap
that
we
could
have.
D
B
D
And
again,.
B
B
Yeah,
as
as
I
told
you
I'll
I'll,
be
off.
B
But
then
I'll
come
back
in
september
and
we
have
also
lots
of
work
at
splunk
to
either
for
I
believe.net
and
a
node.js
hotel
so
also
work
there
and
I'm
pretty
sure
we
will
spot
improvements
upstream.
Also.
B
B
Yeah
I
mean
some
people
are
less
aware
of
the
importance
of
this,
especially
in
documentation
teams.
It's
like
you
know
at
least
tech
writers,
as
blank
are
very
adamant
about
just
having
dogs
in
our
side,
but
it's
part
of
what
I'm
trying
to,
especially
for
telemetry,
I'm
trying
to
appreciate
this
message.
That
is
all
part
of
the
same
ecosystem
and
we
must
tend
to
it
as
a
whole.
So
yeah
we'll
see
how
that
goes,
but
to
count
on
my
support
for
sure
great.
B
You
well
I
I
gotta
go
now,
but
I
enjoyed
this
this
conversation
and
hope
to
see
you
around,
especially
on
github,
see.