►
From YouTube: OKD Working Group 2021 06 01 Doc Meeting Recording
Description
OKD Working Group 2021 06 01 Doc Meeting Recording
A
Absolutely
all
right
folks,
well
well,
diane
does
her
thing.
What
I
wanted
to
do
is
bounce
back
over
to
this
discussion,
which
is
the
item
about
community
support.
So
we
need
to
come
up
with
some
language
and
I'm
assuming
the
docs
folks
would
be
the
ones
most
appropriate
for
that,
at
least
to
have
a
template
or
something
that
we
can
bring
the
larger
group.
So
we
could
put
it
in
actually
in
the
discussion
here
and
modify
it
or
we
could
do
it
as
something
in
github,
as
just
a
document
in
github.
A
A
He
got
another
email
a
couple
days
ago
from
someone
directly
asking
for
support,
and
so
what
we
want
to
do
is
make
it
clear-
and
this
also
has
the
benefit
of
sort
of
inspiring
folks
to
become
a
part
of
the
community,
because
they
can
see
that
that
they
can
help
others
and
they
can
see
a
way
in
which
to
participate
through
helping
others
and
answering
questions
and
whatnot.
So
what
do
you
think?
B
Actually,
I
have
a
question
on
how
could
it
not
be
clear,
like
I
think
the
support
model
is
the
same
like
going
back
to
slackware,
which
is
you
know
like
where
I
started
pre
kernel
1.0,
you
know
with
any
open
source
project
the
that
had
companies
attached
to
it.
The
sport
model
was
always
that
the
companies
weren't
there
you
wanted
support
you
bought
it
if
you're
going
with
open
source,
you
supported
yourself
and
you
could
ask
questions
and
people
might
help
you,
depending
on
how
friendly
the
community
was.
A
B
A
Would
you
exactly
generally
bring
it
to
their
attention
right
and
that's
what
this
can
do
also
is?
Is
it
it's?
It's
gets
ahead
of
things,
but
it
also
allows
us
to
point
to
something
for
the
people
that
choose
to
reach
out
directly
or
choose
to
somehow,
because
it's
also
going
to
clarify
time.
That's
everything
I
should
mention
is
this
would
also
say
that
you
know,
as
I've
posted
in
the
channel
to
folks
before,
is
that
this
is
as
available
as
people
in
the
community
have
time
available
right.
A
So
this
is
something
that
we
can
point
to
after
the
fact
as
well.
So
if
someone
mistakenly,
let's
say
mistakenly,
thinks
that
it
should
be
vadim
or
other
red
hat
employees
or
mistakenly
thinks
that
that
they
have
to
be
responded
to
at
that
moment,
then
we
have
something
to
point
to
and
say
well
here's
this
statement
of
our
and
it's
only
a
couple
sentences,
but
a
very
concise
couple
sentences
that
lays
this
out
my
thoughts,
I
don't
know
anything.
C
You
know
yeah,
like
I
would
like
there
to
be
a
place
where
we
could
direct
people,
and
maybe
there's
also
a
behavior
pattern
that
we
need
to
accept
as
well,
which
is
like
you
know,
for
someone
like
like
a
vadim
who's,
getting
a
lot
of
bandwidth
on
this.
There
needs
to
be
an
easy
way
for
him
just
to
push
a
button
and
redirect
that
person
to
you
know
input.
Your
question
here
create
an
issue.
Do
something
but
like
yeah
vadim
is
not
your
personal
enterprise,
open
source
consultant
that
you
can
just
email
anytime.
A
So
it
might
be
that
we
have
a
paragraph
blurb
and
then
a
page,
that's
literally
like
the
three
things
for
support
and
there's
nothing
else
on
it.
The
email
list,
the
channel
and
putting
an
issue
in
right
like
those
would
be
the
three
ways
in
which
someone
can
get
support
so
literally
just
a
community
support
page
right
and
then
we
have
a
paragraph
and
then
that
paragraph
of
three
sentences
just
contains
a
link
to
the
community
support
page
and
that's
making
that
clear.
You
know.
C
Yeah,
I
think
we
have
to
have
a
link
to
the
issues
form
like
right
there
because,
like,
if
someone's
gotten
to
the
point,
yeah,
hey
and
hey-
welcome
michael,
like,
if
someone's
gotten
to
the
point
where
they're
already
writing
an
email
to
vadim,
like
that
person
needs
to
like
control,
z
on
that
email
or
like
control
c
and
control
p,
all
that
stuff
into
the
form
for
an
issue.
Instead,
you
know
it's
like.
We
need
to
get
that
to
be
the
pattern
of
behavior
right.
D
The
the
other
thing
I
would
add
in
here
too,
is
that
there's
a
little
training
on
vadim's
part
too,
and-
and
I
think
we
all
fall
victim
to
this-
that
we
we
want
to
help
right.
So
vadim
in
the
past
has
answered
questions
that
probably
should
have
been
answered
by
the
community.
So
there's
a
little
bit
of
training
on
the
part
of
the
red
hatters
as
well.
So
you
know-
and
you
know
we
all
want
to
be
heroes
too
so
and
solve
people's
problems.
So
I
think
there's.
D
D
D
I
think
that's
that's
helpful
and
and
really
sets
it
up
and
the
more
we
drive
people
to
that
google
forum
or
to
the
to
the
kubernetes
openshift
users
or
dev
the
better
off.
We
all
are
because
there's
more
people
there
to
answer
questions
other
than
vedim
so
and
the
quicker
we
are
to
respond
like
as
in
before
vedim
wakes
up.
I
think
you
know,
there's
that's
that's
going
to
be
or
vedim
or
whomever
mustafa
or
whomever
steps
into
the
foray
as
we
you
know,
grow
on
and
mature.
D
A
D
B
A
D
So
and
I'm
just
gonna
blather
on
again
jamie,
even
though
we
said
you're
running
the
meeting,
so
michael
one
of
the
reasons
from
last
week's
full
working
group
meeting
that
I
expressed
was.
We
would
like
to
be
able
to
do
some
pair
reviewing
this,
like,
like
pair
programming
type
thing
of
the
okd
dot,
the
docs
dot,
okay,
dot,
io
stuff
to
start
with,
with
mustafa
who's,
just
joined
red
hat.
D
Some
form
of
support
did
thing
that
we
don't,
as
a
community,
have
access
to
whether
it's
some
cool
operator
that
we
we
lust
for
because
that's
where
we're
at
or
you
know
something
but
just
trolling.
Through
a
section
of
the
docks
and
the
questions
we
had
in
where
we
wanted.
Your
participation
was,
if
we
find
them,
what
do
we
do
right?
D
What's
the
best
way
to
communicate
them
to
michael
burke
and
the
docs
team
to
get
them
fixed
and
that's
what
we
don't
know
and
that
what
I
was
thinking
was
to
do
a
three-way
pairing,
so
a
trio
and
have
bruce
mustapha
and
mike
do
one
section
together
and
then
mike
you
could
say
where
you
wanted
it.
You
know
you
could
see
what
they
were
finding
and
see
what
kind
of
issues
tracking
system
we
should
either
set
up
or
use,
always
remembering
that
some
of
these
people
are
going
to
be
external
to
red
hat.
E
D
E
E
D
C
D
D
Zero
open
so
now
the
other
question
I
have
for
you-
and
this
is
really
just
me
being
ridiculously
naive
about
how
docs
are
generated.
If
you
go
to
docs.io.okd.io
and
you
find
an
error,
where
is
the
source
for
that?
Like
should
be
here?
Okay,
so
like?
Is
there
one?
That's
there's
an
open
ship
desk,
docs
and
then
there's
a
repo
that.
E
D
E
D
E
D
D
A
D
D
D
D
D
A
D
D
B
E
D
C
D
If,
if
we
have,
if
we
have
the
solution
replace
x
with
y,
you
know
or
something
like
that,
so
you
know
if
you
know
it,
but
I
think
this
is
where
someone
in
documentation
might
not
know
the
answer
to
this.
You
know
I'm
not
sure,
but
I
don't
know
it.
So
I
think
it's
this
simple
and
then
it
could
be
apply.
The
labels
to
this
issue,
the
kind
is
documentation
and
then
maybe
add
okd
only
as
well.
So
you
get
two
labels
on
them.
D
E
B
C
Oh,
that
was
me
I
was
sorry.
I
was
just
saying
that
I
I
was
checking
out
this.
The
issues
on
this
repo
to
look
at
the
labels,
so
michael
does
have
special
permissions
on
this
repo,
like
I
I'm
not
able
to
change
labels.
If
I
create
an
issue,
so
this
is
something
that
you
know,
someone
who
is
going
to
be
able
to
triage
will
have
to
go
back
and,
like
add
those
labels
or
whatever
right.
B
D
E
A
A
D
Trust
me
that
much
sounds
well
right,
so
that
that's
the
kind
that
so
maybe
if
we
assign
them
all
to
michael
burke,
that
we
find
I
know
mike
that's
not
going
to
make
you
thrilled,
but
can
we
can
we
even
create
one?
Can
someone
outside
can
create
one
and
assign
it
to
you?
Then
you'd
you'd
get
tasked
with
it.
Yeah.
D
Okay,
so
yeah,
so
I
think
we
caught
enough
here
as
long
as
we
have
the
right
section
in
the
in
link
link
to
the
section
to
our
dock.
Put
that
in
and
that's
probably
enough
to
go
on
and
then
we'll
get
mustafa
in
there
and
then
maybe
maybe
I
don't
think
he
has
privileges
he's
only
been
with
us
for
four
months,
maybe
so
yeah.
Well,
I
think.
D
D
B
D
A
C
D
D
C
D
C
D
C
C
C
C
C
C
D
All
right
well
at
least
we
can
assign
people
to
it,
so
we
can
assign
michael
to
to
them
and
myself
and
that
way
between
me
and
michael.
We
can
track
them
all
down,
so
that's
actually
really
cool.
So
that
gets
us
to
the
next
step
and
then
the
other
next
step
is,
is
getting
mustafa
and
bruce
together.
To
do
a
section
pick
a
section-
and
maybe
maybe
it's
maybe
not
a
section,
but
maybe
it's
to
find
all
the
our
cause.
References
to
start
with.
D
D
That
said,
if
you're
using
okd
go
here,
and
I
drew
a
complete
blank
at
what
that
verbage
should
be-
and
I
figure
this
group
might
be
able,
so
if
you
go
into
slack,
I
certainly
I
look
like
I
had
privileges
to
change
that
description
for
some
strange
reason.
So
I
could
do
that
and
I
will
share
my
screen
and
see
if
start
sharing,
if
I
can
get
there
from
here,
tell
me
if
you
can
see
my
black
black.
D
D
A
C
D
C
D
C
Between
the
users
and
dev
channel
is
is
odd
to
me,
because
I
I
noticed
people
showing
up
in
the
dev
channel,
asking
user
questions
and
when
you
point
out,
there's
a
user
channel
they're
like
I'm
looking
for
developers,
I
don't
want
to
be
in
the
user
channel
right
yeah
I
was
like.
Are
you
kidding
me.
D
D
D
D
A
A
C
But
I
was
wondering-
and
I
started
to
think
about
this
before
when
we
were
talking
about
well,
we
need
to
get
the
red
hatters
on
the
right
page
about
doing
the
right
thing
in
the
community,
but
and-
and
so
I
was
thinking
well,
maybe
we
can
gather
the
red
headers
to
talk
about
this.
But
honestly,
I
wonder
if
we
couldn't
start
making
like
maintainer
guidelines
for
okd
right
and
then
like
once
a
quarter.
We
do
like
a
maintainers
meeting
where
people
who
are
interested
in
being
like
a
maintainer
in
the
community.
C
Oh,
let's
pull
the
red
hatters
aside
and
tell
them
what
to
do
or
let's
get
vadim
to
do
something
different
like
let's
just
get
the
whole
community
together
and
say:
look
if
you're
someone
who
loves
okd
and
you're
participating
in
the
community
and
you're
like
answering
questions
for
people,
you
know
we
as
a
community
would
like
to
make
sure
that
no
one's
time
is
being
used
exclusively.
You
know
that
everyone's
having
a
good
time,
and
so,
if
you're,
that
type
of
person
who
likes
to
answer
those
questions
here
are
some
things.
C
You
should
be
aware
of
that
we
as
a
community
endorse.
You
know
we
endorse
your
right
to
say
you
know,
please
don't
contact
me,
you
should
go
to
these
forums.
You
know
we
respect
your
right
to
say.
No.
I
can't
answer
that
question.
You
should
go
look
at
this,
so
just
giving
the
community
members
tools
so
that
they
know
exactly
how
they
could
brush
off
they
get.
A
I
think
that's
great,
and
I
think
that
goes
alongside
the
thing
which
vadim
actually
already
started,
work
on
folks
notice.
He
posted
in
the
channel
he's
created
like
a
how
to
start
troubleshooting
guide
and
he
found
some
documentation
already
exists
and
he
started
to
create
some
new
stuff.
We
need
to
solidify
that
on
the
site
and
then
so
that
same
group
that
you're
talking
about
mike
could
be
informed
or
informing
and
informing
of
that
documentation,
so
that
everyone's
on
the
same
page
of
when
we
want
to
help
folks.
A
This
is
what
we
need
from
them,
and
this
is
what
we
need
for
folks
to
be
able
to
help
themselves
etc.
So
I
think
that
would
pair
nicely
with
those
meetings
is
for
folks
to
talk
about
that
aspect
as
well,
because
the
maintainers
and
the
people
that
are
answering
questions
whatever
they're
gonna
notice,
trends
that
maybe
the
self-help
documentation
is
going
to
need
to
incorporate
or
added
things
or
added
things
to
the
frequently
asked
questions
and
whatnot
you
know
so
yeah.
I
think
that's
a
great
idea.
D
Have
you
ever
been
really,
oh,
that's
gonna,
say
the
other
thing
that
is
not
explicitly
clear
or
if
it
is
I'm,
I
missed
the
link
to
it
is
the
contribution
ladder
like
how
to
become
a
maintainer
or
how
to
become
how
to
get
these
other
privileges
and
because
of
the
nature
of
okd's
sibling
relationship
to
openshift,
it's
tricky,
and
so
so
I
think
more
language
to
describe
the
sibling
relationship,
and
you
know
not
some
so
much
the.
Why
a
bit
of
the
why
but
where,
where
contribution
made,
and
how?
D
That's
what
goes
on
in
my
head
is
that
we
have.
We
have
to
figure
out
something
to
recognize
people's
efforts
and
to
reward
them,
and
you
know
give
them.
You
know
those
those
hero,
badges
and
and
pat's.
On
the
back-
and
I
know
I
can't
do
it
with
t-shirts,
because
I'm
so
great
at
getting
t-shirts
to
people
but.
A
That
actually
also
helps
diane
just
to
point
out.
That
also
helps
in
terms
of
knowing
who
to
contact
for
particular
things,
because
once
people
have
those
descriptors,
those
labels,
then
you
can
say:
okay,
we
need
all
of
the
people
who
are
docs
people.
We
need
all
of
the
you
know
what
I
mean
it's
easier
to
pull
people
together
for
various
tasks,
so
it's
there's
multiple
things
that
are
yeah
so.
D
This
is
a
very
good
and
I
think,
we're
at
a
healthy
point
with
the
community,
where
we
have
enough
people
in
each
of
these
things
like
we
had
enough
people
to
do
different
deployment
tasks,
so
we
had
vsphere
experts
and
we
had
you
know
the
theoretical
bare
metal,
libvert
experts
or
you
know
all
and
home
lab
experts.
So
we're
beginning
to
have
these
things,
and
I
I
know
fedora
has
a
concept
of
badgifying
things.
You
know
where
people
get
a
badge
because
they're
you
know
I've
deployed
my
home
lab.
D
Bravo
and
thank
you
and
and
or
I've
I've
found
a
bug
in
docks.
You
know
kind
of
badges
totally
it
may
it
may
be
time
for
something
like
that
for
at
this
point
it
hasn't
been
in
the
past,
but
something
I
think
would
be
nice
to
put
in
place,
and
I
know
I'm
I'm
happy
to
do
some
research
on
that
and
come
back
and
even
ask.
Maybe
one
of
the
fedora
team
leads.
You
know
how
they
they
created
their
beautiful
badges,
because
I
also
want
to.
D
D
In
terms
of
that-
and
I
know
that's
not
the
same
as
the
contributor
ladder
and
getting
maintainer
privs,
but
I
think
the
community
is
now
at
a
tipping
point
where
we're
not
the
same
10
people
and
we
we
could
be
doing
something
pretty
cool
with
that,
and
so
that
that
that
would
be
my
hope
that
we
could
figure
out
something
like
that
along
the
lines
of
being
more
explicit
about
where
you
go
for
support
and
then
the
reward
for
supporting
people.
Is
you
get
a
badge?
D
C
No
it's
funny.
I
was
just
writing
that
those
like
exact
same
words,
down
diane,
like
because
I
was
thinking
the
same
thing
as
you
were
thinking,
and
I
was
like
you
know
what
what
we
should
do
is
we
should
reach
out
to
the
fedora
community
people
and
ask
them
some
of
these
questions.
Like
look,
we
want
to
kick-start
our
community
to
have
some
similar
features
as
the
fedora
community
and,
like
you
know,
like
your
thought,
about
the
badges
and
whatnot.
C
D
Yeah,
but
that
there's
always
the
administrative
side
of
it
as
well
so
like
how
how
much
of
it
can
we
automate
like
someone
like
mustapha,
does
finds
a
dock
bug.
He
gets
the
dock,
he
gets
a
little
badge
that
has
a
book
on
it
or
a
pen
on
it
or
something.
You
know
that
it's
automated
like
when
it
gets
fixed
or
whatever.
D
C
Automation
too,
though,
sorry
to
cut
you
off
but
like
because
I'm
I've
been
doing
a
lot
of
fedora
stuff
over
the
years,
and
I
still
get
automated
messages
for
packages
that
I've
worked
on
and
whatnot.
So
there's
another
side
of
this
too,
which
is
that
if
we
start
to
build
like
okd,
community,
maintainers
and
whatnot
and
people
sign
up
for
different
areas,
you
know
we
could
very
easily
create
automation.
C
A
What
it
is
that
they're
interested
in
like
their
particular
area
of
participation,
because
that
sort
of
forms
the
foundation
of
all
of
this
is
finding
out
what
it
is
that
people
really
want
to
do
and
do
we
have.
We
have
a
lot
of
people
who
are
members
of
the
working
group
that
are
showing
up
for
meetings.
You
know
17
sometimes
etc.
But
what
do
they
really
want
to
do
and
who
really.
A
A
We
don't
have
a
doc
that
outlines,
where
are
all
the
docs
and
how
are
they
maintained?
Who
has
access,
etc?
People
who
want
to
get
involved
with
docs
it'd
be
nice
to
be
able
to
just
point
them
to
something
that
says
okay
here.
This
is
the
lay
of
the
land
moving
forward.
This
is
how
you
can
participate,
etcetera
for
and
then
for
each
of
those
categories.
D
So
I
yes,
all
of
that,
is
good,
and
so,
with
the
on
the
dock
side
of
stuff,
my
my
initial
foray
is
to
get
to
figure
out
the
workflow
for
updating
docs.okay.d
io.
I
thought
that
was
a
tangible,
simple
thing
to
do,
but
I
do
think
an
overall
audit
of
all
the
docs
that
are
out
there
around
okd
is
something
that
we
need
to
take
on
this.
D
This
little
group
needs
to
take
on
and
do
and
then
then,
from
that,
that's
maybe
how
we
structure
the
review
of
the
hackathon
the
hack,
the
docs
is
like.
Okay,
here
are
the
guides
they're
still
not
over
on
okd
dot
io.
Yet
you
know
let's
yeah.
What
is
this?
This
chunk
needs
to
belong
over
here.
This
chunk
needs.
We
need
a
community
support
page,
you
know,
and
in
the
hackathon
someone
can
work
on
that
and
come
up
with
the
verbage.
For
that
you
know,
we
need
better,
more
explicit
directions
on
the
blog.
D
You
know
some
something
like
that
me
whatever
it
is,
but
that
audit,
I
think,
is
probably
our
next
big
task
of
this
little
bunch
of
folks
beyond
figuring
out
the
pair
programming
peer
review
stuff.
But
I
think
if
we
do
those
two
things
in
parallel,
we
could
have
a
midsummer
hackathon
hack,
the
docs
for
okd
to
kick
off
that
and
then
we
still
then
the
two
tasks
that
vadim
has
can
help
kick
off
the
conversation
about
who
wants
to
be
maintaining
the
core
stuff
and
reviewing
that.
A
C
I
was
just
going
to
say,
like
I,
like
the
talk
you're,
putting
down
jamie
about
like
kind
of
this
being
a
foundational
exercise
in
some
ways,
because,
like
you
know
my
my
long
tail
dream,
you
know
you
know
like
if
we
heard
diane's
dream
in
some
ways
my
long
tail
dream
is.
I
can't
wait
to
see
the
day
that
we
have
okd
community
members
contributing
code
updates
that
are
making
it
all
the
way
into
the
projects
that
we
have
that
build
up,
okay
and
like
for
me.