►
From YouTube: OKD Community Development Meeting 05-30-2023
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
B
Okay,
so
let's
start
first
of
all,
is
anybody
want
to
talk
about
anything,
that's
in
the
done
column
that
they
want
us
to
review
or
talk
about.
B
B
I
haven't
yet
had
a
chance
to
actually
get
that
done,
but
I
will
Endeavor
to
do
that
this
week.
So
it'll
be
available
for
comment
on
review
next
week,
so
I'm
going
to
move
that
one
to
in
progress.
B
Next
we've
got
a
divide,
Define
the
process
to
create
a
document.
Pr
I,
don't
know
who
created
this
one,
but
we
sort
of
do
have
that
in
the
okd.io
docs.
B
So
we
talked
about
that
last
time
and
as
I
created
it
at
the
last
meeting,
I'm
not
sure
whether
we
actually
need
to
do
anything
here.
Michael.
Are
you
aware
of
any
issues
that
people
have
brought
up
around
how
to
create
a
PR?
B
B
So
if
somebody
does
want
to
go
into
the
official
okd
docs,
which
is
in
the
red
hat,
open
shift
repo,
is
there
any
way
that
they
could
get
to
the
point
where
they
can
at
least
build
the
docs
check
that
their
syntax
is
correct?
It
does
actually
create
a
valid
page,
and
if
so,
can
we
actually
Define
that
process?
Nobody
on
the
call
sort
of
seemed
to
know
if
that
was
possible
outside
of
the
the
pipelines
that
were
running
side,
red
hat.
C
Sorry
Brian,
could
you
tell
me
the
number
of
the
cardigan
that
you're
looking
at.
B
B
You
I
haven't
really
put
any
details
in
there.
D
B
So
I
guess
the
question
is:
is
this
something
that
we
want
members
to
community
members
to
do,
or
is
this
where
they
should
write
what
they
want
the
pace
to
say
and
request
that
so
Michael
makes
the
chain
changes
in
collaboration
with
them?
What's
the
what's,
how
should
we
want
to
approach
this?
One.
B
The
problem
is,
though,
we
shouldn't
really
submit
a
PR
if
the
syntax
is
so
broken
that
it
breaks
the
red
hat,
build
because
I
think
that
that's
the
issue
outside
of
the
red
hat
sort
of
firewall,
nobody
can
validate
that.
If
they
create
a
page,
they
haven't
broken
the
syntax
or
they
haven't
invalidated
the
syntax.
B
B
B
D
I
know
currently
there's
like
a
preview
mechanism
that
works
with
some
internal
structure
here,
red
hat
but
like
even
if
it's
like,
and
this
is
where
I
was
trying
to
go
with,
with
my
hacking
on
the
docs
like
if
I
could
contribute
like
a
Docker
file
or
something
like
if
there
were
a
container
I
could
run.
That
would
create
the
docs
for
me
and
allow
me
just
to
run
it
on
my
local
machine,
like
that.
D
It
to
me
would
be
like
the
high
water
mark
for
what
I
would
love
to
see
in
the
repo,
because
that
would
make
it
easy
for
anyone
in
our
community
than
to
be
able
to
like
test
their
PR
out
I,
just
like
I
get
into
a
wall
because
I
don't
know
the
doc's
tooling.
Well
enough
to
understand
like
where
the
limitations
are
there.
C
B
D
D
Probably
someone
just
needs
to
spend
like
some
time
playing
around
with
it
and
seeing
how
to
and
it
doesn't
have
to
be
a
redhead
or
it
could
be
a
Community
member,
because
all
these
tools
are
open
so
but
I
think
someone
needs
to
kind
of
spend
time,
debugging
it
and
figure
out
how
to
make
it
work
and
then,
if
we
could
just
have
like,
then
we
could
have
an
image
that
we
could
just
reuse
a
container
image.
We
could
reuse
to
kind
of
like
run
the
site
locally.
D
B
B
B
So
this
is
a
conversation
really
around.
What
is
the
okd
release
cycle
and
just
make
sure
that
we
we
fully
document.
B
Okay,
that
we
don't
have
formal
support,
but
what
is
the
way
that
people
can
actually
ask
assistants
around
that
release
cycle,
also,
the
fact
that
we
don't
maintain
previous
version
So.
Currently
we
don't
have
that
multiple
streams
of
support
of
of
releases.
We
are
actively
working
on,
so
that
was
a
a
request
just
to
put
that
in
so
again
looking
for
someone
to
actually.
B
B
B
We
just
need
to
work
out
what
we're
going
to
do
and
write
it
up
somewhere
in
in
the
docs
I.
Guess.
C
So
for
okay
on
S
course,
we
now
have
a
pretty
stable
sprintly
release
Cadence,
that
is
every
three
weeks.
That's
been
working
quite
well
for
the
past
six
weeks,
yeah.
Hopefully
we
can
keep
it
that
way.
What
we
haven't
done
yet
is
sync
up
with
Vadim
on
actually
taking
over
the
release.
Engineering
part
from
him.
I
think
what
we
want
to
do
going
forward
is
create
sprinkly.
That
is
three
weekly
releases
of
all
of
our
three
streams
that
is
okd
onf
course:
stable.
C
C
Since
he
is
currently
still
doing
the
Fedora
releases,
but
ideally
we
can.
We
can
take
that
off
of
his
shoulders
and
do
it
through
the
CFE.
C
Is
part
of
and
and
the
okd
streams
team
internally
that
that
we
now
have.
B
Okay,
that's
great
okay!
So
that's
the
new
ones
done
going
into
backlog.
Number
29
move
guides
to
blog
post.
That's
on
me!
I
am
looking
to
integrate
a
new
technology
to
add
a
Blog
section
which
is
automatically
indexes
them.
So
as
part
of
the
build
process,
it'll
automatically
create
the
index
page
of
blog,
some
a
lot
easier
to
provide
blogs
to
the
site.
There
is
a
plugin
to
mpdocs
that
does
that
a
slight
issue
with
it
at
the
minute
I'm
just
trying
to
track
down
resolution.
B
B
The
guys
are
all
out
today,
so
having
them
date
having
them
have
a
date
and
a
context
would
be
a
good
idea.
So
that's
why
we're
moving
them
into
the
blogs.
A
B
B
B
C
Real
quick,
if
I
may,
regarding
the
operators
with
we
have
just
set
up
a
a
new
cluster
on
the
Massachusetts
open
Cloud
that
we're
going
to
use
as
a
build
farm
for
Centos
stream,
core
OS
and,
ideally
in
the
future,
even
more.
But
for
now
we
will
just
build
s-cos
on
on
that
new
cluster
and
that's
going
to
be
an
okd
or
that
is
an
okd
cluster
and
we
need
to
set
up
tecton
and
Argo
there.
C
So,
ideally,
will
be
a
consumer
of
the
community
builds
of
both
the
pipelines
operator
and
the
git
Ops
operator
on
that
cluster.
So
we
can
really
consume
the
community,
build
on
our
official
build
infrastructure
for
official
s-cos
builds,
and
those
are
then
that
cluster
is
going
to
also
become
part
of
the
Centos
infrastructure.
So
we
can
call
it
official
Centos
release,
artifacts
and
yeah.
C
Just
just
a
heads
up,
I
think
we
are
interested
in
consuming
those
operators
as
well,
we'll
we'll
get
started
with
just
using
the
red
hat
provided
builds
since
we,
since
that's
kind
of
an
internal
cluster
still,
and
we
can,
we
can
pull
them
there.
But
ideally
we
want
to
switch
that
over
to
the
community
builds
in
the
long
run.
So.
B
Great
fantastic,
okay,
so
number
two,
this
one's
been
around
for
a
long
time
since
September.
So
the
idea
with
this
one
is
that
we
want
to
get
into
the
habit
of
creating
educational
contents
or
videos.
B
B
We
did
get
a
set
of
topics
and,
as
far
as
I'm
aware,
the
only
one
that
was
done
was
number
one
which
was
El
Nico.
He
took
us
through
how
to
actually
what
the
build
process
was
and
a
little
bit
about
how
you
actually
went
and
debugged
that
do
you
want
to
say
something
you
can
handle.
D
D
Unfortunately,
then
I
I
turned
my
life
upside
down
by
coming
over
to
Europe
for
a
couple
months
and
I
haven't
gotten
back
to
like
doing
the
recording
for
that,
so
like
I
I
still
would
like
to
do
a
must
gather
and
related
tooling
video,
probably
like
30
minutes,
but
what
I
think
like
what
given
the
way
we
were
doing
things
in
the
past.
I
think
something
we
talked
about
going
on
in
the
future.
D
Is
that
maybe
content
creators
could
create
the
video
themselves
and
then
share
it
with
like
Jamie
to
get
the
the
proper
like
bumpers
on
it
or
whatever,
and
then
upload
it
to
the
right
place.
So
I
was
going
to
try
to
continue
working
on
that
angle,
assuming
that
you
know
that
workflow
still
works
for
Jamie
and
for
the
community
and
everything.
F
It
does
for
me
I'm,
you
know,
happy
to
video
tweet,
video
and
code,
video
and
post
it.
If
we
just
need
folks
doing
content,
does
it
works,
yeah.
A
B
Okay,
so
again,
if
you
go
to
item
number
two,
there
is
a
discussion
thread
that
you
can
sort
of
add
thoughts,
but
we
are
looking
for
volunteers
all
the
time.
So
if
you
have
one,
it
would
be
very
useful
if
you're
already
volunteered
again,
if
you
want
to
actually
talk
to
Jamie
about
getting
some
video
help,
you
can
take
that
okay.
B
Number
26
write
a
board
guidelines.
We
haven't
got
a
volunteer
for
that
one,
but
that
still
needs
to
be
done
again.
If
you
see
anything
on
there
that
you
fancy
doing
or
that
you'd
like
to
have
a
go
but
you're
not
sure,
always
look
for
volunteers,
you
can
ping
me
slack
me
and
in
the
kubernetes
slack
Channel
happy
to
help
anyone
get
going
right.
The
single
node
open
shift,
so
Luigi
has
published
his
how
to
do
it
manually.
B
I
noticed
there
was
quite
a
bit
of
chat
around
the
assistant
installer
and
the
agent
install
process,
so
I
need
to
go
back
with
4.13
and
see
if
that
fixed.
The
problems
I
was
having
and
photo
12.
It
did
not
work
on
either
fcos
or
s-cos
in
terms
of
getting
the
assisted,
installer
working
for
a
single
node
installed,
and
so
we
need
to
go
around
the
loop
again
on
that,
if
not
I'll
be
looking
for
help
to
actually
get
that
going
as
far
as
I.
C
C
Hopefully
we'll
get
to
it
next
spring,
which
starts
in
in
two
and
a
half
weeks
after
defconf,
hopefully
by
then
we'll
be
able
to
look
look
into
that
internally
as
well,
but
anything
you
can
already
you
know,
provide
us
in
terms
of
logs
and
and
errors
from
the
community
side
would
be
appreciated.
So
we
kind
of
get
a
head
start
there.
C
E
Sorry
about
what
I
was
gonna
say:
we've
also
been
working
on
the
agent
installer
with
Andrea
fazzano
he's
been
on
the
call
here
as
well,
and
we've
started
on
various
versions
of
Fedora
30
from
38
36
37
we're
still
having
problems
so
there's
there's
some
maturity
needed
there
so
yeah.
If
you
could
also
try
the
edge
into
it
as
as
Christian
mentioned,
it
would
be
great
and
report
back.
B
B
We've
covered
37
going
into
the
ready
column,
so
this
is
work
that
we've
agreed.
That
needs
to
be
done
and
we're
now
just
looking
for
people
to
do
it.
B
So
number
25
is
about
getting
good
tutorials.
The
guides
are
quite
out
of
date,
so
this
is
I've,
never
done.
Okd
I'm,
not
really
sure
it's
about
help
me
get
started
quickly.
So
basically
that's
what
this
is.
B
It's
just
somewhere
that
we
can
refer
people
and
the
documentation
is
quite
thorough,
but
someone
new
coming
in
it's
like
here's
20
options
to
go,
install
it.
It
can
be
quite
daunting,
so
this
is
just
trying
to
get
people
an
easy
get
started
quick.
So
again,
if
you
want
to
take
that
one
on
that
could
be
a
nice
video
or
it
could
be
a
guide.
A
B
H
Can
hear
you
so
and
then
I
think
there
was
a
another
issue
going
back
talking
about
road
map
and
with
that
road
map.
H
I
didn't
want
to
have
that
mix
up
with
the
road
map
you
know,
and
so,
but
I
have
put
number
12
roadmap
in
there
for
everyone
to
chime
on
and
that
will
hopefully
construct
me
on
the
tutorial
so
I'm
in
sync,
with
what
everyone
thinks
are
the
right
layers
for
everyone
to
to.
You
know
begin
to
learn.
You
know.
Maybe
it's
vanilla,
kubernetes,
then
opinionated
kubernetes,
so
that
the
newbies
can
come
in
and
not
have
any
deficiencies
or
any
fear
of
where
to
go.
H
If
that
makes
any
sense,
so
I
just
shared
that
link
and
as
soon
as
I
can
get
back
into
GitHub
I'll
I
sent
you
the
link
where
you,
maybe
you
can
put
it
in
if
I
I'll
try
to
put
it
in
later,
but
you
can
at
least
chop
up
the
road
map
and
see
what's
good,
what's
bad
and
and
then
that
should
be
my
guide
for
our
tutorials,
which
is
what
I'm
trying
to
do.
B
B
I
I
think
we're
sort
of
covering
that
in
what
we
did
last
week
in
terms
of
what's
on
the
home
page,
so
I'll
review
that,
but
I
might
be
closing
number
eight
out
because
we
covered
it
in
the
the
new
home
page
number
19.
B
F
Now
one
thing
I'd
like
to
do
is:
let's
try
to
promote
the
heck
out
of
it,
because
I
I
think
we
can
get
some
interest
to
pull
people
into
the
okd
community
with
this
meeting
and
I've
been
sort
of
promoting
it
and
talking
about
it,
and
so
if
I
could
get
some
help
and
other
folks
sharing
in
your
social
networks
in
your
various
places,
I
think
that
would
be
really
good,
because
operators
and
the
new
catalog
is
a
way
to
get
a
lot
of
people.
A
B
Okay,
the
next
one
is
number
22.,
so
this
is
COC
with
the
okd
auction.
B
So
there
was
a
bug
on
this
that
I
haven't
checked
to
see
if
it's
fixed
I'm
just
looking
now
it
has
been
merged,
so
it
has
been
fixed,
but
there
was
a
request
that
we
should
take
this
on,
as
in
the
Orchid
East
Community
should
take
this
on.
We
should
be
responsible
for
keeping
the
CRC
release
up
to
date.
F
I
sent
a
message
to
that
group.
I
haven't
heard
anything
back
yet,
but
I'll
ping
him
again
voicing
our
interest
in
taking
that
on
and
asking
what
it
is
that
we
need
to
do
so
as
soon
as
I
hear
back
we'll
have
a
path
forward
on
that
for
sure.
B
Yeah
and
I
think
the
idea
here
would
be
to
add
it
to
the
pipeline.
So
when
we
create
a
new
release
of
okd,
we
automatically
do
whatever's
needed
the
bumps,
the
CRC
content
to
be
in
line
with
the
the
current
release.
So,
ideally
that
we
want
that
to
be
automated
as
part
of
our
our
pipeline
for
a
release.
But
again
we
don't
know
what
what
is
involved
in
the
CRC
release.
Yet
so,
what's
the
space
so
number
seven
again,
this
is
some.
B
This
is
documentation
that
we
need
to
get
to
it's
just
really
Define.
How
we're
going
to
manage
projects
in
our
GitHub
and
I.
Think
this
one's
quite
an
important
one,
because
the
last
meeting
we
talked
about
possibility
of
okd
becoming
an
upstream
to
ocp,
and
if
that
happens,
and
as
we
get
into
the
operator
content,
we
might
we'll
start
getting
more
and
more
contributions
into
our
git
organization.
So
I
think
it's
important
that
we
have
an
understanding
of
how
we
want
to
manage
that
as
a
small
community.
B
It's
pretty
much,
people
do
what
they
need
to
do,
but
as
we
grow
and
as
we're
going
to
start
releasing
more
content
from
our
git
repo
I
think
having
some
some
process,
some
sort
of
due
diligence
in
place
to
make
sure
hey,
we
can't
get
hacked
and
there
is
some
resilience
to
the
processes
we
employ
around
the
use
of
GitHub.
B
So
that's
what
number
seven
is
about
again,
that
might
be
a
good
topic
for,
and
one
of
these
Works
work
job
sessions
that
we
have
to
actually
get
an
agreed
process
for
that
24.
B
This
is
on
me
just
to
actually
put
out
the
results
of
the
last
work
group
into
a
proposal,
so
we
can
all
agree
or
disagree
onto
that.
In
a
similar
vein.
We
want
to
alter
the
the
template
of
the
home
page
to
add
in
a
banner
to
it,
so
we
can
actually
have
a
latest
news
section
and
make
it
easy
to
actually
update
that,
so
we
can
just
put
it
like
a
red
flash
or
a
colored
flash
along
the
top.
That
says
this
is
the
latest
news.
B
Things
like
the
operator
working
group
session
would
go
on
there.
New
releases
would
go
on
there.
If
there's
any
known
issues
that
might
cause
people
concerns,
we
could
put
things
on
there.
If
we're
going
to
a
conference,
we
can
just
splash
it
up
there.
Things
like
that.
B
Another
long-standing
111
I,
don't
think,
there's
been
any
progress
on
that.
Just
make
sure.
E
That
we
yeah
yeah
Brian
on
on
that
one
yeah
I've
been
obviously
because
I've
been
away
and
PTO
and
all
the
rest,
but
I
did
speak
to
Karina
I've
added
her
response
in
the
in
the
comments
there.
So
basically
she
she
did
say
keep
the
current
license
in
copyright
templates
as
you
have
in
okd
and
then
just
share
them
with
her
and
Diane,
but
Diane's
I,
suppose
and
they'll
review
it.
E
B
Okay,
I'll
I'll
do
that
one
yeah
17
the
survey
responses
we
actually
haven't
had
the
we
haven't
gone
over
those
yet,
but
I
also
know
that
Jamie
is
about
to
put
out
this
year's
survey,
and
so,
if
you
want
to
go
and
look
at
that,
there's
a
link
I've
seen
in
the
comments
I.
F
Still
have
to
add
the
one
question
that
you
suggested
at
the
last
meeting:
I
haven't
done
that
yet,
but
if
anyone
else
has
any
other
feedback,
let
me
know
pretty
much.
This
would
be
the
last
our
last
meeting
before
it
goes
out,
so
any
feedback
is
appreciated.
Otherwise,
I'm
just
going
to
send
it
out
with
that
additional
question
that
Brian
suggested
and
then
collect
the
results
in
a
a
new
spreadsheet.
So
we'll
have
like
a
new
spreadsheet
every
year.
Basically,.
B
Okay,
great
14
Define
a
diary
calendar
process
to
update
roadmaps,
guys,
glossaries
I,
don't
think
there's
a
there's
been
any
action
on
this,
but
the
idea
here
is
that
we
just
want
to
have
a
process
where
we
actually
have
a
published
calendar,
so
say
quarterly
we're
going
to
review
things
or
every
six
months
we're
going
to
review
things
just
so
we
actually
and
have
a
process
where
we
can
actually
do
regular
reviews.
B
So
we
just
need
to
move
that
one
on
at
some
point.
15
there's
been
no
action
on
the
volunteers
21..
We
still
don't
have
any.
B
Anyone
in
terms
of
handling
the
security
can
we
close
this
one
Jamie,
because
we've
now
got
a
mail
to
security
and
that's
just
going
to
go
to
the
the
people
that
have
access
to
the
to
the
email
account
is.
F
Of
noise
in
the
background,
yeah
I
think
we're
gonna
close
this
one
for
now,
I
think.
Ultimately,
it's
trying
to
search
for
someone
that
had
the
time
and
the
the
ability
to
volunteer
specifically
for
security
just
did
not
work
out.
So,
let's
close
that
one
right
now,
as
you
said,
the
email
goes
to
the
group
and
we'll
just
you
know:
if
an
opportunity
arises
where
we
get
someone
that
wants
to
take
on
security,
specific
stuff
great.
In
the
meantime,.
F
Things
are
looking
at
well,
so
the
goal
was
to
be
able
to
have
someone
sort
of
sealed
security
stuff
and
directed
to
the
appropriate
like
if
someone
had
found
a
security
issue
or
if
they
noticed
that
functionality
had
changed
because
of
a
security
issue
or
because
of
a
security
change
that
there
would
be
someone
in
the
okd
working
group
that
could
direct
any
questions
that
they
have
to
the
appropriate
resource.
F
If
it
was
third
party
like
if
it
was
F,
cost
related
direct,
their
requests
to
the
F
costs,
working
group,
submission
process
or
if
it's
something
related
to
Red,
Hat
to
Red,
Hat
security
team
and
basically
someone
being
a
you
know,
traffic
director,
because
there's
really
not
a
lot
of
stuff,
that's
specific
at
this
time,
that's
specific
to
okd
in
terms
of
security.
A
lot
of
it
is,
you
know
either
gonna
be
fpus,
or
it's
going
to
be
red
hat
ocp
stuff.
F
So
does
that
answer
your
question.
G
F
Anyway,
well,
the
idea
would
be
that
we
would
build
the
institutional
knowledge
once
we
got
someone
to
volunteer
time,
because
you
know
we
have
people
from
fkos
showing
up
at
the
meetings
we
have
obviously
Red
Hat
employees
showing
up
to
the
meetings
said
you
would
be
that
we
would,
you
know,
create
a
spreadsheet
or
you
know
a
you
know,
a
chart
that
says
okay.
If
it's
this
go,
it
goes
here.
If
it's
this,
it
goes
here.
We
just
haven't
done
it
yet,
because
we
haven't
had
anyone
volunteer
in
that
space.
F
We
can
yeah,
let's
we'll
set
yep,
then
I'm
gonna.
Take
you
up
on
your
offer.
Consider
you
a
volunteer
for
that
and
then
we
will
network
with
the
F
cost
folks
and
the
ocp
folks
cool
and
we'll
write
something
out
that
has
you
know
the
appropriate
places
to
put
information
in
regards
to
those
things
and
also
the
appropriate
place
to
check
right.
So
if
someone
comes
to
us
and
says
hey,
you
know,
there's
a
security
issue.
F
G
Thank
you
for
volunteering,
no
worries
and
the
in
the
case
of
videos
and
written
content.
It's
pretty
much
the
same,
like
I,
have
the
the
Cycles
to
help,
but
I
have
no
clue
of
like
how
to
run
a
web
app
and
database
in
AJ
on
okay,
the
like
so
but
I
would
be
totally
willing
to
write
that
or
record
that
video.
If
someone
would
help
with
the
actual
Wizardry.
B
Okay,
so
we're
moving
into
the
in
progress
column.
Almost
there
item
number
two
we've
talked
about:
that's
the
single
node
installer,
that's
actually
getting
it
to
work,
so
I
will
go
and
retest
all
of
that.
B
Updating
the
docs
just
being
clear
that
we
only
have
a
single
update
Channel,
unlike
ocp,
that
have
multiple
update
channels,
so
the
the
stable
the
fast
and
we
only
have
a
single.
So
we
just
need
to
make
sure
that's
reflected
in
the
documentation,
and
it
is
that's
so
that's
now
finished
is
it.
It
is
finished.
Yes,
brilliant.
F
Well,
we
have
you
on
the
horn.
Is
there
any
word
on
fixing
the
pull
down
for
latest.
B
B
B
Yeah
so
I
mean
we
got
a
comment,
but
we
need
to
actually
work
out
which
modules
within
the
support
group
need
to
be
removed,
updated
so
yeah.
We
probably
need
to
just
go
through
that
section
and
and
look
at
each
page
and
and
write
about
so
yeah
I
can
have
a
look
at
that
and
yeah
I.
Think
number
13
is
sorry.
B
B
H
Yeah,
and
and
also
in
that
link
in
the
road
map,
I
tried
to
go
out
and
do
future
things
like
zero
trust,
which
is
a
big
security
issue
and
in
the
U.S.
The
deadline
is
like
next
September
for
for
them
to
do
to
have
some
type
of
zero
trust.
But
that
raises
a
question:
will
okd
be
something
people
in
the
federal
government?
We
want.
H
Because
that
would
that
was
where
you
know:
that's
that
type
of
community
so
but
it
would
be,
you
know
we
have
all
these
people
that
would
love
to
train
in
it.
You
know
for
the
government,
so
that's
another
discussion.
B
B
We
should
probably
discuss
and
just
make
sure,
especially
if
we're
going
to
start
delivering
more
content
as
a
community
team
rather
than
from
the
ocp
build
process.
We
may
have
to
look
into
that
as
part
of
the
the
processes
around
how
we
as
a
community
are
going
to
work.
So
that's
that's
a
good
point
and
there.
B
And
then
three
eleven,
if
you're,
looking
to
document
everything,
but
the
current
one
is
marked.
Michael
has
done
that
for
us,
so
everything,
but
the
current
version
is
Mark.
You
are
viewing
documentation
for
a
release
that
is
no
longer
maintained,
so
that's
from
412
all
the
way
back
into
311.,
so
we've
got
them
fully
covered,
so
it's
only
the
413
and
the
latest
that
don't
have
that
Banner
so
that
one
is
closed,
and
that
is
everything
on
the
board.
So
we've
gone
through
the
entire
board.
B
Obviously
there
are
still
quite
a
lot
of
items
ready
for
someone
to
pick
it
pick
up
and
and
come
and
help
us.
So
if
you
have
any
spare
Cycles,
it
would
be
wonderful
if
we
could
close
off
a
few
more
cards.
B
Does
anybody
have
anything
else
they
want
to
add?
Are
there
any
new
issues
that
they
want
to
add
that
weren't
on
the
board
as
again
as
a
community
I
think
we
need
to
get
used
to
using
this
board
and
actually
use
it
for
everything
going
on
and
within
the
community?
So
don't
feel
that
you
need
permission
to
actually
go
and
add
something
into
the
new
column.
Just
go
create
it,
and
then
we
can
discuss
it
at
the
next
meeting
on
the
agenda
someone's
added
an
okay,
the
community
events.
G
B
G
G
F
G
F
Front
of
me,
but
I'm
pretty
sure,
that's
it.
One
thing
I
should
say
is
that
we
shouldn't
view
different
languages
as
or
I,
don't
think
as
an
impedance.
F
So
what
we're
doing,
because
there's
a
lot
of
users
and
a
lot
of
countries
that
you
know
their
native
language
is
what
they
work
in
still
I.
Don't
I
don't
want
us
to
feel
like
we're,
English
Centric
in
any
way.
D
F
B
Okay,
well,
thank
you
very
much
for
attending
this
next
week,
we'll
go
back
to
our
okd
working
group,
where
we
talk
about
the
engine
from
the
engineering
team,
about
the
project,
and
then
the
week
after,
unless
we
have
to
reschedule,
will
be
the
meeting
on
okd
the
operator
catalog.
So
that's
13th
of
June
and
just
wait
for
confirmation.
B
If
there's
going
to
be
a
lot
of
people
traveling
to
the
event,
we
might
push
it
back
a
week,
but
otherwise
we
will
be
talking
about
the
okay,
the
operator
catalog
next
community
meeting.
So
on
that
I
will
close
out
the
meeting.
H
B
Okay
yeah,
so
everybody
if
we
can
have
a
look
at
that,
the
link
is
in
is
in
the
card.
So
if
you
go
to
the
planning
board,
click
on
card
12,
it's
in
the
review
in
review
column
and
please
post
feedback
on
the
card
into
the
issue.