►
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
Okd
working
group
documentation,
subgroup
meeting
for
april
5th
2022
and
looks
like
we
have
a
new
face
here
with
us
today.
Larry.
Do
you
want
to
introduce
yourself
and
say
hi
to
the
other
members.
B
Oh
I've
been
here
before
it's
just
not
maybe
not
in
this
meeting.
I've
been
around
working
with
the
okd
project,
mostly
for
the
311
stuff
and
following
along
for
everybody
else,
as
they
forged
ahead
into
the
force
stuff
and
trying
to
figure
out
my
path
into
that.
A
Excellent
and
we
had
michael
b
just
show
up
as
well,
so
welcome
michael.
A
Do
you
want
to
get
started
brian
with
community
repo
stuff
start
us
with
that.
D
Yeah,
have
you
posted
the
hack
md?
I
think
most
people
have
found
it.
So
I've
put
a
link
in
the
in
the
agenda.
C
D
Looking
to
remove
the
community
repo
and
so
the
link's
there,
mainly
it
contained
five
or
six
documents,
and
that
was
all
so.
We
wanted
to
roll
that
into
the
okay
dio
website,
so
I've
actually
moved
most
of
the
stuff
and
we've
got
the
charter
into
the
the
ukd
site.
Now
and
I'll
put
the
link
where
it
is,
so
it
lives
under
the
working
group
section
because
it
really
looks
at
how
the
working
groups
work.
However,
there
are
three
documents
left
and
I'm
not
quite
sure
what
we
want
to
do
with
them.
D
One
is
the
owners,
and
that
really
is
just
the
main.
It
looks
like
it's
just
for
the
main
working
group,
where
it
lists
two
of
the
owners
and
then
who
can
approve,
which
I'm
guessing
is
into
the
okd
repo
and
then
the
other
one
is
a
road
map,
and
I
don't.
This
probably
needs
to
be
taken
to
the
main
meeting,
but
I
just
was
worth
discussing
here,
so
we
can
actually
take
a
proposal
to
the
main
meeting.
D
It's
you,
you
get
more
done
that
way,
rather
than
trying
to
have
a
discussion
with
the
bigger
group,
so
my
thought
is
for
each
working
group
do
we
want
to.
Actually,
I
think
we
need
to
actually
have
the
sort
of
offices
of
the
working
group.
So
who
is
the
chair?
Who
are
the
the
primary
drivers
or
the
primary
positions
within
the
work
group?
D
We
seem
to
be
quite
sort
of
dynamic
in
terms
of
membership,
so
I
don't
know
whether
we
want
to
actually
have
a
members
list
for
each
working
group
or
really
just
my.
My
suggestion
is:
let's
just
leave
it
to
the
those
that
have
a
position
or
some
official
duty
within
the
working
group,
and
then
the
membership
can
be
a
bit
dynamic
if
we
grow
and
it
becomes
where
we
need
more
steering
committee
type
membership,
then
I
think
we
we
can
move
it
there.
D
But
for
now
I
just
say
the
chair:
if
there's
anyone
that
actually
has
any
specific
authority
like
who
can
who
can
do
a
release
or
who
can
make
a
commit
to
the
okd
repo
they
should
be
listed,
but
the
membership
is
not
something
we
track
actively
and
roadmap.
D
I
don't
know
what
we
want
to
do
about
roadmap
and,
I
think,
we're
largely
in
the
hands
of
the
red
hatters
in
terms
of
where
the
ocp
product
is
going
so,
whether
we
we
actually
have
a
roadmap
or
whether
we
want
to
do
a
roadmap
of
like
community
activities,
where
we
want
to
do
things
like
the
operator
catalog.
We
want
to
do
projects
like
the
technical
documentation.
We
want
to
do
projects
like
the
testing,
whether
we
actually
have
a
roadmap
for
community
activities.
A
That's
a
lot,
that's
a
mouthful
right
there.
So,
let's,
let's
start
out
with
with
the
the
first
document
in
that
so
well.
Well,
the
very
first
of
that
is
the
charter,
which
has
been
updated
like
yeah.
The
last
change
was
in
june
of
last
year
for
the
charter.
Yes,.
C
A
Yeah
exactly,
but
that
may
be
something
that
we
want
to
revisit,
because
I
I
don't,
I
feel
like
there's
a
couple
things
that
did
eventually
need
to
get
changed
with
that
and
ultimately
we
will
want
to
mention
in
the
in
the
main
charter,
like
we
have
a
thing
for
subgroups,
but
we
don't
actually
like
list
subgroup
chairs
or
anything
like
that,
because
it
says
each
sub
working
group
must
have
a
chair
working
as
an
active
sponsor.
A
D
I
was
gonna
say
within
a
corporation
when
you
have
a
sponsor:
it's
usually
an
executive
sponsor,
so
within
ibm
when
we
say
you
need
a
sponsor
for
a
community,
it
does
have
to
be
an
ibm
executive
sponsor.
I
don't
know
whether
red
hat
has
the
same
thing.
So
that's
where
I
read
it.
We
needed
red
hat
executive,
sponsor
bridge
working
group,
so.
C
The
inclusion
group,
the
diversity
inclusion
groups,
have
executive
sponsors.
A
A
All
right
well,
let's
find
out,
and
then,
if
we
have
to
get
one
we'd
have
to
go
through
the
process
of
deciding
who
that
would
be
so
for
the
members.
I
here's
one
thing
that
came
that
diane
and
I
were
talking
about,
though,
when
we
were
sort
of
chatting
about
the
membership.
The
one
hitch
with
just
letting
it
be
sort
of
whoever
shows
up
is
that
if
there
is
a
vote
on
something
significant
and
we've
generally
there's,
this
hasn't
happened
because
you
know
we're
just
growing
as
a
community
right
now.
A
If
there
were
a
vote
on
something,
that's
significant
and
someone
wanted
to
sort
of
stack
the
deck
by
having
a
bunch
of
people
show
up
and
vote
that
could
be
problematic.
That's
the
only
I
think,
downside
to
to
anyone
being
able
to
vote
and
membership
just
sort
of
being.
D
B
D
Percentage
of
the
active
membership
has
to
vote,
and
then
you
get
into
all
sorts
of
areas
that
get
overly
complex.
I
don't
think
your
community
is
at
that
stage
yet,
and
I
would
say
at
the
end
of
the
day
you
and
I
don't
have
the
casting
vote.
So
if
you
think
things
are
getting
hijacked,
you
are
the
ultimate
authority.
As
far
as
this
community
is
concerned,.
A
Yeah-
and
that
is
kind
of
what
we
put
for
you
know
for
our
statement.
You
know
for
the
the
the.
A
D
So
I
mean
I,
I
I
actually
think
we
we
removed
the
the
members
list
on
the
owners
list
now,
whether
we
actually
put
working
groups
and
the
officers
within
the
charter
or
within
the
description
of
the
working
group.
I
don't
mind
because
we've
got
a
section
on
the
website
for
each
working
group,
whether
the
the
officers
of
that
working
group
get
get
listed
there
or
whether
we
actually
put
it
into
the
charter.
I
don't
mind,
but
the
charter
should
be
should
reflect
whatever
we
decide
to
do.
A
Yeah
for
sure
right
and
then
we
have
the
readme,
of
course,
which.
D
A
We
don't
have
a
say
on
sort
of
the
foundational
elements,
but
we
do
have
a
say
on
some
of
the
testing
or
some
of
the
so,
for
example,
one
of
the
things
I'm
going
to
be
talking
about
later
in
the
meeting
that
vadim
and
I
talked
about
when
we
met
last
week
is,
I
said:
what
do
you?
What
do
you?
What
do?
A
We
really
need
right,
he's
like
bare
metal,
testing
and
and
testing
in
vsphere
and
have
it
be
automated
like
weekly
to
match
with
you
know,
what's
the
releases
basically
and
that
to
me
is
a
road
mappy
type
thing
to
say:
okay
by
the
end
of
quarter,
two
or
whatever,
we
would
like
to
have
a
functioning,
automated
vsphere
testing,
either
through
donations
or
someone
offering
their
hardware
or
whatever
or
at
least
providing
reports
they
could
send
out
to
the
group
or
something
it
seems
to
me
that
that
is
kind
of
road
mapping.
A
You
know
at
the
base
level
there's
this
will
follow
red
hat's
road
map
for
whatever
and
then
the
additional
things,
because,
like
vadim,
also
brought
up
c
group's
v2,
was
something
that
got
tested
first
in
okd
before
it
ended
up
in
any
place
else.
So
our
road
map
could
actually
include
a
fair
amount
of
stuff.
That's
that's
unique.
To
okd,
I
mean.
D
We
we
could
almost
do
something
like
red
hat
does,
with
their
their
releases
so
sort
of
after
every
major
release.
They
do
and
actually
think
it's
on
the
14th
of
this
month.
They
do
a
what's
next
right
and
we
we
could.
We
could
do
a
after
every
major
release
of
okay.
We
could
do
a
what's
next
to
update
the
roadmap.
C
One
of
the
things
you
have
to
remember
is
that
a
lot
of
the
stuff
that
we're
testing
first
is
more
because
of
fedora
core
os,
rather
than
anything
core
with
openshift
itself,
so
we're
we're
sort
of
the
guinea
pigs
for
that
where,
when
red
hat
decides
to
go
to
you
know
rh,
you
know
red
hat,
9
or
red
hat
10
whatever
they
do.
You
know
pull
in
whatever
version
of
fedora
they're
going
to
use,
so
you
know
we're
the
we're
the
bleeding
edge
for
that
to
our
detriment.
C
Sometimes,
but
I
mean
really,
we
don't
do
anything
else
in
you
know
of
the
major
parts
of
openshift.
You
know
it's
the
the
city
on
efcos.
You
know
that
we're
that
we're
the
testers
for.
A
Yeah,
which
is
is
fine
and
that
may
change,
though,
with
the
community
operators
catalog
or
with
I
sorry,
with
the
okd
operators
catalog,
we
may
be
testing
operators
that
aren't
you
know
available
in
red,
hat's
catalog,
yet
you
know
or
in
the
community
catalog
it
could
be.
I
mean
I'm
just
throwing
things
out
that
like
yeah,
they
may
not
be
directly
open
shift
related
or
they
might
be,
but
tangential
or
something,
but
I
think
there's
an
opportunity
for
us
to
have
a
roadmap.
D
But
I
also
think
I
mean
the
conversation
that
we
had.
John
was
it
three
weeks
ago
when
we
were
looking
at,
how
do
we
bring
in
new
features
to
to
and
and
we
have
the
conversation,
should
it
be
at
a
major
release
update
or
should
we
do
it
intro
release?
I
think
that
sort
of
thing
could
go
in
the
roadmap,
so
we
can
decide
when
we
introduce
a
new
feature
like
like
c
groups,
version
two
and
it
could
be
put
on
a
road
map.
D
So
it's
we've
got
six
months,
visibility
of
or
four
month,
visibility
that
we're
working
on
that
and
it's
going
to
come
in
the
next
release.
So
it's
not
a
surprise.
It's
like
a
yeah.
We
did
this
update.
Oh
you
put
it
on.
Didn't
work,
oh
yeah.
By
the
way
we
did
this
whole
bunch
of
stuff
in
it,
and
maybe
that's
what
hit
you
so
maybe
yeah.
I
I
think
again.
I
think
we
should.
D
We
need
to
take
this
to
the
main
group,
but
I
think
the
proposal
is
so
actually
let
me
write
this
in
here,
so
the
proposal
is
that
we
are
going
to
I've
lost
it.
So
I'm
just
updating
if
you're
in
hackmd.
D
So
the
proposal
is
that
we're
gonna
drop
membership,
each
working
group
lists
offices,
I'm
calling
them
offices
whether
we
want
to
call
a
different
name.
I
don't
mind
and
we'll
do
a
major.
D
D
C
A
Yes,
so
yeah
interest,
I
don't
know
brian,
did
you
incorporate,
I
didn't
look,
but
did
you
incorporate
anything
off
of
the
google
doc
into
your
stuff?
Yet
or
do
you
want
me
to
or
how
did
you
want
to
move
forward
with
that
then
stuff
from
vadim.
A
Okay,
so
yeah,
so
for
folks
that
for
a
little
bit
of
context
in
this,
I
met
with
vadim
friday
for
about
an
hour,
and
we
had
a
conversation
about
sort
of,
as
I
said,
future
needs
and
the
future
of
okay
in
general,
vadim
anticipates
being
out
for
at
least
a
little
while
longer
and
so.
A
You
know,
basically,
if
we
find
stuff,
we
can
put
in
a
merge
request
and
either
him
or
christian
or
there's
a
couple
other
people
that
are
listed
there.
That
can
approve
those
merges
in
terms
of
where
what
we're
going
to
be
when
we
grow
up,
and
I'm
just
paraphrasing
for
vadim,
because
he's
not
going
to
be
coming
to
any
meetings.
A
And
then
his
thought
is
that
it
would
be
too
much
to
take
on
to
do
all
of
the
infrastructure
and
stuff
and
sort
of
go
outward
from
red
hat,
because
there's
a
lot
of
like
interaction
that
happens
between
him
and
christian
and
the
other
red
hat
teams
in
terms
of
features,
issues
and
whatever.
And
then
we
would
sort
of
be
on
the
outside
of
that.
A
A
So
that
was
that
was
his
perspective,
because
I
know
the
last
few
meetings
there's
been
discussion
about
well.
Okay,
should
we
just
have
okd
sort
of
split
off
and
and
sort
of
be
its
own
thing
and
vadim's
perspective
was
that
we
shouldn't
do
that,
and
I
was
actually
kind
of
convinced
after
talking
to
him
that
I
I
would
agree
with
his
perspective,
but
I'm
curious
what
other
folks
would
think
about
that
case
of
the
argument
you
made.
C
I
I
agree
with
them
only
because
we
there
is
so
much
that
happens
behind
the
scenes
and
we
don't
have.
We
don't
have
the
manpower
infrastructure
to
take
that
on
ourselves.
You
know
we're
not.
You
know
we're,
not
the
kubernetes
group,
you
know
and
stuff
like
that.
You
know
honestly
there's
what
six
or
seven
people
you
know
that
are
actively
engaged.
C
C
You
know,
maybe
we
should
have
access
to
be
able
to
do
things
like
you
know,
maybe
not
do
the
commits
themselves,
but
have
a
certain
level
of
access
to
be
able
to
do
some
of
our
own
testing
and
experimentation.
You
know
without
having
to
bother
vadim
or
christian
and
stuff
like
that.
You'll
be
able
to
have
almost
developer
access,
but
not
administrative
access.
C
D
D
I
think
that
that
opens
up
some
interesting
possibilities,
but
even
if
that
doesn't
happen,
one
of
the
challenges
I
I
have
is
as
a
community,
we
don't
actually
know
what's
going
on
inside
red
hat
now,
I
know
a
lot
of
okd
is
linked
to
ocp
strategy
and
as
a
as
a
commercial
company,
red
hat
have
a
strategy
of
how
they're
going
to
drive
that
project
forward
driven
by
customer
needs
and
commercial
needs.
So
I
get
that,
but
I
mean
I
I
I'll
come
on
to
this.
D
D
D
D
C
So
so
the
funny
thing
there
is
is
that
that
was
actually
supposed
to
have
been
changed,
because
there
are
community
versions
of
those
red
hat,
build
images,
but
they've
never
done.
It
ran
the
same
issue.
When
I
was
doing
mco
testing,
I
updated
the
image
the
docker
containers
myself
to
put
in
the
proper
image,
and
then
I
was
able
to
you
know
to
continue
forward,
but
yeah
it's
been
mentioned
multiple
times
and
they
have
not
made
any
changes
to
it.
So
yeah.
D
C
D
D
So
if
I
wanted
to
set
up
a
a
mini
pro,
obviously
I'm
not
going
to
be
testing
against
all
the
architectures
and
platforms
that
the
red
hat
system
did,
but
if
I
wanted
to
create
a
cut
down
version
to
run
the
basic
ci
steps,
that's
in
the
release,
repo-
I
don't
know-
I
don't
have
enough
information
even
to
do
that.
I
also
found
out
that
several
of
the
repos
have
out-of-date
information
in
the
readme.
D
So
if
you
look
at
the
readme
to
say
how
to
build
it,
you
will
fail
to
compile,
because
information
is
out
of
date.
Now
yeah
we
can
start
putting
change,
pull
requests.
You
know
raising
issues
to
say
well,
this
says
use
golang15,
but
the
actual
repo
uses
features
that
can't
be
used
before
go
along
17.,
yeah,
right
or
16
or
whatever
yeah.
A
A
B
A
Make
sure
that
we
that
we
just
determine
a
plan
forward
for
this,
so
let's,
let's,
let's
see
where
we
are
here
in
the
agenda:
let's
do.
A
Let's
go
back
to
the
removing
the
community
repo
part,
so
it
sounds
like
we
have
a
plan
with
what
to
do
with
the
stuff.
That's
there.
We
will
rework
the
road
map
to
incorporate
stuff
that
we
are
going
to
do
specific
to
okd,
and
that
will
be
an
interesting
discussion
because
we'll
want
to
revisit
that
road
map
on
a
regular
basis.
D
D
So
again,
if
you
look
at
hack
md,
the
link
is
there
go,
have
a
look
have
a
play.
D
If
you
see
any
issues,
let
me
know
and
I'll
bring
them
up
with
brandon
and
we
can
get
them
fixed,
but
that
is
what
we're
likely
to
push
into
the
new
onto
the
website
as
the
styling
similar
colors
similar
theme,
but
you
notice
that
the
background's
got
lighter
so
he's
made
the
the
main
page
lighter
and
the
side
menu
is
a
little
bit
darker,
actually
flip
that
you
flip
those
those
colors
around
and
things
like
that.
D
A
It's
definitely
more
legible.
A
Does
anyone
have
any
qualms
about
brian
moving
forward
with
those
and
approving
the
pull
request?
That's
going
to
be
made.
A
So
so
by
the
next
meeting,
you
think
by
the
next
docs
meeting
brian
that'll,
be
the
emergency.
D
Oh,
I
spoke
to
him
yesterday.
He
said
he
had
a
couple
of
things
to
check
out
and
then
he'll
do
a
pull
request.
So
I'm
hoping
that's
going
to
be
within
the
next
week
or
certainly
within
the
next
fortnight.
I
hope
it
will
be
live.
D
Timothy
did
a
change
which
was
something
to
take
out
the
license,
which
was
a
duplicate,
so
that
was
good,
but
he
also
did
a
change
to
on
the
main
page
to
the
mailing
list.
You
change
the
google
groups
direct
link
to
a
red
hat
list.openshift.redhat.com,
I'm
not
familiar
with
that
site,
but
it's
giving
a
forum.
It's
not
a
ve.
It's
not
there.
A
So
yeah
yeah
there's
that's
where
they
did
that
there
is
an
open
shift
mailing
list
and
it
is
hold
on
one.
Second,
I
can
actually
probably
find
it
because
the
first
of
the
month,
you
always
get
the
let's
see
the
sort
of
notification
on
it.
There
is
a
mailing
list.
I've
never
seen
anyone
post
on
it.
Oh
here
we
go.
A
Right
open
shift
mm
is
one
of
them.
D
A
A
A
D
A
Back
to
google
group,
we
should
put
it
back
to
google
group.
I
I
can
and
timothy
made
that
change.
B
B
So
I
have
stuff
that
comes
in
on
that
and
this
I
have
that
on
an
archive.
The
actual
list
that
goes
in
there
is
lists.
B
B
So
it's
interesting
that
it
points
to
the
same
location
as
the
old
okd
311
that
they
said
they're
turning
off.
A
B
C
A
I
mean
if
someone
should
mention
I'll
mention
something
to
him
at
the
federal
courtroos
meeting
tomorrow
that
hey
just
you
know,
this
is
a
defunct
mailing
list.
Yeah.
D
I
mean
the
next
one
goes
back
to
what
we
were
just
talking
about.
I
put
a
link.
I
started
writing
up,
so
el
nico
put
a
link
to
a
couple
of
repos
that
had
a
read
me
and
some
documentation
on
how
to
build
modules,
and
so
I've
been
pulling
that,
together
with
some
of
the
stuff,
from
the
the
note
that
jamie
and
vadim
did
so.
D
D
So
we
we,
we
actually
talk
about
what
or
we
can
actually
show
how
to
do
it,
because
I
think,
with
a
lot
of
this
stuff,
the
first
time
you
go
through
it,
it
gets
quite
confusing
in
terms
of
all
the
pieces
and
how
to
actually
go
and
make
a
change,
and,
as
I
say,
I
tried
to
pick
the
simplest
example
I
could
think
of
using
the
console
operator.
It's
very
visual.
D
You
know
immediately
if
it's
worked
or
not,
but
then
you
can
see
and
if
you
look
at
the
documentation
I
can
probably
bring
up
on
screen.
If
you
look
at
the
documentation
it,
it
actually
is.
D
It
is
actually
got
a
lot
of
stuff
in
there
and
start
showing
that
screen.
Hopefully,
you
can
see
that.
B
D
So
yeah,
if
you
look
there's
a
lot
of
questions,
we've
actually
covered
this
like
we
can't
get
access
to
that
registry.
D
It
sounds
like
there
are
meant
to
be
public
images
available,
so
we
actually
need
to
work
out
how
how
we
can
do
that
just
doing
some
to
do's
a
lot
of
the
docker
files.
So
again,
if
anybody
wants
to
comment
on
this
either
comment
on
on
my
repo
and
raise
an
issue
on
it
or
we
could
actually
start
a
discussion
group,
but
this
is
where
actually
going
once
you
start
writing
everything
up.
D
A
lot
of
information
like
that
you
got
jamie,
is
very
useful
in
terms
of
documenting
the
release
process.
Again,
it
sounds
like
you
need
access
to
internal
systems
to
actually
be
able
to
do
a
release,
but
at
least
understanding
how
it
works
where
the
repos
are.
I'm
also
going
to
have
a
section
on
the
operator
hub,
so
as
well
as
the
the
core
functions
in
terms
of
the
add-on
functions
like
operator
hub.
D
D
So
I
just
need
to
work
out
how
all
of
that
works
and
where
they,
where
all
those
little
bits
come
from,
and
I
can
I'll
document
that
as
well
and
then
hopefully
we
are
going
to
get
the
ocp
registry,
so
the
okd
registry
built
into
this
one
as
well.
So
we
can
document
that,
as
that
gets
built
up.
A
Yeah
and
apparently
the
scoop
on
that
is
that
this
bug
that
was
there
was
you
know
this
bug
that
sort
of
hung
everyone
up,
stopped
progress
on
the
okd
catalog,
so.
D
I
I
see
there
is
now
a
repo.
There
is
an
okay
catalog
repo
now
in
the
openshift.org,
so
I'm
guessing
that's
where
it's
going
to
end
up,
and
I
mean
the
other
thing
that
I
would
say
with
that
is
I
mentioned
in
the
last
meeting
that
the
community
repo
is
pretty
much
bricked
on
okd,
because
any
community
operator
that
has
a
dependency
that
red
hat,
have
a
supported
version
for
the
community
catalogue
will
list
that
red
hat,
which
is
in
the
repo
that
obviously
opd,
doesn't
have
access
to.
D
So
even
things
like
eclipse
che
and
the
project
key.
They
have
supported
dependencies
which
are
in
the
red
hat
registry
on
ocp,
so
they
actually
get
broken
on
okd.
So
you
can't
install
che
and
it
says
it's
missing
dependencies.
The
workspace
version
203,
the
default
version
2
operator
is
is
required,
but
that's
in
the
registry.
We
don't
use
the
upstream
one,
so
I'm
hoping
that
the
okd
catalogue
will
fix
the
okd
community,
which
is
identical
to
the
red
hat
openshift
community-
repo,
that's
really
it!
D
So
if
anybody
wants
to
help
out
comment
join
in,
I
plan
to
do
those
and-
and
it
really
then
comes
back
to
what
is
the
purpose
of
the
technical
docs.
If
it's,
if
it's
for
hacking
purposes,
then
we
can
say
just
substitute:
go
and
use
the
the
ubi.
D
Eight
images
your
base
image
and-
and
we
can
say,
is
that
if
we
want
to
actually
want
to
want
documentation,
then
we're
going
to
have
to
find
out
what
is
the
official
image
that
the
build
uses
I'm
going
to
have
to
provide
guidance
on
how
to
do
that?
So
you
can
actually
do
it
a
credible,
build
of
an
operator
and
test
it
before
you.
Do
your
pull
request.
C
I
commented
back
on
that
issue
on
514,
just
saying
that
this
is
still
an
issue.
It's
actually
a
blocker
for
basically
anybody
in
the
community
who
wants
to
do
builds
without
having
to
hack.
You
know
really
the
doctor
file,
but
that
is
really
the
the
way
to
get
around
it
at
this
point
is
to
hack
that
now,
maybe
what
they
could
do
is
have
you
know
dr.community
or
something
in
those.
C
D
Then
I
I
can
see
from
a
commercial
company
that
this
is
a
licensed
product
and
and
the
repos,
although
they're
in
the
public,
they
offer
a
licensed
product.
So
and
I
I
can
see
there
be
some
sensitivity
there
in
terms
of
how
we
do
that.
But
it
goes
back
to
the
point.
A
And
I
think
the
technical
dots
you
could
also
add
as
a
bullet
point
there
or
also
for
testing
to
heaven,
so
yeah
contribute
okd
via
pull
request,
but
also
just
test
release
testing.
I
think
you
could
add
that
as
an
item
and
and
that
sort
of.
A
C
50
000
I'll
build
a
base,
a
bare
metal
environment
in
my
house,
and
I'm
I'm
just
obvious.
A
Yeah
I
mean
well
here's
the
thing
is,
you
know,
vadim
was
actually
talking
about.
He
uses
a
laptop.
He
actually
bought
one
of
his
old
company
provided
laptops
because
apparently
you
can
get
it
for
cheap
after
its
lifespan.
You
know
and
does
his
stuff
on
that.
You
know
I.
I
can
donate
some
some
hardware
cycles
to
it.
I've
got
some
some
machines
I
can
donate.
I
think
the
thing
is
making
it
official
and
actually
getting
feedback
from
folks
that
can
donate
cycles
of
hardware
that
they
have
or
or
cloud
resources
or
whatever.
D
So
again
it
would
be
nice
if
a
red
hat
could
sort
of
unless
there's
anything
proprietary
in
there
that
they
couldn't
release,
but
give
us
some
starting
places
of
this
is
how
ocp
does
it
maybe
on
vsphere
that
would
give
us
a
starting
place
now.
Maybe
we
have
to
migrate
the
script
the
pro
runs
to
run
on.
I
don't
know
techton
or
jenkins
or
whatever,
and
because
that
might
be
easier
to
set
up
than
a
full
prow.
A
Oh,
so
let
me
brian
before
you
got
involved
shortly
before
you
got
involved.
I
actually
wrote
a
suite
of
scripts
for
doing
vsphere,
upi
and
then
recently
modified
them
to
do
ipi,
and
it's
completely
automated
there's
a
repo.
It's
called
oct
openshift.
I
called
it
open
shift
cluster
tools
or
something
like
that
oct.
I
can
add
that
and
walk
people
through
it
to
the
docs
and
we
can
get
people
automating
testing
on
vsphere,
ipi
and
upi
is.
Is
there
anything.
A
A
A
Because
upi,
you
know
your
your
your
hard
code
in
your
ips.
If
you
want
or
you're
doing
it
through
an
external
dhcp
server,
that's
on
the
network
or
whatever,
so
you
don't
necessarily
need
all
of
the
cluster
pieces
of
vsphere.
To
do
that,
you
know,
but
we
should
set
up
like
a
hacking.
This
came
up
with
diane
was
we
need
another
hacking
session?
Basically
right
like
we
should
we
did
one
I
think,
like
a
year
ago,
almost
like,
and
so
it's
time
to
do
another
one.
D
A
Yeah,
okay,
so
we
have
about
10
minutes
left.
It
sounds
like
we've
got
a
plan
for
that
as
well.
To
start
formulating
some
automated
testing,
I
created
like
a
dummy
repo
in
the
okd
project,
github
just
to
play
around
with
stuff
and
and
upload
do
we
we
talked
about
this
a
little
bit
before.
Do
we
want
to
do
the
meeting
minutes
as
plain
text,
or
do
we
want
to
throw
them
in
as
formatted
pages?
D
D
A
D
D
D
D
I
mean
why
do
we
want
to
go
through
a
pull
request
and
have
to
have
multiple
people
involved
in
you
copying
from
a
hackmd
into
the
the
repo
I
to
me,
that's
a
let's
not
make
it
any
more
complex
than
it
needs
to
be.
I'm
happy
if
someone
says
no,
let's,
let's
be
a
bit
more
robust
about
things,
but
I'm
I'm
quite
pragmatic.
I
think
documentation
and.
A
I
will
always.
I
will
always
ask
first
before
I
make
assumptions
about
just
throwing
something
in
just
out
of
respect.
Do
this
so
are
we
can
we
should
we
do
a
ace?
Can
we
can
we
do
a
nested
meeting
minutes
link
so
that
it's
like
okay
working
groups,
okay,
working
group,
meeting
minutes
or
do
you
want
it
like
a
link
in
the
working
groups?
D
Well,
it's
going
to
be
a
separate
repo,
it's
not
going
to
be
in
the
uk,
the
main
doc
main
repo.
So
I
think
there's
going
to
be
a
link
and
we'll
just
put
in
nk
docs
wrap
it
around
that
meeting.
One
so
there'll
be
a
git
of
action
that
when
you
do
a
commit
it'll
just
go
and
run
the
thing
and
create
a
new
copy.
A
All
right,
let's
see
what
else
do
we
got
here.
C
C
D
C
Can
you
that,
in
the
in
the
chat,
real,
quick.
C
A
And
the
other
thing
is,
I
think
we
should
sort
of
troll
the
slack
channel
for
things
that
look
like
like.
I
really
want
to
help
michael
cramer.
This
guy,
that's
really
been
struggling
like
so
stuff,
like
that.
I
want
to
look
at
stuff
like
that,
as
opportunities
to
improve
documentation
right
yeah.
C
So
well,
part
of
it,
I
think,
is-
is
internal
to
him
too,
but
yeah
but
yeah
yeah
yeah,
but
there's
been
other
people
on
there
too,
who
have
struggled
with
a
couple
of
things
and
some
of
it.
I
can
help
with
some
of
what
I
can't
anything
that's
bare
metal.
I
don't
have
the
resources
to
help
with
the
whole
thing,
with
with
all
the
machine,
config
operators
not
being
up
to
date.
A
Michael,
did
you
get
a
an
issue?
I
think
it
was
two
days
ago
for
some
product
documentation,
there's
some
stuff
lingering,
that's
like
references
to
rel
and
whatnot
in
the
okd
documentation.
D
A
Issue
was
created
yeah,
he
said
the
issue
was
created,
but
he
didn't
link
me
to
it
and
basically
it
was
that
on
this
page.
A
Yeah,
it
was
like
it's
it's
kind
of
a
mix
of
of
things
that
need
to
get
changed
and
I
don't
he
didn't
give
me
the
link
to
the
pr,
but
I
can
search
for
it
after
the
meeting
and
or
the
yeah.
C
A
B
So
jamie
I'd
probably
need
to
communicate
with
you
directly.
I
I
tried
the
oct
your
oct
project
and
there
was
some
idiosyncrasies
that
wouldn't
allow
me
to
use
it.
A
Okay,
absolutely
yeah,
it's.
It
was
a
labor
of
love
and
then
I
switched
jobs
and
it
sort
of
languished
a
little
bit
the
past
year
or
so,
and
there's
probably
some
things
that
I
have
assumptions
that
I
need
to
to
code
around
moving
forward
but
yeah,
okay,
so
we'll
call
it
now.
Let
me
stop
recording
thanks.
Everyone
for
attending
the
meeting
and
next
week
is
the
general
group
meeting
and
then,
in
two
weeks,
another
docs
meeting
after
recording.