►
From YouTube: Meshery Development Meeting - Oct 30 2019
Description
Meshery Development Meeting - Oct 30 2019
B
A
C
C
B
C
C
B
C
A
C
C
A
C
A
You
have
to
do
something
like
that,
like
you
know,
so
this
is
what
I
is
telling
that
you
will
have
to
create
a
version
variable
and
and
when
they're
having
a
default
value
for
it
or
not,
is
not
important,
but
you
can
actually
use
this
example.
This
is
a
good
one.
We
don't
need
commit,
we
don't
need
the
date.
I
guess
like,
and
all
we
need
is
the
version
number.
So
you
know,
and
the
version
number
will
be
the
same
version
number
like
you
know
we
tagged
or
release
ass.
A
So
all
you
have
to
do
is
like
I
mean
you,
you
can
follow
the
go
release
or
example,
and
use
this
one
here.
I
think
we
just
need.
The
version
number
like
I
said,
like
just
use,
worship
and
use
the
LD
parts
to
actually
set.
The
version
number
like
you
know
how
the
go
laser
is
actually
showing
it
in
in
their
documentation.
A
C
A
Awesome,
who
was
guys.
A
Okay,
okay,.
A
Okay,
gotcha,
you
don't
wanna
come
after.
This
call,
I
will
talk
to
me
and
we
will
we
will
ensure,
like
you,
have
something
shoes
to
work
on
next.
We
have
quite
a
few
things
going
on.
Like
you
know,
so,
definitely
you
know
you
will
have
something
and
I'm
not
sure.
Like
you
know,
if
we
mentioned
this
to
you,
we
are
SHINee
is
actually
on
the
call,
so
we
are
going
to
be
presenting
mastery
and
the
master
en
SM
adapter
at
NSM
con,
which
is
actually
part
of
cube
con.
A
It's
it's
a
day,
0
event
at
cube
con,
which
is
going
to
happen
in
Santiago,
so
me
and
Lee
are
going
to
be
there
to
present
it
on
stage
with
frame.
So
so
it
will
be
a
great
place
like
you
know,
to
actually
showcase
all
your
work
and
I'm
pretty
sure
like
I'm,
only
usually
I
think
you
might
have
seen
it
like.
He
has
this
deck
like
you
know
where
he
has
the
phone.
A
The
photos
of
all
the
contributors
on
one
page
I
can
hit,
try
I
think
he
has
what's
called
I,
think
he
calls
it
a
collage.
So
it'll
be
a
big
I
mean
you
guys
will
actually
get
recognition
on
stage.
You
know
for
all
the
work
you're
doing
with
my
Suri,
so
you
know
that
that'll
be
that'll,
be
a
wonderful
thing,
so
we
are
actually
now
working
towards.
You
know
getting
some
stuff
ready
for
that
presentation.
So
that's
gonna
happen
at
about
3
weeks.
It's
actually
on
the
November,
18th
I.
A
Think
yeah
I
think
it's
a
the
18th
yeah,
so
so
yeah
I
mean
looking
also
that's
another
place
where
you
know
you
got
your
faces,
will
most
probably
be
presented
on
the
stage
so
yeah
so
keep
up
the
great
work
like
you
guys
are
doing
you
know
all
your
contributions
are
definitely
very
I
mean
be
a
very
happy
to
actually
receive
your
contributions,
yeah
so
yeah.
So
so
pretty
much
looking
at
you,
you
guys
will
be
celebrities
like
you
know
the
next
few
days
again,
I
mean
again
because
we've
been
we've
been
presenting
like
in.
A
Are
you
guys
at
all
the
stages
like
you
know?
We
we're
presenting
at
yeah
so
yeah,
so
Shabana
I'm.
Sorry,
like
I,
didn't
know
that
you
know
we're
not
working
on
anything.
So
I
I
will
talk
to
Lee
I'm.
Looking
a
seat
to
that.
You
know
you
get
something
to
work
on.
You
know,
probably
in
the
next
few
hours
and
let's
take
it
from
there
awesome
I.
C
A
Will
I'll
see
if
I
can
spend
some
time
with
you
know,
with
with
issues
with
the
issues
that
are
assigned
to
you
and,
and
you
know
you
know
me
and
Lee
like
we
will
do
a
revalidation
of
the
shoe.
If
the
issue
still
exists,
then
we
let
you
know
so
that
you
can
continue
working
on
it.
If
not
like.
You
can
actually
move
on
to
your
next
issue.
So
I
think
that
will
be
a
decent
way
to
actually
go
about
it.
Does
it
make
sense.
A
Okay,
no
worries
you
don't
want
to
come
in.
Yeah
you're,
like
I'm,
feel
free
to
pick
an
issue.
There
is
definitely
there
are
quite
a
few
across
all
the
repositories
so
feel
free.
Do
we
don't
find
an
issue
which
you
know
which
will
interest
you
and
you
know
feel
free
to
assign
it?
If
you
have
any
questions
again,
you
know
you
can
you
know
think
of
some
slack
and
you
know
we'll
be
more
than
happy
to
actually
answer
your
questions
so
yeah.
A
That's
that's
also
a
great
way
to
start
so
today
is
kind
of
a
busy
day.
You
know
we
are
I
mean
like
it.
Also.
There
are
quite
a
few
meetings
happening,
so
you're
right,
like
you
know,
we
will
probably
not
get
back
to
you
in
the
next
two
or
three
hours.
Probably
it'll
take
a
mission
much
longer
in
the
sense
of
probably
like
five
or
six
hours
like
you
know,
but
then
we
will
be
back
with
you
guys
to
check
on
these
shoes
to
assign
something
shoes
to
you
guys,
but
but
yeah.
A
C
A
Interesting
I
thought,
okay,
so
it
looks
like
shoe.
Bomb
actually
went
home
and
for
him
it
was
awesome.
That's
that's
great
sure.
Well,
that's
awesome.
Awesome
yeah
Nikhil,
also
like
Ana,
seems
to
have
had
a
nice
one.
How
she
knee
is
actually
on
the
call
with
us
and
her.
She
knee
actually
did
travel
home
for
her
Diwali
celebrations.
So
I'm
I
really
hope
my
gosh.
She
had
a
good
time
as
well.
I
see
gotcha
gotcha
cool
guys.
I
learned
about
anybody
else,
like
you
know,
is,
was
gun.
John's.
E
A
A
A
So
got
you
yeah
I,
yes,
unfortunately,
DCO
cannot
be
fixed
from
the
browser
you
have
to.
You
will
have
to
amend
your
commit.
Ok,
can
you
actually
tell
me
your
branch
branch
name?
Oh
you
know
what,
after
this
call
I
can
you
know,
I
can
probably
give
you
some
instructions
and
let
you
know
see
if
we
can
get
you
past
the
DCO.
She.
A
A
A
So
cool
cool
man-
yeah-
that's
awesome,
yeah
I
mean
now.
For
me,
oh
nice,
nice
Siobhan,
that's
awesome!
So
for
me
the
ball
is
I
mean
here.
Diwali
is
usually
celebrated
in
kind
of
a
software
like
I
mean
here,
people
don't
blast
crackers,
but
what
people
do
is
like
you
know.
So
there
are
some
temples
here.
So
we
go
to
those
temples,
and
you
know
the
temple
has
like
a
really
large
parking
lot.
So
sometimes
they
do
blast
crackers
there,
but
this
week
like
I
could
I
couldn't
go
there.
A
A
E
Interesting,
yes,
sir
okay
King
was
sitting
in
the
country
discuss.
There
was
in
syntax
error
in
the
endless
folders
with
a
file
name
create
country
to
go,
but
so,
when
I
am
going
to
be
correct,
that
inner
the
file,
which
is
there
in
that
gate,
conflicted
in
let
that
go.
It
is
already
corrected
on
it.
So
how
can
I,
sir.
A
A
You
know
what,
after
this
call,
I
will
take
a
look
at
it
and
I'll.
Let
you
know,
like
you
know
what
you
know
the
best
way
to
go
about
it.
One
thing
is
that
sometimes
the
so
some
yeah
somebody
else
probably
are
gonna
fixed
it
and
you
are,
you
know,
I
mean
like
accidentally.
You
know
your
your
fix.
Also
does
the
same
thing
and
what's
going
to
happen
is
it
might
actually
result
in
a
conflict
so
the
best
way
to
do
that
would
be
kind
of
synchronize.
Your
branch
would
like,
for
example,
master.
A
So
that
way,
you
know
you
can
avoid
this
conflict
issue
or
at
least
try
to
resolve
it
in
your
branch.
And
then,
if
you
push
it
like
an
idol,
it
will
actually
take
care
of
the
you
know
the
conflict,
so
you
know
where
they
go,
but
let's
talk
in
detail
like
after
this
call.
You
know
because
lose
just
like
probably
like
eight
minutes,
so
you
know
let's
more
Daniel,
and
then
we
also
have
her.
So
you
know
so
so,
let's,
let's
move
on
together.
A
E
A
Are
you
awesome
dude?
So
so
one
thing
I
mean
ago
before
you
start
I
am
I
was
looking
at
your
branch
and
you
know
I
kind
of
like
you
know,
pulled
the
changes.
You
know,
I
try
I
made
a
very
tiny
change,
but
then
I
mean
that
did
not
resolve
the
issue.
You
try
to
point
out
to
me
so
I'm,
going
to
you
know,
I
need
a
little
more
time
to
spend,
but
unfortunately,
I'm
kind
of
you
know
I'm
kind
of
tied
up
with
something
else.
E
A
So
a
short
answer
to
that
is
that
so
most
of
the
CSS
we
are
leveraging
or
actually
part
of
library.
Now
one
thing
I'll
tell
you
is,
you
know,
switch
to
the
master
branch.
If
you
switch
to
the
master
branch
and-
and
you
know,
do
a
build
and,
like
you
know,
run
it
on
your
local
and
go
to
the
performance
page.
You
know
where
the
where
we
longer
run
the
load
test
now
in
the
low
test.
A
Page
I'm
actually
doing
something
very
similar,
actually
where,
if
you
are
connected
to
kubernetes-
and
you
know,
the
communities
has
a
service
much
like
history
or
link
ready,
it
will
fetch
the
data
and
Kurt
fetches.
It
will
actually
preload
the
value
in
a
Rob
down.
So
in
that
context,
I
don't
have
this
issue,
but
you
know
I'm,
just
saying
I
mean
like
so
so
the
point
I'm
trying
to
make
is
that
most
of
the
CSS
were
later
to
all.
These
components
are
coming
from
their
library.
So
you
know
I'm
not
trying
to
do
anything.
A
Custom
to
you
know,
change
them
in
in
you
know
much
of
a
big
way,
but
most
of
the
CSS
is
coming
from
their
modules
themselves.
So
yeah
it
is.
It
would
be
tricky
if
you
want
to
go
the
CSS
route
and
I
think
it's
also
harder,
but
but
you
know
what
yeah
you
know.
What
give
me
today
I'll
see
if
I
can
spend
some
time
with
it
and
see
if
I
can
and
and
and
let's
go
from
there
worst
case.
You
know,
let's
go
to
the
CSS
ode
and
yeah.
E
E
A
Cool,
so
let's
get
you
some
issues,
you
know
after
I
talk
to
me
again,
the
same
thing
which
you
know
which
shoe
bomb
actually
pointed
out
like
is
that
I
mean
the
sill.
So
this
is
an
open
source
project
right,
but
the
usual
and
strategy,
an
open
source
project
for
assigning
issues
is
that
you
know
sometimes
are
so
many
issues.
It's
hard
to.
A
You
know
pick
and
choose
people
to
assign
the
issues
too,
but
rather
the
approach
is
that
you
know
you
go
find
I
mean,
like
you
know,
we
have
open
like
it
are
definitely
much
more
issues
so
find
an
issue
like
you
know.
You
guys
are
interested
and
you
know
just
assign
your
name
to
it.
I
like
it'll
go
from
there.
So
now,
when
you
assign
the
name
to
it,
it
actually
gives
one
other
thing
that
you
know
you
I
mean
accidentally.
You
don't
step
on
somebody
else's
toe
and
YC.
D
A
B
A
A
A
D
D
A
A
A
Awesome
anything
else
you
want
to
talk
about
her
feeling.
A
Alright,
so
cool
place
thanks
a
lot
for
joining
the
call.
Today
we
are
well
within
the
time
window,
which
is
fantastic,
a
general
instruction
which
I
just
I
mean
like
it,
like
the
one
I
just
mentioned
like
it
is
that
yeah,
if
you
find
any
issues,
you
know
feel
free
to
put
your
name
against
them
and
start
working
on
them.
One
other
thing
is
sometimes
some
issues
like
it
will
take
longer.
A
So
if,
for
example,
you
pick
an
issue
and
you
know
it's
sometimes
it
doesn't
make
sense,
don't
don't
hesitate
to
actually
ask
us,
don't
feel
bad
right
now,
mainly
it's
just
a
learning
process
right,
looking
at
sometimes
some
things
you
can
learn
quickly.
Sometimes
some
things
take
a
little
bit
longer
because
you
know
what
happens
is
when
when
mess
restarted,
like
you
know,
it
was
a
smaller
project.
Now
you
know,
we've
been
putting
adding
features
like
an
eye
into
it,
like
you
know,
from
all
directions
possible.
A
So
now
some
areas
of
memory
are
becoming
much
more
complicated
than
the
others
same
thing
with
a
dock
site
like
you
know,
for
example,
again
a
yesterday
we
had
this
issue
of
the
dock
site
where
the
search
functionality
was
broken
and
it
turned
out
like
you
know,
there
was
do
it.
There
were
no
issues
in
the
search
functionality
itself,
but
then
there
was
an
interesting
redirection
that
was
happening
and
that
was
causing
the
site
to
kind
of
break.
When
that
happened,
so
I
mean
all
these
things
happen.
A
So
you
know
you
just
need
some
patience
to.
Actually
you
know
kind
of
learn.
You
know
dig
out
like
you
know
what
the
problem
is,
learn
about
it
and
then
try
to
find
out
a
potential
possible
fix
for
it
and
work
around
it.
So
you
know
don't
feel
disheartened
is
kind
of
what
I'm
saying
like
you
know.
If,
for
example,
you
know
some
issues
are
confusing
to
you.
The
other
thing
is
that,
just
like
you
know
how
Anand
actually
showed
a
page
like
know
where
all
his
issues
were
listed.
A
You
know
whenever
you
have
some
time,
you
don't
go
to
the
github
page,
the
repository
page,
and
then
you
don't
go
to
the
issue
section
and
then
filter
by
a
name
just
to
ensure
that,
like
you
know,
you
have
addressed
all
the
issues
that
were
assigned
to
you.
You
know.
Sometimes
what
happens
is
like,
for
example,
on
and
had
like
you
know,
five
or
six
issues
assigned
to
him.
So
you
know
he
didn't
have
some
questions
that
you
know
he
remember
working
on
some,
but
you
know
whether
it's
fixed
or
not.
A
A
You
know
help
you
resolve
that,
like
you
know
either
you
know
we
can
say
you
can
close
this
you,
but
but
the
other
thing
is
there
are
also
sometimes
issues
which
are
like
yeah.
You
know
what
you
know.
The
issue
seems
to
be
gone
now.
You
know
what
you
know
it
might
come
up
later
is
kind
of
a
doubt.
You
know.
Sometimes
people
might
have
it's
okay
to
close
issue.
If
the
issue
arises
again,
we
can
always
reopen
the
issue
and
also
so.
A
This
is
like
a
general
instructions
to
everybody.
So
don't
feel
I.
Don't
feel
bad.
That,
like
you
know
that
your
fix
seems
to
have
been
in,
but
then
you
know,
your
issue
is
still
open.
Kind
of
a
situation
make
sense.
So
if
you
think
you
have
submitted
a
PR
and
that's
merged,
you
should
technically
close
the
issue.
If
the
issue
still
exists
or
comes
back
later,
we
can
always
reopen
it,
and
you
know
you
guys
can
continue
working
on
it.
So
that's
pretty
much.
What
I
wanted
to
tell
you
guys?