►
From YouTube: OKD Working Group Meeting 11-09-2021
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
All
right
so
starting
out
this
is
the
okd
working
group
meeting
for
november
9th
of
2021.
A
Don't
forget
to
put
your
name
in
the
attendees
list,
so
we
know
here
and
we'll
do
a
quick
agenda
reviews
everything
in
the
agenda
anything
that
people
want
to
change
your
ad
while
we've
got
it
up
before
we
get
started.
A
Going
once
going
twice
all
right,
then,
let's
jump
into
it
with
release
updates
with
the
dean.
B
So
this
weekend
we
were
supposed
to
have
a
480
release,
but
it's
kind
of
postponed
because
the
rebase
to
121.5
of
kubernetes
and
cubelet
and
things
didn't
land
just
yet
so
it's
gonna
land
today,
so
we're
gonna
skip
this
release
because
first
of
all
we
didn't
have
much
to
fix
and
for
eight
second
issue
on
the
table
is
for
nine,
four,
nine,
nine,
at
least
already
for
at
least
the
testing,
and
we
would
need
to
switch
249
stable.
B
Eventually,
I
think
the
safest
way
would
be
releasing
for
eight
this
weekend
and
releasing
for
nine
is
stable
the
the
weekend
after
that
gives
us
quite
enough
time
to
test
for
nine
night
lease
that
also
approximately
at
this
time,
ocp
upgrades
would
be
allowed
from
four
eight
to
four
nine.
I
think
they
are
allowed
now,
but
probably
blocked
by
something.
At
least.
We
don't
see
a
huge
volume
of
that
when
that
starts
happening,
we
would
have
quite
a
good
results
of
the
health
of
or
nine
and
okay
safe
to
move.
B
Next
on,
mustafa
has
fixed
the
storage
test
in
kubernetes.
All
cherry
picks
have
landed
in
master,
122
and
121
the
branches
we
care
about.
Basically,
they
didn't
land
in
micro
releases
yet,
but
once
they
do
openshift
with
rebates
on
top
of
them,
we'll
get
these
fixes
and
we
would
finally
be
able
to
unpin
this
linux
policy
package,
which
has
been
causing
us
quite
a
lot
of
problems.
Rather,
it's
been
way
too
secure
and
another
problem
has
been
found
in
410.
B
Rather,
it
affects
technically
it
affects
all
of
the
installations,
but
it's
most
visible
on
410,
because
aws
m6
families
using
a
nitro
hypervisor
and
it's
crashing
on
latest
kernel
514.
B
So
you
won't
be
able
to
launch
latest
door
across
once
you
launch
four
nine
or
four
eight
using
this.
It
would
crash
in
for
m6,
but
m5
would
work
and
unfortunately,
410
has
moved
to
m6
by
default,
because
these
machines
are
actually
cheaper
and
so
far
the
mitigation
is
that
we
rolled
back
the
channel
to
5
for
scene.
You'd
still
have
to
use
an
older
fedora
cross
due
to
this
issue
and
some
more
previous
ones,
but
in
the
end
it
starts
correctly.
So
that's
what
we're
testing
right
now.
B
It's
a
it
appears
to
be
an
actual
either
aws
issue
or
upstream,
most
likely
upstream
journal
issues
so
not
much.
We
can
do
until
we
wait
for
the
fix
to
land.
I
believe
the
the
interested
part
isn't
notified
identified
the
upstream
bug
report.
That's
what
we'll
do
if
this
issue
won't
get
resolved.
B
B
Yeah,
that's
pretty
much,
that's
pretty
much
it.
I
don't
think.
There's
been
a
new
changes
but
again
fedora
grows
testing.
The
bell
has
moved
to
35
and
I
would
really
be
interested
to
try
this
out.
But
the
kernel
problem
is
at
this
point
blocking
it
once
we
would
push
it
away
and
would
be
able
to
fix
the
linux
policy.
Pin
we
would
rebase
for
10
to
f35
and
check
out
the
results.
A
Any
questions
or
comments
for
vadim
in
the
okd
updates
any
release
updates.
A
All
right,
seeing
nothing
we'll
move
on
to
the
fcos
updates
with
timothy.
C
C
So
I've
put
the
link
into
the
document
with
a
link
to
the
tracker
of
where
we
are
right
now,
and
so
next
has
been
on
fedora
35
for
a
while.
Now,
testing
is
either
just
right
now
or
just
going
to
be
in
fedor
35
in
next
one.
I
don't
remember,
and
then
we
move
on
to
next
to
stable
in
two
weeks.
C
So
testing
in
is
not
right
now,
so
it
should
be
in
yes
right
in
the
next
release,
which
so
with
the
either
base
with
with
major
releases
we've
we
shipped
to
a
new
way
of
doing
the
release.
This
is
replaced
so
we
kind
of
accelerate
the
pace,
so
the
documentation.
C
Some
will
link
to
the
ticket
if
I
can
find
again
so
that
we
do
the
updates
a
little
bit
faster
during
the
move
to
fedora
35
but
yeah.
So
essentially,
it's
coming
really
really
soon
to
a
testing
release
near
you
and
then
two
weeks
next,
two
weeks
after
to
stable
release.
So
hopefully
that
will
help
okd
a
lot
because
a
lot
of
the
hacks
you
currently
have
will
you
will
be
able
to
drop
them,
so
that
should
have
things
yeah.
C
That's
on
the
front
of
the
on
this
point,
and
then
we
have
a
second
one,
which
is
kind
of
like
an
update
of
what
we
discussed
next
the
previous
time
about
oh,
but
the
previous
time
was
two
times
ago,
where
we're
working
on
creating
a
way
to
create
layers
for
coral
systems.
So
like
for
federal
chorus,
you
could
have
your
base
system
and
then
overlay
on
top
much
more
in
a
much
more
easier
way
all
the
packages
you
need,
for
example,
for
okd
and
the
enhancement
is
posted
there.
C
I've
put
the
link
the
progress
we
were
processing
quite
rapidly
toward
that
and
support
so
should
should
be
available
shortly.
At
least
for
testing
it
out
and
until
it's
fully
integrated
into
the
mco
and
everything
and
we
get
fully
it,
we
get
full
all
the
whole
thing
available
and
yeah.
C
Essentially
right
now,
I
think
we've
got
like
the
ability
to
do
local
tools
from
containers
and
upgrading
layers
and
everything
so,
like
the
basics
should
work,
and
hopefully
this
will
like
really
help
for
okd
to
to
with
the
with
issues
and
everything
avoid
the
rebuilds
and
enable
overriding
packages
when
needed,
offering
a
variety
of
things,
changing
config
defaults
and
everything
so
that,
essentially,
you
just
use
the
base
fedrak
first
image
and
then
do
the
the
tweaks
on
top
and
yeah.
And
that's
the
two
main
items
for
me
today
for
this
week.
A
Right
excellent,
excellent.
Moving
on
to
the
docs
updates,
with
brian
and
driti
actually
and.
D
Okay,
yes,
so
the
the
new
documentation
system
is
now
live.
So
if
you
go
look,
it
looks
a
little
bit
different
and
it's
now
based
on
mk
dock.
So
it's
pure
lockdown,
so
pretty
easy
to
update.
If
you
want
to
I've
now
put
the
instructions
for
if
you
want
to
go
and
update
the
docs,
and
we
can
either
do
it
within
the
container
and
if
you've
got
che
or
call
ready
workspaces
on
a
cluster,
you
can
edit
it
in
the
cluster
or
you
can
install
local
tooling.
D
So
that's
all
set
up.
Let
me
know
if
you
need
any
help
or
any
issues,
but
that's
all
good
to
go,
and
there
is
one
issue
that
I
think
might
be
worth
talking
in
this
group
and
and
it's
an
issue
raised
by
sandro.
I
know
sandra
was
on
so
I
don't
know
whether
you
want
to
actually
pick
this
up
and
talk
about
it.
E
E
A
Don't
just
raising
the
topic
yeah!
No,
that's
a
great
great
question.
We
don't
currently
have
anyone
volunteering
to
scan
the
security
related
security
issues.
I
think
that's
a
great
idea.
Is
there
anyone
in
anyone
currently
in
attendance
that
would
be
interested
in
doing
that
leg.
Work
like
every
two
weeks
or
so
basically,
looking
for
stuff
that
would
impact
okd
so
that
we
can.
A
Let
users
know
that
we
are
aware
of
these
things
and
if
it's
something
upstream,
then
we
can
say
hey
we're
waiting
for
this
fix
up
stream.
If
it's
something
that
we
can
mitigate
in
the
few
cases
where
we
can,
we
can
talk
about
that.
So
everyone
want
to
be
our
security
liaison.
A
F
If
nothing
else,
you
know,
as
far
as
the
open
shift
code
base
itself
goes
because
it's
the
same.
It's
the
same
images
same
code
base,
those
cves.
You
really
could
track
from
the
red
hat
site,
fedora
core
os
on
the
other-
that
that's
a
different
matter.
Any
anything
there
are
likely
being
reported
to
fedora,
but
we
don't
have
that.
We
don't
have
anything.
That's
tying!
Those
together.
G
There's
one
exception
to
that:
charo.
Occasionally
we
or
that
occasionally,
like
you,
know,
semi-regularly
we
have
cvs
come
in
that
we
don't
disclose
through
bugzilla,
so
they're
private,
bugs
that
only
red
hatters
could
see,
but
they
might
affect
pieces
of
openshift
that
those
cves
would
not
be
discoverable
by
people
outside
of
red
hat
and
I
think,
even
for
red
hatters
there's,
probably
some
document
we
signed
that
says
we
won't
expose
those
things.
So
I
think
that's
probably
the
one
area
where
this
might
be
difficult.
C
C
Yeah,
okay,
so
on
the
point
of
contact,
I'm
looking
for
the
exact
urls
and
things,
but
essentially
for
all
corres
repos.
We
have
this
one
security
policy
on
github,
which
I
think
we
can
apply
to
okd,
which
by
default,
says
contact
red
hat
security
team
and
will
take
care
of
that
and
yeah.
I
don't
have
I'm
looking
for
the
exact
link
where
this
is
stored
and
all
this
is
set
up.
But
I
don't
remember
and
I'll
have
to
find
that
again.
G
I
Considering
that
okd
and
ocp
are
actually
identical,
I
hope
they're
okay
with
it,
because
if
they're
not
then
there's
a
problem.
A
All
right:
well,
let's
what
we'll
do
is
as
a
task
we'll
add
the
docs
group
to
actually
come
up
with
a
security
page
that
sort
of
outlines
our
security
posture
and
then
we'll
provide
those
two
links
for
people
to
be
able
to
submit
and
get
info
in
terms
of
f
costs
and
in
terms
of
okd
and
we'll
go
from
there
and
I'll
send
something
out
over
the
working
group.
A
All
right
anything
else
on
the
topic
of
security
sandra
does
that?
Does
that
get
us
closer
to
what
you're
thinking.
A
A
Oh
okay,
then
brian
you
want
to
continue
on
with,
I
guess:
we'd
be
a
code
of
conduct
and
then
twitter
and
then
the
survey.
D
D
We're
looking
at
adding
the
code
of
conduct
taken
from
the
answer,
ansible
repo
michael,
is
adapting
that
and
we're
going
to
actually
use
that
as
our
code
of
conduct,
and
I
think
the
idea
would
be
that
that
we
could
refer
to
it
when
we
started
a
community
event
or
a
meeting.
D
We
can
actually
refer
to
that
and
it'll
be
actually
on
the
dock
side
as
well,
and
then
I
think,
as
far
as
twitter
is
going,
we're
looking
to
set
up
a
twitter
account
and
really
use
whatever
youtube
greasy
actually
set
it
up.
So
it
is
actually.
A
Okay,
yeah,
okay,
so
I
we
didn't
get
a.
We
didn't
come
up
with
a
good
background
image
yet
like
I
think
we're
using
just
something
kind
of
she's
been
handling
all
this
she's,
not
here
but
yeah.
It's
it's
up.
We
just
need
to
start
deciding
on
content,
and
so
that
we've
got
the
one
background
image
that
was
sort
of
pulled
from
like
the
website.
I
think
it
was
like
just
grabbing
the
website,
but
we
might
be
able
to
come
up
with
something
that
looks
a
little
bit
nicer.
A
It's
a
little
bit
fuzzy
but
yeah,
so
she
did
come
up
with
that
and
I
guess
the
docs
group
or
this
group.
If
you
have
any
thoughts
on
what
type
of
things
we
should
be
putting
out
over
this
like
do,
we
want
to
put
every
release
that
comes
out.
You
know,
vadim.
A
Does
that
make
sense
for
every
single
one?
That's
an
official
release
that
we,
you
know,
announced
that
through
the
twitter
announced
the
meetings
things
like
that
is
there
anything
else
that
we
would
want
to
put
through
the
twitter.
A
All
right
well
make
sure
you
follow
it
and
I
think
we'll
probably
have
it
start
following
other
people
to
sort
of
get
that
you
know
grid
going
and
we
will
start
using
it
and
then
folks
can
forward
it.
That's
the
other
thing
is
for
social
media
like
this
to
be
successful,
folks
need
to
forward
and
reshare
social
media.
So
in
this
case,
if
you
could
retweet
the
okd
tweets
when
they
start
coming
out,
that
would
be
super
helpful
because
then
that
builds
up.
A
You
know
that
social
media
grid
and
makes
those
connections
and
stuff
like
that
and
survey.
Truthy
hasn't
gotten
much
farther
on
the
survey,
but
it's
but
she's
taken
that
on
and
we'll
know
more
about
it.
I'll
touch
base
right
now.
It's
like
11
p.m,
we're
getting
close
to
11
p.m
there,
but
I'll
reach
out
to
her
and
see
where
things
are
and
crc
stuff
charo
take
it.
F
A
Are
you
getting
any
feedback
from
it?
Has
anyone
else
played
with
it.
F
Somebody
tried
to
use
the
an
earlier
version
of
the
linux,
one
that
had
a
the
the
upstream
group
made
some
changes,
so
I
had
to.
I
had
to
make
a
patch
and
push
a
new
version,
but
other
than
that,
I
I
don't
know
how
much
use
it
gets.
G
F
G
Mentioned
occasionally
the
okd
variant,
but
it's
like
maybe
once
every
couple
weeks
I'll
see
someone
talk
about
it
on
a
mailing
list,
that's
about
it.
Yeah.
F
It's
it's
just
a
url
hanging
off
of
the
okd
dot
io
and
we're
using
some
borrowed
space
on
one
of
the
fedora
servers.
So
I'd
cats
speak
of.
H
Neil,
do
you
happen
to
know
who
in
fedora
gets
logs
for
that
infrastructure?
Do
you
even
know
what
infrastructure
that
is.
I
So
dl.fedoraproject.org,
which
is
where
it
is,
is
the
download
master
server
dl
ib01,
which
is
in
the
iid
data
center
in
virginia
that
is
managed
by
fedora
infrastructure,
specifically
by
the
release
engineering
team,
so
the
access
to
that
is
controlled
exclusively
by
red
hatters.
So
someone
on
the
red
hat
side
will
have
to
talk
to
the
cpe
team.
For
those
who
don't
know,
that's
community
platform
engineering
to
talk
to
the
fedora
infrastructure
subgroup
of
cpe
about
if
we,
if
there
are
any
stats,
if
not,
if
we
can
start
collecting
any.
A
Can
we
put
that
as
a
to-do
for
either
one
of
you
to
hunt
that
down
so
to
see
if
we
can
get
some
stats
on
on
downloads
or
anything
even
remotely
letting
us
know,
I
mean
we'll,
have
the
survey?
Obviously
sorry
who
were?
Who
are
the
two
people,
so
I've
well
three
of
you
anyway,
okay
or
anybody.
H
F
H
Okay
cool,
so
let's
start
with
you
charo,
since
you
might
be
the
best
at
figuring
out
from
the
red
hat
side
who
has
access
to
that,
and
if
you
already
have
access
to
it,
you
may
have
log
access
to.
H
F
You
know
I
got
access
to
this
machine
before
I
went
to
work
for
red
hat
yeah.
This
was
back,
oh
goodness,
when
did
we?
I
guess
it
was.
F
I
Yeah,
because
the
actual
ok
d4
release
was
late
summer
of
last
year,.
I
F
A
So
does
it
make
sense
to
spin
off
the
crc
stuff
into
a
separate
meeting?
I
noticed
that's
been
added
as
an
item.
Can
someone
take
that
on
so
that
maybe
the
crc
folks
can
or
seriously
folks
I.
H
Had
volunteered
to
organize
the
meeting
last
time-
and
I
was
actually
waiting
on
you-
jamie
for
instructions
on
oh
organize,
said
meeting
that
didn't
actually
make
it
into
the
task
list
last
time.
So
that's
that's
my
bad.
I
put
it
in
the
task
list
this
time.
Okay,
great
there,
you
go
yes,
okay!
If
I,
if
I
don't
hear
from
you
in
like
a
week,
should
I.
A
H
A
H
So
I
think
the
main
two
things
that
we'd
want
from
a
from
a
crc
subgroup
to
start
with,
based
on
the
conversations
we've
had
here,
are
discussions
about
automated
builds
and
the
infra
for
them
and
then
the
larger
existential
question
of.
Does
anyone
use
this,
and
if
not,
is
it
worth
right.
H
J
H
H
J
You
because,
like
if
you,
if
you
look
at
say,
mini
cube
or
something
like
that
as
a
an
alternative
which
doesn't
have
the
same
usability,
and
you
look
at
the
resources
that
that
takes
then
that
sort
of
gives
you
a
useful
baseline
for
comparison.
H
So
yeah,
so
that's
that's!
That's
a
good
question
to
answer.
Besides
a
metric
for
anyone
using
it,
the
the
is
there
a
configuration
of
it
that
would
make
it
useful
for
people
to
use
kind
of
figuring
out
what
the
direction
of
it
should
be.
Okay,
cool!
That's
enough
of
an
agenda
to
get
started.
I
just
wanted
to
make
sure
that
that
the
things
people
wanted
that
committee
or
that
some
committee
to
do
were
actually
going
to
be
done.
F
H
Cool
okay,
so
that
that's
that's
a
bunch
of
good
stuff
that
we
can
that
we
can
cover
in
that
in
that
meeting
and
yeah,
I'm
just
saying
if
you're
looking
for
big
fish
to
fry,
you
know,
I
don't
know,
I
don't
know
what
I'm
looking
for.
I
don't
know
what
I'm
getting
myself
into,
but
that
that
looks
like
a
nice
big
fish
there
yeah.
A
All
right,
let's
move
on
to
any,
are
there
any
issues
in
the
repo
that
are
something
that
came
to
our
attention
that
we
need
to
pay
any
attention
to?
There
are
those
kernel
crashes
vadim
mentioned
that
it
looks
like
all
of
the
other
issues
are
very
old,
so
not
a
lot
of
issues.
Of
course,
kai
rimmel
posted
something
that
came
up
that
looks
like
there
is
a
must
gather
that
he
posted
about
seven
hours
ago.
A
That's
someone
that
we
may
want
to
court
actually
for
the
working
group,
he's
always
he's
actually
running
okd
in
production
and
is
always
posting
stuff.
Where
he's
finding
bugs
and
whatnot,
maybe
I'll
start
a
conversation
with
him
and
see
if
he's
interested,
because
it'd
be
cool
to
have
him
sort
of
contributing,
or
at
least
coming
on
every
once
in
a
while.
We
definitely
want
to
hit
him
up
with
this
survey.
A
Someone
mentioned
the
crc
okd
mismatch
packaging
okd
binaries
for
fedora.
I
did
not
see
that
one
come
in.
A
Yeah,
I
just
noticed
that
yeah
that
was
mike's
thing
all
right.
Well,
we
will
shelf
that
one
to
until
the
next
meeting
anything
else
in
the
discussion
items
there.
A
Yeah,
I
don't
see
anything
all
right.
Let's
move
on
a
lot
of
the
discussion
stuff.
It
seems
to
be
like
just
a
user.
A
Just
to
resolve
here,
location
of
the
main
repo
diane
is
going
to
check
with
legal.
I
need
to
actually
create
a
a
discussion
item
so
for
tasks
moving
forward
and,
if
folks
could
remind
me
or
help
me
with
this,
the
goal
is
to
create
discussion
items
for
every
task,
and
then
this
way
we
can
actually
track
that
people
are
getting
their
tasks
done
and
folks
can
talk
about
tasks
and
things
like
that
and
follow
up
on
them.
A
A
A
Yeah
so
we'll
find
out
about
moving
the
main
repo.
The
other
thing
I
want
to
talk
about
which
is
kind
of
a
a
loaded
question,
and
it
may
lead
to
a
long
discussion
or
short
discussion.
How
do
folks
feel
about
set
weeks
for
the
okd
working
group
meeting,
in
other
words,
the
first
and
third
week
of
the
month
or
the
second
and
fourth
week
of
the
month.
A
This
came
up
and
I'm
starting
to
sort
of
ease
into
participating
in
the
get
ops
working
group,
and
I
asked
the
question
there
and
it
apparently
was
something
they
were
talking
about.
But
I
think
it's
something
we
could
talk
about
here.
It
would
be
a
lot
easier
to
know
which
meeting
between
the
docs
meeting
and
this
meeting
and
be
easier
to
invite
people,
because
they'll
always
know
it'd
be
easier
for
scheduling.
I
J
Yeah,
I
I
move
mine
into
exchange
calendar
so
that
you
know
all
all
the
other
people
at
bcit
can
see
it,
and
I
don't
think
that
that's
as
flexible
as
you
know,
crone
jobs,
so
that
you
can
do
like
the
first.
You
know,
thursday
of
whatever
so
like
every
other.
You
know
like
a
repeat
every
other
week
is
something
that
is
easily
manageable
in
all
calendars.
A
So
some
people
have
scheduling
in
their
day,
jobs
that
are
the
first
and
second
week
or
the
you
know,
or
the
first
and
third
or
the
second
and
fourth
week.
Some
people
have
have
voiced
that
as
something
of
a
concern
and
then
the
other
one
is
that
in
those
weeks
where
you
don't
fall
on
the
first
and
third
or
second
and
fourth
on
that
fifth
week,
there
would
essentially
be
a
break,
and
so
people
could
breathe
a
little
bit.
But
it's
I
mean:
does
anyone
else
have
any
opinions?
A
It
sounds
like
most
folks
are
into
the
into
the
just
every
other
week
thing
and
that's,
and
that
was
the
other
thing
by
the
way,
the
other
that
was
the
impetus,
is
the
initial
impetus.
Was
me
actually
asking
the
get
ups
working
group
well,
what
week
is
this
because
it
says
every
other
week
for
their
meetings
and
I
was
like
well.
What
does
that
translate
to?
A
When
is
the
next
one
so
for
inviting
people
it's
problematic
or
for
for
posting
it
in
such
a
way
that
people
could
just
happen
upon
knowing
when
the
next
meeting
is
so,
we
would
have
to
and
mike.
I
think
you
just
posted
something
yeah
so
mike
just
posted
something
right,
putting
something
on
the
website
and
also
via
the
new
twitter
and
stuff
like
that.
I
If
fedocal
can
be
configured,
you
know
the
pedocal
setup
for
this
event
could
be
configured
with
whatever
way
you
want,
then
it's
fine,
because
it
doesn't
actually
matter
what
restrictions
everybody
else
has,
because
if
they
just
subscribe
to
the
the
live,
ical
feed
they'll
just
get
the
events
as
as
the
calendar
system
pushes
them
but
like.
If
I
have
to
make
calendar
events,
for
this
is
gonna,
be
very
there's
gonna,
be
some
gymnastics
involved,
and
I
don't
know
if
I'm
gonna
get
it
right.
F
I
On
my
personal
google
account
I
have
like
20
different
fedocal
things
imported
in
you
have
and
it
works
fine.
You
have
to
tell
it
when
you're
pulling
in
a
calendar
event
from
there,
you
have
to
grab
the
ical
link,
you
know,
so
you
go
to
that
and
say
copy
ical
link,
and
then
you
tell
google
calendar
to
subscribe
from
a
url
that
me.
That's
not
the
same
as
importing
importing
from
a
url
does
a
one-time
thing
and
then
that'll
be
wrong.
I
A
All
right
so
so
is
the
temperature
of
the
room,
then
that
folks
want
to
just
continue
with
bi-weekly,
alternating
bi-weekly.
That's
the
temperature,
okay,
that's
what
we
will
do
then,
but
don't
be
surprised
if
we
do
cancel
one
of
the
meetings
on
either
of
them
just
so
that
people
do
have
a
break.
It's
because
diana
whatever
you
burn
out.
A
Okay,
we
have
about
15
minutes,
but
we've
made
it
through
our
meeting
items.
Is
there
anything
else
that
folks
want
to
talk
about
before
we
break.
I
A
So
what
do
we?
Let's
see
we
have
december?
J
Well
sounds
like
a
plan
that
we
come
out
with
a
new
f-class
version,
major
version,
a
new
okd
major
version,
and
then
we
cancel
all
the
meetings.
At
the
same
time,
right.
A
So,
are
we
saying
the
14th
through
the
4th
no
meetings.
I
I
mean
my
pto
basically
starts
on
the
week
of
the
12th,
so
so,
after
that,
it's
just
and
and
my
pto
doesn't
end
until
after
new
year's.
So
I
I
expect,
at
least
from
my
perspective,
I'm
personally
canceling
everything
that
I'm
attending
in
that
in
those
three
last
weeks
of
december.
F
D
A
All
right
so
straw
poll
vote
for
canceling
meetings
from
december
21st
through
january
4th
raise
your
hand
or
say
I
do.
A
Okay,
does
anyone
have
an
opposing
opinion
on
this
or
a
different
perspective?
Let
me
say
different
closing
frames.
It
has
different
perspective
on
this
than
what
we've
just
anyone,
no
okay.
Now,
where
are
we
in
terms
of
actually
a
little
bit
closer
november,
are
folks,
okay,
doing
the
23rd,
because
that
would
be
our
next
one
for
november,
I'm.
B
I
B
A
All
right,
so
I
will
see
you
all
in
two
weeks
expect
your
task
list
to
be
created
as
discussion
items
and,
of
course,
if
anything
comes
up
that
you
need
to
talk
about
the
group,
you
can
use
the
slack
and
we
have
been
successful
at
making
the
the
dev
slack
channel
mostly
for
dev
questions
or
dev
discussion,
so
feel
free
to
pop
in
there
or
use
the
google
working
group.