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

License for RFCs #121

Open
Maniues opened this issue May 26, 2024 · 0 comments
Open

License for RFCs #121

Maniues opened this issue May 26, 2024 · 0 comments

Comments

@Maniues
Copy link

Maniues commented May 26, 2024

I propose establishing a license for Haxe RFCs, just like other languages or specifications.

I suggest using:

  • CC-BY 4.0
  • MIT

Since an RFC can contain code samples, you can use CC-BY for the content, MIT for the code samples, CC-BY and MIT for both (dual licensing), or use MIT for the entire RFC at all. A popular strategy in documentation (e.g. MDN) is to license the content and public domain for the code samples (i.e. CC-BY + CC0).

Another option is to adopt CC0 for everything, just as Python adopted the public domain for PEP.

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