vim-jp / vim-jp/vital.vim

License vital.vim under CC0 or WTFPL

Open
#472 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Vim Script
Stars
587
Forks
64
Avg merge
2d 8h
Merged PRs (30d)
1

Description

Currently, vital.vim is released under NYSL.
NYSL is a bit restrictive counterpart of Unlicense in Japan and a tool to insist "my software, public domain".

This license is good for a trivial, private software developed in Japan because the license document was originally written in Japanese and not messed up by a lawyer.

However, NYSL have some problems when a open-source software is released under it.

  1. The NYSL code cannot be used in GPL products, since FSF stated nothing about NYSL.
  2. Nobody knows NYSL is effective as PD outside of Japan as Unlicense.
  3. NYSL is not verified as a open source license.
  4. NYSL has no official documents written in English.
  5. NYSL is no written by a lawyer.

CC0 can resolve all the problems except the third.

List of licenses

  • CC0 waives rights or permits anything if rights cannot be waived.
  • WTFPL permits anything but waives nothing.
  • Unlicense permits anything and waives rights.
  • NYSL allow anything and waives some rights, but the other rights are reserved.
  • No declarations mean all rights are reserved to the author.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no specific file or test; start by locating the repository's current NYSL license declaration and reviewing the unresolved choice between CC0 and WTFPL. Done means replacing the NYSL licensing information with the agreed license and keeping the repository's licensing statements consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
vim
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.