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

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

Closed
zostay opened this issue Jan 2, 2020 · 2 comments · Fixed by #23
Closed

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

zostay opened this issue Jan 2, 2020 · 2 comments · Fixed by #23
Labels
documentation Improvements or additions to documentation transfer transfer from vim-perl6

Comments

@zostay
Copy link
Collaborator

zostay commented Jan 2, 2020

Migration of vim-perl#18 by @Tyil

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.

@zostay zostay added transfer transfer from vim-perl6 documentation Improvements or additions to documentation labels Jan 2, 2020
@Tyil
Copy link
Member

Tyil commented Jan 2, 2020 via email

@zostay
Copy link
Collaborator Author

zostay commented Jan 2, 2020

I am adding my votes in which are: MIT, (any)

This should be done. I'm going to use a very simple ranked choice voting system to tally votes. As there were up to 4 choices made, I give the first choice of anyone 4 votes, the second choice gets 3 votes, the third 2 votes, and the final just 1 vote. My tallys are as follows:

  1. (Any) 19 votes, 31%
  2. MIT 17 votes, 28%
  3. vim 10 votes, 16%
  4. GPL/GPL 3 8 votes, 13%
  5. ISC 4 votes, 7%
  6. AGPL 4 votes, 7%
  7. BSD 3 votes, 5%

I am reading "(any)" as meaning that any FSF or OSI approved license would be considered reasonable. Therefore, "(any)" and "MIT" make up a plurality, which indicates to me that no runoff is necessary as they hold a plurality together.

Therefore, I will go ahead and add the MIT license to plugin as well as add appropriate documentation elsewhere to that effect. The license need not be set in stone, so if someone disagrees with my logic or the way I counted votes, please comment and we can discuss it.

softmoth added a commit to softmoth/vim-raku that referenced this issue Mar 23, 2021
For choice of MIT license, see poll on issue Raku#6.

For "Raku community", I copied what was in use by the most recent other Raku/* project that doesn't use "The Perl Foundation" or "The Free Software Foundation" (neither of which seems correct here). Unfortunately, that is from a little-known project called github.com/Raku/setup-raku/. Fortunately, it's by Shoichi Kaji, who has a fair amount of experience w/ project management. That being said, if there is any objection it's fine by me to modify it or request a change.
softmoth added a commit to softmoth/vim-raku that referenced this issue Mar 23, 2021
For choice of MIT license, see poll on issue Raku#6.

For "Raku community", I copied what was in use by the most recent other Raku/* project that doesn't use "The Perl Foundation" or "The Free Software Foundation" (neither of which seems correct here). Unfortunately, that is from a little-known project called github.com/Raku/setup-raku/. Fortunately, it's by Shoichi Kaji, who has a fair amount of experience w/ project management. That being said, if there is any objection it's fine by me to modify it or request a change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation transfer transfer from vim-perl6
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants