►
From YouTube: November 2019 OpenZFS Leadership Meeting
Description
At this month's meeting we discussed: New ZoL minimum kernel version; ZoL repo move/rename; and Issue tracker curation
Details and meeting notes: https://docs.google.com/document/d/1w2jv2XVYFmBVvG1EGf-9A5HBVsjAYoLIFZAnWHhV-BM/edit
A
A
We
I
actually
tested
this
out
so
using
the
github
like
transfer
ownership
feature,
and
it
seemed
to
work
as
soon
to
transfer
all
of
the
things
that
I
could
think
to
test
like
issues
for
requests,
the
wiki
releases
labels
and
it
also
forwards
all
the
existing
URLs.
So
if
you're
going
to
with
like
a
web
browser-
and
you
click
a
link
in
your
email
or
whatever
it'll
forward
it
from
the
old,
you
know
the
old
ZFS
on
Linux
URL
to
the
open,
ZFS
one
and
also
the
like.
A
If
anybody
has
negative
experience
with
using
the
github
transfer
ownership,
please
let
me
know
so
we
can
figure
out
if
there's
any,
you
know
drawbacks
that
would
impact
us
and
I'm
planning
this
to
know
an
email
about
this.
You
know
so
that
the
folks
who
weren't
at
the
conference
or
didn't
watch
the
talk
can
just
be
aware
of
this
press
them
now
this
week
and
then
you
know
we'll
make
a
change
kind
of
history
as
Brian
and
I
can
coordinate
on
that
yeah.
B
A
But
the
open,
ZFS
mailing
list
I
think,
will
continue
to
be
kind
of
the
canonical
mailing
list
for
discussing
like
development
of
new
features
and
we'll
kind
of
will
continue
to
keep
that
probably
more
developer
focused
and
keep
the
platform
specific
ones
like
the
zero
mailing
list.
More
freeform-
and
you
know
people
looking
for
help
using
ZFS
or
wondering
if
this
is
a
bug
or
how
do
what
you
know?
How
do
I
do
x?
Y&Amp;Z,
those
looking
new
to
be
good
resources
for
that.
B
So
hopefully,
this
is
a
largely
a
non-event
to
mainly
it's
to
help
maintain
the
code
repose,
but
we've
increased
the
minimum
kernel
version
that
we've
support
in
the
links
up
to
the
310
colonel
from
a2
632
colonel,
which
is
very,
very
old.
The
practical
effect
of
this
is
that
we
support
now
back
to
CentOS
or
rel
7
effectively.
B
So
that's
still,
the
vast
majority
of
distributions
we've
only
effectively
dropped
support
for
a
couple
very
old
Enterprise
distributions,
but
it
let
us
shed
a
lot
of
code
from
the
repository
for
maintaining
compatibility,
which
was
really
nice,
but
I
doubt
it
will
affect
many
people.
It's
also
worth
mentioning
that
this
won't
roll
out
until
the
next
major
ZFS
release.
Olicity
opens
the
FS.
2.0
will
drop
support,
so
existing
code,
i7
and
Odate
releases
will
continue
to
build
on
the
older
kernels.
This
is
just
going
forward.
A
A
Don't
know
if
it's
I
don't
know
how
big
of
a
problem
this
is.
Oh,
that's
part
of
whatever,
when
I
get
people's
input
on,
but
I
noticed
in
several
of
the
issues
that
have
been
filed
against
the
APIs
on
Linux.
Sometimes
you
will
find
an
issue.
That's
kind
of
like
I
want
to
feature
X
or
you
know.
Please
do
this
thing.
You
know
please
release
packages
for
this
new
operating
system
or
please
fix
this
bug
or
please
add
this
feature
which
is
great
and
then
I.
A
No,
you
guys
suck
for
whining
about
a
bunch
of
you
know,
volunteers,
not
doing
the
work
that
you
want
them
to
do
like
being
ungrateful,
and
you
know,
in
my
opinion
this
both
of
these
types
of
messages,
kind
of
amount
to
bickering
and
I
think
that
it
discourages
people
from
participating
in
the
community
in
general.
You
know,
folks
that
might
just
like
come
across
and
be
like.
A
Those
comments
do
contribute
to
you
know
having
just
a
lot
of
stuff
to
read
through
to
get
to
the
point
of
like
what
like,
what's
the
whole
like
what
is
the
actual
technical
hold
up
here
like
what
are
we
we
like?
What
are
we
waiting
for
to
move
this
forward
and
is
that
something
that
I
could
help
with
you
know
what
I
mean
so
I
guess
I
wanted
to
just
open
the
discussion
for
what
folks
think
like
is
this
a
problem
that
we
should
it
that
we
should
try
to
address?
A
Is
it
just
something
that
is
a
fact
of
life
for
all
over
in
source
communities?
I
mean
I've,
seen
this
in
it's
not
just
open,
zip
s,
it's
not
just
a
press
linux,
it's
like
other.
You
know
other
random,
unrelated
communities
that
I'm
that
I
participated
in.
You
see
the
same
things,
so
you
know
it
should
we
should
we
bother
trying
to
address
this,
or
should
we
just
ignore
it
and
if
we
do
want
to
address
it
like
I,
wanted
to
see,
if
folks
have
ideas
of
how
we
might
go
about
doing
that.
D
If
I
could
add
one
thing,
I
think
kind
of
similar
to
this
issue
is
not
just
on
an
individual
host
of,
like
you
know
about
a
single
issue,
but
also
we
do
have
like
a
large
number
of
unclosed
issues
and
I.
Think
that
part
of
what
happens
is
just
that
issues
get
like
kind
of
lost
in
the
lost
in
the
backlog
of
things
and
I.
Think
some
things
which
may
be
like.
D
A
D
Doing
mister
we're
not
necessarily
I
just
mean,
like
you,
know,
sipper,
since,
like
a
couple
months
ago,
I
was
looking
through
like
the
issues
and
just
looking
for
the
top
one,
and
it
occurred
to
me
that
I
should
probably
at
some
point
check
for
issues
that
have
the
word
encryption
in
them.
So
I
just
searched
through
the
thing
and
I
saw
that
I
had
actually
missed
a
bunch
and
just
kind
of
didn't
like
and
I
had
forgotten
about
them.
D
Some
of
them
I
had
gotten
tagged
on
some
like
I
hadn't,
but
even
the
ones
that
I
was
tagged
on
I.
Just
didn't
even
remember
and
like
we,
you
know,
III
went
back
and
added
a
couple
of
those
fixes,
just
because,
like
it
was
like
oh
yeah,
that
was
waiting
on
this
other
thing
and
now
there's
implemented.
D
A
I,
don't
think
that
we're
gonna
be
able
to
solve
that
a
hundred
percent,
so
I
think
it's
it's
still
worth
trying
to
think
about
like
what
do
we
want
to
do
if
anything
about
this
kind
of
negative
discussion
around
the
issue,
but
I
totally
agree
that
we
could
do
a
lot
better,
and
that
would
help
with
the
problem.
You
know
yeah
a
bunch.
B
No
I
wasn't
actually
but
I
can't
see
how
what's
happened
in
the
past,
with
a
lot
of
the
negative
comments
we
see
is.
It
is
exactly
these
issues
that
have
been
seem
to
have
been
neglected.
A
long
time
and
they've
been
lost,
track
of
I
would
say
those
are
probably
the
most
common
place.
I
see
that
kind
of
thing.
A
Do
you
think
in
do
you
think
that
those
are
issues
that
we
have
accidentally
ignored
or,
and
so
the
reminder
is
helpful,
where
the
issues
that
like
yeah,
we
know
we
need
to
do
that,
but
we're
waiting
on
X
or
we're
waiting
for
so-and-so
to
have
time
and-
and
you
know,
that's
why
it
hasn't
got
done.
I'd.
D
D
A
B
Would
add
that
we've
left
a
lot
of
these
issues
open
because
they
do
report
real
problems?
They're,
just
you
know
a
really
narrow
use
case,
or
very
few
people
see
it
or
that
kind
of
thing,
but
it's
legitimately
a
problem
right
and
we've
just
never
circled
back
to
address
this
or
that
little
problem.
B
A
I
think
those
though
there
are
ones
where
it's
not
like,
it
is
more
of
a
feature
request.
So,
for
example,
that
you
don't
think
you
are
the
packages
for
the
new
versions
of
Enterprise
Linux,
which
is
like
it's
not
broken.
You're,
just
like
asking
us
to
do
more
work
to
support
more
stuff
right,
which
is
like
sure,
that's
a
legitimate
request
or
the
Cindy
stuff
right,
where
those
are
both
things
that
are,
you
know,
I
think
they're,
both
things
that
are
doable
and
at
least
one
of
them
we
we
did
complete
the
work
for
it.
A
C
A
We
agree
that
it
is
very
severe
or
we
don't
think
it's
very
severe
or
whatever,
and
you
know
we're
looking
for
someone
to
work
on
it
or
someone
so
is
going
to
be
working
on
once
they
finish
X
or
we're
waiting
for
this
other
thing
to
happen,
that's
outside
of
the
project,
in
any
case,
it's
kind
of
like
when
every
time
somebody
complains
be
like
hey,
you
know
we
get
like
we
get.
What
you're
saying
here's
the
current
status
and
you
know,
maybe
that
would
help
to
diffuse
it
a
little
bit
by
having
that
there.
A
You
know
another
another
alternative
might
be
to
like
hide
all
of
those
comments
as
off-topic,
so
that
they
don't
clutter
up
the
messages
and
people
from
outside
the
community
don't
come
and
see
them.
It
might
not.
I
mean
it
in
my
people
might
stole
so
it's
just
as
many
impolite
messages
or
maybe
even
more
because
they
don't
like
having
the
messages
hidden.
A
D
Think
definitely
giving
people
like
a
response
can
help
to
defuse
things
for
a
little
bit.
I
will
not
say
that
it
has
always
completely
too
few
things,
at
least
in
the
past,
in
my
experience
but
but
I
think
you
know,
I
think
what's
really
frustrating
like
just
as
somebody
who
has
reported
issues
on
various
gift,
you
know,
github
pages
is
just
reporting
an
issue
and
then
never
getting
a
response.
You
know
not
seeing
that
anybody's
talked
about
it,
not
saying
that
anything
has
been
done
or,
like
you
know,
maybe
it
gets
done.
E
B
C
A
We
don't
necessarily
do
a
good
job
of
like
respond
to
every
comment.
You
know
when,
especially
when
the
comments
are
alike,
when
the
comments
don't
make,
you
feel
good.
It's
not
like
it's
like
okay.
First
I
got
to
do
with
my
not
feeling
good
before
I
write
a
response,
so
that
I'm,
like
writing,
a
play
response
and
whatnot,
and
it
just
takes
time
and
effort
to
do
that.
A
Well,
what
I'm
supposed
to
do
is
like
figure
out
the
status
reply
to
them
and
then,
like
at
least
I
kind
of
know,
that
I
have
the
backing
of
the
community
leadership
to
to
do
that,
to
put
in
the
kind
of
the
effort
to
do
that.
You
know,
as
opposed
to
being
like.
Would
it
help?
Would
it
not
help
what
you
gonna
even
supposed
to
do
here
should
ignore
the
this
guy
who
kind
of
is
trolling
us.
You
know
yeah.
A
C
E
D
E
Some
of
what
Brian
said
makes
sense
like
just
trying
to
do
the
triage
in
the
cleaning
up.
The
bug
tracker
is
as
much
as
possible,
but
I
think
like
Matt
is
saying
that
will
only
work
if
we
can
get
more
people
working
on
that,
because
there's
a
lot
of
issues
yeah
just
trying
to
read
through
all
open
pull
requests
to
get
an
idea
of
what
different
people
are
working
on.
Is
it's
been
really
hard
to
keep
up
with
yeah.
B
C
Mean
I
think
sometimes
also
depends
on
the
issue.
For
example,
it
has
happened
in
the
past
where
there's
a
dish
you've
been
found.
Let's
say
for
the
meta
slot
layer
or
something
like
that.
A
panic
that's
happen
around
those
past
and,
for
example,
Matt.
You
know
you
would
tell
me
like
hey.
Could
you
take
a
look
at
that?
Sometimes
so
I
think.
C
Maybe
we
could
like
do
a
better
job
of
just
kind
of
like
going
through
the
issues
once
in
a
while,
and
you
know
sometimes
you
know
if
there's
something
that
you
have
at
least
some
experience
on
or
yeah.
Like
similar
reasons,
you
could
just
go
and
reply
and
do
the
triassic
yourself
so
I
don't
think
it's
just
up
to
like
Matt
Ryan
that
I'm
going
to
think
that
you
have
to
reply
to
all
of
them.
But
you
know,
just
in
you
look
at
least
once
in
a
while.
E
B
Personally,
I
would
love
to
see
more
people,
help,
take
care
of
the
issue
tracker
and
pull
requests
and
triage
things,
I
think
more
people
we
can
get
working
on
that
the
better
and
even
going
through
all
the
shoes
I
mean
I'm
sure
there
are
ton
of
old
issues
that
just
aren't
relevant
there
anymore
or
fixed
and
can
be
closed
out.
I
just
take
time
to
go
through
and
do
that.
E
B
E
Have
been
an
ideal
thing
to
do
at
the
hackathon?
Actually,
we've
done
it
and
FreeBSD
before
is
just
yet
a
small
group
people
and
spend
60
seconds
on
each
flow
request,
whether
it's
deciding
to
close
it
or
assign
someone
to
investigate
it.
After
we've
gone
through
the
lights,
and
each
person
comes
away
with
a
short
list
of
of
few
hours
to
go,
look
at
and
see
if
it's
already
been
solved
or
if
there's
something
that
can
be
done
to
move
forward
or
who
the
right
person
to
assign
it
to
is.
E
B
E
D
E
D
Also,
possibly
a
cyan't
similar
to
like
Havel
and
external
has
sub
maintain
errs,
have
like
certain
issues
where,
like
you
know,
certain
people
are
like.
You
know,
sir
again
going
back
to
the
idea
of
how
do
we
make
sure
that
this
isn't
just
one
person
answering
all
of
the
comments
on
you
know
on
github
and
that's
their
full-time
job,
like
maybe
certain
tags
have
certain.
You
know,
people
who
are
you
know
kind
of
I
guess
responsible
for
for
responding
to
comments
in
within
those
tags
or
subsections.
Yeah
like
that.