4 ms·
That is a very good question and something I have been struggling with. Do you have any ideas? I know that it has been done (ex: Sidekiq has OSS, Pro and Enter
by bullcitydev 7y ago
That is a very good question and something I have been struggling with. Do you have any ideas?
I know that it has been done (ex: Sidekiq has OSS, Pro and Enterprise versions).
My thought was to maintain a private fork for the pro version and continuously merge in changes from the OSS version, as well as add back any features into the OSS version that could be beneficial to everyone from the pro version.
But this does sound messy.. would love to know how others have done this in the past.
- _frkl 7y agoNot sure how well that'd work in your situation, but maybe you could license the pro parts with one of the licensezero ( https://licensezero.com https://licensezero.com ) licenses. That would disallow use of your software (or the parts of it you choose) with either closed source software, or in a commercial setting (depending on the license you pick). It would mean more work spelling all that out to your users, but you would make up for it by not having to hide/separate code as much. You'd have to be comfortable with 'showing all your code though.
- bullcitydev 7y agoInteresting.. I've never heard of licensezero. Will check it out this weekend. Thanks for the tip!