►
From YouTube: 2021-04-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
B
C
C
C
D
D
D
Oh
yeah,
I
remember
so
before
we
talk
about
our
release.
D
Let's
talk
about
whether
we
want
to
stick
to
the
release,
schedule
or
I
mean
get,
stick
to
the
sdk
version
numbering
or
allow
our
version
numbers
to
skew
and
potentially
go
faster,
because
I
tucked
with
honorag,
who
would
makes
a
good
point.
I
mean
that
that
it's
less,
what
is
the
less
mental
load
if
the
versions
are
in
sync,
so
kind
of
the
question
is:
do
we
have
you
know
if
we
have
a
compelling
reason
to
go
out
of
sync?
D
A
A
A
B
A
D
We
can
also
punt
on
this
for
now.
Until
you
know
something
comes
up,
that
really
is
compelling.
I
mean
right
now,
we're
in
sync
110
is
out,
so
that's
all
good
for
this.
A
A
We
currently
both
sdk
and
we
are
currently
thinking
about
essentially
that
we
just
going
to
release
next.
My
next
minor
version
every
month,
regardless
of
what
actual
changes
have
happened,
I
mean
miners
versus
patch
version,
so
we
just
always
assume
that
we
have
okay
yeah.
We
always
actually
have
something
for
the
minor
version.
A
A
A
A
B
A
A
C
D
B
B
B
We
don't
like
we
don't
have
many
guys,
that's
the
thing
so,
like
the
chance
of
a
break,
it
is
much
lower
than
something
else
which,
like
the
sdk
during
its
development,
it
was
breaking
every
week,
but
our
agent,
even
during
development,
it
wasn't
actually
breaking
that
often
like.
I
would
rarely
have
to
make
changes
downstream
for
agents
interested.
A
So
you,
you
assume
that
it's
okay
for
vendors
to
depend
on
snapshot,
assuming
that
vendors
are,
can
easily
change,
fix,
minor,
bra,
minor
baggages,
yeah
and
because
it's
a
we
have
a
particular
case
of
perth
or
organization
doing
vendor
distribution,
which
is
not
for
who
this
assumption
is
wrong.
A
A
A
And
if
you
pre,
if
you're,
writing,
custom
instrumentations,
it
depends
on
the
agent
aspi
api
as
well,
and
if
you
upgrade
them
out
of
sync,
who
knows
what
will
happen.
C
A
C
D
You
know
I
mean
we're
trying
to
lock
our
api
down.
I
think
the
auto
configure
the
sdk
auto
configure
extension
went
a
long
way
in
stabilizing
our
our
distro
api,
because
that's
what
people
should
be
using
for
the
most
part
and
then
let's
I
would
propose.
We
keep
them
in
sync
for
now
and
then,
when
something
comes
up
that
we
you
know
want
to
release
sooner
then
we'll
discuss
at
that
time.
You
know.
Do
we
want
to.
A
D
Bring
yeah
when
you
have
when
you
have
a
use
case,
I
mean
when
you
have
next
time
it
comes
up
that
you
want
to
release
a
vendor.
You
know
your
distro
sooner
bring
that
back
as
a
specific
item.
I
think
we
just
need
a
we're
lacking
a
kind
of
specificity
to
this
discussion.
It's
a
little
too
abstract.
A
C
A
D
This
in
here
I
wanted
to
chat
about
and
probably
should
chat
with
john
on
thursday,
but
I
know
we
had
sort
of
thought
about
getting
rid
of
this
in
favor
of
the
spring.
The
spring
cloud
sleuth,
boat,
hotel
and
directing
people
over
to
that
project
just
wanted
to
check
in
any
thoughts
that
you
had.
B
D
B
A
Yeah
one
one
point
is
how
how
stable
and
the
feature
completely
springs
loose
integration
right
now.
That's
the
first
question
and
the
second
question
is:
we
are
providing
cookie
providing
spring
boot
starters,
for
so
not
every
user
of
sprint.
Boot
use
sprint
cloud
and
so
bring
spring
cloud
dependency
just
for
tracing,
maybe
well.
No,
a.
D
B
A
D
D
Cool
then
I
won't
try
to
close
out
these,
possibly
we'll
look
at
them.
A
Plan
to
implement
so
that's
question
what
this
question
actually
mean,
so
we
want
to
add
these
instrumenters.
One
of
the
points
was
that
that
the
single
entry
point
both
for
traces
and
and
metrics,
do
we
have.
A
What
what
metrics
did
we
thought
think
about.
A
A
A
A
B
C
D
Fun
pr
and
I'm
just
just
running
the
builds,
but
oh
it's
the
continuation
of
that.
The
setting
the
reusing
the
request
for
in
the
test.
But
oh
man,
we
have
a
lot
of
http
client
instrumentation,
oh
yeah,
this
one,
the
don't,
create
duplicate
headers.
C
D
D
Issues
so
for
each
one,
that's
why
I
wanted
to
wait
for
that
one
years
to
emerge
to
not
create
massive
conflicts.
D
B
D
D
D
B
A
A
D
B
B
A
Just
in
case,
probably
not
an
issue,
if
we
are
talking
about.
A
Callbacks,
for
example,
that
that's
this
very
same
spring
rest
template
has
quite
different
method
signatures
depending
on
do
you
want
to
pass
call
back
or
not?
I'm
thinking?
A
C
A
I
will
be
on
vacation
in
week
and
a
half
for
a
week
and
a
half
I'll.
Just
just
let
you
know.
D
No,
it's
it's
spring
now,
where
you
are
like
it's,
I
don't
know
how
how's
the
weather
there
these
days.
D
C
D
So
yes,
I
would
not
blame
you
for
going
south
somewhere,
maybe
not
all
the
way
to
mexico.
A
We
have
around
17
percent
vaccinated,
mostly
elder
people
for
general
population.
They
promised
to
open
the
gates
in
somewhere
in
may.
B
C
B
D
It's
submerged,
oh
yeah,
that
was
the
the
our
wrapped
runnables,
the
wrapper
runnables
that
do
the.
D
B
D
B
B
D
D
B
D
B
C
D
Oh,
I
wanted
to
ask:
what
do
you
think
of
having
a
nightly
build
that
does
not
use
the
build
cash?
The
reason.
A
A
D
A
A
So
we
have
to
review
that.
I
think
I
think
I
think
we
we
do
want
both.
We
want
one
run
at
least
one
run
on
main
branch
without
cash,
and
we
won't
run
with
cash
to
populate
cash.
B
C
B
D
B
A
D
Cool
yeah,
I
first
thought
about
it
when
we
noticed
that
some
of
those
modules
weren't
getting
built
yeah
but
then
also
thought
about
it
again
when
the,
because
that
some
of
the
my
recent
prs
have
touched
like
some
base
things
that
so
it
runs
all
the
tests
and
it's
been
the
camel
stuff
was-
has
been
flaking
like
half
50
of
the
time,
and
I
was
kind
of
thinking
like
where,
if
yeah,
I
don't
know
how
long
that
you
know,
our
prs
have
been
not
running
the
camel
stuff,
whereas
if
we
ran
it
lightly,
we
would
run
across
that
sooner.
B
C
A
A
Should
we
or
do
we
want
to
use?
Oh
no,
no!
First,
what
about
our
ga
road
map,
which
we
like
totally
ignored
for
several
months?
Alright,
so
we
released
1.0
but
g.
B
Yeah
we
ideally
we
rga
by
the
time
the
collector's
ga
that's
sort
of
like
if
we
wanted
to
create
a
date,
that's
a
reasonable
date,
because
for
most
people
they
can't
use
it
if,
like.
If
they
care
about
the
word,
ga,
then
both
the
collector
and
the
agent
have
the
bga.
So
that
could
be
one
target
date.
If
you
want
one,
let's.
B
A
A
Do
we
want
to
have
some
visibility
and
tracking
for
our
like
large
initiatives
like
one
we
have
about
probably
about
instrumenters,
and
the
second
is
all
the.
A
C
A
A
I
have
two
goals
for
that:
one
is
to
align
contributors
efforts
because
currently,
when
contributor
comes
in,
they
have
200
issues
without
any
notion.
What
is
more
important,
what
is
less
important.
A
The
when,
for
example,
we
have
splunk
contributors
when
we
talk
to
our
manager
about,
we
want
to
work
on
this
and
that
thing
in
open
telemetry.
Sometimes
question
does
arise
like
why
exactly
these
things.
So
how
do
you
choose
your
work?
So
yeah,
that's
kinda
important
for
open
telemetry,
but
why
so
it's
easier
to
prioritize
our
time
for
our
employee,
like
employer.
D
A
D
I,
like
the
idea
of
you,
know,
having
sort
of
the
large
initiatives
sort
of
bucketed.
D
And
I'm
not
really
yeah
like
I'm,
not
too
worried
from
or
like,
I
feel
like
we're.
We
were
hitting
like
all
the
important
things
just
kind
of
going
forwards,
but
as
we
try
trying
to
pull
in
more
people
into
that,
I
agree
is
hard
because
a
lot
of
this
does
live
in.
You
know
the
four
of
our
the
maintainers
heads.
D
Even
just
like
yeah,
just
briefly
like
what
the
large
initiatives
are,
I
guess
we
could.
I
don't
know
it's
hard,
it's
a
struggle
with
the
over
like
try
spending
too
much
time
on
trying
to
like
project
manage
and
and
do
that,
but
they
do
like
totally
want
to
and.
C
A
Yeah,
but
the
this
meeting
is
for
maintainers,
the
so
thursday
yeah
okay,
but
for
example,
so
we
are
doing.
Is
that
instrumenters
work?
How
can
anybody
any
external
contributor
know
that
we
are
doing
that?
What
why?
What
for?
What
is
the
goal
of
that?
D
Knows
yeah,
but
how
like
that's,
why
I
want
to
like
be
clear
on
I
mean
I
don't
want
to
do
press
like
add
that
kind
of
process
or
something
just
for
to
say.
I
want
to
make
sure
that
it's
helping
our
you
know
velocity
and
if
it's
taking
away,
say
honorag
and
matayish's
time
who
are
focused
on
the
instrumenters
to
write
up
some
something
that
really
is
going
to
be
pretty
hard
for
anybody
else
to
just
jump
in
and
make
helpful
contributions.
A
For
example,
I
think
that,
in
case
of
instrument
of
us
at
least
some
description
of
like
half
a
page
of
what
we
are
doing
and
why?
What
is
our
goal
and
why
would
be
helpful
helpful
even
for
us.
A
A
C
A
So
I
I
think,
better
visibility.
What
is
our
big
priorities
right
now
can
be
helpful,
even
people
who
come
to
repository
and
they
will
see
more
clearly.
What
are
we
working
on?
They
know
where
to
help
either
with
ideas
or
contributions
and
yeah
and
discussions
and
whatnot
and
in
general
people
come
and
say
what
are
these
guys
doing
so.
A
D
Cool
yeah
yeah.
Why
don't?
If
you
want
to
give
that
some
thought
and
then
maybe
next
week
I
mean
like
we
could
split,
split
out
things
like
if
we
each
took
some
something
to
try
to
write
up.
C
B
D
B
Yeah
I
was
having
like
I
mean,
of
course,
some
of
it
is
just
because
maven
is
still
it's
one
of
the
oldest
package
managers,
but
still
the
best
one
npm.
If
it
fails
to
download
in
the
middle
of
downloading
it
just
does
it
just
leaves
that
half
downloaded
artifact
and
tries
to
use
it
and
your
build
fails.
Then
this
is
just
driving
me
insane.
So.
A
To
read
it,
that's
fine,
but
so
they
still
are
completely
data
dog
branded.
They
like
data
dog
everywhere,
still
like
at
least
half
an
hour
half
a
year
after
after
creation,
they
cannot
use
dotnet,
sdk
open
elementary
sdk.
A
A
Yeah,
I
guess
they
cannot
use,
they
cannot
use
open,
telemetry
api
for
the
time
being,
it's
totally
unclear
to
to
me
how
exactly
the
plan
to
do
it,
but
I
I
heard
I
I
heard
a
word,
a
reflection
too
much
so
that
they
are
going
to
rub
something
and
use
reflection
for
something
and
I
just
zone
out
in
horror
and
how
they
how
we
are
going
to
make
our
distributor
distribution
around
the
dotnet
uptrend.
It's
completely
unclear
because
that's
dotnet
is
such
a
huge
monolith.
A
Why
microsoft
don't
don't
contribute
into
dotnet,
auto
instrumentation.
A
D
Yeah
dotnet,
auto
instrumentation,
it's
it's
just
a
very
like
sdk.
I
mean
really
like
it's
just
a
very
entrenched
sdk
world
and
I
mean
there's
a
lot
of
fear
of
auto
instrumentation.
A
C
A
I
am
everyday
amazed
like
things
that
I
take
for
granted
in
our
java
java
world
to
how
they
are
totally
not
in
in
other
languages,
and
it's
it's
very
strange
for
me,
so
trust
in
john.
You
did
like
a
great
work
last
year
before
we
joined
and
well
hopefully
we
helped
a
little
bit
but
other
other
things.
B
D
C
D
To
have
the
the
maintainer
crew
that
we
do
is
pretty
pretty
talented
group
of
folks.
D
A
D
Well,
have
a
good
wednesday
and
have.
D
You
both
free,
I'm
still
trying
to
make
stuff
free
happen,
thursday,
friday.