►
From YouTube: 20180711 testing commons
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
So
if
those
things
we
are
thinking
about
those
two
changes
to
the
queue
midium
Dean,
D,
cluster
I've
done
I
think
we
can
progress
with
this
work-in-progress
PR
to
the
test
cluster
framework
and
drive
out
more
features
regarding
the
electron
config
and
especially,
regarding
the
shape.
If
that
makes
sense,
it
doesn't
make
sense
to
me
it
does.
Does
it
make
sense,
study,
books.
B
B
B
Yeah
other
than
that
I
said,
the
pr
which
is
currently
open
for
the
test.
Cluster
framework
is
very
rough
when
it
comes
to
the
config
and
yeah.
Basically,
when
it
comes
to
everything,
but
still
if
anyone
is
interested
in
looking
into
which
direction
we
are
thinking
of
going,
please
feel
free
to
check
it
and
any
any
comment
or
any
anything
regarding
that
is
very
much
appreciated.
I
think.
A
A
I
don't
know,
I
have
not
talked
with
the
mini
cube
folks
in
forever,
and
I
do
know
that
they
were
also
creating
like
an
interface
library,
for
doing
a
configuration
and
setup,
and
there
was
a
bunch
of
the
reason
why
dinned
was
chosen
originally
was
that
mini
cube
did
not
offer
the
features
that
we
wanted,
basically
of
being
able
to
have
the
multiple
node
configuration.
That
was
a
key
feature
that
was
required.
A
I
have
not
touched
base
with
any
of
those
folks
in
recent
memory
of
to
see
whether
or
not
they've
added
that
capability
or
whether
or
not
they've
developed
a
clean
client,
interface
and
I
also
know
that
there's
four
didn't
implementations
more
antis
was
the
most
ubiquitous
lis
known.
This
has
the
largest
mind
share
for
the
solution,
but
there
are
other
folks
who
have
done
it
from
seed
cluster
life
cycle
perspective.
A
So
that
way
you
could
just
transition
all
of
this,
because
the
current
implementation
from
Aransas
is
bash
right,
which
is
not
ideal
if
you
were
trying
to
like
reference
trucks
and
passes
almost
through
and
make
it
all
clean,
but
I
don't
know
what
the
state
of
that
is
so
I
think
understanding
the
state
of
where
some
of
these
other
pieces
are.
I
know
that
you
can
get
the
implementation
for
that
didn't
in
place
and
you
might
even
want
to
wrap
it
internally.
B
A
A
But
I
will
definitely
definitely
review.
I
saw
it
come
through.
My
Mac
did
an
update
and
destroyed
my
window,
so
I
did
get
a
history
back
on
Chrome
I
had
a
window
a
set
aside
and
I
was
going
to
look
at
it
this
morning
before
we
had
this
meeting
and
then
I
did
a
Mac
update
and
then
my
productivity
with
the
crap.
B
A
I
do
know
that
they
were
separating
out
the
component
config
work,
and
that
was
a
big
one,
because
what
happens
is
some
of
the
parameters
are
very
generic
and
then
all
of
us
and
you
get
to
component
config
the
component
config
links
into
all
this
other
stuff.
So
that
one
was
the
I
think
the
thorny
detail
of
the
the
buckyball
seal
I
picked
up
one
thing
and
you
had
this
entire
hairballs
nest
of
dependencies,
so
that
was
planned.
It's
tentatively
planned
I
need
to
walk
through
that
stuff.
To
do
that,
maybe
today
or
tomorrow,
okay.
B
C
D
I'm
Tim
I
am
actually
the
release
lead
for
1.12,
so
I'm
just
trying
to
pay
a
little
closer
attention
to
test
related
activities
during
the
cycle
and
I
know.
This
isn't
exactly
related
to
the
release.
The
discussion
here,
but
just
to
have
a
a
sense
of
what's
in
flight
and
things
coming
down
the
path
in.
A
D
D
A
There
there
is
definitely
interested
parties,
I
think
I.
Maybe
what
we
could
do
this
cycle,
which
goes
beyond
the
scope
of
just
the
technical
work,
is
to
do
some
more
mindshare
broadcasting
and
I
could
pay
you
and
start
that,
maybe
on
community
stuff,
because
there
are
plenty
of
folks
who
don't
aren't
core
developers
but
are
basically
creating
integrations
with
kubernetes.
This
is
specifically
meant
to
target
part
of
this
is
specifically
meant
to
facilitate
that
level
of
integration
right
to
make
it
easier
for
them
to
set
up
CI.
A
A
So
there
are
plenty
of
other
folks
who
are
building
third-party
integrations
in
without
having
to
actually
spin
up
a
whole
cluster
it
on
a
provider.
You
should
be
able
to
have
a
full
test
environment,
hermetically
sealed
for
CI.
Without
you
having
to
even
even
mini
cube
itself,
there's
only
one
node
right
and
if
you
want
to
be
able
to
simulate
in
a
multi,
node
environment
that
is
pretty
important
totally.
D
Agree
for
death
test
I
mean
they're.
What
I
haven't
looked
at
the
spreadsheet
in
a
while,
but
last
I
looked
probably
in
May.
There
are
like
70
distributions,
so
there's
a
lot
of
people
doing
this
and
there's
a
big
need
than
for
for
pre,
testability
and
testing.
Also
on
the
integrations,
you
can't
just
rely
on
up
streams,
I
commit
going
into
upstream
and
getting
the
CI
results
back
then
that's
way
too
late,
yeah.
A
So
I
think
what
I
try
to
do.
Maybe
I
can
do
with
this
group
is
craft
a
statement
and
then
I'll
I'll
put
it
on
the
slack
channel
to
see.
If
folks
want
to
I
will
craft
a
statement.
I
will
have
Liz
wordsmith
it
because
I'm
terrible
and
tell
me
how
wrong
I
am
and
then
and
then
that
I'll
pass
it
off
to
the
group
here
to
take
a
take,
a
look
to
try
and
see.
If
it
we
went
on
modify
it.
Does
that
seem
like
a
fair
action
item
yeah.
A
B
Oh
one
thing:
maybe
there
is
this
cube,
build
a
thing
which
uses
the
test
cluster
framework
for
their
testing
and
eventually
I
want
to
talk
to
them
and
also
have
them
check,
basically,
our
API
or
whatever.
We
are
working
on
to
validate
that.
They
are
also
happy
with
that.
As
users
of
the
test
framework.