►
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
The
working
group
documentation
subgroup
meeting
for
july
12th
and
we
have
an
agenda
that
is
a
little
bit
light,
but
go
ahead
and
take
a
look
at
it
I'll
give
folks
a
couple
seconds
to
see.
If
there's
anything
you
want
to
add
or
change.
A
All
right
are
we
good
to
go,
then
I
think
we'll
we'll
go
ahead
and
jump
in
with
it.
So
first
item
is
technical
documentation.
There's
no
updates
jack
said
it
would
take
him
a
while
to
work
on
the
the
blog
post
that
he'd
chip
away
at
throughout
the
summer.
Glenn
marcy
has
been
furiously
working
away
in
the
channel.
A
I
noticed
he
was
commenting
on
his
snow
trying
triumphs
and
tribulations
as
he
goes,
but
he's
definitely
chipping
away
at
snow
documentation
for
us
and
getting
successful
working
towards
successful
builds
anything
else
for
technical
documentation,
stuff.
B
Yes
and
no
I'll
leave
it
till
the
later
item
and
we'll
bundle
it
all
within
that
section
and
in
terms
of
all
the
changes
that
have
happened
in
the
last
two
weeks.
Right.
B
A
All
right,
I'm
just
checking
in
with
her,
send
her
a
message
see
if
she's
gonna
make
it
all
right.
Well,
let's
table
that,
then,
because
yeah
I
mean
really,
that's
the
only
thing
that
that
impacts
us
is
just
waiting
for
that.
Okay.
So
then,
moving
on
to
de-personalizing
home
lab
documentation,
one
of
the
things
that
I
think
vadim
is
really
busy.
I
know
sri
is
really
busy
as
well.
A
B
B
B
B
B
It's
almost
like
you,
don't
know
enough
to
be
able
to
use
a
documentation
once
you've
done
it
once
it
all
just
clicks
into
place,
but
the
first
time
through
it's
like
I
don't
know
enough
to
even
know
what
the
terms
mean
and
what
they
should.
What
I'm
looking
for
here
so
having
an
example,
which
is
what
I
use
the
the
youtube
video
for,
was
that
aha
moment.
That's
what
that
means
and
then
you're
good
to
go.
B
B
B
What
can
I
get
what's
free?
What
do
I
have
to
pay
for?
How
much
resource
do
I
need?
And
it's
all
these
questions,
just
like
a
million
of
one
questions
where
someone
can
tell
you
if
you've
got
a
machine
of
this
big.
B
This
is
a
step,
follow
this
step
and
hey
press,
so
you've
got
something
running
and
then
all
the
phrases
like
ipi
upi,
and
this
name,
and
that
name
and
that
id
and
that
resource
and
all
of
a
sudden,
these
things
just
fall
into
place
where,
if
you're
just
reading
it
from
scratch,
you're
just
sort
of
like
I
haven't,
got
a
clue
what
that
means
even
letting
what
the
value
should
be.
A
How
do
we
want
to
approach
this
as
a
project,
then
in
terms
of
defining
a
a
starting
point?
Well,
first
off
this
sounds
like
two
different
things
right.
It
sounds
like,
on
the
one
hand,
we're
talking
about
a
sort
of
getting
started,
a
a
getting
started,
that's
at
the
very
beginning,
and
then
a
template
for
guides
right
for
for
guides,
for
particular
topics
is
that
am
I
reading
that
right.
A
Well,
so
the
guides
was
originally
supposed
to
be,
if
there's
a
particular
angle,
that,
like
okay
upi
on
vsphere
right,
like
that's
a
particular
thing
that,
like
maybe
I
I
think
having
that
as
a
separate
guide,
is
always
going
to
make
sense.
You
know
I
mean
like
I
don't
think
you
could
write
a
generalized
welcome
to
open
shift
or
welcome
to
okd
that
like
gave
people
enough
nuance
to
vsphere
upi,
while
at
the
same
time
being
a
sort
of
general
document.
B
D
B
But
yeah,
what
was
saying
is
is
a
documentation,
a
reference
and
if
it's
a
reference,
then
it's
not
a
how
to
then
we
need
guides,
but
if
the
documentation
should
also
be
that
how
to
then
we
don't
need
guides.
So
I
guess
my
question
is:
is
the
official
documentation
a
reference
for
install
or
is
it
a
how
to
to
do
an
install.
D
No,
no,
I
was
just
going
to
say
the
the
like.
After
you
go
through
a
lot
of
detail,
then
you
know
you
find
out
something
you
should
have
done
at
the
beginning.
That's
one
thing.
The
other
thing
is
that
I've
noticed
recently
that
a
lot
of
the
reference
documentation
seems
to
be
just
additions,
that
solve
specific
issues
and
so
now
there's
a
whole
bunch
of
accretions
to
the
documentation
so
that
it
doesn't
read
as
a
unified
thing
as
much,
and
I
don't
know
if
that.
D
That's
I
guess
the
things
I
read
the
most
are
the
the
vsphere
sections
on
installation,
probably.
C
D
C
And
one
person
described
it
as
it's
a
manual
that
shows
you
all
the
instrumentation
for
a
cockpit
of
an
airplane.
How
do
you
how
it
all
works,
but
it
doesn't
teach
you
how
to
fly
the
plane.
D
A
D
Guess
like
do
we
have
a
sorry
like
maybe
with
the
guides
and
then
I'll
stop
if
we
picked
one
for
reference
environment
because
and
then
try
to
make
a
good
guide
there
that
might
be
easier
than
fixing
all
of
our
guides.
D
You
know
because
we've
got
you
know
like
vsphere,
we've
got
the
you
know
various
you
know,
virtualizations
on
linux,.
D
The
fcos
now
claims
that
you
can
install
it
on
virtualbox,
although
I
did
that
at
the
very
beginning
and
it
didn't
quite
work,
but
probably
now
it
works.
So
like
there's,
you
know
so
many
possible
installations
right
and
I
think
if
you
were
a
total
newbie,
that
all
those
possibilities
don't
make
your
life
easier.
D
Because
again
you
don't
know
what
to
choose.
In
many
cases,
what
you
choose
is
not
so
critical
and
so
the
you
know
some
of
the
opinionated
guides
like
if
we
had
one
that
we
said.
Okay
follow
this.
D
A
Well,
I
think
that
that's
valid.
I
think
that
you
know
we
if
we
had
a
getting
started,
got
a
getting
started
document
that
pointed
to
a
getting
started
with
okd
guide.
That
was,
like
here's,
the
most
basic
cluster
that
you
could
build
on
your
home
machine
to
familiarize
yourself
with
this
or
whatever.
So
I
I
could
see
the
the
two
of
them
sort
of
linked
right
there.
A
C
A
D
So
is
mine,
and
and
actually
the
when
I
was
playing
with
the
tecton
stuff
and
running
to
roadblocks
various
places.
What
I
finally
did
is
I
installed
fedora.
D
You
know
like
a
virtual
fedora
again
and
set
up
my
tool
chain
and
fedora,
and
that
worked
yeah,
because
it
turned
out
that
the
even
after
I
got
the
right
go
version
that
the
tecton
people
were
using,
which
was
back
from
the
current
one.
Their
scripts
didn't
work
under
either
the
macbash
or
zed
shell,
which
is
your
you
know
what
I'm
currently
using.
D
So
it's
and
you
know,
rather
than
debug
the
things
to
get
it
to
work
on
the
mac.
It
was
easier
to
do
it
from
fedora,
and
I
imagine
I
mean
ubuntu
would
have
worked
just
as
well.
I
would
guess.
A
A
B
And
should
that
live
on
docs.okay
I
o
or
should
that
be
on
the
community
site?
Because
but
for
me
that's
the
issue
is:
do
we
want
to
try
and
get
the
docs
to
a
point
where
there's
a
lower
entry
point,
or
do
we
want
to
go
and
create
a
guide
within
the
community
section
that
use
that
then
uses
the
documentation
as
reference
for.
A
The
actual
michael
might
be
able
to
let
us
know,
I
is
it
easy
now
to.
I
know,
there's
like
a
new
document
build
process
right.
Is
it
still
sort
of
like
books
where
we
could
have
a
book
inserted
in
the
in
in
the
list
of
of
books?
Basically,
as
chapters
yeah,
so
I
mean
if
we
came
up
with
something
that
was
nice
and
polished,
so
I
think
we
could
insert
it
into
the
into
the
to
the
docs
um.okd.io.
A
The
question
then
becomes:
if
we
put
something
in
the
official
documentation,
we
have
to
have
a
process
of
review
and
you
know
like
we
have
to
have
the
same
thing
that
basically
red
hat
has
for
the
upstream
docs.
We
need
a
defined
process
for
review
and
we
need
to
make
sure
that
there's
always
someone
who
knows
that
it's
going
to
be
their
responsibility,
this
time
around,
to
review
that
documentation
and
make
sure
that
it's
correct.
A
A
B
Is
that
going
to
lower
the
the
sort
of
entry
point
for
other
installs,
because
once
we
have
the
assist
of
the
solar
process
defined,
we
can
use
that
to
do
a
lot
of
the
ipis
for
all
the
different
platforms.
I've.
I
don't
know
how
it
handles
upi
or
if
it
does
at
all,
it
gives
you
an
easier
starting
point,
maybe
creates
the
isos.
I
don't
know,
but
I'm
aware
that
that
might
change
the
game
for
some
of
the
other
installs
as
well.
So.
A
Yeah,
I'm
looking.
I
need
to
read
through
the
thread
that
glenn
has
in
the
chat,
because
there's
literally
a
hundred
messages
over
a
hundred
messages
that
glenn
posted
as
he
was
working
through
doing
snow.
So
that
kind
of
concerns
me
because,
if
there's
a
lot
of
hacking,
that
needs
to
be
done
to
get
something
that's
functional.
A
B
B
B
C
B
D
A
D
D
B
I
believe
I
believe,
yeah
ocp,
I
believe,
is
already
there,
but,
apart
from
you,
don't
have
to
run
it
locally,
which
is
where,
which
is
where
we
got
stuck,
I
believe,
with
410.
They
removed
the
ability
of
just
doing
a
an
ipi
setting
the
worker
nodes
to
zero,
which
is
how
you
used
to
do
it.
I
believe
you
have
to
go
through
the
insisted
installer
now
because
of
the
way
they're
changing
the
initial
boot
bootstrap.
B
B
B
A
Right
I
can
revisit
mine
and
I
think
that's.
The
first
thing
that
I
should
do
is
revisit
mine
and
decide
where
that
should
go.
I
mean,
ultimately,
that
might
even
be
a
blog
post
in
itself.
B
A
B
A
B
See
mike
mike
corrected
all
of
this
stuff,
he
put
it
all
together,
so
I
I
actually
don't
know
where
it
came
from.
I
mean
some
of
them
actually
have
names
in
it.
D
B
So
that's
why
I
say
I
think
that
if
we
get
the
sno
stuff
running
properly,
then
we
get
a
lot
of
these
ipis
for
free
yeah
and
same
with
the
vsphere
ipi,
and
all
of
these
should
come
through
that
yeah.
I
believe
the
vsphere
one
gives
you
a
bootable
iso
file
that
then
re-registers
itself
within
your
environment
and
then
you
just
click
a
button
and
say:
go.
B
B
Work
out
does
it
make
sense
to
keep
them,
or
should
they
just
be
sunset
or
move
to
a
blog,
okay.
Well,.
B
A
All
right:
well,
let's,
let's
get
started
async
on
that
discussion
about
a
a
getting
started,
base,
level,
guide
or
sorry
base
level
document
or
page
in
the
documentation
even
more
specifically
and
talk
about
what
do
we
really
want
that
document
to
cover?
A
So
we
can
work
in
that
asynchronously
on
that
thread
and
I'll
actually
post
that
thread
in
the
channel
and
see
if
anyone
random
wants
to
contribute
some
ideas
because
we're
in
the
thick
of
it
right,
so
I've
been
working
with
openshift
in
okd
for
like
five
years
now
or
whatever
at
this
point,
we'd
probably
want
to
ask
some
people
who
don't
know
what
would
you
like
to
know
if
you
were
to
come
to
this
fresh?
B
A
Yeah
I
did
vsphere
upi
and
it
was
took
me
a
lot
of
trial
and
error
took
me
a
long
time
to
get
things
running.
I
eventually
did
but,
but
I
also
had
the
advantage
of
having
an
f5
for
my
load,
balancing
up
front
and
stuff,
and
some
that
makes
that
a
little
bit
easier
here
right.
I
have
a
big
ip
all
right
so
up
next
is
I'm.
C
A
C
A
B
A
Okay,
all
right
moving
on
now
to
community
governance
and
processes,
brian
okay,.
B
So
this
is
a
biggie
and,
with
me
doing
the
pictures
with
christian
in
dublin
for
okd,
I
actually
had
time
to
actually
sit
down,
have
a
good
chat
with
him
and,
alongside
that,
we're
trying
to
get
the
community
involved
in
a
lot
of
projects
where
we
have
a
build
process.
We
can
do
that
and
we
had
a
meeting
today
with
some
red
hatters
about
creating
operators
in
a
community
catalog.
B
Git
organization,
which
means
we
can
we're
now
going
to
have
to
take
pull
requests.
We're
going
to
have
to
have
some
sort
of
governance,
some
form
of
making
decisions
and
who
accepts
pull
requests,
and
I
think
we
need
a
project
board.
So
when
we
start
getting
into
this,
we
knew
it's
it's
a
fundamental
shift
from
where
we
are
today,
which
is
basically
an
information
community
and
sharing
stuff
and
what
we
can
do
to
a
where
we
actually
can
take
on
some
responsibility.
B
So
I
think
we
do
need
to
just
think
about
how
we're
going
to
do
that.
What
tools
we
want,
what
process
we
want?
Who
needs
to
be
involved
in
terms
of
people,
and
so
we
need
to.
I
have
some
approvers
and
we
need
to
actually
have
some
formal
process
of.
If
someone
thinks
that
something
shouldn't
be
approved,
how
do
we
actually
come
to
those
decisions?
B
So
I
think
that
is
the
first
one,
and
then
should
that
happen
as
part
of
the
main
group,
or
should
this
meeting
get
I
mean
we've
talked
about
this
being
more
than
documentation.
This
is
more
of
the
community
call.
Rather
than
should
this
become
the
the
community
governance
call
for
want
of
a
better
word.
B
That
then,
feeds
into
the
main
document,
so
I
think
there's
a
lot
of
housekeeping
and
just
stuff
that
we
need
to
sort
of
get
in
front
of
and
just
to
bring
you
up
to
speed
on
some
of
the
other
meetings
before
we
actually
have
the
conversation.
B
So
when
I
was
with
christian,
we
talked
about
the
base
images,
the
fact
that
they
are
actually
defined,
but
they
go
through
a
number
of
prow
transformations
so
trying
to
work
out
what's
actually
in
those
base.
Images
is
not
trivial
and.
B
There's
both
a
build
and
a
base
image
available
within
the
origin
that
we
can
use
but
again
finding
them
find
what
finding
what
the
tags
are,
what
tag
we
should
be
using
and
we
we
can't.
We
don't
have
that
access
so
christian
and
if
you
look
he's
actually
created
the
repo
today
and
we're
going
to
actually
have
a
an
images
repo
in
the
okd
project,
github
and
they're,
going
to
mirror
both
the
container
file
and
then
we've
also
got
a
key.io
project.
B
We'll
have
the
images
in
there.
So
that's
going
to
be
the
base
images
that
we
can
use
as
a
community
to
build
all
our
stuff
on.
So
that
was
one
of
the
conversations
and
in
the
main
group
we
talked
about
the
hack
and
getting
the
community
build
operators
creating
an
okd
catalogue
which
is
parallel
to
the
red
hat
catalog
on
ocp
and
christian
organized
a
call
today,
jamie
and
I
were
invited
to
that-
where
red
hatches
have
got
their
project
week
this
week,
where
they
can
do
their
own
thing,
and
there
is
a
team.
B
The
community
team
are
actually
taking
on
board
the
operators,
so
they
they're
creating
a
tecton
pipeline
and
to
create
to
build
operators
they're
creating
a
generic
pipeline.
Hopefully
they
can
then
build
a
number
of
operators
and
I
cheekily
suggested
they
start
with
the
pipeline
operator,
so
they
accepted
that
they're
taking
that
on
board.
B
A
I
think
you're
right.
I
think
that
this
meeting
is
turning
more
into
a
governance
meeting,
because
the
more
that
we
deal
with
documentation,
I've
noticed
that
it
is
actually
in
it.
It
essentially
impacts
the
direction
of
the
community
as
a
whole,
much
more
than
sort
of
the
technical
conversations
that
happen
at
the
main
meeting
right.
A
I
see
that
we
would
need
to
create
a
team
that
is
sort
of
a
the
technical
team
that
would
approve,
merge,
requests
and
other
technical
things.
A
I
see
that
we
would
actually
need
to
define
this
group
as
a
governance
group
and
actually
like
make
it
official,
as
opposed
to
us
sort
of
calling
it
the
documentation,
group
and
hacking
on
the
government's
part,
and
we
did
have
a
board
before
when
I
first
joined
the
group.
Diane
was
actually
using
a
board,
but
it
was
never
updated,
so
it
was
really
hard
to,
and
it's
probably
still,
I
think,
in
the
community
repo.
A
I
think,
if
you
check
under
the
boards
there,
you
might
see
it
still,
but
it
if
we're
going
to
do
a
board.
I
think
we
have
to
update
it
continuously
and
make
sure
that
that
we,
you
know
configured
in
such
a
way
that
it
that
it's
useful
for
the
tasks
that
it
should
be
used
for.
D
Yo,
I
guess
okay,
so
reasonable.
So
far,
one
of
my
concerns
when
brian
talked
about
setting
up
a
separate
catalog
was
well
okay.
If
you
have
similar
content
to
the
official
one,
then
you
got
a
lot
of
operators
and
with
the
official
one
there's
a
way
of
keeping
everything
up
to
date
and
it
seemed
like
you
would
need
that
as
well
and
in
some
cases
really,
there
are
no
tweaks
that
you
would
have
to
do
for
okd.
D
It's
just
a
matter
of
rebuilding
whatever
is
the
ocp
version?
Some
cases
it's
just
the
open
community
version.
You
know
the
kubernetes
version
works,
fine,
some
cases,
you've
got
a
lot
of
deltas
and,
as
I
discovered
when
I
was
researching
the
serverless
stuff,
there's
even
new
repositories
that
are
not
connected
to
anything
else
that
keep
popping
up.
D
D
D
We
don't
see
huge
numbers
of
new
people
at
our
current
meetings,
so
we
would
somehow
have
to
get
you
know.
People
excited
to
volunteer,
so
you
know,
maybe
we
anyway,
the.
I
guess
that
that's
my
concern
is
that
we
don't
want
to
wind
up
with
a
catalog,
which
you
know
a
year
later,
we're
now
on
4.14
and
our
catalog
is
stuck
on
4.10.
A
D
B
I
was
just
going
to
say
so
I
I
think
part
of
the
part
of
the
the
challenge
is
that
we
can
only
do
this
when
we
get
things
like
the
first
cloud
or
as
we
talked
about
in
last
week's
meeting
there
is
this
new
red
hat,
build
system
that
they
that
we
have
an
opportunity
to
become
an
early
acc,
an
early
adopter
of
so
there
has
to
be
a
a
build
system
that
is
running
all
the
time
that
we
can
use.
B
I
I
agree
that
this
is
a
non-starter
if
we
have
to
do
it
on
people's
home
machines
and
there
isn't
an
official
infrastructure-
and
I
think
part
of
the
project
that
the
red
hat
team
are
looking
at
this
week
and
we
want
to
continue
in
the
hack
is
this
has
to
be
automated?
B
It's
not
something
that
I
mean.
I
believe
vadim
has
to
do
a
certain
amount
of
work
to
do
an
okd
release,
so
I
think
we
need
swimming,
whether
we're
just
scraping
repos
and
comparing
the
latest
release
targo.
How
do
we
do
it?
We
want
to
make
this
as
automated
as
possible,
so
we
build
it
and
then
we
can
test
it
with
a
high
degree
of
confidence
that
we
can
release
it
with
minimal
minimal
human
intervention.
If
we
can't
get
to
there,
I
think
you're
right.
B
So
I
I
think
they
are
very,
very
fair
points
and
I
think
if
it
is
the
community
one,
we
should
push
together
put
into
the
community
hub
and
I've
only
just
found.
I
shared
the
the
repo
where
the
community
hub
is
actually
defined.
It's
a
different
github
organization.
It's
the
red
hat
ecosystem
organization,.
B
A
A
We
need
to
somehow
get
more
people
involved
because
it's
literally
the
same
five
or
six
people
right
and
that's
not
enough
to
float
a
community
taking
on
like
builds
and
no
matter
how
much
automation
you
have.
There's
gonna
be
people
that
need
to
approve
things,
there's
you
know,
and
documentation
and
governments
and
governance
and
etc.
A
We,
I
haven't,
looked
at
the
survey
yet,
but
I
think
we
need
to
promote
the
the
survey
to
get
a
sense
of
what
people
want
and
with
the
survey
say.
Okay,
you
know
if
reach
out
to
us,
if
you're
interested
in
getting
involved
right,
here's
a
survey
and
reach
out
to
us.
If,
if
you
want
to
find
out
more
about
getting
involved,.
B
I
I
also
think
about
if
we
have
a
board,
it
also
helps
people
get
on
board
because
at
the
minute,
if
someone
wants
to
join
a
community,
there's
nothing
for
them
to
do
it's
nothing
obvious
for
them
to
do,
there's
no
way
of
them
saying
oh,
I
could
have
a
go
at
that.
So
a
lot
of
communities
have
the
easy
first,
the
first
issue
tag
or
things
like
that
to
sort
of
say,
come
and
join
us,
and
this
is
the
list
of
jobs
that
we
were
looking
to
get
done
right.
B
And
some
of
them
are
or
tagged
that
these
are
the
easier
ones
to
help
you
get
and
set
because
at
the
minute,
when
someone
comes
on
our
calls
and-
and
I
actually
met
a
couple
at
the
two
two
gatherings
that
I
did
and
they
said
well
it-
it
can
be
quite
daunting
because
there's
nothing
obvious
for
them
to
do
to
join,
to
contribute,
and
it
takes
a
little
while
to
understand
what
we're
all
yakking
on
about
because,
as
you
said,
we're
in
the
thick
of
it,
and
we
pick
up
conversations
from
previous
meetings
and
it's.
B
It
can
be
very
daunting
to
try
and
come
on
board.
So
I
did
tell
them
just
ping
me
or
just
speak
up
and
say
I
haven't
got
a
clue
what
you're
talking
about.
Can
you
please
give
me
some
context,
but
I
I
so
I
I
think
if
we
get
a
little
bit
more
structure
to
how
the
community
works,
that's
an
easier
way
to
try
and
board
somebody,
because
we
can
say
here's
a
group
of
things
that
we
need
help
with
it's
a
concrete
list
and
they
can
decide
if
anything
meets
their
skill
set.
A
Yeah
does
that
make
sense
to
have
a
a
github
project
created
with
this
and
and
the
projects
basically
are
a
spreadsheet.
In
essence,
a
list
of
tasks,
merge
requests
items
and
whatnot.
A
B
I
think
we
have
to.
I
was
trying
to
think
about
that,
because
they,
if
we're
using
discussions
and
we're
using
the
other
one
for
that
for
general
chat,
I
don't
want
to
clutter
up.
Maybe
we
need
a
planning
repo,
but
we
actually
do
just
use
the
issues
off
for
a
github
project
and
we
can
have
a
board
and
it
it's
like
curated
tasks
and
it
doesn't
get
cluttered
by
people
just
raising
issues
of
saying
my
install's
stuck
and
I
I
can't
work
out
how
to
make
this
operator
update,
and
so
I
just
yeah.
A
A
Then,
basically,
we
will
end
up
sort
of
with
what
we
have
now
only
it'll
be
in
our
control
there,
because
there
is
the
community
repo
now
and
then
there's
sort
of
the
technical
one.
So
we'll
just
be
mirroring
that
then-
and
we
want
to
make
sure
that
the
two
so
but
if
there's
technical
things
that
someone
needs
to
do,
then
it
we
need,
it
needs
to
be
across
repo,
and
we
just
need
to
make
sure
everyone
knows
how
to
do.
Crossfit
link
cross
repo
linking
for
issues
and
merge,
requests
and
stuff
like
that.
B
And
then
the
the
other
tricky
thing
here
is
that
internally,
red
hat
have
jira
and
christian
has
given
us
a
link
to
the
jira
board,
but
as
yet,
he
doesn't
think
that
community
members
can
raise
new
tickets
on
that
board,
but
we
can
see
it
so
there
will
be
some
things
that
will
be
getting
done
internally
within
red
hat.
That
would
be
on
the
jira
board.
B
I
think
there's
our
community
project,
which
is
going
to
be
in
the
okd
project,
and
my
initial
thought
is
that
we
have
a
planning
repo
that
hosts
just
that
board
and
that
project
and
then
we're
going
to
have
the
main
okd
repo,
which
is
where
we're
going
to
have
discussion
items
and
anybody
that
wants
to
raise
an
issue.
That's
where
they'd
raise
an
issue,
so
the
planning
one
is
for
only
when
we've
identified
a
task
and
we're
going
to
track
the
task.
A
B
A
B
Then
we
we
write
up,
I
mean
obviously,
we've
got
to
write
up
our
governance
rules
and
our
processes
on
okd.io.
So
and
that's
where
we
would
point
someone
to
on
and
we'd
have
a
within
the
contribution,
we'll
create
contributions,
contributing
section
and
we'll
explain
how
the
planning
repo
works
and
how
they
how
they
can
participate
and.
A
Yeah
we
did,
we
archived
it
anyway,
so
we're
basically
done
with
that.
So
we
can
create
a
new
one.
That
is
just
planning.
B
A
D
B
A
B
That
would
then
move
on
to
the
planning
board
in
the
backlog
with
a
needing
to
be
done,
and
then
that's
where
that
action
would
be,
and
then
we
cross-linked
the
discussion
to
say
this
is
now
being
moved
to
an
official
activity.
The
discussions
over
here,
so
we
shut
down
the
discussion
and
move
it
to
planning.
A
Okay,
so
let's
formulate
this
into
a
coherent
thing
to
bring
to
the
main
group
next
tuesday
and.
A
Maybe
brian
maybe
create
a
bulleted
list
of
things.
We
want
to
touch
on
or
add
it
to
the
meeting
notes
for
next
week's
meeting,
just
bulleted
items
of
things
that
we
want
to
bring
up.
That
came
out
of
this
in
the
covered
in
the
in
the
updates
from
the
documentation
subgroup
and
then
let's
bring
that
concise
list
of
things
to
the
main
group
and
see
what
they
say
and
I
think
just
go
from
there
we'll
see
what
what
other
folks
say.
A
To
be
clear,
the
the
three
or
four
of
us,
five
of
us
are
probably
gonna,
be
doing
a
lot
of
heavy
lifting
for
the
community
aspect
for
a
while,
so
folks
have
to
kind
of
be
invested.
If
we
create
a
separate
repo
and
whatever,
then
we
essentially
have
to
be
committed
until
we
get
more
people
involved
to
maintaining
that
to
make
it
appetizing
for
people
to
get
involved
to
yeah,
you
know
to
help
maintain
it.
A
C
Does
anyone
here?
No,
no,
I'm
sorry
does
anybody.
Does
anyone
here
know
how
a
feature
gets
excluded
from
okd.
A
Gets
excluded,
I
think
it's,
it's
literally
just
is
there
something
proprietary,
not
proprietary,
but
something
with
red
hat
stuff
in
it
like
an
operator
or
something
do
you
know.
B
B
B
Obviously,
there's
a
different
underlying
rail
versus
fedora,
but
where
we
are
missing
functionality
is,
are
the
add-on
operators,
which
is
the
conversation
about
creating
an
okd
catalog,
so
features
like
the
serverless,
like
git
ops
like
techton,
like
storage
features
that
require
the
advanced
cluster
manager,
features
that
require
the
assisted
installer.
B
B
A
A
Actually
have
a:
we
don't
actually
have
a
like
a
translation
of
what
those
operators
actually
are
in
terms
of
features
which
might
be
helpful
because
that'll
help
michael
with
documentation,
because
he's
he's
got
to
know.
Oh,
I
need
to
pull
out
the
get
ops
section
and
stuff.
You
know.
D
Yeah,
if
there's
actually
an
exclusion
list
that
would
be
useful
to
have
right.
You
know
just
sort
of
raise
up
to
higher
visibility
like
some
of
them
are
sort
of
obvious
and
we
keep
mentioning
them,
but
the
I
never
thought
about
the
security
thing.
For
instance,
although
I
was
wondering
about
the
multi-tenancy
recently
and
looked
and
found
that
there
was
some
multi-tenancy
stuff
on
ocp,
that
didn't
seem
to
be
obvious
in
okd,
and
you
know
so.
A
list
lists
are
often
helpful.
D
But
yeah,
no,
the
like
I.
I
am
optimistic
about
the
the
new
plan,
even
though
I
do
raise
concerns,
as
is
my
want.
Yeah,
don't
take
that
for
pessimism.
B
Yeah
sorry
bruce
just
another
point
that
you
raised,
that
I
didn't
answer
is
a
lot
of
the
red
hat.
Engineering
teams
are
very
resource
constrained,
which
is
why
I
mean,
if
you
look
at
that
link
I
sent,
which
is
the
ecosystem.
There
is
an
okd
repo
for
any
an
okd
catalog
repo
there
for
where
they
should
have
been
populated
and
there's
not
a
single
one
being
populated
and
speaking
to
christian.
B
He
doesn't
think
that
that's
gonna
happen
anytime
soon,
so
we've
already
been
waiting
for
red
hat
to
to
help
us
out
and
populate
this
catalogue.
For
what
four
months
now-
and
I
think
the
consensus
is,
the
pressure
on
the
engineering
teams
is
just
too
great
for
them
to
expect
them
to
do
that
for
us
and
which
is
why
we
we're
now
coming
up
with
the
ideas
of
let's,
let's
enable
the
community
to
build
these
catalogs
or
this
catalog.
A
All
right:
well,
that's
a
lot
to
chew
on
so,
let's,
let's
call
it
a
day,
because
I've
been
in
two
hour
long
meetings
for
okd
today
and
and.
A
Okay,
so
we
will
bring
a
list
of
things
to
the
main
meeting,
we'll
see
what
folks
think
and
then,
let's
get
started,
assuming
everyone
is
on
board
with,
on
the
one
hand,
trying
to
drum
up
interest
and
participation
and
what
chicken
egg
situation
goes
hand
in
hand
with
that
is
getting
this.
C
A
All
right,
thank
you
so
much
folks.
This
has
been
a
great
meeting
and
I'll
see
you
online
yep
great
thanks.