►
From YouTube: 2022-01-11 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
the
recording
has
started-
and
this
is
the
january
11th
rook
community
meeting,
and
I
think
that
said
12th,
but
I
made
a
quick
edit
there
if
you
don't
mind
travis,
to
put
it
back
to
the
11th,
which
I
believe
is
the
current
date.
We
can.
A
After
the
meeting,
if
we
need
to-
but
yes
so,
let's
just
start
diving
into
some
of
the
upcoming
milestones,
if
we
don't
have
a
11
yet
for
1.7,
you
know
like
nothing's,
really
driving
it.
Then
I
assume
there's
not
anything
big
on
the
project
board,
also
for
worth
discussing.
A
B
A
Yep
exactly
okay,
so
we
got
a.2
out
recently
and
the
dot
three
is
coming
up:
let's
go
ahead
and
pull
up
the
board
and
talk
about
some
of
the
some
of
the
blockers
and
then
some
of
the
maybe
some
of
the
important
fixes
that
were
in
the
dot
two.
Since
we
haven't
had
a
community,
we
didn't
have
a
community
meeting
over
the
holiday
time
there,
so
maybe
catch
us
up
on
the
what
was
it
the
dot
two
release
also.
A
B
Here
we
go
yeah
yeah.
There
were
definitely
a
few
big
changes
in
that
release.
Like
we
got
a
new
crd
out
for
sub
volume
groups
to
use
with
stuff
ffs
sub
created
that
there
was,
there
were
a
couple
of
critical
fixes.
Oh
the
discover
demon
set
was
not
running
properly.
B
B
C
Yeah
this
one,
this
one
really
slips
yeah,
so.
A
And
I
assume,
there's
a
you,
know:
fair
amount
in
this
to-do
column
here
also
that
we
can
re-evaluate
and
see
if
there
are
priorities.
B
Honestly,
we
might
just
remove
from
a
specific
project
and
when
people
pick
them
up,
then
they
get
picked
up
instead
of
moving
them
release
to
release.
A
You
know
and
something
something
I
found
work
can
work
pretty
well
for
to
have
that
distinction.
Travis
is,
is
a
a
separate
column
here,
instead
of
a
single
to
do
column,
to
have
like
a
proposed
column
as
well.
That's
the
on
the
left
of
this
one.
A
So
it
could
be
a
you
know,
a
bit
of
a
parking
lot
of
things
that
people
are
interested
in
or
people
want
to
see,
so
they
can
put
it
into
that
column
and
it's
kind
of
a
you
know,
but
it's
not
necessarily
committed
to
until
it
gets
moved
into
the
to-do
column
and
it's
things
that
we
do
think
we'll
have
the
resources
for.
We
will
still
spend
time
on.
We
want
to
include
in
the
release,
but
you
can
kind
of
you
know
differentiate
between
hey.
C
C
Can
keep
the
to-do
list
and
have
some
sort
of
an
approved
for
release
column.
B
Right
well-
and
I
guess
the
approach
in
my
mind
where,
if,
if
people
don't
see
it
critical
for
release,
then
we
just
don't
add
it
to
a
specific
project.
But
if
somebody
wants
to
see
it
in
a
project,
that's
when
we
add
it
to
the
project
board
in
the
first
place.
So
I
think,
if
somebody
has
the
mindset
enough
just
to
add
the
label
for
a
project,
then
I
think
we
can
consider
it
for
the
that
release
and
it's
not
like.
We
have
a
hard
commitment
to
it
anyway.
A
What
well
yeah
yeah
and
it's
it
may
not
be
necessarily
important
to
to
classify
you
know,
which
ones
are
hard
commitments.
That's
probably
not
like
it's
you,
that's
kind
of
rare
to
do
in
any
open
source
project
that
has
limited
resources
and-
and
you
know
it's
not
necessarily
like
fully
staffed,
but
but
having
an
idea
of
what,
what
pro,
what
issues
have
interest
in
them
and
then
it
or
or
versus
which
ones
or
people
have
people
working
on
them
or
you
know
intending
to
could
be
interesting.
A
I
don't
think
it's
like
a.
I
don't
think
we're
having
massive
problems
with
this.
It's
not
like.
Oh
gosh,
like
we
can't
deal
with
the
way
we're
dealing
with
projects
anymore,
but
it's
a
possibility.
If
you
wanted
to
start
differentiating
between
things
that
have
interest
in
you
know
like
the
community
has
asked
for
them
versus
things
that
yeah,
where
the
dev
is
going
to
be
looking
at
this
and
actually
doing
something
with
it.
B
I
think,
generally,
if
people
have
interest
in
a
specific
issue
or
really
want
to
see
a
fix,
they'll
comment
on
the
issue
and
then
and
then,
if
it's,
if
someone
can
pick
it
up,
then
they
assign
they're
assigned
to
the
issue
and
we
can
see
who's
assigned
to.
If,
if
there's
no
owner
assigned,
then
that's
another
way
to
see.
Well,
it's
probably
not
getting
priority.
A
Is
there
okay
yeah,
so
you
know,
1.9
is,
has
early
planning
stuff
to
still
go
into
that
anything
else
on
releases
and
upcoming
upcoming
focus
on
the
on
the
map.
Here.
B
Yeah
well
for
1.9.
I
just
put
in
a
to
do
item
action
item
for
me
down
there
for
update
the
road
map
dock,
get
some
ideas
for
1.9
in
there
clean
up
the
board
or
add
things
to
the
board,
maybe
but
yeah.
That's
all
for
me.
A
All
right
say
this
travis.
I
saw
your
pr
to
remove
the
like
the
info
mailing
list
and
our
discussion
with
amy
as
well.
To
that
it's
not
like
a
requirement
and
we
don't
need
it.
So
I
guess
that's
one.
We
can
mourn
the
loss
of
an
interesting
source
of
spam,
but
on
that
it's
it's
gone
so
that
makes
that
makes
sense.
That's
all
merged
in
right,
yep.
A
Yeah
yeah
exactly
in
the
contact
here
yep,
so
that
is
good.
That
is
good
yup.
We
still
have
our
security
stuff,
which
we
need,
but
yeah
no
more
info
at
which
is
great
and
then
yeah.
I
do
have
that
an
issue
assigned
to
me
and
created
an
issue
and
assigned
it
to
me
for
go
ahead
and
closing
out
the
rook
dev.
The
forum
group
group
thing
there.
I
have
not
followed
up
on
it
yet,
but
I
I
will
do
that
so.
A
A
Like
put
a
post
on
it,
that
you
know
points
people
to
the
more
preferred
ways
of
contact
in
the
project
so
that
they
do
go
there
then
they'll
see
you
know
if
it's
like
an
archive
sort
of
thing
or,
like
you
know,
stale
results,
then
at
least
that'll
be
the
latest
post
on
it,
okay,
cool
and
then
so.
Cassandra
operator
discussions.
C
That
around
there
yeah
someone
from
datastax
reached
out
to
me
asking
about
the
cassandra
operator.
It
wasn't
really
clear
what
the
request
was,
but
I
just
essentially
the
person
said
that
he
had
been
given
the
task
of
partnering
of
yeah
or
partnering
with
rook
and
it's
kind
of
vague,
and
I
was
well
yeah.
It
sounds
cool,
but
we
also
have
community
like
we
have
community
meeting
and
it
would
be
good
if
you
can
just
join
and
meet
the
team
and
so
wait.
C
So
then
we
can
just
discuss
what
are
the
topics
you
have
in
mind?
He.
He
said
he
had
a
conflict
in
this
time
slot,
but
he
was
hoping
that
some
of
his
colleagues
could
join,
which
apparently
is
not
the
case.
C
Treat
those
requests
more
openly
from
community
so
like
joining
the
the
meeting
is
one
and
I
think
my
next
answer
would
be.
Can
you
just
maybe
please
open
a
github
issue
so
that
everybody's
aware
of
of
your
request
and
how
it
can
help
because
typically
having
one
wants
like
this,
doesn't
really
help
in
any
ways
so
yeah.
A
Did
they
make
any
sort
of
statement
about
like
like
a
potential
commitment
they'd
want
to
make
or
like
it
was
just
kind
of
or
very
early,
like
explosion,
yeah.
A
Yeah
and
travis
has
saw
that
some
some
other
folks
have
reached
out
to
us
about
being
involved
in
the
project.
I
don't
I
don't
know
if
that
was.
If
yeah
I
don't
know
if
that
was
a
sensitive
thing,
if
they
were
just
kind
of
like
that,
company
is
just
like
starting
to
look
or
if
they
wanted
to
get
publicly.
C
A
B
B
It
from
seagate
or
or
someone
or
someone
like
that
yeah
they
were
asking
about
creating
a
rook
provider,
another
book
operator
for
their
technology.
Basically,
so
I
gave
him
a
pointer
to
our
our
operator's
page
or.
B
A
Yeah,
that's
fair.
I
think
yeah,
like
with
that
documentation
that
we
have
that
you
pointed
to
matt.
You
know
it's
a
reasonable
start
and
then,
if
they
want
to
have
more
of
a
conversation
then
we
can.
We
can
have
that,
but
that's
a
good
place
to
start
right,
cool,
okay,
all
right
any
other
topics
for
today,
then.
B
B
Yeah
yep
and.
A
Is
are
you,
is
that
intended
to
be
in
person
also
not
a
virtual
thing?
Well,.
B
They
said,
oh
so
they
said
it's
in
person
with
a
virtual
component
and
when
you
submitted
your
request,
it
asks
if
you,
if
we
think
we'd,
be
able
to
make
it
or
want
to
plan
on
making
it
or
if
we
want
the
virtual
option
and
I'm
not
sure
how
much
travel
we'll
be
able
to
do
by
then
like
with
red
hat.
So
I
just
said
selected
the
virtual
option
to
record
it
again,
like
usual,
so
we'll
see,
traveling
would
be
nice,
but
it
just
doesn't
feel
like
it's
ever
going
to
happen.
A
Is
that
something?
That's?
Is
it's
not
being
approved
right
now
for
red
hat?
Like
is,
then,
you
all
are
not
allowed
to
travel
in
that's
policy
right
now,.
B
C
B
A
Cool
all
right:
well,
thanks
for
doing
that,
travis
yeah,
and
then
we
can
follow
up
on
these
two
action
items.
This
one
has
an
issue
assigned
to
it
and
to
travis
you'll
just
follow
up
on
that
one
there.
Okay,
then
anything
else
before
we
can
go
ahead
and
adjourn
for
the
week.
C
No
but
I'll
try
to
make
it
quick,
it's
just
it's
just
just
a
a
bit
unrelated,
but
something
I
thought
when
I
was
looking
at
the
replo.
I
was
looking
at
our
github
stars
and
yeah
we're
slowly
progressing
towards
the
10k,
which,
which
is
good,
and
this
actually
reminded
me
of
a
bad
story
of
one
of
my
friends
that
actually
runs
a
startup.
C
They
they
had
this
project
where
the
code
was
publicly
available,
just
like
it
is
for
us
today,
but
then
they
made
a
mistake
and
pushed
something
like
an
amazon,
private
key
or
something
then
github
just
detected.
That
key
was
like.
So
essentially
the
report
is
so
more
less
compromised
and
I
think
when
this
happens,
they
have
bots
that
actually
not
sure
if
they
do
it
automatically.
C
But
the
end
result
was
that
they
turned
the
repo
to
private
that
the
key
wasn't
available
and
then
once
they
turned
on
they
just
like
made
it
public
again,
then
they
had
lost
all
of
their
stars.
B
C
Yeah,
so
I
guess
bottom
line
is
that
if
you,
if
you
ever
have
to
like,
if
you
ever
think
of
turning
the
reaper,
private
and
then
public
again,
then
just
just
don't
or
just
just
keep
in
mind
that
we
will
be
losing
a
lot
of
our
stars
and
there
was
just
no
way
to
get
it
back.
They
just
had
support,
and
it's
just
just
not
possible
today,
so.
B
C
A
That's
really
that's
really
interesting.
I
I
didn't.
I
didn't
know
that
that
was
a
an
impact
to
that.
I
have
seen
some
pushed
keys
in
certain
repos.
I
don't
know
in
the
last
year
or
so,
and
the
automated
detection
of
those
keys
is
getting
faster
and
faster.
I
think,
probably
both
on
the
bots,
the
malicious
side,
but
then
also
on
github's
side
and
then
also
the
cloud
providers
side.
A
Also,
like
amazon,
had
reached
out
and
said
hey
this
this,
this
key
is
exposed
now,
so
it's
it
seems
like
it's
an
arms
race
on
both
sides
to
protect
and
to
attack.
C
A
C
Yeah,
I
can
do
like
some
sort
of
forecast
for
this.
I
don't
remember
how
like
what's
the
growth
every
quarter
or
something
but
yeah.
B
Yeah
we've
got
the
kpis
page.
Can
is
this
public
for
everyone
to
see?
Let's
see,
how
do
I
share
this
in
chat,
so
there's
a
link
to
our
board,
so
it
I
mean
it
looks
like
it
could
take
two
or
three
more
months,
it's
hard
to
say.
C
A
If
you
were
to
drop
a
link
to
the
the
kpis
page
into
the
agenda
notes,
there
then
feel
free.
C
A
A
Go
all
right,
cool
all
right,
well,
good,
to
see
everybody
and
yeah
we'll
see
y'all
in
a
couple
weeks,
then.