►
From YouTube: SIG Instrumentation 20230202
Description
SIG Instrumentation Bi-Weekly Meeting Feb 2nd, 2023
A
I'm,
okay,
welcome
everyone
to
the
Sig
instrumentation
by
weekly
meeting
today
is
Groundhog
Day
February
2nd.
We
are
yeah,
so
we
don't
have
a
lot
on
the
agenda,
so
it
might
be
today
might
be
a
a
pretty
pretty
light
meeting.
A
A
A
Okay,
so
today
is
production,
Readiness
soft
freeze,
so
you
should
have
your
caps
with
the
prr
sections
filled
out.
If
you
have
a
cap,
but
it
is
a
soft
Breeze.
A
B
B
B
A
C
A
B
A
No,
no
there's
no
code
for
this
one.
Oh
the
code
was
in
Alpha.
So
that's
why
I
checked
it.
Yeah
I,
I'll,
I'll,
I'll,
amend
the
thing
cool.
A
This
one
this
one
shouldn't
there
shouldn't
be
anything
to
do
here
because
wasn't
this
approved
for
beta
before?
Why
are
we
doing
prr
review
again.
C
A
B
C
I
did
also
review
I.
Think
there's
a
question
about
monitoring
this
and
right
now.
Hotel
doesn't
have
good
metric
support
in
their
Trace
implementation.
C
A
A
C
A
No
do.
A
B
A
D
B
A
Okay,
let
me
do
my
PR
review
and
then
I'll
bother
him
afterwards.
Yeah
sounds
good,
okay
and
APS
over
tracing
this
one
is
is
pretty
much
handled,
so
we
can.
A
By
the
way,
this
one
is
stable
now
so.
B
A
It
it
was
slated
just
to
be
stable.
We
agreed
on
this
the
last
meeting.
A
A
D
D
Don't
mind
because,
like
the
flag
were
removed,
so
there
should
be
like
one
PR
that
removes
no.
They
were
removed
in
beta.
A
C
A
C
D
Okay,
yes
right
gig
like
At.
First,
we
wanted
to
maybe
broadened
your
foot
and
stop
getting
new
contributors
from
all
over
the
place
like
at
least
from
sea
country
decks,
but
like
since
it's
just
like
we
just
want
to
start
somewhere
in
terms
of
mentoring.
It
might
be
better
to
just
reduce
the
scope
to
just
see
instrumentation
people
in
general,
and
the
idea
at
first
is
to
try
to
find
mentors.
D
D
There
is
no
like
end
goal
to
the
mentorship
program,
like
it's
not
mandatory,
to
become
like
a
maintain.
You
know
or
I,
don't
know
after
the.
D
C
B
A
D
My
idea
with
that
was
to
like,
if
we
don't
have
a
hard
commitment
at
the
end,
it
could
still
grow
the
number
of
contributors
like,
even
if,
at
the
end
of
the
day,
we
like
don't
grow,
necessarily
the
number
of
maintenance.
We
grow.
The
number
of
contributors,
which
is
still
great
for
us,
but
for
sure,
like
the
end
goal
of
this
effort,
is
to
you
have
more
maintenance
and
yeah.
E
Yeah
and
you
just
to
add
on
yeah
just
to
add
on
on
the
what
you
said
regarding
the
six
month
period.
So
that's
the
third
point
there
regarding
onboarding.
If
you
scroll
up
so
we
have
decided
to
basically
accommodate,
for
you
know
the
workloads
that
different
people
experience.
So
if
they
are
not
able
to
commit
to
that
six
month
period,
they
can
also
you
know,
break
that
up
and
basically
talk
to
their
mentors
and
come
to
a
conclusion
that
you
know
I'll
I'll
work
for
three
months
and
then
I'll.
E
You
know
I'll
be
off
for
for
a
month
or
something
and
then
I'll
come
back
and
try
contributing
again
for
this
much
preview.
So
because
of
this
limited
tool
that
we
are
beginning
with
and
not
something
that's
released
us
which
is
basically
sending
out
forms
and,
having
a
like
a
very
large
Outreach,
we
are
aiming
to
basically
yeah
accommodate
for
that
basically
achieve
that
flexibility
between
the
contributors
and
the
mentors.
B
I
am
specifically
interested
in
like
finding
someone
if
they
are
interested
in
like
leading
the
Sig
I
know
that,
like
there
were
some
term
limits
that
were
kind
of
like
generally
thrown
around
like
within
contribex
and
steering
and
I,
don't
actually
know
if
any
of
those
things
will
merge,
but
we
have
not
been
okay,
they
have
not
been
but
like
nonetheless,
I
think
you
know,
I
have
been
doing
this
for
three
years
and
I
have
brought
in
like
we
as
leads
brought
in
Damien,
but
like
eventually
I
gotta
go
so
or
at
least
that's
how
I
kind
of
see
it
so
I
would
be
interested
primarily
in
mentoring,
someone
to
take
over,
like
say,
instrumentation
chair
for
me
at
some
point,
but
there
are
other
areas
that
I'm
having
to
Mentor
in
as
well
I.
D
It
is
mainly
that
like
we
would
try
to
have
at
least
at
least
of
people
that
would
be
interested
in
mentoring
or
at
least
like
if
they
have
a
knowledge
in
a
particular
area
and
feel
comfortable
sharing
it
with
someone
else,
then
for
sure
they
could
add
themselves
and
the
ages
also
like
to
get
these
documentaries
that
we
could
bear
them
with
and
like
it
doesn't
really
matter
where
these
people
are
interested
in
contributing
like
as
long
as
they
have
interest
in.
D
B
Makes
sense,
I
think
it
would
be
good
to
just
gather,
mentees
and
mentors
and
then
like
see
what
the
levels
of
experience
and
availability
are
like.
One
of
my
frustrations
previously
in
doing
mentorship,
programs
have
been
that
you
get
like
lots
and
lots
of
people
sign
up
to
be
mentored
and
then
like
they.
B
Just
don't
show
up
to
stuff
so
like
I
would
ideally
want
like
if
we're
going
to
be
putting
time
in
to
Mentor,
people
like
I
would
hope
that
they
would
be
putting
in
like
some
number
of
hours
a
week
like
I
would
much,
rather
things
be
blocking
on
the
mentor's
time
than
the
mentees
time,
but
unfortunately,
I
have
definitely
had
programs.
Where,
like
you
know
you,
you
set
up
like
a
meeting
or
a
session
to
like
walk
through
a
thing,
and
then
the
mentees
don't
show
up
so
I
want
to
avoid
that.
D
B
That
would
be
a
great
thing
to
add,
as
like,
like
either
a
pre-rep
requisite
or
like
part
of
the
commitment
or
that
kind
of
thing.
B
B
We
ended
up
getting
like
two-thirds
of
the
people
that
were
in
the
program
went
on
to
become
Sig
leads,
which
is
like
unheard
of
success
rates
for
a
mentorship
program
like
really
really
good,
but
I
was
hoping
that
I
could
maybe
share
like
we
have
a
curriculum
for
that
which
is
not
necessarily
not
necessarily
useful
here,
but
we
also
have
a.
B
There's
some
documentation
in
the
community,
repo
I
haven't,
found
the
specific
file,
but
I'll
at
least
there's
a
folder.
So.
A
So
the
way
I
would
do
it
is
I
would
require
bi-weekly
sync
meetings,
like
probably
30
minutes
in
length,
maybe
an
hour
initially
I,
don't
know,
and
then
time
for
Upstream
commitments
and
basically
like
smaller
tests
at
first
and
then
larger,
more
ambiguous
ones
as
time
progresses
and
also,
obviously
it
would
be
required
that
you
attend
the
triage
meetings
and
stuff
so
that
you.
B
Can
yeah
I
would
have
an
expectation
that
people
would
be
putting
in
a
minimum
of
one
one
to
two
hours
a
week
and
not
just
like
for
a
month
like
it
would
have
to
be
at
least
for
like
something
like
if
they
want
to
become
an
approver
or
they
want
to
become
like
a
lead
of
a
Sig,
or
something
like
that
like
I,
would
expect
them
to
be
participating
like
for
a
year,
or
at
least
for,
like
six
months,
to
become
like
a
reviewer
if
they
were
totally
brand
new
to
kubernetes.
So.
D
I
mean
to
to
be
fair,
like
the
reviewer
rules
like
in
my
personal
opinion,
should
be
given
to
anyone
that
wants
it,
because
it's
more
like
of
an
actual
like
job
like
to
do
Resident,
you
don't
have
any
responsibilities
when
you
are
a
regular
besides
like
having
to
go
through
peers
and
issues.
D
So
even
if
you
like
are
pretty
new,
you
should
be
able
to
go
through
PRS
and
give
you
ideas
and
opinion.
I
was
like.
B
I
totally
agree
with
that.
It
also
depends
on
what
area
of
the
code,
the
bar
in
practice,
for
becoming
like
a
reviewer
or
an
approver
in
kubernetes
kubernetes
tends
to
be
much
higher
than
the
project,
because
it's
much
larger
yeah
for
sure,
but
I
was
just
kind
of
thinking
like
from
the
you
know.
If
somebody's,
not
even
an
org
member,
then
it's
going
to
take
some
time
for
them
to
become
an
org
member
and
then,
like
you
know,
learn
enough
to
like
review
PRS
and
then
so
on
and
so
forth.
B
So,
ideally,
I
have
also
found
mentorship
programs
in
general
to
be
the
most
successful.
B
If
people
are
already
org
members,
because
it
demonstrates
some
like
basic
level
of
commitment
and
like
they
will
have
everything
that
they
will
need
in
order
to,
for
example,
like
review
a
PR
like
they
can
lgtm
stuff
but
like
we
can
also
maybe
offer
like
you
know
the
opportunity
to
sort
of
accelerate
like
if
they
are
not
an
org
member,
but
they
want
to
participate
in
this
we'll
hear
some
stuff
you
can
do,
and
if
you
do
that
for
a
month
like
no
problem,
we
will
sponsor
you.
A
C
B
C
A
With
mentoring,
people
who
were
not
organizers,.
B
I
think
it's
fine,
if
you're,
not
an
org
member,
are
they
outside
of
your
company,
though,
or
were
they
like
co-worker,
because
I
think
yeah
the
context
of
like
mentoring,
A
co-worker,
where
there's
an
expectation
that
you're
seeing
this
person
every
day
like
in
the
workplace
and
they
just
can't
like
they're,
not
gonna
ghost.
You
is
very
different
than
like
outside
the
company,
where.
C
B
I
have
been
ghosted
by
many
a
mentee,
so
it
is
a
little
bit
of
a
different
context
and
in
this
case
like
I,
don't
necessarily
I
mean
I
can
certainly
shop
around,
but
I.
Don't
necessarily
have
like
a
large
cohort
of
co-workers
to
pull
into
this,
and
so
like
for
me.
I
would
like
to
to
you
know,
broaden
like
who
I'm
able
to
work
with,
but
then,
like
you
know,
please
don't
post
if
I'm
gonna
put
in
my
time,
I
need
you
to
also
put
in
your
time.
D
I
guess
that's
one
reason
like
I
wanted
to
like
restrict
that
to
only
seeing
instrumentation
or
people
that
actually
attending
meetings
or
even
part
of
the
mailing
list
at
first,
because,
like
that
means
that
they
have
at
least
shown
the
interest
in
the
group
whereas
like
if
you
try
to
reach
out
to
sea
country.
Banks
like
you,
can
have
such
a
variety
of
of
contributors
and
mentees
that
it's
it's
really
hard
to
gauge,
and
then
you
have
to
select
them
and
so
on,
like
it's.
It's
annoying.
D
A
B
D
D
D
Oh,
you
don't
tell
me
well.
B
Introduction
you
might
want
to
just
shape
like
give
edit
his
permission
to
the
the
mailing
list,
so
that
way,
people
on
the
mailing
list
can
sign.
B
Good,
we
got
three
minutes
left
and
I.
Think
we
don't
have
any
agenda
left
I
just
wanted
to
call
out.
We
had
a
usage,
metrics
collector
sub
project
meeting
like
a
kickoff
last
week,
and
it
was
great
we
had
lots
of
people
show
up.
We
did
sort
of
a
an
overview,
and
next
week
we
have
an
hour-long
dive
schedule.
So,
if
you'd
like
to
come
to
that,
that's
going
to
be
on
Wednesday
at
10
a.m.