►
From YouTube: Argo Contributor Office Hours 2nd Sep 2021
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
good
morning,
good
evening,
everyone,
so
let
me
start
from
sharing
my
screen
and
notice.
There
were
several
items
added
to
agenda
thanks
for
people
who
edited
so
today
I
see
we
have
a
request
to
talk
about
application
set
and
it
was
carry
over
it
from
the
previous
meeting
and
as
I
remember,
I
think
it
was
edited
by.
B
Yeah,
I
added
that,
actually,
I
did
the
first
three
items,
so
let
me
talk
about
each
again
like
just
like
how
we
discussed
on
the
cd
milestones.
I
would
like
to
keep
doing
that
for
other
projects
also
so
like,
for
example,
app
sets
or
april
app
arbor
loads
and
even
the
other
lab
projects
so
for
the
app.
B
D
Can
you
hear
me
now
yeah,
okay,
for
some
reason,
this
recent
version
of
fedora
has
done
some
strange
things
to
my
sound
settings.
Yeah
other
people
have
hit
the
same
issue
anyway.
Presuming
you
can
still
hear
me.
Okay,
I
can
show
briefly
what
we've
got
up
for
the
third
milestone
of
application
sets
all.
A
Right,
let
me
stop
shooting,
and
so
you
can
sure
as
well.
D
Yeah,
so
presuming
folks
can
see
my
screen.
This
is
what
we've
currently
got
on.
The
third
milestone
for
application
sets
a
bunch
of
stuff.
That's
red
hat
folks
are
working
on
kind
of
a
big
feature
that
I'm
hoping
someone
from
the
community
will
step
into
and
then
some
documentation
work,
but
I'll
go
through
that,
probably
the
top
one.
It's
been
in
our
milestone
list
for
the
past
couple,
iterations,
that's
moving
the
applications
at
repo
into
the
argo
proj
organization.
D
I
need
to
connect
with
shubik
on
this
one
to
see
if
there
are
any
steps
that
we
need
to
take
on
our
side.
But
from
a
technical
perspective,
it
should
just
be
a
matter
of
moving
the
application
set
repo
to
the
argo
proj
organization
and
then
updating
any
references
in
the
code
or
in
our
ci
cd
pipeline
as
needed,
and
then
within
the
organization,
we'd
figure
out
what
exactly
was
required
in
terms
of
like
paperwork
or
anything
like
that,
but
yeah.
D
That's
the
top
one
and
we're
already
pushing
our
application,
set
images
into
the
argo
proj
key
dot,
io
organization.
So
it
would
make
sense
to
move
the
application
set
repo
there
too.
D
It's
just
a
matter
of
making
sure
that
we
follow
the
correct
process,
I'm
in
the
process
of
so
a
lot
of
what
I
focus
on
personally
is
not
features,
but
things
around
bug,
fixing
and
test
fixing
and
new
tests,
and
things
like
that,
mainly
because,
when
the
community
wants
to
submit
a
pr,
it's
often
a
feature
when
folks
in
the
community
are
making
contributions
to
open
source
projects.
D
D
So
in
that
vein,
a
couple
of
items
related
to
some
test
fixes
and
ci
process
improvements
that
I'd
like
to
get
in
this
is
one
we're
seeing
around
how
the
applications
that
ede
tests
are
run
in
the
cluster
configuration
one
around
improving
how
we
are
running
the
ete
test
against
slightly
argo
cd,
so
like
as
new
commits
go
into
upstream
master
branch
ergo
cd.
It
would
be
great
if
we
had
an
application
set,
github
action
that
ran
on
that
to
make
sure
that
y'all
weren't
breaking
us
upstream.
D
So
that's
what
this
one's
about.
I've
actually
got
a
branch,
that's
mostly
completed
that
and
then
we've
got
some
enhancements.
That
folks
are
working
on.
D
Ishita
is
working
on
adding
error
and
condition
status
to
the
application
set
cr,
which
is
something
that
we've
been
sorely
missing
from
previous
releases,
like
folks,
have
had
to
look
at
the
log
of
the
application
set
pod.
D
In
order
to
get
that
information,
chetten
is
working
on
the
ability
to
trigger
the
git
generators
using
a
web
hook
in
basically
the
exact
same
way
that
argo
cd
does
it,
where
you
can
hook
up
a
git,
for
example,
github
web
hook
to
argo
cd
and
have
it
ping
argo
cd
to
tell
argo
cd
to
do
a
refresh.
D
So
at
the
moment,
parameters
are
limited
to
being
string,
keys
and
string
values,
but
we've
had
a
lot
of
folks
on
many
different
issues,
requesting
the
ability
to
insert
json
objects
into
the
application
set
template
rather
than
just
inserting
strings,
especially
when
it
comes
to
inserting
things
like
helm
parameters.
So
that's
what
that
one
is
about,
and,
as
I
mentioned,
there
have
been
discussions
on
it
on
a
number
of
other
issues
and
then
the
last
ones.
It's
just
some
doc
updates
this
one.
D
I've
got
a
a
branch
for
just
some
general
improvements,
ede
tests
and
I
at
the
moment
our
documentation
on
how
to
write
and
run
tests
is
limiting
is
limited.
Rather
so
I
thought
I'd
just
expand
on
that,
but
you
know
we've
had
plenty
of
folks
that
have
figured
that
out.
However,
I'd
still
like
to
at
least
mention
that
in
the
docs
to
be
consistent
with
what
users
expect,
so
that's
what
I
have
for
the
third
milestone
so
far.
D
The
one
thing
I
wanted
to
add
was
with
application
sets.
A
lot
of
contributions
have
come
from
the
community,
so
those
are
things
we
can't
predict
will
be
in
a
milestone
until,
like
someone's
opened
a
pr
and
we've
reviewed
it
and
it
gets
in.
So
it's
certainly
possible
that
more
stuff
will
be
added,
but
that
stuff's
just
difficult
to
predict.
D
A
I'm
really
happy
to
hear
conditions
and
status.
I
I
second
that
it
was.
You
know
it
will
improve
usability
a
lot
and
I
basically,
I
think,
as
soon
as
we
have
it,
we
should
have
as
health
as
a
health
assessment
function
in
argo
cd,
so
the
status
of
upset
will
be
visible,
enjoy
and
do
you
might?
If
I
I
wanted
to
offer
two
more
features,
and
I
guess
you
know
I'm
not
committing
right
now,
but
I
mean
I'm
pretty
sure
we
will
have
death
cycles
to
contribute
to
features
so
dramatically.
A
If
I,
basically,
if
you
could,
if
you
could
open
issue
three
five,
six,
oh.
A
Yes,
let
me
share
with
you
and
yeah,
so
you
can
see
my
screen
right,
yep,
okay,
this
one
is,
I
want
to
talk
about
it
second,
so
first
one
is
kind
of
it's
like
go
side
by
side
with
new
field
conditions,
but
basically
I
think
it's
kind
of
half
duplicate
of
the
feature
that
you're
already
going
to
work
on,
and
I
just
wanted
to
suggest
to
gracefully
handle
application,
gradation
errors,
and
what
I
mean
by
that
is
that
upset
generates
upside
potentially
can
generate
a
couple
of
dozens
of
applications
and
then
what
we
discovered
is
that
sometimes
application
generated
apps
became
invalid
yeah.
A
You
know
like
later
later
in
time,
for
example,
if
user
decides
to
disconnect
the
cluster
that
was
referenced
by
upset,
then
this
application
becomes
invalid
and
right
now,
application
upset
just
kind
of
stops
generating
everything,
and
so
I
am
proposing
to
kind
of
generate
healthy,
apps
and
report
errors,
in
condition
so
yeah.
I
think
it
will
kind
of
it
looks
like
a
better
behavior
to
me,
yeah,
so
yeah.
D
A
And
it
felt
to
me
kind
of
you
know,
maybe
like
a
big
change,
but
since
we
already
can
explain
that-
and
there
is
already
a
work
so
as
soon
as
we
have
status
and
conditions,
the
second
portion
will
be
extremely
easy
to
implement.
A
A
Yes
and
the
second,
it's
a
little
bigger
feature,
so
it's
kind
of
a
new
generator
type
that
allow
that
this
is
okay.
Let
me
start
back
first.
Actually,
let
me
start
from
the
the
use
case
so
that
what
we're
trying
to
solve
is
kind
of
bulk
management
problem
like
if
you
it's
focused
on
generating
addons
for
clusters
and
basically,
what
we
discovered
is
that
many
users
they
want
to
install
the
same
type
of
applications
in
all
clusters
and
they
always
have
edge
cases
and
right
now
upset.
A
Let
you
either
install
the
same
thing
into
all
clusters
or
kind
of
hard
code,
all
your
cases,
and
we
I'm
kind
of
trying
to
find
a
way
to
to
combine
these
two
approaches.
Yes,
and
I
think
we
maybe
we
should
not
discuss
implementation
details
right
now,
but
this
is
roughly
the
problem
so
and
okay
proposal
is
that
we
introduce
new
generator
that
takes
two
other
generators
and
merge
them,
and
one
generator
is
supposed
to
give
the
common
case.
A
A
D
A
Yeah,
I
have
permission
to
it.
I
just
didn't
okay.
B
I
think
this
is
great.
I
think
anyone
else
have
any
bugs
or
issues
that
they
wanted
to
be
part
of
next
milestone.
Please
bring
in
we'll
continue
to
discuss
in
the
next
week
also
again,
contributions
to
apps.
That's
also
very
appreciated,
like
just
like
how
congratulations
trending,
I
think,
applications
also
one
of
the
training
projects.
I
think
confidence
to
there
is
then
appreciated
there.
B
A
And
I
just
wanted
to
share
that
yeah,
like
upset,
I
found
one
more
production
user,
we're
really
planning
to
use
it
into
it,
for
you
know
to
manage
so
it
we
started
just
using
it
internally.
Basically,
argo
team
uses
it
to
install
algorithms,
and
now
it's
kind
of
spreading
and
more
teams
are
going
to
use
it.
So
now
we
start
dealing
with
you
know.
Basically,
our
team
is
supposed
to
run
upset
as
a
tool
for
more
teams,
and
you
might
expect
more
feature
requests
like.
A
E
Sorry,
I
would
ask
questions,
but
it's
not
about
upsets,
but
I
would
cover
it
with
this.
I'm
not
sure
that,
from
last
conversation
I
understand
which
items
can
be
added
to
milestones,
because,
as
I
understand,
we
cannot
at
milestone
any
regular
issues
it
can
be
like.
So
I
wanted
to
ask
if
I'm
working
on
some
hate
improvements.
A
I
think
we
kind
of
spoke
about
it
and
we
tried
to
document
it's
so
we
have
a
document.
I
think
it's
called
release
cadence,
it's
mostly
about
cd
projekt.
It's
kind
of
upset
is
outlier,
because
it's
basically
as
any
other
labs
project
upset
and
cargo's
identifications,
have
kind
of
have
one
person
who
maintains
it,
and
so
I
guess
for
upset
and
for
notifications.
We
just
have
less
strict
process
about
what
goes
into
milestone
and
for
argo
cd.
A
We
agreed
that
maintainers
must
everything
that
get
more
gets
merged
must
have
a
maintainer
who
committed
to
test
it
and
review,
of
course,
yeah,
and
so
the
agreement
was
that
we
assign
like
every
time
we
merge
change.
We
assign
a
maintainer
who
eventually
will
work
on
making
sure
that
quality
is
good
and
fixing
bugs
closer
to
end
of
release,
but
so
to
answer
your
question.
A
Anything
can
go
into
milestone
as
long
as
there
is
a
maintainer
behind
it
who
wants
to
who
will
test
and
verify
it
and
fix
bugs
if
necessary,
and
we're
trying
to
before,
like
before.
We
start
working
on
milestone,
we're
trying
to
get
all
the
items
that
we
hope
to
get
done
in
that
milestone
just
to
provide
visibility
to
community
and
to
get
you
know,
it's
like
a
data
for
road
map,
but
during
the
milestone
we
can
include
more
if
maintainers
have
time
to
you
know
to
fix
some
tests.
B
E
B
Request
yeah,
I
think
you
usually
can
bring
it
to
the
contributor
meetings,
so
that
maintainers
are
very
aware
of
one
of
the
tickets
of
the
issues
and
the
priority
again
based
on
the
priorities
and
because
based
on
the
release
cadence,
whether
they
can
be
closed
in
time
and
again
like
we
don't
want
to
delay
the
release
because
of
some
of
the
milestones
not
really
done
so
based
on
those
timelines.
I
think
please
get
into
the
contributors
meeting
here.
B
B
So,
apart
from
the
two
of
the
features
that
are
currently
under
review,
I
think
1.1
release
is.
We
are
trying
to
announce
like
in
the
next
couple
of
weeks
to
have
at
least
a
release
cut,
so
I
want
to
see
like
if
any
one
of
the
contributors
or
anyone
who
is
working
on
the
reloads,
any
issues
that
needs
to
be
part
of
1.1
please
bring
in
and
we
will
start
again
reviews
or
anything
that
is
required
or
any
help.
B
Regarding
evaluations,
please
bring
into
the
confidence
meeting
or
offline
to
the
maintenance
or
to
the
approvals
or
reviewers.
I
think
we
will
start
prioritizing
those
issues
based
on
the
priority.
You
know.
A
Yeah,
I
I
think
jesse
was
going
to
join,
but
I
guess
maybe
he
didn't
get
them,
but
I
just
spoke
about
him
about
the
milestone
yesterday
and
I
think
so
as
you
as
harry
mentioned,
there
are
two
issues.
Two
feature
requests,
I
would
say
one
is
a
dynamic,
stable
scale
and
second
cloud
watch
integration.
I
feel
like
cloud
watch.
Integration
is
at
risk
to
be
carry
over
to
the
next
release,
but
it's
like
we
don't
know.
If
about
anyone
who
is
blocked
by
the
future,
so
yeah
speak
up,
please,
if
you
really
need
it.
B
But
any
other
issues
that
you
guys
are
working
on
please
bring
in
if
you
need
help
for
regarding
the
reviews
or
violations,
we'll
happy
to
pay
attention
based
on
the
priority.
C
B
Yeah
next
is,
I
think,
again,
like
we
are
continuing
with
the
price
discussion
stuff,
where
we
are
hoping
to
have
at
least
five
minutes
discussion
every
contributing
session.
So
this
week
I
think
we
have
alex
and
dan
they
are
the
triaz,
slash
discussion,
war
writers.
So
please
share
your
feedback
and
again
I'll
start
with
dan.
Actually,
as
he's
doing
it
for
the
first
time
to
get
his
feedback
and
improvements
that
he
wants
to
propose.
B
G
Sorry
me
yeah,
sorry,
sorry
I
was,
I
was
distracted.
Can
you
ask.
B
Again
so
we
are
actually
discussing
about
the
triads
and
moderator,
discussion,
moderator,
feedback
and
updates.
So
I
think
this
week
alex
and
you
are
the
primary
and
secondary.
So
I
wanted
to
get
feedback
or
any
improvements
that
you
want
to
propose
and
what
is
your
experience
for
the
last
one.
G
Yeah,
so
I
was
able
to
handle
a
couple
of
things
and
a
few
things
look
like
they
were
actually
bugs,
and
so
in
those
cases
I
would
just
encourage
people
like
okay,
like
you've,
reproduced
this
you've
shown
the
output.
This
sounds
like
a
bug.
I
recommend
opening
a
ticket,
one
of
the
things
that
I
couldn't
do
I
don't
know
if
you
can
mark
a
mark.
A
thing
is
answered
because
I
didn't
see
a
way
to
do
that
because
some
of
them
it
was
like.
Well,
I
answered
this.
G
The
person
wants
to,
like
you
know,
complete
it
or
not,
is
like
oh
yeah.
It
sounds
like
a
bug
you
show
up
at
an
issue
answered,
so
I
don't
know
if
that's
a
permissions
thing,
but
I
would
have
liked
to
have
been
able
to
do
that
and
then
something
else
that
actually
I
did
want
to
bring
up
with
the
group
is
code
fresh.
G
We
actually
want
to
hire
somebody
whose
job
is
essentially
to
do
this
full
time,
including
in
in
both
slack
as
well
as
the
issues.
So
we
have
a
job
posting
for
that
I
can
throw
it
in
the
I'll,
throw
it
in
the
agenda
here.
G
But
if,
if
anybody,
if
you
know
anybody
that
would
like
hey
I'd
love
to
just
be
hanging
out
in
the
community,
answering
questions
working
with
like
people
implementing
argo,
we
actually
have
the
open
head
so
like
we
would
love
to
hire
somebody
to
do
this
full
time
and
definitely
spending
like
the
last
week
on
it,
where
I
was
only
able
to
answer
like
a
couple
of
questions,
and
there
were
several
that
were
a
little
bit
like
beyond
me,
so
I
wasn't
able
to
tackle
those
ones.
G
A
I
just
my
take
on
it,
so
I
think
I
in
github
discussions.
I
didn't
try
to
mark
discussion
as
answered.
I
would
just
let
you
know
user
and
I
think
the
reason
is
I.
I
was
not
worried
much
about
having
to
make
too
much
of
discussions
which
are
not
answered,
but
for
issues
we
have
a
label
called
answered
and
what
I
think
we
do
with.
As
soon
as
I
post
an
answer,
I
apply
that
label
and
then
I
would
just
use
that
label
to
kind
of
you
know.
A
The
week
later,
I
would
filter
all
issues
which
has
that
label
and
they
open,
and
then
you
know
just
click
through
all
of
them
and
see.
If
you
know
user
responded,
anything
or
maybe
acknowledge
transfer
and
if
they
were
no
activity.
So
it's
kind
of
a
way
to
find
all
issues
which
supposed
to
be
discussions
and
clean
them
up
so
yeah.
I
guess
that's
my
suggestion
too.
A
If
you
have
an
issue,
that's
supposed
to
be
just
a
discussion
but
you're
not
sure,
and
then
you
kind
of
need
confirmation
from
user
I,
and
once
you
provide
an
answer,
just
apply
transfer
label
and
then
someone
else
will
see
that
label
again
in
the
future.
And
then,
if
there
is
follow-up
question
we
can
continue.
If
not,
we
can
just
close.
A
I
feel,
like
I
developed
lots
of
discussions
that
happens
to
be
regressions,
not
a
lot
lots
lots
but
at
least
actually
ended
up
to
be
regressions
that
we
missed
in
2.1
and
then
I'm
basically
already
have.
I
think
three
bug
fixes
that
we
should
release
sooner
or
later,
yeah
so
expect
2.1.2
yeah
bit
today.
A
G
Yeah,
I
didn't
identify
any
regressions,
but,
like
it
looks
like
there's
a
bug
in
how
argo
handles
taking
templates
that
use
range
to
generate
multiple
instances
of
an
application,
so
that
was
like
there
were
there
was
there
were
a
couple
of
things
like
that
that
were
like?
Oh
yeah,
like
that's,
not
like
something
that
people
commonly
do
and
it
appears
not
to
be
working.
G
I
haven't
tested
it
myself,
but
I
did
encourage
the
people
to
give
me
enough
information
that,
if
what
they
posted
is
accurate,
it
looks
like
it's
a
bug
so.
A
A
It's
easy
to
lose
these
type
of
notifications,
because
it's
just
a
comment
on
a
closed
back
and
easy
to
to
just
miss
it
yeah
and
yeah.
So
I
don't
know
why
people
may
be
shy
to
open
bugs,
so
they
don't
want
to
create
duplicates
and
instead
they
just
put
a
comment,
and
the
comment
says:
no.
It
is
still
happening
and
no
additional
with
no
additional
information
almost
impossible
to
so.
Basically,
they
think
the
same
symptom,
but
the
root
cause
might
be
new,
so
yeah.
A
A
A
Kind
of
you
know
just
thinking
clouded,
I
feel
like
by
personally
next
time.
I
will
not
reopen
an
old
issue.
Instead,
I
will
ask
a
person
to
file
bug
again
and
predict
and
provide
steps
to
reproduce,
because
it's
a
it's
a
wrong
assumption
that
all
steps
to
reproduce
are
going
to
reproduce
the
same
bug.
B
A
A
All
is
yes,
let's
move
on,
so
I
guess
next
topic
is
from
russia.
Oh
yes,
yes
and
I'm
I'm
guessing
we're
going
to
talk
about.
We
can
we're
going
to
continue
to
think
about
ui
redesign
and
I
can
open
this
url
or
I
can
just
let
basha
or
whoever
is
going
to
speak.
I
don't
want
to
see
a
wonder
to.
H
Yes,
of
course,
hello,
my
name
is
naistya.
I
am
your
utics
designer
in
code
rush,
I'm
going
to
help
you
with
design,
and
I
know
that
you
thought
about
design
in
previous
meeting
and
to
decide
to
start
the
design
from
site
drawer
and
that
we
must
keep
all
the
colors
palette
and
phone
okay.
I
share
my
screen.
H
H
Okay,
this
is
a
new
design.
What
I
propose,
because
previous
design
was
too
lighter,
I
tried
to
do
a
little
a
bit
different
line
using
your
colors
and
fonts
from
your
oto.
H
H
H
I
think
it
would
be
more
user
friendly,
because
when
user
fill
the
form
he
moves
from
top
part
to
bottom
and
after
he
finished
fill
this
form,
he
don't
have
to
come
back
to
top
and
okay
and
we
have
white
sections
as
in
all
design,
all
sections
have
a
header,
and
if
we
have
some
interaction
in
this
section.
H
H
H
I
propose
you
to
use
a
radio
button.
Instead,
it
and
I
redesigned
this
single
checkbox.
I
use
toggle
component.
Instead
it
and
I
a
little
bit
stylized
as
a
component.
H
And
this-
and
this
section
this
I
a
little
bit
stylized
too,
I
move
this.
I
move
this.
A
Awesome,
I
feel
like
even
without
clothes.
Looking
guys
I
like
to
design
more
than
what
we
have
now
and
it
it's,
and
it's
really
helps
that
you
use
argo
colors
again,
because,
yes,
basically
it's
much
easier
to,
I
feel
like.
If
we
decide
to
execute
it,
then
we
would
definitely
not
change
colors
in
the
beginning
and
we
would
have
to
mentally
re-kind
of
imagine
the
mock-up,
but
now
the
mock-up
uses
same
type
of
fonts
and
colors.
A
So
it's
much
easier
to
you
know,
digest
it
and
understand
what
we're
going
to
do
so
I
can
like
personally,
I
don't
have
any
complaints
about
it.
I
I
I
like
it
a
lot
to
me.
It
looks
much
cleaner.
I
really
like
that.
We
have
better
way
to
render
kind
of
headers
of
each
panel
or
I
don't
know
how
to
call
it.
We
call
it
white
box
so
and
before
white
box
was
just
a
white
box
literally
with
no
and
then
everything
inside
of
it
was
just
a
content.
A
B
I
think
this
is
looking
good
and
I
have
only
one
small
comment
again.
I
don't
know
like
which
one
is
better
like
if
the
right
side,
you
see
all
the
cap,
letters
like
most
of
them
and
on
the
left,
you
have
a
kind
of
camel
case
kind
of
stuff,
so
I
don't
like,
which
is
the
preferred
way
or
which
one
people
like
it
any
comments
on
that.
Oh,
so
you
think
you
know
the
the
most
of
the
letters
on
the
right
side
right.
B
They
are
capitals
like
maybe
head
or
if
you
scroll
up
the
application
names
and
like
yeah,
I
like
schema
validations.
A
Because
it's
kind
of
due
to
lack
of
imagination,
that
was
the
simplest
way
to
make
it
distinct,
basically
general
and
sword
this
this
thing's
a
kind
of
header
of
the
panel,
and
that's
why
we
choose
to
make
it
capital
case
so
that
it
would
be
different
from
content
yeah.
But
I
I
don't
know
I
guess
I
don't
know
last
year.
What
do
you
think
like
would
do
you
think
that
capital
is
too
much
or
or
you
don't
care
or
or.
G
Now
I
think
it's
better,
not
capitalized.
I
think
it's
really
clearly
laid
out
here
with
with
sort
of
sentence
case,
the
all
caps
one.
What
does
that
give
us?
I
don't
know
they.
They
really.
B
Yeah,
that's
right.
My
question
is
actually
what
is
the
user's
I'm
like?
What
is
the
user's
perspective
right,
how
the
changing
design,
or
maybe
coming
back
to
the
original
question
right?
What
is
the
thought
process
when
they
came
up
with
the
original
design,
where
there
is
a
distinction
between
caps
and
small
letters
like
if
you
see
in
the
base
you
have
both
actually
so
what
is
the
thought
process
and
changing
it?
How
it
actually
affects
the
user
behavior?
So
that's
a
question
yeah.
I.
G
Yeah
and
then
yi
brought
up
a
good
point
in
the
chat
here.
Is
there
anastasia?
Is
there
a
way
to
see
that
a
field
is
required
before
somebody
clicks
on
it,
because
it
looks
like
path
is
here
is
like
an
error
message
that
somebody
got
when
they
skipped
it.
Is
there
a
proactive
requirement
somewhere.
I
E
A
Fields
required-
I
was
just
thinking
if
we
could,
like
aesthetics,
might
be
annoying.
At
least
I
feel
I
find
it
annoying
if
you
have
astrix
next
to
everything,
but
maybe
some
kind
of
better
way
to
visualize
required
what,
if
we
simply
put
that
asterix
into
a
right
bottom
corner
of
every
input
field
which
is
required.
So
if,
if
we
find
a
way
to
make
it,
if
we
find
a
nicer
way
to
indicate
required
fields,
I
would
not
mind
to
as
a
user.
A
I
What
if
we
had
an
indicator
of
fields
that
are
explicitly
not
required?
Because
I
think
that
that's
the
exception,
and
so
you
know
we
could
just
have
a
little,
maybe
not
an
asterisk,
because
that
has
connotation
to
it,
but
some
sort
of
symbol.
That
indicates
this
is
not
required
in
the
cases
where
it's
not
because
that's
relatively
rare,
maybe
color
change
like
slightly
yeah
like
a
blue
or
a
gray,
or
something
or.
A
But
I
I
agree
with
this
conscious
point
that
it
has
to
be
kind
of
consistent
like
if
you
you
know
like
if
we
in
this
particular
case
most
of
the
fields
required
and
you
know,
and
then
it's
easier
to
put
nothing
because
everything
is
required
in
some
other
forms.
We
might
have
half
of
fields
required,
half
note
and
like
we
don't
want
to
reinvent
the
way
to
indeed
have
indicator,
it's
good
to
have
one
way
that
works
in
both
places.
A
I
A
And
I
I
know
that
you
know
if
everyone,
I'm
I'm
sure
everyone
in
the
call
has
ideas.
If
everyone
starts
throwing
these
ideas,
it
will
take
us
like
it
will
take
the
whole
meeting
just
to
hear
out
so
so
in
this
form,
any
of
them
are
optional.
Actually
yeah,
apart
from
the
sync
options,
I
don't
think
so.
A
I
think,
oh
okay,
if
we
scroll
down
all
the
way
to
the
bottom,
the
parameters
one,
I
think
most
of
okay
yeah
here
everything
is
optional,
but
you
kind
of
you
need
to
click,
add
new
to
get
an
option.
Okay,
now
I
take
it
back.
Everything
is
required,
even
in
this
last
section
you
kind
of
have
no
inputs
elements
in
in
the
beginning,
then
you
click
plus
button,
and
then
you
get
two
inputs
and
these
two
inputs
must
be
filled
in.
They
are
not
optional.
H
A
Yes,
I
guess
the
point
is
that
if
we
ever,
I
mean
we're
kind
of
trying
to
invent
like
a
forms
framework
right
now
and
and
then
later
we
will
use
the
same
framework
for
another
form
and
likely
that
form
will
have
half
of
fields
required,
half
of
them
not
required
and
then
same
question
will
be
again
like
we
will
have
to
decide.
How
do
we
differentiate
required.
F
A
A
F
F
I
speak
up
louder.
Maybe
can
you
hear
me
better
now
I
don't
know
where's
the
mic,
take
it
which
one
which
one
is
working
but
anyway,
so
I
was
saying
that
typically,
you
only
see
an
asterisk.
When
I
feel
is
required
you
don't
you
never
see
a
field
say
do
not
require
it's
not
required.
Typically,
you
don't
do
annotation
or
anything.
The
indicator
field
is
not
required,
even
though
for
a
form.
There's
a
lot
of
required
field.
You'll
see
a
lot
of
hashtags
right.
F
That's
that's
that's
what
I'm
trying
to
say,
but
I
I
think,
you're
saying
this
form
using
some
sort
of
framework.
So,
even
though,
in
this
form
everything
is
required,
but
I
think
we
use
the
same
kind
of
I
guess
the
ui
framework.
Eventually
we
come
into
some
some
pages,
some
form
that
have
some
optional
fields
and
some
quite
a
few
and
then.
F
Does
that
mean
if
we
do
the
required
this
will
an
entire
page
will
show
the.
F
I
don't
know
how
the
back
end
works.
I
don't
know
I
mean
I
don't
know
how
the
form
the
ui
actually
works.
So
I
I
like
what
I
hear
I
guess
is.
A
Yeah,
I
I
think
it's
I
mean
the
framework
is
not
implemented,
so
whatever
we
yeah,
we
will
have
this
option.
To
kind
of
you
know,
have
indicators
for
required
have
indicators
for
optional
only,
but
I
think
we
want
to
avoid
you
know
this
thinking
process
and
then
have
a
very
simple
rule
and
to
me
it
would
be
just
perfect
if
we
have
something
less
annoying
than
asterisk
or
like
some
way
to
basically
some
simple
way
to
so
that
developers
can
simply
indicate
to
the
framework
that
hey
this
field
is
required.
A
A
Yeah,
so
how
about?
If
we
just
you
know,
let
last
year
propose
couple
options,
because
I
know
that
your
discussions
will
take
forever
and
we
have
only
10
minutes
left
so
yeah.
I
guess
I'll
put
a
note
in
this
meeting
notes
that
we
kind
of
want
to
address
this
problem,
and
I
just
realized
that
this
is.
We
didn't
even
think
about
it
before
at
all.
Our
current
forums
have
no
indicators
of
required
non-required
fields,
so
yeah.
So
it's
it's
like
not
a
blocker,
I
would
say,
but
it's
really
good
to
have
it.
A
B
So
one
thing
I
think
I
have
is
again:
you
know
like
this
destination
director
and
all
can
you
actually
do?
We
have
like
close
or
kind
of
button?
Like
you
know
the
pages
you
see
right
forms
they
just
close
and
then,
when
you
click
on
it,
it
opens
once,
instead
of
showing
everything
in
the
one
place
you
will
have
like
fall
back
like
only
when
you
click
on
that
directory.
B
E
E
I
think
this.
Okay,
if
I
understood
it
right
this
button,
it's
kinda
it's
kind
of
bottom.
Here
you
click
on
it
and
it's
like
it's
a
drop
down
that
at
least
okay,
okay,.
A
E
A
A
Just
you
know
all
these
forms,
and
then
we
didn't
do
it,
because
I
was
worried
that
let's
say
user,
make
a
mistake
and
then
collapse
the
destination
and
then
click
create
and
nothing
happens
because
of
cluster
url
is
empty,
for
example,
but
if
destination
is
collapsed,
user
won't
know,
because
we
don't
have
like
it's
unclear
how
to
how
to
communicate
to
the
user
that
some
field
within
of
the
destination
form
is
invalid,
and
so
we
just
we're
kind
of
moving.
We
were.
A
A
B
I
think
william,
someone
actually
already
commented
in
this
chart
yeah.
So,
for
example,
like
usually
like
the
standard
is
like,
if
it
is
required
you
put
star
but
optional,
you
don't
really
put
option
as
something
actually.
So
it's
like
a
standard.
I
don't
think
we
should
deviate
from
that.
A
Okay-
and
I
guess
one
of
the
goals
of
the
meeting
was
to
you
know,
we
won't
apprec,
we
want
to
progress
and
you
know
commit
to
something
so
like
in
our
last
meeting.
We
narrowed
the
scope
to
just
the
panels
and
and
then
today
I
think
we
wanted
to
see
if
we
like
the
panel
purpose
panel
designs,
and
what
do
you
thought
people
like?
I
I
I
basically
feel
like
it's
good
enough
to
create
tickets
and
we
didn't
even
collect
enough
of
complaints.
A
I
think
we
only
have
we
need.
We
want
to
brainstorm
about
asterisks
or,
like
some
other
way,
to
indicate
required
fields,
any
other
blockers.
Anyone
see
or
we're
good
to
create
issue
for
that
and
then
try
to
work
on
it.
I
would
at
the
next
step
honestly,
I
would
create
mockup
for
for
panel
and
then
create
ticket
per
panel
and
and
then
execute
these
tickets.
A
Okay,
anyone
agrees
with
me
and-
and
I
think
and
thinks
this
is
good
way
too.
Oh
yeah,
I
see,
I
see,
convince
the
people
yeah.
I
I
think
it's
awesome
progress
here.
We,
I
guess
we
we
don't
have
to
like
it-
will
be
difficult
to
execute
it
in
parallel,
because
first
we
still
need
a
framework,
and
maybe
you
know
we
can
pick
one
panel
as
a.
A
We
should
pick
one
panel.
I
guess
which
has
most
of
the
input
elements
and
then
let
one
or
two
developers
work
on
it
and
kind
of
come
up
with
a
framework
and
then
once
framework
is
ready
and
one
panel
is
ready.
It
will
be
hopefully
trivial
to
update
all
other
panels
and
reuse
components,
and
I
guess
this
is
the
question
to
like
basha
and
nastia.
How
do
you
think
is
it
feasible
to
create
mock-ups
for
all
other
panels,
or
is
it
too
much?
That's
my
question,
which
one.
E
E
F
E
Sorry
just
my
opinions,
it
would
be
nice
to
draw
everything
and
in
such
case
we
can
see
it
just
before
an
implementation,
and
actually
we
can
compare
it
with
final
implementation
in
such
case
yeah.
It's
just
my
opinion
because
it's
not
so
huge
effort
to
draw
everything,
but
it
will
be
huge
effort
to
re-implement
it
and
so
on.
So
it
would
be
nice
to
see
it
before
implementation,
and
I
know
that.
A
It
might
look
like
if
you
look
at
this
panel,
you
might
think.
Oh,
it's
obvious
how
similar
panel
will
look
like,
but
when
you
try
to
actually
when
you
start
making
these
changes,
then
a
little
like
details
pop
up
and
then
we'll
have
to
you
know
like
a
developer
in
the
middle
of
working
on
a
ticket
we'll
have
to
will
be
blocked.
Then
we'll
have
to
to
try
to
reach
out
to
nasty,
probably
and
ask
questions.
A
E
Can
create
tickets
and
no,
we
can't
I
I
didn't
say
that
we
cannot
start.
I
just
mentioned
that
it
would
be
nice
to
like
before,
implement,
coming
and
coming
panels,
just
draw
them
and
yeah.
E
It
with
community,
I
agree,
it's
not
a
blocker
yeah.
I
think
we
basically
it's.
I
don't
think
it's
a
blocker
too,
and
I
think
it's
most
useful
after
synchronized
panel,
so
it
will
it
it
will
bring
huge
benefit
to
our
to
users,
even
just
after
they
implement
this
panel.
I
think
cool.
A
I
will
just
go
ahead
and
create
ticket
for
for
that
panel
and
then-
and
I
have
a
feeling,
I'm
just
looking
for
an
opportunity
to
add
one
more
item
into
a
roadmap
because,
as
I
said
before,
like
we
wanted
to
give
a
little
bit
more
meat
into
a
roadmap
so
that
people
who
waiting
for
tutor
to
release
you
know
get
more
excited,
they
know
what
is
coming
and
then
I
want
to
basically
create
tickets
for
all
the
panels
and
then
claim
we're
hoping
to
refresh
all
panels
in
in
argo
cd.
A
I
think
we'll
need
to
find
kind
of
a
better
name
in
into
into
world
map,
so
yeah
and
if
we
sleep
we'll
just
move
it
to
the
t
if,
but
hopefully
we'll
we'll
get
it
done
in
2-2
cool.
I
think
it's
yeah
awesome
progress
again
all
right.
We
just
reached
the
end
of
our.
So
it's
already
nine,
like
10
10
10
a.m.
In
my
time
zone
at
least
and
yeah,
we
have
to
wrap
up
all
right.