►
From YouTube: KubeVirt Community Meeting 2023-03-15
Description
Meeting Notes: https://docs.google.com/document/d/1nE09vQWcCTW-9Ohe9oCldWrE0he-T_YFJ5D1xNzMtg4/
A
All
right,
we've
got
a
bunch
of
people
already
here
and
we're
two
minutes
past
the
hour.
So
we
may
as
well
start
welcome
everybody
wherever
you
are
and
whatever
time
it
is
to
the
convert
community
meeting.
A
A
All
right,
I've
got
a
few
things.
It
looks
like
a
lot,
but
we'll
cover
very
quickly
just
because
it's
a
giant
list
of
cfps
that
are
open
at
the
moment.
The
first
and
most
important
is
that
Cuba
Summit.
A
A
The
schedule
is
in
the
two
links
there
and
you
will
need
to
register
in
order
to
attend.
It
is
free.
All
you
need
to
do
is
register
with
the
cncf
events
platform
and
yeah
and
then
and
then
turn
up
in
two
weeks
time.
It's
a
a
dense
and
interesting
schedule,
so
I
highly
recommend
checking
out
and
tagging
a
couple
of
things
will
be
interesting
for
you.
A
The
next
is
just
a
giant
list
of
cfps
I
I!
Don't
do
this
all
this
time,
but
I
had
to
do
it
recently,
so
I
figured
I'd
paste
it
here.
We've
got
two
Dev
comps,
multiple
kcds
and
also
open
source
Summit,
EU
2023..
A
So
that's
all
there
I
do
try
and
keep
the
cube
vert
community
events
page,
which
is
in
the
wiki
up
to
date,
and
all
these
things
are
in
there
and
if
you're
new
to
this
Wiki
I
haven't
really
looked
at
it
much
the
Linux
foundation,
events
and
the
cncf
community
events-
I,
don't
know,
that's
where
the
kcds
are.
A
That's,
where
a
bunch
of
other
things,
a
lot
of
things
might
Escape
my
notice,
and
so,
if
you
do
have
20
minutes
in
a
week
or
something
and
you
feel
like
going
through
them
and
something
jumps
out,
please
let
me
know
I'll
add
to
this
add
to
this
Wiki
and
I'll
I'll
popularize
it,
and
we
can
support
you
in
your
proposals
and
what
have
you
so
yep?
That's
it
from
me.
B
Hey
yeah,
so
I
I
want
to
cover
So,
Daniel
and
I
want
to
talk
a
little
bit
about
the
next
release.
So
does
everyone
that
is
aware
we
covert
zero
five
on
release
just
recently
went
through
on
the
new
Cadence.
So
let
me
progress
everyone
on
on
migrating
to
this
new
release,
schedule
and
I.
With
this
release,
that's
going
to
be
coming
more
changes,
I
think
we're
going
to
see
and
we're
going
to
discuss
a
bunch
of
them
and-
and
you
know
in
future
meetings,
but
I
want
to
talk
about
here.
B
I
kind
of
want
to
set
expectations
with
the
community
in
terms
of
what's
ahead
with
the
next
release
and
and
so
I
I
have
here
a
schedule
but
I
before
I
go
through
the
schedule,
though
I
I
want
to
turn
over
to
Daniel
and
Daniel.
Can
you
talk
a
little
bit
about
some
of
your
expectations
like
going
into
this
next
release?
What
are
the
things
that,
like
the
community,
needs
to
expect?
D
C
Folks,
yeah,
okay,
cool
yeah,
so
to
chime
in
about
What.
What
we
got
out
of
the
last
I
should
say:
probably
I
should
call
it
somehow
confusion
about
what
Lanes
should
actually
be
getting
the
release
or
not
I.
In
a
nutshell,
it
was
like
that
we
settled
on
on
so
we
want
what
we
first
wanted
to
achieve.
Was
we
wanted
to
change
the
base
node
platform
on
the
provider
to
to
a
newer
one?
So
that's
why
we
created
the
126
provider
on
Central
stream
9..
C
C
So
we
had
to
some
confusion
about
some
tests
that
were
not
running
or
that
were
failing
actually,
and
we
had
some
conclusion
about
how
we
should
proceed
on
that
that
was
caused
in
part
by.
We
us
not
being
really
clear
what
we
exactly
we
wanted
to
have
as
a
base
platform
for
testing.
C
So
what
we
got
out
of
that
was
in
the
end,
we
ended
up
with
two
provider
versions
that
were
testing
the
release,
so
we
had
eight
base
Lanes
regarding
to
the
sick,
Lane,
so
the
two
times
the
sick
Lane
for
each
126
provider,
except
was
eight
and
centers
nine
base,
and
then
there
was
another
bit
of
confusion
around
how
or
what
Lanes
should
be
then
be
gating
the
mergers.
C
So
in
the
end
we
have
we
fixed
all
that,
and
we
settled
upon
that.
We
want
to
have
said
to
us
9
as
a
base
for
for
testing
on
the
Node
OS,
and
also
we
want
to
have
a
PSA
enabled
and
so
on.
But
that
came
out
pretty
pretty
late,
so
yeah
it
was
a
lot
of
confusion
and
what
we
got
out
of
the
Retro
which,
where
we
discussed
about
how
we
should
proceed
next
time,
would
be
that
we
want
to
make
clear
or
determined
by
a
separate
Community
meetings.
C
Somehow
not
I'm
not
exactly
sure
if
this
should
be
a
separate
community
meeting,
but
it
should
be
inside
the
community
meeting,
for
example,
where
we
want
to
make
clear
what
the
next
testing
platform
for
the
next
kubernetes
release
should
actually
be
defined.
Like
so
like
what
features
does
it
need?
What
Bezos
would
probably
need
and
what
other
things
would
we
want
to
have
in
order
to
be
sure
where
we
want
to
work
against?
C
So
what
we
want
to
do
is
we
want
to
discuss
before
we
start
the
next
provider
work
to
to
to
have
it
defined
somehow
by
the
community,
yeah
I
think
I
think
that's
in
a
nutshell
or
in
a
bigger
nutshell,
probably
what
we
discussed
Ryan
did
I
forget
anything.
Do
you
do
you
want
to
keep
me
honest,
or
do
you
want
to
add
anything
on
this.
B
No,
no,
that
what
you
said
sounds
good
to
me.
Yeah
I
mean
I,
I
was
gonna,
I
mean
the
only
thing
I
would
say:
I
mean
I.
I
was
kind
of
I
was
about
to
write
this
as
like
I
was
trying
to
summarize.
Basically,
like
you
know,
we
def,
let's
define
we
wanted
to
find
the
configuration
for
for
the
testing
Wings
well
in
advance
for
this
next
release,
and
then
we
want
to
clarify
like
that,
these
all
the
Sig
Lanes,
the
the
jobs,
need
to
be
voting
and
passing
before.
B
What
did
we
say
before
we
cut
the
the
release?
Branch
I
think
that's
what
it
was.
C
C
So
yeah,
just
just
as
a
last
sentence
on
this
this
topic
next
time,
we
want
to
be
a
little
bit
better
prepared
so
that
we
have
a
more
defined
Baseline
on
which
we
can,
which
we
can
work
again
so
that
we
don't
so
what
the
confusion
caused
was
a
lot
of
duplicate
work
that
we
did
regarding
duplicate
Lanes.
Then
we
had
to
solidify
anything
against
changing,
changing
things
and
even
porting
stuff
back
to
the
release
branch
in
behind.
C
So
that
was
really
not
not
that
good
from
a
retro
perspective,
scene,
I'd,
say
so.
B
Short,
so
should
we
go
through
the
exercise
now
of
actually
going
through
and
defining
this?
Do
we
have
the
right
people
and
forum
for
this
like?
Should
we
take
a
few
minutes
here
and
can
we
make
the
decision
of
like
you
know
what
you
know?
What's
the
configuration
I
think
like
things
that
we
wanted
to
cover
right?
These
were
like
the
things
I
had
for
notes
that
could
affect
us
right
like
the
release,
the
oldest
version.
B
C
Yeah
and
from
my
opinion,
we
should
probably
we
should.
We
could
probably
as
well
do
that
right
now.
B
B
B
Okay,
it
sounds
like
there
are
any
I
think
what
we
need
to
do.
Daniel
then,
if
there
aren't
any
specific
configuration
that
we
need
to
have
I
think
then
maybe
we
can
do
is
take
this
to
the
mailing
list
and
if
there
isn't
anything
specific,
then
I
think
maybe
what
we
can
kind
of
carry
forward
is
that
we
keep
the
status
quo.
We
keep
the
existing
configuration
in
place.
C
B
C
Say
I'd
say
that
that
we
should
somehow
Define
that
the
configuration
for
127
will
be
the
same
as
the
configuration
for
the
126
provider,
that
that
should
be
something
that
we
should
probably
point
out
and
yeah
I
think
that
Cuba
deaf
would
probably
be
a
good
place
for
people
to
chime
in
if
they
disagree.
That
makes
sense.
If
no
one
here
already
disagrees.
B
Okay
sounds
like
there
sounds
like
there
isn't
any
comments:
okay,
okay
and
one
other
thing
about
expectation
actually,
I
want
to
add
in
here
and
Daniel
feel
free
to
chime
in
I.
Think
what
would
be-
and
if
you
might
have
mentioned
this
I
alluded
to
it.
I
think
what
it
would
be
useful
is
that
maybe
what
we
could
do
is
like
in
in
these
calls.
B
If
we
have
the
right
Representatives
we
can,
we
can
talk,
we
can
just
bring
up
where
we
are
in
the
release,
just
to
sort
of
give
make
people
aware
of
the
progress
like
kind
of
what
I
have
in
mind.
Daniel
is
like
when
you
start
working
on
the
provider.
You
know
that's
that's
kind
of
a
milestone
for
us
when
we,
when
we
have
the
provider
complete
and
we're
starting
talking
about
the
CI
Lanes
being
voting,
and
that's
like
another
important
Milestone.
So
like
things
like
that,
we
can
I
think
would
be
worth.
B
Maybe
we
can
reserve
a
section
of
the
meeting
in
this
Community
College
just
to
get
the
word
out
so
that
people
are
aware,
like
hey
it's
time,
to
start
working
on
these
voting.
Lanes,
you
know
starting
to
start
working
on
stabilizing
against
this
code
and
and
then
same
with.
You
know
when
we're
getting
close
to
doing
when
we're
when
we
Branch,
when
we
feature
freeze
and
then
we
kind
of
working
towards
the
final
release
same
same
kind
of
concept,
we
use
the
community
call
to
communicate
with
where
we
are.
C
Actually
that
makes
total
sense
and
and
I
think
at
some
point
in
earlier
meetings.
We
did
that,
but
since
I
think
for
quite
a
while,
the
the
introduction
of
the
of
the
kubernetes
providers
went
pretty
smoothly,
so
we
disregard
it
or
we
stayed
away
from
doing
this
and
yeah
now
now
that
we
are
so
I
think
we
should
have
done
that
also
upfront,
because
we
were
changing
the
kubernetes
provider
entry.
C
Somehow,
since
we
were
starting
with
an
RC
candidate
already
so
I
think
in
hindsight,
we
should
have
done
that
right
away
so
because
the
provider
said
I
was
was
being
changed.
Somehow
yeah
I
think
that
makes
a
lot
of
sense
to
just
keep
a
quick
update
on
how
we
stand
or
where
we
stand
on
the
kubernetes
provider.
That
makes
sense.
B
E
B
E
B
E
And
you
know
in
the
configuration
because
that
we
deploy
a
certain
version
of
CDI
automatically
at
this
point
so
and
that's
probably
not
the
version
that
CDI
CDI
releases
at
the
same
Cadence
so
or
maybe
like
a
week
later.
So
the
CDI
version
that
we're
testing
against
will
be
older
than
the
actual
release.
Cdi
version
do.
C
That's
a
really
interesting
point:
yeah
you're,
totally
right
yeah,
we
always
just
consuming
inside
the
cupid
CI.
So
for
everyone
who
is
not
aware
of
that,
we
have
the
CDI
bundled
inside
the
cupid
CI
provider
at
the
moment,
and
we
are
just
consuming
the
released
versions
and
it
might
make
sense
when
we're
setting
up
a
new
provider
to,
for
example,
also
include
newer
versions
like
RC
versions
or
something
like
that
or
even
beta
versions.
I,
don't
know
what
makes
the
most
sense
here,
but
CDI.
E
Cdi
is
I,
think
the
last
release
we
we
did
on
RC
a
couple
of
weeks
before
we
actually
made
the
CDI
release
and
before
that,
we've
never
made
an
RC
or
a
beta
version,
or
anything
like
that.
Where
we're
just
releasing
every
three
weeks-
and
you
know
you
would
just
grab
whatever
the
latest
was,
but
since
we're
now
on
the
same
Cadence
that
you
know,
we
probably
need
to
get
CDI
sorted
a
little
bit
before
foreign.
B
So
Alexander
that
would
mean
so
that
would
mean
then,
when
you
guys,
you
have
your
Cadence.
It
means
that
you
guys
need
to
tag
these
releases
for
CBI
and
then
so
like
thinking
about
this,
to
turn
the
schedule
like
before
we
can
we
like
Daniel's
working
on
the
starts
working
on
the
127
provider.
We
need
to
have
we're
saying
we
would
want
to
have
a
CDI
release
candidate
somewhere
that
we
would
consume.
E
C
I
mean
I
mean
we
could
still
sorry
to
Chairman.
Ryan
I
was
just
thinking
we
can.
We
can
still
just
install
another
or
a
more
recent
CDI
version,
I
guess
from
from
from
the
repository
somehow
so
now
that
I
think
of
it
I
think
it
makes
the
most
sense
to
just
bundle
the
the
stable
version
with
the
qvci
provider.
C
But
if
people
need
more
advanced
features
like
from
unreleased
CDI
versions,
then
it
will
probably
make
sense
to
just
install
that,
like
like
in
the
usual
way
so
and
and
just
yeah.
The
the
only
backdrop
drawback
would
be,
then
that
that
we
just
probably
would
not
spare
the
bandwidth
somehow
that
we
that
we
get
Now
by
just
using
whatever
is
the
latest
release.
Cdr
SML
right
does.
E
You
want
to
use
a
a
more
recent
CDI
version
if
CDI
makes
any
major
API
changes
and-
and
we
haven't
done
that
in
a
while
and
I'm,
not
you
know,
I,
don't
think
we're
going
to
do
it
in
the
foreseeable
future,
so
I
think
we're
okay
with
just
consuming
whatever
the
stable
is
I
just
wanted
to
mention
CDI
here,
because
there's
a
lot
of
testing
that
uses
CDI
and
if
we're
using
a
weird
feature
in
CD
our
new
feature
in
CDI
that
you
know
needed
for
the
testing,
it
might
start
failing.
C
Yeah
I
mean
I
mean
we
could
probably
introduce
something
like
like
a
mechanism
in
qubit
CI
that
would
probably
grab
the
latest
or
or
a
different
version
that
that
you
would
need
to
consume
somehow
but
yeah
I
yeah.
You
can
either
just
install
it
by
by
using.
C
Somehow
or
yeah
I'm
struggling
a
little
bit
I
I
guess
I'll
keep
my
most
close
now
sorry
for
that.
Well,.
B
I
I
guess
the
I
mean,
from
my
perspective
it's
it's
sort
of
what
level
of
support
like
I
mean
this
is
this
sounds
like
like
it
would
be
a
big
commitment
from
you
Alexander
to
do
this
kind
of
thing
and
and
for
what
you're
saying
is
that
the
gain
is
is
like,
since
there
aren't
all,
since
you
haven't,
had
any
major
breaking
changes,
it's
sounds
like
the
gain
is
well,
we
get
maybe
one
newer
release
version,
but
it
might
not
be
something
we
see
like
I
guess
what
I'm
saying
is
like
like
this
bullet
point
here
is
like.
B
Maybe
we
should
wait
till
this
use
case
appears
where
we
have.
We
want
to
do
a
cubit
release
and
we
need
a
specific
CVI
feature.
That's
not
going
to
be,
that's
only
going
to
be
in
the
newest
version
of
CDI,
and
maybe
that's
when
we
should
look
doing
this.
Otherwise,
it
sounds
like
it's
going
to
be
a
lot
of
work
and
a
big
commitment
from
you
to
be
able
to
pull
us
off
exactly.
E
F
E
Think
you
should
leave
it
as
it
is
right
now
until
we
actually
have
a
need
for
it.
I
I
just
wanted
to
mention
it,
so
we
consider
it.
That's
all
and
I
I
think
after
talking
through
I,
think
we
can
just
consume
the
whatever
the
stable
CDI
is
in
my
lanes,
and
if
we
run
into
an
issue
there,
we
can
talk
about
it.
B
Sounds
good
that
makes
sense
to
me,
I
think
I
I
think
that's
probably
the
right
way
to
go
yeah!
Let's,
let's
keep
this
in
the
back
of
our
minds,
it's
good
to
know
that
we
can
now
that
the
releases
some
of
the
same
Cadence
this
is
possible.
We
can.
We
can
consider
this
as
an
option
and
if
it
becomes
something
that
we
consistently
want
to
do,
then
maybe
we
can
look
at
making
it
a
consistent
feature
that
is
supported.
Okay,
all
right.
Any
other
comments
and
thoughts
about
this
before
I
go
to
the
schedule.
F
You
know
I
heard
a
quick
question
so,
while,
while
talking
about
releases,
one
thing
I
was
trying
to
find
out
is
the
upgrade
test.
That
is
a
kind
of
test
where
current
version
of
keyword
is
installed.
We
run
a
bunch
of
tests.
That
version
is
upgraded
to
the
latest,
one
that
we
are
going
to
release
and
make
sure
that
things
continue
to
work.
F
Do
we
have
lanes
that
that
track
those
kind
of
tests
I
would
be
interested
in
finding
out
that
the
upgrades
are
working
right
before
the
release.
C
I
think
the
operator
line
does
that
I'm
I,
hope
someone
can
keep
you
on
honest
on
that,
but
I
think
so
even
we
even
had
to
change
a
little
bit
when
we
were
trying
to
test
the
upgrade
from
o58
to
59,
since
59
is
PSA
enabled
and
58
is
not
so
of
course,
upgrade
on
PSA
enabled
cluster
would
not
work
for
59.,
so
I
think
we
had
to
what
was
it
again
yeah
we
had
to
split
the
lanes
into
one
part,
PSA
enabled
and
one
PSA.
C
Still
see
this
in
the
o59
Lane
configuration
somewhere,
okay,
yeah
did
I
forget
anything
any
anyone
else
which
I've
been
here.
F
So
one
maybe
we
can
take
this
discussion
discussion
on
slack
but
like
I,
had
a
follow-up
question
as
to
when,
when
you
say
the
cube
word
operator,
operand
test,
does
it
actually
test
the
the
entire
life
cycle
of
VM,
or
it
just
says
that
the
upgrade
is
working
as
expected.
F
Yeah
now
I'll
share
more
thoughts
on
on
slack,
but
what
I
was
thinking
is
that,
if
we
have
some
kind
of
test
that
can
keep
the
API
backward
compatibility
checks
across
our
API
surface,
that
would
that
would
help
us
gain
confidence
in
in
the
upgrades
that
are
working
and
right
before
the
release,
we
can
track
those
those
kinds
of
tests,
yeah.
D
So
what
we
do
is
we
downgrade
for
the
previous
release
and
then
we
do
upgrade
to
new
release,
which
is
basically
Main
in
this
case
right,
and
we
make
a
couple
of
VMS
in
the
old
release
and
we
make
sure
they
can
be
migrated
after
they're
already
after
the
upgrade
or
they
are
still
running
so
yeah.
We
should
have
some
confidence.
D
B
All
right,
let's
go
to
the
schedule:
can
you
scroll
down
Andrew
a
little
bit
all
right?
That's
good!
Okay,
so
I'm
gonna
have
to
change
the
dates
a
little
bit
because
we're
we're
already
a
little
a
little
off
on
a
few
things,
and
so
basically
what
the
the
idea
here
is
that
in
in
the
March
timeline
here,
what
we
want
to
do
is
we
want
to
tag
an
alpha
off
of
Maine
and
we
want
to
start
the
127
provider.
B
Kubernetes
has
already
released
it's
127,
Alpha
three,
so
they're
already
far
along
with
their
next
release.
So
the
idea
is,
we
want
to
start
so
we're
going
to
get
a
tag
for
Alpha
and
we
want
to
start
the
work
on
the
provider
so
going
to
April.
B
We
there'll
be
a
second
tag.
We're
going
to
call
this
alpha.1,
so
it'll
be
a
second
tag
and
then
we
want
to
have
at
this
point
a
pre-submit
job
based
on
the
127
provider.
So
the
idea
is,
we
can
just
run
the.
B
So
that's
April
and
may
the
goal
is
that
we
we
have
our
CI
Lanes
voting
on
the
new
provider
so
that
CI
Lane
127
is
up
and
we're
and
we're
we're
now
have
precinate
John's
running
everywhere
against
rprs
and
and
their
voting,
and
then
we
hit
June
June
is
when
we
want
to
have
our
feature:
freeze,
release,
candidates
and
the
the
release.
B
So
this
is
important
that
we
close
in
on
having
the
127
Lanes
being
fully
voting
and
enforcing
and
we're
testing
against
this,
and
and
we
hit
our
branch
in
in
the
beginning
of
June,
and
then
we
go
through
our
usual
stabilization
phase
and
do
our
release.
So,
just
to
summarize,
it's
it's
a
few
phases.
It's
just
so
so
March
we're
gonna
March,
the
provider.
April
is
going
to
be.
We
work
on
adding
a
pre-submit
job
based
on
the
new
provider.
May
is
going
to
be
working
toward
making
Lanes
voting.
B
Okay,
any
questions
and
thoughts
from
people
on
that.
A
I
have
one's
vague
question,
which
said
this
looks
like
we're:
releasing
10
weeks
after
the
kubernetes
127
release.
Is
it
about
10
weeks?
Thereabouts
is.
Is
that
something
we're
looking
at
maintaining
over
time
or
will
we
eventually
look
to
shorten
that.
B
Yeah,
so
it's
a
good
question,
so
the
what
we
have
said
in
the
in
the
for
for
releases
that
we
want
to
do
I
think
it's
plus
it's
about
about
plus
eight
from
the
eight
weeks
from
the
kubernetes
release.
B
That's
like
our
it's
going
to
be
at
least
the
initial
Target,
this
one,
the
math
just
kind
of
worked
out
that
it
ends
up
being
a
little
bit
more,
so
the
so
the
kind
of
second
part
of
your
question
of
whether
this
can
be
shortened.
B
It's
possible
I
think
where
there
are
some
other
factors
at
play
here
like
particularly
when
we
talk
about
like
look
at
fenders
people
who
are
using
this
stuff.
We
want
to
have
some
time
after
the
kubernetes
has
been
released,
to
make
sure
that
that
any
features
that
we
need
to
have
against
that
release,
get
developed
and
get
into
tree
before
the
releases
is
cut.
B
So
there's
this
there's
a
little
bit
of
time
in
between
so
that's
kind
of
that
eight
week,
Gap
that
we
want
to
use
to
make
sure
that
we
we
develop
any
of
those
features.
So
it's
possible
I!
Guess,
as
the
answer
is
that
it
could
shrink
it's
just
really
dependent
on
you
know
whether
we
can
come
to
an
agreement
that
you
know,
we
don't
need
as
much
time
and
our
event
and
vendors
don't
need
as
much
time
to
work
on
those
features,
and
maybe
then
this
can
be
lowered.
C
I
mean
I
think
if
I,
if
I
may
chime
on
this,
which
I
mean
on
this,
that's
actually
why
we
are
wanting
to
discuss
the
base
platform
which
we
are
testing
on,
which
actually
is
like.
So
so
we
are
just.
C
We
are
trying
to
test
as
early
on
as
as
possible
against
the
new
release
of
kubernetes,
so
we
of
course
Target
RC
or
even
earlier
versions
to
be
included
inside
the
cupidity
I
provider,
so
that
we
can
be
as
sure
as
possible
that
we
can
land
as
soon
as
possible,
as
as
it
gets
somehow
so.
Yeah
so
like,
like
Ryan
already
said,
I
think
this
could
be
shrinked
if
we
are
successful
in
providing
a
stable
provider
for
testing
as
soon
as
possible.
B
Okay,
well,
that's
that's
all
I
had
for
for
the
schedule
and
and
for
the
next
review,
so
I'll
we'll
have
a
lost
involved.
Mailing
list
thread
so
keep
an
eye
on
for
those.
If
you
have
any
more
questions
or
comments,
thank
you.
A
Just
before
we
wrap
up
with
this,
we
talked
about
on
a
regular
basis.
I
think
every
Community
call
will
have
a
look
and
just
check
in
where,
in
the
schedule
we
are
and
celebrate
the
Milestones
as
we
pass
them
did
we
want
to
have
like
do
we
want
to
copy
this
and
move
it
up
to
the
top
of
the
template,
or
do
we
want
to
have
this
in
a
central
spot
like
in
the
Wiki
release
that
we
just
refer
to?
B
Yeah
I
like
the
idea
of
having
this
in
a
Wiki,
and
then
we
can
open
the
web
page
and
and
review,
and
you
know
see
as
we're
progressing
through
our
milestones
and
just
raise
them
as
we.
You
know
as
we
approach
them
as
I.
A
Mean
yeah
sounds
good
and
yeah,
so
it
seems
like
you
had
this
pre-prepared.
Is
this
somewhere
now
or
is
this
just
you've
got
some
of
the
local
and
you're
still
working
on
it.
B
This
was,
it
was
a
so
I
was
originally
in
the
wiki
and
then
I
copied
it
and
made
some
modifications
and
yeah
I
need
to
bring
it
back
to
the
wiki
I
gotta.
If
you
I,
don't
have
permissions,
though
so,
if
you
would
do
or
I
was
gonna
ask
Fabian
to
do
it
then
please
do
I
will
need
to
make
modifications,
though,
because
like
we
haven't
tagged,
Alpha
zero.
Yet
so
there's
there's,
but
if
you
want
to
take
what's
here,
that's
fine
and
we
can
do
modifications
later.
That's
that's!
Okay,
too.
A
A
All
right
thanks
for
that,
nothing
on
the
open
floor.
But
if
anyone
wants
to
add
something
there,
then
we
will
have
time
while
we
run
through
some
of
these
pull
requests
that
require
some
attention.
A
Similarly,
if
you
have
any
pull
requests
that
require
attention
to
anything
that
you
want
to
highlight
from
the
mailing
list
or
any
bugs
that
have
come
up
that
need
attention,
I've
tried
to
grab
the
ones
that
jumped
out
at
me,
which
we'll
run
through
now,
but
by
all
means
as
we
go
through.
Please
please
add
them.
A
Console
API,
it
needs
an
okay
to
test.
It
doesn't
look
like
it's
got
one
while
at
the
start
of
the
thing,
if
anyone's
able
to
have
a
look
at
that
and
see
if
it
makes
sense,
that
would
be
great.
A
We
have
another
one
here,
which
is
using
an
environment,
run
book.
A
If
this
makes
sense
to
someone,
anyone
have
a
look
at
it
and
have
some
time
this
week.
That
would
be
great.
A
So
when
I
think
this
is
someone
who's
involved
or
interested
in
the
Google
summer
of
code
hit
this
problem
building
qubit
manifests.
This
was
from
last
week
and
I
haven't
said
an
answer.
Is
it
unable
to
provide
some
insight
into
this.
A
A
A
Yeah,
it's
it's
there.
If
you
want
to
read
about
it
and
this
one
also
highlighting
just
in
case
anyone
is
still
using
Docker
hub,
which
I
don't
think
any
of
us
are
based
on
email
from
Stu.
But
if,
if
that
is
you
please
read
that
and
act
accordingly,.
A
This
was
for
a
kilico
thing,
but
it's
interesting
that
it
seems
as
though
that
they
a
nurse
that
it
worked
with
0.58
that
no
longer
works
for
0.59.
A
That
that
means
something
some
people
you
wish
to
investigate
there.
It
is
there's
also
a
bunch
of
what
are
they
called
improvements
in
the
enhancement
tags
from
last
week,
if
anyone's
interested
in
having
a
look
at
them,
I
don't
think
we
normally
go
through
them
in
this
meeting,
tear
it
there
and
I'm
in
the
interest
of
time,
don't
think
anyone's
added
anything
else
to
the
agenda
or
the
open
floor.
A
Does
anyone
have
anything
that
they
wish
to
raise
or
suggest
or
talk
about
before
we
wrap
up.