Merged
Conversation
Hey Mostafa! Pawel recommends changing the license for xk6 from AGPL-3 to Apache 2.0 because we want to assure users that they are free to execute extensions in all modes: locally, using k6-operator on their own infrastructure and in the k6-cloud. Apache 2.0 license makes this more explicit.
Owner
|
Hey @FloorD, I'm usually not a fan of relicensing to permissive licenses myself, but happy to cooperate. So I'll merge this. |
mostafa
pushed a commit
that referenced
this pull request
May 31, 2022
Relicense from AGPL-3 to Apache 2.0 because k6.io wants to assure users that they are free to execute extensions in all modes: locally, using k6-operator on their own infrastructure and in the k6-cloud. Apache 2.0 license makes this more explicit.
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
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.
Hey Mostafa! Pawel recommends changing the license for xk6 from AGPL-3 to Apache 2.0 because we want to assure users that they are free to execute extensions in all modes: locally, using k6-operator on their own infrastructure and in the k6-cloud. Apache 2.0 license makes this more explicit.