►
From YouTube: Meshery Development Meeting (June 30th, 2021)
Description
Meshery Development Meeting - June 30th, 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
Welcome
everyone:
this
is
the
mashery
development
meeting
and
today
is
30th
of
june,
and
before
we
start
with
the
topics,
I'd
like
to
mention
that
we
have
moved
our
the
measuring
organ,
the
some
of
the
machinery
projects
and
service
mesh
performance
projects
into
a
new
github
organization-
and
this
is
in
relation
with
mashiri
being
being
a
cncs
sandbox
project.
A
So
the
the
measuring
project
has
not
been
moved
yet,
but
it
will
be
moved
shortly
and
many
of
you
guys
have
have
been
working
on
some
of
these
projects
that
have
been
moved.
So
it's
in
a
new
organization
and
yeah.
If
you
feel
like
you,
you
lost
some
of
the
some
of
your
permissions
that
you
had
before,
like
just
let
me
know,
and
there
might
be
some
issues
with
the
with
moving
things
around
so
yeah
and
we
also
moved
the
smp
the
service
match
performance
repo.
A
Similarly,
and
before
we
go
to
the
items,
I
think
we
have
a
couple
of
newcomers
on
the
call
today,
I'm
not
sure
aditya
chatterjee.
Is
this
your
first
time
on
discord
yeah?
This
is
my
first
call.
I.
C
Yeah
sure
hi
everyone-
I
am
aditya
chatterjee,
I'm
a
cs.
A
D
Awesome
awesome:
yeah
did
you
say
you're
already
you're
already
working
on
an
issue.
Yeah.
B
D
Beautiful
you've
made
yourself
right
at
home.
That's
wonderful!.
A
A
Yourself,
if
you,
if
you
have
having
mic
problems,
then
you
can
introduce
yourself
on
on
the.
A
Okay,
if
you
are
okay,
okay,
so
kanwal
is
having
some
mic
issues.
He
will
introduce
himself
on
chat.
So
are
there
anybody
else?
Who
is
new
on
this
call.
A
So,
first
of
all
welcome
welcome
to
you
guys
we
we,
we
have
some
interesting
projects
here,
and
we
also
have
a
new
commerce
call
that's
happening
tomorrow.
So
it
would
benefit
you
if
you
would
jump
onto
the
card
and
yeah
you'll
be
introduced
to
all
the
layer,
5
projects
and
how
you
can
start
contributing.
A
A
Thank
you
guys
welcome,
welcome
again,
and
we
will
move
on
to
the
agenda
agendas
for
today,
and
we
also
have
some
open
prs
that
needs
to
be
reviewed,
so
one
of
which
is
push
spr
for
unit
test
in
measuring
ctm.
A
G
E
So
it
should
work
now,
yeah,
okay,
so
if
you
go
into
the
agenda,
you
can
see
total
request,
link
there
and
that
are
about
error
code,
utility
merging
them
into
ci.
If
you
don't
know
about
error,
votes
utility
was
something
made
by
michael
to
analyze,
error
codes
in
various
repositories
and
which
could
be
used
to
update
a
reference
at
the
site,
the
layer,
5
mystery
talks
and
basically
the
site
and
to
perform
checks
in
pr,
so
integrating
it
into
ci,
and
this
is
the
one
for
mystery
server
and
messaging
ctl
right
now.
E
E
E
E
E
D
Let
me
ask
you
real
quick,
the
anchor
link
for
which,
which
components.
D
Yeah
yeah
there's
a
couple
yeah
okay,
so
so
this
documentation
is
like
you
know,
I'm
saying
it's
for
everyone
else's
benefit,
but
that
the
documentation
is
auto-generated
and
there's
a
and
between
the
auto-generated
docs
and
making
them
legible
a
little
bit
of
a
challenge,
because
there's
a
lack
of
white
space
in
certain
areas
like
the
component
names
or
there's
been
like
camel
casing
versus
other
types
of
casing,
and
so
I
don't
know
that
that
so
I
think
that's
part
of
our
issue,
something
like
mesh
kit
like
technically
the
k
and
mesh
kit
should
be
capitalized
and
in
the
mashery
adapter
library.
D
Those
are
three
individual
words,
all
of
which
should
have
their
own
capitalization
with
no
hyphenation
between
and
so
but
the
anchor
that
would
be
used
for
any
of
those.
Like
the
eight
the
anchor
tag
it
doesn't
support,
white
space
and
so
like.
I
think
those
are
the
small
snafus
that
are
happening
in
the
page
itself.
D
Those
things
are
definitely
solvable
within
the
docs,
so
actually
anyone
who's
on
the
call
who
fancies
themselves,
you
know
handy
with
html.
This
is
well.
This
is
a
challenge
that
will
get
you
into
working
a
little
bit
with
liquid
in
jekyll
or
not
in
jekyll,
but
liquid
as
a
gosh.
I
guess
a
templating
language,
that's
used
by
the
jekyll
framework,
so
it's
ruby.
E
E
D
So
rude
rocks
one
thing
that
I
don't
know
so
there's
a
couple
of
things
about
what's
being
done
here.
First
of
all,
it's
fantastic
that
we
are
automatically
generating
error
codes.
They
become
extremely
useful
for
people
to
just
do
a
google
search
on
and
then
come
to
understand
what
their
issue
is.
It's
really
helpful.
D
And
michael
and
abhishek
and
yourself
and
a
few
others
have
been
involved,
there's
been
a
recent
call
for
volunteers,
especially
for
those
who
are
somewhat
new
to
go
to
help
make
this
new
f
framework
for
error
code,
for
the
way
that
we
publish
error
codes
if
you're
on
the
call
you're
either
looking
for
something
to
do
new
to
golang
or
very
old,
at
golang,
very
experienced
with
golang,
rather
either
way.
D
This
is
a
good
thing
for
you
to
jump
into
is
to
in
measuring
server
itself
in
the
server
code
to
swap
out
old
references
like
with
new
ones
and
there's
instructions
specifically
for
how
to
do
that,
and
redox
is
showing
that
here.
D
So
if
you,
if
all
you
got
just
now,
was
hey
if
you're
a
newbie
to
golang,
there's
something
for
you
to
do
great.
Look
to
the
meeting
minutes
as
rudraksha
updates
those
with
this
link,
and
you
can
dig
in
there's
a
number
of
easier
to
grasp
issues
around
the
autumn,
auto
documentation
of
errors
and
measuring
something.
That's
that
we've
covered
this
topic
quite
a
bit
in
prior
meeting
minutes,
and
so
all
of
those
meetings
are
recorded
and
posted
on
youtube.
So
you
can
definitely
watch
them
there.
E
E
D
Yeah,
that's
awesome
and
then
the
the
really
neat
thing
about
this
too,
that
we
we
do
this
in
some
areas,
but
not
a
lot,
and
that
is
this.
Workflow
will
actually
be
making
a
commit,
get
a
get
commit
and
get
push
in
to
a
different
repo
to
the
mystery
repo.
So
it'll
be
an
auto
documenting
system.
It'll
be
an
auto
error
code
generating
system
that
also
then
auto
documents
in
a
distributed.
Repo
way.
E
D
So
that's
that's
awesome.
You
tend
to
think
of
distributed
systems,
as
you
know,
active
processes
that
are
running
geographically
and
geographically
distributed
areas
and
that
you
know
and
and
all
of
the
challenges
that
comes
with
that.
But
some
of
the
challenges
that
come
with,
like
developing
micro
services,
we're
seeing
right
here,
mesherie
as
a
project,
is
a
collection
of
microservices.
D
D
There
are
other
components:
the
adapters
and
the
operators,
the
custom
controllers,
mesh
sync
and
things
those
are
in
different
repositories,
keeping
them
all
in
sync
is
in
part
what
rudraksha
is
showing
here
so
distributed.
E
Another
thing
that
I
had
in
mind
is:
can
we
have
some
sort
of
separate
page
for
adapters
like
there'll,
be
too
many
of
them,
and
it
would
make
this
page
a
little
bigger
but
yeah?
That's
exactly
why
we
have
connect
and
never
mind.
D
Yeah
I
mean
yeah,
it
kind
of
it's
a
good
tbd.
I
get
time
will
tell
probably
yeah
yeah.
H
D
B
B
Yeah,
so
I
was
working
on
the
teacher,
the
user
handler,
so
I
did
something
different
like
I.
I
think
the
previous
speaker
already
told
about
the
part.
But
if
you
ask
me
like
how
did
I
do
like?
B
I
did
some
changes
like
I
first
get
into
this
error
like
what
was
the
error
about,
and
then
I
read
about
this
error,
and
then
I
found
that
what
should
be
the
specific
name
like
it
was
written
in
that
michael
has
already
told
something
about
how
to
name
the
errors.
So
in
that
way
I
have
just
named
the
error
so
like.
B
Foreign
and
then
I
I
have
passed
an
object
like
different
errors,
have
got
different
types
of
objects
like
error,
I'm
not
selling
the
payloads
or
something
of
that
sort.
So
I'm
just
use
that
as
an
object
and
pass
it
as
both
of
the
parameters
like
an
error
and
an
object.
B
B
The
first
one
is
about
the
code.
What
was
actually
the
code
of
the
error?
Then
there
is
an
error,
dot,
alert
and
then
the
third
one
was
about
the
short
description.
The
fourth
one
was
about
the
long
description
and
then
that
another
one
was
about
the
item.
B
That
was
the
four
parameters
we
needed
to
pass
and,
after
our
word,
we
drew
by
learning
that
we
shouldn't
give
full
stop
on
the
last
stream,
and
in
this
long
description
we
should
only
pass
the
error,
dot
education.
D
This
is
great.
This
is
a
great
example
of
exactly
what
we
were
just
talking
about
about
people
jumping
in
and
helping
be
rid
of
the
old
style,
error,
logging
and
doing
the
new
style,
which
is
a
lot
more
robust
and
dynamic,
and
so
this
is
an
appropriate
moment
to
pause
and
ask:
is
this?
I
Lee
I
would
also
like
to
help
out.
I
I've
said
this
before,
but
I
I
will
do
it
start
doing
some
of
the
stuff.
A
Today,
I
also
think
like
khao
zambi
would
also
like
to
jump
in
right.
He
mentioned
on.
A
A
H
A
G
A
So
the
pr
is
already
up
on
this,
but
unfortunately
I
won't
be
able
to
show
a
dockerized
demo
because
I'm
unable
to
merge
it.
However,
I
can
show
you
a
local
demo.
A
Basically
I
can
run
the
machine
operator
loop,
and
so
what
the
pr
is
about
is
that,
when
measuring
operator
is
deployed
in
the
cluster,
it
spins
up
two
controllers,
which
are
mesh
sync
and
meshri
broker,
and
basically
the
feature
that
I
added
is
that
when
machine
operator
is
killed
or
when
it
is
stopped
it,
it
also
removes
the
controllers
that
it
created.
A
A
A
Then
so,
apart
from
this
minor
feature,
this
pr
also
covers
the
other,
the
other
items
that
I
mentioned
here.
Basically,
there
are
some
fixes
around
the
q
builder
manifest
that
we
have
and
and
yeah
that's
mostly
about
it,
so
so
yeah
so
broker
is
running
now
and
mesh
sync
is
also.
It
will
be
up.
A
It's
it's
actually.
Neither
because
operator
creates
this
as
a
as
a
controller
object
like
it
does
not
have
a
manifest.
It
internally
creates
the
object.
A
So
this
is
just
a
corner
case
that
is
being
handled
ideally
mystery.
Ctl.
Would
it
so
measure
your
measures,
mystery
ctl
will
be
removing
the
operator,
but
in
case
of
something
that
went
wrong
and
if
someone
manually
deleted
operator
it
won't,
the
the
controllers
will
not
be
left
back
as
a
residue.
So
so,
basically
now,
if
I
stop
my
operator,
it
terminates
whatever
the
controllers
that
it
created.
A
Okay,
so
yeah.
That's
that's
that's
mostly
about
what
my
demo
is.
Is
any
review
or
comment
from
in
here.
D
A
A
D
Terminate
is
adidi
she's,
not
on
the
call.
Is
she
no
there's?
There's
there's
a
con
question
or
a
concern
about
those.
You
know
people
who
have
deployed
mescheri
when
they
run
mesri
ctl
system
update
that
updates
the
vast
majority
of
the
components
for
measuring,
and
I
know
we've
had
discussions
about
that.
Updating
the
operator
and
the
custom
controllers
as
well,
and
I
I
think
that
has
been
accounted
for.
A
So
the
operator
is
currently
not
merged,
it's
special
master,
so
there
is
no
update
like
there
is
no
logic
of
update
or
deleting
in
case
of
notification.
A
Yeah,
as
in
even
that
is
it
always
point
to
points
to
stable
latest.
D
Okay,
that's
fine
as
long,
but
it's
still
as
long
as
we're
versioning
and
releasing
the
operator
the
custom
controllers,
the
it's
fine
that
their
deployments
are
always
a
subscription.
You
know
to
stable
latest.
That's
that's
good,
it's
desired,
but
the.
D
But
so
so,
then,
that
makes
the
job
easier
for
mesri
ctl
system
update
largely
it
makes
it
easier
that
what
would
need
to
be
done
is
that
those
pods
just
need
to
be
yeah
deleted
and
recreated,
and
so
can
can
we
confirm
that
mastery
ctl
system
update
does
that.
A
It
does
it,
it
basically
deletes
all
the
parts
and
that's
the
controller
created,
recreate
it
perfect
cool,
that's
great,
and
we
had
an
issue
where,
like
sometimes
when
we
stop
misery
and
kubernetes
like
mesh
sink
and
brocara,
is,
are
not
getting
deleted.
Right,
like
yeah.
A
D
Server,
yes,
there
is
most
settings
and
completions
right,
yeah,
there's
kind
of
two.
D
Maybe
we
should
write
this
down
so
that
it's
a
little
more
succinct.
There
are
lord,
the
the
is
a
great
question
and
it
largely
comes
down
to
the
the
part
of
the
purpose
of
a
measuring
provider
that
measuring
provides
a
couple
of
things.
Measury
proper
mastery
server
itself
doesn't
like
in
by
design
it
doesn't
address.
D
So
one
of
those
is
identity
that
it's
the
provider
that
offers
identity
and,
and
then
another
area
of
consideration,
is
persistence
or
persistent
storage
that,
like
for
identity,
part
of
the
concern
there
is
like
hey,
look.
Those
are
those
get
into
secret
things
and
it's
slightly
to
the
side
of
what
we're
trying
to
focus
on
for
the
for
measuring
server
itself.
Let's
let
something
out.
Let's,
let's
have
an
extension
point
for
identity
for
persistence.
It
kind
of
the
same
thing
follows
it's
like.
Oh,
you
know,
persistence
is
hard.
D
People
are
people
get
super
like
justifiably,
super
upset
when
data
goes
missing
and
it's
kind
of
a
side
note
like
it's,
not
the
primary
purpose
of
the
project,
the
proper
project
so
to
speak,
and
so
it
leaves
that
to
providers
so
the
local
provider,
the
built-in
provider
in
mashery
that
that
it's
called
none
when
you
sign
in
it
mounts
your
the
the
local
file
system
of
the
deployment
that
it
or
the
host
that
is
deployed
on
and
actually
abhishek
correct
me
so
on
a
docker
host,
that's
true
mastery
server.
D
Will
its
deployment
will
mount
portions
of
the
local
file
system
to
like
retrieve
cubeconfig
to
retrieve
the
meshery
application
info
under
dot
mesh
tree
under
the
users
like
dot
mastery
folder,
but
in
a
kubernetes
deployment?
D
Is
it
mounting?
Is
it
using
temporary
storage
in
it's
empty.
C
A
D
And
so
they're
in
like
in
so
in
part,
that's
where,
like
the
a
provider
like
the
mescheri
cloud
provider,
it
provides
persistent
storage,
so
it
keeps
it
remote
and
then.
D
Yeah
offers
persistence
of
configuration,
settings
and
performance
test
results
and
patterns
and
filters
and
applications.
Some
things
that
I
don't
think
are
exposed
in
the
ui
just
yet,
but
some
early
features
and
so.
D
Yeah,
there's
four
yeah
there's
a
couple
of
ways
to
yeah.
This
is
this
is
good.
This
is
a
good.
We
should
write
down
what
some
of
those
manual
steps
are
like,
because
there's
a
couple
of
areas
of
concern,
I
think
like
one
of
those
is:
maybe
your
old
test
results
like
how
to
maybe
back
those
up
or
export
those,
and
then
another
concern
is
like
your
specific
configuration
settings.
D
C
D
Yeah
definitely,
then
those
would
be
stored
in
pattern
in
pattern
like
yeah
you're
right,
it's
it's
patterns,
it's
filters
and
then
there's
another
area
of
the
ui
that
it's
probably
helpful
for
everyone
to
see
and
helpful
in
this
discussion
with
samir,
and
that
is.
D
I
think
I
have
a
mastery
system
running
here,
so
so
here's
a
mastery
system.
There
are
a
couple.
D
D
Yes,
and
so
just
as
soon
as
that
starts,
which
I
think
drove
is
gonna,
do
any
day
now
will
be
you'll
start
to
see
some
additional
menu
items,
because
these
are
almost
ready
to
be
released,
almost
ready
for
people
to
poke
at
and
use,
and
so
it's
filters,
your
patterns
now.
These
are
there's
still
work
to
be
done,
which
is
in
part,
why
they're
not
generally
published
part
of
the
work
to
be
done?
D
Is
that
yeah
exactly
what
you're
saying
about
like
if
you've
applied
if
you've
designed
and
applied
a
filter
to
a
given
deployment,
then
that
information
gets
persisted
and
some
of
that
gets
depending
upon
how
you
do
it?
You
can
either
have
that
designed
into
your
pattern
or
there's
a
long
answer
here.
I'm
basically
short
of
it
is
yeah
it
in
terms
of
persistence
in
terms
of
the
ability
to
back
up
it
that
a
lot
of
that
revolves
around
providers.
D
People
can
still
do
some
of
those
things
manually.
Okay,.
J
A
So
we
have
a
couple
of
questions
in
chat.
Leah
vijay
asks:
where
does
all
this
data?
All
the
data
exist
now.
A
And
to
sum
up
as
question
and
discussion
on
chat,
meshery
ctl
does
not
track
the
version
of
the
operators
currently,
so
we
always
pull
pull
it
from
the
latest
release
of
the
of
the
in
the
github.
So
that
needs
to
be
changed.
I
think
adidas
been
working
on
considering
that
support
yeah,
so
that.
A
Okay,
lee
has
said
the
link
to
the
doc
in
chat.
A
Okay,
next
up,
we
have
a
demo
on
the
rest,
api
docs
by
kaushambi
question.
Would
you
like
to
share
your
screen.
K
A
K
A
K
So
the.
K
K
K
K
Yeah,
so
this
was
the
first
self-generated
page
and
I
I
would
like
to
thank
you
for
helping
me
out
with
the
suv
I
think.
K
A
Thank
you,
it
really
looks
great
and
yeah.
Samir
has
a
suggestion
that
we
can
have
a
plus
sign
to
let
the
users
know
that
the
that
this
is
expandable
so
yeah.
That
is
something
you
might
be
interested
in
to
look
into
roshabi
so,
but
from
the
previous
previous
state,
this
looks
really
nice
neat
and
yeah.
This
looks
really
good.
Anybody
has
some
suggestions
for
questioning.
L
I
think
the
swagger
documentation
is
like
this
right,
so
people
know
that
they
have
to
keep
on
there.
There
is
no
need
for
a
plus
sign.
D
One
other
thing
to
consider,
as
as
this
suggestion
is
digested
is
in
if
the
venue,
if
you
don't
mind,
if
you
go
to
the
contributing
section
in
the
docs
there
are
recently
there
are
new
sections
about
contributing
to
different
components.
One
of
those
is
measuring
docs.
D
If
you
go
to
mystery
docs,
it
will
tell
you,
like
you
know,
with
the
various
frameworks
that
it's
using
and
how
to
do
work
with
jekyll
and
but
it
should
also
tell
you,
I
think,
if
you
go,
if,
on
the
very
bottom
there's
a
section
called
using
the
features
of
measuring
docs
now,
I
think
we
only
have
one
feature.
D
D
How
do
you
know
that
there's
a
copy
to
clipboard
function?
Well,
hopefully,
you
read
this
documentation,
but
then
it
will
tell
you
how
to
use
that.
Well,
we're
missing
another
feature
of
this.
These
docs
another
feature
is
there's
this
expandable
and
collapsible.
D
Div
or
like
there's
already
a
feature
that
lets
you
expand
and
collapse
content
because
sometimes
the
docs
go
on
forever
and
you
don't
depending
upon
what
you're
looking
for.
You
may
not
care
for
all
that
detail.
So
one
there's
a
call
for
help
right
now,
right
here,
right
in
this
area,
someone
needs
to
document
what
I'm
about
to
say
next,
which
is
nivendu.
If
you
go
to
supported
platforms
into
windows,
or
I
believe
that
there's
an
example
of
this
expandable
collapsible
thing
that
I'm
referring
to
so
there's
prior
art
for
this
particular
challenge.
D
So
one
right
here
we're
seeing
the
clipboard
right
the
see
the
copy
to
clipboard.
That's
great
right!
That's
one
feature
the
other
feature
and
by
the
way
this
is
not
intuitive.
If
you
go
back
up
because
actually
the
venue
didn't
necessarily
see
it
see
the
wsl
one,
if
you
click
that,
okay,
oh
great
it
like
expanded
and
it
showed
you
some
stuff,
it
show
hide
right
like
that's,
not
horrifically
intuitive,
so
there's
some
thought
that
probably
needs
to
be
given
as
to
how
that
is
used.
D
There's
another
area
in
the
docs
that
uses
that
same
show
hide
function.
The
reason
I'm
pointing
this
out
is
one.
We
need
to
document
that
two
to
samir's
point
and
I
think
husseina's
point.
We
need
to
be
consistent
like
with
how
it
is
that
we're
we
need
to
be
intuitive
and
we
need
to
be
consistent
and
so.
I
Yeah,
if
I
make
a
comment
see,
I
know
it's
not
the
same
thing:
it's
not
documented,
but
in
visual
studio
they
have
this
concept
called
region,
so
it
will
put
a
little
plus
sign
and
we'll
put
you
know
the
first
line
there
see
if
you
click
the.
If
you
click
that
plus
you
know
it,
it
expands
the
rest
of
the
stuff
and
then
the
plus
turns
into
a
minus.
I
I
I
mean,
may
not
be
I
mean
it
may
not
be
intuitive
or
or
or
I
I
just
wanted
to
mention
that
whatever
this.
D
Word
so
so
on
this
it
sounds
like
kashambi.
Samir
husseina
might
continue
in
slack
and
sort
of.
K
A
Thank
you.
Thank
you
guys,
thanks
for
suggestion,
so
anything
else
on
this
before
we
move
on.
F
I
wanted
to
point
something
out
like
this.
Particular
dogs
are
auto
generated
right,
so
the
thing
is:
whenever
a
new
comer
will
try
and
come
to
update
the
dogs,
let's
say
for
ui,
they
will
most
probably
update
the
md
file
or
in
case
of
swagger,
the
yam
will
find
it
to
update
like.
Is
there
a
good
place?
We
could
specify
that
they
are
auto
generated,
because
most
of
them
will
first
like
update
the
generated
files
itself
to
make
changes
if
they
are
not
aware
of
it.
D
Yeah
totally
true,
great
and
I'll,
someone
else
can
make
another
suggestion
I'll
jump
in
and
suggest
two
things.
One
is
that
the
place
where
people
are
most
likely
going
to
look
to
edit
this
file
or
this
area
is
like
right
here
when
they're
looking
at
it
they're
going
to
think
well
that
needs
to
be
changed,
or
there
should
be
a
note
and
so
they're
going
to
click
like
edit.
This
page,
you
know
likely
like
well
and
then
hey,
that's
gonna
be
wrong
because
their
changes
will
be
overwritten,
and
so
it
would
be
like
somewhere.
D
In
terms
of
how
far
you
want
to
take
it,
because
what
will
happen
is
because,
like
that
logic
that
says
edit
this
page,
that's
a
central
script,
that's
referenced
by
every
single
page
on
the
site.
That
is,
you
know,
relatively
small
and
just
says,
grab
the
name
of
the
page
and
create
a
hyperlink
with
the
name
of
the
page,
so
that
when
you
click
edit
this
page,
it
takes
you
right
to
this
specific
page
and
that's
great.
D
That's
a
nice
convenience
operation,
but
in
there
you'll
need
to
have
an
if
statement
that
you
know
says.
Well,
though,
unless
there's
front,
you
have
to
then
create
your
own,
our
own,
like
front
matter
value
that
says
like
show,
show
edit
this
page
or
not
type
thing
like
some
flag
that
you
use
to
then
not
show
that,
and
so
it's
totally
achievable.
A
D
Yeah,
actually,
this
is
just
this
is
great.
This
is
probably
a
good
thing
to
end
on.
This
is
just
a
quick
note
that
nithish
and
I
will
spend
a
little
bit
of
time
directly
after
this
meeting
talking
about
a
couple
of
small
enhancements
in
mesherie's
ui
small
enhancements
on
mesherie's
ui
on.
J
D
All
right
right
here
is
there's
a
couple
of
ux
changes
that
we
will
look
to
do
and
rather
than
describe
them
to
you
all
right
here,
nitish
and
I
were
just
going
to
meet
up
and
talk
about
a
couple
of
those
changes,
and
so
I
figured
we
would
call
that
out
in
case
it's
in
case
working
on
mesher's
ui.
If
that's
of
of
interest
to
anyone,
you
know,
please
feel
free
to
hang
out
on
this
same
zoom
after
the
call
is
over
and
then
we'll
start
to
talk
about
this.
D
As
we
go
to
wrap
up
I'll
ask
this
real
quick,
so
I
see
a
couple
of
people
who
are
here
from
the
recent
hackathon
that
happened
this
last
weekend
that
aditya
krishna
was
is
an
organizer
of
so
I
know,
bharath
kumar
is
here
having
been
a
participant
in
that
hackathon.
Anyone
else
participated
in
that
hackathon.
M
Good
day,
krishna
here,
krishna
koster,
even
I
was
the
team
member
of
the
jit
hackathon.
We
we
secured
the
third
prize.
D
Cool
well
good,
and
so
I
know
the
vendor
and
adi
aditya
krishna
have
been
talking
about
some
next
steps
for
those
that
have
been
involved
in
that
hackathon.
So
good
nice
to
see
you
guys
good
to
have
you.
A
A
So
we
are
almost
out
of
time
and
I
think
we
are.
We
are
going
a
little
bit
more
today
where
we
will
be
discussing
about
mystery
performance
profiles
in
dui.
So
if
you
are
interested,
you
can
stay
stay
with
us
and
for
others.