►
From YouTube: 2019-09-10 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
September
10th
2019
Brook
community
meeting,
and
we
are
working
towards
a
1.1
release.
So
we
will
discuss
sort
of
the
patch
releases
that
we
still
have
yet
for
1.0,
as
well
as
the
burn
down
in
remaining
items
for
1.1
I'm,
hoping
that
by
the
end
of
this
call
here,
we
will
have
a
bit
of
agreement
on
what
the
released
target
date
is
for
1.1
and
so
that
we
can
start
making
plans
on
announcements,
and
you
know,
information
being
shared
and
socialized
about
the
release
coming
up.
A
A
B
A
B
B
A
Okay,
so
at
least
in
terms
of
self
issues,
no
interface
has
worked
towards.
You
know
the
v1.
My
excuse
me
moving
towards
stable
v1
in
this
release,
and
so
that's
been
some
great
progress
there.
There
are
a
number
of
selfish
OU's
still
here
terms.
Do
you
want
to
go
ahead
and
speak
through
those
issues,
and
you
know
one
of
the
big
blockers.
What
are
the
risks?
What
are
we
concerned
about?
What
are
the
long
poles
right?
Could
you
actually.
B
A
B
A
B
B
A
And
how
I
think
you
Blaine?
How?
How
would
you
say,
because
this
is
the
first
release
where
we've
gone
to
this
process
of
having
a
bit
of
a
longer
the
least
branch
baked
time,
and
you
know
having
like
the
beta
tagged
on
the
on
the
release
versioning
as
well?
How
is
that
process
gone
in
your
opinion
and
there
are
improvements
or
things
that
are
one
did
not
work
well,
or
has
it
been
pretty
smooth.
B
One
thing
that
I
think
I
was
wasn't
sure
how
it
would
work
out
is
all
the
backboards.
Well,
as
long
as
we
didn't
diverge
mastered,
it
was
pretty
straightforward
with
what
Blaine
found
out
how
to
create
the
back
door.
Prs
with
get
magic,
so
I
think
that
worked
pretty
smoothly
once
he
figured
that
out
and.
A
C
I
did
document
what
I
did?
Can
you
hear
me?
Yeah
I
could
hear
you
blade
yeah
yeah,
okay,
yeah
I
documented.
What
I
did
this
morning
and
then
also
like
what
I
did
I
guess
it
was
last
week,
but
it
like
an
upside-down
rebase,
where
instead
of
rebasing
like
a
branch
on
to
master
her
like
rebasing
master,
underneath
her
branch,
I
rebase
a
branch
underneath
a
branch
off
master
in
order
to
get
all
of
all
of
the
missing
commits.
A
C
A
Got
it
yeah
so
that
it
looks
like
then
that
we
are
in
good
position
for,
for
you
know
I.
Can
you
know
but
figuring
out
our
final
testing
and
getting
everything
to
signed
off?
What
are
the
big
remaining
like
sign-off
things
that
you
know
of
travelers
is
to
be
tree
or
new
from
edgy
fests
on
the
call
to
I?
A
B
It
blocks
NFS
on
open
shipped,
but
it's
a
really
simple
fix
and
I
was
just
testing.
Its
I
may
have
a
fix
for
this,
but
even
still
I
don't
know
that
anybody
would
be
blocked
on
that
for
the
release.
It's
a
less
common
or
less
used
to
be
true
anyway.
So
we
could.
My
view
is
I.
Think
all
the
blocking
issues
are
really
resolved.
B
Well,
I'd
one
thought
I
had
around
the
blogs
is
that
with
so
much
work,
that's
going
on
in
the
different
storage
providers?
Now
it
it
feels
like
a
single
blog
post
is
not
going
to
be
able
to
capture
all
the
work.
That's
being
done,
so
my
thought
was
what,
if
each
story
from
writer
that
has
made
your
changes
in
here,
creates
its
own
blog
posts
on
the
root
plug,
and
then
we
have
one
overall
blog
post,
that
kind
of
summarizes
and
then
points
to
those
blog
posts.
A
C
C
A
C
A
We
can,
we
can
add
them
as
an
editor
or
an
author
contributor,
whatever
the
term
is
on
the
medium
blog,
so
that
we
can
add
that
you
know
in
a
draft
form
and
like
Travis
was
suggesting,
and
then
we
could
solicit
feedback
iterate
over
it
there
in
the
format
that
it's
going
to
be
publicized
in.
So
if
we
know
who
who's
the
primary
author
or
who's,
you
know
who's
accountable
for
driving
the
blog
post,
for
you
could
might
to
completion,
then
we'd
be
we'd,
be
happy
to
add
them
as
a
contributor
to
the
blog.
C
A
B
D
Maybe,
as
a
point
to
nodes,
besides
to
your
release,
post
I'll
probably
be
soon
writing
a
blog
post
for
the
well
people.
I
did
something
we've
seen
CF
I,
think
til
the
end
or
monitors
like
a
change
for
some
companies
or
so
to
write
up
like
blog
posts
or
something
from
media
site,
and
there
would
also
be
from
my
site
to
mention
there
about
the
release
and
that
separate
post.
Just
to
noted,
where.
D
D
A
D
A
D
D
D
A
Let
us
say:
let
us
know
if
you
need
a
if
you
want
any
like
feedback
or
review
of
what
you're
writing
up.
Alex
are
happy
to
provide
people
watching.
Thank
you.
Cool
cool,
cool,
okay,
so
so
then,
like
the
technical
stuff
seems
to
be
wrapping
up
and
you
know
we're
getting
good
feeling
good
about
the
quality
level
etc.
We
do
need
confirmation,
I
think
from
edge
FS
still,
but
it
seems
like
the
the
last
pieces
here
or
around
getting
the
write-ups
and
blog
posts
done.
A
So
we
can
drive
those
asynchronously
and
it'll
be
good
to
drive
those
from
the
medium.com.
You
know
Brooke
blog
site
as
well,
so
that
they're
all
in
one
place
and
they're
not.
We
don't
have
to
look
in
multiple
places
and
multiple
Docs
to
kind
of
pull
everything
together
so
it'll,
be
it
all
in
one
view
there
and
we
can
do
Drive
feedback
and
iterate
over
those
to
get
those
two
ready
to
from
draft
to
ready
to
publicize.
B
A
Way,
yeah,
if
you
could
do
that
right
now,
while
I'm
taking
these
notes
here,
just
ping
Dimitri
about
if
you
have
what
their
blog
post
plan
is.
A
Okay
sounds
great,
then
looks
like
we're
in
good
shape.
For
for
one,
not
one,
that's
awesome!
Okay!
So
do
we?
Let's
move
on
to
the
major
features
merged
since
the
last
meeting
section,
and
so
you
know
Travis
you're,
writing
there.
So
I'll
give
you
a
second
here.
A
big
accomplishment
was
for
edge
of
s
to
move
from
v1
beta
one
of
two,
the
b1
status
for
the
other
CR
DS
and
their
API.
A
A
B
I
meet
myself
again,
alright,
yeah,
just
a
couple
of
features
that
come
to
mind
since,
with
my
last
I
rent
that
could
be
useful
for
other
providers
as
well,
so
we've
got
Sopot
disruption
budgets.
It's
a
concept
in
Cabernets
that
helps
applications
handle
upgrades
of
the
underlying
humanities
cluster,
so
they're
PV
bees
are
really
designed
around
a
pod
disruption.
B
Well,
if,
if
a
story
provider
in
this
example
is
more
tied
to
a
node
than
a
pod
like
what's
in
the
case
of
Seth,
Seth
is
tight,
well
OS
DS
to
the
nodes,
and
you
might
have
multiple
OS
DS
per
node,
so
we
really
want
something
that
acts
more
like
a
machine
disruption
budget
during
the
upgrade
process
to
disrupt
all
of
the
OS
DS
at
once.
So
this
you
know
this
is
in
force.
F
now
and
I
just
want
to
point
out.
B
It
could
be
a
useful
pattern
for
others:
storage
providers
if,
if
the
normal
PD
bees
don't
work
for
them,
the
machine
destruction
budgets
are
an
open
shift.
Specific
concept
really
similar
to
the
PD
bees,
just
at
the
Machine
level,
so
I'm
not
sure
how
how
much
well
the
pattern
is.
There
is
four:
if
people
are
using,
you
don't
open
shift
and
not
yeah.
Those
are
the
main
main
things
other
than
stabilization.
A
Awesome
thanks
for
sharing
that
Travis,
something
I
realized,
I
completely
glossed
over
and
skipped
was
that
we
talked
about
what's
left
and
the
one
that
one
milestone,
and
we
talked
about
driving
the
blog
posts
to
completion
and
ready
to
publicize
in
terms
of
the
actual
target
date
for
the
release
I.
It
feels
like,
then,
that
you
know
getting
blog
posts
together
and
iterating
over
the
feedback,
etc.
A
That
did
to
target
Thursday
would
be
my
vote
so
that
we
have
time
to
get
some
of
the
posts
together
and
then
get
the
feedback
and
get
everything
to
a
good
state
like
by
the
end
of
day
tomorrow
and
then
actually
run
the
release.
Maybe
on
Thursday.
Does
that
sound
reasonable
to
other
folks
or
what
we
thought
if
they
keep
out
that.
B
D
There
might
be
one
kind
of
issue
which
we
may
overlook
right
now
is
that
we
should
document
the
kernel
requirements
that
a
kernel
version
requirements
for
the
safe
Nautilus
version
as
there
is
I
can't
tell
you
no
I'm,
true
I'm,
trying
to
find
it,
but
I
really
haven't
really
found
it.
No,
it
was
a
good
one.
D
B
D
B
A
D
If
you
go
ahead
and
add
like
team
/
groups,
whatever
its
call
and
get
up
to
be
able
to
mention
the
people
like
that,
that
I
can
do,
for
example,
at
IO
/
SF
to
get
the
people
that
you
mostly
serve
stuff
for
self
suicide
and
there
to
get
the
people
that
do
this.
F,
these
iPods
integration
and
so
on
on
the
on
the
roof
side,
to
kind
of
make
it
easier
to
hate,
isn't
an
issue
for
you,
guys,
kind
of
and
like
well,
like
hey
ping?
Could
you
please
take
a
look
or
something
it.
A
A
B
A
A
Cool
all
right,
so
the
next
topic
here,
Travis
and
I-
met
with
the
security
team
that
the
CN
CF
works
with
to
do
security
audits
of
CN
CF
projects.
A
security
audit
is
one
of
the
requirements
for
being
able
to
graduate
a
project
in
the
CN
CF.
So
we
had
a
kickoff
call
with
them
this
morning
and
kind
of
figured
out
what
the
scope.
A
A
They
would
not
be
able
to
commit
this
work
until
December
or
January,
so
we
need
to
evaluate
what
what
what
we
can
do
for
security
audits
in
you
know,
nearer
timeframes
and
that
and
figure
out
what,
where
what
our
plans
are
for
how
that
fits
into
graduation
process
and
all
that,
but
I
wanted
to
make
everyone
aware
that
you
know
with
the
process.
Excuse
me,
the
process
is
started
for
performing
the
security
audit
and
getting
the
security
disclosure
process
in
place
as
well
and
in
getting
all
that
completed.
So
we're
working
on
that
now.
A
A
A
That,
then,
we
will
over
the
next
two
days
we
are
targeting
Thursday
for
the
1.1
release.
We
will
work
on
iterating
on
the
blog
posts
on
the
blog
network
that
IO
we
will
give
contributor
access,
editor
access
to
anybody,
who's
going
to
be
authoring,
a
blog
post
there
and
we'll
collect
liked
feedback
and
we'll
drive
those
blog
posts
to
be
ready
to
complete.
We
will
follow
up
on
final
sign-off
for
the
release
from
all
these
storage
providers
and
ad
blocking
issues
that
come
up.
A
We
will
deal
with
in
real
time
and
the
1.1
project
board
will
try
to
keep
up
to
date
for
any
of
the
lingering
issues
that
are
blocking
or
preventing
the
1.1
release.
So
hopefully
by
Thursday
we
will
have
blog
posts
ready
and
we
will
be
able
to
run
the
release
and
get
that
out
in
the
hands
of
our
users.