►
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
Hello,
hello,
all
right:
let's
get
started
no
update
on
charter
update
and
placement.
I've
been
busy
with
the
other
stuff,
the
the
shining
star
of
the
hour,
brian
beta
site,
updates.
B
And
quite
a
lot
to
talk
about
so
I've
created
a,
I
don't
know,
which
one
are
we
in.
C
B
Do
the
tasks?
First,
let
me
do
the
tasks
first,
so
I've
created
an
issue
which
I'll
put
a
link
there.
It's
two
two
three
just
to
list
everything
we
need
to
do
is
a
bit
of
a
fuller
list
than
this
one.
B
The
first
thing
I
really
want
to
do
is
just
check
that
we're
not
going
to
mess
up
anything
internally
with
red
hat.
There
are
a
couple
of
web
hooks
on
the
repo
that
are
active,
so
I
don't
know
where
they
go,
what
they
do
and
as
we
do
things
with
the
repo,
is
it
going
to
upset
people
and
start
firing
errors
or
issues
around?
B
B
C
Yeah,
so
I
so
just
just
so
you
know
I
reached
out
to
will
gordon
and
jerry
follow
who
I've
at
assigned
also
to
this
issue
just
in
the
past
hour,
and
they
are
going.
They
are
going
to
repoint
the
dns
for
us,
but
they'll
also
they'll
now
review
your
thing.
I
don't
think
any
of
the
web
hooks
that
are
in
there
in
the
site
are
going
to
be
bothered
by
what
you
do,
but
that's
my
my
opinion
and
they
put
the
hooks
in
there,
so
I'm
gonna
double
check
with
them.
Today.
C
Jiri
is
on
check
time
he's
in
the
czech
republic,
so
he's
we
got
him
early,
hopefully
today
so
we'll
do
that.
But
what
my
hope
is
by
next
tuesday's
meeting
we
will
have
resolved
and
will
be
pointing
to
the
new
new
site.
B
Okay,
so
just
just
so,
everyone
knows,
because
we've
called
the
repo
okd
dot
io,
when,
if
her
pages
creates
the
site,
it
uses
the
org
name
and
then
slash
and
the
repo
name.
B
B
So
when
we
do
the
redirect
to
okd.io
I'm
hoping
that,
even
though
it's
redirecting
here
it'll
still
go
and
work
that
that's
my
concern
there.
Okay,
the
way
around
it
is
and
say:
okay,
the
io
just
put
a
dash
okay
d
io,
but
that
means
we'll
be
renaming
the
repo
and
again
I
don't
know
what
points
to
it
and
what
else
is
going
to
break?
If
we
have
to
do
that,
but
hopefully
we
won't
have
to
do
that
and
everything
else.
I
think
I'm
pretty.
B
Okay
on
and
the
other
thing
I
just
wanted
to
take
the
opportunity
to
we've
got
a
lot
of
branches,
so
I
was
just
going
to
hopefully
take
the
opportunity
to
just
get
rid
of
all
of
these
old
branches
and
tidy
them
all
up.
As
you
can
see,
we've
got
pages
of
branches,
so
anybody
has
an
objection.
I
was
just
going
to
just
close
all
the
old
branches
and
close
all
the
pull
requests
that
relate
to
the
old
one
yeah.
B
So
that's
that's
that
and
then
the
other
one
is
the
status
and
the
attack
the
beta
site.
So
that's
all
working
we've
had
a
couple
of
pull
requests
from
the
virtual,
the
virtualization
subgroup,
which
raised
a
couple
of
issues.
B
The
first
one
is
there:
they
suggested
putting
in
the
exact
steps
to
actually
in
create
the
development
environment,
and
if
we
do
that,
do
we
need
to
actually
look
at
all
the
major
linux
distros,
the
macos
and
then
the
windows,
given
that
50
of
developers
are
on
windows,
either
40,
something
or
mac
and
relatively
few
tend
to
be
on
linux
distros.
B
B
A
And
well,
let's
go
question
by
question
so
for
this
one
I
know
that
in
some
of
the
other
sites
that
I'm
involved
with
that
are
sort
of
repo
based.
There
are
example
issues
that
people
create
of,
like
you
know,
just
like
others:
how
to
create
an
issue.
There'll
be
a
a
page
of
how
to
create
a
page
or
an
issue
of
how
to
create
a
page,
how
to
run
it
locally
and
whatever
there
are.
A
Theoretically,
we
could
script
it
for,
like
the
three
major
os's
like,
but
the
linux
thing,
obviously
you're
splitting
it
into
you
know:
you're
gonna
have
yum
app
like
so
yeah.
I
don't
know,
I
mean
I'm
torn
between
writing
instructions,
because
then
you
have
to
maintain
them,
creating
a
script
for
each
which
then
again
you
have
to
maintain
it
or
just
giving
general.
B
C
Can
I
ask
a
naive
question
because
that's
what
most
of
my
questions
are?
Is
this
how
to
build
them
the
make
docs
version
of
the
site,
and
if
so,
does
the
make
docs
site
itself
where
make
docs
live?
Does
it
have
documentation
on
how
to
build
make
doc
sites
that
we
can
just
link
to.
B
It
is
this
section
here,
so
I
need
to
write
the
bit
about
how
to
use
a
docker.
I
was
hoping
we
could
use
partner
machine,
but
you
can't
mount
a
volume
on
podman,
so
it's
gonna
have
to
be
docker.
I'm
gonna
put
the
docker
instructions
here,
but
on
this
site
this
is
what
we've
got.
So
it's
installed
python
and
soul.
Node.
D
B
D
B
The
problem
is
because
you've
got
mk
docs
and
then
you've
got
these
other
tools
like
to
do
the
link
checker
and
the
spelling
which
isn't
on
the
mk
doc
site.
So
the
idea
is
this
is
the
set
of
instructions
that
you
need
to
get.
I
got
a
button.
A
C
Yeah
but
the
minute
mk
docs
does
their
next
release
and
you
know
it's
python
three-point,
something
or
you
know.
B
Yeah,
well,
you
actually
get
it
because
I've
actually
put
a
requirements
fire
file
in
which
has
all
the
the
python
stuff.
So
by
doing
it
store
minus
r
you're
getting
mk
docs
on
the
markdown
extensions
okay.
So
the
the
biggest
issue
are
these
two,
because
you've
got
different
instructions
on
various
linux
packages
depending
on
the
distro.
C
E
E
Sufficient
actually,
brian,
the
only
thing
that
I
might
say
is:
if
there
are
any
version
dependencies
on
python,
you
know
like
subversions,
then
you
should
say
that
otherwise,
you
don't
have
to.
E
B
A
B
Well,
I'm
doing
it
that
if
you
want
to
contain
that,
if
you've
got
docker
installed,
you
can
do
it
on
docker.
If
you
want
to
install
it
locally,
you
can
install
it
locally.
So
I'm
just
giving
you
both
options,
but
I'm
expecting
most
people
will
use
a
container
if
you
don't
want
to
put
docker
on.
I
mean
the
problem
is
now:
the
dockers
are
paid
for.
B
A
B
So
if
you
have
your
editors
on
editor
on
windows
or
ide
on
window,
you
want
to
be
able
to
build
and
and
test
the
sites
editor.
So
you've
got
to
be
able
to
mount
the
volume
within
the
container
I'm
trying
to.
I
did
look
at
doing
the
the
clone
within
the
container,
but
then
it's
a
pain
to
actually
go
and
change
the
content.
B
B
A
E
B
B
So
what
they
want
to
do
is
they
want
to
actually
put
a
social
media
panel
in
and
and
what
they've
done
is
they've
got
again
the
source.
B
What
they've
done
is
they've
actually
gone
and
modified
the
site
css
to
create
their
own,
their
own
sort
of
css
tags
and
content,
and
then
they've
put
a
bunch
of
html
at
the
top
of
their
page
and
again,
one
of
the
design
principles
was
get
rid
of
all
html,
so
everything
is
marked
down
within
the
site.
C
Yeah,
so
so
maybe
what
we
should
do
is
invite
them
to
come
to
the
docs
meeting,
the
next
one
and
say,
and
just
put
a
com
cont,
you
mean
adding
a
section
to
the
page
is
not
not
a
bad
thing,
it's
more
like
they
need
to
do
it
within
the
context
of
make
docs
as
opposed
to
adding
html
is
is
our
is,
is
the
rule?
I
think
that
we've
we're
trying.
B
A
C
E
Oh
and
on
like,
if
we're
okay,
so
what
are
we
comparing
with
we're,
comparing
with
the
old
okd
site,
which
was
not
terribly
friendly
to
for
outsiders
to
edit
yeah
terribly,
not,
and
so
we're
this
version
anyway,
trying
this
particular
technology
and
presumably
we
would
have.
We
have
something
in
the
document.
Excuse
me
documentation
that
says
this
is
sort
of
the
design
framework
for
the
site
so
that
we
could
point
them
to.
E
If
somebody's
coming
with
a
completely
different,
you
know
html
based
flavor,
then
you
know,
I
would
think
that
the
thing
to
do
would
be
to
reject
the
requests
point
them
to
the
design
or
at
least
continue
the
discussion.
E
Otherwise,
you
get
a
big
hodgepodge
where
you
know,
maybe
part
of
it
is
using
ruby
on
rails
and
part
of
it's
using
react.
And,
oh,
why
not
jsf
and
it's
a
big
disaster.
A
B
A
E
E
Right
now,
if
I'm
coming
from
a
conciliatory
hat-
okay,
because
I
just
gave
you
my
authoritarian
hat,
the
conciliatory
hat
would
say
that
for
the
cube
people,
we
actually
want
to
pull
them
in.
E
So
we
want
to
work
with
them
to
make
this
transition,
and
certainly
some
of
them
can
get
their
backs
up.
You
know
at
least
as
well
as
I
can.
I
would
like
to
avoid
that.
C
This
is
this
is
what
I
this
is
the
way,
the
diplomatic
way
that
I
would
would
try
and
frame
it,
and
I
will
reach
out
to
sandro,
because
I
think
he's
a
red
hatter.
I'm
pretty
curious
is
that
if
he,
what
he's
doing
what
he's
asking
for
is
to
add
some,
it
looks
like
a
little
social
media
pizzazz
to
the
the
landing
page.
C
B
And
that's
what
I
suggested
that
if
we're
going
to
do
that,
let's
make
it
a
template,
which
is
how
I've
done
the
home
page.
So
if
you
look
notice
the
home
page
formatting
is
a
little
bit
different
because
we
we've
got
the
things
there,
but
the
source
is
still
pure.
A
Maybe
do
maybe
do
it
in
two
steps
right
so
reach
out
to
them
and
continue
on
the
path
of
trying
to
integrate
it
across
the
site
in
a
way
that
that
doesn't
break
things
and,
at
the
same
time,
write
something
out
for
future,
because
we
have
other
working
groups
coming
online
and
beginning
to
solidify
this.
As
as
as
process.
B
Yeah
and
yeah
I
mean
I,
I
just
didn't-
really
know
I
don't
we
don't
really
have
a
way
of
any
of
this
written
down,
so
I
just
yeah.
This
was
just
really.
What
is
our
approach
to
this
and
then
the
second
one
is
obviously
the
last
working
group,
the
main
working
group.
We
we
have
a
conversation
about,
should
we
actually
have
social
media
accounts,
and
that
was
the
second
part
of
this.
Is
I
I
accepting
the
the
pull
request?
B
Am
I
meant
to
be
validating
that
what
they
put
in
is
in
line
with
agreements
in
the
the
main
working
group,
or
is
that
not
what
the
role
of
who
of
the
documentation?
Whoever
accepts
the
pull
request?
Because
again,
I
was
a
little
bit
unsure
of
that,
because
we
sort
of
said
that
we
didn't
want
social
media,
and
yet
this
pull
request
is
adding
a
sub
group,
not
even
okay,
social
media
to
sub
group.
Social
media
accounts
twitter
and
things.
B
A
C
I
really
want
them
to
come
to
this
meeting
to
talk
about
it
with
us,
as
opposed
to
us
putting
an
edict
down
on
it
and
we
have
not
and
raise
it
to
a
higher
level,
because
we
don't
even
have
an
okd
twitter
handle
so
have
the
conversation
be
about
okd,
social
media
presence
and
then
the
sub
working
groups,
and
so
I'd
like
to
get
just
pinging,
sandro
and
he's
not
on.
I
think
he's
in
italy.
So
I
he.
C
He's
not
not
responding
here,
but
I'd
rather
rather
than
have
them
go
off
and
create
their
own
thing
and
then
have
to
rein
it
back
in
or
edit
it
after
they've
built
up
some
sort
of
a
following.
Whatever
I'd
like
to
have
a
bigger
conversation
about
whether
or
not
we
should
have
an
okd
sub
presence
and
how
we're
going
to
manage
that
and
and
who
is
going
to
manage
that
because,
as
I
said
it
at
one
of
the
last
meetings,
I
think
the
last
main
group
meeting
it.
C
I
I
already
manage
openshift
commons
and
have
a
access
to
openshift
as
twitter
handles
to
get
stuff
retweeted
on
and
I've
never
opened
up
the
can
of
worms
of
managing
yet
another
twitter
handle.
It
may
be
time
to
do
that,
so
I'm
not
adverse
to
it.
But
I'd
like
to
have
that
as
a
bigger
conversation
about
how
we
resource
managing
it,
who
has
access
to
it
and
that
and
then,
if
there,
if
we
can
do
something
with
the
overt
stuff,
then
ruby
I
keep
saying
over
it.
C
So
I
probably
shouldn't
be
yet,
but
the
virtual,
the
okd
virtualization
cuber
stuff,
I'm
stuck
on
over
it
this
morning-
apologies
to
everybody
rather
than
us,
giving
them
an
edict
saying
no
or
whatever.
But
I
what
I
want
to
get
them
is
more
involved
in
the
okd
working
group,
discussion
of
social
media
and
how
we
should
do
outreach,
because
you
know
jamie
and
the
other
chairs
and
everybody
should
have
access
to
that
twitter
handle.
C
But
maybe
we
have
a
social
media
manager
for
the
community
that
that
just
does
promotions
and
stuff
and
and
books
that,
and
you
know.
A
B
A
B
Yeah,
so
so,
once
that's
resolved
and
say
we
have
a
pull
request
to
actually
pull
their
their
site
in
which
is
the
other
link
in
in
this
subgroup
work
content
session.
So
that
is
the
pull
request,
but
at
the
minute
it
actually
does
break
the
page,
but
we
also
have
the
questions
of
social
media
and
and
adding
it
correctly.
So
that's
that
one
and
yeah,
so
that's
me
decide
so
as
soon
as
I
I
get
an
official
sort
of
comment
that
yeah
the
web
hooks
aren't
important.
B
I
can
actually
stop
doing
the
the
changes
and
yeah,
hopefully
it'll,
take
only
half
an
hour
to
get
everything
sorted
and
switched
over.
A
All
right,
let's
move
on
here,
we're
about
halfway
through
the
meeting
name
and
scope
of
install
and
readme.
We
agreed
that
it
needs
to
be
done.
Reworking
will
begin
after
the
beta
site
goes
to
prod
lots
of
stuff.
Here
is
beta
cycles
to
prod
inclusive
language.
Same
thing
just.
B
A
Right
vadim
was
video,
wanted
to
make
sure
that
that
that
stuff
didn't
change
in
the
repo
until
the
other
stuff
was
actually
public
and
at
the
at
the
main
url.
So,
okay,
cool,
inclusive
language,
that's
going
to
be
addressed
and
then
we're
going
to
do
a
a
regular.
Maybe
we'll
do
like
a
quarterly
check-in,
or
something
like
that.
Just
to
make
sure
that
anything.
A
Brian,
would
this
be
something
that
once
you've
added
it
to
the
automation
that
you
can
put
this,
so
we
need
a
document
that
basically
says
this
is
what
is
in
there.
This
is
what's
set
up
so
that
you
know
if,
if
you
need
to
share
tasks
or
you
need
to
hand
it
off
at
some
point
or
anything
that
we
know
what
is
in
there
and
how
it
works
and
what
not.
B
A
That
would
be
awesome,
upgrade
path.
Notations
vadim
was
talking
about
upgrade
stuff
and
upgrade
path.
He
came
up
with
a
4.7
to
4.8,
but
it's
unclear
there's
some
issues
that
people
are
having
with
it.
So
I
think
we'll
shelve
that
until
we
get
some
clarity
from
from
vadim.
E
It's
only
from
one
particular
4.7
and
that's
so
you
have
to.
E
E
So
it's
a
little
bit
of
a
minefield,
but
it's
it's
all
documented
in
the
you
know
the
sort
of
release
website,
if
you
actually
well,
you
know
if
you
look
sort
of
behind
the
initial
link
into
the
footnotes
as
it
were,
and
of
course,
if
you,
if
you
get
there,
then
you
have
the
wrong
kubernetes
version.
E
A
So
well,
I
think
once
the
team
gets
a
little
bit
of
clarity
on
where
things
go
by
the
way.
I
don't
know
if
anyone
saw
that
christian
added
some
comments
to
a
couple
of
those
tickets
and
in
conversation
with
other
folks,
has
pointed
out
that
they're
going
to
try
to
pull
okd
back
into
the
openshift
repo
and
out
of
the
deems
like
private
repo.
A
So
I
think
that's
going
to
change
things
a
little
bit
in
terms
of,
but
it's
it's
going
to
change
things
a
little
bit
so
we'll
I
think
we'll
have
to
shelve
this
until
we
get
more
clarity
from
the
dean
and
we
see
sort
of
where
things
are
going
in
terms
of
resources.
A
I
accidentally
glossed
over,
create
docs
process
document,
so
everyone
is
signed
off
on
michael's
document.
Does
someone
want
to
add
that
into
the
beta
site
repository?
Oh,
is
it
great
all
right?
So
that's
done
excellent.
A
A
Okay,
next,
okay,
the
office
hour.
We
need
to
do
some
promotion
for
this
because
it's
like
next
week
and
we
haven't
really
posted
anything
about
it.
Diane
is
there
an
official
picture.
C
Somewhere
yeah
there
is
a
landing
page
I
will
grant,
I
will
grab
it
and
throw
it
in
the
chat
and
it
is
listed
and
the
powers
that
be
at
red
hat
are
promoting
our
presence
at
kubecon,
so
it
will
get
promoted
as
part
of
that
slipstream,
probably,
we
should
add
a
send
a
note
to
the
okd
google
group
and
that
would
be
personally
sufficient
marketing.
From
our
point
of
view.
C
A
And
I
also
tend
to
spam
the
open
shift
in
facebook,
the
openshift
users
and
you
can
post
it
up
there
and
people
actually
respond.
Google.
C
A
All
right
well,
while
she's
doing
that
code
of
conduct,
there's
an
issue
there
for
a
code
of
conduct
that
diane,
created
and
michael
is
added
to
we're
going
to
be
added
to
this
is
basically
a
ansible
code
of
conduct,
page
lifted
and
shifted
into
our
code
of
conduct.
C
So
what
what
I'm
hoping-
and
this
is
why
I'm
really
thrilled
that
michael
perkins
here
is,
if
you
look
where
the
ansible
folks
tucked
it,
they
tucked
it
right
into
the
docks,
and
I
know
openshift
doesn't
have
that
in
the
docks
right
now
for
like
docs.openshift.com
or
whatever
the
site
is,
and
we
don't
have
it
there,
but
I
wouldn't.
C
I
would
really
like
to
have
it
live
in
the
docks,
because
then
it
not
only
will
and
then
link
to
it
from
the
site
that
brian
has
created,
which
means
that
the
cut
and
paste
and
search
and
replace
for
ansible
and
tweaks
that
we
want
to
make
would
be
moved
into
the
docs
and
it
would
be
maintained
over
time
and
partially,
because
I
know
the
ansible
folks
got
their
stuff
all
nicely
reviewed
by
red
hat,
legal
and
and
and
I
kind
of
like
their
their
code
of
conduct.
C
I
know
other
people
have
other
opinions
about
codes
of
conduct
and
that
sort
of
stuff
too
so,
but
I
wanted
to
get
it
out
there
and
and
see
if
michael,
if
that
was
okay
with
you
to
to
move
it
there
and
that
way
then
brian,
basically,
all
you
have
to
do
is
is
link
to
it
and
if,
if
legal
or
red
hat
or
the
community
decides
to
change
it,
they
change
it
in
the
docs,
with
the
help
from
michael
burke
and
the
red
hat
docs
team
that
manages
that
I
think
that
way
it
will
live
on
a
lot
longer
and
get
a
lot
more
readership
than
the
landing
page
itself,
and
that's
just
my
opinion.
A
Okay,
so
be
prepared
at
the
next
meeting
to
provide
feedback
on
this.
One
thing
I
would
suggest
is
that
we
actually
use
this
as
I
like.
In
other
words,
I
like
what
cncf
does
for
all
of
their
like
streams,
event,
streams
and
even
their
meeting
streams
and
stuff.
As
they
actually
say,
this
is
a
cncf
event
and
as
such,
it
falls
under
our
code
of
conduct
and
they
might
link
to
it
or
whatever,
and
I
I
would
be
totally
fine
if
we
did
that
at
the
beginning
of
all
of
our
meetings.
C
C
Yeah
one
of
the
things
that
and
I'm
on
a
bunch
of
cncf
things
they
have
is
at
the
beginning
of
every
meeting,
and
it
might
be
a
meeting
etiquette
thing
that
we
do.
We
don't
tend
to
use
slides
or
anything
visuals,
but
they
have
one
slide
that
they
open
the
meeting.
C
With
that
it
says
what
the
meeting
is,
what
the
date
is
and
then
the
next
slide
is
usually
at
least
most
of
the
meetings
that
I
go
to
is
a
link
with
a
blurb
about
the
code
of
conduct,
and
then
they
go
into
that
so
on
every
recording.
You
have
that
as
well.
There
is
sort
of
the
opening
act
for
every
meeting.
A
That
actually
leads
me
to
a
question:
do
are
we
free
to
use
the
little
mascot
in
our
slides,
like
for
the
intro
to
the
videos?
I
mean
no
offense
to
to
what
you
did
with
the
gray
and
red
thing
a
couple
of
years
ago,
but
then
taken
you
know
it's.
It
would
be
nice
to
have
like
a
white.
C
A
C
The
graphics
are
all
in
in
the
repo
items
here
in
some
image
file
and,
if
not,
I
will
send
you
and
upload.
They
should
also
the
okay
dot
io
repo.
C
Yeah,
that's
true
yeah,
so
yeah
they're,
all
in
the
open
joseph
myers,
did
a
rework
of
them
at
one
point.
Another
guy
inside
of
red
hat
did
one
that
that
panda
has
been
tweaked,
oh,
not
as
much
as
the
github
octa
octocat,
but
it
should
be,
and
I
think
we
should
all
have
our
own
variations.
C
People
keep
sending
me
stickers
with
different
panda-like
things,
with
openshift
logos,
incorporated
in
them
that
they've
done
for
their
local
meetups
and
things
so
feel
free
to
dance
away
with
that
and
use
it
as
you
wish,
yeah
my
graphic
skills.
I
keep
saying
this
to
people
are
from
ms
paint,
so
I
have
no
I'm
very
buddhist
about
my
attachment
to
the
website,
as
you
found
out
brian
and
to
any
graphical
thing.
So
all.
A
Right
so
I
will
add
that,
to
the
beginning
of
the
video
and
I'll
create
a
new
like
flash
screen
at
the
beginning
and
it'll
feature
the
date
and
stuff
like
that,
and
also
the
link
to
the
code
of
conduct.
A
You
could
do
a
gist
or
you
could
do
a
heck
md.
I
o
like
just
like
the.
C
A
I
would
suggest
that
meetings
are
not
slice
and
dice
meetings
during
meetings
text
license
can
sometimes
be
not
the
best.
So
if
folks,
maybe
maybe
we
have
this
discussion
over
the
working
group-
email
list-
okay,
that
might
be
better
instead
of
like
taking
up
the
whole
hour
like
sort
of
should
this
go
there?
Should
you
know
what
I
mean
like
that
could
be
gotcha.
C
I
think
we
will
be
pretty
close
to
going
there,
but
then
I
just
want
to
make
sure
that
everybody's
on
board,
with
the
content
you
know
and
having
that
there
and
excellent
everybody
has
an
opinion
about
them.
Yes,.
A
Okay,
this
next
one
is
directed
at
michael.
There
was
an
issue.
Does
anyone
know
where
this
issue
is
someone
commented
and
I'm
not
I'm
doing
a
search
and
I'm
not
finding?
It
was
either
an
issue
or
discussion
item,
but
there
are
4.9
references
now
in
the
okd
docs,
because
it
just
copied
everything
over
and
obviously
we're
not
even
to
for
we're
just
rolling
out
4.8.
F
F
A
Okay,
if
you
could
just
if
we
could
go
to
her
release
and
and
not
do
latest
anymore,
that
would
probably
like
solve
this.
Just
not
have
it
be
latest
just
be.
People
will
assume
that
the
last
number
in
the
pull
down
is
the
latest
deadline.
A
All
right,
and
once
we
find
that
issue,
we'll
point
it
to
you
point
you
to
it
point
it
to
you
point
you
to
it,
and
so
what
are
the
next
steps?
Next
on
the
list
is
twitter
and
facebook.
We
sort
of
decided,
I
think,
to
wait
on
facebook,
but
we
did
decide
that
we
wanted
to
have
stuff
sent
out
through
the
openshift
twitter
diane.
Do
you
have
that
as
a
task
to
do.
A
A
If
you
create
an
issue
and
we
might
be
able
to
even
get
vadim
to
add
a
a
tag
or
a
type
whatever
those
those
types
that
is
like
task
or
something
like
that,
and
then
anytime,
we
have
a
task
for
someone
we
just
put
that
in
there
and
then
include
their
name
and
in
the
content
or
something
like
and
for
folks
that
didn't
catch
this
at
the
main
meeting.
A
I
am
going
to
start
doing
a
task
list
and
what
that
task
list
will
do
then
was
just
link
to
these
individual
issues
and
the
repo
that
explain
what
it
is
that
people
are
supposed
to
be
doing,
because
we're
getting
to
the
point
where
we're
getting
big
enough,
where
we
have
to
actually
like
be
accountable
to
each
other
and
stuff
like
that.
So
is
it.
Is
it
worthwhile.
E
B
A
Not
that
that's
ever
happened
to
all
of
us
right,
I
don't
know
what
do
folks
think
about
it.
E
A
E
E
E
So
the
anyway
I'll
see
if
I
can
find
something
and
I'll
sort
of
bring
it
to
the
next
meeting.
E
Well
right
and
a
lot
of
the
stuff
that's
on
like
so
git
is
proprietary
as
well.
You
know
microsoft
owned
last
night.
Looked
gitlab
is
a
bit
more
flexible
but
they're,
apparently
looking
at
ipo.
That
seems
to
be
going
public.
E
But
sure
I
mean
I
I
would
look
in
those
places
preferentially.
I
guess
and
if
you
have
any,
if
you
have
any
suggestions,
just
you
know
pass
them
on
to
me
you're
doing
my
work,
so
I
can't
complain
about
that.
A
A
C
The
other
thing
that
I
that
suggested
that
you
made
at
the
last
meeting
that
I
think
might
make
sense
is
to
discuss,
is
whether
we
call
this
group,
the
docs
group
or
the
communications
group,
so
that
we
could
cover
more
than
just
documentation,
but
the
out,
you
know
maybe
documentation
and
outreach.
C
C
Because
I
think,
when
you
just
say
docs
not
no
offense,
michael
you,
we
just
get
the
docs.okd.io
folks
and
not
the
twitter
handle
wannabes
and
which
is
all
good
and
and
if
we
need
to
break
them
out
into
two
separate
subgroups
like
opd
marketing
or
outreach
or
whatever.
C
C
It
will
be,
and
I
have
lost
the
link
to
the
hackmd
thing.
Can
you
throw
the
hackmd
url
back
into
the
chat?
I've
got
too
many
windows.
C
Yeah
yeah
yeah,
it's
for
me.
I
mean
the
lesson
that
I've
learned
over
the
years
is
that
creating
a
twitter
handle
is
wonderful
and
easy.
Managing
it
and
keeping
it
alive
and
feeding
it
is,
is
a
resource
heavy
thing
so
and
I
think
that's
we
had
the
little.
A
Oh
diane
reinviting
the
cubert
folks
to
this
meeting
yep.
C
A
Yeah
so
yeah
all
right.
A
I
think
that's,
that's
everything
any
last-minute
stuff
that
we
need
to
talk
about.
C
C
A
Well,
this
was
a
very
productive
meeting
and
it's
amazing
that
this
little
group
gets
so
much
done
actually
appreciate
everyone's
hard
work.
A
A
All
right,
I
think,
we're
good
we're,
actually
ending
a
couple
minutes
early
and
I'll
check
in
I'll
send
something
out
over
the
mailing
list,
checking
in
on
people's
tasks
and
pointing
you
to
the
actual,
get
issues
that
I'll
create
or
get.
I
don't
know
I'll
talk
to
vidim
about
which
way
to
do
this,
but
they
might
be
discussion,
items
that
have
a
special
like
task
category
or
something
awesome
all
right.
Thank
you
folks.