Skip to content
This repository has been archived by the owner on Jan 2, 2020. It is now read-only.

Add a LICENSE file (and refer to it in the README) #18

Open
Tyil opened this issue Mar 21, 2018 · 17 comments
Open

Add a LICENSE file (and refer to it in the README) #18

Tyil opened this issue Mar 21, 2018 · 17 comments

Comments

@Tyil
Copy link
Contributor

Tyil commented Mar 21, 2018

Description of issue

This project currently does not carry a LICENSE. In the spirit of free software I'd like it to adopt a free license clearly in the project root. If possible, refer to the license in the README.md as well.

Since this is something we should decide with all contributors, all of them have been tagged in this issue. Please respond to this issue with the license you are OK with to put on this codebase.

License votes

Contributor License options
@0racle
@atweiden
@blueyed (Any)
@cfa (Any)
@eiro
@grondilu MIT, GPL, vim
@hinrik vim, MIT, GPL, BSD
@hoelzro
@itchyny MIT, (Any)
@KrisShannon
@petdance vim
@samcv (Any)
@simmel ISC, MIT,BSD, (Any)
@Tyil AGPL-3.0, GPL-3.0
@Util
@hoelzro
Copy link
Member

hoelzro commented Mar 23, 2018

@Tyil this is a great idea - I wonder if we technically need contributors' permission first? If not, would you mind drafting a PR to add this to the repo?

@Tyil
Copy link
Contributor Author

Tyil commented Mar 24, 2018

I would've drafter a PR already, but I'm not sure what license it would fall under. I'm personally a big fan of (A)GPL, but I'm not sure what you or other contributors would think about that.

Since the project is currently unlicensed, that mean everyone has to agree on the license picked as well if I'm correct. But I'm not a lawyer, so don't take it as legal advice. I'd like input from all contributors anyway, since it is a community project after all.

@hoelzro
Copy link
Member

hoelzro commented Mar 24, 2018

I think the typical choice for Vimscript is the Vim license itself - I think that you may be right about the "everyone must agree" part =/

@Tyil
Copy link
Contributor Author

Tyil commented Mar 24, 2018

It's 15 contributors. What would be the best way to contact them? Just send everyone an email and hope they respond? We can tag them each in the issue as well, perhaps they'll get a notification about that too.

@hoelzro
Copy link
Member

hoelzro commented Mar 26, 2018

I guess let's try tagging them in this issue - otherwise, trying e-mail would be a good idea.

@Tyil
Copy link
Contributor Author

Tyil commented Mar 26, 2018

ping @0racle, @atweiden, @blueyed, @cfa, @eiro, @grondilu, @hinrik, @itchyny, @KrisShannon, @petdance, @samcv, @simmel, @Util

Please respond with your LICENSE options for this codebase.

@simmel
Copy link
Contributor

simmel commented Mar 26, 2018

I'd prefer a permissive license like ISC, MIT or BSD but I can cave in if everyone else wants something different.

@blueyed
Copy link
Contributor

blueyed commented Mar 26, 2018

I am fine with any open license - have not checked, but my contribution is probably very small anyway.

@itchyny
Copy link
Contributor

itchyny commented Mar 26, 2018

Good idea to add LICENSE. Personally I'm a fan of MIT but I'll follow the decision of main contributors. My change to this repo is just a nitpick.

@petdance
Copy link
Contributor

Seems to me that we should use whatever license Vim uses, especially if this gets folded into the main vim distribution.

@cfa
Copy link
Contributor

cfa commented Mar 26, 2018

I'm happy with anything—my contribution was minor.

@hoelzro
Copy link
Member

hoelzro commented Mar 26, 2018

FWIW, choosing something other than the Vim license might limit our ability to have changes to this incorporated with the upstream Vim project.

@petdance
Copy link
Contributor

There would have to be a pretty strong argument to NOT use Vim's license.

@grondilu
Copy link
Contributor

I'm ok with MIT, GPL or whatever Vim uses,

@hinrik
Copy link
Contributor

hinrik commented Mar 27, 2018

Any of the mentioned choices (Vim, MIT, GPL, BSD...) are fine by me.

@Tyil
Copy link
Contributor Author

Tyil commented Mar 27, 2018

First half of the contributors have responded, thanks for your feedback thus far people!

@samcv
Copy link
Contributor

samcv commented Mar 27, 2018

I'm ok with any any OSI approved software license.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants