►
From YouTube: March 2020 SIG Chair/TL Mtg: Cluster Lifecycle Triage
Description
@neolit123, Chair of SIG Cluster Lifecycle discusses their way of issue/PR triage
A
Mm
mm
mm
every
week,
but
if
it's
filtered
well,
we
can
still
track
what
you're
interested
in
so,
for
instance,
I
know
the
team
copiously
that
he
watches
KK,
but
he
has
filters
for
sig
network.
He
sees
his
assignments,
so
it's
definitely
doable
with
Gmail
I
just
want
to
share
my
thoughts
on
that
and
I
have
a
water
filters
or
sub
projects,
and
this
is
like
my
father
for
direct
mentions
now:
okay,
because
I'm,
not
watching
KK
in
particular,
and
because
sequence
lifecycle
only
maintains
Kapadia
meters
of
KK
I
basically
have
on
demand
link
here.
A
So
every
time
somebody
mentions
cue,
medium
I
can
appear
like
a
boogie
man
on
their
ticket
very
much
and
I.
Basically
just
look
what
they
are
doing,
why
they
are
using
comedian.
Where
is
the
bug
and
I
use
this
as
a
method
potentially
to
also
modify
other
six,
because
Kapadia
miss
a
high
level
too
and
often
times
it
may
be
a
bug
in
the
couplet,
for
instance,
so
I
am
going
to
remove
sequence,
lifecycle
or
area
/,
give
a
diem
and
I'm
going
to
assign
signal.
A
So
this
is
in
a
way
at
three
hours
that
I'm
doing
for
Cuba
name
in
particular,
but
if
also
this
is
not
really
a
cube.
Like
I
said,
if
this
is
a
serious
bug
for
Cuba
D
I'm
going
to
close
the
cake
a
ticket,
because
you
have
a
separate
repository
medium
and
it's
here,
so
we
this
moves
the
ticket
outside
of
kaykai,
basically
into
the
dedicated
issue
tracker
for
this
project,
also
something
that
I'm
doing
over
pretty
much
regular
basis
as
well.
A
We
say
just
click
issues
without
any
filters
and
I
go
through
the
issues
from
you
know.
I
cannot
read
everything,
but
I
go
on
a
quick
glance
if
something
needs
a
seek,
or
if
just
the
title
is
interesting
to
me.
I'm
going
to
click
look
inside
potentially
a
sinus,
sick
or
just
I
may
I
can
also
pink
people
directly.
I
can
mention
them
if,
if
I
think
this
needs
escalation
of
priority.
A
A
This
one
appears
with
a
cube:
a
DM
label,
I,
obviously
triage
for
the
chameleon
pairs,
but
I.
Also
look
at
the
other
peers
like
what
everything
that
is
going
to
medium
are
soaring.
Kk
I
also
look
at
it,
for
instance,
if
this
is
a
small
type
of
fix,
and
it's
outside
of
code
freeze
I'm
just
going
to
okay
to
test
it
so
I'm
just
going
to
help
the
contributor,
by
enabling
the
tester
to
run
and
to
help
them
get
on
board
faster,
because
I
seen
peers
get
stale
with
a
simple
type
of
fix.
A
Obviously,
something
is
like
a
critic
of
urgent
I'm
going
to
look
at
it
as
well
the
applications,
but
this
is
like
it
becomes
a
question,
was
how
much
time
do
you
have
for
today
and
like?
Are
you
really
interested
in
some
of
these
adjacent
peers
to
your
area
because,
for
instance,
if
you
work
on
strictly
on
the
couplet,
it
might
also
not
be
interested
in
I.
A
Don't
know
a
comedian,
because
it's
a
high
level
to
higher
level
to
so
you
might
break
you
medium,
but
at
the
same
time
the
comedian
maintenance
is
there
as
possibility
to
also
watch
change
in
the
corporate
I
mean
I
can
also
explain
how
we
do
particularly
shoe
triage
in
the
for
a
scenic
you
media
repository.
If
you
want
that.
B
Why
why
is
it
different
and
that's
a
you
know
it
just
a
general
question:
why
do
you
do
triage
differently
per
repo
or
a
project
I
think.
A
This
is
related
to
the
cap
that
we
are
currently
working
on
as
well.
I
think
it's
always
important
to
measure
the
volume
to
be
able
to
figure
out
what
is
the
demand
for
triage?
So
KK
is
a
massive
volume,
and
so
it
has
to
be.
There
has
to
be
ways
to
delegate
the
responsibility
across
different
people,
and
other
projects
are
doing
that,
but
by
you
know,
either
a
chain
of
command
type
of
pattern,
or
they
are
basically
splitting
stuff
into
modules
separately.
Posters
in
case
you
cannot
wash
everything
I
mean.
A
Even
if
you
have
a
team
of
10
people,
you
cannot
watch
like
everything
that
is
coming
in.
You
cannot
even
guess
if
a
certain
ticket
is
affecting
your
particular
area,
you
just
have
to
look
at
it
and
it
becomes
very
difficult
at
the
difference
here
with
cue,
medium
and
other
projects
outside
of
KK.
Is
that
they're
much
smaller
volume,
so
I
can
show
you.
A
If
I
go
to
Cafe
diem,
we
have
80
issues
here
and
I
would
argue
that
this
is
a
like
an
example
of
a
repository
that
is
very
well
managed
because
we
have
like
you,
can
see
the
ratio
here.
A
What
we
do
on
a
regular
basis.
We
look
for
new
issues.
We
move
stuff
around
close
them,
like
the
other
day,
I,
pretty
much
moved
all
of
the
tickets
to
the
118
sorry
119
miles
long,
a
118
was
all
applicable
because
we
are
in
countries
and
also
I
I
can
go
through
all
these
80
tickets.
I
know
what
they're
about
like
I
have
the
I
have
them
in
my
head,
because
I
have
already
dressed
this.
A
So
this
is
an
example,
something
that
is
very
low
volume.
A
cubed
M
is
also
G.
A
is
much
more,
so
it's
quite
different
than
what
is
happening
in
KK.
Kk
is
very
fast-moving.
It's
you
know
a
lot
of
moving
parts.
Different
owners
there
is
a
mixture
of,
for
example,
can
what
is
the
triage
like
a
support
ticket?
B
Thank
you
so
much
Lumiere
I
am
gonna,
cut
you
right
here
and
ask
for
questions
from
folks,
so
that
we
can
do
a
open
discussion
and
talk
about
what
some
other
folks
are
challenging
or
with
some
of
the
challenges
and
things
effects
are
seeing.
Does
anybody
have
any
questions
directly
for
Lumiere
right
now,
as
far
as
what
he
just
showed?
Yes,.
C
So
I
think,
what's
different
about
sit
closer
life
cycle
is
that
y'all
actually
I
think
it
are
one
of
the
only
things
that
has
a
grooming
dock?
That's
in
the
that's
in
the
community
repo!
You
also
actively
use
the
life
cycle
active
label
which
not
a
lot
of
people
do
so.
Can
you
talk
about
how
you
move
something
from
maybe
not
triaged
into
life.
Psychoactive.
A
A
So,
like
the
other
day,
I
load,
the
ticket
and
I
said
hey.
I
need
help
on
this
good
first
issue:
it's
a
cleanup
and
it's
low
priority
and
I
said
here
is
what
you
have
to
do
like
it's,
a
pretty
simple
change.
You
just
have
to
go
up
an
error
and
from
there
we
got
some
folks
coming
by
and
saying:
hey
I
cannot
work
on
this
and
someone
actually
I,
don't
know
how
they
know
about
the
labor
even
but
they
use
this
label.
A
So
now
they
are
pretty
much
assigned
because
I
look
at
this
person's
github
header
of
their
message.
I
see
that
they
are
not
a
member
I.
Don't
think
that
actually
came
seeded,
the
seed
is
here,
but
they
are
probably
not
a
member
and
that
that
is
one
of
the
actually
I
think
he's
probably
a
member,
but
the
difference
between
assigning
someone,
a
lifecycle
active
is
that
you
can
basically
say
that
somebody's
working
on
the
issue,
even
if
they
are
not
a
member-
and
this
was
the
original
argument
for
adding
this
lifecycle
label
exactly.
A
As
you
can
see
the
people
that
know
about
it,
they
can
just
like
they
can
say:
okay,
I'm
working
on
this
already,
if
they're,
not
a
member,
that's
the
only
way
to
indicate
that
somebody's
working
on
the
ticket.
If
for
some
reason
they
disappear,
the
fatal
bot
is
going
to
kick
in
and
mark.
The
issue
is
fail
because
the
last
cycle-
a
boss,
overrides
themself,
like
her
life
cycle,
say
I
was
going
to
remove
life
cycle
active.
A
C
Look
words
this:
does
the
lifecycle
active
the
I
know
the
like
a
little
stale
label
likely
removes
like
psychoactive,
but
mechanically
the
labels?
Don't
remove
each
other
fada
about
actually
issues
the
the
bot
command
to
say,
remove
lifecycle
foo
to
do
that,
it
doesn't
happen
that
happens
within
the
issue,
not
within
browse
magic
land.
C
Yeah
I
guess
I
guess
what
is,
what
is
the
so
I
guess
like
exiting
exiting
triage
for
me
would
mean
that
the
issue
has
enough
details
to
proceed
right.
That
has,
it
may
be
assigned,
or
it
may
have,
like.
You
said,
the
the
Help,
Wanted
or
good
first
issue
labels
on
it
is
that
kind
of
the
same
mechanisms
that
you
go
with.
A
A
Yes,
okay,
but
life
psychoactive.
This
is
this
was
an
argument
where,
when
we
created
the
label,
it's
more
of
a
case
when
it's
useful
for
like
in
conjunction
with
a
calming
PR.
So
if
imagine
that,
if,
if
you
apply
this
label,
there
has
to
be
a
PR
that
comes
after
so
it's
an
issue
that
is
actionable
and
it's
not
a
ticket
that
has
been
triaged
and,
for
instance,
requires
more
discussion.
It's
it's
an
actionable
ticket.
This
was
something
that
we
like
design
the
the
label
to
be
so.
C
A
I
have
made
available
both
the
label
multiple
times,
because
the
fatal
bot
is
going
to
kick
the
stale
label
in
2090
days.
So
it's
like
three
months
I
think
I
got
cases
where
I
know
that
somebody's
not
no
longer
working
on
this.
They
said
to
me
in
slack
so
I
mentally,
go
here
and
I
labeled
our
psycho
active
label
and
maybe
are
a
comment
that
hey
person.
X
is
no
longer
working
on
this.
You
can
take
this.
That
may
be
asked
know
the
previous
person.
B
Right
Steven
I
wanted
to
cut
the
actual
recording
so
I'm
stopping
the
recording.
Now.