@geraldss Thanks for pinging @eben
Hi @eben Thanks for responding. To be clear, I will be developing a proprietary platform that I do not want to make open-source (on a GPL / BSD type basis). Obviously any JS would have the source-code viewable, but I’m talking about licensing terms for the whole application.
If I made any changes specifically to the Couchbase workbench side of things, I’m happy to send them to you (should they be of potential use to you guys), and I’m certainly happy to send in bug reports / fixes etc (I like to give back too) - and to make such changes available using whatever licensing you use.
I would like to confirm, though, that if I were to include one (or several) of your workbench JS scripts that I would not be forced to make my entire application conform to that license - only the relevant parts, pertaining to our integration with Couchbase.
I got the impression from your message that this would be OK, but it was not explicitly stated, and I want to be 100% sure that you guys are OK with me integrating your code with mine (without affecting the overall licensing of my product) before beginning.
Note: some time early-to-mid next year, once our platform / site is developed and launched, I am fully intending on approaching Couchbase to look at partnership opportunities / a strong business relationship, as Couchbase will be a key part of our platform (and the primary database used). If the usage of the relevant workbench code without licensing restrictions on the rest of my code would be dependent on that, I’m happy to discuss privately what I’m doing (on superficial levels at this stage, for obvious reasons).
I’m hoping that that won’t be a necessity, but for my own peace of mind, if you could clarify your position, I would be most grateful.