Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: relicense under MIT/Apache 2.0 #841

Merged
merged 1 commit into from
Mar 12, 2023
Merged

docs: relicense under MIT/Apache 2.0 #841

merged 1 commit into from
Mar 12, 2023

Conversation

arxanas
Copy link
Owner

@arxanas arxanas commented Mar 12, 2023

No description provided.

See #813 for discussion and assent from major contributors to relicense git-branchless. From that link:

> Hi everyone, as you may know, git-branchless was licensed as GPL-2.0-only so that it could use Sapling SCM's DAG implementation (see #65). It was always my intention to license the program source code itself more permissively, but the resulting program (when linked against a GPL library) becomes GPL-licensed as a whole. This is confusing to explain and implement, so I simply licensed the whole program under GPL 2.0.
>
> The DAG library is licensed as MIT as of v0.3.0. After upgrading, we will no longer have any GPL dependencies. I am proposing that we relicense git-branchless to a dual MIT/Apache-2.0 license, so that we can reuse components in other systems such as Jujutsu (i.e. copy and paste some code one day). I've already started writing smaller modules licensed under MIT/Apache-2.0 to that end.
@arxanas arxanas enabled auto-merge (rebase) March 12, 2023 01:11
@arxanas arxanas merged commit fe2c999 into master Mar 12, 2023
@arxanas arxanas deleted the arxanas/docs2 branch March 12, 2023 01:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant