►
From YouTube: Meshery Development Meeting (April 29th, 2020)
Description
How to use a probot to assist contributors with DCO (commit signing). Integrating chaos into Meshery.
A
A
Don't
know
point
how
we
will
do
that.
But
point
is
put
your
name
down
in
the
meeting
minutes
all
right
couple
of
announcements
this
morning
and
then
a
few
topics
to
chew
through
in
terms
of
the
announcements.
We
have
a
number
of
newcomers
this
week
since
last
time
that
we
met
so
very,
very
excited
about
these
folks.
As
a
matter
of
fact,
nick
is
I
think
he
is
I'm.
Gonna
call
me
show
you
with
St.
You
want
to
do
a
quick
introduction.
It'd
be
nice
to
get
to
know
you
better
than
I
do
already.
A
B
B
A
A
Another
announcement
there
was
the
project
organizers
of
chaos.
Mesh
would
presented
on
this
call
I
think
a
couple
times
now,
I'm
had
invited
the
community
to
their
first
community
was
kind
of
weird
to
say,
community
twice
and
but
they're,
inviting
both
to
come,
join
the
first
community
meeting
on
April
30th
and
so
there's
a
link
to
their
the
details
of
that
meeting
in
the
announcements.
A
Another
announcement
was
that
there
has
I,
don't
know
who
knows
this
before,
but
there
is
a
well
a
couple
of
digital
marketing,
digital
marketing
internships
available
directly
through
layer
5.
So
if
you're
interested
or
you
know
of
people
interested,
please
point
them
there-
that
we
just
opened
up
the
description
of
that
internship
and
have
had
quite
the
influx
of
is
just
end
it.
So
so
that's
we're
fortunate
in
that.
On
that
same
note,
I
would
say
that
there
is.
A
A
Kosh
is
helping
ensure
that
we're
participating
in
google
season
of
docs
so
that
that
could
be
really
exciting
actually
and
then
also
in
community
bridge,
which
is
has
a
new
mentorship
program.
Our
SMI
work,
our
service
mesh
interface
work
is
likely
to
go
through
there
and
then
outside
of
those
internships.
There's
also
a
few
they're
going
to
be
offered
direct
through
layer,
5
I'm,
starting
with
digital
marketing,
probably
two
of
them
here.
There's
a
lot
of
work
to
be
done
and
then
looking
into
engineering
oriented
internships
this
summer.
A
D
D
We
are
working
on
so
as
I
discussed
with
him,
people
would
mean
that
he
have
reached
the
point.
There
welcome
what
is
working
but
as
per
he
suggested.
Maybe
two
meetings
before
he
said
that
why
not
be
checked
DCO,
is
it
like
it
is?
Is
it
signed
or
not
so
for
that
I
discussed
with
ashes
so
either
we
need
a
new
board,
which
already
does
the
task
or
we
need
to
put
a
condition
where
we
can
check
that
that
this,
your
board
is
fast.
D
So
for
that
we
efficient
I
were
brainstorming
and
we
did
not
really
find
any
such
solution
until
on
unless
they
include
both
the
boards,
so
I
personally,
I,
don't
know
if
a
she
says
actually
was
there
on
today's
call
or
not,
but
I
personally
was
unable
to
understand
how
to
include
one
bought
into
another,
so
that
both
tasks,
then
we
go
after
one
another,
so
yeah.
That
is
one
of
the
issues.
Anyone
have
an
idea.
D
A
Good,
it's
been
it's
Jesus
funny,
it's
been
a
while
since
I've
spoken
on
mute,
but
both
of
those
times
before
you've
been
you
have
helped
me
not
do
that.
A
couple
of
thoughts
that
others
might
jump
in
on
one
is
that,
based
on
the
work
that
'no
poor
and
she
she
had
done,
we
ended
up
including
this
just
a
couple
of
days
ago,
or
maybe
just
yesterday,
a
welcome
baat
across
all
of
the
layer.
Five
repose
at
that
welcome,
bought
I'm
a
little
confused
on
the
vernacular
or
on
that.
A
But
but
this
welcome
baat
includes
three
plugins
or
three
other
BOTS,
or
it
says
three
plugins
here,
I
actually
kind
of
think
it
includes
like
four
and
we
can
go.
Take
a
look.
This
welcome
about
is
nice
and
that
it,
you
know
it
encourages
new
users
when
they're
opening
up
an
issue
or
or
opening
a
request,
it's
a
bit
of
encouragement.
It's
also
a
bit
of
curating.
A
A
A
Okay,
very
good,
so
I
mention
this
bot,
because
this
is
the
bot
that
nip
or
is
talking
about,
also
because
it's
intriguing
to
me
that
it
wrapped
it
that
it
has
a
plug-in
model
or
that
it
wraps
I,
know
others.
Other
community
members
here
have
talked
about
or
spoken
to,
the
notion
that
is
relatively
easy
to
create
additional
bots
and
easy.
A
As
a
relative
term,
I'd
I
haven't
looked
into
it
myself,
but
what
I
was
going
to
show
is
that
we
just
enabled
the
welcome
this
welcome
bot
its
configuration
is,
is
here
and
our
use
of
it.
He
includes
a
short
comment
to
when
someone
opens
up
an
issue
for
the
first
time
when
someone
opens
up
a
new
pull
request.
A
A
A
Maybe
that
license
is
amenable
for
reuse
and
or
maybe
it's
not-
maybe
it's
very
friendly.
Maybe
it's
not
that's
a
consideration.
Another
consideration,
as
part
of
your
contribution,
is
whether
or
not
maybe
that
code
was
copied
from
somewhere
else
or
whether
or
not
it's
sort
of
your
original
work.
That's
an
open
question
that
something
needs
to
be
addressed.
A
Another
concern
is
whether
or
not
even
if
it
is
your
original
work,
if
you're
freely
giving
of
it
so
to
speak
or
if
what
what
rights
you
continue
to
have
to
it
forth
going,
and
so
those
are
three
concerns.
There's
there's
other
concerns
like
hey.
Are
you
importing
in
packages
that
have
security
vulnerabilities
or
are
you
introducing
security
vulnerabilities
and
there's
there's
a
lot
of
concerns
I
just
how
it
is
that
you
make
the
open
source
sausage.
A
If
you
will
how
you
make
the
software
so
of
one
of
the
or
of
a
couple
of
those
they're
addressed
by
in
by
our
projects
and
ever
repository
inside
the
layer,
five
IO
org
and
forces
a
requirement
around
having
a
developer
certificate
of
origin.
The
acronym
is
DCO
and
that
certificate
is
really
just
a
signature,
and
this
is
what
is
meant
by
signing
off
on
your
commits.
If
you
were
to
go
look
at
pull
requests
inside
of
the
macerate
project,
you
should
see
really
toward
the
top
of
the
pull
request
description.
A
A
Probot
being
a
framework
that
many
other
bots
are
built
on
top
of,
and
one
of
those
is
this
developer
certificate
of
original?
Just
relatively
you
know,
in
concept,
well,
relatively
simplistic
in
nature
in
terms
of
what
it
does.
You
know.
Here's
an
example
here
that
this
you
know,
Bex
Warner
has
signed
off
and
the
DCO
bot
discovered
that-
and
you
know,
checks
it
and
so
understanding
that
this
hangs
up
a
lot
of
contributors.
A
A
Understanding
the
that's
kind
of
a
hassle
and
people
don't
want
to
go
back
and
amend
all
their
commits.
There
are
instructions
in
the
contributing
in
the
contributors
guide
that
talk
about
how
to
just
sort
of
configure
your
git
command
or
your
IDE
and
I
think
we
only
have
one
IDE
example:
it's
Visual
Studio
code,
but
but
people
use
all
you
know
all
kinds
of
IDs
about
how
to
configure
those
things
so
that
those
signatures
that
sign-off
just
happens
implicitly
like
automatically
any
time
that
you
do
a
commit.
A
So
you
don't
even
have
to
worry
about
it
so
one-time
setup.
So
once
people
get
over
the
one
time
setup
that
they're
generally
doing
fine,
the
issue
is
before
that
has
happened.
They
will
stumble
into
they'll
bump
up
into
this
bot
and
the
poor,
and
if
she
are
brainstorming
about
how
it
is
to
include
an
additional
message,
that's
the
to
the
user
on
their
PR.
A
You
know
basically
beat
these
things
or
points
them
to
the
same
section
in
a
contributor
guide.
So
that's
her
ask
of
folks
on
the
call.
As
has
anyone,
does
anyone
have
suggestions
about
how
to
improve
and
improve?
Does
anyone
know
if
maybe
it's
common
practice
to
augment
the
DCO
bot?
That's
here,
I.
A
A
E
Don't
really
comment
about
this
things
in
the
BC.
Boo
itself
is
fairly
descriptive.
So
if
someone
has
the
ability
to
go
and
check
the
failure
message
on
the
beard
without
us
having
to
prompt,
that
is
also
good
enough.
I
think
we've
been
using
it
that
way,
but
you
can
see
the
use
of
the
message
right
of
the
beards.
A
You
said
because
the
you
guys
as
well
are
using
that
same
bot
and
that
when
the
bot
fails
it
does
that
give
a
description
of,
does
give
you
explicit
instructions
as
to
how
to
go
back
and
amend
your
comments
or
your
commands,
but
which
is
true.
Our
issues
is
kind
of
things
like
this,
a
Capri.
We
just
take
this
as
an
example.
A
E
A
D
D
Yeah
definitely
before
that
I
just
assembled
on
something
else,
while
going
through
different
welcome
boards.
I
also
stumbled
upon
one
welcome
board,
which
is
used
for
welcoming
newcomers
on
stock,
which
we
are
currently
doing
manually.
I
like.
I,
have
no
issue
welcoming
newcomers
for
smelly,
but
just
a
suggestion
like
everytime
in
a
newcomer,
joins
the
group.
We
can
create
a
welcome
board
for
that
as
well,
and
we
definitely
can
personally
welcome
them
as
well,
but
in
case
sometimes
someone
joins
in
any
of
us,
miss
it.
D
A
B
A
A
You
know
what
let
me,
let
me
I'll
show
you
what
those
look
like
and
we
try
to
balance
between
automation
and
that
feeling
insincere
and
then
yeah
the
manual
overhead
of
welcoming
folks.
At
some
point
we
do.
We
do
want
to
get
to
know
everybody,
but
yeah
boy.
It's
a
lot
of
it's
a
lot
of
time,
so
putter,
but
yeah,
no
good
it
would.
A
D
D
Sort
them
all
and
you
all
can
go
through
and
suggest
some
of
the
things
which
we
can
add
into
it.
Lee
and
I
discussed
that
we
will
also
add
one-line
description
to
all
the
layer,
5
projects
which
are
mentioned
here,
so
you
all
can
give
up
your
suggestions
also,
while
working
on
all
the
repositories.
I
also
don't
know
all
the
repositories
very
well.
D
A
A
So
all
to
Newport-
that's
very
much
so
needed
and
that's
very
helpful
for
those
that
all
of
you
that
have
access
to
the
mastery
community
drive
that
particular
document
actually
sits
at
the
root
level.
Now
of
the
of
our
shared
team
drive,
because
it
does
do
that
service
of
introducing
well
newcomers
and,
like
I,
said
all
old-timers
alike
to
the
lay
of
the
land
from
a
project
from
I'm.
Sorry
from
a
repo
perspective,
I'm
there
on
that
subject
and
so
I
by
the
way.
A
I
think
this
is
probably
the
first
of
a
couple
of
things
that
new
floor
is
trying
to
is
working
on
to
help
get
people
oriented
in
that
same
vein,
I'll
note
that
there
are
a
couple
of
presentations
about
nursery
and
and
a
little
bit
about
the
surface
mesh
performance
specification,
which
is
which
is
its
own
project
and
a
little
bit
about
the
landscape
and
the
work
that
people
put
into
that.
So
this
particular
presentation
is
probably
also
serves
part
of
that
same
purpose
of
being
a
general
overview,
but
to
wrap
this
topic.
A
The
thinking
of
poor
for
this
and
the
poor
is
asked
of
each
of
you
is,
if
you're
familiar
with
a
repo
or
some
of
the
work
that
that's
happening
to
come
and
give
it
just
a
short
one.
You
know
couple
of
sentences
like
this
to
describe
what
what
its
purpose
is,
so
that
others
can
others
who
either
are
familiar
with
see
or
go
or
react,
or
you
know
that
some
of
the
tech
that's
used
in
there
or
some
of
their
area
of
focus
that
excites
them
and
they'll
understand.
What's
going
on
where
to
jump
in.
A
Along
of
just
another
thought,
there
has
been
that's
occasionally:
people,
because
there
are
a
number
of
repose
people
have
missed
out
on
the
action.
So
to
speak,
the
action
that's
occurring
in
another
repository,
and
so
we
tried
to
provide
links
in
the
readme
of
each
repository.
That
will
take
you
to
like
that.
That
will
take
you
to
a
search
for
help.
The
Help
Wanted
label
any
issue
that
has
help
on
it
and
it
does
that
searches
across
the
entire
github
org.
A
So
it's
across
all
the
repos,
just
kind
of
a
verbal
reminder
that
as
you're
looking
at
issues,
if
you're
looking
at
it
on
a
single
repo,
you
you
have
a
limited
perspective,
so
I
tossed
a
yoosh
on
the
agenda
here
and
I.
Don't
know
if
I
you
she's
here,
I,
don't
think
he
is
so
this
problem
get
to
this
any
other
comments
on
the
pours
items
before
we
go
I
tossed
I'm.
Sorry
on
here
as
well,
I,
don't
think
he's.
Okay,.
F
Regarding
the
welcome
board,
which
Newport
was
talking
about
like
having
a
I,
mean
yeah
welcome
board,
so
that
I
mean
if
anyone
has
used
this
card,
you'll
notice
that
this
code
actually
writes
an
unique
message
for
every
user
it
invite
it
I
mean
it
looks
it
feels
more
personal
I
mean
if
we
could
look,
how
it
does
it
be
cold
or
have
it
like
in
every
discard,
like
channel,
you
create,
there's
a
default
welcome,
but
which
kind
of
generates
a
unique
message
based
on
your
name,
I,
guess
and
yeah.
It's
it's
like
pretty
interesting.
A
Which
is
that's
great,
that's
a
one
of
the
reasons
what
we've
only
used
bots
so
much,
because
because
the
community
and
most
of
you
pride
yourself
on
being
genuine
and
and
really
being
excited
that
others
are
here
and
so
ok.
So
this
next
item,
we
won't
go
over
here's
a
brief
update
on
the
architecture
of
nursery.
Nothing,
not
many
things
in
particular
have
changed
here.
It
was
just
I've,
been
having
a
few
different
conversations
and
realizing
that
this
graphics,
that
I've
been
pointing
people
to
are
somewhat
aged,
and
so
they
just
kind
of
uplifted.
A
A
So
it's
a
repeat
back
Raja's
question,
I,
think
for
me,
and
maybe
for
everyone
else
does
is.
That
is
an
acknowledgment
that
measure
e
will
as
part
of
providing
doing
you
know,
performance
management
and
doing
an
analysis
over
some
metrics
and
how
well
how
well
the
service
message
is
performing.
Not
only
does
mesh
regenerate
some
of
its
own
somewhat
original
shirts,
but
it
also
is
a
reckoning.
A
There's
also
recognition
that
poor
fauna
is
a
very
popular
open-source,
graphing
utility
or
charting
the
dashboard
utility
rather
and
measure
ease
purposes,
displace
or
or
redo
reinvent
that
we
help
but
to
acknowledge
that
users
have
an
investment
there
and
would
like
to
and
we'd
like
for
the
Mestre
to
fit
into
that.
So
mastery
will
connect
to
existing
grifone
an
instance
if
people
point
mastery
at
it
read
in
the
boards
and
the
charts
that
they
may
have
and
then
help
display
them
here.
A
Second
reason
that
it's
important
is
because
when
people
are
analyzing,
the
performance
of
the
service
finish,
it's
not
just
image
that
they
need
to
look
at
the
performance
of,
but
also
the
underlying
nodes
and
any
other
metrics
that
they
might
consider
to
be
important
and
so
putting
those
all
in
the
same
place
and
letting
people
go
get
them
on
the
same
time.
So
Rogers
question
is.
G
H
A
Mesh
Ria's
and
mystery
encourages
anyone
to
create
a
new
provider.
So
basically
there's
a
local
provider
that
comes
with
the
project
and
it's
called
none
and
it's
what
you
see
when
you
go
to
login
to
mystery.
Are
you
good
choice
of
your
provider?
If
you
choose
none?
Basically,
the
metrics
gets
stored
in
the
ephemeral
system
of
a
mystery
server.
So
whenever
you
want
to
end
up
a
new
instance
of
mystery,
you
wouldn't
you
wouldn't
have
those
metrics
and
they
would
be
transient.
A
A
A
It
I'll
say
this
that
if
this
mechanism
that
that's
being
used
like
is
not,
is
not
robust,
it
is
the
the
metrics
that
it
persisted
here
are
really
intended
for
the
point
in
time
that
you've
done
a
performance
test
and,
as
you
gather
like,
let's
say
that
you
ran
it
for
five
minutes.
You
ran
a
performance
test
where
you
generated
upon
too
low
hammered
on
that
service
endpoint.
We
did
a
statistical
analysis
to
say.
A
Here's
your
latency,
here's,
your
throughput,
oh
by
the
way,
here's
some
other
metrics
that
you
might
have
been
looking
at
in
your
environment
will
take
that
five
minutes
worth
of
you
know
any
number
of
metrics,
hopefully
not
hundreds
of
them,
but
just
you
know:
twenty
fifty
of
them
and
ship
those
off
for
storage,
and
so
the
solution
here
is
not
designed
to
retain
things
for
many
years
and
to
retain
them
at
very
there's.
No
aggregation!
A
A
Then
let
you
look
back
over
time
and
basically
the
thinking
there
and
the
goal
was
really
about
benchmarking
and
baselining,
and
so
the
measure
e
will
allow
you
then,
to
compare
the
results
you
can,
you
know,
go
pick
and
choose
which
which
performance
test
results.
You
want
to
compare
against
and
then
you'll
get
a
perspective
about
whether
or
not
you're,
improving
or
digressing
in
terms
of
overhead.
H
A
H
I'm
still
on
that
connection,
yeah
so
yeah,
just
only
to
given
update
that
I
have
included
the
latest
changes
that
have
been
made.
As
you
know,
we
discussed
in
the
last
committee
call
and
so
again,
everything
with
the
leg,
the
page
that
we
need
regarding
the
releases
I
have
made
that
and
if
you
want
I'll,
just
Floyd
as
a
separate
branch
or
where
we
can
test
it
out
so
Oh.
What
should
I
do
regarding
that
was
I
have
included
the
latest
changes
and
those
have
been
made
into
a
separate
branch.
A
H
Okay,
I
haven't
seen
this.
Is
it
so
that
even
those
shouldn't
be
left
out,
for
example,
all
the
changes
that
we
made
to
the
mushy
cereal
and
towards
the
ones
that
we
have
right
now.
We
have
example
all
the
new
boards
that
we
have
created
in
the
past
one
to
two
last
one,
two
weeks
late.
Regarding
that.
H
A
A
H
Actually,
I
do
update
that
as
well,
since
we
are
including
all
the
latest
changes
as
well
in
the
release,
I
mean,
if
that
that's
fine
with
you
I
can
remove
the
latest
sins
if
you
want
from
the
liquid
in
zero
point
four
point:
100
point
four
point:
zero
release,
but
if
that
is
the
case,
if
you're,
including
them,
then
in
the
layer
five
or
in
the
markdown
that
we
have
created,
we
can
include
those
changes
as
well
in
the
blog
post
as
it,
but
the
blog
post
will
be
going
up
from
the
layer.
Five
repository.
I
A
A
C
A
E
Okay,
that
seems
to
be
an
interesting
use
case,
which
we
are
also
coming
across
in
other
communities.
So
there
have
been
instances
where
Intuit
has
been
using
the.
It
was
chaos
while
they
have
some
application.
Performance
benchmark
runs
going
on
and
there
is
report
that
we
just
sort
of
created
into
the
litmus
pians
or
called
as
chaos.
E
A
E
E
A
E
We
get
with
machete,
for
let's
say
the
cluster,
which
has
deployed
a
service
mission,
so
we're
talking
about
chaos
during
the
performance.
One
of
the
the
most
we
did
in
the
measure
is
community
call.
Last
week
we
employed
this
ele
dashboard
and
in
there
something
we
did
it
for
that
demo
and
it
was
really
helpful
for
us
as
a
team,
to
sort
of
look
at
and
visualize
impact
of
chaos.
E
A
I,
don't
know
they
put
it
like
that.
We
couldn't
agree
with
what
you
said.
More
I
think
is
the
first
thing
that
visualizations
are
in
context
of
service
missions,
are
really
helpful
to
people
just
understand
what
the
heck's
going
on
and
that
that
had
been
a
road
minute
met
him
before
there
was
a
road
map
or
what
I
like
that,
but
yet
to
go
over
to
it
in
mind,
Rangers
of
visualization
but
the
most
economical
one
or
the
most
commonplace.
One
is
a
visual.
A
Like
along
the
lines
of
what
you're
thinking
mental,
you
won't
think
of
tre,
we
are
on
precedent
under
some
prototypes
of
what
I
think
that
would
be
done.
Some
technical
details
on
frameworks,
but
but
you,
but
that
capability
is
still
roadmap,
or
rather
it's
a
very
it's
something
that
we
intentionally
haven't
done,
because
we
really
want
to
do.
A
Yeah
there
isn't,
but
there
isn't
really
other
than
chart
or
in
I
think
the
product
isn't
published
and
thoughts
there
aren't
polished,
but
because
it's
a
hard
thing
to
do
and
want
to
make
sure
that,
if
your
own
best
that
we
invest
correctly,
that
you
know
that
you're
in
your
investigation,
there
may
well
spur
us
to
try
to
focus
and
giving
you're
going
there.
It
really
is.
It
really
is.
E
Associated
thing
would
be
when
there's
an
experiment
being
performed
on
a
cluster.
Let's
say
you
have
mentioned.
You
know
today
in
stone
which
is
trying
to
gauge
the
performance
and
what
on
information
would
be
useful
to
fit
in
into
the
result
of
an
experiment,
for
example.
So
what
do
you
think
is
necessary
information
that
you
would
like
to
pass
out
or
derive
out
of
an
experiments
to
result?
E
I
think
is
also
will
be
pretty
helpful,
so
we're
trying
to
put
some
kind
of
framework
in
place
in
litmus
fair
custom
information
for
each
context
of
the
experiment
can
be
pushed
into
the
resin.
So
will
be
a
that
it.
It
will
be
great
to
get
some
feedback
around.
What
kind
of
things
can
they
push
their.
A
Some
of
them
might
think
that
some
of
those
things
are
other
standards,
but
like
history,
no
showing
in
mystery
or
lady
seen
through
putting
things
it
is
maybe
go
to
other
types
of
experiments,
but
it's
it's
certainly
custom
to
service
mesh
that
if
for
nothing
else,
having
a
link
to
where
to
go,
see
those
results.
That's
clean.
It
like
I
know
that
that's
not
a
very
original
idea,
but
but
like
it,
does
actually
protect
in
a
box
for
extensibility.
E
Fish,
whereas
let's
say
you
have
a
different
set
of
resources
for
a
different
category
of
application,
we
different
databases
might
probably
have
their
own
kind
of
it
is
EXO,
and
then
there
could
be
a
really
custom
one.
You
do
not
did
not
classify
it
and
rating,
and
it's
just
a
Jason
block
that
you
push
along
at
the
inside
of
the
resource,
where
user
happens,
to
write
his
own
information
about
what
his
performance
indicators
are.
A
Yeah,
you
might
I
think
what
you're
saying
is
that
you
might
have
a
blob
so
to
speak
or
like
as
part
of
every
experiment
and
the
reporting
results
of
every
experiment
that
those
that
are
creating,
that
type
of
experiment
can
output
their
results
in
this
blob
or
like
yeah.
That
makes
sense
to
me
the
notion
there
would
be
a
link
to
more
rich
context
or
a
richer
set
of
presentation
of
those
results.
A
That's
another
one
that
might
that's
probably
fairly
Universal,
that
that
litmus
chaos
as
a
platform
or
as
a
workflow
engine
it
uses
in
some
respects.
If
you
were
to
weekly
look
at
it
generically
is
we
have
a
workflow
engine
where
you've
got
any
number
of
the
shelf
activities.
Work
like
if
these
be
chaos,
experiments
and
then
that
you
want
to
schedule
along
those.
A
Those
have
you
know
different
steps
included
and
that
you
might
be
stringing
up
a
few
experiments
in
a
row,
so
you're
sort
of
executing
workflow
and
then,
at
the
end
of
that
you've
got
ya
results.
Service,
I,
yeah
I
led
a
team
of
over
a
hundred
people
at
Cisco
building
out
a
workflow
engine.
That
was
focused
on
cloud,
automation
and
yeah.
These
concepts
are
were
hearing
all
of
the
considerations
that
that
that
we
had
worked
on
the
I'll
say
this
on
the
reporting,
but
is
that
just
you
know
with
with
eat
worthy.
A
Experiments
but
they
would
have
their
own
status,
whether
or
not
that
experiment
was
that's.
We
executed
or
not.
You
know
in
in
the
string
of
experiments
that
might
run
in
the
context
of
the
technologies
that
were
being
used
for
that
product
customers
could
optionally
deploy
I,
think
it
was
Microsoft,
sequel
server
and
what's
it
called
the
dashboard
visual
reports,
writer
or
fewer
or
there's
some
other
component
to
Microsoft
sequel
server.
A
I'm,
actually
it
but
I
forget
what
it's
called,
but
so
the
results
of
each
experiment
of
that
workflow
engine
would
be
published
in
an
XML
format
and
then
view
those
in
web
browser
and
I
know.
This
is
sort
of
using.
Maybe
maybe
some
dated
technology-
maybe
not,
but
when
you
publish
an
XML
format
they
would.
They
would
then
use
to
transform
and
markup
that
XML
in
a
format
which
was
presentable
in
a
browser
and
the
XSL
T.
Maybe
was
a
good
point.
A
Yeah
I
envy
your
project,
because
it's
there's
a
lot
of
interesting
challenges
and
there's
sort
of
a
lot
to
wrap
your
arms
around
and
then
what
is.
Sometimes
people
will
come
over
and
measure
the
worth
of
the
project
on
well.
How
many
experiments
whoa
wait?
A
second,
that's
not
real.
Like
yes,
it's
certainly
part
of
the
venue,
but
please
don't
ignore
all
the
other
hard
work
that
went
into
the
overall
engine.