This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
Update License of Alizer #176
Assignees
Labels
area/documentation
All issues related to documentation updates, corrections or bugs
Comments
openshift-ci
bot
added
the
area/documentation
|
UPDATE: We can create a PR with the new license and inform all previous contributors to review and agree on. |
|
UPDATE: A PR and will discuss the onboarding of alizer to devfiles project during the 8th may community call. |
|
UPDATE: The onboarding has been mentioned during the community call. Now we have to reach out to all contributors for license update |
|
I've contacted all contributors via email and asked to approve the license update :) |
|
I've sent reminders to people who haven't replied yet to my emails |
|
All contributors have agreed with the re-licensing :) |
github-project-automation
bot
moved this from Review in Progress
to Done
in Alizer Project
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which area this feature is related to?
/area documentation
Issue details
As a part of the #166 EPIC we need to update the license of Alizer before the onboarding to devfiles org.
The current license is Eclipse Public License 2.0 which is actually the case of
redhat-developerorganization.On the other hand, the devfiles org uses the Apache License. More information can be found in the CNCF Proposal Issue and a license related PR.
Target Date: 13 June 2023
The text was updated successfully, but these errors were encountered: