►
From YouTube: 2019-12-03 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
Okay,
the
recording
has
started-
and
this
is
the
December
3rd
2019
rook
community
meeting
and
we
are
getting
close
to
1.2
released
here.
I,
don't
think
that
there's
any
more
1.1
patches
left
I
think
we
got
up
to
what
when
I
went
out,
7
and
so
I,
don't
think
there
any
expected
patch
releases
since
we're
heading
towards
a
code.
Freeze
now
Travis.
Is
that
correct
and
your
book
as
well
so.
B
One
comment
around
that
I
guess
we
we
have
had
something
back,
poured
21.1
release
branch
since
one
died,
1.7
and
we're
I'd
say
we're
entering
a
new
phase
now,
because
I
anticipate
we'll
want
to
back
port
things
to
one,
not
one
branch,
even
after
we've
released
1.2
and
have
releases
going
in
parallel
now,
since
we'll
have
basically
have
a
downstream
product
that
needs
bug
fixes
based
on
1.1.
Even
while
1.2
moves
on.
A
B
A
B
Fixes
that
are
considered
sort
of
high
priority.
We
need
these
things.
We
can
still
back
forth
those
to
the
1.1
branch
and
yeah
we're
not
back
porting
new
features.
It's
really
just
these
bug
fixes
and-
and
so
that's
the
great
it's
I
mean
I
lose
criteria
in
my
mind
and
we
can
define
that
more.
Yes,.
A
B
B
One
thing
to
consider
around
this
is
that,
after
we
release
1.2
during
our
release,
process
for
1.1
we
no
longer
should
promote,
builds
to
the
release
channel
right
so
that
the
main
place
that
impacts
the
help
chart.
So
if
you
want,
if
you
install
a
helmet
just
on
the
release
channel,
you
expect
the
latest
one
to
be
installed
well
after
1.2
is
released
and
it
will
be
based
on
1.2
and.
A
B
A
B
Exactly
so,
we
originally
proposed
our
quarterly
cycle.
Let's
have
feature
freeze
today
and
then
released
next
Tuesday
well,
just
with
coop,
con
and
holiday
last
week
in
the
US
I
feel
like
we're
still
catching
up,
and
there
are
some
things
we
need
to
finish
up
and
I
feel
like
there's
a
bunch
of
work
to
do.
But
if
we
target
end
of
this
week
for
getting
to
a
feature,
freeze,
wrap
up,
some
final
seems
reasonable.
A
It's
something
that's
also
interesting
there
for
me.
Travis
is
that
you
know,
since
the
security
audit
is
on
is
going
on
this
week,
there
could
be
a
findings
that
come
out
of
that,
as
the
week
goes
on,
that
are,
you
know,
critical
vulnerabilities
or
things
that
we
really
want
to
include
or
to
fix
period,
and
that
could
easily
start
a
conversation
around,
depending
on
the
severity
of
the
vulnerabilities
to
to
delay
a
1.2
to
include
these
new
security
issues.
Essentially
right.
B
That
potentially
yep
and
then
hopefully
we
don't
need
any
RER
contexture,
because
that
anyway
I
don't
anticipate
that,
but
we'll
see
so
we
would
have
so
end
of
this
week
for
feature
freeze
and
then
end
of
next
week
for
code
freeze,
meaning
hopefully
we
can
get
all
the
bug
fixes
in
test
upgrades
and
things
and
then
December
17th
being
a
Tuesday.
It
gives
us
a
couple
days
after
the
weekend
to
create
a
blog,
get
ready
for
the
release
and
target
the
17th
for
four
extra
days.
B
B
There's
still
a
bunch
in
there
that
were
optimistic,
but
so
we
need
to
make
it
pass
on
the
board.
Okay
and,
let's
see
I,
don't
see
anybody
from
other
storage
providers
here
today,
just
to
speak
to
if
they
have
features
the
main-yard
I'm
thinking
over
in
SEF,
so
I'll
ping.
The
storage
owners
that
you
wanna
add.
B
B
A
See
like
we
had
talked
about
this
a
little
bit
before,
but
I
so
I
I
see
more
pull,
requests
than
I
do
issues
on
the
board
and
it's
definitely
a
mix
of
it
like
is
it?
Do
you
think
it's
fairly
common
that
just
across
the
entire
community
here
now
that
people
just
want
to
include
pull
requests
on
the
board.
B
From
my
perspective,
a
pull
request
or
an
issue
can
track
something
that
needs
to
change
and
if
we
have
an
issue,
I
prefer
to
put
on
the
board
if
there's
only
a
pull
request
and
not
an
issue
than
putting
the
PO
request
on
the
board
seems
valid
to
me.
So
that's
what
I've
been
doing
it
at
least
but
I
think
being
strict
about
having
an
issue
to
track
every
PR.
It's
it's
overkill.
B
A
Which
is
fair,
yeah
I,
don't
think
you
strict
requirements,
have
an
issue
for
every
single
ProQuest,
but
I
like
the
first
one
I
clicked
on
it
does
support
requests
on
the
board
and
it's
for
a
particular
issue,
and
then
that
issue
isn't
even
it's
not
in
the
milestone
at
all.
So
I
should
so
think
that
that
kind
of
thing
like
makes
it
harder
to
do
bookkeeping
of
like
burned
down,
or
you
know
the
quantity
or
scope
of
things.
A
B
A
A
So
the
first
item
here
is
that
on
Monday
morning,
so
yesterday
morning
we
officially
started
the
security
audit,
a
review
with
trail
of
bits,
a
security
security
firm
that
I
think
is
based
out
of
New
York
New
York
City,
and
so
we
did
a
kickoff
call
me
and
Travis
and
Alexander
with
a
few
of
their
security
security,
researchers
and
experts,
and
so
they
are
diving
into
the
codebase.
Now
they
are,
you
know,
doing
penetration
testing,
and
you
know
also
like
threat
models
and
all
sorts
of
cool
stuff
there.
A
A
We
have
another
call
scheduled
a
wrap-up
call
with
the
security
firm
and
we're
will
go
over
all
the
results
and
findings
and
the
report
would
be
published
and
we'll
need
to
do
a
triage
as
well
to
figure
out
if
there's
any
issues
that
are
severe
severe
enough,
that
we
need
to
address
them
immediately,
and
we
can
do
that
in
real
time
too.
We
don't
have
to
wait
until
the
end
of
the
week.
If
issues
get
open
that
are
critical
severity,
then
we
can
go
ahead
and
triage
and
assess
or
address
them
very
quickly.
C
A
A
Yes,
security,
I
mean
I,
did
I,
definitely
see
the
value
in
addressing
security
issues.
One
good
one
really
good
thing,
though
here
is
that
you
know
this
is
coming
up
as
part
of
the
process
for
graduating
the
road
project
at
CNCs,
and
so
we
have
we
wit
with
trail
of
bits,
not
only
because
of
their
expertise
and
their
quality.
A
Anyone
who
we
haven't
really
kicked
off
this
effort
fully
yet,
but
I
am
open
for
any
testimonials
from
production
users.
So
if
you
have
any
you
know
of
any
production
users,
you
know
that
would
like
to
chat
about.
So
you
know
the
share
some
details
about
their
environments
and
their
story.
You
just
connect
them
with
me.
I'll,
be
happy
to
collect
all
their
information
and
do
a
little.
You
know
interview
and
stuff
like
that
to
get
more
details
so
just
point
him
in
a
a
Jared
and
I'll
be
happy
to
follow
up
with
them
after.
A
There
was
one
person
who
came
and
talked
to
me
after
that,
but
yeah
not
like
I
yeah
I,
when
we
were
doing
this,
for
the
incubation
proposal
was
like
reaching
out
on
slack,
exciting
emails
to
people
etc
like
when
we
started
like
a
focused
sort
of
effort
to
reach
out
is
when
we
really
started
getting
people
coming
in
there
so
yeah,
but
then,
if
some
of
this
will
be
outreach,
not
in
you
know,
inbound
stuff,
so
the
people
that
we
know
are
aware
of
that
are
definitely
using
in
production
like
that,
helps
a
lot
more
to
be
able
to
focus
and
try
to
target
them
and
get
responses
from
them
more
so
than
blanket.
A
You
know
sending
out
slack
messages
to
like
the
you
know.
2,000
people
slack
so
focused
ones
help
a
lot.
Okay,
all
right
so
Minaya
can
we
can
we
run
a
survey?
Maybe
yeah,
that's
that's.
What
we
did
for
incubation
sebastian
is
a
big
survey
that
people
could
just
easily
respond
to
and
like
provide
their
information.
Like
one
of
the
questions,
is
you
know,
are
you
comfortable?
You
know?
Can
you
share
these
details
with
publicly
and
then
those
people
are
follow
up
with
to
get
more
of
their
story
so
yeah?
That's.
A
A
B
A
B
We,
a
few
of
us,
talked
to
coop
con,
so
you
discovered
first
of
all,
Mineo
has
its
own
operator
now
that
they
put
in
github,
comm,
/,
Mineo
and
they've
never
come
to
the
rook
project.
We
don't
have
any
Gration
tests
without
the
community
support.
It
just
seems
like
we
need
to
go
ahead
and
remove
it
from
rook.
There's
nothing
happened
with
it
since
it
was
added
to
rook
so
any
yeah.
A
B
A
B
B
C
A
Yeah:
okay:
let's:
let's
take
an
action
item
just
to
reach
out
to
them
and
it's.
A
C
C
A
A
Cool
okay,
so
let's
I
wanted
to
just
a
quick
second
here
you
know:
cubed
on
San
Diego
was
two
weeks
ago,
not
last
week
for
Thanksgiving
holiday
in
the
United
States
here.
But
did
anybody
have
any
observations
and
thoughts
or
any
any
experiences
that
they
wanted
to
share
from
your
on
San
Diego.
C
B
C
C
Nothing
comes
to
mind
think
it
was
a
good
event.
We
got
a
pretty
good
turnout
that
at
the
session,
the
root
attack
session
and
at
the
booth
I
think
it
was
well
attended.
Even
though
I
wish
we
had
a
proper
booth,
not
a
community
slash
project
thing,
but
I
guess
we
managed
to
fit
it
a
little
bit.
So
in
the
end
it
looked
way
better
than
initially
so.
I
guess,
yeah.
B
B
A
D
B
B
A
C
C
B
B
A
B
B
B
So
it's
interesting
Brooke
being
in
the
you
know,
the
project
it
is
is
very
different
from
others
where
they're
just
focused
on
their
project.
It's
like
multiple
storage
providers,
means
well.
We
kind
of
need
our
own
sessions.
I
wonder
if
we
could
even
s
CN
CF
can
we
have
multiple
sessions
like
ok,
let's
have
a
rock
intro
session
and
then
a
deep
dive
for
each
storage
provider.
That's
interested
that
would.
A
A
A
A
I
saw
somebody
on
Twitter
making
comments
about
that,
and
it
was
hilarious.
They
that
yeah
I
think
there's
a
curse
now
long
queue.
C
A
C
A
A
D
Yeah
I
did
I
want
to
add
that
in
case,
anyone
outside
the
normal
Oh
like
chef
world,
wanted
to
comment
on.
So
this
this
has
evolved
a
little
bit,
but
we
we
want
to
deprecate.
Creating
new
file
store,
OS
T's,
because
file
store
is
in
sustaining
ancef
but
still
be
able
to
run.
My
call
legacy
existing
file,
star,
OS,
DS
and
then
also
deprecated
directory
based
OS
DS,
because
those
are
like
those
those
were
never
really
supportive
for
production
and
in
cepheid's,
just
sort
of
something
that
has
existed
for
for
testing
and
is.
B
D
Think
the
goal
is
to
not
be
able
to
create
new
file
stories
and
1.2,
given
the
like
prototyping
prototyping
work
that
I
have
done
so
far
it
it
might
be
a
little
more
challenging
or
we
might
I
don't
know
we
might
be
able
to
do
a
stopgap
that
is,
is
less
than
sort
of
stripping
out
at
as
much
of
the
code
as
much
as
just
throwing
some
sort
of
failure.
If,
if
you
just
try
to
create
new
file,
store,
OS
DS
but
yeah
ripping
out
like
those
cuts,
is
there
they're
kind
of
tangled
in
there?