On 01/14/2016 07:29 PM, Josh Boyer wrote:
C - Find maintainers ( I would volunteer - I'd have to learn packaging)
>
>I'd certainly be willing to assist if it were allowed.
I will be honest and say I do not foresee this being allowed in an
official capacity. People are better off using the existing ZFS repo
or contacting rpmfusion about it.
To be clear, maintainers would need to be willing to deal with any and
all kernel issues reported with ZFS loaded. We cannot staff the
existing "next-generation" filesystem that is already upstream, let
alone another that never will be.
Also, willing maintainers should be item A:).
Being a maintainer of a file system is a very, very large task. Specifically,
file systems (especially ZFS and btrfs) have a lot of hooks/dependencies into
the core IO/block layer and memory management system.
It definitely is not a "packaging" job, you need serious kernel skills here.
Putting the license aside, I think that it would be a really bad idea to pull in
any kernel component that was not upstream in the mainline kernel. The
maintainers of the ZFS code (who I know) can share the pain of chasing the rest
of the kernel. Building a file system as a kernel module or having it built in
is just a packaging issue, we should not use packaging as a way to circumvent
legal and community norms (in Fedora or the upstream kernel community).
Coming back to the issue of the license, I think that there is no chance that it
will ever land in the upstream kernel as long as it has this license.
My personal opinion is that the effort is better spent on working on btrfs or
the host of technologies in device mapper that provide very similar
features/functions to what people are looking for in ZFS.
Regards,
Ric
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
