Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
osxfuse's new non-free license #616
New releases have the following message in their description:
For those of us considering contributing this project or using it as a dependency, can we get a clarification on the project's new non-free license from @bfleischer?
@cadmartin the project is no longer open source either.
The latest at https://github.com/osxfuse/osxfuse/tree/support/osxfuse-3 is v3.8.3.
Silently making a project closed-source like this, is at the very least, poor form. The updater should at least notify end users that this is happening, as well.
This post on the Google group seems to indicate what's going on: https://groups.google.com/d/msg/osxfuse-group/_5PBFQ_BQB8/z1mu2H0rFAAJ
@d235j How would you have handled the situation? You have read #590, so you know that FUSE on macOS would most likely have died without external funding. Trust me, I tried to convince companies to fund the project for years but nothing much came of it.
@cadmartin FUSE releases up until version 3.8.3 are open source. For now, newer releases are closed source, with libosxfuse being the exemption. FUSE is and always will be free for non-commercial use. Bundling FUSE with commercial software however requires a license starting with version 3.10. If you are interested in obtaining such a license write me an email.
@bfleischer while I dislike that it’s closed source, that is a separate issue. I’m only advocating for transparency here.
Informing people means updating the main repo README to state that versions starting with 3.9.0 are no longer open source, and that versions starting with 3.10.0 are under a new license, with a link to the license, and
Informing people updating from 3.8.0 or 3.9.0 to 3.10.0 using the updater, as well as informing anyone who has updated via updater without being informed, of the source code availability change and the license change.
When I find out that some software package has changed license only because I’ve gone to the website and poked around, I tend to become very disillusioned due to the lack of transparency — it feels like a bait and switch. Go ahead and change the license — but let me know about it before I install the new version.
(Also separately — note that the APSL which might still cover some components of the package outside of libfuse has a weak copyleft. libosxfuse is derived from LGPL code and cannot be closed.)