►
From YouTube: Meshery CI Working Group (June 6th, 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
B
B
A
So
it
depends
up
on
the
country
Austria.
It's
pretty.
There
is
a
lot
of
freedom
in
Austria
in
Vienna.
I
will
say
so
know.
Also
more
Erica
more
flight
company
are
gonna
opened,
I
bought
the
ticket
to
Romania
at
the
beginning
of
July,
but
still
officially
it's
not
the
airlines
that
the
route
is
not
opened.
B
B
The
the
Q
Khan
EU-
it
will
be
virtual
for
sure,
and
then
there
is
a
cube
con,
China
or
Asia
or
something
as
well,
and
it
will
be
virtual
and
I.
Don't
remember
the
dates
for
that,
but
then
cubic
on
North
America
in
Boston
I
think
that's
a
TBD
like
I.
Don't
that
I
haven't
heard
word
one
way
or
the
other
on
that.
B
We
anticipate
probably
a
that
there's
some
travel
restrictions
and
just
general
restrictions
that
are
being
lifted
and
that
I
think
I
think
there's
an
anticipation
that
things
are
going
to
get
kind
of
nasty
again
in,
like
toward
the
end
of
the
summer
or
even
like
in
October.
After
a
lot
of
kids
go
back
to
school
yeah,
it's
I,
don't
I,
don't
I'm,
not
sure
if
we've
seen
the
worst
of
it
or
not,
hopefully
just
people
how,
hopefully
there's
people
wearing
more
masks,
I,
guess,
I
think
a
while.
Well.
A
That
says,
that
being
says,
it's
just
not
to
spread
the
virus,
not,
but
actually
I,
don't
think
it's
like
what
I'm
going
to
protect
you
anyway.
Now
it's
pretty
a
lot
of
freedom,
I
will
say
in
the
restaurant
and
in
the
lot
of
places
they
are
not
wearing
masks
anymore.
Also,
in
India
office
noise
I
mean
you
need
to
have
like
1
meter
distance,
put.
B
A
B
Ok,
fair
enough,
so
a
couple
a
couple
items
as
we
get
going
now,
so
we're
six
after
welcome
everyone,
a
couple
topics
up
for
discussion.
The
first
is
maybe
an
easy
one,
and
that
is
just
that.
We
might
pull
back
our
meeting
time
to
about
30
minutes
a
week
up
until
the
point
that
we
can
I
get
a
better
attraction
and
hopefully
30
minutes.
Will's
will
force
us
to
squeeze
some
things
and
be
more
concise
in
part,
because
we've
got
a
lot
of
meetings
going
on
each
week
so
good.
B
D
Is
so
since
we
were
having
less
labels
about
issues
and
thoughts
and
we
seriously
needed
to
add
tables
at
a
triads
and
better
contributing
experience,
so
we
were
having
a
long
discussion
since
around
two
weeks
to
have
to
have
new
labels
for
layer
five
organization
and
for
mash
a
project.
Also
so
I
have
pulled
off
the
list
for
all
of
which
we
are
going
to
a
better.
Let's
read
descriptions
against
them,
so
here's
the
list
you
can.
B
Just
as
refresher,
we
talked
about
the
importance
of
labels
ongoing
not
only
for
just
good
hygiene
in
in
keeping
track
of
all
the
various
activities
that
we're
doing
and
github,
but
also
to
ultimately
begin
to
wrap
some
better
automation
around
some
better
workflows
around
for
either
building
out
for
a
bunch
of
things
for
better
release,
drafter
notes
for
better
conditional
logic
inside
of
the
CI
workflows,
and
so
this
is,
you
know,
essentially
kind
of
a
final
draft
of
what
we
consider
that
that
probably
looks
like
very
briefly.
There
are
some.
B
There
are
some
labels
that
identify
the
area
that
a
particular
issue
falls
into.
These
aren't
all
of
the
areas
that
the
project
has,
but
so
all
of
these
labels
that
you
see
have
been
defined
at
an
organizational
level
for
layer,
5
I/o
as
an
org,
so
anytime,
a
new
repo
is
created.
All
of
these
labels
are
available
to
that
new
repo.
We
just
created
a
new
repo
yesterday
for
a
mesh
reoperation
umber
of
new
repos
that
have
been
created
recently.
B
B
E
B
D
B
F
C
A
A
B
I
mean
it's
a
that's
a
great
question
in
that
in
the
Mestre
repo
we
do
specifically
in
there
begin
to
call
out
a
couple
of
components
like
ma
cherie.
Ctl
is
a
good
example
and
that
measure
CTL
isn't
exactly
covered
under
one
of
the
areas
that
we
have
defined
right
now,
but
that
yeah
it
building
only
my
sri
CTL
could
really
help
save
a
lot
of
time.
You
know
so,
do
we
as
we
look
at
defining
more
explicitly
a
given
component
yeah.
A
B
Yeah,
as
we
were
going
through,
this
I
think
that
was
one
of
I
didn't
explicitly
write
it
down
in
this
doc,
but
maybe
I
did,
and
one
of
the
goals
is
to
just
keep
the
number
of
labels
as
low
as
part
or
the
yeah
as
small
as
few
as
possible,
because
it
becomes
unwieldy
and
and
the
reality
is
like.
The
use
of
the
labels
is
in
some
respects
only
so
good
as
the
people
that
are
curating
them
that
are
taking
the
issues
and
assigning
the
correct
labels.
B
It
is
you
know,
any
that
the
name
of
the
label
ends
up
just
being
a
string
and
so
yeah.
A
conditional
logic
that
you
can
have
inside
of
a
workflow
can
just
match
against
that
string.
Then
the
label
string
and
so
yeah
I
think
so
it's
okay,
that
we
sort
of
make
up
our
own
hierarchy.
So
to
speak,
it's
not
literally
a
hierarchy,
it's
just
it's
just
a
string.
B
D
B
Yes,
thank
you
guys,
right
now,
the
label
is
called
ma
cherie
CTL,
but
if
we're
being
forward
thinking
about
it,
maybe
its
component,
slash,
CLI
or
component
slash
mastery,
CTL
or
I'll
give
that
some
thought,
but
very
briefly,
brainstorming
with
the
rest
of
you
is
there
another
label
that
we
know
we
could
use.
Think
right
now,
there's
an
area
UI,
maybe
that's!
Maybe
that
should
be
named
something
else,
but
if
there's
an
area
UI
that
might
mean
that
we
should
then
build
the
mastery
UI
and
if
not,
we
should
skip
it.
B
B
B
Lead
or
I'm
kind
of
I'm
eyeballing
you
right
now,
if
you
can't,
if
you
don't
feel
it,
there
was
the
image
hub,
the
learn
layer,
five
and
as
of
the
weekend,
there's
well,
the
repository
right
now
is
called
macerator
and
really
this
is
a
mesh
writer
for
kubernetes,
I'm,
sorry
kubernetes
operator
from
essary.
We
will
probably
rename
that
soon.
B
But
lead
or
the
this
will
be
an
implementation
of
kubernetes
operator
using
the
operator
SDK,
so
it'll
be
in
go.
B
B
G
G
B
B
Right,
yeah,
the
the
stuff
from
the
stuff
from
the
past
was
really
this.
These
three
issues
right
here
and
it
was
about
beginning
to
version
the
mesh
reserver
bill,
yeah
and
lead
or
knocked
out
the
first
of
them,
which
was
to
create
a
a
properties
that
yeah
mo
file
to
be
included
inside
the
mystery
container
image.
The
next
two
are
a
bit
more
go
based,
so
one
of
them
is
create
an
endpoint
in
Mussoorie
server
that
returns.
A
B
C
G
B
So
today,
I'm
in
a
mystery
project.
We
don't
have
any
kubernetes
operators
or
any
controller
or
custom
resource
definitions
for
mesh
tree,
but
we're
gonna
go
build
one
out
and
when
we
do
we'll
base
that
work
on
the
operator,
SDK
and
so
in
it-
and
this
is
go
based
so
we'll
end
up
taking
probably
forking
this
repo
and
building
out
our
operator,
using
that
SDK
and
I
would.
A
B
A
B
A
B
B
B
B
G
G
C
I
was
going
through
their
five
organization,
all
the
repertory
today
and
got
to
know-
and
you
also
mentioned-
that
there
are
a
lot
of
them
or
added
new,
so
we
need
to
add
them
in
the
list
we
give
to
the
new
contributors
there.
We
mentioned
that
these
many
are
the
repository
and
what
specific
repository
does
so.
We
need
to
update
that
and
for
that
I
could
do
it,
but
I
need
to
get
a
brief,
so
I
can
find
that
in
the
previous
meeting,
I
can
watch
the
video.