I intentionally have avoided saying "open source" as it's not yet. Please let me know where it says it, as I may have made a mistake. I just haven't seen enough demand from current or potential users to justify the effort. If you feel strongly on this, please leave a comment here to help justify the effort: https://github.com/timeseries/qstudio/issues/43
You host binary blob releases in the qstudio GitHub alongside a License file in the repo indicating apache license. If you didn't open source everything that made up those releases including it's dependencies, you should remove or clarify what exactly is covered by the license to avoid the confusion.
I added the releases at the specific request of 1 large finance firm, a top 3 American bank by size. They requested it as their procurement department trusted downloads from github more than timestored.com. It probably sounds insane to you (or anyone sensible) especially as the downloads are digitally signed but I could write essays on the crazy hoops large firms ask you to jump through to provide software.
It doesn't sound crazy for those of us that have dealt with large firms, especially banking. The issue would be including an Apache license with the binary blob, when that is not the correct license.
I've dealt with extremely customized licenses for businesses (financial) that wanted software built for their use, but also to have the ability to resell the software that was built specifically for them. Not much surprises me anymore when it comes to expectations of legal departments. You just don't want to get into any kind of legal battle in the future over your software. I don't know anything about the size of your business, or who uses your software, but I do know that when it gets ugly and someone is looking for rights to software, you need to have things clearly laid out or you could end up devastated by a company that has funds to keep putting into legal fees that you may not.
I hope that this scenario never plays out, because I think releasing this is something that really adds value to the community that deals with databases. I just don't want to see someone trying to make a living get hurt by a licensing issue. Unfortunately, when it comes to high-end business, it's not so uncommon when things don't go the way your client wishes them to go. Best of luck to you!
