►
From YouTube: 2022-07-26 Rook Community Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Let
me
share
my
screen
and
then
we'll
get
going
here.
Let's
see,
why
am
I
feeling
challenged
with
starting
the
screen
share?
Let's
see,
share
screen
there.
It
is
okay.
A
A
If
I
look
at
the
project
board
here,
we
do
have
a
few
things.
That
would
still
be
nice
to
get
into
the
1.9
release,
but
I
don't
think
any
of
them
are
blocking
for
today
and
we've
got
a
number
of
fixes
in
their
lease
from
the
last
couple
of
weeks.
So
go
ahead
today,
unless
anyone
else
has
something
that
they
want
to
get
in
for
now,.
A
Yep,
so
I
think
we're
good
for
today
the
maybe
just
to
comment
on
the
nf
nfs
test.
Yeah
it
was
disabled.
It
would
be
nice
to
get
that
enabled
again
to
sign
direction
so
yeah
I
haven't
seen
any
progress
on
that
lately.
B
A
B
I
thought
reaction
had
some
other
some
other
things
come
up,
but
I
can
I
can
ping
him
and
see
if
he's
able
to
resume
work
on
that
and
if
not,
I
can
probably
take
it
over
as
well.
B
B
B
I
think
I
think
this
is
the
pr
that
ends
up
finding.
What
might
have
been
an
issue
I
can
post
that.
Well,
I
can
put
it
in
my
meeting
as
well.
A
Sounds
good,
so
these
other
things.
I
don't
think
we
need
to
talk
through
those
issues.
In
the
to-do
column,
I
moved
a
couple
out
of
the
2d
column
here
into
the
1.10
milestone,
so
we're
yeah
we're
about
that
point
where
it's
we'll
probably
focus
more
on
1.10,
but
we
can
still,
of
course,
backward
to
1.9
as
needed.
B
A
The
1.10
release
then
coming
up
so
previously
we
hadn't
set
any
dates
around
the
release.
This
morning
I
just
put
in
some
tentative
dates.
I
I
guess
I'd
propose
for
the
release
so
usually
a
week
before
the
final
release.
We
have
the
beta
release
where
we
create
the
branch,
make
sure
the
ci's
all
working
run,
tests
upgrade
and
all
of
that,
so
I'm
going
to
propose
august
11th
and
then
a
week
later,
the
18th
to
target
the
release.
B
B
A
A
B
A
Right
so
on
to
the
community
topics
and
questions.
Today,
a
few
things
to
mention.
Last
week
we
talked
about
telemetry
that
had
been
enabled
in
rook.
That
requires
like
1.9.6
of
rook
and
cef17.2.1,
as
I
recall,
and
we
decided
to
go
ahead
and
document
that
in
the
quick
start
guide
so
just
to
just
for
posterity
sake.
Here's
this
new
section
and
the
quick
start
guide
on
telemetry,
really
all
you
have
to
do
is
go
to
the
toolbox
and
they
set
telemetry
on
and
then
you'll
get
the
reporting.
A
A
Nope
all
right
moving
on
then
just
want
to
make
sure
the
communities
where
that
17.2.2
release
of
seth
that
came
out
last
week,
the
manager,
consistently
crashes
and
rook
deployments,
so
we're
recommending
not
to
upgrade
the
1722
and
just
if,
if
you're
on,
if
you're
on
quincy
releases,
v17
just
stay
on
2.1
until
we
can
get
that
fix,
nsf
release
got
more
details
in
that
issue.
Link
there.
B
A
And
the
last
item
here
just
pointing
out
if
anybody's
interested
in
the
history
of
rook
or
some
more
general
background,
I
did
an
interview
today
with
kbe
insider
and
there's
a
link
to
that
interview.
I
can't
stand
watching
myself,
so
I
won't
ever
watch
it
again,
but
if
anybody
else
is
interested.