►
From YouTube: Layer5 Community Meeting (May 1st, 2020)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
C
D
E
Thought
thought
oh
yeah.
D
D
A
E
D
F
D
D
All
right
there,
everybody
welcome
to
the
Mestre
community,
call
Friday
May
1st
well
gosh.
Well,
what's
the
4th
gonna
be?
Is
that
Tuesday
boy?
Oh
that's
Monday,
boy,
that
that's
we'll
have
all
kinds
of
jokes,
I!
Guess
on
the
CI
Working
Group
about
the
4th,
all
right,
hey
some
housekeeping
items,
I
put
the
link
to
the
meeting
minutes
into
the
chat.
D
Help
make
a
decision
if
we've
got
if
we
need
to
have
a
tiebreaker
or
if
we
can't
figure
out
how
to
how
to
go
forth
on
something
we
might
have
voting
rights,
and
so
part
of
those
voting
rights
would
be
it'll,
be
a
really
convoluted
thing
or
it
would
be
based
on
contribution
and
part
of
how
contribution
is
measured
is
yeah
it's
code,
but
not
clearly,
not
always
actually
not
doing
any
code
is
just
fine.
Just
showing
up
at
a
meeting
is
contribution
as
well.
D
Writing
a
blog
post
talking
about
it
using
it
providing
feedback.
You
know
these.
All
of
those
things
count
how
they
count.
I,
don't
know,
that's
the
complicated
part.
My
the
point
is
meeting
attendance
will
be.
It
will
be
considered
as
well
so
good
to
have
a
record
of
that.
It's
actually
been
a
little
bit
of
a
discussion
in
the
community.
D
That
said
whether
or
not
that
individual
is
active
in
the
community
is
maybe
something
to
signal
here,
because
actually
this
illness
represents
only
a
fraction
of
those
who've
contributed,
and
so
there
are
forthcoming
profiles
to
be
put
up
and
maybe
and
maybe
signaling
who's
active
who's,
not
where
we've
begun
to
establish
some
working
groups
and
who's
leading
those
groups
and
we've
begun
to
establish
some
roles
and
things.
So
there's
just
there's
a
lot
of
work
to
be
done
in
the
community
about
organizing
ourselves.
D
So
all
of
that
to
say,
if
you're
on
the
call
it's
like
your
name
down,
that
would
be
nice
outside
of
that.
The
other
housekeeping
notes
are
that
we
much
like
it
all
other
open
source
called,
not
all
of
them,
but
a
lot
about
other
calls
and
we
record
ours
and
post
them
on
YouTube,
so
that
you
can
look
back
at
them
and
laugh
at
yourself
for
the
silly
things
you
said
and
how
funny
your
voice
sounds.
D
D
So
there
are
a
few
of
us
who
are
new
today,
which
is
fantastic,
because
there
are
a
couple
of
us
started
in
new
we're
gonna
do
a
couple
of
things:
one
we're
gonna
put
you
on
the
spot
and
ask
you
to
introduce
yourself
and
that's
our
way
of
getting
to
know
you
and
making
you
feel
uncomfortable
at
the
same
time.
So
now,
I'll
also
note
that
there
are
about.
D
So
I
mentioned
that
to
say
that
on
this
meeting,
the
the
agendas
of
those
individual
meetings
are
slightly
different.
This
one
is
really
broad
scoping
in
nature.
We
tend
to
have
people
from
various
projects
presenting
on
interesting
technologies
in
the
ecosystem,
so
some
of
the
announcements
and
things
that
we
speak
to
are
aren't
necessarily
are
intentionally
not
confined
to
its
communities
specific
stewardship,
but
but
rather
things
that
are
happening
in
and
around.
D
Very
good,
okay
with
that,
if
you're
new,
today,
or
rather,
if
you
haven't
been
on
this
particular
community-
call,
if
you
would
take
a
moment
to
introduce
yourself,
I'm
gonna
call
out
some
names
to
the
extent
that
I
can
read
them
and
so
Nitish
do
you
want.
You
want
to
say
a
few
words
get
introduced.
H
Hey
guys,
this
is
my
first
community
call
that
I'm
really
excited
to
be
part
of
her
and
following
Lee's
work
and
in
a
big
fan
of
its
new
up
and
running
his
book
with
Zack,
fortunately
didn't
get
a
chance
to
meet
Lee
at
cube
on
North
America
about
me.
I
am
in
the
telco
domain,
specifically
in
the
5g
domain,
and
5g
is
all
cloud
native,
so
I'm
a
technology
architect
at
a
firm
networks.
Now
Microsoft,
no
microsoft,
subsidiary,
no
I
work
on
all
things.
D
D
D
All
right,
we
also
have
probably.
I
D
D
J
Women,
this
is,
nothing,
must
fall
good
to
be
part
of
your
part
of
the
community.
Coming
to
my
experience,
I
have
our
own
fires
of
experience
into
devstream
more
on
see
a
CD
process.
I
would
like
to
know
about
the
open
source
community,
how
it
works
and
more
on
sto
and
kubernetes,
see
more
things
on
the
networking
side.
D
D
Who've
been
around
for
a
while
part
of
what
I
was
gonna
ask
today
is
that
there
have
been
there
has
been
and
continues
to
be,
an
influx
of
new
folks
every
week,
some
passers-by
and
some
of
whom
passed
by
in
part,
because
they
didn't
necessarily
find
their
foothold
and
so
we're
gonna,
I'm
gonna,
we're
gonna.
Try
to
work
to
well
have
some
structure
that
some
of
you
can.
Some
of
you
who've,
been
here.
D
Awhile
can
help
us
ensure
that
people
are
being
embraced
in
the
best
of
ways,
recognizing
that
that
some
will
never
find
a
foothold,
and
that
was
okay.
They
were
just
exploring,
but
but
for
others
we
want
to
make
sure
that,
if
they're
interested
that
they
know
that
there's
a
spot,
there's
there's
a
an
extraordinarily
long
roadmap
here.
D
Many
more
initiatives
than
any
of
us
represented
on
the
call
can
accomplish
on
to
our
own
and
that's
not
the
intention,
and
so
so
actually,
that's
a
maybe
a
statement
to
make
that,
if
you're
on
the
call
and
you're
not
you
haven't
quite
found
in
the
area
of
interest
or
somewhere,
where
you
think
you
can
make
a
mark,
let
me
know
or
there's
a
handful
of
others
that
I'll
point
you
to
as
well
in
the
community
to
get
connected
with
and
explore.
So
some
of
them
you'll
hear
from
today.
G
G
Managed
Aggie
98
made
a
forced
to
issue,
so
if
you
could
see
that
the
welcome
board
commented
automatically
that
you
made
your
first
pull
request
and
all
the
stuff
which
was
required
for
a
newcomer
and
then
or
just
because
his
DS
you
fail,
there
was
like,
in
the
review
a
she's
left,
a
comment
that
you
should
improve
it,
but
when
the
marginal
successful,
the
welcome
aboard
again
comment.
If
the
thank
you
for
the
contribution
to
layer
5
community,
so
that
is
the
opt-in,
our
work
that
have
been
gone.
Welcome
board.
G
D
Patients
to
any
of
the
repositories
in
the
lair
file
organization
will
have
a
check
for
whether
or
not
you've
signed
off
on
your
commit.
I
won't
go
into
why
because
I
just
got
done
doing
a
Wednesday
and
we've
done
it
a
handful
of
times
over
the
last
year.
A
lot
of
that
logic,
how
it
works,
and
why
is
written
into
the
contributing
guide?
D
But
it
is
not
infrequent
that
people
will
roll
over
that
as
they
go
to
make
a
contribution
and
so
yeah.
To
the
extent
that
a
welcome
bot
can
gently,
you
can
provide
people
instructions
on
how
to
just
make
commit
signing
an
implicit
part
of
their
motion.
You
know
their
get
activities,
whether
it's
an
alias
or
whether
it's
an
IDE
configuration
I
think
is
just
as
helpful
to
streamlining
process
contributions.
G
G
So
robot
is
one
of
the
repository
all
we're
like
oh
I'm,
showing
you
the
welcome
board,
which
we
have
been
using,
which
is
get
above,
so
it
have
been
developed
by
a
robot.
So
if
we
go
to
the
repository
of
it,
we
can
definitely
see
a
lot
of
both
what's
there,
one
of
which
is
welcome,
bought.
So
when
we
last
this
person
Wednesday
meeting
the
way
I
am
thinking
that
we
should
approach
to
this
problem
is.
G
We
should
try
to
use
this
framework
to
develop
a
code
in
which
we
can
do
these
you're
checking
initial
thought
was
like
somehow
we
put
a
if
else
in
the
code
we
have
done,
but
I
did
not
find
a
way
to
do
that.
So
currently,
I
am
planning
to
approach
this
via
using
the
framework
which
they
have
used
in
developing
the
Welcome
board.
So
maybe
that
may
help
us
to
reach
the
required
result,
but
any
of
you
is
having.
G
I
B
I
G
You
level
that
just
that
gorgeous
check,
that
is
the
PR
is
signed
or
not,
which
I
guess
we
are
using
in
the
gate
of
action
which
X.
That
is
the
request,
a
sign
or
not,
so
that
will
just
check
that
it
is
done
or
not,
but
we
want
to
welcome
the
new
command
as
well.
So
for
that
we
were
using
welcome
board
and
I,
don't
know
how
to
merge
both
the
board's.
That
was
my
first
question.
I
asked
in
the
last
meeting.
That
is
there
any
way
we
can
mold
both
the
ports.
A
F
G
So
currently
we're
using
if
I
show
you
my
screen
again,
I
guess
links
presenting
that.
So,
if
you
see
in
this
one
when
the
Welcome
bought
worked
fine,
so
it
given
message
without
checking
that
the
pull
request
was
signed
or
not,
but
all
the
actions
we
see
that
they're
running
there
it
represented
the
DCO
check-
is
failed.
So
mostly
the
first
commerce
were
new
to
the
community
or
to
the
open
source
world.
They
don't
really
eat
that
part,
so
we
can
directly
I.
G
We
wanted
that
in
the
Welcome
message,
if
we
can
mention
instead
of
writing,
be
sure
to
double
check
that
you
have
signed
your
commit
or
not.
We
can
directly
mention
that
or
you
have
not
signed
your
commit
or
we
can
like
that
kind
of
message
if
we
could
be
positively
able
to
give
to
the
users.
So
that
is
the
need
of
the
are
in
this.
We
are
so.
G
Yeah,
like
the
one
at
least
currently
highlighting
these
you're
successful
or
this
one,
so
that
say,
is
passed
or
failed,
but
these
checks
are
rare
for
a
newcomer
to
check.
So
we
are
trying
to
merge
both
of
them
and
I
am
the
new
to
this.
What
or
think
so
I
am
facing
a
bit
of
difficulty
but
you're
like
do
you
get
the
problem
short
of
what
we
are
talking
here,
yeah.
F
G
G
F
F
G
D
That
would
be
ideal
if
the
existing
box
can
be
enhanced,
it
can
be
customized
a
little
bit.
It's
sort
of
a
natural
path
that
it's
the
one
determining
whether
or
not
someone
signed
off
and
if
they
didn't
great
yeah
I'm.
Actually
I
would
be
surprised
that,
with
a
little
bit
of
searching,
we
didn't
find
that
someone
else
hasn't
already
augmented,
be
that
Probot
the
DCO
Probot
to
do
that,
because
that's
such
a
common
yeah.
G
I
was
also
surprised
when
I
look
for
the
things
that,
if
they're
aboard,
we
check
the
welcome
board
with
check
that
DCA
check
or
not
and
I
really
did
not
find
any
and
I
was
really
shocked.
Like
I
checked
at
the
communities
with
the
boss
they're
using-
and
there
was
nothing
which
was
the
doing
this
thing
in
the
welcome
board.
D
Okay,
good
okay,
I
got
a
number
of
other
topics,
I'm
going
to
push
us
forth.
If
I
can't,
there
were
just
a
few
announcements
to
knock
out.
We
announced
I
think
earlier
in
the
week
that
that
a
well
that
we're
participating
in
a
few
internship
programs.
We,
the
community,
did
last
year
and
is
doing
so
again
this
year
in
a
bit
of
an
expanded
form.
D
Last
year
it
was
just
google
Summer
of
Code
this
year
again
it's
google
Summer
of
Code,
but
also
well
a
hopefully
community
bridge
are
not
hopefully
but
but
community
bridge
and
then
I
guess
hopefully
on
google
season
of
docs.
Whether
we
really
need
all
the
help
that
we
can
get
and
so
will
likely
be.
Having
an
you
know,
a
number
of
you
that
are
on
the
call
applied
through
chuseok.
D
Some
of
you
will
have
an
opportunity
for
google,
for
hopefully,
community,
bridging
and
season
of
dogs.
That
docks
might
actually
be
best
suited
for
a
software
engineer
in
terms
of
some
of
the
things
that
we're
thinking
of
doing
and
then
there's
all
direct
internship
through
their
five
about
getting
the
word
out
about
many
of
the
activities
that
are
going
on.
So
you
open
that
up
earlier
this
week
and
had
a
couple
hundred
applicants.
So
we
need
to
probably
turn
off
that.
D
Turn
off
that
pipeline
anyway,
the
the
other
internship
programs
that
they'll
be
focused
on
envoy
SMI,
distributed
performance,
testing,
mystery
I.
Think
a
number
of
you
know
that
it's
our
intention
have
my
sure
you
head
into
the
CN
CF
first
half
of
this
year
so
relatively
shortly.
It's
a
couple
of
items
for
us
to
knock
off
before
we
go.
Do
that,
but
but
it's
really
rather
close.
Other
quick
announcements
are
just
that.
D
D
Actually,
there's
a
number
of
you
whose
faces
are
up
on
that
page.
So
if
your
face
hasn't
gone
up
on
that
page,
yet
I
guess
work
harder,
then
also
thanks
to
taraj
too,
but
really
the
thanks
to
thanks
to
a
few
different
things
that
there
was
a
spike
in
github
stars
recently
as
well,
which
is
fantastic.
That
put
us
past
the
threshold
of
300,
which
is
what
we
were
waiting
for
in
order
to
have
a
measure
listed
in
the
CN
CF
landscape.
D
D
Great
those
were
the
announcements,
a
few
topics
to
chat
through
I,
don't
know
yet
so
there's
a
new
blog
post
being
drafted
on
getting
started
with
Mary
CTL
I,
don't
know
if
it
could
push
drafted
this
I'm,
not
sure.
If
he's
on
the
call.
This
is
a
an
announcement
as
a
request
for
comment.
It's
also
an
announcement.
D
D
D
D
G
D
Circle
right
back
next
item
was
just.
It
was
just
a
quick
note
that
we've
done
a
little
bit
of
uplifting
on
some
architecture,
slides.
So
if
you're,
new
or
old,
to
ma
cherie,
there's
about
three
architecture,
slides
that
look
at
measure
II
as
its
deployed
either
external
to
the
kubernetes
cluster
or
well.
Actually,
this
diagram
is
yeah.
It
can
be
taken
either
way
you
can
deploy
missery
outside
of
a
cluster
or
in
the
kubernetes
cluster,
either
way
make
sure
he
has
a
couple
of
points
of
extensibility.
D
D
Hopefully
these
visuals
help
people
understand
the
componentry,
the
api's
sort
of
the
project
overall.
So
it's
just
a
recent
left,
lift
is
I
use
with
us
today.
I,
don't
know
that
he
is
he's
been
doing
he's
but
made
a
couple
of
changes
both
within
on
layer,
5,
I/o
and
within
mesh.
We
itself
thought
it
would
be
good
for
him
to
demo
those
fixed.
A
couple
of
bugs
that
have
been
well
bugging
us
for
a
lot
he's
not
on
school
will
will
come
back.
We
talked
about
the
landscape.
D
F
Yeah,
so
I
didn't
put
it,
it
might
be
only
so.
The
thing
is
that
we
are
thinking
of
taking
machinery
CDL
forward
by
giving
like
we
already
discussed
this
last
Friday,
and
we
are,
we
are
like
thinking
of
adding
more
features
and
more
commands
to
the
mystery
CTL
CLI,
so
that
what
people
can
do
from
the
UI
are
also
able
to
do
from
CLI.
F
Also,
please
correct
me
if
I'm
wrong
and
that's
what
so
we
are
thing,
first
of
all,
going
through
all
the
steps
that
we
can
do
and
him
start
implementing
on
the
CLI
part.
What
are
the
different
flags
that
we
can
provide
and
the
different
commands
which
can
help
the
user?
Like
recently,
we
talked
about
the
connection
bridging
so
one
issue
is
open,
so
how
we
can
connect
our
machinery
container
or
machine
kubernetes
service
with
the
running
mesh.
So
that's
how
we
can
we
can
do
that
from
the
musci
Reese
ETL
command
line
on
you
directly.
F
F
To
the
docker
but
and
the
Walker
bridge
connection
command,
we
can
directly
put
it
using
the
machinery
CTL
command
only
and
he
can
connect
the
Machine
service
with
his
own
service
mesh
directly
from
the
machine
you
come
on,
so
we
have
to
discuss
about
this
I'm
asking.
If
we
can,
we
can
get
together
and
do
something
about
it.
F
D
It's
one
of
those
considerations
is:
it
needs
a
bit
of
a
step
back
to
kiss
to
look
at
the
all
of
the
functions
and
functionality
that
would
come
forth
through
mesh.
We
CTL
while
it
while
Mestre
CTL
the
command-line
interface,
is
not
graphical.
It
is
a
point
of
interact.
You
know
a
point
of
it's
a
user
experience
for
operators,
and
so
it's
the
CLI
is
a
client
of
the
memory
servers.
Rest
API,
just
like
the
measure
e
UI
is
a
client
of
that
same
REST,
API,
so
I
guess
what
I'm
trying
to
say
is
mesh.
D
We
CTL
as
a
CLI
should
be
given
equal
billing
in
terms
of
its
of
considerations,
around
user
experience
and
to
sarbs
point
the
right
now.
Mastery
CTL,
as
utility,
really
is
focused
on
lifecycle
management
of
measure
e
as
an
application
itself
and
the
deployment
of
mastery,
the
caretaking,
a
mystery,
the
configuration
of
mystery
but
and
that
that's
good,
but
that
means
that
it's
mastery
CTL
as
a
utility
is
missing.
Thank
you.
Velvet,
sir
mastery
CTR
utility
is
missing.
What
are
really
two
categories
of
capabilities
that
are
include
that
are
exposed
through
the
mesh.
D
D
We
would
ideally
put
some
forethought
into
what
that
looks
like
the
most
recent
command
have
come
forth
is
is
called
perf,
it's
a
very
important
one
because
it
unlocks
what
will
soon,
hopefully
soon
be
measure
ease
used
by
the
ischial
project
by
the
linker
D
project
by
each
by
really
any
of
the
projects
that
any
one
of
you
could
prattle
off.
We've
had
discussions
with
them.
D
Actually,
it's
kind
of
a
nice
little
announcement
that
I
I
didn't
realize
that
we
actually
do
have
today,
I
think
it
was
Naveen
or
or
Kanishka.
My
memory
fails
that
recently
or
and
I
mean
II
was
the
one
who
won
the
fight.
Okay,
actually,
so
I
shouldn't
talk
to
it
rather
Naveen
if
you're
on
I
don't
know.
If
you
want
to
talk
about
the
service
measure
performance
specification
without
that
format,
the
the
flag
that
you
recently
added
yeah.
M
So
currently
we
have
a
repository
called
sorry.
Business
service
match
specification
performance
specification
in
the
ER
SMPS
dot
ml,
which
is
basically
which,
which
is
the
intended
format
of
service
mass
performance
or
file.
But
the
thing
is
currently,
it
is
not
exported
through
the
UI.
I
have
opened
an
issue
for
it
and
it
is
being
worked
upon.
M
So
the
thing
would
be
like
anyone
who
runs
a
performance
test
would
be
able
to
export
the
SMPS
file,
and
then
they
would
be
able
to
run
the
snps
like
they
would
be
able
to
run
the
similar
tests
using
that
file
through
either
UI
or
CLI,
and
same
goes
for
CLI.
We
might
like,
in
future
export
the
results
through
CLI
and
in
that
way,
what
so
the
the
file
flag
is
added.
In
that
way,
we
can
achieve
basically
the
CIC,
the
pipeline
integration
by
machete
so
measure.
M
D
K
D
M
So
but
the
thing
is
like
you
would
have
to
manually
like
enter
in
SMPS
Padma.
Currently
we
have
no
tool
to
export
the
results
in
SMPS
format.
Once
it
is
there
we
will
like
well
like
we
will.
It
will
be
much
more
usable
by
everyone
steadily.
It
is
the
hard
part
is
that
you,
you
have
to
manually,
write
the
snps
file.
D
That
makes
for
a
good
note
that
that
particular
discussion
is
a
good
discussion
for
a
forthcoming
working
group
on
performance
management.
We
had
had
a
discussion
in
partnership.
One
of
our
partners
is
University
of
Texas
Austin
or
UT
Austin.
So
there's
a
professor
and
a
couple
of
PhD
candidates
that
are
well
I,
guess
coming
up
on
a
year
now,
we've
been
kind
of
engaged
in
some
research
on
surface
national
performance.
D
As
a
matter
of
fact,
we
were
to
have
spoken
at
cute
Connie,
you
I,
guess
a
week
ago
on
some
of
that
research,
we've
spoken
on
it
in
the
past
just
become
it
looks
like
it
looks
like
again
coming
up,
which
means
that,
as
we
established
that
working
group
there
are
there's
the
that
will,
there
will
shortly
be
some
public
venues
to
publish
some
of
that.
There's
a
there's
a
lot
of
goals
within
there.
D
It's
one
of
the
deeper
areas
from
history,
one
of
the
areas
of
value-
okay,
fair
enough
next
up
is
Shiv
I
is
he
should
by
is
not
on
the
call
with
us.
We
are
overdue
to
make
this
least
shibai
didn't
do
some
work
recently.
So
the
release
itself
is
fantastic.
There's
it's
sort
of
the
longer
that
we
delay
the
larger
that
this
thing
gets.
D
Create
a
new
page
on
Mary
Jo
that
will
speak
to
what
all
those
releases
are
today
the
releases
are
published
in
the
mesh
redox
on
this
page
here
speaks
to
you
know
what
the
version
was
when
it
was
released,
but
this
process
is
manual
and
a
number
of
you
have
been
discussing
how
to
make
that
a
bit
more
automated
and
then
also
to
maybe
beautify
I.
Think
some
of
what
this
is
and
so
art
occupies
work
was
to
get
that
onto
the
mesh.
We
I
own,
the
site.
D
J
J
Currently,
the
layer
of
eyesight
is
a
bit
of
waste
color
using
blue,
blue
and
gray
gray
scale.
So,
while
the
machine
dot
IO
site
exactly
suit
Z
logo
and
it's
color
scheme
of
layer
5
so
I,
we
have
been
thinking
that
if
the
layer
of
I
boy
I
outside,
can
also
be
revamped
using
those
color
schemes,
so
I
just
made
some
changes
and
shared
the
screenshots
with
Lee.
He
will
be
sharing
with
you
all
in
a
moment.
D
A
little
bit
more
context
here
and
yeah
as
Nikhil
is
thinking
about
the
is
enhancing
and
beautifying.
This
particular
son
he's
looking
over
the
color
schemes
that
have
been
laid
out,
the
colors
for
the
layer,
5
and
then
the
colors
for
Mary
and
by
the
way
I.
Don't
know
how
well-known
it
is,
but
there
are
brand
kits
which
include
all
of
the
logos
for
Mary
and
for
layer
5
that
are
both
have
on
this
site.
D
J
Currently
there
is
one
more
issue
with
the
layoff
eyesight.
The
particle
dot
J's
feature
that
we're
using
it's
the
Deaf
section
of
that
is
a
bit
of
means.
It's
a
bit
down
shifted
towards
the
lower
section.
It
should
be
utilizing
the
holding
what
it
means
the
whole
new
section,
blue
part
of
the
body
so
and
it
shouldn't
be
opened
for
adults
if
I'm
not
wrong.
You're
right.
D
Yeah
yeah,
when
Nicky
was
referring
to
these
particles
back
here,
which
probably
at
some
point
maybe
should
go
away.
It
is
rather
mushy
looking
kind
of
neat
in
that
regard,
but
I
think
we've
had
some
difficulty,
placing
it
in
the
center
of
the
screen,
so
anyone
who
has
opinions
on
coloring
or
other
enhancements
to
the
site.
D
G
Yeah,
so
I
have
been
working
on
documenting
the
brief
for
all
the
repositories
we
have
in
layer
five
organization,
for
that
I
definitely
need
helps
of
different
contributors
who
are
working
in
different
domains.
For
example,
Nick
Hill
is
working
in
the
I
mean,
so
if
you
could
just
give
one
line
or
two
line
description
about
each
of
the
frontline
projects
and
like
there
is
one
very
race
like
precise
and
short
description
for,
go
WR,
k2
which
which
has
been
written
here.
G
So
just
one
line
or
two
line
description
of
all
the
repositories
which
can
help
a
newcomer,
so
I
have
just
suggested
some
names
in
the
document.
So
if
any
of
you
would
like
to
pick
up
some
topics
and
start
with
that
like
if
the
people
are
present
on
the
meeting
like
Nick,
Hill,
sort
of
Naveen,
Shubham
Ashish
concern
and
like
if
these
people
can
just
give
one
or
two
line
or
discussing
so
that's
one
volunteer
task.
If
anyone
wants
to
do
that.
D
Did
that
since
everyone
it's
intended
to
help
people
get
their
bearings
as
they
joined
the
project
kind
of
like
the
newcomers.
Welcome
guide
points
out
the
various
resources
that
that
this
document
would
let
people
you
know,
there's
there's
a
bunch
of
repositories
inside
of
the
layer,
five
ward,
so
it
helps
give
people
an
overview
and
a
guide
to
what
their
purpose
is.
Very.
D
D
L
It
it's
led
by
him
together
with
me.
Maybe
I
will
be
of
some
help.
Also
so
yeah
see
I
see
no
and
automations
on
pushing
the
code
or
contributions
or
repositories
or
kind
of
this
I.
Don't
know
if
I'm
good
the
meeting
it's
every
day
every
week
on
Monday
at
5:00,
I,
don't
know
the
time
my
climates
with
p.m.
European
time
last
one
and
maybe
so
so
you
can
the
same
or
he
I
don't
know
what
I'm
saying
yeah,
no
that's
perfect
and
sign
where
you
want
so
sorry
for
saying
wrong
the
name
it.
L
K
K
D
Yes,
if
you
haven't
worked
with
github
actions,
there's
an
opportunity,
one
of
the
more
significant
things
in
my
mind,
that
is
missing
from
the
project
that
is
a
focus
of
continuous
integration,
is
the
is
release
channels
for
measuring
itself.
D
Today,
there's
this
there's,
essentially
a
single
channel,
which
is
the
Hey,
which
is
to
say
that
there
is
a
release,
but
there
isn't
really
a
stable
or
an
edge,
which
means
that
occasionally,
the
the
release
is
in
stable
because
you
know,
because
there's
only
one
channel
so
the
establishment
of
two
it
could
be
a
really
helpful
thing
for
the
project
and
could
be
an
area
that
some
of
you
want
to
jump
into.
If
you,
if
you're
interested,
please
ping,
Edina
she'll
show
you
around
anything,
we
missed
today,
other
than
Hasaan.