Repository Transfer

[lmangani]

This community repository contains my own work and was hosted on my personal github and not part of chdb or its codebase. I was convinced to host this (and other) personal repositories with chdb integrations under the chdb-io organization with a written warranty I could fully manage them, and sadly this is no longer the case as of today.

@auxten @alexey-milovidov for fairness and since I never signed any CLA for this code/repo for which I am the principal author and maintainer alongside my friends and colleagues as anyone can see, I am formally and kindly asking you here in public to migrate this repo back to the rightful owner (my username) as soon as possible, so I can continue my (blocked) development for the community and for other projects using this resource.

Note this project actions are linked to external resources I personally own and still contains my private access tokens.
Feel free by all means to fork it and contribute if useful for chdb, although I'm sure you will not need this in the future.

[lmangani]

Sadly 48 hours later, no response, no contacts and my code is still seized by strangers.
At least this public post will help people understand, but I would urge those involved to act fast(er)

@alexey-milovidov IMHO you should be the one working the hardest to resolve this situation. Silence speaks too.

[ghenry]

Have you had a chat with the Apache Foundation or FSF? Both have very helpful legal departments.

Either way, this is not very professional behaviour by those you mention nor the organisations that they represent. All existing and future contributors should be made aware of this history.

No community == No product

[alijared]

You can clearly see @lmangani as the primary contributor here... It's sad to see a large company take away something designed by a community, for a community with the spirit of open source, and then even refuse a simple request. Especially when there is a potential security risk with access tokens and the like.

They need to take responsibility. @ghenry's suggestion seems like a good avenue to consider pursuing