►
From YouTube: Layer5 Community Meeting (Nov 26th, 2021)
Description
Layer5 Community Meeting - November 26th 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,
great
hey
we're
about
three
after
let's
get
rolling,
so
I'm
gonna.
If
I
do
I'm
going
to
borrow
hosts
from
you
today,
if
I
can,
we
might
be
able
to
wrap
up
before
the
end
of
the
hour.
I'm
not
sure,
let's
see
see
how
much
there
is
to
talk
about
so
welcome
everyone
to
the
layer,
5
community
meeting
we
meet
every
week
on
friday
at
this
time.
A
It's
been
at
this
time
since,
since
we
started
meeting
so
it's
and
actually
I
think
it's
been
the
same
doc
since
we've
started
meeting.
So
if
you
go
back
to
the
very
beginning,
you
might
see
some
of
the
same
names.
You
might
see
a
lot
of
new
names
and
you'll
see
you'll
notice,
things
have
progressed
and
changed
and
we've
gotten
more
and
more
participation.
So
there's
about
about
20
of
you
on
call
right
now.
Well,
we've
had
some
community
meetings
where
we've
had
gosh.
I
don't
know
what
is
the
is
it
38.
A
Is
that
the
record?
Is
it
40?
I
don't
know
somewhere
in
there,
we're
going
to
the
community
is
going
to
continue
to
grow.
You
all
are
doing
some
really
interesting
things.
One
of
the
interesting
things
that
you're
doing
is
open
source.
There
is
coding
and
is
open
source
and
coding,
go
hand
in
hand,
open
source
and
other
things
also
go
hand
in
hand.
One
of
the
things
that
goes
hand
in
hand
with
open
source
here
is
learning
a
lot
of
learning
that
goes
on
here.
A
So
that's
good
okay,
so
as
we
get
going,
if
you
go
ahead
and
drop
your
name
into
the
attendees
list,
if
you
haven't
already
it's
nice
to
get
representation
also,
if
you've
got
a
webcam
pop
it
on
like
it's
really
nice
to
connect
with
you
all
one
of
our
traditions
here
is
to
explicitly
connect
with
any
anyone
who's
new
on
this
call
or
any
of
the
calls
that
we
have
the
first
time
you
join
one
of
the
calls,
that's
a
fantastic
opportunity
to
let
people
get
to
know
you
and
so
to
kick
us
off.
A
I
think
we
have
one
or
two
newcomers
varun,
you
might
be
our
winner
today.
Do
you
want
to
take
a
second
excuse
me,
take
a
second
and
introduce
yourself
and
say
hi.
A
Nice
yeah
very
good.
I
see
your
chat
if
you
have
audio
say
hi
that
way,
but
if
you
don't
keep
the
chat
coming.
B
A
Awesome
never
nice
to
meet.
You
did
you
by
chance.
I
don't
know
how
many
of
you
have
all
seen
this,
but
this
is
something
that
well.
Anyone
on
this
call
is
welcome.
To
help
represent,
represent
the
the
projects
that
go
on.
Speaking
of
the
cncf,
two
of
our
projects
are
in
the
cncf
and
and
the
other
project
nighthawk
that
we
work
on
is
well,
it's
really
advanced
in
context
of
the
cncf.
A
That
project
isn't
a
cncf
project
yet,
and
then
there
are
other
and
there's
a
bunch
of
other
projects
other
than
those
three
that
we
just
mentioned,
but
two
of
them
are
listed
here
and
I
had
recently
just
submitted
an
update
to
add
rust
and
c,
plus
plus
as
things
you
know,
languages
that
are
in
focus
for
measuring,
as
well
as
like
I
added
devops
on
here,
which
I
don't
think
we
see
listed
any
on
any
of
the
other
projects
and
the
reality
is
in
like
in
the
service
mesh
performance
project.
A
A
We're
gonna
need
to
be
running
some
benchmark
tests
here
soon
and
really
that
that
calls
upon
the
need
for
setting
up
kubernetes,
which
doesn't
have
to
be
complex,
but
then
using
mescheri
to
run
a
litany
of
different
types
of
performance
tests
and
so
we'll
be
using
the
cncf's
labs,
we'll
be
borrowing.
A
Well,
I
don't
know
maybe
20,
maybe
30,
of
their
servers
so
bare
metal
testing
and
that
one
of
the
engineers
from
intel
has
already
signed
up
to
help,
but
but
he
but
he's
gonna
need
help.
So,
just
by
a
random
example,
if
someone's
interested
in
helping
there,
please
just
message
good
way:
to
reinforce
some
of
your
devops
skills.
A
Okay
back
to
things
at
hand,
so
varun
introduced,
and
one
of
the
first
topics
that
we
have
up
is
well
it's
a
web-based
community
member
forum
who
would
like
to
speak
to
this.
C
A
C
Yeah,
so
basically
now
this
is
the
new
community
member
firm.
So
when
everyone
joins
the
community,
we
tell
them
to
fill
in
a
community
member
form
to
get
access
to
all
the
community
drives
and
everything
that
to
the
community
drive
and
everything
that
it
holds.
So
we've
been
using
a
google
form
till
now,
so
we
recently
switched
over
to
a
web-based
firm,
which
has
an
integromat
automation
which
passes
the
data
into
a
web
book
and
then
that
data
goes
into
a
google
sheet
and
then
into
main
gym
yeah.
So
this
is
how
it
works.
C
The
one
problem
that
we've
been
having
with
this
is
that
we
don't
have
validation
for
the
feeds.
So
if
there's
an
incorrect
like
it
happens
mostly
for
just
emails,
so
if
there's
an
inca
incorrect
format
for
the
email,
the
integromat
automation
stops.
I've
added
a
basic
validation
for
it.
My
pr
is
up
for
that,
but
I
think
there
are
better
ways,
but
there
are
better
approaches
to
validate
fields,
but
I'm
not
sure
how
to
do
that.
C
C
So
yeah,
so
this
is
like
the
site
is
built
on
gatsby
we're
using
formic
to
make
the
form.
A
Varun,
you
again,
you
might
be
the
lucky
winner
in
a
couple
of
ways
like
so
mario,
you
filled
in
a
google
form
which
really
should
have
had
like
the
the
same
questions.
The
community
felt
like
having
a
web-based
form.
That's
on
the
layer.
5
site
was
a
bit
more
classy
and
provide
a
little
more
control,
a
better
experience
about
explaining.
A
Maybe
why
we're
asking
for
your
profile
photo
like
what
are
we
gonna
do
with
that
and
trying
to
understand
who
you
are
and
why
you're
here?
A
So
a
lot
of
you
had
done
google
form,
which
makes
a
lot
of
sense.
Some
of
you
have
been
here
for
for
quite
a
while,
and
so
that
that
google
form
has
been
deprecated
like
a
dk,
said
the
layer,
5io
site,
it's
been
contributed
to
by
a
little
over
a
couple
hundred
people
and
it's
a
static
content
site.
It
uses
gatsby
as
its
framework
and
this
form,
and
so
the
gatsby
is
uses
react
as
its
framework.
A
A
A
A
And
when
you
complete
the
form
well,
this
is
a
static
site.
So
there's
no
server.
That's
running
this
site.
These
are
just
files,
static,
html
files,
css
files
that
are
sitting
out
on
github
github
pages.
Actually
well,
then
so
is
github
processing
the
form
submission,
no
there's
any
number
of
other
ways
that
you
could.
A
You
know
process
a
form
like
this,
and
so
the
community
here
has
chosen
to
use
well
like
a
low
code,
automation,
engine
or
like
workflow
engine,
and
so
there's
an
active
scenario
out
here
that
the
community
managers
have
access
to
to
review
and
fix
and
update
a
lot
of
you
have
been
on
the
receiving
end
of
this
particular
activity.
So
if
you
filled
in
the
google
form,
if
you
filled
in
your
member
form,
then
you
will
have
been
processed.
A
You
should
have
a
small
little
process
tattoo
with
your
community
member
id
somewhere,
and
so
I
just
clicked
submit,
and
so
I
think
I've
just
been
recently
processed.
But
this
is
what
it
looks
like
there's
the
web
hook
that
fires
and
it
goes
through
making
sure
that
people
get
permissions
to
the
community,
drive
and
add
it
to
the
right
mailing
list,
so
that
they're
they
have
access
to
resources
and
so
aditya
and
zayn
and
nikhil
and
a
bunch
of
other
folks
have
been
involved.
A
We
had
long
held
off
on
too
much
automation.
We
didn't
want
to
make
it
impersonal,
as
people
join
like
it's.
It's
important
to
us
that
you're
all
here
and
understanding
who
you
are
and
what
you're
here
for
and
trying
to
get
you
engaged
in
the
right
way,
and
so
we
didn't
want
that
to
be
too
robotic,
as
the
community
has
grown
to
a
little
over
2
000
people.
A
It's
been
a
ton
of
effort,
and
so
some
of
that
has
just
been
automated
over
time
because
because
there's
only
so
many
maintainers,
only
so
many
community
managers
to
go
around
so
so
speaking
of
community
managers
after
the
community
call.
Today
there,
a
few
of
you
in
the
community,
have
been
identified
and
asked
to
be
caught
to
put
on
a
community
manager
hat
in
an
official
capacity,
and
so
we'll
have
a
training
for
those
individuals.
A
C
Yeah
sure
so
yeah,
so
even
for
the
community
handbook,
we
were
using
a
google
doc,
like
it's
a
google
doc
that
probably
everyone
receives
when
they
join
slack,
there's
a
message
that
comes
with
this
google
doc.
So
this
has
also
been
moved
to
the
layer
5
website.
C
Yeah
yeah.
C
It
and
it
actually
consists
of
like,
like
the
later
two
points
that
are
here
like
the
repository
overview
and
the
community
guide,
even
the
newcomers
guide,
all
of
them
are
actually
present
in
the
community
handbook
as
well.
So
it's
like
a
good
consolidation
of
everything.
A
A
Well,
I
don't
know
how
you
you
say
this:
there
were
a
number
of
native
english
speakers
that
helped
create
this,
but
so
how
do
you?
So?
I
don't
know
the
english
needs
a
healthy
review.
A
I
guess
it's
just
always
like
so
there's
going
to
be
any
number
of
defects
in
here,
and
it
would
be
good
to
go
over
one
of
the
things
too,
that
I
think
is
outlined
in
here,
but
really
wasn't
much
discussed
and
needs
a
probably
a
lot
more
thought
is:
there's
an
inherent
kind
of
contributor
ladder
to
the
various
roles
that
happen
within
the
community
and
what's
expected
of
them
and
and
how
to
go
about
attaining
such
a
role,
what
it
means
to
sustain
the
role
and
there's
actually
a
number
of
more
roles
than
what
we
have
listed
but
anyway,
so
this.
A
Please
point
out
any
issues
that
you
find
it's
a
little
bit
interesting.
So
we
have
a
projects
page,
okay,
good,
but
then
we
have
a
repository
overview.
So
this
okay.
So
this
is
just
a
simple
index
and
then
the
projects
page
really
explains
them.
Okay,
all
right.
Somebody
has
their
hand
raised
mario.
D
A
Think
yeah
yeah,
I
think
so
because
yeah
right
there's
an
implicit
snooty
hierarchy
that
I
think
people
might
interpret
from
there.
It's
probably
not
that
it's
probably
a
nuanced
notion.
We
want.
D
To
avoid
like
giving
the
image
of
a
corporate
corporate
environment
and
more
of
a
yeah,
there's
always
a
hierarchy,
but
I
think
journey
is
more
accurate,
yeah
like
in
there
it's
journey,
so
it's
just
maybe
to
update
the
community
handbook
page.
D
D
A
A
That's
actually
that'll
be
a
little
bit
of
a
topic
of
discussion
for
a
few
of
the
community
managers
kind
of
going
through
I'm
training
later
today.
There's
you
know
this
is.
I
think
this
is
of
interest
to
many
of
you,
and
so
maybe
we'll
take
take
a
quick
look
at
kind
of
a
graphical
view
of
what
that
journey
looks
like
we
generally
don't
public.
Well,
this
isn't
published
and
we
generally
don't.
A
We
occasionally
show
this
once
every
few
months,
but
it's
but
like
really
trying
to
curate
the
community
and
curate
the
experience
that
people
have
or
try
to
it
takes
a
lot
of
time,
but
we
try
to
pay
attention
to
where
people
are
at
and
whether
or
not
they're
getting
fed
they're
learning.
They're
they've
got
they've
found
a
foothold
in
the
community.
A
A
We
ask
a
ton
of
the
of
interns,
just
ask
barak,
ashish
and
others
interns
that
are
on
the
current
interns
that
are
on
the
call,
there's
no
mercy
and,
as
such
those
individuals
are
being
hardened.
I
think
fairly
well,
they're
they're
doing
some
impressive
things
at
this
point,
so
anyway
we
take
the
internships
really
seriously.
I
guess
is
what
I'm
saying
and
to
be
forthright
like.
A
If
that's
a
topic
for
any
of
you
about
lfx
internships,
the
there's
an
faq
about
like
how
to
land
one
and
the
gist
of
it,
is
very
simply
engage
consistently
and
significantly
like
we've
got
more
internships
open
than
we
have
maintainers
to
or
mentors
to
help
people
you
know,
take
them
through
an
internship.
A
So
like
force
our
hand,
the
internships
are
available
force
our
hand,
make
it
so
much
that
you're
here
and
being
helpful,
and
we
can.
We
like,
we
only
want
to
reinforce
what
you're
doing
don't
come,
yeah
come
and
get
it
don't
come
and
say:
hey,
I'm
interested
and
I'd
like
it
like
prove
it
get
involved
in
the
project.
Be
impactful
show
that
you're
interested
show
that
commune
well
with
the
community
and
that
you've
found
an
area
to
call
home
we'll
make
an
internship
around
that.
A
A
This
was
more
about
resourcing
the
individual
and
helping
them
kind
of
uplifting
them
and
recognizing
them
as
they
go
and
sort
of
as
they
go,
and
then
their
responsibility
increases
so
too
should
their
recognition
and
their
uplifting
of
the
activities
that
they
do
and
so,
and
so
too
should
their
direct
representation
of
like
of
measuring,
of
nighthawk
of
s
p
of
layer.
Five,
like
those
two
things
you
know
the
individual
and
and
those
two
things
reflect
very
well
on
one
another
and
what's
good
for
one
is
good
for
the
other.
So.
A
All
right
good
deal
the
venue:
do
you
want
to
talk
about
this
next
topic.
E
Surely
so,
if
you
go
to
that
link,
you
will
see
that
cncf
offers
quite
quite
a
lot
of
online
programs.
So
as
layer
5
is
a
silver
member
of
cncf
and
both
mastery
and
service
mesh
performance
are
cncf
projects.
E
We
get
access
to
quite
a
lot
of
these
programs,
one
of
which
is
a
webinar
and
the
others
include.
Live
events
live
events
on
cncf
twitch
channel,
so
so
a
while
back.
We
recorded
a
webinar
on
missouri.
E
And
it's
about
an
hour
long
and
it
is
on
youtube.
So
after
that
we
we
haven't
really
looked
into
recording
new
webinar.
So
there
is.
There
is
like
a
lot
of
open
need
or
for
there's
a
lot
of
a
open
area
for
people
to
come
in
and
participate,
and
they
and
like
we
can
decide
on
what
topics
we
can
present
in
these
webinars
or
maybe
we
can
even
host
live
sessions
on
twitch.
E
So
yeah
like
I
just
wanted
to
open
up
the
floor
for
discussion
on
some
of
the
topics
that
we
could
probably
take
a
webinar
on
or
take
a
live
session
on
yeah.
So
if,
if
you
have
any
any
such
idea
or
if
you
are
interested
in
being
part
of
such
an
event,
feel
free
to
reach
out.
A
Very
good,
all
right
next
topic,
who
wants
to
take
the
mystery
v060
topic,
maintainer
like
budkash
or
someone
who's,
been
really
focused
on
it,
like
ashish
or
barak
or
husseina,
or
a
combination
of
all
of
you.
Maybe
what
is
it?
What
does
it
mean
that
we've
got
a
release
candidate
now.
A
So
good,
well
I'll
tell
you
what
it
means.
It
means
that
we've
been
well.
It
actually
one
one
way
of
looking
at
this.
If,
if
you
go
out
to
mesh
redox
mesh
redox,
some
of
it
most
of
it
is
hand,
curated
information
that
the
contributor
contributors
here
have
written
down
and
and
try
to
organize
into
flowing
thought
that
isn't
always
successful.
A
The
sum
of
the
documentation
is
auto
generated
and
automatically
published,
and
really
that
aspect
of
the
there's
a
couple
of
areas,
some
of
the
api,
docs
and,
and
also
the
releases
and
the
release
notes.
So
when
this
release
candidate,
one
was
really
was
merged
35
minutes
ago
or
whatever
it
was.
These
the
same
release
notes
that
you
see
on
github
happen
here,
and
these
are
the
changes
from.
A
That's
a
lot
of
release,
notes
the
there's
a
number
of
you
in
the
community
who
are
who
already
have
and
are
writing
a
release
announcement
as
a
collection
of
all
of
the
new
features
that
have
come
from
dot,
five
to
dot
six,
and
so
the
release
candidate
notation
here
means
that
the
maintainers
and
other
contributors
generally
feel
like
we've
achieved
the
mission
of
what
dot
6
is
and
that
we
have
the
p1
bugs
the
highest,
the
egregious
bugs
well
in
hand,
and
that
it's
time
to
put
out
a
build
that
could
that
could
potentially
qualify
as
a
dot
six
release.
A
So
we
will,
as
a
community,
make
a
bit
of
noise
and
tell
a
lot
of
folks
about
dot
six
v0.6
when
it
comes
out,
so
we
want
to
make
sure
that
they
have
a
quality
experience.
So
the
release
candidate
is
a
way
of
signaling
that
we're
in
a
position
where
we're
hardening
the
code.
Not
a
lot
of
changes
are
going
on.
Just
bug
pictures
we're
landing
the
plane
plane
is
descending
right.
Now
the
runway
isn't
too
far
away.
A
March
end
of
march
april
may
june
hi
holy
smokes.
It
takes
a
long
time
to
well.
There
was
a
lot
in
the
dot
six
release
by
the
way,
there's
a
lot
to
talk
about
some
fundamental
architectural
changes
by
like
in
the
way
in
which
measury
manages
service
meshes.
A
lot
of
that
has
to
do
with
pattern.
Management
service
mesh
patterns
are
a
new
concept
still
emerging
as
we
go
to
do
the
dot
six
release.
A
This
page
probably
needs
a
little
bit
of
update.
I
think
this
is
still
accurate,
still
under
active
development,
but
an
emergent
area,
a
really
powerful
area.
A
One
of
one
of
the
users
earlier
on
samir
he's
been
on
any
number
of
mesh
recalls
and
he
was
pointing
out.
He
was
having
some
trouble
provisioning,
linker
d
using
meshri
and
the
operations.
The
the
code
that's
being
executed,
as
he's
provisioning,
linker
d
well,
is,
is
not
using
patterns.
It's
using
sort
of
this.
This
meshery,
this
mesh,
ops,
v1
mesh
ops,
v2,
is,
is
a
pattern-based
way
of
managing
service
meshes,
and
so
we
are
close
to
flipping
the
flag
like
being
rid
of
meshop's
v1
and
moving
to
measure
up
to
v2.
So.
A
Okay,
if
some
of
this
is
still
new
to
some
of
you
about
service
mesh
patterns,
it's
one
way
of
diget
comprehending
this
rocking.
It
is
through
some
effort
that
well
that
I
think
an
email
was
sent
out
about
recently.
It
was
this
notion
that
there'll
be
a
service
mesh
patterns
catalog,
where
commonly
used
functions,
features
of
a
mesh
can
be
plucked
from
a
catalog
and
then
deployed
into
people's
environments,
and
so
this
is
the
sort
of
a
draft
of
what
that
would
look
like
the
mock-ups
for
what
that
looked
like.
A
A
A
A
0.6
features
there's
an
open
issue
that
highlights
where
you
can
participate,
not
only
an
open
issue,
but
there's
also
an
open
google
doc
that
identifies
the
various
features
and
then
what
needs
written
up
zane
if
you
have
a
link
to
either
the
two
of
those
please
do
share
in
the
doc
or
enchant.
A
Yep,
so
I
did
you
had
a
great
question
about.
You
know
the
fact
that
the
mesh
redox
are
now
versioned.
So
this
is
a
relatively
new
drop
down
here.
So
just
as
soon
as
the
actual
v0.60
release
is
made,
a
snapshot
of
the
docs
should
be
taken
and
that
that
will
be
the
permanent
archive
for
b050
and
what
will
be
latest
will
represent
v060.
A
A
All
right!
Well,
that
means
you
know
if
that's
about
to
go
out
the
door.
What
does
v070
look
like?
Did
everyone?
That's
on
the
call,
get
an
email
like
within
the
last
couple
of
days
that
pointed
to
v070
roadmap
and
was
at
soliciting
some
feedback?
A
There's
kind
of
two
quick
ways
of
reviewing
what
you
know:
the
community,
what
we
collectively
considered
to
be
the
upcoming
roadmap.
One
is
in
mark
down
here
but
another,
but
this
only
captures
like
part
of
the
picture
really
the
other
way
of
looking
at
you
know,
understanding
what's
forthcoming
and
what
what
would
be
a
focus?
There's
a
this
deck,
meshery
architecture,
deck
put
a
link
to
it
out
here.
A
E
Here
we
are
stuck
at
33
right
now:
okay,.
A
So,
okay,
so
code
quality.
Isn't
you
know
it's
something
that
needs
to
be
planned
for
each
of
the
components?
This
is.
This
is
what
dot
six
looks
like
this
is
what's
proposed
for
dot.
Seven.
A
A
So,
as
we,
you
know,
look
forward
to
a
1.0,
we
want
to
set
some
of
those
coverage
goals,
so
this
is
dot
nine
getting
closer.
A
Anybody
have
early
feedback
feedback
on
b070.
There
will
be
another
email
that
goes
out
call
soliciting
feedback
and
probably
will
set
aside
time
on
the
weekly
measuring
development
call
to
go
through
more
of
this
there's
a
lot
in
there,
though,
so
something
good
to
digest.
Asynchronously
ask
some
questions
about
if
you're
on
the
call
and
you're
looking
to
contribute
to
this
project,
which
is
you
know,
one
of
a
number
of
projects,
but
I
encourage
you
to
peruse
the
specs
comment
on
the
specs.
A
A
As
we
take
just
a
bit
a
brief
intermission
here,
it's
well
actually,
I
think,
as
we
reach
the
end
of
our
topics,
it's
actually
a
great
time
to
say,
there's
a
couple
of
you
who
are
new
on
today's
call.
I
think
so
varun
got
to
introduce
earlier
it's
nice
to
meet
varun,
but
we
might
have
a
couple
of
others.
I
mean
anybody
else
new
on
the
call
today
love
to
hear
hear
from
you
just
to
ask
that
you
introduce
yourself
so
junaid
and
michael,
have
you
gotten
a
chance
to
introduce,
say
hi.
A
Yes,
yes,
you
junit,
yes,
you
micah,
oh,
if
your
audio
isn't
working
or
you
can't
speak
right
now,
just
say
hi
in
the
chat.
Introduce
yourself.
A
So,
oh
I've
got
one.
So
this
is
a
community,
not
not
a
mesherie.
We
kind
of
measure
is
our
biggest
project,
so
that's
the
one
we
kind
of
we
let
it
let's
let
it
permeate
a
community
meeting,
because
there's
so
much
going
on
something
that's
relevant
to
all
of
you
and
if
you've
done
anything
here
code
or
not,
I
think
it's
a
great
opportunity
to
be
proud
of.
A
Try
to
find
a
link
to
this,
so
we've
got.
You
know
upcoming
event:
cubecon
china.
What's
going
on
one
of
the
mesh
mates,
meshmate
anita
she's,
giving
a
talk
on
how
to
adopt
a
service,
mesh
and
she's
talking
about
measuring,
so
pretty
cool.
That's
pretty
awesome.
We'll
also
have
another
talk
about
things
that
that
this
community
does
inside
of
the
technical
advisory
group
for
network.
A
They
changed
the
they
might
have
changed
the
link
to
it.
We
want
to
find
it,
though,
because
because
it
you
can,
you
can
review
the
slide
deck
in
advance
of
it
actually
being
announced,
and
I
think
you
might
be
pleasantly
surprised
by
what's
in
the
deck.
A
The
deck
is
out
there
already
go,
take
a
look
at
the
service
mesh
working
group-
oh,
that
looks
nice.
That's
a
okay!
Some
of
you
all
worked
on
publishing
in
an
ieee
magazine.
This
is
actually
this
talks.
A
lot
about
meshi
and
surface
mesh
performance.
That's
pretty
cool!
The
other
part.
That's
pretty
cool
is
on
this
deep
dive.
I'll
just
show
you
one
slide.
A
A
D
Just
a
question
from
the
layer,
five
io
home
page:
how?
How
would
someone
look
at
the
contributor
handbook,
like
yeah.
A
That's
a
great
yeah,
so
so
somebody's
here
that
they
generally
would
nav
probably
to
this
community
section,
but
there's
no
direct
link
to
the
handbook
itself
and
that's
intentional,
because
we
haven't
really
gone
through
the
handbook
with
a
fine-tooth
comb,
but
it
just
as
soon
as
we
do
very
shortly.
Like
part
part
of
that
is
what
mario
is
just
doing.
That's
part
of
combing
through
it.
It's
like
the
open
question.
A
D
Maybe
in
the
resources,
once
you
click
on
see
all
newcomer
like
in
the
bottom
there's
a
yellow
yup
that
one,
so
you
click
there.
It's
not
found
there
right
or
is
it.
A
E
D
I
can
open
up
another
issue
for
that.
A
That'd
be
great
yeah,
it
yeah,
because
this
newcomers
page
it
is
linked
right
right
here.
So
we
do
expect
people
to
get
to
this.
One
pretty
prominently
and
yeah
that
that
centralized
resource
should
be.
C
Actually,
there's
an
issue
already
opened
on
that
we're
still
in
like
the
works
of
designing
a
call
out
for
the
handbook
and
since
because
I
think
it
was
like,
like
everyone
thinks
that
the
mega
menu
is
too
filled
up
to
like
put
in
another
like
another
option,
therefore
handbook
it
would
probably
like
look
really
bad
over
there.
So
we
are
still
designing
a
call
out
that
that
would
probably
go
on
the
resources
page
or
on
the
community
page.
A
And
so
by
by
call
out
for
everyone's
reference.
I
think
this
is
an
example
of
a
call
out
yeah
yep.
C
A
Yep
yeah,
please
do
and
mario.
If
you
have
ideas
as
you
go
like
it
might
be,
that
there
needs
to
be
a
hyperlink
here
to
see
the
handbook
or,
like
you
know
it,
you
know
it
probably
doesn't
hurt
like
like
like
if
we're
gonna
error
on
one
side
or
the
next,
we
should
probably
err
on
too
many
links
to
things
rather
than
too
few.
D
C
D
D
Guidelines
for
opening
issues
yeah
it's
in
the
chat
in
zoom,
so
I'm
just
wondering
if,
like
any
labels,
that
should
get
added.
A
Yeah,
that's
a
great
question.
That's
a
really
good
question.
So
when
you,
when,
when
any
of
you
go
to
create
a
new
and
you're
all
welcome
to
create
a
new
issues,
suggest
changes
identify
problems.
You
know
I
would
suggest
by
the
way,
if
you
create
an
issue
just
before
spending
10
days,
working
on
a
thing.
D
Make
sure
it's
there's
no
issue
open
already.
A
Well,
yeah,
there's
that
and
also
make
sure
that
that
it's
a
desired,
that
that
people
agree
that
it's
a
defect
or
that
that
people
agree
that
it's
a
desired
change
just,
but
that
doesn't
mean
you
shouldn't
open
the
issue
like
open
the
issue,
but
just
but
then
before.
D
Investing
work
on
it
or
contributions
to
fixing
it
right
right,
like
get
a
consensus
of
if
it's
seemed
as
relevant
or
important,
yeah.
A
A
Oh,
oh,
that,
oh
that's
a
defect
hold
on
and
you
know
what
it's
actually
not
it's
like.
We
work
with
so
many
we
we
didn't
intend
to
like
list
them
all.
It's
not
intended
to
be
complete,
and
so,
but
so
a
lot
of
times
like
we've,
had
three
or
four
or
five
people
open
issues
on
this.
D
A
So
that's
a
great
example
of,
like
you
know,
just
before
people
invest
but
but
to
your
other
question,
mario
yeah,
sometimes
a
suggest
a
change
or
a
suggestion
falls
neatly
into
a
pre-defined.
A
D
A
And
seeing
this
is
like
a
choice.
A
Yeah,
here's
an
appropriate
label
like
the
what
type
of
shore
is
it
or
what
area
does
that
chore
fall
into
you.
A
No,
that
can
be
that
could
be
really
good
actually
sometimes
like.
That
is
the
point
of
the
issue
like
like
you're,
actually
saying,
and
so
some
of
the
like,
like
you
know,
maybe
I
wonder
if
this
feature
request,
like
some
of
we
use
templates
issue
templates
across
all
the
repos
and
they're
generally
consistent,
but
so,
but
not
always,
some
of
them
will
have
a
section
that
that
says
that
says
implementation
and
also
says
like
mockups
and
also
says
like
acceptance
criteria
and
like
yep
to
the
end.
A
A
Okay
but
yeah
dropping
mock-ups
or
screenshots
or
recordings
it's
great
mario's
touching
on
some
great
questions
about
issue.
Triage
is
kind
of
another
one.
A
If,
if
you
look
at
you
know
some
of
the
projects,
the
issues
can
go,
you
can
go
really
far
back
at
least
recently
updated
if
we
sort
by
that,
it's
like
well
wow
looks
like
this
character
has
got
this
old
one,
and
so
the
reason
I
bring
this
up
is
to
say:
hey,
you
know
it's
occasionally
appropriate
to
like
bump
this
guy
and
say:
are
you?
Are
you
done
squatting
on
this
or
like
you're
gonna?
Do
something
here
and
one
of
the
ways
to
sort
of
politely
do
that?
A
But
this
is
open
for
all
of
you
and
to
do
it
politely,
you
could
do
something
like
there's
a
few
automations
that
we
have
around
labels.
It
isn't
always
just
about
categorizing
things.
Sometimes
these
labels,
they
affect
release,
notes.
A
These
labels
will
invoke
a
small
automation
like
you
might
just
want
to
kindly
remind
this
person
that
so
so,
if
you
label
it
with
issue
remind
and
then
all
of
you
who've
been
invited
to
the
github
org,
like
mario
you're,
entitled
to
empowered
to
do
this,
and
so
here
here
in
the
moment,
I
would
expect
there'll
be
a
bot
come
up
there.
He
goes
hey,
it's
been
a
while.
D
A
A
And
so
we
should
probably
have
those
described.
A
Yeah
and
or
and
yeah,
and
we're
right
right
exactly
like,
because
because
your
journey,
an
individual's
journey
might
be
focused
in
one
area
or
on
one
role
versus
the
next
and
so
like
in
part.
What
navindi
was
calling
out
earlier
on?
The
call
was
kind
of
falls
into
this
between
digital
marketing
and
kind
of
community
ambassador,
which
is
to
say,
hey.
A
There
are
these
prominent
venues
hosted
by
the
cncf
that
are
open
to
us
for
the
projects
that
we
do
and
we're
not
we're
not
using
up
all
of
our
credits
or
like,
like
more
of
that,
is
open
to
us
and
so
yeah
that,
like
that
type
of
thing,
falls
into
these
roles.
And
so,
but
we
don't
describe
those
roles
in
the
community
handbook,
and
so
we
should
and
then
and
some
people
yeah.
D
Maybe
like
some
drop
down
where
the
visitor
or
the
page
can
see
those
different
descriptions,
I
don't
know,
I
think.
A
A
Yeah,
actually
one
is
to
is
that
inside
of
the
github
process,
doc,
we
should
it's
probably
the
appropriate
place,
to
document
the
fact
that
these
automations
are
available
to
us
another.
Another
probably
issue
to
open
is
that
these
roles,
only
three
of
these
roles
are
described
or
like
what
is
it
you
know?
Well,
I
guess
this
is
a
little
bit.
I'm
kind
of
I'm
this
is
this,
isn't
exactly
calling
out
the
roles
but
somewhere
in
there?
A
We
should
describe
the
fact
that,
like
people
can
become
a
community
manager,
they
can
be
a
community
ambassador.
What
does
that
mean?
What
does
it
look
like?
What
does
it
mean
to
say
that
you're
interested
in
focus
on
devops,
and
how
would
you
get
involved
in
those?
How
do
you
look
for
those
things
there
yeah,
so
an
open
issue,
probably
on
further
describing
those
in
the
handbook
would
be
good.
A
Cool
all
right
and
varun
has
a
question.
You
know
hey,
why
don't
we
have
only?
Why
do
we
have
a
translation
in
the
measuring
docs,
but
only
for
one
language
and
yeah?
That's
a
great
question
like
hey.
What's
so
special
about
spanish
anyway,
I
I
say
that
I
say
that
with
the
most
offense
aimed
at
mario
and
that
is
yeah,
there's
a
great
there's,
a
great
question.
Actually
it's
just
happenstance.
It's
just
the
notion
that
we've
given
over
the
last
three
years
we've
participated
in
a
mario.
A
A
Actually,
maybe
just
really
quick
answers
like
hey,
because
spanish-speaking
people
showed
up
and
said
it'd
be
nice
to
have
a
translation.
I
said
that'd
be
great
and
that's
why
that's?
Why
there's
a
a
spanish
translation,
varun,
that's
a
varun
that
that
does
mean
that
there's
prior
art
you're,
like
prior
example
for
building
in
support
for
other
languages
as
well.
D
Sure
so
can
you
guys
see
the
screen?
You
can
well
yeah
very
quickly,
so
basically
there's
this
open
source
event.
So
it's
like
open
source
software
contributors
summit.
It's
made
every
year,
you
have,
you
know
some
sponsors,
and
so
I
think
it's
oriented
for
latin
america.
You
know
everywhere
where
people
speak,
speak
spanish
and.
D
Well,
yeah,
basically,
this
yearly
event
a
actually.
This
is
how
I
got
got
to
know
of
measuring,
so
they
have
different
sessions
and
I
believe,
yeah,
here's
the
measuring
one
that
was
held.
D
I
think
they
were
covered
more
in
the
documentation
written
in
jekyll
and
but
but
also
a
cypress,
end-to-end
testing
or
end-to-end
functional
testing,
and
so
I
found
that
very
interesting
and
anything
you
want
me
to
focus
on
about
the
translations
right.
A
D
D
I
believe
this
is
where
the
yup
measuring
dog's
lips
in
and
well
there
should
be
some
instructions
for
trans
nope
yup.
This
is
all
I
know,
sorry,
but
but
I
just
know
yeah
there's.
You
know
there's
certain
workflows
to
contribute
in
in
translations,
but
that's
all
anything
you
like
to
add.
A
Yeah
the
I
don't
know
that
yeah,
that's
a
great
great
point
like
that's
another
good
issue
to
raise
is
that
I
don't
think
that
there's
any
explicit
document
guides
written
as
to
how
to
provide
translation
in
any
language.
The
the
theme
that
we're
using.
D
Here,
yeah
sorry
that
theme
go
ahead
box.
A
A
A
Mandarin,
as
a
translation
is
a
great
suggestion
from
navendu
there's,
a
number
of
chinese
chinese-speaking
folks
that
are
using
or
looking
at
measuring
is
helpful.
A
I
also
recognize
say
this
that,
like
it's
one
of
those
things
where
oh
it's,
the
translated
language
will
always
perpetually
be
out
of
date.
It's
just
the
more
content,
it's
kind
of
like
docs
like
the
more
docs
you
have
the
more
out
of
date.
They
are
just
as
a
know.
A
Everyone
has
the
best
intentions
and
then
but
yeah,
there's
some
prior
art
to
look
at
in
terms
of
potentially
using
a
framework
for
those
translations
right
now.
What's
happening
is
there's
mostly
just
a
copy
stored
separately
like
it
is
fairly
a
simple
and
straightforward
way
of
doing
it,
and
that
would
probably
suffice
to
continue
in
the
existing
path.
A
Cool
okay,
hey
we're
over
time!
It's
been
nice
to
see
you
all.
Some
of
you
will
see
here
in
just
a
bit
for
some
community
manager.
Training,
otherwise
go
go
work
off
that
turkey,
I
guess
at
least
for
those
that
stuff
their
faces
over
thanksgiving.