►
From YouTube: OKD Community Development Meeting 08-08-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
Welcome
folks
to
the
okd
Community
Development
meeting
for
August,
8th
of
the
Year
2023,
and
if
there's
anything
to
the
agenda
that
you
want
to
add
other
than
just
going
through
the
cards
and
talking
about
planning
board
stuff.
Let
me
know.
A
B
A
To
the
agenda,
let
me
know.
B
Otherwise,
we'll
just
go
through
the
various
things
that
we
have
in
the
planning
board.
B
B
So
going
to
the
planning
board
so
video
stuff-
let's
see
where
we're
at
here
a
lot
of
folks
have
been
on
vacation,
so
we
don't
actually
have
updates
to
many
of
these
ignition
and
butane
stuff
and
F
costs
with
Timothy.
B
C
Christian
has
been
I
think
last
the
week
last
week
was.
It
was
basically
art
and
I.
Think
this
week
he's
focused
on
getting
some
stuff
done
on
Moc,
with
the
layering
yeah
as
as
soon
as
that's
out
the
way,
I
think
we
get
started
on
the
escoster.
Yes,
I'm,
sorry
about
that!
Still
a
bit
yeah.
B
That's
right,
this
is
the
this
is
the
the
time
of
year
that
just
a
lot
of
people
are
sort
of
doing
other
stuff,
and
you
know
vacations
and.
B
Okay
and
so
I'll
I'll
take
the
next
three
ones.
I
would
assume
that
the
okd
on
F
cost
build
modifications
and
okd
as
cost
build
that
those
are
all
sort
of
in
waiting.
Is
that
right,
yeah,
okay,
great
yeah
yeah
and
we
do
not
have
yeah
okay,
so
we'll
installation
options
he's
not
here.
Let's
see
MCO,
we
haven't
really
tackled
that
one
yet
other
than
the
video
that
we
had
I
don't
know.
B
Did
folks
have
a
chance
to
look
at
that
video
yet
that
I
posted
that
was
the
Youtube
video
I.
Don't
know
if
folks
had
a
chance
to
check
that
out.
Yet
I
think
I
put
the
link.
A
D
Didn't
check
it
out
yet
I
did
ask
around
internally
to
see
if
I
could
find
someone
who
wanted
to
do
like
an
MCO
video
but
I
didn't
I
didn't
get
any
strong
bites.
There's
like
a
few
people.
I
know
who
might
be
good
for
it,
but
it
sounded
like
they
were
just
busy
to
the
point
where
they
couldn't
even
consider
like
doing
something
like
that.
You
know
unless,
unless
I
was
able
to
show
up
with
like
a
script
and
be
like
all
right.
A
D
It
right
so,
unfortunately,
I
haven't
been
able
to
find
someone
internally
who
would
like
who
like
wants
to
do
it?
Basically
so
I'm.
B
B
That's
not
okd
specific,
it's
it's
I
think
he
does
it
actually
on
ocp,
but
we
can
just
sort
of
run
with
that
for
now
and
then
he
offered
to
make
a
one.
That's
more
specific.
So,
let's
just
run
with
that.
He
offered
and
it's
it's
he's
great
at
making
videos
so
I'll
plug
in
for.
D
Right
yeah
so
like
baby
steps
from
my
side,
I've
I
had
to
reset
up
my
like
video
recording
here
so
I've
got
like
OBS
working
well
on
my
machine
now
and
I.
D
Think
I'm
good
to
like
make
the
videos
I've
also
been
trying
to
reorient
my
content
towards
a
15
minute,
like
we
talked
about
before
so
I'm,
like
mostly
through
what
I
consider
to
be
a
script
of
what
I'd
like
to
say:
I'm,
hoping
maybe
in
the
next
couple
weekends
I'll
get
a
chance
to
try
and
like
just
test
record
and
see
if
it
comes
out
the
way
I,
like
so
I,
don't
know.
D
Maybe
in
the
next
like
two
three
weeks,
I
could
have
something
to
share
with
you
Jamie
and
then
you
know,
then,
if
you
can
mix
it
up
or
whatever
or
put
some
bumpers
on
it
or
you
know
whatever
the
lingo
is
like
you
know,
yeah
that'd
be
awesome.
Yeah.
B
Yeah
and
then
actually
what
I'll
do
is
Bruce
is
not
here
this
weekend.
I,
don't
think
he
was
at
the
meeting
last
week
either
so
for
the
troubleshooting
Essentials,
let's
just
like,
maybe
share
out
a
hack,
MD
doc
and
start
throwing
ideas
in
of
like
where
we
would
start
the
three
of
us
and
I'll.
Let
Bruce
know
about
it
and
then
we'll
just
get
a
script
going
between
the
three
of
us
and
then
record
that
yeah.
D
B
Any
other
stuff
on
videos
so.
B
Okay-
and
we
do
have
the
comment
about
Hardware,
preparation
and
stuff,
like
that,
I
think
that
that
gets
into
like
a
whole
other
ball
of
wax
like
we
talked
about,
and
if
we
know
someone
that
wants
to
talk
about
Hardware
prep
or
that's
able
to
talk
about
Hardware
crap,
it
kind
of
varies.
You
know,
depending
on
what
you're
going
to
be
installing
and
whatnot.
E
B
E
Know
I
know
I
saw
Fedora
I
was
getting
ready
to
go
on.
What's
that
silicon
Apple
silicon
I'm
like
wow,
that's
a
serious
change
in
the
world.
B
B
All
right
moving
guides
to
blog
posts,
that's
Brian,
and
he
will
deal
with
that
when
he
gets
a
chance
creating
techton
on
an
okd
document.
I
haven't
Revisited
this
yet
because
I've
been
sort
of
focused
on
the
video
series.
B
Okay,
Dio
video
content,
yeah
that
sort
of
connects
into
that
video
series.
So
we'll
move
past
that
write
up
project
board
guidelines.
We
haven't
gotten
anyone
to
to
volunteer
for
that
one.
Yet,
basically,
that's
and
you
wrote
something:
yeah
go
ahead.
Man.
D
I
I
just
wanted
to
say
something
real,
quick
about
the
previous
card
that
okd.io
video
content.
Should
we
be
does
that
card
need
to
be
like
moved
it
like
joined
with
the
other
card
or
like
do
we
need
to
have
two
people
open
I
was
just
curious,
yeah.
D
D
B
B
Yeah
I
guess
we
could
throw
that
in
with
the
foundations
video
series,
so
I
could
do
this.
Do.
D
I
mean
if
you,
if
you
think
they
should
be
two
separate
cards
like
that's
totally
cool
I,
just
think
we
should
differentiate.
You
know.
F
B
A
D
Stuff,
yeah,
okay,
cool
yeah,
just
as
long
as
it's
clear
like
why
we
have
two
cards:
I
think
that's
awesome,
yeah!
So,
okay,
yeah
now
on
to
the
next
point
about
the
project
guidelines,
yeah.
A
B
B
D
Yeah,
so
I
was
just
trying
to
share
like
kind
of
my
thoughts
on
on
the
direction
I
thought
we
should
go
like
I
I,
honestly,
like
I,
can't
commit
to
like
writing
like
a
formal
version
of
this
like
I.
Just
don't
think
I'll
have
the
time
to
do
it,
but
like
I'm,
happy
to
participate
in
a
conversation
or
like
share
more
yeah.
D
This
was
kind
of
like
my
first
shot
at
like
I
I
thought
we
should
just
try
and
come
up
with
I
think
if
we're
going
to
operate
as
a
community,
and
we've
got
like
this
notion
of
like
okay,
we
would
like
the
community
to
have
certain
processes
and
rituals
around
how
we
get
our
work
done.
I
think
it's
probably
best
for
us
to
try
and
enshrine
some
of
those
things
in
a
document
where
we
can
say
all
right,
we're
the
okd
community.
This
is
how
we
host
meetings.
This
is
where
we
host
meetings.
D
If
you'd
like
to
interact
with
us.
This
is
how
the
project
organizes
itself.
You
know
just
to
help
providing
some
structure
because
in
my
mind-
and
maybe
this
is
like
optimistic
or
aspirational
or
whatever
but
I
look
at
like
all
the
great
work
the
Fedora
Community
has
done,
and
they've
really
built
like
a
strong
community
and
I.
D
Think
we're
seeing
that
now,
in
light
of,
like
some
things
coming
to
the
Fedora
community,
that
are
kind
of
shaking
the
community's
stability
right,
like
they're
they've
got
some
big
decisions
and
questions
that
are
open
that
are
causing
the
community
to
really
you
know,
engage
and
I
think
because
they
have
such
good
processes.
Their
Community
is
like
healthy
enough
to
withstand
that
and
like
succeed
through
it,
and
so
I
would
love
to
see
the
okd
community
kind
of
get
to
a
similar
place
where
it's
like.
D
We've
got
a
well-defined
way
that
we
kind
of
do
do
business
for
lack
of
a
better
metaphor,
and
that
makes
it
easier
than
for
people
outside
the
community
to
have
a
very
clear
understanding
of
like.
Oh,
like
you
know,
this
is
the
project
board.
I
can
go
look
here
and
understand
like
how
things
work,
and
you
know
this
is
how
they
like
to
you
know
triage
things
or
whatever,
so
that
was
kind
of
my
my
I
guess
impetus
here
for
for
writing
something
down.
B
I,
like
it
and
I
and
Roofing
on
it
I
when
I
look
at
like
number
one
Community
member
would
like
to
see
a
change
in
okd
or
the
community
I
view
the
the
Community
page
or
the
get
involved
page
could
be
broken
down
into
sections
with
just
do
you
want
to
get
involved
with
a
technical
suggestion?
Do
this?
Do
you
want
to
get
involved
with
the
community
process?
You
know
or
have
a
suggestion
for
Community
process
open
this
type
of
issue.
B
Like
we
tell
people,
you
can
open
an
issue
or
open
a
discussion,
but
we
don't
tell
them
which
item
to
select
or
point
out
that
there's
multiple
categories
to
select
and
stuff
like
that
it
would
be
nice
if
you
had
one
page
that
literally
just
breaks
this
down
for.
Would
you
like
to
get
involved
this
way
or
provide
feedback?
Then
this
way,
then,
or
for
this
type
of
thing,
then
do
this,
for
this
type
of
thing
then
do
this?
Is
that
sort
of
align
with
your
vision,
yeah.
D
D
B
Let's
actually
set
that
up,
then,
for
let's
tackle
this
at
the
next
meeting,
we'll
just
start
with
a
blank
document
and
just
have
us
Riff
on
what
we
think
the
section
should
be
the
different
ways
in
which
someone
can
get
involved,
and
then
after
that,
then
we
just
map
it
to
the
particular.
Is
it
an
issue?
Is
it
a
discussion?
If
it's
a
discussion,
this
particular
you
know
category
Etc,
okay,
that
sounds
good
for
for
next
meeting
just
to
get
this
on,
because
yeah.
E
Go
ahead,
yeah
in
in
that
process.
How
critical
do
you
think
it
is
for
a
newcomer
to
have
the
knowledge
of
apis
such
that
they
can
pinpoint
where
they
want
to
go
or
or
try
to
figure
out
how
one
API
works
with
another
API
in
case
they
want
to
use
a
certain
set
of
apis
to
work
with
operators
or
something
you
know,
but
if
they
don't
understand
any
of
the
basic
protocols-
and
that
seems
like
that.
That's
a
hard
thing
to
put
into
the
code
and
into
the
Linux
and
into
the
testing.
B
B
Yeah
I
feel
like
once
we
get
the
basic
Community
stuff
down
of
what
we
just
discussed.
B
That
page
that
we
just
discussed
then
have
a
a
sort
of
technical
launch
page
for
things
like
apis
operators
or
whatever,
like
one
thing
that
came
up
and
I'll
talk
about
this
in
a
second
is
that
at
the
last
working
group
meeting
last
week,
I
volunteered
myself
to
start
creating
a
operators
page
that
basically
links
to
the
working
group
meeting
or
sorry,
the
community
development
meeting
from
two
weeks
ago,
where
Shireen
and
Luigi
provided
a
really
awesome
overview
of
some
operator
stuff.
B
Plus
we
had
the
working
group
meeting
from
like
a
month
and
a
half
ago,
I
think
it
was
or
two
months
ago
where
you
know
we
had
a
great
overview
of
operators,
and
we
also
have
two
examples
of
operator
creation,
pipelines,
Brian's
and
the
one
that
Luigi
did,
and
so
my
thought
is
to
create
a
sort
of
a
landing
page
for
okd
operator
stuff.
So
people
know
where
we're
at
in
in
in,
and
everyone
can
sort
of
start
at
the
same
level
of
knowledge.
B
I
would
think
that
we
could
do
the
same
thing
with
apis
right
and
sort
of
sort
of
frame
it
in
a
landing
page
where
people
can
basically
find
out
about
the
apis
find
out
how
the
apis
factor
into
you
know
how
okd
Works
and
go
from
there.
So
yeah
I'll
make
a
good.
D
So
I
was
going
to
say
to
you
know
to
Dwayne's
point
like
I
think
what
you're
saying
makes
some
sense
to
me,
but
I
think
we're
to
begin
with.
We
need
to
look
at
even
like
a
higher
level
than
that
like
we
need
to
zoom
out
a
little
further
because
I
think
like
it
like
we.
If
someone
shows
up-
and
they
have
a
technical
based
question
around
like
apis
or
some
very
specific
part
like
this
operator.
Isn't
working
or
you
know,
machine
API
doesn't
work
or
something
like
that.
D
I
think
you're
right
like
yes,
people
would
have
to
have
a
certain
amount
of
knowledge
to
be
able
to
to,
like
you
know,
reliably
open
up
an
issue
or
something
there,
but
I
think
we
also
need
as
a
community.
We
need
to
look
at
a
little
bit
higher
level
for
even
people
who
maybe
aren't
that
technical,
yet
and
they're
coming
to
the
project.
D
And
it's
like:
oh
I,
you
know
I
noticed
a
problem
in
the
documentation
or
like
I'm
curious
about
this
story
about
usage
patterns
around
openshift,
so
like
I,
think
even
before
we
get
to
the
point
where,
where
we're
breaking
down
the
technical
topics,
I
think
there's
a
level
above
that
which
is
like
you
first
need
to
figure
out.
Is
this
person
trying
to
communicate
about
a
technical
topic,
or
do
they
actually
have
some
other
way
that
they'd
like
to
interact
with
the
community
and
so
I
think
to
what
Jamie
was
originally
talking
about?
D
E
Yeah
I
mean
that
sounds
fine.
I
guess
you
know,
there's
gonna,
be
people
going
at
different
speeds
and
getting
turned
around
and
then
to
rabbit
holes
anyway.
You
know
yeah.
D
Absolutely-
and
we
just
I
think
for
our
first
for
our
initial
swag
at
this.
We
just
need
to
make
sure
that
we
have
like
the
slow
lane,
the
medium
Lane,
the
fast
lane
and
the
passing
lane
or
whatever
you
know.
We
just
need
to
have
those
General
categories,
and
then
we
can
start
to
get
into
like
okay.
You
know
how
do
we
subdivide
them
or
something.
D
B
B
Okay
update
the
installing
openshift
on
a
single
node
instruction
in
the
end
user
docs.
We
don't
have
a
volunteer
yet
for
that
I've
not
dealt
with
any
Sno
stuff
and.
B
C
Yes,
sorry
with
that
one,
what
did
I
mean
updating
the
installing
openshift
on
a
single
node
instruction,
yeah.
B
So
the
the
there's
in
the
user
documentation,
there's
openshift
installing
openshift
on
a
single
node
and.
B
B
Dude,
so
do
you
want
me
to
to
add
you
as
the
assignee
on
that?
Yes,.
B
All
right
I
will
do
that
once
we
get
done
with
this
I'll
keep
going
here,
create
page
outline,
release
cycle
and
support
assistance.
I
haven't
done
that
yet
trying
to
get
through
some
of
the
video
stuff
just
so
we
can
get
more
volunteers,
but
this
would
be.
This
actually
aligns
I.
Think
with
the
project
board.
Guidelines
is
like
you
know,
just
outlining
the
release
cycle
and
support
and
assistance
stuff
and
that
sort
of
ties
into
the
community
stuff
and
where
do
people
go
and
what
can
they
expect
from
us?
B
I
think
that
that
all
sort
of
ties
together
and
I
I
feel
like
there's
a
I
feel
like
Vadim,
has
slowed
down
to
being
two
releases
a
month
for
the
F
cost
version.
B
Does
that
feel
right,
I,
don't
know
if
anyone
else
has
been
attuned
to
this
or
not,
but
it
seems
like
it's
like
two
a
month
now
so
I
think
maybe
I'm
going
to
ask
him
if
he
feels
like
he's
ready
to
do
something
to
say
it's
always
going
to
be
on
a
you
know,
on
a
Saturday
twice
a
month
or
something
like
something
where
we
can
at
least
give
people
a
sense
of
when
to
expect
it,
because
we
haven't
really
had
a
discussion
with
the
dean
recently
about
sort
of
an
expectation
of
a
release
and
when
we
might
expect
it
he's
just
been
sort
of
cutting
him
on
his
own
and
like
they
and
I,
see
that
they
pop
up
and
we
get
the
message
and
whatever.
B
But
there
hasn't.
There's
there.
Isn't
this
like
concerted
effort
to
like
okay
release
is
coming,
okay,
promote
it
type
thing,
and
so
I'd
like
to
to
get
a
conversation
going
with
them
about
that
and
I'll
reach
out
to
him
about
that.
Reviewing
the
survey
responses,
I'm
gonna
close
the
survey
this
week
and
then
we'll
look
at
the
responses
and
put
them
in
a
visual
format
and
bring
them
back
in
September.
B
So,
basically,
during
that
time,
off
I'm
going
to
massage
the
survey
results
into
something,
that's
visually
pleasing
for
us
to
look
at
and
then
in
September
have
that
ready
to
to
view
and
help
us
get
some
steps
forward.
B
The
tutorials
for
setting
up
okay
to
determine
if
we
have
good
good
options
for
for
people
from
okd.io
right.
So
that's
the
external
links
and
Dwayne
I,
don't
know
if
you've
had
a
chance
to
look
at
that
and
sort
of
narrow
down
external
links
that
you
think
are
are
valuable.
E
E
Okay,
I'll
I'll
try
to
have
something
before
the
Hiatus:
okay,
cool.
B
And
what
is
okd's
section
of
getting
started?
We've
got
a
couple.
People
have
volunteered,
but
any
any
I
think
we
might
as
well
pull
Diane
off
I.
Think
she's,
probably
not
she's,
not
really
involved
anymore.
So
my
my
inclination
is
to
just
pull
it
yeah.
A
B
And
Community
virtual
meeting
to
help
create
Community
catalog
of
operators
for
operator
Hub.
We
still
haven't
set
up
the
meeting
and
I
I
think
it's
good
that
we
have
done
all
of
the
foundational
work.
I
think
everyone
has
a
much
better
sense
of
operators
now
moving
forward
and
I.
Think
September
would
probably
be
a
good
time
to
set
up.
A
B
And
investigate
the
crcno
kitty
option
from
the
red
hat
team
and
that
I'm
gonna
pull
Diane
off
of
that
and.
B
Reach
out
to
the
CRC
folks
again
and
get
a
sense
of
if
they
have
everything
that
they
they
need
from
us.
B
A
B
B
D
A
D
Concrete
So
like
do
we
did
we
pick
like.
D
Maybe,
like
you
know,
to
get
this
to
the
next
stage.
If
we
really
want
to
get
more
Community
people
working
on
it.
Maybe
we
should
put
another
comment
in
this
card
and
say:
like
you
know,
we
decided
we
like
number
four
yeah,
the
here's.
What
the
code
kind
of
looks
like!
Could
someone
go
and
take
a
look
and
like
see
if
they
can
get
this
working?
Maybe
that
would
help
us
get
to
the
next
step
in
terms
of
helping
to
cast
this
wider
net.
You
know
yeah.
B
And
if
and
I
think,
we
did
decide
on
four
actually
in
in
conversation
that
that
was
that
was
the
one
but
yeah.
Let's
next
meeting
when
Brian
is
back,
let's
revisit
this
one
in
particular
and
see
if
we
can
narrow
that
down.
I
think
that's
a
great
idea
and
just
be
like
here's.
We
need
someone
to
do
these
five
things
to
get
us
to
what
this
image
represents.
You
know
what
I
mean:
I,
absolutely
I,
think
that's
perfect.
B
All
right
and
haven't
defined
a
diary
or
calendar
process
to
update
guides
and
glossers
and
stuff
I
I
feel
like
now
that
we've
gotten
the
survey
out
we're
starting
to
get
a
rhythm,
so
I'll
revisit
that.
As
time
permits
reach
out
to
volunteers,
I
have
been
reaching
out
to
volunteers.
We
get
a
couple
people,
but
then
people
sort
of
disappear.
B
A
little
bit
Amy
was
going
to
do
some
volunteering
and
I
didn't
see
her
I
think
she
like
called
in
the
last
meeting,
but
I,
don't
think
she
participated
much,
but
I
want
to
be
able
to
get
folks
like
that
to
to
leverage
them
to
leverage
their
time
on
even
some
small
things
and
stuff
like
that
to
find
the
process
to
create
a
doc
PR
and.
B
You
know
build
being
folks
being
able
to
to
build
the
website
and
view
these
changes.
Brian
was
going
to
look
I
want
to
when
Brian
comes
to
the
next
meeting.
I
want
to
ask
him
if
we're.
D
I
mean
I
think
you're
spot
on
Jamie,
like
we
like,
unfortunately,
the
because
of
the
way
the
docs
is
linked
to
like
the
red
hat
product
docs
and
everything
yeah.
It's
just
a
complex
procedure
to
to
kind
of
see
the
output
and
I
I
totally
get
what
you're
saying
like.
If
we
want
Community
contributors,
they
have
to
have
a
localized
way
to
just
say:
I
I
made
a
change.
I
hit
this
command
I
see
what
the
change
looks
like
now.
I
propose
the
pr
so
yeah
I
totally
agree
with
what
you're
saying.
B
D
B
So
that's
that
one's
that's
in
the
backlog
right
so
that
one
is
it
goes
and
but
yeah
that's
in
that
one's,
that's
the
one
in
backlog
right.
This
is
sort
of
rely
that
one
is
reliant
on
this
one
like
once
this
is
written
out,
then
we
can
update
the
well
it's.
We
would
pull,
probably
because
things
keep
well.
We
have
two
options
right.
B
You
know
what
I
mean,
because
that's
what
this
is
about,
creating
our
own
documentation
and
then
we
would
sort
of
use
that
knowledge
to
update
the
product
docs,
but
it
might
make
more
sense
to
just
pull
that
or
add
a
link
to
these
so
that
we're
not
reliant
on
having
to
anytime.
We
need
to
make
a
change
to
the
product
Docs.
B
You
know
every
time
we
want
need
to
make
a
change
about
single
node,
install
or
anything
with
assisted
installer.
We
have
to
go
and
go
through
the
whole
updating
the
product,
docs.
A
D
I
mean
this
is
gonna,
I
mean
this
is
going
to
bring
us
to
kind
of
a
larger.
Quite
in
my
mind,
at
least,
this
brings
us
to
a
larger
question
about
the
documentation
which
is
like
I
mean
I
totally
agree
with
what
you're
saying
here
in
terms
of
like
having
an
having
a
separate
page
that
we
can
maintain
on
our
own
will
be
a
lot
easier
in
terms
of
like
getting
reviews
done
and
getting
it
updated
and
everything
it
reduces.
D
The
burden
forever
is
doing
it,
but
it
also,
in
my
mind,
brings
us
back
to
a
question
about
like
how
we're
using
the
product
docs
as
like
our
source
to
begin
with,
and
and
do
we
as
a
community
at
some
point,
want
to
investigate
the
option
of
like
forking
those
Docs
and
having
some
sort
of
rebase
procedure
where
we
have.
D
We
have
some
commits
that
we
carry
that
customize
the
documentation,
the
way
we
like
to
and
we
frequently
rebase
from
the
Upstream,
so
that
we
always
have
fresh
information,
but
we
also
have
the
ability,
then
to
vary
the
documentation
like
how
we
want
to
so
like
you
know,
because
I
think
what
you're
kind
of
getting
at
is
like.
It
would
be
nice
if
we
just
had
a
way
to
carry
a
patch
on
top
of
it
and
say:
okay
yeah,
we
can
just.
We
can
modify
that.
How
we
want
to
you
know,
yeah.
B
B
B
Let's,
let's
I
need
to
reach
out
to
Brian
anyway,
but
let's
see
if
we
can
investigate
that
as
an
option.
Okay,
yeah.
D
D
You
know,
like
there's,
tooling,
that
my
like
my
team
inside
of
red
hat,
we
have
tooling
that,
like
automates
a
lot
of
these
rebases
and
syncing
external
repos,
you
know
because
we
do
a
lot
of
this
work
with
the
openshift
release,
as
it
is
right
like
we
replicate
things
from
Upstream.
You
know
like
the
kubernetes,
repo
and
stuff
like
that.
D
So
I
think
there
is
a
way
that
we
could
discuss
like
how
we
do
that
in
red
hat,
and
some
of
that
tooling
might
be
useful
to
this
community
because
it
might
show
us
a
really
easy
way
to
say
look.
We
can
have
an
automation
set
up
that,
like
once
or
twice
or
three
times
a
week.
Rebases
are
docs
from
the
Upstream
docs
and
then
applies
a
series
of
patches
on
top
of
it
that
we
carry
and
those
patches
would
allow
us
then
to
yeah.
Do
whatever
we
want
to
right
and
yeah.
D
B
B
This
is
in
the
product
docs
for
okd,
and
it's
not
right
or
is
this
right,
so
we
do
sort
of
get
community
feedback
and
and
Community
participation
up
to
that
point,
the
problem
is:
is
that
we've
had
to
again
have
them
open
a
ticket
with
Brian's
group
someone
there
has
to
address
it,
then
that
has
to
you
know
get
through.
It
would
be
much
faster
if
someone
says
that
to
us
and
we
immediately
go
Oh
yeah,
that's
not
right,
and
then
one
of
I
always
like
to
have
three
people.
B
It's
kind
of
like
like
SCD
right,
the
the
I
forget
the
name
for
the
theory
behind
having
three
Masters.
But
basically,
if
you
have
three
people
that
are
technically
knowledgeable
on
something
there'll
always
be
somebody
available
generally
to
go
and
do
that
that
change
right
and
if
we
could
do
that
for
the
docs
amongst
us.
That
would
be
fantastic
right.
A
A
B
All
right
and
then
Brian
investigating
the
blog
plug-in
and
then
remove
support
section
that
we
didn't
get
clarity
on
that,
because.
B
Yeah,
and-
and
this
goes
back
to
that
question
of
like
okay-
we
need
to
establish
which
modules
within
the
support
book
need
to
be
removed.
So
we
need
to
basically
maybe
at
the
next
meeting,
let's
look
over
the
docs,
we'll
spend
like
15
minutes
looking
over
the
docs
and
just
okay.
These
need
to
be
removed
from
the
support
section.
You
know
or
10
minutes
I.
Don't
even
think
it'll
take
that
long.
So,
but
I'll,
we
won't
do
that
today,
but
basically
we
need
to
just
open
up
the
product.
B
Docs
go
to
the
support
section
and
go
okay.
This
needs
to
get
pulled.
This
needs
to
get
pulled.
This
needs
to
get
pulled
because
there
is
some
stuff
in
there.
That's
useful,
like
I,
think
that's
where
the
chapter
on
must
gather
resides,
and
we
definitely
want
must
gather
right
so
I,
don't
think
we
would
pull
out
the
whole
thing.
I,
don't.
B
Yes,
we
would
basically
want
to
go
through
this
and
go
okay.
What
is
available
like
Telemetry
is
not
available.
Gathering
data
about
your
cluster
is
so
we
won't
do
it
at
this
meeting.
We
can
do
it
at
the
next
one,
but
you
know
if
folks
could,
between
now
and
the
next
meeting,
take
a
look
at
the
support
section
and
think
about
which
which
of
these
we
should
pull
out,
which
blocks
basically
with
text,
because
I
think
we
can
actually
do
it
at
the
at
the
at
the
the
section
level.
B
So
if
we
can
remove
it
at
the
section
level,
that
would
be
great
things
like
you
know
the
Insight
operator,
I
think
and
then
SOS
report
s,
but
you
can't
really
send
it
anywhere
like
you,
can
download
the
container
and
run
it,
but
it's
not
really
going
to
do
anything
for
you,
so,
okay,
something
for
us
to
look
at
at
the
next
meeting.
So
those
will
be
our
two
things
to
discuss
with
the
next
meeting.
B
Is
the
the
web
selecting
the
web
look
and
feel
that
we
want
for
the
front
page
and
and
narrowing
down
on
the
out
of
the
five
options
that
we
had
mocked
up
for
us
and
then
also
looking
at
the
docs
and
and
getting
the
support
stuff
cleared
away?
C
Yeah
one
next
week
we
have
a
public
holiday
in
Italy,
so
I
don't
think
Alex
and
myself
will
be
around
so
and
then
I
think.
We
said
from
the
week
after
we're
going
to
I
think.
What's
that
the
22nd
or
23rd
yeah.
B
Right,
yeah,
very
cool,
okay!
Well,
what's
the
holiday
by
the
way,
what.
C
F
C
B
Right
all
right
cool.
Well,
this
was
a
great
meeting
thanks
for
your
participation,
everyone,
and
for
those
of
you
that
we
won't
see
until
September
have
a
great
next
couple
weeks
and
enjoy
your
time
off
and
for
the
rest
of
you,
we'll
see
you
at
the
working
group
meeting
next
week.
All.