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

Why non-free license? #316

Open
Maniues opened this issue Oct 12, 2023 · 3 comments
Open

Why non-free license? #316

Maniues opened this issue Oct 12, 2023 · 3 comments

Comments

@Maniues
Copy link

Maniues commented Oct 12, 2023

Is there any chance that the specification (and other related projects such as the reference parser) will be released under an open license?

I don't fully understand the attempt to limit specification modifications through licensing. There are many other specifications that can be freely changed without any ill effects.

@mooreb
Copy link

mooreb commented Jan 23, 2024

Under what license is the yaml spec published?

@Maniues
Copy link
Author

Maniues commented Jan 23, 2024

This document may be freely copied, provided it is not modified.

@UnePierre
Copy link

Just a suggestion: if you come across a good solution for a change to said license, how about proposing a pull request?

Just a guess: as long as the team (of which I'm no part) is working on two specs at the same time and doing complicated refactoring (as far as I understand), maybe they want to cut down on the tedious work of unifying spread-out different versions of their work? I mean, I can understand if they want to choose a good level of specification first.

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

3 participants