Hi Joe,
If you're going to ship Hypertable as part of a closed-source product,
you'll need to make any modification to Hypertable "per-se" open source.
In other words, all of the porting work you've done will need to be made
open source. As far as application code goes, here is our policy:
1. If you're building a non-database application, then we do not consider
that to be an extension of Hypertable and therefore you can ship your
product close-sourced without fear of GPL violation.
2. If you're building a database application (e.g. FonzyDB) then we do
consider that an extension of Hypertable and you'll need to obtain a
commercial license from Hypertable, Inc.
- Doug
On Wed, Oct 17, 2012 at 5:19 AM, Fonzy <joemac
...@gmail.com> wrote:
> Doug,
> If we compile against your libraries does this mean we will have to make
> our source code available as well? We would like to keep our code
> proprietary, is the only way to do this to use the Thrift method for
> connection?
> Thanks,
> On Friday, January 6, 2012 2:24:15 AM UTC-5, Doug Judd wrote:
>> Hypertable is currently licensed under GPLv2. We're planning to change
>> to GPLv3. This license is similar to v2 except that it contains protection
>> against "Tivoization" and Discriminatory patent deals (see A Quick Guide
>> to GPLv3 <http://www.gnu.org/licenses/quick-guide-gplv3.html>). If
>> this causes a problem for any of you, please let us know.
>> - Doug
>> --
> You received this message because you are subscribed to the Google Groups
> "Hypertable User" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/hypertable-user/-/wwcFDdPN8oMJ.
> To post to this group, send email to hypertable-user@googlegroups.com.
> To unsubscribe from this group, send email to
> hypertable-user+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/hypertable-user?hl=en.
--
Doug Judd
CEO, Hypertable Inc.
