Skip to content

Clarify the scope of open source license #14934

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.

Sign up for GitHub

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

Merged
josevalim merged 1 commit into from
Nov 20, 2025
Merged

Clarify the scope of open source license #14934

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions OPEN_SOURCE_POLICY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,9 @@ These licenses are considered acceptable for any files or code that form part of
an Elixir repository. If a contribution requires a different license, it must
either be rejected or prompt an update to this policy.

## 4. Contributing to Elixir Projects
## 4. Contributing to the Elixir repository

Any code contributed to Elixir repositories must fall under one of the accepted
Any code contributed to the Elixir repository must fall under one of the accepted
licenses (Apache-2.0, Unicode, or Elixir Trademark). Contributions under any
other license will be rejected unless this policy is formally revised to include
that license. All files except those specifically exempted (e.g., certain test
Expand All @@ -51,13 +51,9 @@ configuration and undergo review.

Contributions must not introduce executable binary files into the codebase.

Every Elixir project within the organization will have an automated GitHub
Action to enforce these rules. This mechanism aids in detecting non-compliant
licenses or files early in the review process.
Copy link
Member Author

@josevalim josevalim Nov 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@maennchen I removed this for now, until it is actually reality. It may also not apply to all (such as the website), so we may just list of all of them at the top instead.


## 5. Preservation of Copyright and License Information

Any third-party code incorporated into Elixir projects must retain original
Any third-party code incorporated into the Elixir repository must retain original
copyright and license headers. If no such headers exist in the source, they must
be added. This practice ensures that original authors receive proper credit and
that the licensing lineage is preserved.
Expand Down Expand Up @@ -165,4 +161,4 @@ necessary, by the EEF CISO. Any significant changes will be communicated to
contributors and made publicly available.

*Effective Date: 2025-02-20*
*Last Reviewed: 2025-02-20*
*Last Reviewed: 2025-11-20*