►
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
Okd
working
group
documentation,
subgroup
meeting
for
june
14th
of
2022,
and
if
you
do
not
have
a
link
to
the
agenda,
I
can
drop
it
in
the
channel.
Please
put
your
name
to.
Let
us
know
that
you
were
here
and
take
a
moment
to
look
over
the
agenda
and
see
if
there's
anything,
that's
been
missed.
Basically,
a
lot
of
copy
and
paste
from
the
last
meeting,
just
because
folks
have
been
so
busy.
A
And
let's
throw
over
to
you
brian
for
technical
documentation,
stuff
and
then
I
have
a
question
for
you
that
I
added
to
to
that
item.
B
Obviously
the
conversation
at
the
last
general
group,
when
we
potentially
going
to
add
a
second
os
I've
been
looking
at
what
implication
that
has
I've
also
been
looking
at,
which
goes
to
our
of
our
pre-meeting
chat,
is
to
how
easy
it
is
to
join
the
community,
and
I
listened
to
a
a
talk.
No
I'm
not
sure
whether
it
was
an
internal
company
talk
or
an
external
one.
B
I
need
to
go
find
it,
but
they
were
talking
about
what
makes
a
good
open
source
community
and
one
of
the
factors
of
the
really
successful
ones
is
the
ease
of
boarding
ease
of
getting
into
the
community.
If
you
have
to
struggle,
then
you
get
the
die-hards
that
really
want
to
be.
There
will
join
but
you're
not
going
to
get
people
with
a
general
interest
to
come
and
start
participating
and
becoming
active
member
and-
and
I
think
I
think
we
need
to
look
at
that
because,
as
just
say,
we
we
can't
build
easily.
B
So
I
am
looking
at
what
are
the
options,
so
I've
actually
just
put
a
pause
on
what
I
was
going
to
do
and
I'm
just
trying
to
think
more
strategically.
Where
do
we
want
to
get
to
the
documentation,
and
I
I
think
we
do
want
to
get
to
a
point
where
somebody
can
build,
and
even
maybe
to
the
point
where
we
have
the
scripts
or
the
githubs
setup
that
they
can
just
import
with
a
very
easy
way
of
this
is
how
you
can
get
started.
B
This
is
how
you
can
do
a
build
with
almost
zero
learning
curve.
So
I
think
that's
where
we
want
to
get
to
the
challenge
is
how
do
we
get
there
in
a
way
that
would
work
for
both
fedora
and
centos
streams?
So
so
that's
what
I've
been
looking
at,
so
I've
been
looking
at
things
just
like.
B
Is
there
an
easy
way
to
do
that
with
play
strategy,
where
we've
got
the
internal
images?
There
are
a
couple
of
technologies
that
we
could
use,
whether
it's
a
whether
it's
a
hook
mutating
hook
or
whether
it
is
using
the
the
cryo
going
and
figuring
the
cryo
mirror.
B
With
the
tag
thing,
I
think
we
have
to
put
a
machine
set
config
or
something
in
there.
The
the
configuration
only
does
the
the
hashes
at
the
mirror
at
the
minute,
so
until
version
412.,
so
I've
been
looking
at
things
like
that.
Can
we
actually
get
a
generic
pipeline
tecton
pipeline
going?
I've
also
been
looking
at.
B
B
But
could
we
then
build
something
in
our
in
our
repo
when
we
have
the
repo
that
says
import
this
and
you
get
an
a
build
pipeline
and
just
plug
in
the
name
of
the
component?
You
want
to
build,
or
something
like
that,
so
I've
been
doing
a
lot
of
exploring
around,
hopefully
with
the
idea
of
coming
up
with
a
proposal
of
saying
this
is
what
we
want
as
a
a
sort
of
no
hassle
getting
started
or
building
your
own
and
rather
than
just
having
to
go.
B
I
know
mike
mentioned
it
that
maybe
we
can
actually
try
and
get
a
standardized
approach
across
the
repos,
because
I've
also
been
looking
at
what
are
the
images
and
I
was
shocked
at
how
many
base
images
how
many
different
base
images
now
I
know
the
pro
system
does
a
replace,
so
they
actually
don't
build
from
those.
But
if
you
look
at
the
state
of
the
repos
there's
a
huge
number
of
of
base
images
where
they
just
haven't
been
updated
because
they're
not
used
for
active
builds,
so
none
of
the
maintainers
have
been
looking.
B
So
I
think,
there's
there's
a
set
of
actions
like
that
where
we
can
go
and
maybe
do
raise
issues
or
do
pull
requests
onto
the
red
hat
repose
and
suggest
that
they
change
the
base
image
and
come
up
with
the
standard
of
doing
that.
So
maybe
get
getting
some
of
the
red
hatches
to
push
that
internally
within
the
community
as
well.
So
that's
what
I've
been
looking
at,
so
I've
sort
of
stopped,
adding
new
content
and
I've
really
just
taken
a
step
back.
B
A
So
one
thing
I
want
to
ask
is:
how
do
we,
how
do
we
get
people
beforehand
to
participate
in
the
group?
How
can
we,
as
the
documentation,
subgroup,
get
people
interested
in
writing
some
of
these
docs
and
contributing
towards
writing
some
of
the
pipelines
that
will
you
know,
swap
out
images
and
build
and
and
whatnot?
Because
that's
to
me
there's
the
three
of
us.
You
know
yeah
and
michael
when
he
has
time
right.
B
C
B
D
Working
group
is
a
doom
if
you're
trying
to
attract
technical
people
because
remember
it
started.
It
started
out
as
the
for
about
one
meeting
as
the
operators
working
group
and
then
changed
the
focus,
and
some
of
us
are
too
dumb
to
leave.
You
know,
but
the
really
it's
not
just
the
documentation,
because
we
we
do.
You
know
like
the
the
stuff
that
brian
is
now
getting
into,
is
more
digging
into
technical
things.
B
C
So
you,
the
other,
the
piece
of
that
and
I
think
you
guys
are
hitting
on
something
good
is
like.
If
you
look
at
kubernetes,
they
have
the
contributor
sig,
which
is
all
about
onboarding
people,
and
you
know
creating
letters
for
contributions
and
and
that
stuff.
So
I
think
we're
on
to
something
here
too.
C
The
other
thing
is
once
you,
if
you
do,
do
the
proposal
that
you're
doing
and
if
we
had
a
template
for
what
people,
what
we
wanted
to
ask
of
people
like
if
we
had
a
template
that
we
could
give
to
cern
and
say
here,
tell
us
about
your
build
process.
Put
it
into
this
templated
form
and
structure.
We
could
do
that
just
once
and
have
one
good
example:
we've
done
in
the
past
these
these
hackathons
they're
other
community
building
tools
like
incentivizing
people
to
to
share
their
stuff.
C
C
The
the
other
thing
is
to
figure
out
how
to
get
main
other
maintainers
external
maintainers
on.
Maybe
we
call
it
documentation,
but
on
these
get
offs
patterns
or
the
build
patterns
and
and
different
things,
so
that
they're
actually
getting
to
be
a
contributor
and
getting
to
be
a
maintainer
in
this.
You
know
you
know
we
could.
C
I
don't
know
what
you
want
to
call
the
group
or
how
you
want
to
structure
it,
but
once
we
perhaps
see
the
proposal
and
we
had
a
template
because
I
know
jamie
you're,
you
know
and
everybody's
the
hot
stuff
is
get
offs
and
get
ups
patterns,
and
things
like
that,
if
we
you
know,
we
could
do
some
interesting
things
around
that
before
deploying
okd
and
building
okd,
and
I
I
think
you
we
could
host
a
hackathon
we
did
that
a
while
ago
and
that
got
that
get
garnered
me
without
templating,
without
a
pattern
that
we
wanted.
C
People
to
fit
into
for
our
documentation
needs
a
whole
lot
of
really
good
insights
into
deploying
and
testing
on
different
platforms,
and
we
haven't
done
anything
like
that
in
a
long
time
and
yeah.
You
know
so
maybe
the
outcome
of
this
and
then
to
do
get
some
marketing
behind
it.
You
know
to
get
some
real
marketing
appeal,
you
know,
especially
if
we
call
the
get
offs
or
I
don't
know
pick
a
good
name.
B
C
B
If
this
is
something
that
you
feel
is
is
useful
or
valuable.
Come
join,
come
help.
A
Here's
my
impression,
let
me
let
me
know
if
you
folks
think
this
is
right.
The
people
who
are
really
deep
and
have
the
access
to
resources
to
spin
up
in
aws
etc
are
the
ones
who
are
the
most
busy,
the
ones
who
would
have
the
time
and
who
are
sort
of
the
passionate
folks
starting
out
in
this
don't
have
the
resources.
Generally,
you
know
they're
trying
to
do
snow
or
something
like.
A
Would
it
be
beneficial
for
us
to
find
the
resources
to
get
someone
to
volunteer
the
resources
for
there
to
be
an
okd
cluster
that
folks
can
access
who
want
to
participate,
participate
play
around
and
or
whatever
I
mean,
that
gets
into
the
whole
issues
of
okay.
You'd
have
to
administer
it
and
whatever,
but
so
many
people
seem
to
be
stuck
on
being
able
to
to
run
it
a
single
note
or
whatever,
because
they
don't
have
the
resources
but
they're
interested
in
okay
right.
B
You
have
to
be
a
restricted
user
and
the
benefit
for
me
of
okd
is
without
having
to
either
break
the
openshift,
license
agreement
and
running
a
hooky
version
of
openshift.
I
have
a
legal
runtime
environment
which
is
very
similar
to
openshift
of
the
same
as
openshift
humanity
changes,
but
I
have
complete
control.
I
can
trash
it.
I
can.
I
can
do
the
what
ifs
I
can
really
get
under
the
cover.
D
To
go
ahead
well,
no
one
of
thoughts
came
to
me
is
that,
in
terms
of
sort
of
a
hackathon
with
a
catchy
name,
is
the
phrase
closing
the
gaps.
D
Okay,
because,
like
we
do
have
these
gaps
between
ocp
and
okd,
which
everybody
is
totally
aware
of
and
with
all
the
yeah
sort
of
the
red
hat,
you
know,
watch
what's
cool
this
time.
You
know
with
you
know,
edison
and
company
they're,
always
using
ocp,
and
that's
probably
like
those
videos
would
be
a
common
place
where
people
are
going
to
have
heard
of
us
and
then
they
might
come
looking
for
okay.
How
can
they
do
that
yeah
and
they
want
to
get
beyond
the
mini
cube
demos.
A
Right
so
to
circle
around
this,
though,
like
do
we
need
to
really
beef
up
the
snow,
documentation
and
tutorials.
We
need
something.
If
we,
if
we're
saying
okay
cluster,
is
a
bad
idea.
Public
cluster
is
about
it
or
managed
cluster,
providing
that
is
a
bad
idea.
We
need
to
make
the
entrance
to
running
okd
in
general.
B
I
mean
we
talked
about
that
one
about
a
month
ago
where-
and
I
think
there
was
something
on
red
hut
tv
where
there
was
a
refocus
on
core
ready
containers,
I'm
hoping
that
does
produce
a
a
viable
laptop
experience
which
still
has
the
ui.
Maybe
not
all
the
security
features,
but
it
still
has
the
ui
and
the
dev
experience,
but
it
will
run
on
a
16,
gig
laptop.
A
Okay,
but
one
of
the
things
that
we
talked
about
as
a
group
recently
was:
we
can't
support
carc
right
because
we
don't
have
enough
people
to
we've
been
talking
about.
Oh
yeah,
we're
going
to
do
a
dock
or
we're
going
to
do
whatever,
and
we
haven't
really
been
able
to
do.
We
hop
on
that
thread.
That's
in
the
discussion
between
the
crc
folks.
A
I
don't
know
if
you
saw
that
it's
like
who
is
on
that
there's
a
thread:
that's
like
multiple
people,
some
of
them
involved
with
crc
and
some
of
them
okd
talking
about
this
this
gap.
That's
there!
A
Do
we
hop
on
there
and
push
on
the
crc
folks
to
get
an
okd
version
out
of
them
directly
right,
because
they
were
talking
about
there's
some
tricks
that
they
could
do
and
whatever
it
seems
to
me
that,
then,
if
we
can't
do
it
ourselves,
then
we
need
to
put
the
pressure
on
to
get
a
version
put
out
with
the
ocp.
You
know.
At
the
same
time,
the
ocp.
B
C
C
The
following
week,
we'll
have
a
deeper
dive.
Timothy
will
be
back
and
we
can
ask
more
questions,
but
I
don't
think
you
can
ask
the
crc
question
out
of
timothy
but
yeah.
Hopefully
a
few
others
will
fabiano
and
a
few
folks
from
the
team
that
are
working
on
this
sprint.
Yeah,
okay,
dion
s,
cost
will
be
there.
B
I
mean,
I
think
something
like
the
red
hat
sandbox
or
the
openshift
sandbox
or
okd
would
help
those
that
want
it
as
a
user
experience,
rather
than
an
admin
or
or
a
contributor
experience.
So
I
think
they
would
be
married
in
trying
to
replicate
say,
like
the
openshift
sandbox
environment,
for
a
user
community
that
wanted
dev.
But
then
you
asked
the
question.
Well,
if
it's
the
same
dev
experience,
what
are
we
getting.
B
C
Is
that
well,
if
that's,
if
that's
the
case,
just
go
use
the
sandbox,
because
the
sandbox
is
there
and
that's
the
experience.
I
think
what
you
said
earlier,
brian,
about
wanting
to
be
able
to
get
under
the
hood
and
crash,
looks
and
break
things
and
stuff
like
that
that
that's
different
than
a
sandbox
or
a
developer.
C
Up
deploy
an
application,
that's
how
do
I
break
things?
Rebuild
them
get
to
be
a
good
disadmin
for
this
platform
and
understand.
You
know
how
things
break
and
rebuild
themselves
and
and
all
that
kind
of
goodness,
and
and
that's
the
experience
that
we
want
to
get,
and
you
can't
get
that
from
any
of
the
try
before
you
buy
stuff
for
ocp.
C
Really,
no
crc,
you
know
I'd,
say
yes,
but
it's
it's
not
real.
I
don't
know
it
doesn't
feel
like
to
me
like
a
real.
I
use
the
word
sysadmin.
So
just
shoot
me
if
I'm
using
the
wrong
thing,
but
it
doesn't
feel
like
that
that
experience
for
me
and
the
thing
that
that
would
make
me
really
thrilled
is
if
like
on
aws,
there
was
all
the
images
and
everything
you
need
to
deploy
okd
with
either
f
costs.
C
Everything
was
there
and
you
could
just
go
to
a
menu
and
say:
okay,
I
want
to
deploy
this
on
and
here's
my
credit
card
or
here's,
my
university's
account
and
I'm
gonna
spin
it
up
and
then
you
get
to
play,
but
and
that
would
be
something
that
we
don't
really
do
for
our
product.
It
might
be
something
you
know
that
week.
D
Well,
that
would
be
something
actually
diane,
where
a
strip
down
version
would
help
a
lot,
because,
with
the
full
version,
it's
quite
chatty,
and
it's
doing
all
these
monitoring
things
and
you
know
so
you're
gonna
have
to
update
your
credit
card.
You
know
max
balance
pretty
quickly,
which
is
not
great
for
students.
A
I
did
an
okd
in
aws
and
just
for
testing
what
a
base
okd
install
was,
and
it
was
it
ends
up
costing
about
500
a
month.
You
know
what
I
mean
or
460,
or
something.
A
That's
like
that's,
like
you
know,
it's
three
control,
plane
and
three
workers.
You
know,
that's
the
that's
the
default
and
just
to
clarify,
I
wasn't
thinking
of
creating
a
a
dev
workspace
for
just
deploying
applications,
but
instead
like
for
doing
pipelines
for
building
components
of
of
okd
and
whatnot.
So
not
that
so
more,
like
working
group
members
having
a
space
to
do
some
of
these
pipeline
things,
we've
talked
about
in
terms
of.
A
C
So
that
that
was
the
conversation
that
I
was
trying
to
have
with
people
like
brian
cook
and
marcel
hild
and
karsten
wade
who's
the
community
manager
for
operate
first
there
in
theory,
is
a
way
for
us
to
get
that
kind
of
access
to
have
a
cluster
running
okd
on
the
what's
called
called
mass
open
cloud.
It's
I
call
it
boston
university,
their
cloud
that
we
have
access
to
that
we
could
have
a
build
pipelines.
C
We
could
do
all
of
that
stuff
for
it
and-
and
I
think
that's
the
conversation
I'd
like
to
pursue
for
the
working
group
members.
So
maybe
you
know
not
the
general
public
yet
like,
but
just
for
the
you
know
you.
You
belong
to
the
working
group
and
you
know
you
you
get
access
to.
I
don't
know
what
the
gatekeeping
would
be,
but
there
is
and
and
they're
keen
to
do
it.
C
You
know
I
I'm
I'm
keen
to
get
them
on
a
call
with
all
of
us
to
really
walk
through
what
the
logistics
of
that
looks
like
and
so
maybe
reaching
out
to,
and
brian
cook
is
really
the
technical
person
working
on
improving
the
build
processes
for
openshift
for
ocp
and
tangentially
he's
associated
with
the
operate
first
team,
because
they're
all
everybody's
agenda,
but
the
operate
first
guys
have
a
sl
a
separate
agenda
where
they
want
to
do
other
things
and
build
patterns
and
pipeline
stuff.
C
But
I
those
people
I
think
if
we
can
get
them
engaged
with
us,
are
keen
to
work
with
us
because
they
think
of
us
as
a
really
big
community
and
a
big
big.
You
know
it's
all
in
perspective
right
and
also
almost,
I
think,
as
a
way
to
justify
operate.
First
participation.
C
You
know
existing
as
an
as
an
initiative,
so
we
have
an
advantage
there
because
we
have
some
real
needs
and
the
people
who
do
mass
open
cloud
are
all
openshift
people,
they're,
very
ocp,
and
so
I
think,
there's
an
opportunity
there.
So
I
didn't
try.
I
don't
think
I
tried
to
pull
in
brian
cook
and
the
operate
first,
people
for
the
next
okd
working
group,
but
perhaps
we
should
you
think.
C
A
So
move
on
in
here,
brian
moving
back
to
technical
documentation,
is
there
anything
that
you
can
glean
from
what
jack
henschel
was
talking
about
from
cern
last
week
to
inform
our
build
docs
or
can
should
we
meet
with
him
and
maybe
pick
his
brain
in
a
one
on
one
or
two
on
one
yeah.
B
B
Where
did
you
struggle
in
building
okd
and
just
how
much
did
they
build
and
customize?
Because
I
got,
I
got
the
impression
that
for
some
of
it
it
wasn't
a
lot
of
change.
A
B
A
B
So
how
was
that
like
two
containers,
or
was
it
20
containers
or
and
what
what
challenges
did
they
hit
and
was
it
guess,
work
or
was?
Did
they
go
through
a
process
to
actually
figure
out
what
the
the
containers
substitutions
were,
or
do
they
just?
It
was
a
pure
guesswork,
so
yeah,
I
think,
it'd
be
really
worth
while
having
that
conversation
with
them.
A
Do
we
want
to
set
something
up?
That's
more
informal,
then,
like
just
a
quick
meeting
and
yes,
maybe
come
with
some.
B
A
All
right:
well,
let's,
let's
reach
out
to
him,
I'm
happy
to
reach
out
to
him
and
just
say
what
would
be
your
preferred
method
of
having
a
more
technical
conversation
and
is
he
the
the
appropriate
person
there
might
be
someone
who's
more
did
more
of
the
actual,
hands-on
okay,
I
will
add
that
as
a
task
for
myself,
so
amy
reach
out
to
jack.
D
Okay,
can
I
ask
you
questions
related
to
what
we've
been
talking
about,
so
the
partially?
It's
not
like.
I
remember
you
know
with
with
version
three
cluster
up
and
so
on,
which
sort
of
got
lost
with
version
four,
and
when
I'm
looking
at
why
things
are
so
big.
D
A
lot
of
the
stuff
seems
to
be
things
that
are
required
for
an
operational
system
that
you
don't
really
need
for
a
dev
system
in
terms
of
reliability
and
also
monitoring,
and
then
what's
so
you
know
you
need
to
pull
some
of
that
stuff
up
out.
But
if
you
try
and
do
that,
what
you
immediately
will
find
is
that
there's
massive
dependencies
so
like
if
you
try
and
pull
out
the
monitoring
all
of
a
sudden,
your
cluster,
your
console
doesn't
work.
D
So
then,
what
I
wonder
on
a
technical
standpoint
is
whether
or
not
people
have
actually
looked
at
the
sort
of
dependency
graph
and
if
they've
looked
at
the
the
issue
of
how
coupled
everything
is
to
everything
else
and
whether
or
not
you
can
decouple
it
so
that
you
can
actually
pull
out
parts
that
you
don't
need
and
have
the
rest
of
it
work.
D
No,
I
was
gonna
say,
and
it
may
be
that
if
you're
going
to
try
and
experiment
on
the
outside,
then
you
know
maybe
that's
post
building
it
the
way
it
is
so,
but
I
I
think
that
that
was
one
of
the
things
I
was
hoping
that
we
would
get
into
when
we
had
this
very
brief
crc
working
group
of
how
do
we
slim
it
down.
B
And-
and
I
thought
that's
what
red
hat
were
looking
at,
because
when,
when
they
did
the
410
launch
streams,
they
did
talk
about
reinvigorated
effort
around
code,
ready
containers.
C
I
think
they've
even
rebranded
it
and
we
keep
calling
it
crc,
but
there's
another
name,
and
it's
escaping
my
brain
right
now,
but
they
have
been
re-looking
at
it.
But
I
not
in
the
context
of
okay,
they
haven't
been
a
conversation
but
yeah
and
spinning
it
down.
B
D
Yeah
is
anybody
diane
looking
at
like
what
would
be
the
benefits
of
microsoft
versus
the
15
other
kubernetes
alternatives?
You
know
like
kubernetes
and
docker,
or
you
know,
mini
cube
or
all
those
things.
A
C
Yeah,
I
also
think
that
microshift
is
serving
a
different
master.
It's
serving
the
edge
computing
telco
automotive,
reaching
to
the
very
edges
of
devices
and
things
and
needs.
You
know
it
needs
bits
and
pieces
of
kubernetes,
but
not
all
of
it.
Just
like
you're
describing
there
I
so,
but
I
think
we
have
different
needs
for
different
bits
and
pieces,
especially
the
developer
experience
pieces.
C
You
know
the
slenderman
version
of
okd
as
a
community
if
we
wanted
to
especially
if
we
owned
our
build
process
just
like
if
we
could
get
on,
I
mean
this
is
the
I
was
shutting
down.
So
I
could
log
in
and
see
if
I
could
get
everybody
to
talk
about
the
opera.
C
C
I
know
we
keep
looking
back
at
the
mothership
at
red
hat,
to
do
something
for
a
slender,
but
it
might
be
something
we
have
we'd
have
to
hack
and
build
ourselves
pack
out
everything
you
don't
want
bruce
and
and
see
if
we
can
make
it
work
and
it
might
be
an
experiment
for
a
bunch
of
interns.
B
C
C
And
that's
that's
what
I'm
hoping
and
so
anyways
I
digress
and
I
will
I'll
go
send
that
email
and
get
the
operate
first.
People
on
the
all
next
week.
A
All
right,
let's
move
on
real
quickly,
repository
move
timeline
and
steps
doesn't
seem
like
anyone
else
has
added
anything
in
terms
of
discussion
to
that
item.
B
Well,
I
I,
I
think
that
I
think
the
big
one
is
the
okay
recall,
because
that's
where
we've
got
our
discussion
and
that's
where
everyone's
been
pointing
to
so
I
think
we're
gonna
have
to
manage
the
migration
of
that
one.
I
did
an
experiment
and
worked
out.
If
you
transfer
ownership,
then
everything
goes
with
it.
So
I
think
we
know
how
to
move
it
now,
but
it's
going
to
be
that.
B
How
do
we
manage
getting
everybody
that
we've
just
got
going
to
the
discussion
forum
there
over
to
the
new
discussion
forum,
so
so
that
that's
the
challenge
there
for
the
okd?
I
one
we
just
need
to
coordinate
with
whoever
looks
after
the
dns
right
to.
A
B
Once
a
transfer
ownership,
it
goes,
wants
to
transfer
ownership,
it'll
all
be
in
our
new
one.
So
we're
just
going
to
move
everything
that's
there
across,
but
it's
if
people
have
bookmarked
it
and
now
I
think
if
nobody
else
grabs
the
name.
Github
will
do
an
automatic
redirect
for
us
for
a
short
amount
of
time.
But
it's
it's
more
about.
A
D
A
A
All
right
moving
on,
because
we've
got
about
12
minutes,
left
survey
will
go
out
tomorrow
in
all
the
places
I'm
gonna
post
it
in,
and
let
me
see
if
I've
got
this
right.
Anyone,
let
me
know
if
I've
missed
anything
the
slack
channel
diane.
Do
you
have
control
of
the
twitter
at
least.
C
A
Can
tweet
okay,
so
the
tweet
will
go
out?
Should
we
put
a
blog
post
on
the
website
for
it.
B
C
Keep
keep
it
up
for
as
yeah
keep
keep
it
make
it
indefinite.
I
would
say,
because
we
can
just
keep
gathering
data
from
it
as
we
go.
You
know.
The
the
other
thing
is,
the
talk
that
brian
and
christian
are
going
to
give
in.
Dublin
is
going
to
be
recorded
so
brian
in
in
whatever
you
do.
Think
of
that
as
something
that's
going
to
get
embedded
into
the
okd.io
homepage.
B
C
So
as
you're
talking
the
you
know,
because
I
I
really
capture
that
content,
the
freshest
stuff
with
the
s-cos
conversation
in
it
and
get
that
on
the
home
page
as
well.
B
C
Yes,
he
just
booked
his
stuff
and
then,
when
in
london,
he's
not
going
to
go
and
what
we
might
end
up
doing
is
just
the
10-minute
sprint
version
of
what
you
guys
do
for
the
half
hour
there
and
just
have
you
on
stage
talking
about
and
basically
recruiting
again
so
think
about
it
that
in
that
way,
we've
done
both
versions.
But
I
really
would
like
the
in-depth
one
for
okay,
you
got
a
half
an
hour,
so
use
it,
and
I'm
okay.
A
Okay,
next
up
is
the.
Are
there
any
other
faq
suggestions?
I've
got
those
there,
I'm
sort
of
chipping
away
at
them.
Do.
Does
anyone
else?
Have
any
suggestions
for
frequently
asked
questions
that
we
should
ask
or
that
we
should
add
the
answers
to
anyway?
If
you
do,
please
add
that
maybe
I'll
do
a
discussion
item.
That's
like
people
can
just
throw
suggestions
into
it.
Like
okay,
here's
things,
sno
documentation,
nothing,
nothing!
I
don't
think
there's
any
more
discussion
on
that,
but.
B
I
think
that's
an
important
point
from
what
you
were
talking
about
the
first
item
at
the
minute.
We
don't
have
sno
on
the
site,
yeah
and
I
think
that's
really
important,
because
that
means
that
we
nobody
can
do
a
reduced
resource
install
of
okd
now.
B
Well,
let
me
let's
see
so
I
think,
and
ask
of
the
main
meeting
is
somebody
that
understands
the
new
process.
Yeah
needs
to
write
the
instructions
and
I'll
say
michael's
on
and
needs
to
work
with,
michael
to
get
those
instructions
into
the
docs.
A
Okay,
well,
I
will
add
that
to
something
to
ask
at
the
main
meeting
depersonalizing
home
lab
documentation,
are
we
just
going
to
do?
We
want
to
just
go
and
change
these,
or
do
we
want
to
reach
out
to
the
demon
shree?
I
haven't
seen
shri
at
the
last
meeting,
or
so
now.
D
C
B
Well,
I
I
think
I
mean
I
I'd
like
to
know
what
value
they
provide,
not
not
not
in
a
nasty
way,
but
because,
when
I
see
the
word
guide,
I
think
it's
going
to
guide
me
to
do
something
or
help
me
do
something.
These
are
literally
example.
Installs
they're
not
guides
in
any
way
they
are
just.
This
is
what
you
can
do
with
okd.
It's
an
example
of
an
install,
so
maybe.
C
Create
another
heading
that
is
example
installs
and
then,
but
also
take
the
de-personalize
it
a
little
bit
and
you
can
keep
in
in
the
heading
and
just
keep
it.
You
know
who
the
author
is
and
everything
like
that,
but
that,
if
that
I'd
be
more
comfortable
with
that
as
well-
and
this
goes
to
like
getting
a
template
for
people
to
use
and
reuse
too
so.
But
I
think
I
I
I
think
example:
installs
is
a
good
thing
and
then
we
could
go
get.
B
I
was
going
to
say,
there's
also
some
an
issue
with
with
currency,
because
I
think
I
think
it's
for
deans,
but
he
went
and
did
a
hacked
single
note
in
store
before
single
note
install
was
there
because
these
wrote
these
are
version
four
five
or
four
six.
B
C
D
C
Have
them
there
so
that
we
don't
lose
the
legacy
and
then
make
a
request
at
the
next
meeting
to
see
if
there's
anybody
who's
willing
to
take
vadim's
document
document
his
example
and
try
it
again
right
now
that
we
have
snow
and
then
make
and
and
and
but
again
we
need
the
template.
We
need
a
little
bit
of
better
turn
and
look
for
a
volunteer
to
take
what
vadim
did
and
what
sri
did
and
turn
it
updated.
C
B
B
C
B
Because,
even
with
the
doctor
io,
it
was
taking
me
through
the
configuration-
and
I
didn't
know
the
vocabulary,
I
didn't
know
the
terminology,
I
look
at
it
now
and
it
makes
sense
to
me,
but
the
very
first
time
I
did
there.
I
I
just
didn't,
I
didn't
know
the
vocabulary,
I
didn't
know
the
domain.
I
didn't
know
what
it
was
asking
me
for.
So
I
went
and
found
a
youtube
video
and
it
showed
me
exactly
what
I
needed
to
do.
B
I
could
pause
the
video
and
say:
oh
that's
what
that
value
means,
and
so
I
I
think
it
is
worth
just
look
going
back
and
maybe
having
a
workshop.
If
we
can
get
enough
people
four
or
five
people
and
let's
do
a
two
three
hour
workshop
and
let's
define
what
a
guide
needs
to
be
for
each
for
a
platform,
create
a
template
and
then
we
can
go
and
ask
for
volunteers.
B
A
Brian,
this
is
actually
this
predates
you,
but
we
did
that.
What
was
it
two
years
ago
or
yeah?
I
think
it
was
or
a
year
and
a
half
ago.
Maybe
it
was
like,
maybe
the
last
winter.
We
did
something
like
that
and
it
actually,
this
work
that
you're
seeing
was
sort
of
spawned
out
of
that
and
the
guides
were
sort
of
spawned
out
of
that,
and
that
was
the
effort
when
we
started
to
sort
of
migrate.
A
C
I
I
would
love
to
do
something
in
august
yeah,
because
that
would
give
us
enough
time
to
publicize
it.
So
if
you
want
to
look
at
your
calendars,
including
michael
burke,
because
it
would
be
lovely
to
have
a
documentation
person
on
you
know
around
and
see
what
dates
and
just
let
me
know-
and
maybe
think
about
it
by
next
week,
and
we
could
socialize
a
date
and
I'm
we're
I'm
happy
to
use
blue
jeans
or
zoom
zoom.
C
You
can
have
breakout
rooms
and
stuff
like
that
and
host
it,
but
we
can
even
do
it
using
not
hack,
md
pop-in
again
because
and
then
just
just
have
four
tracks
or
you
know,
whatever
one
big
track
and
then
spawn
up
new
tracks
as
we
need
them
and
hop
in
because
then
we
then
we'd
also
capture
their
names
and
everything
else
for
future
recruitment.
Hop-In
was.
C
I'd
be
happy
to
do
that.
Just
pick
a
date.
I
will
look
I'll
just
say
that
I'm
going
to
be
busy
mid
july
so
august.
I
love
I'm
moving
my
mother
to
canada
slowly
but
surely,
and
hopefully
by
august
things
will
calm
down
so
that
we'll
get
that.
I
I'd
love
to
do
that.
I
I'd
be
happy
to
do
that
and
start
to
do
a
cadence
of
things
along
that
line.
C
C
15
ish,
but
that's
theory
and
practice
is
something
else
so
we'll
hear
we
can
ask
timothy,
but
I
think
right
after
that,
so
it
would
be
nice
to
have
a
hackathon
on
explaining
how
to
you
know
the
differences
if
any
and
how
to
get
it
and
and
do
something
simplistically
around
that
to
see
who
does
it,
and
I
haven't
heard
anyways
now
we're
in
the
end
of
our
hour.
A
Yeah,
so
we're
at
the
end
of
the
hour
what
I
actually
had
s
costs
on
as
an
agenda
item
I'll
bump
it
to
next
documentation.
Meeting
the
gist
is
gonna,
be
we
should
probably
have
a
conversation
of.
How
do
we
talk
to
the
community
about
it
right
and-
and
I
don't
think
we
have
enough
details
yet
to
be
able
to
talk
to
the
community
about
it,
but
we're
going
to
want
to.
C
And
just
so,
you
know
what
I
have
asked
is
michelle
crickey
and
fabiano,
and
that
team
to
write
a
blog
and
with
timothy
and
steven
about
the
coming
of
s
cause
not
in
relationship
with
okd
and
then
a
follow-on
one
in
relationship
with
that
so
and
maybe
highlight
the
work
that
the
the
folks
who
are
in
the
sprint
to
the
engineers
and
get
them
to
come.
C
My
goal
is
fabiano,
probably
will
show
up
again
next
week,
I'm
hoping
he
drags
luigi
and
there's
a
few
other
folks
on
that
team
that
are
doing
that
sprint.
I
really
need
them
just
to
get
engaged
with
the
okd
working
group
on
an
ongoing
basis.
I
think
the
more
we
love
them
for
what
they're
doing
the
more
likely
they'll
want
to
stay
invested
in
and
it
will
they'll
be
invested
in
it
for
a
while.
C
But
again
I
don't
want
to
burn
people
out
like
we've
done
with
vadim,
so
all
the
support
and
love
we
can
show
them
for
the
work
that
they've
done,
and
this
is
probably
their
first
attempt
at
doing
anything
with
okd
the
guys
that
and
gals
that
are
working
on
it.
C
C
A
Takes
awesome
all
right
well
we're
over
time.
So
let's
call
it
a
call.
The
meeting
now
and
I'll
see
most
of
you
all
next
week.