►
From YouTube: 2020-09-16 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
Okay,
I
think
we
can
start.
Are
you
having
the
agenda?
I
put
this
here
david
about
your
pr
that
you
have
in
progress.
Is
there
anything
that
you'd
like
to
talk
about
in
regards
to
the
pr
with
I
mean
the
pr
that
you
have
in
the
java
sdk
that
begins
the
implementation
of
the.
C
Volume
support
it's
approved
by
bogdan.
It's
definitely
worth
taking
a
look
at
and
make
sure
I
didn't
make
any
boneheaded
mistakes,
but
his
last
request
was
for
readme
and
I
added
that
so
I
I
think
it
should
be
ready
to
start
playing
with.
C
Yeah,
so
the
next
next
piece
is
no
tlp
exporter
and
then
there's
also
at
that
point.
It's
really
simple:
to
go
back
to
the
log
for
j
extension.
I
added
and
put
in
support
there,
and
somebody
else
also
put
in
a
log
back
exporter,
so
should
be
able
to
get
both
those
going
at
once.
A
Okay.
Next,
then,
you
have
an
update.
D
Yeah,
just
briefly
so
my
cto
mike
and
we've
been
talking
to
christian
and
some
others
and
our
plan
for
stanza
is
to
apply
to
the
cncf
for
sandbox
status.
D
So
to
hang
the
project
over,
I
think
we'll
be
doing
that
in
the
next
two
weeks
or
so
just
need
to
do
a
few
things,
define
our
governance
process
and
whatnot,
and
then
the
hope
there
is
that
from
there
you
know
with
it
the
control
and
governance
more
shared
and
open
that
you
know
the
path
forward
can
be
more
clear
for
open
telemetry
and
that
this
can
become
a
standard
component.
D
Eventually
christian,
I
I
know
you,
you
probably
have
some
thoughts
on
this
and
I
don't
know
if
it's
worth
the
elaborating
at
all
on
on
what
the
process
has
looked
like
or
how
you
see
could
see
this
going
forward
from
here.
But
that's
our
that's
our
planned
next
step
here.
E
Yeah,
so
I
have
I
I
can
kind
of
not
a
ton
of
color.
I
think
I
need
to
add.
I
think
this
is
a
really
good
development,
and
you
know
you
guys
have
been
you
know,
leaning
in
really
hard.
You
know
to
get
this
done
and
you
know
obviously
there's
a
business
behind
that.
You
know
that
has
considerations
as
well
and
it
was
generally
failed
that
you
know
getting
it
into
the
cncf
umbrella.
E
You
know,
while
maintaining
an
identity
as
stanza
is,
is
you
know
basically
the
right
path?
And
you
know
it's
sort
of
you
know
it's
good
for
the
goose
and
the
gander,
and
you
know
from
that
perspective.
You
know
you
know.
I
would
consider
this
to
be
a
huge
step
for
the
observer,
iq
organization
to
basically
say
hey.
We
are
going
to
make
that
step
to
you
know,
put
it
into
or
we
made
a
decision
to
put
it
into
cncf.
E
You
know,
adopt
a
sort
of
open
governance
model
and
all
that
I
think
that
is
a
huge,
huge
step
for
the
organization,
and
you
know
I
I'm
super
happy.
I
can
only
applaud
it.
You
know
so
I
also
understand
that
you
know
observation
folks,
won't
you
know
they're
trying
to
establish
themselves
as
a
company,
and
you
know
they're
starting
it
out
by
you
know
you
know
throwing
their.
E
You
know
throwing
them
on
goodwill,
and
you
know
you
know
folks,
like
dan
and
so
forth,
behind
the
stanza
thing
and
that
they
would
understandably
like
to
get
some
some
of
the
halo
that
that
brings.
You
know
from
a
branding
perspective,
so
I
think
we
can
all
we
can
all
like
wrap
our
head
around
that
pretty
easily.
In
the
discussion
that
we've
had
was
pretty
clear
that
you
know
there
is
a
there's,
a
midterm
path
to
align
this
even
closer
with
open
telemetry.
E
I
I
just
think
the
initial
hurdle
of
getting
you
know
getting
it
into
cncf
is
just
in
many
ways,
probably
the
biggest
hurdle
of
them.
All.
I
think
most
of
the
really
important
things
are
gonna
get
cleared.
So
I'm
super
happy.
So
you
know,
then
I
have
like
just
one
question.
You
know
coming
out
of
the
conversation
that
we've
had
yesterday,
so
there
were
basically
you
know
two
things
that
were
suggested
right.
E
One
is,
you
know
to
to
basically
aim
for
like
a
top-level
project
for
stanza,
or
you
know
the
alternative
that
sarah
and
rodney
kind
of
proposed
was.
It
is
certainly
worth
considering,
or
something
that
I
didn't
even
actually
realize
was
possible
was
to
have
it
as
an
open,
telemetry
subproject.
D
I
think
the
preferences
for
a
standalone
project,
but
if
I
think
that
would
be
open
to
you,
know
further
conversation
about
that
like
if,
if
they,
if
there's
a
case
to
be
made
that
that
would
be
easier
for
everyone,
then
I
think
that
we'd
certainly
be
open
to
that.
So.
F
F
If
you
think
the
majority
of
your
use,
cases
will
be
using
stanza
on
its
own
probably
makes
more
sense
to
make
it
a
separate
cncf
project.
But
then
it's
sort
of
continuously
integrated
with
the
collector.
D
I'll
I'll
take
this
back
to
mike
the
question,
because
I
think
it's
a
good
it's
a
good
question
but
yeah.
I
think.
F
It's
certainly
faster
to
make
it
a
sub
project
of
open
telemetry,
but
I
don't
know
if
that's
what
you're
optimizing
for
it
makes
the
integration
slightly
easier
and
cleaner,
just
because
it's
like
one
meeting
with
the
same
people,
but
you
know
selfishly,
like
speaking
with
my
open
telemetry
hat
on.
That
would
be
great.
I
can
understand,
though,
like
if
you
wanted
a
separate
sub
project
that
you
know
makes
some
kind
of
sense
that,
because
I
happen
to
know
a
lot
of
your
use
cases.
A
Anyway,
it's
it's,
I'm
also
very
happy.
Like
christian
said,
I
think
this
is
a
very
important
step
forward,
whether
it's
a
separate
project
in
cncf
or
a
sub
project
in
open
climate
iii.
I
think
it
will
help
us
a
lot
with
having
tighter
integration
working
together
right.
A
It
would
be
great-
let's
say
if
it's
a
separate
project
in
cncf,
if
there,
if
in
the
governance
of
that
project,
there
were
some
inflammatory
people
involved
as
well.
That
would
be
a
good
approach.
I
think,
but
either
way
I
like
this
a
lot.
This
is
very
good
guys
in
the
meantime.
While
we're
solving
this,
I
think
we
could
also
move
forward
with
the
specific
implementations
right.
D
Yeah
yeah
we'd
still
like
to
do
that,
and
we've
been
we've
been
moving
forward
on
our
end
with
that
as
well.
I
know
it's
taken
a
little
longer
than
expected,
but
I
think
we've
increased
the
scope
a
little
bit
as
well
of
what
we
were
trying
to
do
so
yeah
I
mean
just.
I
can
update
very
quickly
on
that.
D
You
know
so
we
modularized
our
operators
so
that
you
can
import
them
one
by
one
so
that
we
can
start
by
importing
this
just
very
like
file
input,
json,
parsing,
regex,
parsing,
the
very
basics
and
we've
been
hardening
our
file
input
operator
we're
working
on
integrating
with
the
testbed
writing
integration
tests.
Those
are
coming
along
and
we
also
you
know
in
the
previous
pr
tigran.
You
suggested
that,
like
a
utility
that
can
assist
with
testing
like
log
rotation
and
things
like
this
would
be
useful.
D
So
we,
what
I
did
is
I
forked
lumberjack,
which
is
a
popular
open
source
file,
rotation,
library
and
just
stripped
it
down
and
kind
of
customized
it
for
testing,
so
that
it's
just
very
precise
in
the
way
that
it
rotates
files
after
writing.
End
lines,
for
example,
also
enhanced
it
to
support
alternate
rotation
patterns.
D
I'm
sure
there
are
more
patterns
that
we'll
come
up
with
that.
We
want
to
support
eventually,
but
for
now
it
supports
a
couple
of
basic
things
and
then
so
we're
using
that
in
our
own
tests,
and
then
I
think,
if
it
makes
sense,
we'll
use
those
in
the
integration
and
test
bed
tests
as
well
as
a
way
to
exercise
the
especially
the
file
input
operator.
D
Given
that
that's
going
to
be
such
a
critical
one
so
that
pr
is
still
coming
along
and
I'll
have
that
for
you
probably
late
this
week
or
early
next
week.
So.
A
Okay
sounds
good
excellent.
Thank
you,
good
good,
we're,
making
steady
progress,
I'm
very
happy
in
all
fronts,
right
both
with
sdk
side
of
things
and
with
collector,
although
we
are
a
very
small
fraction
of
the
people
of
entire
telemetry
who
are
still
making
progress.
This
is
very
good
thanks
everyone,
and
thanks
christian
for
for
for
leaving
the
initiative
here.
Thank
you.
No.
D
A
A
G
B
B
It'll
be
doing
fine,
I
think
it's
a
great
company
yeah,
all
right.
You
guys
alrighty.