Clearing the Air on the Build Script Changes - What It Means for You | TrueNAS Tech Talk (T3) E057

Perhaps you should read into the latest blog around TrueNAS Connect as that’s part of the purpose of that software:

While we have not laid out the exact feature set or process, it is part of the plan to have enablement of select Enterprise features, delivered via TNC.

We have an entire distribution network of partners across the EU in order to provide direct sales, support, and pricing that includes VAT as well as local inventories for both sales and support, so I’m not sure where this is coming from.

That’s exactly what’s going on. Again, to repeat what was said in the episode - there’s no problems with forks as long as the GPL and licenses are respected. And we (TrueNAS) do that with regards to upstream sources that we’re forking. We commit a bunch of code upstream, not just to OpenZFS, but to Samba, NFS, iSCSI targets, and more.

But that same respect isn’t happening from downstream - we’re not seeing “forks” as much as we are:

git pull
sed s/truenas/totallynewnas/g *
make clean

apologies for the bad pseudo-code there, but you get the idea.

2 Likes