►
From YouTube: Websites Weekly Call (23rd May 2022)
Description
Layer5 Websites Meeting - May 23rd, 2022
Agenda:
Leaderboard updates
Leaderboard demo
Coverage and Press Release filter to news #2821
CTA for Meshmap #2710
MeshMark page
Updates: Convert meshery.io from jekyll to gatsby site. branch
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/
B
A
B
B
D
D
They've
been
working
on.
You
know
a
data
board
for
the
discourse
platform
and
they
are
going
to
be
demoing
what
they
have
been
working
on.
I'm
really
excited
of
what
they
have
done
and
they're
going
to
be
demoing
their
project.
So
as
they
demo,
you
can
also
not
sound
like
features
or
feedback
for
them.
You
can
either
you
know,
do
their
chat
or
maybe,
after
that
demo
you
give
them
feedback
as
well.
C
C
Okay,
so
this
is
a
little
what
we've
created.
We
used
three
metrics
to
basically
rank
the
users,
so
we
have
the
likes,
received
the
posts
and
the
solutions
and
the
solutions
accepted,
and
we
got
this
data
from
from
this
endpoint.
So
from
here
we
got
the
likes
received
and
the
post
count
and
then
for
the
accepted
solutions.
We
had
to
run
it
for
each
user
because
we're
passing
the
username
on
the
url.
C
C
So
initially
the
leaderboard
is
designed
to
only
show
the
top
five
users
and
then,
when
a
user
clicks
on
show
more,
it
goes
to
another
page
that
basically
ranks
all
the
users
yeah.
So
in
terms
of
what
we
did
in
the
back
end.
So
we
we,
we
basically
fetched
the
data
and
then
saved
them
into
json
files
and
then,
after
saving
it
to
json
files.
So
what
it
to
populate
the
html,
we
basically
call
refresh
the
data
from
now
the
json
files
that
we
already
saved
the
data
from
so
yeah.
C
So
we
basically
have
two
functions:
each
that
populates
two
separate
html
files.
So
for
the
top
five
users
we
have
the
winners,
that's
being
populated
by
different
function
from
the
one
that
populates
all
the
users
yeah.
So
that's
that's
a
brief
overview
of
what
the
leaderboard
is
in
terms
of
responsiveness.
We
basically,
we
include
it
as
a
scroll
feature
so
that
a
user
on
on
a
cell
phone
can
scroll
and
view
the
entire
leaderboard,
but
yeah.
So
that's
that's
a
brief
overview.
E
F
F
A
G
A
G
G
File,
so
I
think
wally's
asking
is,
if,
if
we
have
actually
infused
this
particular
design,
this
particular
this
particular
solution
into
our
local
discourse.
So
if
that's
the
questions,
I
don't
think
we
have
we've
only
like
mentalities
in
the
vanilla,
html,
css
and
javascript,
so
we
haven't
actually
like
infused
it
into
like
a
local
disk
costs,
so
we
well
the
the
intentions
was.
G
If
we
could
get
this
like
this,
then
maybe
some
one
of
the
admins
that
knows
how
to
infuse
this
sort
of
thing
into
this
girls
could
do
it
so,
but
I
think
all
it
means
is
that
we
should
could
have
actually
texted
ourselves
on
our
local
discuss.
So
if
that's,
if
I'm
correct,
I
think
that's
really
those
action.
A
A
Okay,
so
now,
why
were
you
guys
going?
Okay,
all
right,
I
just
think
I
think
you
guys
spent
a
lot
of
time
doing
stuff.
You
probably
didn't
need
to
do
yeah
or
if
you
did
do
it,
then
you
could
have
written
it
differently
than
this,
because
what's
written
is
so
edna's
done,
I'm
fantastic
for
leonard
and
ruth
and
raj,
like
some
feedback.
Is
one
you're
probably
calling
this,
especially
when
you
go
to
the
show
more,
how
many
times
you're
going
to
make
requests
of
the
api
once
for
every
user
right.
G
Okay,
so
the
show
more
button
is
actually
is
once
for
every
user,
so
the
show
mod
basically
has
we
have.
We
have
our
json
json
data
that
that
will
fetch
and
skip.
So
it's
just
it's
json
that
is
rendered
in
the
page.
So
this
json
should
fetch-
maybe
intervally,
probably
like
some
time
in
a
day,
maybe
midnight
in
the
day,
so
yeah.
A
A
C
A
C
C
A
H
Request
that
that
we
are
calling
each
username
for
is
just
to
grab
the
solutions
accepted.
So
maybe,
if
we
can
calculate
this
particular
leaderboard
data
without
adding
the
solutions
accepted,
then
would
not
need
to
call
every
user
over
and
over
again.
I
think
we
do
not
need
to
call
every
design
in
their
five.
A
Is
the
same
stuff
we
talked
about
a
couple
months
ago,
which
is
just
it's
probably
to
write.
It
have
a
sql
query,
one
to
make
sure
that
the
queries
that
aren't
there
don't
already
include
a
list
of
accepted
solutions
because
they,
so
I
think,
if
I
recall
part
of
the
point
of
you
guys
running
the
system
locally,
was
to
be
able
to
look
and
see
what
administrative
reports
are
in
the
admin
dashboard
and
whether
or
not
those
have
accepted
solutions
included.
A
Because
what
you
ultimately
want
is
a
sql
query
that
runs
efficiently
catalog
or
catalogs
and
orders
users
by
accepted
solutions,
and
then
it
would
be
a
single
it
should
be.
It
should
be
like
a
single
api
query,
an
api
call
to
get
the
board
its
contents
and
its
users
sequence.
Otherwise,
what
you're
going
to
find
is
that
you've
got
a
solution
that
doesn't
necessarily
scale
if
you
have
300
users
you're
going
to
have
to
call
to
make
301
requests
the
first
request
to
get
all
300.
A
A
No
30
requests
wait
three
weeks,
wow
it's
too
early
for
math,
but
but
a
lot
of
requests
just
to
get
the
users
and
then
one
request
per
user.
Because,
because
what
you're
saying
is
you've
got
to
go
out
and
get
and
then
from
there,
then
you
would
have
aggregated
all
that
info
and
written
it
in
javascript.
A
To
then
do
what
you
otherwise
would
have
done
with
a
sql
query
and
that
that's
like
that's
fine.
That
doesn't
mean
I'm
not
so.
Actually
all
I'm
trying
to
do
is
one
is
let
the
organizers,
ruth
and
the
mentors
know
that
you
should
be
helping
the
two
mentees
as
much
as
you
can
and
providing
some
feedback
early
on.
What
what
you
guys
have
have
looks
very
nice.
It's
not
responsive.
A
So
the
fact
that
people
can
scroll
left
to
right,
that's
nice,
but
that's
actually
not
responsive
at
all.
That's
what
you
just
normally
get
when
you
put
html
on
a
page
anyway.
It
feels
like
for
the
the
mentors
here,
perhaps
you're,
not
providing
feedback
or,
if
you're
going
to
spend
time,
setting
up
something
locally,
then
get
some
value
out
of
it
like
using
a
sql
query.
A
In
that
case,
I
don't
know
or
like,
is
there
a
design
spec
that
talks
about
how
many
requests
are
being
made,
or
I
think
what
you
guys
were
saying,
you're,
creating
your
own
point
based
system?
What
you're
saying
is:
if
a
user
wants
to
get
a
lot
of
total
points
here,
what
they
could
do
is
just
game.
The
system
go
in
and
just
like
as
many
posts
as
they
want
to
every
single
post.
They
would
at
least
get
one
point
for
that.
A
Ultimately,
the
hard
thing
where
they
would
get
three
points
in
this
weighted
system
would
be
on
the
solutions,
acceptance
that
maybe
might
be
kind
of
hard
for
them,
but
at
least
they
could
game
this
system
by
just
going
through
and
liking
whatever
they
want
to,
and
that
would
that
would
count
in
this
context,
so
be
careful
of
the
behavior
that
you're
incentivizing
as
you
design
such
a
board,
because
most
there's
a
lot
of
humans
out
there.
That
will.
A
I
don't
know
what
are
the
phrases
to
use
but
gain
the
system.
You
know
so
think
think
about
that.
If
you're
only
accounting
for
accepted
solutions,
perhaps
that
avoids
some
of
how
they
might
game
the
board,
maybe
not
entirely
because
they
still
might
be
going
for
an
easy
solution.
Maybe
they're
copying
someone
else's
solution,
or
I
don't
know.
A
A
A
I
would
think
this
is
something
to
put
into
your
design.
It
might
be
demoralizing
to
newcomers
who
see
anita
is
like
number
one
here
and
she
has
thousands
of
points.
How
would
I
ever
make
it
to
that
like
it?
Maybe
that's
fine,
maybe
not
like
it,
and
maybe,
if
you've
considered
for
this
I'd,
love
to
hear
you
know
hear
about
what
you
guys
are
thinking.
F
D
D
D
Folks
can
just
go
in
and
put
in
different
lights
and
just
go
on
like
a
lot
of
post
and
then
it
just
populates
this
and
that's
not
really
the
motive
of
it.
So
I
I
agree
with
that
point.
You
know
making
the
design
the
design
of
this
so
that
folks
do
not
folks
are
coming
to
the
community.
Do
not
misinterpret
what
the
leaderboard
is
and
just
we
just
have
people
I
can
and
putting
up
random
posts
to
get
to
dvd
starters.
H
In
case
we
have
a
lot
of
users,
which
is
the
solutions
accepted,
but
it
seems
it's
like
a
really
prominent
part
of
this
leaderboard
so
honestly,
and
so
if
we
can
get
other
data
from
one
particular
api,
that
is
one
of
the
apis
and
then
look
into
it
and
see
what
other
things
we
could
like
explore
and
also
leave
this
little
boat
come
to
life,
even
though
this
is
still
going
to
be
the
same
thing.
If
this
solution
is
accepted
is
still
implemented.
G
G
G
G
So
the
the
design
for
the
for
this
is
about
the
design
spec
for
the
leaderboard
doesn't
really
like
outline
so
much
on
how
design
would
look.
So
we
I,
I
would
say,
we
really
mentors
kind
of
gave
the
mentees
some
sort
of
for
them
to
take
their
own
initiatives
on
how
to
set
up
leaderboard
from
from
the
formal
leaderboard
we
have
so
and
that's
how
they
were
able
to
come
up
with
these
and
because,
with
the
color
aligned
with
what
we
had.
I.
A
Yeah
leonard,
you
don't
have
to
necessarily
respond
to
each
other.
Anyway,
you
guys
should
write
down
a
design
spec
which
accounts
for
stuff.
Like
hey.
Are
they
you
know?
Is
someone
going
to
abuse
the
system?
Is
it
going
to
scale
like
hey,
just
to
be
clear
on
all
the
the
feedback
that
I
just
dumped
on
to
you
guys?
I
I'm
sure
it
kind
of
felt
like
a
dump
and
that
I
want
to
be
clear,
like
edna
and.
A
Oyen
de
mola-
it
you
you
guys,
have
done
well
like
there's
a
lot
of
nice
things
to
say
about
what
the
work
that
you've
done.
So
it's
early
in
the
morning
for
me,
so
my
voice
is
hoarse.
I'm
a
grumpy
bastard!
I
haven't
had
any
coffee,
like
I'm
sitting
on
the
side
of
this.
By
the
way
the
the
presentation
really
isn't
to
me
it's
to
yourselves
and
to
the
other,
mentors
and
organizers
here,
and
to
just
the
other
togaro
to
everybody.
A
That's
on
the
call,
I'm
I'm
just
the
one,
that's
dumping
on
you
and
I
don't
want
it
to
feel
like
that.
Like
so
there's
a
ton
of
great
things
to
say
about,
what's
already
been
done
like
then,
by
the
way
from
from
my
perspective,
the
ux
design
is
great
like
like
this.
Will
the
the
you
could
improve
it
by
working
on
responsiveness
of
the
of
what's
shown,
I'm
not
sure
how
much
you
have
to
work
with
it's
kind
of
something
like
as
it
gets
smaller
in
width.
A
Maybe
you
might
start
by
dropping
the
likes
posts
and
solutions
accepted
and
then
just
leaving
rank
avatar
image,
username
and
points,
and
if
it
gets
really
squished,
maybe
removing
the
name.
So
it's
just
rank
avatar
image
and
points,
but
just
stuff
like
stuff
like
that
to
just
iterate
a
little
bit
on
the.
If
you
were
to
do
anything
about
the
ux,
you
know
using
the
design
constraints
of
taking
advantage
of
of
the
rest
api.
That's
there
and
and
only
being
able
to
do
that.
A
The
approach
is
seems
somewhat
reasonable
to
me
like
if
you
didn't
have
sql
at
hand
to
be
able
to
do,
and
that
wasn't
part
of
what
was
possible
like
last
time
that
we
spoke,
we
talked
about.
Oh
hey,
there's
these
rest
apis.
What
do
they
do
and
how
could
they
be
used?
And-
and
from
my
perspective,
you
all
have
iterated
very
well
from
there
from
that
vantage
point
of
like
what
are
the
rest
apis
and
how
to
use
them.
A
A
That
whole
set
of
conversations
is
like
not
necessarily
obvious
at
all.
It
is
not
necessarily
technical
in
nature;
it
does
affect
the
technical
approach,
but
so
so
anyway,
lots
of
don't
be
dismayed
about
the
end
of
the
conversation
is
what
I'm
and,
by
the
way,
any
almost
any
piece
of
software.
That's
worth
its
salt
or
that's
like
worth.
Having
done
a
it's
generally
kind
of
difficult
b,
you
usually
have
to
rewrite
it
once
or
twice
like
it's.
Usually
you
you
go
through.
You
learn
a
ton
of
stuff.
A
B
So
moving
on
to
next
topic,
we
have
by
harshit-
and
I
guess
he's
not
on
the
wall.
So
let's
visit
his
pr,
add
coverage
to
press
release
and
filter.
So
he
has
added
a
filter
on
the
news
page
and
some
reviews
and
some
reviews
were
made
by
me
and
nikhil
so
he'll
be
pushing
changes
by
today.
So
let's
visit
the
deployment
of
the
pr.
A
E
A
Do
other
people
have
feedback
so
so
it's
a
very
simple
new
feature
request.
There's
a
list
of
news
news
is
either
generated
from
layer,
5
and
published
as
a
press
release
or
news
is
coverage
given
by
analysts.
So
I
think,
on
friday
or
saturday,
lair
five's
works
were
in
the
news
that
piece
of
news
isn't
listed
here,
there's
an
open
issue
on
it,
but
that
piece
of
news
was
from
an
analyst
a
reporter.
A
A
A
A
B
E
E
B
B
E
B
F
F
B
F
B
Yeah
and
this
not
a
back-end
specific
meeting,
so
you
can
subscribe
to
this
layer
5
calendar,
so
we
have
a
mystery
mystery
call
week
on
every
wednesday
at
7,
30
pm
ist
and
we
have
bi-weekly
build
and
release
calls.
So
that
also
includes
back-end
latest
stuff,
so
I'll
be
sharing
the
link
of
the
calendar.
You
can
subscribe
this
calendar
to
get
updates
to
your
own
calendar.
B
E
I
B
B
B
A
A
B
I
I
I
I
B
Okay,
so
like
there
could
be
two
possibilities,
so
one
would
be
that
this
button
is
wrapped
under
a
parent
class
which
is
having
this
particular
styles
and
you
might
be
applying
styles
to
the
child
class
or
yeah.
There
must
be
some
issues
with
the
class
names
or
any
things
you
might
have
to
look
into
the
code.
A
A
It
isn't
great
for
exact,
potentially
exactly
what's
happening
to
you,
which
is
you're
making
changes
which
are
affecting
the
correct
classes,
and
you
should
be
seeing
the
effects
of
those
changes,
except
as
it
turns
out
the
css.
That's
getting
loaded.
Every
time
is
the
minified
public
version
from
somewhere
else
that
doesn't
have
any
of
your
changes.
A
I
B
I
I
A
C
B
B
So
most
of
them
are
done
and
if,
if
you
want
to
like
take
any
of
the
component,
you
can
simply
add
the
component
name
and
assign
it
to
yourself
and
start
working
on
that
and
then
make
a
pr.
So
if
you
are
totally
new
to
this
machine
project,
I
would
suggest
to
take
a
very
small
component
that
is
not
being
implemented,
so
you
will
gain
much
more
confidence
in
implementation.
B
B
Okay,
so
previously
for
the
first
iteration,
we
were
showing
the
performance
profiles
on
the
basis
of
service
mesh
and,
according
to
a
result,
we
are
showing
test
specification
and
environment
details.
But
now,
after
further
consideration,
we
are,
you
know,
planning
for
a
second
integration
and
some
design
changes
for
which
we
have
finally
down
to
three
page
layout,
in
which
the
first
first
landing
page
would
be
of
what
are
the
different
types
of
tests
that
the
user
wants
to
see
the
results
of
like
control,
pin,
test
or
network
test.
B
And
after
that,
when
we
click
when
we
select
a
particular
test,
we'll
show
all
the
performance
profiles
for
which
the
that
particular
type
of
dash
is
run
and
after
that,
the
user.
If
wants
to
see
the
results
of
a
particular
performance
profiles,
he
then
clicks
to
a
individual
profile,
and
then
it's
redirect
to
a
page
in
which
he
can
see
all
the
graph
and
test
specification,
environment,
details
and
everything.
B
So
right
now
we
have
initialized
all
the
three
pages
and,
after
a
proper
analysis
of
what
data
is
coming
from
smp
like
cncf
clusters,
we'll
actually
make
made,
make
it
dynamic
and
yeah.
That's
the
plan
right
now
we
have
just
initialized
the
page
and
have
a
basic
like
basic
workflow
of
how
things
should
work
and
yeah.
That
was
my
update.
A
Guys,
as
it
gives
some
consideration,
if
you
would
as
to
how
people
navigate
those
three
layers,
it
looks
like
on
the
left-hand
side
that
left-hand
menu.
They
can
navigate
that
first
layer
by
choosing
maybe
the
first
and
second
layer
they
could
navigate.
If,
like
all,
profiles
represents
the
first
layer
and
then
an
individual
profile
represents
the
second
layer
and
then
for
the
third
like
you
might,
you
might
need
a
cookie
crumb
trail
or
a
back
button,
or
I
don't
know,
but
it's
something
to
think
about.
B
B
B
A
If
it's
just
a
blank
playground
where
they
can
type
commands
and
do
things
they're,
not
necessarily
going
to
know
what
those
commands
are
or
what
they
should
do.
The
these
learning
paths
here
tell
them
that
tell
them
that
this
is
what
a
mesh
does,
and
these
are
the
things
that
you
can
do
with
it.
These
are
the
chapters
and
labs
that
you
can
walk
through,
and
so
it's,
but
this
doesn't
have
a
live
playground,
environment
necessarily,
so
it's
the
it's
the
merging
of
those
two
that
at
some
point
will
want
to
work
toward.