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

Open license #333

Open
Maniues opened this issue Jun 14, 2024 · 0 comments
Open

Open license #333

Maniues opened this issue Jun 14, 2024 · 0 comments

Comments

@Maniues
Copy link

Maniues commented Jun 14, 2024

Hello,
I would like to ask about the YAML specification license. I know it states, "This document may be freely copied, provided it is not modified."
I want to start a discussion about this. This

license has several issues:

  1. What does "copied" mean? Copied publicly, like including it in the documentation of a YAML implementation or redistributing the YAML specification on a website? Or does it only refer to private copies?
  2. "Provided it is not modified" is a VERY restrictive and problematic condition. Why?May I (under this license, not under fair use or something) cite this specification (provided that "copied" means I can make public copies) or only make full specification copies?
  3. Contributing to YAML. With this restriction, nobody can legally send you pull requests. I think I don't have to explain why this is not a good thing.
  4. New versions of YAML. When one copyright owner restricts modification, the next version of the YAML specification must be approved for redistribution by ANY previous contributor. This is impractical.
  5. Open source projects. This restriction is not popular in Free and Open Source Projects nor approved by OSI and FSF for use in this kind of project.
  6. Use of reference parsers. Reference parsers are based on this specification DIRECTLY, which means their use is restricted by this license. So, any project that derives from reference parsers is illegal.

What do I propose instead? A CC-BY license or a liberal code license like MIT.

If you want to restrict the use of this specification, there is CC-BY-SA, but it is copyleft, so any project that uses reference parsers must be used under this license (which is not designed for software), so I don't recommend it.

Let me know what you think about this. I hope the discussion will start even if the license won't be changed.

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

No branches or pull requests

1 participant