Hacker News new | ask | show | jobs
by ewy1 4 days ago
pretty dystopian to ask a robot to recreate your favorite software just so you can relicense it for your business venture
1 comments

We're choosing a license that is usable by the entire community. Our goal is a linkable library, which makes GPL impossible. If we had chosen to go with LGPL or GPL with linking exception (like libgit2), it would have the same issue of changing the license, so we went with whatever was the most permissive so everyone could use it for anything if they wish. This has nothing to do with business - I hope I can get the project to the point where Jujutsu or whomever can use whatever is valuable here for whatever they want.

We clearly learned from how Git does operations and emulated it in order to function interoperably, the same way that Gitoxide and libgit2 have, and released it under a license that would be the most valuable for people wanting to use a linkable library, the same way that Gitoxide and libgit2 have.

> Our goal is a linkable library, which makes GPL impossible

Not impossible. It forces the code using the library to be under a GPL-compatible license and requires the binary to be released under the GPL license.

The distinction is quite important. It's only impossible in the mind of someone who wants to release proprietary software. Even for people releasing software under permissive license it's not impossible, just highly inconvenient (and the LGPL is always an option in this case).

>We're choosing a license that is usable by the entire community.

What a weaselly way to put it.

A GPL library, as I'm sure you know, is perfectly usable by anyone including jujutsu and anyone else. They just have to also license under the GPL and this is no barrier to open source projects.

I love how he uses the word "community", effectively washing away what is really happening which is taking a community protected asset and turning it into a corporate one.

Ok, my coffee just kicked in and I'm incensed. Might go do an FSF donation.

> We clearly learned from how Git does operations and emulated it in order to function interoperably

So you didn't just let an AI go nuts with access to the source code of Git so as to produce a derivative work?

> We're choosing a license that is usable by the entire community. Our goal is a linkable library, which makes GPL impossible.

And what issues did GPL impose on the community all these 21 years of git existence?