gcloud happybase port violates happybase license

hello, happybase author here.

the gcloud happybase port violates my software's license. i do not like this.

the happybase license (mit+apache) is quite clear:

the above copyright notice and this permission notice shall be
included in all copies or substantial portions of the software.

http://happybase.readthedocs.io/en/latest/license.html

however, i don't see my name, the required notice, or even a small "thanks" or whatever, anywhere, neither in the gcloud docs, nor in the distributed software package itself.

the happybase port that is distributed with hbase contains considerable amounts of code written by me (for instance the whole api, and the implementation of connection pooling and other features is the same). and even though various docstrings have been partially adapted, proper attribution is in order here as well.

please fix this ASAP since this is NOT ok at all.

@wbolster

@wbolster This is totally my fault. Sorry for the mess up. It's something I had planned to do but the implementation process / porting over from https://github.com/dhermes/gcloud-python-bigtable took quite some time.

We fully intended gcloud.bigtable.happybase to be a drop-in replacement for happybase, hence the interface matching ("for instance the whole api"). It is a quite good abstraction for a somewhat contrived HBase / Thrift / Google Cloud Bigtable API. I assure the majority of the code (beyond the interface) is novel to this library, though as you mentioned connection pooling (and some string helpers) are quite similar.

@jgeewax Can we put license info directly in modules or should it go in the project or maybe something else?

ok, thank your for acknowledging my objections.

please keep me posted about the resolution.

btw, regardless of the number of lines of code that are shared, the simple fact that this library tries to be a drop-in replacement (on top of a different technology stack), and even (re)uses the original name, obviously makes this part of gcloud libs a derivative work of happybase, and hence the original work deserves mentioning, as prescribed by its license.

btw, i'm totally fine with this library existing. i encourage derivative works. i open-source my work so that others can benefit from it. and it's good to see that exactly that is what's happening.

happybase's license is very permissive exactly for this reason, so please adhere to it. :)

@jgeewax

Thanks for the clarification.

@jgeewax PTAL

@wbolster

@wbolster : First -- huge apology if we didn't go about this the right way. IANAL but we certainly didn't intend to violate the MIT license. Second, thanks so much for being understanding here. I was out on vacation otherwise I would've replied much more quickly... Sorry about that.

Again, IANAL, but it sounds like we should...

Make sure there's proper attribution in the docs for the gcloud.bigtable.happybase module (along with a pointer to the Happybase library)
Add the Happybase license to the repo

@tseaver / @dhermes : Is it acceptable to do as @wbolster did where we say that gcloud-python is Apache 2.0 licensed, and implements the Happybase API surface which is MIT licensed in our LICENSE file?

Thanks for getting back to me.

The easiest way to get everything solved is to simply include a snippet like this in a "license" page of the docs, alongside other licenses, including gcloud-python's own license, and be done with it:

Happybase API emulation for BigTable
====================================

The Happybase API emulation for BigTable as distributed with
gcloud-python is based on Happybase, which is distributed under the
MIT license. The original license text is included below.

HappyBase License

Copyright © 2012 Wouter Bolsterlee

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
“Software”), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

That way everything is covered. You don't need to get into specifics about whether APIs are copied, (parts of the) code is reused, docs are (partially) rewritten, and you don't have to worry about that either from a legal perspective since the original license allows you to do whatever you want with it, as long as you put the above notice somewhere.

@wbolster

That sounds great. Thanks again @wbolster for being so accommodating -- I really really appreciate it.

@dhermes : Does this look good to you guys? Can you toss up a PR and CC everyone?

A PR would be great, but before we merge let's let our open-source people review and make sure we're doing the right thing for everyone. I've reached out to them.

<sarcasm>
i am very happy to see that google has taken appropriate steps to resolve this issue in such a timely manner. that "fix asap" label really helped.
</sarcasm>

to be clear: google is violating my software's license, and it can be fixed by JUST COPYING AND PASTING SOME TEXT INTO YOUR DOCS as i mentioned before in #1762 (comment)

very professional. great work. kudos.

@jgeewax

ping @jgeewax @dhermes @jonparrott

... for future reference I don't have permissions on the org to create repos... but we know who does.

@jonparrott

@jonparrott I've sent invites to the two of you, and will make you admins as soon as they are completed.

@jonparrott

@jonparrott I see you have accepted the invite, but I don't seem to have the ability to give you anything other than "Collaborator" access (no "Teams" on personal repos).

@tseaver

@tseaver yeah hang tight.

If I have push access to the new "canonical" repo, I can just push there and delete my repo.

Canonical repo is setup at https://github.com/GoogleCloudPlatform/google-cloud-python-happybase

All admins here should have admin there.

I synced the canonical one with yours, so feel free to go ahead and delete yours.

Thanks everyone!

PR #2109 removes the Happybase-related code from this repository.

I also created an issue in the new repo for the one open Happybase-releated issue here (#1546).

@wbolster

@wbolster thank you for your patience. Is everything acceptable to you? Please let us know if there's anything else you feel we should do.

@wbolster

@wbolster : Again, apologies for the lag on getting this done, and thank you for the patience. Can you let us know if this fixes things?

Thanks all (@tseaver, @jonparrott , @daspecster , and everyone else) who helped to resolve this. Let's try to speed up next time so it doesn't take so long...

yeah, as i said numerous times before, just include the license and point out that your package is an emulation of my happybase package. i think both are covered now in the new repo's README.

fix: add detailed message in job error (#1762)

deps: avoid `gcsfs==2025.5.0` (#1762)

Navigation Menu

Repository navigation

gcloud happybase port violates happybase license #1762

31 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

gcloud happybase port violates happybase license #1762

Description

Activity

dhermes commented on Apr 28, 2016

wbolster commented on Apr 28, 2016

wbolster commented on Apr 28, 2016

dhermes commented on Apr 29, 2016

jgeewax commented on May 3, 2016

wbolster commented on May 3, 2016

jgeewax commented on May 3, 2016

theacodes commented on May 3, 2016

wbolster commented on Aug 12, 2016

wbolster commented on Aug 12, 2016

31 remaining items

omaray commented on Aug 17, 2016

tseaver commented on Aug 17, 2016

tseaver commented on Aug 17, 2016

theacodes commented on Aug 17, 2016

tseaver commented on Aug 17, 2016

theacodes commented on Aug 17, 2016

tseaver commented on Aug 17, 2016

theacodes commented on Aug 17, 2016

jgeewax commented on Aug 22, 2016

wbolster commented on Sep 7, 2016

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions