►
From YouTube: Meshery CI Working Group 2020 04 27 at 08:00 GMT 7
Description
Our first Continuous Integration Working Group meeting. Welcome @vullinitish!
A
Think
it
has
something
to
do
with
coffee
being
in
the
end.
I
don't
know
well
so
Syme
was
just
on
a
second
ago
and
I
think
he's
having
technical
difficulties
I'm,
actually
having
a
little
difficulty.
I
joined
with
the
wrong
browser.
I'm
gonna
switch
over
to
Chrome
in
case
I
need
to
share
the
screen,
so
there
might
be
a
blip
here.
Bear
with
me.
A
A
Okay,
very
good
I,
think
I,
think
well.
Yeah
I
think
this
is
our
first
ever
continuous
integration
working
group
meeting.
This
is
nice.
What
a
cool
thing
to
be
able
to
kick
off
a
working
group
and
have
this
many
people
show
up
that.
First
of
all,
our
ability
to
start
a
working
group
is
a
sign
of
growth
in
the
well
in
the
community
and
in
the
missionary
project
in
specific.
So
this
is
this:
is
nice
I've
been
waiting
for
this
day?
I
think
we
might
be
on
the
verge
of
opening
up.
A
A
second
working
group,
which
is
just
fantastic,
being
able
to
open
up
working
groups
is
in
no
small
part
due
to
folks
like
Edina
and
sine
who
have
whether
their
arms
were
twisted
or
not.
They've,
both
agreed
to
help
this
working
group
and
make
sure
that
it
kind
of
gets
off
the
ground
and
sort
of
establishes
a
cadence
begins
to
set
some
priorities
towards
things
that
the
group
wants
to
accomplish.
I.
A
We
don't
control
the
release
of
those
versions
rather
very
well,
and
so
there's
there's
much
work
to
be
done
here
in
this
group
in
this
particular
group
as
it
gets
off
the
ground.
My
intention
is
to
have
my
my
voice
in
particular
sort
of
fade
into
the
background
today
and
next
time
we
meet
next
time.
A
We
meet
that
as
you
guys
as
a
working
group
in
Edina
and
sign
begin
to
steward
our
focus
here
that
I'm
just
a
facilitator,
I'm
the
guy
pressing
the
record
button,
because
I
think
I'm,
the
only
one
that
has
it
but
but
will
actually
get
that
fixed
as
well.
So
so
on
that
I'm
gonna
say
a
couple
more
things
and
then
try
to
try
to
try
to
start
being
quiet,
and
that
is
that
folks
are
doing
precisely
what
I
would
hope
for
them
to
do,
which
is
filling
in
their
name.
A
If,
if
they're
attending
and
I
think
what
we
might
be
doing
in
this
format
is
sort
of
listing
out
assignment.
Correct
me
if
I'm
wrong.
But
it
looks
like
we're
probably
listing
out
those
that
are
invited
and
then,
if
you're
in
attendance,
maybe
putting
your
name
in
bold
or
something
like
that,
because
they're
right
I.
C
A
C
A
A
A
Everyone
sees
the
meeting
minutes
now
that
I'll
be
sharing
right.
I,
think!
That's
that
that's
a
deal!
Okay!
Stop!
Stop
me!
If
not,
but
one
of
those
is
very
good
one
of
those
is
that
there's
been
a
new
label
inside
of
github
called
area
/ci,
and
that's
just
there
to
help
us
try
to
organize
the
set
of
concerns
across
the
repositories
kind
of
all
the
repositories
in
the
layer.
Five
org
that
are
concerned
with
you
know
that
this
working
group
might
be
concerned
with
that's
one
item.
A
Another
item
is
a
bit
of
a
longer
document,
describing
sort
of
both
I
think
the
state
of
where
we
are
in
terms
of
how
it
is
that
builds
are
done.
The
various
artifacts
that
are
produced
in
those
builds,
which
artifact
repositories
we're
using
today
for
those
to
store
and
persistent
and
keep
a
history
and
versioning
of
those
artifacts
and
kind
of
the
document,
goes
on.
I
think
it
also
is
I
believe
in
some
areas.
A
Aspirational
for
where
we
would
probably
ideally
go
and
so
I'll
call
out
that
that
link,
so
these
are
just
kind
of
common
common
tools
that
we
might
use
in
this
group.
Another
one
is
that
you
know
so
all
of
you,
except
for
nitish,
will
make
sure
that
you
do.
If,
if
you
don't
but
I'm,
all
of
you
have
access
to
a
team
drive.
A
A
google
google
team
drive
that
we
use
as
a
community
drive,
there's
a
I'm,
not
sure
if
this
is
the
best
structure
at
the
moment,
but
but
there's
a
CI
working
group
folder
that
has
the
meeting
minutes
at
the
moment
it
is
under
community
it.
My
I
think
there's
a
little
bit
of
restructuring
that
might
make
sense,
because
there's
a
building
release
folder.
That
has
a
few
other.
A
That
has
the
document
that
we
were
just
looking
at
and
a
few
other
artifacts
but
point
is
that
I
expect
that
we're
producing
artifacts
in
this
working
group
and
we'll
need
a
home
for
those
there.
Also
there's
a
slack
channel,
that's
kind
of
specific
to
this
area
of
focus.
So
all
the
names
on
this
list,
I
think
I
believe
are
in
there
everyone's
welcome
to
jump
in
and
then,
and
so
we've
got
a
link
toward
the
meeting
that
that
everyone
that
hopefully
works
for
the
most
of
the
people
that
that
join.
A
We
are
recording
our
meeting.
Sorry,
it's
just
kind
of
a
housekeeping
note
to
mention
that
hey
we
this
this
meeting
is
being
recorded.
We
do
post
our
meetings
publicly,
just
in
in
the
vein
of
being
open,
and
so
those
things
are
there
that
will
likely
have
end
up
with
probably
potentially
a
playlist
special
for
this
working
group.
A
If
you'd
like
to
join
the
mailing
list,
I
figured
that
the
mailing
list
might
be
a
good
way
for
Edina
and
sign,
and
and
consequently
for
everyone
else
here
to
message,
one
another
outside
of
the
slack
channel,
if
that's
needed,
if
that's
helpful,
and
so
with
that,
there's
a
bit
of
infrastructure
set
up
a
bit
of
topics,
kind
of
teed
up
and
I.
Don't
know
that
they're
necessarily
in
any
priority
order
other
than
this.
A
This
first
one
here,
which
is
a
little
bit
of
a
bigger
item,
but
but
it's
an
important
one,
and
so
with
that
Edina
and
sign.
Thank
you
guys
for
stepping
up
here
stepping
up
to
help
us
figure
out
how
to
make
kind
of
grease
the
how
to
have
better
sausage
making
machinery
software
sausage,
making
machine
earrings
Oh
with
that
yeah.
Where
do
you
guys
want
to
start?
How
do
you
anything
you
guys
want
to
change
about
the
way
that
we
can
have
this
setup
or.
C
Thank
you
for
making
this
group
and
really
the
plan.
I
fear
in
the
this
group
is
that
that
we
can
move
forward
and
consistently
without
removing
the
hurdles
that
we
already
have
projects
and
I
think
we
I
think
we
have
take
once
I
am
thinking
that
we
have
taken
approach
that
the
IE
and
the
map
working
together.
So
one
of
our
members
are
looking
forward
to
manage
the
release
pipeline
and
pit
strategy
for
that,
and
other
members
is
looking
forward.
The
initial
issues
is
that
we
have.
We
have
sort
out
so
also
I.
C
C
Previously
they
have
working
the
DevOps
feel
they
have
grayed
out
their
name
in
a
meeting
list,
so
I
can
know
that
so
can
I
assign
the
work
accordingly
in
the
forward.
So
one
thing
is:
I
asked,
also
I
think
the
strategy
that
I
have
decided
that
we
have
the
Athena
and
I
working
together
as
a
team
and
also
one
of
the
members,
is
looking
forward
to
build
the
automation
strategy
where
we
had
it.
What
are
the
tools
available?
What
are
the
right
directions
for
the
automation,
building,
automation
and
one
is
for
working.
C
B
I'm
good,
you
have
ideas
on
approaches,
so
I
would
just
double
check
if
I
understand
properly,
even
if
it's
in
the
meeting,
so
you
have
two
direction.
One
is
for
release
managing
and
automations
and
whatever
is
new
and
tools
and
the
other
one
is
for
the
current
issues
that
are
facing,
and
then
you
have
the
people
who
have
more
than
one
year
experience
which
I
didn't
understand
exactly
where
in
which
category
you
put,
but
that's
kind
of
my
understanding
and
the
two
of
us.
B
C
Yes,
yes,
very,
that's
my
point,
as
you
have
correctly
identified
with
that,
so
we
we
can
make
out
a
separate
meeting
for
that,
so
we
can
assign
some
some
rules
for
ourselves.
So
meanwhile,
I
think
there's
two
points
there.
There
is
a
lot
of
improvements
that
we
need
to
be
done
in
that
project
and
one
is
there
to
get
familiar
with
that
project
as
well.
So
we
have
have
tracked
down
some
lists
of
that.
We
can
move
in
that
direction.
C
C
B
Was
my
availability
I'm
practically
available
in
any
day,
except
Saturday
and
Sunday,
starting
with
the
hour
of
this
when
we
had
when
we
start
this
meeting
today,
for
instance,
for
me,
it
was
5:00
p.m.
in
the
afternoon.
So
any
time
with
these
hours,
starting
for
the
next
ten
or
nine
hours,
I'm
up
I
can
be
available
in
any
time.
I
have
one.
B
C
C
Okay,
Leah
I
just
want
to
know
that
the
people
that
listed
are
here
so
one
of
member
that
I've
more
than
have.
Then
they
have
one
year
experience
of
working.
So
so
luckily
in
the
memory
so
I
got
to
know
some.
If
I
can
have
difficulties,
I
can
ping
them
out.
So
so
their
suggestion.
What
they
are
thinking
I
thinks.
A
Yeah
appropriate
for
those
that
have
that
feel
a
little
bit
comfortable
or
have
been
assisting
in
some
of
the
workflows
because
self
signal.
If
you
will
there's
a
couple
of
folks
that
whose
names
I
see
in
the
call
that
I
know
have
touched
either
one
or
many
workflows
across
the
repo,
so
I
she's
guns
in
Sochi
sing
guns
in
Paul,
Chryst,
Trivedi
and
Naveen
Jain,
the
poor
might
have
Shubham.
A
Kumar
is
not
on
the
call,
but
has
there's
some
other
folks
who
have
and
and
aren't
on
the
call
just
because
I
didn't
call
out
other
people's
names
doesn't
mean
that
they
aren't
entirely
capable
or
maybe
even
more
capable
than
those
that
I
did
call
out.
I
was
just
calling
out
names
of
people
that
I
know
literally
like
me
to
commit
or
change
the
work,
clothes
that
we
use
today
and
so
just
to
help
facilitate
and
provide
some
context
and
background
for
well.
A
A
A
All
right
good,
if
you
guys,
are
not
seeing
the
measure
repo,
then
please
interrupt
again,
please
let
me
know
so
in
this
repo
there's
and
as
in
each
of
the
repositories,
you'll
find
a
dot
github
folder
in
different
repositories.
You'll
find
differing
amounts
of
config
about
how
it
is
that
that
repository
is
configured
to
use
github.
A
Most
of
them
will
only
have
a
CI
mo
and
it's
not
necessary
that
that
Yama
file
file
is
called
CI,
but
that's
just
the
convention
that
we've
used
pervasively
across
each
repository.
This
is
probably
where
much
of
this
groups
focus
is
sort
of
conceptually
intended
to
be
I'm.
Gonna,
I'm
gonna,
look
at
this
one,
because
it's
fairly
short
and
because
I
think
it
will
expand
our
minds
a
little
bit
about
the
ways
in
which
part
of
how
we
might
use
github
actions
and
workflows
in
the
projects
and
in
the
community.
A
It
just
messages
the
slack
channel
called
buzz.
So
all
of
you
are
inside
of
the
layer.
Five
community
slack,
there's
a
channel
in
there
called
buzz.
You
will
notice
that
you'll
notice
this
message
in
there
it's
kind
of
nice
I
wanted
to
give
a
do
a
couple
of
things.
One
say
that
we're
using
across
the
projects,
github
actions
and
workflows
that
these
have
been
building
up
somewhat
rapidly.
A
Recently,
folks,
like
cush
and
and
some
others
have
been
working
to
make
sure
that
they
are
that
not
all
jobs,
not
all
aspects
of
the
workflow
are
executing
every
single
time
that
someone
submits
a
PR
every
time
that
they
submit
push
a
new
commit
to
that
PR,
because
it's
not
always
appropriate
that
each
of
these
run
and
so
trying
to
optimize
this
a
little
bit
as
we've
gone
to
expand.
It
I
think
that
that's
been
helpful.
A
This
goes
on
for
a
while,
as
many
of
you
are
familiar,
and
some
of
you
aren't
familiar
with
the
various
languages
that
are
used
in
the
project
in
measure
e
go
is
a
central
language.
Javascript
with
was
react.
Next
Jas
is
is
another
for
the
measure,
e
UI
and
there's
another
component,
there's
kind
of
three
components
inside
of
measure,
your
repo
itself,
one
of
those
that
the
biggest
one
is
that
measure
e
server.
If
you
Lowe's,
is
misery,
another
component
is
the
UI.
So
this
is
where
our
react.
App
is
another
one.
A
Is
my
sri
CTL?
It's
it's
a
command-line
client
as
the
project
and
the
community
grows.
It's
likely
that
these
might
that
measure,
ECT,
l
and
measure
UI
might
split
out
into
their
own
repositories.
We
wouldn't
want
to
do
that
until
we
wouldn't
want
to
do
that.
Currently
and
there's.
That's
it
that's
another
discussion
we
can.
A
We
can
walk
through
that
my
point
of
calling
out
the
fact
that
there
are
different
components
and
about
well
I
said
there
are
three
but
actually
I'm
skipping
one
there's
a
fourth
one
and
it's
a
set
of
Doc's,
it's
the
docs
for
the
project.
The
project
Doc's
are
based
on
Jekyll,
it's
possible
to
also
pull
out
this
fourth
component
into
a
separate
repo.
A
But
right
now
it's
it's
in
the
repository,
and
so
my
point
is
these:
individual
components
can
have
different
build
needs
and
when
someone
submits
a
pull
request
that
only
contains
changes
in
the
docks.
For
example,
it's
not
necessary
to
run
all
of
the
other
jobs
to
build
all
of
the
rest
of
the
system,
so
so
some
amount
of
optimization
and
a
focus
there's
kind
of
nice.
A
So
what
I
was
trying
to
do
is
give
some
context
as
to
kind
of
the
environment
that
we're
in
I'm
gonna
touch
on
briefly
to
skip
across
a
couple
of
topics
that
I
think
will
spur
some
conversation
and
maybe
set
some
initial
goals.
So
we
just
so
one
of
those
topics
is,
is
the
use
of
bots
bots
can
be
used
for
curating
issues,
identifying
issues
as
stale
triaging
them
trying
to
get
them
into
the
right
area
or
or
trying
to
make
sure
that
if
one
is
ready
for
a
review
that
it's
flagged
as
such?
A
That's
labeled
as
such
others
can
be
used
to
welcome
people
as
they
maybe
submit
their
first
issue
or
their
first
pull
request.
So
we
just
did
one
of
these
today.
I
won't
digress
and
demo
it
or
show
it,
but
but
but
it's
up
there
and
you
can
see
it
rather,
what
I
would
say
is
as
we're
exploring
things
like
BOTS
or
the
use
of
automation
like
release
drafter,
to
help
us
in
to
help
us
when
we
get
to
toward
the
end
of
a
release,
and
we
go
back
to
create
our
change
log
and
our
release.
A
Notes
that
automation
like
this
might
be
quite
helpful
in
terms
of
yeah
in
terms
of
making
that
easy
by
the
way,
as
I
walk
through
this
I
know.
These
aren't
all
of
my
ideas
for
certain
there
are
individuals
that
have
are
either
have
either
thought
of
these
things.
And/Or
are
working
on
them,
so,
if
you
would
each
of
you,
if
you
would,
it
would
probably
be
helpful
back
to
Simon's
question
about
you
know
getting
more
with
each
of
you
and
come
wherever
your
focus
on.
A
If
you
would
put
your
name,
maybe
you
know
next
to
next
to
some
of
these
things.
We've
got
a
couple
here,
but
you
know
something
like
some
some
marker
or
some
some
way
of
kind
of
denoting
that
hey
on
this
topic.
These
are
the
folks
you
might
want
to
go
talk
to
her.
These
are
people
that
might
want
to
work
on
it.
A
That
would
help
on
on
this
there's
another
resource
to
call
out
and
that
that's
that
some
of
these
changes
to
to
how
the
project
is
built.
You
know,
if
they're
done,
you
know
just
like
other
bugs.
If
those
changes
are
done
incorrectly,
they
might
break
the
bill
and
that
can
be
anxiety
invoking
for
those
that
are
trying
to
improve
the
CI
and
also
for
the
others
that
are
trying
to
you
know,
get
get
out
a
particular
build.
A
So
because
of
that,
and
because
you,
because
you
you
need
the
ability
to
test
your
continuous
integration
and
the
changes
that
you're
making
there's
a
repository
called
mastery
temp.
It
just
acts
as
a
sandbox
for
trying
out
new
BOTS
for
trying
out.
You
know
rabies,
drafter
or
new
changes
in
the
flows.
If
we
need
another
sandbox
we
can,
we
can
get
one
of
those
as
well.
A
All
of
you,
if
you
have
can,
if
you've
contributed
to
the
project
in
github
I,
think
you
very
quickly
end
up
receiving
an
invite
to
join
the
github
org
or
the
layer.
Five
org.
When
you
do
each
of
you,
it
should
have
the
appropriate
level
of
permission
to
this
sandbox
to
to
play
and
explode
things.
You
know
to
play
and
write
to
the
sandbox,
and
so
I
wouldn't
expect
that
this
is
functional
code
or
really
working
builds
per
se.
So
if
we
need
another
sandbox,
that's
fine,
we
can
make
one
of
those
as
fine.
A
You
guys
are
also
all
welcome
to
test
out
those
changes
in
your
own
Fork.
Repos
I
know
that
sometimes
that
can
be
in
Union,
based
on
the
logic.
That's
included
inside
of
the
work
clothes,
because
some
of
that
logic
like
pushes
images
to
docker
hub
or
requires
particular
secrets
that
are
stored
inside
of
the
repos,
so
fair
enough.
A
A
Or
I
had
given
perspective
about
one
of
the
larger
items
that
I
can
that
I,
you
know
from
my
part,
can
consider
is
something
of
a
priority
I'm
not
being
at
the
establishment
of
where
these
channels
does.
Anyone
else
have
other
items
that
they
think
we
might
want
to
chew
off.
First,
something
like
a
release,
drafter,
something
that's
a
little
more
less
involved,
a
little
more
straightforward.
A
So
to
kind
of
fill
in
the
it
should
interrupt
me.
Anyone
as
we're
going
I'm
listening
down
another
known
issue,
and
that
is
that
that
is
that,
if
you're
familiar
with
the
CLI
mastery
CTL,
it
will
tell
you
what
the
client
version
is
and
it'll
also
in
an
inappropriate
fashion.
It
will
also
tell
you
what
the
server
version
is.
A
The
reality
is
that
that's
kind
of
made-up
and
fake,
and
so
I'm
gonna
demo,
that
real
quick
just
to
this
is
one
think
might
be
of
interest
to
some
folks,
because
this
is
an
issue
that
helps
with
functionality
of
the
project
but
is
but
needs
to
be
addressed
in
this
working
group.
So
the
issue
that
I'm
describing
is
that
here's,
the
command-line
tool
for
interacting
with
massery
there's
a
few
different
commands
that
can
be
run.
One
of
those
is
version.
So
if
you
do
Mestre
tto,
it's
not
a
flag,
it's
a
command!
A
So
if
you
measure
a
CTL
urgent
meeting
on
my
system
and
I,
think
this
is
the
latest
release.
It'll
say
that
the
client
version
of
ma
cherie
and
the
client
by
the
way
is
ma
cherie
CTL.
So
the
mastery
CTL
version
is
this
and
you
can
check
your
local
binary.
It's
you
know
sha.
You
know
this
is
the
Shah
of
that
release.
A
It
also
will
tell
you
that
there's
the
server
version,
like
the
memory
containers
that
you
might
be
running,
that's
the
mesh
it's
hard
to
see
but
I'm
running
a
bunch
of
containers
and
some
of
those
are
messy,
I'm
running
mystery
and
it
looks
like
I.
My
measure
was
updated
27
minutes
ago
that
that
server
Marie
the
client
here
is
telling
me
that
that
server
version
is
also
314
and-
and
it's
actually
not
there's
some
work
to
be
done
to
ensure
that
it's
actually
not
it's.
A
It's
a
stubbed
out
piece
of
functionality,
it's
sort
of
lying
to
us
at
the
moment
when
we
run
execute
this
command,
it
actually
needs
to
interrogate
my
Cherie
server,
just
hit
a
REST
API
on
a
mystery
server
and
pull
back
the
latest
version
number.
It's
not
doing
that
right
now
and
part
of
the
reason
it's
not
doing.
That
is
one
because
I
don't
think
we
have
that
REST
API,
which
is
easy
enough
to
make.
A
But
the
reason
we
haven't
made
it
is
because,
when
measure
a
is
built
this
this
version
tag
is
available
in
the
workflow
that
executes,
but
we're
not
persisting.
That
number
I
mean
like
like
to
the
file
system
of
my
Cherie
server
like
we're,
not
embedding
it
anywhere
in
that
build
in
the
I'm.
Sorry
in
the
artifact
that's
released,
so
this
artifact
this
container
image
it
doesn't
know
what
version
it
is
and
so
consequently,
that's
why
I'm
listing
that
down
as
a
something
of
a
smaller
item.
G
A
A
So
when
the
next
release
comes
up,
we
end
up
drafting
a
new
release.
At
the
same
time,
we
end
up
creating
a
new
tag
and
formatting
our
release
in
Saskatchewan,
when
this
release
is
published
that,
in
that
just
invokes
a
build,
it
invokes
that
CI
mo
that
we
were
looking
at
briefly
earlier
and
that
CI
llamo
has
a
number
of
jobs
inside
the
workflow,
and
so
those
jobs
will
check
for
the
presence
of
a
version
tag
it.
Basically,
the
presence
of
a
version
tag
when
a
build
is
happening
when
a
workflow
is
running
through
that.
A
Indeed,
that's
an
indicator
that
this
is
in
fact
a
release.
It
is
time
to
produce
you
know,
compile
all
the
artifacts
and
make
a
release
and
I
think
we
can
probably
see
some
of
that
logic
here.
Just
taking,
for
example,
mesh
Reis
ETL,
the
CLI
component
as
its
executing
various
parts
of
the
workflow.
It
there's
a
step
that
it's
skipped,
because
this
last
merge
did
not
include
a
release.
A
A
H
B
H
H
A
So,
that's
that's
not
how
it
sounds
like
a
wonderful
topic
to
present,
like
that
yeah,
that's
in
general,
I
mean
without
without
trying
to
pre
pre
bless
that
motion.
It
sounds
pretty
great
to
me
and
I.
Think
it's
one
of
those
things
that
we
well,
you
know
and
I'ma
could
make
sense
to
you
guys.
Yeah,
maybe
look
to
next
week
to
ask
for
someone
to
present
what
release
drafter
is
and
how
they
consider
that
we
would
use
it,
and
maybe
you
know,
show
an
example
had
been
used
and
I.
H
H
A
C
Yesterday,
I
think
he
has
I
think
you
think
on
that
last
time
we
have
a
small
discussion
on
that
topic
at
least
often
so
I
think
I
think
him
had
the
game,
so
he
could
prepare
a
demo
and
he
presented
the
next
call
next
movie.
So
one
thing
that,
sadly,
that
I
want
to
know
that's
every
we
have.
A
branch
is
available
in
the
get
up
the
layer
file
project.
C
That
I
was
thinking
so
I
think
every
member
of
the
team
working,
whether
in
on
their
own
branch
and
then
he
commits
sets
and
then
he
multiple
requests
out
of
there.
And
then
we
subtitle
request
from
the
master
branch
and
then
the
release
drafter
or
in
the
release
versioning
going
forward.
Is
it
there's
a
processes?
That's
the
same.
That
I
thinking
good
is
change.
C
Yeah
have
one
think,
just
just
a
small
point
that
I
think
every
member
of
the
team
that
working
in
the
mystery
they
have
their
own
branches
available
for
that,
so
everything
we
commit
a
change
to
that.
So
we
have
how
many
changes
he
committed
to
that
before
resolving
the
issue
or
completing
the
feature
is
going
to
the
release
drafter
there,
so
they
have
three
commits.
That's
then,
then,
that
in
that
position
of
the
day
and
I
think
that's
that's
a
that's
a
process
that
we
are
following
here
or
is
something
gah.
A
It
is
certainly
the
case
that
everyone
can
fork
ma
cherie
and
make
changes
in
their
local
repository
and
change.
The
way
that
the
builds
are
done.
Some
aspects
of
the
build.
Some
of
the
jobs,
though,
can
be
kind
of
a
pain
to
try
to
test
in
your
own
repo.
Everyone
can
do
it.
It
just
requires
more
setup,
and
so
it
was
some
time
ago
that
we
had
just
Forked
a
copy
of
the
repo
to
just
function
as
a
sandbox
to
let
people
play
within,
but
you're
right.
C
A
Good
question
so
the
going
back
into
the
buildin
release
strategy
doc,
the
this
section
on
artifacts
will
provide
folk
people
with
the
URL
here
to
docker
hub,
which
is
the
only
place
currently
that
builds
are
being
pushed
to
well.
I
shouldn't
say
that
that's
not
inaccurate.
Let
me
go
back
to
the
dock
because
it
the
the
that's
the
the
place
where
ma
cherie
server
and
measuring
adapter
container
images
are
being
pushed
to
the
other
artifact
like
mesh
reefs,
ETL,
it's
being
pushed
to
github.
C
And
Leah
I
said
the
question
that
I'm
asking
here
is
this
I
think
a
AWS
providing
an
app
mesh,
the
gutter
service
mesh
they
are
providing.
Such
man
is
add
mesh.
So
if
we
have
a
roadmap
for
that,
that's
we
can
link
in
that
add
mesh
to
the
survey
we
get.
The
Mishra
can
do
that.
So,
if
I
have
any
roadmap
for
that
that
we
can
in
future
go
for
the
cloud-hosted
it.
Yes,
as
your
G's,
be
kind
of
things,
so
we
can
host
these
images
on
that
container
container.
A
Question
so
with
there
is
a
plan
for
an
at
mesh.
Adapter
I
spoke
with
AWS
last
week,
last
Monday
I
believe
about
their
ability,
their
willingness
to
come
and
spend
time
to
help
build
out
this
mesh
adapter
I've
spoken
to
them
any
number
of
times.
I,
don't
hold
out
hope
that
they
will
come
do
that
soon
and
consequently
we
may
not
get
to
this
adapter
soon,
not
because
we
don't
desire
to
just
because
there
aren't
I,
don't
know
with
folks
with
some
of
the
folks
on
this
call.
A
So,
as
we
so
very
good,
I
just
said,
maybe
I'll
help
close
up
here
and
sounds
like
a
couple
of
items
as
we
go
to
wrap
up
our
first
work,
CI
working
group
meeting,
one
is
I,
think
something
like
Adina
and
Simon.
You
guys
might
have
some
some
ketchup
that
you
want
to
do
so.
You
guys
will
probably
get
together
at
some
point
this
week,
the
next
week,
because
Krish
wasn't
here
or
wasn't
here.
While
we
talked
about
it,
was
that
we
gave
him
an
action
item.
So
that's.
A
A
It's
more
important
that
we
start
to
I'm
exactly
Idina
to
what
you
were
asking
about,
that
we
start
to
capture
the
version
tag
inside
of
the
Mestre
container
as
its
built
and
have
that
available
to
facilitate
an
API
call
for
measure
e
itself
to
be
cognizant
of
what
version
it
is
because
today
it
it
doesn't
know
what
version
it
is.
So.
A
A
A
And
since
I
feel
entirely
comfortable
to
do
this,
so
I'm
going
to
suggest
a
few
things,
so
one
cush
is
gonna
demo
next
week,
really
strapped
her
to
sure.
If
Shiva
doesn't
demo
on
Wednesdays
call
the
release
notes
for
the
upcoming
zero
four
zero
that
he
would
do
it
on
Monday
yeah.
You
know
that
next
time
that
we
meet
here
and
can
a
demo
the
blog
and
then
survive
the
new
releases
UI
on
mesh
redial.
A
That
would
happen.
I'll
also
suggest
that
you
know
it
sounds
like
you.
You
might
be
inclined
to
help
ensure
that
the
mastery
server
tag
is
going
into
the
container,
maybe
iterating
on
a
spec
on
that
would
be
good
and
sarra.
I
know.
We've
got
some
review
to
do
on
mastery
CTL
and
the
commands
that
it
has
so
I.
Don't
know
if
that
mastery
CTL
version
might
be
of
interest
to
you
as
well.
So.
B
For
me,
it
will
be
more
easy
to
say
which
are
the
mastery
projects
or
components
like
you
said
you
have
the
front
end
one
which
is
doing
react.
Then
you
have
the
mess-free
CTL,
my
stream
server
dogs
may
be
project
SMI
things
or
things
like
that
doing
on
the
release.
What
what
do
we
consider
to
be
project?
B
Are
actually
it's
my
need
to
destroy
things
not
a
destroyed
to
make
them
in
spin
pieces,
which
is
not
necessary
good,
so
you
said
dogs.
Are
they
don't
need
to
be
built
every
time
or
something
like
that?
I
thought
that
need
to
be
removed
from
the
mouse
free,
github
repo.
That
would
be
a
separate
repo
and
things
like
this.
B
Okay
yeah,
maybe
a
dog
or
I
don't
know
just
to
identify
and
have
like
a
continuous
list
which
are
things
to
be
worsened,
because
from
from
what
I
see,
we
have
only
one
type
of
version
which
is
used
for
two
types
of
version
which
is
used
for
mastery
and
mastery
CTL.
But
you
also
have
talks,
workshops,
emi,
MMI
things
right.
B
A
And
then
that's
a
great
point
about
the
docks
not
being
versioned,
because
there's
there's
just
a
presumption
that
that
you're
looking
at
you're
looking
at
the
latest
and
it's
speaking
to
latest.
So
that's
a
great
that's,
an
item
that
needs
to
be
before
I
called
out
your
name
there
briefly,
because
I
think
you
were
considering.
Maybe
writing
it
a
little
bit
of
a
guy.
G
Yeah
early
I
I
am
doing
that.
I
started
that
initially
I
can
discuss
the
rough
idea
of
it.
I
forgot
to
share
the
document
with
you.
The
part
I
am
doing
currently
is:
I
am
first
trying
to
differentiate
the
projects
on
the
basis
of
front-end
and
back-end,
and
then
on
what
specific
language
like,
for
example,
in
machinery
CTL
the
project
is
on
go
language,
so
I'll
do
that
kind
of
which
github
is
also.
G
Data
will
help
me
that
which
project
is
under
which
language,
so
that
kind
of
what
is
that
earth
flowchart
or
our
division
of
projects
I'm
doing
I
may
need
help
of
some
people
who
are
already
like
known,
like
I'm,
not
familiar
with
all
of
the
project.
I'm
familiar
with
few,
like
I'm,
not
familiar
with
the
front-end
project,
so
as
I
will,
I
will
also
try
to
write
description
about
all
of
the
projects.
G
A
A
C
Lee
I
think
if
we
have
time
left
in
the
next
meeting,
we
can
discuss.
Wsl
do
I
think
is
a
very
good
technology.
I
think
it's
a
good
time
to
introduce
to
the
guys,
because
I
think
eventually
make
our
list
to
go
for
that,
because
Microsoft
and
done
is
tremendous
job
executing
to
operating
system
in
a
fun
way
you
have.
Can
this
sandbox
is
to
environment
and
sampling,
so
I
try
to
prepare
some
demos
for
that.
What
are
some
slides
shells
and
if
we
turn
through
time
permits
we
can
discuss
on
that
debris,
sn2
ice.
C
Think
Lisa
moving
forward
Alta
is
summer
plans
to
a
it's
going
to
create
a
consistent
environment
from
next
NWSL.
To
is
one
sa
great
way
to
constrain
size,
the
environment,
because
some
of
the
people
working
there
Linux
some
of
the
people
of
Becky
that
Maxim
of
bugging
the
windows,
so
WS
l2
is
kind
of
a
thing.
They
have
mixture,
the
windows,
kind
of
thing
and
Linux
kind
of
things,
so
I
think
some
just
prepared
for
vice
to
that.
That's
eventual
goal
is
about
that,
so
it
hits
that
sparked
it
in
that
box.
C
A
C
Lee,
just
one
note,
I'd,
say:
I
windows.
Vps
code
has
a
very
good
extension
there
WSL
too,
so
they
have
a
UI
that
working
in
the
Windows
domain
there
and
Windows
operating
systems
are
running
on
the
Windows
operating
system,
the
UI
of
that
BS
code,
but
that
the
command
line
the
server-side
is
running
in
the
Linux
operating
system.
So
it's
kind
of
a
very
kind
of
heaven
for
event.
Web
developers
they
are
working
in
a
two
different
environment
and
fighting
for
the
environment.
C
A
A
So
ping,
no
okay,
well
fair
enough!
Now,
I'm
really
sensitive
to
the
fact
that
we're
like
10
minutes
over,
and
so
we
should
let
everyone
go
thanks.
So
much
to
everyone
for
joining
the
first
see
I
call
so
lots
of
work
to
do
in
this
area.
I
will
see
it.
Hopefully
all
of
you
either
on
Wednesday
or
Friday.