►
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
Welcome
to
the
openshift
working
group,
documentation,
subgroup
meeting
for
february
8th
the
link
to
the
notes
is
in
the
meeting
chat
if
you
could
put
your
name
in
the
attendance
section.
So
we
know
who
was
here
and
who
was
was
available
to
hear
some
of
the
information
being
discussed
and
that
helps
us
to
know.
A
Maybe
if
someone
wasn't
here
that
we
need
to
reach
out
for
something
that
was
discussed,
that
relates
to
something
working
on
and
take
a
quick
second
to
look
over
the
agenda,
and
let
me
know
if
there's
anything
that
you
want
to
change
and
again
this
is
our
february
8
2022
meeting.
B
A
Okay,
anyone
else
have
any
suggestions.
Any
modifications
to
the
agenda.
A
Sounds
like
folks
are
good
with
it.
So,
let's
start
out
with.
C
Your
projects,
quick
questions
are,
are
we
gonna
talk
about
the
you
know,
operators
at
all.
A
Yes,
talking
about
operators
that
is
down,
let's
see,
I
think
it's
in
it
should
be
in
here.
It's
not
yeah,
so
there's
a
new
subgroup
for
operator
catalog,
that's
the
third
item
or
second
or
third
item.
Yes,
third
item,
so
we
will
be
talking
about
that.
A
B
A
That's
a
question
for
this
group
to
decide
right
now,
so
it
wasn't.
We
had
a
variety
of
opinions
and
I
think
it
was
depending
on
if,
if
vadim
did
sign
off
on
closing
the
the
dev
once
so,
vadim
is
more
than
happy
to
do
that.
Elmiko
left,
basically,
everyone's
been
bailing
out
of
the
channel,
except
for
me
and
a
handful
of
other
folks.
So
there's
really
no
one,
even
there.
Okay,
so
that
would
be.
A
B
B
So
if,
if
there
is
a
history,
that's
important
to
people
there
and
if
the
kubernetes
folks
say
changing
the
name
changes
the
is
basically
creating
a
new
one
and
losing
the
history
in
that,
then
probably
sticking
with
openshift
users
is
probably
a
good
thing.
B
A
D
B
Yeah
it
might
so
that's
that's
the
only
thing
I
these
are
the
things
when
you're
on
a
hike
and
you're
not
supposed
to
be
thinking
about
work
that
pop
in
your
head
and
that
that's
so
I
will
ask
that
question
and
if
of
the
kubernetes
admin
folks
for
that
channel,
and
if
it
is
that
it
has
history
that
is
semi-important.
B
The
other
thing
is
that
if
we
change
the
name,
we
might
lose
the
subscribers
to
people
who
are
already
in
that
channel.
So
that's
what
was
feeding
you
know
the
history
and
people
who
are
already
in
it.
So
I
will
ask
that
question
and
if
we
don't
lose
either
of
those
things
changing
it
to
okd
is
that
the
proposal
openshift
dash
okd.
D
Right,
well,
I
mean,
I
think,
one
of
the
questions
to
ask
is:
is
there
actually
any
open
ship
support
provided
in
the
channel
because
by
calling
it
openshift
you'd
be
sort
of
giving
the
impression
that
there
is
open
shift?
So
if
you
did
have
a
a
a
customer
ocp
customer,
would
they
expect
to
get
responses
from
that
channel?
D
I
personally
I
I
like
the
idea
of
having
okd
in
the
name
to
actually
show
it,
but
whatever
we
do,
I
think
we
need
clarity,
because
I
mean
the
the
the
sort
of
strap
line
is
discussion
of
open
shift,
installation
and
usage
queries,
sorry
questions
issues
yeah
and
we
actually
tell
them
for
okd
go
elsewhere.
A
B
A
B
It's
always
a
spare
time
thing,
but
I
I
do
think
there
are
a
number
of
openshift
customers
that
go
there
and
that
they,
you
know
so,
and
it's
not
a
bad
thing.
In
my
opinion,
it
gives
it
gives
branding
from
a
red
hat
perspective,
to
openshift
in
the
kubernetes
space
that
we
like
to
have
so.
Sharing
that
one
channel
with
openshift
and
okd
is,
in
my
mind,
optimal,
and
then
we
only
have
one
stop
shopping
and
we
do
get
some
recognition.
B
B
A
A
Because
then,
we're
not
committed
to
it
so
much,
because
we
are
trying
to
direct
people
to
use
the
discussion
and
get
for
stuff
so
that
there's
a
searchable,
grouped
history
on
topics
and
things
like
that
and
tagging
and
whatnot.
So
we
can.
Maybe
we
don't
spend
too
much
time
on
this.
You
know
and
focus
more
on
her
getting
people
replaced
where
we
want
them.
A
B
Yeah,
oh,
it
looks
like
I
have
edit
capabilities
on
that,
so
I
can
edit,
as
we
wish.
B
Yeah
cool
so
yeah,
so
the
question
would
be
to
the
admins.
B
D
A
D
Because
I'm
trying
to
log,
I
tried
to
follow
the
link
to
log
in
there
and
he
told
me
that
my
domain
wasn't
supported.
So.
D
B
So
I
think
part
of
me
is
this
is
just
if
there's
something
on
the
topic
that
we
want
to
rewrite
that
in
some
way.
Obviously
jamie
and
I
both
can
edit
the
topic
and
the
descript
the
description
we
can.
We
can
do
that
because
back
in
2070
sarah-
and
I
did
this
so
I'm
not
saying
that
it
doesn't,
but
I
can't
see
any
way
to
change
the
name
you
can
only
archive.
B
So
I
think
our
discussion
about
changing
the
name
is
kind
of
moot
yeah,
it's
kind
of
moot.
It's
not.
B
E
C
The
actuality
is
not
quite
as
black
and
white
as
we're
suggesting
in
the
topic,
because
there's
a
lot
of
okd
stuff,
which
is
identical
to
ocp
yeah
and
you
know
vadim,
will
you
know
if
it
seems
that
way
to
him?
He
will
suggest
you
know
moving
a
bug
report
to
the
ocp.
You
know
bugzilla
or
whatever,
and
so
some
of
the
ocp
discussion
would
also
be
useful
to
okd
users.
A
So
maybe
that
maybe
that
this
actually
is,
if
there's
maybe
there's
a
better
way
than
dash
okay
dash
specific,
but
maybe
the
description
actually
is
okay
or
the
topic
actually
is
for
the
most
part
correct.
You
know
what
I
mean
it's
like.
If
you
want
something
specific
to
okd,
go
to
the
discussions,
if
you
want,
if
it's
something
that
could
be
solved
by
either
of
them,
this
is
as
good
as
places
any.
I
don't
want
to
spend
too
much
because
we're
17
minutes
into
the
meeting.
B
And
I
don't
know
I've
been
sharing
my
screen,
so
I
think
we
also
someone
whether
it
was
jamie
or
vadim
mentioned
in
the
description
for
a
dash
dev
that
it
was
being
depreciated.
So
I
think
what
we
do
is
we
give
it
a
month
and
then
archive
the
sucker,
and
that
way
we
don't
lose
any
members.
We
keep
these
and
then
maybe
I
can
periodically
go
into
the
dev
and
just
put
a
reminder,
please
migrate
over
over
the
next
month.
B
Every
you
know
once
every
friday,
while
I'm
having
coffee,
remind
people
to
move
to
dash
dev
and
then
at
the
end
of
the
month,
get
the
kubernetes
folks
to
archive
it.
But
people
will
just
move
over
to
dash
users
right
yeah
exactly
so,
I
think
what
I'm
putting
on
the
table
is,
leave
it
as
is,
and
the
depreciation
notice
is
in
the
dev
right
up
and
then,
if
I
go
in
and
you
know
periodically
say
hey,
this
is
being
depreciated
at
the
end
of
the
month.
B
It
will
be
archived
boom,
maybe
I'll
edit,
the
the
dev
one
saying
it's
going
to
be
archived
at
on
what
is
february
28th.
The
last
day
of
the
month
and
then
go
for
that,
and
then
we
can
move
on
in
the
agenda
jamie
if
that
works.
For
folks.
A
Show
of
hands
does
that
work
works
for
me
all
right.
Excellent!
Let's
move
on
now
to
our
next
item
here,
which
is
the
code
of
conduct.
I
did
send
an
email
out
reminding
folks
one
more
time
that
the
deadline
for
comments
is
february
15th.
This
brings
up
an
interesting
question.
A
Sandra
brought
it
up
and
it
actually
relates
to
a
couple
of
things
we
have
on
the
table,
which
is
that
diane,
you
can
go
ahead
and
end
your
screen
sharing
and
then
that
way
we
talked
about
this
before
contact
email
addresses
and
what
our?
What
are
our
options
for
contact
email
addresses
related
to
okd,
so
can
do
we
have
diane
the
ability
to
ask
that
the
mx
for
okd
dot,
io
point
to
a
mail
system
that
we
can
use.
A
B
Yes,
but
I
think
I'm
sure
we
we
could
figure
it
out,
we're
all
technical
enough
to
figure
out
how
to
get
that
working.
I
think
what,
from
my
understanding
of
codes
of
context
and
the
person
to
contact
that
needs
to
be.
B
Usually
that
is
someone
in
the
legal
department.
It
is
not
or
it
is
a
jointly
held
email
address.
Let
me
I'll
have
to
think
about
it,
because
I
wasn't
thinking
about
having
a
contact
person.
That's
always
been.
The
sticking
point
is
who's
going
to
answer
and
who's
going
to
adjudicate
and
manage
all
of
the,
and
if
anyone
has
an
issue,
so
I
think
what
we
really
need
is.
Some
is
a
yeah.
B
I
don't
have
a
good
answer,
I'm
putting
this
in
as
a
task
for
you
then
yeah,
thank
you
and
I
I
think
it
could
be.
We
could
have
like
chair
at
okd.io
and
it
could
go
to
all
you
know
jamie
and
myself
and
and
vadim
and
we'd
all
get
notified.
It
has
to
be
confidential
too.
So
there's
there's
something.
So
I
will
ask
the
legal
team.
A
And
so
there's
basically
that
once
we
solve
that,
and
unless
we
get
any
other
request
to
to
modify
the
document,
then
it
can
go
up
on
the
website
after
the
15th
next
up
at
new
subgroup
for
operator
catalog.
A
Where
do
we?
My
first
question
is
where
we
want
to
collate
this
information.
We
were
talking
about
organizing
our
catalog
operator,
catalog
efforts
and
the
research
we
were
going
to
do
about
what
control
we
have
do.
We
want
to
do
this
in
the
hack
md,
or
do
we
want
to
do
it
as
a
discussion
item
in
the
repo
or,
where
do
folks
want
to
do
this
work.
D
Don't
we
just
need
to
have
a
a
a
call
or
a
meeting
or
a
discussion
to
find
because
I
think
from
the
couple
of
meeting
a
couple
of
discussions
we've
had
the
big
sticking
point
is:
are
we
able
to
do
anything
around
this
or
oh,
or
is
it
all
going
to
be
done
within
the
red
hat
right
right?
Is
there
anything
for
us
to
do
with
this
respect,
and
I
guess
until
we
know
that
answer.
A
A
Maybe
we
do
this
as
a
discussion
item
in
the
repo
so
that
when
people
ask
the
question
they're
already
pointing
to
that
they're
already
issues
open
around
the
like
for
the
general
question
about
the
catalog
there's
the
one:
that's
that's
that
christian
open
that
has
the
list
of
the
individual
operators,
but
do
we
have
anything,
that's
sort
of
like
a
collating
ticket
or
issue.
A
A
D
Yeah,
so
we've
been
having
a
conversation,
and
I
mean
the
the
the
gist
of
it
is
that
we
need
a
good
readme
on
the
openshift
main
repo.
It's
primarily
going
to
be
used
for
color,
coalescing
issues
and
discussions,
and
all
I
mean
the
way
that
input
it
is
or
document
worthy
content
should
be
either
in
docs.okd.io
or
okd.io
the
community
site.
So
we
want
to
move
all
sort
of
documentation
guides
from
that
repo
into
our
documentation.
D
We
sort
of
finish
that
conversation
just
this
afternoon
or
if
you're
in
this
morning,
if
you're
west
coast
based
off
so
yeah,
I
think
that
that's
the
way
to
go
so
it
does
actually
bring
up
the
question
about
technical
documentation,
because
the
only
place
that
really
is
is
the
sort
of
notes
that
vadim's
put
together
in
that
okd
repo-
and
I
I
guess
I
have
a
question
for
the
the
wider
group
is-
is
this
something
that
we
feel
that
we
want
to
do
and
want
to
support?
D
Could
I
build
okd
from
source,
for
example,
if
I
wanted
to
change
the
operator
catalog,
and
I
build
that
part
of
the
distribution
myself
from
source-
and
I
very
quickly
came
to
the
to
the
conclusion
that
I
don't
have
enough
information
with
what's
in
the
current
repose
and
the
amount
of
time
I
need
to
spend
to
figure
it
out
was
just
too
much
amount
of
spare
time.
So
I
I
think
that
that
is
a
question
that
this
brings
up
for
me.
D
If
we
start
looking
at
the
the
content
that
jamie's
the
damn
vadim
sorry
put
in
the
okd,
it
gives
a
shell
of
the
sort
of
activity
he
does
to
pull
a
release
together,
but
not
enough
to
actually
allow
somebody
to
replicate
that
work,
and
is
that
something
we
want
to
fill
out
and
build
out
that
top
technical
documentation,
and
so
somebody
could
effectively
go
to
github
and
build
okd
from
scratch.
I
don't
know
if
that's
even
feasible,
I
know
there's
a
lot
of
infrastructure
within
red
hat
that
is
used
to
do
that
build.
D
C
Yeah,
I
think
he
raised
a
bunch
of
really
good
questions
like
I
guess
I
would
say
that
in
principle,
if
we're
claiming
to
be
supporting
open
source,
then
it
should
be
possible
for
an
interested
third
party
to
build
it
from
the
source.
C
C
At
the
point
that
red
hat
was
an
independent
company,
they
always
supported
open
source,
and
I
haven't
heard
that
changing
on
paper
anyway,
since
they
were
required
by
ibm.
C
So
I'm
guessing
that
that
still
is
the
case
at
least
somewhere
in
red
hat
and
the
the
issue
of
whether
or
not
it
is
feasible
to
do
that
or
if
there
are
things
that
are
completely
tied
to
internal
rhythm
structure
that
are
impossible
to
duplicate
outside.
That's
really
a
red
hat
question
that
we
can't
answer,
although
we
could
ask,
but
but
I
think
that
that
would
be
worth.
C
I,
I
guess,
trying
to
sort
of
you
know,
answer
the
question
one
way
or
the
other,
given
that
it
would
be
a
desirable
thing
to
be
able
to
do.
C
You
have
to
build
from
source
and
the
I
guess
in
yeah
this
is
sort
of
going
back.
You
know
to
you,
know,
sort
of
the
new
foundations,
and
you
know
richard
stallman,
all
those
sorts
of
things,
but
the
the
the
basis
of
trust
is
that
you
can.
C
A
A
A
They
do
whatever
else
to
fill
in
those
gaps
you
know
so
having
documentation
up
to
that
point
is
good,
and
I
also
think
it's
important,
because
you
know-
and
I've
mentioned
this
before
even
early
on
having
vedim-
be
the
single
sort
of
like
everything
resting
on
vadim
shoulders
is
probably
not
a
great
idea
for
a
community
project
right,
and
I
know
that
they
have
now
moved
things
under.
So
okd
is
like
an
official
upstream
now,
but
that
still
doesn't
change
it.
A
B
Yeah,
it
would
be
wonderful
for
someone
external
to
have.
You
know
that
a
capability
and
at
some
point
vadim,
will
get
promoted
out
of
that
position,
hopefully
for
his
career,
and
we
will
have
to
retrain
somebody
else
and
so
anything
we
can
do
to
document
it
better,
even
if
it
is
a
red
hat
or
that
we
slot
back
in
not
that
he.
You
know
not,
that
he's
not
getting
promoted
recent
soon.
But
you
know
that
happens.
It's
part
of
the
process
here,
so
the
better
documentation.
B
A
D
So
I
think
what
we
need
to
do
and
again
I
look
for
suggestions.
How
we
do
this.
We
do
need
to
pull
together.
That
community
of
I
think,
exclusively
red
hat
is
at
the
minute
that
have
that
knowledge
to
create
a
technical
documentation
section
within
the
okidi.io
and,
as
I
say,
we're
going
to
move
it
out
of
the
repo
as
we
as
you
transition.
The
okadi.io
repo,
I
think,
what's
there
is,
is
a
useful
insight,
but
it's
not
sufficient
if
anybody
wanted
to
go
and
do
that
and
and
make
use
of
that
information.
D
So
I
I
think
now
I
know
that
we
had
the
the
document
work
sessions
in
the
past,
where
we
had
like
a
hack
day
or
whatever.
D
I
don't
know
whether
we
do
that
we
we
try
and
do
it
just
by
asking
for
volunteers
or
contributions,
and
even
if
it's
just
bullet
points
and
and
this
team
then
takes
on
the
job
of
turning
it
into
pros
and
and
tidying
it
up.
But
I
think
it's
going
to
have
to
come
from
initially
the
red
hat
people,
because
they
are
the
only
ones
that
have
the
knowledge.
As
far
as
I'm
aware,
in
terms
of
how
all
this
works
and
what
are
the
missing
pieces
and.
B
So
I
have
a
call
once
a
week
with
chris
alfonso,
who
is
that
runs
the
engineering
managers,
the
engineers,
what
I
I'll
bring
it
up
with
him
this
week
or
I'll
just
reach
out
to
him
right
now
and
ask
him,
maybe
because
I
don't
want
to
burden
vadim
anymore,
but
maybe,
if
there's
a
new
engineer
that
is,
could
go
through.
Can
you
pop
the
in
the
chat,
the
url
to
what's
there
now?
B
So
I
have
that,
and
I
could
just
send
an
email
to
chris
alfonso
and
ask
him
if
there's
a
newbie
or
someone
that
can
shadow
him
and
then
and
and
see
if
we
can
get
some
red
hatters
to
do
that
before
we
like
try
and
set
up
a
hackathon
to
hack
on
it
first
and
see
what
what
chris
comes
up
with,
because
chris
he
may
have
somebody
already
that
he's
in
training
or
whatever.
D
D
That
actually
tells
talks
about
the
os
tree
type
stuff,
and
there
is
something
in
the
readme
in
in
the
main
read
me,
which
just
talk
a
little
bit
about,
but
it
it's
all
within
that
one
repo,
the
okd
main
repo.
A
D
Yeah-
and
this
is
one
of
the
problems
that
when
once
you
start
at
the
okie,
do
you
mean
repo
will
actually
work
out
what
you
need
to
build
it,
and
it's
how
many
of
these
other
repos
within
the
oak
within
the
open
shift
organization,
and
there
are
623
of
them
by
the
way
which
of
those
623s?
D
Do
I
actually
need
to
start
looking
at
to
work
out
how
I
do
all
this
stuff?
How
do
they
interlink
and
and
you
shouldn't
get
that
it's
a
problem?
That's
too
big
for
one
person
just
to
actually
sit
through
in
in
their
spare
time.
C
So
and
probably
some
of
them
like
the
some
of
this
may
go
back
to
ocp,
because
you
know,
if
there's
a
cont,
an
operator
that
okd
uses
which
isn't
changed,
then
there
isn't
going
to
be
any
okd.
C
C
Yeah,
because
you
know
there
are
other
sort
of
mega
projects
like
if
you
look
at
wildfly,
then
you
know
that
application
server
is
tons
of
modules,
but
there
is
a
sort
of
master
make
file
that
goes
through
and
and
builds
everything
and
you
know
that's
sort
of
a
technology
like
a
prop,
maybe
an
ocp
issue
rather
than
an
okd
issue.
But
again
I
don't
know
like
I.
I
look
at
it,
but
it's
been
about
a
year
and
I
got
stopped
pretty
instantaneously.
C
D
Yeah,
I
think
we
both
have
the
same
experience,
so
I'm
happy
to
help
coordinate,
but
I
just
don't
have
the
the
technical
knowledge
to
actually
do
this,
but
I
I
actually
do
think
we
do
need
a
technical
section
which
explores
some
of
this,
and
I
think
this
will
then
also
feed
into
the
operator
discussion,
because
it
may
be
that
red
hat
will
do
and
through
through
their
sort
of
engineering
that
their
product
they
will
produce
something.
B
So
can
I
just
ask
for
a
cleric.
I
just
want
to
make
sure
I'm
asking
chris
alfonso
for
the
right
thing
here,
because
I
hear
two
words
that
I
in
my
brain
and
it's
is
the
build
process
for
building
the
release,
is
one
whole
thing
that
isn't
really
well
documented
and
then
the
insulin
when
you
want
to
go
and
install
it
on
some
target
cloud
or
hardware.
Those
are
two
separate
tracks,
and
so,
when
I
was
asking
about
the
link
there,
the
link
goes.
It's
all
intertwined,
interlinked.
D
B
The
documentation
so
yes
prioritizing
that
the
build
process
first
and
then
the
install
or.
A
A
A
way
we
can
approach
this,
so
let
me
let
me
sort
of
I
reached
out
to
vadim
and
he
gave
me
the
ur.
I
was
trying
to
find
the
right
repo
and
I
found
it.
I
put
the
link
in
the
meeting
notes.
We
don't
necessarily
have
to
get
any
external
people
involved.
Yet
what
we
can
do
is
have
a
day
where
we
go
through
that
repo
and
go
through
the
machine
content
process.
There.
A
I've
actually
gone
through
those
scripts
before
I
didn't
document
what
I
found
or
how
it
all
works,
but
that
is
the
stuff
that
puts
okd
specific
content
onto
a
cluster
and
everything
else
then
comes
from
openshift.
So
what
my
suggestion
would
be
is
before
we
even
get
anyone
else
involved.
Let's
ourselves,
those
of
us
who
are
interested
in
the
engineering
part
go
through
this
together
and
write
up
some
notes.
So
we
better
understand
what
we're
talking
about
to
ask
the
right
questions
of
other
people.
A
That's
that's
it
right
there
and
if
you
look
at
there's
the
overlays
and
the
manifests
are
sort
of
the
key
points
of
to
look
at
right
and
then
it
actually
shows
you
where
the
fedora
core
os
gets
built
using
the
assembler
there,
and
so
this
repo
has
it
all.
Actually,
okay
in
terms
of
okay,.
D
But,
but
just
just
to
go
back
to
your
to
your
question
and
I
I
think
the
the
install
we've
got
covered
because
we've
already
got
the
guides
and
we've
got
the
official
install
within
the
docks.
So
I
think
the
install
we
have
largely
got
covered.
There
may
be
a
slightly
different
if
you
build
it
yourself.
I
don't
know
whether
we
actually
create
the
right
assets
to
plug
into
that
process,
but
I
think
that
that
one,
I
see
as
a
we've
largely
got
that
covered
in
the
okay.
D
The
there
is
some
of
that
content
in
the
in
the
okd
and
that's
overlap,
and
I
think
most
of
it's
out
of
date.
It's
been
superseded
with
the
work
that
el
nico
did
in
the
okd.io
and
what
we
don't
have
anywhere
other
than
what's
in
the
okd
is
the
technical
documentation
which
is
about
building
and
customizing
a
release
of
okd.
D
B
No,
so
if
we
set
up
a
time,
maybe
we
can
bring
this
up
at
the
next
next
week's
meeting
jamie
to
review
the
this
machine
os
repo
and
make
sure
that
it's
sufficient
and
maybe
the
read,
needs
a
little
deeper.
I'm
happy
to
host
it
a
separate
meeting
for
whomever
and
and
do
that.
B
So
if
we
can
add
it
to
the
agenda
next
week
and
see
if,
if
you
think
that's
right
and
then
in
my
weekly
meeting
with
chris
alfonso
and
a
few
other
folks,
I
will
see
if
I
can
just
plant
the
seed
and
see
if
there
are
red
hat.
If
there
is
a
backup
plan
for
vedim
and
who
those
people
are,
who
might
come
and
and
be
part
of
that
as
well.
B
A
B
Can
I
just
I'm
just
going
to
ask
one
question:
michael
burke,
who's
been
listening
in
quietly
here.
Is
there
any
section
of
the
ocp
documentation
that
is
about
building
from
scratch.
B
A
All
right:
well,
let's
move
on
now
to
presentation
template.
Does
anyone
need
to
diane
just
for
clarity?
Does
anyone
need
to
weigh
in
on
the
okd
presentation
template
like
we
can
just.
B
Do
whatever
we
want
you
can
you
know
as
long
as
you
are
using
the
right
logo
and
you
don't
change,
I
think
the
message
the
tagline
you
can
make
it
as
cartoony
or
high-tech
or
matrix-like
or
whatever
you
want
yeah
in.
B
A
All
right,
let's
put
a
due
date
of
the
meeting
of
the
23rd
for
folks
to
look
at
sandra's
template,
and
then
we
will
decide
at
that
point
to
sort
of
sign
off
on
it
as
version
1.0
and
then
version
it
from
then
from
then
forth.
That's
work
and
the
I
guess
the
thing
is
is
so
is
this
something
we
would
want
to
store
in
git
or
just
keep
it
as
a
google
presentation
or.
A
Yeah
sandro
mentioned
that,
like
apparently.
A
C
A
B
C
Because
I
guess
I'm
just
saying
that
if
we
can't,
if
nobody
can
actually
see
it,
it's
going
to
be
sort
of
hard.
A
But
I
mean
ultimately
we'll
want
to
work
out
the
the
access
issue
and
the
versioning.
Do
we
want
to
keep
it
as
a
google
presentation
and
just
keep
you
know,
because
you
can
look
at
versions
in
the
version
history
and
rely
on
that?
Is
that
safe
are
folks
comfortable
with
that?
Or
would
you
rather
something
more
tightly
controlled?
What
do
folks
think.
D
If
somebody
wants
to
use
it
or
they're
more
likely
to
use
it
on
the
laptops
or
from
google
docs,
I
mean
when
you
do
presentations.
Do
you
trust
google
docs
to
be
there
and
available
at
the
conference
center,
giving
a
lot
of
conference?
Wi-Fi,
isn't
always
the
most
reliable,
because
I'm
guessing
the
end
of
the
day.
This
is
going
to
be
used
to
give
presentations,
whether
we're
standing
based
at
a
conference
or
a
virtual
conference.
So.
F
A
All
right,
and
so
now
again
so
the
by
the
23rd
any
types
of
changes
that
you
want
to
that
basic
template.
Let
us
know,
and
then
we
also
should
off
of
that
template
and
maybe
off
of
that
version
that
was
floating
around
of
like
a
full
presentation,
come
up
with,
like
the
basic
okd
presentation
about
what
it
is,
what
it
does
and
stuff
like
that.
That's
down
the
road,
though
I'm
sure,
because
someone's
gonna
have
to
do
that
work.
A
Okay
issues
hold
sight
into
the
new
repo,
well
we're
sort
of
discussing
that
now
in
terms
of
the
the
technical
stuff.
Well,
no
I
I
should
update
that
ticket,
though
probably
with
discussions
from
today.
A
D
B
D
B
D
B
If
this
yeah,
I
haven't
even
tried
yet
so
I
will
endeavor
to
do
that
too
as
well
and
see
that
I
haven't
so
when
when
did
it
get
set
up,
and
what
is
the
url
to
it
is
that
in
the
meeting
notes
and.
B
B
Okay,
we'll
go
back
and
take
a
peek
but
yeah.
I
I
don't
know.
Is
there
an
admin
for
the
matrix
that
you
sounds
like
such
a
strange
thing
to
say
if.
A
You
actually
go
to
the
link
there
in
our
current
meeting
notes.
If
you
go
to
that
github
issue,
there
is
a
link
to
it
within
there.
A
A
Yeah
well,
let's
play
with
it
and
see
what
benefit
it
adds
or
detraction
that
it
adds
we're
not
publicizing
it
all.
Yet,
let's
see
if
we
can
get
some
of
us
in
there
and
play
around
and
see
I'm
not
that
familiar
with
matrix
myself,
so
it'd
be
nice
to
get
in
and
just
play
around
and
see
what
we
can
do.
B
Yeah,
I'm
all
for
playing
with
new
toys
and,
seeing
you
know
if
this
is
going
to
take
off
it
may
be.
Our
just-
are
linked
to
the
fedora
core
os
conversations
too.
So
because
I
think
they're
reluctant
to
use
slack
so
which
for
all
kinds
of
good
reasons,.
A
Okay,
next
up
is
so
I
talked
about
the
the
security
liaison
requests.
We
talked
about
like
trying
to
get
someone
to
volunteer,
to
help
us
with
collate
security,
stuff
and
and
maybe
write
something
up
that
we
can
provide
the
community
since
there's
lots
of
security
issues
popping
up.
I
have
a
link
to
my
just
a
very
simple
one.
A
If
folks
want
to
go
ahead
and
put
comments
in
there,
then
we'll
sign
off
on
it
in
the
next
couple
days.
Async.
This
also
has
the
issue
of
who
do
they
contact?
Who
do
we
tell
them
to
send
an
email
to
what?
What?
What
are
people's
thoughts
on
this
diane?
Are
you
saying
that
we
don't
want
to
for,
under
any
circumstances,
try
to
get
ok
email
as
a
thing.
B
B
That
yet
I
just
while
you
were
talking,
I
sent
an
email
to
the
legal
team
to
ask
them
what
the
what
the
advice
was
on.
Who
should
receive
those
things
because
they
do.
There
is
some
confidentiality
stuff,
yes
for
the
code
of
conduct,
so
we
can.
B
We
can
figure
out
if
we
can
create
a
okay
dot,
io
mail,
server
somewhere,
but
let's,
let's
get
the
code
to
contact
one
done
the
security
one
I
think
we
already
have
has
for
security,
but
it's
a
different,
a
different
question
for
security,
because
it's
since
it's
not
a
supported
product
by
red
hat.
A
Well,
no,
but
this
is
this
is
who
do
they
contact
to
get
to
the
working
group
to
let
them
know
that
they're
interested
in
being
like
a
little
doing,
some
liaison
volunteer
work,
so
this
is
the
other.
This
is
incoming
to
us.
For
someone
to
say
hey.
This
will
be
for
other
volunteer
things
that
we
send
stuff
out
asking
for
right.
B
I
don't
have
a
great
answer
for
you
at
the
moment.
Okay,
that's
why
I
set
up
the
google
group
so
that
we
would
have
a
way
to
get
contacted
yeah.
B
A
C
You
have
to
either,
I
guess,
create
an
account
or
use.
You
know.
Google
or
50
000
other
things
with
sso,
and
then
you
have
to
create
a
username
and.
F
So
I'm
not
sure
if
it
will
fit
because,
for
example,
for
example,
innovate
we
are
requiring
to
be
registered
on
irc
as
well.
So
you
still
need
to
be
registered
somewhere.
A
B
It's
it's
six
of
one
half
a
dozen
of
another
they're
gonna
either
have
to
join
fedora
or
join
our
google
group,
which
is
what
I
think
personally
that
joining
the
google
group
is
more
transparent
and
more
open
than
you
know.
Kick
me
if
I'm
wrong,
then
joining
fedora
and
creating
a
fedora
account.
It's
a
lighter
ask
to
ask
people
to
join
the
google
group
than
to
sign
up
for
discord
or
matrix
or
slack
or
anything
else.
It's
it
was
at
the
time
the
lightest
ask.
I
could
do.
B
A
A
There's
the
get
ops
event
tomorrow
at
what
is
it
noon?
Eastern
noon,
eastern
9
a.m,.
B
A
B
Significant
amount
of
times
yes,
okay
cool,
then
I
will
make
sure
we
capture
that
and
reuse
that
content
and
get
that
up
there
somewhere.
It's
on
the
side,
so
cool
thanks.
A
All
right!
Well,
that
brings
us
down
to
the
end
of
the
meeting.
Folks,
we've
got
our
task
list
there
I'll
send
a
little
reminder
of
the
task
list
out-
probably
next
beginning
of
next
week,
just
so
that
folks
can
get
refreshed
on
what
needs
to
be
done.
Any
last-minute
comments
or
questions
before
we
break
for
the
day.
C
C
There's
some
old
openshift
three
books,
that
sort
of
are
o'reilly
books,
that
red
hat
gives
you
free
pdfs
to
or
something
like
that
and
the
one
of
the
menu
it
was,
I
think,
by
shipley
and
company,
and
it
seemed
like
it
would
be
not
that
much
work
and
useful
to
update
them
to
okd.
B
B
C
B
That
offline,
because
I
think
that's
a
really
great
idea
and
figure
out
how
to
do
that
and
since
you're
in
canada
and
nearby,
we
might
be
able
to
collaborate
on
that
in
real
time.
B
That
would
be
very
cool
to
do
something
like
that.
The
the
one
thing
I'll
say-
and
I
then
we're
going
to
run
out
of
time
to
say
getting
a
book
published-
is
an
expensive
endeavor.
So
if
we
did
it
as
an
open
book
that
was
just
available
online,
a
community
hosted
thing
that
would
probably
where
we
do
it.
We
will
probably
never
be
given
or
find
the
money
to
publish
an
actual
hard
copy
book
that
is
a
marketing,
endeavor
and
cost.
B
I
I
was
just
in
a
review
of
that
and
it's
redonkulous
how
much
they
charge
o'reilly
to
print
a
book,
so
aspirations
of
having
an
isbn
number
and
a
hard
copy
are
limited
so,
but
we'll
see
all
right.
Thank
you,
everybody
for
taking
the
time
while
I
was
away
and-
and
I
will
catch
up
with
everybody,
but
let's
get
that
okd
book
out
there,
brian.
That
would
be.