►
From YouTube: Layer5 Websites Meeting (June 21st, 2021)
Description
Layer5 Websites Meeting - June 21st, 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
Okay,
so
it's
already
four
minutes
past
and
we'll
be
starting
with
the
website's
call.
So
every
monday
we
do
have
websites
call
and
we
have
around
half
a
dozen
of
websites
ranging
from
react
gatsby
to
jekyll,
and
we
talk
about
issues
and
progress
or
updates
on
those
websites,
and
so
I
have
dropped.
The
link
to
the
and
leo's
also
dropped
the
link
to
the
meeting
minutes.
A
B
No,
this
might
be
anshu's
first
websites
meeting,
but
he's
been
kind
of
busy
on
measuring
docks.
So
anshu
do
you
want
to
say
hi,
though,
to
introduce
yourself
on
this.
C
C
A
C
Yeah,
okay,
so
yeah
this
is
for
website.
This
is
my
second
reading
I
attended
from
you
know
anonymous
my
next
email
id
but
yeah.
This
is
my
first
bit.
A
Cool
welcome
welcome
to
the
website
spawn,
so
I
will
go
through
the
today's
topics,
so
we
so
if
you
guys
feel
you
have
any
topics
to
discuss,
you
can
just
drop
down
your
topics
in
the
list
and
we
can
discuss
over
it.
So
moving
on
the
first
topic
is
by
lee
about
remove
the
launch
category
on
discuss
so
lee.
Would
you.
B
Oh
yeah
yeah.
Let
me
share
by
the
way,
if
you
guys
have
seen
this
on
the
rest
of
the
calls
always
share
or
don't
be
stingy
share,
so
there
was
a
yeah
I
had
so
you
guys
are.
I
hope
aware
that
josh
in
particular,
but
a
few
other
folks
had
collaborated
to
create
this
new
well
to
stand
up
a
new
instance
of
discourse
and
I
think
well,
let
me
ask
this
so
nitish
to
anshu
nikhil
are
all
of
you
guys
signed
up
on
this
site
yeah,
I
thought
so.
B
Good
good,
good,
okay,
and
so
anyway,
so
josh
has,
and
others
have
been,
considering
how
it
is
that
this
is
con.
You
know
so
it's
styled
and
configured
and
different
plug-ins,
and
you
know
backups
and-
and
you
know
a
number
of
considerations
as
to
how
we
should
run
this
and
how
we
get
activity
going
and,
and
so
one
of
the
as
the
site
has
so
there's
two
of
these
sites.
B
There's
the
the
production
site,
disqus.layer5.io
and
then
there's
the
staging
site
staging
hyphen
disqus.layer5.io
the
staging
site
is
actually
missing
a
change
recently.
We
ended
up
updating
the
logo
here,
not
that
this
is
really
important,
but
just
to
say
that
the
staging
site
is
for
purposes
of
well
testing.
Staging
is
probably
the
wrong
word.
B
It's
probably
more
like
dev
or
is
what
this
one
is
for,
but
it's
one
of
those
things
that's
going
on,
and
I
think
you
guys
will
talk
about
later,
but
I
was
on
the
site
and
had
considered
that
one
of
the
default
private
one
of
the
default
categories.
Each
of
these
are
categories
of
topics.
B
It
was
a
private
category
and
you
can
see
this
one
here.
It's
called
staff
and
so
private
category
for
staff
discussions
it's
visible
to
admins
and
moderators,
and
by
the
way,
I'm
hopeful
that
some
of
you
will
become
moderators
at
some
point
like
as
you
familiarize
with
the
projects.
Hopefully
you
will
josh
is
seeking
out
captain
captains
of
community
to
help
curate
activity
in
order
to
curate
answers,
help
with
the
activities
and
anyway.
So
getting
to
my
point
was
there's
this.
B
B
The
lounge
wa
is
was
for
any
user
that
had
reached
a
trust
level
of
three
meaning,
and
and
how
do
you
reach
that
trust
level
is
like
you?
You
join.
You
make
some
comments,
you
create
some
threads,
you
respond
kindly
or
you
do
so
within
a
certain
amount
of
time
frame
as
well.
Like
you,
it's
just.
The
system
itself
works
like
that
and
by
default,
if
you'd
reach
that
level,
then
you'd
be
able
to
access
the
lounge.
B
Like
this
special
category
in
which
community
members
of
a
certain
rank
could
converse
privately,
I
was
like
well,
I
don't
think
we
really
need
this
like.
I
don't
think
that
that's
that's
not
what
we're
trying
to
do
we're
trying
to
talk
publicly
as
much
as
possible
and
acknowledging
that
not
all
conversations
can
be
public,
but
but
most
of
them,
and
so
does
anyone
disagree.
B
Does
anyone
feel
strongly
that
we
should?
We
should
retain
something
like
this
that
all
community
members
of
a
certain
level
need
a
private
place
to
chat
kind
of
behind
the
scenes?
B
B
D
That
your
point
is
right,
so
the
main
purpose
of
having
a
website
like
this
is
that
you
should
like
you
will
be
able
to
keep
track
of
all
those
things
that
we
have
done
right.
So
in
that
case,
if
you
want
to
discuss
something
personal,
then
we
could
use
slack
or
something
else.
So
that's
what
I
was
feeling.
B
Yeah
yeah,
that's
my
sentiment
as
well,
and
yeah
you're
right,
like
that's
a
large
part
of
the
lot,
the
reasoning
behind
why
we
why
the
site
was
created
in
the
first
place
was
to
because
we
chat
a
lot
in
slack
and
and
publicly,
and
you
know
so,
there's
some
private
chats
that
go
on
that's
a
natural
thing,
hopefully
most
of
the
chats
that
you
guys
that
we
all
have
are
as
public
as
possible.
Just
so
that
everyone
learns.
Everybody
gets
a
chance,
an
equal
opportunity
to
engage.
A
Okay,
so
by
the
time
I
was
just
looking
around
to
the
stats
from
discuss-
and
I
found
it-
we've
already
crossed
50
user
mark,
like
we
have
already
55
users
on
this
course
discussed
on
layer,
5
tile,
nice.
A
Yeah,
so
congratulations
install
to
all
the
community
members
because
it's
it's
possible
because
of
all
of
the
members
and
yeah
so
yeah.
If
you
can
scroll
down,
you
can
just
see
that
thing,
nice,
the
users
per
trust
level.
B
Oh
there
it
is
nice
I
was
just
trying
to.
I
was
just
looking
at
my
content
and
how
popular
my
content
is.
I
was
just
no
I'm
kidding.
That's
fantastic
yeah
good,
actually
like
the
like
to
to
the
earlier
point
about
being
open.
Like
you
know
like
right
now,
this
call
is
being
recorded
and
while
we
don't
want
to
leak
anyone's
personal
info,
but
some
anonymous
statistics
like
this,
this
is
you
know
something
that
josh
might
end
up.
B
You
know
over
time
and
end
up
sharing
more
broadly
because
it's
it's
a
community
forum,
so
you
know
to
all
of
you,
especially
you
that
are
discussing
and
and
assisting
here
it
becomes
interesting
to
see.
B
A
A
Screen
yeah
so
moving
on,
we
do
have
the
next
topic.
That's
by
us.
A
I
I
don't
remember
his
name,
so
it's
about
the
twitter
feed
on
discuss.
So
I
I
don't
think
it's
present.
Is
it
present
today.
A
A
So
yeah,
so
this
is
the
section
that
is
working
on.
This
is
the
embedding
the
twitter
timeline
on
the
discussion
forum,
so
he
has
already
done
this
on
the
staging
discuss
website.
So
this
is
basically,
as
we
mentioned,
for
testing
purposes
for
trying
out
new
stuff,
and
then
we
can
migrate.
This
changes
onto
the
discus.layer
fair
prototype.
A
So
if
you
guys
also
any
one
of
you
wants
to
have
like
think
that
there
should
be
improvements
in
any
design
layout
or
have
any
additional
components,
then
you
can
just
ping
me
I'll,
give
you
admin
access
to
the
staging
website,
and
then
you
can
bring
out
some
changes
that
we
can
reflect
on
our
discussion
forum,
so
the
tweet,
the
twitter
section
he
has
been.
He
has
implemented
this
with
the
use
of
I
like,
with
the
use
without
the
use
of
api.
A
He
has
made
a
component
to
fetch
data
directly
from
twitter
and
so
like.
There
are
a
couple
of
methods
to
do
this,
and
I
had.
I
admired
myself
seen
one
of
those
methods,
so
I
think
we'll
provide
him
feedback
on
slack
instead
because,
as
is
not
present
over
here,
so
basically,
if
any
one
of
you
want
to
just
look
into
or
want
to
learn
about
the
same
thing
you
can
just
visit
like
you
can
just
look
into
the
repo
from
which
we
are
getting
this
thing.
A
So
this
is
the
discourse
twitter
feed
component
theme
component,
that
is
created
which
is
being
used
for
generating
the
twitter
timeline
or
on
staging
discuss.
So
if
you
guys
want
to
have
a
look
into
it,
you
can
just
have
a
look
into
it.
So
yeah,
that's
broadly
for
that
topic,
and
I
guess
we'll
provide
him
feedback
on
slack
in
case
he's
not
present
yet
and
we'll
move
on
to
the
next
topic.
That's
by
nikhil
and
many
others
who
are
already
working
on
the
learn
ng.
A
So
just
to
give
a
brief
about
the
initiative
so
learn.
Ng
is
I'll
just
show
because
visuals
are
more
effective.
A
So
learn
ng
is
basically
an
initiative
to
have
learning
paths.
So
currently
we
already
have
a
section
or
a
collection
of
books
and
workshops
and
labs
that
are
category
instances
to
learn
working
with
mashri
and
other
service
meshes.
A
So
we
we
also
look
forward
to
have
learning
paths
through
which
you
will
have
the
entire
a
path
from
the
beginning
to
the
end
of
learning
things
regarding
mastery
and
or
other
service
meshes
so
nikhil
and
a
few
others
are
already
working
on
this
pro
project
and
you
can
see
the
progress
currently
on
layer.
Five
dot,
io
learn
ng,
so
we'll
discuss
on
what's
the
up
status,
update
on
the
thing,
so
thank
you.
If
you
can,
just
if
you
wish
to
share
you,
can
you
can't
share
this
game?
A
No
problem
with
that
yeah?
Okay,
so
yeah
everyone.
So
today
recently,
I
have
opened
a
new
epic
issue.
We
are
in,
like
the
designs
are
flowing
in.
We
have
here
the
designs
and
most
of
the
components
are
already
migrated
and
to
start
off
with
an
actual
complete
course.
I
recently
opened
an
epic
issue
which
would
simply
involve
you
to
move
data
from
one
of
the
already
present
repository
status,
sql
services
workshop
to
the
learn
site.
A
So
just
if
you
could
open
that
link
in
the
issue
page.
A
Yeah,
so
we
have
multiple
labs
over
here,
and
these
labs
will
represent
a
chapter
in
that
course,
and
each
lab
is
a
md
file
which
basically
has
all
the
details
to
how
to
set
up
the
services
issue,
service,
mesh
and
start
off
with
using
it,
so
any
use
anyone
who
wants
to
go
through
the
course
anyone
who
wants
to
migrate.
The
take
on
this
issue
simply
needs
to
convert
this
md
file
to
mdx
files
in
what
we
learn
site
and
it
will
be
ready
with
the
complete
course
for
sample
design
is
attached.
A
A
A
A
Okay,
so,
basically
we'll
be
opening
up
multiple
issues
after
the
course
gets
added,
like
the
sample
course
gets
added
so,
and
we
also
have
issues
revolving
around
the
react
thing
like
this.
This
issue
is
specific
to
the
data
migration.
It
won't
involve
much
of
react
knowledge,
so
you
can
do
it.
If
you
don't
have
any
expertise
in
react
as
well,
it
would
be
just
converting
md
to
mdx
and
having
few
components,
but
not
in
depth
react
knowledge,
but
there
are
other
things
where
a
little
react.
A
Knowledge
would
be
required
and
we
do
have
issues
or
we
do
have
components
around
them
where,
as
nikhil
mentioned,
chinma
is
already
working
on.
So
if
you
guys
want
to
take
up
those
issues
as
well,
you
can
just
ping
you
can
just
ask
on
websites
channel
on
slack
either
or
you
can
just
ping
nikhil
or
chinmay
or
me
will
just
guide
you
to
those
issues
and
yeah.
If
you
don't
have
access
to
the
sigma
project,
you
can
ping
any
one
of
us
me
or
nikhil
and
we'll
give
you
access
to
it
as
well.
A
So,
in
continue
in
continuation
to
the
topic,
there
is
a
status
update
from
anita
as
well
anita
is
present.
I
guess.
A
Yeah,
so
you
want
to
talk
about
what's
the
status
on
recent
improvements
on
the
learn,
ng
initiative.
E
Oh
yeah,
one
of
the
last
changes
that
we
made
was
add
the
call
call
to
participation,
of
course,
join,
discuss,
features
and
so
far
I
I
took
the
content
side
of
the
of
each
courses
of
the
courses
there,
but
I've
I'm
not
really
familiar
with
gas
fields.
So
I'm
really
having
a
hard
time
implementing
that
feature
and
that's
where
I
am
right
now.
E
And
yeah
those,
I
think
you
should
click
on
the
courses
there
does
the
parts
yeah
yeah
by
this
side,
the
content
area,
the
other
side,
the
left,
yeah.
E
A
Issues,
okay,
so
so
as
if
you
are
not
aware
so,
gatsby
is
basically
react
and
from
the
data
comes
from
graphql
queries.
So
if
you
are
familiar
with
it
or
want
to
learn
so,
as
I
mentioned,
there
are
issues
similar
to
one
which
anita
is
working
and
you
can
just
jump
on
those
issues
and
take
up
and
work
on
them
and
I
think
yeah,
that's
all
from
the
learn
engine
initiative
for
now.
B
A
To
add
this
topic
to
the
next
meeting,
so
just
a
brief
about
message:
ctl
docs!
So
these
are
the
these
are
based
on
j
kyle.
They
are
the
they
are
like.
You
can
just
visit
him
on
docs
dot.
A
Mystery
so
they
are
similar
to
the
mastery
docs
and
measuring
cpl
commands
yeah.
So
this
is
the
thing
I
guess
and
we
do
have
two
or
three
items
apart
from
the
ones
we
discussed,
but
we
don't
have
the
contributors
present,
so
I
don't
think
we'll
be
discussing
on
them.
So
moving
on
we
can.
We
can
just
discuss
on
the
improvements
that
nikhil
has
been
trying
to
make
on
the
get
nighthawk
website
and
the
mastery
docs
website.
A
F
Yeah
and
images
like
the
old
image
was
cropped
no
no
above
eyes,
yeah,
yeah,
okay
and
also
like.
If
you
go.
F
F
E
E
Someone
took
this
issue,
I
would
ask
him
how
he's
going
with
it.
A
E
All
right,
I
wanted
to
mention
something.
A
A
Yeah,
that's
a
nice
point.
I
guess
we
can
have
a
separate
tag
for
those
things
and
we
can
have
those
issues
listed
on
the
repo
itself
where,
like
we
do
have
the
tags
currently
showing
the
kind
or
area
area
test.
So
we
can
have
one
having
the
area
design
for
the
designers
yeah.
That's
a
nice
point.
I
guess
we'll
talk
about
it
and
we
can
implement
those
things
as
well.
A
D
A
Io,
where
I
have
seen
multiple
prs
open.
A
We
can
talk
about
it
as
well
nikhil,
if
you
want
to
talk
about
this.
A
Okay
and
the
so
I
guess
I
saw
multiple
of
them
have
already
been
approved,
but
are
waiting
for
merge
so
I'll,
look
into
it
and
I'll
do
the
required
things
for
them
and
yeah
so
good
to
see
you
taking
up
the
issues
and
by
yourself
and
making
those
changes
on
both
the
websites
and
yeah.
If
you
are
interested
for
the
react
gets
be
work,
then
you
are
welcome
out
there
as
well.
A
Okay,
cool,
okay,
apart
from
the
websites,
I
think
we
are
out
of
topics
today.
A
A
A
E
A
You,
okay,
then,
if
there
is
nothing
else
to
discuss,
so
we'll
be
winding
up
on
today's
meeting
and
looking
forward
for
multi
more
than
the
issues
and
more
time
we
can
spend
on
into
into
the
next
websites
meeting
the
next
monday
and
yeah.
So
I
think
this
is
because
we
do
have
less
number
of
issues
open,
so
we
get
less
topics
currently
so
we'll
try
to
open
up
more
issues
on
the
work
that
needed.
That
needs
to
be
done
and
we
can
have
the
things
for
the
next
meeting
yeah.