►
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
A
A
B
A
A
A
B
A
A
B
A
That's
right
so
I
mean
so
the
idea
is
to
well
essentially
kind
of
started
off
by
the
sorry
like.
Initially
there
are
a
few
people
who
all
had
their
own
implementations
where
they
had
some
kind
of
object
that
described
their
cluster
right.
The
object
looked
like
a
typical
converting
use
object,
but
the
way
that
those
were
well
kind
of
like
the
life
cycles
of
those
objects
and
where
they
lived
or
whatever
wasn't.
You
know,
what's
very
specific
to
each
individual
implementation.
How
was
this
the
cluster
API
working
group?
A
There
are
some
convergence
taking
place
right,
so
I
guess.
Yes,
there
are
a
few
examples
out.
There
were
of
the
providers
that
existed
before
class
they
P
I
existed
under
and
now
they
kind
of
trying
to
converge.
But
it's
it's
happening
at
a
very
low
end
of
it
and
it's
kind
of
complicated
and
personally
I
don't
know
I
have
mixed
opinions,
but
how
it
is
actually
looking
at
the
moment
from
usability
perspective.
A
But
essentially
the
idea
is
that
you
know
we
define
these
api's
that
have
providers
of
the
road
and
it's
not
part
of
Cabrini's
project.
We
just
sorta
gather-
and
this
calls
and
there's
a
common
project
where
some
of
the
useful
bits
leave
and
well
the.
In
essence,
people
find
different
things
a
whole
time.
A
A
I
think
I
think
those
are
kind
of
vague
at
the
moment
right.
So
it's
like
there's
some
stuff
that
is
common
and
then
there's
stuff
that
is
specific
to
any
individual
provider
right.
So
the
people
who
work
on
providers
they
have
their
own
goals
and
milestones
and
they
link
towards
you
know
complete
implementation
of
some
sort
on
yeah.
So
it's
a
it's
kind
of
loose
at
the
moment
so
that
there
is
enough
freedom
for
people
to
kind
of
build
their
own
things,
and
you
know,
there's
sort
of
like
I
mean
I.
Guess
it's!