►
From YouTube: OKD Working Group - Docs Subgroup Meeting 08-10-2021
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 will also include the discussion of shared community goals for OKD 4 and beyond. Additionally, the Working Group will produce supporting materials and best practices for end-users and will provide guidance and coordination for CNCF projects working within the SIG's scope.
More info: https://okd.io
A
All
right
welcome
to
the
okd
working
group,
docs
sub
group
and
we're
gonna
jump
right
into
it.
We're
gonna
try
something
different.
Instead
of
doing
introductions
would
encourage
folks
to
look
at
the
meeting
notes
and
there
you
will
see
the
people
who
have
attended
the
meeting
and
their
affiliation
and
for
any
new
folks
that
are
here
will
give
you
a
chance
to
introduce
yourself
if
there's
anyone
new
nope,
no
one
knew
here.
So,
let's
jump
right
into
the
crux
of
the
biscuit
current
projects,
the
guide
transition.
B
So
I
fixed
up
the
pr
that
I
had
there.
I
took
out
the
references
to
openshift
and
changed
them
to
okd
and
also
put
a
note
in
the
readme
about
how
to
add
more
guides.
I
think
like
we're
at
mvp
status,
for
this
thing
like
if
we
were
ready
to
merge
it
before,
like
it's
probably
enough
of
a
baseline,
that
we
could
merge
it
now
and
at
least
people
will
know
how
to
add
more
things,
and
you
know
I
think
it's
it's
probably
tuned
up
as
much
as
we
want
for
just
an
initial
outlook.
C
And
you
know
what
I
did
today
today
I
broke
github,
I'm
blaming
all
of
github
going
to.
I
couldn't
add
an
issue
on
something
today
and
apparently
that
the
web
hooks
are
down
so
okay
I'll
merge
it.
I
think
you
can
still
emerge.
I
just
for
some
reason,
there's
certain
little
things
that
that
aren't
working
like
had
an
issue.
So
so
I
will.
I
will
merge
it
after
this
call,
as
soon
as
it
comes
back
to
life
and
and
send
out.
A
D
C
A
A
C
Well,
I
have
an
opinion
about
that.
I
think
there's
some
clarification
that
should
go
on
about
what
kinds
of
issues
we
would
vote
on
because
things
like
adding
the
guides
or
changing
the
okd
dot
io
website
don't
really
require
any
kind
of
major
voting,
just
consensus
in
my
humble
opinion,
but
if
and
when
we
wanted
to
say
fork,
okd
or
arm
like
scenario
something
out
there
right
or
to
make
sure
that
it
worked
well
on.
C
You
know
some
other
cloud
platform
and
that
I
think,
would
then
then
be
required
so
like
if
it
was
a
code
based
change,
and
I
don't
know
what
you
call
that
level
distinction
there,
but
that's
where
I
think
the
vote
would
have
to
come,
because
we
we
have.
We
have
conversations
where
we're
like
yeah,
it's
not
doing
this
and
we
need
it
to
support
that
and
you
know-
and
you
know
we've
heard
I
don't
want
to
call
neil
out,
but
I
will
neil
gamba
often
says
things
like
you
know.
C
Well,
fedor
is
going
this
way
and
you're
going
that
way.
So
I
think
some
clarify-
and
I
don't
know
what
off
the
top
of
my
head,
I
can't
think
of
a
suggestion,
but
something
that
is
documentation,
changes,
marketing
or
brand
awareness
changes.
Those
kinds
of
things
don't
require
just
consensus
and
informing
the
group
and
things
that
were
yeah.
Consensus
is
good
and
and
other
things
like
a
major
fork
or.
E
Most
of
the
people
that
are
active
and
want
would
want
to
have
a
say,
turn
up
to
the
meetings.
I
don't
think
from
my
understanding
that
we
have
a
large
population
of
interested
users
that
aren't
really
aren't
really
being
active
in
the
meetings.
So
I
I
would
say
a
statement
like
that
is
more
applicable
where
you
have
a
much
larger
community
and
it's
impractical
for
everybody
to
join
into
meetings
and
and
contribute
meetings,
because
it's
too
big.
C
C
Trust
me
that
entire
working
group
of
mailing
list
would
wake
up
really
quickly
and
want
to
say
in
it
so,
and
we
would
have
a
very
interesting
first
meeting
or
second
meeting
after
we
put
it
out
there
as
an
issue.
I
think
it's
always
surprises
me.
Who's
who's
actually
paying
attention
and
yeah.
So
that's
I
think,
but
for
the
smaller,
but
it
is
it's
totally
maturity.
We
haven't
hit
the
tipping
point
and
we
also
haven't
requested
any
major
changes
to
the
code
base.
E
And
I
think
the
other
thing
is,
then:
we
need
a
process
on
how
how
we
announce
the
votes
and
how
we
get
votes.
People's
votes
in
is
putting
it
in
the
meeting
in
the
hack
md.
Is
that
good
enough,
or
do
we
need
a
more
formal
process
of
these?
Are
the
areas
that
we're
requesting
people
to
vote
on?
So
I
think
the
charter.
A
C
C
A
All
right,
okay,
I'll,
give
a
stab
at
creating
some
clarification
on
the
different
types
so
by
the
next
docs
meeting.
I'll
have
something
and
folks
can
take
a
look
at
it
in
terms
of
like
delineations
of
what
is
votable
versus
what
is
just
non-votable
like
words
that
accurately
describe
it
something
like
process,
technical
and
then
the
other
thing
being
like
non-votable
would
be
like
cosmetic
or
documentation
or
something.
But
I
guess
I
don't
know
something
along
those
lines:
okay,
so
updates
to
the
okd
banner.
A
B
E
C
C
A
E
I
actually
think
it's
it's
more
to
do
with
the
documentation.
So
when
people
arrive
at
the
other
community,
they've
got
a
landing
site
and
there's
a
clear
and
vadim
was
very
clear.
We
didn't
use
the
web
support,
so
if
you
want
to
connect
with
other
community
members
to
help
to
ask
for
help
resolving
issues
and
go
here,
and
we
should
have
an
etiquette
guide,
I
think
where
we
just
lay
out
how
you
ask
for
help.
E
So
the
information
you
should
include
like
what
platform
you're
on
if
you're,
following
a
set
of
instructions,
put
the
link
there
and
any
error
messages
how
to
get
the
must
the
the
the
help
bundle
the
log
bundle
together.
We
should
just
put
little
things
like
that
and
in,
but
that's
very,
very
much
about
community
member
to
community
member
to
resolve
issues,
and
then
we
should
have
another
group
if
you
want
to
become
involved,
whether
we
call
it
the
working
in
the
working
group
or
the
steering
committee
or,
however,
you
want
to
word
it.
E
We
have
a
separate
section
and
then
it
talks
about
the
process
of
how
we
meet
where
the
minute
meetings
are,
how
you
can
raise
a
question,
how
we
track
issues
and
work
in
progress.
So
it's
very
clear.
This
is
where
community
members
ask
for
help.
This
is
where
community
members
come,
who
want
to
contribute,
and
it
it's
very
clearly
documented,
and
it
means
that
if
somebody
wants
to
join
in,
they
don't
feel
the
am
I
doing
this
in
the
right
place.
E
I'm
am
I
doing
this
right,
because
that
was
my
first,
the
first
time
you
put
something
somewhere.
It's
like
I'm
just
trying
to
work
out
what
everyone
else
is
doing
and
hopefully
doing
the
right
thing
without
getting
the
hate
mail
from
communities,
as
you
often
do
if
you've
got
it
wrong.
So
it's
getting
that.
A
A
A
A
Would
it
be
good
to
have
a
link
here
to
how
to
ask
questions
or
I
th,
can
you
can
you
pin
discussion
items?
I
don't
know
if
those
can
be
pinned
or
not
by
the
repo
owners?
Oh
here's!
What's
what's
contributing
go
to?
Oh
okay?
Here
we
go
so
we
could
have
whoever
has
right
access
over
this
repo
vadim
or
whoever
put
a
how
to
ask
questions
under
helpful
resources.
Does
that
make
sense
yeah,
because.
A
Linking
we're
going
to
change
things
so
that
community
goes
right.
I
think
we're
going
to
change
things
so
that
community
goes
to
this
discussions
page
and
then
folks
could
have
links
down
here
and
then,
when
they
go
to
new
discussion,
there
could
be
under
helpful
resources
like
how
to
ask
questions
or
something
like
that.
E
Again,
what's
the
use
of
the
various
classifications
within
the
discussion,
because
you
can
sort
of
classify
what
what
are
you
asking?
Is
it
a
general?
Is
it
an
idea?
Is
it
a
question?
Is
there's
a
go
and
tell
so
again
we
can.
We
can
help
people
sort
of
be
more
direct
in
terms
of,
as
you
say,
this
is
how
you
ask
a
question.
A
Yeah
and
isn't
there
a
isn't
there
like
default
for
each
category,
can't
you
do
like
a
can't.
You
modify
this
to
actually
have
a
template.
I
believe
you
can
you
can
right.
So
why
don't
we
come
up
with
templates
for
each
of
those
categories
that
fill
it
in
and
so
for
q,
a
for
example
when
folks
select
that
the
text
would
be
something
like
here's
the
best
way
to
ask
a
question
or
for
a
ideas.
Here's
the
best
way
to
you
know:
that's
a
brian!
E
E
Yeah,
if
it
works,
I'm
not
that
familiar
with
discussions.
I
know
it's
peter.
I
haven't
really
got
that
done,
that
deep
with
them
yet
so
and
yeah.
That
would
work,
but
also,
I
think,
back
on
okidi.io
just
have
a
page
where
we
just
sort
of
lay
it
out.
So
if
people
are
being
sort
of
anti-social,
we've
got
somewhere
to
post
them
to
where
we
sort
of
say
these
are
the
rules.
Please
follow
them.
E
C
And
we
have
an
and
this-
and
I
would
say
this
is
one
thing
that
we
have
a
failing
at
red
hat
with
our
projects.
Is
we
don't
have
a
unif,
unified
code
of
contact
template
that
we
can
use
on
projects?
I
haven't
seen
one
el
mico
recently
and
the
last
time
I
asked
legal
for
something
I
got
some
pushback
of
on
that,
because
one
of
the
issues
we
have
is
like,
if
you
put
something
like
that
in
place,
is
what
I
was
heard
and
I'll
go
back
to
the
well
again.
C
But
you
need
to
have
a
process
or
dealing
with
it
and
people
willing
to
deal
with.
You
know
the
you
know
reaching
out
and
talking
to
people
and
all
of
that,
and
I
don't
think
we
have
and
I'll
ask
deb
bryant
in
the
osbo
team
again
what
the
and
that
was
about
a
year
or
a
year
and
a
half
ago
that
I
have.
C
C
And
not
a
cncf
project
like
kubernetes,
or
something
like
that.
I
normally
what
I
do,
especially
when
I
host
events
that
are
co-located
with
cncf.
I
just
put
in
a
link
that
we
follow
the
code
of
conduct
for
cncf
because
we're
co-located
with
their
events,
so
that
covers
my
events,
pretty
much
all
the
time,
because
then,
because
I'm
on
their
premise
and
using
their
facilities
and
stuff
so
yeah,
it's
it's
something
mike
that
that
we
need
to.
We
need
to
figure
out
it
may
in
the
year
and
a.
C
So
let
me
take
a
look
at
that
and
mike
maybe
I'll
rope
you
into
that
too,
as
the
other
red
hatter
on
this
call
to
see
if
we
can
find
a
good
example
of
an
existing
red
hat
sponsored
project,
because
if
you
look
at
the
bottom
of
the
okd
page,
it's
got
a
little
bit
of
a
footer
around
red
hat.
So
it's
yeah.
B
Yeah
a
little
bit
of
inside
baseball
here,
it's
like
yeah
when
you
look
at
the
red
hat,
open
source
communities
like
in
a
lot
of
cases,
we
are
participating
in
communities
that
are
either
have
their
own
foundation
or
they
have
their
own
community
infrastructure
and
okd
just
happens
to
be
one
of
the
projects
that
we
host
so
yeah.
I
mean
I
totally
echo
everything
diane's
saying
it's.
It's
a
little
bit
of
a
weird
place
inside
red
hat.
B
B
C
Trust
me:
I've
been
thinking
about
it,
a
lot
like
because
and
and
I
and
jamie
and
I
were
chatting
earlier.
I
just
ran
into
some
folks
from
brazil
who
are
hosting
okd
at
sao
paulo
university,
and
they
have
a
beautiful
cloud
that
they
use
and
the
ui
and
the
inter
interactions
are
just
amazing
and
I
would
love
to
see
a
hosted
okd
somewhere,
even
if
it
was
a
test
environment
for
us
to
use
and
and
as
a
playground.
B
I
know
have
you
been
talking
with
marcel
at
all
sorry
to
take
this
in
a
completely
different
direction,
but,
like
I've
had
some
discussions
internally
recently
with
like
marcel
hill
and
emilia
and
machi
about
like
the
operate
first
effort
and
how
we
can
reach
out
to
the
okd
community
as
having
a
public
cloud
that
we
could
do
that
kind
of
work
on.
So
I
think
there's
a
lot
of
talk
happening
about
this.
C
Yeah
and-
and
we
have-
and
that
and
the
other
reason
I
think
we
have
a
big
planning
meeting
coming
up
for
the
with
under
stephanie
cheers
group
that
I've
been
bringing
I'm
bringing
it
up
again
that
you
know
it
is
if
they
want
us
to
do
the
testing
of
the
edge
cases
for
cloud
deployments
and
which
is
one
of
you
know.
The
value
propositions
for
having
an
open
source
thing
is
that
they
get
all
this
feedback
from
things
that
we
can't
resource
the
hosting.
C
A
A
All
right:
well,
let's,
let's
leave
it
where
it
is
because
things
might
become
a
little
bit
clearer
once
el
mico
gets
that
last
bug
fixed
and
that's
merged
in
and
the
web
new
website
stuff
is
rolled
out,
and
then
we
can
look
at
the
front
page
and
the
various
other
pages
and
bryant.
You
have
a
lot
of
input
and
I
want
to
make
sure
that
we
go
through
that
list
again
and
make
sure
we've
covered
everything
in
the
near
future.
A
The
next
thing
I
wanted
to
do
is
go
through
the
the
read
me
and
then
it
so
and
this
sort
of
factors
into
the
install
thing.
A
lot
of
people
have
commented
that
the
readme
seems
to
be
like
every
single
possible
idea
about
okd,
and
it's
really
problematic
do
folks
share
that
I
have
that
opinion
brian.
I
know
you
voiced
some
concern
about
it.
Anyone
else
have
a
sense
about
the
readme
being
overloaded
a
little
bit.
E
I
o
and
there's
information
in
here
about
doing,
install,
there's
an
install
section
on
the
I'm
going
to
get
installer
section.
Okay,
I
o,
so
there
just
seems
to
be
a
lot
of
overlap,
and
I
I
just
think
some
clarity.
What
should
be
in
here
versus
what
should
be
on
okay,
I
o
and
let's,
let's
get
some
some
sort
of
uniform.
E
A
B
D
B
A
A
E
I'm
gonna
say:
should
this
not
just
be
a
go
to
okd.io
readme
and
then
everything
else
is
in
in
the
documentation
site,
or
is
this
going
to
be
more
documentation
for
the
working
group?
Do
we
do
it
that
way,
so
this
becomes
the
the
repo
is
more
about
how
you
compile
okay
d
or
how
you
can
probably
install
it
and
put
that
sort
of
stuff
in
here
and
put
the
end
user
community
on
okd
or
io.
E
E
I
I
I
mean,
I
think
we
need
to
change
the
underlying
technology
so
that
it
becomes
easy
to
add
things
there
and
and
then
that
should
become
our
single
shopping
point
and
working
group
members
should
be
encouraged
to
contribute
and
add
stuff
there.
So
that
becomes
the
one
point
anything
you
want.
You
should
start
by
punching
them
at
okdioc.io
and
then
that
should
give
them
all
the
information
and
all
links
off
to
other
places.
F
D
F
A
Are
we
suggesting
then
yeah,
I
agree
bruce
should
are
we
suggesting
then
that
right
here,
where
it's,
where
the
getting
started
starts
that
we
actually
just
cut
it
and
have
like
like
okay?
We
just
have
this
paragraph
and
then
it
just
says
for
details
about
installation
and
contributing
and
blah
blah
and
the
working
group
go
to
okd.io,
and
just
all
of
this
gets
subsumed
into
the
pages
that
we're
creating
off
of
okd.io
and
just
over
time,
move
this
over
to
okd.io
pages
like
over
the
next
couple
months.
A
E
C
I
think
that
means
yeah.
I
mean
yeah
much
much
better
if
it
was
yeah
if
we
switched
the
technology
and
it
was
more
community
updates,
driven
as
opposed
to
diane
and
yaml-
and
you
know
occasionally
a
community
member
who
hacks
through
it
and
tells
me
that
everything's
out
of
date
yeah,
I
would
much
I
if
we
can
get
the
resources
and
people's
brain
trust
working
on
moving
it
over
to,
as
brian
suggests.
B
I'll
be
in
all
the
instructions
on
this
like
in
this,
read
me
about
like
how
to
manipulate
images
and
how
to
extract
things
and
do
installation
like.
I
don't
think
we
want
any
of
that
here.
We
want
to.
We
want
people
to
go
into
docs.okd.io
if
they're
going
to
like,
if
you're
going
to
do
an
installation
go
to
the
official
docs.
Don't
like
you
know
like
what's
here,
I
have
a
feeling
people
are
coming
here
and
trying
to
do
this.
B
D
B
C
We
do
that
I'd
like
to
circle
back,
I
put
a
link
in
the
chat
to
the
ansible
groups,
code
of
conduct
which,
to
me
work
reads
really
nicely
and
I
would
be
happy
to
lift
and
shift
that
over
to
somewhere
and
and
and
brad
and
michael
burke
is
on
here.
Is
that
something
we
can
slide
in
like
if
I
make
an
edited
version
of
that
for
us
into
the
to
docs?
G
C
Yeah,
because
what
my
my
whole
thing
was,
I
I
mean
ask
forgiveness
later:
if
someone
else
that
red
hat
on
another
red
hat
project
has
gotten
a
code
of
conduct
reviewed
by
legal
then
and
into
their
docs,
then
it
would
just
all
always
live
there.
We
can
point
to
that
from
wherever
from
okd
dot
io
from
in
github
in
the
in
the
contributing
documentation
and
if
it,
if
legal,
deemed
that
we
needed
to
change
it,
we
could
just
change
it
as
part
of
the
docs
itself.
C
F
I
had
a
quick
look
at
that
and
it
looks
pretty
good.
The
only
thing
that
stood
out
for
me
is
the
word
offensive,
because
these
days
people
get
offended
by
anything
and
everything
and
it's
very
hard
to
adjudicate
yeah.
So
but
the
you
know
so
and
then
I
guess
the
secondary
issue
would
be
okay,
so
who
decides.
C
C
E
Is
okay,
so
this
is
actually
a
site,
that's
based
on
mk
docs,
which
is
a
static
site
generator
and
based
of
markdown,
which
uses
the
python
standard,
markdown
library,
and
so
what
I've
done
is
I've
just
taken
some
of
the
content?
That's
on
there
and
just
played
with
it
for
the
front
page
I
more
or
less
copied
exactly
what's
on
the
current
site,
but
you'll
notice,
the
header
and
the
footer
is
different.
E
Unfortunately,
there
is
some
clash
of
css,
because
the
mk
docs
css
and
the
bootstrap
css
that
the
front
page
they
use
some
of
the
same
and
some
of
the
same
attributes.
So
it's
not
perfect,
but
what
mk
docs
does
is
it
does
give
you
the
ability
to
to
customize
things.
So
this
is
just
a
demonstration
of
how
you
could
customize
a
page
if
you
wanted
it
to
look
different
and
but
what
you
get
along
the
top.
Is
you
get
your
navigation
and
again,
you've
got
a
lot
of
choice
here.
E
E
E
E
E
That
this
is
based
on,
so
you
can
see
that
it's
all
based
on
github
actions
in
the
github.github
folder
and
if
you
push
to
the
main
branch
and
you've
got
an
action
here
that
will
actually
build
and
republish
to
get
your
pages.
This
is
host
on
github
pages,
so
this
will
automatically
build
along
with
the
build.
It
does
a
spell
check
on
the
link
checker.
So
if
you've
got
broken,
spelling
or
broken
links
in
there,
it
won't
publish
it.
E
The
git
of
action
will
fail,
but
that'll
go
there
and
then,
if
you
look
at
any
of
the
pages,
you'll
see
that
they're
all
just
pure
markdown,
so
in
the
dock
section
is
where
all
the
content
is.
So
there
you
you've
got
the
pure
markdown.
If
you
go
into
the
blog
section,
that
shows
you
one
of
the
yeah
go
into
the
yeah.
E
So
if
you
just
look
at
raw
there,
you'll
see
that
this
has
got
one
of
the
extensions
it
just
uses
the
table
and
you've
got
just
the
table
as
pure
markdown.
Just
using
the
you've
also
see
at
the
top.
There
we've
actually
added
some
spelling
where
there's
some
words
that
weren't
in
the
standard
dictionary,
I
think,
just
put
a
comment
in
to
actually
add
words
that
aren't
in
the
standard
dictionary
so
and
other
than
that
it's
it's
sort
of
fairly
standard
markdown.
E
E
So
anybody
can
get
up
to
speed
as
long
as
you
know,
standard
markdown,
I
don't
get
up
to
speed
and
create
content
very
very
easily
whether
we
want
to
put
a
pipeline
in
and
build
it
within
a
red
hat
sort
of
infrastructure
or
whether
we
just
want
to
leave
it
to
github
actions
and
pages.
I
guess
we've
got
to
change
the
the
footer
because
it
says
power
by
red
open
shift
online.
E
I
did
sort
of
raise
a
lot
of
issues
in
terms
of
the
styling
because
we
can
style
this
anywhere.
We
want
in
terms
of
what.
How
do
we
want
to
style
it?
What
should
the
front
page
be?
What
color
schemes
do
we
want?
I
just
picked
the
colors
from
the
current
top
header
section
on
the
current
site,
but
we
may
not
want
those
colors
so
that
there's
a
whole
and
actually,
if
I
actually
put
it
within
the
site,
didn't
I.
E
And
then
the
okdiyo
review
yeah.
This
is
the
content.
I
actually
put
it
on
the
site.
So
just
little
things
about
the
project
landing
page,
the
actual
styling
we
want
and
then
obviously
we've
got
to
think
about
how
how
we
want
to
organize
it.
What
do
the
top
level
menus
be,
and
how
do
you
want
the
content
to
look
and
where
we
want
to
go
from
it
and
again?
This
shows
then
you've
got
the
high
level
navigation
for
community
on
the
left
and
then
the
table
of
content
or
this
page
on
the
right.
E
So
I
think
this
is
a
good
technology.
I've
been
using
it
for
a
few
years
now
in
a
couple
of
projects-
and
I
know
there's
somebody
on
the
king
k
native
project.
They
have
a
similar
problem
where
their
current
technology,
you
need
sort
of
a
master's
degree
to
actually
understand
how
to
write
a
simple
page
so
they're
looking
at
the
same
technology
for
k
native
and
there's
a
couple
of
projects
in
ibm
that
I've
put
onto
this-
and
it
just
seems
a
reasonable-
a
reasonably
stable,
easy
to
use
technology.
B
B
E
B
E
C
E
Yeah
I
mean
there
are
quite
a
lot
of
questions
about
styling
because
I
said
I
just
did
this
very
quickly
within
sort
of
a
couple
of
hours,
so
the
front
page
needs
to
change
quite
quite
drastically.
I
think
it
needs
to
be
simplified
and
made
easier
to
navigate
there's
a
lot
of
sort
of
bootstrap
in
there.
C
A
I
I
think
one
of
the
things
in
pulling
someone
in
is
that
they,
because
they're
not
familiar
with
the
history
and
sort
of
the
discussions
there
might
be
some
hand-holding
at
the
beginning
to
get
them
sort
of
aware
of
where
we
want
to
go
and
whatnot,
particularly
because
theoretically,
we'll
be
editing
and
cleaning
things
up
as
we
move
it
over
right.
That's
a
process
of
you
know,
cleaning
up
the
pages
and
jettisoning
some
things
and
adding
other
things
I
can
ask
around
for
sure
yeah.
C
Yeah,
I'm
just
trying
to
think
of
you
know
yeah.
I
know
all
of
us
have
workloads
mostly.
What
I
usually
do
in
stuff
is
lift
and
shift,
as
is
which
is
not
quite
what
I
hear
everybody
wanting
to
do,
I'd
like
to
make
sure
there's
a
home
for
everything
that
exists
right
now
on
okd.io
and
then
cut
over
and
then
keep
clean
clean
up
from
there.
So
you
know
we
don't
lose
anything.
F
E
E
We
get
it
working
and
when
we're
happy
it's
live
and
then
we
can
just
switch
it
over
and
we
can
just
do
the
push
into
the
the
okay
I
o
site.
So
it's
probably
easier
as
just
having
a
working
beta
that
we
can
build
on.
Let
people
contribute
to
without
necessarily
maybe
having
to
do
the
full
pull
pull
request
as
as
sort
of
official,
as
we
do
just
a
bit
bit
of
a
looser
project
to
move
it
quickly.
E
A
A
D
D
C
A
Well,
we've
got
seven
minutes.
I
do
want
to
get
through
everything
else.
So,
let's,
let's
get
up
to
that
point
of
getting
that
diane,
give
brian
access
brian
go
ahead,
create
the
branch
and
then
we'll
take
it
from
there
in
communication
offline.
I
do
want
to
get
in
the
meeting
to
the
we
have
like
three
more
things
to
get
through
so
inclusive
language
update.
I
have
a
quick
one
on
that.
Actually
well
brian
go
ahead
and
give
us
an
update
as
to
where
you
are
and
I'll
throw.
E
This
nothing's
really
changed
since
last
time.
I
did
the
all
the
scans
and
I
created
the
pull
request
with
all
of
the
issues
that
come
out,
I
mean
most
of
them
were
were
just
in
the
sort
of
comments
of
code
there
weren't
too
many
issues
on
the
site,
so
yeah
the
main
one,
obviously
is
the
branch
name
master
going
to
maine,
and
then
there
was
just
a
couple
of
other
for
the
typos,
but
I'm
guessing.
If
we're
going
to
change
the
technology,
we
can
fix
that
as
we
migrate.
The
technology.
A
C
A
C
That
I
get
that,
so
what
do
I
want
to?
Do
we're
no
longer
using
the
agenda?
That's
there
for
for
meetings,
so
I
don't
have
a
real,
strong
opinion
about
what
we
do
with
that.
I
think
there
should
be
because
it
exists
there.
There
should
be
a
a
landing
page
of
some
ilk
there
that
gets
people
to
the
okd
working
group
and
and
otherwise,
and
but
I
don't
have
a
strong
opinion
to
be.
C
A
A
Do
we
want
to
use
part
of
okd.io
as
the
working
group
like
meeting
notes
and
membership,
and
we
should
cares
and
all
that
stuff?
Does
that
make
sense?
Yeah
we
should
is.
Is
there
any
issue
with
a
separate
folder,
brian
being
non-website
stuff
or
things
that
get
rendered
differently,
or
maybe
don't
get
rendered.
E
A
E
A
E
A
C
A
A
G
D
E
E
H
B
No,
it's
not.
I
mean
if
you're
talking
about
upi
installations,
you
know
you
you
can
install
it
on
whatever
kind
of
like
bare
metal
infrastructure
you
want
to.
But
if
you're
talking
about
like
cloud
integration
with
oracle
cloud,
I
don't
think
it's
coming
anytime
soon.
I
haven't
it's
not
slated
on
our
next
few
releases
and
when
I
say
that
I
mean
like
there
wouldn't
there's
no
machine
api
provider
for
oracle
cloud.
H
Okay
cool.
I
actually
asked
that
because
they've
got
apparently
arm
based
processors
and
they
actually
have
a
lot
of
it.
I
don't
know
how,
so
that
would
be
a
good
playground,
testing
for
deployments
and
stuff,
and
there
is
a
problem
with
they
don't
give
you
access
to
the
machine
directly,
so
I
don't
know
for
upi
installation.
A
Let's
see
yeah,
let's
talk
about
that
actually
in
the
main
meeting,
because
there'll
be
more
engineers
on
in
the
main
meet
to
talk
about
that.
So
we'll
talk
about
that
next
tuesday
in
the
in
the
main
meeting
with
the
larger
group,
because
vadim
will
be
there.
Christian
will
be
there
and
they'll
be
able
to
chime
in
on
some
of
these
things.
I'm
sure
okay,
cool.