Use of git-filter-repo
as a library in my proprietary, commercial and closed-source software
#623
Unanswered
suhasdotcom
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Team,
I want to use the dual-licensed git-filter-repo as a library in my proprietary, commercial and closed-source application, by this I mean:
git-filter-repo is dual licensed as such:
My application project is still in planning phase hence I am experimenting before actual implementation and I do not want to break any license compliances.
There are three main ways in which I plan to use the git-filter-repo software:
Call as a subprocess from my application:
As a library:
This means that I may put
git-filter-repo
as a dependency in my project'spyproject.toml
file, as such (experimental):As source, Copying the git_filter_repo file (this is the only file I am interested in) into my project and then import it:
I need clarification on:
I have already been through:
Using an MIT licensed library in my project.
This question only talks about MIT License and not dual-license and I am not able to understand whether I need to open-source/link the source-code of git-filter-repo alongwith my code's documentation or user manual.
Is it legal to use GPL code in a proprietary, closed-source program by putting it in a separate, standalone program?.
2.a) Do I need to open-source my own application if I used the git-filter-repo as a library or a python import?
2.b) What are my obligations?
How to manage multi-licensed components in a project.
As git-filter-repo is dual-licensed, according to the answer to the question above, can I assume the MIT-license since it looks more permissive towards closed-source proprietary commercial software than GPL?
Any help is appreciated.
Beta Was this translation helpful? Give feedback.
All reactions