Hi, my advise is to change it to APL from now before you start having
contributors, a project with contributors will need written permission from
each to change the license.

Best regards,
Cheyenne

On Wed, May 9, 2018 at 1:57 PM, Water Guo <[email protected]> wrote:

> Well, I didn’t expect the license has become the concern instead of the
> software itself. So I did my homework trying to have a good understanding
> of the license. So GPL means you need to open source derived work as long
> as you make the software public, even by dynamically linking to a GPL
> library. Sounds pretty good to me personally. I have no issue with that.
> Sure I understand it can be bitch to make a profitable business on top of
> that. LGPL means you can link to a LGPL library without publishing derived
> work.
>
> As of today, AntsDB does more than linking to the MySQL JDBC driver. There
> are private members of the network protocol implementation in the JDBC
> driver that I use. Yah I mean i copied some of the source code for the sake
> of laziness. But don’t let license hold your feet. I own 100% of the source
> code. If the community find good use of my program, I’d be more than happy
> to overcome my laziness and rewrite the GPLed code, making it LGPL.
>
> ~water
>
> > On May 9, 2018, at 1:59 PM, Sanel Zukan <[email protected]> wrote:
> >
> > What about Connector/J from MariaDB? It is LGPL and (I think) that
> > should make it easier to mix with Apache license.
> >
> > Best,
> > Sanel
> >
> > Water Guo <[email protected]> writes:
> >> I am not an expert with software license. But my gut’s feeling is I
> can’t claim Apache if I am using code from MySQL JDBC driver (GPL), can I?
> >>
> >>> On May 8, 2018, at 11:49 AM, Stack <[email protected]> wrote:
> >>>
> >>> On Mon, May 7, 2018 at 11:58 AM, Water Guo <[email protected]>
> wrote:
> >>>
> >>>> Not it is not. AntsDB has no dependence on MySQL code. It is written
> in
> >>>> Java and uses a couple of open source libraries.
> >>>>
> >>>>
> >>> Sorry. There seems to be a misunderstanding. I was just asking if why
> >>> antsdb has a GPL license rather than say an Apache one:
> >>> https://github.com/waterguo/antsdb/blob/master/LICENSE.txt
> >>>
> >>> Thanks,
> >>> S
> >>>
> >>>
> >>>>> Sounds great Water. Lets take it for a spin. Quick question, why the
> "GNU
> >>>>> Affero General Public License, version 3" Is it up from mysql?
> Thanks,
> >>>>> S
> >>>>
> >>>> On Mon, May 7, 2018 at 10:09 AM, Water Guo <[email protected]>
> wrote:
> >>>>
> >>>>> Dear HBase Community,
> >>>>>
> >>>>> I’d like to take this opportunity to introduce my open source project
> >>>>> AntsDB. It is a database virtualization software that brings MySQL
> >>>>> compatibility to HBase. It means you can use any MySQL bindings such
> as
> >>>>> JDBC, ODBC, PHP, Perl to manipulate data in HBase. It supports most
> MySQL
> >>>>> DDLs and all DMLs, transaction control, table locks, row locks etc.
> Up to
> >>>>> date applications such as MySQL console, MySQL command lines,
> >>>> BenchmarkSQL,
> >>>>> MediaWiki, SonarQube, DBeaver, SquirrelSQL and many others can run
> >>>> directly
> >>>>> on HBase using AntsDB layer. The project is hosted at
> >>>>> https://github.com/waterguo/antsdb.
> >>>>>
> >>>>> AntsDB is designed to support high concurrency, low latency
> applications.
> >>>>> It uses local storage as cache so it can further reduce the latency
> of
> >>>>> HBase. We have benchmarked AntsDB using YCSB. The result is at
> >>>>> http://www.antsdb.com/?p=171.
> >>>>>
> >>>>> People always ask me how it is different from Phoenix. While Phoenix
> is
> >>>>> building a powerful SQL layer for HBase, we want to focus on backward
> >>>>> compatibility. We want to have applications built for MySQL can be
> used
> >>>>> directly on HBase. And people who are familiar with traditional
> >>>> relational
> >>>>> database can adopt HBase/Hadoop stack with ease.
> >>>>>
> >>>>> I’d be very glad if you find the project is useful and your feedback
> is
> >>>>> very welcome.
> >>>>>
> >>>>> Thanks
> >>>>> -water
> >>>>>
> >>>>
> >>>>
>
>

Reply via email to