Response from CTO on the matter
Hey everyone,
I’ve seen the concerns in the Community about us moving the build scripts internal for TrueNAS 27, so I want to address this directly.
Why we did it: We had a growing problem with bad actors forking TrueNAS, selling closed-source commercial derivatives under their own brands, and ignoring GPL and other licensing obligations. No attribution. No contribution back to the project. No support for the community or the engineering effort that built what they’re reselling. Unfortunately, many of these are in regions where we have little to no legal recourse. To address this challenge, we were already planning to take the build scripts internal. With the upcoming refactor of the new Secure Boot feature, along with myriad other changes we wanted to make to the build infrastructure, TrueNAS 27 was a natural time to make this change.
What this does NOT mean: We are not paywalling existing free features. Period. If it’s free today, it stays free.
What hasn’t changed: We’ve always made decisions about which
new features are fully open source (GPL or BSD), which are proprietary, and which land in the free edition vs. TrueNAS Enterprise products. That’s how we fund the engineering that builds TrueNAS for everyone. That model isn’t new, and it isn’t changing.
Happy to answer questions.
— Kris