Every implementation would port changes from this central repository instead of searching the commit history of the other implementations.
#Openzfs github install#
Developers from any implementation could then easily install and test platform-independent changes in that central repository. We want to simplify the sharing of code between implementations by having a platform-independent central repository that runs as a userland process on any operating system. One of the goals of OpenZFS is to simplify this porting process.Īre there plans to merge the different repositories? Each implementation regularly ports platform-independent changes from the other implementations. Even though the core of OpenZFS is platform-independent, there are a significant number of platform-specific changes need to be maintained for the parts of ZFS which interact with the rest of the operating system (VFS, memory management, disk i/o, etc.).Īre new features and improvements shared between the different repositories? OpenZFS brings together developers from multiple open-source forks of the original ZFS project from OpenSolaris to help ensure the compatibility and quality of all of our implementations.ĭevelopment Model Why are there four different repositories?Įach repository supports a different operating system.
Yes, the OpenZFS community has a code of conduct. General Does OpenZFS have a Code of Conduct? 5.1 What are the tradeoffs involved in using RAIDZ?.
4.1 Do you plan to release OpenZFS under a license other than the CDDL?.3.4 Can disks that use ZFS be used with Microsoft® Windows®?.3.3 Are pools created by Solaris compatible with OpenZFS?.3.2 Are storage pools created by OpenZFS compatible with ZEVO and with Oracle® Solaris?.
#Openzfs github portable#