►
From YouTube: Argo Contributors Office Hours 26th 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).
B
A
He
had
a
proposal
about
discussion,
moderators
and
issue
treasures,
and
then
I
added
a
couple
topics
myself,
I'm
not
sure
if
it's
going
to
happen
or
not,
but
I
know
that
we
wanted
we're,
probably
going
to
have
two
discussions
about
ui
changes
and
we
wanted
to
get
feedback
so,
but
let
me
start
from
yeah
just
update
that
we
finally
created
argo
cd,
2.1
release
and
then
release
candidate
after
shortly
to
address
couple
regressions
and
jonathan,
published
application
set
release.
So
release
happened.
That's
awesome.
A
A
I'm
looking
into
the
list
of
attendees
right
now
and
trying
to
see
if
harry
joined.
There
is
h
and
I
don't
understand
you
know
that
the
zoom
shows
me
someone
whose
name
is
h,
but
not
the
name
of
attendee
all
right,
I'm
assuming
he's
not
here
yet
maybe
he
will
join
later
and
then
next
we
had
a
couple
topics
from
basham.
B
Yeah
all
right
guys
so,
actually,
on
last
week,
I
have
contributed
the
feature
which
named
ability
to
run
local
environment
with
exclude
mode.
What
does
it
mean?
That's
from
the
day
when
we
start
to
contribute
to
rcd
rx,
helped
me
to
configurate
my
local
environment
with
government
tool,
and
I
understand
that
each
time
for
one
local
environment,
I
need
to
write
like
list
of
all
services
that
we
have
like
api
server,
ui
server
and
other
things
controller
and
so
on,
and
I
understand
that,
for
example,
ui
developers
don't
need
all
these
things.
B
B
B
A
B
You
know
and
comments
so
if
you
think
it
can
be
somehow
improved
and
so
on,
actually
what
I
think
can
be
improved,
but
I
didn't
find
how
to
implement
how
to
implement
it.
It's
like
I
thought
about
solution
with
flux
and
not
with
environment
variable,
but
I
didn't
find
how
to
pass
it
use
make
files.
So
if
somebody
can
help
me
or
contribute
it,
it
would
be
nice.
I
just
didn't
find
how
to
do
it
in
internet
world.
A
C
B
B
B
C
B
Yes,
that's
the
problem
that
I
met
that
I
need
to
remember
all
the
service
names
yeah
and
in
in
all
the
combinations
in
quarters.
We
have
experience
that
and
I
think
it's
good
experience
that
you
like.
We
have
20
plus
services
and
if
you
will
use
such
approach
you
in
some
place,
you
will
need
to
remember
all
these
service
names
and
in
most
case
you
just
need
to
exclude
one
maximum.
Two
micro
service
will
start
contribute
locally.
So
it's
to
my
opinion,
such.
A
Yeah
and
I'm
basically,
I
agree
because,
like
I
started
using
the
tool
and
yeah
and
I
feel
like
it's,
it
was
important
to
mention
that
in
that
meeting,
because
it's
kind
of
I
mean
it's
expensive
to
document
each
and
every
possible
shellscript
that
we
use
for
development
and
it
was
kind
of
cheap
today
to
you
know
just
mention
it
for
all
contributors.
A
It
on
behalf
of
you
that
sync
windows,
page
redesign,
I
thought
you
will
present.
B
A
So
alex
you
will
explain
yes,
okay,
yeah,
and
I
I
guess,
if
you
switch
back
to
the
mock-up,
I
can
start,
I
hope
so
yeah
just
to
step
back
today
is
not
you
know
your
eccentric
meeting
but
yeah.
Basically,
we
we
just
happens
to
have
two
ui
related
topics,
and
since
there
was
nothing
else,
I
think
we
can
discuss
it.
A
But
basically
the
idea
is
that
we
have
kind
of
two
initiatives
right
now
and
one
of
these,
like
remington,
was
working
on
redesigning
the
sidebar
and
then
the
code
first
team
has
designer
and
the
designer
basically
has
ideas,
but
you
know
to
refresh
argo
ui
so
and
kind
of
it
was.
I
felt
like
it
was
important
to
present,
maybe
both
ideas
today
or
at
least
one
and
get
feedback.
A
So
this
is
the
new
sync
window
page
and
we
we
met
with
pasha
recently
and
basically,
both
of
us
felt
that
it
doesn't
really
change
much
of
your
your
exp.
You
know
ux
experience
on
the
page,
but
it
mostly
changes
kind
of
look
and
feel
and
tries
to
make
ui
cleaner.
So
it
kind
of
touches
pretty
much
all
components
we
have.
A
As
you
can
see,
there
is
input
components
this
you
know,
icons
that
represents
kind
of
information
changed,
and
you
know
the
style
of
sliding
panel
titles
changed
and
it's
impossible
to
just
go
ahead
and
redesign
this
one
page
and
don't
touch
anything
else,
it's
possible,
but
it
would
be
not
good
for
users,
so
it
must
be
consistent,
and
so
we
need
opinions.
A
They
should
be
looking
yeah.
That
is
the
first
step
and
I'm
yeah
I'm
inviting
ui
patient
people
to
speak
up
like
remington,
regina
yeah,
and
I
guess
we
tried
it
many
times
before
you
know
like
we
spoke
about
color,
so
it's
one
more
attempt
to
try
to
you
know
bring
forces
of
everyone.
You
are
patient
and
yeah.
A
A
Like
to
be
even
more
honest,
like
we
have
a
designer
who
doesn't
know
much
about
githubs
but
knows
about
building
quiz
and
basically
it's
up
to
us
how
we
help
you
know,
we
should
help
the
person
to
by
giving
feedback
and
then
eventually
we'll
get
something
good
but
yeah.
Basically,
this
is,
I
guess,
the
proposal
of
how,
in
general,
like
argo,
ui
would
change
and
I
feel
like
it's.
You
know
it
requires.
A
It
will
be
a
lot
of
work
if
we
just
go
ahead
and
up
try
to
redesign
the
whole
aggregate
ui
like
this
and
then
and
then
see
if
it's
good
or
not.
So
we
need
to
try
to
you
know,
I
guess
maybe
catch
things
that
is
hard
to
implement
and
then
and
then
maybe
suggest,
like
which
pages.
B
I
would
just
add,
comment
on
this,
so
just
because
we
started
with
no
directions
like
we
just
came
and
say:
okay,
this
screen
not
looking
good.
Let's
try
to
do
some
poc
and
redesign
it,
and
maybe
community
will
like
it
or
don't
like,
and
from
this
we
will
understand
how
we
want
because,
like
we
have
designer
capacity-
and
we
may
want
to
use
it
somehow-
and
I
think
that,
for
example,
if
you
don't
like
especially
something
in
this
screen,
we
can
create
few
other
proposals.
B
A
A
A
I
spotted
that
you
know
instead
of
a
drop
down
these
two
options.
Now
we
have
a
kind
of
new
element
like
not
sure
how
to
call
it
kind
of
the
switch,
the
the
kind
right
now
it's
a
drop
down,
but
it
can
be
only
hello
at
nd9
and
you
must
pick
one
and
I
think
in
the
mock-up.
Now
we
have
this
kind
of
switch.
It's
like
yeah,
not
sure
how
to
call
it
two
buttons,
and
I
guess
if
you
click
one,
it
changes
the
style
of
another
one.
E
E
B
A
I
know
why
it's:
it
is
gray
right
now
there
is
just
a
history
behind
it,
so
argo
ui
used
to
be
more
blue.
A
This
navigation,
the
sidebar
navigation,
was
kind
of
bluish
and
basically
we
were
using
the
same
base
color
for
all
blueish
elements,
and
then
we
at
some
point.
We
decided
to
change
it
to
more
gray,
and
that's
why
you
know
the
active
button
became
great,
so
it
was
not
intended.
It
kind
of
you
know
like
a
side
effect
of
a
different
design.
That's
why
it
yeah
this
way.
It
is,
and
I
I
kind
of
agree
that
it
became
a
little
strange
because
it
used
to
be
kind
of
it.
A
There
was
a
good
fit
for
active,
color
and
now
yeah.
So
maybe
I
think
it's
even
overlooked.
We
should
have
changed
it
when
we
switched
to
gray
from
from
blue
right-
and
I
there
is
a
proposal
in
comments
to
try
to
you-
know
just
show
it
side
by
side.
Basically,
I
think
this
screen
is
wide
enough
to
show
both
pages
at
the
same
time,
so
people
can
see
better
pasha.
A
B
A
I
I
know
that
there
was
one
comment
about
colors
and
a
for
y
contrast
requirements
and
we
spoke
about
it
before,
and
I
think
we
should
not
forget
about
this
topic
so
like
like
some
time
ago,
we
had
we
brainstormed
already
about
improving
cargo
cd
colors
from
I
guess
usability
perspective.
Basically,
we
just
wanted
to
make
sure
that
it's
easy
to
read
text,
and
I
know
nothing
about
it
like
I
don't
know
how
to
validate.
A
D
Yeah
like
that,
especially
on
just
like
the
pl,
not
the
create,
but
more
the
the
lighter
color
blue
there
maybe
like.
If
you
hover
over
it
or
have
it
selected,
it
would
have
like
a
darker
border
if
you
didn't
want
to
change
it
to
a
darker
color
overall,
and
especially
at
the
very
top
the
select
with
the
allow
and
deny.
D
I
feel,
like
that's
a
really
hard
distinction.
If
you
can't
see
that
color
blue,
like
I
can
barely
see
that.
E
B
F
My
opinion
about
this
is,
it
looks
good,
but
I
think
that
it's
essentially
just
a
new
coat
of
paint
over
the
same
thing,
and
I
I
don't
know
what
the
usability
complaints
over
the
sink
windows
panel
was
before.
But
if
there
were
usability
complaints
before,
I
don't
think
that
this
would
necessarily
solve
them.
F
But
at
the
same
time
I
think
that
we're
kind
of
just
getting
into
the
weeds
of
like
you
know
what
individual
components
look
better
and
I
think
at
the
end
of
the
day,
what
maybe
eventually
needs
to
happen
is
we
need
some
sort
of
design
system
because,
instead
of
you
know,
spending
time
every
few
weeks
discussing
the
minutia
of
you
know
individual
components.
F
A
Yeah,
I
think,
you're
right,
we
had
the
exact
same.
You
know
discussion
so
basically
designer
she
like.
Basically,
she
said
that
there
is
nothing
she
wants
to
change
a
lot
about
this
page.
It's
just
kind
of
a
little
bit
plain,
and
then
you
know
like
this
bunch
of
boxes
to
select
minutes
and
hours
was
not
it
has.
It
has
kind
of
almost
like
no
styling
check
box.
She
didn't
like
I
mean
she
wanted
to
propose
improving
checkbox
and
basically
she
just
at
the
end
of
this
exercise
when
she
prepared
this
new
design
page.
A
We
all
realized
that
yeah,
it's
like
your
ex
is
good.
It's
just
some
individual
components
needs
improvements,
and
then
we
realized
okay,
it's
not
it's
impossible
to
just
execute
it
independently.
We
need
to
have
meetings
and
then
it
just-
and
you
know,
discussions
and
and
so
on-
and
I
guess
the
first
pretty
much
we
we
get.
The
first
part
already
like
the
first
feedback
from
everyone,
seems
like
it's
good.
Basically,
people
agreeing
that
yes,
overall,
it
looks
good
and
it's
the
right
direction.
A
A
A
It's
it
I
mean
if
we
make
this
change,
I
guess
we
it
would
take
easily.
I
guess,
maybe
a
few
weeks
of
work
for
a
single
person
to
make
this
change
and
and
then
you
know,
make
sure
nothing
broke
yeah
and
I
guess
yeah.
I
want
to
hear
what
people
think
about
this
change
like
do
you
think
it
makes
sense
to
improve
inputs
in
this
way.
F
I
I
think
that
it,
it
makes
sense
and
I,
but
I
also
think
that
maybe
this
is
such
a
huge
undertaking
that
it
would
make
sense
to
do
something.
You
know
beyond
the
surface
level,
beyond
the
just
the
appearance
of
it,
and
I
think
that
was
kind
of
my
mission
when
I
was
aiming
to
you,
know
kind
of
revamp,
argo
ui
and
some
new
components
and
refactor
them
in
a
more
maintainable
way.
F
And
so
I
I
would
kind
of
move
to
say
that
if
we're
going
to
do
this,
we
should
maybe
drop
in
those
new
components,
and
you
know
change
the
style
of
the
components
to
match
whatever
design
system
we
settle
on.
But
I
do
think
that
we
should
kind
of
go
to
a
more
componentized
system.
A
Yeah,
I
mean
it's
a
good
chance
to
do
refactoring
as
well.
If
you,
if
you're
changing,
I
agree,
yeah
and
I
feel
like
we
should.
I
would
just
separate
implementation
from
design.
You
know
I
kind
of
discuss
the
end
result.
First
and
then
we
can
discuss
how
we
get
there,
and
I
agree
that
you
know
I
would
use
it
as
a
chance
to
refactor
what
you
what
we
don't
like
about
existing
qr
library.
B
Yeah,
in
addition,
I
agree
with
remington
about
design
system
and
components
in
terms
of
ui
in
terms
of
implementations,
maybe
not
so
important,
but
in
addition,
I
think
this
with
the
redesign
of
input
that
you
proposed
alex.
I
think
we
may
can
redesign
this
at
application
and
I
think
we
use
such
component
in
a
lot
of
places
like
in
projects
at
source
repository,
so
it
can
be
reduced
as
well,
because
it
has
better
cancel
button,
it's
visible
it's.
It
will
be
consistent
in
terms
of
inputs
with
such
input
as
well.
B
So
I
think
here
here
can
be
changes
and
we
can
try
to
move
on,
for
example,
this
separators.
It
will
not
affect
our
style
of
argo
cd
at
all,
but
it
will
bring
a
good
experience
to
users
to
see
how
sections
is
separated.
You
cannot
understand
from
this
that
here,
like
application
applications
is
the
same
size
as
manage
applications.
B
A
A
Limit
it
to
like
forms
and
and
even
the
input
here
is
kind
of
like
yeah-
maybe
what?
If
we
think
about
it
as
a
way
to
redesign
this
sliding
panels
in
the
application,
we
would
have
to
change
background
color,
because
I'm
assuming
because
right
now,
it's
gray
and
it's
kind
of
inverted
in
in
the
in
the
you
know
in
the
mock-up,
and
I
feel
like
it's
not
such
a
big
big
change
like
it.
It
can
be
probably
should
be
doable
to
just.
A
You
know
like
execute
it
and
we
don't
have
to
build
prototypes
for
all
existing
sliding
panels
and
then
okay
and
I'm
just
you,
know,
thinking
about
and
the
second,
so
the
duration.
Maybe
we
could
have
like
right
now.
We
have
a
single
kind
of
brand
set
of
css
classes
for
a
input
element
and
we
use
it
everywhere.
A
Maybe
we
can
think
about
it
differently
and
we
can
introduce
a
new
component.
As
I
mentioned
mentioned,
you
know
the
form,
input
and
and
that
form
input
can
be
different.
So
as
long
as
we
use
the
same
style
in
all
forms,
it
can
be
different
from
inputs
which
are
not
part
of
input
forms
like
we
have,
for
example,
some
couple
other
places
where
we
have
input,
but
so
basically,
it's
okay
to
have
two
type
of
inputs
and
the
second
type
that
we're
going
to
introduce
is
only
going
to
be
used
in
in
this.
A
E
So,
just
just
on
top
of
it
right,
so
what
we
have
decided,
actually,
we
lost
keep
track
of
so
in
the
new
window
right.
So
what
are
the
elements
that
we
will
be
that.
A
Yeah,
I
guess
we
we
were
trying
to
find
you
know.
Where
do
we
move
next
from
these?
So
far,
I
could
catch
that
feeling.
I
think
the
idea
that
you
know
we
now
reducing
the
scope
just
to
sliding
panel
component
pretty
much
okay,
okay
and
yeah,
and
then,
if
you
look
at
it
from
this
particular,
basically
I
think
we
will
need
to.
We
should
assume
that
we
won't
change.
A
You
know
like
phones,
maybe
because
fonts
has
to
be
consistent,
like
it
would
look
strange
if
sliding
queen
had
a
different
fonts,
but
it's
okay,
totally
to
change
the
color,
the
header
color
and
then
introduce
new
elements
like
this
section,
separators,
not
sure
how
to
call
them.
You
know
the
schedule
one.
It's
pretty
much.
The
separator
that
separates.
E
That's
right,
yeah,
that
is
there's
a.
I
think
those
are
good.
I
think
as
well
someone
etcetera
the
color
light
blue
color
and
all
I
think,
those
I
think
we
are
implementing
that
needs
to
be
taken
care
of
it's
very,
very
light.
Yeah.
A
Okay,
maybe
yeah.
Maybe
we
should
not
change
yeah
color
palette.
We
basically
need
to
pick
colors
from
from
existing
palette.
Basically,
if
something
is
blue
here,
it's
like
less.
You
know
it's
slightly
different
color
than
from
what
we
have,
but
when
we
implement
it
we
can
just
pick
exact
same
color
and
basically
it
it
will
be
the
same
set
of
colors.
B
Here
that
we
should
not
introduce
like
this
blue
that
on
allo
button,
yes,
we
should
use
the
same.
I
guess
here
I
guess
this
is
I'm
not
confused
yeah.
A
D
A
I
think
that's
what
I
was
trying
to
propose.
I
guess
I
wanted
to
say
that
if
we
yeah
that
this
is
the
biggest
challenge
like,
if
you
introduce
your
eye
change,
you
kind
of
have
to
make
it
everywhere
and
yeah.
It
felt
like
extremely
difficult
to
redesign
everything,
but
if
we
just
limit
it
to
sliding
panels-
and
I
think
like
five
or
six
of
these-
you
know
where
we
create
applications.
B
B
A
Okay,
yeah,
then
it
would
be
awesome.
I
would
pick
if
you're
looking
for
for
the
next
one,
I
would
choose
to
implement
application,
create
creation
as
panel
yeah
this
one
it's
kind
of
it's
because
I
felt
I
feel
like
it's
similar
to
create
sync
window
panel.
It's
just
a
bunch
of
sections
or
I'm
not
sure
how
to
call
them.
Yeah,
yes,
and
it
also.
It
has
few
more
input
types
like
drop
downs.
I
don't
think
we
have
drop
down
some
create
sync
window,
no
yeah.
We
don't
okay,
okay,
yeah!
A
B
A
And
then
everyone,
if
anyone
has
objections,
please
speak
up.
I
think
it
was
another
goal
of
this
presentation
too.
I
know
ui
is
maybe
the
most
opinionated
topic,
like
everyone
has
opinion
about
ui,
even
if
you
don't
develop
it
so
yeah,
that's
why
we
felt
it's
fair
to
bring
it
up
all
right.
Thank
you.
Thank
you,
awesome
all
right
and
we
had
another
similar
topic.
I'm
not
sure
if
you
prepared
anything
remington,
but
basically
it's
one
more
idea
of
an
improvement
of
existing
ui,
which
remington
already
started
working
on
pc
to
implement
this.
A
F
A
F
Yeah,
I
I
it
should
be
pretty
quick.
I
just
have
the
a
side-by-side
comparison,
so
this
is
I
this
is
what
I've
implemented.
It's
not
completely
polished
yet,
but
it
is
pretty
close.
So
essentially,
what
we're
doing
is
just
making
the
sidebar
a
little
bit
wider
and
we're
moving
the
filters
to
it.
So
for
reference,
here's
what
we
have
currently-
and
this
is
kind
of
new
to
the
latest-
release
where
you
can
pin
this
here
and
you
can
have
it
hide
and
at
smaller
screen
widths.
F
So
I
just
think
it's
a
little
bit
better
use
of
screen
real
estate
and
it's
a
little
bit
more
of
an
elegant
solution
to
the
the
filters
problem
and
then
the
same
thing
with
the
applications.
F
The
application
details,
the
resource
filters,
they've
been
moved
over
here
as
well,
so
yeah,
it's
a
pretty
straightforward
change
and
another
kind
of
thought
that
I
had
was,
if
you've
been
following
the
extensions
concept.
That's
pretty.
That
was
actually
incorporated
into
this
release,
where
we
enabled
the
ability
to
serve
extensions
to
the
argue,
ui,
and
so
the
first
use
case
of
this
would
be
for
a
rollout.
F
If
you
click
on
a
rollout
and
you
install
this
extension
you'll
be
able
to-
I
don't
have
it
installed
in
this
cluster,
but
you'll
be
able
to
you
know
view
more
metadata
about
the
rollout
and
by
expanding
the
sidebar.
I
was
considering
that
in
the
future
we
could
maybe
offer
some
extensibility
to
the
sidebar
at
an
application
level
or
at
a
cluster
level
or
an
argosy
instance
level,
and
it
just
kind
of
you
know,
adds
another
area
where
we
could
potentially
expand
some
things.
A
F
Yeah
yeah
exactly
it
just
I
I
guess
it
just
kind
of
it
offers
more
customers
customizability
to
the
ui
that,
but
even
more
so
than
you
know,
just
adding
some
new
some
new
metadata
for
crds.
But
yeah
I
mean
that's,
that's
just
the
concept
that
hasn't
been
implemented
at
all,
but
it's
just
something
some
context.
I
guess
behind.
It's
not
just
you
know,
redesigned
for
redesign's
sake
it.
It
kind
of
opens
up
this
this
door
for
later
on.
A
Yeah,
thank
you.
I
think
it's
we
it's
good
to
have.
You
know
more
arguments
for
this
change,
I'm
kind
of
I'm.
I
don't
have
this,
I'm
basically
speaking,
just
as
a
user
of
a
ui,
usually
users
kind
of
you
know
like
refreshes,
but
at
the
same
time
there
are
always
someone
who
who
doesn't
like
the
change.
A
A
F
Yeah,
that's
a
that's
a
great
point.
I
think
a
thought
that
I
had
had
when
we
were
discussing
the
sliding
panel
actually
is
this.
The
sliding
panel
has
always
made
me
think
about
you
know
this
grayed
out
portion
is
really
unusable
when
you're
using
the
sliding
panel-
and
I
I
thought
that
you
know-
maybe
we
could
even
expand
the
sliding
panel
to
take
up
the
entire
page
and
just
have
it
be
a
new
page
rather
than
an
overlay,
and
it
would
kind
of
complement
the
sidebar.
F
Well
because,
like
you
said,
we
could
move
some
actions
over
here
and
have
this
kind
of
just
expand
a
little
bit
and
be
its
own
page
and
instead
of
being
an
overlay
and
kind
of
like
a
halfway,
it
could
be
expanded.
And
if
we're
going
to
do
the
sliding
panel
anyway,
then
or
redesign
the
sliding
panel
anyway,
we
could
maybe
incorporate
some
of
that.
F
A
C
The
same
comment
as
sam
samyak
about
the
when
you
collapse
the
side
panel.
F
Oh
yeah,
that's
a
that's
a
bug.
That's
just
my
implementation!
Yeah!
I
was
planning
on
adding
some
sort
of
icon
here
and
and
actually
potentially
replacing
this
arrow
button
with
with
even
a
context,
sensitive
icon
that
you
know
if
you.
D
F
On
this,
it's
going
to
expand
so
that
you
can
see
the
filters
something
like
that,
but
yeah.
Thank
you
so
yeah.
It
looks
great
thanks.
A
See
some
comments,
but
I
think
these
comments
also
should
make
it
eventually
into
pr.
You
know
like
try
to
change
text
slightly,
make
it
smaller
and
then
yeah,
because
it
will
be
really
hard
to
catch
it
right
right
now,
yeah.
F
F
All
right
that
was
pretty
much
it.
Okay,.
A
E
So
I
think,
before
going
there,
maybe
we
can
discuss
again
on
the
current
experience
like
the
trials
and
discussion
experience
probably
share
with
everyone.
That
would
be
great,
I
think,
in
the
last
and
this
week
we
have
william
and
abhishek
and
chaitan
and
pasha
probably
who
wants
to
come
next?
Can
you
please
share
your
experience
and
how
is
it
is
and
any
feedback.
B
I
actually
didn't
answer
on
discussions,
but
I
answered
in
slack
because
in
discussions
I
didn't
find
the
tickets
that
I
can
answer,
but
in
slack
I
saw
people
ask
few
questions,
I'm
not
sure
that
I
was
able
to
help,
but
so
it's
already
second
time
that,
for
me
happens
I
I
know
how
to
start.
I
know
answer,
but
in
the
end
I
have
like
a
lack
of
knowledge.
So
what
is
your
recommendation
in
such
case?
B
E
Yeah,
that
is
true.
I
think
we
have
a
primary,
also
chaitan,
so
there
are
two
right
primary
and
secondary,
so
the
assumption
is
like
chatan
will
be
able
to
help
more
and
you
can
ask
help
from
chatham
and
learn
from
him.
So
that
is
the
idea
why
we
have
two
members
again:
it's
not
just
you
only
need
to,
but
if
you
don't
have
answers,
probably
corresponding.
E
Or
if
there
is
not,
it
is
still
open.
You
can
check
with
or
point
to
any
contributors
like
slack
and
the
slack
channel
or
anywhere
you
can
post
like
need
help
on
this.
Maybe
right
so
it
is
still
doable,
but
I
think
primary
will
be
able
to
more
help,
but
you
can
still
point
to
the
community
and
in
the
the
contributors
or
maintenance
and
like
but
alex
what
do
you
think
actually
in
this
kind
of
situations,
anything
any
other
solutions
that
you
think
about.
A
B
And
then
yeah
it's
in
the
end.
It's
helped
me
to
learn
something
because
I
I
start
to
help.
It's
ask
its
requirement
to
go
to
the
code
to
check
code
to
understand
code,
and
it's
helped
me
to
improve
my
skills
in
arca.
But
in
the
end
I
can
be
blocked
that
exactly
happens
for
me
for
today
and
few
days
ago
ago,
and
I
don't
want
to
confuse.
A
I
The
conversation
perfect,
so
I
so
I
addressed
couple
of
our
discussions
this
time
and
for
the
ones
I
had
doubts.
I
reached
out
to
people,
but
so
I
did
find
few
of
them
a
little
difficult
because
they
were
very
specific
to
the
to
the
user
or
the
use
case
or
the
context
in
which
they
had
faced
that
issue,
but
yeah,
I
think
so,
reaching
out
to
people
and
asking
them.
I.
A
So
basically,
that's,
I
think
perfect
outcome,
like
we
catched
a
regression
used
in
2.1
release
and
and
and
fixed
it
yeah,
and
I
it's
kind
of
I
think
it
was
like
chetan-
had
no
chance
to
know
about
it,
because
it
was
like
kind
of
just
a
side
effect
of
a
different
change
that
I
worked
on
and
I
haven't
I
happen
to
know
yeah
and
we
totally
missed
it
during
the
testing.
E
I
think
the
idea
is
not
both
primary
and
secondary
to
know
everything
I
don't
think
they'll
know
everything,
but
as
much
as
like,
if
you
can
reply
like,
will
they
get
back
to
you
or
get
more
interest
from
the
other
contributors,
probably
most
of
the
channel
like
help
me
with
this,
I
think
that
is
a
good
starting
point,
because
not
all
of
them
will
look
at
the
issues
and
for
some
which
we
don't
know.
If
you
asking
the
contributors,
then
confidence
will
be
able
to
help
who
are
in
that
relevant
domain.
E
I
think
that
will
be
definitely
a
good
start
as
alexa.
I
think
it
will
be
a
learning
curve
also
for
everyone.
E
Thank
you
for
that
and
from
the
shooterizer,
william
and
upshake
any
feedback
or
any
issues
or
how
we
can
make
it
better.
Video.
J
So
yeah,
I
think
me
and
abhishek,
is
it
I
think,
was
the
triad
last
week.
No,
no
problem,
I
find
I
think
I
do
realize.
Having
a
partner
helps.
Sometimes
you
know
we
can
cover
each
other.
Like
you
have
you,
you
know
your
business
again
and
that
that
I
think
that's
working
out
pretty
well
yeah
and
yeah
I
found
doing.
Chia
is
less
occupying
than
answering
questions
in
this
in
the
discussion.
J
So
there's
also,
you
know,
there's
another
feedback.
I
guess
yeah.
G
J
A
I
would
just
read
the
comment
and
just
execute
what
was
in
that
comment,
so
it
helped
me
at
least-
and
I
hope
that
soon
I
I
I
don't
remember
the
day
jc
like
when
we
can
finally
permissions
to
members
to
do
these
changes.
I
hope
it
will
be
like
yeah.
C
I
think
I
I
think
we
pretty
much
have
unanimous
consent
on
this.
Let
me
go
check
the.
Let
me
count
up
the
thing,
because
I
think
we
can
do
that
early
then
september.
First.
C
Two
week
period,
but
I
I
put
in
the
if
we
already
achieved
a
super
majority
by
before
then
that
we
can
go
proceed:
okay,
yeah,
I
guess
yeah
and
I'm
pretty
sure
we
did.
We
met
that
so.
E
And
just
on
top
of
that
right
so
now
the
solution
is,
if
you
imagine
the
shoes
and
trials
together.
However,
instead
of
having
four
members
like
too
far
issues
issue
discussions
and
two
for
trials,
can
you
have
only
two
for
both
of
them
and
any
comments?
If
you
do
that.
E
So
one
advantage
that
I
see
is,
I
will
have
a
long
cycle-
will
be
available
rather
than
short
cycles
for
a
few,
so
that
will
be
one
advantage
and
at
the
same
time
again,
you
will
see
like
you
know
like
what
are
the
issues
that
are
coming
in,
that
triads
forum
and
also
the
discussions
you'll
be
able
to
you'll,
have
the
ability
to
move
back
and
forth
or
move
the
triads
to
discussions.
It
is
not
appropriate,
so
those
are
some
of
the
advantages
that
I
see.
A
I
kind
of
like
that
idea
because
it
gives
us
way
more
people
like
now
we're
going
to
have
really
long
list
of
people
who
might
participate
in
both
yeah,
and
then
I
I
think
I
heard
just
now
that
william
said
it
was
not
so
difficult
to
try.
So.
J
Yeah,
comparing
to
moderating
the
discussion.
Yes,
it's
yeah
because
for
questions
you
know
the
person
kind
of
waiting
for
your
answer.
Then
you
have
to
go.
Do
some
research
and
come
back
and
may
have
more
more
questions?
Yeah
a
little
more
occupied
that
during
doing
discussion.
Then
then,
then
you,
you
know
you
look
at
the
issue.
Maybe
you
may
have
to
take
it
a
little
bit
but
yeah.
You
know
you're
not
looking
to
have
some
answer
there
right.
So
so
that's
that's.
Why
I'm
saying
that.
J
E
J
I
okay,
that
you
can
try
it.
I
think
you
I
mean
I
have
more
people.
So,
like
you
guys,
you
have
two
people
so
like
four
people
doing
the
both
together
in
one
cycle.
J
You
probably
have
to
commit
quite
a
bit
of
time,
if
you,
if
you
do
the
two
people
doing
all
of
this,
I
think
a
problem.
If
you
you
throw
in
more
people,
maybe
yeah,
but
you
use
riding
on
the
sis
the
same
people
doing
both
the
trihard
and,
I
think
gonna
be
a
little
heavy.
A
A
J
So
I'm
not
sure
we
have,
I
think
the
well
just
because
the
discussion
is
quite
quite
quite
a
bit
of
time
by
itself
and
then
you
feel
it
more
more
responsibility
in
one
cycle
than
probably
a
little
bit
much.
E
I
mean,
like
the
other
means
yeah
that
is
right,
so
we'll
have
you'll
be
upgraded
more,
but
the
other
way
is
the
cycle
will
be
runs
longer.
So
you'll
have
one
week
you
will
dedicate
here,
but
you
won't
get
the
cycle
again
after
maybe
several
weeks.
So
that
is
the
advantage
that
I
see.
E
E
Okay,
jesse,
do
you
have
anything?
Do
you
have
a
comment.
E
I
mean
like
we
got
the
count
comment
like
it
will
be
more
work
for
two
people
to
have
both
and
having
two
separate
paths
for
two
to
each
will
be
less
work.
So
that
is
one
comment
we
got.
But
what
do
you
think
about
that?.
C
I
I
think
that
would
be
a
good
idea,
but
to
me
I
I
lumped
the
two
together
because
to
me
they're
kind
of
similar
work
and
it
makes
sense
to
me.