►
From YouTube: Meshery Development Meeting (Aug 25th 2021)
Description
Meshery Development Meeting - Aug 25th 2021
Join the community at https://layer5.io/community
Find Layer5 on:
GitHub: https://github.com/layer5io
Twitter: https://twitter.com/layer5
LinkedIn: https://www.linkedin.com/company/layer5
Docker Hub: https://hub.docker.com/u/layer5/
A
A
Is
there
any
newcomer
on
this
call?
Who
is
joining
this
call
for
the
first
time
subradio
like?
Did
you
get
a
chance
to
introduce
yourself
before.
C
Yeah
I
have
just
joined.
I
have
introduced
myself
in
the
slack
room
and
I
am
a
student.
I
am
a
final
aerobatic
student
from
iit
medley
in
india.
C
A
You
welcome
welcome
to
the
community.
I
hope
you
will
be
able
to
learn
something
new.
Today
we
have
a
long
list
of
topics
as
well.
A
Oh,
I
don't
think
so.
If
everyone
is
all
people
here
in
the
community
all
right,
let's
started
with
today's
topic.
First
up,
so
basically
I
want
to
point
out
this
document
document
in
measuring
docs,
which
talks
about
the
design
principles
that
are
that
are
taken
into
consideration,
while
building
measuring
and
the
components
surrounding
to
it.
So
basically,
these
are
set
of
guidelines
that
we
expect
everyone
to
follow
to
make
sure
that.
A
We
are
following
the
best
practices
when
we
are
developing
measuring,
so
the
link
to
it
is
in
the
chat.
I
won't
spend
too
much
time
talking
about
it.
You
can
it.
A
A
good
exercise
to
look
into
it
and
try
to
take
up
those
principles
or
keep
those
principles
in
mind
when
you
make
your
next
beer,
so
it
also
has
a
specific,
specific
design
principles
for
each
of
the
components
as
well.
So
you
can
look
at
look
into
that
as
well.
A
All
right
with
that,
let's
move
on
to
yeah.
D
I'll
I'll
toss
in
a
little
bit
of
color
there,
if
I
could,
on
that
last
page
in
particular
the
one
I
think
right
now,
it
might
only
be
on
measuring
cli
on
this
particular
page
that
it
well.
No,
I
guess
it's
not
true.
I
think
I
think
we
talk
about
mostly.
I
think
the
contributor
guides
talk
about
the
mechanics
of
contributing
which
is
like
have
git
installed
on
your
system.
D
Do
you
know
use
this
make
that
build
this.
You
know
this
sort
of
you
know
the
the
procedural
things
by
which
code
or
pictures
or
yaml
or
whatever
you're
you
know,
whatever
you're
contributing
here
or
into
github
is
done.
D
The
the
thing
is:
there's
a
couple:
there's
a
couple
other
things
about
this,
so
so
this
I'm
sorry,
there's
a
couple
of
other
things
about
contributing
that
have
to
do
that
are
softer
than
this
that
aren't
necessarily
procedural
in
nature
per
se
or
they're
harder
to
quantify
in
a
binary
way
or
or
articulate
in
a
binary
way.
So
some
of
it
becomes
well
touchy-feely
or
maybe
a
little
subjective,
but
we
try
to
wrap
some
guidance
around
aspects
of
user
experience.
D
User
experience
ends
up
being
a
bit
touchy-feely,
it's
where
humans
get
involved
and
and
the
code
touches
the
human
and
so.
D
And
so
there's
there's
a
bit
of
a
style
guide
for
the
user
experience,
at
least
on
the
command
line,
and
how
we,
you
know
how
the
cli
and
the
interactions
that
users
have
should
uphold
certain
principles
of
consistency
or
or
other
principles
that
are
articulated
here,
and
so
these
are.
D
You
know
these
require
a
little
bit
of
simmering
if
you
will
a
little
bit
of
percolating,
so
once
you've
read
them
and
then
you've
begun
to
interact
as
a
user
yourself
with
the
cli.
In
this
case,
then
you
begin
to
reflect
on
these
principles
and
understand
whether
or
not
the
current
experience
is
achieving
these
and
whether
or
not
maybe
these
need
to
be
enhanced.
These
contributing
guides
are
living
documents.
Much
like
the
software
itself
is,
and
much
like
the
rest
of
the
docs
are.
D
The
thing
is
is
like
well,
okay,
so
the
cli
is
one
such
client
with
which
users
interface
with
the
project
there's
another
significant
client
that
that
users
use
to
interface
with
meshary.
That's
the
ui
here,
which
is
probably
when
you
think
about
user
experience.
That's
probably
the
first
thing
that
pops
to
mind
is
like.
Oh,
it's
the
ui
right,
it's
the
well,
it's
also
the
cli.
It's
all.
It's
basically
any
client,
and
so
I
don't
think
that
we
have
as
many
we
don't
have
us.
We
have.
D
D
A
set
of
design
principles
for
how
it
is
that,
well
a
little
bit
like
these
design
goals,
they
start
to
become.
They
are
in
essence,
design
principles
so
that
first
one
user
experience
should
be
intuitive
great.
That's
a
great
principle
to
have
and
to
go
after
that.
Very
much
so
is
part
of
the
value
proposition
of
measuring
is
that
people
can
go
off
and
use
these
service
meshes
onto
their
own,
and
so
what
value
is
measuring
providing
well,
it
can
provide
a
ton
of
other
things.
D
Some
of
the
style
guides
are
easier
to
capture
than
others,
like
a
style
guide,
literally
being
like
a
a
color
theme
or
a
design
aspect
of
a
design
language
like
that's
easier
to
you
know,
capture
and
spec
and
by
the
way
there
are
style
guides
both
for
layer
five
as
a
community
there's
a
brand
guide,
that's
in
the
slide
deck
in
the
community
drive
and
then
for
mesh
for
for
the
very
the
six
different
websites
and
for
measuring
itself.
D
There's
a
couple
of
figma
design
files,
I
believe,
is
the
right
term
within
there
it
captures
or
they
capture.
D
You
know
a
variety
of
considerations
and
so
on
anyway,
with
that
as
there's
currently,
I
think
navindu
and
push
and
some
others
are
probably
going
through
something
of
an
audit
of
measuring
of
measuring
ctl
and
its
interactions
and
how
whether
or
not
we're
doing
a
good
job
of
adhering
to
these
conventions,
these
these
style
conventions.
D
So
it's
kind
of
top
of
mind,
and
I
think
that's
why
vendo
is
making
sure
to
highlight
it.
So
it's
a
good
highlight.
A
Yes,
thank
you
lee
so
ashley
mentioned.
I
highlighted
this
because
of
some
ux
inconsistencies
across
measuring
ctl.
So
if
you
find
any
inconsistencies
or
if
you
find
something
unintuitive
imaginary
ctl,
especially
because
we
want
to
make
sure
like
most
probably,
the
cli
would
be
first
thing,
the
user
would
interact
with
as
they
installed
measuring.
So
it
is
pretty
important
to
make
it
intuitive.
So
please
raise
any
bugs
if
you
find
fine,
find
these
all
right.
E
So
yeah
I
can
also
yesterday
the
thing
is
showcased
in
mesh
kit
that
pr
is
still
pending
to
be
merged
the
basically
it
would
not
take
more
than
like
15
to
20
minutes
to
actually
write
that
there's
just
one
single
function
that
is
needed
to
be
written
in
the
westy
adapters,
and
I
wanted
to
actually
ask
there
are
two
ways
to
do
it,
and
I
wanted
to
go
through
these
two
ways
and
if
lee
can
tell
me
which
one
is
better
because
he
is
in
favor
of
persisting
the
components
as
well.
E
So
one
of
the
ways
is
that
actually
right
now
there
is
a
function
in
there
is
a
function
in
this
function,
known
as
I
guess,
register
workload,
something
currently
it
registers
the
static
components
that
are
inside
the
template
directory.
Now
I
was
thinking
about
using
that
that
same
function,
but
what
that
would
require
is
to
actually
dynamically
generate
those
components
to
person
to
actually
store
them
on
file
system,
then
from
there
open
them,
and
then
you
know
this
is
this
two-step
process.
E
So,
instead
of
that,
I
was
thinking
more
more
like
I
can
rewrite
another
function
so
that
you
know
these
static
and
dynamic
things
can
be
completely
separate,
so
we
can
choose
which
functions
to
invoke
at
what
point.
There
is
no
coupling
between
the
two,
so
I
can
write
another
function
which
is
solely
responsible
for
the
dynamic
generation.
It
would
just
fetch
the
components
and
just
reuse
the
that
code
that
wrote.
I
would
just
use
that
bit
where
he
used
the
exponential
backup
to
actually
hit
the
message
server.
E
So
I
would
just
generate
the
components
and
send
those
components
to
the
messy
server
and
then
in
future.
If
you
want
to
persist
it,
we
can
just
add
another
persister
function
and
it's
gonna
spin
it
up
as
a
routine
and
persist.
It
version
it
any
way
we
want.
So
I
was
thinking
to
not
use
the
current
register
function
and
to
write
another
function
so
that
you
know
these
two
things
can
be
separate
and
it
would
not
take.
It
is
just
one
function.
E
It
would
not
take
more
than
15
minutes,
so
I'm
still
waiting
for
that
mesh
kit,
pr
to
be
masked.
So,
as
just
just
like
as
soon
as
it
could
be
merged,
I
will
go
ahead
and
make
a
pr
for
for
the
mystery
or
for
the
easter
adapter.
D
Just
for
my
part
and
others
can
give
feedback
as
well
as
that
sounds
like
a
great
plan
like
I'm
hard
to
pick
any
bones
with
that
one.
For
me,.
D
And
I
think
sohom
is
gonna,
provide
some
context
as
to
what
it
is
that
ashish
is
talking
about
pattern,
components
and
so
he'll
give
a
link.
But
anybody
else
have
a
descent,
a
dissenting
opinion
as
to
what
she
should
how
he
should
proceed.
D
Of
course,
if
there's
any
dissenting
opinions
on
the
call,
that
would
be
heresy,
so
just
keep
it
to
yourself,
but
in
all
seriousness,
yeah,
I'm
that
I
don't
you
know,
I
guess
I'll
just
say
it
again,
like
yeah
great
part
of
what
she's
just
said.
D
Even
if
you
don't
know
what
the
heck
he's
talking
about
is
he
just
said
like
hey,
rather
than
overloading
one
function
with
two
behaviors
he'll
create
two
functions
for
one
for
each
behavior
one
is
to
do
runtime
registration,
the
other
one
is
to
persist
to
do
persistent
registration
if
you
will,
and
so
that
makes
a
ton
of
sense
and
without
explaining
further
good.
I
don't
hear
anybody
suggesting
otherwise.
So.
D
Cool
and
so
she's
been
looking
forward,
is
any
aspect
of
the
run
time
generation
for
pattern
components
right
now.
It
sounds
like
there's
an
open
pr
on
mesh
kit
and
by
the
way,
by
the
way
we
have
a
habit
in
the
community
of
like
interrupting
ourselves
to
explain
things
as
we
talk
about
them,
because
when
I
say
mesh
kit,
I'm
not
going
to
explain
it,
but
rather
I'll
ask
mr
mesherie
maintainer
michael
who
wrote
a
really
nice
blog
post
on
what
mesh
kit
is.
D
F
F
F
Few
of
the
adapters
on
the
console
traffic
and
instant,
we'll
have
to
take
care
of
a
few
things
in
consoles,
so
yeah
I'll
have
to
think
about
that
and
traffic
it
doesn't
use
crds
assets,
so
I
guess
the
configuration
here
will
be
mostly
based
on
labels
and
annotations,
and
I
think
that
will
better
be
great
and
I
don't
know
about
anything
yet
yep.
That's
the
update
on
build
time.
D
At
this
point,
we're
not
just
quick
clarification,
we're
not
leveraging
any
libraries
from
flux
at
this
point.
Are
we.
F
Nope
that
in
build
time
it's
just
scripts,
hacky
bass,
scripts
and
in
runtime
it's
hell,
hell,
libraries
for
extracting
stuff
from
health
charts
and
yeah,
nothing
more!
That's
the
json
schema.
D
It's
just
it's
just
our
it's
just
our
optimistic
code,
probably
a
little
delusional,
but
yeah,
no
flux,
okay,
cool!
D
If
you
would
d,
do
you
get
between
you
and
the
shiat,
and
perhaps
you
guys
could
just
do
a
quick
update
in
that
column
b
or
whatever
column
it
was.
You
don't
have
to
do
it
now,
but
but
cool.
Thank
you.
Nice.
All
right,
that's
great!
Oh
by
the
way
so
on
this
topic
is
shreyas.
Mishra
on
he
might
be,
might
not
be.
D
If
he's
not
someone's
gonna
have
to
tell
him
that
we
talked
about
him
and
then
give
him
some
fomo
for
not
being
on
the
call,
which
is
so.
He
has
an
there's,
an
open
pull
request
from
shreyas
on
mescheri
hyphen
istio
or
on
the
measuring
adapter
for
istio,
and
if
memory
serves.
D
D
I
think
my
my
finger
gets
timid
when
it
reaches
for
the
mouse
button,
just
because
there's
1300
files
in
the
pr
and
so
then
I
my
finger-
gets
weak
and
I
don't
have
the
strength
to
click,
merge
so
rudrox.
If
you
could
do
that,
that
would
be
great.
That
way
we
can.
We
can
blame
you
for
if
anything
goes
wrong,
but
the
the
point
here
is
that
what
what's
going
on
what
treyas
has
done
is
he's.
In
effect
with
this
pull
request,
he
has
added
mescheri's
support
for.
D
What
I
don't
know
for
a
long
list
of
versions
of
istio,
so
istio
is,
I
think,
in
its
1.10
1.11ish
range,
for
you
know,
of
its
current
release.
But
you
know,
just
like
any
software
project
has
had
any
number
of
releases,
starting
from
you
know,
0.1
to
all
the
way
until
what
it
is,
and
so
when
people
come
through
part
of
you
know,
mescheri's
task.
D
It's
responsibility,
the
the
cross
that
it
bears
as
management
software,
as
any
management
software
does,
is
sustaining
and
carrying
a
a
compatibility
matrix,
which
is
to
say
that
mesh
is
compatible
with
10
different
service
meshes
today.
Maybe
it'll
be
an
11th
with
nginx
soon,
maybe,
but
but
how
many
versions
of
each
of
those
service
meshes?
Does
measure
support?
D
They
only
go
so
far
as
three
versions
back
and
depending
on
how
they
want
to
phrase
it.
They
might
say
four,
that's
it
and
you
gotta
pay
for
that
stuff.
D
I
wow
that's
impressive,
yeah.
D
D
A
Moving
on
to
the
next
topic,
would
you
like
to
talk
about
the
changes
in
the
navigation
menu.
G
G
Okay,
so
the
issue
was
here:
there
is
a
navigator
on
the
side
menu
as
a
side
menu.
So
when
we
were
collapsing
the
navigator,
all
the
categories,
sub
categories
under
the
categories
were
expanded
and
it
actually
pushes
down
the
chevron
menu
to
the
very
bottom,
and
you
have
to
scroll
to
that
and
the
task
was
to
you
know,
make
that
subcategories
under
the
categories
as
a
not
non
expanded
menu.
So.
D
Sorry
so
sorry
to
interrupt
us
actually
it'll
be
if
we're
gonna
actually
talk
about
this.
We're
gonna
actually
talk
about
this
and
try
to
work
it
out.
It'll
be
so
much
more
conducive
to
doing
so.
If
you're
able
to
share
an
active
interface,
otherwise
we'll
try
to
watch
the
videos
a
bunch
of
times
and.
D
G
G
D
I
don't
sweat
it
in
the
least
as
a
matter
of
fact.
Let
me
let
me
here
here:
I've
got
one
here.
D
G
All
the
subcategories
will
be
shown,
and
after
implementing
that
we
were
actually
discussing
if
it
should
be
same
like
when
on
the
menu
bar
is
not
collapsed
like
in
the
expanded
view
like
whenever
we
are
clicking
the
expand
more,
we
will
do
the
hover
effect
instead,
but
as
lee
suggested
that
it
should
not
be
done
like
it
was
okay
for
when
it
was
the
menu
bar
was
collapsed,
but
when
it
is
expanded,
I
think
lee
wasn't
not
approving
the
changes
to
implement
the
hover
effect
in
in
expanded
view.
D
That'd
be
great
yeah,
please
so
so
by
the
way.
So
here
very
briefly,
I'm
going
to
do
this
and
then
we'll
switch
to
adidas,
which
is
so
today.
Today
we
were
just
kind
of
looking
at
the
experience
which
so
there's
the
whole
collapsed
kind
of
issue,
but
but
the
uncollapsed
or
the
expanded
form-
I
is
just
just,
looks
like
this
and
and
has
already
well
cipher
girl.
D
B
Yeah,
so
this
is
what
it's
doing
right
now
yeah,
so
she
I
think,
like
she
also
made
changes
to
it
when
the
drawer
was
open,
but
she
hasn't
committed
that
so
right
now
it's
like
this,
but
the
behavior
would
be
like
it
would
open
up
on
hover,
even
when
it's
opened
up.
So
this
is
what's
happening
right
now,.
B
D
Oh
cool,
yeah
and
yeah
we
do.
We
do
probably
want
for
the
interactions
to
be
somewhat
consistent,
that
if
on
hover
during
collapse
by
the
way
it
hasn't
just
for
a
moment,
if
you
don't
mind,
muting
the
there's,
a
feedback
loop
on
your
mic,
which
I
think
is
made
okay
and-
and
we
want
to
be
consistent
like
just
don't
don't
make
me
talk
about
consistency
and
quality.
D
D
You
know
either
can
potentially
work
like
on
hover.
You
just
you
know,
expand
to
let
people
see.
What's
underneath,
I
think
the
beef
the
bone
that
I
was
attempting
to
pick
but
ran
out
of
time
late
last
night
to
articulate
with
my
fingers
was
that
in
the
this
this
is
the
current.
These
are
the
current
proposed
changes.
B
Also,
she
hasn't
committed
the
ones
where
even
these
ex,
like
these
expand
on
hover.
So
we
are
planning
for
that
too.
D
D
There's
a
lot
to
talk
about
in
that
interaction,
and
some
of
you
are
thinking
I'm
nuts
for
saying
that
you're,
like
you're
nuts,
you
just
hover
over
the
thing
and
you
click
the
thing
like
what
I
don't.
How
could
you
go
on
for
about
45
minutes
on,
like
and
and
like?
It
is
about
a
30-minute
discussion
where
you,
because
there's
a
bunch
of
scenarios
of
you're
collapsed
or
you're
not,
and
so
you
have
a
bunch
of
scenarios
within
those
two
environments,
you're
choosing
either
to
auto,
expand
or
not
to
the.
D
I
think
the
to
be
concise.
The
biggest
beef
that
I
probably
had
with
the
latest
proposed
changes
in
the
last
screen.
Recording
on
that
pr
was
the
fact
that
we
were
auto
not
only
auto
expanding
but
also
auto,
closing
as
people
nabbed
away
and
what
happens
is
people
lose
their
frame
of
reference
they
might
open
up
so
that
yeah?
That's
that's
fun,
but
can
you
stop
stop
for
just
a
moment?
So
when
you,
when
you
can
you
navigate
to
one
of
those
service,
meshes.
D
And
this
isn't
the
latest,
but
if
you
were
to
click
on
one
of
these,
so
you're
sitting
here
well,
what
was
happening
in
the
the
latest.
Our
proposal
is
that
the
user
would
open
the
accordion.
They
would
choose
a
mesh
then
when
they
navigate
away
it
would
close
on
them
and
without
cookie
crumbs
or
something
else.
It's
kind
of
like
when
you
walk
into
a
building
and
the
door
closes
behind
you
that's
a
bad
analogy.
D
It's
like
you
get
off
the
airplane
and
you
you
get
out
of
the
taxi
cab
and
you
weren't.
Looking
around,
you
were
looking
at
your
phone.
You
stepped
out
of
the
taxicab
like
fudge.
Where
am
I
you're
not
sure
which
way
is
north
and
which
way
like
you
lose
your
total
frame
of
reference,
because
what
you
did
was
just
you
took
away
the
map.
You
took
away
the
cookie
crumb,
so
that's
probably
the
biggest
thing
to
take
a
look
at
in
the
last
proposed
thing.
D
E
What
a
hello!
So
what
if
we
can
expand
like
when
we
are
on
the
collapse
like
collapse
door?
So
when
we
click
once
on
any
parent
item,
it
will
expand
the
items
and
on
the
second
click
it
will
actually
go
to
the
life
cycle.
So
that
looks
good
like
if
you
have.
E
If
you
have
collapsed
menu,
then
the
draw,
then
everything
will
be
collapsed
initially
in
the
very
initial
state,
then,
when
we
click
first
on
any
parent
icon,
that
is
dashboard,
lifecycle
or
configuration
or
performance,
then
it
will
just
expand
it
for
the
first
time,
then,
if
again,
any
equipment
occurs
on
lifecycle,
it
will
just
go
to
the
lifecycle
url
or
if
the
the
children's
are
already
expanded
by
clicking
once
then,
any
further
click
on
any
children
item
will
get
back
to
that
url
because
yeah
yeah.
D
Yeah
I
mean
yeah.
That
makes
I
hear
what
you're
saying
yeah.
Actually
you
bring
up
a
good
set
of
discussions
around
the
notion
that
the
parent
menu
item-
sometimes
it
performs
the
the
function
of
just
being
a
category
and
like
it
itself,
is
not
something
to
click
on
and
navigate
to,
but
it
is
just
organizing
submenu
items
while
other
times
that
parent
menu
item
in
fact
is
navigable
itself,
and
so
that
becomes
computer
and
so
that's
a
whole
and
so
yeah.
E
E
So
here's
the
right
so
just
like
us,
this
is
the
collapsible
menu
and
when
we
go
like
when
we
collapse
the
door,
so
everything
just
get
expanded,
all
the
icons,
everything
and
they
are
separated
out
by
dividers.
So
we
can
also
take
you
know
reference
from
there.
E
So
yeah
there
is
something
and
it's
collapsible
and
when
we
go
back,
everything
is
just
expanded
and
all
the
items
are
divided
by
your
divider.
Like
the
horizontal
row.
H
D
Wonderful,
I
love
seeing
the
references
to
other
prior.
You
know
pieces
of
work.
That's
because
many
other
people
have
had
to
sit
here
and
chew
through
all
the
same
considerations
and
try
to
get
it
right,
and
maybe
they
got
it
just
perfect.
Maybe
we
need
to
augment
what
they've
done
or
maybe
we
need
to
take
anti-inspiration.
D
But
my
request
here
is
actually,
if
hasanah
abi
aditya,
would
you
mind
huddling
with
sohom
and
iterating
a
little
bit
and
then
and
then
coming
back.
H
Just
to
add
to
that,
like
what
someone
said
that
the
issue
was
to
issue
was
that,
like
some,
I
mean
like
clicking
on
life
cycle,
would
take
you
to
a
different
page
and
clicking
on
the
html.
It
should
take
you
to
every
different
page
right.
So
that's
basically
a
problem
with
the
routes
management
that
we
have
and
yeah
that
that
is
something
that
is
different
from
the
navigation
thing
person.
So.
H
H
A
H
So
like,
we
actually
currently
have
a
problem
with
the
measuring
ui
dev
server,
which
which
is
actually
listening
at
localhost,
3000
and
coincidentally,
like
defron,
is
also
listening
at
localhost.
D
H
So
when
you
are
to
run
machine,
ui
and
then
measuring
server
and
then
refine
at
the
same
time,
then
I
mean
like
one
of
one
of
either
of
those
like
any
one
of
those
two
will
not
be
able
to
run
because
oneplus
would
already
be
occupied
by
either
so
so
I
was
thinking
whether
we
could
change
it
to
a
different
board
like
for
the
anyways
like
we
couldn't
change
the
port
of
grafana.
So
I
thought
we
could
change
the
boat
of
the
development
server
to
something
else
like
three
zero
one.
H
Build
version:
it's
just
something:
it's
just
a
change
in
the
development
server,
so
we
need
not
think
about
it.
Much.
D
One
other
quick
heads
up
or
something
to
think
about
is
the
notion
that
the
provider
ui,
if
the
developer
so
happens,
to
run
that
separately,
which
I
was
last
night
as
I
was
checking
out
barracks
stuff
by
default.
It
runs
on
3001
and
so
potential
conflict
with
the
3001.
But
but
that
brings
up
another
question
like
do
we
do
we
have
a
make
command
that
will
run
both
measure
ui
and
the
provider
ui
under
the
same
port
for
development
like
a
development
command.
H
At
the
same
port,
I
mean
like
those
both
are
different
projects
in
itself.
Right
so.
H
Yeah,
that's
actually
because
they
are
built
and
then
served
by
measuring
server
right.
So
in
that
case,
it's
a
totally
different
scenario.
In
that
case,.
D
A
H
A
All
right
moving
on,
thank
you
midish.
So
we
have
a
couple
of
design
specs.
That
needs
needs
to
be
reviewed,
so
we
have
three
that's
on
the
line
right
now
so
drew.
Do
you
want
to
give
a
quick
idea
about
what
this
pack
is?
F
Currently,
basically,
a
sub
dynamically
updates,
your
data
and
currently,
if
we
have
more
than
one
subs,
which
uses
the
same
trigger
to
say
that
we
have
to
update
the
data,
not
all
of
them
would
be
sending
the
updated
data.
This
design
spec
basically
has
a
work
around
in
that
where,
instead
of
using
channels,
you
will
implement
something
of
a
broadcasting
where
every
trigger
will
receive
the
particular
signal,
update
the
data
and
send
it
back.
So
that's
a
very
brief
gist
of
it.
D
F
D
D
If
you
please
feel
empowered
to
rewrite
where
the
question
marks
are
under
the
scenarios
to
just
rewrite
it
as
a
statement
of
truth
of
like
oh
okay,
I
guess
you
did
but,
but
maybe
if
you
have
then
delete
the
question
mark
like
try
to
make
that
question
mark
into
a
statement
or
change
it
to
the
correct
statement,
if
you
would
also
if
those
scenarios
aren't
yeah
yeah.
No
that's
great.
Please
do.
A
Thank
you
dru,
so
anybody
anyone
else
have
comments
on
this
spec.
So
the
link
to
this
package
in
chat.
You
can
add
your
comments
there
and
look
into
it
in
detail.
A
So
the
another
spec
here
is
to
package
basically
have
seed
content
for
patterns
filters
and
applications.
So
this
talks
about
measuring
being
an
artifact
repository
for
these
service
mesh
patterns.
So
when
users
first
start
measuring,
they
will
have
some
seed
content
with
some
sample
patterns
that
they
can
readily
deploy.
A
So
this
specs
talks
about
that,
and
this
needs
a
couple
of
more
iterations.
I
guess
so
I'll
share
the
link
in
chat
and
you
can
check
it
out
any
suggestions
you
have
and
the
final
specs
spectra
talks
about
state
management
in
measuring
ui
nadesh.
Would
you
like
to
give
a
quick
overview
of
what
this
pack
is.
H
Yeah
so,
basically
like
we
have
some
problems
with
like.
Currently,
the
state
management
in
measuring
ui,
like
react,
is
managing
all
the
states
now,
and
this
is
not
something
which
is
which
should
be
scalable
like
if
we
are
going
to
move
forward
and
and
yeah.
So
basically,
some
of
the
problems
related
to
the
state
management
and
the
cash
and
all
those
stuff
are
being
addressed
in
this
proposal
and
the
proposal.
D
H
Basically,
to
bring
in
redex
and
some
other
medieval
middle
class
as
well.
So
if
you
want
to
take
a
deep
look
into
it,
you
can
just
go
to
the
proposal
and
add
your
views
on
views
all
and
as
well.
So
it's
it's
kind
of
in
the
final
stage
right
now
and
they
would
be
pushing
to
implement
this
thing.
But
still
we
have
some
unresolved
comments
and
we
are
working
on
it
right
now.
A
A
So
right
next
up
we
have
do
you
want
to
talk
about
the
center
theme
for
measuring
ui.
B
B
So
what
material
ui
allows
us
to
centrally
define
is
only
a
single
primary
color,
with
a
lighter
version
of
that
and
a
darker
version
of
that,
and
we
cannot
just
use
them
anywhere.
We
want
directly.
B
It
auto
adjusts
itself
unless
we
override
the
css
of
course,
so
the
the
thing
is
that
we
need
to
narrow
down
the
set
of
to
basically
a
single
primary
color
and
lighter
version
that
machi
can
that
it
a
material
ui
should
automatically
take.
B
B
D
Yeah
and
if
you
go
back
to
figma
for
a
moment
there
is
I'm
not
telling
you
anything
that
you
don't
know,
but,
but
so
there
is
this
set
of
colors
and
then
there's
also
a
second
set
of
colors
specific
to
notifications.
B
D
Okay
and
so,
which
you
know,
which
works
out
well
with
respect
to
the
predefined
set
of
colors
for
notifications,
so
that
that's
good,
so
the
existing
theme
has
placeholders
for
our
notification
colors.
D
D
B
Yeah
the
first
one
was
this
blue
gray.
It's
almost
similar
to
this
color
right,
but
not
not
exactly,
but
you
cannot
make
out
the
difference.
Yeah
right.
B
Yeah,
the
one
problem
with
secondary
is
that
this
is
a
red,
and
this
is
black
and
we
are
just
using
them
any
way.
We
want
it
not
basically
following
any
convention
right.
D
D
By
the
way,
if
this
is
anyone
else's
area,
like
forte
area
like
if
anyone
else
is
skilled
in
theming
or
like,
please
sound
off
and
chat,
this
is.
B
So
most
of
the
components
we
directly
pass,
a
property
called
color
equals
to
primary
secondary,
and
if
we
try
to
pass
anything
else
that
we
define
here,
let's
tertiary,
it
doesn't
take
it
automatically.
So
what
what
we
need
to
do?
What
would
what
we
have
to
do
then,
is
basically
in
either
create
a
central
component
for
this
button,
or
in
this
page
you
we
override
the
css
here
of
that
button
right
by
importing
that
you
know
theme,
of
course,
but
we
cannot
use
them
directly.
D
That's
we
that
seems
weird
to
me,
like
the
the
the
string
primary
and
the
string
secondary.
If
you
were
to
pass
it
a
string
of
disneyland
or
like
tertiary,
why
is
that
not
variabilized
like?
Why
is
that
not.
D
Using
this
particular
component
as
an
example
like,
if
yeah,
I
guess,
if
you
go
to
the
source
component
like
the
source
button
component
or
something
that
comes
from
material,
you
are
oh,
yes
does
there,
it
would
seem
the
weirdest
thing
that
there's
hard-coded
strings
primary
and
secondary,
like
certainly
they're
hard-coded
into
the
theme
and
that's
what's
defined
in
the
theme.
If
we
take
and
extend
the
theme,
though,
and
add
a
third
color
set,
the
fact
that
you
can't
dynamically
provide
that
it
doesn't
dynamically.
D
D
H
Yeah,
actually,
I
think
there
might
be
a
reason
behind
that
because,
like
they
are
trying
to
enforce
like
they're
trying
to
make
it
like
a
design
language
in
the
sense,
so
that
might
be
the
reason
behind
that,
but
actually
they
give
us
a
lot
of
flexibility
over
how
to
customize
these
components
still.
So
if
we
are
not
able
to
do
it
that
way,
then
they
are
providing
us
some
other
apis
as
well.
D
D
D
D
I
mean
another
potential
approach
like
as
a
question
if
you
go
back
to
the
theme
so
so
similar
to
the
notification
colors
that
they
have
that
that
material
ui
defines
it's
like
here's
success,
but
success
with
like
two
or
three
lighter
shades
of
success
or
different.
Like
there's
the
palette
that
info
dot
light
palette
info
dot
main
palette
dark.
Can
there
also
be
a
palette
dot
info
dot,
neon.
B
H
Yeah,
I
feel
the
same
way
as
well,
because,
like
the
library
being
the
like,
I
mean
like
a
lot
of
people,
are
using
this
library
and
they
won't
be
using
it.
If
not,
it
is
capable
of
doing
like
it's
not
capable
of
referencing
we're
not
able
to
reference
the
theme
from
a
global
level
right.
B
Yeah
we
can
reference
the
theme
but,
like
this
theme,
dot
palette,
but
we
cannot
use
them
in
as
a
prof
to
a
component.
That's
the
problem.
We
can.
F
So
like
what's
wrong
with
using
theme.
background
like
we
can,
we
can
centralize
the
color
scheme
itself
in
the
theme
and
then,
if
for
primary
secondary,
let
them
be
as
it
is,
and
if
we
want
to
tweak
a
tweak
it
a
bit,
we
can
use
the
theme
specified
colors,
which
we
already
have
to
change.
That
makes
sense
right.
D
D
B
There's
nothing
wrong
with
that.
I
I.
The
only
thing
I
wanted
was
that
the
prime
we,
when
you're,
using
all
the
things
for
buttons
and
all
we
just
need
one
color
for
primary
and
a
lighter
and
a
darker
shade,
and
if
we
want
all
the
other
colors,
we
can
override
the
css.
D
Oh
okay,
wait.
Let
me
regurgitate
that
back
to
you.
So
is
it
okay,
so
understanding
that
we
can
have
well
so
the
accent
and
the
let's
say
that
that
last
one
was
just
called
black
within
each
of
the
four
rows
of
color.
D
I
think
you're,
saying
hey,
you
can
conveniently
have
up
to
two
colors
within
each
group.
You
can
extend
it
to
all
of
them,
but
that's
gonna.
You
know,
that's
gonna
make
it
it's
gonna,
be
even
harder.
So
conveniently
you
could
have
two
in
each
group
and
is
the
limitation.
The
number
of
groups
that
you
can
have
like.
B
B
We
will
have
to
in
that
component
we
have
to.
It
will
be
like
for
that
button
over
at
the
css
as
background
color
equals
to
theme,
dot,
palette,
dot,
accent,
dot,
teal,
blue.
D
I'm
I'm
convinced
I'm
still
slightly
confused
as
to
how
to
give
the
best
guidance.
I
do
know
that
it
is
okay
if
we
only
have
one
color
in
each
of
those
groups,
if
it's
convenient
enough
for
us
to
have
50
groups
without
having
to
do
a
lot
of
rigmarole,
like
that's
another
way
of
achieving
any
number
of
colors
that
you
want
and
yeah,
we.
D
F
Material
ui,
we
can
define
the
the
variation
of
the
color
like
blue
203
under
so
when
you
are
custom,
defining
the
theme
which
you
already
have.
It
is
basically
different
variation
of
the
same
color.
So
can
we
define
it
in
an
array
form?
I
think
that
might
be
a
better
idea.
B
Yeah
that
can
be
done.
The
the
only
drawback
I
mentioned
was
that
you
cannot
use
that
as
a
prop.
B
B
D
Oh
oman,
I
just
saying
your
name
out
loud
just
in
case
you
have
an
opinion
where
zane
is.
E
Yes,
even
I
have
also
faced
similar
issues
in
the
past,
because
material
ui
in
the
code
generally
prefers
only
two
colors
like
primary
and
secondary
and
as
he
mentioned
it
in
primary,
only
two
extra
shades
can
be
given.
So
we
could
even
do
two
ways
possible.
One
would
be
to
limit
to
change
the
color
variation
defined
in
the
sigma
file
to
only
two
like
in
the
primary
section.
We
define
only
three
colors
in
the
secondary
section.
E
D
Okay,
yeah,
I
think
the
the
problem
to.
I
think
that
the
problem
statement
is
that
that
we
have
a
set
of.
We
have
four
color
groups.
There
are
many
shades
within
those
color
groups.
We
probably
don't
need
to
use
all
the
shades
that
like
if
we
were
able
like
if
we
were
able
to
achieve
four
color
groups
with
two
colors,
a
piece.
D
E
Like
if
you're
talking
about
the
theming
part,
then
yes
in
material
ui,
we
can
have
a
as
a
drop
down.
We
can
have
multiple
theme,
like
light
themed,
dark
theme
and
a
medium
theme,
but
in
all
those
theme
we
have
to
define,
we
can
define
primary
colors
differently.
Like
the
for
dark
theme.
Primary
color
might
be
different
and
for
us
live
team
it
might
be
different,
but
in
both
cases
it
would
be
good
if
we
can
define
only
three
shades
of
primary
colors
and
three
shades
of
secondary
color.
E
So
are
we
open
to
change
those
six
seven
colors
into
two
or
three.
D
Yeah
I
mean
from
from
my
perspective
like
if,
if
the,
if,
if
in
our
theme,
we
said
primary
and
then
we
had
pink
and
it
had
the
color
for
the
hex
code
for
pink
and
then
we
had
yellow
and
yellow
and
red,
and
it
was
like
totally
messed
up
and
not
like
random,
just
like
all
the
like.
D
While
that's
somewhat
perverse,
and
not
necessarily
maybe
the
intention
that
they
were
going
for,
it
still
achieves
the
goal
of
not
having
to
write
a
bunch
of
extra
code
but
also
being
able
to
reference
charcoal
keppel
and
teal
blue.
All
in
one
like
primary.kappleprimary.tealprimary.blackprimary.charcoal.
D
And
then
in
secondary
it
can
be
the
so
like
in
primary.
It
would
be
primary.charcoal
and
you'd
get
the
first.
The
leftmost
box
that
says
charcoal
primary.keppel
would
be
the
left
most
box
like
it
for
all
four
of
those
and
then
on
the
secondary
color
theme.
It
might
be
the
see
the
it
might
be,
the
the
square,
that's
just
to
the
right,
or
something
like
that,
like
that,
that's,
like
eight
colors,
that's
quite
a
bit
and
that's
you
know.
B
The
approach
that
you
suggested
is
possible,
but
then
again
you
will
have
to
override
the
css
in
that
manner,
because,
okay,
it
has
to
be
either.
There
has
to
be
a
primary
color,
a
single
primary
color
and
a
shade
of
light
and
a
dark,
and
this
light
and
dark
it
automatically
picks
up,
and
we
cannot
just
pass
it
as
a
prof
like
primary
dot,
yellow.
We
cannot
pass
this
as
a
prop.
D
Okay,
cool
I'll
withhold,
I
am
we're
over
time
and
and
it
sounds
like
there's
not
a
readily
yeah.
Can
you
guys
do
this?
Do
you
mind
just
writing
down
making
the
best
proposal
that
you
think
that
you
can
to
achieve
two
things?
It
sounds
like
the
ability
to
allow
a
user
to
switch
between
themes
is
pretty
routine
and
that's
fairly.
D
You
know,
but
then
the
second
proposal
is
like
hey
here's,
how
many
colors
we
think
that
we
could
get
to
and
and
it's
okay,
if
we
can't
get
to
it
within
in
an
easy
way
like
it's.
Okay,
if
we
only
get
to
one
of
each
of
those
four
groups
or
two
of
each
of
those
four
groups.
B
D
Rudraksha
the
sounds
like
you
were:
gonna
go,
get
potentially
busy
on
the
nginx
adapter
and,
if
you
would,
I
think
near
as
I
can
tell
jared
is
well.
He
said
it
a
few
times
now
he's
like
hey,
put
me
to
work,
which
that's
always
so
so
do
it.
F
D
Great
nice,
it's
very
nice
to
talk
to
you
all.
The
venue
take
bring
us
home.
A
Thank
you
for
joining
everyone
and
staying
so
late,
we'll
see
you
tomorrow
or
friday
or
next
week.
Bye.