►
From YouTube: Argo Contributors Office Hours 19th Aug 20201
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
And
right
so
good
morning,
good
evening,
everyone
I'm
going
to
start
from
sharing
my
screen
just
to
see
what
we
have
in
the
agenda
today
and
we
today
is
supposed
to
be
ux
focused
meeting,
and
I
just
inserted
a
couple
updates
before
we
start
talking
about
ui.
So
one
is
just
continuation
from
the
last
meeting.
Basically,
we
spoke
that
it's
hard
to
share
triage
responsibilities,
because
members
don't
really
have
permission
to
make
changes
in
labels
and
then
jesse
basically
fixed
it.
A
He
created
a
proposal
that
explains
that
members
supposed
to
have
these
permissions
and
basically,
we
supposed
to
vote
on
it
and
we
already
got
a
bunch
of
thumbs
ups.
So
please
use
that
link.
If
you
want
to
vote
as
well
and
give
your
opinion-
and
I
don't
know
jc,
how
long
are
you
going
to
wait
to
before
you
merge
it
and.
B
A
Yes,
so
please
please
just
a
comment
and
basically
yeah
express
your
opinion.
If
you
like
this
change
comment
and
we
can
get
it
done
sooner
and
next,
I'm
assuming
it
was
then
just
edit
one
more
reminder
about
cubecon
is
then
in
that
meeting,
did
you
want
to.
C
Yeah,
no,
I
wanted
to
make
a
reminder
for
argo
con,
which
is
coming
up
in
december
until
I
think
september
15th,
and
we
have
some
good
talks
that
have
been
submitted
so
far,
but
we
definitely
want
to
see
more
end
users
and
more
people
submitting.
So
if
you
have
any
talks-
or
you
know
some
users
that
you
think
would
give
great
talks,
please
encourage
them
to
do
so.
It's
at
the
you
can
just
google
argo
con
and
that's
gonna
be
coming
up
so
want
to
definitely
get
more
people
there.
C
Oh
one
other
update
with
it.
We
are
moving
it
to
be
a
virtual,
only
conference
right
now
it's
listed
as
happening
in
san
francisco
and
virtual,
but
because
of
delta
we've
decided
to
move
it
virtual
only
apologize
for
that,
but
definitely
all
the
virtual
tickets
are
free,
so
there's
no
reason
not
to
register.
If
you
haven't.
A
All
right-
and
I
had
one
more
last
minute
call
basically
four
so
201
release
is
ready
and
it
was
supposed
to
be
like
it
was
ready.
Yesterday.
I
just
decided
to
you
know:
ask
everyone
in
that
meeting.
If
you
want
to
cherry
pick
any
last
minute
fix
you
have
like
an
hour
or
two
today
after
that
meeting,
I
think
we'll
just
push
the
button
and
release
to
that.
One.
A
And
yeah
feel
free
to
message.
I
guess
use
maybe
contributors
channel
if
you
want
to
cherry
pick
something
or
if
you
want
to
hold
on
on
releasing
2.1
and
work
on
some
on
fixing
something
and
all
right,
and
I
don't
see.
I
know
that
I
wanted
to
talk
about
some
processes
and
I
I
don't
want
to
you
know
still
completely
ux
topic
from
that
meeting.
Maybe
we
can
talk
about
ux
and
if
harry
is
in
that
meeting,
we
might
have
time
at
the
end
of
the
meeting
to
speak
about
it.
So,
okay,
I'm!
A
I
guess
we
can
talk
about
these
two
issues
that
we
have
in
the
list.
Do
you
want
to
speak
about
the
first
one
that
covers
him
proposal.
A
D
The
issue
is,
we
have
suspended
color
in
the
pie,
chart
which
we
didn't
specify
a
color,
so
it's
rendered
as
black
like,
because
we
didn't
specify
the
color
of
fill.
So
I
want
to
add
two
one
more
color.
I
want
to
use
the
out
of
sync
warning:
yellow
as
the
color
of
missing
for
the
house
state
status
and
add
another
color
for
suspended,
which
is
currently
in
the
app
is
grey
same
as
I
know
it.
D
A
D
Yeah,
okay,
this
one,
so
this
shade
of
blue
gray
generated
based
on
our
current
color
scheme
between
the
red
and
the
blue.
We
have
I
just
so
you
can
see
the
missing
now
is
same
as
out
of
sync
and
below
this
pie
chart.
You
can
see
the
future
view
of
how
it
looks
for
each
status
and.
A
D
Yeah
they,
wherever
we
use
one
status,
we
use
same
color.
So,
as
you
can
see
in
the
sync
see
the
second
one,
sync,
there's
green
and
in
the
pie
chart
it's
green
as
well,
so
same
color
should
be
used
across
the
app
so
because
we
want
to
make
each
pie
slice
distinct,
unique
color,
so
it
will
change
change
the
filter,
icon
color
as
well.
That's
why
I
want
to
reset
it
up
so
that
I
don't
affect
like
across
the
app.
I
want
everyone
on
the
same
page.
D
So
is
that
okay
to
use
same
yellow.
D
For
the
missing
and
the
outer
sink,
as
I
see
the
healthy
and
the
sink,
both
green,
so
I
said
it
could
be
same
for
out
of
sync
and
missing.
F
Is
a
bit
difficult
to
read,
I
think
the
no
no
not
on
the
pie
chart,
but
they
weren't
like
the.
H
A
F
A
D
A
D
A
I
feel
like
one
comment
about
missing.
I
kind
of
I
see
some
logic
to
make
it
yellow,
because
outer
thing
it's
either
basically
element
when
element
is
missing.
It's
considered
outer
sink
and
only
caveat
is
that
it
might
be
there,
but
it's
like
not
matching
to
the
state,
but
it's
like
it's
really
difficult
to
find
color
that
really
represents
missing
status,
and
I
guess
yellow
is
the
closest
one.
So
I
personally
I
would
you
know
I
would
not
be
confused
by
that.
I
would
say
yeah.
It
makes
sense
to
make
it
yellow.
D
A
A
F
Yeah,
I
think
the
black
tags,
maybe
like
you
said,
like
you
mentioned-
maybe
the
icon-
to
have
different
color
because
you
can
get
yeah.
I
cannot
even
meet
the
the
great
you
you
didn't
tell
me.
There's
a
great,
I
didn't
see
it.
Yes,
definitely
I
think
you
know
you
were
unable
to
read
the
text.
F
I
On
this
page,
can
you
hear
me
yes,
okay
on
this
page?
Would
it
be
better
to
kind
of
like
remove
the
the
little
the
the
key
and
basically
because,
like
the
key
basically
says
the
same
thing
that
the
the
table
says
below,
but
you
could
move
so
you
could
have
like
the
sync
status
square
under
the
sync
status
pie
chart
and
the
health
status
square
under
the
health
status
pie
chart.
A
I
But
like
underneath
basically
like
have
each
like
the
sync
status,
the
filter.
Sorry
filter
is
a
better
word.
The
sync
status
filter
and
the
whole
status
filter
underneath
their
respective
pie
charts.
Would
that
make
more
sense
or.
A
I
A
A
G
I
A
Okay,
all
right,
so
it
will
be
yellow
ghost.
D
Yes,
basically,
wherever
we
have,
this
ghost
will
be
yellow
just
make
it
consistent.
If
I
make
this
change.
D
Oh,
but
I
got
a
feedback
from
josh.
If
you
scroll
down
like
a
he,
he
wanted
it's
a
purple.
One!
Isn't
that
purple!
Is
it
not?
D
A
I
think
it
solves
more
problems
than
so.
Basically,
even
if
it's,
I
don't
think
it's
confusing.
You
know,
it's
just
happened
to
be
gray
for,
like
almost
randomly,
because
gray
is
okay
for
missing,
but
it
it
introduced
confusion.
So
if
we're
resolving
confusion,
it's
better
than
what
we
have
before
I
I
would
like
I
personally
I
would
set
yes,
I
would
say
yeah
it's
better
to
make
it
yellow
and
have
distinct
color
for
every
status.
D
D
A
E
D
D
A
D
A
D
A
E
J
A
All
right
looks
like
this
is
that
was
productive.
We
managed
to
find
colors
and
oh
nice,
how
he
just
added
the
topics
and
yeah.
So
we
have
one
more
issue
that
we
want
to
discuss.
I
do
not
know
who
edited
sorry.
I
I
looked
into
this
issue
because
there's
this
issue
and
another
one
that's
linked
to
it
somewhere
in
here,
but
people
want
like
a
like
a
bulk
delete
option
where,
if
you're
deleting
an
app,
you
don't
have
to
type
the
entire
name
of
the
app
in
order
to
delete
it.
I
So
if
you're
deleting
a
bunch
of
apps
at
the
same
time,
it
takes
a
really
long
time
and
I
tried
to
yeah,
I
tried
to
do
a
shift,
click
to
delete
it,
and
I
it
was
not
gonna
happen
unless
there
were
like
huge
changes
to
the
way
that
react
forms
being
implemented.
So
I
don't
think
that
that's
an
option
to
do
that.
I
E
I
got
a
quick
question
about
this:
is
this
the
same
delete
when
you're
deleted
a
sub
resource
of
an
application?
You
have
to
type
the
long
name
of.
I
E
Right
yeah,
I'm
walking
my
dog.
H
E
E
B
I
actually
agree
with
al
alex
about
this,
like
we
wanted
some
cognitive
dissonance
when
actually
going
through
this,
but
it
the
the
dissonance
is
so
drying
that
it's
it's
not
productive.
It
doesn't
need
to
be
that
intense
in
in
terms
of
just
deleting.
It
is
mostly
to
prevent
accidental
thing,
rather
than
so.
A
It's
truly
accidental,
but
I
just
remembered
some
history
about
this
change.
Basically,
we
had
several
extremely
frustrated
users
who
deleted
production
by
you
know
accidentally,
so
it's
kind
of
between
two
evils
and
I
yeah
it
would
be
awesome
if
we
find
some
compromise
like.
I
would
not
regret
it
like
even.
E
We
want
friction,
but
just
like
less,
it's
too
much
friction
at
the
moment.
It's
good
friction,
but
it's
too
much
I
would
maybe
replace
replace
the
box.
Where
you
I
mean
what
I
do
with
this.
Was
I
copy
the
line
above
it
into
the
box?
That's
what
I
would
do,
but
that's
not
easy
to
do,
because
the
user
interface
kind
of
reacts
to
you
clicking
on
that.
I
would
just
replace
the
box
for
the
check
box.
Can
we.
B
J
E
I
I'm
about
resource
deletion.
I
can't
I
can't
speak
so
much
for
application
deletion.
Maybe
a
different
level
of
friction
is
right.
There.
A
B
B
I'm
pretty
sure
most
people
are
complaining
about
myself
includes
deleting
a
single
resource
is
too
painful.
A
Yes,
I
understand
how
you
know
deleting
a
single
resource
like
you
you,
I
often
did
it
too,
like
I
had
to,
especially
if
you
work
with
just
a
dev
application.
You
know
like
a
temporal
application
and
you
want
to
experiment
yeah
yeah,
but
maybe
just
just
to
give
another
idea
like
what,
if
we
introduce
bulk
deletion
in
the
application
details
page.
A
So
this
way
we
still
can
have
annoying
qi,
but,
like
I
think,
it's
question
to
alex
like
let's
say
if
you
have
a
way
to
delete
to
like
select
a
bunch
of
resources
from
the
top,
and
you
know,
click
delete
once
and
then
set
and
then,
like
basically
say
yes,
I
agree
or
like
type
something
like
actually
okay.
I
think
I
want
to
take
it
back
like
if
you're
deleting
a
bunch
of
resources.
A
And
and
yeah,
so
maybe
this
is
just
too
much
here.
Maybe
we
just
need
a
checkbox.
B
I
I
think
checkbox
is
fine
with
me,
but
if
that's
too
easy,
I
was
wondering
if
there's
some
more
like
an
interactive
confirmation
that
you
know
how
you
can
slide
or
move
something
like.
I
don't
know,
I'm
just
thinking
like
a
lot
but
like
on
your
phone,
you
can
slide
some
thing
to
yeah.
I.
A
A
F
A
So
maybe
like
one
more
way,
so
we
did
some
so
basically,
if
you're
trying
to
delete
this
source
that
won't
recreate
itself
automatically.
We
ask
for
this
change,
but
if
you're
deleting
a
child
resource,
like
you
know
this
replica
set,
for
example,
we
don't
ask
anything
because
we,
you
know.
Basically
we
have
some
context.
We
know
that
child
resources
typically
managed
by
by
its
parent,
so
it
was
safe
to
you
know
not
ask
for
confirmation
here.
Maybe
we
can
find
some
type
of
like
more
context,
so
top-level
resources
managed
by
the
application
and
okay,
okay.
A
F
F
Doesn't
look
very
good
either
I
mean
if
that
matters
yeah.
I
think
you
put
a
checkbox.
M
A
B
B
I
I
don't
think
we
need
to
be
that
much.
I
honestly,
I
just
think
we
need
to
make
it
less
difficult
than
typing
the
whole
resource
name.
A
And
okay,
one
last
chance
what
if
we
have
copy
button
here,
you
know
like
copy
resource
name
and
then
you
click
on
it
and
you
know
paste
like
you
know.
If
we
just
minimize
interaction
and
you
know
small
copy
button
yeah,
you
click
on
that
button
and
you
get
resource
name
on
the
clipboard
and
then
you
paste
it
here
and
you're
done.
I
M
A
E
If
I
could
just
click
on
the
name
of
like,
if
you
want
me
to
my
eyes
to
look
at
the
name-
which
I
think
is
one
of
the
goals
in
you
know,
that's
the
friction.
I
have
to
look
at
the
name
of
the
thing
I'm
deleting
and
if
I
can
just
click
on
the
name
and
the
name
is
copied
and
pasted
directly
into
the
box.
That
would
be
brilliant.
I
don't
want
to
switch
from
mouse
to
keyboard.
When
I
do
this,
I
don't
have
to
right
click
and
don't
copy.
E
A
J
E
B
E
A
I
A
Yeah,
or
at
least
we
need
to
yeah,
we
can
just
document
that
it
just
moment
in
that
issue
that
okay,
we've
we've
got
another
idea
which
a
lot
of
people
like
you
know
to
be
able
to.
Maybe
you
know,
just
use
the
mouse
and
like
one
way
to
use
mouse,
is
to
add
this
copy
button,
and
you
know
this
way.
You
kind
of
you
can
easily
get
name
into
clipboard
and
then
use
mouse
to
insert.
F
It
into
so
just
yeah,
so
is
this
common
thing
to
do
like
if
people
just
just
try
to
see
if
this
is,
is,
if
you
do
this
right,
is
it
intuitive
for
the
user
to
to
think
okay?
Well,
I
have
to
copy
this.
I.
F
Keystroke
for
this
just
I
just
want
to
see
if
anyone
have
seen
similar
you,
you
use
usage
of
another
application.
I'm
trying
to
see
you
know
is
it?
Does
it
look
weird
or
is
it
I
mean
I'm
trying
to
think?
Maybe
maybe
I
created
more
more
trouble.
I
think
maybe
checkpoint
may
not
be,
though
you
know,
maybe
fine,
I'm
just
asking
if,
if
anyone's
think
that
doing
this
cut
and
paste
it
look
weird
like
it's
just
can't
be
looks
they
look
weird
to
some
users,
not
not
intuitive.
G
A
F
Yeah,
if
it's,
I
don't
want
to
make
this
dialogue,
become
like
okay,
well,
the
user
may
be
confused
like
what
do
I
have
to
do
that
probably
more
problems,
so
maybe
maybe
the
checkbox
may
not
be
the
you
know,
maybe
maybe
writing
I
do
know
like
in
places
where
you
have
to
do
confirmation.
You
have
to
check
a
box
before
you
can
before
the
the
okay
button,
the
shoes
of
things
like
that
right.
F
Then
I
know
we're
trying
to
see
find
a
way
that
that
the
best
solution
to
to
for
user-
maybe
maybe
maybe
doing
the
check
box.
Maybe
you
know.
F
Trying
to
yes
we're
trying
to
maybe
maybe
a
bit
yeah,
maybe
maybe
be
working
too
hard.
F
Really
is
just
let
me
I
don't
want
this
to
feel
weird
become
a
strange
thing
for
a
user.
Maybe
maybe
I
go
back.
Maybe
hey.
J
F
J
I
think
the
common
pattern
is
really
to
type
in
the
name
of
the
resource,
but
you
know
just
like
when
you
delete
when
you're
trying
to
delete
it
or
get
off
get.
B
For
bigger,
more
consequential
things
like
a
good
repo,
it's
like
pretty
consequential
yeah,
a
res
like
I
guess
the
equivalent
for
us
would
be
application.
So
I
think
at
the
application
level
that
makes
sense
in
an
individual
resource
object.
I
think
we
can
afford
to
be
a
little
looser
and
because
I
I
I
think,
that's
actually
a
common
thing.
B
A
A
repository
or
deployment
and
ripple
server
service,
you
know,
like
a
community
service,
both
might
have
the
same
name
and
that
dialogue
would
not
even
protect
from
this
type
of
mistake.
You
would
put
the
name
of
your
resource
and
you
still
delete
something
so
yeah.
Maybe
we
simply
have
a
check
box,
but
more
prominent
information
about
the
type
and
name
you
know
like
deployment
in
bold
name
and
bolt,
and
maybe
the
resource
icon
next
to
the
deployment.
I
Yeah,
I
I
agree
with
that.
I
think
I
mean
definitely
there
needs
to
be
more
acknowledgement
of
this,
the
name
at
least
on
this
page
like
just
having
it
the
same
font
and
everything
is,
I
feel
like
not
very
good
user
experience
I,
but
I
think,
like
a
check
box
with
like
more
acknowledgement
on
what
they're
actually
deleting
is
sufficient.
I
G
A
M
Sure
yeah,
I
think
this
isn't
continuous
to
the
last
contributor
meeting
regarding
the
milestone
review.
I
think
we
just
wanted
to
again.
I
just
want
to
see
like
if
anyone
got
a
chance
to
review
those
tickets
and
maybe
add
new.
My
new
items
in
that.
E
K
M
Posted
where
a
couple
of
them,
I
think
these
three
right
alexa
two
are,
I
think,
intuit
is
working
on
and
this
one
is
not
from
quote
fresh
and
there
is
two
which
is
still
anyone
scraps
and
the
particles
now
so
before,
going
more
tutorials
like
any
opinions
or
any
feedback
on
adding
more
more
enhancements
or
anything
or
william
or
anyone
else
to
talk
about.
A
And
okay,
maybe
maybe
I
wanted
to
add
a
little
bit-
we
had
conversation
about
it
and
harry
had
a
great
idea.
Basically,
he
kind
of
highlighted
and
that,
for
example,
we
see
a
lot
of
contributions
from
you
know
both
actually
red
hat
and
code
fresh
and
as
well
into
it.
We
all
kind
of
periodically
pick
tickets,
which
are
not
big.
A
It's
like
usually
you
know,
small
enhancement
or
small
bug
fix,
and
these
tickets
contribute
it's
like
a
significant
contribution
to
release
and
they
go
unnoticed
and
we
were
just
performing
how
to
fix
it,
and
one
proposal
was
to
at
least
try
to
you
know
kind
of
plan
a
little
bit
ahead
of
time
and
try
to
choose
ones
which
are
related
to
each
other
and
group
them,
and
that
will
really
help
to
increase
visibility
and
will
have
more
information
to
put
it
into
release.
Block
and
more
credit
goes
to
you
basically.
A
So
so,
for
example,
like
we,
you
know
why
keep
working
on
user
keep
working
on
improving
qi,
and
it
will
be
difficult
for
me
to
you
know
because
all
like
whoever
writes
the
release
blog
to
catch
all
the
fixes.
A
We've
made
and
highlight
it
well
in
the
release,
but
if
we
try
to
think
about
it
now
and
find
like
for
us
like
some
number
of
related
tickets
and
try
to
give
it
a
name,
you
know
give
the
name
to
that
group,
and
maybe
we
can
say
that
you
know
improve
consistency
of
yeah
and
some
some
some
smart
name.
That
explains
what
exactly
we're
doing.
Then
it's
like
a
benefit
to
everyone.
A
A
We
if
we
go
through
2.2
release
and
we
could
like,
if
we
just
look
at
all
ui
tickets
and
we
kind
of
know
most
likely,
who
is
going
to
work
on
the
stickers
if
we
simply
group
them
and
then
people
commit
to
that
group,
then
we
kind
of
know
that
it
will
be
easier
to
go
and
maybe
add
one
more
line
into
roadmap
of
next
release,
and
it
will
give
more
clarity
to
users
plus
we're
going
to.
We
will
know
that
we
will
get.
M
Yeah,
not
just
ui
means
anything
actually
any
enhancements
box
or
anything,
but
anything
that
can
be
grouped.
Maybe
you
can
group
them
and
produce
maybe
performance,
enhancement
or
ui
enhancements
so
like
that
you
can
quickly
pick
and
group
those
tickets.
A
A
I
feel
bad
because
it's
like
you
know
we
usually
write
release
block
in
the
rush
and
it's
like
it
would
require
a
whole
investigation
to
find
all
these
groups,
and
you
know,
try
to
name
them
and
that's
why
we
typically
just
it's
literally
like
two
sentences,
but
these
two
sentences
kind
of
describe
a
lot
of
work.
I
mean
two
sentences
kind
of
we
had
a
lot
of
performance
and
improvements
and
bug
fixes,
but
in
reality
it's
much
more.
A
Yeah
I
was
hoping
to
quickly
find
an
example
and
let
me
yeah
I'll
share
and
yeah.
So
by
grouping
I
mean
if
we
find
okay-
and
I
guess
it's
pointless
to
share,
because
I
won't
be
able
to
find
the
example
right
right
now
easy,
so
I
will
have
to
make
it
up.
Let's
say
we
work
on
like
we
have
two
tickets,
one
is
changing
colors
of
the
icons
another
one
changing.
Maybe
you
know
some
paddings
and
you
know
like
like
buttons.
A
Maybe
these
two
could
be,
could
look
like
they're,
not
related,
but
we're
kind
of
improving.
You
know,
consistency
of
you
of
ui
and
and
that's
you
know
the
name
of
a
group.
So
and
basically,
if
you
have
the
name
of
this
group,
then
you
can
write
couple
sentences
and
explain
why
a
user
benefit
from
it
and
user
will
benefit
because
it
will
be
easier
to
navigate.
A
A
Okay,
I
I
was
hoping
to
this
group
eventually
should
make
it
into
roadmap.
That's
what
this
is
where
it
would
really
like
help.
Let
me
switch
to
s
latest
kind
of
it
was
a
little
bit
improved
road
map
yeah.
So
like
now,
I
feel
like
we're
switching
to
have
brought
like
more
kind
of
realistic
roadmap,
so
in
2.2
we
working
on
this
four,
but
this
okay,
this.
Actually
this
is
supposed
to
be
in
two.
It's
done
yeah.
A
Basically,
these
three
it
looks
like
we
have
commitment
to
work
on
this,
but
in
the
energy
we're
going
to
make
way
more
work,
because
this
is
just
kind
of
top
like
you
know,
features
that
naturally,
must
have
name,
because
these
are
new
things.
But
at
the
same
time,
I
guess
like
around
80
of
work
are
not
going
to
be
related
to
these
features,
and
we
won't
even
mention
them
and
yeah
so
and
we
won't
give
appropriate
credit
and
users
won't
know.
Some
enhancements
are
coming
and
yeah.
A
But
I
guess
it's
a
call
for
action
like
harry
was
wanted
to.
You
know
to
kind
of
ask
people
to
try
to
it's
hard
to
do
that.
You
know,
for
example,
I
don't
know
how
would
I
be
able
to
to
do
that
work
because
I
do
not
know
you
know
I
basically
I
would
need
help.
I
I
know
that
trying
to
find
who
do
I
put
on
the
spot,
like
pasha,
actively
picking
issues,
and
I
guess
you
have
some
kind
of
you
know.
A
Basically,
maybe
you
already
have
some
idea
of
what
kind
of
issues
you're
looking
for
and
that
you
know,
if
maybe
we
can
work
together
to
try
to
try
to.
You
know,
come
up
with
a
list
of
things
that
will
you
think
you
will
work
on
and
then
try
to
try
to
name
that
list
and
same
for
red
hat
folks,
like
yeah.
M
Yeah,
I
think
that
that
is
one
item
and
the
other
one
is,
I
think,
just
continues
from
the
last
one
right
from
the
milestone
point
of
view
like
if
anyone
has
new
features
that
they
want
to
work
on,
please
add
it
as
well,
we'll
again
repeat.
M
Next
week,
also
just
to
give
more
time
for
all
the
users
or
all
the
contributors,
but
we
plus
please
go
through
the
milestones
and
see
like
which
one
you
can
pick
it
up
or
your
team
can
work
on.
I
think
that
would
be
great
so
that
we
can
start
planning
anyway.
In
that
way,.
M
In
any
I
mean
feedback
already.
E
M
Okay,
then
we
can
move
on
to
the
next
one
trash
feedback
inputs.
I
think
last
week
I
think
william
and
abhishek
are
the
priors
owners,
so
we
want
to
hear
from
them
like
what
is
that
experience
and
any
issues
or
any
improvements
that
you
want
to
propose.
F
O
Next
week
yeah
same
here,
actually
I
want
to
start
it
from
this
monday
and
I
thought
that
pasha
and
alex
were
doing
this
week.
My
bad
on
that
sorry.
I
would
start
working
on
that
from
this
monday.
M
F
So
I
did
look
at
all
the
labels,
so
let's
try
to
understand,
understand
what
the
labels
1999
like
seven
two
there's
a
bunch
of
labels
but
yeah
yeah,
so
well,
yeah
was
doing
an
electric
cycle
and
in
the
meantime,
probably
before
we
have
the
permission,
probably
just
comment-
you
know
put
it
in
the
comments
but
yeah.
Oh.
A
B
I
think
that
responsibility
should
include
like
getting
clarifying
questions
and,
if
there's
not
enough
details,
you
know
things
like
you
know
what
version,
if
you,
if
you
have
insight
on
you,
know
law
areas
of
the
logs
that
they
may
need
to
paste,
and
you
have
that
that
knowledge
and
you
can
ask
those
clarifying
questions.
M
That's
right,
yeah,
so
william
and
object
show
you
want
to
continue
from
tomorrow
right,
yeah,
okay,
okay,
okay,
that's
great!
So
I
think
we
will
put
the
timeline
also
so
that
you
can
continue
on
that
and
going
to
the
discussions.
Part
right.
You
see
like
any
new
discussions
that
you
want
to
share.
B
Here
I
was
able
to
handle
all
the
questions,
except
for
one
which
was
related
to
key
cloak
login
for
cli,
and
I
think
I
wasn't
able
to
answer
it
because
I
think
this
is
highly
dependent
on
the
oidc
provider
and
since
key
clock
is,
is
a
red
hat
product.
If
I'm
not
mistaken,
do
you
let
me
bring
up
the
the
the
discussion.
B
All
right,
so
this
is
the
the
user's
problem.
They
were
trying
to
do
a
cli
login
using
odc,
and
we
support
this,
but
they
get
this
error
and
and
it's
different
for
every
provider
because,
like
I
know
with
dex,
there's
an
option
to
I
think,
to
enable
this
and
then
I
think,
with
octa.
B
There
was
also
another
way
of
of
allowing
cli
logins,
using
like
proof
of
key
for
code
exchange
and
then
for
key
cloak.
I'm
thinking
it's
something
else,
so
I
was
hoping
if
anyone
on
the
red
hat
side
has
experience
with
this.
They
could
kind
of
chime.
In
with
doing
this,.
O
Sure
I
can
take
a
look.
I
I
mean
I
have
some
experience
on
key
clock.
So
I'll
have
a
look
at
this
okay
discussion.
B
M
I'm
like
alex,
if
you
want,
maybe
any
new
one,
a
new
counterpart
can
do
it.
I
mean
you
mean
like
a
right
like
a
shadow
moderator
someone
who
wants
to
maybe
because
I
see
like
I
don't
like
how
long
we
are
in
this
list,
because.
M
New
contributors
to
be
part
to
start
having
to
involve
more
in
the
discussions
as
well,
because
I
think
new
names
are
added
right.
Probably
we
are
just
going
again
on
the
same
names
seriously.
A
M
M
A
Yeah
and
I'm
trying
to
figure
out
like
how
do
I
just
put
you
to
the
top
at
some
point
I
should
be
so.
I
basically
will
keep
my
name
and
then
put
volunteers
in
front
of.
A
That's
true
right,
yeah,
yeah,
some
perfect
timing.
We
just
basically
reached
the
end
of
an
hour
and
I
think
that's
it
for
today.
A
Yeah,
please
think
about
the
issues,
and
you
know,
grouping
of
issues
or
whatever
we
call
it
and
it
will
really
help
and
I
think
it
will
help
to
contribute
as
well,
because
I
wish
I
see,
I
think
we
kind
of
we
did
not
give
enough
credit
in
like
at
least
2.1
release.
There
was
a
ton
of
bug
fixes,
like
literally
like
dozens
and
dozens,
and
it
was
hard
to
explain
it
in
release,
but
in
the
least
blog
I
wish
we
improved
it
next
time
and
yeah.
We
need
help
from
everyone
who
contributes
to.
K
I
I
have
one
last
question
alright,
so
since
we
have
a
trash
process
now,
so
how
should
we
handle
old
issues
like
so?
We
have.
There
are
issues
from
2019,
so.
A
We
kind
of
thought
about
it
and
I
I
don't
think
we'll
make
a
decision,
but
it's
just
observation.
So,
like
few
months
ago,
I
think
we
were
like
in
a
disaster
state
where
number
of
issues
was
growing
and
we
could
not
even
stop
it
now
it
goes
down.
So
it's
like
a
step
forward
now.
I
think
we're
in
more
stable
position.
A
I
I
was
my
feeling
was
that
we
keep
doing
it
a
little
bit
and
once
we're
even
more
stable,
then
we
can
go
and
you
know
we'll
we
can
go
and
try
to
triage
old
issues.
I
I
tried
to
do
and
it
some
time
ago,
and
it
was
the
whole
effort-
was
wasted.
I
think
I
spent
like
a
week.
I
was
trying
to
close
and
grow
virtues
and
it
was
kind
of
it
was
wasted,
because
I
tried
like
500
issues
and
then
few
months
later
we
almost
doubled
yeah.
A
So
I
guess
if
we
run
in
a
good
state
and
we
basically,
if
we,
if
like
in
the
months
from
now,
we
see
that
really
issues
number
of
issues
is
not
growing
it's
going
down.
Then
it's
a
good
indication
that
it's
time
to
clean
up
old
ones-
and
that
was
yeah-
that
that's
my
my
feeling,
but
I
think
it's
a
longer
conversation
to
be
honest.
Well,.
B
I
do
think
we
should
reconsider
turning
on
the
stale
bot
yeah,
so
I
I
mean
all
projects
especially
of
this
size
are
using
some
form
of
automation
to
help
manage
issues
so.