►
From YouTube: 2022-11-29 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
All
right
welcome
to
the
community
meeting
for
November
29
2022,
so
we'll
get
started
by
talking
about
the
Milestones.
We've
got.
First
of
all,
we
had.
We
had
a
holiday
last
week,
Thanksgiving.
So
not
a
lot
of
changes
since
our
last
community
meeting,
but
we'll
talk
through
it,
1.9
I'd
say
no
updates
there,
no
planned
releases
I
think
we're
we've
been
pretty
stable
with
1.9,
so
just
to
double
check.
I
haven't
looked
at
the
the
boards
here
today,
but
yeah,
nothing
in
1.9,
that's
blocking
or
anything
so
I
think
1.9
is
looking
fine.
A
1.10
then
we
let
me
go
back
to
this.
We
did
have
the
1.10.6
release
a
couple
of
Thursdays
ago.
The
release
notes
are
there
for
that
one
and
then
our
bi-weekly
Cadence
would
be
this
coming.
Thursday
December
1st
for
the
1.10.7
I
think
that'll
be
fine
to
go
ahead
and
keep
that
we
may
not
have
as
many
changes
this
release.
A
B
Not
really
I
would
just
I
would
love
to
get
the
about
no
for
1.10.
No,
nothing.
A
A
1.11
then
yeah
1.11
I,
haven't
put
a
more
specific
date
in
there.
I'll
try
and
do
that
by
the
next
meeting,
but
yeah
I
still
plan
for
mid-January,
which
that's
coming
up
already
in
six
weeks
or
so
so
we
should
get
a
date
on
the
board
there
and
yeah
1.11
is
feeling
like
not
some
real
major
changes.
It'll
just
be
kind
of
our
next
incremental
release
and
trying
to
get
some
of
these
work
items
done.
A
Well.
Honestly,
we've
been
we've,
we've
did
it
we're
tending
more
and
more
to
I
feel
like
backboard
new
features
even
to
our
existing
releases
like
1.10
right
now,
since
they're
not
tending
to
be
big
or
breaking
or
risky
features
since
we're
a
stable
project,
but
yep
1.11
we'll
see
what
I
need
to
talk
about
what
big
things
we
need
to
consider.
But,
honestly,
there's
not
a
lot
that
we've
been
talking
about
as
far
as
features
but
Alexander
did
you
have
something
for
1.11,
then.
B
Yeah
I
I
hope
that
we
can
get
the
automated
help
doc
generation
there
or,
like
the
at
least
automatic
helmetics
generation
that
so
here
is
working
on
merge
till
then,
and
maybe
even
the
crd
documentation
that
it's
automatically
generated
in
for
1211
right
now,
no
would
be
cool
to
have
yes
resolved.
Finally,
I
guess.
A
B
Yeah,
like
the
main,
maybe
do
I
guess
already
talk
a
little
bit
about
that.
The
main
aspect
is
really
adjusted
instead
of
having
it
in
the
documentation
file
and
in
the
crd
that
we
just
only
have
the
documentation
on
the
crds
themselves
and
the
types
that
go
file
probably
and
then
have
that
auto
generated
out
into
like
well
into
the
actual
markdown
for
the
documentation
and
yeah.
B
So
we
don't
forget
about
updating.
It's
like
I,
don't
want
to
say
every
time
but,
like
you
know,
if
we
don't
forget
to
update
it
once
in
a
while,
then
with
a
new
Option
or
something.
But
it's
just
done
like
a
oh
see,
I
failed.
Why
oh
I
forgot
to
Auto,
generate
the
documentation
and
committed
as
well
and.
C
A
Yeah,
that
sounds
good
I
mean
maybe
we
could
update,
make
build
to
also
generate
the
Dark
Cloud
of
access,
but
we've
already
got
separate
commands
for
things
that,
like
this
I,
think
it's
fine.
If
it's
just
separate
because
I
think
make
crds,
for
example,
is
automatically
part
of
just
to
make
build.
B
Yeah
I
think
might
like
I,
don't
know
how
Sarah
plans
to
implement
it
at
the
moment,
but
I
think
it'll
probably
be
either
like
a
separate
check
for
the
docs
check.
That's
where
currently,
the
home
docs
check
is
being
added
with
the
just
like
a
get
div
exit
code
flag,
so
it
exits
with
like
well
non-zero
code.
If
there's
changes
so
at
least
for
the
documentation
there
I
think.
Let's
talk
about
that
again
or
like
in
the
ticket,
then
when
suhair
is
ready
with
his
PR
I
would
say
right
now.
B
Basically,
the
same
implies
that,
like
the
pr
for
the
helm
docs
is,
there
looks
good
from
my
site,
at
least
like
obviously
someone
else.
Please
take
a
look
as
well
as
it's
somewhere
from
Kerr
and
for
the
CID
generation.
We
still
he's
still
working
on
that
plr.
So.
A
Checkup
as
well
so
in
the
community
topics,
there's
just
one
more
bullet.
We
haven't
already
talked
about
just
point
out
yesterday:
I
got
an
email
with
the
main
trainer.
Maintainer
track
is
open
for
kubecon
in
Amsterdam
for
April
by
the
end
of
January.
We
need
to
submit
that.
As
far
as
deciding
do
we
speak
in
person.
Should
we
try
virtual
I'm,
hoping
it's
not
virtual
and
I'm
hoping
we
can
just
be
there
yeah
tired
of
these
virtual
events
personally,
so
looking
forward
to
to
being
there
in
prison
and
I?
B
Hi,
it's
yeah
I
would
put
it
like
maybe
six
hours
at
Max,
which
is
might
sound
like
much,
but
it's
like
reasonable,
like
especially
for
that
distance.
C
C
B
After
my
flight
to
the
US,
also
like
I'm
I
I
enjoyed
the
trains
to
the
airport
more
than
a
flight
in
the
end,
because,
like
it's,
it's
like
this,
oh
I
want
to
go
to
like
grab
a
snack
and
I'll
just
stand
up
and
go
to
the
board
Bistro
to
the
onboard
Bistro
or
restaurant.
Depending
on
what
kind
of
train
it
is
and
well.
C
A
A
B
A
B
Let's
talk
about
it
at
the
next
community
meeting
I
got
some
more
feedback
as
well
from
someone
like,
for
example,
changing
the
name
to
be
a
bit
more,
let's
say
shot
on
a
little
bit
more
to
the
point
and
all
on
like
yeah.
Let's
talk
about
it
in
the
next
community
meeting
I'll
have
something
more
ready,
then.
A
Sure
sounds
good
alrighty
with
that,
then
oh
there's
an
accident,
but
I
just
want
to
mention
to
follow
up
on
what
was
it?
Oh
for
slack,
we
talked
about
last
time.
We
should
get
so
I
added
all
the
maintainers
as
workspace
admins.
So
if
people
hopefully
everybody
all,
the
maintainers
should
be
able
to
like
delete
messages
that
are
duplicate
or
whatever
workspace.
A
Admins
shouldn't
need
to
use
that
power
very
often,
but
sometimes
it's
useful
and
then
Alexander
I
also
need
to
get
back
to
you
on
being
able
to
add
more
users
to
the
GitHub
repo,
oh
I,
yeah
I
looked
at
that
before
the
holidays
and
I
need
to
get
back
to
that.
So
I
didn't
quite
figured
out
well
so
far,
it
looks
like
the
only
way
to
do
it
is
to
the
owners
of
the
organization.
Can
only
add
people
to
the
org
so.
A
A
Yeah
I
mean
you
know
the
GitHub,
just
the
GitHub
GitHub
access
right,
they're
kind
of
fine-grained
but
doesn't
seem
like
they
do.
What
we
want,
neither
so
just
I
mean
just
adding
people
to
the
org
doesn't
seem
like
that
big
of
a
permission
right.
That
would
require
owners,
but
that's
what
it's
that's,
how
effective?