►
Description
The OKD Working Group's purpose is to discuss, give guidance to, and enable collaboration on current development efforts for OKD, Kubernetes, and related CNCF projects. The OKD Working Group includes the discussion of shared community goals for OKD 4 and beyond. Additionally, the Working Group produces supporting materials and best practices for end-users and provides guidance and coordination for CNCF projects working within the SIG's scope.
https://okd.io
A
Okay,
welcome
to
the
okd
working
group,
documentation,
subgroup,
meeting
for
may
31st
of
2022,
and
I
can
put
the
agenda
link
in
the
chat
and
please
take
a
look,
real,
quick
and
let
me
know
if
there's
anything
that's
been
missed.
Anything
that
needs
to
be
added,
and
also
please
add
your
name
so
that
folks
know
that
you
were
here
and
then,
if
you
weren't
here
and
there
was
important
information.
B
I'm
going
to
add
one
agenda
item,
someone
internal
to
red
hat
was
looking
at
our
documentation
and
we
refer
to
a
couple
of
things
like
vedim's
internal
working
group
and
suggesting
that
we
should
come
up
with
a
more
formal
name
for
that.
There's
vadim's
and
one
other
one.
So
I'm
just
gonna
bring
that
to
the
party
today.
So
I'll.
Add
that
into
the
agenda.
B
C
And
I
added
one
about
this
single
node
installs
looking
michael's
here
so
hopefully
we
can
cover
that
up.
A
Fantastic
all
right
go
ahead
and
add
those
things
and,
let's
start
out
brian
with
technical
documentation.
We
now
have
it
merged
into
the
main
site.
Is
there
any.
C
Yeah
I
mean
so
I
I
decided
instead
of
working
in
my
private
or
personal
repo.
I
think
the
docs,
the
community
doc
should
be
work
in
progress.
It
should
be
a
working
living
document
so
documentation,
so
I
actually
did
move
it
into
there.
C
There's
still
a
lot
of
information
needed
there
so
and,
as
bruce
said
just
before
we
started
recording,
we
were
having
a
discussion.
A
lot
of
the
repos
are
really
quite
difficult
for
community
members
and
I'm.
I
would
like
to
bring
it
up
on
next
week's
meeting
in
terms
of
do.
C
We
have
an
official
list
of
substitution
images,
because
there
are
various
language
images
and
there
are
various
sort
of
building
images,
and
so
the
one
I'm
looking
at
is
the
console
and
that's
got
six
docker
files
and
they
all
refer
to
different
images,
so
just
trying
to
work
out
what
each
of
them
do
and
say
how
would
I
do
this
outside
of
the
pro
system?
C
And
it's
quite
difficult
to
know
and
as
bruce
said
it's,
how
do
I
know
that
I'm
actually
doing
something,
that's
an
equivalent
of
and
producing
some
it's
an
equivalent
of
the
official
build
image,
because
I
think,
if
you're
going
to
test
something
and
raise
a
burger,
do
a
pull
request.
C
We
do
want
it
to
be
an
equivalent
image
that
we're
working
against.
So
I've
been
going
sort
of
round
around
the
houses
looking
at
that
at
the
minute,
but
I
think
I
am
going
to
need
one
of
the
red
hatters
to
chime
in
on
that
and
actually
explain
a
is.
The
source
of
the
internal
images
available.
Is
the
docker
file
that
they
were
built
from
available,
if
not
the
actual
binary?
C
If
not,
what
are
the
equivalent
community
versions
of
those
files
that
we
should
be
working
with,
and
then
I'm
hoping
there's
some
way
we
can
actually
get
that
into
the
readme
of
the
project.
So
a
community
member
will
be
able
to
pick
pick
each
project
up
and
the
readme
should
have
a
community
section.
Ideally
her.
I
don't
know
whether
that's
going
to
fly
within
the
red
hat
product
teams,
but
ideally
it
would
be
nice
to
have
a
community
build
section
on
every
repo
read
me.
C
A
One
of
the
things
that
came
up
is
you
know
mike
has
mentioned
this
a
couple
times
is
that
his
group
and
a
couple
other
groups
are
doing
internal
and
external
docker
files,
and
that
that
would
be
something
that,
if
everyone
were
doing
that,
it
would
be
easy
to
sort
of
suss
out
what's
happening
as
long
as
you
knew
where
the
documentation
for
the
particular
project
was
right
and
where
to
file
bugs
for
the
particular
project.
A
So
I
would
say
pick
three
things
like
console
is
one
and
then
pick
two
others
and
then
through
that
we
can
sort
of
flesh
out
some
some
some
process
to
documenting
these
things.
Okay,
that
sound
reasonable
yeah.
D
A
slightly
bigger
ask,
which
is
that
I
think,
a
lot
of
these
things
predated
the
ubi
images
that
red
hat
has
made
and
it's
been
promoting
and
if
the
internal
images
could
be
based
on
that,
then
there
would
be
no
reason
why
the
base
image
couldn't
be
public
like
it
may
be
that
it's
only
historical
rather
than
substantive,.
A
Yeah,
that's
a
good
question.
Let's
actually
ask
that
to
add
that
to
the
list
of
questions,
so
if
you
could
brian
under
technical
documentation,
if
you
could
add
those
bullet
points,
so
add
the
three
things
and
then
add
bruce's
question
and
then
I'll
transfer
that
to
the
agenda
for
the
next
meeting
so
list
your
three
things
when
you
get
a
chance
and
then
for
like
a
second
bullet
point
there
put
bruce's
question:
is:
are
these
ubi
or
can
they
be
ubi
to
circumvent
any
internal
external
stuff.
C
I'd
love
it
if
there's
some
more
help,
if
we
need
to
try
and
encourage
people
to
chip
in
and
cover
all
aspects,
including
the
operators
and
what's
going
on
so
there's
no
reason
why
I
mean,
ideally
from
from
the
documentation,
we
should
be
able
to
get
someone
to
do
a
full
build
of
okd
that
that's
the
plan
for
everything
we
provide
should
be
enough
to
give
a
full
build
of
okd
and
it'd
be
an
equivalent
functionality
of
what
the
official
bill
does.
A
All
right
is
it
possible
to
break
down
what
we
need
into
bullet
points
so
that
we
can
say
hey.
We
need
a
volunteer
for
this
particular
area
of
documentation
and
this
other
particular
area,
so
that,
as
you've
talked
about
before
brian,
making
sure
that
people
know
what
they're
volunteering
for
or
what
we
need
volunteers
for
is
that
something?
Maybe
you
and
I
can
work
on
over
the
next
couple
days-
just
look
it
over
and
sort
of
break
it
down
into
sections.
C
A
Well,
that's
that's
up
to
you.
So
if
I'll
take
a
stab
at
it
and
if
you
you
know
I'll
message,
you
you
know
and
you
can
decide
to
get
involved
or
not.
So
I
I
don't
want
to
take
up
your
vacation
time
if
you're
actually
enjoying
a
true
vacation.
C
D
So
that's
and
if
you
were
trying
to
build
the
whole
thing,
I
guess
you
could
not
clone
it,
but
just
sorry
not
fork
it,
but
just
clone
it.
But
the
way
it's
set
up
it
would
be
a
bit
labor-intensive.
C
That
side
of
it,
but
if
we
can
do
it
once
it
means
that
every
piece
is
accessible
to
the
community,
so
so
that
was
the
goal
whether
we
could
actually
come
up
with
an
argo
tecton
config
that
would
just
do
it
automatically.
That
would
be
really
cool.
B
I'm
gonna
say
in
the
next
working
group,
meaning
the
full
one:
we're
gonna
have
people
from
brian
cook's
group.
That's
also
working
on
a
build
process
with
tectonic
and
the
operate
first
guys,
hopefully
showing
up
and
talking
about
what
it's
going
to
do.
Take
to
do
a
community
hosted
and
managed
build
process,
and
I
put
another
item
in
there
that
I'll
we'll
talk
about
a
little
bit,
there's
a
third
initiative
going
on
inside
of
red
hat.
That
has
some
customer
facing
engineers.
B
So
it's
very
timely,
but
we
can
also
ask
them
what's
missing
right
and
ask
them
to
contribute
updates
to
it
as
they
try
and
use
it.
So
I
think
if
you,
if
you
did
this
little
bit
of
staging
work
with
that
in
mind
for
the
next
meeting
and
have
a
call
to
action
of
as
you
go
and
try
and
do
this
with
your
new
tools-
and
you
know
your
new
power
tools-
take
notes.
What's
missing,
what
was
you
know
what
was
behind
firewalls?
B
What
did
you
have
to
do
the
sign
into
red
hat?
To
get
a
you
know,
you
know
those
kinds
of
things
then
I
think
there's
enough
people
right
now
who
are
focusing
on
this,
that
if
we
enroll
them
to
take
good
notes
and
journals
and
make
edits
as
they
find
them,
this
is.
This
is
the
time.
A
A
Brian,
because
you
weren't
at
the
last
main
meeting
at
the
last
main
meeting,
we
actually
did
have
someone
from
cern
who
they've
actually
done
a
build
of
their
own
and
so
yeah,
so
they've
actually
done
their
own
right.
Now
they
have
one
that's
based
on
four
or
nine,
and
so
that's
who's
gonna
be
one
of
the
people.
Who's
gonna
be
talking
next,
so
we
can
compare
notes
and
then
find
out
how
to
sort
of
standardize
that
and
then
document
those
and
few
tweaks
and
stuff
like
that.
C
B
D
Because,
I'm
pretty
sure
everybody
that's
around
has
a
a
developer
key.
You
know
which,
even
though
it's
expired
60
days
with
ocp
still
works,
I
I
imagine
at
least
it
works
to
down
to
download
the.
D
Crc,
local,
whatever
that
is
yeah.
You
know
yeah,
because
because
I
checked
out
that
one
still
works,
I'm
trying
to
find
the
source
repository
for
that
because
it
doesn't
seem
to
be
the
same
one
that
char
was
using
before,
but
with
the
five
minutes
that
I've
tracked.
Looking
with
that,
I
may
just
not
have
found
it.
D
I
mean
I
I
seem
to
have
somehow
this
bipolar
relation
with
crc,
because
my
level
of
caring
is
very
low,
but
every
now
and
then
I
look
at
it
and
see
whether
or
not
I
can
get
it
to
work.
A
Well,
we'll
see
what
happens
we'll
see
what
happens
with
that
all
right,
so
is
that
it
for
technical
documentation,
okay,
yep
all
right.
Let's
move
on
to
repository,
move
timeline
and
steps,
there's
now
a
discussion
item
for
it
and
basically
we
said
july
1st,
and
so
we
just
need
to
fill
in
the
steps
in
this
discussion
of
what
steps
do
we
have
left
before
we
can
just
move
things
over
to
the
new
repo.
A
So
let's
fill
that
in
async
over
maybe
the
next
between
now
and
the
next
meeting
and
then
go
through
them
at
the
next
meeting.
The
steps
be
sure
that
we
are
have
it
covered
who's
doing
what
with
that,
and
then
we
should
be
on
target
then
to
for
july
1st
to
move
things
over
july,
1st
ish.
C
I
I
guess
the
big
investigation
to
happen
is
what's
the
best
way
to
for
the
main
okd
one,
so
we
don't
lose
any
of
the
discussions
because
I
think
if
you
fork,
then
you
don't
take
the
discussions
with
you,
but
I
think
if
you
transfer
ownership
and
actually
transfer
into
the
new
org,
I
think
everything
will
go
with
it.
So
I
think
unless
anybody
knows
that's
an
investigation.
C
C
Yeah,
that's
my
one
big
unknown.
I
think
I've
thought
about
it
and
I
think
everything
else,
I'm
quite
happy
that
we
all
know-
and
we
can
do
that's
the
one
big
because
we
don't
want
to
lose
all
of
the
discussions
and
the
issues
history
and
all
of
that
on
the
obd
one.
Okay,.
A
Okay,
any
any
more
feedback
on
that
on
the
repo
transition,
all
right.
Let's
definitely
work
async
on
that
and
I'll
remind
folks.
You
know,
maybe
towards
the
end
of
this
week,
to
be
sure
that
we're
filling
in
the
various
steps
there,
let's
now
walk
through
the
survey.
Let's
just
do
this,
get
it
done
and
ship
it
out,
like
maybe
the
end
of
the
week
or
something
we
just
we've
been
sitting
on
this
for
so
long.
A
The
only
feedback
we
got
so
far
was
what
version
are
you
using
and
that
that
needs
to
be
edited
to
to
include-
and
I
will
I
can
add-
do
we
want
to
drop
four
three
and
four
four
and
just
shift
these
down
perhaps
or
do
we.
B
A
A
A
Do
we
want
to
go
all
the
way
down
to
version
four
three
or
I
because
I
don't
even
know
is
43
even
available
still
on
the
on
the
site
on
the
releases,
I
don't
know
yeah.
I.
B
B
Anybody
is
using
that
yeah
yeah,
but
it's
all
beta,
and
can
you
make
this
question
required
so
there's
a
little
required
slider
there
at
the
bottom,
underneath
lower,
lower,
lower
lower.
A
A
C
A
Okay,
because
people
might
have
multiple
versions
yeah,
what
is
the
biggest
challenge
you
face
using
okd
today.
B
No
go
ahead.
The
cr,
the
critical
features
is
a
great
question.
How
many
people
question
is
an
interesting
but
a
hard
one.
To
answer
I
mean,
would
it
be
easier
to
say
how
many
applications
or
clusters
has
do
you
have
deployed
like
a
num
like
something
that's
a
tangible
thing?
They
can
go
and
look
up
this.
The
stack
I
mean.
C
B
Maybe,
rather
than
people
not
that
people
developers
aren't
people,
but
how
many
developers.
A
How
are
you
use
how
about
as
an
open-ended
question?
How
are
you
using
nokiti,
or
do
we
want
to
break
it
into
a
multiple
choice,
checkboxes
of
of
commercial
or
commun?
Like
I
don't
know
what
we
would
come
up
with
for
that
like
what
are
the?
What
are
the
different
uses,
so
personal.
B
A
Let's
add
a
new
question:
where
do
we
want
this
question?
Do
we
want
it
to
be?
I
feel
like
it
jumping
down
it
sort
of
jumps
to
ask
the
biggest
challenge
like
I
feel
that
should
be
further
down
like
and
that
questions
about
usage
should
be
of
like
who's
using
it
now
should
be
further
up.
Does
that
make
sense?
I
agree
with
that.
A
Yep,
so
how
do
we
want
to
change
the
how
many
people
or
do
we
want
to
add
up
above.
A
You
using
okd,
and
this
would
be
check
box-
we're
saying,
develop
development
platform.
C
B
C
B
A
A
C
Are
we
asking
what
red
hut
operators
would
you
want
to
see
in
the
ukd
catalogue?
Is
that
the
question
we're
actually
asking
here
or
is
it
a
more
general
open?
Is
there
a
product
that
there
is
an
operator
for
that?
You
want
an
operator
for.
D
Yeah
as
well,
I
think
that
the
way
the
way
ocp
is
promoted,
there
are
some
things
which
are,
in
fact,
operators
but
are
promoted
as
part
of
the
package.
You
know
so
like
serverless
pipelines,.
B
A
B
A
C
A
A
I
think
just
operators,
I
think
just
I
think
personally,
I
think
just
in
general,
because
some
folks
may
not
really
be
thinking
of
oh,
that's
an
ocp
operator
or
that's
a
versus.
Oh,
I
need
this
community
operator
or
whatever
some
people
might
not
understand
the
operator
ecosystem
and
I'd
actually
be
willing
to
bet
that
a
significant
number
or
using
okd
just
based
on
chat
and
and
emails
and
stuff
that
we
see,
probably
don't,
have
a
sense
of
the
ecosystem.
We
we
have
internal
knowledge.
A
B
C
B
In
production,
but
the
one
thing
that
I
r
is
critical
for
me
to
get
out
is
some
semblance
of
a
count
of
people
who
are,
you
know,
willing
to
say,
stand
up
and
say
they
are
using
okd
in
production
because
that's
you
know,
as
we
fight
for
engineering
resources,
that's
kind
of
one
of
the
that's
the
thing
I
I
face.
Every
every
conversation.
A
A
So,
which
features
do
you
need
that
are
not
available
in
opd
today,
right
that
sound
right,
folks,
yep
all
right
so
which
features
all
right
so
pulling
that
one
up,
and
then
we
ask
about
which
operators
are
using
now,
which
operators
would
you
like
to
see
in
okay,
whoops,
the
in
okd,
which
are
not
currently
available.
C
D
A
B
It
open,
you
think,
I
think
we
could
leave
it
open
and
then
we
can
follow
back
up
and
or
maybe
that
that
might
be
the
biggest
challenge
and
they
may
go
back
up
and
say
the
biggest
challenge
is
finding
documentation.
A
Should
we
then
ask
for
a
question
below
that?
That's
like,
if
you
answered
such
and
such
above,
can
you
provide
more
details
or
something
like
that,
or
is
that
getting.
B
Too
tedious,
I
think
it's
getting
too
long,
because
what
I
would
say
is
there's
too
many
questions
here.
We
want
people
to
actually
do
that
and
then
they
can
have
additional
content.
I
love
the
welcoming
one.
I
think
that's
a
great
question
and
I
would
keep
it
just
like
that.
I
think
it's
great.
Do
we.
A
Want
to
ask
about
well
code,
ready
containers,
slash
open
shift,
local
or
no.
B
A
B
And
I
would
even
throw
in
micro
shift
yeah.
I
know
that
sounds
a
little
naughty
but
like
to
see
see
where
people
are
playing
here.
B
Just
okay
in
any
of
the
yeah
configurations
code,
ready,
containers
no
and
check
boxes
again.
B
What
else
I
would
I
would
like
to
add
in
micro
shift
here
I
know
it.
People
are
confused
micro
shift
and
would
we
say
home
labs
here
or
is
that.
D
B
At
all,
not
at
all
go
ahead.
Do
it
just
I'm
I'm
happy
to
do
that.
C
C
A
C
B
A
B
A
All
good
so
aws
azure
alibaba
bare
metal,
oh
gcp,
right
gcp,.
C
We've
got
vmc,
I'm
guessing
that's
overt.
Is
it
hang
on?
B
B
A
Want
to
ask,
would
you
like
to
provide
contact
information.
A
C
You're
you're
in
the
world
of
all
sorts
of
privacy
laws.
If
you
ask
that,
because.
C
A
So,
let's,
let's
go
through
the
description
up
here:
okay,
the
community
distribution
of
kubernetes
that
powers
red
hats,
open
shift.
We
would
appreciate
it
if
you
could
take
a
few
minutes
to
answer
some
questions
to
help
us
improve
the
okd
experience,
and
can
we
say
something
about
the
community
like
improve
the
okd
experience
and
expand
the
community
or
something.
B
I
I
would
almost
say
rather
than
expand
the
community,
but
something
along
the
side
of
our
road
map
and
and
help
us
prioritize.
Our
community
roadmap.
B
A
Oh,
this
needs
to
change
right
here.
Where
do
we
want
to
direct
people.
C
B
A
B
Or
feedback,
please
feedback,
please
join
us
or
please
feel
free
to
join
us
to
join
the
club,
feel
free
to
join
the
conversations
right
with
an
s
on
it.
On
yeah
there
you
go.
A
A
A
How
are
you
using
okd
home
lab
development,
sandbox
platform
production?
Other?
Oh,
did
we
want
other
to
capture
for
the
versions?
If
someone
happens
to
be
okay,
there
we
go
all
right
and
which
features
do
you
need
that
are
not
available
today?
Oh,
this
should
actually
be
a
paragraph.
A
A
Oh,
how
about
which
yeah,
but
you
could
phrase
it
as
please,
please
explain
below
or
something
like
that.
C
C
A
B
I
think
you
can
kill
the
first
one
and
the
reason
is
that
we
could
do
a
follow-on
one
that
was
more
operator-centric
once
we
got
this
feedback.
That's
a
good
point,
that's
a
good
one,
and
hopefully
it.
A
A
Should
we
be
moving
the
platforms
and
configurations
further
up,
then.
B
Nah,
I
think
I
you
know,
I
think
they're
good,
where
they
are
it's
a
good
mix
of
paragraphs
of
information
and
yeah.
A
A
A
C
C
B
Yeah,
I
almost
think
that
if
you
did
one
right
after
the
documentation,
helpful
one
you'd
get
more
of
a
documentation,
specific
thing,
and
you
know
that
would
be
more
helpful
to
michael
you
know.
Is
there
any
feedback
you
can
give
us
on
the
documentation.
A
B
A
Right,
fantastic
and
we've
got
10
minutes,
so
we
got
to
sort
of
burn
through
this
here.
Technical
repository
survey,
faq
suggestions,
so
I'm
going
to
start
putting
this
as
a
standing
item.
If
you
have
faq
suggestions,
please
add
them
here:
one
that
we've
gotten
a
lot
lately
is
installing,
on
other
os's
and
vadim,
provided
a
good
response
that
I
think,
could
form
an
faq
so
I'll
shape
that
into
an
faq
and
then
I'm
still
starting
with
language
on
the
release.
Cadences
faq.
A
So
if
you
have
any
suggestions,
feel
free
now
or
at
a
future
meeting
to
add
things
under
there:
okay,
okay,
sno
documentation
removed
from
okd
docs
discussed
here.
Brian.
Did
you
add
that
who
had
it
then.
C
Yeah,
so
I
I
noticed
that
there
is
a
discussion
item
which
is
discussed
here
where
it
looks
like
the
process
of
doing
a
single
node
install
is
changing.
I
think
it's
something
to
do
with
how
we
do
the
we're
not
going
to
have
the
boot
bootstrap
node,
so
it
actually
replaces,
and
ocp
now
has
to
use
the
assistant
installer
to
do
sno,
which
obviously
isn't
supported,
and
I'm
just
making
sure
that
within
the
discussion,
because
we've
actually
closed
the
discussion
item
or
michael
closed,
it
saying
that
he
actually
removed
the
invalid
instructions.
A
C
B
B
C
A
B
I
think
we
need
to
make
the
ask
for
a
volunteer
to
write
this
at
next
week's
meeting
with
meeting.
If
you
could
so.
C
B
Yeah
good
all
right,
the
the
next
two
things:
the
depersonalizing,
the
home
lab
documentations.
I
don't
have
an
opinion
one
way
or
the
other.
However,
a
few
people
inside
of
red
hat
noticed
the
other
day
that
we
were.
We
had
personalized
the
two
home
lab
things
with
vadim
and
sri's
name
on
it
and
suggested
that
that
might
not
be
best
practice
or
informative
enough
for
someone
who
wasn't
on
the
in
crowd.
B
So
I
just
wanted
to
bring
that
to
this
group's
attention
and
think
about
renaming
at
least
the
item
and
still
giving
vadim
and
sri
credit
in
the
documentation.
B
But
I
didn't
have
a
suggestion
as
to
what
the
new
name
should
be.
C
I
I
actually
again,
we've
probably
got
time
to
go
into
this.
I
actually
want
to
actually
have
a
conversation
around
what
the
guy
should
be,
because
they're
not
quite
enough
information
to
let
somebody
repeat
what
they're
doing
so
other
guides
just
to
give
an
indication
of
the
sort
of
hardware
people
are
doing,
in
which
case
we
can
make
them
much
more
concise
and
standard,
or
do
we
want
to
go
and
put
what
they're
doing
and
as
an
example,
if
I
just
put
into
the
chat,
I
know
this
isn't
going
to
help
for
recordings.
C
As
I'm
setting
up
mine,
I'm
actually
documenting
what
I'm
doing
with
my
own
home
lab,
and
the
idea
is
that
hey?
If
I
need
to
come
back
to
this,
this
is
going
to
help
me
but
b.
If
anybody
else
wants
to
do
a
similar
thing,
these
instructions
should
be
good
enough.
C
B
C
Yeah,
I
think
that's
what
I
think
of
as
a
guide,
but
so
I
think
we
just
need
clarification
of
what
we
want
and
I
know
daniel
started
leading
this
project,
but
it
seemed
to
have
stalled
again
so,
but
but
I
think
it's
worth
having
a
conversation
of
what
should
the
guides
be?
B
C
B
But
yeah,
but
I
like,
I
really
like
the
way
you've
done-
yours,
brian
and
maybe
making
vedims
and
sris
a
little
more
concise,
not
this
week.
But
it's
just
a
suggestion
that
you
know
I.
It
was
too
much
an
in
joke,
not
an
in
joke
but
in
you
had
to
know
vadim
or
shree
and
naming
people
specifically
was
was
tough
yeah.
B
I
just
wanna
just
timing.
I
really
wanna
make
sure
I
hit
on
this
last
point
agenda
item
before
so
maybe
we
could
think
about
this
home
lab
stuff,
but
I
I
just
I
just
wanna
make
sure
I
mentioned
to
you
guys
this
class
goes.
I
don't
even
know
how
you
pronounce
this
initiative,
because
I
want
to
make
sure
it
gets
communicated
out
to
you
guys
before
and
this
week
and
at
next
week's
working
group
meeting.
B
If
you
don't
mind,
because
we
only
have
four
minutes
left
and
I'm
sure
you'll
have
questions
what
I'm
talking
about
here,
so
internal
to
red
hat,
as
you,
you
know,
might
suspect,
there's
lots
of
things
going
lots
of
initiatives
going
on
and
one
of
them
is
taking
centos
stream
and
creating
a
closer
tyrell
for
os
centos
stream,
core
os
and
making
it
available
and
timothy
reviewer
who's.
A
regular
working
on
the
fedora
coreos
stuff
is
also
working
on
that
and
he
hasn't
talked
about
it
out
loud.
B
We
finally
got
him
to
like
and
get
his
powers
that
be
to
let
us
talk
about
it
out
loud
and
in
the
public,
and
so
I
wanted
to
give
people
a
heads
up
on
that
on
this
group
call
and
then
we're
going
to
talk
about
timothy
may
talk
about
it
a
little
bit
next
week,
but
it
is
an
opportunity
for
us
and
there
are
some
folks
working
on
an
experimental
sprint
inside
of
building
a
version
of
okd
on
this
as
it
comes
to
fruition.
B
So
I
wanted
to
say
that
out
loud
here,
so
everybody
could
think
about
what
that
that
means
and
the
opportunity
that
it
presents
for
the
community
to
have
something
in
addition
to
fedora
core
os
okd
that
might
be
slightly
more
stable,
with
each
release
and
built
and
maintained
again
in
the
same
process
pipeline
that
we
were
doing
fedora
core
os
and
that
that
is
a
live
initiative.
B
Now
that
we
can
talk
about
publicly
and
it
is
resourced,
with
three
customer
facing
engineers
right
now
under
the
same
group
that
christian
glombeck
is
in
inside.
So
that
is,
I
think,
good
news
for
us
and
what
I
want
to
start
trying
to
do
is
see
if
I
can
find
folks
within
the
okd
community
who
would
test
and
deploy
that
thing
once
the
sprint
is
done,
which
I
think
probably
gets
shot
for
saying
anything
out
loud
but
mid-july-ish.
B
We
should
have
this
first
release
of
okd
on
scuzz
and
I
wanted
to
make
sure
you
all
were
aware
of
that.
Especially
jamie.
So
didn't
come
as
a
huge
it
might.
B
It
may
get
delayed
a
little
bit
because
everything's
resource
constrained
and
there's
queens,
jubilees
and
other
vacations
coming,
but
I'm
trying
to
time
a
little
bit
of
more
announcements
of
it
around
the
july
6
london
openshift
commons,
gathering
too,
and
see
if
people
like
cern
or
john
fortin
or
other
people
would
have
any
interest
in
using
this
or
at
least
testing
it.
People
who
have
been
complaining
vociferously
about
being
on
the
bleeding
edge.
B
B
And
you
can
ask
timothy
questions
about
it
next
week.
Let
him
say
the
words
first,
because
we'll
see
how
comfortable
he's
gotten
I've
gotten
steve
milner
who's
his
boss
to
tell
him
that
it's
okay
to
talk
about
it
out
loud.
I
don't
know
how
long
you
know
in
duration.
They've
been
working
on
it,
not
that
long
so,
but
it
is
definitely
a
viable
thing.
B
That's
going
to
happen
and
I
was
loathe
to
say
anything
about
it
earlier
for,
like
it
might
just
drop
off
the
radar
as
some
things
do,
but
it's
it's
coming
and
it's
it
should
be
interesting
and
of
interest
to
this
community.
I
think.
A
Excellent
well,
let's
add
that
to
the
agenda,
there's
also
something
that
something
else
that
christian
added
to
next
week's
agenda.
So
it
sounds
like
next
week's
agenda
might
be
packed
I'll
reach
out
to
the
various
people
and
see
if
we
can
get
a
sense
of
timing
so
that
everyone
can
and
get
their
their
time
in
and
maybe
get
the
agenda
done
ahead
of
time
in
a
in
a
way.
That's
that
allows
everyone
a
chance.
B
Yeah,
so
I
I
think
that's
that's
the
thing
that
my
goal
next
week
is
is
to
get
cern
to
do
a
little
deeper
dive.
So
we
understand
that
thing
to
have,
hopefully
timothy
say
the
word
centos
dream
core
os
out
loud
publicly
to
the
working
group
and
to
get
a
sense.
I
almost
was
to
the
point
where
I
wanted
to
ask
that
question
in
the
survey,
but
I'm
not
ready
to
do.
B
I
don't
think
we're
ready
to
do
that
yet
until
we
have
a
viable
experimental
release,
first,
release
of
it,
because
I
don't
want
to
get
people's
hopes
up
too
high
that
it's
coming
too
soon,
but.
D
Sorry
go
ahead.
Yeah
now
I
noticed
that
the
centos
stream
people
have
now
changed
the
versions,
so
they're
centos,
eight
and
centos
9
and
no
upgrade
path
between
them.
So
does
this
one
also
have
a
version,
then
I.
A
Let's
ask
technical
questions
when
the
technical
people
are
here
that
are
actually
working
on
it.
Yeah,
oh.
A
Week,
all
right
diane,
you
have
three
items,
just
a
reminder:
research,
the
transition
to
zoom
for
meetings
to
see
if
red
hat
wants
to
help
us
with
that
change,
twitter
email
address
right
and
research,
mx
record
change
to
the
okda.io
domain,
so
that
we
might
be
able
to
support
our
own
email.
Those
are
all.
C
Just
just
the
one
for
me
that
was
done,
the
link
checking
is
now
a
warning
only
so.
A
Oh,
thank
you.
Thank
you.
So
much,
oh
and
one
more
for
me,
which
is
that
meeting
notes
are
now
getting
posted.
There's
a
meeting
minutes
are
now
getting
done.
A
There's
a
2022
page
that
I'm
actually
going
to
start
adding
them
to
and
then
we'll
do
them
by
year
and
so
it'll
be
the
index
then
broken
down
by
year
and
then
within
the
year
brian,
do
you
know
if
it's
possible
to
auto
generate
pages
like
if,
if
the
dock
is
just
thrown,
if
a
dock
is
just
thrown
in
there
to
auto,
generate
the
page
and
add
to
an
index,
you
know
what
I
mean
like
if
there's
nested.
C
B
A
C
A
Meeting
folks
talk
to
you
soon,
all.