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

Why GPL3 for YouCompleteMe and ycmd? #139

tony opened this issue May 22, 2015 · 2 comments

Why GPL3 for YouCompleteMe and ycmd? #139

tony opened this issue May 22, 2015 · 2 comments


Copy link

@tony tony commented May 22, 2015

#21 This discussion here was closed, along with others:

I have a few clarifications directed toward the author, @Valloric . When these is issues are being closed, it gives me the impression these issues seem cut off with little sensitivity to the ramifications for users downstream.

  1. Why did you choose to viral license ycm and youcompleteme?
  2. Are you aware that one of the primary reasons behind LLVM / Clang's stakeholder's incubating it was to avoid viral licensing, namely, GPLv3 in gcc/gdb?
  3. Are you aware of the ramifications of how permissively licensed projects and their users have to go out of their way to reinvent the wheel so as to not risk cross-contamination with GPL?
Copy link

@oblitum oblitum commented May 22, 2015

IMO, I think it's good to have this stated short and simple for reference without much further discussion. Personally, I think there's no big issue regarding cross-contamination with a client/server model since new clients, even with permissive licenses, can request their users to download the server or link to it as a submodule. And I think the client being GPL does more good than harm. This project is not part of LLVM and libclang completion is just one of the several completers.

Copy link

@Valloric Valloric commented May 22, 2015

I closed and locked those issues (as I will close and lock this one) because discussing something that can't be changed is pointless and a waste of everyone's time. Would I have picked Apache v2 instead of GPL v3 if I were doing this again? Most likely. But that doesn't change the fact that YCM will remain GPL v3; we can't change it now for so many reasons.

Please don't start new issues about this; you are just wasting your time and mine.

@Valloric Valloric closed this May 22, 2015
@ycm-core ycm-core locked and limited conversation to collaborators May 22, 2015
tony added a commit to tony/vim-config-framework that referenced this issue May 23, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants