javascript-tutorial / javascript-tutorial/en.javascript.info

LICENSE page inconsistency

Aberta
#2,924 1 comentário 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Linguagem predominante
HTML
Estrelas
25.5k
Forks
4k
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

Hello, the LICENSE page has two conflicts or inconsistencies that I can see.

The "SHORT" description says: "The license is basically [CC-BY-NC](https://creativecommons.org/licenses/by-nc/4.0/legalcode), revocable and exclusive."

Yet this conflicts with the full Legal license below:
...
"Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to:"
...

Here would be my suggestions as a humble potential user:
1. Suggestion "please get a permission from Ilya Kantor" to "we request that you please inform Ilya Kantor of your intended usage"
(Reasoning: This is confusing. Is the repo under CC-BY-NC, or is not? is it CC-BY-NC **AND** IK's permission? Do I just need IK's permission, and I can ignore the CC-BY-NC?)

2. Suggestion:
Change "The license is basically [CC-BY-NC](https://creativecommons.org/licenses/by-nc/4.0/legalcode),revocable and exclusive."
To "The license is unmodified [CC-BY-NC](https://creativecommons.org/licenses/by-nc/4.0/legalcode)."

This is very very very confusing. The original CC-BY-NC is both "non-exclusive,and irrevocable"
Have you modified the terms of the CC-BY-NC? If so, why didn't you change the words in the Legal description?

Anyway, you think this is a good idea:
1. Remove confusion about CC-BY-NC license, or CC-BY-NC+IK' permission license.
2. Remove confusion about conflicting language between Short and Legal description.
3. Follow the original, unmodified CC-BY-NC license, which is "non-exclusive,and irrevocable".

Should I submit a PR to see if you like these ideas?

definitions:

"exclusive" means you have agreed to the receive, that they should be the only person/company that you are giving a license to.

"non-exclusive" means you are granting them a license, but you keep the right to give the license to other people/companies. (this is the norm in open-source and default in CC-BY-NC)

"revocable" means you can cancel/terminate the license you previously gave to others. some people won't use your open source software in this case because it is too risky to invest the time.

"irrevocable" means you cannot cancel/terminate the license you previously gave to others. (this is the norm in open-source and default in CC-BY-NC)

Please let me know if I should submit a PR

Guia de contribuição

Nenhum guia de contribuição indexado para este repositório

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Direção de pesquisa

Comece lendo as seções SHORT e Legal da página LICENSE e compare o texto citado da CC-BY-NC com o texto completo. Considera-se concluído quando o mantenedor seleciona e aprova um texto que remova o conflito sobre permissão, exclusividade, revogabilidade e a relação com a CC-BY-NC; nenhum caminho de arquivo ou teste é fornecido.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Domínio
documentation
Tipo de issue
Documentação
Dificuldade
4/5
Tempo estimado
3-5 dias
Status de atividade
Estagnada
Clareza
Razoavelmente clara
Facilidade para iniciantes
38/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.