Dual-license under Apache 2.0 and MIT#34
Merged
stasm merged 1 commit intoprojectfluent:masterfrom Oct 19, 2017
Merged
Conversation
Closed
zbraniecki
approved these changes
Oct 18, 2017
krobelus
added a commit
to krobelus/fluent-langneg-rs
that referenced
this pull request
Oct 21, 2025
Most of fluent-rs is already dual-licensed. This crate is not, which can make it harder for GPL-2-only projects to use fluent-rs. Fix that by allowing use under MIT lincense. All (or almost all?) nontrivial contributions seem to be from the same author, so this should be easy? Ref: projectfluent/fluent-rs#34 Ref: fish-shell/fish-shell#11928
krobelus
added a commit
to krobelus/fluent-langneg-rs
that referenced
this pull request
Oct 21, 2025
Most of fluent-rs is already dual-licensed. This crate is not, which can make it harder for GPL-2-only projects to use fluent-rs. Fix that by allowing use under MIT lincense. All (or almost all?) nontrivial contributions seem to be from the same author, so this should be easy? Ref: projectfluent/fluent-rs#34 Ref: fish-shell/fish-shell#11928 Closes projectfluent#30
4 tasks
krobelus
added a commit
to krobelus/fluent-langneg-rs
that referenced
this pull request
Oct 22, 2025
Most of fluent-rs is already dual-licensed. This crate is not, which can make it harder for GPL-2-only projects to use fluent-rs. Fix that by allowing use under MIT lincense. All (or almost all?) nontrivial contributions seem to be from the same author, so this should be easy? Ref: projectfluent/fluent-rs#34 Ref: fish-shell/fish-shell#11928 Closes projectfluent#30
alerque
pushed a commit
to krobelus/fluent-langneg-rs
that referenced
this pull request
Oct 22, 2025
Most of fluent-rs is already dual-licensed. This crate is not, which can make it harder for GPL-2-only projects to use fluent-rs. Fix that by allowing use under MIT lincense. All (or almost all?) nontrivial contributions seem to be from the same author, so this should be easy? Ref: projectfluent/fluent-rs#34 Ref: fish-shell/fish-shell#11928 See also the previous discussion of relicensing fluent-rs where the same change was made to the other crates: Ref: https://bugzilla.mozilla.org/show_bug.cgi?id=1408992 Co-authored-by: Eemeli Aro <[email protected]> Signed-off-by: Caleb Maclennan <[email protected]>
alerque
pushed a commit
to krobelus/fluent-langneg-rs
that referenced
this pull request
Oct 22, 2025
Most of fluent-rs is already dual-licensed. This crate is not, which can make it harder for GPL-2-only projects to use fluent-rs. Fix that by allowing use under MIT lincense. All (or almost all?) nontrivial contributions seem to be from the same author, so this should be easy? Ref: projectfluent/fluent-rs#34 Ref: fish-shell/fish-shell#11928 See also the previous discussion of relicensing fluent-rs where the same change was made to the other crates: Ref: https://bugzilla.mozilla.org/show_bug.cgi?id=1408992 Co-authored-by: Eemeli Aro <[email protected]> Signed-off-by: Caleb Maclennan <[email protected]> Signed-off-by: Emilio Cobos Álvarez <[email protected]>
alerque
pushed a commit
to krobelus/fluent-langneg-rs
that referenced
this pull request
Oct 23, 2025
Most of fluent-rs is already dual-licensed. This crate is not, which can make it harder for GPL-2-only projects to use fluent-rs. Fix that by allowing use under MIT lincense. All (or almost all?) nontrivial contributions seem to be from the same author, so this should be easy? Ref: projectfluent/fluent-rs#34 Ref: fish-shell/fish-shell#11928 See also the previous discussion of relicensing fluent-rs where the same change was made to the other crates: Ref: https://bugzilla.mozilla.org/show_bug.cgi?id=1408992 Co-authored-by: Eemeli Aro <[email protected]> Signed-off-by: Caleb Maclennan <[email protected]> Signed-off-by: Colin Rofls <[email protected]> Signed-off-by: Emilio Cobos Álvarez <[email protected]> Signed-off-by: Zibi Braniecki <[email protected]>
alerque
pushed a commit
to projectfluent/fluent-langneg-rs
that referenced
this pull request
Oct 23, 2025
Most of fluent-rs is already dual-licensed. This crate is not, which can make it harder for GPL-2-only projects to use fluent-rs. Fix that by allowing use under MIT lincense. All (or almost all?) nontrivial contributions seem to be from the same author, so this should be easy? Ref: projectfluent/fluent-rs#34 Ref: fish-shell/fish-shell#11928 See also the previous discussion of relicensing fluent-rs where the same change was made to the other crates: Ref: https://bugzilla.mozilla.org/show_bug.cgi?id=1408992 Co-authored-by: Eemeli Aro <[email protected]> Signed-off-by: Caleb Maclennan <[email protected]> Signed-off-by: Colin Rofls <[email protected]> Signed-off-by: Emilio Cobos Álvarez <[email protected]> Signed-off-by: Zibi Braniecki <[email protected]>
alerque
pushed a commit
to alerque/fluent-langneg-rs
that referenced
this pull request
Oct 24, 2025
(This was initially released as 0.14.2, but since most fluent-rs crates depend on the 0.13.x series right now this is a backport to clear up any meta data issues in SBOM when using Fluent ecosystem crates.) Most of fluent-rs is already dual-licensed. This crate is not, which can make it harder for GPL-2-only projects to use fluent-rs. Fix that by allowing use under MIT lincense. All (or almost all?) nontrivial contributions seem to be from the same author, so this should be easy? Ref: projectfluent/fluent-rs#34 Ref: fish-shell/fish-shell#11928 See also the previous discussion of relicensing fluent-rs where the same change was made to the other crates: Ref: https://bugzilla.mozilla.org/show_bug.cgi?id=1408992 Co-authored-by: Eemeli Aro <[email protected]> Signed-off-by: Caleb Maclennan <[email protected]> Signed-off-by: Colin Rofls <[email protected]> Signed-off-by: Emilio Cobos Álvarez <[email protected]> Signed-off-by: Zibi Braniecki <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.