►
From YouTube: 2020-04-07 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
April
7th
2020
Brook
community
meeting.
We
don't
have
a
very
long
agenda
today,
so
we'll
just
hop
right
on
into
it
and
see
what
we
can
get
through
here.
We
do
not
have
any
further
current
1.2
patch
releases
going
up.
So,
let's
hop
on
over
to
1.3
and
we
have
finished
all
the
testing
in
the
code.
Freeze
and
everything
is
looking
good
to
go
ahead
and
actually
perform
or
run
the
1.3
release
today,
so
intricate
fixes
going
out
in
there.
A
You
know
these
to
do
ones
here.
I
think
that
those
will
probably
be
done
in
patch
releases,
but
yeah
yeah.
It
looks
like
we've
got
a
couple
of
issues
here
that
are
marked
as
blocking
the
release,
but
there
looks
like
they're
closed
as
well,
so
I
said
to
you
or
blade
to
you
or
Alex.
Do
you
know
about
if
these
can
be
just
moved
to
the
done
column,
since
it
looks
like
they're
closed
I?
Think
some
of
the
back
ports.
A
They're
still
in
movies,
ok,
ok,
they
will
move
out
in
an
hour
or
so
cool.
That's
that's
perfect
yep!
So
then
we
do
seem
to
still
be
on
track
to
go
ahead
and
ship
1.3.
Today,
Travis
has
a
blog
post
draft
that
is
up
and
submitted
to
the
blog
I
believe
that
for
these
links
that
you
need
to
have
a
blog
editor
access
to
be
able
to
review
and
add
comments
stuff.
A
Send
me
a
direct
message
on
slack
if
you
do
not
have
blog
access,
but
you
would
like
it
to
review
Travis
this
draft
here
and
that
shouldn't
be
any
any
issues.
That's
giving
you
access
to
that
like
it
since
it's
through
medium,
it
uses
your
Twitter
account
to
for
authentication.
So
just
let
me
know
if
you
need
access
to
that.
A
Good
all
right,
so,
let's
move
ahead
in
on
to
the
community
topics.
So,
to
give
you
an
update
on
graduation
the
we
got
some
feedback
from
the
technical
Oversight
Committee
of
the
CN
CF
that
they
were
wondering
where
the
due
diligence
document
was
from
the
special
interest
group,
the
storage
sig,
and
that
is
a
newer
requirement
for
projects
at
the
incubation
level
to
make
it.
Thank
you
Bayesian.
You
need
to
go
through
a
due
diligence
process
with
the
sig
and
they
write
up
a
doc.
A
That
was
not
a
step
in
the
process
when
rook
was
accepted,
incubation
back
in
2018,
so
I
followed
up
with
the
TOC
to
bring
that
up
as
a
concern.
You
know,
I
think
it's
ideal
for
us
not
to
have
to
retro
actively
go
back
and
do
a
new
requirement
for
a
stage
of
the
prostate
life
cycle
process
of
a
CN
CF
project
we
already
have
accomplished.
A
So
that's
what
I
added
that
to
the
proposal
updated
the
templates
and
made
note
to
the
TOC
I
got
feedback
from
our
TOC
sponsor
and
and
also
Aaron
Boyd
who's
on
the
storage
cig.
That
was
a
brief
discussion
or
was
it
was
mentioned
in
the
TOC
call
this
morning
and
I?
Don't
think
that
there
was
major
push
back
from
the
TOC,
so
hopefully
we
will
not
have
to
go
back
and
retroactively
lis.
A
Do
this
due
diligence
document
and
then
we'll
be
able
to
go
ahead
and
call
the
vote
soon,
so
things
I
think
this
is
I,
think
this
will
be
okay,
but
I
mean
if
it
comes
down
to
the
TOC.
You
know
really
requires
or
demands
that
we
do
this
due
diligence
document.
Then
you
know
we'll
go
ahead
and
do
it.
You
know
we
don't
want
Brooks
to
try
to
make
it
through
graduation
with
less
criteria
than
other
projects
were
held
up
to.
A
A
Another
note
here
so
the
google
Summer
of
Code
those
applications
and
proposals
from
students
have
been
submitted.
The
application
process
is
now
over
and
it's
in
the
review
stage.
So
we
have
a
handful
of
proposals
that
were
submitted
there
and
we
need
to
follow
up
with
the
with
the
CNC
F
to
secure
our
slot.
A
For
the
summer
we
have
three
mentors,
and
so
we
have
plenty
of
mentors
to
handle
that
and
a
couple
of
proposals
to
look
at
so
I
believe
that
we'll
probably
be
getting
another
summer
a
third
summer
in
a
row
we'll
be
having
a
google
Summer
of
Code
project.
So
we'll
keep
you
updated.
Excuse
me
updated
on
that.
One.
A
B
A
B
B
A
A
It
looks
like,
though
this
is
not
a
immediate
blocker,
since
Travis
has
gone
ahead
and
as
a
temporary
workaround
removes
from
the
oldest
tags
from
those
repos
to
get
back
below
the
artificial
limits
imposed
by
that
bug
or
issue
in
the
man
festival.
So
I
think
we're
like
this.
Then
I
would
assume
that
this
would
not
block
the
one
that
release
process
since
we
have
a
workaround
here.
But
it's
something
to
that.
We'll
run.
B
A
B
A
A
Nice
yeah,
hopefully
it'd,
be
interesting
to
see
I
mean
I.
You
would
not
expect
any
regressions
to
be
picked
up
as
well
manifest
tool,
but
it
being
sure
to
see
what
what
all
changes
are
there.
What's
the
diff
of
features
or
changes
from
the
version
we're
currently
using
and
the
version
that
has
this
fix,
that
we
need.
A
Okay,
are
there
any
pr's
that
folks,
once
you
bring
up
for
a
discussion
here,
possibly
not
since
for
basically
got
everything
wrapped
up
for
a
release,
and
it's
going
out
today
so
looks,
looks
like
this.
Is
a
nice
little
window
here
or
in
between
in
between
development,
storms,
okay
and
then
some
of
the
action
items
from
last
meeting
I
played
with
this
again
and
tried
to
get
Travis
to
test
it
for
me,
but
the
rook
email
addresses
info
and
security
at
rook
dot.
A
So
I'm
gonna
still
we're
gonna
continue
to
follow
up
on
that
did
follow
up
last
week,
but
it
has
not
been
resolved
and
then
I
will
responds
to
this
issue.
That
Travis
brought
up
for
was
waiting
for
a
comment
from
me
cool.
So
that's
all
we
had
in
the
official
agenda
and
the
document
here
were
there
any
agenda
items
if
folks
wanted
to
bring
up
or
discuss
in
this
call
today.
A
Okay
cool!
Well:
if
there
are
no
further
discussion
points,
then
we
can
go
ahead
and
adjourn
this
short
agenda
for
today,
and
we
will
follow
up
on
getting
the
1.3
release
outs
later
on
this
afternoon
and
any
backports
that
needs
to
get
done,
Sebastian
that
you
mentioned
and
go
ahead
and
follow
up
on
those
and
then
we'll
run
the
release
train
later
on
this
afternoon.